mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 110. AclRule schema reference Used in: KafkaUserAuthorizationSimple Full list of AclRule schema properties 110.1. AclRule schema properties Property Property type Description host string The host from which the action described in the ACL rule is allowed or denied. operation string (one of [Read, Write, Delete, Alter, Describe, All, IdempotentWrite, ClusterAction, Create, AlterConfigs, DescribeConfigs]) The operation property has been deprecated, and should now be configured using spec.authorization.acls[*].operations . Operation which will be allowed or denied. Supported operations are: Read, Write, Create, Delete, Alter, Describe, ClusterAction, AlterConfigs, DescribeConfigs, IdempotentWrite and All. operations string (one or more of [Read, Write, Delete, Alter, Describe, All, IdempotentWrite, ClusterAction, Create, AlterConfigs, DescribeConfigs]) array List of operations which will be allowed or denied. Supported operations are: Read, Write, Create, Delete, Alter, Describe, ClusterAction, AlterConfigs, DescribeConfigs, IdempotentWrite and All. resource AclRuleTopicResource , AclRuleGroupResource , AclRuleClusterResource , AclRuleTransactionalIdResource Indicates the resource for which given ACL rule applies. type string (one of [allow, deny]) The type of the rule. Currently the only supported type is allow . ACL rules with type allow are used to allow user to execute the specified operations. Default value is allow .

Commands:
7.124. libtevent 7.124.1. RHBA-2013:0354 - libtevent bug fix and enhancement update Updated libtevent packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libtevent packages provide Tevent, an event system based on the talloc memory management library. Tevent supports many event types, including timers, signals, and the classic file descriptor events. Tevent also provides helpers to deal with asynchronous code represented by the tevent_req (Tevent Request) functions. Note The libtevent packages have been upgraded to upstream version 0.9.17, which provides a number of bug fixes and enhancements over the version. These updated libtevent packages are compliant with requirements of Samba 4. (BZ# 766336 ) All users of libtevent are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
E.2. Metadata Contents The volume group metadata contains: Information about how and when it was created Information about the volume group The volume group information contains: Name and unique id A version number which is incremented whenever the metadata gets updated Any properties, such as: read/write or resizable Any administrative limit on the number of physical volumes and logical volumes it may contain The extent size (in units of sectors which are defined as 512 bytes) An unordered list of physical volumes making up the volume group, each with: Its UUID, used to determine the block device containing it Any properties, such as whether the physical volume is allocatable The offset to the start of the first extent within the physical volume (in sectors) The number of extents An unordered list of logical volumes, each consisting of An ordered list of logical volume segments. For each segment the metadata includes a mapping applied to an ordered list of physical volume segments or logical volume segments

Commands:
Chapter 3. Supported configurations 3.1. Supported Migration Toolkit for Runtimes migration paths The Migration Toolkit for Runtimes (MTR) supports the following migrations: Migrating from third-party enterprise application servers, such as Oracle WebLogic Server, to JBoss Enterprise Application Platform (JBoss EAP). Upgrading to the latest release of JBoss EAP. Migrating from a Windows-only .NET 4.5+ Framework to cross-platform .NET 8.0. (Developer Preview) MTR provides a comprehensive set of rules to assess the suitability of your applications for containerization and deployment on Red Hat OpenShift Container Platform (RHOCP). You can run an MTR analysis to assess your applications' suitability for migration to multiple target platforms. Table 3.1. Supported Java migration paths: Source platform ⇒ Target platform Source platform ⇒ Migration to JBoss EAP 7 & 8 OpenShift (cloud readiness) OpenJDK 11, 17, and 21 Jakarta EE 9 Camel 3 & 4 Spring Boot in Red Hat Runtimes Quarkus Open Liberty Oracle WebLogic Server ✔ ✔ ✔ - - - - - IBM WebSphere Application Server ✔ ✔ ✔ - - - - ✔ JBoss EAP 4 ✘ [a] ✔ ✔ - - - - - JBoss EAP 5 ✔ ✔ ✔ - - - - - JBoss EAP 6 ✔ ✔ ✔ - - - - - JBoss EAP 7 ✔ ✔ ✔ - - - ✔ - Thorntail ✔ [b] - - - - - - - Oracle JDK - ✔ ✔ - - - - - Camel 2 - ✔ ✔ - ✔ - - - Spring Boot - ✔ ✔ ✔ - ✔ ✔ - Any Java application - ✔ ✔ - - - - - Any Java EE application - - - ✔ - - - - [a] Although MTR does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform to JBoss EAP 7. [b] Requires JBoss Enterprise Application Platform expansion pack 2 (EAP XP 2) .NET migration paths: Source platform ⇒ Target platform (Developer Preview) Source platform ⇒ OpenShift (cloud readiness) Migration to .NET 8.0 .NET Framework 4.5+ (Windows only) ✔ ✔

Commands:
7.10. Creating a Virtual Machine Based on a Template Create a virtual machine from a template to enable the virtual machines to be pre-configured with an operating system, network interfaces, applications and other resources. Note Virtual machines created from a template depend on that template. This means that you cannot remove a template from the Manager if a virtual machine was created from that template. However, you can clone a virtual machine from a template to remove the dependency on that template. See Section 7.11, "Creating a Cloned Virtual Machine Based on a Template" for more information. Creating a Virtual Machine Based on a Template Click Compute Virtual Machines . Click New . Select the Cluster on which the virtual machine will run. Select a template from the Template list. Enter a Name , Description , and any Comments , and accept the default values inherited from the template in the rest of the fields. You can change them if needed. Click the Resource Allocation tab. Select the Thin or Clone radio button in the Storage Allocation area. If you select Thin , the disk format is QCOW2. If you select Clone , select either QCOW2 or Raw for disk format. Use the Target drop-down list to select the storage domain on which the virtual machine's virtual disk will be stored. Click OK . The virtual machine is displayed in the Virtual Machines tab.

Commands:
Chapter 2. Prerequisites On RHEL Atomic Host , atomic is part of the OSTree and is ready to use. On Red Hat Enterprise Linux , make sure you have covered the following: Subscribe the system to the Extras channel which provides the atomic package. For Red Hat Subscription Management run this command: If you are using Satellite, run: Install atomic using Yum: Make sure the docker service is running: If the output states "inactive", use the following command: Note On both systems, you need to have root privileges to use atomic .

Commands:
subscription-manager repos --enable rhel-7-server-extras-rpms
rhn-channel --add --channel rhel-x86_64-server-extras-7
yum install atomic
systemctl status docker
systemctl start docker
Chapter 32. Entitlement subscription-manager component, BZ#910345 The default firstboot behavior is to prompt for Subscription Manager or Subscription Asset Manager (SAM) details. It no longer offers a path to use the Red Hat Network Classic registration tool. rhn-client-tools component, BZ#910345 The rhn-client-tools utility is no longer configured by default to communicate with xmlrpc.rhn.redhat.com , instead, it prompts for the user's Red Hat Satellite or Red Hat Proxy details to be entered.

Commands:
Chapter 3. Tuning Satellite Server with predefined profiles If your Satellite deployment includes more than 5000 hosts, you can use predefined tuning profiles to improve performance of Satellite. Note that you cannot use tuning profiles on Capsules. You can choose one of the profiles depending on the number of hosts your Satellite manages and available hardware resources. The tuning profiles are available in the /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes directory. When you run the satellite-installer command with the --tuning option, deployment configuration settings are applied to Satellite in the following order: The default tuning profile defined in the /usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml file The tuning profile that you want to apply to your deployment and is defined in the /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/ directory Optional: If you have configured a /etc/foreman-installer/custom-hiera.yaml file, Satellite applies these configuration settings. Note that the configuration settings that are defined in the /etc/foreman-installer/custom-hiera.yaml file override the configuration settings that are defined in the tuning profiles. Therefore, before applying a tuning profile, you must compare the configuration settings that are defined in the default tuning profile in /usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml , the tuning profile that you want to apply and your /etc/foreman-installer/custom-hiera.yaml file, and remove any duplicated configuration from the /etc/foreman-installer/custom-hiera.yaml file. default Number of hosts: 0 - 5000 RAM: 20G Number of CPU cores: 4 medium Number of hosts: 5001 - 10000 RAM: 32G Number of CPU cores: 8 large Number of hosts: 10001 - 20000 RAM: 64G Number of CPU cores: 16 extra-large Number of hosts: 20001 - 60000 RAM: 128G Number of CPU cores: 32 extra-extra-large Number of hosts: 60000+ RAM: 256G Number of CPU cores: 48+ Procedure Optional: If you have configured the custom-hiera.yaml file on Satellite Server, back up the /etc/foreman-installer/custom-hiera.yaml file to custom-hiera.original . You can use the backup file to restore the /etc/foreman-installer/custom-hiera.yaml file to its original state if it becomes corrupted: Optional: If you have configured the custom-hiera.yaml file on Satellite Server, review the definitions of the default tuning profile in /usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml and the tuning profile that you want to apply in /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/ . Compare the configuration entries against the entries in your /etc/foreman-installer/custom-hiera.yaml file and remove any duplicated configuration settings in your /etc/foreman-installer/custom-hiera.yaml file. Enter the satellite-installer command with the --tuning option for the profile that you want to apply. For example, to apply the medium tuning profile settings, enter the following command:

Commands:
cp /etc/foreman-installer/custom-hiera.yaml /etc/foreman-installer/custom-hiera.original
satellite-installer --tuning medium
Providing feedback on Red Hat documentation We appreciate your input on our documentation. Do let us know how we can make it better. To give feedback, create a Bugzilla ticket: Go to the Bugzilla website. In the Component section, choose documentation . Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. Click Submit Bug . Red Hat OpenShift Data Foundation 4.12 supports deployment of Red Hat OpenShift on IBM Cloud clusters in connected environments.

Commands:
Chapter 12. Working with certmonger Part of managing machine authentication is managing machine certificates. The certmonger service manages certificate life cycle for applications and, if properly configured, can work together with a certificate authority (CA) to renew certificates. The certmonger daemon and its command-line clients simplify the process of generating public/private key pairs, creating certificate requests, and submitting requests to the CA for signing. The certmonger daemon monitors certificates for expiration and can renew certificates that are about to expire. The certificates that certmonger monitors are tracked in files stored in a configurable directory. The default location is /var/lib/certmonger/requests . Note The certmonger daemon cannot revoke certificates. A certificate can only be revoked by a relevant Certificate Authority, which needs to invalidate the certificate and update its Certificate Revocation List. 12.1. certmonger and Certificate Authorities By default, certmonger can automatically obtain three kinds of certificates that differ in what authority source the certificate employs: Self-signed certificate Generating a self-signed certificate does not involve any CA, because each certificate is signed using the certificate's own key. The software that is verifying a self-signed certificate needs to be instructed to trust that certificates directly in order to verify it. To obtain a self-signed certificate, run the selfsign-getcert command. Certificate from the Dogtag Certificate System CA as part of Red Hat Enterprise Linux IdM To obtain a certificate using an IdM server, run the ipa-getcert command Certificate signed by a local CA present on the system The software that is verifying a certificate signed by a local signer needs to be instructed to trust certificates from this local signer in order to verify them. To obtain a locally-signed certificate, run the local-getcert command. Other CAs can also use certmonger to manage certificates, but support must be added to certmonger by creating special CA helpers . For more information on how to create CA helpers, see the certmonger project documentation at https://pagure.io/certmonger/blob/master/f/doc/submit.txt .

Commands:
Chapter 7. Templates and Pools 7.1. Templates and Pools The Red Hat Virtualization environment provides administrators with tools to simplify the provisioning of virtual machines to users. These are templates and pools. A template is a shortcut that allows an administrator to quickly create a new virtual machine based on an existing, pre-configured virtual machine, bypassing operating system installation and configuration. This is especially helpful for virtual machines that will be used like appliances, for example web server virtual machines. If an organization uses many instances of a particular web server, an administrator can create a virtual machine that will be used as a template, installing an operating system, the web server, any supporting packages, and applying unique configuration changes. The administrator can then create a template based on the working virtual machine that will be used to create new, identical virtual machines as they are required. Virtual machine pools are groups of virtual machines based on a given template that can be rapidly provisioned to users. Permission to use virtual machines in a pool is granted at the pool level; a user who is granted permission to use the pool will be assigned any virtual machine from the pool. Inherent in a virtual machine pool is the transitory nature of the virtual machines within it. Because users are assigned virtual machines without regard for which virtual machine in the pool they have used in the past, pools are not suited for purposes which require data persistence. Virtual machine pools are best suited for scenarios where either user data is stored in a central location and the virtual machine is a means to accessing and using that data, or data persistence is not important. The creation of a pool results in the creation of the virtual machines that populate the pool, in a stopped state. These are then started on user request.

Commands:
Chapter 11. Swap Space 11.1. What is Swap Space? Swap space in Linux is used when the amount of physical memory (RAM) is full. If the system needs more memory resources and the RAM is full, inactive pages in memory are moved to the swap space. While swap space can help machines with a small amount of RAM, it should not be considered a replacement for more RAM. Swap space is located on hard drives, which have a slower access time than physical memory. Swap space can be a dedicated swap partition (recommended), a swap file, or a combination of swap partitions and swap files. The size of your swap should be equal to twice your computer's physical RAM for up to 2 GB of physical RAM. For physical RAM above 2 GB, the size of your swap should be equal to the amount of physical RAM above 2 GB. The size of your swap should never be less than 32 MB. Using this basic formula, a system with 2 GB of physical RAM would have 4 GB of swap, while one with 3 GB of physical RAM would have 5 GB of swap. Note Unfortunately, deciding on the amount of swap to allocate to Red Hat Enterprise Linux is more of an art than a science, so hard rules are not possible. Each system's most used applications should be accounted for when determining swap size. Important File systems and LVM2 volumes assigned as swap space cannot be in use when being modified. For example, no system processes can be assigned the swap space, as well as no amount of swap should be allocated and used by the kernel. Use the free and cat /proc/swaps commands to verify how much and where swap is in use. The best way to achieve swap space modifications is to boot your system in rescue mode, and then follow the instructions (for each scenario) in the remainder of this chapter. Refer to Chapter 5, Basic System Recovery for instructions on booting into rescue mode. When prompted to mount the file system, select Skip .

Commands:
Chapter 9. 4.6 Release Notes 9.1. New Features This following major enhancements have been introduced in Red Hat Update Infrastructure 4.6. New Pulp version: 3.28 This update introduces a newer version of Pulp, 3.28, the latest LTS version. This update significantly modifies the Pulp database model, addressing many of the deadlock issues RHUI encountered when synchronizing large content volumes simultaneously. Redis is no longer included Redis is no longer included as part of the Pulp installation. Shared mount options for RHUI Installer have been enhanced With this update, the RHUI Installer's shared storage mounting options have been enhanced. You can now use the force option to alter the remote storage. For more information, see rhui-installer --help . rhui-manager status now includes CDS SSL certificate expiration checks With this update, CDS NGinx SSL certificate expiration checks are now available in the rhui-manager status report. RHUI Installer automatically initiates rhui-subscription-sync With this update, RHUI Installer automatically initiates rhui-subscription-sync after a successful installation. You no longer need to manually initiate the syncronization. 9.2. Bug Fixes The following bugs have been fixed in Red Hat Update Infrastructure 4.6 that have a significant impact on users. RHUI avoids not recognizing new RHEL minor version repositories Previously, RHUI failed to recognize new minor version RHEL repositories because of cached mappings. With this update, the issue has been fixed. Special characters can be used in the admin password Previosuly, you could not use certain special characters in the RHUI administrator password. With this update, the issue has been fixed. RHUI Installer did not handle rhui_active_login_file Previously, due to a problem in RHUI Installer, it failed to successfully process the rhui_active_login_file variable. With this update, the issue has been fixed.

Commands:
24.6. Monitoring Performance with Net-SNMP Red Hat Enterprise Linux 6 includes the Net-SNMP software suite, which includes a flexible and extensible Simple Network Management Protocol ( SNMP ) agent. This agent and its associated utilities can be used to provide performance data from a large number of systems to a variety of tools which support polling over the SNMP protocol. This section provides information on configuring the Net-SNMP agent to securely provide performance data over the network, retrieving the data using the SNMP protocol, and extending the SNMP agent to provide custom performance metrics. 24.6.1. Installing Net-SNMP The Net-SNMP software suite is available as a set of RPM packages in the Red Hat Enterprise Linux software distribution. Table 24.2, "Available Net-SNMP packages" summarizes each of the packages and their contents. Table 24.2. Available Net-SNMP packages Package Provides net-snmp The SNMP Agent Daemon and documentation. This package is required for exporting performance data. net-snmp-libs The netsnmp library and the bundled management information bases (MIBs). This package is required for exporting performance data. net-snmp-utils SNMP clients such as snmpget and snmpwalk . This package is required in order to query a system's performance data over SNMP. net-snmp-perl The mib2c utility and the NetSNMP Perl module. net-snmp-python An SNMP client library for Python. To install any of these packages, use the yum command in the following form: yum install package For example, to install the SNMP Agent Daemon and SNMP clients used in the rest of this section, type the following at a shell prompt: Note that you must have superuser privileges (that is, you must be logged in as root ) to run this command. For more information on how to install new packages in Red Hat Enterprise Linux, see Section 8.2.4, "Installing Packages" .

Commands:
~]# yum install net-snmp net-snmp-libs net-snmp-utils
7.2. Migrate from Synchronization to Trust Manually Using ID Views You can use ID views to manually change the POSIX attributes that AD previously generated for AD users. Create a backup of the original synchronized user or group entries. Create a trust with the synchronized domain. For information about creating trusts, see Chapter 5, Creating Cross-forest Trusts with Active Directory and Identity Management . For every synchronized user or group, preserve the UID and GIDs generated by IdM by doing one of the following: Individually create an ID view applied to the specific host and add user ID overrides to the view. Create user ID overrides in the Default Trust View. For details, see Defining a Different Attribute Value for a User Account on Different Hosts . Note Only IdM users can manage ID views. AD users cannot. Delete the original synchronized user or group entries. For general information on using ID views in Active Directory environments, see Chapter 8, Using ID Views in Active Directory Environments .

Commands: