mtpti5iD/redhat-docs_dataset huggingface dataset:
16.20. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. Depending on the available resources, you might see the following progress bar while the installer resolves dependencies of the packages you selected for installation: Figure 16.53. Starting installation During installation of the selected packages and their dependencies, you see the following progress bar: Figure 16.54. Packages completed

Commands:
5.132. kdelibs3 5.132.1. RHBA-2012:1244 - kdelibs3 bug fix update Updated kdelibs3 packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The kdelibs3 packages provide libraries for the K Desktop Environment (KDE). Bug Fixes BZ# 681901 Prior to this update, the kdelibs3 libraries caused a conflict for the subversion version control tool. As a consequence, subvervision was not correctly built if the kdelibs3 libraries were installed. This update modifies the underlying code to avoid this conflict. Now, subversion builds as expected with kdelibs3. BZ# 734447 kdelibs3 provided its own set of trusted Certificate Authority (CA) certificates. This update makes kdelibs3 use the system set from the ca-certificates package, instead of its own copy. All users of kdelibs3 are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. OperatorHub APIs 1.1. CatalogSource [operators.coreos.com/v1alpha1] Description CatalogSource is a repository of CSVs, CRDs, and operator packages. Type object 1.2. ClusterServiceVersion [operators.coreos.com/v1alpha1] Description ClusterServiceVersion is a Custom Resource of type ClusterServiceVersionSpec . Type object 1.3. InstallPlan [operators.coreos.com/v1alpha1] Description InstallPlan defines the installation of a set of operators. Type object 1.4. OLMConfig [operators.coreos.com/v1] Description OLMConfig is a resource responsible for configuring OLM. Type object 1.5. Operator [operators.coreos.com/v1] Description Operator represents a cluster operator. Type object 1.6. OperatorCondition [operators.coreos.com/v2] Description OperatorCondition is a Custom Resource of type OperatorCondition which is used to convey information to OLM about the state of an operator. Type object 1.7. OperatorGroup [operators.coreos.com/v1] Description OperatorGroup is the unit of multitenancy for OLM managed operators. It constrains the installation of operators in its namespace to a specified set of target namespaces. Type object 1.8. PackageManifest [packages.operators.coreos.com/v1] Description PackageManifest holds information about a package, which is a reference to one (or more) channels under a single package. Type object 1.9. Subscription [operators.coreos.com/v1alpha1] Description Subscription keeps operators up to date by tracking changes to Catalogs. Type object

Commands:
3.3. SELinux Contexts for Users Use the id -Z command to view the SELinux context associated with your Linux user: In Red Hat Enterprise Linux, Linux users run unconfined by default. This SELinux context shows that the Linux user is mapped to the SELinux unconfined_u user, running as the unconfined_r role, and is running in the unconfined_t domain. s0-s0 is an MLS range, which in this case, is the same as just s0 . The categories the user has access to is defined by c0.c1023 , which is all categories ( c0 through to c1023 ).

Commands:
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
Chapter 15. Configuring API tokens Red Hat Advanced Cluster Security for Kubernetes (RHACS) requires API tokens for some system integrations, authentication processes, and system functions. You can configure tokens using the RHACS web interface. 15.1. Creating an API token Procedure In the RHACS portal, go to Platform Configuration Integrations . Scroll to the Authentication Tokens category, and then click API Token . Click Generate Token . Enter a name for the token and select a role that provides the required level of access (for example, Continuous Integration or Sensor Creator ). Click Generate . Important Copy the generated token and securely store it. You will not be able to view it again. 15.2. About API token expiration API tokens expire one year from the creation date. RHACS alerts you in the web interface and by sending log messages to Central when a token will expire in less than one week. The log message process runs once an hour. Once a day, the process lists the tokens that are expiring and creates a log message for each one. Log messages are issued once a day and appear in Central logs. Logs have the format as shown in the following example: Warn: API Token [token name] (ID [token ID]) will expire in less than X days. You can change the default settings for the log message process by configuring the environment variables shown in the following table: Environment variable Default value Description ROX_TOKEN_EXPIRATION_NOTIFIER_INTERVAL 1h (1 hour) The frequency at which the log message background loop that lists tokens and creates the logs will run. ROX_TOKEN_EXPIRATION_NOTIFIER_BACKOFF_INTERVAL 24h (1 day) The frequency at which the loop lists tokens and issues notifications. ROX_TOKEN_EXPIRATION_DETECTION_WINDOW 168h (1 week) The time period before expiration of the token that will cause the notification to be generated.

Commands:
Warn: API Token [token name] (ID [token ID]) will expire in less than X days.
Chapter 24. Virtualization Performance monitoring in KVM guests As a Technology Preview, KVM can virtualize a performance monitoring unit (vPMU) to allow virtual machines to use performance monitoring. Additionally it supports Intel's "architectural PMU" which can be live-migrated across different host CPU versions, using the -cpu host option. The virtual performance monitoring feature allows virtual machine users to identify sources of performance problems in their guests, using their preferred pre-existing profiling tools that work on the host as well as the guest. Note that this is an addition to the existing ability to profile a KVM guest from the host. Package: kernel-2.6.32-696 System monitoring using SNMP As a Technology Preview, Red Hat Enterprise Linux 6 allows Simple Network Management Protocol (SNMP) to be used for system monitoring. This allows KVM hosts to send SNMP traps on events so that hypervisor events can be communicated to the user via standard SNMP protocol. In addition, SNMP is capable of performing basic virtual networking operations, such as starting and stopping the virtual domain. Package: libvirt-snmp-0.0.2-5 Zero-copy compatibility for macvtap-vhost The macvtap-vhost zero-copy capability is available on Red Hat Enterprise Linux 6 as a Technology Preview. This feature allows running networking work loads in very high wire speeds but with low CPU resource consumption, and it does not limit other features such as memory overcommit and guest migration, which is not the case when using PCI device assignment to achieve the wire speed. Note that this feature is disabled by default. Package: qemu-kvm-0.12.1.2-2.499 vCPU hot unplug Although hot-plugging a virtual CPU (vCPU) is a supported operation, hot-unplugging a vCPU remains a Technology Preview in Red Hat Enterprise Linux 6, and is strongly recommended not to be used in high-value deployments. Package: libvirt-0.10.2-62

Commands:
Chapter 5. Using NVIDIA GPU resources with serverless applications NVIDIA supports using GPU resources on OpenShift Container Platform. See GPU Operator on OpenShift for more information about setting up GPU resources on OpenShift Container Platform. 5.1. Specifying GPU requirements for a service After GPU resources are enabled for your OpenShift Container Platform cluster, you can specify GPU requirements for a Knative service using the Knative ( kn ) CLI. Prerequisites The OpenShift Serverless Operator, Knative Serving and Knative Eventing are installed on the cluster. You have installed the Knative ( kn ) CLI. GPU resources are enabled for your OpenShift Container Platform cluster. You have created a project or have access to a project with the appropriate roles and permissions to create applications and other workloads in OpenShift Container Platform. Note Using NVIDIA GPU resources is not supported for IBM zSystems and IBM Power on OpenShift Container Platform or OpenShift Dedicated. Procedure Create a Knative service and set the GPU resource requirement limit to 1 by using the --limit nvidia.com/gpu=1 flag: USD kn service create hello --image <service-image> --limit nvidia.com/gpu=1 A GPU resource requirement limit of 1 means that the service has 1 GPU resource dedicated. Services do not share GPU resources. Any other services that require GPU resources must wait until the GPU resource is no longer in use. A limit of 1 GPU also means that applications exceeding usage of 1 GPU resource are restricted. If a service requests more than 1 GPU resource, it is deployed on a node where the GPU resource requirements can be met. Optional. For an existing service, you can change the GPU resource requirement limit to 3 by using the --limit nvidia.com/gpu=3 flag: USD kn service update hello --limit nvidia.com/gpu=3 5.2. Additional resources for OpenShift Container Platform Setting resource quotas for extended resources

Commands:
kn service create hello --image <service-image> --limit nvidia.com/gpu=1
kn service update hello --limit nvidia.com/gpu=3
Chapter 2. Multicluster storage health To view the overall storage health status across all the clusters with OpenShift Data Foundation and manage its capacity, you must first enable the multicluster dashboard on the Hub cluster. 2.1. Enabling multicluster dashboard on Hub cluster You can enable the multicluster dashboard on the install screen either before or after installing ODF Multicluster Orchestrator with the console plugin. Prerequisites Ensure that you have installed OpenShift Container Platform version 4.13 and have administrator privileges. Ensure that you have installed Multicluster Orchestrator 4.13 operator with plugin for console enabled. Ensure that you have installed Red Hat Advanced Cluster Management for Kubernetes (RHACM) 2.8 from Operator Hub. For instructions on how to install, see Installing RHACM . Ensure you have enabled observability on RHACM. See Enabling observability guidelines . Procedure Create the configmap file named observability-metrics-custom-allowlist.yaml and add the name of the custom metric to the metrics_list.yaml parameter. You can use the following YAML to list the OpenShift Data Foundation metrics on Hub cluster. For details, see Adding custom metrics . Run the following command in the open-cluster-management-observability namespace: After observability-metrics-custom-allowlist yaml is created, RHACM will start collecting the listed OpenShift Data Foundation metrics from all the managed clusters. If you want to exclude specific managed clusters from collecting the observability data, add the following cluster label to your clusters: observability: disabled . To view the multicluster health, see chapter verifying multicluster storage dashboard . 2.2. Verifying multicluster storage health on hub cluster Prerequisites Ensure that you have enabled multicluster monitoring. For instructions, see chapter Enabling multicluster dashboard . Procedure In the OpenShift web console of Hub cluster, ensure All Clusters is selected. Navigate to Data Services and click Storage System . On the Overview tab, verify that there are green ticks in front of OpenShift Data Foundation and Systems . This indicates that the operator is running and all storage systems are available. In the Status card, Click OpenShift Data Foundation to view the operator status. Click Systems to view the storage system status. The Storage system capacity card shows the following details: Name of the storage system Cluster name Graphical representation of total and used capacity in percentage Actual values for total and used capacity in TiB

Commands:
kind: ConfigMap apiVersion: v1 metadata: name: observability-metrics-custom-allowlist Namespace: open-cluster-management-observability data: metrics_list.yaml: | names: - odf_system_health_status - odf_system_map - odf_system_raw_capacity_total_bytes - odf_system_raw_capacity_used_bytes matches: - __name__="csv_succeeded",exported_namespace="openshift-storage",name=~"odf-operator.*"
oc apply -n open-cluster-management-observability -f observability-metrics-custom-allowlist.yaml
Part IV. OptaPlanner score calculation Every @PlanningSolution class has a score. The score is an objective way to compare two solutions. The solution with the higher score is better. The solver aims to find the solution with the highest score out of all possible solutions. The best solution is the solution with the highest score the solver has encountered during solving, which might be the optimal solution . OptaPlanner cannot automatically know which solution is best for your business, so you must tell it how to calculate the score of a specified @PlanningSolution instance according to your business requirements. If you forget or are unable to implement an important business constraint, the solution is probably useless, as illustrated in the following image:

Commands:
11.2. Adding Swap Space Sometimes it is necessary to add more swap space after installation. For example, you may upgrade the amount of RAM in your system from 128 MB to 256 MB, but there is only 256 MB of swap space. It might be advantageous to increase the amount of swap space to 512 MB if you perform memory-intense operations or run applications that require a large amount of memory. You have three options: create a new swap partition, create a new swap file, or extend swap on an existing LVM2 logical volume. It is recommended that you extend an existing logical volume. 11.2.1. Extending Swap on an LVM2 Logical Volume To extend an LVM2 swap logical volume (assuming /dev/VolGroup00/LogVol01 is the volume you want to extend): Disable swapping for the associated logical volume: Resize the LVM2 logical volume by 256 MB: Format the new swap space: Enable the extended logical volume: Test that the logical volume has been extended properly:

Commands:
swapoff -v /dev/VolGroup00/LogVol01
lvm lvresize /dev/VolGroup00/LogVol01 -L +256M
mkswap /dev/VolGroup00/LogVol01
swapon -va
cat /proc/swaps # free
Chapter 5. Using custom Red Hat build of Keycloak images 5.1. Red Hat build of Keycloak custom image with the Operator With the Keycloak Custom Resource (CR), you can specify a custom container image for the Red Hat build of Keycloak server. Note To ensure full compatibility of Operator and Operand, make sure that the version of Red Hat build of Keycloak release used in the custom image is aligned with the version of the operator. 5.1.1. Best practice When using the default Red Hat build of Keycloak image, the server will perform a costly re-augmentation every time a Pod starts. To avoid this delay, you can provide a custom image with the augmentation built-in from the build time of the image. With a custom image, you can also specify the Keycloak build-time configurations and extensions during the build of the container. Warning When using optimized custom image, health-enabled and metrics-enabled options need to be explicitly set in the Containerfile. For instructions on how to build such an image, see Running Red Hat build of Keycloak in a container . 5.1.2. Providing a custom Red Hat build of Keycloak image To provide a custom image, you define the image field in the Keycloak CR as shown in this example: apiVersion: k8s.keycloak.org/v2alpha1 kind: Keycloak metadata: name: example-kc spec: instances: 1 image: quay.io/my-company/my-keycloak:latest http: tlsSecret: example-tls-secret hostname: hostname: test.keycloak.org Note With custom images, every build time option passed either through a dedicated field or the additionalOptions is ignored. Note The Operator is unaware of any configuration options that are specified in a custom image. Use the Keycloak CR for any configuration that requires Operator awareness, namely the TLS and HTTP(S) settings reflected when configuring services and probes. 5.1.3. Non-optimized custom image While it is considered a best practice use a pre-augmented image, if you want to use a non-optimized custom image or build time properties with an augmented image that is still possible. You just need set the startOptimized field to false as shown in this example: apiVersion: k8s.keycloak.org/v2alpha1 kind: Keycloak metadata: name: example-kc spec: instances: 1 image: quay.io/my-company/my-keycloak:latest startOptimized: false http: tlsSecret: example-tls-secret hostname: hostname: test.keycloak.org Keep in mind this will incur the re-augmentation cost on every start.

Commands:
apiVersion: k8s.keycloak.org/v2alpha1 kind: Keycloak metadata: name: example-kc spec: instances: 1 image: quay.io/my-company/my-keycloak:latest http: tlsSecret: example-tls-secret hostname: hostname: test.keycloak.org
apiVersion: k8s.keycloak.org/v2alpha1 kind: Keycloak metadata: name: example-kc spec: instances: 1 image: quay.io/my-company/my-keycloak:latest startOptimized: false http: tlsSecret: example-tls-secret hostname: hostname: test.keycloak.org
Chapter 21. Networking Mellanox SR-IOV Support Single Root I/O Virtualization (SR-IOV) is now supported as a Technology Preview in the Mellanox libmlx4 library and the following drivers: mlx_core mlx4_ib (InfiniBand protocol) mlx_en (Ethernet protocol) Package: kernel-2.6.32-696 QFQ queuing discipline In Red Hat Enterprise Linux 6, the tc utility has been updated to work with the Quick Fair Scheduler (QFQ) kernel features. Users can now take advantage of the new QFQ traffic queuing discipline from userspace. This feature is considered a Technology Preview. Package: kernel-2.6.32-696

Commands:
Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Red Hat Fuse on OpenShift enables you to deploy Fuse applications on OpenShift Container Platform.

Commands:
Chapter 109. KafkaUserAuthorizationSimple schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserAuthorizationSimple type from other subtypes which may be added in the future. It must have the value simple for the type KafkaUserAuthorizationSimple . Property Property type Description type string Must be simple . acls AclRule array List of ACL rules which should be applied to this user.

Commands:
Chapter 28. Network Driver Updates The tg3 driver has been updated to version 3.137. The e1000 driver has been updated to version 7.3.21-k8-NAPI, which provides support for txtd update delay when using the xmit_more Boolean variable. The e1000e driver has been updated to version 3.2.5-k. The igb driver has been updated to version 5.2.15-k. The igbvf driver has been updated to version 2.0.2-k. The ixgbevf driver has been updated to version 2.12.1-k. The ixgbe driver has been updated to version 4.0.1-k. The bna driver and firmware have been updated to version 3.2.23.0r. The bnx2 driver has been updated to version 2.2.6. The CNIC driver has been updated to version 2.5.21. The bnx2x driver has been updated to version 1.710.51-0, which also adds qlogic NPAR support for qlogic-nx2 adapters. The be2net driver has been updated to version 10.6.0.3r. The qlcnic driver has been updated to version 5.3.62. The qlge driver has been updated to version 1.00.00.34. It fixes a race condition between the New API (NAPI) registration and unregistration which previously led to the system crash. This race condition occured if certain parameters were changed while the Network Interface Card (NIC) was set to "down". The r8169 driver has been updated to version 2.3LK-NAPI. The i40e driver has been updated to version 1.3.21-k. The i40evf driver has been updated to version 1.3.13. The netxen_nic driver has been updated to version 4.0.82. The sfc driver has been updated to the latest upstream version. This update adds the fm10k driver of version 0.15.2-k. This update adds VTI6 support including netns capabilities. The bonding driver has been updated to version 3.7.1. The iwlwifi driver has been updated to the latest upstream version. The vxlan driver has been updated to version 0.1.

Commands:
5.180. m2crypto 5.180.1. RHBA-2012:0975 - m2crypto bug fix update An updated m2crypto package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The m2crypto package allows Python programs to call OpenSSL functions. Bug Fixes BZ# 742914 The M2Crypto.httpslib.HTTPSConnection class always created an IPv4 socket. This made it impossible to connect to IPv6 servers using this class. With this update, the implementation now correctly creates an IPv4 or IPv6 socket, as necessary, thus adding support for IPv6 servers. BZ# 803520 Prior to this update, the AES_crypt() function did not free a temporary buffer. This caused a memory leak when the function was called repeatedly. This problem has been fixed and the AES_crypt() function now frees memory correctly. BZ# 803554 The implementation of HTTPS connections via a proxy did not reflect the changes in Python 2.6. Consequently, every attempt to connect to an HTTPS server using a proxy failed, generating an exception. The M2Crypto implementation has been updated and now works correctly. All users of m2crypto are advised to upgrade to this updated package, which fixes these bugs.

Commands:
6.5. Additional Resources hostnamectl(1) man page - Describes hostnamectl including the commands and command options. hostname(1) man page - Contains an explanation of the hostname and domainname commands. hostname(5) man page - Contains an explanation of the host name file, its contents, and use. hostname(7) man page - Contains an explanation of host name resolution. machine-info(5) man page - Describes the local machine information file and the environment variables it contains. machine-id(5) man page - Describes the local machine ID configuration file. systemd-hostnamed.service(8) man page - Describes the systemd-hostnamed system service used by hostnamectl .

Commands: