mtpti5iD/redhat-docs_dataset huggingface dataset:
4. Feedback If you spot a typo, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in Bugzilla ( http://bugzilla.redhat.com/bugzilla/ ) against the component rh-cs . Be sure to mention the manual's identifier: By mentioning this manual's identifier, we know exactly which version of the guide you have. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

Commands:
rh-clvm(EN)-4.8 (2009-05-14T12:46)
Chapter 3. Installing the high availability and RHOSP packages and agents Install the packages required for configuring a Red Hat High Availability cluster on Red Hat OpenStack Platform (RHOSP). You must install the packages on each of the nodes you will use as cluster members. Prerequisites A server group for the RHOSP instances to use as HA cluster nodes, configured as described in RHOSP server group configuration for HA instances An RHOSP instance for each HA cluster node The instances are members of a server group The instances are configured as nodes running RHEL 9.1 or later Procedure Enable the RHEL HA repositories and the RHOSP tools channel. Install the Red Hat High Availability Add-On software packages and the packages that are required for the RHOSP cluster resource agents and the RHOSP fence agents. Installing the pcs and pacemaker packages on each node creates the user hacluster , which is the pcs administration account. Create a password for user hacluster on all cluster nodes. Using the same password for all nodes simplifies cluster administration. If firewalld.service is installed, add the high-availability service to the RHEL firewall. Start the pcs service and enable it to start on boot. Verify that the pcs service is running. Edit the /etc/hosts file and add RHEL host names and internal IP addresses. For information about /etc/hosts , see the Red Hat Knowledgebase solution How should the /etc/hosts file be set up on RHEL cluster nodes? . Additional resources For further information about configuring and managing Red Hat high availability clusters, see Configuring and managing high availability clusters .

Commands:
subscription-manager repos --enable=rhel-9-for-x86_64-highavailability-rpms subscription-manager repos --enable=openstack-17-tools-for-rhel-9-x86_64-rpms
dnf install pcs pacemaker python3-openstackclient python3-novaclient fence-agents-openstack
passwd hacluster
firewall-cmd --permanent --add-service=high-availability firewall-cmd --add-service=high-availability
systemctl start pcsd.service systemctl enable pcsd.service
systemctl status pcsd.service pcsd.service - PCS GUI and remote configuration interface Loaded: loaded (/usr/lib/systemd/system/pcsd.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-03-01 14:53:28 UTC; 28min ago Docs: man:pcsd(8) man:pcs(8) Main PID: 5437 (pcsd) CGroup: /system.slice/pcsd.service └─5437 /usr/bin/ruby /usr/lib/pcsd/pcsd > /dev/null & Mar 01 14:53:27 ip-10-0-0-48.ec2.internal systemd[1]: Starting PCS GUI and remote configuration interface... Mar 01 14:53:28 ip-10-0-0-48.ec2.internal systemd[1]: Started PCS GUI and remote configuration interface.
6.5. xguest: Kiosk Mode The xguest package provides a kiosk user account. This account is used to secure machines that people walk up to and use, such as those at libraries, banks, airports, information kiosks, and coffee shops. The kiosk user account is very limited: essentially, it only allows users to log in and use Firefox to browse Internet websites. Any changes made while logged in with this account, such as creating files or changing settings, are lost when you log out. To set up the kiosk account: As the Linux root user, run the yum install xguest command to install the xguest package. Install dependencies as required. In order to allow the kiosk account to be used by a variety of people, the account is not password-protected, and as such, the account can only be protected if SELinux is running in enforcing mode. Before logging in with this account, use the getenforce command to confirm that SELinux is running in enforcing mode: If this is not the case, refer to Section 2.4, "SELinux States and Modes" for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled. You can only log in to this account via the GNOME Display Manager (GDM). Once the xguest package is installed, a Guest account is added to the GDM login screen.

Commands:
~]USD getenforce Enforcing
Chapter 11. Volume cloning A clone is a duplicate of an existing storage volume that is used as any standard volume. You create a clone of a volume to make a point in time copy of the data. A persistent volume claim (PVC) cannot be cloned with a different size. You can create up to 512 clones per PVC for both CephFS and RADOS Block Device (RBD). 11.1. Creating a clone Prerequisites Source PVC must be in Bound state and must not be in use. Note Do not create a clone of a PVC if a Pod is using it. Doing so might cause data corruption because the PVC is not quiesced (paused). Procedure Click Storage Persistent Volume Claims from the OpenShift Web Console. To create a clone, do one of the following: Beside the desired PVC, click Action menu (...) Clone PVC . Click on the PVC that you want to clone and click Actions Clone PVC . Enter a Name for the clone. Click Clone . You will be redirected to the new PVC details page. Note Clones are created with the access mode of the parent PVC. Currently, you cannot specify the access mode using the OpenShift Web Console UI. However, you can specify the access mode from the CLI using the YAML. For more information, see Provisioning a CSI volume clone . Wait for the cloned PVC status to become Bound . The cloned PVC is now available to be consumed by the pods. This cloned PVC is independent of its dataSource PVC.

Commands:
Part II. OpenApi Java Component Available as of Camel 3.1.0 The Rest DSL can be integrated with the camel-openapi-java module which is used for exposing the REST services and their APIs using OpenApi . Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-openapi-java</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> The camel-openapi-java module can be used from the REST components (without the need for servlet)

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-openapi-java</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
Chapter 24. Reviewing the IT_Orders sample project Before you create your own case management project, review the existing IT_Orders sample case management project in Business Central. This sample project contains predefined case management assets as a reference for your own case projects. Important The business process application example includes features that are Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and are not recommended for 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 Red Hat Technology Preview support, see Technology Preview Features Support Scope . Procedure In Business Central, go to Menu Design Projects . If there are existing projects, you can access the samples by clicking the MySpace default space and selecting Try Samples from the Add Project drop-down menu. If there are no existing projects, click Try samples . Select IT_Orders and click Ok . The Assets view of the project opens. Select each example asset to explore how the project is designed to achieve the specified goal or workflow. Review the orderhardware business process to help you understand the business process flow.

Commands:
Chapter 29. Revision History 0.14-26 Mon Aug 05 2019, Marie Dolezelova ( mdolezel@redhat.com ) Preparing document for 7.7 GA publication. 0.14-23 Mon Aug 13 2018, Marie Dolezelova ( mdolezel@redhat.com ) Preparing document for 7.6 Beta publication. 0.14-19 Tue Mar 20 2018, Marie Dolezelova ( mdolezel@redhat.com ) Preparing document for 7.5 GA publication. 0.14-17 Tue Dec 5 2017, Marie Dolezelova ( mdolezel@redhat.com ) Updated Samba section. Added section about Configuring RELP with TLS. Updated section on Upgrading from GRUB Legacy to GRUB 2. 0.14-16 Mon Aug 8 2017, Marie Dolezelova ( mdolezel@redhat.com ) Minor fixes throughout the guide, added links to articles dealing with choosing a target for ordering and dependencies of the custom unit files to the chapter "Creating Custom Unit Files". 0.14-14 Thu Jul 27 2017, Marie Dolezelova ( mdolezel@redhat.com ) Document version for 7.4 GA publication. 0.14-8 Mon Nov 3 2016, Maxim Svistunov ( msvistun@redhat.com ) Version for 7.3 GA publication. 0.14-7 Mon Jun 20 2016, Maxim Svistunov ( msvistun@redhat.com ) Added Relax-and-Recover (ReaR) ; made minor improvements. 0.14-6 Thu Mar 10 2016, Maxim Svistunov ( msvistun@redhat.com ) Minor fixes and updates. 0.14-5 Thu Jan 21 2016, Lenka Spackova ( lspackova@redhat.com ) Minor factual updates. 0.14-3 Wed Nov 11 2015, Jana Heves ( jheves@redhat.com ) Version for 7.2 GA release. 0.14-1 Mon Nov 9 2015, Jana Heves ( jheves@redhat.com ) Minor fixes, added links to RH training courses. 0.14-0.3 Fri Apr 3 2015, Stephen Wadeley ( swadeley@redhat.com ) Added Registering the System and Managing Subscriptions , Accessing Support Using the Red Hat Support Tool , updated Viewing and Managing Log Files . 0.13-2 Tue Feb 24 2015, Stephen Wadeley ( swadeley@redhat.com ) Version for 7.1 GA release. 0.12-0.6 Tue Nov 18 2014, Stephen Wadeley ( swadeley@redhat.com ) Improved TigerVNC . 0.12-0.4 Mon Nov 10 2014, Stephen Wadeley ( swadeley@redhat.com ) Improved Yum , Managing Services with systemd , OpenLDAP , Viewing and Managing Log Files , OProfile , and Working with the GRUB 2 Boot Loader . 0.12-0 Tue 19 Aug 2014, Stephen Wadeley ( swadeley@redhat.com ) Red Hat Enterprise Linux 7.0 GA release of the System Administrator's Guide. 29.1. Acknowledgments Certain portions of this text first appeared in the Red Hat Enterprise Linux 6 Deployment Guide ,

Commands:
Preface Thank you for your interest in Red Hat Ansible Automation Platform automation controller. Automation controller helps teams manage complex multitiered deployments by adding control, knowledge, and delegation to Ansible-powered environments. Using automation controller describes all of the functionality available in automation controller. It assumes moderate familiarity with Ansible, including concepts such as playbooks, variables, and tags. For more information about these and other Ansible concepts, see the Ansible documentation .

Commands:
Chapter 55. Clustering Data corruption occurs on RAID 10 reshape on top of VDO with el7 kernel. RAID 10 reshape (with both LVM and mdadm ) on top of VDO corrupts data and can eventually trigger the raid10.c:1011 kernel bug. Stacking RAID 10 (or other RAID types) on top of VDO does not take advantage of the deduplication/compression capabilities of VDO and is not recommended. (BZ# 1528466 , BZ#1530776)

Commands:
4.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: allow_ftpd_anon_write When disabled, this Boolean prevents vsftpd from writing to files and directories labeled with the public_content_rw_t type. Enable this Boolean to allow users to upload files via FTP. The directory where files are uploaded to must be labeled with the public_content_rw_t type and Linux permissions set accordingly. allow_ftpd_full_access When this Boolean is on, only Linux (DAC) permissions are used to control access, and authenticated users can read and write to files that are not labeled with the public_content_t or public_content_rw_t types. allow_ftpd_use_cifs Having this Boolean enabled allows vsftpd to access files and directories labeled with the cifs_t type; therefore, having this Boolean enabled allows you to share file systems mounted via Samba through vsftpd . allow_ftpd_use_nfs Having this Boolean enabled allows vsftpd to access files and directories labeled with the nfs_t type; therefore, having this Boolean enabled allows you to share file systems mounted via NFS through vsftpd . ftp_home_dir Having this Boolean enabled allows authenticated users to read and write to files in their home directories. When this Boolean is off, attempting to download a file from a home directory results in an error such as 550 Failed to open file . An SELinux denial is logged. ftpd_connect_db Allow FTP daemons to initiate a connection to a database. httpd_enable_ftp_server Allow httpd to listen on the FTP port and act as a FTP server. tftp_anon_write Having this Boolean enabled allows TFTP access to a public directory, such as an area reserved for common files that otherwise has no special access restrictions. 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, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 4. Advisories related to this release The following advisories have been issued to bugfixes and CVE fixes included in this release. RHSA-2021:1307 RHSA-2021:1306 RHSA-2021:1305 RHSA-2021:1297 RHSA-2021:1447 RHSA-2021:1446 Revised on 2024-05-09 16:46:28 UTC

Commands:
6.2.3. What Barriers Are in Place To Prevent Abuse of Resources The careful organization of groups and assignment of permissions for shared resources is one of the most important things a system administrator can do to prevent resource abuse among users within an organization. In this way, those who should not have access to sensitive resources are denied access. But no matter how your organization does things, the best guard against abuse of resources is always sustained vigilance on the part of the system administrator. Keeping your eyes open is often the only way to avoid having an unpleasant surprise waiting for you at your desk one morning.

Commands:
5.173. lohit-kannada-fonts 5.173.1. RHBA-2012:0870 - lohit-kannada-fonts bug fix update An updated lohit-kannada-fonts package that fixes one bug is now available for Red Hat Enterprise Linux 6. The lohit-kannada-fonts package provides a free Kannada TrueType/OpenType font. Bug Fix BZ# 603415 When using Kannada (kn_IN) locale, multiple strings could appear incomplete due to incorrect rendering of the end characters. As a consequence, users were not able to properly read the menu items on the desktop panel's menu bar. With this update, all characters are rendered correctly and users are now able to read the menu items. All users of lohit-kannada-fonts are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 4. Adding RHEL metering to a Microsoft Azure integration If you converted from a compatible third-party Linux distribution to Red Hat Enterprise Linux (RHEL) and purchased the RHEL for third party migration listing in Microsoft Azure, you can update an Microsoft Azure integration you created to add RHEL metering. With RHEL metering, Red Hat processes your bill to meter my hourly RHEL usage associated with a Red Hat offering in Microsoft Azure. Procedure In Microsoft Azure, tag your instances of RHEL that you want to meter. For more information about tagging your instances of RHEL in Microsoft Azure, see Adding tags to a Microsoft Azure resource . From Red Hat Hybrid Cloud Console , click Settings . Click Integrations . Click the more options menu for your integration. Click Edit . In Metered Product , select Red Hat Enterprise Linux from the drop-down to activate metering.

Commands:
3.2.2. Preparing to convert a local Xen virtual machine The following is required when converting virtual machines on a host which used to run Xen, but has been updated to run KVM. It is not required when converting a Xen virtual machine imported directly from a running libvirt/Xen instance. Procedure 3.3. Preparing to convert a local Xen virtual machine Obtain the XML for the virtual machine. virt-v2v uses a libvirt domain description to determine the current configuration of the virtual machine, including the location of its storage. Before starting the conversion, obtain the XML from the host running the virtual machine with the following command: This will require booting into a Xen kernel to obtain the XML, as libvirt needs to connect to a running Xen hypervisor to obtain its metadata. The conversion process is optimized for KVM, so obtaining domain data while running a Xen kernel, then performing the conversion using a KVM kernel will be more efficient than running the conversion on a Xen kernel.

Commands:
virsh dumpxml guest_name > guest_name.xml
Chapter 7. Configuring the system and running tests by using RHCert CLI Tool To run the certification tests by using CLI you need to upload the test plan to the HUT first. After running the tests, download the results and review them. This chapter contains the following topics: Section 7.1, "Using the test plan to prepare the host under test for testing" Section 7.2, "Running the certification tests using CLI" Section 7.3, "Submitting the test results file" 7.1. Using the test plan to prepare the host under test for testing Running the provision command performs a number of operations, such as installing the required packages on your system based on the certification type, and creating a final test plan to run, which is a list of common tests taken from both the test plan provided by Red Hat and tests generated on discovering the system requirements. For instance, required hardware packages will be installed if the test plan is designed for certifying a hardware product. Procedure Run the provision command in either way. The test plan will automatically get downloaded to your system. If you have already downloaded the test plan: Replace <path_to_test_plan_document> with the test plan file saved on your system. Follow the on-screen instructions. If you have not downloaded the test plan: Follow the on-screen instructions and enter your Certification ID when prompted. 7.2. Running the certification tests using CLI Procedure Run the following command: When prompted, choose whether to run each test by typing yes or no . You can also run particular tests from the list by typing select . Note After a test reboot, rhcert is running in the background to verify the image. Use tail -f / var /log/rhcert/RedHatCertDaemon.log to see the current progress and status of the verification. 7.3. Submitting the test results file Procedure Log in to authenticate your device. Note Logging in is mandatory to submit the test results file. Open the generated URL in a new browser window or tab. Enter the login and password and click Log in . Click Grant access . Device log in successful message displays. Return to the terminal and enter yes to the Please confirm once you grant access prompt. Submit the result file. When prompted, enter your Certification ID.

Commands:
rhcert-provision _<path_to_test_plan_document>_
rhcert-provision
rhcert-run
rhcert-cli login
rhcert-submit
5.5. Space Indicated as Used in Empty File System If you have an empty GFS2 file system, the df command will show that there is space being taken up. This is because GFS2 file system journals consume space (number of journals * journal size) on disk. If you created a GFS2 file system with a large number of journals or specified a large journal size then you will be see (number of journals * journal size) as already in use when you execute the df . Even if you did not specify a large number of journals or large journals, small GFS2 file systems (in the 1GB or less range) will show a large amount of space as being in use with the default GFS2 journal size.

Commands:
Chapter 16. Change resources on virtual machines using director Operator To change the CPU, RAM, and disk resources of a OpenStackVMSet use the OpenStackControlPlane. 16.1. Change the CPU or RAM of an OpenStackVMSet You can use the OpenStackControlPlane to change the CPU or RAM of an OpenStackVMSet. Procedure Change the number of Controller virtualMachineRole cores to 8: Change the Controller virtualMachineRole RAM size to 22GB: Validate the virtualMachineRole resource: From inside the virtual machine do a graceful shutdown. Shutdown each updated virtual machine one by one. Power on the virtual machine: Replace <VM> with the name of your virtual machine. 16.2. Add additional disks to an OpenStackVMSet You can use the OpenStackControlPlane to add additional disks to a virtual machine by editing the additionalDisks property. Procedure Add or update the additionalDisks parameter in the OpenStackControlPlane object: Apply the patch: Validate the virtualMachineRole resource: From inside the virtual machine do a graceful shutdown. Shutdown each updated virtual machine one by one. Power on the virtual machine: Replace <VM> with the name of your virtual machine.

Commands:
oc patch -n openstack osctlplane overcloud --type='json' -p='[{"op": "add", "path": "/spec/virtualMachineRoles/controller/cores", "value": 8 }]'
oc patch -n openstack osctlplane overcloud --type='json' -p='[{"op": "add", "path": "/spec/virtualMachineRoles/controller/memory", "value": 22 }]'
oc get osvmset NAME CORES RAM DESIRED READY STATUS REASON controller 8 22 1 1 Provisioned All requested VirtualMachines have been provisioned
`virtctl start <VM>` to power on the virtual machine.
spec: virtualMachineRoles: Controller: additionalDisks: - baseImageVolumeName: openstack-base-img dedicatedIOThread: false diskSize: 10 name: "data-disk1" storageAccessMode: ReadWriteMany storageClass: host-nfs-storageclass storageVolumeMode: Filesystem
oc patch -n openstack osctlplane overcloud --patch-file controller_add_data_disk1.yaml
oc get osvmset controller -o json | jq .spec.additionalDisks [ { "baseImageVolumeName": "openstack-base-img", "dedicatedIOThread": false, "diskSize": 10, "name": "data-disk1", "storageAccessMode": "ReadWriteMany", "storageClass": "host-nfs-storageclass", "storageVolumeMode": "Filesystem" } ]
`virtctl start <VM>` to power on the virtual machine.
Preface Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in four versions: 8u, 11u, 17u, and 21u. Packages for the Red Hat build of OpenJDK are available on Red Hat Enterprise Linux and Microsoft Windows platforms and shipped as a JDK and a JRE in the Red Hat Ecosystem Catalog.

Commands:
Appendix F. Adding additional managed namespaces to the AAP Operator The following are the steps to add an additional managed namespace to the already existing AAP operator that resides in the aap namespace. Login to the Red Hat OpenShift UI. Within the Operators->Installed Operators , select Ansible Automation Platform Within the Details page, scroll down to the ClusterServiceVersion Details On the right column, click on the OperatorGroup Within the OperatorGroup details, select YAML Under the spec section add any additional namespaces, e.g. aap-devel Click Save Note The targeted namespace must already exist prior to adding to the OperatorGroup spec file.

Commands:
spec: targetNamespaces: - aap - aap-devel