mtpti5iD/redhat-docs_dataset huggingface dataset:
12.4.3. Creating an LVM-based Storage Pool with virsh This section outlines the steps required to create an LVM-based storage pool with the virsh command. It uses the example of a pool named guest_images_lvm from a single drive ( /dev/sdc ). This is only an example and your settings should be substituted as appropriate. Procedure 12.3. Creating an LVM-based storage pool with virsh Define the pool name guest_images_lvm . Build the pool according to the specified name. If you are using an already existing volume group, skip this step. Initialize the new pool. Show the volume group information with the vgs command. Set the pool to start automatically. List the available pools with the virsh command. The following commands demonstrate the creation of three volumes ( volume1 , volume2 and volume3 ) within this pool. List the available volumes in this pool with the virsh command. The following two commands ( lvscan and lvs ) display further information about the newly created volumes.

Commands:
virsh pool-define-as guest_images_lvm logical - - /dev/sdc libvirt_lvm \ /dev/ libvirt_lvm Pool guest_images_lvm defined
virsh pool-build guest_images_lvm Pool guest_images_lvm built
virsh pool-start guest_images_lvm Pool guest_images_lvm started
vgs VG #PV #LV #SN Attr VSize VFree libvirt_lvm 1 0 0 wz--n- 465.76g 465.76g
virsh pool-autostart guest_images_lvm Pool guest_images_lvm marked as autostarted
virsh pool-list --all Name State Autostart ----------------------------------------- default active yes guest_images_lvm active yes
virsh vol-create-as guest_images_lvm volume1 8G Vol volume1 created virsh vol-create-as guest_images_lvm volume2 8G Vol volume2 created virsh vol-create-as guest_images_lvm volume3 8G Vol volume3 created
virsh vol-list guest_images_lvm Name Path ----------------------------------------- volume1 /dev/libvirt_lvm/volume1 volume2 /dev/libvirt_lvm/volume2 volume3 /dev/libvirt_lvm/volume3
lvscan ACTIVE '/dev/libvirt_lvm/volume1' [8.00 GiB] inherit ACTIVE '/dev/libvirt_lvm/volume2' [8.00 GiB] inherit ACTIVE '/dev/libvirt_lvm/volume3' [8.00 GiB] inherit lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert volume1 libvirt_lvm -wi-a- 8.00g volume2 libvirt_lvm -wi-a- 8.00g volume3 libvirt_lvm -wi-a- 8.00g
2.3. Deprecated Features Note This is the last Red Hat Gluster Storage release supporting Red Hat Enterprise Linux 6. Customers are adviced to upgrade to Red Hat Enterprise Linux 7 . The following features are deprecated as of Red Hat Gluster Storage 3.5, or will be considered deprecated in subsequent releases. Review individual items for details about the likely removal time frame of the feature. Gluster-NFS Gluster-NFS is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends the use of Gluster-NFS, and does not support its use in new deployments on Red Hat Gluster Storage 3.5 and above. Existing deployments that upgrade to Red Hat Gluster Storage 3.5 remain supported, but users are encouraged to migrate to NFS-Ganesha, which provides enhanced functionality, additional security features, and performance improvements detailed in Section 2.1, "What's New in this Release?" . Remote Direct Memory Access (RDMA) Using RDMA as a transport protocol is considered deprecated in Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support new deployments on Red Hat Gluster Storage 3.5. Existing deployments that upgrade to Red Hat Gluster Storage 3.5 remain supported. Tiering Tiering is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support tiering in new deployments on Red Hat Gluster Storage 3.5. Existing deployments that upgrade to Red Hat Gluster Storage 3.5 remain supported. Red Hat Enterprise Linux 6 (RHEL 6) based ISO image for RHGS server Starting with Red Hat Gluster Storage 3.5 release, Red Hat Enterprise Linux 6 based ISO image for Red Hat Gluster Storage server will no longer be included. Parallel NFS (pNFS) As of Red Hat Gluster Storage 3.4, Parallel NFS is considered unsupported and is no longer available as a Technology Preview. Several long-term issues with this feature that affect stability remain unresolved upstream. Information about using this feature has been removed from Red Hat Gluster Storage 3.4 but remains available in the documentation for releases that provided Parallel NFS as a Technology Preview. Parallel NFS (pNFS) As of Red Hat Gluster Storage 3.4, Parallel NFS is considered unsupported and is no longer available as a Technology Preview. Several long-term issues with this feature that affect stability remain unresolved upstream. Information about using this feature has been removed from Red Hat Gluster Storage 3.4 but remains available in the documentation for releases that provided Parallel NFS as a Technology Preview.

Commands:
Chapter 4. Notifications Notifications are sent to admins and members to make it easier to parse developer activity (new account). 4.1. Types of notifications There are different types of notifications: Accounts Billing Applications Service subscriptions Usage alerts 4.2. Visibility Admin users have access to all notifications. Member users have access only to notifications of the areas they have been given access to. For example, a member will only have access to notifications related to billing if they have access to the billing section. For enterprise accounts , member users will only have access to notifications regarding activity of the services they have been granted access to. 4.3. Subscribing to notifications by email Subscriptions are personal and can only be modified by the person receiving those notifications. To edit your subscriptions: Navigate to Account Settings > Personal > Notification Preferences . Select the notifications you would like to receive. Click Update Notification Preferences . 4.4. Web notifications In addition to email notifications, you can find information about the last activities in your Dashboard:

Commands:
Chapter 3. Package Namespace Change for JBoss EAP 8.0 This section provides additional information for the package namespace changes in JBoss EAP 8.0. JBoss EAP 8.0 provides full support for Jakarta EE 10 and many other implementations of the Jakarta EE 10 APIs. An important change supported by Jakarta EE 10 for JBoss EAP 8.0 is the package namespace change. 3.1. javax to jakarta Namespace change A key difference between Jakarta EE 8 and EE 10 is the renaming of the EE API Java packages from javax.* to jakarta.* . This follows the move of Java EE to the Eclipse Foundation and the establishment of Jakarta EE. Adapting to this namespace change is the biggest task of migrating an application from JBoss EAP 7 to JBoss EAP 8. To migrate applications to Jakarta EE 10, you must complete the following steps: Update any import statements or other source code uses of EE API classes from the javax package to the jakarta package. Update the names of any EE-specified system properties or other configuration properties that begin with javax to begin with jakarta . For any application-provided implementations of EE interfaces or abstract classes that are bootstrapped using the java.util.ServiceLoader mechanism, change the name of the resource that identifies the implementation class from META-INF/services/javax.[rest_of_name] to META-INF/services/jakarta.[rest_of_name] . Note The Red Hat Migration Toolkit can assist in updating the namespaces in the application source code. For more information, see How to use Red Hat Migration Toolkit for Auto-Migration of an Application to the Jakarta EE 10 Namespace . In cases where source code migration is not an option, the Open Source Eclipse Transformer project provides bytecode transformation tooling to transform existing Java archives from the javax namespace to the jakarta namespace. Note This change does not affect javax packages that are part of Java SE. Additional resources For more information, see The javax to jakarta Package Namespace Change . Revised on 2024-02-21 14:02:54 UTC

Commands:
Chapter 16. Network File System A Network File System ( NFS ) allows remote hosts to mount file systems over a network and interact with those file systems as though they are mounted locally. This enables system administrators to consolidate resources onto centralized servers on the network. [16] In Red Hat Enterprise Linux, the nfs-utils package is required for full NFS support. Enter the following command to see if the nfs-utils is installed: If it is not installed and you want to use NFS, use the yum utility as root to install it: 16.1. NFS and SELinux When running SELinux, the NFS daemons are confined by default except the nfsd process, which is labeled with the unconfined kernel_t domain type. The SELinux policy allows NFS to share files by default. Also, passing SELinux labels between a client and the server is supported, which provides better security control of confined domains accessing NFS volumes. For example, when a home directory is set up on an NFS volume, it is possible to specify confined domains that are able to access only the home directory and not other directories on the volume. Similarly, applications, such as Secure Virtualization, can set the label of an image file on an NFS volume, thus increasing the level of separation of virtual machines. The support for labeled NFS is disabled by default. To enable it, see Section 16.4.1, "Enabling SELinux Labeled NFS Support" . [16] See the Network File System (NFS) chapter in the Storage Administration Guide for more information.

Commands:
~]USD rpm -q nfs-utils package nfs-utils is not installed
~]# yum install nfs-utils
Chapter 38. Verifying the KIE Server installation Verify that KIE Server is installed correctly. Prerequisites KIE Server is installed and configured. Procedure To start KIE Server, enter one of the following commands in the JWS_HOME /tomcat/bin directory: On Linux or UNIX-based systems: USD ./startup.sh On Windows: startup.bat After a few minutes, review the files in the JWS_HOME /tomcat/logs directory and correct any errors. To verify that KIE Server is working correctly, enter http://localhost:8080/kie-server/services/rest/server in a web browser. Enter the user name and password stored in the tomcat-users.xml file.

Commands:
./startup.sh
startup.bat
probe::kprocess.release Name probe::kprocess.release - Process released Synopsis Values pid PID of the process being released task A task handle to the process being released Context The context of the parent, if it wanted notification of this process' termination, else the context of the process itself. Description Fires when a process is released from the kernel. This always follows a kprocess.exit, though it may be delayed somewhat if the process waits in a zombie state.

Commands:
kprocess.release
Chapter 1. How to read the Red Hat JBoss Enterprise Application Platform 8.0 documentation We are in the process of modernizing the Red Hat JBoss Enterprise Application Platform 8.0 documentation. We are working to create more solution-centric documentation. The JBoss EAP 8.0 documentation contains content specific to the JBoss EAP 8.0 release including new and enhanced features found in JBoss EAP 8.0. Functionality from releases that are still supported in JBoss EAP 8.0 can be accessed in the JBoss EAP 7.4 documentation set. You can access the documentation set at Product Documentation for Red Hat JBoss Enterprise Application Platform 7.4 . The following is a suggested approach for using the JBoss EAP 8.0 documentation: Read the JBoss EAP 8.0 Release notes to learn about new, enhanced, unsupported, and removed features. Read the other JBoss EAP 8.0 documentation set for detailed information about new and enhanced features. Read the JBoss EAP 8.0 Migration Guide for details on how to migrate applications to JBoss EAP 8.0. If you need information on features supported from releases that have not been enhanced in JBoss EAP 8.0, see the JBoss EAP 7.4 documentation set at Product Documentation for Red Hat JBoss Enterprise Application Platform 7.4 . For example, development and configuration guides are available in the JBoss EAP 7.4 documentation set.

Commands:
5.3.11. Splitting a Volume Group To split the physical volumes of a volume group and create a new volume group, use the vgsplit command. Logical volumes cannot be split between volume groups. Each existing logical volume must be entirely on the physical volumes forming either the old or the new volume group. If necessary, however, you can use the pvmove command to force the split. The following example splits off the new volume group smallvg from the original volume group bigvg .

Commands:
vgsplit bigvg smallvg /dev/ram15 Volume group "smallvg" successfully split from "bigvg"
Chapter 6. Monitoring and managing upgrade of the storage cluster After running the ceph orch upgrade start command to upgrade the Red Hat Ceph Storage cluster, you can check the status, pause, resume, or stop the upgrade process. The health of the cluster changes to HEALTH_WARNING during an upgrade. If the host of the cluster is offline, the upgrade is paused. Note You have to upgrade one daemon type after the other. If a daemon cannot be upgraded, the upgrade is paused. Prerequisites A running Red Hat Ceph Storage cluster 5. Root-level access to all the nodes. At least two Ceph Manager nodes in the storage cluster: one active and one standby. Upgrade for the storage cluster initiated. Procedure Determine whether an upgrade is in process and the version to which the cluster is upgrading: Example Note You do not get a message once the upgrade is successful. Run ceph versions and ceph orch ps commands to verify the new image ID and the version of the storage cluster. Optional: Pause the upgrade process: Example Optional: Resume a paused upgrade process: Example Optional: Stop the upgrade process: Example

Commands:
ceph orch upgrade status
ceph orch upgrade pause
ceph orch upgrade resume
ceph orch upgrade stop
Chapter 8. Asynchronous errata updates 8.1. RHSA-2025:0082 OpenShift Data Foundation 4.16.5 bug fixes and security updates OpenShift Data Foundation release 4.16.5 is now available. The bug fixes that are included in the update are listed in the RHSA-2025:0082 advisory. 8.2. RHSA-2024:11292 OpenShift Data Foundation 4.16.4 bug fixes and security updates OpenShift Data Foundation release 4.16.4 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:11292 advisory. 8.3. RHSA-2024:8113 OpenShift Data Foundation 4.16.3 bug fixes and security updates OpenShift Data Foundation release 4.16.3 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:8113 advisory. 8.4. RHSA-2024:6755 OpenShift Data Foundation 4.16.2 bug fixes and security updates OpenShift Data Foundation release 4.16.2 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:6755 advisory. 8.5. RHSA-2024:5547 OpenShift Data Foundation 4.16.1 bug fixes and security updates OpenShift Data Foundation release 4.16.1 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:5547 advisory.

Commands:
14.5.2. Connecting the Serial Console for the Guest Virtual Machine The USD virsh console <domain> [--devname <string>] [--force] [--safe] command connects the virtual serial console for the guest virtual machine. The optional --devname <string> parameter refers to the device alias of an alternate console, serial, or parallel device configured for the guest virtual machine. If this parameter is omitted, the primary console will be opened. The --force option will force the console connection or when used with disconnect, will disconnect connections. Using the --safe option will only allow the guest to connect if safe console handling is supported.

Commands:
virsh console virtual_machine --safe
Chapter 1. Introduction As OpenStack consists of many different projects, it is important to test the interoperability of the projects within your OpenStack cluster. The OpenStack Integration Test Suite (tempest) automates the integration testing of your Red Hat OpenStack Platform deployment. Running tests ensures that your cluster is working as expected, and can also provide early warning of potential problems, especially after an upgrade. The Integration Test Suite contains tests for OpenStack API validation and scenario testing, as well as unit testing for self-validation. The Integration Test Suite performs black box testing using the OpenStack public APIs, with tempest as the test runner.

Commands:
Chapter 4. Using domain-specific LDAP backends with director Red Hat OpenStack Platform director can configure keystone to use one or more LDAP backends. This approach results in the creation of a separate LDAP backend for each keystone domain. 4.1. Setting the configuration options For deployments using Red Hat OpenStack Platform director, you need to set the KeystoneLDAPDomainEnable flag to true in your heat templates; as a result, this will configure the domain_specific_drivers_enabled option in keystone (within the identity configuration group). Note The default directory for domain configuration files is set to /etc/keystone/domains/ . You can override this by setting the required path using the keystone::domain_config_directory hiera key and adding it as an ExtraConfig parameter within an environment file. You must also add a specification of the LDAP backend configuration. This is done using the KeystoneLDAPBackendConfigs parameter in tripleo-heat-templates , where you can then specify your required LDAP options. 4.2. Configure the director deployment Create a copy of the keystone_domain_specific_ldap_backend.yaml environment file: Edit the /home/stack/templates/keystone_domain_specific_ldap_backend.yaml environment file and set the values to suit your deployment. For example, these entries create a LDAP configuration for a keystone domain named testdomain : You can also configure the environment file to specify multiple domains. For example: This will result in two domains named domain1 and domain2 ; each will have a different LDAP domain with its own configuration.

Commands:
cp /usr/share/openstack-tripleo-heat-templates/environments/services/keystone_domain_specific_ldap_backend.yaml /home/stack/templates/
parameter_defaults: KeystoneLDAPDomainEnable: true KeystoneLDAPBackendConfigs: testdomain: url: ldaps://192.0.2.250 user: cn=openstack,ou=Users,dc=director,dc=example,dc=com password: RedactedComplexPassword suffix: dc=director,dc=example,dc=com user_tree_dn: ou=Users,dc=director,dc=example,dc=com user_filter: "(memberOf=cn=OSuser,ou=Groups,dc=director,dc=example,dc=com)" user_objectclass: person user_id_attribute: cn
KeystoneLDAPBackendConfigs: domain1: url: ldaps://domain1.example.com user: cn=openstack,ou=Users,dc=director,dc=example,dc=com password: RedactedComplexPassword domain2: url: ldaps://domain2.example.com user: cn=openstack,ou=Users,dc=director,dc=example,dc=com password: RedactedComplexPassword
4.362. yaboot 4.362.1. RHBA-2011:1767 - yaboot bug fix update An updated yaboot package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The yaboot package provides a boot loader for Open Firmware based PowerPC systems. It can be used to boot IBM eServer System p machines. Bug Fixes BZ# 638654 Previously, yaboot could not check whether an IP address is valid. As a consequence, yaboot netboot failed to operate in an environment where the gateway was not the same as the 'tftp' server, even though the 'tftp' server was on the same subnet. With this update, an IP address validity check has been added. Now,yaboot netbot operates as expected. BZ# 746340 Previously, yaboot discarded passed parameters to anaconda after the Client Architecture Support (CAS) was rebooted. This update upgrades the yaboot binary and modifies the source file. Now, the parameters are passed to the anaconda installer as expected. All users of yaboot are advised to upgrade to this updated package, which fixes these bugs.

Commands:
4.2.4. Hard Drives All the technologies discussed so far are volatile in nature. In other words, data contained in volatile storage is lost when the power is turned off. Hard drives, on the other hand, are non-volatile -- the data they contain remains there, even after the power is removed. Because of this, hard drives occupy a special place in the storage spectrum. Their non-volatile nature makes them ideal for storing programs and data for longer-term use. Another unique aspect to hard drives is that, unlike RAM and cache memory, it is not possible to execute programs directly when they are stored on hard drives; instead, they must first be read into RAM. Also different from cache and RAM is the speed of data storage and retrieval; hard drives are at least an order of magnitude slower than the all-electronic technologies used for cache and RAM. The difference in speed is due mainly to their electromechanical nature. There are four distinct phases taking place during each data transfer to or from a hard drive. The following list illustrates these phases, along with the time it would take a typical high-performance drive, on average, to complete each: Access arm movement (5.5 milliseconds) Disk rotation (.1 milliseconds) Heads reading/writing data (.00014 milliseconds) Data transfer to/from the drive's electronics (.003 Milliseconds) Of these, only the last phase is not dependent on any mechanical operation. Note Although there is much more to learn about hard drives, disk storage technologies are discussed in more depth in Chapter 5, Managing Storage . For the time being, it is only necessary to keep in mind the huge speed difference between RAM and disk-based technologies and that their storage capacity usually exceeds that of RAM by a factor of at least 10, and often by 100 or more.

Commands:
4.145. libsndfile 4.145.1. RHBA-2011:1226 - libsndfile bug fix update An updated libsndfile package that fixes one bug is now available for Red Hat Enterprise Linux 6. The libsndfile package provides a library for reading and writing sound files. Bug Fix BZ# 664323 Prior to this update, the libsndfile package was built without the Ogg container format support. As a result, applications using the libsndfile library were not able to work with the Ogg format. With this update, the problem has been fixed so that applications can now work with the Ogg format as expected. All users of libsndfile are advised to upgrade to this updated package, which fixes this bug.

Commands:
8.219. talk 8.219.1. RHBA-2013:1148 - talk bug fix update Updated talk packages that fix one bug are now available for Red Hat Enterprise Linux 6. The talk utility is a communication program that copies lines from one terminal to the terminal of another user. Bug Fix BZ#691355 The talk utility allows a user to specify the target user in the "username.hostname" form. Consequent to this, versions of the utility did not support usernames that contained a period. With this update, a new command line option (that is, "-x") has been added to enforce the use of the "username@hostname" form, so that the username can contain periods. As well, the corresponding manual page has been extended to provide a complete list of supported command line arguments. Users of talk are advised to upgrade to these updated packages, which fix this bug.

Commands:
function::print_syms Name function::print_syms - Print out kernel stack from string Synopsis Arguments callers String with list of hexadecimal (kernel) addresses Description This function performs a symbolic lookup of the addresses in the given string, which are assumed to be the result of prior calls to stack , callers , and similar functions. Prints one line per address, including the address, the name of the function containing the address, and an estimate of its position within that function, as obtained by symdata . Returns nothing.

Commands:
print_syms(callers:string)