mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Deprecated features The features deprecated in this release, and that were supported in releases of AMQ Streams, are outlined below. 6.1. RHEL 7 deprecated in AMQ Streams 2.5.x (LTS) Support for RHEL 7 is deprecated in AMQ Streams 2.5.x. AMQ Streams 2.5.x (LTS) is the last LTS version to support RHEL 7. 6.2. Java 8 support removed in AMQ Streams 2.4.0 Support for Java 8 was deprecated in Kafka 3.0.0 and AMQ Streams 2.0. Support for Java 8 was removed in AMQ Streams 2.4.0. This applies to all AMQ Streams components, including clients. AMQ Streams supports Java 11 and Java 17. Use Java 11 or 17 when developing new applications. Plan to migrate any applications that currently use Java 8 to Java 11 or 17. If you want to continue using Java 8 for the time being, AMQ Streams 2.2 provides Long Term Support (LTS). For information on the LTS terms and dates, see the AMQ Streams LTS Support Policy . 6.3. OpenTracing Support for OpenTracing is deprecated. The Jaeger clients are now retired and the OpenTracing project archived. As such, we cannot guarantee their support for future Kafka versions. We are introducing a new tracing implementation based on the OpenTelemetry project. 6.4. Kafka MirrorMaker 2 identity replication policy Identity replication policy is a feature used with MirrorMaker 2 to override the automatic renaming of remote topics. Instead of prepending the name with the source cluster's name, the topic retains its original name. This setting is particularly useful for active/passive backups and data migration scenarios. To implement an identity replication policy, you must specify a replication policy class ( replication.policy.class ) in the MirrorMaker 2 configuration. Previously, you could specify the io.strimzi.kafka.connect.mirror.IdentityReplicationPolicy class included with the AMQ Streams mirror-maker-2-extensions component. However, this component is now deprecated and will be removed in the future. Therefore, it is recommended to update your implementation to use Kafka's own replication policy class ( org.apache.kafka.connect.mirror.IdentityReplicationPolicy ). See Using AMQ Streams with MirrorMaker 2 . 6.5. Kafka MirrorMaker 1 Kafka MirrorMaker replicates data between two or more active Kafka clusters, within or across data centers. Kafka MirrorMaker 1 was deprecated in Kafka 3.0.0 and will be removed in Kafka 4.0.0. MirrorMaker 2 will be the only version available. MirrorMaker 2 is based on the Kafka Connect framework, connectors managing the transfer of data between clusters. As a result, MirrorMaker 1 has also been deprecated in AMQ Streams as well. If you are using MirrorMaker 1 (referred to as just MirrorMaker in the AMQ Streams documentation), use MirrorMaker 2 with the IdentityReplicationPolicy class. MirrorMaker 2 renames topics replicated to a target cluster. IdentityReplicationPolicy configuration overrides the automatic renaming. Use it to produce the same active/passive unidirectional replication as MirrorMaker 1. See Using AMQ Streams with MirrorMaker 2 .

Commands:
Preface Standalone Manager installation is manual and customizable. You must install a Red Hat Enterprise Linux machine, then run the configuration script ( engine-setup ) and provide information about how you want to configure the Red Hat Virtualization Manager. Add hosts and storage after the Manager is running. At least two hosts are required for virtual machine high availability. In a local database environment, the Manager database and Data Warehouse database can be created automatically by the Manager configuration script. Alternatively, you can create these databases manually on the Manager machine before running engine-setup . See the Planning and Prerequisites Guide for information on environment options and recommended configuration. Red Hat Virtualization Key Components Component Name Description Red Hat Virtualization Manager A service that provides a graphical user interface and a REST API to manage the resources in the environment. The Manager is installed on a physical or virtual machine running Red Hat Enterprise Linux. Hosts Red Hat Enterprise Linux hosts (RHEL hosts) and Red Hat Virtualization Hosts (image-based hypervisors) are the two supported types of host. Hosts use Kernel-based Virtual Machine (KVM) technology and provide resources used to run virtual machines. Shared Storage A storage service is used to store the data associated with virtual machines. Data Warehouse A service that collects configuration information and statistical data from the Manager. Standalone Manager Architecture The Red Hat Virtualization Manager runs on a physical server, or a virtual machine hosted in a separate virtualization environment. A standalone Manager is easier to deploy and manage, but requires an additional physical server. The Manager is only highly available when managed externally with a product such as Red Hat's High Availability Add-On. The minimum setup for a standalone Manager environment includes: One Red Hat Virtualization Manager machine. The Manager is typically deployed on a physical server. However, it can also be deployed on a virtual machine, as long as that virtual machine is hosted in a separate environment. The Manager must run on Red Hat Enterprise Linux 8. A minimum of two hosts for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1. Standalone Manager Red Hat Virtualization Architecture

Commands:
Chapter 20. Virtualization virt-v2v converts virtual machine CPU topology With this update, the virt-v2v utility preserves the CPU topology of the converted virtual machines (VMs). This ensures that the VM CPU works the same way after the conversion as it did before the conversion, which avoids potential runtime problems. (BZ# 1541908 ) virt-v2v can import virtual machines directly to RHV The virt-v2v utility is now able to output a converted virtual machine (VM) directly to a Red Hat Virtualization (RHV) client. As a result, importing VMs converted by virt-v2v using the Red Hat Virtualization Manager (RHVM) is now easier, faster, and more reliable. Note that this feature requires RHV version 4.2 or later to work properly. (BZ# 1557273 ) The i6300esb watchdog is now supported by libvirt With this update, the libvirt API supports the i6300esb watchdog device. As a result, KVM virtual machines can use this device to automatically trigger a specified action, such as saving a core dump of the guest if the guest OS becomes unresponsive or terminates unexpectedly. (BZ# 1447169 ) Paravirtualized clock added to Red Hat Enterprise Linux VMs With this update, the paravirtualized sched_clock() function has been integrated in the Red Hat Enterprise Linux kernel. This improves the performance of Red Hat Enterprise Linux virtual machines (VMs) running on VMWare hypervisors. Note that the function is enabled by default. To disable it, add the no-vmw-sched-clock option to the kernel command line. (BZ# 1507027 ) VNC console is supported on IBM Z This update enables the virtio-gpu kernel configuration in guests running on the IBM Z architecture. As a result, KVM guests on an IBM Z host are now able to use the VNC console to display their graphical output. (BZ#1570090) QEMU Guest Agent diagnostics enhanced To maintain qemu-guest-agents compatibility with the latest version of VDSM, a number of features have been backported from the most recent upstream version. These include the addition of qemu-get-host-name , qemu-get-users , qemu-get-osinfo , and qemu-get-timezone commands, which improve the diagnostic capabilities of QEMU Guest Agent. (BZ# 1569013 )

Commands:
12.3. XML Document Modeling 12.3.1. Create XML View Documents from Schema You can create XML View Documents by selecting an element in the Model Explorer and selecting the Modeling > Create XML View Documents action. Note You can create XML View Documents also by right-clicking on the XML model and select Child > XML document . Then XML Document builder page will be displayed which is described at the end of the section 12.3.1 (figure 12.23). Figure 12.25. Create XML View Documents Action The action will query you for a target XML Document model. You can either select an existing XML Document model from your workspace, or enter a unique model name and the wizard will create a new model for you. Figure 12.26. Select or Create XML View Model Dialog After selecting or creating your new XML Document model, the XML Document builder page will be displayed. This page is explained in greater detail in the document view from schema section. Figure 12.27. Build XML Documents From XML Schema Dialog

Commands:
4.10. RHEA-2012:1576 - new packages: kmod-pch_gbe New kmod-pch_gbe packages are now available for Red Hat Enterprise Linux 6. The kmod-pch_gbe packages provide kernel modules for controlling Ethernet adapter in Intel EG20T Platform Controller Hub and OKI Semiconductor ML7223 Input/Output Hub. The kmod-pch_gbe packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.3: * Intel EG20T PCH / OKI Semiconductor ML7223 IOH Gigabit Ethernet This enhancement update adds the kmod-pch_gbe packages to Red Hat Enterprise Linux 6 as part of the Red Hat Enterprise Linux Driver Update Program (DUP). (BZ# 878375 ) Only users requiring temporary driver support for the specific hardware noted above should install these packages. Unless a system includes the exact hardware explicitly supported by kmod-pch_gbe packages, these packages must not be installed.

Commands:
15.8. GVFS Tools and xdg-utils in GNOME GVFS ships with several commands that may come useful for scripting or testing. A set of POSIX commands counterparts is offered: gvfs-cat gvfs-less gvfs-mkdir gvfs-mount gvfs-rename gvfs-set-attribute gvfs-copy gvfs-ls gvfs-move gvfs-rm gvfs-trash gvfs-info gvfs-save gvfs-tree Some more additional commands are provided for more control of GVFS specifics: gvfs-monitor-dir gvfs-monitor-file gvfs-mime gvfs-open All these commands are native GIO clients, there is no need for the fallback FUSE daemon to be running. Their purpose is not to be drop-in replacements for POSIX commands, in fact, a very little range of switches is supported. In their basic form, an URI string (instead of a local path) is taken as an argument. This all allows GNOME to be well-supported within xdg-tools (a freedesktop.org interoperability project). For example, the commonly used xdg-open actually calls gvfs-open when a running GNOME session is detected, reading file type associations from the correct location. The following are a few examples of the GVFS commands usage: To lists all files in /tmp on a local file system, execute: The command below lists contents of a text file from a remote machine: To copy the referenced text file to a local /tmp directory, run: Note For user convenience, bash completion is provided as a part of the package.

Commands:
gvfs-ls file:///tmp
gvfs-cat ssh://joe@ftp.myserver.net/home/joe/todo.txt
gvfs-copy ssh://joe@ftp.myserver.net/home/joe/todo.txt /tmp/
Chapter 1. Open Virtual Network (OVN) Open Virtual Network (OVN) is an Open vSwitch-based software-defined networking (SDN) solution for supplying network services to instances. OVN provides platform-agnostic support for the full OpenStack Networking API. OVN allows you to programmatically connect groups of guest instances into private L2 and L3 networks. OVN uses a standard approach to virtual networking that is capable of extending to other Red Hat platforms and solutions. This release of the Red Hat OpenStack Platform (RHOSP) does not provide a supported migration from the ML2/OVS mechanism driver to the ML2/OVN mechanism driver. This RHOSP release does not support the OpenStack community migration strategy. Migration support is planned for a future RHOSP release. To track the progress of migration support, see https://bugzilla.redhat.com/show_bug.cgi?id=1862888 . Note The minimum Open vSwitch (OVS) version required is OVS 2.9. OVN uses Python 3.6 packages by default. This section describes the steps required to deploy OVN using director. Note OVN is supported only in an HA environment. We recommend that you deploy OVN with distributed virtual routing (DVR). 1.1. Quick Steps: Deploying Containerized OVN on the overcloud If you are already familiar with OVN, you can use this quick step to deploy OVN with DVR in an HA configuration on the overcloud: 1.2. OVN Architecture The OVN architecture replaces the OVS ML2 plugin with the OVN Modular Layer 2 (ML2) plugin to support the Networking API. OVN provides robust networking services for the Red Hat OpenStack platform. The OVN architecture consists of the following components and services: OVN ML2 plugin Translates the OpenStack-specific networking configuration into the platform-agnostic OVN logical networking configuration. This plugin typically runs on the Controller node. OVN Northbound (NB) database ( ovn-nb ) Stores the logical OVN networking configuration from the OVN ML2 plugin. This database typically runs on the Controller node and listens on TCP port 6641 . OVN Northbound service ( ovn-northd ) Converts the logical networking configuration from the OVN NB database to the logical data path flows and populates these on the OVN Southbound database. This service typically runs on the Controller node. OVN Southbound (SB) database ( ovn-sb ) Stores the converted logical data path flows. This database typically runs on the Controller node and listens on TCP port 6642 . OVN controller ( ovn-controller ) Connects to the OVN SB database and acts as the open vSwitch controller to control and monitor network traffic. Runs on all Compute and gateway nodes where OS::Tripleo::Services::OVNController is defined. OVN metadata agent ( ovn-metadata-agent ) Spawns the haproxy instances for managing the OVS interfaces, network namespaces and HAProxy processes used to proxy metadata API requests. Runs on all Compute and gateway nodes where OS::TripleO::Services::OVNMetadataAgent is defined.

Commands:
openstack overcloud deploy --templates /usr/share/openstack-tripleo-heat-templates -e /usr/share/openstack-tripleo-heat-templates/environments/services/ neutron-ovn-dvr-ha.yaml .
34.2.3. Unsupported Backup Methods With unsupported backup methods, there are two options: The rescue system prompts the user to manually restore the files. This scenario is the one described in "Basic ReaR Usage", except for the backup file format, which may take a different form than a tar archive. ReaR executes the custom commands provided by the user. To configure this, set the BACKUP directive to EXTERNAL . Then specify the commands to be run during backing up and restoration using the EXTERNAL_BACKUP and EXTERNAL_RESTORE directives. Optionally, also specify the EXTERNAL_IGNORE_ERRORS and EXTERNAL_CHECK directives. See /usr/share/rear/conf/default.conf for an example configuration.

Commands:
5.9. Multipath Command Options Table 5.1, "Useful multipath Command Options" describes some options of the multipath command that you may find useful. Table 5.1. Useful multipath Command Options Option Description -l Display the current multipath configuration gathered from sysfs and the device mapper. -ll Display the current multipath configuration gathered from sysfs , the device mapper, and all other available components on the system. -f device Remove the named multipath device. -F Remove all unused multipath devices. -w device Remove the wwid of the specified device from the wwids file. -W Reset the wwids file to include only the current multipath devices.

Commands:
Chapter 6. Using the Tekton plugin You can use the Tekton plugin to visualize the results of CI/CD pipeline runs on your Kubernetes or OpenShift clusters. The plugin allows users to visually see high level status of all associated tasks in the pipeline for their applications. You can use the Tekton front-end plugin to view PipelineRun resources. Prerequisites You have installed the Red Hat Developer Hub (RHDH). You have installed the Tekton plugin. For the installation process, see Installing and configuring the Tekton plugin . Procedure Open your RHDH application and select a component from the Catalog page. Go to the CI tab. The CI tab displays the list of PipelineRun resources associated with a Kubernetes cluster. The list contains pipeline run details, such as NAME , VULNERABILITIES , STATUS , TASK STATUS , STARTED , and DURATION . Click the expand row button besides PipelineRun name in the list to view the PipelineRun visualization. The pipeline run resource includes tasks to complete. When you hover the mouse pointer on a task card, you can view the steps to complete that particular task.

Commands:
Chapter 112. KafkaUserQuotas schema reference Used in: KafkaUserSpec Full list of KafkaUserQuotas schema properties Kafka allows a user to set quotas to control the use of resources by clients. 112.1. quotas You can configure your clients to use the following types of quotas: Network usage quotas specify the byte rate threshold for each group of clients sharing a quota. CPU utilization quotas specify a window for broker requests from clients. The window is the percentage of time for clients to make requests. A client makes requests on the I/O threads and network threads of the broker. Partition mutation quotas limit the number of partition mutations which clients are allowed to make per second. A partition mutation quota prevents Kafka clusters from being overwhelmed by concurrent topic operations. Partition mutations occur in response to the following types of user requests: Creating partitions for a new topic Adding partitions to an existing topic Deleting partitions from a topic You can configure a partition mutation quota to control the rate at which mutations are accepted for user requests. Using quotas for Kafka clients might be useful in a number of situations. Consider a wrongly configured Kafka producer which is sending requests at too high a rate. Such misconfiguration can cause a denial of service to other clients, so the problematic client ought to be blocked. By using a network limiting quota, it is possible to prevent this situation from significantly impacting other clients. AMQ Streams supports user-level quotas, but not client-level quotas. Example Kafka user quota configuration spec: quotas: producerByteRate: 1048576 consumerByteRate: 2097152 requestPercentage: 55 controllerMutationRate: 10 For more information about Kafka user quotas, refer to the Apache Kafka documentation . 112.2. KafkaUserQuotas schema properties Property Description consumerByteRate A quota on the maximum bytes per-second that each client group can fetch from a broker before the clients in the group are throttled. Defined on a per-broker basis. integer controllerMutationRate A quota on the rate at which mutations are accepted for the create topics request, the create partitions request and the delete topics request. The rate is accumulated by the number of partitions created or deleted. number producerByteRate A quota on the maximum bytes per-second that each client group can publish to a broker before the clients in the group are throttled. Defined on a per-broker basis. integer requestPercentage A quota on the maximum CPU utilization of each client group as a percentage of network and I/O threads. integer

Commands:
spec: quotas: producerByteRate: 1048576 consumerByteRate: 2097152 requestPercentage: 55 controllerMutationRate: 10
2.2.2.7. pykickstart The pykickstart package contains utilities that can be used to make migration easier. Make sure you have the latest package installed. The ksverdiff command takes a starting and ending syntax version, and reports differences in commands and options for the two given versions. It states the new, deprecated and removed commands and options. For example: You can also check the validity of your Kickstart file with the ksvalidator command. This command checks the validity of the file against any Kickstart syntax version that you specify. However, it cannot inform you about problems that would only happen at install time, for example if you specify part --ondisk=sdr and no such device exists. Example usage:

Commands:
ksverdiff --from RHEL5 --to RHEL6 The following commands were removed in RHEL6: langsupport mouse key The following commands were deprecated in RHEL6: monitor The following commands were added in RHEL6: sshpw group rescue updates fcoe
ksvalidator --version RHEL6 my-rhel5-ks.cfg
Chapter 13. Installing automation hub using the Ansible Automation Platform Operator Use the following procedure to install automation hub using the Ansible Automation Platform Operator. Procedure Navigate to Operator Installed Operators . Select your Ansible Automation Platform Operator deployment. Select the Automation hub tab. Click Create Automation hub . Select YAML view . The YAML should be similar to: apiVersion: automationhub.ansible.com/v1beta1 kind: AutomationHub metadata: name: private-ah 1 namespace: aap spec: sso_secret: automation-hub-sso 2 pulp_settings: verify_ssl: false route_tls_termination_mechanism: Edge ingress_type: Route loadbalancer_port: 80 file_storage_size: 100Gi image_pull_policy: IfNotPresent replicas: 1 3 web_replicas: N task_replicas: N file_storage_access_mode: ReadWriteMany content: log_level: INFO replicas: 2 postgres_storage_requirements: limits: storage: 50Gi requests: storage: 8Gi api: log_level: INFO replicas: 1 postgres_resource_requirements: limits: cpu: 1000m memory: 8Gi requests: cpu: 500m memory: 2Gi loadbalancer_protocol: http resource_manager: replicas: 1 worker: replicas: 2 1 Set metadata.name to the name to use for the instance. 2 Set spec.sso_secret to the name of the secret created in Creating a Secret to hold the Red Hat Single Sign On connection details . 3 Scale replicas up or down for each deployment by using the web_replicas or task_replicas respectively, where N represents the number of replicas you want to create. Alternatively, you can scale all pods across both deployments by using replicas . See Scaling the Web and Task Pods independently for details. Note This YAML turns off SSL verification ( ssl_verify: false ). If you are not using self-signed certificates for OpenShift this setting can be removed. Click Create and wait for the process to complete.

Commands:
apiVersion: automationhub.ansible.com/v1beta1 kind: AutomationHub metadata: name: private-ah 1 namespace: aap spec: sso_secret: automation-hub-sso 2 pulp_settings: verify_ssl: false route_tls_termination_mechanism: Edge ingress_type: Route loadbalancer_port: 80 file_storage_size: 100Gi image_pull_policy: IfNotPresent replicas: 1 3 web_replicas: N task_replicas: N file_storage_access_mode: ReadWriteMany content: log_level: INFO replicas: 2 postgres_storage_requirements: limits: storage: 50Gi requests: storage: 8Gi api: log_level: INFO replicas: 1 postgres_resource_requirements: limits: cpu: 1000m memory: 8Gi requests: cpu: 500m memory: 2Gi loadbalancer_protocol: http resource_manager: replicas: 1 worker: replicas: 2