mtpti5iD/redhat-docs_dataset huggingface dataset:
4.24. IPMI over LAN The fence agents for IPMI over LAN ( fence_ipmilan ,) Dell iDRAC ( fence_idrac ), IBM Integrated Management Module ( fence_imm ), HP iLO3 devices ( fence_ilo3 ), and HP iLO4 devices ( fence_ilo4 ) share the same implementation. Table 4.25, "IPMI (Intelligent Platform Management Interface) LAN, Dell iDrac, IBM Integrated Management Module, HPiLO3, HPiLO4" lists the fence device parameters used by these agents. Table 4.25. IPMI (Intelligent Platform Management Interface) LAN, Dell iDrac, IBM Integrated Management Module, HPiLO3, HPiLO4 luci Field cluster.conf Attribute Description Name name A name for the fence 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 of a user capable of issuing power on/off commands to the given port. Password passwd The password used to authenticate the connection to the port. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Authentication Type auth Authentication type: none , password , or MD5 . Use Lanplus lanplus True or 1 . If blank, then value is False . It is recommended that you enable Lanplus to improve the security of your connection if your hardware supports it. Ciphersuite to use cipher The remote server authentication, integrity, and encryption algorithms to use for IPMIv2 lanplus connections. Privilege level privlvl The privilege level on the device. IPMI Operation Timeout timeout Timeout in seconds for IPMI operation. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. The default value is 2 seconds for fence_ipmilan , fence_idrac , fence_imm , and fence_ilo4 . The default value is 4 seconds for fence_ilo3 . Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Method to Fence method The method to fence: on/off or cycle Figure 4.19, "IPMI over LAN" shows the configuration screen for adding an IPMI over LAN device Figure 4.19. IPMI over LAN The following command creates a fence device instance for an IPMI over LAN device: The following is the cluster.conf entry for the fence_ipmilan device:

Commands:
ccs -f cluster.conf --addfencedev ipmitest1 agent=fence_ipmilan auth=password cipher=3 ipaddr=192.168.0.1 lanplus=on login=root passwd=password123
<fencedevices> <fencedevice agent="fence_ipmilan" auth="password" cipher="3" ipaddr="192.168.0.1" lanplus="on" login="root" name="ipmitest1" passwd="password123"/> </fencedevices>
4.2. abrt and libreport 4.2.1. RHBA-2011:1598 - abrt and libreport bug fix and enhancement update Updated abrt and libreport packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The abrt packages contain the Automatic Bug Reporting Tool (ABRT) version 2. In comparison with ABRT version 1, this version provides more flexible configuration, which covers a variety of customer use cases that the version was unable to cover. It also moves a lot of data processing from the daemon to separate tools that run without root privileges, which makes the daemon less error prone and the whole processing more secure. Note: This update obsoletes the former report tool and replaces the report library to unify the reporting process in all Red Hat applications (Anaconda, setroubleshoot, ABRT). The most interesting feature for end-users is the problem solution searching: when ABRT is configured to report to the Red Hat Customer Portal, it tries to search Red Hat problem databases (such as Knowledge Base or Bugzilla) for possible solutions and refers the user to these resources if the solution is found. Bug Fixes BZ# 610603 The abrt-gui application used to list plug-ins multiple times if they were configured in the configuration file. This is now fixed. BZ# 627621 In the version of ABRT, a daemon restart was required for any changes in the configuration to take effect. In the new version, most of the options in the configuration file no longer require a restart. BZ# 653872 Support for retrace server has been added. Refer to https://fedorahosted.org/abrt/wiki/AbrtRetraceServer for more information about this new feature. BZ# 671354 By default, ABRT stores all problem information in the /var/spool/abrt/ directory. Previously, this path was hard coded and could not be changed in the configuration. With this update, this path can be changed in the /etc/abrt/abrt.conf configuration file. BZ# 671359 The documentation failed to cover some customer use cases. This error has been fixed, and all of these use cases are now covered in the Red Hat Enterprise Linux 6 Deployment Guide. BZ# 673173 In ABRT version 1, it was not possible to use wildcards to specify that some action should happen for any user. ABRT version 2 adds support for this functionality. BZ# 695416 The lacking information about configuring a proxy has been added to the Red Hat Enterprise Linux 6 Deployment Guide. BZ# 707950 Previously, a bug in ABRT version 1 was preventing a local Python build to finish. This is now fixed. BZ# 725660 The report tool and report library have been obsoleted by abrt and libreport. Users can notice the change in the problem reporting user interface of Anaconda, setroubleshoot, and ABRT. All users of ABRT are advised to upgrade to these updated packages, which provide numerous bug fixes and enhancements.

Commands:
2.10. Pre-Installation Script Figure 2.15. Pre-Installation Script You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area. To specify a scripting language to use to execute the script, select the Use an interpreter option and enter the interpreter in the text box beside it. For example, /usr/bin/python2.2 can be specified for a Python script. This option corresponds to using %pre --interpreter /usr/bin/python2.2 in your kickstart file. Warning Do not include the %pre command. It is added for you.

Commands:
Chapter 1. Preparing to install on Alibaba Cloud Important Alibaba Cloud on OpenShift Container Platform is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 1.1. Prerequisites You reviewed details about the OpenShift Container Platform installation and update processes. You read the documentation on selecting a cluster installation method and preparing it for users . 1.2. Requirements for installing OpenShift Container Platform on Alibaba Cloud Before installing OpenShift Container Platform on Alibaba Cloud, you must configure and register your domain, create a Resource Access Management (RAM) user for the installation, and review the supported Alibaba Cloud data center regions and zones for the installation. 1.3. Registering and Configuring Alibaba Cloud Domain To install OpenShift Container Platform, the Alibaba Cloud account you use must have a dedicated public hosted zone in your account. This zone must be authoritative for the domain. This service provides cluster DNS resolution and name lookup for external connections to the cluster. Procedure Identify your domain, or subdomain, and registrar. You can transfer an existing domain and registrar or obtain a new one through Alibaba Cloud or another source. Note If you purchase a new domain through Alibaba Cloud, it takes time for the relevant DNS changes to propagate. For more information about purchasing domains through Alibaba Cloud, see Alibaba Cloud domains . If you are using an existing domain and registrar, migrate its DNS to Alibaba Cloud. See Domain name transfer in the Alibaba Cloud documentation. Configure DNS for your domain. This includes: Registering a generic domain name . Completing real-name verification for your domain name . Applying for an Internet Content Provider (ICP) filing . Enabling domain name resolution . Use an appropriate root domain, such as openshiftcorp.com , or subdomain, such as clusters.openshiftcorp.com . If you are using a subdomain, follow the procedures of your company to add its delegation records to the parent domain. 1.4. Supported Alibaba regions You can deploy an OpenShift Container Platform cluster to the regions listed in the Alibaba Regions and zones documentation . 1.5. steps Create the required Alibaba Cloud resources .

Commands:
3.2.2. Direct Routing and iptables You may also work around the ARP issue using the direct routing method by creating iptables firewall rules. To configure direct routing using iptables , you must add rules that create a transparent proxy so that a real server will service packets sent to the VIP address, even though the VIP address does not exist on the system. The iptables method is simpler to configure than the arptables_jf method. This method also circumvents the LVS ARP issue entirely, because the virtual IP address(es) only exist on the active LVS director. However, there are performance issues using the iptables method compared to arptables_jf , as there is overhead in forwarding/masquerading every packet. You also cannot reuse ports using the iptables method. For example, it is not possible to run two separate Apache HTTP Server services bound to port 80, because both must bind to INADDR_ANY instead of the virtual IP addresses. To configure direct routing using the iptables method, perform the following steps: On each real server, run the following command for every VIP, port, and protocol (TCP or UDP) combination intended to be serviced for the real server: iptables -t nat -A PREROUTING -p <tcp|udp> -d <vip> --dport <port> -j REDIRECT This command will cause the real servers to process packets destined for the VIP and port that they are given. Save the configuration on each real server: The commands above cause the system to reload the iptables configuration on bootup - before the network is started.

Commands:
service iptables save chkconfig --level 2345 iptables on
Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads Red Hat OpenShift Data Foundation 4.14 The OpenShift Data Foundation Disaster Recovery capabilities for Metropolitan and Regional regions is now General Available which also includes Disaster Recovery with stretch cluster. Red Hat Storage Documentation Team Abstract The intent of this solution guide is to detail the steps necessary to deploy OpenShift Data Foundation for disaster recovery with Advanced Cluster Management and stretch cluster to achieve a highly available storage infrastructure.

Commands:
Chapter 4. Using Samba for Active Directory Integration Samba implements the Server Message Block (SMB) protocol in Red Hat Enterprise Linux. The SMB protocol is used to access resources on a server, such as file shares and shared printers. You can use Samba to authenticate Active Directory (AD) domain users to a Domain Controller (DC). Additionally, you can use Samba to share printers and local directories to other SMB clients in the network. 4.1. Using winbindd to Authenticate Domain Users Samba's winbindd service provides an interface for the Name Service Switch (NSS) and enables domain users to authenticate to AD when logging into the local system. Using winbindd provides the benefit that you can enhance the configuration to share directories and printers without installing additional software. For further detail, see the section about Samba in the Red Hat System Administrator's Guide . 4.1.1. Joining an AD Domain If you want to join an AD domain and use the Winbind service, use the realm join --client-software=winbind domain_name command. The realm utility automatically updates the configuration files, such as those for Samba, Kerberos, and PAM. For further details and examples, see the Setting up Samba as a Domain Member section in the Red Hat System Administrator's Guide .

Commands:
Chapter 3. Group Management 3.1. Manage Keystone Groups 3.1.1. Using the Command-line You can use Identity Service (keystone) groups to assign consistent permissions to multiple user accounts. This example creates a group and then assigns permissions to the group. As a result, members of the group will inherit the same permissions that were assigned to the group: Note The openstack group subcommands require keystone v3 . Create the group grp-Auditors : View a list of keystone groups: Grant the grp-Auditors group permission to access the demo project, while using the _member_ role: Add the existing user user1 to the grp-Auditors group: Confirm that user1 is a member of grp-Auditors : Review the effective permissions that have been assigned to user1 : 3.1.2. Using Dashboard You can use the dashboard to manage the membership of keystone groups. You will need to use the command-line to assign role permissions to a group, as covered in the example. 3.1.2.1. Create a Group As an admin user in the dashboard, select Identity > Groups . Click +Create Group . Enter a name and description for the group. Click Create Group . 3.1.2.2. Manage Group Membership You can use the dashboard to manage the membership of keystone groups. As an admin user in the dashboard, select Identity > Groups . Click Manage Members for the group you need to edit. Use Add users to add a user to the group. If you need to remove a user, mark its checkbox and click or Remove users .

Commands:
openstack group create grp-Auditors +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | | | domain_id | default | | id | 2a4856fc242142a4aa7c02d28edfdfff | | name | grp-Auditors | +-------------+----------------------------------+
openstack group list --long +----------------------------------+--------------+-----------+-------------+ | ID | Name | Domain ID | Description | +----------------------------------+--------------+-----------+-------------+ | 2a4856fc242142a4aa7c02d28edfdfff | grp-Auditors | default | | +----------------------------------+--------------+-----------+-------------+
openstack role add _member_ --group grp-Auditors --project demo
openstack group add user grp-Auditors user1 user1 added to group grp-Auditors
openstack group contains user grp-Auditors user1 user1 in group grp-Auditors
openstack role assignment list --effective --user user1 +----------------------------------+----------------------------------+-------+----------------------------------+--------+-----------+ | Role | User | Group | Project | Domain | Inherited | +----------------------------------+----------------------------------+-------+----------------------------------+--------+-----------+ | 9fe2ff9ee4384b1894a90878d3e92bab | 3fefe5b4f6c948e6959d1feaef4822f2 | | 0ce36252e2fb4ea8983bed2a568fa832 | | False | +----------------------------------+----------------------------------+-------+----------------------------------+--------+-----------+
30.2.3. Configuring for Power Systems Servers If tftp-server is not yet installed, run yum install tftp-server . In the tftp-server config file at /etc/xinetd.d/tftp , change the disabled parameter from yes to no . Configure your DHCP server to use the boot images packaged with yaboot . (If you do not have a DHCP server installed, refer to the DHCP Servers chapter in the Red Hat Enterprise Linux Deployment Guide .) A sample configuration in /etc/dhcp/dhcpd.conf might look like: You now need the yaboot binary file from the yaboot package in the ISO image file. To access it, run the following commands as root: Extract the package: Create a yaboot directory within tftpboot and copy the yaboot binary file into it: Add a config file named yaboot.conf to this directory. A sample config file might look like: For instructions on how to specify the installation source, refer to Section 7.1.3, "Additional Boot Options" Copy the boot images from the extracted ISO into your tftp root directory: Clean up by removing the yaboot-unpack directory and unmounting the ISO: Boot the client system, and select the network device as your boot device when prompted.

Commands:
host bonn { filename "yaboot"; next-server 10.32.5.1; hardware ethernet 00:0e:91:51:6a:26; fixed-address 10.32.5.144; }
mkdir /publicly_available_directory/yaboot-unpack mount -t iso9660 / path_to_image/name_of_image .iso / mount_point -o loop,ro cp -pr / mount_point /Packages/yaboot- version .ppc.rpm / publicly_available_directory /yaboot-unpack
cd / publicly_available_directory /yaboot-unpack rpm2cpio yaboot- version .ppc.rpm | cpio -dimv
mkdir /var/lib/tftpboot/yaboot cp publicly_available_directory /yaboot-unpack/usr/lib/yaboot/yaboot /var/lib/tftpboot/yaboot
init-message = "\nWelcome to the Red Hat Enterprise Linux 6 installer!\n\n" timeout=60 default=rhel6 image=/rhel6/vmlinuz-RHEL6 label=linux alias=rhel6 initrd=/rhel6/initrd-RHEL6.img append="repo=http://10.32.5.1/mnt/archive/redhat/released/RHEL-6/6.x/Server/ppc64/os/" read-only
cp /mount_point/images/ppc/ppc64/vmlinuz /var/lib/tftpboot/yaboot/rhel6/vmlinuz-RHEL6 cp /mount_point/images/ppc/ppc64/initrd.img /var/lib/tftpboot/yaboot/rhel6/initrd-RHEL6.img
rm -rf / publicly_available_directory /yaboot-unpack umount / mount_point
5.57. e2fsprogs 5.57.1. RHBA-2012:0944 - e2fsprogs bug fix update Updated e2fsprogs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The e2fsprogs packages provide a number of utilities for creating, checking, modifying, and correcting any inconsistencies in second (ext2), third (ext3), and fourth (ext4) extended file systems. Bug Fixes BZ# 786021 Prior to this update, checksums for backup group descriptors appeared to be wrong when the "e2fsck -b" option read these group descriptors and cleared UNINIT flags to ensure that all inodes were scanned. As a consequence, warning messages were sent during the process. This update recomputes checksums after the flags are changed. Now, "e2fsck -b" completes without these checksum warnings. BZ# 795846 Prior to this update, e2fsck could discard valid inodes when using the "-E discard" option. As a consequence, the file system could become corrupted. This update modifies the underlying code so that disk regions containing valid inodes are no longer discarded. All users of e2fsprogs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 5. Migrating a non-containerized Red Hat Ceph Storage cluster to a containerized environment To manually migrate a non-containerized, bare-metal, Red Hat Ceph Storage cluster to a containerized environment, use the ceph-ansible switch-from-non-containerized-to-containerized-ceph-daemons.yml playbook. Note If the storage cluster has an RBD mirror daemon not deployed by ceph-ansible , you need to migrate the daemons prior to converting to a containerized cluster. For more details, see Migrating RBD mirroring daemons . Prerequisites A running Red Hat Ceph Storage non-containerized, bare-metal, cluster. Access to the Ansible administration node. An ansible user account. Sudo access to the ansible user account. Procedure Edit the group_vars/all.yml file to include configuration for containers: Important For the ceph_docker_image_tag , use latest if your current storage cluster is on latest version or use the appropriate image tag. See the What are the Red Hat Ceph Storage releases and corresponding Ceph package versions? for more information. Navigate to the /usr/share/ceph-ansible directory: On the Ansible administration node, run the Ansible migration playbook: Syntax Example Verify the cluster is switched to containerized environment. On the monitor node, list all running containers: Red Hat Enterprise Linux 7 Red Hat Enterprise Linux 8 Additional Resources See the Installing a Red Hat Ceph Storage cluster chapter in the Red Hat Ceph Storage Installation Guide for information on installation of a bare-metal storage cluster. See the Creating an Ansible user with sudo access section in the Red Hat Ceph Storage Installation Guide for providing sudo access to the ansible user. See the Configuring two-way mirroring using the command-line interface section in the Red Hat Ceph Storage Block Device Guide for more details.

Commands:
ceph_docker_image_tag: "latest" ceph_docker_image: rhceph/rhceph-4-rhel8 containerized_deployment: true ceph_docker_registry: registry.redhat.io
[ansible@admin ~]USD cd /usr/share/ceph-ansible
ansible-playbook ./infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml -i INVENTORY_FILE
[ansible@admin ceph-ansible]USD ansible-playbook ./infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml -i hosts
[root@mon ~]USD sudo docker ps
[root@mon ~]USD sudo podman ps
Chapter 2. Metrics solution components Red Hat recommends using the Performance Co-Pilot to collect and archive Satellite metrics. Performance Co-Pilot (PCP) Performance Co-Pilot is a suite of tools and libraries for acquiring, storing, and analyzing system-level performance measurements. You can use PCP to analyze live and historical metrics in the CLI. Performance Metric Domain Agents (PMDA) A Performance Metric Domain Agent is a PCP add-on which enables access to metrics of an application or service. To gather all metrics relevant to Satellite, you have to install PMDA for Apache HTTP Server and PostgreSQL. Grafana A web application that visualizes metrics collected by PCP. To analyze metrics in the web UI, you have to install Grafana and the Grafana PCP plugin.

Commands: