mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. About quick start tutorials If you are creating quick start tutorials for the Red Hat OpenShift Service on AWS web console, follow these guidelines to maintain a consistent user experience across all quick starts. 7.1. Understanding quick starts A quick start is a guided tutorial with user tasks. In the web console, you can access quick starts under the Help menu. They are especially useful for getting oriented with an application, Operator, or other product offering. A quick start primarily consists of tasks and steps. Each task has multiple steps, and each quick start has multiple tasks. For example: Task 1 Step 1 Step 2 Step 3 Task 2 Step 1 Step 2 Step 3 Task 3 Step 1 Step 2 Step 3 7.2. Quick start user workflow When you interact with an existing quick start tutorial, this is the expected workflow experience: In the Administrator or Developer perspective, click the Help icon and select Quick Starts . Click a quick start card. In the panel that appears, click Start . Complete the on-screen instructions, then click . In the Check your work module that appears, answer the question to confirm that you successfully completed the task. If you select Yes , click to continue to the task. If you select No , repeat the task instructions and check your work again. Repeat steps 1 through 6 above to complete the remaining tasks in the quick start. After completing the final task, click Close to close the quick start. 7.3. Quick start components A quick start consists of the following sections: Card : The catalog tile that provides the basic information of the quick start, including title, description, time commitment, and completion status Introduction : A brief overview of the goal and tasks of the quick start Task headings : Hyper-linked titles for each task in the quick start Check your work module : A module for a user to confirm that they completed a task successfully before advancing to the task in the quick start Hints : An animation to help users identify specific areas of the product Buttons and back buttons : Buttons for navigating the steps and modules within each task of a quick start Final screen buttons : Buttons for closing the quick start, going back to tasks within the quick start, and viewing all quick starts The main content area of a quick start includes the following sections: Card copy Introduction Task steps Modals and in-app messaging Check your work module

Commands:
Chapter 7. Director test This test, also known as openstack/director, ensures that the deployment-under-test is originally installed using RHOSP Director. This test is required for all OpenStack software certifications. Red Hat OpenStack Platform (RHOSP) Director is the supported toolset for installing and managing a RHOSP environment in production. It helps in easy installation of a lean and robust OpenStack cloud and is targeted specifically for enterprise cloud environments where updates, upgrades and infrastructure control are critical for underlying OpenStack operations. Success criteria The deployment under test is originally installed using Red Hat OpenStack Platform Director. Additional resources For more information about installing RHOSP Director, see Director Installation and Usage Guide .

Commands:
function::tz_ctime Name function::tz_ctime - Convert seconds since epoch into human readable date/time string, with local time zone Synopsis Arguments epochsecs number of seconds since epoch (as returned by gettimeofday_s ) Description Takes an argument of seconds since the epoch as returned by gettimeofday_s . Returns a string of the same form as ctime , but offsets the epoch time for the local time zone, and appends the name of the local time zone. The string length may vary. The time zone information is passed by staprun at script startup only.

Commands:
tz_ctime(epochsecs:)
Chapter 1. Postinstallation configuration overview After installing OpenShift Container Platform, a cluster administrator can configure and customize the following components: Machine Bare metal Cluster Node Network Storage Users Alerts and notifications 1.1. Post-installation configuration tasks You can perform the post-installation configuration tasks to configure your environment to meet your need. The following lists details these configurations: Configure operating system features : The Machine Config Operator (MCO) manages MachineConfig objects. By using the MCO, you can configure nodes and custom resources. Configure bare metal nodes : You can use the Bare Metal Operator (BMO) to manage bare metal hosts. The BMO can complete the following operations: Inspects hardware details of the host and report them to the bare metal host. Inspect firmware and configure BIOS settings. Provision hosts with a desired image. Clean disk contents for the host before or after provisioning the host. Configure cluster features . You can modify the following features of an OpenShift Container Platform cluster: Image registry Networking configuration Image build behavior Identity provider The etcd configuration Machine set creation to handle the workloads Cloud provider credential management Configuring a private cluster : By default, the installation program provisions OpenShift Container Platform by using a publicly accessible DNS and endpoints. To make your cluster accessible only from within an internal network, configure the following components to make them private: DNS Ingress Controller API server Perform node operations : By default, OpenShift Container Platform uses Red Hat Enterprise Linux CoreOS (RHCOS) compute machines. You can perform the following node operations: Add and remove compute machines. Add and remove taints and tolerations. Configure the maximum number of pods per node. Enable Device Manager. Configure users : OAuth access tokens allow users to authenticate themselves to the API. You can configure OAuth to perform the following tasks: Specify an identity provider Use role-based access control to define and supply permissions to users Install an Operator from OperatorHub Configuring alert notifications : By default, firing alerts are displayed on the Alerting UI of the web console. You can also configure OpenShift Container Platform to send alert notifications to external systems.

Commands:
18.3. Unmounting a File System To detach a previously mounted file system, use either of the following variants of the umount command: Note that unless this is performed while logged in as root , the correct permissions must be available to unmount the file system (see Section 18.2.2, "Specifying the Mount Options" ). See Example 18.9, "Unmounting a CD" for an example usage. Important When a file system is in use (for example, when a process is reading a file on this file system, or when it is used by the kernel), running the umount command will fail with an error. To determine which processes are accessing the file system, use the fuser command in the following form: For example, to list the processes that are accessing a file system mounted to the /media/cdrom/ directory, type: Example 18.9. Unmounting a CD To unmount a CD that was previously mounted to the /media/cdrom/ directory, type the following at a shell prompt:

Commands:
umount directory umount device
fuser -m directory
~]USD fuser -m /media/cdrom /media/cdrom: 1793 2013 2022 2435 10532c 10672c
~]USD umount /media/cdrom
Chapter 3. Kafka 4 impact and adoption schedule Streams for Apache Kafka 3.0 is scheduled for release in 2025. The introduction of Apache Kafka 4 in the release brings significant changes to how Kafka clusters are deployed, configured, and operated. For more information on how these changes affect the Streams for Apache Kafka 3.0 release, refer to the article Streams for Apache Kafka 3.0: Kafka 4 Impact and Adoption .

Commands:
Chapter 2. Creating the first administrator After installing Red Hat Single Sign-On, you need an administrator account that can act as a super admin with full permissions to manage all parts of Red Hat Single Sign-On. With this account, you can log into the Red Hat Single Sign-On Admin Console where you create realms and users and register applications that are secured by Red Hat Single Sign-On. Prerequisites Perform the installation and configuration tasks defined in the Server Installation and Configuration Guide to the point that the Red Hat Single Sign-On server is running. 2.1. Creating the account on the local host If your server is accessible from localhost , perform these steps. Procedure In a web browser, go to the http://localhost:8080/auth URL. Supply a username and password that you can recall. Welcome page 2.2. Creating the account remotely If you cannot access the server from a localhost address, or just want to start Red Hat Single Sign-On from the command line, use the ... /bin/add-user-keycloak script. Add-user-keycloak script The parameters are a little different depending if you are using the standalone operation mode or domain operation mode. For standalone mode, here is how you use the script. Linux/Unix Windows The generated file is owned by a different user than the Red Hat Single Sign-On running user. Use this command to set the permissions so the Red Hat Single Sign-On user can read the file upon restarting the server. chgrp jboss /opt/rh/rh-sso7/root/usr/share/keycloak/standalone/configuration/keycloak-add-user.json For domain mode, you have to point the script to one of your server hosts using the -sc switch. Linux/Unix Windows

Commands:
.../bin/add-user-keycloak.sh -r master -u <username> -p <password>
> ...\bin\add-user-keycloak.bat -r master -u <username> -p <password>
chgrp jboss /opt/rh/rh-sso7/root/usr/share/keycloak/standalone/configuration/keycloak-add-user.json
.../bin/add-user-keycloak.sh --sc domain/servers/server-one/configuration -r master -u <username> -p <password>
> ...\bin\add-user-keycloak.bat --sc domain/servers/server-one/configuration -r master -u <username> -p <password>
23.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: postfix_local_write_mail_spool Having this Boolean enabled allows Postfix to write to the local mail spool on the system. Postfix requires this Boolean to be enabled for normal operation when local spools are used. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
2.7. Clustering corosync component, BZ# 722469 A double ring failure results in the spinning of the corosync process. Also, because DLM relies on SCTP, which is non-functional, many features of the cluster software that rely on DLM do not work properly. luci component, BZ# 615898 luci will not function with Red Hat Enterprise Linux 5 clusters unless each cluster node has ricci version 0.12.2-14

Commands:
6.2. I/O Scheduling with Red Hat Enterprise Linux as a Virtualization Host When using Red Hat Enterprise Linux as a host for virtualized guests, the default cfq scheduler is usually ideal. This scheduler performs well on nearly all workloads. However, if minimizing I/O latency is more important than maximizing I/O throughput on the guest workloads, it may be beneficial to use the deadline scheduler. The deadline scheduler is also the scheduler used by the tuned profile virtual-host .

Commands:
Chapter 7. Kernel Kernel dumps are now reliably generated under high memory load Previously, if a kernel panic occurred under high memory load, a deadlock in some cases occurred and a kernel dump was not generated. This update fixes the vmalloc_sync_all() function to avoid waiting on a spinlock that may be never released. As a result, the kernel dump is collected correctly. (BZ#1146727) Runqueues no longer ignore clock updates Previously, runqueues on systems with overcommitment of CPUs were prone to ignoring clock updates for extended periods of time. As a consequence, the real-time runqueues were limited, which prevented critical tasks and their dependant tasks from running. This update ensures that the runqueues do not ignore clock updates for extended periods of time. As a result, critical tasks and their dependant tasks are able to run in such situations. (BZ#1212959) dma_pin_iovec_pages() no longer causes the system out of memory Previously, when the dma_pin_iovec_pages() function requested a large amount of memory but the request failed, it was unable to release the memory that was reserved. As a consequence, the system run out of memory. With this update, dma_pin_iovec_pages() now allocates the full amount of memory correctly and releases the memory when it is not needed. As a result, the described problem no longer occurs. (BZ#1459263) A cgroups deadlock has been fixed In certain circumstances when using cgroups , a system deadlock occurred due to a race condition. This update adds a work queue that fixes the race condition, which prevents the deadlock from happening. (BZ#1463754) Audit of unsuccessful execve() now works properly Previously, the audit call in the Linux kernel used the arguments of its parent process when logging arguments of an unsuccessful execve() system call. As a consequence, audit was able to use pointers to non-mapped addresses, and the process terminated with a segmentation fault. With this update, audit has been fixed to reinstate the check for the failed execve() . As a result, processes no longer terminate erroneously after unsuccessful execve() . (BZ#1488822) vmcp now successfuly executes cp Previously, the kernel memory allocation using the GFP_DMA flag caused the vmcp command to fail to execute the cp command. This update removes the need to use GFP_DMA and allows the GFP_KERNEL flag to allocate the kernel memory instead. As a result, vmcp succeeds to execute cp . (BZ#1496105)

Commands:
Chapter 5. Test the Configured Back End After deploying the back end, test whether you can successfully create volumes on it. Doing so will require loading the necessary environment variables first. These variables are defined in /home/stack/overcloudrc by default. To load these variables, run the following command as the stack user: Note For more information, see Accessing the Overcloud . You should now be logged in to the Controller node. From there, you can create a volume type , which can be used to specify the back end you want to use (in this case, the newly-defined back end in Chapter 3, Define a Single Back End ). This is required in an OpenStack deployment where you have other back ends enabled (preferably, also through Director). To create a volume type named dellps , run: , map this volume type to the back end defined in ]. Given the back end name tripleo_dellps (as defined through the CinderDellPsBackendName parameter, in xref:edityaml[ ), run: You should now be able to create a 2GB volume on the newly defined back end by invoking its volume type. To do so, run:

Commands:
source /home/stack/overcloudrc
cinder type-create dellps
cinder type-key dellps set volume_backend_name=tripleo_dellps
cinder create --volume-type dellps 2
Chapter 7. Configuring AWS billing plans For more information about AWS billing, see Understanding Consolidated Bills in the AWS documentation. Cost management supports three cost calculation options to accommodate AWS billing plans: Unblended Your costs are calculated according to your usage cost for that date. Amortized (Default) Your recurring and upfront costs will be distributed evenly throughout the billing period. Blended Your costs are calculated according to AWS blended rates. This procedure describes how to set your cost calculation to Amortized or Blended from the default Unblended . Prerequisites Access to Red Hat Hybrid Cloud Console as an Organization Administrator. Procedure From Red Hat Hybrid Cloud Console , navigate to the cost management settings page. Under Show cost as select Amortized or Blended . Click Save .

Commands:
8.96. iptables 8.96.1. RHBA-2014:1547 - iptables bug fix and enhancement update Updated iptables packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The iptables utility controls the network packet filtering code in the Linux kernel. Bug Fixes BZ# 1059214 Previously, when alternative packages were removed manually, it was impossible to uninstall the iptables-ipv6 packages. The underlying source code has been patched, and iptables-ipv6 can now be uninstalled regardless of manually modified alternatives. BZ# 1070123 When upgrading the Red Hat Enterprise Linux 6.5 minimal installation to version 7.0 using the redhat-upgrade-tool utility, the "%postun" scriptlet of iptables-ipv6 failed. Blocks preventing the old package from uninstalling have been removed, and iptables-ipv6 can now be uninstalled successfully. In addition, this update adds the following Enhancement BZ# 1033270 With this update, IPv6 support has been added to the ipset utility, and thus the user can now manage IPSets of IPv6 addresses. Users of iptables are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 7. Red Hat Enterprise Linux Atomic Host 7.7.4 7.1. Atomic Host OStree update : New Tree Version: 7.7.4 (hash: 422dc6900aa50ce4fb23adee368890e770007a644addb0558e23cfb52d4efd26) Changes since Tree Version 7.7.3 (hash: 5e5cf3cb9a7ddcdcb31391935f339b29cc8bb72c195bd61caa3462fb2462aa37) 7.2. Extras New packages : python-jmespath-0.9.0-6.el7_7 Updated packages : python-docker-py-1.10.6-11.el7 rhel-system-roles-1.0-10.el7_7 containernetworking-plugins-0.8.1-4.el7_7 7.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.7 Container Image (rhel7.7, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Universal Base Image 7 Container Image (rhel7/ubi7) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) Red Hat Universal Base Image 7 Minimal Container Image (rhel7/ubi7-minimal)

Commands:
Appendix C. Reverting Satellite Server to Download Content from Red Hat CDN If your environment changes from disconnected to connected, you can reconfigure a disconnected Satellite Server to download content directly from the Red Hat CDN. Procedure In the Satellite web UI, navigate to Content > Subscriptions . Click the Manage Manifest button. Switch to the CDN Configuration tab. Select Red Hat CDN . Edit the URL field to point to the Red Hat CDN URL: https://cdn.redhat.com Click Update . Satellite Server is now configured to download content from the Red Hat CDN the time that it synchronizes repositories. CLI Procedure Log in to the Satellite Server using SSH. Use Hammer to reconfigure the CDN:

Commands:
hammer organization configure-cdn --name=" My_Organization " --type=redhat_cdn
7.179. perl-SOAP-Lite 7.179.1. RHBA-2012:1388 - perl-SOAP-Lite bug fix update An updated perl-SOAP-Lite package that fixes one bug is now available for Red Hat Enterprise Linux 6. SOAP::Lite is a collection of Perl modules, which provides a simple and lightweight interface to the Simple Object Access Protocol (SOAP) both on client and server side. Bug Fix BZ# 748376 XMLRPC requests could fail if the MOD_PERL environment value was defined. The standard read() function is now used instead of the sysread() function when MOD_PERL is defined. As a result, XMLRPC no longer fails in this scenario. All users of perl-SOAP-Lite are advised to upgrade to this updated package, which fixes this bug.

Commands:
14.9.4. Rebooting a Guest Virtual Machine Use the virsh reboot command to reboot a guest virtual machine. The prompt will return once the reboot has executed. Note that there may be a time lapse until the guest virtual machine returns. You can control the behavior of the rebooting guest virtual machine by modifying the <on_reboot> element in the guest virtual machine's configuration file. Refer to Section 20.12, "Events Configuration" for more information. By default, the hypervisor will try to pick a suitable shutdown method. To specify an alternative method, the --mode option can specify a comma separated list which includes initctl , acpi , agent , and signal . The order in which drivers will try each mode is not related to the order specified in the command. For strict control over ordering, use a single mode at a time and repeat the command.

Commands:
#virsh reboot {domain-id, domain-name or domain-uuid} [--mode method ]
Chapter 3. Deploying the configured back ends To deploy the configured back ends, complete the following steps: Log in as the stack user. Run the following command to deploy the custom back end configuration: Important If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud. For more information, see Modifying the overcloud environment in the Director Installation and Usage guide.

Commands:
openstack overcloud deploy --templates -e /home/stack/templates/custom-env.yaml
probe::tcpmib.RetransSegs Name probe::tcpmib.RetransSegs - Count the retransmission of a TCP segment Synopsis tcpmib.RetransSegs Values op value to be added to the counter (default value of 1) sk pointer to the struct sock being acted on Description The packet pointed to by skb is filtered by the function tcpmib_filter_key . If the packet passes the filter is is counted in the global RetransSegs (equivalent to SNMP's MIB TCP_MIB_RETRANSSEGS)

Commands:
B.95. tdb-tools B.95.1. RHEA-2011:1430 - new packages: tdb-tools New tdb-tools packages are now available for Red Hat Enterprise Linux 6. The tdb-tools packages contain tools that can be used to backup and manage tdb files created by Samba. BZ# 717689 This enhancement update adds the tdb-tools packages to Red Hat Enterprise Linux 6. All tdb users who wish to backup and manage tdb files are advised to install these new packages.

Commands: