mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Opting out of Telemetry The decision to opt out of telemetry should be based on your specific needs and requirements, as well as any applicable regulations or policies that you need to comply with. 2.1. Consequences of disabling Telemetry In Red Hat Advanced Cluster Security for Kubernetes (RHACS) version 4.0, you can opt out of Telemetry. However, telemetry is embedded as a core component, so opting out is strongly discouraged. Opting out of telemetry limits the ability of Red Hat to understand how everyone uses the product and which areas to prioritize for improvements. 2.2. Disabling Telemetry If you have configured Telemetry by setting the key in your environment, you can disable Telemetry data collection from the Red Hat Advanced Cluster Security for Kubernetes (RHACS) user interface (UI). Procedure In the RHACS portal, go to Platform Configuration > System Configuration . In the System Configuration header, click Edit . Scroll down and ensure that Online Telemetry Data Collection is set to Disabled.

Commands:
Appendix A. Component Versions This appendix provides a list of key components and their versions in the Red Hat Enterprise Linux 6.10 release. Table A.1. Component Versions Component Version kernel 2.6.32-754 QLogic qla2xxx driver 8.07.00.26.06.8-k QLogic ql2xxx firmware ql2100-firmware-1.19.38-3.1 ql2200-firmware-2.02.08-3.1 ql23xx-firmware-3.03.27-3.1 ql2400-firmware-7.03.00-1 ql2500-firmware-7.03.00-1 Emulex lpfc driver 0:11.0.1.6 iSCSI initiator utils ( iscsi-initiator-utils ) 6.2.0.873-27 DM-Multipath ( device-mapper-multipath ) 0.4.9-106 LVM ( lvm2 ) 2.02.143-12

Commands:
8.105. logrotate 8.105.1. RHBA-2013:1095 - logrotate bug fix update Updated logrotate packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. Bug Fixes BZ# 841520 The logrotate utility always tried to set owner of the rotated log even when the owner was the same as the current owner of the log file. Conseqeuntly, the rotation failed on file systems or systems where changing the ownership was not supported. With this update, before the ownership is changed, logrotate check if it is a real ownership change; that is, logrotate verifies if the new ownership is not the same as the one, and skips the change if the ownership change has not been real. The logrotate utility now rotates logs as expected in this scenario. BZ# 847338 Setting the Access control list (ACL) on a rotated log overwrote the previously set mode of the log file. As a consequence, the "create" directive was ignored. To fix this bug, the ACL is no longer copied from the old log file when using the "create" directive and the mode defined using the "create" directive is used instead. As a result, "create" mode works as expected and it is no longer ignored in the described scenario. BZ# 847339 Both the acl_set_fd() and fchmod() functions were called to set the log files permissions. Consequently, there was a race condition where the log file could have unsafe permissions for a short time during its creation. With this update, only one of those functions is now called depending on directives combination used in the configuration file and race condition between the acl_set_fd() and fchmod() function is not possible in the described scenario. BZ# 848131 Because the inverse umask value 0000 was used when creating a new log file, the newly created log file could have unwanted 0600 permissions for a short time before the permissions were set to the proper value using the fchmod() function. With this update, umask is set to 0777 and the newly created log file has proper 0000 permissions for this short period. BZ#920030 The default SELinux context was set after the compressed log file had been created. Consequently, the compressed log did not have the proper SELinux context. With this update, the default SELinux context is now set before the compressed log file creation and compressed log files have proper SELinux context. BZ#922169 Temporary files created by the logrotate utility were not removed if an error occurred during its use. With this update, temporary files are now removed in such a case. Users of logrotate are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install Red Hat build of Apache Qpid ProtonJ2 in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with Red Hat build of Apache Qpid ProtonJ2, you must install Apache Maven . To use Red Hat build of Apache Qpid ProtonJ2, you must install Java. 2.2. Installing on Red Hat Enterprise Linux 2.3. Using the Red Hat Maven repository Procedure Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.qpid</groupId> <artifactId>protonj2-client</artifactId> <version>1.0.0.M18-redhat-00002</version> </dependency> The client is now available in your Maven project. 2.4. Installing a local Maven repository As an alternative to the online repository, Red Hat build of Apache Qpid ProtonJ2 can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the amq-qpid-protonj2-1.0.0.M18 Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-qpid-protonj2-1.0.0.M18-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.5. Installing the examples Use the git clone command to clone the source repository to a local directory named qpid-protonj2 : USD git clone https://github.com/apache/qpid-protonj2.git Change to the qpid-protonj2 directory and use the git checkout command to checkout the commit associated with this release: USD cd qpid-protonj2 USD git checkout 1.0.0-M18 USD cd protonj2-client-examples The resulting local directory is referred to as <source-dir> in this guide.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.qpid</groupId> <artifactId>protonj2-client</artifactId> <version>1.0.0.M18-redhat-00002</version> </dependency>
unzip amq-qpid-protonj2-1.0.0.M18-maven-repository.zip
git clone https://github.com/apache/qpid-protonj2.git
cd qpid-protonj2 git checkout 1.0.0-M18 cd protonj2-client-examples
Chapter 2. Setting up to Manage Application Versions Effective version control is essential to all multi-developer projects. Red Hat Enterprise Linux is distributed with Git , a distributed version control system. Select the Development Tools Add-on during the system installation to install Git . Alternatively, install the git package from the Red Hat Enterprise Linux repositories after the system is installed. To get the latest version of Git supported by Red Hat, install the rh-git227 component from Red Hat Software Collections. Set the full name and email address associated with your Git commits: Replace full name and email_address with your actual name and email address. To change the default text editor started by Git , set the value of the core.editor configuration option: Replace command with the command to be used to start the selected text editor. Additional Resources Chapter 11, Using Git

Commands:
yum install git
yum install rh-git227
git config --global user.name " full name " git config --global user.email " email_address "
git config --global core.editor command
8.2. Configuring NFS Client The mount command mounts NFS shares on the client side. Its format is as follows: This command uses the following variables: options A comma-delimited list of mount options; for more information on valid NFS mount options, see Section 8.4, "Common NFS Mount Options" . server The hostname, IP address, or fully qualified domain name of the server exporting the file system you wish to mount /remote/export The file system or directory being exported from the server , that is, the directory you wish to mount /local/directory The client location where /remote/export is mounted The NFS protocol version used in Red Hat Enterprise Linux 7 is identified by the mount options nfsvers or vers . By default, mount uses NFSv4 with mount -t nfs . If the server does not support NFSv4, the client automatically steps down to a version supported by the server. If the nfsvers / vers option is used to pass a particular version not supported by the server, the mount fails. The file system type nfs4 is also available for legacy reasons; this is equivalent to running mount -t nfs -o nfsvers=4 host : /remote/export /local/directory . For more information, see man mount . If an NFS share was mounted manually, the share will not be automatically mounted upon reboot. Red Hat Enterprise Linux offers two methods for mounting remote file systems automatically at boot time: the /etc/fstab file and the autofs service. For more information, see Section 8.2.1, "Mounting NFS File Systems Using /etc/fstab " and Section 8.3, " autofs " . 8.2.1. Mounting NFS File Systems Using /etc/fstab An alternate way to mount an NFS share from another machine is to add a line to the /etc/fstab file. The line must state the hostname of the NFS server, the directory on the server being exported, and the directory on the local machine where the NFS share is to be mounted. You must be root to modify the /etc/fstab file. Example 8.1. Syntax Example The general syntax for the line in /etc/fstab is as follows: The mount point /pub must exist on the client machine before this command can be executed. After adding this line to /etc/fstab on the client system, use the command mount /pub , and the mount point /pub is mounted from the server. A valid /etc/fstab entry to mount an NFS export should contain the following information: The variables server , /remote/export , /local/directory , and options are the same ones used when manually mounting an NFS share. For more information, see Section 8.2, "Configuring NFS Client" . Note The mount point /local/directory must exist on the client before /etc/fstab is read. Otherwise, the mount fails. After editing /etc/fstab , regenerate mount units so that your system registers the new configuration: Additional Resources For more information about /etc/fstab , refer to man fstab .

Commands:
mount -t nfs -o options server : /remote/export /local/directory
server:/usr/local/pub /pub nfs defaults 0 0
server : /remote/export /local/directory nfs options 0 0
systemctl daemon-reload
4.307. strace 4.307.1. RHBA-2012:0028 - strace bug fix update An updated strace package that fixes one bug is now available for Red Hat Enterprise Linux 6. The strace program intercepts and records the system calls called and received by a running process. It can print a record of each system call, its arguments and its return value. The strace utility is useful for diagnosing, debugging and instructional purposes. Bug Fix BZ# 772569 The strace utility did not properly track switches between 32-bit and 64-bit process execution domains (so called "personalities") when tracing multiple processes with multiple "personalities". This caused strace to output the wrong system call names and arguments for the traced processes. This update corrects personality tracking in strace so that it now prints system call names and arguments as expected. All users of strace are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 4. Post-installation integrations After installing RHTAP, complete the following tasks to ensure that RHTAP works properly. 4.1. (Optional) Integrating Quay into ACS If you are using your own Quay instance instead of Quay.io, or if you plan to use private repositories in Quay, then you must integrate Quay into ACS. This ensures ACS has access to the repositories you use in Quay. Procedure Go to your ACS instance. If you did not have ACS before installing RHTAP, you can find the access details in the rhtap-cli deploy command output, which you saved to ~/install_values.txt at the end of the installation procedure. Follow the instructions in the Red Hat Advanced Cluster Security for Kubernetes 4.6 documentation to integrate Quay into ACS. Revised on 2025-02-13 19:17:36 UTC

Commands:
Chapter 7. sVirt sVirt is a technology included in Red Hat Enterprise Linux 6 that integrates SELinux and virtualization. sVirt applies Mandatory Access Control (MAC) to improve security when using virtual machines. The main reasons for integrating these technologies are to improve security and harden the system against bugs in the hypervisor that might be used as an attack vector aimed toward the host or to another virtual machine. This chapter describes how sVirt integrates with virtualization technologies in Red Hat Enterprise Linux 6. Non-Virtualized Environment In a non-virtualized environment, hosts are separated from each other physically and each host has a self-contained environment, consisting of services such as a Web server, or a DNS server. These services communicate directly to their own user space, host kernel and physical host, offering their services directly to the network. The following image represents a non-virtualized environment: Virtualized Environment In a virtualized environment, several operating systems can be housed (as "guests") within a single host kernel and physical host. The following image represents a virtualized environment: 7.1. Security and Virtualization When services are not virtualized, machines are physically separated. Any exploit is usually contained to the affected machine, with the obvious exception of network attacks. When services are grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to not only attack the host, but also other guests running on that host. This is not theoretical; attacks already exist on hypervisors. These attacks can extend beyond the guest instance and could expose other guests to attack. sVirt is an effort to isolate guests and limit their ability to launch further attacks if exploited. This is demonstrated in the following image, where an attack cannot break out of the virtual machine and extend to another host instance: SELinux introduces a pluggable security framework for virtualized instances in its implementation of Mandatory Access Control (MAC). The sVirt framework allows guests and their resources to be uniquely labeled. Once labeled, rules can be applied which can reject access between different guests.

Commands:
Chapter 1. About OpenShift Virtualization Learn about OpenShift Virtualization's capabilities and support scope. 1.1. What you can do with OpenShift Virtualization OpenShift Virtualization is an add-on to OpenShift Container Platform that allows you to run and manage virtual machine workloads alongside container workloads. OpenShift Virtualization adds new objects into your OpenShift Container Platform cluster by using Kubernetes custom resources to enable virtualization tasks. These tasks include: Creating and managing Linux and Windows virtual machines Connecting to virtual machines through a variety of consoles and CLI tools Importing and cloning existing virtual machines Managing network interface controllers and storage disks attached to virtual machines Live migrating virtual machines between nodes An enhanced web console provides a graphical portal to manage these virtualized resources alongside the OpenShift Container Platform cluster containers and infrastructure. OpenShift Virtualization is designed and tested to work well with Red Hat OpenShift Data Foundation features. Important When you deploy OpenShift Virtualization with OpenShift Data Foundation, you must create a dedicated storage class for Windows virtual machine disks. See Optimizing ODF PersistentVolumes for Windows VMs for details. You can use OpenShift Virtualization with the OVN-Kubernetes , OpenShift SDN , or one of the other certified default Container Network Interface (CNI) network providers listed in Certified OpenShift CNI Plugins . 1.1.1. OpenShift Virtualization supported cluster version OpenShift Virtualization 4.10 is supported for use on OpenShift Container Platform 4.10 clusters. To use the latest z-stream release of OpenShift Virtualization, you must first upgrade to the latest version of OpenShift Container Platform.

Commands:
3.10. Example: Activate Storage Domains This example activates the data1 and iso1 storage domains for the Red Hat Virtualization Manager's use. Example 3.11. Activate data1 storage domain Request: cURL command: Example 3.12. Activate iso1 storage domain Request: cURL command: This activates both storage domains for use with the data center.

Commands:
POST /ovirt-engine/api/datacenters/d70d5e2d-b8ad-494a-a4d2-c7a5631073c4/storagedomains/ 9ca7cb40-9a2a-4513-acef-dc254af57aac/activate HTTP/1.1 Accept: application/xml Content-type: application/xml <action/>
curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u [USER:PASS] --cacert [CERT] -d "<action/>" https:// [RHEVM Host] :443/ovirt-engine/api/datacenters/d70d5e2d-b8ad-494a-a4d2-c7a5631073c4/storagedomains/9ca7cb40-9a2a-4513-acef-dc254af57aac/activate
POST /ovirt-engine/api/datacenters/d70d5e2d-b8ad-494a-a4d2-c7a5631073c4/storagedomains/ 00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da/activate HTTP/1.1 Accept: application/xml Content-type: application/xml <action/>
curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u [USER:PASS] --cacert [CERT] -d "<action/>" https:// [RHEVM Host] :443/ovirt-engine/api/datacenters/d70d5e2d-b8ad-494a-a4d2-c7a5631073c4/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da/activate
Chapter 7. GitOps CLI for use with Red Hat OpenShift GitOps The GitOps argocd CLI is a tool for configuring and managing Red Hat OpenShift GitOps and Argo CD resources from a terminal. With the GitOps CLI, you can make GitOps computing tasks simple and concise. You can install this CLI tool on different platforms. 7.1. Installing the GitOps CLI See Installing the GitOps CLI . 7.2. Additional resources What is GitOps?

Commands:
A.7. Loop Device Errors If file-based guest images are used you may have to increase the number of configured loop devices. The default configuration allows up to eight active loop devices. If more than eight file-based guests or loop devices are needed the number of loop devices configured can be adjusted in the /etc/modprobe.d/ directory. Add the following line: This example uses 64 but you can specify another number to set the maximum loop value. You may also have to implement loop device backed guests on your system. To use a loop device backed guests for a full virtualized system, use the phy: device or file: file commands.

Commands:
options loop max_loop=64
Chapter 6. Installing automation controller With the installation of the Ansible Automation Platform operator completed, the following steps install an automation controller within a Red Hat OpenShift cluster. Note The resource requests and limits values are specific to this reference environment. Ensure to read the Chapter 3, Before you start section to properly calculate the values for your Red Hat OpenShift environment. Warning When an instance of automation controller is removed, the associated Persistent Volume Claims (PVCs) are not automatically deleted. This can cause issues during migration if the new deployment has the same name as the deployment. It is recommended to remove old PVCs prior to deploying a new automation controller instance in the same namespace. The steps to remove deployment PVCs can be found within Appendix B, Delete existing PVCs from AAP installations . Log in to the Red Hat OpenShift web console using your cluster credentials. In the left-hand navigation menu, select Operators Installed Operators , select Ansible Automation Platform . Navigate to the Automation Controller tab, then click Create AutomationController . Within the Form view, provide a Name , e.g. my-automation-controller and select the Advanced configuration to expand the additional options. Within the Additional configuration , set the appropriate Resource Requirements for each container as calculated from the Before you Start section. Expand Web Container Resource Requirements Limits: CPU cores: 2000m, Memory: 1.5Gi Requests: CPU cores: 500m, Memory: 1.5Gi Expand Task Container Resource Requirements Limits: CPU cores: 4000m, Memory: 8Gi Requests: CPU cores: 1000m, Memory: 8Gi Expand EE Control Plane Container Resource Requirements Limits: CPU cores: 500m, Memory: 400Mi Requests: CPU cores: 100m, Memory: 400Mi Expand Redis Container Resource Requirements Limits: CPU cores: 500m, Memory: 1.5Gi Requests: CPU cores: 250m, Memory: 1.5Gi Expand PostgreSQL Container Resource Requirements Limits: CPU cores: 1000m, Memory: 1Gi Requests: CPU cores: 500m, Memory: 1Gi At the top of the Create AutomationController page, toggle the YAML view Within the spec: section add the extra_settings parameter to pass the AWX_CONTROL_NODE_TASK_IMPACT value calculated in the Chapter 3, Before you start section Within the YAML view , add the following to the spec section to add dedicated node for your control pod. Note Ensure to have your node label and taints to the appropriate dedicated worker node that shall run the control pods. Details to set can be found within Appendix C, Applying labels and taints to Red Hat OpenShift node . Click the Create button

Commands:
spec: extra_settings: - setting: AWX_CONTROL_NODE_TASK_IMPACT value: "5"
spec: node_selector: | aap_node_type: control topology_spread_constraints: | - maxSkew: 1 topologyKey: "kubernetes.io/hostname" whenUnsatisfiable: "ScheduleAnyway" labelSelector: matchLabels: aap_node_type: control tolerations: | - key: "dedicated" operator: "Equal" value: "AutomationController" effect: "NoSchedule"
2.2.8. Java The java-1.6.0-openjdk package adds support for the Java programming language. This package provides the java interpreter. The java-1.6.0-openjdk-devel package contains the javac compiler, as well as the libraries and header files required for developing Java extensions. Similarly, Red Hat Enterprise Linux also provides Java 7 via the java-1.7.0-openjdk* packages and Java 8 via the java-1.8.0-openjdk* packages. 2.2.8.1. Java Documentation For more information about Java, see man java . Some associated utilities also have their own respective man pages. You can also install other Java documentation packages for more details about specific Java utilities. By convention, such documentation packages have the javadoc suffix (for example, dbus-java-javadoc ). The main site for the development of Java is hosted on http://openjdk.java.net/ . The main site for the library runtime of Java is hosted on http://icedtea.classpath.org .

Commands: