mtpti5iD/redhat-docs_dataset huggingface dataset:
1.3.2. Tell Your Users What You Are Doing This step is primarily a last-minute warning of the impending change; as such, it should be a brief repeat of the first message, though with the impending nature of the change made more apparent ("The system upgrade will take place TONIGHT."). This is also a good place to publicly answer any questions you may have received as a result of the first message. Continuing our hypothetical example, here is one possible last-minute warning: System Downtime Scheduled for Tonight Reminder: The system downtime announced this past Monday will take place as scheduled tonight at 6pm (midnight for the Berlin office). You can find the original announcement on the company intranet website, on the System Administration page. Several people have asked whether they should stop working early tonight to make sure their work is backed up prior to the downtime. This will not be necessary, as the work being done tonight will not impact any work done on your personal workstations. Remember, those of you that have written your own SQL queries should be aware that the layout of some indices will change. This is documented on the company intranet website, on the Finance page. Your users have been alerted; now you are ready to actually do the work.

Commands:
Chapter 4. Managing Red Hat Cluster With Conga This chapter describes various administrative tasks for managing a Red Hat Cluster and consists of the following sections: Section 4.1, "Starting, Stopping, and Deleting Clusters" Section 4.2, "Managing Cluster Nodes" Section 4.3, "Managing High-Availability Services" Section 4.4, "Diagnosing and Correcting Problems in a Cluster" 4.1. Starting, Stopping, and Deleting Clusters You can perform the following cluster-management functions through the luci server component of Conga : Restart a cluster. Start a cluster. Stop a cluster. Delete a cluster. To perform one of the functions in the preceding list, follow the steps in this section. The starting point of the procedure is at the cluster tab (at the Choose a cluster to administer page). At the right of the Cluster Name for each cluster listed on the Choose a cluster to administer page is a drop-down box. By default, the drop-down box is set to Restart this cluster . Clicking the drop-down box box reveals all the selections available: Restart this cluster , Stop this cluster / Start this cluster , and Delete this cluster . The actions of each function are summarized as follows: Restart this cluster - Selecting this action causes the cluster to be restarted. You can select this action for any state the cluster is in. Stop this cluster / Start this cluster - Stop this cluster is available when a cluster is running. Start this cluster is available when a cluster is stopped. Selecting Stop this cluster shuts down cluster software in all cluster nodes. Selecting Start this cluster starts cluster software. Delete this cluster - Selecting this action halts a running cluster, disables cluster software from starting automatically, and removes the cluster configuration file from each node. You can select this action for any state the cluster is in. Deleting a cluster frees each node in the cluster for use in another cluster. Select one of the functions and click Go . Clicking Go causes a progress page to be displayed. When the action is complete, a page is displayed showing either of the following pages according to the action selected: For Restart this cluster and Stop this cluster / Start this cluster - Displays a page with the list of nodes for the cluster. For Delete this cluster - Displays the Choose a cluster to administer page in the cluster tab, showing a list of clusters.

Commands:
Chapter 12. Security Fixed ordering in the output of semanage fcontext -l Previously, the semanage fcontext -l command did not print SELinux rules in the order in which the user added them and the restorecon utility used them. This could pose problems when managing SELinux rules, because the order in which the rules were displayed to the user did not match the order in which restorecon executed them. A patch has been applied to fix this problem, and semanage fcontext -l now displays the rules in the correct and expected order. (BZ# 1206767 )

Commands:
B.21.4. RHSA-2011:0373 - Important: firefox security update Updated firefox packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. Mozilla Firefox is an open source web browser. XULRunner provides the XUL Runtime environment for Mozilla Firefox. Security Issue BZ# 689430 This erratum blacklists a small number of HTTPS certificates. All Firefox users should upgrade to these updated packages, which contain a backported patch. After installing the update, Firefox must be restarted for the changes to take effect.

Commands:
4.107. java-1.6.0-ibm 4.107.1. RHSA-2012:0514 - Critical: java-1.6.0-ibm security update Updated java-1.6.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM Java SE version 6 release includes the IBM Java 6 Runtime Environment and the IBM Java 6 Software Development Kit. Security Fixes CVE-2011-3563 , CVE-2011-5035 , CVE-2012-0497 , CVE-2012-0498 , CVE-2012-0499 , CVE-2012-0500 , CVE-2012-0501 , CVE-2012-0502 , CVE-2012-0503 , CVE-2012-0505 , CVE-2012-0506 , CVE-2012-0507 This update fixes several vulnerabilities in the IBM Java 6 Runtime Environment and the IBM Java 6 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. All users of java-1.6.0-ibm are advised to upgrade to these updated packages, containing the IBM Java 6 SR10-FP1 release. All running instances of IBM Java must be restarted for the update to take effect. 4.107.2. RHSA-2012:0034 - Critical: java-1.6.0-ibm security update Updated java-1.6.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM Java SE version 6 release includes the IBM Java 6 Runtime Environment and the IBM Java 6 Software Development Kit. Security Fixes CVE-2011-3389 , CVE-2011-3516 , CVE-2011-3521 , CVE-2011-3544 , CVE-2011-3545 , CVE-2011-3546 , CVE-2011-3547 , CVE-2011-3548 , CVE-2011-3549 , CVE-2011-3550 , CVE-2011-3551 , CVE-2011-3552 , CVE-2011-3553 , CVE-2011-3554 , CVE-2011-3556 , CVE-2011-3557 , CVE-2011-3560 , CVE-2011-3561 This update fixes several vulnerabilities in the IBM Java 6 Runtime Environment and the IBM Java 6 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. All users of java-1.6.0-ibm are advised to upgrade to these updated packages, containing the IBM Java 6 SR10 release. All running instances of IBM Java must be restarted for the update to take effect.

Commands:
Chapter 58. Hardware Enablement The i40e driver rejects the most general HWTSTAMP filter Because of disabling L4 timestamping (UDP) in the security fix for Intel Ethernet Controller X710 and XL710 family described in the INTEL-SA-00063 advisory, the i40e device driver rejects the most general HWTSTAMP filter. This problem only affects the Intel X710 devices, not the newer X722 device. (BZ#1431964)

Commands:
4.10. ePowerSwitch Table 4.11, "ePowerSwitch" lists the fence device parameters used by fence_eps , the fence agent for ePowerSwitch. Table 4.11. ePowerSwitch luci Field cluster.conf Attribute Description Name name A name for the ePowerSwitch device connected to the cluster. IP Address or Hostname ipaddr The IP address or host name assigned to the device. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Name of Hidden Page hidden_page The name of the hidden page for the device. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Port (Outlet) Number port Physical plug number or name of virtual machine. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Figure 4.9, "ePowerSwitch" shows the configuration screen for adding an ePowerSwitch fence device. Figure 4.9. ePowerSwitch The following command creates a fence device instance for an ePowerSwitch device: The following is the cluster.conf entry for the fence_eps device:

Commands:
ccs -f cluster.conf --addfencedev epstest1 agent=fence_eps ipaddr=192.168.0.1 login=root passwd=password123 hidden_page=hidden.htm
<fencedevices> <fencedevice agent="fence_eps" hidden_page="hidden.htm" ipaddr="192.168.0.1" login="root" name="epstest1" passwd="password123"/> </fencedevices>
3.7. Active-State Power Management Active-State Power Management (ASPM) saves power in the Peripheral Component Interconnect Express (PCI Express or PCIe) subsystem by setting a lower power state for PCIe links when the devices to which they connect are not in use. ASPM controls the power state at both ends of the link, and saves power in the link even when the device at the end of the link is in a fully powered-on state. When ASPM is enabled, device latency increases because of the time required to transition the link between different power states. ASPM has three policies to determine power states: default sets PCIe link power states according to the defaults specified by the firmware on the system (for example, BIOS). This is the default state for ASPM. powersave sets ASPM to save power wherever possible, regardless of the cost to performance. performance disables ASPM to allow PCIe links to operate with maximum performance. You can forcibly enable or disable ASPM support by using the pcie_aspm kernel parameter: pcie_aspm=off disables ASPM pcie_aspm=force enables ASPM, even on devices that do not support ASPM If the hardware supports ASPM, the operating system enables ASPM automatically at boot time. To check the ASPM support, see the output of the following command: Warning If you forcibly enable ASPM by using pcie_aspm=force on hardware that does not support ASPM, the system might become unresponsive. Before setting pcie_aspm=force , ensure that all PCIe hardware on the system supports ASPM. To set the ASPM policies, use one of the following options: modify the settings in the /sys/module/pcie_aspm/parameters/policy file specify the pcie_aspm.policy kernel parameter at boot time For example, pcie_aspm.policy=performance sets the ASPM performance policy.

Commands:
~]USD journalctl -b | grep ASPM
4.9. Kernel Memory Type Range Register (MTRR) setup on some hyperthreaded machines may be incorrect following a suspend/resume cycle. This can cause graphics performance (specifically, scrolling) to slow considerably after a suspend/resume cycle. To work around this issue, disable and then re-enable the hyperthreaded sibling CPUs around suspend/resume, for example: Loading the megaraid_sas driver on the kdump kernel will result in the insmod command being blocked, returning messages similar to: Refer to BZ#682110 for more information. In Red Hat Enterprise Linux 6.1, the nmi_watchdog registers with the perf subsystem. Consequently, during boot, the perf subsystem grabs control of the performance counter registers, blocking oprofile from working. To resolve this, either boot with the nmi_watchdog=0 kernel parameter set, or run echo 0 > /proc/sys/kernel/nmi_watchdog to disable at run time. To re-enable the watchdog, use the command echo 1 > /proc/sys/kernel/nmi_watchdog . Due to the way ftrace works when modifying the code during startup, the NMI watchdog causes too much noise and ftrace can not find a quiet period to instrument the code. Consequently, machines with more than 512 cpus will encounter issues with the NMI watchdog. Such issues will return error messages similar to "BUG: NMI Watchdog detected LOCKUP" and have either 'ftrace_modify_code' or 'ipi_handler' in the backtrace. To work around this issue, disable nmi_watchdog using the command: Creating many 'cpu' control groups (cgroups) on a system with a large number of CPUs will slow down the machine when the control groups feature is enabled. To work around this issue, disable control groups. On 64-bit POWER systems the EHEA NIC driver will fail when attempting to dump a vmcore via NFS. To work around this issue, utilize other kdump facilities, for example dumping to the local filesystem, or dumping over SSH. A BIOS emulated floppy disk might cause the installation or kernel boot process to hang. To avoid this, disable emulated floppy disk support in the BIOS. The preferred method to enable nmi_watchdog on 32-bit x86 systems is to use either nmi_watchdog=2 or nmi_watchdog=lapic parameters. The parameter nmi_watchdog=1 is not supported. The kernel parameter, pci=noioapicquirk , is required when installing the 32 bit variant of Red Hat Enterprise Linux 6 on HP xw9300 workstations. Note that the parameter change is not required when installing the 64 bit variant. On IBM PowerPC systems, the exec-shield value in sysctl or /proc/sys/kernel/exec-shield parameter is not enforced.

Commands:
#!/bin/sh Disable hyper-threading processor cores on suspend and hibernate, re-enable on resume. This file goes into /etc/pm/sleep.d/ case USD1 in hibernate|suspend) echo 0 > /sys/devices/system/cpu/cpu1/online echo 0 > /sys/devices/system/cpu/cpu3/online ;; thaw|resume) echo 1 > /sys/devices/system/cpu/cpu1/online echo 1 > /sys/devices/system/cpu/cpu3/online ;; esac
INFO: task insmod:201 blocked for more than 120 seconds.
nmi_watchdog=0
Chapter 11. Configuring burst and QPS for net-kourier The queries per second (QPS) and burst values determine the frequency of requests or API calls to the API server. 11.1. Configuring burst and QPS values for net-kourier The queries per second (QPS) value determines the number of client requests or API calls that are sent to the API server. The burst value determines how many requests from the client can be stored for processing. Requests exceeding this buffer will be dropped. This is helpful for controllers that are bursty and do not spread their requests uniformly in time. When the net-kourier-controller restarts, it parses all ingress resources deployed on the cluster, which leads to a significant number of API calls. Due to this, the net-kourier-controller can take a long time to start. You can adjust the QPS and burst values for the net-kourier-controller in the KnativeServing CR: KnativeServing CR example apiVersion: operator.knative.dev/v1beta1 kind: KnativeServing metadata: name: knative-serving namespace: knative-serving spec: workloads: - name: net-kourier-controller env: - container: controller envVars: - name: KUBE_API_BURST value: "200" 1 - name: KUBE_API_QPS value: "200" 2 1 The QPS rate of communication between controller and the API Server. The default value is 200. 2 The burst capacity of communication between Kubelet and the API Server. The default value is 200.

Commands:
apiVersion: operator.knative.dev/v1beta1 kind: KnativeServing metadata: name: knative-serving namespace: knative-serving spec: workloads: - name: net-kourier-controller env: - container: controller envVars: - name: KUBE_API_BURST value: "200" 1 - name: KUBE_API_QPS value: "200" 2
4.3.10. Combining Volume Groups Two combine two volume groups into a single volume group, use the vgmerge command. You can merge an inactive "source" volume with an active or an inactive "destination" volume if the physical extent sizes of the volume are equal and the physical and logical volume summaries of both volume groups fit into the destination volume groups limits. The following command merges the inactive volume group my_vg into the active or inactive volume group databases giving verbose runtime information.

Commands:
vgmerge -v databases my_vg
14.8.8. Updating the Domain XML File that will be Used for Restoring the Guest The virsh save-image-define file xml --running | --paused command will update the domain XML file that will be used when the specified file is later used during the virsh restore command. The xml argument must be an XML file name containing the alternative XML with changes only in the host physical machine specific portions of the domain XML. For example, it can be used to account for the file naming differences resulting from creating disk snapshots of underlying storage after the guest was saved. The save image records if the domain should be restored to a running or paused state. Using the options --running or --paused dictates the state that is to be used.

Commands:
Chapter 9. Removing Windows nodes You can remove a Windows node by deleting its host Windows machine. 9.1. Deleting a specific machine You can delete a specific machine. Note You cannot delete a control plane machine. Prerequisites Install an OpenShift Container Platform cluster. Install the OpenShift CLI ( oc ). Log in to oc as a user with cluster-admin permission. Procedure View the machines that are in the cluster by running the following command: USD oc get machine -n openshift-machine-api The command output contains a list of machines in the <clusterid>-<role>-<cloud_region> format. Identify the machine that you want to delete. Delete the machine by running the following command: USD oc delete machine <machine> -n openshift-machine-api Important By default, the machine controller tries to drain the node that is backed by the machine until it succeeds. In some situations, such as with a misconfigured pod disruption budget, the drain operation might not be able to succeed. If the drain operation fails, the machine controller cannot proceed removing the machine. You can skip draining the node by annotating machine.openshift.io/exclude-node-draining in a specific machine. If the machine that you delete belongs to a machine set, a new machine is immediately created to satisfy the specified number of replicas.

Commands:
oc get machine -n openshift-machine-api
oc delete machine <machine> -n openshift-machine-api
Chapter 7. Action scripts Action scripts are pieces of code that define the Script property or the interceptor action of an element. Action scripts can access the global variables, process variables, and predefined variable kcontext . kcontext is an instance of the ProcessContext interface. For more information about kcontext variable, see the ProcessContext Javadoc . Java and MVEL are supported as dialects for action script definitions. MVEL accepts valid Java code and additionally provides support for nested access to parameters. For example, the MVEL call person.name is equivalent of Java call person.getName() . Example action script in Java and MVEL dialects You can also use action scripts to view information about process instances. For example, use the following commands to: Return the ID of a process instance: Return the parent process instance ID if a process instance has a parent: Return the ID of a process definition related to a process instance: Return the name of a process definition related to a process instance: Return the state of a process instance: To set a process variable in an action script, use kcontext.setVariable("VARIABLE_NAME", "VALUE") .

Commands:
// Java dialect System.out.println(person.getName()); // MVEL dialect System.out.println(person.name);
System.out.println(kcontext.getProcessInstance().getId());
System.out.println(kcontext.getProcessInstance().getParentProcessInstanceId());
System.out.println(kcontext.getProcessInstance().getProcessId());
System.out.println(kcontext.getProcessInstance().getProcessName());
System.out.println(kcontext.getProcessInstance().getState());
Chapter 2. Configuring Red Hat Identity management You can configure Red Hat OpenStack Platform with federated user management with the following features: Red Hat Identity Management (IdM) is external to Red Hat OpenStack Platform Red Hat IdM is the source of all user and group information Red Hat Single Signon (RH-SSO) is configured to use Red Hat IdM for user Federation 2.1. Creating the IdM service account for RH-SSO If you use anonomous binds, some information that is essential for Red Hat Single Sign-On (RH-SSO) is withheld for security reasons. As a result, you need provide the appropriate privileges for RH-SSO in the forma a dedicated account to query the IdM LDAP server for this information: Note You can use the configure-federation script to perform the above step: USD ./configure-federation create-ipa-service-account 2.2. Creating a test user Create a user account in IdM for testing: Procedure Create a user jdoe in IdM: Assign a password to the user: 2.3. Creating an IdM group for OpenStack users You must have an IdM group openstack-users to map to the Keystone group federated_users . Map the test user to this group. Create the openstack-users group in Red Hat Identity Management (IdM): Procedure Ensure that the openstack-users group does not exist: Add the openstack-users group to IdM: Add the test users to the openstack-users group: Verify that the openstack-users group exists and has the test user as a member:

Commands:
LDAP_URL="ldaps://USDFED_IPA_HOST" DIR_MGR_DN="cn=Directory Manager" SERVICE_NAME="rhsso" SERVICE_DN="uid=USDservice_name,cn=sysaccounts,cn=etc,USDFED_IPA_BASE_DN" ldapmodify -H "USD{LDAP_URL}" -x -D "USD{DIR_MGR_DN}" -w <_FED_IPA_ADMIN_PASSWD_> <<EOF dn: USD{SERVICE_DN} changetype: add objectclass: account objectclass: simplesecurityobject uid: USD{SERVICE_NAME} userPassword: <_FED_IPA_RHSSO_SERVICE_PASSWD_> passwordExpirationTime: 20380119031407Z nsIdleTimeout: 0 EOF
USDipa user-add --first John --last Doe --email jdoe@example.com jdoe
USDipa passwd jdoe
ipa group-show openstack-users ipa: ERROR: openstack-users: group not found
ipa group-add openstack-users
ipa group-add-member --users jdoe openstack-users
ipa group-show openstack-users Group name: openstack-users GID: 331400001 Member users: jdoe