mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. alarming This chapter describes the commands under the alarming command. 8.1. alarming capabilities list List capabilities of alarming service Usage: Table 8.1. Command arguments Value Summary -h, --help Show this help message and exit Table 8.2. 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 8.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 8.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 8.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.

Commands:
openstack alarming capabilities list [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty]
5.4. Moving swap File Systems from a Single Path Device to a Multipath Device By default, swap devices are set up as logical volumes. This does not require any special procedure for configuring them as multipath devices as long as you set up multipathing on the physical volumes that constitute the logical volume group. If your swap device is not an LVM volume, however, and it is mounted by device name, you may need to edit the /etc/fstab file to switch to the appropriate multipath device name. Determine the WWID number of the swap device by running the /sbin/multipath command with the -v3 option. The output from the command should show the swap device in the paths list. You should look in the command output for a line of the following format, showing the swap device: For example, if your swap file system is set up on sda or one of its partitions, you would see a line in the output such as the following: Set up an alias for the swap device in the /etc/multipath.conf file: Edit the /etc/fstab file and replace the old device path to the root device with the multipath device. For example, if you had the following entry in the /etc/fstab file: You would change the entry to the following:

Commands:
WWID H:B:T:L devname MAJOR : MINOR
===== paths list ===== 1ATA WDC WD800JD-75MSA3 WD-WMAM9F 1:0:0:0 sda 8:0
multipaths { multipath { wwid WWID_of_swap_device alias swapdev } }
/dev/sda2 swap swap defaults 0 0
/dev/mapper/swapdev swap swap defaults 0 0
Chapter 10. Disconnected environment Disconnected environment is a network restricted environment where the Operator Lifecycle Manager (OLM) cannot access the default Operator Hub and image registries, which require internet connectivity. Red Hat supports deployment of OpenShift Data Foundation in disconnected environments where you have installed OpenShift Container Platform in restricted networks. To install OpenShift Data Foundation in a disconnected environment, see Using Operator Lifecycle Manager on restricted networks of the Operators guide in OpenShift Container Platform documentation. Note When you install OpenShift Data Foundation in a restricted network environment, apply a custom Network Time Protocol (NTP) configuration to the nodes, because by default, internet connectivity is assumed in OpenShift Container Platform and chronyd is configured to use the *.rhel.pool.ntp.org servers. For more information, see the Red Hat Knowledgebase solution A newly deployed OCS 4 cluster status shows as "Degraded", Why? and Configuring chrony time service of the Installing guide in OpenShift Container Platform documentation. Red Hat OpenShift Data Foundation version 4.12 introduced the Agent-based Installer for disconnected environment deployment. The Agent-based Installer allows you to use a mirror registry for disconnected installations. For more information, see Preparing to install with Agent-based Installer . Packages to include for OpenShift Data Foundation When you prune the redhat-operator index image, include the following list of packages for the OpenShift Data Foundation deployment: ocs-operator odf-operator mcg-operator odf-csi-addons-operator odr-cluster-operator odr-hub-operator Optional: local-storage-operator Only for local storage deployments. Optional: odf-multicluster-orchestrator Only for Regional Disaster Recovery (Regional-DR) configuration. Important Name the CatalogSource as redhat-operators .

Commands:
7.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: allow_cvs_read_shadow This Boolean allows the cvs daemon to access the /etc/shadow file for user authentication. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 18. Annotating encrypted RBD storage classes Starting with OpenShift Data Foundation 4.14, when the OpenShift console creates a RADOS block device (RBD) storage class with encryption enabled, the annotation is set automatically. However, you need to add the annotation, cdi.kubevirt.io/clone-strategy=copy for any of the encrypted RBD storage classes that were previously created before updating to the OpenShift Data Foundation version 4.14. This enables customer data integration (CDI) to use host-assisted cloning instead of the default smart cloning. The keys used to access an encrypted volume are tied to the namespace where the volume was created. When cloning an encrypted volume to a new namespace, such as, provisioning a new OpenShift Virtualization virtual machine, a new volume must be created and the content of the source volume must then be copied into the new volume. This behavior is triggered automatically if the storage class is properly annotated.

Commands:
6.3. Converting to an ext3 File System The tune2fs program can add a journal to an existing ext2 file system without altering the data already on the partition. If the file system is already mounted while it is being transitioned, the journal is visible as the file .journal in the root directory of the file system. If the file system is not mounted, the journal is hidden and does not appear in the file system at all. Note A default installation of Red Hat Enterprise Linux uses ext3 for all file systems. To convert an ext2 file system to ext3, log in as root and type, where <file_system> is an appropriate LVM2 file system. A valid LVM2 file system could be one of two types of entries: A mapped device - A logical volume in a volume group, for example, /dev/mapper/VolGroup00-LogVol02 . A static device - A traditional storage volume, for example, /dev/ hdb X , where hdb is a storage device name and X is the partition number. Issue the df command to display mounted file systems. For more detailed information on the LVM file system, refer to Chapter 8, LVM Configuration . For the remainder of this section, the sample commands use the following value: After doing this, be certain to change the partition type from ext2 to ext3 in the /etc/fstab file. If you are transitioning your root file system, you must use an initrd image (or RAM disk) to boot. To create this, run the mkinitrd program. For information on using the mkinitrd command, type man mkinitrd . Also, make sure your GRUB configuration loads the initrd . If you fail to make this change, the system still boots, but the file system is mounted as ext2 instead of ext3.

Commands:
/sbin/tune2fs -j <file_system>
/dev/mapper/VolGroup00-LogVol02
Chapter 1. Logging 1.1. Viewing Argo CD logs You can view the Argo CD logs with the logging subsystem for Red Hat OpenShift. The logging subsystem visualizes the logs on a Kibana dashboard. The OpenShift Logging Operator enables logging with Argo CD by default. 1.1.1. Storing and retrieving Argo CD logs You can use the Kibana dashboard to store and retrieve Argo CD logs. Prerequisites The Red Hat OpenShift GitOps Operator is installed on your OpenShift Container Platform cluster. The logging subsystem for Red Hat OpenShift is installed with default configuration on your OpenShift Container Platform cluster. Procedure In the OpenShift Container Platform web console, go to the menu Observability Logging to view the Kibana dashboard. Create an index pattern. To display all the indices, define the index pattern as * , and click step . Select @timestamp for Time Filter field name . Click Create index pattern . In the navigation panel of the Kibana dashboard, click the Discover tab. Create a filter to retrieve logs for Argo CD. The following steps create a filter that retrieves logs for all the pods in the openshift-gitops namespace: Click Add a filter + . Select the kubernetes.namespace_name field. Select the is operator. Select the openshift-gitops value. Click Save . Optional: Add additional filters to narrow the search. For example, to retrieve logs for a particular pod, you can create another filter with kubernetes.pod_name as the field. View the filtered Argo CD logs in the Kibana dashboard. 1.1.2. Additional resources Installing the logging subsystem for Red Hat OpenShift using the web console

Commands:
14.6. Editing a Guest Virtual Machine's configuration file Instead of using the dumpxml option (refer to Section 14.5.23, "Creating a Virtual Machine XML Dump (Configuration File)" ), guest virtual machines can be edited either while they are running or while they are offline. The virsh edit command provides this functionality. For example, to edit the guest virtual machine named rhel6 : This opens a text editor. The default text editor is the USDEDITOR shell parameter (set to vi by default). 14.6.1. Adding Multifunction PCI Devices to KVM Guest Virtual Machines This section will demonstrate how to add multi-function PCI devices to KVM guest virtual machines. Run the virsh edit [guestname] command to edit the XML configuration file for the guest virtual machine. In the address type tag, add a multifunction='on' entry for function='0x0' . This enables the guest virtual machine to use the multifunction PCI devices. For a PCI device with two functions, amend the XML configuration file to include a second device with the same slot number as the first device and a different function number, such as function='0x1' . For Example: lspci output from the KVM guest virtual machine shows:

Commands:
virsh edit rhel6
<disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/var/lib/libvirt/images/rhel62-1.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/ </disk>
<disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/var/lib/libvirt/images/rhel62-1.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/var/lib/libvirt/images/rhel62-2.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </disk>
lspci 00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:05.1 SCSI storage controller: Red Hat, Inc Virtio block device
Chapter 2. Managing Puppet modules 2.1. Installing a Puppet module on Satellite server You can install a pre-built Puppet module from the Puppet Forge. The Puppet Forge is a repository that provides Puppet modules contributed by the community. Puppet modules flagged as supported are officially supported and tested by Puppet Inc. This example shows how to add the ntp module to hosts. Procedure Navigate to forge.puppet.com and search for ntp . One of the first modules is puppetlabs/ntp . Connect to your Satellite Server using SSH and install the Puppet module: Use the -i parameter to specify the path and Puppet environment, for example production . Once the installation is completed, the output looks as follows: An alternative way to install a Puppet module is to copy a folder containing the Puppet module to the module path as mentioned above. Ensure to resolve its dependencies manually. 2.2. Updating a Puppet module You can update an existing Puppet module using the puppet command. Procedure Connect to your Puppet server using SSH and find out where the Puppet modules are located: This returns output as follows: If the module is located in the path as displayed above, the following command updates a module:

Commands:
puppet module install puppetlabs-ntp -i /etc/puppetlabs/code/environments/production/modules
Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules Notice: Created target directory /etc/puppetlabs/code/environments/production/modules Notice: Downloading from https://forgeapi.puppet.com Notice: Installing -- do not interrupt /etc/puppetlabs/code/environments/production/modules |-| puppetlabs-ntp (v8.3.0) |-- puppetlabs-stdlib (v4.25.1) [/etc/puppetlabs/code/environments/production/modules]
puppet config print modulepath
/etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules:/usr/share/puppet/modules
puppet module upgrade module name
7.5. Exporting Templates 7.5.1. Migrating Templates to the Export Domain Note The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disks, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains. Export templates into the export domain to move them to another data domain, either in the same Red Hat Virtualization environment, or another one. This procedure requires access to the Administration Portal. Exporting Individual Templates to the Export Domain Click Compute Templates and select a template. Click Export . Select the Force Override check box to replace any earlier version of the template on the export domain. Click OK to begin exporting the template; this may take up to an hour, depending on the virtual disk size and your storage hardware. Repeat these steps until the export domain contains all the templates to migrate before you start the import process. Click Storage Domains and select the export domain. Click the domain name to see the details view. Click the Template Import tab to view all exported templates in the export domain. 7.5.2. Copying a Template's Virtual Hard Disk If you are moving a virtual machine that was created from a template with the thin provisioning storage allocation option selected, the template's disks must be copied to the same storage domain as that of the virtual disk. This procedure requires access to the Administration Portal. Copying a Virtual Hard Disk Click Storage Disks . Select the template disk(s) to copy. Click Copy . Select the Target data domain from the drop-down list(s). Click OK . A copy of the template's virtual hard disk has been created, either on the same, or a different, storage domain. If you were copying a template disk in preparation for moving a virtual hard disk, you can now move the virtual hard disk.

Commands:
Preface Open Java Development Kit (OpenJDK) is a free and open-source implementation of the Java Platform, Standard Edition (Java SE). Eclipse Temurin is available in four LTS versions: OpenJDK 8u, OpenJDK 11u, OpenJDK 17u, and OpenJDK 21u. Binary files for Eclipse Temurin are available for macOS, Microsoft Windows, and multiple Linux x86 Operating Systems including Red Hat Enterprise Linux and Ubuntu.

Commands:
Chapter 1. Load Balancer Overview The Load Balancer is a set of integrated software components that provide for balancing IP traffic across a set of real servers. It consists of two main technologies to monitor cluster members and cluster services: Keepalived and HAProxy. Keepalived uses Linux virtual server ( LVS ) to perform load balancing and failover tasks on the active and passive routers, while HAProxy performs load balancing and high-availability services to TCP and HTTP applications. 1.1. keepalived The keepalived daemon runs on both the active and passive LVS routers. All routers running keepalived use the Virtual Redundancy Routing Protocol (VRRP). The active router sends VRRP advertisements at periodic intervals; if the backup routers fail to receive these advertisements, a new active router is elected. On the active router, keepalived can also perform load balancing tasks for real servers. Keepalived is the controlling process related to LVS routers. At boot time, the daemon is started by the systemctl command, which reads the configuration file /etc/keepalived/keepalived.conf . On the active router, the keepalived daemon starts the LVS service and monitors the health of the services based on the configured topology. Using VRRP, the active router sends periodic advertisements to the backup routers. On the backup routers, the VRRP instance determines the running status of the active router. If the active router fails to advertise after a user-configurable interval, Keepalived initiates failover. During failover, the virtual servers are cleared. The new active router takes control of the virtual IP address ( VIP ), sends out an ARP message, sets up IPVS table entries (virtual servers), begins health checks, and starts sending VRRP advertisements. Keepalived performs failover on layer 4, or the Transport layer, upon which TCP conducts connection-based data transmissions. When a real server fails to reply to simple timeout TCP connection, keepalived detects that the server has failed and removes it from the server pool.

Commands:
Providing feedback on JBoss EAP documentation To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account. Procedure Click the following link to create a ticket . Enter a brief description of the issue in the Summary . Provide a detailed description of the issue or enhancement in the Description . Include a URL to where the issue occurs in the documentation. Clicking Submit creates and routes the issue to the appropriate documentation team.

Commands:
Chapter 104. KafkaUserTlsClientAuthentication schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserTlsClientAuthentication type from KafkaUserTlsExternalClientAuthentication , KafkaUserScramSha512ClientAuthentication . It must have the value tls for the type KafkaUserTlsClientAuthentication . Property Property type Description type string Must be tls .

Commands:
Chapter 3. Analyzing your projects with the MTR plugin You can analyze your projects with the MTR plugin by creating a run configuration and running an analysis. 3.1. Creating a run configuration You can create multiple run configurations to run against each project you import to IntelliJ IDEA. Procedure In the Projects view, click the project you want to analyze. On the left side of the screen, click the Migration Toolkit for Runtimes tab. If this is your first configuration, the run configuration panel is displayed on the right. If this is not your first configuration, right-click configuration in the list and select New configuration . The run configuration panel is displayed on the right. Complete the following configuration fields: cli : Enter the path to the cli executable. For example: USDHOME/mtr-cli-1.2.7.GA-redhat-00001/bin/mta-cli . Input : Click Add and enter the input file or directory. Target : Select one or more target migration paths. Note The location shown in the Output is set by the plugin. In the list of configurations, right-click the new configuration and select Run Analysis . The Console (MTR) terminal emulator opens, displaying information about the progress of the analysis. When the analysis is completed, you can click either Report or Results below the name of the configuration file you ran. Reports opens the MTR report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide . Results opens a directory displaying hints (issues) per application.

Commands:
2.8. Performance Issues: Check the Red Hat Customer Portal For information on recommendations for deploying and upgrading Red Hat Enterprise Linux clusters using the High Availability Add-On and Red Hat Global File System 2 (GFS2) see the article "Red Hat Enterprise Linux Cluster, High Availability, and GFS Deployment Best Practices" on the Red Hat Customer Portal at https://access.redhat.com/kb/docs/DOC-40821 .

Commands:
Chapter 4. Supported operating systems and architectures .NET 6.0 is available on x86_64 , aarch64 , and s390x on Red Hat Enterprise Linux 8 and later. Table 4.1. Supported deployment environments for .NET 6.0 Platform Architecture RPM Repository Red Hat Enterprise Linux 7 (Until 30 June 2024 ) AMD64 and Intel 64 ( x86_64 ) rh-dotnet60 Red Hat Enterprise Linux 7 Server: rhel-7-server-dotnet-rpms Red Hat Enterprise Linux 7 Workstation: rhel-7-workstation-dotnet-rpm Red Hat Enterprise Linux 7 HPC: rhel-7-hpc-node-dotnet-rpms Red Hat Enterprise Linux 8 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit Arm ( aarch64 ) dotnet-sdk-6.0 Appstream NOTE: The AppStream repositories are enabled by default in Red Hat Enterprise Linux 8. Red Hat Enterprise Atomic Host AMD64 and Intel 64 ( x86_64 ) OpenShift Container Platform 3.11 and later AMD64 and Intel 64 ( x86_64 ) OpenShift Container Platform 4.2 and later IBM Z and LinuxONE ( s390x )

Commands: