mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. PolicyKit The PolicyKit utility is a framework that provides an authorization API used by privileged programs (also called mechanisms ) offering services to unprivileged programs (also called subjects ). The following are details on the changes PolicyKit , or its system name polkit , has undergone. 4.1. Policy Configuration As far as the new features are concerned, authorization rules are now defined in JavaScript .rules files. This means that the same files are used for defining both the rules and the administrator status. Previously, this information was stored in two different file types - *.pkla and *.conf , which used key/value pairs to define additional local authorizations. These new .rules files are stored in two locations; whereas polkit rules for local customization are stored in the /etc/polkit-1/rules.d/ directory, the third party packages are stored in /usr/share/polkit-1/rules.d/ . The existing .conf and .pkla configuration files have been preserved and exist side by side with .rules files. polkit has been upgraded for Red Hat Enterprise Linux 7 with the compatibility issue in mind. The logic in precedence in rules has changed. polkitd now reads .rules files in lexicographic order from the /etc/polkit-1/rules.d and /usr/share/polkit-1/rules.d directories. If two files are named identically, files in /etc are processed before files in /usr . In addition, existing rules are applied by the /etc/polkit-1/rules.d/49-polkit-pkla-compat.rules file. They can therefore be overridden by .rules files in either /usr or /etc with a name that comes before 49-polkit-pkla-compat in lexicographic order. The simplest way to ensure that your old rules are not overridden is to begin the name of all other .rules files with a number higher than 49. Here is an example of a .rules file. It creates a rule that allows mounting a file system on a system device for the storage group. The rule is stored in the /etc/polkit-1/rules.d/10-enable-mount.rules file: Example 4.1. Allow Mounting a File system on a System device polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.udisks2.filesystem-mount-system" && subject.isInGroup("storage")) { return polkit.Result.YES; } }); For more information, see: polkit (8) - The man page for the description of the JavaScript rules and the precedence rules. pkla-admin-identities (8) and pkla-check-authorization (8) - The man pages for documentation of the .conf and .pkla file formats, respectively.

Commands:
polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.udisks2.filesystem-mount-system" && subject.isInGroup("storage")) { return polkit.Result.YES; } });
Chapter 5. Creating a basic cluster on Red Hat OpenStack Platform This procedure creates a high availability cluster on an RHOSP platform with no fencing or resources configured. Prerequisites An RHOSP instance is configured for each HA cluster node The HA cluster node is running RHEL 8.7 or later High Availability and RHOSP packages are installed on each node, as described in Installing the high availability and RHOSP packages and agents . Procedure On one of the cluster nodes, enter the following command to authenticate the pcs user hacluster . Specify the name of each node in the cluster. In this example, the nodes for the cluster are node01 , node02 , and node03 . Create the cluster. In this example, the cluster is named newcluster . Verification Enable the cluster. Start the cluster. The command's output indicates whether the cluster has started on each node.

Commands:
pcs host auth node01 node02 node03 Username: hacluster Password: node01: Authorized node02: Authorized node03: Authorized
pcs cluster setup newcluster node01 node02 node03 Synchronizing pcsd certificates on nodes node01, node02, node03... node02: Success node03: Success node01: Success Restarting pcsd on the nodes in order to reload the certificates... node02: Success node03: Success node01: Success
pcs cluster enable --all node01: Cluster Enabled node02: Cluster Enabled node03: Cluster Enabled
pcs cluster start --all node02: Starting Cluster... node03: Starting Cluster... node01: Starting Cluster
1.5. Devices Brocade BFA driver The Brocade BFA driver is considered a Technology Preview feature in Red Hat Enterprise Linux 6. The BFA driver supports Brocade FibreChannel and FCoE mass storage adapters. SR-IOV on the be2net driver, BZ# 602451 The SR-IOV functionality of the Emulex be2net driver is considered a Technology Preview in Red Hat Enterprise Linux 6.

Commands:
4.14. RHEA-2012:0868 - new packages: libwacom New libwacom packages are now available for Red Hat Enterprise Linux 6. The libwacom packages contain a library that provides access to a tablet model database. The libwacom packages expose the contents of this database to applications, allowing for tablet-specific user interfaces. The libwacom packages allow the GNOME tools to automatically configure screen mappings, calibrations, and provide device-specific configurations. This enhancement update adds the libwacom packages to Red Hat Enterprise Linux 6. (BZ# 786100 ) All users who require libwacom should install these new packages.

Commands:
Chapter 13. Troubleshooting builds Use the following to troubleshoot build issues. 13.1. Resolving denial for access to resources If your request for access to resources is denied: Issue A build fails with: requested access to the resource is denied Resolution You have exceeded one of the image quotas set on your project. Check your current quota and verify the limits applied and storage in use: USD oc describe quota 13.2. Service certificate generation failure If your request for access to resources is denied: Issue If a service certificate generation fails with (service's service.beta.openshift.io/serving-cert-generation-error annotation contains): Example output secret/ssl-key references serviceUID 62ad25ca-d703-11e6-9d6f-0e9c0057b608, which does not match 77b6dd80-d716-11e6-9d6f-0e9c0057b60 Resolution The service that generated the certificate no longer exists, or has a different serviceUID . You must force certificates regeneration by removing the old secret, and clearing the following annotations on the service: service.beta.openshift.io/serving-cert-generation-error and service.beta.openshift.io/serving-cert-generation-error-num : USD oc delete secret <secret_name> USD oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error- USD oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-num- Note The command removing annotation has a - after the annotation name to be removed.

Commands:
requested access to the resource is denied
oc describe quota
secret/ssl-key references serviceUID 62ad25ca-d703-11e6-9d6f-0e9c0057b608, which does not match 77b6dd80-d716-11e6-9d6f-0e9c0057b60
oc delete secret <secret_name>
oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-
oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-num-
4.77. gnome-system-monitor 4.77.1. RHEA-2011:1612 - gnome-system-monitor enhancement update An enhanced gnome-system-monitor package that provides an enhancement is now available for Red Hat Enterprise Linux 6. The gnome-system-monitor package contains a tool which allows to graphically view and manipulate the running processes on the system. It also provides an overview of available resources such as CPU and memory. Enhancement BZ# 571597 Previously, the CPU History graph could be hard to read if it displayed large numbers of CPUs. This update modifies the design: scrollbars were added for easier manipulation of the window and random color is now generated to each CPU. Users of gnome-system-monitor are advised to upgrade to this updated package, which adds this enhancement.

Commands:
Part I. Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 4 using Operators As a system engineer, you can deploy a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 4 to provide an infrastructure to develop or execute services, process applications, and other business assets. You can use OpenShift Operators to deploy the environment defined in a structured YAML file and to maintain and modify this environment as necessary. Prerequisites A Red Hat OpenShift Container Platform 4 environment is available. For the exact versions of Red Hat OpenShift Container Platform that the current release supports, see Red Hat Process Automation Manager 7 Supported Configurations . The OpenShift project for the deployment is created. You are logged into the project using the OpenShift web console. The following resources are available on the OpenShift cluster. Depending on the application load, higher resource allocation might be necessary for acceptable performance. For an authoring environment, 4 gigabytes of memory and 2 virtual CPU cores for the Business Central pod. In a high-availability deployment, these resources are required for each replica and two replicas are created by default. For a production or immutable environment, 2 gigabytes of memory and 1 virtual CPU core for each replica of the Business Central Monitoring pod. 2 gigabytes of memory and 1 virtual CPU core for each replica of each KIE Server pod. 1 gigabyte of memory and half a virtual CPU core for each replica of a Smart Router pod. In a high-availability authoring deployment, additional resources according to the configured defaults are required for the MySQL, Red Hat AMQ, and Red Hat Data Grid pods. Note The default values for MaxMetaspaceSize are: Business Central images: 1024m KIE Server images: 512m For other images: 256m Dynamic persistent volume (PV) provisioning is enabled. Alternatively, if dynamic PV provisioning is not enabled, enough persistent volumes must be available. By default, the deployed components require the following PV sizes: Each KIE Server deployment by default requires one 1Gi PV for the database. You can change the database PV size. You can deploy multiple KIE Servers; each requires a separate database PV. This requirement does not apply if you use an external database server. By default, Business Central requires one 1Gi PV. You can change the PV size for Business Central persistent storage. Business Central Monitoring requires one 64Mi PV. Smart Router requires one 64Mi PV. If you intend to deploy a high-availability authoring environment or any environment with Business Central Monitoring pods, your OpenShift environment supports persistent volumes with ReadWriteMany mode. If your environment does not support this mode, you can use NFS to provision the volumes. For information about access mode support in OpenShift public and dedicated clouds, see Access Modes in Red Hat OpenShift Container Platform documentation.

Commands:
Chapter 6. Using custom rule categories You can create custom rule categories and assign MTR rules to them. Note Although MTR processes rules with the legacy severity field, you must update your custom rules to use the new category-id field. 6.1. Adding a custom category You can add a custom category to the rule category file. Procedure Edit the rule category file, which is located at <MTR_HOME>/rules/migration-core/core.windup.categories.xml . Add a new <category> element and fill in the following parameters: id : The ID that MTR rules use to reference the category. priority : The sorting priority relative to other categories. The category with the lowest value is displayed first. name : The display name of the category. description : The description of the category. Custom rule category example <?xml version="1.0"?> <categories> ... <category id="custom-category" priority="20000"> <name>Custom Category</name> <description>This is a custom category.</description> </category> </categories> This category is ready to be referenced by MTR rules. 6.2. Assigning a rule to a custom category You can assign a rule to your new custom category. Procedure In your MTR rule, update the category-id field as in the following example. <rule id="rule-id"> <when> ... </when> <perform> <hint title="Rule Title" effort="1" category-id="custom-category"> <message>Hint message.</message> </hint> </perform> </rule> If this rule condition is met, incidents identified by this rule use your custom category. The custom category is displayed on the dashboard and in the Issues report. Figure 6.1. Custom category on the dashboard

Commands:
<?xml version="1.0"?> <categories> <category id="custom-category" priority="20000"> <name>Custom Category</name> <description>This is a custom category.</description> </category> </categories>
<rule id="rule-id"> <when> </when> <perform> <hint title="Rule Title" effort="1" category-id="custom-category"> <message>Hint message.</message> </hint> </perform> </rule>
Chapter 3. Upgrading from RHEL 6.10 to RHEL 7.9 The in-place upgrade from RHEL 6 to RHEL 7 consists of two major stages, a pre-upgrade assessment of the system, and the actual in-place upgrade: In the pre-upgrade phase, the Preupgrade Assistant collects information from the system, analyzes it, and suggests possible corrective actions. The Preupgrade Assistant does not make any changes to your system. In the in-place upgrade phase, the Red Hat Upgrade Tool installs RHEL 7 packages and adjusts basic configuration where possible. To perform an in-place upgrade from RHEL 6 to RHEL 7: Assess the upgradability of your system using the Preupgrade Assistant, and fix problems identified in the report before you proceed with the upgrade. For detailed instructions, see the Assessing upgrade suitability section in the Upgrading from RHEL 6 to RHEL 7 documentation. Use the Red Hat Upgrade Tool to upgrade to RHEL 7.9. For a detailed procedure, see the Upgrading your system from RHEL 6 to RHEL 7 section in the Upgrading from RHEL 6 to RHEL 7 documentation.

Commands:
25.3. XML Representation of a Virtual Machine Creation Event In addition to user , an event representation also contains a set of XML element relationships to resources relevant to the event. Example 25.2. An XML representation of a virtual machine creation event This example representation provides XML element relationships to a virtual machine resource and a storage domain resource.

Commands:
<event id="635" href="/ovirt-engine/api/events/635"> <description>VM bar was created by rhevadmin.</description> <code>34</code> <severity>normal</severity> <time>2011-07-11T16:32:03.172+02:00</time> <user id="4621b611-43eb-4d2b-ae5f-1180850268c4" href="/ovirt-engine/api/users/4621b611-43eb-4d2b-ae5f-1180850268c4"/> <vm id="9b22d423-e16b-4dd8-9c06-c8e9358fbc66" href="/ovirt-engine/api/vms/9b22d423-e16b-4dd8-9c06-c8e9358fbc66"/> <storage_domain id="a8a0e93d-c570-45ab-9cd6-3c68ab31221f" href="/ovirt-engine/api/storagedomains/a8a0e93d-c570-45ab-9cd6-3c68ab31221f"/> </event>
Chapter 17. Workload partitioning in single-node OpenShift In resource-constrained environments, such as single-node OpenShift deployments, use workload partitioning to isolate OpenShift Container Platform services, cluster management workloads, and infrastructure pods to run on a reserved set of CPUs. The minimum number of reserved CPUs required for the cluster management in single-node OpenShift is four CPU Hyper-Threads (HTs). With workload partitioning, you annotate the set of cluster management pods and a set of typical add-on Operators for inclusion in the cluster management workload partition. These pods operate normally within the minimum size CPU configuration. Additional Operators or workloads outside of the set of minimum cluster management pods require additional CPUs to be added to the workload partition. Workload partitioning isolates user workloads from platform workloads using standard Kubernetes scheduling capabilities. The following is an overview of the configurations required for workload partitioning: Workload partitioning that uses /etc/crio/crio.conf.d/01-workload-partitioning pins the OpenShift Container Platform infrastructure pods to a defined cpuset configuration. The performance profile pins cluster services such as systemd and kubelet to the CPUs that are defined in the spec.cpu.reserved field. Note Using the Node Tuning Operator, you can configure the performance profile to also pin system-level apps for a complete workload partitioning configuration on the node. The CPUs that you specify in the performance profile spec.cpu.reserved field and the workload partitioning cpuset field must match. Workload partitioning introduces an extended <workload-type>.workload.openshift.io/cores resource for each defined CPU pool, or workload type . Kubelet advertises the resources and CPU requests by pods allocated to the pool within the corresponding resource. When workload partitioning is enabled, the <workload-type>.workload.openshift.io/cores resource allows access to the CPU capacity of the host, not just the default CPU pool. Additional resources For the recommended workload partitioning configuration for single-node OpenShift clusters, see Workload partitioning .

Commands:
Chapter 10. availability This chapter describes the commands under the availability command. 10.1. availability zone list List availability zones and their status Usage: Table 10.1. Command arguments Value Summary -h, --help Show this help message and exit --compute List compute availability zones --network List network availability zones --volume List volume availability zones --long List additional fields in output Table 10.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 10.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 10.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 10.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack availability zone list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--compute] [--network] [--volume] [--long]
2.2.10.2. Installation Perl's capabilities can be extended by installing additional modules. These modules come in the following forms: Official Red Hat RPM The official module packages can be installed with yum or rpm from the Red Hat Enterprise Linux repositories. They are installed to /usr/share/perl5 and either /usr/lib/perl5 for 32bit architectures or /usr/lib64/perl5 for 64bit architectures. Modules from CPAN Use the cpan tool provided by the perl-CPAN package to install modules directly from the CPAN website. They are installed to /usr/local/share/perl5 and either /usr/local/lib/perl5 for 32bit architectures or /usr/local/lib64/perl5 for 64bit architectures. Third party module package Third party modules are installed to /usr/share/perl5/vendor_perl and either /usr/lib/perl5/vendor_perl for 32bit architectures or /usr/lib64/perl5/vendor_perl for 64bit architectures. Custom module package / manually installed module These should be placed in the same directories as third-party modules. That is, /usr/share/perl5/vendor_perl and either /usr/lib/perl5/vendor_perl for 32bit architectures or /usr/lib64/perl5/vendor_perl for 64bit architectures. Warning If an official version of a module is already installed, installing its non-official version can create conflicts in the /usr/share/man directory.

Commands:
1.6. Kernel Support for Fiber Channel over Ethernet (FCoE) target mode Red Hat Enterprise Linux 6.2 includes support for Fiber Channel over Ethernet (FCoE) target mode as a Technology Preview . This kernel feature is configurable via targetadmin , supplied by the fcoe-target-utils package. FCoE is designed to be used on a network supporting Data Center Bridging (DCB). Further details are available in the dcbtool(8) and targetadmin(8) man pages. Important This feature uses the new SCSI target layer, which falls under this Technology Preview, and should not be used independently from the FCoE target support. This package contains the AGPL license. Kernel Media support The following features are presented as Technology Previews: The latest upstream video4linux Digital video broadcasting Primarily infrared remote control device support Various webcam support fixes and improvements Remote audit logging The audit package contains the user space utilities for storing and searching the audit records generated by the audit subsystem in the Linux 2.6 kernel. Within the audispd-plugins subpackage is a utility that allows for the transmission of audit events to a remote aggregating machine. This remote audit logging application, audisp-remote , is considered a Technology Preview in Red Hat Enterprise Linux 6. Linux (NameSpace) Container [LXC] Linux containers provide a flexible approach to application runtime containment on bare-metal systems without the need to fully virtualize the workload. Red Hat Enterprise Linux 6.2 provides application level containers to separate and control the application resource usage policies via cgroup and namespaces. This release introduces basic management of container life-cycle by allowing creation, editing and deletion of containers via the libvirt API and the virt-manager GUI. Linux Containers are a Technology Preview. Diagnostic pulse for the fence_ipmilan agent, BZ# 655764 A diagnostic pulse can now be issued on the IPMI interface using the fence_ipmilan agent. This new Technology Preview is used to force a kernel dump of a host if the host is configured to do so. Note that this feature is not a substitute for the off operation in a production cluster. EDAC driver support, BZ# 647700 Red Hat Enterprise Linux 6.2's EDAC driver support for the latest Intel chipset is available as a Technical Preview.

Commands: