mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 18. CIDR range definitions You must specify non-overlapping ranges for the following CIDR ranges. Note Machine CIDR ranges cannot be changed after creating your cluster. Important OVN-Kubernetes, the default network provider in OpenShift Container Platform 4.11 and later, uses the 100.64.0.0/16 IP address range internally. If your cluster uses OVN-Kubernetes, do not include the 100.64.0.0/16 IP address range in any other CIDR definitions in your cluster. 18.1. Machine CIDR In the Machine CIDR field, you must specify the IP address range for machines or cluster nodes. The default is 10.0.0.0/16 . This range must not conflict with any connected networks. 18.2. Service CIDR In the Service CIDR field, you must specify the IP address range for services. The range must be large enough to accommodate your workload. The address block must not overlap with any external service accessed from within the cluster. The default is 172.30.0.0/16 . 18.3. Pod CIDR In the pod CIDR field, you must specify the IP address range for pods. The pod CIDR is the same as the clusterNetwork CIDR and the cluster CIDR. The range must be large enough to accommodate your workload. The address block must not overlap with any external service accessed from within the cluster. The default is 10.128.0.0/14 . You can expand the range after cluster installation. Additional resources Cluster Network Operator Configuration 18.4. Host Prefix In the Host Prefix field, you must specify the subnet prefix length assigned to pods scheduled to individual machines. The host prefix determines the pod IP address pool for each machine. For example, if the host prefix is set to /23 , each machine is assigned a /23 subnet from the pod CIDR address range. The default is /23 , allowing 510 cluster nodes, and 510 pod IP addresses per node.

Commands:
4.338. virt-top 4.338.1. RHBA-2011:1692 - virt-top bug fix and enhancement update An updated virt-top package that fixes three bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The virt-top utility displays statistics of virtualized domains and uses many of the same keys and command line options as the top utility. Bug Fixes BZ# 730208 Prior to this update, the terminal was not properly restored if the --csv flag was given. This update modifies the code so that the terminal is now restored in the correct mode. BZ# 665817 The CSV output of virt-top contains only the headers for the first virtual machine. This update adds a processcsv.py script to virt-top so that the CSV output can now be split up into multiple files, each file containing full headers. BZ# 680031 When a libvirt error happens early during virt-top start-up, an obscure error message can be printed. With this update, the manual page contains added instructions for debugging libvirt errors that can occur during program initialization. Enhancement BZ# 680027 With this update, the domain memory information is now displayed in the CSV output mode. All virt-top users are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
Chapter 2. Enabling view-only access for your private automation hub By enabling view-only access, you can grant access for users to view collections or namespaces on your private automation hub without the need for them to log in. View-only access allows you to share content with unauthorized users while restricting their ability to only view or download source code, without permissions to edit anything on your private automation hub. Enable view-only access for your private automation hub by editing the inventory file found on your Red Hat Ansible Automation Platform installer. If you are installing a new instance of Ansible Automation Platform, follow these steps to add the automationhub_enable_unauthenticated_collection_access and automationhub_enable_unauthenticated_collection_download parameters to your inventory file along with your other installation configurations: If you are updating an existing Ansible Automation Platform installation to include view-only access, add the automationhub_enable_unauthenticated_collection_access and automationhub_enable_unauthenticated_collection_download parameters to your inventory file then run the setup.sh script to apply the updates: Procedure Navigate to the installer. Bundled installer USD cd ansible-automation-platform-setup-bundle-<latest-version> Online installer USD cd ansible-automation-platform-setup-<latest-version> Open the inventory file with a text editor. Add the automationhub_enable_unauthenticated_collection_access and automationhub_enable_unauthenticated_collection_download parameters to the inventory file and set both to True , following the example below: [all:vars] automationhub_enable_unauthenticated_collection_access = True 1 automationhub_enable_unauthenticated_collection_download = True 2 1 Allows unauthorized users to view collections 2 Allows unathorized users to download collections Run the setup.sh script. The installer will now enable view-only access to your automation hub. Verification Once the installation completes, you can verify that you have view-only access on your private automation hub by attempting to view content on your automation hub without logging in. Navigate to your private automation hub. On the login screen, click View only mode . Verify that you are able to view content on your automation hub, such as namespaces or collections, without having to log in.

Commands:
cd ansible-automation-platform-setup-bundle-<latest-version>
cd ansible-automation-platform-setup-<latest-version>
[all:vars] automationhub_enable_unauthenticated_collection_access = True 1 automationhub_enable_unauthenticated_collection_download = True 2
Chapter 83. usage This chapter describes the commands under the usage command. 83.1. usage list List resource usage per project Usage: Table 83.1. Command arguments Value Summary -h, --help Show this help message and exit --start <start> Usage range start date, ex 2012-01-20 (default: 4 weeks ago) --end <end> Usage range end date, ex 2012-01-20 (default: tomorrow) Table 83.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 83.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 83.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 83.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 83.2. usage show Show resource usage for a single project Usage: Table 83.6. Command arguments Value Summary -h, --help Show this help message and exit --project <project> Name or id of project to show usage for --start <start> Usage range start date, ex 2012-01-20 (default: 4 weeks ago) --end <end> Usage range end date, ex 2012-01-20 (default: tomorrow) Table 83.7. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 83.8. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 83.9. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 83.10. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack usage list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--start <start>] [--end <end>]
openstack usage show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] [--project <project>] [--start <start>] [--end <end>]
4.288. seabios 4.288.1. RHBA-2011:1680 - seabios bug fix update An updated seabios package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The seabios package contains a legacy BIOS implementation which can be used as a coreboot payload. Bug Fixes BZ# 727328 Previously, the smp_mtrr array was not large enough to hold all 31 entries of model-specific registers (MSRs) with current qemu-kvm implementations. As a consequence, installation of a Windows Server 2008 32-bit guest failed when more than one virtual CPU was allocated in it. With this update, the size of the smp_mtrr array has been increased to 32 and now Windows Server 2008 guests install successfully in the described scenario. BZ# 733028 On reboot, reinitialization of the USB HID (Human Interface Device) devices was not done before seabios was setting up timers. Consequently, when the "shutdown -r now" command was executed in a guest, the guest became unresponsive, could not be rebooted, and the "usb-kbd: warning: key event queue full" error message was returned. A patch has been provided to address this issue and the guest now reboots properly in the described scenario. BZ# 630975 Previously, seabios only supported address space up to 40 bits per one address. As a consequence, guests with 1 TB of RAM could not boot. A patch has been provided to address this issue, which raises the memory space limit up to 48 bits, thus supporting up to 281 TB of virtual memory in a guest. BZ# 736522 Previously, the S3/S4 power state capability was advertised in the DSDT (Differentiated System Description Table) tables. This could have caused various power management issues. With this update, the S3/S4 capability has been removed from the DSDT tables, thus fixing this bug. BZ# 750191 Previosly, Windows guests failed to generate memory dumps on NMIs (Non-Maskable Interrupts), even if they were properly configured to. With this update, a NMI descriptor has been added to seabios, and Windows guests now generate memory dumps on NMIs correctly. All users of seabios are advised to upgrade to this updated package, which fixes these bugs.

Commands:
5.292. sanlock 5.292.1. RHEA-2012:0996 - sanlock enhancement update Updated sanlock packages that add multiple enhancements are now available for Red Hat Enterprise Linux 6. The sanlock packages provide a shared disk lock manager that uses disk paxos to manage leases on shared storage. Hosts connected to a common Storage Area Network (SAN) can use sanlock to synchronize the access to the shared disks. Both libvirt and vdsm can use sanlock to synchronize access to shared virtual machine (VM) images. The sanlock packages have been upgraded to the latest upstream version, which provides a number of enhancements over the version. (BZ# 782600 ) All users of sanlock are advised to upgrade to these updated packages, which add these enhancements.

Commands:
Appendix B. Troubleshooting: Solutions to Specific Problems For troubleshooting advice for: Servers, see Section B.1, "Identity Management Servers" Replicas, see Section B.2, "Identity Management Replicas" Clients, see Section B.3, "Identity Management Clients" Authentication, see Section B.4, "Logging In and Authentication Problems" Vaults, see Section B.5, "Vaults" B.1. Identity Management Servers B.1.1. External CA Installation Fails The ipa-server-install --external-ca command fails with the following error: The env|grep proxy command displays variables such as the following: What this means: The *_proxy environmental variables are preventing the server from being installed. To fix the problem: Use the following shell script to unset the *_proxy environmental variables: Run the pkidestroy utility to remove the unsuccessful CA subsystem installation: Remove the failed IdM server installation: Retry running ipa-server-install --external-ca . B.1.2. named Daemon Fails to Start After installing an IdM server with integrated DNS, the named-pkcs11 fails to start. The /var/log/messages file includes an error message related to the named-pkcs11 service and the ldap.so library: What this means: The bind-chroot package is installed and is preventing the named-pkcs11 service from starting. To fix the problem: Uninstall the bind-chroot package. Restart the IdM server. B.1.3. Installing a Server Fails on a System with IPv6 Disabled When attempting to install an IdM server on a system with IPv6 disabled, the following error occurs during the installation process: What this means: Installing and running a server requires IPv6 to be enabled on the network. See Section 2.1.3, "System Requirements" . To fix the problem: Enable IPv6 on your system. For details, see How do I disable or enable the IPv6 protocol in Red Hat Enterprise Linux? in Red Hat Knowledgebase. Note that IPv6 is enabled by default on Red Hat Enterprise Linux 7 systems.

Commands:
ipa : CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/ configuration_file ' returned non-zero exit status 1 Configuration of CA failed
env|grep proxy http_proxy=http://example.com:8080 ftp_proxy=http://example.com:8080 https_proxy=http://example.com:8080
for i in ftp http https; do unset USD{i}_proxy; done
pkidestroy -s CA -i pki-tomcat; rm -rf /var/log/pki/pki-tomcat /etc/sysconfig/pki-tomcat /etc/sysconfig/pki/tomcat/pki-tomcat /var/lib/pki/pki-tomcat /etc/pki/pki-tomcat /root/ipa.csr
ipa-server-install --uninstall
ipaserver named[6886]: failed to dynamically load driver 'ldap.so': libldap-2.4.so.2: cannot open shared object file: No such file or directory
yum remove bind-chroot
ipactl restart
CRITICAL Failed to restart the directory server Command '/bin/systemctl restart dirsrv@EXAMPLE.service' returned non-zero exit status 1
33.11. Post-Installation Script Figure 33.14. Post-Installation Script You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area. Important The version of anaconda in releases of Red Hat Enterprise Linux included a version of busybox that provided shell commands in the pre-installation and post-installation environments. The version of anaconda in Red Hat Enterprise Linux 6 no longer includes busybox , and uses GNU bash commands instead. Refer to Appendix G, Alternatives to busybox commands for more information. Important Do not include the %post command. It is added for you. For example, to change the message of the day for the newly installed system, add the following command to the %post section: Note More examples can be found in Section 32.8, "Kickstart Examples" . 33.11.1. Chroot Environment To run the post-installation script outside of the chroot environment, click the checkbox to this option on the top of the Post-Installation window. This is equivalent to using the --nochroot option in the %post section. To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/ . For example, if you select Run outside of the chroot environment , the example must be changed to the following:

Commands:
echo "Welcome!" > /etc/motd
echo "Welcome!" > /mnt/sysimage/etc/motd
Chapter 3. Getting started with Kaoto The following procedure explains how to create and store integrations with Kaoto. Open VS Code and select "Open Folder". In the folder selection dialog select the folder to store your integrations or create a new folder and select it. Open Command Palette ( Ctrl+Shift+P ), paste the following command, and press enter. Create a Camel route using YAML DSL Provide a name for the new file without extension and press enter. The file is created with extension camel.yaml . (Here: demo.camel.yaml ). Select the log step to configure the Message in the configuration panel. Using the icons below the route image, you can choose between a vertical/horizontal layout of the route, zoom in/out, etc. Open Catalog on the far right displays the Camel catalog. There are also several filtering options in the Catalog, which greatly simplifies finding what you need. To add a component to the Camel route, click on the dot pattern of an existing component or invoke the right-click context menu on the step and select "Append" . The camel component Catalog will be displayed, click on the additional component and it will be added to the route. To remove the added component from the Camel route, click on the dot pattern of the existing component or invoke the right-click context menu on the step and select "Delete" . The existing component will be removed from the route. 3.1. Running the Camel Route To get started with simple routes, they can be launched with Camel JBang. With demo.camel.yaml open, click the button Run Camel Application with JBang in the editor quick action menu at the top right of the editor. The terminal will open with the running Camel route. It can take several seconds the first time for Camel JBang to initialize.

Commands:
Create a Camel route using YAML DSL
Chapter 5. Setting up your development environment You can follow the procedures in this section to set up your development environment to create automation execution environments. 5.1. Installing Ansible Builder You can install Ansible Builder using Red Hat Subscription Management (RHSM) to attach your Red Hat Ansible Automation Platform subscription. Attaching your Red Hat Ansible Automation Platform subscription allows you to access subscription-only resources necessary to install ansible-builder . Once you attach your subscription, the necessary repository for ansible-builder is automatically enabled. Note You must have valid subscriptions attached on the host before installing ansible-builder . Procedure In your terminal, run the following command to install Ansible Builder and activate your Ansible Automation Platform repo: # dnf install --enablerepo ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-builder 5.2. Installing Automation content navigator on RHEL from an RPM You can install Automation content navigator on Red Hat Enterprise Linux (RHEL) from an RPM. Prerequisites You have installed RHEL 8 or later. You registered your system with Red Hat Subscription Manager. Note Ensure that you only install the navigator matching your current Red Hat Ansible Automation Platform environment. Procedure Attach the Red Hat Ansible Automation Platform SKU: USD subscription-manager attach --pool=<sku-pool-id> Install Automation content navigator with the following command: # dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-navigator Verification Verify your Automation content navigator installation: USD ansible-navigator --help The following example demonstrates a successful installation: 5.3. Downloading base automation execution environments Base images that ship with Ansible Automation Platform 2.0 are hosted on the Red Hat Ecosystem Catalog (registry.redhat.io). Prerequisites You have a valid Red Hat Ansible Automation Platform subscription. Procedure Log in to registry.redhat.io USD podman login registry.redhat.io Pull the base images from the registry USD podman pull registry.redhat.io/aap/<image name>

Commands:
dnf install --enablerepo ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-builder
subscription-manager attach --pool=<sku-pool-id>
dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-navigator
ansible-navigator --help
podman login registry.redhat.io
podman pull registry.redhat.io/aap/<image name>
Chapter 10. Multi-Source Models 10.1. Multi-Source Models Multi-source models can be used to quickly access data in multiple sources with homogeneous metadata. When you have multiple instances of data that are using identical schema (horizontal sharding), JBoss Data Virtualization can help you aggregate data across all the instances, using "multi-source" models. In this scenario, instead of creating/importing a model for every data source, user must define one source model that represents the schema and configure multiple data "sources" underneath it. During runtime, when a query issued against this model, the query engine analyzes the information and gathers the required data from all the sources configured and aggregates the results and provides in a single result set. Since all sources use the same physical metadata, this feature is most appropriate for accessing the same source type with multiple instances.

Commands:
12.3. JSON Representation of a Storage Domain Example 12.2. A JSON representation of a storage domain

Commands:
{ "storage_domain" : [ { "type" : "data", "master" : "false", "storage" : { "address" : "192.0.2.0", "type" : "nfs", "path" : "/storage/user/nfs" }, "available" : 193273528320, "used" : 17179869184, "committed" : 0, "storage_format" : "v3", "name" : "NFS_01", "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba", "id" : "8827b158-6d2e-442d-a7ee-c6fd4718aaba", "link" : [ { "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba/permissions", "rel" : "permissions" }, { "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba/disks", "rel" : "disks" }, { "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba/storageconnections", "rel" : "storageconnections" }, { "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba/disksnapshots", "rel" : "disksnapshots" }, { "href" : "/ovirt-engine/api/storagedomains/8827b158-6d2e-442d-a7ee-c6fd4718aaba/diskprofiles", "rel" : "diskprofiles" } ] } ] }
5.193. mingw32-qpid-cpp 5.193.1. RHBA-2012:0756 - mingw32-qpid-cpp bug fix update Updated mingw32-qpid-cpp packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The mingw32-qpid-cpp packages provide a message broker daemon that receives, stores, and routes messages by means of runtime libraries for Advanced Message Queuing Protocol (AMQP) client applications developed using the Qpid C++ language. Bug Fixes BZ# 751349 Previously, HTML documentation was required by the mingw32-qpid-cpp package builds, but was not available. Consequently, the following error message was displayed during the build process: As the HTML documentation is not considered essential, this update disables its generation. As a result, the aforementioned error message is not displayed during the build process of the mingw32-qpid-cpp package. BZ# 807345 Previously, mingw32-qpid-cpp had an unnecessary dependency on the mingw32-gnutls package. This update removes the dependency. BZ# 813537 Previously, mingw32-qpid-cpp had an unnecessary dependency on the mingw32-libxslt package. This update removes the dependency. All users of mingw32-qpid-cpp are advised to upgrade to these updated packages, which fix these bugs.

Commands:
CMake Error at docs/api/cmake_install.cmake:31 (FILE): file INSTALL cannot find file "/usr/src/redhat/BUILD/qpid-cpp-0.12/build/docs/api/html" to install.