mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Preparing to install on IBM Power 1.1. Prerequisites You reviewed details about the OpenShift Container Platform installation and update processes. You read the documentation on selecting a cluster installation method and preparing it for users . 1.2. Choosing a method to install OpenShift Container Platform on IBM Power You can install a cluster on IBM Power infrastructure that you provision, by using one of the following methods: Installing a cluster on IBM Power : You can install OpenShift Container Platform on IBM Power infrastructure that you provision. Installing a cluster on IBM Power in a restricted network : You can install OpenShift Container Platform on IBM Power infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.

Commands:
1.8. Making the Kickstart File Available A kickstart file must be placed in one of the following locations: On a boot diskette On a boot CD-ROM On a network Normally a kickstart file is copied to the boot diskette, or made available on the network. The network-based approach is most commonly used, as most kickstart installations tend to be performed on networked computers. Let us take a more in-depth look at where the kickstart file may be placed. 1.8.1. Creating Kickstart Boot Media Diskette-based booting is no longer supported in Red Hat Enterprise Linux. Installations must use CD-ROM or flash memory products for booting. However, the kickstart file may still reside on a diskette's top-level directory, and must be named ks.cfg . To perform a CD-ROM-based kickstart installation, the kickstart file must be named ks.cfg and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to the Installation Guide for instructions on creating boot media; however, before making the file.iso image file, copy the ks.cfg kickstart file to the isolinux/ directory. To perform a pen-based flash memory kickstart installation, the kickstart file must be named ks.cfg and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the ks.cfg file. For example, the following transfers a boot image to the pen drive ( /dev/sda ) using the dd command: Note Creation of USB flash memory pen drives for booting is possible, but is heavily dependent on system hardware BIOS settings. Refer to your hardware manufacturer to see if your system supports booting to alternate devices.

Commands:
dd if=diskboot.img of=/dev/sda bs=1M
7.5. Replacing a Missing Physical Volume If a physical volume fails or otherwise needs to be replaced, you can label a new physical volume to replace the one that has been lost in the existing volume group by following the same procedure as you would for recovering physical volume metadata, described in Section 7.4, "Recovering Physical Volume Metadata" . You can use the --partial and --verbose arguments of the vgdisplay command to display the UUIDs and sizes of any physical volumes that are no longer present. If you wish to substitute another physical volume of the same size, you can use the pvcreate command with the --restorefile and --uuid arguments to initialize a new device with the same UUID as the missing physical volume. You can then use the vgcfgrestore command to restore the volume group's metadata.

Commands:
39.5. Additional Resources To learn more about gathering system information, refer to the following resources. 39.5.1. Installed Documentation ps --help - Displays a list of options that can be used with ps . top manual page - Type man top to learn more about top and its many options. free manual page - type man free to learn more about free and its many options. df manual page - Type man df to learn more about the df command and its many options. du manual page - Type man du to learn more about the du command and its many options. lspci manual page - Type man lspci to learn more about the lspci command and its many options. /proc/ directory - The contents of the /proc/ directory can also be used to gather more detailed system information.

Commands:
Chapter 7. Evaluating and testing policies When designing your policies, you can simulate authorization requests to test how your policies are being evaluated. You can access the Policy Evaluation Tool by clicking the Evaluate tab when editing a resource server. There you can specify different inputs to simulate real authorization requests and test the effect of your policies. Policy evaluation tool 7.1. Providing identity information The Identity Information filters can be used to specify the user requesting permissions. 7.2. Providing contextual information The Contextual Information filters can be used to define additional attributes to the evaluation context, so that policies can obtain these same attributes. 7.3. Providing the permissions The Permissions filters can be used to build an authorization request. You can request permissions for a set of one or more resources and scopes. If you want to simulate authorization requests based on all protected resources and scopes, click Add without specifying any Resources or Scopes . When you've specified your desired values, click Evaluate .

Commands:
13.4. Exposing Automount Maps to NIS Clients When the NIS service is enabled on a system, the IdM server is automatically configured to set the NIS domain to the IdM domain's name, and to include IdM users, groups, and netgroups as passwd, group, and netgroup maps in the NIS domain. If any automount maps are already defined, these maps need to be manually added to the NIS configuration in Identity Management for them to be exposed to NIS clients. The NIS server is managed by a special plug-in entry in the IdM LDAP directory; this is a container entry, and each NIS domain and map used by the NIS server is configured as a child entry beneath that container. The NIS domain entry in the must have the name of the NIS domain, the name of the NIS map, how to find the directory entries to use as the NIS map's contents, and which attributes to use as the NIS map's key and value. Most of these settings will be the same for every map. The IdM server stores the automount maps, grouped by automount location, in the cn=automount branch of the IdM directory tree. The NIS domain and map is added using LDAP tools, like ldapadd , and editing the directory directly. For example, this adds an automount map that is named auto.example in a location named default and for a server named nisserver : A similar add operation needs to be run for every map that is configured.

Commands:
ldapadd -h nisserver.example.com -x -D "cn=Directory Manager" -w secret dn: nis-domain=example.com+nis-map=auto.example,cn=NIS Server,cn=plugins,cn=config objectClass: extensibleObject nis-domain: example.com nis-map: auto.example nis-filter: (objectclass=automount) nis-key-format: %{automountKey} nis-value-format: %{automountInformation} nis-base: automountmapname=auto.example,cn=default,cn=automount,dc=example,dc=com
9.3. Disk Usage Considerations Although, you can find information about all JBoss Data Virtualization settings using the Management CLI (see Section 10.1, "JBoss Data Virtualization Settings" ), this section provides some additional information about those settings related to disk usage. buffer-service-max-buffer-space Default is 51200. For table page and result batches, the buffer manager will limit the number of files that are dedicated to a particular storage size. However, creation of Large Object (LOB) values (for example through SQL/XML) will typically create one file per LOB once the LOB exceeds the allowable in memory size of 8KB. In heavy usage scenarios, consider pointing the buffer directory on a partition that is routinely defragmented. By default, JBoss Data Virtualization will use up to 50GB of disk space. This is tracked in terms of the number of bytes written by JBoss Data Virtualization. For large data sets, you may need to increase the buffer-service-max-buffer-space property.

Commands:
24.4. Server Settings The Server tab allows you to configure basic server settings. The default settings for these options are appropriate for most situations. Figure 24.10. Server Configuration The Lock File value corresponds to the LockFile directive. This directive sets the path to the lockfile used when the server is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or USE_FLOCK_SERIALIZED_ACCEPT. It must be stored on the local disk. It should be left to the default value unless the logs directory is located on an NFS share. If this is the case, the default value should be changed to a location on the local disk and to a directory that is readable only by root. The PID File value corresponds to the PidFile directive. This directive sets the file in which the server records its process ID (pid). This file should only be readable by root. In most cases, it should be left to the default value. The Core Dump Directory value corresponds to the CoreDumpDirectory directive. The Apache HTTP Server tries to switch to this directory before executing a core dump. The default value is the ServerRoot . However, if the user that the server runs as can not write to this directory, the core dump can not be written. Change this value to a directory writable by the user the server runs as, if you want to write the core dumps to disk for debugging purposes. The User value corresponds to the User directive. It sets the userid used by the server to answer requests. This user's settings determine the server's access. Any files inaccessible to this user are also inaccessible to your website's visitors. The default for User is apache. The user should only have privileges so that it can access files which are supposed to be visible to the outside world. The user is also the owner of any CGI processes spawned by the server. The user should not be allowed to execute any code which is not intended to be in response to HTTP requests. Warning Unless you know exactly what you are doing, do not set the User directive to root. Using root as the User creates large security holes for your Web server. The parent httpd process first runs as root during normal operations, but is then immediately handed off to the apache user. The server must start as root because it needs to bind to a port below 1024. Ports below 1024 are reserved for system use, so they can not be used by anyone but root. Once the server has attached itself to its port, however, it hands the process off to the apache user before it accepts any connection requests. The Group value corresponds to the Group directive. The Group directive is similar to the User directive. Group sets the group under which the server answers requests. The default group is also apache.

Commands:
Chapter 15. complete.adoc This chapter describes the commands under the complete.adoc command. 15.1. complete print bash completion command Usage: Table 15.1. Command arguments Value Summary -h, --help Show this help message and exit --name <command_name> Command name to support with command completion --shell <shell> Shell being used. use none for data only (default: bash)

Commands:
openstack complete [-h] [--name <command_name>] [--shell <shell>]
Chapter 1. Preface You can use the Red Hat High Availability Add-On to configure a Red Hat High Availability (HA) cluster on Red Hat OpenStack Platform (RHOSP) instances. This requires that you install the required packages and agents, configure a basic cluster, configure fencing resources, and configure HA cluster resources. For RHOSP documentation, see Product Documentation for Red Hat Openstack Platform . For Red Hat's policies, requirements, and limitations applicable to the use of RHOSP instances in a RHEL High Availability cluster, see Support Policies for RHEL High Availability Clusters - OpenStack Virtual Machines as Cluster Members - Red Hat Customer Portal .

Commands:
Chapter 11. Viewing and managing Quartz Schedules Quartz ( http://www.quartz-scheduler.org/ ) is a richly featured, open source job scheduling library that you can integrate within most Java applications. You can use Quartz to create simple or complex schedules for executing jobs. A job is defined as a standard Java component that can execute virtually anything that you program it to do. The Fuse Console shows the Quartz tab if your Camel route deploys the camel-quartz2 component. Note that you can alternately access Quartz mbeans through the JMX tree view. Procedure In the Fuse Console, click the Quartz tab. The Quartz page includes a treeview of the Quartz Schedulers and Scheduler , Triggers , and Jobs tabs. To pause or start a scheduler, click the buttons on the Scheduler tab. Click the Triggers tab to view the triggers that determine when jobs will run. For example, a trigger can specify to start a job at a certain time of day (to the millisecond), on specified days, or repeated a specified number of times or at specific times. To filter the list of triggers select State , Group , Name , or Type from the drop-down list. You can then further filter the list by selecting or typing in the fill-on field. To pause, resume, update, or manually fire a trigger, click the options in the Action column. Click the Jobs tab to view the list of running jobs. You can sort the list by the columns in the table: Group , Name , Durable , Recover , Job ClassName , and Description .

Commands:
Chapter 44. ip This chapter describes the commands under the ip command. 44.1. ip availability list List IP availability for network Usage: Table 44.1. Optional Arguments Value Summary -h, --help Show this help message and exit --ip-version <ip-version> List ip availability of given ip version networks (default is 4) --project <project> List ip availability of given project (name or id) --project-domain <project-domain> Domain the project belongs to (name or id). this can be used in case collisions between project names exist. Table 44.2. Output Formatters 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 44.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 44.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 44.5. Table Formatter 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. 44.2. ip availability show Show network IP availability details Usage: Table 44.6. Positional Arguments Value Summary <network> Show ip availability for a specific network (name or ID) Table 44.7. Optional Arguments Value Summary -h, --help Show this help message and exit Table 44.8. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 44.9. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 44.10. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 44.11. Table Formatter 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 ip availability 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] [--ip-version <ip-version>] [--project <project>] [--project-domain <project-domain>]
openstack ip availability show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] <network>
3.5. Notes on UEFI Support 3.5.1. Feature Support Red Hat Enterprise Linux 6.9 supports both BIOS and UEFI firmware on AMD64 and Intel 64 systems (x86_64). UEFI-based systems are supported with the following limitations: The system must support UEFI Specification 2.0 or later. Earlier revisions are not supported. The Secure Boot technology is not supported, and will prevent Red Hat Enterprise Linux from being installed. Systems using UEFI Specification 2.2 or later must have Secure Boot disabled in order to install and run Red Hat Enterprise Linux 6.9. Systems using UEFI 2.0 later with Secure Boot disabled (if present) can install and boot Red Hat Enterprise Linux without issues, although not all features in the relevant UEFI specification are supported. For more information about UEFI specifications, see http://www.uefi.org/specifications .

Commands:
20.44. Disk I/O Throttling The virsh blkdeviotune command sets disk I/O throttling for a specified guest virtual machine. This can prevent a guest virtual machine from over utilizing shared resources and thus impacting the performance of other guest virtual machines. The following format should be used: The only required parameter is the domain name of the guest virtual machine. To list the domain name, run the virsh domblklist command. The --config , --live , and --current arguments function the same as in Section 20.43, "Setting Schedule Parameters" . If no limit is specified, it will query current I/O limits setting. Otherwise, alter the limits with the following flags: --total-bytes-sec - specifies total throughput limit in bytes per second. --read-bytes-sec - specifies read throughput limit in bytes per second. --write-bytes-sec - specifies write throughput limit in bytes per second. --total-iops-sec - specifies total I/O operations limit per second. --read-iops-sec - specifies read I/O operations limit per second. --write-iops-sec - specifies write I/O operations limit per second. For more information, see the blkdeviotune section of the virsh man page. For an example domain XML see Figure 23.27, "Devices - Hard drives, floppy disks, CD-ROMs Example" .

Commands:
virsh blkdeviotune domain < device > [[--config] [--live] | [--current]] [[total-bytes-sec] | [read-bytes-sec] [write-bytes-sec]] [[total-iops-sec] [read-iops-sec] [write-iops-sec]]
Preface Open Java Development Kit (OpenJDK) is a free and open-source implementation of the Java Platform, Standard Edition (Java SE). Eclipse Temurin is available in three LTS versions: OpenJDK 8u, OpenJDK 11u, and OpenJDK 17u. Binaries for Eclipse Temurin are available for macOS, Microsoft Windows, and on multiple Linux x86 Operating Systems including Red Hat Enterprise Linux and Ubuntu.

Commands:
Preface For OpenShift Data Foundation, node replacement can be performed proactively for an operational node and reactively for a failed node for the following deployments: For Amazon Web Services (AWS) User-provisioned infrastructure Installer-provisioned infrastructure For VMware User-provisioned infrastructure Installer-provisioned infrastructure For Red Hat Virtualization Installer-provisioned infrastructure For Microsoft Azure Installer-provisioned infrastructure For local storage devices Bare metal VMware Red Hat Virtualization IBM Power For replacing your storage nodes in external mode, see Red Hat Ceph Storage documentation .

Commands:
Chapter 3. Opening a new certification case by using the Red Hat Certification portal Prerequisites You have established a certification relationship with Red Hat. You have the user login credentials. You have the vendor and products linked to your user login. Procedure Log in to Red Hat Certification Portal . On the homepage, click Open Certification . A new window will display. Click . Select the Partner from the drop-down list. On the Product drop-down list, select your product name. If your product does not appear, create it by entering its name in the Product field. Then, select it. In the What kind of product is this? section, select the checkbox applicable to your product. Your product might qualify for more than one ecosystem. Click . Enter the Make . The Model appears automatically based on the inputs. Select the applicable checkbox under Which category best describes your product? Optional: Enter the Product URL . Optional: Enter the Support URL . Optional: Enter the Specification URL . Click . A new product gets created based on the inputs you provided in the steps. The Partner Product appears by default based on the inputs in the steps. Select Red Hat Certification from the drop-down list, and click . Review the information you provided and click Open . Verification A message displays that a new certification case for your product is created. steps Red Hat will prepare your test plan based on the product specification you provided. In the meantime, see Chapter 4, Setting up the test environment to prepare the systems for running tests.

Commands:
1.6. Cluster Logical Volume Manager The Cluster Logical Volume Manager (CLVM) provides a cluster-wide version of LVM2. CLVM provides the same capabilities as LVM2 on a single node, but makes the volumes available to all nodes in a Red Hat cluster. The logical volumes created with CLVM make logical volumes available to all nodes in a cluster. The key component in CLVM is clvmd . clvmd is a daemon that provides clustering extensions to the standard LVM2 tool set and allows LVM2 commands to manage shared storage. clvmd runs in each cluster node and distributes LVM metadata updates in a cluster, thereby presenting each cluster node with the same view of the logical volumes (refer to Figure 1.15, "CLVM Overview" ). Logical volumes created with CLVM on shared storage are visible to all nodes that have access to the shared storage. CLVM allows a user to configure logical volumes on shared storage by locking access to physical storage while a logical volume is being configured. CLVM uses the lock-management service provided by the cluster infrastructure (refer to Section 1.3, "Cluster Infrastructure" ). Note Shared storage for use in Red Hat Cluster Suite requires that you be running the cluster logical volume manager daemon ( clvmd ) or the High Availability Logical Volume Management agents (HA-LVM). If you are not able to use either the clvmd daemon or HA-LVM for operational reasons or because you do not have the correct entitlements, you must not use single-instance LVM on the shared disk as this may result in data corruption. If you have any concerns please contact your Red Hat service representative. Note Using CLVM requires minor changes to /etc/lvm/lvm.conf for cluster-wide locking. Figure 1.15. CLVM Overview You can configure CLVM using the same commands as LVM2, using the LVM graphical user interface (refer to Figure 1.16, "LVM Graphical User Interface" ), or using the storage configuration function of the Conga cluster configuration graphical user interface (refer to Figure 1.17, "Conga LVM Graphical User Interface" ) . Figure 1.18, "Creating Logical Volumes" shows the basic concept of creating logical volumes from Linux partitions and shows the commands used to create logical volumes. Figure 1.16. LVM Graphical User Interface Figure 1.17. Conga LVM Graphical User Interface Figure 1.18. Creating Logical Volumes

Commands: