mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix D. Understanding LVM LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as physical volumes . One or more physical volumes are combined to form a volume group . Each volume group's total storage is then divided into one or more logical volumes . The logical volumes function much like standard partitions. They have a file system type, such as ext4 , and a mount point. Note On most architectures, the boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your /boot partition. However, on System z, the zipl boot loader supports /boot on LVM logical volumes with linear mapping. To understand LVM better, imagine the physical volume as a pile of blocks . A block is simply a storage unit used to store data. Several piles of blocks can be combined to make a much larger pile, just as physical volumes are combined to make a volume group. The resulting pile can be subdivided into several smaller piles of arbitrary size, just as a volume group is allocated to several logical volumes. An administrator may grow or shrink logical volumes without destroying data, unlike standard disk partitions. If the physical volumes in a volume group are on separate drives or RAID arrays then administrators may also spread a logical volume across the storage devices. You may lose data if you shrink a logical volume to a smaller capacity than the data on the volume requires. To ensure maximum flexibility, create logical volumes to meet your current needs, and leave excess storage capacity unallocated. You may safely grow logical volumes to use unallocated space, as your needs dictate. Note By default, the installation process creates / and swap partitions within LVM volumes, with a separate /boot partition.

Commands:
Chapter 3. Assigning automation hub administrator permissions Hub administrative users will need to be assigned the role of hubadmin in order to manage user permissions and groups. You can assign the role of hubadmin to a user through the Ansible Automation Platform Central Authentication client. Prerequisites A user storage provider (e.g., LDAP) has been added to your central authentication Procedure Navigate to the ansible-automation-platform realm on your SSO client. From the navigation bar, select Manage Users . Select a user from the list by clicking their ID. Click the Role Mappings tab. Using the dropdown menu under Client Roles , select automation-hub . Click hubadmin from the Available Roles field, then click Add selected > . The user is now a hubadmin . Repeat steps 3-6 to assign any additional users the hubadmin role.

Commands:
D.13. Search Results View Below is an example set of search results. The view contains rows representing matches for your search parameters. You can double-click a entry and the object will be opened and selected in an editor and/or the Model Explorer if applicable. Figure D.23. Search Results View The toolbar actions for the Search Results view are: Show Match - Navigates down one row in the view. Show Match - Navigates up one row in the view. Remove Selected Matches - Removes selected results from the view. Remove All Matches - Clears the view. Expand All - Expand all nodes in the search. Collapse All - Collapse all nodes in the search. Search - Launches the Teiid Designer Dialog. Search Results - Select search results from history. You can also perform some of these actions via the right-click menu: Figure D.24. Search Results Context Menu

Commands:
Chapter 10. Kafka clients The kafka-clients JAR file contains the Kafka Producer and Consumer APIs together with the Kafka AdminClient API. The Producer API allows applications to send data to a Kafka broker. The Consumer API allows applications to consume data from a Kafka broker. The AdminClient API provides functionality for managing Kafka clusters, including topics, brokers, and other components. 10.1. Adding Kafka clients as a dependency to your Maven project This procedure shows you how to add the AMQ Streams Java clients as a dependency to your Maven project. Prerequisites A Maven project with an existing pom.xml . Procedure Add the Red Hat Maven repository to the <repositories> section of your pom.xml file. Add the clients to the <dependencies> section of your pom.xml file. Build your Maven project.

Commands:
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <repositories> <repository> <id>redhat-maven</id> <url>https://maven.repository.redhat.com/ga/</url> </repository> </repositories> <!-- ... --> </project>
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <dependencies> <dependency> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</artifactId> <version>2.8.0.redhat-00002</version> </dependency> </dependencies> <!-- ... --> </project>
Chapter 1. Features AMQ Streams 2.1 introduces the features described in this section. AMQ Streams version 2.1 is based on Strimzi 0.28.x. Note To view all the enhancements and bugs that are resolved in this release, see the AMQ Streams Jira project . 1.1. Kafka 3.1.0 support AMQ Streams now supports Apache Kafka version 3.1.0. AMQ Streams uses Kafka 3.1.0. Only Kafka distributions built by Red Hat are supported. For upgrade instructions, see AMQ Streams and Kafka upgrades . Refer to the Kafka 3.0.0 and Kafka 3.1.0 Release Notes for additional information. Note Kafka 3.0.x is supported only for the purpose of upgrading to AMQ Streams 2.1. For more information on supported versions, see the AMQ Streams Component Details . Kafka 3.1.0 requires ZooKeeper version 3.6.3, which is the same version as Kafka 3.0.0. Therefore, you will not need to upgrade ZooKeeper when upgrading from AMQ Streams 2.0 to AMQ Streams 2.1. Warning Kafka 3.1.0 provides access to self-managed mode , where Kafka runs without ZooKeeper by utilizing the Raft protocol. Note that self-managed mode is not supported in AMQ Streams . 1.2. Support for IBM Power architecture AMQ Streams 2.1 is enabled to run on IBM Power ppc64le architecture. Support for IBM Power applies to AMQ Streams running with Kafka 3.0.0 and later, and Open JDK 11, on Red Hat Enterprise Linux 8. The Kafka versions shipped with AMQ Streams 1.8 and earlier versions do not contain the ppc64le binaries. 1.2.1. Requirements for IBM Power Red Hat Enterprise Linux 8 Open JDK 11 Kafka 3.0.0 and later 1.2.2. Unsupported on IBM Power Red Hat Enterprise Linux 7 Kafka 2.8.0 and earlier Open JDK 8, Oracle JDK 8 & 11, IBM JDK 8

Commands:
4.8. Devices The Emulex lpfc driver should not be unloaded. If the driver is unloaded, a system crash might occur. Red Hat Enterprise Linux 6 only has support for the first revision of the UPEK Touchstrip fingerprint reader (USB ID 147e:2016). Attempting to use a second revision device may cause the fingerprint reader daemon to crash. The command will return the version of the device being used in an individual machine. The Emulex Fibre Channel/Fibre Channel-over-Ethernet (FCoE) driver in Red Hat Enterprise Linux 6 does not support DH-CHAP authentication. DH-CHAP authentication provides secure access between hosts and mass storage in Fibre-Channel and FCoE SANs in compliance with the FC-SP specification. Note, however that the Emulex driver ( lpfc ) does support DH-CHAP authentication on Red Hat Enterprise Linux 5, from version 5.4. Future Red Hat Enterprise Linux 6 releases may include DH-CHAP authentication. The recommended minimum HBA firmware revision for use with the mpt2sas driver is "Phase 5 firmware" (i.e. with version number in the form 05.xx.xx.xx .) Note that following this recommendation is especially important on complex SAS configurations involving multiple SAS expanders.

Commands:
lsusb -v -d 147e:2016 | grep bcdDevice
B.10.3. RHBA-2012:0534 - corosync bug fix update Updated corosync packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The corosync packages provide the Corosync Cluster Engine and the C language APIs for Red Hat Enterprise Linux cluster software. Bug Fix BZ# 810915 Previously, the underlying library of corosync did not delete temporary buffers used for Inter-Process Communication (IPC) that are stored in the /dev/shm shared memory file system. Therefore, if the user without proper privileges attempted to establish an IPC connection, the attempt failed with an error message as expected but memory allocated for temporary buffers was not released. This could eventually result in /dev/shm being fully used and Denial of Service. This update modifies the coroipcc library to let applications delete temporary buffers if the buffers were not deleted by the corosync server. The /dev/shm file system is no longer cluttered with needless data in this scenario and IPC connections can be established as expected. All users of corosync are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.211. scrub 8.211.1. RHBA-2014:1493 - scrub bug fix and enhancement update Updated scrub packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. Scrub writes patterns on files or disk devices to make retrieving the data more difficult. It is a program for erasing disks. Bug Fix BZ# 903890 When the "scrub -X" command was executed, it rewrote free space on given disk partition but failed to remove files created during this process. As a consequence, the respective file system remained full after this process. With this update, the newly created files are removed, and the file system regains the free space. In addition, this update adds the following Enhancement BZ# 907173 With this update, the new "-E" option has been added to scrub, which has the ability to scrub only used blocks of a sparse file. This option is especially useful in combination with large sparse files, as it skips the holes in the sparse file. Nevertheless, use this option with caution, as the result may not be compliant with cited standards and information about the actual on-disk data allocation may leak since only the allocated parts will be scrubbed. Users of scrub are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Part III. Activating simple content access Beginning on October 25, 2024, and continuing for several weeks in the month of November, the majority of the remaining Red Hat accounts that use hosted Red Hat Subscription Management but have not migrated to simple content access will be migrated to the simple content access workflow. Therefore, manual activation of simple content access for these accounts is no longer necessary. For Red Hat Satellite, simple content access has been the default workflow for new Red Hat accounts since the release of Satellite 6.9. Also with that version, simple content access has been the default for new Satellite manifests and organizations in existing accounts, although this default could be changed. For Red Hat Satellite 6.16, only the simple content access workflow is available. Regardless of the subscription management tools that you use, when simple content access is activated you must do some post-migration checks and steps to ensure that you understand the changes in the workflow and can adapt any customized processes that you have in place for your Red Hat account and organization. Do these steps To enable simple content access with Red Hat Subscription Management, see the following information: Enabling simple content access with Red Hat Subscription Management To enable simple content access with Satellite, see the following information: Enabling simple content access with Satellite

Commands:
Chapter 2. Component overview Red Hat AMQ consists of AMQ Broker, AMQ Interconnect, and AMQ Clients. They work together to enable network communication in distributed applications. AMQ Broker AMQ Interconnect AMQ Clients 2.1. AMQ Broker AMQ Broker is a full-featured, message-oriented middleware broker. It offers advanced addressing and queueing, fast message persistence, and high availability. AMQ Broker supports multiple protocols and operating environments, enabling you to use your existing assets. AMQ Broker supports integration with Red Hat JBoss Enterprise Application Platform. For more information, see Getting Started with AMQ Broker . 2.2. AMQ Interconnect AMQ Interconnect provides flexible routing of messages between AMQP-enabled endpoints, including clients, brokers, and standalone services. With a single connection into a network of AMQ Interconnect routers, a client can exchange messages with any other endpoint connected to the network. AMQ Interconnect does not use master-slave clusters for high availability. It is typically deployed in topologies of multiple routers with redundant network paths, which it uses to provide reliable connectivity. AMQ Interconnect can distribute messaging workloads across the network and achieve new levels of scale with very low latency. For more information, see Using the AMQ Interconnect router and Release Notes for AMQ Interconnect 2.0 . 2.3. AMQ Clients AMQ Clients is a suite of AMQP 1.0 and JMS clients, adapters, and libraries. It includes JMS 2.0 support and new, event-driven APIs to enable integration into existing applications. For more information, see AMQ Clients Overview . AMQP clients AMQ C++ AMQ JavaScript AMQ JMS (Java) AMQ .NET AMQ Python AMQ Ruby JMS clients AMQ JMS (AMQP 1.0) AMQ Core Protocol JMS AMQ OpenWire JMS Adapters and libraries AMQ JMS Pool AMQ Spring Boot Starter 2.4. Component compatibility The following table lists the supported languages, platforms, and protocols of AMQ components. Note that any components supporting the same protocol can interoperate, even if their languages and platforms differ. For instance, AMQ Python can communicate with AMQ JMS. Table 2.1. AMQ component compatibility Component Languages Platforms Protocols AMQ Broker - JVM AMQP 1.0, MQTT, OpenWire, STOMP, Core Protocol AMQ Interconnect - Linux AMQP 1.0 AMQ C++ C++ Linux, Windows AMQP 1.0 AMQ JavaScript JavaScript Node.js, browsers AMQP 1.0 AMQ JMS Java JVM AMQP 1.0 AMQ .NET C# .NET AMQP 1.0 AMQ Python Python Linux AMQP 1.0 AMQ Ruby Ruby Linux AMQP 1.0 AMQ Spring Boot Starter Java JVM AMQP 1.0 AMQ Core Protocol JMS Java JVM Core Protocol AMQ OpenWire JMS Java JVM OpenWire AMQ JMS Pool Java JVM - For more information, see Red Hat AMQ 7 Supported Configurations .

Commands:
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Streams entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2021-08-18 09:24:23 UTC

Commands:
Chapter 7. Assigning a Puppet Class to a Host Group Use a host group to assign the ntp Puppet class to multiple hosts at once. Every host you deploy based on this host group has this Puppet class installed. Procedure In the Satellite web UI, navigate to Configure > Host Groups to create a host group or edit an existing one. On the Host Group tab, set the following parameters: The Lifecycle Environment describes the stage in which certain versions of content are available to hosts. The Content View is comprised of products and allows for version control of content repositories. The Environment allows you to supply a group of hosts with their own dedicated configuration. Navigate to the Puppet ENC tab. Add the Puppet class to the Included Classes or to the Included Config Groups if a Puppet config group is configured. Click Submit to save the changes.

Commands:
Chapter 30. Setting Up an Installation Server The following steps must be performed to prepare for a network installation: Configure the network (NFS, FTP, HTTP, HTTPS) server to export the installation tree. Configure the files on the tftp server necessary for network booting. Configure which hosts are allowed to boot from the network configuration. Start the tftp service. Configure DHCP. Boot the client, and start the installation. 30.1. Setting Up the Network Server First, configure an NFS, FTP, HTTP, or HTTPS server to export the entire installation tree for the version and variant of Red Hat Enterprise Linux to be installed. Refer to Section 4.1, "Preparing for a Network Installation" for detailed instructions.

Commands:
2.7. Packaging the Adapter When development is complete, the resource adapter files are packaged into a deployable artifact called a Resource Adapter Archive or RAR file. Note The file format is defined by the JCA specification and must not be confused with the RAR file compression format. The method of creating a RAR artifact will depend on your build system: JBoss Developer Studio If you create a Java Connector project in JBoss Developer Studio, it will include a build target that produces a RAR file. Apache Ant When using Apache Ant, you can use the standard rar build task. Apache Maven When using Apache Maven, set the value of the <packaging> element to rar . Since Red Hat JBoss Data Virtualization uses Maven, you can refer to any of the Connector projects; for example, pom.xml shown below. <project> <modelVersion>4.0.0</modelVersion> <artifactId>connector-{name}</artifactId> <groupId>org.company.project</groupId> <name>Name Connector</name> <packaging>rar</packaging> <description>This connector is a sample</description> <dependencies> <dependency> <groupId>org.jboss.teiid</groupId> <artifactId>teiid-api</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.jboss.teiid</groupId> <artifactId>teiid-common-core</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>javax.resource</groupId> <artifactId>connector-api</artifactId> <scope>provided</scope> </dependency> </dependencies> The RAR file under its associated META-INF directory must contain the ra.xml file. If you are using Apache Maven, see http://maven.apache.org/plugins/maven-rar-plugin/ . In the root of the RAR file, you can embed the JAR file containing your connector code and any dependent library JAR files.

Commands:
<project> <modelVersion>4.0.0</modelVersion> <artifactId>connector-{name}</artifactId> <groupId>org.company.project</groupId> <name>Name Connector</name> <packaging>rar</packaging> <description>This connector is a sample</description> <dependencies> <dependency> <groupId>org.jboss.teiid</groupId> <artifactId>teiid-api</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.jboss.teiid</groupId> <artifactId>teiid-common-core</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>javax.resource</groupId> <artifactId>connector-api</artifactId> <scope>provided</scope> </dependency> </dependencies>
function::json_add_array_string_metric Name function::json_add_array_string_metric - Add a string metric to an array Synopsis Arguments array_name The name of the array the string metric should be added to. metric_name The name of the string metric. metric_description Metric description. An empty string can be used. Description This function adds a string metric to an array, setting up everything needed.

Commands:
json_add_array_string_metric:long(array_name:string,metric_name:string,metric_description:string)
Chapter 2. Patching Existing Server Instances Micro releases for the JBoss Data Grid server are distributed as a patch. This is for your convenience, as the new version will not completely replace the installation. The base version to be patched is the x.y.0 release, and the patches x.y.# (micro release or cumulative patch) may be applied to that instance. The patch can be rolled back (including the configuration) if there is any issue during the patching process, and any subsequent patches may be applied in the same way. This process is similar to the already known procedure in JBoss Enterprise Application Platform (EAP). Note It is strongly recommended to back up your existing installation, including all configuration files, before applying the patch. Procedure 2.1. Applying the JBoss Data Grid 6.6.1 Patch Download the patch from the Red Hat Customer Portal at https://access.redhat.com/downloads/ Connect to the running instance to be patched using the JBoss CLI: Ensure that there are no active connections to the server, and then apply the patch: Restart the server: All other distributions, such as the EAP modules, client's, and standalone library mode are provided as a full release. Due to this there is no possibility to patch existing archives for these distributions. Report a bug

Commands:
USDJDG_HOME/bin/cli.sh --connect=127.0.0.1:9999
patch apply /path/to/jboss-datagrid-6.6.1.CR1-server-patch.zip
shutdown --restart=true
Chapter 3. IdM API and IdM CLI commands comparison You can use the IdM API commands in the Python interactive console. The IdM API commands are different from the ipa tool commands. IdM CLI and IdM API commands difference Command naming structure The ipa CLI commands use the hyphen, as in user-add , but IdM API commands use the underscore instead, as in user_add . Parameter naming The parameters are different for IdM CLI commands and IdM API commands. For example, the IdM CLI user-add command has a parameter first but the IdM API user_add command has a parameter givenname . Date format The following date formats are available for IdM CLI: %Y%m%d%H%M%SZ %Y-%m-%dT%H:%M:%SZ %Y-%m-%dT%H:%MZ %Y-%m-%dZ %Y-%m-%d %H:%M:%SZ %Y-%m-%d %H:%MZ Additionally, the IdM API can use the Python built-in class datetime . Useful CLI tools The console starts an interactive Python console, which you can use to run IdM API commands. The help command shows description of the topics and the commands and includes various examples. The show-mapping command shows the mapping between CLI parameter names and LDAP attributes.

Commands: