mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Requirements for enabling Regional-DR You must have three OpenShift clusters that have network reachability between them: Hub cluster where Advanced Cluster Management for Kubernetes (RHACM operator), ODF Multicluster Orchestrator and OpenShift DR Hub controllers are installed. Primary managed cluster where OpenShift Data Foundation, OpenShift DR Cluster controller, and applications are installed. Secondary managed cluster where OpenShift Data Foundation, OpenShift DR Cluster controller, and applications are installed. Ensure that you have installed RHACM operator and MultiClusterHub on the Hub cluster and logged on to the RHACM console using your OpenShift credentials. See RHACM installation guide for instructions. Find the Route that has been created for the Advanced Cluster Manager console: Example Output: After logging in using your OpenShift credentials, you should see your local cluster imported. Ensure that you have either imported or created the Primary managed cluster and the Secondary managed clusters using the RHACM console. To connect the managed OpenShift cluster and service networks using the Submariner add-ons, you need to validate that the two clusters have non-overlapping networks by running the following commands for each of the managed clusters. Example output for cluster1 (for example, ocp4perf1 ): Example output for cluster2 (for example, ocp4perf2 ): For more information, see Submariner add-ons documentation . Ensure that the Managed clusters can connect using Submariner add-ons . After identifying and ensuring that the cluster and service networks have non-overlapping ranges, install the Submariner add-ons for each managed cluster using the RHACM console and Cluster sets . For instructions, see Submariner documentation . Ensure OpenShift Data Foundation 4.9 or greater is installed on each of the managed clusters. For information about the OpenShift Data Foundation deployment, refer to your infrastructure specific deployment guides (for example, AWS, VMware, Bare metal, Azure). Validate the successful deployment on each managed cluster with the following command: If the status result is Ready on the Primary managed cluster and the Secondary managed cluster , then continue with enabling mirroring on the managed clusters.

Commands:
oc get route multicloud-console -n open-cluster-management -o jsonpath --template="https://{.spec.host}/multicloud/clusters{'\n'}"
https://multicloud-console.apps.perf3.example.com/multicloud/clusters
oc get networks.config.openshift.io cluster -o json | jq .spec
{ "clusterNetwork": [ { "cidr": "10.5.0.0/16", "hostPrefix": 23 } ], "externalIP": { "policy": {} }, "networkType": "OpenShiftSDN", "serviceNetwork": [ "10.15.0.0/16" ] }
{ "clusterNetwork": [ { "cidr": "10.6.0.0/16", "hostPrefix": 23 } ], "externalIP": { "policy": {} }, "networkType": "OpenShiftSDN", "serviceNetwork": [ "10.16.0.0/16" ] }
oc get storagecluster -n openshift-storage ocs-storagecluster -o jsonpath='{.status.phase}{"\n"}'
27.2. IBM Redbooks Publications for System z Current versions of IBM Redbooks publications can be found at http://www.redbooks.ibm.com/ . They include: Introductory publications Introduction to the New Mainframe: z/VM Basics . IBM Redbooks . 2007. SG24-7316. z/VM and Linux on IBM System z The Virtualization Cookbook for Red Hat Enterprise Linux 5.2 . IBM Redbooks . 2008. SG24-7492. Practical Migration to Linux on System z . IBM Redbooks . 2009. SG24-7727. Performance and high availability Linux on IBM System z: Performance Measurement and Tuning . IBM Redbooks . 2011. SG24-6926. Achieving High Availability on Linux for System z with Linux-HA Release 2 . IBM Redbooks . 2009. SG24-7711. Security Security for Linux on System z . IBM Redbooks . 2013. SG24-7728. Using Cryptographic Adapters for Web Servers with Linux on IBM System z9 and zSeries . IBM Redbooks . 2006. REDP-4131. Networking IBM System z Connectivity Handbook . IBM Redbooks . 2013. SG24-5444. OSA Express Implementation Guide . IBM Redbooks . 2009. SG24-5948. HiperSockets Implementation Guide . IBM Redbooks . 2007. SG24-6816. Fibre Channel Protocol for Linux and z/VM on IBM System z . IBM Redbooks . 2007. SG24-7266.

Commands:
5.3. Splitting a Volume Group In this example, an existing volume group consists of three physical volumes. If there is enough unused space on the physical volumes, a new volume group can be created without adding new disks. In the initial set up, the logical volume mylv is carved from the volume group myvol , which in turn consists of the three physical volumes, /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . After completing this procedure, the volume group myvg will consist of /dev/sda1 and /dev/sdb1 . A second volume group, yourvg , will consist of /dev/sdc1 . 5.3.1. Determining Free Space You can use the pvscan command to determine how much free space is currently available in the volume group.

Commands:
pvscan PV /dev/sda1 VG myvg lvm2 [17.15 GB / 0 free] PV /dev/sdb1 VG myvg lvm2 [17.15 GB / 12.15 GB free] PV /dev/sdc1 VG myvg lvm2 [17.15 GB / 15.80 GB free] Total: 3 [51.45 GB] / in use: 3 [51.45 GB] / in no VG: 0 [0 ]
2.3. Single Sign-on (SSO) The Red Hat Enterprise Linux SSO functionality reduces the number of times Red Hat Enterprise Linux desktop users have to enter their passwords. Several major applications leverage the same underlying authentication and authorization mechanisms so that users can log in to Red Hat Enterprise Linux from the log-in screen, and then not need to re-enter their passwords. These applications are detailed below. For more information on Pluggable Authentication Modules, see the Red Hat Enterprise Linux 6 Managing Single Sign-On and Smart Cards guide.

Commands:
Appendix A. Further Information A.1. SELinux and sVirt Further information on SELinux and sVirt: Main SELinux website: https://www.nsa.gov/portals/75/documents/what-we-do/research/selinux/documentation/presentations/2004-ottawa-linux-symposium-bof-presentation.pdf . Main sVirt website: http://selinuxproject.org/page/SVirt . Dan Walsh's blog: http://danwalsh.livejournal.com/ .

Commands:
Chapter 3. Features and benefits 3.1. Current features and benefits .NET 9.0 offers the following features and benefits. Runtime and framework libraries .NET consists of the framework libraries as well as compilers, build tools, tools to fetch NuGet packages, and a command-line interface to tie everything together. Benefits include: Automatic memory management Type safety Delegates and lambdas Generic types Language Integrated Query (LINQ) Async programming Native interoperability Source generators .NET 9.0 supports developing applications using ASP.NET Core 9.0 and EF Core 9.0, which bring benefits such as: Lightweight and modular HTTP request pipeline Ability to host on a web server or self-host in your own process Built on .NET, which supports true side-by-side app versioning Integrated support for creating and using NuGet packages Single aligned web stack for web UI and web APIs Cloud-ready environment-based configuration Built-in support for dependency injection Tools that simplify modern web development 3.2. New features and benefits .NET 9.0 continues to broaden its support and tools for application development in an open source environment. The latest version of .NET includes the following improvements: The SDK supports using the latest C# (C# 13) and F# (F# 9) versions. The SDK now uses the new terminal logger by default which improves theusability of the .NET 9.0 command-line interface. The base library, GC, and JIT have seen many performance improvements. The GC now defaults to the dynamic adaption to application sizes (DATAS) mode which resizes the heap based on the active workload. .NET 9.0 comes with many API additions that improve performance, like overloads using the new C# 13 params Span and allow C# 13 generic ref struct parameters to eliminate allocations..NET 9.0 also includes many enhancements to its JSON support. For interop and efficient operations on AI data, .NET 9.0 provides a new Tensor<T> type. ASP.NET Core 9.0 comes with built-in support for OpenAPI document generation. Additionally, the new MapStaticAssets middleware provides optimized support for delivering static assets.

Commands:
5.255. pykickstart 5.255.1. RHBA-2012:0882 - pykickstart bug fix and enhancement update Updated pykickstart packages that fix multiple bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The pykickstart package contains a python library for manipulating kickstart files. Bug Fixes BZ# 758603 If using the "raid" command with the "--useexisting" option without specifying the members that were part of the RAID set, the system installation failed with the following error message on system startup: With this update, the library scripts check if the RAID members are defined and, if this is not the case, the scripts raise an error. BZ It was not possible to configure and use multipath for iSCSI devices using different network interfaces on one subnet during installation as all devices used the default network interface. The "--iface[number]" option has been provided for the "iscsi" command to allow explicit specification of interface binding. Enhancements BZ# 821315 The "part" command can now take the "--hibernation" option, which allows specifying the size of the swap partition. The existing "--recommended" option follows the Installation Guide swap recommendation, which is not necessarily correct for all systems. This new option allows for a different sizing algorithm that can be more suitable, especially if the system uses hibernation. BZ# 790457 Logical Volume groups can now have free space reserved using either the "--reserved-space" or "--reserved-percent" parameters. The "--reserved-space" option takes a number representing megabytes as its argument, while the "--reserved-percent" option takes a number representing the percentage of the volume group that should be left free. The options can only be used for volume groups created during installation. All users of pykickstart are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Partitions required for raid
22.16.3. Adding a Peer Address To add the address of a peer, that is to say, the address of a server running an NTP service of the same stratum, make use of the peer command in the ntp.conf file. The peer command takes the following form: peer address where address is an IP unicast address or a DNS resolvable name. The address must only be that of a system known to be a member of the same stratum. Peers should have at least one time source that is different to each other. Peers are normally systems under the same administrative control.

Commands:
7.2. Enable Clustering in JBoss Data Virtualization Ensure JBoss Data Virtualization is installed on each JBoss EAP node and that JBoss EAP has started using either the standalone-ha.xml or the standalone-full-ha.xml profile before starting the cluster. (These profiles provide high availability, or clustering, as their names imply.) For more information, see the Red Hat JBoss Data Virtualization Installation Guide and Red Hat JBoss Enterprise Application Platform documentation. Note Artifacts such as VDBs cannot be deployed via file deployment when clustering is used. Use other methods of VDB deployment.

Commands:
Release notes Red Hat Satellite 6.15 Learn about added, deprecated, and removed features, known issues, and key references Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
hammer alternate-content-source bulk refresh-all
satellite-installer --foreman-rails-cache-store type:redis
satellite-installer --foreman-rails-cache-store type:file
Unable to load certs Neither PUB key nor PRIV key
permission denied to create extension "hstore"
subscription-manager repos --enable= reponame
subscription-manager repos --disable= reponame
4.282. sblim-cmpi-nfsv3 4.282.1. RHEA-2011:1578 - sblim-cmpi-nfsv3 bug fix and enhancement update An updated sblim-cmpi-nfsv3 package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The sblim-cmpi-nfsv3 package provides SBLIM (Standards Based Linux Instrumentation for Manageability) CMPI (Common Manageability Programming Interface) NFSv3 Providers for NFSv3 related CIM (Common Information Model) classes. The sblim-cmpi-nfsv3 package has been upgraded to upstream version 1.1.1, which provides a number of bug fixes and enhancements over the version. (BZ# 694508 ) All users of sblim-cmpi-nfsv3 are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 1. Red Hat JBoss Web Server 6.0 Service Pack 3 Welcome to the Red Hat JBoss Web Server version 6.0 Service Pack 3 release. Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library. JBoss Web Server includes the following key components: Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1. The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies. Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server. The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster , or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy , see the Apache HTTP Server Connectors and Load Balancing Guide . Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides. OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides. This release of JBoss Web Server includes an important security update. This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8.

Commands:
Chapter 15. Configuring Queue Proxy resources The Queue Proxy is a sidecar container to each application container within a service. It improves managing Serverless workloads, ensuring efficient resource usage. You can configure the Queue Proxy. 15.1. Configuring Queue Proxy Resources for a Knative Service Apart from configuring the Queue Proxy resource requests and limits globally in the deployment configmap, you can set them at the service level using the corresponding annotations targeting CPU, memory, and ephemeral storage resource types. Prerequisites Red Hat OpenShift Pipelines must be installed on your cluster. You have installed the OpenShift ( oc ) CLI. You have installed the Knative ( kn ) CLI. Procedure Modify the configmap of your service with resource requests and limits: apiVersion: serving.knative.dev/v1 kind: Service metadata: name: example-service namespace: default spec: template: metadata: annotations: queue.sidecar.serving.knative.dev/cpu-resource-request: "1" queue.sidecar.serving.knative.dev/cpu-resource-limit: "2" queue.sidecar.serving.knative.dev/memory-resource-request: "1Gi" queue.sidecar.serving.knative.dev/memory-resource-limit: "2Gi" queue.sidecar.serving.knative.dev/ephemeral-storage-resource-request: "400Mi" queue.sidecar.serving.knative.dev/ephemeral-storage-resource-limit: "450Mi" Alternatively, you can use the special queue.sidecar.serving.knative.dev/resource-percentage annotation, which calculates the Queue Proxy resources as a percentage of the application container. When CPU and memory resource requirements are calculated from the application container requirements and they are outside the boundaries below, the values are adjusted to fit within the boundaries. In this case, the following minimum and maximum boundaries are applied to the CPU and memory resource requirements: Table 15.1. Resource requirements boundaries Resource requirements Min Max CPU request 25m 100m CPU limit 40m 500m Memory request 50Mi 200Mi Memory limit 200Mi 500Mi Note If you simultaneously set a percentage annotation and a specific resource value using the corresponding resource annotation, then the latter takes precedence. Warning The queue.sidecar.serving.knative.dev/resource-percentage annotation is now deprecated and will be removed in a future version of OpenShift Serverless.

Commands:
apiVersion: serving.knative.dev/v1 kind: Service metadata: name: example-service namespace: default spec: template: metadata: annotations: queue.sidecar.serving.knative.dev/cpu-resource-request: "1" queue.sidecar.serving.knative.dev/cpu-resource-limit: "2" queue.sidecar.serving.knative.dev/memory-resource-request: "1Gi" queue.sidecar.serving.knative.dev/memory-resource-limit: "2Gi" queue.sidecar.serving.knative.dev/ephemeral-storage-resource-request: "400Mi" queue.sidecar.serving.knative.dev/ephemeral-storage-resource-limit: "450Mi"
Appendix A. Revision History Revision History Revision 9-1 Wed Mar 15 2017 Mirek Jahoda Version for 6.9 GA publication. Revision 9-0 Wed Dec 21 2016 Mirek Jahoda Version for 6.9 Beta publication. Revision 8-0 Wed May 3 2016 Robert Kratky Red Hat Enterprise Linux 6.8 GA release of the Managing Confined Services guide. Revision 7-1 Thu Jul 9 2015 Barbora Ancincova Red Hat Enterprise Linux 6.7 GA release of the Managing Confined Services guide. Revision 6-0 Fri Oct 10 2014 Barbora Ancincova Red Hat Enterprise Linux 6.4 GA release of the Managing Confined Services guide. Revision 5-0 Tue Nov 19 2013 Tomas Capek Red Hat Enterprise Linux 6.5 GA release of the Managing Confined Services guide. Revision 4-0 Fri Feb 22 2013 Tomas Capek Red Hat Enterprise Linux 6.4 GA release of the Managing Confined Services guide. Revision 3-0 Wed Jun 20 2012 Martin Prpic Red Hat Enterprise Linux 6.3 GA release of the Managing Confined Services guide. Revision 2-0 Tue Dec 6 2011 Martin Prpic Red Hat Enterprise Linux 6.2 GA release of the Managing Confined Services guide. Revision 1-0 Thu May 19 2011 Martin Prpic Red Hat Enterprise Linux 6.1 GA release of the Managing Confined Services guide. Revision 0-0 Tue Nov 9 2010 Scott Radvan 6.0 GA release

Commands:
Chapter 67. Constant Language Available as of Camel version 1.5 The Constant Expression Language is really just a way to specify constant strings as a type of expression. Note This is a fixed constant value that is only set once during starting up the route, do not use this if you want dynamic values during routing. 67.1. Constant Options The Constant language supports 1 options, which are listed below. Name Default Java Type Description trim true Boolean Whether to trim the value to remove leading and trailing whitespaces and line breaks 67.2. Example usage The setHeader element of the Spring DSL can utilize a constant expression like: <route> <from uri="seda:a"/> <setHeader headerName="theHeader"> <constant>the value</constant> </setHeader> <to uri="mock:b"/> </route> in this case, the Message coming from the seda:a Endpoint will have 'theHeader' header set to the constant value 'the value'. And the same example using Java DSL: from("seda:a") .setHeader("theHeader", constant("the value")) .to("mock:b"); 67.3. Dependencies The Constant language is part of camel-core .

Commands:
<route> <from uri="seda:a"/> <setHeader headerName="theHeader"> <constant>the value</constant> </setHeader> <to uri="mock:b"/> </route>
from("seda:a") .setHeader("theHeader", constant("the value")) .to("mock:b");
Chapter 3. Enabling automatic login You can enable automatic login in order to streamline your computing experience, avoiding the need to repeatedly enter your password during every session startup. This can be convenient for single-user environments where security risks are minimal, such as on a personal home computer that is not shared with others. Warning Enabling automatic login poses security risks. It allows direct access to the user account without requiring a password. This might lead to unauthorized use of the system or sensitive data. This risk is significant when the computer is shared, in public spaces, or physically accessible. Consider whether the login convenience outweighs the potential compromise of security and privacy. Procedure Open Settings . Click Users . Select the Unlock button and enter your password. Toggle the switch to enable automatic login. Once you have enabled automatic login, your computer will automatically log in to the specified user account the time you start it up.

Commands:
5.2. About Encrypted Disk Red Hat Gluster Storage provides the ability to create bricks on encrypted devices to restrict data access. Encrypted bricks can be used to create Red Hat Gluster Storage volumes. For information on creating encrypted disk, refer to the following product documentation: For RHEL 6, refer to Disk Encryption Appendix of the Red Hat Enterprise Linux 6 Installation Guide . Important Red Hat Gluster Storage is not supported on Red Hat Enterprise Linux 6 (RHEL 6) from 3.5 Batch Update 1 onwards. See Version Details table in section Red Hat Gluster Storage Software Components and Versions of the Installation Guide For RHEL 7, refer to Encryption of the Red Hat Enterprise Linux 7 Security Guide . Starting in RHEL 7.5, Red Hat has implemented an additional component that can be used to enable LUKS disks remotely during startup called as Network Bound Disk Encryption (NBDE). For more information on NBDE, refer to Configuring Automated Unlocking of Encrypted Volumes using Policy-Based Decryption of the Red Hat Enterprise Linux 7 Security Guide. For RHEL 8, refer to Encrypting Block Devices Using LUKS of the Red Hat Enterprise Linux 8 Security Guide.

Commands: