mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. Using your subscription Debezium 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 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 . Scroll down to INTEGRATION AND AUTOMATION . Click the name of a component to display a list of the artifacts that are available to download. Click the Download link for the artifact that you want. Revised on 2024-10-09 03:05:58 UTC

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ Python in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To use AMQ Python, you must install Python in your environment. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. Replace <version> with 2 for the main release stream or 2.9 for the long term support release stream. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-8-x86_64-rpms Use the yum command to install the packages. Main release stream USD sudo yum install python3-qpid-proton python-qpid-proton-docs AMQ Clients 2.9 long term support stream USD sudo yum install python-qpid-proton python-qpid-proton-docs For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages . 2.3. Installing on Microsoft Windows Procedure 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 Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.10.0 Python .whl file for your Python version. Python 3.6 python_qpid_proton-0.35.0-cp36-cp36m-win_amd64.whl Python 3.8 python_qpid_proton-0.35.0-cp38-cp38-win_amd64.whl Open a command prompt window and use the pip install command to install the .whl file. Python 3.6 > pip install python_qpid_proton-0.35.0-cp36-cp36m-win_amd64.whl Python 3.8 > pip install python_qpid_proton-0.35.0-cp38-cp38-win_amd64.whl

Commands:
sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-8-x86_64-rpms
sudo yum install python3-qpid-proton python-qpid-proton-docs
sudo yum install python-qpid-proton python-qpid-proton-docs
> pip install python_qpid_proton-0.35.0-cp36-cp36m-win_amd64.whl
> pip install python_qpid_proton-0.35.0-cp38-cp38-win_amd64.whl
18.3.4. Installation using a VNC listener To connect from your temporary Linux installation system to a VNC client running on your workstation in listening mode, use the vncconnect option in your parameter file, in addition to the options vnc and optionally vncpassword . The network and firewalls must allow an IP connection from your temporary Linux installation to your workstation. To have the temporary Linux installation system automatically connect to a VNC client, first start the client in listening mode. On Red Hat Enterprise Linux systems, use the -listen option to run vncviewer as a listener. In a terminal window, enter the command: Refer to Chapter 31, Installing Through VNC for details.

Commands:
vncviewer -listen
E.3.7. /proc/net/ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the /proc/net/ directory: arp - Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system. atm/ directory - The files within this directory contain Asynchronous Transfer Mode (ATM) settings and statistics. This directory is primarily used with ATM networking and ADSL cards. dev - Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more. dev_mcast - Lists Layer2 multicast groups on which each device is listening. igmp - Lists the IP multicast addresses which this system joined. ip_conntrack - Lists tracked network connections for machines that are forwarding IP connections. ip_tables_names - Lists the types of iptables in use. This file is only present if iptables is active on the system and contains one or more of the following values: filter , mangle , or nat . ip_mr_cache - Lists the multicast routing cache. ip_mr_vif - Lists multicast virtual interfaces. netstat - Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more. psched - Lists global packet scheduler parameters. raw - Lists raw device statistics. route - Lists the kernel's routing table. rt_cache - Contains the current routing cache. snmp - List of Simple Network Management Protocol (SNMP) data for various networking protocols in use. sockstat - Provides socket statistics. tcp - Contains detailed TCP socket information. tr_rif - Lists the token ring RIF routing table. udp - Contains detailed UDP socket information. unix - Lists UNIX domain sockets currently in use. wireless - Lists wireless interface data.

Commands:
1.2. Red Hat JBoss Data Virtualization Connector Architecture The process of integrating data from an enterprise information system into Red Hat JBoss Data Virtualization requires one to two components: a translator (mandatory) and a resource adapter (optional), also known as a connector. Most of the time, this will be a Java EE Connector Architecture (JCA) Adapter. A translator is used to: translate Red Hat JBoss Data Virtualization commands into commands understood by the datasource for which the translator is being used, execute those commands, return batches of results from the datasource, translated into the formats that Red Hat JBoss Data Virtualization is expecting. A resource adapter (or connector): handles all communications with individual enterprise information systems, (which can include databases, data feeds, flat files and so forth), can be a JCA Adapter or any other custom connection provider (the JCA specification ensures the writing, packaging and configuration are undertaken in a consistent manner), Note Many software vendors provide JCA Adapters to access different systems. Red Hat recommends using vendor-supplied JCA Adapters when using JMS with JCA. See http://docs.oracle.com/cd/E21764_01/integration.1111/e10231/adptr_jms.htm removes concerns such as connection information, resource pooling, and authentication for translators. With a suitable translator (and optional resource adapter), any datasource or Enterprise Information System can be integrated with Red Hat JBoss Data Virtualization.

Commands:
Red Hat Ansible Automation Platform Service on AWS Ansible on Clouds 2.x Install and configure Red Hat Ansible Automation Platform Service on AWS Red Hat Customer Content Services

Commands:
Title: Ansible Automation Platform Service on AWS PrivateLink Template Describe your problem: Enable AWS PrivateLink connectivity from control plane to customer's network Endpoint Service references are for the Endpoint Service created in the customer's VPC. Endpoint Service name: <enter here> Endpoint Service AWS region: <enter here> Endpoint Service ports or port ranges: <enter here>
Title: Ansible Automation Platform Service on AWS PrivateLink Template Describe your problem: Enable AWS PrivateLink connectivity from customer's network to control plane Customer AWS account ID: <enter here> Endpoint AWS region(s): <enter here> After Red Hat has configured the control plane Endpoint Service allowed principal and supported regions, a response will be added to your support ticket to create your Endpoint and share the Endpoint Service name, which you can find at https://console.redhat.com/ansible/service.
7.54. fence-virt 7.54.1. RHBA-2015:1401 - fence-virt bug fix and enhancement update Updated fence-virt packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The fence-virt packages provide a fencing agent for virtual machines, as well as a host agent that processes fencing requests. Bug Fixes BZ# 1125290 Previously, the fence-virt utility in some case incorrectly returned a zero exit code when it detected an error in processing a request. With this update, the static analysis errors that caused this problem have been fixed, and fence-virt now returns appropriate error codes if it detects an error. BZ# 1078197 Due to an incorrectly configured range of supported TCP and multicast ports, fence-virt did previously not work properly with certain ports. This update fixes the range of supported TCP and multicast ports, which prevents the problem form occurring. Enhancement BZ# 1020992 When the fence-virt and fence-xvm utilities are invoked with the "-o status" parameter, they now print their status in a more comprehensible manner, as either "Status: ON" or "Status: OFF". Users of fence-virt are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
5.3. s390x Architectures Bugzilla #249775 On Red Hat Enterprise Linux 4.8 , N_Port ID Virtualization (NPIV) for System z guests using zFCP is now enabled. NPIV allows a Fibre Channel HBA to log in multiple times to a Fibre Channel fabric using a single physical port (N_Port). With this functionality, a Storage Area Network (SAN) administrator can assign one or more logical unit numbers (LUNs) to a particular System z guest, making that LUN inaccessible to others. For further information, see "Introducing N_Port Identifier Virtualization for IBM System z9, REDP-4125" available at http://www.redbooks.ibm.com/abstracts/redp4125.html

Commands:
Chapter 8. Managing file systems using the Web Console 8.1. Formatting a logical volume using the Web Console Follow these steps to format a logical volume with a file system using the Web Console. Log in to the Web Console. Click the hostname Storage . Click any volume group under Volume Group . The Volume Group Overview page opens. Click the logical volume. On the Filesystem subtab, click Format . Figure 8.1. The logical volume summary Note If this logical volume does not have an existing file system, this tab is labelled Unrecognised Data . Specify whether to Erase existing data completely by overwriting it with zeroes. Specify the file system Type to use. Specify a Name for the file system. Specify whether to use default or customized Mounting behavior. If you selected Custom , specify a Mount Point and check any Mount options you want this file system to use. Click Format . 8.2. Configuring a mount point using the Web Console Log in to the Web Console. Click the hostname Storage . Click any volume group under Volume Group . The Volume Group Overview page opens. Click the logical volume. On the Filesystem subtab, click the value of Mount Point . Figure 8.2. The logical volume summary For this volume the mount point is /gluster_bricks/engine The Filesystem Mounting window opens. Specify a behavior to use for Mounting . If you select Custom , specify a Mount Point and check any Mount Options you want to use. Click Apply . 8.3. Mounting a file system using the Web Console Log in to the Web Console. Click the hostname Storage . Click any volume group under Volume Group . The Volume Group Overview page opens. Click the logical volume. On the Filesystem subtab, click Mount . 8.4. Unmounting a file system using the Web Console Log in to the Web Console. Click the hostname Storage . Click any volume group under Volume Group . The Volume Group Overview page opens. Click the logical volume. On the Filesystem subtab, click Unmount . Figure 8.3. The logical volume summary

Commands:
Chapter 1. Edge clusters Edge clusters are a solution for cost-efficient object storage configurations. Red Hat supports the following minimum configuration of an Red Hat Ceph Storage cluster: A three node cluster with two replicas for SSDs. A four-node cluster with three replicas for HDDs. A four-node cluster with EC pool with 2+2 configuration. With smaller clusters, the utilization goes down because of the amount of usage and the loss of resiliency.

Commands:
Chapter 2. Migrating Apicurio Registry data Migrating data to Apicurio Registry 2.x requires exporting all data from your existing 1.1 deployment and importing it into the new 2.x deployment. If you are using Apicurio Registry as a schema registry for Kafka applications, data migration is critical because each Kafka message carries the global identifier for the schema stored in Apicurio Registry. This identifier must be preserved during registry data migration. Apicurio Registry 2.x provides an API to bulk import/export all data from your registry deployment, which guarantees that all identifiers are kept when importing data from your existing registry. The export API downloads a custom .zip file containing all the information for your artifacts. The import API accepts this .zip and loads all artifacts into the registry in a single batch. Apicurio Registry 1.1 does not provide an import/export API. However, version 2.x provides an export tool compatible with Apicurio Registry 1.1 to export a .zip , which you can import into your 2.x registry. This tool uses common existing APIs to export all content in the registry. However, it is less performant than the 2.x export API, and should only be used when exporting from a 1.1 registry. Prerequisites Running Apicurio Registry instances of the 1.1 server you are exporting from and the 2.x server you are importing into. Download the Apicurio Registry exportV1 tool from the Red Hat Customer Portal. This is a Java application that you can run on the command line. Procedure Export all the data from Apicurio Registry 1.1 using the exportV1 tool. This generates a registry-export.zip file in your current directory: java -jar apicurio-registry-utils-exportV1-2.6.5.Final-redhat-00001.jar http://old-registry.my-company.com/api Import the .zip file into Apicurio Registry 2.x using the import API: curl -X POST "http://new-registry.my-company.com/apis/registry/v2/admin/import" \ -H "Accept: application/json" -H "Content-Type: application/zip" \ --data-binary @registry-export.zip Check that all the artifacts have been imported into the new 2.x registry by running these commands and comparing the count field: curl "http://old-registry.my-company.com/api/search/artifacts" curl "http://new-registry.my-company.com/apis/registry/v2/search/artifacts" Additional resources For more details on the import/export REST API, see the Red Hat build of Apicurio Registry User Guide . For more details on the export tool for migrating from version 1.x to 2.x, see the Apicurio Registry export utility for 1.x versions .

Commands:
java -jar apicurio-registry-utils-exportV1-2.6.5.Final-redhat-00001.jar http://old-registry.my-company.com/api
curl -X POST "http://new-registry.my-company.com/apis/registry/v2/admin/import" -H "Accept: application/json" -H "Content-Type: application/zip" --data-binary @registry-export.zip
curl "http://old-registry.my-company.com/api/search/artifacts"
curl "http://new-registry.my-company.com/apis/registry/v2/search/artifacts"
Appendix B. iSCSI Gateway Variables iSCSI Gateway General Variables seed_monitor Purpose Each iSCSI gateway needs access to the Ceph storage cluster for RADOS and RBD calls. This means the iSCSI gateway must have an appropriate /etc/ceph/ directory defined. The seed_monitor host is used to populate the iSCSI gateway's /etc/ceph/ directory. gateway_keyring Purpose Define a custom keyring name. perform_system_checks Purpose This is a Boolean value that checks for multipath and LVM configuration settings on each iSCSI gateway. It must be set to true for at least the first run to ensure the multipathd daemon and LVM are configured properly. iSCSI Gateway RBD-TARGET-API Variables api_user Purpose The user name for the API. The default is admin . api_password Purpose The password for using the API. The default is admin . api_port Purpose The TCP port number for using the API. The default is 5000 . api_secure Purpose Value can be true or false . The default is false . loop_delay Purpose Controls the sleeping interval in seconds for polling the iSCSI management object. The default value is 1 . trusted_ip_list Purpose A list of IPv4 or IPv6 addresses that have access to the API. By default, only the iSCSI gateway nodes have access.

Commands:
18.7. Additional Resources Refer to the following sources for additional information on packet filtering with iptables . Security Guide ; Red Hat, Inc - Contains a chapter about the role of firewalls within an overall security strategy as well as strategies for constructing firewall rules. System Administrators Guide ; Red Hat, Inc - Contains a chapter about configuring firewalls using Security Level Configuration Tool . 18.7.1. Installed Documentation man iptables - Contains a description of iptables as well as a comprehensive list of targets, options, and match extensions.

Commands:
Chapter 2. Overview of the all-in-one Red Hat OpenStack Platform environment This section contains information about installing, configuring, and deploying a simple, single-node Red Hat OpenStack Platform environment. In this scenario, there is no pre-existing undercloud dependency. Instead, the installer runs an inline heat-all instance to bootstrap the deployment process and convert the selected heat templates into Ansible playbooks that you can execute on a local machine. Use the all-in-one installation for basic testing and development. The all-in-one installation is a good starting point and test environment for Red Hat OpenStack Platform, but if you want to perform complex operations, you must deploy a production-level scaled cloud. Workflow To install, configure, and deploy a simple, single-node Red Hat OpenStack Platform environment, complete the tasks in the following basic workflow: Prepare your environment. Install packages for the all-in-one environment. Configure the all-in-one environment. Deploy the all-in-one environment. Benefits of the all-in-one installation Composable services. Pre-defined roles. Condensed single-node environment. Playbooks that you can use to run the small-footprint installer in a container and generate Ansible playbooks. Configuration If you want to experiment with configuring roles and services, see Chapter 8, Working with custom roles and services and Section 7.1, "Core heat templates" . Composable roles You can create custom composable roles and deploy specific services for each role. Ansible This installation applies Ansible playbooks automatically with the deployment command. You can also direct the deployment command to output Ansible playbooks that you can use on other environments. For example, you can complete testing in the all-in-one installation, and then apply the verified Ansible playbook to other environments.

Commands:
Chapter 11. Finding and cleaning stale subvolumes (Technology Preview) Sometimes stale subvolumes don't have a respective k8s reference attached. These subvolumes are of no use and can be deleted. You can find and delete stale subvolumes using the ODF CLI tool. Important Deleting stale subvolumes using the ODF CLI tool is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, see Technology Preview Features Support Scope . Prerequisites Download the OpenShift Data Foundation command line interface (CLI) tool. With the Data Foundation CLI tool, you can effectively manage and troubleshoot your Data Foundation environment from a terminal. You can find a compatible version and download the CLI tool from the customer portal . Procedure Find the stale subvolumes by using the --stale flag with the subvolumes command: Example output: Delete the stale subvolumes: Replace <subvolumes> with a comma separated list of subvolumes from the output of the first command. The subvolumes must be of the same filesystem and subvolumegroup. Replace <filesystem> and <subvolumegroup> with the filesystem and subvolumegroup from the output of the first command. For example: Example output:

Commands:
odf subvolume ls --stale
Filesystem Subvolume Subvolumegroup State ocs-storagecluster-cephfilesystem csi-vol-427774b4-340b-11ed-8d66-0242ac110004 csi stale ocs-storagecluster-cephfilesystem csi-vol-427774b4-340b-11ed-8d66-0242ac110005 csi stale
odf subvolume delete <subvolumes> <filesystem> <subvolumegroup>
odf subvolume delete csi-vol-427774b4-340b-11ed-8d66-0242ac110004,csi-vol-427774b4-340b-11ed-8d66-0242ac110005 ocs-storagecluster csi
Info: subvolume csi-vol-427774b4-340b-11ed-8d66-0242ac110004 deleted Info: subvolume csi-vol-427774b4-340b-11ed-8d66-0242ac110004 deleted
8.11. Accessing Snapshots Snapshot of a Red Hat Gluster Storage volume can be accessed only via FUSE mount. Use the following command to mount the snapshot. parent-VOLNAME - Volume name for which we have created the snapshot. For example, Since the Red Hat Gluster Storage snapshot volume is read-only, no write operations are allowed on this mount. After mounting the snapshot the entire snapshot content can then be accessed in a read-only mode. Note NFS and CIFS mount of snapshot volume is not supported. Snapshots can also be accessed via User Serviceable Snapshots. For more information see, Section 8.13, "User Serviceable Snapshots" Warning External snapshots, such as snapshots of a virtual machine/instance, where Red Hat Gluster Storage Server is installed as a guest OS or FC/iSCSI SAN snapshots are not supported.

Commands:
mount -t glusterfs <hostname>:/snaps/<snapname>/parent-VOLNAME / mount_point
mount -t glusterfs myhostname:/snaps/snap1/test_vol /mnt