mtpti5iD/redhat-docs_dataset huggingface dataset:
4.5.2. Configuring Fence Daemon Properties Clicking on the Fence Daemon tab displays the Fence Daemon Properties page, which provides an interface for configuring Post Fail Delay and Post Join Delay . The values you configure for these parameters are general fencing properties for the cluster. To configure specific fence devices for the nodes of the cluster, use the Fence Devices menu item of the cluster display, as described in Section 4.6, "Configuring Fence Devices" . The Post Fail Delay parameter is the number of seconds the fence daemon ( fenced ) waits before fencing a node (a member of the fence domain) after the node has failed. The Post Fail Delay default value is 0 . Its value may be varied to suit cluster and network performance. The Post Join Delay parameter is the number of seconds the fence daemon ( fenced ) waits before fencing a node after the node joins the fence domain. luci sets the Post Join Delay value to 6 . A typical setting for Post Join Delay is between 20 and 30 seconds, but can vary according to cluster and network performance. Enter the values required and click Apply for changes to take effect. Note For more information about Post Join Delay and Post Fail Delay , see the fenced (8) man page.

Commands:
REST API Guide Red Hat Virtualization 4.3 Using the Red Hat Virtualization REST Application Programming Interface Red Hat Virtualization Documentation Team rhev-docs@redhat.com Abstract This guide describes the Red Hat Virtualization Manager Representational State Transfer Application Programming Interface. This guide is generated from documentation comments in the ovirt-engine-api-model code, and is currently partially complete. Updated versions of this documentation will be published as new content becomes available.

Commands:
Chapter 150. StrimziPodSetStatus schema reference Used in: StrimziPodSet Property Description conditions List of status conditions. Condition array observedGeneration The generation of the CRD that was last reconciled by the operator. integer pods Number of pods managed by this StrimziPodSet resource. integer readyPods Number of pods managed by this StrimziPodSet resource that are ready. integer currentPods Number of pods managed by this StrimziPodSet resource that have the current revision. integer

Commands:
20.43. Setting Schedule Parameters The virsh schedinfo command modifies host scheduling parameters of the virtual machine process on the host machine. The following command format should be used: Each parameter is explained below: domain - the guest virtual machine domain --set - the string placed here is the controller or action that is to be called. The string uses the parameter = value format. Additional parameters or values if required should be added as well. --current - when used with --set , will use the specified set string as the current scheduler information. When used without will display the current scheduler information. --config - - when used with --set , will use the specified set string on the reboot. When used without will display the scheduler information that is saved in the configuration file. --live - when used with --set , will use the specified set string on a guest virtual machine that is currently running. When used without will display the configuration setting currently used by the running virtual machine The scheduler can be set with any of the following parameters: cpu_shares , vcpu_period and vcpu_quota . These parameters are applied to the vCPU threads. The following shows how the parameters map to cgroup field names: cpu_shares :cpu.shares vcpu_period :cpu.cfs_period_us vcpu_quota :cpu.cfs_quota_us Example 20.98. schedinfo show This example shows the shell guest virtual machine's schedule information Example 20.99. schedinfo set In this example, the cpu_shares is changed to 2046. This effects the current state and not the configuration file. libvirt also supports the emulator_period and emulator_quota parameters that modify the setting of the emulator process.

Commands:
virsh schedinfo domain --set --current --config --live
virsh schedinfo shell Scheduler : posix cpu_shares : 1024 vcpu_period : 100000 vcpu_quota : -1
virsh schedinfo --set cpu_shares=2046 shell Scheduler : posix cpu_shares : 2046 vcpu_period : 100000 vcpu_quota : -1
2.8.9.2.2. Command Options Command options instruct iptables to perform a specific action. Only one command option is allowed per iptables command. With the exception of the help command, all commands are written in upper-case characters. The iptables command options are as follows: -A - Appends the rule to the end of the specified chain. Unlike the -I option described below, it does not take an integer argument. It always appends the rule to the end of the specified chain. -D <integer> | <rule> - Deletes a rule in a particular chain by number (such as 5 for the fifth rule in a chain), or by rule specification. The rule specification must exactly match an existing rule. -E - Renames a user-defined chain. A user-defined chain is any chain other than the default, pre-existing chains. (Refer to the -N option, below, for information on creating user-defined chains.) This is a cosmetic change and does not affect the structure of the table. Note If you attempt to rename one of the default chains, the system reports a Match not found error. You cannot rename the default chains. -F - Flushes the selected chain, which effectively deletes every rule in the chain. If no chain is specified, this command flushes every rule from every chain. -h - Provides a list of command structures, as well as a quick summary of command parameters and options. -I [<integer>] - Inserts the rule in the specified chain at a point specified by a user-defined integer argument. If no argument is specified, the rule is inserted at the top of the chain. Important As noted above, the order of rules in a chain determines which rules apply to which packets. This is important to remember when adding rules using either the -A or -I option. This is especially important when adding rules using the -I with an integer argument. If you specify an existing number when adding a rule to a chain, iptables adds the new rule before (or above) the existing rule. -L - Lists all of the rules in the chain specified after the command. To list all rules in all chains in the default filter table, do not specify a chain or table. Otherwise, the following syntax should be used to list the rules in a specific chain in a particular table: iptables -L <chain-name> -t <table-name> Additional options for the -L command option, which provide rule numbers and allow more verbose rule descriptions, are described in Section 2.8.9.2.6, "Listing Options" . -N - Creates a new chain with a user-specified name. The chain name must be unique, otherwise an error message is displayed. -P - Sets the default policy for the specified chain, so that when packets traverse an entire chain without matching a rule, they are sent to the specified target, such as ACCEPT or DROP. -R - Replaces a rule in the specified chain. The rule's number must be specified after the chain's name. The first rule in a chain corresponds to rule number one. -X - Deletes a user-specified chain. You cannot delete a built-in chain. -Z - Sets the byte and packet counters in all chains for a table to zero.

Commands:
8.100. java-1.6.0-openjdk 8.100.1. RHBA-2014:1527 - java-1.6.0-openjdk bug fix and enhancement update Updated java-1.6.0-openjdk packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The java-1.6.0-openjdk packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Java Software Development Kit. Bug Fixes BZ# 1112806 A bug previously caused the LineBreakMeasurer class to produce the ArrayIndexOutOfBoundsException error when Java attempted to display certain characters in certain fonts. This update fixes the bug and Java now displays the affected characters correctly. BZ# 1098399 Prior to this update, an application accessing an unsynchronized HashMap could potentially enter an infinite loop and consume an excessive amount of CPU resources. As a consequence, the OpenJDK server became unresponsive. This update prevents unsynchronized HashMap access from causing an infinite loop and as a result, the OpenJDK server no longer hangs in the described scenario. In addition, this update adds the following Enhancement BZ# 1059925 Shared Java libraries have been modified to allow users to run Java with the cap_net_bind_service, cap_net_admin, and cap_net_raw capabilities granted. Users of java-1.6.0-openjdk are advised to upgrade to these updated packages, which fix these bugs. All running instances of OpenJDK Java must be restarted for the update to take effect.

Commands:
4.4. GFS2 File System Does Not Mount on Newly Added Cluster Node If you add a new node to a cluster and find that you cannot mount your GFS2 file system on that node, you may have fewer journals on the GFS2 file system than nodes attempting to access the GFS2 file system. You must have one journal per GFS2 host you intend to mount the file system on (with the exception of GFS2 file systems mounted with the spectator mount option set, since these do not require a journal). You can add journals to a GFS2 file system with the gfs2_jadd command, as described in Section 3.6, "Adding Journals to a GFS2 File System" .

Commands:
2.3. Text-Based Installer The text-mode installation option in Red Hat Enterprise Linux 6 is significantly more streamlined than it was in earlier versions. Text-mode installation now omits the more complicated steps that were previously part of the process, and provides you with an uncluttered and straightforward experience. This section describes the changes in behavior when using the text-based installer: Anaconda now automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. Anaconda still presents you with the initial screen from versions that allows you to specify where Anaconda will install Red Hat Enterprise Linux on your system. You can choose to use a whole drive, to remove existing Linux partitions, or to use the free space on the drive. However, Anaconda now automatically sets the layout of the partitions and does not ask you to add or delete partitions or file systems from this basic layout. If you require a customized layout at installation time, you must perform a graphical installation over a VNC connection or a Kickstart installation. More advanced options, such as logical volume management (LVM), encrypted filesystems, and resizable filesystems are still only available in graphical mode and Kickstart. Refer to the Red Hat Enterprise Linux Installation Guide for more information on performing a graphical (VNC) installation. Anaconda now performs boot loader configuration automatically in the text-based installer. Text-mode installations using Kickstart are carried out in the same way that they were in versions. However, because package selection, advanced partitioning, and boot loader configuration are now automated in text mode, Anaconda cannot prompt you for information that it requires during these steps. You must therefore ensure that the Kickstart file includes the packaging, partitioning, and boot loader configurations. If any of this information is missing, Anaconda will exit with an error message.

Commands:
Chapter 1. OpenShift Dedicated CLI tools overview A user performs a range of operations while working on OpenShift Dedicated such as the following: Managing clusters Building, deploying, and managing applications Managing deployment processes Developing Operators Creating and maintaining Operator catalogs OpenShift Dedicated offers a set of command-line interface (CLI) tools that simplify these tasks by enabling users to perform various administration and development operations from the terminal. These tools expose simple commands to manage the applications, as well as interact with each component of the system. 1.1. List of CLI tools The following set of CLI tools are available in OpenShift Dedicated: OpenShift CLI ( oc ) : This is the most commonly used CLI tool by OpenShift Dedicated users. It helps both cluster administrators and developers to perform end-to-end operations across OpenShift Dedicated using the terminal. Unlike the web console, it allows the user to work directly with the project source code using command scripts. Knative CLI (kn) : The Knative ( kn ) CLI tool provides simple and intuitive terminal commands that can be used to interact with OpenShift Serverless components, such as Knative Serving and Eventing. Pipelines CLI (tkn) : OpenShift Pipelines is a continuous integration and continuous delivery (CI/CD) solution in OpenShift Dedicated, which internally uses Tekton. The tkn CLI tool provides simple and intuitive commands to interact with OpenShift Pipelines using the terminal. opm CLI : The opm CLI tool helps the Operator developers and cluster administrators to create and maintain the catalogs of Operators from the terminal. Operator SDK : The Operator SDK, a component of the Operator Framework, provides a CLI tool that Operator developers can use to build, test, and deploy an Operator from the terminal. It simplifies the process of building Kubernetes-native applications, which can require deep, application-specific operational knowledge.

Commands:
Chapter 3. Installing power monitoring for Red Hat OpenShift Important Power monitoring is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . You can install power monitoring for Red Hat OpenShift by deploying the Power monitoring Operator in the OpenShift Container Platform web console. 3.1. Installing the Power monitoring Operator As a cluster administrator, you can install the Power monitoring Operator from OperatorHub by using the OpenShift Container Platform web console. Warning You must remove any previously installed versions of the Power monitoring Operator before installation. Prerequisites You have access to the OpenShift Container Platform web console. You are logged in as a user with the cluster-admin role. Procedure In the Administrator perspective of the web console, go to Operators OperatorHub . Search for power monitoring , click the Power monitoring for Red Hat OpenShift tile, and then click Install . Click Install again to install the Power monitoring Operator. Power monitoring for Red Hat OpenShift is now available in all namespaces of the OpenShift Container Platform cluster. Verification Verify that the Power monitoring Operator is listed in Operators Installed Operators . The Status should resolve to Succeeded . 3.2. Deploying Kepler You can deploy Kepler by creating an instance of the Kepler custom resource definition (CRD) by using the Power monitoring Operator. Prerequisites You have access to the OpenShift Container Platform web console. You are logged in as a user with the cluster-admin role. You have installed the Power monitoring Operator. Procedure In the Administrator perspective of the web console, go to Operators Installed Operators . Click Power monitoring for Red Hat OpenShift from the Installed Operators list and go to the Kepler tab. Click Create Kepler . On the Create Kepler page, ensure the Name is set to kepler . Important The name of your Kepler instance must be set to kepler . All other instances are ignored by the Power monitoring Operator. Click Create to deploy Kepler and power monitoring dashboards.

Commands:
Chapter 9. Revision History 0.1-8 Tue Sep 29 2020, Jaroslav Klech ( jklech@redhat.com ) Document version for 7.9 GA publication. 0.1-7 Tue Mar 31 2020, Jaroslav Klech ( jklech@redhat.com ) Document version for 7.8 GA publication. 0.1-6 Tue Aug 6 2019, Jaroslav Klech ( jklech@redhat.com ) Document version for 7.7 GA publication. 0.1-5 Fri Oct 19 2018, Jaroslav Klech ( jklech@redhat.com ) Document version for 7.6 GA publication. 0.1-4 Mon Mar 26 2018, Marie Dolezelova ( mdolezel@redhat.com ) Document version for 7.5 GA publication. 0.1-3 Mon Jan 5 2018, Mark Flitter ( mflitter@redhat.com ) Document version for 7.5 Beta publication. 0.1-2 Mon Jul 31 2017, Mark Flitter ( mflitter@redhat.com ) Document version for 7.4 GA publication. 0.1-0 Thu Apr 20 2017, Mark Flitter ( mflitter@redhat.com ) Initial build for review

Commands:
Chapter 35. System and Subscription Management Undercloud no longer fails on a system with no configured repositories Previously, when the user tried to install the OpenStack Undercloud on a system with no configured repositories, the yum package manager required installation of MySQL dependencies which have been already installed. As a conseqence, the Undercloud install script failed. To fix the bug, yum has been fixed to correctly detect already installed MySQL dependencies. As a result, the Undercloud install script no longer fails on a system with no configured repositories. (BZ#1352585) the yum commands provided by the yum-plugin-verify now set the exit status to 1 if any mismatches are found The yum commands provided by the yum-plugin-verify plug-in returned exit code 0 for any discrepancies found in a package. The bug has been fixed, and the exit status is now set to 1 in case any mismatches are found. (BZ#1406891)

Commands:
3.6. Suspending an XFS File System To suspend or resume write activity to a file system, use the following command: Suspending write activity allows hardware-based device snapshots to be used to capture the file system in a consistent state. Note The xfs_freeze utility is provided by the xfsprogs package, which is only available on x86_64. To suspend (that is, freeze) an XFS file system, use: To unfreeze an XFS file system, use: When taking an LVM snapshot, it is not necessary to use xfs_freeze to suspend the file system first. Rather, the LVM management tools will automatically suspend the XFS file system before taking the snapshot. For more information about freezing and unfreezing an XFS file system, see man xfs_freeze .

Commands:
xfs_freeze mount-point
xfs_freeze -f /mount/point
xfs_freeze -u /mount/point
1.3. Pacemaker Overview The High Availability Add-On cluster infrastructure provides the basic functions for a group of computers (called nodes or members ) to work together as a cluster. Once a cluster is formed using the cluster infrastructure, you can use other components to suit your clustering needs (for example, setting up a cluster for sharing files on a GFS2 file system or setting up service failover). The cluster infrastructure performs the following functions: Cluster management Lock management Fencing Cluster configuration management

Commands:
6.11. Setting Up Server-side Key Generation Server-side key generation means that keys are generated by a Key Recovery Authority (KRA), an optional Certificate System subsystem. Generating keys by the KRA is necessary to allow recovery of keys on lost or damaged tokens, or key retrieval in the case of external registration. This section describes how to configure server-side key generation in TMS. During TPS installation you are asked to specify whether you want to use key archival. If you confirm, setup will perform automatic basic configuration, specifically the following parameters: TPS connector parameters for the KRA: TPS profile-specific parameters for server-side key generation: Set the serverKeygen.enable=true option for serverKeygen.archive to take effect. Important The LunaSA HSM does not support a smaller key size than 2048 bits for RSA encryption. For example, to configure a key size of 2048 bits, set the following parameter in the /var/lib/pki/ instance_name /tps/conf/CS.cfg file: TKS configuration: The following configures the nickname of the transport certificate used for communication between the TKS and KRA (via TPS): The referenced transport certificate must also exist in the TKS instance security module. For example: KRA configuration Depending on the PKCS#11 token, parameters kra.keygen.temporaryPairs , kra.keygen.sensitivePairs , and kra.keygen.extractablePairs can be customized for key generation options. These parameters are all set to false by default. The following values for these parameters have been tested with some of the security modules supported by Red Hat Certificate System: NSS (when in FIPS mode): nCipher nShield Connect 6000 (works by default without specifying): For specifying RSA keys: (Do not specify any other parameters.) For generating ECC keys: LunaSA CKE - Key Export Model (non-FIPS mode): Note Gemalto SafeNet LunaSA only supports PKI private key extraction in its CKE - Key Export model, and only in non-FIPS mode. The LunaSA Cloning model and the CKE model in FIPS mode do not support PKI private key extraction. Note When LunaSA CKE - Key Export Model is in FIPS mode, pki private keys cannot be extracted.

Commands:
tps.connector.kra1.enable=true tps.connector.kra1.host=host1.EXAMPLE.com tps.connector.kra1.maxHttpConns=15 tps.connector.kra1.minHttpConns=1 tps.connector.kra1.nickName=subsystemCert cert-pki-tomcat tps.connector.kra1.port=8443 tps.connector.kra1.timeout=30 tps.connector.kra1.uri.GenerateKeyPair=/kra/agent/kra/GenerateKeyPair tps.connector.kra1.uri.TokenKeyRecovery=/kra/agent/kra/TokenKeyRecovery
op.enroll.userKey.keyGen.encryption.serverKeygen.archive=true op.enroll.userKey.keyGen.encryption.serverKeygen.drm.conn=kra1 op.enroll.userKey.keyGen.encryption.serverKeygen.enable=true
op.enroll.userKey.keyGen.encryption.keySize=2048
tks.drm_transport_cert_nickname=transportCert cert-pki-tomcat KRA
transportCert cert-pki-tomcat KRA u,u,u
kra.keygen.extractablePairs=true
kra.keygen.temporaryPairs=true
kra.keygen.temporaryPairs=true kra.keygen.sensitivePairs=false kra.keygen.extractablePairs=true
kra.keygen.temporaryPairs=true kra.keygen.sensitivePairs=true kra.keygen.extractablePairs=true