mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. OS/JVM certifications This release is supported for use with the following operating system and Java Development Kit (JDK) versions: Operating System Chipset Architecture Java Virtual Machine Red Hat Enterprise Linux 9 x86_64 Red Hat build of OpenJDK 11 Red Hat build of OpenJDK 17 Red Hat build of OpenJDK 21 Oracle JDK 11 Oracle JDK 17 Oracle JDK 21 Red Hat Enterprise Linux 8 x86_64 Red Hat build of OpenJDK 11 Red Hat build of OpenJDK 17 Red Hat build of OpenJDK 21 Oracle JDK 11 Oracle JDK 17 Oracle JDK 21 Microsoft Windows 2019 Server x86_64 Red Hat build of OpenJDK 11 Red Hat build of OpenJDK 17 Red Hat build of OpenJDK 21 Oracle JDK 11 Oracle JDK 17 Oracle JDK 21 Note Red Hat Enterprise Linux 7 and Microsoft Windows 2016 Server are not supported.

Commands:
Chapter 42. Importing projects from Git repositories Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created. Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is embedded in Business Central. If you have projects in other Git repositories, you can import those projects into the Business Central Git repository through Business Central spaces. Prerequisites Red Hat Process Automation Manager projects exist in an external Git repository. You have the credentials required for read access to that external Git repository. Procedure In Business Central, click Menu Design Projects . Select or create the space into which you want to import the projects. The default space is MySpace . To import a project, do one of the following: Click Import Project . Select Import Project from the drop-down list. In the Import Project window, enter the URL and credentials for the Git repository that contains the projects that you want to import and click Import . The projects are added to the Business Central Git repository and are available from the current space.

Commands:
Chapter 2. Performance tuning quick start You can tune your Satellite Server based on expected host counts and hardware allocation by using built-in tuning profiles included in Satellite that are available by using the installation routine's tuning flag. For more information, see Tuning Satellite Server with Predefined Profiles in Installing Satellite Server in a connected network environment . There are four sizes provided based on estimates of the number of hosts your Satellite manages. You can find the specific tuning settings for each profile in the configuration files contained in /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes . Name Number of hosts Recommend RAM Recommend Cores default 0 - 5000 20 GiB 4 medium 5000 - 10000 32 GiB 8 large 10000 - 20000 64 GiB 16 extra-large 20000 - 60000 128 GiB 32 extra-extra-large 60000+ 256 GiB+ 48+ Procedure Select an installation size: default , medium , large , extra-large , or extra-extra-large . The default value is default . Run satellite-installer : Optional: Run a health check. For more information, see Section 5.1, "Applying configurations" . Optional: Tune the Ruby app server directly by using the Puma Tuning section. For more information, see Section 5.2, "Puma tunings" .

Commands:
satellite-installer --tuning " My_Installation_Size "
Chapter 18. Concurrent Versioning System The Concurrent Versioning System (CVS) is a free revision-control system. It is used to monitor and keep track of modifications to a central set of files which are usually accessed by several different users. It is commonly used by programmers to manage a source code repository and is widely used by open source developers. In Red Hat Enterprise Linux, the cvs package provides CVS. Enter the following command to see if the cvs package is installed: If it is not installed and you want to use CVS, use the yum utility as root to install it: 18.1. CVS and SELinux The cvs daemon runs labeled with the cvs_t type. By default in Red Hat Enterprise Linux, CVS is only allowed to read and write certain directories. The label cvs_data_t defines which areas cvs has read and write access to. When using CVS with SELinux, assigning the correct label is essential for clients to have full access to the area reserved for CVS data.

Commands:
~]USD rpm -q cvs package cvs is not installed
~]# yum install cvs
Appendix A. List of tickets by component Bugzilla and JIRA tickets are listed in this document for reference. The links lead to the release notes in this document that describe the tickets. Component Tickets Hypervisor Jira:KATA-1376 Sandboxed Containers Jira:HCIDOCS-557 kata-agent Jira:KATA-1376 kata-containers Jira:KATA-3193 podvm-builder Jira:KATA-3462 , Jira:KATA-3478 , Jira:KATA-3480 sandboxed-containers Jira:KATA-2030 , Jira:KATA-2579

Commands:
1.5. DM-Multipath Setup Overview DM-Multipath includes compiled-in default settings that are suitable for common multipath configurations. Setting up DM-multipath is often a simple procedure. The basic procedure for configuring your system with DM-Multipath is as follows: Install the device-mapper-multipath rpm. Create the configuration file and enable multipathing with the mpathconf command. You can also start the multipath daemon with this command if you do not need to edit the configuration file. If necessary, edit the multipath.conf configuration file to modify default values and save the updated file. Start the multipath daemon. For detailed setup instructions for multipath configuration see Chapter 3, Setting Up DM-Multipath .

Commands:
19.6. Configuring a Kerberos 5 Client Setting up a Kerberos 5 client is less involved than setting up a server. At a minimum, install the client packages and provide each client with a valid krb5.conf configuration file. Kerberized versions of rsh and rlogin also requires some configuration changes. Be sure that time synchronization is in place between the Kerberos client and the KDC. Refer to Section 19.5, "Configuring a Kerberos 5 Server" for more information. In addition, verify that DNS is working properly on the Kerberos client before configuring the Kerberos client programs. Install the krb5-libs and krb5-workstation packages on all of the client machines. Supply a valid /etc/krb5.conf file for each client (usually this can be the same krb5.conf file used by the KDC). Before a workstation in the realm can allow users to connect using kerberized rsh and rlogin , that workstation must have the xinetd package installed and have its own host principal in the Kerberos database. The kshd and klogind server programs also need access to the keys for their service's principal. Using kadmin , add a host principal for the workstation on the KDC. The instance in this case is the hostname of the workstation. Use the -randkey option for the kadmin 's addprinc command to create the principal and assign it a random key: Now that the principal has been created, keys can be extracted for the workstation by running kadmin on the workstation itself , and using the ktadd command within kadmin : To use other kerberized network services, they must first be started. Below is a list of some common kerberized services and instructions about enabling them: rsh and rlogin - To use the kerberized versions of rsh and rlogin , enable klogin , eklogin , and kshell . Telnet - To use kerberized Telnet, krb5-telnet must be enabled. FTP - To provide FTP access, create and extract a key for the principal with a root of ftp . Be certain to set the instance to the fully qualified hostname of the FTP server, then enable gssftp . IMAP - To use a kerberized IMAP server, the cyrus-imap package uses Kerberos 5 if it also has the cyrus-sasl-gssapi package installed. The cyrus-sasl-gssapi package contains the Cyrus SASL plugins which support GSS-API authentication. Cyrus IMAP should function properly with Kerberos as long as the cyrus user is able to find the proper key in /etc/krb5.keytab , and the root for the principal is set to imap (created with kadmin ). The dovecot package also contains an IMAP server alternative to cyrus-imap , which is also included with Red Hat Enterprise Linux, but does not support GSS-API and Kerberos to date. CVS - To use a kerberized CVS server, gserver uses a principal with a root of cvs and is otherwise identical to the CVS pserver . For details about how to enable services, refer to the chapter titled Controlling Access to Services in the System Administrators Guide .

Commands:
addprinc -randkey host/ blah.example.com
ktadd -k /etc/krb5.keytab host/ blah.example.com
4.8. Virtualization Red Hat Enterprise Linux 6.6 Hosted as a Generation 2 Virtual Machine As a Technology Preview, Red Hat Enterprise Linux 6.6 can be used as a generation 2 virtual machine in the Microsoft Hyper-V Server 2012 R2 host. In addition to the functions supported in the generation, generation 2 provides new functions on a virtual machine; for example: boot from a SCSI virtual hard disk, and UEFI firmware support.

Commands:
3.3. Configuring Storage Devices By default, DM Multipath includes support for the most common storage arrays that themselves support DM Multipath. For information on the default configuration value, including supported devices, run either of the following commands. If you need to add a storage device that is not supported by default as a known multipath device, edit the /etc/multipath.conf file and insert the appropriate device information. For example, to add information about the HP Open-V series the entry looks like this. This example sets the device to queue for a minute (or 12 retries and 5 seconds per retry) after all paths have failed. For more information on the devices section of the configuration file, see Section 4.5, "Configuration File Devices" .

Commands:
multipathd show config multipath -t
devices { device { vendor "HP" product "OPEN-V" no_path_retry 12 } }
Chapter 1. About specialized hardware and driver enablement The Driver Toolkit (DTK) is a container image in the OpenShift Container Platform payload which is meant to be used as a base image on which to build driver containers. The Driver Toolkit image contains the kernel packages commonly required as dependencies to build or install kernel modules as well as a few tools needed in driver containers. The version of these packages will match the kernel version running on the RHCOS nodes in the corresponding OpenShift Container Platform release. Driver containers are container images used for building and deploying out-of-tree kernel modules and drivers on container operating systems such as Red Hat Enterprise Linux CoreOS (RHCOS). Kernel modules and drivers are software libraries running with a high level of privilege in the operating system kernel. They extend the kernel functionalities or provide the hardware-specific code required to control new devices. Examples include hardware devices like field-programmable gate arrays (FPGA) or graphics processing units (GPU), and software-defined storage solutions, which all require kernel modules on client machines. Driver containers are the first layer of the software stack used to enable these technologies on OpenShift Container Platform deployments.

Commands:
1.5. Persistence and Firewall Marks In certain situations, it may be desirable for a client to reconnect repeatedly to the same real server, rather than have a Load Balancer Add-On load balancing algorithm send that request to the best available server. Examples of such situations include multi-screen web forms, cookies, SSL, and FTP connections. In these cases, a client may not work properly unless the transactions are being handled by the same server to retain context. Load Balancer Add-On provides two different features to handle this: persistence and firewall marks . 1.5.1. Persistence When enabled, persistence acts like a timer. When a client connects to a service, Load Balancer Add-On remembers the last connection for a specified period of time. If that same client IP address connects again within that period, it is sent to the same server it connected to previously - bypassing the load-balancing mechanisms. When a connection occurs outside the time window, it is handled according to the scheduling rules in place. Persistence also allows the administrator to specify a subnet mask to apply to the client IP address test to control which addresses have a higher level of persistence, thereby grouping connections to that subnet. Grouping connections destined for different ports can be important for protocols which use more than one port to communicate, such as FTP. However, persistence is not the most efficient way to deal with the problem of grouping together connections destined for different ports. For these situations, it is best to use firewall marks .

Commands:
Chapter 2. User Interfaces There are different interfaces for managing certificates and subsystems, depending on the user's role: administrators, agents, auditors, and end users. 2.1. User Interfaces Overview Administrators can use the following interfaces to securely interact with a completed Certificate System installation: The PKI command-line interface and other command-line utilities The PKI Console graphical interface The Certificate System web interface. These interfaces require configuration prior to use for secure communication with the Certificate System server over TLS. Using these clients without proper configuration is not allowed. Some of these tools use TLS client authentication. When required, their required initialization procedure includes configuring this. Which interface is used depends on the administrator's preferences and functionality available. Common actions using these interfaces are described in the remainder of the guide after this chapter. By default, the PKI command-line interface uses the NSS database in the user's ~/.dogtag/nssdb/ directory. Section 2.5.1.1, "pki CLI Initialization" provides detailed steps for initializing the NSS database with the administrator's certificate and key. Some examples of using the PKI command-line utility are described in Section 2.5.1.2, "Using "pki" CLI" . Additional examples are shown through the rest of the guide. Interfacing with Certificate System (as an administrator in other user roles) can be done using various command-line utilities to submit CMC requests, manage generated certificates, and so on. These are described briefly in Section 2.5, "Command Line Interfaces" , such as Section 2.5.2, "AtoB" . These utilities are utilized in later sections such as Section 5.2.1.2, "Creating a CSR Using PKCS10Client " . The Certificate System web interface allows administrative access through the Firefox web browser. Section 2.4.1, "Browser Initialization" describes instructions about configuring the client authentication. Other sections in Section 2.4, "Web Interface" describe using the web interface of Certificate System. The Certificate System's PKI Console is a graphical interface. Please note that it is being deprecated. Section 2.3.1, " pkiconsole Initialization" describes how to initialize this console interface. Section 2.3.2, "Using pkiconsole for CA, OCSP, KRA, and TKS Subsystems" gives an overview of using it. Later sections, such as Section 3.2.2, "Managing Certificate Enrollment Profiles Using the Java-based Administration Console" go into greater detail for specific operations. Note To terminate a PKI Console session, click the Exit button. To terminate a web browser session, close the browser. A command-line utility terminates itself as soon as it performs the action and returns to the prompt, so no action is needed on the administrator's part to terminate the session.

Commands:
7.18. RHEA-2014:1540 - new package: rsyslog7 New rsyslog7 packages are now available for Red Hat Enterprise Linux 6. The rsyslog7 packages provide an enhanced, multi-threaded syslog daemon. It supports on-demand disk buffering, reliable syslog over TCP, SSL, TLS and RELP, writing to databases (MySQL, PostgreSQL, Oracle, and many more), email alerting, fully configurable output formats (including high-precision timestamps), the ability to filter on any part of the syslog message, on-the-wire message compression, and the ability to convert text files to syslog. This enhancement update adds the rsyslog7 packages to Red Hat Enterprise Linux 6. These packages are a replacement for previously used rsyslog packages. (BZ# 869600 ) All users who require rsyslog7 are advised to install these new packages. All users of rsyslog are advised to migrate to these new packages.

Commands:
4.133. libgcrypt 4.133.1. RHEA-2011:1734 - libgcrypt enhancement update An updated libgcrypt package that add an enhancement is now available for Red Hat Enterprise Linux 6. The libgcrypt package contains a library which provides general-purpose implementations of various cryptographic algorithms. Enhancement BZ# 727283 With this update, the libgcrypt library has been recompiled with read-only relocation support that improves the security vulnerability properties of applications that use the library. All users of libgcrypt are advised to upgrade to this updated package, which adds this enhancement. 4.133.2. RHEA-2012:0486 - libgcrypt enhancement update Updated libgcrypt packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The libgcrypt library provides general-purpose implementations of various cryptographic algorithms. Enhancement BZ# 810320 With Federal Information Processing Standards (FIPS) mode enabled, the libgcrypt library always started in the soft FIPS mode which allows applications to use the MD5 cryptographic hash algorithm. The libgcrypt API previously did not allow the library to programmatically switch from the soft FIPS mode to the enforced FIPS mode. With this update, if the application does not need MD5 support for the Transport Layer Security (TLS) protocol or non-cryptographic purposes, libgcrypt can be preset in the enforced FIPS mode. All users of libgcrypt are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 2. Configuring the model registry component To configure the model registry feature for your data scientists to use in OpenShift AI, you must install the following Operators in OpenShift, and then enable the modelregistry component in OpenShift AI. Red Hat Authorino Operator (Technical Preview) Red Hat OpenShift Serverless Operator Red Hat OpenShift Service Mesh Operator Red Hat OpenShift AI Operator version 2.14+ Important You should install the Red Hat OpenShift AI Operator only after the other listed Operators are installed and in a running state. For more information about installing Operators in OpenShift, see Adding Operators to a cluster . For more information about installing the Red Hat OpenShift AI Operator, see Installing the Red Hat OpenShift AI Operator . After you install the Operators, you can use the following steps to enable the modelregistry component. Prerequisites You have cluster administrator privileges for your OpenShift cluster. You have access to the data science cluster. You have installed the Red Hat OpenShift AI Operator on your OpenShift cluster. You have installed the Red Hat Authorino, Red Hat OpenShift Serverless, Red Hat OpenShift Service Mesh, and Red Hat OpenShift AI Operators. You have sufficient resources. For more information about the minimum resources required to use OpenShift AI, see Installing and deploying OpenShift AI (for disconnected environments, see Deploying OpenShift AI in a disconnected environment ). Procedure In the OpenShift console, click Operators Installed Operators . Search for the Red Hat OpenShift AI Operator version 2.14+, and then click the Operator name to open the Operator details page. Click the Data Science Cluster tab. Click the default instance name (for example, default-dsc ) to open the instance details page. Click the YAML tab to show the instance specifications. Find the spec.components section, and then add or update it to include the following modelregistry component entry, with the managementState field set to Managed , and the registriesNamespace field set to rhoai-model-registries : Click Save . Verification Confirm that the model registry namespace was created successfully: In the OpenShift console, click Home Projects . Confirm that the rhoai-model-registries namespace appears in the Projects drop-down list. Check the status of the model-registry-operator-controller-manager pod: In the OpenShift console, from the Project list, select redhat-ods-applications . Click Workloads Deployments . Search for the model-registry-operator-controller-manager deployment. Check the status: Click the deployment name to open the deployment details page. Click the Pods tab. View the pod status. When the status of the model-registry-operator-controller-manager- <pod-id> pod is Running , the pod is ready to use. step OpenShift AI administrators can create, delete, and manage permissions for model registries. For more information, see Managing model registries .

Commands:
modelregistry: managementState: Managed registriesNamespace: rhoai-model-registries
2.3. Enabling the Required Repositories To install packages signed by Red Hat you must register the target system to the Content Delivery Network. Then, use an entitlement from your subscription pool and enable the required repositories. Enabling the Required Repositories Using Subscription Manager Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted: Locate the relevant subscription pools and note down the pool identifiers: Use the pool identifiers to attach the required subscriptions: When a system is attached to a subscription pool with multiple repositories, only the main repository is enabled by default. Others are available, but disabled. Enable any additional repositories: Ensure that all packages currently installed are up to date:

Commands:
subscription-manager register
subscription-manager list --available
subscription-manager attach --pool= pool_id
subscription-manager repos --enable= repository
yum update
3. Feedback If you spot a typo, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in Bugzilla ( http://bugzilla.redhat.com/bugzilla/ ) against the component rh-cs . Be sure to mention the manual's identifier: By mentioning this manual's identifier, we know exactly which version of the guide you have. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

Commands:
rh-gfsg(EN)-4.8 (2010-03-17T16:33)