mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Expanding the Cluster Once the initial cluster is running and in an active+clean state, add additional OSD nodes and Ceph Object Gateway nodes to the cluster. Apply the steps detailed in Tuning the Kernel to each node. See the Adding and Removing OSD Nodes section in the Red Hat Ceph Storage 4 Administration Guide for details on adding nodes. For each OSD node added to the cluster, add OSDs to the cluster for each drive in the node that will store client data. See the Adding an OSD section in the Red Hat Ceph Storage 4 Administration Guide for additional details. When using Ansible to add OSD nodes, see Configuring Ansible Groups , and add the OSD nodes to the appropriate group if the cluster will support multiple use cases. For each Ceph Object Gateway node, install a gateway instance. For details, see the Installing the Ceph Object Gateway section in the Red Hat Ceph Storage 4 Installation Guide. Once the cluster returns to an active+clean state, remove any overrides and proceed with Developing Storage Strategies . Note Step 3 of Adding a Node and Step 10 of Adding an OSD With the Command Line Interface will be revisited in topics beginning with Developing CRUSH Hierarchies .

Commands:
Chapter 2. Configure Red Hat build of OpenJDK 11 in FIPS mode Red Hat build of OpenJDK 11 checks if the FIPS mode is enabled in the system at startup. If yes, it self-configures FIPS according to the global policy. This is the default behavior since RHEL 8.3. RHEL 8 releases require the com.redhat.fips system property set to true as a JVM argument. For example, -Dcom.redhat.fips=true . Note If FIPS mode is enabled in the system while a JVM instance is running, the instance needs to be restarted for changes to take effect. For more information on how to enable FIPS mode, see Switching the system to FIPS mode . You can configure Red Hat build of OpenJDK 11 to bypass the global FIPS alignment. For example, you might want to enable FIPS compliance through a Hardware Security Module (HSM) instead of the scheme provided by Red Hat build of OpenJDK. Following are the FIPS properties for Red Hat build of OpenJDK 11: security.useSystemPropertiesFile Security property located at USDJAVA_HOME/conf/security/java.security or in the file directed to java.security.properties . Privileged access is required to modify the value in the default java.security file. Persistent configuration. When set to false , both the global FIPS and the crypto-policies alignment are disabled. By default, it is set to true . java.security.disableSystemPropertiesFile System property passed to the JVM as an argument. For example, -Djava.security.disableSystemPropertiesFile=true . Non-privileged access is enough. Non-persistent configuration. When set to true , both the global FIPS and the crypto-policies alignment are disabled; generating the same effect than a security.useSystemPropertiesFile=false security property. If both properties are set to different behaviors, java.security.disableSystemPropertiesFile overrides. By default, it is set to false . com.redhat.fips System property passed to a JVM as an argument. For example, -Dcom.redhat.fips=false . Non-privileged access is enough. Non-persistent configuration. When set to false , disables the FIPS alignment while still applying the global crypto-policies. If any of the properties is set to disable the crypto-policies alignment, this property has no effect. In other words, crypto-policies is a prerequisite for FIPS alignment. By default, it is set to true .

Commands:
B.48. logrotate B.48.1. RHSA-2011:0407 - Moderate: logrotate security update An updated logrotate package that fixes multiple security issues is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. CVE-2011-1154 A shell command injection flaw was found in the way logrotate handled the shred directive. A specially-crafted log file could cause logrotate to execute arbitrary commands with the privileges of the user running logrotate (root, by default). Note: The shred directive is not enabled by default. CVE-2011-1098 A race condition flaw was found in the way logrotate applied permissions when creating new log files. In some specific configurations, a local attacker could use this flaw to open new log files before logrotate applies the final permissions, possibly leading to the disclosure of sensitive information. CVE-2011-1155 An input sanitization flaw was found in logrotate. A log file with a specially-crafted file name could cause logrotate to abort when attempting to process that file a subsequent time. All logrotate users should upgrade to this updated package, which contains backported patches to resolve these issues.

Commands:
Chapter 1. Connectivity Link observability You can use the Connectivity Link observability features to observe and monitor your cloud-based applications, APIs, and Gateways. 1.1. Connectivity Link observability features Connectivity Link uses Kuadrant-maintained Gateway API state metrics, metrics exposed by Connectivity Link components, and standard metrics exposed by Envoy to build a set of template dashboards and alerts. You can download and use these Kuadrant community templates to integrate with Grafana, Prometheus, and Alertmanager deployments, or use them as starting points to modify for your specific needs. Figure 1.1. Platform engineer Grafana dashboard The platform engineer dashboard displays details such as the following: Policy compliance and governance. Resource consumption. Error rates. Request latency and throughput. Multi-window, multi-burn alert templates for API error rates and latency. Multicluster split. Figure 1.2. Application developer Grafana dashboard The application developer dashboard is less focused on policies than the platform engineer dashboard and is more focused on APIs and applications. For example, this includes details such as request latency and throughput per API, and total requests and error rates by API path. Figure 1.3. Business user Grafana dashboard The business user dashboard includes details such as the following: Requests per second per API. Increase or decrease in rates of API usage over specified times. Additional resources Kuadrant example dashboards and alerts

Commands:
Chapter 4. Overview of packages with printer drivers Red Hat Enterprise Linux (RHEL) provides different packages with printer drivers for CUPS. The following is a general overview of these packages and for which vendors they contain drivers: Table 4.1. Driver package list Package name Drivers for printers cups Zebra, Dymo c2esp Kodak foomatic Brother, Canon, Epson, Gestetner, HP, Infotec, Kyocera, Lanier, Lexmark, NRG, Ricoh, Samsung, Savin, Sharp, Toshiba, Xerox, and others gutenprint-cups Brother, Canon, Epson, Fujitsu, HP, Infotec, Kyocera, Lanier, NRG, Oki, Minolta, Ricoh, Samsung, Savin, Xerox, and others hplip HP pnm2ppa HP splix Samsung, Xerox, and others Note that some packages can contain drivers for the same printer vendor or model but with different functionality. After installing the required package, you can display the list of drivers in the CUPS web interface or by using the lpinfo -m command.

Commands:
8.18. bash 8.18.1. RHBA-2014:1503 - bash bug fix update Updated bash packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The bash packages provide the Bash (Bourne-again shell) shell, which is the default shell for Red Hat Enterprise Linux. Bug Fixes BZ# 948207 Under certain circumstances, a file descriptor leak occurred in nested Bash functions. This bug has been fixed and file descriptors are no longer leaked in the described case. BZ# 951171 Due to a bug in the tty driver, an ioctl call could return the "-EINTR" error code when the "read" command was interrupted by a signal, such as SIGCHLD. As a consequence, the subsequent "read" call caused the Bash shell to abort with a "double free or corruption (out)" error message. The applied patch corrects the tty driver to use the "-ERESTARTSYS" error code so the system call is restarted if needed. As a result, Bash no longer crashes in this scenario. BZ# 986095 When the HISTFILESIZE variable was set to a value larger than zero, the HISTSIZE variable was set to zero as well. If the .bash_history file had time stamps enabled and was not empty, executing the "su - " command caused Bash to become unresponsive. This bug has been fixed, and Bash no longer hangs in the aforementioned scenario. BZ# 1007926 Previously, Bash did not process quote characters correctly when using here-strings with multi-line input in a function declaration. Consequently, the declaration was corrupted, which affected copying such functions, or transferring them to another shell. This bug has been fixed, and here-strings with multi-line input are now processed correctly. BZ# 1010164 When processing larger associative arrays inside Bash scripts, a memory leak occurred. This bug has been fixed, and Bash no longer leaks memory when working with associative arrays. BZ# 1012015 If a command substitution enclosed in double-quote characters contained a double-quoted string, Bash performed brace expansion on the command before performing command substitution. Consequently, the command created different output than expected. The bug has been fixed, and command substitution now precedes brace expansion in the described case. BZ# 1102803 After editing a command in vi visual mode, Bash echoed every substituted command, which produced a lengthy shell output when editing loops. This behavior has been changed and Bash now only echoes the original string in the described scenario. Users of bash are advised to upgrade to these updated packages, which fix these bugs.

Commands:
23.6. Partition and File System Tools This section describes how different partition and file system management tools interact with a device's I/O parameters. util-linux-ng's libblkid and fdisk The libblkid library provided with the util-linux-ng package includes a programmatic API to access a device's I/O parameters. libblkid allows applications, especially those that use Direct I/O, to properly size their I/O requests. The fdisk utility from util-linux-ng uses libblkid to determine the I/O parameters of a device for optimal placement of all partitions. The fdisk utility will align all partitions on a 1MB boundary. parted and libparted The libparted library from parted also uses the I/O parameters API of libblkid . The Red Hat Enterprise Linux 6 installer ( Anaconda ) uses libparted , which means that all partitions created by either the installer or parted will be properly aligned. For all partitions created on a device that does not appear to provide I/O parameters, the default alignment will be 1MB. The heuristics parted uses are as follows: Always use the reported alignment_offset as the offset for the start of the first primary partition. If optimal_io_size is defined (i.e. not 0 ), align all partitions on an optimal_io_size boundary. If optimal_io_size is undefined (i.e. 0 ), alignment_offset is 0 , and minimum_io_size is a power of 2, use a 1MB default alignment. This is the catch-all for "legacy" devices which don't appear to provide I/O hints. As such, by default all partitions will be aligned on a 1MB boundary. Note Red Hat Enterprise Linux 6 cannot distinguish between devices that don't provide I/O hints and those that do so with alignment_offset=0 and optimal_io_size=0 . Such a device might be a single SAS 4K device; as such, at worst 1MB of space is lost at the start of the disk. File System tools The different mkfs. filesystem utilities have also been enhanced to consume a device's I/O parameters. These utilities will not allow a file system to be formatted to use a block size smaller than the logical_block_size of the underlying storage device. Except for mkfs.gfs2 , all other mkfs. filesystem utilities also use the I/O hints to layout on-disk data structure and data areas relative to the minimum_io_size and optimal_io_size of the underlying storage device. This allows file systems to be optimally formatted for various RAID (striped) layouts.

Commands:
Chapter 2. Prerequisites for Installation Before you install IdM, ensure that the installation environment is suitably configured. You also need to provide certain information during the installation and configuration procedures, including realm names and certain usernames and passwords. This section describes the information that you need to provide. 2.1. Supported Server Platforms IdM 3.0 is supported on these platforms: Red Hat Enterprise Linux 6 i386 Red Hat Enterprise Linux 6 x86_64

Commands:
Backup and restore Red Hat Advanced Cluster Security for Kubernetes 4.6 Backing up and restoring Red Hat Advanced Cluster Security for Kubernetes Red Hat OpenShift Documentation Team

Commands:
export ROX_API_TOKEN=<api_token>
export ROX_ENDPOINT=<address>:<port_number>
roxctl central backup 1
export ROX_ENDPOINT=<address>:<port_number>
roxctl -p <admin_password> central backup 1
oc get central -n _<central-namespace>_ _<central-name>_ -o yaml > central-cr.yaml
oc get secret -n _<central-namespace>_ central-tls -o json | jq 'del(.metadata.ownerReferences)' > central-tls.json
oc get secret -n _<central-namespace>_ central-htpasswd -o json | jq 'del(.metadata.ownerReferences)' > central-htpasswd.json
helm get values --all -n _<central-namespace>_ _<central-helm-release>_ -o yaml > central-values-backup.yaml
export ROX_API_TOKEN=<api_token>
export ROX_ENDPOINT=<address>:<port_number>
roxctl central db restore <backup_file> 1
export ROX_ENDPOINT=<address>:<port_number>
roxctl -p <admin_password> \ 1 central db restore <backup_file> 2
roxctl central generate interactive
Enter path to the backup bundle from which to restore keys and certificates (optional): _<backup-file-path>_
./central-bundle/central/scripts/setup.sh
cat central-bundle/password
oc apply -f central-tls.json
oc apply -f central-htpasswd.json
oc apply -f central-cr.yaml
roxctl central generate k8s pvc --backup-bundle _<path-to-backup-file>_ --output-format "helm-values"
helm install -n stackrox --create-namespace stackrox-central-services rhacs/central-services -f central-values-backup.yaml -f central-bundle/values-private.yaml
21.3. Resolving glusterd Crash glusterd crash is observed in the following scenarios: glusterd recieves a Termination Signal or SIGTERM . Segmentation fault error message when upgrading Red Hat Gluster Storage. glusterd service is being stopped. Important There is no functionality impact to these crashes as they occur during the shutdown path of glusterd . If the glusterd crash is persistent in any other scenarios, contact Red Hat Support

Commands:
Chapter 2. Enabling applications that are connected to OpenShift AI You must enable SaaS-based applications before using them with Red Hat OpenShift AI. On-cluster applications are enabled automatically. Typically, you can install, or enable applications connected to OpenShift AI using one of the following methods: Enabling the application from the Explore page on the OpenShift AI dashboard, as documented in the following procedure. Installing the Operator for the application from OperatorHub. OperatorHub is a web console for cluster administrators to discover and select Operators to install on their cluster. It is deployed by default in OpenShift ( Installing from OperatorHub using the web console ). Note Deployments containing Operators installed from OperatorHub may not be fully supported by Red Hat. Installing the Operator for the application from Red Hat Marketplace ( Install Operators ). Installing the application as an Operator to your OpenShift cluster ( Adding Operators to a cluster ). For some applications (such as Jupyter), the API endpoint is available on the tile for the application on the Enabled page of OpenShift AI. Certain applications cannot be accessed directly from their tiles, for example, OpenVINO provides notebook images for use in Jupyter and does not provide an endpoint link from its tile. Additionally, it may be useful to store these endpoint URLs as environment variables for easy reference in a notebook environment. Some independent software vendor (ISV) applications must be installed in specific namespaces. In these cases, the tile for the application in the OpenShift AI dashboard specifies the required namespace. To help you get started quickly, you can access the application's learning resources and documentation on the Resources page, or on the Enabled page by clicking the relevant link on the tile for the application. Prerequisites You have logged in to Red Hat OpenShift AI. Your administrator has installed or configured the application on your OpenShift cluster. Procedure On the OpenShift AI home page, click Explore . On the Explore page, find the tile for the application that you want to enable. Click Enable on the application tile. If prompted, enter the application's service key and then click Connect . Click Enable to confirm that you want to enable the application. Verification The application that you enabled appears on the Enabled page. The API endpoint is displayed on the tile for the application on the Enabled page.

Commands:
Chapter 3. Compatibility and support matrix 3.1. Products and versions RHTAP installs on OpenShift Container Platform. The cluster where you deploy RHTAP should have the OpenShift Platform Plus subscription, as RHTAP relies on several products available through OpenShift Platform Plus. These products integrate seamlessly with RHTAP and its software templates, and the RHTAP installer automatically deploys them during installation. However, please note that these products are not included with RHTAP. OpenShift Platform Plus Product Version OpenShift Container Platform 4.15, 4.16, 4.17 OpenShift Pipelines 1.17 OpenShift GitOps 1.15 Advanced Cluster Security 4.6 Quay 3.13 The RHTAP installer also deploys the following products, which form the RHTAP subscription: RHTAP Product Version Red Hat Developer Hub 1.4 Red Hat Trusted Artifact Signer 1.1 Red Hat Trusted Profile Analyzer 1.2 Enterprise Contract 0.6.104 3.2. Red Hat Developer Hub plugins RHTAP enables a selection of RHDH dynamic plugins to support creation and monitoring of trusted secure supply chain applications. Some of the plugins enabled by RHTAP include Technology Preview and community plugins that may not be functionally complete. Regardless of the plugins levels of support, pipelines produced by the RHTAP software templates are fully supported and leverage the security features of Trusted Software Supply Chain products and features: Red Hat Trusted Application Signer, Red Hat Trusted Profile Analyzer, and Enterprise Contract. Technology Preview and community plugins enabled by RHTAP: Level of support Name Technology Preview plugins JFrog Artifactory Community plugins Jenkins GitHub Actions GitLab Bitbucket Cloud To learn more about the supported levels of the individual dynamic plugins, refer to the Developer Hub documentation .

Commands:
Migrating Fuse 7 Applications to Red Hat build of Apache Camel for Quarkus Red Hat build of Apache Camel 4.0 Migrating Fuse 7 Applications to Red Hat build of Apache Camel for Quarkus Red Hat build of Apache Camel Documentation Team fuse_docs_support@redhat.com Red Hat build of Apache Camel Support Team http://access.redhat.com/support

Commands:
Preface This guide provides an overview of the requirements and procedures for a high availability deployment of your automation hub. A high availability (HA) configuration increases reliability and scalablility for automation hub deployments. HA deployments of automation hub have multiple nodes that concurrently run the same service with a load balancer distributing workload (an "active-active" configuration). This configuration eliminates single points of failure to minimize service downtime and allows you to easily add or remove nodes to meet workload demands. This guide covers deployment of a HA automation hub application stack only. Other HA components, such as database and file system HA, or setting up DNS load balancing, are out of scope for this guide.

Commands:
5.297. sed 5.297.1. RHBA-2012:0955 - sed bug fix update Updated sed packages that fix three bugs are now available for Red Hat Enterprise Linux 6. Sed is a stream or batch non-interactive editor. It takes text as input, performs an operation or set of operations on the text, and outputs the modified text. Bug Fixes BZ# 709956 When the "--copy" option was used with the sed utility, sed created a back-up copy of the original file. However, the back-up file was not deleted after a successful operation. A patch has been provided to address this bug and back-up files are now properly deleted in the described scenario. BZ# 724962 Previously, the sed test suite was setting locale for UTF-8 variants incorrectly. Consequently, operation of the rpmbuild utility could fail, among other issues. This bug has been fixed and the test suite now sets the locale correctly. BZ# 812316 A static analysis tool discovered several minor file I/O resource leaks, which occurred when sed encountered an error. This bug has been fixed and the leaks no longer occur. All users of sed are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.49. espeak 7.49.1. RHBA-2012:1118 - espeak bug fix update Updated espeak packages that fix one bug are now available for Red Hat Enterprise Linux 6. The espeak packages contain a software speech synthesizer for English and other languages. eSpeak uses a "formant synthesis" method, which allows many languages to be provided in a small size. Bug Fix BZ#789997 Previously, eSpeak manipulated the system sound volume. As a consequence, eSpeak could set the sound volume to maximum regardless of the amplitude specified. The sound volume management code has been removed from eSpeak, and now only PulseAudio manages the sound volume. All users of espeak are advised to upgrade to these updated packages, which fix this bug.

Commands:
4.16. RHEA-2012:0826 - new package: ppc64-diag A new ppc64-diag package is now available for Red Hat Enterprise Linux 6. The ppc64-diag package provides platform diagnostics for Linux for 64-bit PowerPC architectures. This enhancement update adds the ppc64-diag package to Red Hat Enterprise Linux 6. (BZ# 632735 ) All users who require ppc64-diag are advised to install this newly released package.

Commands:
18.2. Basic Firewall Configuration Just as a firewall in a building attempts to prevent a fire from spreading, a computer firewall attempts to prevent malicious software from spreading to your computer. It also helps to prevent unauthorized users from accessing your computer. In a default Red Hat Enterprise Linux installation, a firewall exists between your computer or network and any untrusted networks, for example the Internet. It determines which services on your computer remote users can access. A properly configured firewall can greatly increase the security of your system. It is recommended that you configure a firewall for any Red Hat Enterprise Linux system with an Internet connection. 18.2.1. Security Level Configuration Tool During the Firewall Configuration screen of the Red Hat Enterprise Linux installation, you were given the option to enable a basic firewall as well as to allow specific devices, incoming services, and ports. After installation, you can change this preference by using the Security Level Configuration Tool . To start this application, use the following command: Figure 18.1. Security Level Configuration Tool Note The Security Level Configuration Tool only configures a basic firewall.

Commands:
system-config-selinux