mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. System requirements Installing a private automation hub instance requires the following: Table 1.1. System Requirements Required Subscription Valid Red Hat Ansible Automation Platform OS RHEL 8.4 or later 64-bit (x86), or RHEL 9.0 or later 64-bit (x86) Ansible Version 2.14 required RAM 8 GB minimum CPUs 2 minimum Disk 60 GB dedicated hard disk space Dependent on size of collections stored Browser A currently supported version of Mozilla Firefox or Google Chrome Database PostgreSQL version 13 Note You cannot install Ansible Automation Platform and a private automation hub instance on the same node. The inventory file can handle the installation of both Ansible Automation Platform and automation hub. These instructions are only for the installation of Ansible Automation Platform.

Commands:
Chapter 6. Migrating from synchronization to trust manually by using ID views In RHEL 8, the synchronization approach to integrating RHEL systems into Active Directory (AD) indirectly is deprecated. Red Hat recommends migrating to the approach based on a trust between Identity Management (IdM) and AD instead. This chapter describes how to migrate from synchronization to trust manually, by using ID views. 6.1. Migrating from synchronization to trust manually using ID views You can use ID views to manually change the POSIX attributes that Active Directory (AD) previously generated for AD users. Prerequisites On RHEL 7, you configured synchronisation between RHEL Identity Management (IdM) and AD. Procedure Create a backup of the original synchronized user and group entries. Create a trust with the synchronized domain. See For details, see Installing trust between IdM and AD . For every synchronized user or group, preserve the UID and GIDs generated by IdM by doing one of the following: Individually create an ID view applied to the specific host and add user ID overrides to the view. Create user ID overrides in the Default Trust View. Note Only IdM users can manage ID views. AD users cannot. Delete the original synchronized user or group entries. Additional resources Using ID views for Active Directory users Defining a different attribute value for a user account on different hosts

Commands:
5.44. cyrus-sasl 5.44.1. RHBA-2012:1495 - cyrus-sasl bug fix update Updated cyrus-sasl packages that fix a bug are now available for Red Hat Enterprise Linux 6. The cyrus-sasl packages contain the Cyrus implementation of Simple Authentication and Security Layer (SASL). SASL is a method for adding authentication support to connection-based protocols. Bug Fix BZ# 878357 Previously, the GSSAPI plug-in kept credential handles open the whole time a client was connected. These handles hold a pointer to a Kerberos replay cache structure. When the replay cache is a file, that structure includes an open file descriptor. When too many clients were using GSSAPI, the server could run out of file handles. Consequently, the client could become unresponsive until restarted. With this update, a GSSAPI credential handle is closed immediately after the plug-in gets the security context, thus preventing this bug. Users of cyrus-sasl are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 32. Using LLDP to debug network configuration problems You can use the Link Layer Discovery Protocol (LLDP) to debug network configuration problems in the topology. This means that, LLDP can report configuration inconsistencies with other hosts or routers and switches. 32.1. Debugging an incorrect VLAN configuration using LLDP information If you configured a switch port to use a certain VLAN and a host does not receive these VLAN packets, you can use the Link Layer Discovery Protocol (LLDP) to debug the problem. Perform this procedure on the host that does not receive the packets. Prerequisites The nmstate package is installed. The switch supports LLDP. LLDP is enabled on neighbor devices. Procedure Create the ~/enable-LLDP-enp1s0.yml file with the following content: interfaces: - name: enp1s0 type: ethernet lldp: enabled: true Use the ~/enable-LLDP-enp1s0.yml file to enable LLDP on interface enp1s0 : Display the LLDP information: Verify the output to ensure that the settings match your expected configuration. For example, the LLDP information of the interface connected to the switch shows that the switch port this host is connected to uses VLAN ID 448 : - type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488 If the network configuration of the enp1s0 interface uses a different VLAN ID, change it accordingly. Additional resources Configuring VLAN tagging

Commands:
interfaces: - name: enp1s0 type: ethernet lldp: enabled: true
nmstatectl apply ~/enable-LLDP-enp1s0.yml
nmstatectl show enp1s0 - name: enp1s0 type: ethernet state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false lldp: enabled: true neighbors: - - type: 5 system-name: Summit300-48 - type: 6 system-description: Summit300-48 - Version 7.4e.1 (Build 5) 05/27/05 04:53:11 - type: 7 system-capabilities: - MAC Bridge component - Router - type: 1 _description: MAC address chassis-id: 00:01:30:F9:AD:A0 chassis-id-type: 4 - type: 2 _description: Interface name port-id: 1/1 port-id-type: 5 - type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488 oui: 00:80:c2 subtype: 3 - type: 127 ieee-802-3-mac-phy-conf: autoneg: true operational-mau-type: 16 pmd-autoneg-cap: 27648 oui: 00:12:0f subtype: 1 - type: 127 ieee-802-1-ppvids: - 0 oui: 00:80:c2 subtype: 2 - type: 8 management-addresses: - address: 00:01:30:F9:AD:A0 address-subtype: MAC interface-number: 1001 interface-number-subtype: 2 - type: 127 ieee-802-3-max-frame-size: 1522 oui: 00:12:0f subtype: 4 mac-address: 82:75:BE:6F:8C:7A mtu: 1500
- type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488
7.148. openssl-ibmca 7.148.1. RHBA-2015:0792 - openssl-ibmca bug fix update Updated openssl-ibmca packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The openssl-ibmca packages provide a dynamic OpenSSL engine for the IBM eServer Cryptographic Accelerator (ICA) crypto hardware on IBM eServer zSeries machines. Bug Fixes BZ# 1075183 Prior to this update, an incorrect flag was passed to the elliptic curve crypto signing method. Consequently, the selftest in the OpenSSL library failed when the IBMCA engine was in use. Now, the correct flag is passed, and the OpenSSL selftest succeeds. BZ# 1193071 Previously, the IBMCA engine truncated the SHA256 hash data computed by the Library for IBM Cryptographic Architecture (libica). As a consequence, the certificate verification process used a malformed hash and failed. Now, the correct length is used for the SHA256 data, and certificate verification proceeds without errors. Users of openssl-ibmca are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 24. Installing DNS on an existing IdM server Install the DNS service on an Identity Management (IdM) server that was originally installed without it. Prerequisites You understand the advantages and limitations of using IdM with integrated DNS as described in Installing an IdM server: With integrated DNS, with an integrated CA as the root CA . You have root access to the IdM server. Procedure Optional: Verify that DNS is not already installed on the IdM server. The output confirms that IdM DNS is not available on the server. Enable the idm:DL1 stream: Download the ipa-dns-server package and its dependencies: Start the script to install DNS on the server: The script prompts for per-server DNS forwarders. To configure per-server DNS forwarders, enter yes , and then follow the instructions on the command line. The installation process will add the forwarder IP addresses to the IdM LDAP. For the forwarding policy default settings, see the --forward-policy description in the ipa-dns-install (1) man page. If you do not want to use DNS forwarding, enter no . With no DNS forwarders, hosts in your IdM domain will not be able to resolve names from other, internal, DNS domains in your infrastructure. The hosts will only be left with public DNS servers to resolve their DNS queries. The script prompts to check if any DNS reverse (PTR) records for the IP addresses associated with the server need to be configured. If you run the search and missing reverse zones are discovered, the script asks you whether to create the reverse zones along with the PTR records. Note Using IdM to manage reverse zones is optional. You can use an external DNS service for this purpose instead. Additional resources man ipa-dns-install(1)

Commands:
ipa server-role-show r8server.idm.example.com Role name: DNS server Server name: r8server.idm.example.com Role name: DNS server Role status: absent
yum module enable idm:DL1
yum module install idm:DL1/dns
ipa-dns-install
Do you want to configure DNS forwarders? [yes]:
Do you want to search for missing reverse zones? [yes]:
Do you want to create reverse zone for IP 192.0.2.1 [yes]: Please specify the reverse zone name [2.0.192.in-addr.arpa.]: Using reverse zone(s) 2.0.192.in-addr.arpa.
Chapter 15. Configuring NetworkManager to ignore certain devices By default, NetworkManager manages all devices except the ones described in the /usr/lib/udev/rules.d/85-nm-unmanaged.rules file. To ignore certain other devices, you can configure them in NetworkManager as unmanaged . 15.1. Permanently configuring a device as unmanaged in NetworkManager You can permanently configure devices as unmanaged based on several criteria, such as the interface name, MAC address, or device type. Procedure Optional: Display the list of devices to identify the device or MAC address you want to set as unmanaged : Create the /etc/NetworkManager/conf.d/99-unmanaged-devices.conf file with the following content: To configure a specific interface as unmanaged, add: To configure a device with a specific MAC address as unmanaged, add: To configure all devices of a specific type as unmanaged, add: To set multiple devices as unmanaged, separate the entries in the unmanaged-devices parameter with a semicolon, for example: Reload the NetworkManager service: Verification Display the list of devices: The unmanaged state to the enp1s0 device indicates that NetworkManager does not manage this device. Troubleshooting If the device is not shown as unmanaged , display the NetworkManager configuration: If the output does not match the settings that you configured, ensure that no configuration file with a higher priority overrides your settings. For details about how NetworkManager merges multiple configuration files, see the NetworkManager.conf(5) man page on your system. 15.2. Temporarily configuring a device as unmanaged in NetworkManager You can temporarily configure devices as unmanaged , for example, for testing purposes. Procedure Optional: Display the list of devices to identify the device you want to set as unmanaged : Set the enp1s0 device to the unmanaged state: Verification Display the list of devices: The unmanaged state to the enp1s0 device indicates that NetworkManager does not manage this device. Additional resources NetworkManager.conf(5) man page on your system

Commands:
ip link show 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:74:79:56 brd ff:ff:ff:ff:ff:ff
[keyfile] unmanaged-devices=interface-name:enp1s0
[keyfile] unmanaged-devices=mac:52:54:00:74:79:56
[keyfile] unmanaged-devices=type:ethernet
[keyfile] unmanaged-devices=interface-name:enp1s0;interface-name:enp7s0
systemctl reload NetworkManager
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet unmanaged --
NetworkManager --print-config [keyfile] unmanaged-devices=interface-name:enp1s0
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet disconnected --
nmcli device set enp1s0 managed no
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet unmanaged --
Chapter 4. Red Hat build of OpenJDK 8.0.422 release notes The latest Red Hat build of OpenJDK 8 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from Red Hat build of OpenJDK 8 releases. Note For all the other changes and security fixes, see OpenJDK 8u422 Released . Red Hat build of OpenJDK new features and enhancements Review the following release notes to understand new features and feature enhancements that Red Hat build of OpenJDK 8.0.422 provides: System properties for controlling the keep-alive behavior of HTTPURLConnection Red Hat build of OpenJDK 8.0.422 includes the following new system properties that you can use to control the keep-alive behavior of HTTPURLConnection in situations where the server does not specify a keep-alive time: The http.keepAlive.time.server property controls the number of seconds before an idle connection to a server is closed. The http.keepAlive.time.proxy property controls the number of seconds before an idle connection to a proxy is closed. Note If the server or proxy specifies a keep-alive time in a Keep-Alive response header, this keep-alive time takes precedence over any value that you specify for the http.keepAlive.time.server or http.keepAlive.time.proxy property. See JDK-8278067 (JDK Bug System) . GlobalSign R46 and E46 root certificates added In Red Hat build of OpenJDK 8.0.422, the cacerts truststore includes two GlobalSign TLS root certificates: Certificate 1 Name: GlobalSign Alias name: globalsignr46 Distinguished name: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE Certificate 2 Name: GlobalSign Alias name: globalsigne46 Distinguished name: CN=GlobalSign Root E46, O=GlobalSign nv-sa, C=BE See JDK-8316138 (JDK Bug System) .

Commands:
Chapter 5. Configuring Transport Security 5.1. Transport Security Configuration There are three types of direct remote transports, each with its own encryption configuration: teiid - By default, this only encrypts login traffic when none of the other configuration properties are used. odbc - This default to "no SSL". odata Here is an example OData transport configuration: Here is a configuration for OData: Note The pg protocol for ODBC access uses cleartext username and password authentication by default. You should consider using a security domain that utilizes non-plaintext passwords, kerberos, or SSL. The SSL configuration is part of the transport configuration in the Teiid subsystem. Other indirect methods of access to the Teiid subsystem rely on the container settings for HTTP/HTTPS access.

Commands:
<transport name="jdbc" socket-binding="teiid-jdbc" protocol="teiid"> <authentication security-domain="teiid-security"/> </transport> <transport name="odbc" socket-binding="teiid-odbc" protocol="pg"> <authentication security-domain="teiid-security"/> <ssl mode="disabled"/> </transport>
<transport name="odata"> <authentication security-domain="teiid-security"/> </transport>
3.6.3. Starting, Stopping and Restarting stunnel To start stunnel , run the following command as root : By default, stunnel uses /var/log/secure to log its output. To terminate stunnel , kill the process by running the following command as root : If you edit the configuration file while stunnel is running, terminate stunnel and start it again for your changes to take effect.

Commands:
~]# stunnel /etc/stunnel/stunnel.conf
~]# kill `cat /var/run/stunnel/stunnel.pid`
C.4.3. Format the Device as a dm-crypt/LUKS Encrypted Device Warning The command below will destroy any existing data on the device. Note For more information, read the cryptsetup(8) man page. After supplying the passphrase twice the device will be formatted for use. To verify, use the following command: To see a summary of the encryption information for the device, use the following command:

Commands:
cryptsetup luksFormat <device>
cryptsetup isLuks <device> && echo Success
cryptsetup luksDump <device>
8.6. Snapshot Deletion You can delete individual snapshots that are no longer required. Deleting a snapshot removes the ability to restore a virtual disk to that particular restoration point. It does not necessarily reclaim the disk space consumed by the snapshot, nor does it delete the data. The disk space will only be reclaimed if a subsequent snapshot has overwritten the data of the deleted snapshot. For example, if the third snapshot out of five snapshots is deleted, the unchanged data in the third snapshot must be preserved on the disk for the fourth and fifth snapshots to be usable; however, if the fourth or fifth snapshot has overwritten the data of the third, then the third snapshot has been made redundant and the disk space can be reclaimed. Aside from potential disk space reclamation, deleting a snapshot may also improve the performance of the virtual machine. Figure 8.4. Snapshot Deletion Snapshot deletion is handled as an asynchronous block job in which VDSM maintains a record of the operation in the recovery file for the virtual machine so that the job can be tracked even if VDSM is restarted or the virtual machine is shut down during the operation. Once the operation begins, the snapshot being deleted cannot be previewed or used as a restoration point, even if the operation fails or is interrupted. In operations in which the active layer is to be merged with its parent, the operation is split into a two-stage process during which data is copied from the active layer to the parent layer, and disk writes are mirrored to both the active layer and the parent. Finally, the job is considered complete once the data in the snapshot being deleted has been merged with its parent snapshot and VDSM synchronizes the changes throughout the image chain. Note If the deletion fails, fix the underlying problem (for example, a failed host, an inaccessible storage device, or even a temporary network issue) and try again.

Commands:
Chapter 40. GAV check management In Business Central, projects are identified by the Group ID , Artifact ID , and Version (GAV) Maven naming convention. GAV values differentiate projects and project versions as well as identify dependencies with particular projects. By default, Business Central detects duplicate GAVs. This feature can be disabled by users with the admin role. 40.1. Configuring GAV checks and child GAV edition This procedure describes how to configure GAV checks in Business Central. Procedure In Business Central, go to Menu Design Projects and click the project name. In the project window, click the Settings tab. In the General Settings tab, perform any of the following tasks: To enable other projects to have the same GAV, select the Disable GAV conflict check check box. To enable child projects to have GAV edition, select the Allow child GAV edition check box. Click Save . Note You can click Reset to undo all changes. Click Save to confirm the changes. Note Duplicate GAV detection is disabled for projects in Development Mode . To enable duplicate GAV detection in Business Central, go to project Settings General Settings Version and toggle the Development Mode option to OFF (if applicable). 40.2. Configuring GAV checks for all projects This procedure describes how to configure GAV checks for all projects in Business Central. You can also disable GAV checks at system startup. Procedures In Business Central, select the Admin icon in the top-right corner of the screen and select Projects . The Projects window opens. In the Advanced GAV preferences tab, perform any of the following tasks: To enable other projects to have the same GAV, select the Disable GAV conflict check check box. To enable child projects to have GAV edition, select the Allow child GAV edition check box. Click Save . Note You can also disable the duplicate GAV detection feature by setting the org.guvnor.project.gav.check.disabled system property to true for Business Central at system startup:

Commands:
~/EAP_HOME/bin/standalone.sh -c standalone-full.xml -Dorg.guvnor.project.gav.check.disabled=true
Chapter 383. Zip Deflate Compression DataFormat Available as of Camel version 2.12 The Zip Data Format is a message compression and de-compression format. Messages marshalled using Zip compression can be unmarshalled using Zip decompression just prior to being consumed at the endpoint. The compression capability is quite useful when you deal with large XML and Text based payloads. It facilitates more optimal use of network bandwidth while incurring a small cost in order to compress and decompress payloads at the endpoint. INFO:*About using with Files* The Zip data format, does not (yet) have special support for files. Which means that when using big files, the entire file content is loaded into memory. This is subject to change in the future, to allow a streaming based solution to have a low memory footprint. 383.1. Options The Zip Deflate Compression dataformat supports 2 options, which are listed below. Name Default Java Type Description compressionLevel -1 Integer To specify a specific compression between 0-9. -1 is default compression, 0 is no compression, and 9 is best compression. contentTypeHeader false Boolean Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. 383.2. Marshal In this example we marshal a regular text/XML payload to a compressed payload employing zip compression Deflater.BEST_COMPRESSION and send it an ActiveMQ queue called MY_QUEUE. from("direct:start").marshal().zip(Deflater.BEST_COMPRESSION).to("activemq:queue:MY_QUEUE"); Alternatively if you would like to use the default setting you could send it as from("direct:start").marshal().zip().to("activemq:queue:MY_QUEUE"); 383.3. Unmarshal In this example we unmarshal a zipped payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the UnZippedMessageProcessor. Note that the compression Level employed during the marshalling should be identical to the one employed during unmarshalling to avoid errors. from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor()); 383.4. Dependencies This data format is provided in camel-core so no additional dependencies are needed.

Commands:
from("direct:start").marshal().zip(Deflater.BEST_COMPRESSION).to("activemq:queue:MY_QUEUE");
from("direct:start").marshal().zip().to("activemq:queue:MY_QUEUE");
from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor());
2.4. Discard unused blocks Batch discard and online discard operations are features of mounted file systems that discard blocks not in use by the file system. They are useful for both solid-state drives and thinly-provisioned storage. Batch discard operations are run explicitly by the user with the fstrim command. This command discards all unused blocks in a file system that match the user's criteria. Both operation types are supported for use with ext4 file systems as of Red Hat Enterprise Linux 6.2 and later, so long as the block device underlying the file system supports physical discard operations. This is also the case with XFS file systems as of Red Hat Enterprise Linux 6.4 and later. Physical discard operations are supported if the value of /sys/block/ device /queue/discard_max_bytes is not zero. Online discard operations are specified at mount time with the -o discard option (either in /etc/fstab or as part of the mount command), and run in realtime without user intervention. Online discard operations only discard blocks that are transitioning from used to free. Online discard operations are supported on ext4 file systems as of Red Hat Enterprise Linux 6.2 and later, and on XFS file systems as of Red Hat Enterprise Linux 6.4 and later. Red Hat recommends batch discard operations unless the system's workload is such that batch discard is not feasible, or online discard operations are necessary to maintain performance.

Commands: