mtpti5iD/redhat-docs_dataset huggingface dataset:
5.2.5. Removing Physical Volumes If a device is no longer required for use by LVM, you can remove the LVM label with the pvremove command. Executing the pvremove command zeroes the LVM metadata on an empty physical volume. If the physical volume you want to remove is currently part of a volume group, you must remove it from the volume group with the vgreduce command, as described in Section 5.3.7, "Removing Physical Volumes from a Volume Group" .

Commands:
pvremove /dev/ram15 Labels on physical volume "/dev/ram15" successfully wiped
4.4. CPU Frequency Governors The frequency of a CPU affects both performance and power usage. The cpufreq governors determine the frequency of a CPU at any given time based on a set of rules about the kind of behavior that prompts a change to a higher or lower frequency. Red Hat recommends the cpufreq_ondemand governor for most situations, as this governor provides better performance through a higher CPU frequency when the system is under load, and power savings through a lower CPU frequency when the system is not being heavily used. Note When calculating CPU load, the 'ondemand' CPU governor takes into account the sysfs parameter io_is_busy . If this is set to 1 , Input/Output (I/O) activity is included in CPU activity calculations, and if set to 0 it is excluded. The default setting is 1 . If I/O activity is excluded, the ondemand governor may reduce the CPU frequency to reduce power usage, resulting in slower I/O operations. The full path for the io_is_busy parameter is /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy . For maximum performance at the expense of power savings, you can use the cpufreq_performance governor. This governor uses the highest possible CPU frequency to ensure that tasks execute as quickly as possible. This governor does not make use of power saving mechanisms such as sleep or idle, and is therefore not recommended for data centers or similar large deployments. Procedure 4.1. Enabling and configuring a governor Ensure that cpupowerutils is installed: Check that the driver you want to use is available. If the driver you want is not available, use the modprobe command to add it to your system. For example, to add the ondemand governor, run: Set the governor temporarily by using the cpupower command line tool. For example, to set the ondemand governor, run: The profiles that ship with the tuned-adm tool also make use of CPU frequency governors; for details, see Section 3.6, "Tuned and ktune" .

Commands:
yum install cpupowerutils
cpupower frequency-info --governors
modprobe cpufreq_ondemand
cpupower frequency-set --governor ondemand
40.5.3. Using opannotate The opannotate tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting files generated should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function. For this utility to work, the executable must be compiled with GCC's -g option. By default, Red Hat Enterprise Linux packages are not compiled with this option. The general syntax for opannotate is as follows: The directory containing the source code and the executable to be analyzed must be specified. Refer to the opannotate man page for a list of additional command line options.

Commands:
opannotate --search-dirs <src-dir> --source <executable>
B.2. apr-util B.2.1. RHSA-2010:0950 - Moderate: apr-util security update Updated apr-util packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A 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 Apache Portable Runtime (APR) is a portability library used by the Apache HTTP Server and other projects. apr-util is a library which provides additional utility interfaces for APR; including support for XML parsing, LDAP, database interfaces, URI parsing, and more. CVE-2010-1623 It was found that certain input could cause the apr-util library to allocate more memory than intended in the apr_brigade_split_line() function. An attacker able to provide input in small chunks to an application using the apr-util library (such as httpd) could possibly use this flaw to trigger high memory consumption. All apr-util users should upgrade to these updated packages, which contain a backported patch to correct this issue. Applications using the apr-util library, such as httpd, must be restarted for this update to take effect.

Commands:
Chapter 2. Installing the Red Hat Ansible Automation Platform on Red Hat OpenShift Container Platform Prerequisites You have installed the Red Hat Ansible Automation Platform catalog in OperatorHub. You have created a StorageClass object for your platform and a persistent volume claim (PVC) with ReadWriteMany access mode. See Dynamic provisioning for details. To run Red Hat OpenShift Container Platform clusters on Amazon Web Services (AWS) with ReadWriteMany access mode, you must add NFS or other storage. For information about the AWS Elastic Block Store (EBS) or to use the aws-ebs storage class, see Persistent storage using AWS Elastic Block Store . To use multi-attach ReadWriteMany access mode for AWS EBS, see Attaching a volume to multiple instances with Amazon EBS Multi-Attach . Important You cannot deploy Ansible Automation Platform in the default namespace on your OpenShift Cluster. The aap namespace is recommended. You can use a custom namespace, but it should run only Ansible Automation Platform. Procedure Log in to Red Hat OpenShift Container Platform. Navigate to Operators OperatorHub . Search for the Red Hat Ansible Automation Platform operator and click Install . Select an Update Channel : stable-2.x : installs a namespace-scoped operator, which limits deployments of automation hub and automation controller instances to the namespace the operator is installed in. This is suitable for most cases. The stable-2.x channel does not require administrator privileges and utilizes fewer resources because it only monitors a single namespace. stable-2.x-cluster-scoped : deploys automation hub and automation controller across multiple namespaces in the cluster and requires administrator privileges for all namespaces in the cluster. Select Installation Mode , Installed Namespace , and Approval Strategy . Click Install . The installation process begins. When installation finishes, a modal appears notifying you that the Ansible Automation Platform Operator is installed in the specified namespace. Verification Click View Operator to view your newly installed Ansible Automation Platform Operator and verify the following operator custom resources are present: Automation controller Automation hub Event-Driven Ansible (EDA) Red Hat Ansible Lightspeed Automation Controller Automation Controller Backup Automation Controller Restore Automation Controller Mesh Ingress Automation Hub Automation Hub Backup Automation Hub Restore EDA EDA Backup EDA Restore Ansible Lightspeed Important You can only install a single instance of the Ansible Automation Platform Operator into a single namespace. Installing multiple instances in the same namespace can lead to improper operation for both operator instances.

Commands:
5.337. tuned 5.337.1. RHBA-2012:0924 - tuned bug fix and enhancement update Updated tuned packages that fix two bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The tuned package contains a daemon that tunes system settings dynamically. It does so by monitoring the usage of several system components periodically. Bug Fixes BZ# 747210 When the diskdevstat or netdevstat tool was run with wrong command-line arguments, the tool returned a compilation error and exited. Both tools have been fixed to check the command-line arguments. With this update, a short usage help message is printed in the described scenario, describing the available options. BZ# 725497 When the tuned utility was running in a virtual guest, the disk-scheduler setting was not applied on virtual disks (vd*). Now, default configuration files that cover virtual disks have been updated and the disk-scheduler setting is now applied on the virtual disks in virtual guests. Enhancements BZ# 740976 With this update, a new "virtual-host" profile has been added to the tuned package, providing fine-tuned profile for hypervisors managed by Red Hat Enterprise Virtualization Manager. BZ# 740977 With this update, a new "virtual-guest" profile for virtual systems has been added to the tuned package, providing fine-tuned profile for Red Hat Enterprise Linux 6 KVM virtual guests. Users of tuned are advised to upgrade to these updated packages which fix these bugs and add these enhancements.

Commands:
20.2. Setting Access ACLs There are two types of ACLs: access ACLs and default ACLs . An access ACL is the access control list for a specific file or directory. A default ACL can only be associated with a directory; if a file within the directory does not have an access ACL, it uses the rules of the default ACL for the directory. Default ACLs are optional. ACLs can be configured: Per user Per group Via the effective rights mask For users not in the user group for the file The setfacl utility sets ACLs for files and directories. Use the -m option to add or modify the ACL of a file or directory: Rules ( rules ) must be specified in the following formats. Multiple rules can be specified in the same command if they are separated by commas. u: uid : perms Sets the access ACL for a user. The user name or UID may be specified. The user may be any valid user on the system. g: gid : perms Sets the access ACL for a group. The group name or GID may be specified. The group may be any valid group on the system. m: perms Sets the effective rights mask. The mask is the union of all permissions of the owning group and all of the user and group entries. o: perms Sets the access ACL for users other than the ones in the group for the file. Permissions ( perms ) must be a combination of the characters r , w , and x for read, write, and execute. If a file or directory already has an ACL, and the setfacl command is used, the additional rules are added to the existing ACL or the existing rule is modified. Example 20.1. Give read and write permissions For example, to give read and write permissions to user andrius: To remove all the permissions for a user, group, or others, use the -x option and do not specify any permissions: Example 20.2. Remove all permissions For example, to remove all permissions from the user with UID 500:

Commands:
setfacl -m rules files
setfacl -m u:andrius:rw /project/somefile
setfacl -x rules files
setfacl -x u:500 /project/somefile
Chapter 2. Setting up RHEL image builder Use RHEL image builder to create your customized RHEL for Edge images. After you install RHEL image builder on a RHEL system, RHEL image builder is available as an application in RHEL web console. You can also access RHEL image builder on the command line by using the composer-cli tool. Note It is recommended to install RHEL image builder on a virtual machine. 2.1. Image builder system requirements The environment where RHEL image builder runs, for example a virtual machine, must meet the requirements that are listed in the following table. Note Running RHEL image builder inside a container is not supported. Table 2.1. Image builder system requirements Parameter Minimal Required Value System type A dedicated virtual machine Processor 2 cores Memory 4 GiB Disk space 20 GiB Access privileges Administrator level (root) Network Connectivity to Internet Note The 20 GiB disk space requirement is enough to install and run RHEL image builder in the host. To build and deploy image builds, you must allocate additional dedicated disk space. 2.2. Installing RHEL image builder To install RHEL image builder on a dedicated virtual machine, follow these steps: Prerequisites The virtual machine is created and is powered on. You have installed RHEL and you have subscribed to RHSM or Red Hat Satellite. You have enabled the BaseOS and AppStream repositories to be able to install the RHEL image builder packages. Procedure Install the following packages on the virtual machine. osbuild-composer composer-cli cockpit-composer bash-completion firewalld RHEL image builder is installed as an application in RHEL web console. Reboot the virtual machine Configure the system firewall to allow access to the web console: Enable RHEL image builder. The osbuild-composer and cockpit services start automatically on first access. Load the shell configuration script so that the autocomplete feature for the composer-cli command starts working immediately without reboot: Additional resources Managing repositories

Commands:
yum install osbuild-composer composer-cli cockpit-composer bash-completion firewalld
firewall-cmd --add-service=cockpit && firewall-cmd --add-service=cockpit --permanent
systemctl enable osbuild-composer.socket cockpit.socket --now
source /etc/bash_completion.d/composer-cli
Chapter 1. About the Bare Metal Service The OpenStack Bare Metal service (ironic) provides the components required to provision and manage physical machines for end users. The Bare Metal service in the overcloud interacts with the following OpenStack services: OpenStack Compute (nova) provides scheduling, tenant quotas, IP assignment, and a user-facing API for virtual machine instance management, while the Bare Metal service provides the administrative API for hardware management. OpenStack Identity (keystone) provides request authentication and assists the Bare Metal service in locating other OpenStack services. OpenStack Image service (glance) manages images and image metadata. OpenStack Networking (neutron) provides DHCP and network configuration. OpenStack Object Storage (swift) is used by certain drivers to expose temporary URLs to images. The Bare Metal service uses iPXE to provision physical machines. The following diagram outlines how the OpenStack services interact during the provisioning process when a user launches a new machine with the default drivers.

Commands:
Chapter 23. KafkaAuthorizationKeycloak schema reference Used in: KafkaClusterSpec The type property is a discriminator that distinguishes use of the KafkaAuthorizationKeycloak type from KafkaAuthorizationSimple , KafkaAuthorizationOpa , KafkaAuthorizationCustom . It must have the value keycloak for the type KafkaAuthorizationKeycloak . Property Description type Must be keycloak . string clientId OAuth Client ID which the Kafka client can use to authenticate against the OAuth server and use the token endpoint URI. string tokenEndpointUri Authorization server token endpoint URI. string tlsTrustedCertificates Trusted certificates for TLS connection to the OAuth server. CertSecretSource array disableTlsHostnameVerification Enable or disable TLS hostname verification. Default value is false . boolean delegateToKafkaAcls Whether authorization decision should be delegated to the 'Simple' authorizer if DENIED by Red Hat Single Sign-On Authorization Services policies. Default value is false . boolean grantsRefreshPeriodSeconds The time between two consecutive grants refresh runs in seconds. The default value is 60. integer grantsRefreshPoolSize The number of threads to use to refresh grants for active sessions. The more threads, the more parallelism, so the sooner the job completes. However, using more threads places a heavier load on the authorization server. The default value is 5. integer grantsGcPeriodSeconds The time, in seconds, between consecutive runs of a job that cleans stale grants from the cache. The default value is 300. integer grantsAlwaysLatest Controls whether the latest grants are fetched for a new session. When enabled, grants are retrieved from Red Hat Single Sign-On and cached for the user. The default value is false . boolean superUsers List of super users. Should contain list of user principals which should get unlimited access rights. string array connectTimeoutSeconds The connect timeout in seconds when connecting to authorization server. If not set, the effective connect timeout is 60 seconds. integer readTimeoutSeconds The read timeout in seconds when connecting to authorization server. If not set, the effective read timeout is 60 seconds. integer httpRetries The maximum number of retries to attempt if an initial HTTP request fails. If not set, the default is to not attempt any retries. integer enableMetrics Enable or disable OAuth metrics. The default value is false . boolean grantsMaxIdleTimeSeconds The time, in seconds, after which an idle grant can be evicted from the cache. The default value is 300. integer

Commands:
Chapter 7. Managing your Red Hat subscriptions in the Hybrid Cloud Console With a Red Hat subscription, you can download Red Hat tested and certified enterprise software. Your active subscriptions provide continuous access to Red Hat software as is developed by Red Hat and its partners. Subscription Services, available from the Hybrid Cloud Console, simplifies how you interact with your subscriptions by providing subscription management capabilities, historical subscriptions usage reporting, and hybrid committed spend drawdown data. By using Subscription Services, you can more effectively manage and track your subscriptions over their life cycle. Prerequisites You are logged in to the Hybrid Cloud Console. You have at least one Red Hat subscription. Procedure On the home page of the Hybrid Cloud Console, scroll to the Subscription Services tile. Click View all subscriptions . The Subscription Services overview page opens and the Subscription Services menu appears in the left navigation panel. Review the options available from the Subscription Services menu: Overview : Provides information about Subscription Services and includes links to purchase subscriptions. Subscriptions Inventory : Lists all of the current subscriptions in your account, including their statuses and subscription details. For more information about subscriptions inventory, see Viewing and managing your subscription inventory on the Hybrid Cloud Console . Subscriptions Usage : Reports account-level information about the usage of select Red Hat subscriptions, organized by major Red Hat platforms. Subscriptions usage simplifies how you interact with your subscriptions by providing both historical subscriptions usage data and an ability to make informed, forward-facing decisions based on that usage and your remaining subscription capacity. For more information about Subscriptions Usage, see Getting Started with the Subscriptions Service . Hybrid Committed Spend : Automatically aggregates and processes cost and usage data from the required integrations and shares this data with other Hybrid Cloud Console services such as subscriptions usage and cost management. Therefore, configuring integrations for hybrid committed spend reduces the need for manual reporting of hybrid committed spend data. For more information about hybrid committed spend, see Getting started with hybrid committed spend . Note To access hybrid committed spend, your organization must sign a hybrid committed spend contract and your account must have permission to view hybrid committed spend. Contact your Red Hat sales or support representative for more information. Manifests : Provides the ability to create, export, and perform other management tasks on manifests for Red Hat Satellite Server. A manifest is a set of encrypted files that contains the subscription information that is required to import subscriptions into Satellite. For more information about manifests, see Creating and managing manifests for a connected Satellite Server . Additional resources For more information about subscriptions, see the Subscription Central product documentation page .

Commands:
4.4.2. The Working Set The group of physical memory pages currently dedicated to a specific process is known as the working set for that process. The number of pages in the working set can grow and shrink, depending on the overall availability of pages on a system-wide basis. The working set grows as a process page faults. The working set shrinks as fewer and fewer free pages exist. To keep from running out of memory completely, pages must be removed from process's working sets and turned into free pages, available for later use. The operating system shrinks processes' working sets by: Writing modified pages to a dedicated area on a mass storage device (usually known as swapping or paging space) Marking unmodified pages as being free (there is no need to write these pages out to disk as they have not changed) To determine appropriate working sets for all processes, the operating system must track usage information for all pages. In this way, the operating system determines which pages are actively being used (and must remain memory resident) and which pages are not (and therefore, can be removed from memory.) In most cases, some sort of least-recently used algorithm determines which pages are eligible for removal from process working sets.

Commands:
Chapter 1. Rotating a username or password for database accounts in RHOSO You can rotate the username and password used for database accounts in Red Hat OpenStack Services on OpenShift (RHOSO) by editing an openstackcontrolplanes custom resource. 1.1. Generating a new username and password for database accounts You can generate a new username and password for a database account by editing the YAML file that contains the templates for the database accounts. The database account corresponds to a MariaDBAccount YAML resource. The MariaDBAccount YAML refers to an actual database username and a Secret that contains a password. The name of the MariaDBAccount and the username that the MariaDBAccount refers to are different. The MariaDBAccount is a resource identifier, which uses dashes to seperate each word, and the MariaDB username uses underscores to seperate each word. When you change the value of databaseAccount: parameter in the yaml file, this creates a new MariaDBAccount resource, that has a randomly-generated username and secret that contains a password. This resource creates a pod that creates an actual MariaDB database username in the target database. Important To avoid interruptions to long-running migrations that cannot be interrupted, use a maintenance window. For example, block storage (Cinder) volume migrations or compute service (Nova) host migrations. Procedure To retrieve the name of the YAML file that contains the details of the database, use the oc get openstackcontrolplanes command. To access the YAML file, use the oc edit openstackcontrolplanes <YAML_File_Name> command. Replace <YAML_File_Name> with the name of the YAML file that you retrieved in step 1. In the YAML file, locate the database account that you want to generate a new username and password for. to the databaseAccount: label, change the name of the database account. A new database account and password is automatically generated, and the services automatically switch to the new database account. Note You must separate each word in the MariaDBAccount name with a dash. Optional: To delete the old database account, use the oc delete mariadbaccounts <mariadbaccount_name> command. The MariaDBAccount remains until the resources are updated to use a new MariaDBAccount. Replace <mariadbaccount_name> with the name of the database account that you want to delete.

Commands: