mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 16. Configuring node-specific values using node attributes Pacemaker supports the configuration of node-specific values, which you specify using node attributes . You can use node attributes to track information associated with a node. For example, you can define node attributes for how much RAM and disk space each node has, which OS each node uses, or which server room rack each node is in. There are three primary uses for node attributes: In Pacemaker rules for the cluster configuration For example, you can set a node attribute named department to accounting or IT on each node, depending on which department that node is dedicated to. You can then configure a location rule to ensure that an accounting database runs only on servers where department is set to accounting . For information about node attribute expressions in Pacemaker rules, see Pacemaker rules . In resource agents for the specific resource requirements For example, a database resource agent can use a node attribute to track the latest replication position for use in a promote action. In external scripts for use outside Pacemaker For example, you can set data-center and rack attributes for each node, for use by an external inventory script. Defining a node attribute You define a node attribute with the pcs node attribute command. A node attribute has a name and a value, and can have a distinct value for each node. When you define a node attribute with the pcs node attribute command, the node attribute is permanent . Permanent node attributes keep their values even when the cluster restarts on a node. Note You can define a transient node attribute, which is kept in the CIB's status section, and does not remain when the cluster stops on the node. For information about defining transient node attributes, see the crm_attribute (8) and attrd_updater (8) man pages on your system. Procedure Run the following commands to define a node attribute with the name rack for node1 and node2 , setting a value of 1 for the rack attribute of node1 and a value of 2 for the rack attribute of node2 .

Commands:
pcs node attribute node1 rack=1 pcs node attribute node2 rack=2
Chapter 28. Uninstalling the IdM CA service from an IdM server If you have more than four Identity Management (IdM) replicas with the CA Role in your topology and you run into performance problems due to redundant certificate replication, remove redundant CA service instances from IdM replicas. To do this, you must first decommission the affected IdM replicas completely before re-installing IdM on them, this time without the CA service. Note While you can add the CA role to an IdM replica, IdM does not provide a method to remove only the CA role from an IdM replica: the ipa-ca-install command does not have an --uninstall option. Prerequisites You have the IdM CA service installed on more than four IdM servers in your topology. Procedure Identify the redundant CA service and follow the procedure in Uninstalling an IdM server on the IdM replica that hosts this service. On the same host, follow the procedure in Installing an IdM server: With integrated DNS, without a CA .

Commands:
Chapter 9. Important links Red Hat AMQ Broker 7.9 Release Notes Red Hat AMQ Broker 7.8 Release Notes Red Hat AMQ Broker 7.7 Release Notes Red Hat AMQ Broker 7.6 Release Notes Red Hat AMQ Broker 7.1 to 7.5 Release Notes (aggregated) Red Hat AMQ 7 Supported Configurations Red Hat AMQ 7 Component Details Revised on 2024-06-10 15:28:56 UTC

Commands:
9.9. Publishing Cross-Pair Certificates The cross-pair certificates can be published as a crossCertificatePair entry to an LDAP directory or to a file; this is enabled by default. If this has been disabled, it can be re-enabled through the Certificate Manager Console by doing the following: Open the CA console. In the Configuration tab, select the Certificate Manager link in the left pane, then the Publishing link. Click the Rules link under Publishing . This opens the Rules Management pane on the right. If the rule exists and has been disabled, select the enable checkbox. If the rule has been deleted, then click Add and create a new rule. Select xcerts from the type drop-down menu. Make sure the enable checkbox is selected. Select LdapCaCertMap from the mapper drop-down menu. Select LdapCrossCertPairPublisher from the publisher drop-down menu. The mapper and publisher specified in the publishing rule are both listed under Mapper and Publisher under the Publishing link in the left navigation window of the CA Console. The mapper, LdapCaCertMap , by default designates that the crossCertificatePair be stored to the LdapCaSimpleMap LDAP entry. The publisher, LDAPCrossPairPublisher , by default sets the attribute to store the cross-pair certificate in the CA entry to crossCertificatePair;binary . For more information on using cross-pair certificates, see Section 17.5, "Using Cross-Pair Certificates" . For more information on creating cross-pair certificate profiles, see the Configuring Cross-Pair profiles section in the Red Hat Certificate System Planning, Installation, and Deployment Guide . Note pkiconsole is being deprecated.

Commands:
pkiconsole https://server.example.com:8443/ca
29.7. Example Usage While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example: Determine which applications and services are used the most on a system - opreport can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems. Determine processor usage - The CPU_CLK_UNHALTED event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.

Commands:
9.6. GSettings Keys Properties You can set a GSettings key in a dconf database only once. If you set the same key to different values in different places in the dconf database, only one of them will take effect. In other words, you will override one key setting with another. In each dconf system database, each key can only have one value. Values for some keys are of an array type. For this value type, the value can be specified as a list of multiple elements separated by a comma. An example of an array value is shown below: Example 9.3. The org.gnome.desktop.input-sources.xkb-options GSettings Key Setting the org.gnome.desktop.input-sources.xkb-options GSettings key works as follows. It can only be set once, so if you want two elements in the value you need to specify them in the same configuration file. Since this value is an array type, it can have several elements:

Commands:
key=[ 'option1' , 'option2' ]
Enable Ctrl-Alt-Backspace for all users Set the Right Alt key as the Compose key and enable it xkb-options=['terminate:ctrl_alt_bksp', 'compose:ralt']
Chapter 2. access This chapter describes the commands under the access command. 2.1. access token create Create an access token Usage: Table 2.1. Optional Arguments Value Summary -h, --help Show this help message and exit --consumer-key <consumer-key> Consumer key (required) --consumer-secret <consumer-secret> Consumer secret (required) --request-key <request-key> Request token to exchange for access token (required) --request-secret <request-secret> Secret associated with <request-key> (required) --verifier <verifier> Verifier associated with <request-key> (required) Table 2.2. 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 2.3. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 2.4. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 2.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.

Commands:
openstack access token create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --consumer-key <consumer-key> --consumer-secret <consumer-secret> --request-key <request-key> --request-secret <request-secret> --verifier <verifier>
Chapter 35. KafkaClusterTemplate schema reference Used in: KafkaClusterSpec Property Property type Description statefulset StatefulSetTemplate The statefulset property has been deprecated. Support for StatefulSets was removed in Streams for Apache Kafka 2.5. This property is ignored. Template for Kafka StatefulSet . pod PodTemplate Template for Kafka Pods . bootstrapService InternalServiceTemplate Template for Kafka bootstrap Service . brokersService InternalServiceTemplate Template for Kafka broker Service . externalBootstrapService ResourceTemplate Template for Kafka external bootstrap Service . perPodService ResourceTemplate Template for Kafka per-pod Services used for access from outside of OpenShift. externalBootstrapRoute ResourceTemplate Template for Kafka external bootstrap Route . perPodRoute ResourceTemplate Template for Kafka per-pod Routes used for access from outside of OpenShift. externalBootstrapIngress ResourceTemplate Template for Kafka external bootstrap Ingress . perPodIngress ResourceTemplate Template for Kafka per-pod Ingress used for access from outside of OpenShift. persistentVolumeClaim ResourceTemplate Template for all Kafka PersistentVolumeClaims . podDisruptionBudget PodDisruptionBudgetTemplate Template for Kafka PodDisruptionBudget . kafkaContainer ContainerTemplate Template for the Kafka broker container. initContainer ContainerTemplate Template for the Kafka init container. clusterCaCert ResourceTemplate Template for Secret with Kafka Cluster certificate public key. serviceAccount ResourceTemplate Template for the Kafka service account. jmxSecret ResourceTemplate Template for Secret of the Kafka Cluster JMX authentication. clusterRoleBinding ResourceTemplate Template for the Kafka ClusterRoleBinding. podSet ResourceTemplate Template for Kafka StrimziPodSet resource.

Commands:
E.2.7. /proc/execdomains This file lists the execution domains currently supported by the Linux kernel, along with the range of personalities they support. Think of execution domains as the "personality" for an operating system. Because other binary formats, such as Solaris, UnixWare, and FreeBSD, can be used with Linux, programmers can change the way the operating system treats system calls from these binaries by changing the personality of the task. Except for the PER_LINUX execution domain, different personalities can be implemented as dynamically loadable modules.

Commands:
0-0 Linux [kernel]
Chapter 47. Red Hat Enterprise Linux System Roles Powered by Ansible New packages: ansible Red Hat Enterprise Linux System Roles, now available as a Technology Preview, is a configuration interface for Red Hat Enterprise Linux subsystems, which makes system configuration easier through the inclusion of Ansible Roles . This interface enables managing system configurations across multiple versions of Red Hat Enterprise Linux, as well as adopting new major releases. With Red Hat Enterprise Linux 7.4, the Red Hat Enterprise Linux System Roles packages are distributed through the Extras channel. For details regarding Red Hat Enterprise Linux System Roles, see https://access.redhat.com/articles/3050101 . Notes: Currently, Ansible is not a part of the Red Hat Enterprise Linux FIPS validation process. We hope to address this in future releases. Ansible is being included as an unsupported runtime dependency. (BZ#1313263)

Commands:
Chapter 3. Creating snapshots from an active recording You can take a snapshot of an active JFR recording to capture any collected data, up to a specific point in time, for your target JVM application. A snapshot is like a checkpoint marker that has a start point and an end point for a given time segment in a running JFR recording. A snapshot gets stored in the memory of a target JVM application. This differs from an archive in that Cryostat stores an archive on a cloud storage disk, which is a more permanent solution for storing a JFR recording's data. You can take snapshots of recordings if you want to experiment with different configuration changes among active JFR recordings. When you create a snapshot for your JFR recording, Cryostat creates a new target JVM named snapshot - <snapshot_number> , where <snapshot_number> is the number that Cryostat automatically assigns to your snapshot. A target JVM recognizes a snapshot as an active recording. Cryostat sets any JFR snapshots in the STOPPED state, which means that the JFR snapshot does not record new data to the target JVM. Depending on the JFR configuration, active JFR recordings can continue to monitor the target JVM regardless of the number of snapshots taken. Note For a JFR recording that you set for continuous monitoring of a target JVM application, ensure that you create archived recordings to avoid losing JFR recording data. If you choose to take regular snapshots to store your JFR recording data, the target JVM application might free some of its data storage space by replacing older recording data with newer recording data. Prerequisites Entered your authentication details for your Cryostat instance. Created a target JVM recording and entered your authenticated details to access the Recordings menu. See Creating a JDK Flight Recorder (JFR) recording (Creating a JFR recording with Cryostat). Procedure On the Active Recordings tab, click the Create button. A new window opens on the web console. Figure 3.1. Example of creating an active recording Click the Snapshot Recording tab. Figure 3.2. Example of creating a snapshot recording Click Create . The Active Recordings table opens and it lists your JFR snapshot recording. The following example shows a JFR snapshot recording named snapshot-3 . Figure 3.3. Example of a completed snapshot recording Note You can identify snapshots by the snapshot prefix from the list of active recordings. steps To archive your JFR snapshot recording, see Archiving JDK Flight Recorder (JFR) recordings .

Commands:
3.17. Starting a Virtual Machine with Cloud-Init This Ruby example starts a virtual machine using the Cloud-Init tool to set the root password and network configuration. # Find the virtual machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] # Find the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) # Create a cloud-init script to execute in the # deployed virtual machine. The script must be correctly # formatted and indented because it uses YAML. my_script = " write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' " # Start the virtual machine, enabling cloud-init and providing the # password for the `root` user and the network configuration: vm_service.start( use_cloud_init: true, vm: { initialization: { user_name: 'root', root_password: 'redhat123', host_name: 'myvm.example.com', nic_configurations: [ { name: 'eth0', on_boot: true, boot_protocol: OvirtSDK4::BootProtocol::STATIC, ip: { version: OvirtSDK4::IpVersion::V4, address: '192.168.0.100', netmask: '255.255.255.0', gateway: '192.168.0.1' } } ], dns_servers: '192.168.0.1 192.168.0.2 192.168.0.3', dns_search: 'example.com', custom_script: my_script } } ) For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/VmService:start .

Commands:
Find the virtual machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] Find the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) Create a cloud-init script to execute in the deployed virtual machine. The script must be correctly formatted and indented because it uses YAML. my_script = " write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' " Start the virtual machine, enabling cloud-init and providing the password for the `root` user and the network configuration: vm_service.start( use_cloud_init: true, vm: { initialization: { user_name: 'root', root_password: 'redhat123', host_name: 'myvm.example.com', nic_configurations: [ { name: 'eth0', on_boot: true, boot_protocol: OvirtSDK4::BootProtocol::STATIC, ip: { version: OvirtSDK4::IpVersion::V4, address: '192.168.0.100', netmask: '255.255.255.0', gateway: '192.168.0.1' } } ], dns_servers: '192.168.0.1 192.168.0.2 192.168.0.3', dns_search: 'example.com', custom_script: my_script } } )
Chapter 5. Login Page Settings There are several nice built-in login page features you can enable if you need the functionality. 5.1. Forgot Password If you enable it, users are able to reset their credentials if they forget their password or lose their OTP generator. Go to the Realm Settings left menu item, and click on the Login tab. Switch on the Forgot Password switch. Login Tab A forgot password link will now show up on your login pages. Forgot Password Link Clicking on this link will bring the user to a page where they can enter in their username or email and receive an email with a link to reset their credentials. Forgot Password Page The text sent in the email is completely configurable. You just need to extend or edit the theme associated with it. See the Server Developer Guide for more information. When the user clicks on the email link, they will be asked to update their password, and, if they have an OTP generator set up, they will also be asked to reconfigure this as well. Depending on the security requirements of your organization you may not want users to be able to reset their OTP generator through email. You can change this behavior by going to the Authentication left menu item, clicking on the Flows tab, and selecting the Reset Credentials flow: Reset Credentials Flow If you do not want OTP reset, then just chose the disabled radio button to the right of Reset OTP . Note Be sure to leave Update Password enabled on the Required Actions tab. Otherwise, Forgot Password does not work. 5.2. Remember Me If a logged in user closes their browser, their session is destroyed and they will have to log in again. You can set things up so that if a user checks a remember me checkbox, they will remain logged in even if the browser is closed. This basically turns the login cookie from a session-only cookie to a persistence cookie. To enable this feature go to Realm Settings left menu item and click on the Login tab and turn on the Remember Me switch: Login Tab Once you save this setting, a remember me checkbox will be displayed on the realm's login page. Remember Me

Commands:
Chapter 9. Red Hat Enterprise Linux Atomic Host 7.7.2 9.1. Atomic Host OStree update : New Tree Version: 7.7.2 (hash: 7b95d939d6c53a3c972154f8ffce3e74f3e5f1826c766911602db43d6beafb6c) Changes since Tree Version 7.7.1 (hash: eb2a0972825a436fe9df83f19621ac69419bf8cba5bbaedcc90f32e7ef40b5ea) 9.2. Extras Updated packages : docker-1.13.1-104.git4ef4b30.el7 9.2.1. Container Images Updated : Red Hat Universal Base Image 7 Minimal Container Image (rhel7/ubi7-minimal) Red Hat Universal Base Image 7 Container Image (rhel7/ubi7) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) Red Hat Enterprise Linux 7.7 Container Image for aarch64 (rhel7.7, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd)

Commands:
Preface After you create your OSTree images, install the RHEL for Edge images on your devices, and register these systems with the Red Hat Insights application, you can organize systems into groups. With that, you can manage multiple systems simultaneously, and perform various tasks, such as vulnerability assessment. You can also check for vulnerabilities. If Common Vulnerabilities and Exposures (CVEs) are identified, you can use the Insights Inventory application to update the image and simultaneously deploy the update to multiple systems. If you are using Edge management : To be able to edit, delete, or to display host's details, you must have the Inventory Hosts Administrator role assigned to your account. If you just want to be able to display the host's details, but you have no access to actions you must have at least the Workspaces Hosts Viewer role assigned to your account. If you are using Inventory under Red Hat Insights: If you want to use Workspaces access, see the User access to Workspaces documentation to learn more on how to manage groups access. If you do not want to use granular Workspaces access, you must have at least the Inventory Hosts Administrator and the Workspaces Administrator roles assigned to your account. Warning If you want your non-org administrator users to be able to see or manage their Workspaces, you must add one of the Workspaces roles to the Default Access RBAC group. Otherwise, non-org administrator users will not be able to see or manage the Workspaces. Workspaces support role-based access (RBAC). By using RBAC, you can set custom permissions on Workspaces according to the user role. See User access to Workspaces for more details.

Commands:
6.5. RHEA-2013:0356 - new package: haproxy A new haproxy package is now available for Red Hat Enterprise Linux 6. The haproxy package provides a reliable, high-performance network load balancer for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. This enhancement update adds the haproxy package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ#846067) More information about Red Hat Technology Previews is available at https://access.redhat.com/support/offerings/techpreview/ All users who want to use the haproxy Technology Preview should install this newly-released package, which adds this enhancement.

Commands: