mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 14. Scaling Multicloud Object Gateway performance The Multicloud Object Gateway (MCG) performance may vary from one environment to another. In some cases, specific applications require faster performance which can be easily addressed by scaling S3 endpoints. The MCG resource pool is a group of NooBaa daemon containers that provide two types of services enabled by default: Storage service S3 endpoint service S3 endpoint service The S3 endpoint is a service that every Multicloud Object Gateway (MCG) provides by default that handles the heavy lifting data digestion in the MCG. The endpoint service handles the inline data chunking, deduplication, compression, and encryption, and it accepts data placement instructions from the MCG. 14.1. Automatic scaling of MultiCloud Object Gateway endpoints The number of MultiCloud Object Gateway (MCG) endpoints scale automatically when the load on the MCG S3 service increases or decreases. OpenShift Data Foundation clusters are deployed with one active MCG endpoint. Each MCG endpoint pod is configured by default with 1 CPU and 2Gi memory request, with limits matching the request. When the CPU load on the endpoint crosses over an 80% usage threshold for a consistent period of time, a second endpoint is deployed lowering the load on the first endpoint. When the average CPU load on both endpoints falls below the 80% threshold for a consistent period of time, one of the endpoints is deleted. This feature improves performance and serviceability of the MCG. You can scale the Horizontal Pod Autoscaler (HPA) for noobaa-endpoint using the following oc patch command, for example: The example above sets the minCount to 3 and the maxCount to `10 . 14.2. Increasing CPU and memory for PV pool resources MCG default configuration supports low resource consumption. However, when you need to increase CPU and memory to accommodate specific workloads and to increase MCG performance for the workloads, you can configure the required values for CPU and memory in the OpenShift Web Console. Procedure In the OpenShift Web Console, navigate to Storage Object Storage Backing Store . Select the relevant backing store and click on YAML. Scroll down until you find spec: and update pvPool with CPU and memory. Add a new property of limits and then add cpu and memory. Example reference: Click Save . Verification steps To verfiy, you can check the resource values of the PV pool pods.

Commands:
oc patch -n openshift-storage storagecluster ocs-storagecluster --type merge --patch '{"spec": {"multiCloudGateway": {"endpoints": {"minCount": 3,"maxCount": 10}}}}'
spec: pvPool: resources: limits: cpu: 1000m memory: 4000Mi requests: cpu: 800m memory: 800Mi storage: 50Gi
8.64. gcc-libraries 8.64.1. RHBA-2014:1438 - gcc-libraries bug fix and enhancement update Updated gcc-libraries packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The gcc-libraries packages contain various GNU Compiler Collection (GCC) runtime libraries, such as libatomic and libitm. Note The gcc-libraries packages have been upgraded to upstream version 4.9.0, which provides a number of bug fixes and enhancements over the version to match the features in Red Hat Developer Toolset 3.0. Among others, this update adds the libcilkrts library to gcc-libraries. (BZ# 1062230 , BZ# 1097800 ) Users of gcc-libraries are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
5.9. augeas 5.9.1. RHBA-2012:0967 - augeas bug fix and enhancement update Updated augeas packages that fix three bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. Augeas is a configuration editing tool. Augeas parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native configuration files. Bug Fixes BZ# 759311 Previously, the "--autosave" option did not work correctly when using Augeas in batch mode, which caused that configuration changes were not saved. As a consequence, configuration changes could be saved only in interactive mode. This update ensures that the "--autosave" option functions in batch mode as expected. BZ# 781690 Prior to this update, when parsing GRUB configuration files, Augeas did not parse the "--encrypted" option of the "password" command correctly. Instead, it parsed the "--encrypted" part as the password, and the password hash as a second "menu.lst" filename. This update ensures that the "--encrypted" option of the password command is parsed correctly when parsing GRUB configuration files. BZ# 820864 Previously, Augeas was not able to parse the /etc/fstab file containing mount options with an equals sign but no value. This update fixes the fstab lens so that it can handle such mount options. As a result, Augeas can now parse an /etc/fstab file containing mount options with an equals sign but no value correctly. Enhancements BZ# 628507 Previously, the finite-automata-DOT graph tool (fadot) did not support the -h option. Consequently, when fadot was launched with the -h option the "Unknown option" message was displayed. This update adds support for the -h option and ensures that a help message is displayed when fadot is launched with the option. BZ# 808662 Previously, Augeas did not have a lens to parse the /etc/mdadm.conf file. Consequently, the tool for conversion of physical servers to virtual guests, Virt-P2V, could not convert physical hosts on MD devices. This update adds a new lens to parse the /etc/mdadm.conf file, enabling Virt-P2V to convert physical hosts on MD devices as expected. All users of Augeas are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 4. External storage services Red Hat OpenShift Data Foundation can use IBM FlashSystems or make services from an external Red Hat Ceph Storage cluster available for consumption through OpenShift Container Platform clusters running on the following platforms: VMware vSphere Bare Metal Red Hat OpenStack platform (Technology preview) The OpenShift Data Foundation operators create and manage services to satisfy persistent volume and object bucket claims against external services. External cluster can serve Block, File and Object storage classes for applications running on OpenShift Container Platform. External clusters are not deployed or managed by operators.

Commands:
Managing clusters OpenShift Cluster Manager 1-latest Using Red Hat OpenShift Cluster Manager to work with your OpenShift clusters Red Hat Customer Content Services

Commands:
https://console.redhat.com/openshift/
oc login -u=<username> -p=<password> --server=<your-openshift-server> --insecure-skip-tls-verify
oc get nodes -o wide
oc describe nodes | egrep 'Name:|InternalIP:|cpu:'
oc get clusterversion <version> -o jsonpath='{.spec.clusterID}{"\n"}'
oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=pull-secret.txt
oc create secret generic pull-secret -n openshift-config --type=kubernetes.io/dockerconfigjson --from-file=.dockerconfigjson=/path/to/downloaded/pull-secret
oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=pull-secret.txt
oc create secret generic pull-secret -n openshift-config --type=kubernetes.io/dockerconfigjson --from-file=.dockerconfigjson=/path/to/downloaded/pull-secret
oc get pods -n openshift-monitoring -l app.kubernetes.io/name=telemeter-client
oc delete pod -n openshift-monitoring -l app.kubernetes.io/name=telemeter-client oc delete pod -n openshift-insights -l app=insights-operator
oc get secret pull-secret -n openshift-config -o jsonpath='{.data.\.dockerconfigjson}' | base64 -d | jq
11.7. Choose a Boot Method Installing from a DVD requires that you have purchased a Red Hat Enterprise Linux product, you have a Red Hat Enterprise Linux 6.9 DVD, and you have a DVD drive on a system that supports booting from it. Refer to Chapter 2, Making Media for instructions to make an installation DVD. Other than booting from an installation DVD, you can also boot the Red Hat Enterprise Linux installation program from minimal boot media in the form of a bootable CD. After you boot the system with boot CD, you complete the installation from a different installation source, such as a local hard drive or a location on a network. Refer to Section 2.2, "Making Minimal Boot Media" for instructions on making boot CDs.

Commands:
3.5. Listing Hosts This Ruby example lists the hosts. # Get the reference to the root of the services tree: system_service = connection.system_service # Get the reference to the service that manages the # collection of hosts: host_service = system_service.hosts_service # Retrieve the list of hosts and for each one # print its name: host = host_service.list host.each do |host| puts host.name end In an environment with only one attached host ( Atlantic ) the example outputs: For more information, see HostsService:list-instance_method .

Commands:
Get the reference to the root of the services tree: system_service = connection.system_service Get the reference to the service that manages the collection of hosts: host_service = system_service.hosts_service Retrieve the list of hosts and for each one print its name: host = host_service.list host.each do |host| puts host.name end
Atlantic
6.4. RHEA-2013:0369 - new packages: pcs New pcs packages are now available for Red Hat Enterprise Linux 6. The pcs packages provide a command-line tool and graphical web interface to configure and manage pacemaker and corosync. This enhancement update adds the pcs package as a Technology Preview. (BZ# 657370 ) More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ All users who want to use the pcs Technology Preview are advised to install these new packages.

Commands:
Part V. Red Hat JBoss Data Grid Quickstarts The following lists the quickstarts included in this document and provides information about which container and mode they are used in: Table 14. Quickstarts Information Quickstart Name Container JBoss Data Grid Mode Link to Details Hello World JBoss EAP Library mode Chapter 13, The Hello World Quickstart Carmart Non-Transactional JBoss EAP and JBoss Enterprise Web Server Library mode Section 14.3, "The (Non-transactional) CarMart Quickstart Using JBoss EAP" Carmart Non-Transactional JBoss EAP and JBoss Enterprise Web Server Remote Client-Server mode Section 14.5, "The (Non-transactional) CarMart Quickstart in Remote Client-Server Mode (JBoss EAP)" and Section 14.6, "The (Non-Transactional) CarMart Quickstart in Remote Client-Server Mode (JBoss Enterprise Web Server)" Carmart Transactional JBoss EAP and JBoss Enterprise Web Server Library mode Section 14.7, "The (Transactional) CarMart Quickstart Using JBoss EAP" and Section 14.8, "The (Transactional) CarMart Quickstart Using JBoss Enterprise Web Server" Football Application No container Remote Client-Server mode Chapter 15, The Football Quickstart Endpoint Examples Rapid Stock Market No container Remote Client-Server mode Chapter 16, The Rapid Stock Market Quickstart Cluster App JBoss EAP Library mode Chapter 17, The Cluster App Quickstart camel-jbossdatagrid-fuse JBoss Fuse Library mode Chapter 18, The camel-jbossdatagrid-fuse Quickstart Report a bug

Commands:
Chapter 33. Configuring an FCoE Interface to Automatically Mount at Boot Note The instructions in this section are available in /usr/share/doc/fcoe-utils- version /README as of Red Hat Enterprise Linux 6.1. Refer to that document for any possible changes throughout minor releases. You can mount newly discovered disks via udev rules, autofs , and other similar methods. Sometimes, however, a specific service might require the FCoE disk to be mounted at boot-time. In such cases, the FCoE disk should be mounted as soon as the fcoe service runs and before the initiation of any service that requires the FCoE disk. To configure an FCoE disk to automatically mount at boot, add proper FCoE mounting code to the startup script for the fcoe service. The fcoe startup script is /etc/init.d/fcoe . The FCoE mounting code is different per system configuration, whether you are using a simple formatted FCoE disk, LVM, or multipathed device node. Example 33.1. FCoE mounting code The following is a sample FCoE mounting code for mounting file systems specified via wild cards in /etc/fstab : The mount_fcoe_disks_from_fstab function should be invoked after the fcoe service script starts the fcoemon daemon. This will mount FCoE disks specified by the following paths in /etc/fstab : Entries with fc- and _netdev sub-strings enable the mount_fcoe_disks_from_fstab function to identify FCoE disk mount entries. For more information on /etc/fstab entries, refer to man 5 fstab . Note The fcoe service does not implement a timeout for FCoE disk discovery. As such, the FCoE mounting code should implement its own timeout period.

Commands:
mount_fcoe_disks_from_fstab() { local timeout=20 local done=1 local fcoe_disks=(USD(egrep 'by-path\/fc-.*_netdev' /etc/fstab | cut -d ' ' -f1)) test -z USDfcoe_disks && return 0 echo -n "Waiting for fcoe disks . " while [ USDtimeout -gt 0 ]; do for disk in USD{fcoe_disks[*]}; do if ! test -b USDdisk; then done=0 break fi done test USDdone -eq 1 && break; sleep 1 echo -n ". " done=1 let timeout-- done if test USDtimeout -eq 0; then echo "timeout!" else echo "done!" fi # mount any newly discovered disk mount -a 2>/dev/null }
/dev/disk/by-path/fc-0xXX:0xXX /mnt/fcoe-disk1 ext3 defaults,_netdev 0 0 /dev/disk/by-path/fc-0xYY:0xYY /mnt/fcoe-disk2 ext3 defaults,_netdev 0 0
Chapter 6. Installing a three-node cluster on OpenStack In OpenShift Container Platform version 4.18, you can install a three-node cluster on Red Hat OpenStack Platform (RHOSP). A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster on installer-provisioned infrastructure only. 6.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... 6.2. steps Installing a cluster on OpenStack with customizations

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
Chapter 18. Configuring allowed-address-pairs 18.1. Overview of allowed-address-pairs Use allowed-address-pairs to specify mac_address/ip_address (CIDR) pairs that pass through a port regardless of subnet. This enables the use of protocols such as VRRP, which floats an IP address between two instances to enable fast data plane failover. Note The allowed-address-pairs extension is currently supported only by the ML2 and Open vSwitch plug-ins. 18.2. Creating a port and allowing one address pair Use the following command to create a port and allow one address pair: 18.3. Adding allowed-address-pairs Use the following command to add allowed address pairs: Note You cannot set an allowed-address pair that matches the mac_address and ip_address of a port. This is because such a setting has no effect since traffic matching the mac_address and ip_address is already allowed to pass through the port.

Commands:
openstack port create --network net1 --allowed-address mac_address=<mac_address>,ip_address=<ip_cidr> PORT_NAME
openstack port set <port-uuid> --allowed-address mac_address=<mac_address>,ip_address=<ip_cidr>
Chapter 1. Overview of deploying in external mode Red Hat OpenShift Data Foundation can make services from an external Red Hat Ceph Storage cluster or use IBM FlashSystems available for consumption through OpenShift Container Platform clusters running on the following platforms: VMware vSphere Bare metal Red Hat OpenStack platform (Technology preview) See Planning your deployment for more information. For instructions regarding how to install a RHCS 4 cluster, see Installation guide . Follow these steps to deploy OpenShift Data Foundation in external mode: If you use Red Hat Enterprise Linux hosts for worker nodes, Enable file system access for containers . Skip this step if you use Red Hat Enterprise Linux CoreOS (RHCOS) hosts. Deploy one of the following: Deploy OpenShift Data Foudation using Red Hat Ceph Storage . Deploy OpenShift Data Foudation using IBM FlashSystem . Regional-DR requirements [Developer Preview] Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites in order to successfully implement a Disaster Recovery solution: A valid Red Hat OpenShift Data Foundation Advanced subscription A valid Red Hat Advanced Cluster Management for Kubernetes subscription For detailed requirements, see Regional-DR requirements and RHACM requirements .

Commands:
Chapter 8. Understanding ingress When you create a site that can be linked to, you need to enable ingress on that site. By default, ingress is enabled, however you can disable it or set it to use a specific ingress type. By default, the ingress type is set to: route if available (OpenShift) loadbalancer Other options include: none useful if you do not need to link to the current site. nodeport nginx-ingress-v1 contour-http-proxy You can set the ingress type using the CLI when creating the site skupper init --ingress <type> or by setting the type in your site YAML, for example to disable ingress: apiVersion: v1 kind: ConfigMap metadata: name: skupper-site data: name: my-site ingress: "none" If the default ingress is not suitable, an alternative is nginx-ingress-v1 . Nginx uses Server Name Indication (SNI) to identify connection targets, which eliminates the need for assigning separate IP addresses as required by loadbalancer . Note When using nginx-ingress-v1 you must enable SSL Passthrough as described in Ingress-Nginx Controller documentation . 8.1. CLI options For a full list of options, see the Skupper Kubernetes CLI reference and Skupper Podman CLI reference documentation. Warning When you create a site and set logging level to trace , you can inadvertently log sensitive information from HTTP headers. USD skupper init --router-logging trace By default, all skupper commands apply to the cluster you are logged into and the current namespace. The following skupper options allow you to override that behavior and apply to all commands: --namespace <namespace-name> Apply command to <namespace-name> . For example, if you are currently working on frontend namespace and want to initialize a site in the backend namespace: USD skupper init --namespace backend --kubeconfig <kubeconfig-path> Path to the kubeconfig file - This allows you run multiple sessions to a cluster from the same client. An alternative is to set the KUBECONFIG environment variable. --context <context-name> The kubeconfig file can contain defined contexts, and this option allows you to use those contexts.

Commands:
apiVersion: v1 kind: ConfigMap metadata: name: skupper-site data: name: my-site ingress: "none"
skupper init --router-logging trace
skupper init --namespace backend
Chapter 7. Kafka breaking changes This section describes any changes to Kafka that required a corresponding change to AMQ Streams to continue to work. 7.1. Using Kafka's example file connectors Kafka no longer includes the example file connectors FileStreamSourceConnector and FileStreamSinkConnector in its CLASSPATH and plugin.path by default. AMQ Streams has been updated so that you can still use these example connectors. The examples now have to be added to the plugin path like any connector. Two example connector configuration files are provided: examples/connect/kafka-connect-build.yaml provides a Kafka Connect build configuration, which you can deploy to build a new Kafka Connect image with the file connectors. examples/connect/source-connector.yaml provides the configuration required to deploy the file connectors as KafkaConnector resources. See the following: Deploying example KafkaConnector resources Extending Kafka Connect with connector plugins

Commands:
Chapter 44. Technology Previews containernetworking-plugins now available The Container Network Interface (CNI) project consists of a specification and libraries for writing plug-ins for configuring network interfaces in Linux containers, along with a number of supported plug-ins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. The containernetworking-plugins package is now available as a technology preview. It is a dependency of the podman tool, and will remain as a technology preview until podman becomes fully supported. LiveFS now available Previously, layering packages on Atomic Host required a reboot for the software to be available on the system. The LiveFS feature removes the need to reboot, making layered packages available instantly. See Package Layering for more information and usage instructions. Identity Management in a container Identity Management (IdM) in a container is provided as a Technology Preview. To install this new image, use the atomic install --hostname <IPA_server_hostname> rhel7/ipa-server command. In addition to --hostname , The atomic install command supports the following keywords for specifying the style of the container to be run: net-host - share the host's network to the container publish - publish all ports to the host's interfaces cap-add - add a capability to the container You can also use the atomic install rhel7/ipa-server help command to list these keywords and their usage.

Commands: