mtpti5iD/redhat-docs_dataset huggingface dataset:
2.11. Thin Provisioning and Storage Over-Commitment The Red Hat Virtualization Manager provides provisioning policies to optimize storage usage within the virtualization environment. A thin provisioning policy allows you to over-commit storage resources, provisioning storage based on the actual storage usage of your virtualization environment. Storage over-commitment is the allocation of more storage to virtual machines than is physically available in the storage pool. Generally, virtual machines use less storage than what has been allocated to them. Thin provisioning allows a virtual machine to operate as if the storage defined for it has been completely allocated, when in fact only a fraction of the storage has been allocated. Note While the Red Hat Virtualization Manager provides its own thin provisioning function, you should use the thin provisioning functionality of your storage back-end if it provides one. To support storage over-commitment, VDSM defines a threshold which compares logical storage allocation with actual storage usage. This threshold is used to make sure that the data written to a disk image is smaller than the logical volume that backs the disk image. QEMU identifies the highest offset written to in a logical volume, which indicates the point of greatest storage use. VDSM monitors the highest offset marked by QEMU to ensure that the usage does not cross the defined threshold. So long as VDSM continues to indicate that the highest offset remains below the threshold, the Red Hat Virtualization Manager knows that the logical volume in question has sufficient storage to continue operations. When QEMU indicates that usage has risen to exceed the threshold limit, VDSM communicates to the Manager that the disk image will soon reach the size of it's logical volume. The Red Hat Virtualization Manager requests that the SPM host extend the logical volume. This process can be repeated as long as the data storage domain for the data center has available space. When the data storage domain runs out of available free space, you must manually add storage capacity to expand it.

Commands:
7.8. RHEA-2014:1467 - new packages: java-1.8.0-openjdk New java-1.8.0-openjdk packages are now available for Red Hat Enterprise Linux 6. java-1.8.0-openjdk packages provide the OpenJDK runtime environment. This enhancement update adds the java-1.8.0-openjdk packages to Red Hat Enterprise Linux 6. (BZ# 1081073 , BZ# 1113078 ) All users who require java-1.8.0-openjdk are advised to install these new packages. All running instances of OpenJDK Java must be restarted for the update to take effect.

Commands:
Chapter 5. Running Directory Server in FIPS mode Directory Server fully supports the Federal Information Processing Standard (FIPS) 140-2. When you run Directory Server run in FIPS mode, security-related settings change. For example, SSL is automatically disabled and only TLS 1.2 and 1.3 encryption is used. 5.1. Enabling the FIPS mode To use Directory Server in Federal Information Processing Standard (FIPS) mode, enable the mode in RHEL and Directory Server. Prerequisites You enabled the FIPS mode in RHEL. Procedure Enable the FIPS mode for the network security services (NSS) database: # modutil -dbdir /etc/dirsrv/slapd- instance_name / -fips true Restart the instance: # dsctl instance_name restart Verification Verify that FIPS mode is enabled for the NSS database: # modutil -dbdir /etc/dirsrv/slapd- instance_name / -chkfips true FIPS mode enabled. The command returns FIPS mode enabled , if the module is in FIPS mode. 5.2. Additional resources Federal Information Processing Standard (FIPS) Switching the system to FIPS mode

Commands:
modutil -dbdir /etc/dirsrv/slapd- instance_name / -fips true
dsctl instance_name restart
modutil -dbdir /etc/dirsrv/slapd- instance_name / -chkfips true FIPS mode enabled.
Chapter 20. MariaDB (a replacement for MySQL) The MariaDB database is a multi-user, multi-threaded SQL database server that consists of the MariaDB server daemon ( mysqld ) and many client programs and libraries. [18] In Red Hat Enterprise Linux, the mariadb-server package provides MariaDB. Enter the following command to see if the mariadb-server package is installed: If it is not installed, use the yum utility as root to install it: 20.1. MariaDB and SELinux When MariaDB is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates the MariaDB processes running in their own domain. This example assumes the mariadb-server package is installed: Run the getenforce command to confirm SELinux is running in enforcing mode: The command returns Enforcing when SELinux is running in enforcing mode. Enter the following command as the root user to start mariadb : Confirm that the service is running. The output should include the information below (only the time stamp will differ): Enter the following command to view the mysqld processes: The SELinux context associated with the mysqld processes is system_u:system_r:mysqld_t:s0 . The second last part of the context, mysqld_t , is the type. A type defines a domain for processes and a type for files. In this case, the mysqld processes are running in the mysqld_t domain. [18] See the MariaDB project page for more information.

Commands:
~]USD rpm -q mariadb-server package mariadb-server is not installed
~]# yum install mariadb-server
~]USD getenforce Enforcing
~]# systemctl start mariadb.service
~]# systemctl status mariadb.service mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled) Active: active (running) since Mon 2013-08-05 11:20:11 CEST; 3h 28min ago
~]USD ps -eZ | grep mysqld system_u:system_r:mysqld_safe_t:s0 12831 ? 00:00:00 mysqld_safe system_u:system_r:mysqld_t:s0 13014 ? 00:00:00 mysqld
Chapter 4. Configuring Red Hat High Availability Add-On With Conga This chapter describes how to configure Red Hat High Availability Add-On software using Conga . For information on using Conga to manage a running cluster, see Chapter 5, Managing Red Hat High Availability Add-On With Conga . Note Conga is a graphical user interface that you can use to administer the Red Hat High Availability Add-On. Note, however, that in order to use this interface effectively you need to have a good and clear understanding of the underlying concepts. Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail. This chapter consists of the following sections: Section 4.1, "Configuration Tasks" Section 4.2, "Starting luci " Section 4.3, "Controlling Access to luci" Section 4.4, "Creating a Cluster" Section 4.5, "Global Cluster Properties" Section 4.6, "Configuring Fence Devices" Section 4.7, "Configuring Fencing for Cluster Members" Section 4.8, "Configuring a Failover Domain" Section 4.9, "Configuring Global Cluster Resources" Section 4.10, "Adding a Cluster Service to the Cluster" 4.1. Configuration Tasks Configuring Red Hat High Availability Add-On software with Conga consists of the following steps: Configuring and running the Conga configuration user interface - the luci server. Refer to Section 4.2, "Starting luci " . Creating a cluster. Refer to Section 4.4, "Creating a Cluster" . Configuring global cluster properties. Refer to Section 4.5, "Global Cluster Properties" . Configuring fence devices. Refer to Section 4.6, "Configuring Fence Devices" . Configuring fencing for cluster members. Refer to Section 4.7, "Configuring Fencing for Cluster Members" . Creating failover domains. Refer to Section 4.8, "Configuring a Failover Domain" . Creating resources. Refer to Section 4.9, "Configuring Global Cluster Resources" . Creating cluster services. Refer to Section 4.10, "Adding a Cluster Service to the Cluster" .

Commands:
Chapter 57. JmxTransSpec schema reference The type JmxTransSpec has been deprecated. Used in: KafkaSpec Property Description image The image to use for the JmxTrans. string outputDefinitions Defines the output hosts that will be referenced later on. For more information on these properties see, JmxTransOutputDefinitionTemplate schema reference . JmxTransOutputDefinitionTemplate array logLevel Sets the logging level of the JmxTrans deployment.For more information see, JmxTrans Logging Level . string kafkaQueries Queries to send to the Kafka brokers to define what data should be read from each broker. For more information on these properties see, JmxTransQueryTemplate schema reference . JmxTransQueryTemplate array resources CPU and memory resources to reserve. For more information, see the external documentation for core/v1 resourcerequirements . ResourceRequirements template Template for JmxTrans resources. JmxTransTemplate

Commands:
Chapter 27. External Array Management (libStorageMgmt) Red Hat Enterprise Linux 7 ships with a new external array management library called libStorageMgmt . 27.1. Introduction to libStorageMgmt The libStorageMgmt library is a storage array independent Application Programming Interface (API). As a developer, you can use this API to manage different storage arrays and leverage the hardware accelerated features. This library is used as a building block for other higher level management tools and applications. End system administrators can also use it as a tool to manually manage storage and automate storage management tasks with the use of scripts. With the libStorageMgmt library, you can perform the following operations: List storage pools, volumes, access groups, or file systems. Create and delete volumes, access groups, file systems, or NFS exports. Grant and remove access to volumes, access groups, or initiators. Replicate volumes with snapshots, clones, and copies. Create and delete access groups and edit members of a group. Server resources such as CPU and interconnect bandwidth are not utilized because the operations are all done on the array. The libstoragemgmt package provides: A stable C and Python API for client application and plug-in developers. A command-line interface that utilizes the library ( lsmcli ). A daemon that executes the plug-in ( lsmd ). A simulator plug-in that allows the testing of client applications ( sim ). Plug-in architecture for interfacing with arrays. Warning This library and its associated tool have the ability to destroy any and all data located on the arrays it manages. It is highly recommended to develop and test applications and scripts against the storage simulator plug-in to remove any logic errors before working with production systems. Testing applications and scripts on actual non-production hardware before deploying to production is also strongly encouraged if possible. The libStorageMgmt library in Red Hat Enterprise Linux 7 adds a default udev rule to handle the REPORTED LUNS DATA HAS CHANGED unit attention. When a storage configuration change has taken place, one of several Unit Attention ASC/ASCQ codes reports the change. A uevent is then generated and is rescanned automatically with sysfs . The file /lib/udev/rules.d/90-scsi-ua.rules contains example rules to enumerate other events that the kernel can generate. The libStorageMgmt library uses a plug-in architecture to accommodate differences in storage arrays. For more information on libStorageMgmt plug-ins and how to write them, see the Red Hat Developer Guide .

Commands:
Chapter 3. Supported configurations Command-line interface Red Hat Enterprise Linux 8 x86-64 and aarch64 Red Hat Enterprise Linux 9 x86-64 and aarch64 Linux x86-64 and aarch64 macOS x86-64 Windows x86-64 IBM Z and IBM LinuxONE (s390x) Router For use in Kubernetes-based sites and as a gateway for containers or machines. Red Hat Enterprise Linux 8 x86-64 and aarch64 Red Hat Enterprise Linux 9 x86-64 and aarch64 IBM Z and IBM LinuxONE (s390x) for containers. Note Red Hat Service Interconnect is not supported for standalone use as a messaging router. Red Hat Service Interconnect Operator The operator is supported with OpenShift 4.x only. OpenShift versions OpenShift 3.11 OpenShift 4.14, 4.15 and 4.16 ROSA and ARO OpenShift Container Platform and OpenShift Dedicated Installing Red Hat Service Interconnect in a disconnected network by mirroring the required components to the cluster is supported. Ingress types LoadBalancer OpenShift Routes CPU architecture x86-64, aarch64, and s390x Kubernetes distributions Red Hat provides assistance running Red Hat Service Interconnect on any CNCF-certified distribution of Kubernetes . Note, however, that Red Hat Service Interconnect is tested only on OpenShift. Ingress types Contour Nginx - This requires configuration for TLS passthrough NodePort Upgrades Red Hat supports upgrades from one downstream minor version to the , with no jumps. While Red Hat aims to have compatibility across minor versions, we recommend upgrading all sites to latest version. Note If you have applications that require long lived connections, for example Kafka clients, consider using a load balancer as ingress instead of a proxy ingress such as OpenShift route. If you use an OpenShift route as ingress, expect interruptions whenever routes are configured. For information about the latest release, see Red Hat Service Interconnect Supported Configurations .

Commands:
8.2.6. Restoration Issues While backups are a daily occurrence, restorations are normally a less frequent event. However, restorations are inevitable; they will be necessary, so it is best to be prepared. The important thing to do is to look at the various restoration scenarios detailed throughout this section and determine ways to test your ability to actually carry them out. And keep in mind that the hardest one to test is also the most critical one. 8.2.6.1. Restoring From Bare Metal The phrase "restoring from bare metal" is a system administrator's way of describing the process of restoring a complete system backup onto a computer with absolutely no data of any kind on it -- no operating system, no applications, nothing. Overall, there are two basic approaches to bare metal restorations: Reinstall, followed by restore Here the base operating system is installed just as if a brand-new computer were being initially set up. Once the operating system is in place and configured properly, the remaining disk drives can be partitioned and formatted, and all backups restored from backup media. System recovery disks A system recovery disk is bootable media of some kind (often a CD-ROM) that contains a minimal system environment, able to perform most basic system administration tasks. The recovery environment contains the necessary utilities to partition and format disk drives, the device drivers necessary to access the backup device, and the software necessary to restore data from the backup media. Note Some computers have the ability to create bootable backup tapes and to actually boot from them to start the restoration process. However, this capability is not available to all computers. Most notably, computers based on the PC architecture do not lend themselves to this approach.

Commands:
Chapter 5. Installing and configuring the Nexus Repository Manager plugin The Nexus Repository Manager plugin displays the information about your build artifacts in your Developer Hub application. The build artifacts are available in the Nexus Repository Manager. Important The Nexus Repository Manager plugin is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for 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 on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. 5.1. Installation The Nexus Repository Manager plugin is pre-loaded in Developer Hub with basic configuration properties. To enable it, set the disabled property to false as follows: global: dynamic: includes: - dynamic-plugins.default.yaml plugins: - package: ./dynamic-plugins/dist/backstage-community-plugin-nexus-repository-manager disabled: false 5.2. Configuration Set the proxy to the desired Nexus Repository Manager server in the app-config.yaml file as follows: proxy: '/nexus-repository-manager': target: 'https://<NEXUS_REPOSITORY_MANAGER_URL>' headers: X-Requested-With: 'XMLHttpRequest' # Uncomment the following line to access a private Nexus Repository Manager using a token # Authorization: 'Bearer <YOUR TOKEN>' changeOrigin: true # Change to "false" in case of using self hosted Nexus Repository Manager instance with a self-signed certificate secure: true Optional: Change the base URL of Nexus Repository Manager proxy as follows: nexusRepositoryManager: # default path is `/nexus-repository-manager` proxyPath: /custom-path Optional: Enable the following experimental annotations: nexusRepositoryManager: experimentalAnnotations: true Annotate your entity using the following annotations: metadata: annotations: # insert the chosen annotations here # example nexus-repository-manager/docker.image-name: `<ORGANIZATION>/<REPOSITORY>`,

Commands:
global: dynamic: includes: - dynamic-plugins.default.yaml plugins: - package: ./dynamic-plugins/dist/backstage-community-plugin-nexus-repository-manager disabled: false
proxy: '/nexus-repository-manager': target: 'https://<NEXUS_REPOSITORY_MANAGER_URL>' headers: X-Requested-With: 'XMLHttpRequest' # Uncomment the following line to access a private Nexus Repository Manager using a token # Authorization: 'Bearer <YOUR TOKEN>' changeOrigin: true # Change to "false" in case of using self hosted Nexus Repository Manager instance with a self-signed certificate secure: true
nexusRepositoryManager: # default path is `/nexus-repository-manager` proxyPath: /custom-path
nexusRepositoryManager: experimentalAnnotations: true
metadata: annotations: # insert the chosen annotations here # example nexus-repository-manager/docker.image-name: `<ORGANIZATION>/<REPOSITORY>`,
4.2.5. Removing Physical Volumes If a device is no longer required for use by LVM, you can remove the LVM label with the pvremove command. Executing the pvremove command zeroes the LVM metadata on an empty physical volume. If the physical volume you want to remove is currently part of a volume group, you must remove it from the volume group with the vgreduce command, as described in Section 4.3.5, "Removing Physical Volumes from a Volume Group" .

Commands:
pvremove /dev/ram15 Labels on physical volume "/dev/ram15" successfully wiped
Managing security compliance Red Hat Satellite 6.15 Plan and configure SCAP compliance policies, deploy the policies to hosts, and monitor compliance of your hosts Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
hammer scap-content list --location " My_Location " --organization " My_Organization "
hammer scap-content bulk-upload --type default
rpm2cpio scap-security-guide-0.1.69-3.el8_6.noarch.rpm | cpio -iv --to-stdout ./usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml > ssg-rhel-8.6-ds.xml
hammer scap-content bulk-upload --type directory --directory /usr/share/xml/scap/my_content/ --location " My_Location " --organization " My_Organization "
oscap info /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml | grep "WARNING" WARNING: Datastream component 'scap_org.open-scap_cref_security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2' points out to the remote 'https://access.redhat.com/security/data/oval/com.redhat.rhsa-RHEL8.xml.bz2'. Use '--fetch-remote-resources' option to download it. WARNING: Skipping 'https://access.redhat.com/security/data/oval/com.redhat.rhsa-RHEL8.xml.bz2' file which is referenced from datastream
oscap info /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml | grep "WARNING" WARNING: Datastream component 'scap_org.open-scap_cref_security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2' points out to the remote 'https://access.redhat.com/security/data/oval/com.redhat.rhsa-RHEL8.xml.bz2'. Use '--fetch-remote-resources' option to download it. WARNING: Skipping 'https://access.redhat.com/security/data/oval/com.redhat.rhsa-RHEL8.xml.bz2' file which is referenced from datastream
oscap info /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml Referenced check files: ssg-rhel8-oval.xml system: http://oval.mitre.org/XMLSchema/oval-definitions-5 ssg-rhel8-ocil.xml system: http://scap.nist.gov/schema/ocil/2 security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2 system: http://oval.mitre.org/XMLSchema/oval-definitions-5
curl -o security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2 https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL8.xml.bz2
curl -o /root/ security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2 http:// satellite.example.com /pulp/content/ My_Organization_Label /Library/custom/ My_Product_Label / My_Repo_Label / security-data-oval-com.redhat.rhsa-RHEL8.xml.bz2
failed > 5
host ~ prod- AND date > "Jan 1, 2023"
"1 hour ago" AND compliance_policy = date = "1 hour ago" AND compliance_policy = rhel7_audit
xccdf_rule_passed = xccdf_org.ssgproject.content_rule_firefox_preferences-auto-download_actions
xccdf_rule_failed = xccdf_org.ssgproject.content_rule_firefox_preferences-auto-download_actions
xccdf_rule_othered = xccdf_org.ssgproject.content_rule_firefox_preferences-auto-download_actions
4.151. libvirt-cim 4.151.1. RHBA-2011:1587 - libvirt-cim bug fix and enhancement update An updated libvirt-cim package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. The libvirt-cim package contains a Common Information Model (CIM) provider based on Common Manageability Programming Interface (CMPI). It supports most libvirt virtualization features and allows management of multiple libvirt-based platforms. Bug Fix BZ# 728245 Prior to this update, libvirt-cim contained several defects for null variables. As a result, using null variables did not work as expected. This update resolves these defects and now null variables work as expected. Enhancements BZ# 633337 With this update, libvirt-cim supports libvirt networking Access Control Lists (ACL). BZ# 712257 This update aprovides read-only access to ensure that the remote CIM access cannot modify the system state. This is useful when CIM is used only for monitoring and other software is used for virtualization management. All libvirt-cim users are advised to upgrade to this updated package, which fixes this bug and adds these enhancements.

Commands: