mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Choosing and obtaining a Red Hat Ansible Automation Platform installer Choose the Red Hat Ansible Automation Platform installer you need based on your Red Hat Enterprise Linux environment internet connectivity. Review the following scenarios to decide which Red Hat Ansible Automation Platform installer meets your needs. 7.1. Installing with internet access Choose the Red Hat Ansible Automation Platform installer if your Red Hat Enterprise Linux environment is connected to the internet. Installing with internet access retrieves the latest required repositories, packages, and dependencies. Choose one of the following ways to set up your Ansible Automation Platform installer. Tarball install Navigate to the Red Hat Ansible Automation Platform download page. Click Download Now for the Ansible Automation Platform <latest-version> Setup . Transfer the file to the target server using scp or curl : Using scp : Run the following command, replacing private_key.pem , user , and server_ip with your appropriate values: USD scp -i private_key.pem aap-bundled-installer.tar.gz user@server_ip: Using curl : If the setup file URL is available, you can download it directly to the target server using curl . Replace <download_url> with the file URL: USD curl -0 <download_url> Note If the file needs to be extracted after downloading, run the following command: USD tar xvzf aap-bundled-installer.tar.gz RPM install Install Ansible Automation Platform Installer Package v.2.5 for RHEL 8 for x86_64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.5-for-rhel-8-x86_64-rpms ansible-automation-platform-installer v.2.5 for RHEL 9 for x86_64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms ansible-automation-platform-installer Note dnf install enables the repo as the repo is disabled by default. When you use the RPM installer, the files are placed under the /opt/ansible-automation-platform/installer directory. 7.2. Installing without internet access Use the Red Hat Ansible Automation Platform Bundle installer if you are unable to access the internet, or would prefer not to install separate components and dependencies from online repositories. Access to Red Hat Enterprise Linux repositories is still needed. All other dependencies are included in the tar archive. Procedure Go to the Red Hat Ansible Automation Platform download page. Click Download Now for the Ansible Automation Platform <latest-version> Setup Bundle . Extract the files: USD tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz

Commands:
scp -i private_key.pem aap-bundled-installer.tar.gz user@server_ip:
curl -0 <download_url>
tar xvzf aap-bundled-installer.tar.gz
sudo dnf install --enablerepo=ansible-automation-platform-2.5-for-rhel-8-x86_64-rpms ansible-automation-platform-installer
sudo dnf install --enablerepo=ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms ansible-automation-platform-installer
tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz
Appendix B. Revision History Revision History Revision 1.0-21 Tue April 13 2016 Jiri Herrmann Update of the Red Hat Enterprise Linux 6.5 Release Notes to correct the description for Enabling and Disabling CPUs in Linux Guests. Revision 1.0-20 Tue Apr 7 2015 Milan Navratil Update of the Red Hat Enterprise Linux 6.5 Release Notes to fix the version of the QLogic qla2xxx driver. Revision 1.0-18 Mon Feb 17 2014 Eliska Slobodova Republished the book to include a note about support for EDEV. Revision 1.0-16 Fri Dec 20 2013 Eliska Slobodova Republished the book to include notes about networking controllers. Revision 1.0-13 Fri Dec 13 2013 Eliska Slobodova Republished the book to include a security note. Revision 1.0-12 Thu Nov 21 2013 Eliska Slobodova Release of the Red Hat Enterprise Linux 6.5 Release Notes. Revision 1.0-3 Thu Oct 3 2013 Eliska Slobodova Release of the Red Hat Enterprise Linux 6.5 Beta Release Notes.

Commands:
Chapter 15. Disabling anonymous binds If a user attempts to connect to Directory Server without supplying any credentials, this operation is called anonymous bind . Anonymous binds simplify searches and read operations, such as finding a phone number in the directory by not requiring users to authenticate first. However, anonymous binds can also be a security risk, because users without an account are able to access the data. Warning By default, anonymous binds are enabled in Directory Server for search and read operations. This allows unauthorized access to user entries as well as configuration entries, such as the root directory server entry (DSE). 15.1. Disabling anonymous binds using the command line To increase the security, you can disable anonymous binds. Procedure Set the nsslapd-allow-anonymous-access configuration parameter to off : # dsconf -D " cn=Directory Manager " ldap://server.example.com config replace nsslapd-allow-anonymous-access=off Verification Run a search without specifying a user account: # ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed 15.2. Disabling anonymous binds using the web console To increase the security, you can disable anonymous binds. Prerequisites You are logged in to the instance in the web console. Procedure Navigate to Server Server Settings Advanced Settings . Set the Allow Anonymous Access parameter to off . Click Save . Verification Run a search without specifying a user account: # ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed

Commands:
dsconf -D " cn=Directory Manager " ldap://server.example.com config replace nsslapd-allow-anonymous-access=off
ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed
ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed
6.2. Virtual Machine Network Quality of Service Virtual machine network quality of service is a feature that allows you to create profiles for limiting both the inbound and outbound traffic of individual virtual network interface controllers. With this feature, you can limit bandwidth in a number of layers, controlling the consumption of network resources. 6.2.1. Creating a Virtual Machine Network Quality of Service Entry Create a virtual machine network quality of service entry to regulate network traffic when applied to a virtual network interface controller (vNIC) profile, also known as a virtual machine network interface profile. Creating a Virtual Machine Network Quality of Service Entry Click Compute Data Centers . Click a data center's name to open the details view. Click the QoS tab. Under VM Network , click New . Enter a Name for the virtual machine network quality of service entry. Enter the limits for the Inbound and Outbound network traffic. Click OK . You have created a virtual machine network quality of service entry that can be used in a virtual network interface controller. 6.2.2. Settings in the New Virtual Machine Network QoS and Edit Virtual Machine Network QoS Windows Explained Virtual machine network quality of service settings allow you to configure bandwidth limits for both inbound and outbound traffic on three distinct levels. Table 6.1. Virtual Machine Network QoS Settings Field Name Description Data Center The data center to which the virtual machine network QoS policy is to be added. This field is configured automatically according to the selected data center. Name A name to represent the virtual machine network QoS policy within the Manager. Inbound The settings to be applied to inbound traffic. Select or clear the Inbound check box to enable or disable these settings. Average : The average speed of inbound traffic. Peak : The speed of inbound traffic during peak times. Burst : The speed of inbound traffic during bursts. Outbound The settings to be applied to outbound traffic. Select or clear the Outbound check box to enable or disable these settings. Average : The average speed of outbound traffic. Peak : The speed of outbound traffic during peak times. Burst : The speed of outbound traffic during bursts. To change the maximum value allowed by the Average , Peak , or Burst fields, use the engine-config command to change the value of the MaxAverageNetworkQoSValue , MaxPeakNetworkQoSValue , or MaxBurstNetworkQoSValue configuration keys. You must restart the ovirt-engine service for any changes to take effect. For example: 6.2.3. Removing a Virtual Machine Network Quality of Service Entry Remove an existing virtual machine network quality of service entry. Removing a Virtual Machine Network Quality of Service Entry Click Compute Data Centers . Click a data center's name to open the details view. Click the QoS tab. Under VM Network , select a virtual machine network quality of service entry and click Remove . Click OK .

Commands:
engine-config -s MaxAverageNetworkQoSValue=2048 systemctl restart ovirt-engine
Chapter 4. Reviewing and resolving migration issues You can review and resolve migration issues identified by the MTR plugin in the left pane. 4.1. Reviewing issues You can use the MTR plugin icons to prioritize issues based on their severity. You can see which issues have a Quick Fix automatic code replacement and which do not. The results of an analysis are displayed in a directory format, showing the hints and classifications for each application analyzed. A hint is a read-only snippet of code that contains a single issue that you should or must address before you can modernize or migrate an application. Often a Quick Fix is suggested, which you can accept or ignore. A classification is a file that has an issue but does not have any suggested Quick Fixes. You can edit a classification. Procedure In the Migration Toolkit for Runtimes view, select a run configuration directory in the left pane. Click Results . The modules and applications of the run configuration are displayed, with hints and classifications beneath each application. Prioritize issues based on the following icons, which are displayed to each hint: : You must fix this issue in order to migrate or modernize the application. : You might need to fix this issue in order to migrate or modernize the application Optional: To learn more about a hint, right-click it and select Show More Details . 4.2. Resolving issues You can resolve issues by doing one of the following: Using a Quick Fix to fix a code snippet that has a hint Editing the code of a file that appears in a classification 4.2.1. Using a Quick Fix You can use a Quick Fix automatic code replacement to save time and ensure consistency in resolving repetitive issues. Quick Fixes are available for many issues displayed in the Hints section of the Results directory. Procedure In the left pane, click a hint that has an error indicator. Any Quick Fixes are displayed as child folders with the Quick Fix icon ( ) on their left side. Right-click a Quick Fix and select Preview Quick Fix . The current code and the suggested change are displayed in the Preview Quick Fix window. To accept the suggested fix, click Apply Quick Fix . Optional: Right-click the issue and select Mark As Complete . A green check ( ) is displayed by the hint, replacing the error indicator. 4.2.2. Editing the code of a file You can directly edit a file displayed in the Classifications section of the Results directory. These files do not have any Quick Fixes. Procedure In the left pane, click the file you want to edit. Make any changes needed to the code and save the file. Optional: Right-click the issue and select Mark as Complete or Delete . If you select Mark as Complete , a green check ( ) is displayed by the hint, replacing the error indicator.

Commands:
2.47. RHEA-2011:0657 - new package: tomcatjss A new tomcatjss package is now available for Red Hat Enterprise Linux 6. The tomcatjss package provides a Java Secure Socket Extension (JSSE) implementation using Java Security Services (JSS) for Tomcat 6. This enhancement update provides the Java Native Interface (JNI) extension for JSS based on Network Security Services (NSS). (BZ# 643544 ) All tomcat users who wish to use NSS for servlet connectors are advised to install this new package.

Commands:
Chapter 5. Changing how your system behaves when you close the laptop lid When you close the lid of your laptop, it suspends by default to save battery. You can customize this behavior according to your preferences. WARNING Some laptops can overheat if they are left running with the lid closed, especially in confined spaces. Consider whether changing this setting is safe for your laptop, especially if you intend to keep the laptop running with the lid closed for extended periods of time. Prerequisites Administrative access. Procedure Open the /etc/systemd/logind.conf configuration file. Look for the line that says HandleLidSwitch=suspend . If the line starts with the # symbol, remove it to enable the setting. Replace suspend with one of the following options: poweroff to shut down the computer. lock to lock the screen. ignore to do nothing. For example, to lock the screen upon closing the lid, use this setting: Save your changes and close the editor.

Commands:
HandleLidSwitch=lock
4.6. Controlling LVM Device Scans with Filters At startup, the vgscan command is run to scan the block devices on the system looking for LVM labels, to determine which of them are physical volumes and to read the metadata and build up a list of volume groups. The names of the physical volumes are stored in the cache file of each node in the system, /etc/lvm/.cache . Subsequent commands may read that file to avoiding rescanning. You can control which devices LVM scans by setting up filters in the lvm.conf configuration file. The filters in the lvm.conf file consist of a series of simple regular expressions that get applied to the device names in the /dev directory to decide whether to accept or reject each block device found. The following examples show the use of filters to control which devices LVM scans. Note that some of these examples do not necessarily represent best practice, as the regular expressions are matched freely against the complete pathname. For example, a/loop/ is equivalent to a/.*loop.*/ and would match /dev/solooperation/lvol1 . The following filter adds all discovered devices, which is the default behavior as there is no filter configured in the configuration file: The following filter removes the cdrom device in order to avoid delays if the drive contains no media: The following filter adds all loop and removes all other block devices: The following filter adds all loop and IDE and removes all other block devices: The following filter adds just partition 8 on the first IDE drive and removes all other block devices: For more information on the lvm.conf file, see Appendix B, The LVM Configuration Files and the lvm.conf (5) man page.

Commands:
filter = [ "a/.*/" ]
filter = [ "r|/dev/cdrom|" ]
filter = [ "a/loop.*/", "r/.*/" ]
filter =[ "a|loop.*|", "a|/dev/hd.*|", "r|.*|" ]
filter = [ "a|^/dev/hda8USD|", "r/.*/" ]
Chapter 2. Managed broker configuration When you deploy AMQ Streams on OpenShift, you specify broker configuration through the config property of the Kafka custom resource. However, certain broker configuration options are managed directly by AMQ Streams. As such, if you are using AMQ Streams on OpenShift, you cannot configure the following options: broker.id to specify the ID of the Kafka broker log.dirs directories for log data zookeeper.connect configuration to connect Kafka with ZooKeeper listeners to expose the Kafka cluster to clients authorization mechanisms to allow or decline actions executed by users authentication mechanisms to prove the identity of users requiring access to Kafka Broker IDs start from 0 (zero) and correspond to the number of broker replicas. Log directories are mounted to /var/lib/kafka/data/kafka-log IDX based on the spec.kafka.storage configuration in the Kafka custom resource. IDX is the Kafka broker pod index. For a list of exclusions, see the KafkaClusterSpec schema reference . These exclusions don't apply when using AMQ Streams on RHEL. In this case, you need to add these properties in your basic broker configuration to identify your brokers and provide secure access. Example broker configuration for AMQ Streams on RHEL # ... broker.id = 1 log.dirs = /var/lib/kafka zookeeper.connect = zoo1.my-domain.com:2181,zoo2.my-domain.com:2181,zoo3.my-domain.com:2181 listeners = internal-1://:9092 authorizer.class.name = kafka.security.auth.SimpleAclAuthorizer ssl.truststore.location = /path/to/truststore.jks ssl.truststore.password = 123456 ssl.client.auth = required # ... Additional resources Configuring Kafka on OCP Configuring Kafka on RHEL

Commands:
broker.id = 1 log.dirs = /var/lib/kafka zookeeper.connect = zoo1.my-domain.com:2181,zoo2.my-domain.com:2181,zoo3.my-domain.com:2181 listeners = internal-1://:9092 authorizer.class.name = kafka.security.auth.SimpleAclAuthorizer ssl.truststore.location = /path/to/truststore.jks ssl.truststore.password = 123456 ssl.client.auth = required
2.3.2. Have Each Node Allocate its Own Files, If Possible Due to the way the distributed lock manager (DLM) works, there will be more lock contention if all files are allocated by one node and other nodes need to add blocks to those files. In GFS (version 1), all locks were managed by a central lock manager whose job was to control locking throughout the cluster. This grand unified lock manager (GULM) was problematic because it was a single point of failure. GFS2's replacement locking scheme, DLM, spreads the locks throughout the cluster. If any node in the cluster goes down, its locks are recovered by the other nodes. With DLM, the first node to lock a resource (like a file) becomes the "lock master" for that lock. Other nodes may lock that resource, but they have to ask permission from the lock master first. Each node knows which locks for which it is the lock master, and each node knows which node it has lent a lock to. Locking a lock on the master node is much faster than locking one on another node that has to stop and ask permission from the lock's master. As in many file systems, the GFS2 allocator tries to keep blocks in the same file close to one another to reduce the movement of disk heads and boost performance. A node that allocates blocks to a file will likely need to use and lock the same resource groups for the new blocks (unless all the blocks in that resource group are in use). The file system will run faster if the lock master for the resource group containing the file allocates its data blocks (that is, it is faster to have the node that first opened the file do all the writing of new blocks).

Commands:
probe::ioscheduler.elv_add_request Name probe::ioscheduler.elv_add_request - probe to indicate request is added to the request queue. Synopsis Values disk_major Disk major no of request. rq Address of request. q Pointer to request queue. elevator_name The type of I/O elevator currently enabled. disk_minor Disk minor number of request. rq_flags Request flags.

Commands:
ioscheduler.elv_add_request
4.9.2. Mount with noatime The noatime Linux mount option can be specified when the file system is mounted, which disables atime updates on that file system. Usage BlockDevice Specifies the block device where the GFS2 file system resides. MountPoint Specifies the directory where the GFS2 file system should be mounted. Example In this example, the GFS2 file system resides on the /dev/vg01/lvol0 and is mounted on directory /mygfs2 with atime updates turned off.

Commands:
mount BlockDevice MountPoint -o noatime
mount /dev/vg01/lvol0 /mygfs2 -o noatime
Chapter 4. General Principles of Information Security The following general principles provide an overview of good security practices: Encrypt all data transmitted over networks to help prevent man-in-the-middle attacks and eavesdropping. It is important to encrypt authentication information, such as passwords. Minimize the amount of software installed and running services. Use security-enhancing software and tools, for example, Security-Enhanced Linux (SELinux) for Mandatory Access Control (MAC), Netfilter iptables for packet filtering (firewall), and the GNU Privacy Guard (GPG) for encrypting files. If possible, run each network service on a separate system to minimize the risk of one compromised service being used to compromise other services. Maintain user accounts: create and enforce a strong password policy; delete unused user accounts. Routinely review system and application logs. By default, security-relevant system logs are written to /var/log/secure and /var/log/audit/audit.log . Note: sending logs to a dedicated log server helps prevent attackers from easily modifying local logs to avoid detection. Never log in as the root user unless absolutely necessary. It is recommended that administrators use sudo to execute commands as root when required. Users capable of running sudo are specified in /etc/sudoers . Use the visudo utility to edit /etc/sudoers .

Commands:
Chapter 1. Software management tools in Red Hat Enterprise Linux 9 In Red Hat Enterprise Linux (RHEL) 9, use the DNF utility to manage software. For compatibility reasons with major RHEL versions, you can still use the yum command. However, in RHEL 9, yum is an alias for dnf which provides a certain level of compatibility with yum . Note Although RHEL 8 and RHEL 9 are based on DNF , they are compatible with YUM used in RHEL 7.

Commands:
5.304. smartmontools 5.304.1. RHBA-2012:0803 - smartmontools bug fix and enhancement update Updated smartmontools packages that fix various bugs and adds multiple enhancements are now available for Red Hat Enterprise Linux 6. The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA and SCSI hard disks. In many cases, these utilities will provide advanced warning of disk degradation and failure. The smartmontools package has been upgraded to version 5.42, which provides a number of bug fixes and enhancements over the version. This update also features improved support of SATA disks on 3ware 9750 RAID controllers, improved support of SSD devices, and a much larger database of supported devices. (BZ# 697235 , BZ# 698317 ) Bug Fix BZ# 784925 Prior to this update, the format in which certain HP SAS (Serial Attached SCSI) drives returned SMART data was not recognized by smartmontools and the following error message "scsi response fails sanity test" was logged. With this update, smartmontools now correctly recognizes the data and this error no longer occurs. All users of smartmontools are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Appendix A. Revision History Revision History Revision 0.1-12 Tue May 10 2016 Lenka Spackova Moved Btrfs and eCryptfs file systems from Technology Previews to Deprecated Functionality. Revision 0.1-10 Thu Apr 07 2016 Lenka Spackova Removed a fixed known issue (in-place upgrade and zipl ). Revision 0.1-9 Thu Jan 21 2016 Lenka Spackova Added information about the removed systemtap-grapher package to the Deprecated Functionality Chapter. Revision 0.1-8 Thu June 11 2015 Jana Svarova Update of the Red Hat Enterprise Linux 6.6 Technical Notes. Revision 0.1-6 Wed May 27 2015 Milan Navratil Update of the Red Hat Enterprise Linux 6.6 Technical Notes. Revision 0.1-5 Tue Oct 14 2014 Milan Navratil Release of the Red Hat Enterprise Linux 6.6 Technical Notes.

Commands: