mtpti5iD/redhat-docs_dataset huggingface dataset:
8.3.2. Backup Sites: Cold, Warm, and Hot One of the most important aspects of disaster recovery is to have a location from which the recovery can take place. This location is known as a backup site . In the event of a disaster, a backup site is where your data center will be recreated, and where you will operate from, for the length of the disaster. There are three different types of backup sites: Cold backup sites Warm backup sites Hot backup sites Obviously these terms do not refer to the temperature of the backup site. Instead, they refer to the effort required to begin operations at the backup site in the event of a disaster. A cold backup site is little more than an appropriately configured space in a building. Everything required to restore service to your users must be procured and delivered to the site before the process of recovery can begin. As you can imagine, the delay going from a cold backup site to full operation can be substantial. Cold backup sites are the least expensive sites. A warm backup site is already stocked with hardware representing a reasonable facsimile of that found in your data center. To restore service, the last backups from your off-site storage facility must be delivered, and bare metal restoration completed, before the real work of recovery can begin. Hot backup sites have a virtual mirror image of your current data center, with all systems configured and waiting only for the last backups of your user data from your off-site storage facility. As you can imagine, a hot backup site can often be brought up to full production in no more than a few hours. A hot backup site is the most expensive approach to disaster recovery. Backup sites can come from three different sources: Companies specializing in providing disaster recovery services Other locations owned and operated by your organization A mutual agreement with another organization to share data center facilities in the event of a disaster Each approach has its good and bad points. For example, contracting with a disaster recovery firm often gives you access to professionals skilled in guiding organizations through the process of creating, testing, and implementing a disaster recovery plan. As you might imagine, these services do not come without cost. Using space in another facility owned and operated by your organization can be essentially a zero-cost option, but stocking the backup site and maintaining its readiness is still an expensive proposition. Crafting an agreement to share data centers with another organization can be extremely inexpensive, but long-term operations under such conditions are usually not possible, as the host's data center must still maintain their normal production, making the situation strained at best. In the end, the selection of a backup site is a compromise between cost and your organization's need for the continuation of production.

Commands:
20.2.5. Using an FCP-attached SCSI DVD Drive This requires to have a SCSI DVD drive attached to an FCP-to-SCSI bridge which is in turn connected to an FCP adapter in your System z machine. The FCP adapter has to be configured and available in your LPAR. Insert your Red Hat Enterprise Linux for System z DVD into the DVD drive. Double-click Load . In the dialog box that follows, select SCSI as the Load type . As Load address fill in the device number of the FCP channel connected with the FCP-to-SCSI bridge. As World wide port name fill in the WWPN of the FCP-to-SCSI bridge as a 16-digit hexadecimal number. As Logical unit number fill in the LUN of the DVD drive as a 16-digit hexadecimal number. As Boot program selector fill in the number 1 to select the boot entry on the Red Hat Enterprise Linux for System z DVD. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty. Click the OK button.

Commands:
Chapter 6. Known issues This section provides information about known issues in Ansible Automation Platform 2.5. 6.1. Ansible Automation Platform Added the podman_containers_conf_logs_max_size variable for containers.conf to control the max log size for Podman installations. The default value is 10 MiB. (AAP-12295) Setting the pg_host= value without any other context no longer results in an empty HOST section of the settings.py in the automation controller. As a workaround, delete the pg_host= value or set it to pg_host='' . (AAP-31915) Using Prompt on launch for variables for job templates, workflow job templates, workflow visualizer nodes, and schedules will not show the default variables when launching the job, or when configuring the workflows and schedules. (AAP-30585) The unused ANSIBLE_BASE_ settings are included as environment variables in the job execution. These variables suffixed with SECRET are no longer used in the Ansible Automation Platform and might be ignored until they are removed in a future patch. (AAP-32208) 6.2. Event-Driven Ansible mTLS event stream creation should be disallowed on all installation methods by default. It is currently disallowed on OpenShift Container Platform installation, but not disallowed in the containerized installations or on RPM installations. (AAP-31337) If a primary Redis node enters a failed state and a new primary node is promoted, Event-Driven Ansible workers and scheduler are unable to reconnect to the cluster. This causes activations to fail until the containers or pods are recycled. (AAP-30722) For more information, see the KCS article Redis failover causes Event-Driven Ansible activation failures . 6.3. Ansible plug-ins for Red Hat Developer Hub Python VS Code extension v2024.14.1 does not work in OpenShift Dev Spaces version 1.9.3, prohibiting the Ansible VS Code extension from loading. As a workaround, downgrade the Python VS Code extension version to 2024.12.3. The Ansible Content Creator Get Started page links do not work in OpenShift Dev Spaces version 1.9.3. As a workaround, use the Ansible VS Code Command Palette to access the features.

Commands:
3.10. Configuring Cluster Storage To configure storage for a cluster, click the storage tab. Clicking that tab causes the display of the Welcome to Storage Configuration Interface page. The storage tab allows you to monitor and configure storage on remote systems. It provides a means for configuring disk partitions, logical volumes (clustered and single system use), file system parameters, and mount points. The storage tab provides an interface for setting up shared storage for clusters and offers GFS and other file systems as file system options. When a you select the storage tab, the Welcome to Storage Configuration Interface page shows a list of systems available to the you in a navigation table to the left. A small form allows you to choose a storage unit size to suit your preference. That choice is persisted and can be changed at any time by returning to this page. In addition, you can change the unit type on specific configuration forms throughout the storage user interface. This general choice allows you to avoid difficult decimal representations of storage size (for example, if you know that most of your storage is measured in gigabytes, terabytes, or other more familiar representations). Additionally, the Welcome to Storage Configuration Interface page lists systems that you are authorized to access, but currently are unable to administer because of a problem. Examples of problems: A computer is unreachable via the network. A computer has been re-imaged and the luci server admin must re-authenticate with the ricci agent on the computer. A reason for the trouble is displayed if the storage user interface can determine it. Only those computers that the user is privileged to administer is shown in the main navigation table. If you have no permissions on any computers, a message is displayed. After you select a computer to administer, a general properties page is displayed for the computer. This page is divided into three sections: Hard Drives Partitions Volume Groups Each section is set up as an expandable tree, with links to property sheets for specific devices, partitions, and storage entities. Configure the storage for your cluster to suit your cluster requirements. If you are configuring Red Hat GFS, configure clustered logical volumes first, using CLVM. For more information about CLVM and GFS refer to Red Hat documentation for those products. Note Shared storage for use in Red Hat Cluster Suite requires that you be running the cluster logical volume manager daemon ( clvmd ) or the High Availability Logical Volume Management agents (HA-LVM). If you are not able to use either the clvmd daemon or HA-LVM for operational reasons or because you do not have the correct entitlements, you must not use single-instance LVM on the shared disk as this may result in data corruption. If you have any concerns please contact your Red Hat service representative.

Commands:
Preface Red Hat Fuse provides two enterprise monitoring tools for viewing and managing Fuse integrations: The Fuse Console is a web-based console that you access from a browser to monitor and manage a running Fuse container. The Fuse Console is based on Hawtio open source software ( https://hawt.io/ ). This guide describes how to use the Fuse Console. Prometheus stores system and integration-level metrics for Fuse distributions. You can use a graphical analytics interface, such as Grafana, to view and analyze the stored historical data. To learn more about using Prometheus, see the Prometheus documentation . The audience for this guide is Red Hat Fuse on JBoss EAP administrators. This guide assumes that you are familiar with the Red Hat Fuse platform, Apache Camel, and the processing requirements for your organization.

Commands:
6.9. RHEA-2013:0341 - new package: scipy New scipy packages are now available for Red Hat Enterprise Linux 6. The SciPy package provides software for mathematics, science, and engineering. The NumPy package, which is designed to manipulate large multi-dimensional arrays of arbitrary records, is the core library for SciPy. The SciPy library is built to work with NumPy arrays and provides various efficient numerical routines, for example routines for numerical integration and optimization. This enhancement update adds the scipy packages to Red Hat Enterprise Linux 6. (BZ# 697530 ) All users who require scipy are advised to install these new package.

Commands:
7.231. wpa_supplicant 7.231.1. RHSA-2015:1439 - Low: wpa_supplicant security and enhancement update An updated wpa_supplicant package that fixes one security issue and adds one enhancement is now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The wpa_supplicant package contains an 802.1X Supplicant with support for WEP, WPA, WPA2 (IEEE 802.11i / RSN), and various EAP authentication methods. It implements key negotiation with a WPA Authenticator for client stations and controls the roaming and IEEE 802.11 authentication and association of the WLAN driver. Security Fix CVE-2015-4142 An integer underflow flaw, leading to a buffer over-read, was found in the way wpa_supplicant handled WMM Action frames. A specially crafted frame could possibly allow an attacker within Wi-Fi radio range to cause wpa_supplicant to crash. Enhancement BZ# 1186806 Prior to this update, wpa_supplicant did not provide a way to require the host name to be listed in an X.509 certificate's Common Name or Subject Alternative Name, and only allowed host name suffix or subject substring checks. This update introduces a new configuration directive, 'domain_match', which adds a full host name check. All wpa_supplicant users are advised to upgrade to this updated package, which contains a backported patch to correct this issue and adds this enhancement. After installing this update, the wpa_supplicant service will be restarted automatically.

Commands:
Resource Management Guide Red Hat Enterprise Linux 7 Using cgroups to manage system resources on RHEL 7 Marie Dolezelova Red Hat Customer Content Services mdolezel@redhat.com Milan Navratil Red Hat Customer Content Services Eva Majorsinova Red Hat Customer Content Services Peter Ondrejka Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Martin Prpic Red Hat Product Security Rudiger Landmann Red Hat Customer Content Services

Commands:
B.98. tuned B.98.1. RHBA-2010:0847 - tuned bug fix update Updated tuned packages that fix profiles performing I/O scheduler changes. Tuned is a utility for tuning system performance and power-consumption. Various profiles are available. Bug Fix BZ# 638975 Prior to this update, I/O scheduler changes were not applied to device mapper (dm) devices, which affected the enterprise-storage, latency-performance and throughput-performance profiles. This error has been fixed, device mapper devices have been added to the "ELEVATOR_TUNE_DEVS" list, and I/O scheduler changes are now applied to all devices as expected. All users of tuned are advised to upgrade to these updated packages, which resolve this issue.

Commands:
7.7. Searching the Audit Log Files The ausearch utility allows you to search Audit log files for specific events. By default, ausearch searches the /var/log/audit/audit.log file. You can specify a different file using the ausearch options -if file_name command. Supplying multiple options in one ausearch command is equivalent to using the AND operator between field types and the OR operator between multiple instances of the same field type. Example 7.7. Using ausearch to Search Audit Log Files To search the /var/log/audit/audit.log file for failed login attempts, use the following command: To search for all account, group, and role changes, use the following command: To search for all logged actions performed by a certain user, using the user's login ID ( auid ), use the following command: To search for all failed system calls from yesterday up until now, use the following command: For a full listing of all ausearch options, see the ausearch (8) man page.

Commands:
~]# ausearch --message USER_LOGIN --success no --interpret
~]# ausearch -m ADD_USER -m DEL_USER -m ADD_GROUP -m USER_CHAUTHTOK -m DEL_GROUP -m CHGRP_ID -m ROLE_ASSIGN -m ROLE_REMOVE -i
~]# ausearch -ua 1000 -i
~]# ausearch --start yesterday --end now -m SYSCALL -sv no -i
Chapter 4. Bookmarks 4.1. Saving a Query String as a Bookmark A bookmark can be used to remember a search query, and shared with other users. Saving a Query String as a Bookmark Enter the desired search query in the search bar and perform the search. Click the star-shaped Bookmark button to the right of the search bar to open the New Bookmark window. Enter the Name of the bookmark. Edit the Search string field, if required. Click OK . Click the Bookmarks icon ( ) in the header bar to find and select the bookmark.

Commands:
7.32. crash 7.32.1. RHBA-2015:1309 - crash bug fix and enhancement update Updated crash packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The crash packages provide the core analysis suite, which is a self-contained tool that can be used to investigate live systems, as well as kernel core dumps created by the kexec-tools packages or the Red Hat Enterprise Linux kernel. Note The crash packages have been upgraded to upstream version 7.1.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1111357 ) Bug Fixes BZ# 1179480 A prior update of the AMD64 and Intel 64 kernels removed the STACKFAULT exception stack. As a consequence, using the "bt" command with the updated kernels previously displayed an incorrect exception stack name if the backtrace originated in an exception stack other than STACKFAULT. In addition, the "mach" command displayed incorrect names for exception stacks other than STACKFAULT. This update ensures that stack names are generated properly in the described circumstances, and both "bt" and "mach" now display correct information. BZ# 1208557 Attempting to run the crash utility with the vmcore and vmlinux files previously caused crash to enter an infinite loop and became unresponsive. With this update, the handling of errors when gathering tasks from pid_hash[] chains during session initialization has been enhanced. Now, if a pid_hash[] chain has been corrupted, the patch prevents the initialization sequence from entering an infinite loop. This prevents the described failure of the crash utility from occurring. In addition, the error messages associated with corrupt or invalid pid_hash[] chains have been updated to report the pid_hash[] index number. BZ# 1073987 On certain system configurations, the "kmem -f", "kmem -F", and "kmem [address]" command options previously took a very long time to complete. This update increases the internal hash queue size used to store the address of each free page, and streamlines the free page search to only check the NUMA node that contains a specified address. As a result, the mentioned "kmem" options no longer have a negative impact on performance. Enhancement BZ# 1195596 The makedumpfile command now supports the new sadump format that can represent more than 16 TB of physical memory space. This allows users of makedumpfile to read dump files over 16 TB, generated by sadump on certain upcoming server models. Users of crash are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
16.3. Methods 16.3.1. Creating a Floating Disk When creating a new floating disk, the API requires the size and storage_domains elements. Example 16.2. Creating a new a floating disk device

Commands:
POST /ovirt-engine/api/disks HTTP/1.1 Accept: application/xml Content-type: application/xml <disk> <storage_domains> <storage_domain id="fabe0451-701f-4235-8f7e-e20e458819ed"/> </storage_domains> <size>8589934592</size> <type>system</type> <interface>virtio</interface> <format>cow</format> </disk>
Chapter 11. The InitializingScoreTrend class You can add the InitializingScoreTrend class to optimization algorithms to specify how the score changes when additional variables are initialized and the already-initialized variables do not change. Some optimization algorithms, such Construction Heuristics and Exhaustive Search, run faster when this information is available. You can specify one of the following trends for the score or each score level separately: ANY (default): Initializing an extra variable can change the score positively or negatively. This trend does not provide a performance gain. ONLY_UP (rare): Initializing an extra variable can only change the score positively. The ONLY_UP trend requires the following conditions: There are only positive constraints. Initializing the variable cannot unmatch a positive constraint that was matched by a initialized variable. ONLY_DOWN : Initializing an additional variable can only change the score negatively. ONLY_DOWN requires the following conditions: There are only negative constraints. Initializing the variable cannot unmatch a negative constraint that was matched by a initialized variable. Most use cases have only negative constraints. Many of those use cases have an InitializingScoreTrend class that only goes down, as shown in the following example: <scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.cloudbalancing.score.CloudBalancingConstraintProvider</constraintProviderClass> <initializingScoreTrend>ONLY_DOWN</initializingScoreTrend> </scoreDirectorFactory> Alternatively, you can also specify the trend for each score level separately, as shown in the following example: <scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.cloudbalancing.score.CloudBalancingConstraintProvider</constraintProviderClass> <initializingScoreTrend>ONLY_DOWN/ONLY_DOWN</initializingScoreTrend> </scoreDirectorFactory>

Commands:
<scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.cloudbalancing.score.CloudBalancingConstraintProvider</constraintProviderClass> <initializingScoreTrend>ONLY_DOWN</initializingScoreTrend> </scoreDirectorFactory>
<scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.cloudbalancing.score.CloudBalancingConstraintProvider</constraintProviderClass> <initializingScoreTrend>ONLY_DOWN/ONLY_DOWN</initializingScoreTrend> </scoreDirectorFactory>
Chapter 4. Installing Red Hat Enterprise Linux To use RHUI efficiently and to access Red Hat repositories and support, you must first install Red Hat Enterprise Linux (RHEL) on each of your RHUA, CDS, and HAProxy nodes. Prerequisite Make sure you have the latest version of RHEL 8 available, either as an ISO or as a subscription. Procedure Navigate to the node on which you wish to install RHEL. Install RHEL. For detailed instructions on how to install RHEL, see Performing a standard RHEL 8 installation .

Commands:
Chapter 8. Frequently asked questions Is it possible to deploy applications from OpenShift Dev Spaces to an OpenShift cluster? OpenShift user token is automatically injected into workspace containers which makes it possible to run oc CLI commands against OpenShift cluster. For best performance, what is the recommended storage to use for Persistent Volumes used with OpenShift Dev Spaces? Use block storage. Is it possible to deploy more than one OpenShift Dev Spaces instance on the same cluster? Only one OpenShift Dev Spaces instance can be deployed per cluster. Is it possible to install OpenShift Dev Spaces offline (that is, disconnected from the internet)? See Installing Red Hat OpenShift Dev Spaces in restricted environments on OpenShift . Is it possible to use non-default certificates with OpenShift Dev Spaces? You can use self-signed or public certificates. See Importing untrusted TLS certificates . Is it possible to run multiple workspaces simultaneously? See Enabling users to run multiple workspaces simultaneously .

Commands:
26.4. Changing the Certificate Chain You can modify the certificate chain by renewing the CA certificate using the ipa-cacert-manage renew . Self-signed CA certificate externally-signed CA certificate Add the --external-ca option to ipa-cacert-manage renew . This renews the self-signed CA certificate as an externally-signed CA certificate. For details on running the command with this option, see Section 26.2.2, "Renewing CA Certificates Manually" . Externally-signed CA certificate self-signed CA certificate Add the --self-signed option to ipa-cacert-manage renew . This renew the externally-signed CA certificate as a self-signed CA certificate.

Commands: