mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Red Hat Enterprise Linux 6 This section outlines the packages released for Red Hat Enterprise Linux 6. 4.1. Red Hat Satellite Client 6 (for RHEL 6 Server - ELS) (RPMs) The following table outlines the packages included in the rhel-6-server-els-satellite-client-6-rpms repository. Table 4.1. Red Hat Satellite Client 6 (for RHEL 6 Server - ELS) (RPMs) Name Version Advisory gofer 2.11.9-1.el6sat RHBA-2022:96562 katello-agent 3.5.7-3.el6sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el6sat RHBA-2022:96562 katello-host-tools-fact-plugin 3.5.7-3.el6sat RHBA-2022:96562 pulp-rpm-handlers 2.21.5-2.el6sat RHBA-2022:96562 puppet-agent 7.16.0-2.el6sat RHBA-2022:96562 python-gofer 2.11.9-1.el6sat RHBA-2022:96562 python-gofer-proton 2.11.9-1.el6sat RHBA-2022:96562 python-isodate 0.5.0-4.el6sat RHBA-2022:96562 python-pulp-agent-lib 2.21.5-2.el6sat RHBA-2022:96562 python-pulp-common 2.21.5-2.el6sat RHBA-2022:96562 python-pulp-rpm-common 2.21.5-2.el6sat RHBA-2022:96562 python-qpid-proton 0.28.0-3.el6_10 RHBA-2022:96562 qpid-proton-c 0.28.0-3.el6_10 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el6sat RHBA-2022:96562 rubygem-json 1.4.6-2.el6 RHBA-2022:96562 4.2. Red Hat Satellite Client 6 (for RHEL 6 for System Z - ELS) (RPMs) The following table outlines the packages included in the rhel-6-for-system-z-els-satellite-client-6-rpms repository. Table 4.2. Red Hat Satellite Client 6 (for RHEL 6 for System Z - ELS) (RPMs) Name Version Advisory gofer 2.11.9-1.el6sat RHBA-2022:96562 katello-agent 3.5.7-3.el6sat RHBA-2022:96562 katello-host-tools 3.5.7-3.el6sat RHBA-2022:96562 katello-host-tools-fact-plugin 3.5.7-3.el6sat RHBA-2022:96562 pulp-rpm-handlers 2.21.5-2.el6sat RHBA-2022:96562 python-gofer 2.11.9-1.el6sat RHBA-2022:96562 python-gofer-proton 2.11.9-1.el6sat RHBA-2022:96562 python-isodate 0.5.0-4.el6sat RHBA-2022:96562 python-pulp-agent-lib 2.21.5-2.el6sat RHBA-2022:96562 python-pulp-common 2.21.5-2.el6sat RHBA-2022:96562 python-pulp-rpm-common 2.21.5-2.el6sat RHBA-2022:96562 python-qpid-proton 0.28.0-3.el6_10 RHBA-2022:96562 qpid-proton-c 0.28.0-3.el6_10 RHBA-2022:96562 rubygem-foreman_scap_client 0.5.0-1.el6sat RHBA-2022:96562 rubygem-json 1.4.6-2.el6 RHBA-2022:96562

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. To install the Manager with a remote Manager database, manually create the database on the remote machine before running engine-setup . To install the Data Warehouse database on a remote machine, run the Data Warehouse configuration script ( ovirt-engine-dwh-setup ) on the remote machine. This script installs the Data Warehouse service and can create the Data Warehouse database automatically. 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 6. Investigating the operators of the RHOSO High Availability services You can use the following command to list the operators of your Red Hat OpenStack Services on OpenShift (RHOSO) environment to obtain the full names of the operators of the RHOSO High Availability services: Note When using these operators you can abbreviate the operator name by excluding the .openstack-operators portion of the name. For example, you can use the infra-operator to manage the memcached service. You can use the full name of an operator to retrieve its custom resource definition (CRD), by first using the following command to obtain the name of the CRD of the required operator: Replace <operator-name> with the full name of the required operator. This example obtains the name of the CRD of the Galera operator: Then you can use the following command to describe the CRD of this operator: Replace <operator-crd-name> with the full name of the CRD of required operator obtained from the command. This example describes the CRD of the Galera operator: For more information about Red Hat OpenShift Container Platform (RHOCP) operators, see What are Operators?

Commands:
oc get operators NAME AGE infra-operator.openstack-operators 9h mariadb-operator.openstack-operators 9h rabbitmq-cluster-operator.openstack-operators 9h
oc describe operator/<operator-name>
oc describe operator/mariadb-operator.openstack-operators |less Status: Components: Kind: CustomResourceDefinition Name: galeras.mariadb.openstack.org
oc describe crd/<operator-crd-name>
oc describe crd/galeras.mariadb.openstack.org Name: galeras.mariadb.openstack.org Namespace: Labels: operators.coreos.com/mariadb-operator.openstack-operators= Annotations: controller-gen.kubebuilder.io/version: v0.11.1 operatorframework.io/installed-alongside-96a31840a95472ca: openstack-operators/mariadb-operator.v0.0.1 API Version: apiextensions.k8s.io/v1 Kind: CustomResourceDefinition Metadata: Creation Timestamp: 2024-03-21T22:08:06Z Generation: 1 Resource Version: 64637 UID: f68caee7-b4ec-4713-8095-c4ee9b1fd13e Spec: .
Chapter 1. Schedule and quota APIs 1.1. AppliedClusterResourceQuota [quota.openshift.io/v1] Description AppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.2. ClusterResourceQuota [quota.openshift.io/v1] Description ClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.3. FlowSchema [flowcontrol.apiserver.k8s.io/v1beta1] Description FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher". Type object 1.4. LimitRange [v1] Description LimitRange sets resource usage limits for each kind of resource in a Namespace. Type object 1.5. PriorityClass [scheduling.k8s.io/v1] Description PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer. Type object 1.6. PriorityLevelConfiguration [flowcontrol.apiserver.k8s.io/v1beta1] Description PriorityLevelConfiguration represents the configuration of a priority level. Type object 1.7. ResourceQuota [v1] Description ResourceQuota sets aggregate quota restrictions enforced per namespace Type object

Commands:
Chapter 4. Deploying the configured back ends To deploy the configured back ends, complete the following steps: Procedure Log in as the stack user. Run the following command to deploy the custom back end configuration: Important If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud. For more information, see Modifying the overcloud environment in the Installing and managing Red Hat OpenStack Platform with director guide.

Commands:
openstack overcloud deploy --templates -e /home/stack/templates/custom-env.yaml
8.14. cjkuni-fonts 8.14.1. RHBA-2013:0962 - cjkuni-fonts bug fix update Updated cjkuni-fonts packages that fix one bug are now available. CJK Unifonts are Unicode TrueType fonts derived from original fonts made available by Arphic Technology under the Arphic Public License and extended by the CJK Unifonts project. Bug Fix BZ# 651651 Previously, under some configurations, the KDE startup menu did not show any Chinese characters in Chinese locales (both zh-CN and zh-TW), while Japanese and Korean did not have this problem. With this update, the KDE startup menu now displays Chinese characters in Chinese locales. Users of cjkuni-fonts are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Updating a model Red Hat Enterprise Linux AI allows you to upgrade LLMs that you locally downloaded to the latest version of the model. 2.1. Updating the models You can upgrade your local models to the latest version of the model using the RHEL AI tool set. Prerequisites You installed the InstructLab tools with the bootable container image. You initialized InstructLab and can use the ilab CLI. You downloaded LLMs on Red Hat Enterprise Linux AI. You created a Red Hat registry account and logged in on your machine. Procedure You can upgrade any model by running the following command. USD ilab model download --repository <repository_and_model> --release latest where: <repository_and_model> Specifies the repository location of the model as well as the model. You can access the models from the registry.redhat.io/rhelai1/ repository. <release> Specifies the version of the model. Set to latest , or a specific version of the model, for the most up to date version of the model. Verification You can view all the downloaded models on your system with the following command: USD ilab model list

Commands:
ilab model download --repository <repository_and_model> --release latest
ilab model list
Chapter 12. Flow metrics This section shows the metrics available to a Prometheus instance when you enable the flow collector using skupper init --enable-flow-collector . Most metrics share a set of common labels as shown below, exceptions are shown beside appropriate metrics. Note The metrics are available from https://skupper.<namespace>.svc.clusterlocal:8010/api/v1alpha1/metrics when console-auth is set to internal (default) or unsecured . Replace <namespace>` with the appropriate namespace where the Service Interconnect is deployed. Metrics The following metrics are available to a Prometheus instance: flows_total For tcp protocol this is the total number of connections. For http or http2 protocol this is the total number of distinct requests made. octets_total The total number of bytes delivered through the service network. active_flows The number of flows currently active including open tcp connections and in flight http requests. http_requests_method_total Total number of http requests grouped by method. Additional label: The http method , for example, GET , HEAD , POST . http_requests_result_total Total number of http requests by response code. Additional label: The http response code , for example 200 , 403 , 503 . active_links The total number of links between sites. Only sourceSite and direction labels are available for these metrics. active_routers The total number of routers. No labels available for filtering. active_sites The total number of sites. No labels available for filtering. Labels The following labels are common to most of the metrics allowing you to filter and categorize the data: address The address relating to the metric. Typically, this is the service name. sourceSite The site where the flow originated for the metric. This string is a combination of the site name and the site ID. destSite The site where the flow terminated for the metric. This string is a combination of the site name and the site ID. direction The direction of flow. For traffic sent from a client to server the value is incoming . For traffic sent from a client to server the value is outgoing . protocol The protocol used by the flow, tcp , http , or http2 . sourceProcess The name of the process originating the flow. destProcess The name of the process receiving the flow.

Commands:
7.190. scap-security-guide 7.190.1. RHBA-2015:1334 - scap-security-guide bug fix and enhancement update Updated scap-security-guide package that fixes several bugs and adds various enhancements are now available for Red Hat Enterprise Linux 6. The scap-security-guide package provides the security guidance, baselines, and associated validation mechanisms that use Security Content Automation Protocol (SCAP). SCAP Security Guide contains the necessary data to perform system security compliance scans regarding prescribed security policy requirements; both a written description and an automated test (probe) are included. By automating the testing, SCAP Security Guide provides a convenient and reliable way to verify system compliance on a regular basis. Bug Fixes BZ# 1133963 The SCAP content for Red Hat Enterprise Linux 6 Server is now shipped also in the datastream output format. * The SCAP content for Red Hat Enterprise Linux 7 Server has been included in order to enable the possibility to perform remote scans of Red Hat Enterprise Linux 7 Server systems from Red Hat Enterprise Linux 6 systems. * This update also includes the United States Government Configuration Baseline (USGCB) profile kickstart file for a new installation of USGCB-compliant Red Hat Enterprise Linux 6 Server system. Refer to Red Hat Enterprise Linux 6 Security Guide for further details. BZ# 1183034 Previously, when checking the sysctl kernel parameters configuration, the SCAP content recognized only the settings present in the /etc/sysctl.conf file. With this update, the content has been updated to also recognize the sysctl utility settings from additional configuration files located in the /etc/sysctl.d/ directory. BZ# 1185426 Prior to this update, when performing a validation if the removable media block special devices were configured with the "nodev", "noexec", or "nosuid" options, the content could incorrectly report shared memory (/dev/shm) device as the one missing the required setting. With this update, the corresponding Open Vulnerability and Assessment Language (OVAL) checks have been corrected to verify mount options settings only for removable media block special devices. BZ# 1191409 Due to a bug in the OVAL check validation, if the listening capability of the postfix service was disabled, the system property scan returned a failure even if the postfix package was not installed on the system. This bug has been corrected and the feature of the postfix service is now reported as disabled. Also, the underlying scan result returns "PASS" when the postfix package is not installed on the system. BZ# 1199946 An earlier version of the scap-security-guide package included also an Extensible Configuration Checklist Document Format (XCCDF) profile named "test". Since the purpose of this profile is just to check basic sanity of the corresponding SCAP content and it is not intended to be applied for actual system scan, the "test" profile has now been removed. Users of scap-security-guide are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 9. Supported Configurations Supported configurations for the AMQ Streams 2.5 release. 9.1. Supported platforms The following platforms are tested for AMQ Streams 2.5 running with Kafka on the version of Red Hat Enterprise Linux (RHEL) stated. Operating System Architecture JVM RHEL 7 x86, amd64 Java 11 RHEL 8 and 9 x86, amd64, ppc64le (IBM Power), s390x (IBM Z and IBM(R) LinuxONE), aarch64 (64-bit ARM) Java 11 and Java 17 Platforms are tested with Open JDK 11 and 17. The IBM JDK is supported but not regularly tested against during each release. Open JDK 8, Oracle JDK 8 & 11, and IBM JDK 8 are not supported. Note Support for aarch64 (64-bit ARM) applies to AMQ Streams 2.5 when running Kafka 3.5.0 only. 9.2. Supported Apache Kafka ecosystem In AMQ Streams, only the following components released directly from the Apache Software Foundation are supported: Apache Kafka Broker Apache Kafka Connect Apache MirrorMaker Apache MirrorMaker 2 Apache Kafka Java Producer, Consumer, Management clients, and Kafka Streams Apache ZooKeeper Note Apache ZooKeeper is supported solely as an implementation detail of Apache Kafka and should not be modified for other purposes. Additionally, the cores or vCPU allocated to ZooKeeper nodes are not included in subscription compliance calculations. In other words, ZooKeeper nodes do not count towards a customer's subscription. 9.3. Additional supported features Kafka Bridge Drain Cleaner Cruise Control Distributed Tracing See also, Chapter 11, Supported integration with Red Hat products . 9.4. Storage requirements Kafka requires block storage; file storage options like NFS are not compatible. Additional resources For information on the supported configurations for the AMQ Streams 2.2 LTS release, see the AMQ Streams Supported Configurations article on the customer portal.

Commands:
2.7. Considerations for Using Conga When using Conga to configure and manage your Red Hat Cluster, make sure that each computer running luci (the Conga user interface server) is running on the same network that the cluster is using for cluster communication. Otherwise, luci cannot configure the nodes to communicate on the right network. If the computer running luci is on another network (for example, a public network rather than a private network that the cluster is communicating on), contact an authorized Red Hat support representative to make sure that the appropriate host name is configured for each cluster node.

Commands:
Chapter 5. Backing OpenShift Container Platform applications with OpenShift Data Foundation You cannot directly install OpenShift Data Foundation during the OpenShift Container Platform installation. However, you can install OpenShift Data Foundation on an existing OpenShift Container Platform by using the Operator Hub and then configure the OpenShift Container Platform applications to be backed by OpenShift Data Foundation. Prerequisites OpenShift Container Platform is installed and you have administrative access to OpenShift Web Console. OpenShift Data Foundation is installed and running in the openshift-storage namespace. Procedure In the OpenShift Web Console, perform one of the following: Click Workloads Deployments . In the Deployments page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop-down menu on the top right of the page. Click Workloads Deployment Configs . In the Deployment Configs page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment Config to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop-down menu on the top right of the page. In the Add Storage page, you can choose one of the following options: Click the Use existing claim option and select a suitable PVC from the drop-down list. Click the Create new claim option. Select the appropriate CephFS or RBD storage class from the Storage Class drop-down list. Provide a name for the Persistent Volume Claim. Select ReadWriteOnce (RWO) or ReadWriteMany (RWX) access mode. Note ReadOnlyMany (ROX) is deactivated as it is not supported. Select the size of the desired storage capacity. Note You can expand the block PVs but cannot reduce the storage capacity after the creation of Persistent Volume Claim. Specify the mount path and subpath (if required) for the mount path volume inside the container. Click Save . Verification steps Depending on your configuration, perform one of the following: Click Workloads Deployments . Click Workloads Deployment Configs . Set the Project as required. Click the deployment for which you added storage to display the deployment details. Scroll down to Volumes and verify that your deployment has a Type that matches the Persistent Volume Claim that you assigned. Click the Persistent Volume Claim name and verify the storage class name in the Persistent Volume Claim Overview page.

Commands:
3.6. Other Schema Resources See the following links for more information about standard LDAPv3 schema: RFC 2251: Lightweight Directory Access Protocol (v3), http://www.ietf.org/rfc/rfc2251.txt RFC 2252: LDAPv3 Attribute Syntax Definitions, http://www.ietf.org/rfc/rfc2252.txt RFC 2256: Summary of the X.500 User Schema for Use with LDAPv3, http://www.ietf.org/rfc/rfc2256.txt Internet Engineering Task Force (IETF), http://www.ietf.org/ Understanding and Deploying LDAP Directory Services . T. Howes, M. Smith, G. Good, Macmillan Technical Publishing, 1999.

Commands:
4.79. gnutls 4.79.1. RHSA-2012:0429 - Important: gnutls security update Updated gnutls packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The GnuTLS library provides support for cryptographic algorithms and for protocols such as Transport Layer Security (TLS). Security Fixes CVE-2012-1573 A flaw was found in the way GnuTLS decrypted malformed TLS records. This could cause a TLS/SSL client or server to crash when processing a specially-crafted TLS record from a remote TLS/SSL connection peer. CVE-2011-4128 A boundary error was found in the gnutls_session_get_data() function. A malicious TLS/SSL server could use this flaw to crash a TLS/SSL client or, possibly, execute arbitrary code as the client, if the client passed a fixed-sized buffer to gnutls_session_get_data() before checking the real size of the session data provided by the server. Red Hat would like to thank Matthew Hall of Mu Dynamics for reporting CVE-2012-1573 . Users of GnuTLS are advised to upgrade to these updated packages, which contain backported patches to correct these issues. For the update to take effect, all applications linked to the GnuTLS library must be restarted, or the system rebooted.

Commands: