mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Selecting a system-wide archive Red Hat build of OpenJDK version If you have multiple versions of Red Hat build of OpenJDK installed with the archive on RHEL 8, you can select a specific Red Hat build of OpenJDK version to use system-wide. Prerequisites Know the locations of the Red Hat build of OpenJDK versions installed using the archive. Procedure To specify the Red Hat build of OpenJDK version to use for a single session: Configure JAVA_HOME with the path to the Red Hat build of OpenJDK version you want used system-wide. USD export JAVA_HOME=/opt/jdk/jdk-1.8.0 Add USDJAVA_HOME/bin to the PATH environment variable. USD export PATH="USDJAVA_HOME/bin:USDPATH" To specify the Red Hat build of OpenJDK version to use permanently for a single user, add these commands into ~/.bashrc : To specify the Red Hat build of OpenJDK version to use permanently for all users, add these commands into /etc/bashrc : Note If you do not want to redefine JAVA_HOME , add only the PATH command to bashrc , specifying the path to the Java binary. For example, export PATH="/opt/jdk/jdk-1.8.0/bin:USDPATH" Additional resources For more information about the exact meaning of JAVA_HOME , see Changes/Decouple system java setting from java command setting .

Commands:
export JAVA_HOME=/opt/jdk/jdk-1.8.0 export PATH="USDJAVA_HOME/bin:USDPATH"
export JAVA_HOME=/opt/jdk/jdk-1.8.0 export PATH="USDJAVA_HOME/bin:USDPATH"
Chapter 1. Overview Ceph Object Gateway, also known as RADOS Gateway (RGW) is an object storage interface built on top of librados to provide applications with a RESTful gateway to Ceph storage clusters. Ceph object gateway supports two interfaces: S3-compatible: Provides object storage functionality with an interface that is compatible with a large subset of the Amazon S3 RESTful API. Swift-compatible: Provides object storage functionality with an interface that is compatible with a large subset of the OpenStack Swift API. The Ceph object gateway is a server for interacting with a Ceph storage cluster. Since it provides interfaces compatible with OpenStack Swift and Amazon S3, the Ceph object gateway has its own user management. Ceph object gateway can store data in the same Ceph storage cluster used to store data from Ceph block device clients; however, it would involve separate pools and likely a different CRUSH hierarchy. The S3 and Swift APIs share a common namespace, so you may write data with one API and retrieve it with the other. Warning Do not use RADOS snapshots on pools used by RGW. Doing so can introduce undesirable data inconsistencies.

Commands:
7.226. setroubleshoot 7.226.1. RHBA-2013:0387 - setroubleshoot bug fix update Updated setroubleshoot packages that fix several bugs are now available for Red Hat Enterprise Linux 6. This package provides a set of analysis plugins for use with setroubleshoot. Each plugin has the capacity to analyze SELinux AVC (Access Vector Cache) data and system data to provide user friendly reports describing how to interpret SELinux AVC denial messages. Bug Fixes BZ# 788196 Prior to this update, the "sealert -a /var/log/audit/audit.log -H" command did not work correctly. When opening the audit.log file, the sealert utility returned an error when the "-H" option was used. The relevant source code has been modified and the "-H" sealert option is no longer recognized as a valid option. BZ#832143 Previously, SELinux Alert Browser did not display alerts even if SELinux denial messages were present. This was caused by the sedispatch utility, which did not handle audit messages correctly, and users were not able to fix their SELinux issues according to the SELinux alerts. Now, SELinux Alert Browser properly alerts the user in the described scenario. BZ#842445 Under certain circumstances, sealert produced the " 'tuple' object has no attribute 'split' " error message. A patch has been provided to fix this bug. As a result, sealert no longer returns this error message. BZ# 851824 The sealert utility returned parse error messages if an alert description contained parentheses. With this update, sealert has been fixed and now, the error messages are no longer returned in the described scenario. BZ# 864429 Previously, improper documentation content was present in files located in the /usr/share/doc/setroubleshoot/ directory. This update removes certain unneeded files and fixes content of others. Users of setroubleshoot are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Release Notes and Known Issues Red Hat CodeReady Workspaces 2.15 Release Notes and Known Issues for Red Hat CodeReady Workspaces 2.15 Robert Kratky rkratky@redhat.com Fabrice Flore-Thebault ffloreth@redhat.com Jana Vrbkova jvrbkova@redhat.com Max Leonov mleonov@redhat.com Red Hat Developer Group Documentation Team devtools-docs@redhat.com

Commands:
Chapter 1. Updating Red Hat Enterprise Linux AI Red Hat Enterprise Linux AI allows you to update your instance so you can use the latest version of RHEL AI and InstructLab. 1.1. Updating your RHEL AI instance You can update your instance to use the latest version of RHEL AI and InstructLab Prerequisets You installed and deployed a Red Hat Enterprise Linux AI instance on one of the supported platforms. You created a Red Hat registry account. Procedure Log into your Red Hat registry account with the podman command: USD sudo podman login registry.redhat.io --username <user-name> --password <user-password> --authfile /etc/ostree/auth.json Or you can log in with the skopeo command: USD sudo skopeo login registry.redhat.io --username <user-name> --password <user-password> --authfile /etc/ostree/auth.json Upgrading to a minor version of Red Hat Enterprise Linux AI You can upgrade your instance to use the latest version of Red Hat Enterprise Linux AI by running the following command: USD sudo bootc switch <latest-rhelai-image> where <path-to-latest-image> Specify the latest version of the RHEL AI image. Example command USD sudo bootc switch registry.redhat.io/rhelai1/bootc-nvidia-rhel9:1.2 Restart your system by running the following command: USD sudo reboot -n Upgrading to a z-stream version of Red Hat Enterprise Linux AI If a z-stream exists, you can upgrade your system to a z-stream version of RHEL AI by running the folllowing command: USD sudo bootc upgrade --apply

Commands:
sudo podman login registry.redhat.io --username <user-name> --password <user-password> --authfile /etc/ostree/auth.json
sudo skopeo login registry.redhat.io --username <user-name> --password <user-password> --authfile /etc/ostree/auth.json
sudo bootc switch <latest-rhelai-image>
sudo bootc switch registry.redhat.io/rhelai1/bootc-nvidia-rhel9:1.2
sudo reboot -n
sudo bootc upgrade --apply
8.2.6. Other Interfaces Other common interface configuration files include the following: ifcfg-lo - A local loopback interface is often used in testing, as well as being used in a variety of applications that require an IP address pointing back to the same system. Any data sent to the loopback device is immediately returned to the host's network layer. Warning Never edit the loopback interface script, /etc/sysconfig/network-scripts/ifcfg-lo , manually. Doing so can prevent the system from operating correctly. ifcfg-irlan0 - An infrared interface allows information between devices, such as a laptop and a printer, to flow over an infrared link. This works in a similar way to an Ethernet device except that it commonly occurs over a peer-to-peer connection. ifcfg-plip0 - A Parallel Line Interface Protocol (PLIP) connection works much the same way as an Ethernet device, except that it utilizes a parallel port. ifcfg-tr0 - Token Ring topologies are not as common on Local Area Networks ( LANs ) as they once were, having been eclipsed by Ethernet.

Commands:
5.3.3. Splitting the Volume Group To create the new volume group yourvg , use the vgsplit command to split the volume group myvg . Before you can split the volume group, the logical volume must be inactive. If the file system is mounted, you must unmount the file system before deactivating the logical volume. You can deactivate the logical volumes with the lvchange command or the vgchange command. The following command deactivates the logical volume mylv and then splits the volume group yourvg from the volume group myvg , moving the physical volume /dev/sdc1 into the new volume group yourvg . You can use the vgs command to see the attributes of the two volume groups.

Commands:
lvchange -a n /dev/myvg/mylv vgsplit myvg yourvg /dev/sdc1 Volume group "yourvg" successfully split from "myvg"
vgs VG #PV #LV #SN Attr VSize VFree myvg 2 1 0 wz--n- 34.30G 10.80G yourvg 1 0 0 wz--n- 17.15G 17.15G
Chapter 3. Red Hat build of OpenJDK 11.0.20.1 release notes Review the following release notes for an overview of the changes from the Red Hat build of OpenJDK 11.0.20.1 patch release. Note For all the other changes and security fixes, see OpenJDK 11.0.20.1 Released . Fixed Invalid CEN header error on valid .zip files Red Hat build of OpenJDK 11.0.20 introduced additional validation checks on the ZIP64 fields of .zip files (JDK-8302483). However, these additional checks caused validation failures on some valid .zip files with the following error message: Invalid CEN header (invalid zip64 extra data field size) . To fix this issue, Red Hat build of OpenJDK 11.0.20.1 supports zero-length headers and the additional padding that some ZIP64 creation tools produce. From Red Hat build of OpenJDK 11.0.20 onward, you can disable these checks by setting the jdk.util.zip.disableZip64ExtraFieldValidation system property to true . See JDK-8313765 (JDK Bug System) Increased default value of jdk.jar.maxSignatureFileSize system property Red Hat build of OpenJDK 11.0.20 introduced a jdk.jar.maxSignatureFileSize system property for configuring the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file ( JDK-8300596 ). By default, the jdk.jar.maxSignatureFileSize property was set to 8000000 bytes (8 MB), which was too small for some JAR files. Red Hat build of OpenJDK 11.0.20.1 increases the default value of the jdk.jar.maxSignatureFileSize property to 16000000 bytes (16 MB). See JDK-8313216 (JDK Bug System) Fixed NullPointerException when handling null addresses In Red Hat build of OpenJDK 11.0.20, when the serviceability agent encountered null addresses while generating thread dumps, the serviceability agent produced a NullPointerException . Red Hat build of OpenJDK 11.0.20.1 handles null addresses appropriately. See JDK-8243210 (JDK Bug System) Advisories related to Red Hat build of OpenJDK 11.0.20.1 The following advisories have been issued about bug fixes and CVE fixes included in this release: RHBA-2023:5225 RHBA-2023:5227 RHBA-2023:5229

Commands:
Chapter 1. Introduction Monitoring tools are an optional suite of tools designed to help operators maintain an OpenStack environment. The tools perform the following functions: Centralized logging: Allows you gather logs from all components in the OpenStack environment in one central location. You can identify problems across all nodes and services, and optionally, export the log data to Red Hat for assistance in diagnosing problems. Availability monitoring: Allows you to monitor all components in the OpenStack environment and determine if any components are currently experiencing outages or are otherwise not functional. You can also configure the system to alert you when problems are identified.

Commands:
6.5. Shadow Passwords In multiuser environments it is very important to use shadow passwords (provided by the shadow-utils package). Doing so enhances the security of system authentication files. For this reason, the installation program enables shadow passwords by default. The following lists the advantages pf shadow passwords have over the traditional way of storing passwords on UNIX-based systems: Improves system security by moving encrypted password hashes from the world-readable /etc/passwd file to /etc/shadow , which is readable only by the root user. Stores information about password aging. Allows the use the /etc/login.defs file to enforce security policies. Most utilities provided by the shadow-utils package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the /etc/shadow file, any commands which create or modify password aging information do not work. The following is a list of commands which do not work without first enabling shadow passwords: chage gpasswd /usr/sbin/usermod -e or -f options /usr/sbin/useradd -e or -f options

Commands:
Chapter 18. Post-installation security hardening RHEL is designed with robust security features enabled by default. However, you can enhance its security further through additional hardening measures. For more information about: Installing security updates and displaying additional details about the updates to keep your RHEL systems secured against newly discovered threats and vulnerabilities, see Managing and monitoring security updates . Processes and practices for securing RHEL servers and workstations against local and remote intrusion, exploitation, and malicious activity, see Security hardening . Control how users and processes interact with the files on the system or control which users can perform which actions by mapping them to specific SELinux confined users, see Using SELinux . Tools and techniques to improve the security of your networks and lower the risks of data breaches and intrusions, see Securing networks . Packet filters, such as firewalls, that use rules to control incoming, outgoing, and forwarded network traffic, see Using and configuring firewalld and Getting started with nftables .

Commands:
Chapter 1. High availability services Red Hat OpenStack Platform (RHOSP) employs several technologies to provide the services required to implement high availability (HA). Service types Core container Core container services are Galera , RabbitMQ , Redis , and HAProxy . These services run on all Controller nodes and require specific management and constraints for the start, stop and restart actions. You use Pacemaker to launch, manage, and troubleshoot core container services. Note RHOSP uses the MariaDB Galera Cluster to manage database replication. Active-passive Active-passive services run on one Controller node at a time, and include services such as openstack-cinder-volume . To move an active-passive service, you must use Pacemaker to ensure that the correct stop-start sequence is followed. Systemd and plain container Systemd and plain container services are independent services that can withstand a service interruption. Therefore, if you restart a high availability service such as Galera, you do not need to manually restart any other service, such as nova-api . You can use systemd or Podman to directly manage systemd and plain container services. When orchestrating your HA deployment with the director, the director uses templates and Puppet modules to ensure that all services are configured and launched correctly. In addition, when troubleshooting HA issues, you must interact with services in the HA framework using the podman command or the systemctl command. Service modes HA services can run in one of the following modes: Active-active : Pacemaker runs the same service on multiple Controller nodes, and uses HAProxy to distribute traffic across the nodes or to a specific Controller with a single IP address. In some cases, HAProxy distributes traffic to active-active services with Round Robin scheduling. You can add more Controller nodes to improve performance. Active-passive : Services that are unable to run in active-active mode must run in active-passive mode. In this mode, only one instance of the service is active at a time. For example, HAProxy uses stick-table options to direct incoming Galera database connection requests to a single back-end service. This helps prevent too many simultaneous connections to the same data from multiple Galera nodes.

Commands:
8.206. ruby 8.206.1. RHBA-2014:1470 - ruby bug fix and enhancement update Updated ruby packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. Ruby is an extensible, interpreted, object-oriented scripting language. It has features to process text files and to do system management tasks. This update also fixes the following bugs: Note The ruby package has been upgraded to upstream version 1.8.7, which provides a number of bug fixes and enhancements over the version. (BZ# 830098 ) This update also fixes the following bugs: Bug Fixes BZ# 784766 The Tracer module introduced with SystemTap probes in a release of the ruby package collided with native Tracer class implemented in Ruby. Consequently, when using Ruby with debugger or tracer, the following exception was raised: /usr/lib/ruby/1.8/tracer.rb:16: Tracer is not a class (TypeError) With this update, the Tracer module has been renamed to SystemTap, or DTrace alternatively. To apply this fix, instances of the Tracer.fire method should be changed to SystemTap.fire or DTrace.fire in previously written Ruby code. BZ# 802946 Prior to this update, ruby failed to start a SSL server in FIPS mode due to usage of a forbidden MD5 algorithm. With this update, MD5 has been replaced by SHA256, thus fixing this bug. BZ# 997886 , BZ# 1033864 Due to changes in OpenSSL configuration options, the ruby package was not compatible with builds of OpenSSL that have enabled support for Elliptic Curve Cryptography (ECC) introduced in Red Hat Enterprise Linux 6. Consequently, ruby failed to build. This update enables ECC support in Ruby, thus fixing the build problem. The ruby package has been upgraded to upstream version 1.8.7, which provides a number of bug fixes and enhancements over the version. (BZ#830098) All ruby users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

Commands:
Chapter 2. Resource Adapter Development 2.1. Developing Custom Adapters For situations in which an existing JCA Adapter (or other connector mechanism) is not suitable, Red Hat JBoss Data Virtualization provides a framework for developing custom JCA Adapters. Red Hat JBoss Data Virtualization uses standard JCA Adapters. Base classes for all of the required supporting JCA SPI (Service Provider Interface) classes are provided by the Red Hat JBoss Data Virtualization API. The JCA CCI (Common Client Interface) support is not provided because Red Hat JBoss Data Virtualization uses the translator API as its common client interface. Note If you are not familiar with the JCA API, read the JCA 1.5 Specification at http://docs.oracle.com/cd/E15523_01/integration.1111/e10231/intro.htm . The process for developing a Red Hat JBoss Data Virtualization JCA Adapter is as follows (the required classes can be found in org.teiid.resource.spi ): Define a Managed Connection Factory by extending the BasicManagedConnectionFactory class Define a Connection Factory by extending the BasicConnectionFactory class Define a Connection by extending the BasicConnection class Specify configuration properties in an ra.xml file Note The examples contained in this book are simplified and do not include support for transactions or security which would add significant complexity. For sample resource adapter code, see the teiid/connectors directory of the Red Hat JBoss Data Virtualization 6.4 Source Code ZIP file. This ZIP file can be downloaded from the Red Hat Customer Portal at https://access.redhat.com .

Commands:
16.3. Tiering Limitations (Deprecated) Warning 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 and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. The following limitations apply to the use Tiering feature: Native client support for tiering is limited to Red Hat Enterprise Linux version 6.7, 6.8 and 7.x clients. Tiered volumes cannot be mounted by Red Hat Enterprise Linux 5.x clients. Tiering works only with cache friendly workloads. Attaching a tier volume to a cache unfriendly workload will lead to slow performance. In a cache friendly workload, most of the reads and writes are accessing a subset of the total amount of data. And, this subset fits on the hot tier. This subset should change only infrequently. Tiering feature is supported only on Red Hat Enterprise Linux 7 based Red Hat Gluster Storage. Tiering feature is not supported on Red Hat Enterprise Linux 6 based Red Hat Gluster Storage. Only Fuse and gluster-nfs access is supported. Server Message Block (SMB) and nfs-ganesha access to tiered volume is not supported. Creating snapshot of a tiered volume is supported. Snapshot clones are not supported with the tiered volumes. When you run tier detach commit or tier detach force , ongoing I/O operations may fail with a Transport endpoint is not connected error. Files with hardlinks and softlinks are not migrated. Files on which POSIX locks has been taken are not migrated until all locks are released. Add brick, remove brick, and rebalance operations are not supported on the tiered volume. For information on expanding a tiered volume, see Section 11.7.1, "Expanding a Tiered Volume" and for information on shrinking a tiered volume, see Section 11.8.2, "Shrinking a Tiered Volume "

Commands:
Chapter 1. Introduction Past versions of Red Hat OpenStack Platform used services managed with Systemd. However, more recent version of OpenStack Platform now use containers to run services. Some administrators might not have a good understanding of how containerized OpenStack Platform services operate, and so this guide aims to help you understand OpenStack Platform container images and containerized services. This includes: How to obtain and modify container images How to manage containerized services in the overcloud Understanding how containers differ from Systemd services The main goal is to help you gain enough knowledge of containerized OpenStack Platform services to transition from a Systemd-based environment to a container-based environment. 1.1. Containerized Services and Kolla Each of the main Red Hat OpenStack Platform services run in containers. This provides a method of keep each service within its own isolated namespace separated from the host. This means: The deployment of services is performed by pulling container images from the Red Hat Custom Portal and running them. The management functions, like starting and stopping services, operate through the podman command. Upgrading containers require pulling new container images and replacing the existing containers with newer versions. Red Hat OpenStack Platform uses a set of containers built and managed with the kolla toolset.

Commands: