mtpti5iD/redhat-docs_dataset huggingface dataset:
4.5. Controlling LVM Device Scans with Filters At startup, the vgscan command is run to scan the block devices on the system looking for LVM labels, to determine which of them are physical volumes and to read the metadata and build up a list of volume groups. The names of the physical volumes are stored in the LVM cache file of each node in the system, /etc/lvm/cache/.cache . Subsequent commands may read that file to avoiding rescanning. You can control which devices LVM scans by setting up filters in the lvm.conf configuration file. The filters in the lvm.conf file consist of a series of simple regular expressions that get applied to the device names in the /dev directory to decide whether to accept or reject each block device found. The following examples show the use of filters to control which devices LVM scans. Note that some of these examples do not necessarily represent recommended practice, as the regular expressions are matched freely against the complete pathname. For example, a/loop/ is equivalent to a/.*loop.*/ and would match /dev/solooperation/lvol1 . The following filter adds all discovered devices, which is the default behavior as there is no filter configured in the configuration file: The following filter removes the cdrom device in order to avoid delays if the drive contains no media: The following filter adds all loop and removes all other block devices: The following filter adds all loop and IDE and removes all other block devices: The following filter adds just partition 8 on the first IDE drive and removes all other block devices: Note When the lvmetad daemon is running, the filter = setting in the /etc/lvm/lvm.conf file does not apply when you execute the pvscan --cache device command. To filter devices, you need to use the global_filter = setting. Devices that fail the global filter are not opened by LVM and are never scanned. You may need to use a global filter, for example, when you use LVM devices in VMs and you do not want the contents of the devices in the VMs to be scanned by the physical host. For more information on the lvm.conf file, see Appendix B, The LVM Configuration Files and the lvm.conf (5) man page.

Commands:
filter = [ "a/.*/" ]
filter = [ "r|/dev/cdrom|" ]
filter = [ "a/loop.*/", "r/.*/" ]
filter =[ "a|loop.*|", "a|/dev/hd.*|", "r|.*|" ]
filter = [ "a|^/dev/hda8USD|", "r/.*/" ]
13.2.25. SSSD and UID and GID Numbers When a user is created - using system tools such as useradd or through an application such as Red Hat Identity Management or other client tools - the user is automatically assigned a user ID number and a group ID number. When the user logs into a system or service, SSSD caches that user name with the associated UID/GID numbers. The UID number is then used as the identifying key for the user. If a user with the same name but a different UID attempts to log into the system, then SSSD treats it as two different users with a name collision. What this means is that SSSD does not recognize UID number changes. It interprets it as a different and new user, not an existing user with a different UID number. If an existing user changes the UID number, that user is prevented from logging into SSSD and associated services and domains. This also has an impact on any client applications which use SSSD for identity information; the user with the conflict will not be found or accessible to those applications. Important UID/GID changes are not supported in SSSD. If a user for some reason has a changed UID/GID number, then the SSSD cache must be cleared for that user before that user can log in again. For example: ~]# sss_cache -u jsmith Cleaning the SSSD cache is covered in the section called "Purging the SSSD Cache" .

Commands:
~]# sss_cache -u jsmith
Chapter 5. FIPS test The Federal Information Processing Standard (FIPS) Publication 140-2, is a computer security standard, developed by a U.S. Government and industry working group to validate the quality of cryptographic modules. FIPS publications (including 140-2) can be found at the following URL: http://csrc.nist.gov/publications/PubsFIPS.html . Note Red Hat recommends partners to enable FIPS mode on both control plane and data plane nodes. Additional resources For more information about FIPS, see Federal Information Processing Standard (FIPS) and Installing a Cluster in FIPS mode .

Commands:
Chapter 13. Key Manager (barbican) Parameters Parameter Description ATOSVars Hash of atos-hsm role variables used to install ATOS client software. BarbicanDogtagStoreGlobalDefault Whether this plugin is the global default plugin. The default value is False . BarbicanDogtagStoreHost Hostname of the Dogtag server. BarbicanDogtagStoreNSSPassword Password for the NSS DB. BarbicanDogtagStorePEMPath Path for the PEM file used to authenticate requests. The default value is /etc/barbican/kra_admin_cert.pem . BarbicanDogtagStorePort Port for the Dogtag server. The default value is 8443 . BarbicanKmipStoreGlobalDefault Whether this plugin is the global default plugin. The default value is False . BarbicanKmipStoreHost Host for KMIP device. BarbicanKmipStorePassword Password to connect to KMIP device. BarbicanKmipStorePort Port for KMIP device. BarbicanKmipStoreUsername Username to connect to KMIP device. BarbicanPassword The password for the OpenStack Key Manager (barbican) service account. BarbicanPkcs11AlwaysSetCkaSensitive Always set CKA_SENSITIVE=CK_TRUE. The default value is True . BarbicanPkcs11CryptoAESGCMGenerateIV Generate IVs for CKM_AES_GCM encryption mechanism. The default value is True . BarbicanPkcs11CryptoATOSEnabled Enable ATOS for PKCS11. The default value is False . BarbicanPkcs11CryptoEnabled Enable PKCS11. The default value is False . BarbicanPkcs11CryptoEncryptionMechanism Cryptoki Mechanism used for encryption. The default value is CKM_AES_CBC . BarbicanPkcs11CryptoGlobalDefault Whether this plugin is the global default plugin. The default value is False . BarbicanPkcs11CryptoHMACKeyType Cryptoki Key Type for Master HMAC key. The default value is CKK_AES . BarbicanPkcs11CryptoHMACKeygenMechanism Cryptoki Mechanism used to generate Master HMAC Key. The default value is CKM_AES_KEY_GEN . BarbicanPkcs11CryptoHMACLabel Label for the HMAC key. BarbicanPkcs11CryptoLibraryPath Path to vendor PKCS11 library. BarbicanPkcs11CryptoLogin Password to login to PKCS11 session. BarbicanPkcs11CryptoMKEKLabel Label for Master KEK. BarbicanPkcs11CryptoMKEKLength Length of Master KEK in bytes. The default value is 256 . BarbicanPkcs11CryptoRewrapKeys Cryptoki Mechanism used to generate Master HMAC Key. The default value is False . BarbicanPkcs11CryptoSlotId Slot Id for the HSM. The default value is 0 . BarbicanPkcs11CryptoThalesEnabled Enable Thales for PKCS11. The default value is False . BarbicanSimpleCryptoGlobalDefault Whether this plugin is the global default plugin. The default value is False . BarbicanSimpleCryptoKek KEK used to encrypt secrets. BarbicanWorkers Set the number of workers for barbican::wsgi::apache. The default value is %{::processorcount} . NotificationDriver Driver or drivers to handle sending notifications. The default value is messagingv2 . ThalesHSMNetworkName The network that the HSM is listening on. The default value is internal_api . ThalesVars Hash of thales-hsm role variables used to install Thales client software.

Commands:
21.3.5. Adding an IPP Printer An IPP printer is a printer attached to a different system on the same TCP/IP network. The system this printer is attached to may either be running CUPS or configured to use IPP. If a firewall is enabled on the printer server, then the firewall must be configured to allow incoming TCP connections on port 631. Note that the CUPS browsing protocol allows client machines to discover shared CUPS queues automatically. To enable this, the firewall on the client machine must be configured to allow incoming UDP packets on port 631. Follow this procedure to add an IPP printer: Open the New Printer dialog (see Section 21.3.2, "Starting Printer Setup" ). In the list of devices on the left, select Network Printer and Internet Printing Protocol (ipp) or Internet Printing Protocol (https) . On the right, enter the connection settings: Host The host name of the IPP printer. Queue The queue name to be given to the new queue (if the box is left empty, a name based on the device node will be used). Figure 21.6. Adding an IPP printer Click Forward to continue. Select the printer model. See Section 21.3.8, "Selecting the Printer Model and Finishing" for details.

Commands:
Chapter 13. Scheduling Messages You can specify a time in the future, at the earliest, for a message to be delivered. This can be done by setting the _AMQ_SCHED_DELIVERY scheduled delivery property before the message is sent. The specified value must be a positive long that corresponds to the time in milliseconds for the message to be delivered. Below is an example of sending a scheduled message using the Jakarta Messaging API. // Create a message to be delivered in 5 seconds TextMessage message = session.createTextMessage("This is a scheduled message message that will be delivered in 5 sec."); message.setLongProperty("_AMQ_SCHED_DELIVERY", System.currentTimeMillis() + 5000); producer.send(message); ... // The message will not be received immediately, but 5 seconds later TextMessage messageReceived = (TextMessage) consumer.receive(); Scheduled messages can also be sent using the core API by setting the _AMQ_SCHED_DELIVERY property before sending the message.

Commands:
// Create a message to be delivered in 5 seconds TextMessage message = session.createTextMessage("This is a scheduled message message that will be delivered in 5 sec."); message.setLongProperty("_AMQ_SCHED_DELIVERY", System.currentTimeMillis() + 5000); producer.send(message); // The message will not be received immediately, but 5 seconds later TextMessage messageReceived = (TextMessage) consumer.receive();
1.6. Encryption Teiid Transports Teiid provides built-in support for JDBC/ODBC over SSL. JDBC defaults to just sensitive message encryption (login mode), while ODBC (the pg transport) defaults to just clear text passwords if using simple username/password authentication. The Red Hat JBoss EAP instance must be configured for SSL as well so that any web services consuming Teiid may use SSL. Configuration Passwords in configuration files are stored as a hash. Source Access Encrypting remote source access is the responsibility for the resource adapter and library/driver used to access the source system. Temporary Data Teiid temporary data which can be stored on the file system as configured by the BufferManager may optionally be encrypted. Set the buffer-service-encrypt-files property to true on the Teiid subsystem to use 128-bit AES to encrypt any files written by the BufferManager. A new symmetric key will be generated for each start of the Teiid system on each server. A performance hit will be seen for processing that is memory intensive such that data typically spills to disk. This setting does not affect how VDBs (either the artifact or an exploded form) or log files are written to disk.

Commands:
2.7. GNOME Power Manager GNOME Power Manager is a daemon that is installed as part of the GNOME desktop environment. Much of the power-management functionality that GNOME Power Manager provided in earlier versions of Red Hat Enterprise Linux has become part of the DeviceKit-power tool in Red Hat Enterprise Linux 6, renamed to UPower in Red Hat Enterprise Linux 7 (see Section 2.6, "UPower" ). However, GNOME Power Manager remains a front end for that functionality. Through an applet in the system tray, GNOME Power Manager notifies you of changes in your system's power status; for example, a change from battery to AC power. It also reports battery status, and warns you when battery power is low.

Commands:
11.5. Column Options You can use the following options when specifying columns in the creation of a table or view. Any others properties defined will be considered as extension metadata. Property Data Type or Allowed Values Description UUID string A unique identifier for the column NAMEINSOURCE string If this is a column name on the FOREIGN table, this value represents name of the column in source database, if omitted the column name is used when querying for data against the source CASE_SENSITIVE 'TRUE'|'FALSE' SELECTABLE 'TRUE'|'FALSE' TRUE when this column is available for selection from the user query UPDATABLE 'TRUE'|'FALSE' Defines if the column is updatable. Defaults to true if the view/table is updatable. SIGNED 'TRUE'|'FALSE' CURRENCY 'TRUE'|'FALSE' FIXED_LENGTH 'TRUE'|'FALSE' SEARCHABLE 'SEARCHABLE'|'UNSEARCHABLE'|'LIKE_ONLY'|'ALL_EXCEPT_LIKE' column searchability, usually dictated by the data type MIN_VALUE MAX_VALUE CHAR_OCTET_LENGTH integer ANNOTATION string NATIVE_TYPE string RADIX integer NULL_VALUE_COUNT long costing information. Number of NULLS in this column DISTINCT_VALUES long costing information. Number of distinct values in this column

Commands:
19.5. Clustering and High Availability High Availability Add-On Administration The High Availability Add-On Administration guide provides information on how to configure and administer the High Availability Add-On in Red Hat Enterprise Linux 7. High Availability Add-On Overview The High Availability Add-On Overview document provides an overview of the High Availability Add-On for Red Hat Enterprise Linux 7. High Availability Add-On Reference High Availability Add-On Reference is a reference guide to the High Availability Add-On for Red Hat Enterprise Linux 7. Load Balancer Administration Load Balancer Administration is a guide to configuring and administering high-performance load balancing in Red Hat Enterprise Linux 7. DM Multipath The DM Multipath book guides users through configuring and administering the Device-Mapper Multipath feature for Red Hat Enterprise Linux 7.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 9.1 is distributed with the kernel version 5.14.0-162, which provides support for the following architectures at the minimum required version: AMD and Intel 64-bit architectures (x86-64-v2) The 64-bit ARM architecture (ARMv8.0-A) IBM Power Systems, Little Endian (POWER9) 64-bit IBM Z (z14) Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures .

Commands:
Chapter 149. KafkaNodePoolTemplate schema reference Used in: KafkaNodePoolSpec Property Property type Description podSet ResourceTemplate Template for Kafka StrimziPodSet resource. pod PodTemplate Template for Kafka Pods . perPodService ResourceTemplate Template for Kafka per-pod Services used for access from outside of OpenShift. perPodRoute ResourceTemplate Template for Kafka per-pod Routes used for access from outside of OpenShift. perPodIngress ResourceTemplate Template for Kafka per-pod Ingress used for access from outside of OpenShift. persistentVolumeClaim ResourceTemplate Template for all Kafka PersistentVolumeClaims . kafkaContainer ContainerTemplate Template for the Kafka broker container. initContainer ContainerTemplate Template for the Kafka init container.

Commands:
24.4. Parent Tags 24.4.1. Parent Tags An API user assigns a parent element to a tag to create a hierarchical link to a parent tag. The tags are presented as a flat collection, which descends from the root tag, with tag representations containing a link element to a parent tag Note The root tag is a special pseudo-tag assumed as the default parent tag if no parent tag is specified. The root tag cannot be deleted nor assigned a parent tag. This tag hierarchy is expressed in the following way: Example 24.5. Tag Hierarchy In this XML representation, the tags follow this hierarchy: 24.4.2. Setting a Parent Tag POST ing a new tag with a parent element creates an association with a parent tag, using either the id attribute or the name element to reference the parent tag Example 24.6. Setting an association with a parent tag with the id attribute Example 24.7. Setting an association with a parent tag with the name element 24.4.3. Changing a Parent Tag A tag changes a parent using a PUT request: Example 24.8. Changing the parent tag

Commands:
<tags> <tag id="-1" href="/ovirt-engine/api/tags/-1"> <name>root</name> <description>root</description> <parent> <tag id="-1" href="/ovirt-engine/api/tags/-1"/> </parent> </tag> <tag id="f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e" href="/ovirt-engine/api/tags/f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e"> <name>Finance</name> <description>Resources for the Finance department</description> <parent> <tag id="-1" href="/ovirt-engine/api/tags/-1"/> </parent> </tag> <tag id="ac18dabf-23e5-12be-a383-a38b165ca7bd" href="/ovirt-engine/api/tags/ac18dabf-23e5-12be-a383-a38b165ca7bd"> <name>Billing</name> <description>Billing Resources</description> <parent> <tag id="f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e" href="/ovirt-engine/api/tags/f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e"/> </parent> </tag> </tags>
root (id: -1) - Finance (id: f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e) - Billing (id: ac18dabf-23e5-12be-a383-a38b165ca7bd)
POST /ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720/tags HTTP/1.1 Accept: application/xml Content-Type: application/xml HTTP/1.1 200 OK Content-Type: application/xml <tag> <name>Billing</name> <description>Billing Resources</description> <parent> <tag id="f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e"/> </parent> </tag>
POST /ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720/tags HTTP/1.1 Accept: application/xml Content-Type: application/xml HTTP/1.1 200 OK Content-Type: application/xml <tag> <name>Billing</name> <description>Billing Resources</description> <parent> <tag> <name>Finance</name> </tag> </parent> </tag>
PUT /ovirt-engine/api/tags/ac18dabf-23e5-12be-a383-a38b165ca7bd HTTP/1.1 Accept: application/xml Content-Type: application/xml <tag> <parent> <tag id="f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e"/> </parent> </tag>
9.4. What Are dconf Profiles? A profile is a list of system's hardware and software configuration databases, which the dconf system collects. dconf profiles allow you to compare identical systems to troubleshoot hardware or software problems. The dconf system stores its profiles in text files. The USDDCONF_PROFILE environment variable can specify a relative path to the file from the /etc/dconf/profile/ directory, or an absolute path, such as in a user's home directory. Key pairs which are set in a dconf profile will override the default settings unless there is a problem with the value that you have set. 9.4.1. Selecting a dconf Profile On startup, dconf consults the USDDCONF_PROFILE environment variable whether the variable is set. If set, dconf attempts to open the named profile and aborts if this step fails. As long as the environment variable is not set, dconf attempts to open the profile named user . Provided this step still fails, dconf falls back to an internal hard-wired configuration. Each line in a profile specifies one dconf database. The first line indicates the database used to write changes whereas the remaining lines show read-only databases. The following is a sample profile stored in /etc/dconf/profile/user : This sample profile specifies three databases: user is the name of the user database which can normally be found in ~/.config/dconf , and local and site are system databases, located in /etc/dconf/db/ . Important The dconf profile for a session is determined at login, so users will have to log out and log in to apply a new dconf user profile to their session.

Commands:
user-db: user system-db: local system-db: site
7.3. Pools Virtual machine pools allow for rapid provisioning of numerous identical virtual machines to users as desktops. Users who have been granted permission to access and use virtual machines from a pool receive an available virtual machine based on their position in a queue of requests. Virtual machines in a pool do not allow data persistence; each time a virtual machine is assigned from a pool, it is allocated in its base state. This is ideally suited to be used in situations where user data is stored centrally. Virtual machine pools are created from a template. Each virtual machine in a pool uses the same backing read-only image, and uses a temporary copy-on-write image to hold changed and newly generated data. Virtual machines in a pool are different from other virtual machines in that the copy-on-write layer that holds user-generated and -changed data is lost at shutdown. The implication of this is that a virtual machine pool requires no more storage than the template that backs it, plus some space for data generated or changed during use. Virtual machine pools are an efficient way to provide computing power to users for some tasks without the storage cost of providing each user with a dedicated virtual desktop. Example 7.1. Example Pool Usage A technical support company employs 10 help desk staff. However, only five are working at any given time. Instead of creating ten virtual machines, one for each help desk employee, a pool of five virtual machines can be created. Help desk employees allocate themselves a virtual machine at the beginning of their shift and return it to the pool at the end.

Commands:
8.2. sVirt Labeling Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest instances. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt. As shown in the following output, when using sVirt, each Virtual Machine (VM) process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels: The actual disk images are automatically labeled to match the processes, as shown in the following output: The following table outlines the different labels that can be assigned when using sVirt: Table 8.1. sVirt Labels Type SELinux Context Description Virtual Machine Processes system_u:system_r:svirt_t:MCS1 MCS1 is a randomly selected MCS field. Currently approximately 500,000 labels are supported. Virtual Machine Image system_u:object_r:svirt_image_t:MCS1 Only processes labeled svirt_t with the same MCS fields are able to read/write these image files and devices. Virtual Machine Shared Read/Write Content system_u:object_r:svirt_image_t:s0 All processes labeled svirt_t are allowed to write to the svirt_image_t:s0 files and devices. Virtual Machine Image system_u:object_r:virt_content_t:s0 System default label used when an image exits. No svirt_t virtual processes are allowed to read files/devices with this label. It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a virtual machine. Administrators who run statically-labeled virtual machines are responsible for setting the correct label on the image files. The virtual machine will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple virtual machines with different sensitivity levels on a system, depending on your requirements.

Commands:
~]# ps -eZ | grep qemu system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm system_u:system_r:svirt_t:s0:c639,c757 27989 ? 00:00:06 qemu-system-x86
~]# ls -lZ /var/lib/libvirtimages/* system_u:object_r:svirt_image_t:s0:c87,c520 image1