mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 10. Volume cloning A clone is a duplicate of an existing storage volume that is used as any standard volume. You create a clone of a volume to make a point in time copy of the data. A persistent volume claim (PVC) cannot be cloned with a different size. You can create up to 512 clones per PVC for both CephFS and RADOS Block Device (RBD). 10.1. Creating a clone Prerequisites Source PVC must be in Bound state and must not be in use. Note Do not create a clone of a PVC if a Pod is using it. Doing so might cause data corruption because the PVC is not quiesced (paused). Procedure Click Storage Persistent Volume Claims from the OpenShift Web Console. To create a clone, do one of the following: Beside the desired PVC, click Action menu (...) Clone PVC . Click on the PVC that you want to clone and click Actions Clone PVC . Enter a Name for the clone. Select the access mode of your choice. Important The ReadOnlyMany (ROX) access mode is a Developer Preview feature and is subject to Developer Preview support limitations. Developer Preview releases are not intended to be run in production environments and are not supported through the Red Hat Customer Portal case management system. If you need assistance with ReadOnlyMany feature, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules. See Creating a clone or restoring a snapshot with the new readonly access mode to use the ROX access mode. Click Clone . You are redirected to the new PVC details page. Wait for the cloned PVC status to become Bound . The cloned PVC is now available to be consumed by the pods. This cloned PVC is independent of its dataSource PVC.

Commands:
10.2. Encryption Ciphers The encryption cipher is configurable on a per-attribute basis and must be selected by the administrator at the time encryption is enabled for an attribute. The following ciphers are supported: Advanced Encryption Standard (AES) Triple Data Encryption Standard (3DES) Note For strong encryption, Red Hat recommends using only AES ciphers. All ciphers are used in Cipher Block Chaining mode. Once the encryption cipher is set, it should not be changed without exporting and reimporting the data.

Commands:
5. Authentication and Interoperability System Security Services Daemon (SSSD) The System Security Services Daemon (SSSD) implements a set of services for central management of identity and authentication. Centralizing identity and authentication services enables local caching of identities, allowing users to still identify in cases where the connection to the server is interrupted. SSSD supports many types of identity and authentication services, including: Red Hat Directory Server, OpenLDAP, 389, Kerberos and LDAP. SSSD in Red Hat Enterprise Linux 6.1 is updated to version 1.5, providing the following bug fixes and enhancements: Netgroups support Improved online/offline detection Improved LDAP access-control provider with support for shadow and authorizedService Improved caching and cleanup logic for different schemata Improved DNS based discovery Automatic Kerberos ticket renewal Enablement of the Kerberos FAST protocol Better handling of password expiration Note The Deployment Guide contains a section that describes how to install and configure SSSD. IPA Red Hat Enterprise Linux 6.1 features IPA as a Technology Preview. IPA is an integrated security information management solution which combines Red Hat Enterprise Linux, Red Hat Directory Server, MIT Kerberos, and NTP. It provides web browser and command-line interfaces, and its numerous administration tools allow an administrator to quickly install, set up, and administer one or more servers for centralized authentication and identity management. Note The Enterprise Identity Management Guide contains further information on the IPA Technology Preview. Samba Samba is an open source implementation of the Common Internet File System (CIFS) protocol. It allows the networking of Microsoft Windows, Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba in Red Hat Enterprise Linux 6.1 is updated to version 3.5.6. Samba in Red Hat Enterprise Linux 6.1 allows users to use their own Kerberos credentials when accessing CIFS mount, rather than needing the same mount credentials for all access to the mount. FreeRADIUS FreeRADIUS is an Internet authentication daemon, which implements the RADIUS protocol, as defined in RFC 2865 (and others). It allows Network Access Servers (NAS boxes) to perform authentication for dial-up users. FreeRADIUS in Red Hat Enterprise Linux 6.1 is updated to version 2.1.10. Kerberos Kerberos is a networked authentication system which allows users and computers to authenticate to each other with the help of a trusted third party, the KDC. In Red Hat Enterprise Linux 6.1, Kerberos (supplied by the krb5 package) is updated to version 1.9.

Commands:
Chapter 1. Insights client overview The Insights client ( insights-client ) is the client for Red Hat Insights for Red Hat Enterprise Linux. Run insights-client from the command line. 1.1. Red Hat Insights client distribution Insights client is available for the following releases of Red Hat Enterprise Linux (RHEL). RHEL release Comments RHEL 9 Distributed with Insights client pre-installed. RHEL 8 Distributed with Insights client pre-installed, unless RHEL 8 was installed as a minimal installation. RHEL 7 Distributed with the Insights client RPM package loaded but not installed. RHEL 6.10 and later You must download the Insights client RPM package and install it. Note Insights client installation on older versions RHEL versions 6 and 7 do not come with the Insights client pre-installed. If you have one of these versions, run the following commands in your terminal: Then, register the system to Red Hat Insights for Red Hat Enterprise Linux: Additional resources Getting Started with Insights

Commands:
yum install insights-client
insights-client --register
22.16. Configure NTP To change the default configuration of the NTP service, use a text editor running as root user to edit the /etc/ntp.conf file. This file is installed together with ntpd and is configured to use time servers from the Red Hat pool by default. The man page ntp.conf(5) describes the command options that can be used in the configuration file apart from the access and rate limiting commands which are explained in the ntp_acc(5) man page. 22.16.1. Configure Access Control to an NTP Service To restrict or control access to the NTP service running on a system, make use of the restrict command in the ntp.conf file. See the commented out example: The restrict command takes the following form: restrict address mask option where address and mask specify the IP addresses to which you want to apply the restriction, and option is one or more of: ignore - All packets will be ignored, including ntpq and ntpdc queries. kod - a " Kiss-o'-death " packet is to be sent to reduce unwanted queries. limited - do not respond to time service requests if the packet violates the rate limit default values or those specified by the discard command. ntpq and ntpdc queries are not affected. For more information on the discard command and the default values, see Section 22.16.2, "Configure Rate Limiting Access to an NTP Service" . lowpriotrap - traps set by matching hosts to be low priority. nomodify - prevents any changes to the configuration. noquery - prevents ntpq and ntpdc queries, but not time queries, from being answered. nopeer - prevents a peer association being formed. noserve - deny all packets except ntpq and ntpdc queries. notrap - prevents ntpdc control message protocol traps. notrust - deny packets that are not cryptographically authenticated. ntpport - modify the match algorithm to only apply the restriction if the source port is the standard NTP UDP port 123 . version - deny packets that do not match the current NTP version. To configure rate limit access to not respond at all to a query, the respective restrict command has to have the limited option. If ntpd should reply with a KoD packet, the restrict command needs to have both limited and kod options. The ntpq and ntpdc queries can be used in amplification attacks (see CVE-2013-5211 for more details), do not remove the noquery option from the restrict default command on publicly accessible systems.

Commands:
Hosts on local network are less restricted. #restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
23.5. Creating an LDIF File with Nested Example Entries Use the dsctl ldifgen nested command to create an LDIF file that contains a heavily nested cascading fractal structure. For example, to create an LDIF file named /tmp/nested.nldif , that adds 600 users in total in different organization units (OU) under the dc=example,dc=com entry, with each OU containing a maximum number of 100 users: For further details about the options, enter:

Commands:
dsctl instance_name ldifgen nested --num-users 600 --node-limit 100 --suffix "dc=example,dc=com"
dsctl instance_name ldifgen nested --help
Chapter 3. KVM Guest Virtual Machine Compatibility To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the Red Hat Enterprise Linux Virtualization Administration Guide . 3.1. Red Hat Enterprise Linux 6 Support Limits Red Hat Enterprise Linux 6 servers have certain support limits. The following URLs explain the processor and memory amount limitations for Red Hat Enterprise Linux: For host systems: http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits For hypervisors: http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors Note Red Hat Enterprise Linux 6.5 now supports 4TiB of memory per KVM guest. The following URL is a complete reference showing supported operating systems and host and guest combinations: http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support

Commands:
B.3. Create a Private/Public Key Pair with Keytool Procedure B.1. Create a Private/Public Key Pair with Keytool Run the keytool -genkey -alias ALIAS -keyalg ALGORITHM -validity DAYS -keystore server.keystore -storetype TYPE command: If the specified keystore already exists, enter the existing password for that keystore, otherwise enter a new password: Answer the following questions when prompted: Enter yes to confirm the provided information is correct: Enter your desired keystore password: Result The server.keystore file contains the newly generated public and private key pair.

Commands:
keytool -genkey -alias teiid -keyalg RSA -validity 365 -keystore server.keystore -storetype JKS
Enter keystore password: <password>
What is your first and last name? [Unknown]: <userA¢A\u0080A\u0099s name> What is the name of your organizational unit? [Unknown]: <department name> What is the name of your organization? [Unknown]: <company name> What is the name of your City or Locality? [Unknown]: <city name> What is the name of your State or Province? [Unknown]: <state name> What is the two-letter country code for this unit? [Unknown]: <country name>
Is CN=<userA¢A\u0080A\u0099s name>, OU=<department name>, O="<company name>", L=<city name>, ST=<state name>, C=<country name> correct? [no]: yes
Enter key password for <server> (Return if same as keystore password)
Chapter 1. Red Hat Advanced Cluster Security for Kubernetes 4.5 Documentation Welcome to the official Red Hat Advanced Cluster Security for Kubernetes documentation, where you can learn about Red Hat Advanced Cluster Security for Kubernetes and start exploring its features. To go to the Red Hat Advanced Cluster Security for Kubernetes documentation, you can use one of the following methods: Use the left navigation bar to browse the documentation. Select the task that interests you from the contents of this Welcome page. 1.1. Installation activities Understanding installation methods for different platforms : Determine the best installation method for your product and platform. 1.2. Operating Red Hat Advanced Cluster Security for Kubernetes Explore various activities you can perform by using Red Hat Advanced Cluster Security for Kubernetes: Viewing the dashboard : Find information about the Red Hat Advanced Cluster Security for Kubernetes real-time interactive dashboard. Learn how to use it to view key metrics from all your hosts, containers, and services. Compliance feature overview : Understand how to run automated checks and validate compliance based on industry standards, including CIS, NIST, PCI, and HIPAA. Managing vulnerabilities : Learn how to identify and prioritize vulnerabilities for remediation. Responding to violations : Learn how to view policy violations, drill down to the actual cause of the violation, and take corrective actions. 1.3. Configuring Red Hat Advanced Cluster Security for Kubernetes Explore the following typical configuration tasks in Red Hat Advanced Cluster Security for Kubernetes: Adding custom certificates : Learn how to use a custom TLS certificate with Red Hat Advanced Cluster Security for Kubernetes. After you set up a certificate, users and API clients do not have to bypass the certificate security warnings. Backing up Red Hat Advanced Cluster Security for Kubernetes : Learn how to perform manual and automated data backups for Red Hat Advanced Cluster Security for Kubernetes and use these backups for data restoration in the case of an infrastructure disaster or corrupt data. Configuring automatic upgrades for secured clusters : Stay up to date by automating the upgrade process for each secured cluster. 1.4. Integrating with other products Learn how to integrate Red Hat Advanced Cluster Security for Kubernetes with the following products: Integrating with PagerDuty : Learn how to integrate with PagerDuty and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to PagerDuty. Integrating with Slack : Learn how to integrate with Slack and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Slack. Integrating with Sumo Logic : Learn how to integrate with Sumo Logic and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Sumo Logic. Integrating by using the syslog protocol : Learn how to integrate with a security information and event management (SIEM) system or a syslog collector for data retention and security investigations.

Commands:
Chapter 10. Support policies Supported for certain RHEL releases: RHEL for SAP Solutions follows the general RHEL product lifecycle and related policies . Important SAP defines its own release strategy regarding the support of operating systems and operating system versions. For SAP NetWeaver-based solutions, refer to the SAP Product Availability Matrix . For SAP HANA, see SAP Note 2235581 . For general information, see SAP Note 2369910 . Production environments must comply with Red Hat and SAP support conditions. Additional SAP certifications may apply. Intel Optane DC Persistent Memory File System DAX support: Red Hat fully supports Intel Optane DC Persistent Memory (pMEM) File System DAX (FS-DAX) as part of RHEL for SAP Solutions for production deployments of SAP HANA 2.0 SPS 04, revision 40 (or later). For more information, see Red Hat fully supports persistent memory (pMEM) FS-DAX mode in RHEL 7.6 and later versions for SAP Solutions . Support for RHEL HA clusters, as part of RHEL for SAP Solutions: The RHEL for SAP Solutions subscription includes the Red Hat Enterprise Linux (RHEL) High Availability Add-on. Users of RHEL High Availability clusters should adhere to general Support Policies for RHEL High Availability Clusters in order to be eligible for support. In addition, RHEL for SAP Solutions provides resource agents, scripts and documentation for integration with & support of the following SAP applications and scenarios: Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications .

Commands:
2.15. The Virtual Database The critical artifact that Teiid Designer is intended to manage is the VDB, or Virtual DataBase. Through the JBoss Data Virtualization server, VDB's behave like standard JDBC database schema which can be connected to, queried and updated based on how the VDB is configured. Since VDB's are just databases once they are deployed, they can be used as sources to other view model transformations. This allows creating and deploying re-usable or common VDB's in multiple layers depending on your business needs.

Commands:
20.10. Resource Partitioning Hypervisors may allow for virtual machines to be placed into resource partitions, potentially with nesting of said partitions. The <resource> element groups together configuration related to resource partitioning. It currently supports a child element partition whose content defines the path of the resource partition in which to place the domain. If no partition is listed, then the domain will be placed in a default partition. It is the responsibility of the app/admin to ensure that the partition exists prior to starting the guest virtual machine. Only the (hypervisor specific) default partition can be assumed to exist by default. <resource> <partition>/virtualmachines/production</partition> </resource> Figure 20.12. Resource partitioning Resource partitions are currently supported by the QEMU and LXC drivers, which map partition paths to cgroups directories in all mounted controllers.

Commands:
<resource> <partition>/virtualmachines/production</partition> </resource>
B. Package Updates Important The Red Hat Enterprise Linux 6 Technical Notes compilations for Red Hat Enterprise Linux 6.0, 6.1 and 6.2 have been republished. Each compilation still lists all advisories comprising their respective GA release, including all Fastrack advisories. To more accurately represent the advisories released between minor updates of Red Hat Enterprise Linux, however, some advisories released asynchronously between minor releases have been relocated. Previously, these asynchronously released advisories were published in the Technical Notes for the most recent Red Hat Enterprise Linux minor upate. Asynchronous advisories released after the release of Red Enterprise Linux 6.1 and before the release of Red Hat Enterprise Linux 6.2 were published in the Red Hat Enterprise Linux 6.2 Technical Notes, for example. Most of these asynchronous advisories were concerned with, or even specific to, the then extant Red Hat Enterprise Linux release, however. With these republished Technical Notes, such advisories are now incorporated into the Technical Notes for the Red Hat Enterprise Linux release they are associated with. Future Red Hat Enterprise Linux Technical Notes will follow this pattern. On first publication a Red Hat Enterprise Linux X.y Technical Notes compilation will include the advisories comprising that release along with the Fastrack advisories for the release. Upon the GA of the succeeding Red Hat Enterprise Linux release, the Red Hat Enterprise Linux X.y Technical Notes compilation will be republished to include associated asynchronous advisories released since Red Hat Enterprise Linux X.y GA up until the GA of the successive release. B.1. apr B.1.1. RHSA-2011:0507 - Moderate: apr security update Updated apr packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The Apache Portable Runtime (APR) is a portability library used by the Apache HTTP Server and other projects. It provides a free library of C data structures and routines. CVE-2011-0419 It was discovered that the apr_fnmatch() function used an unconstrained recursion when processing patterns with the '*' wildcard. An attacker could use this flaw to cause an application using this function, which also accepted untrusted input as a pattern for matching (such as an httpd server using the mod_autoindex module), to exhaust all stack memory or use an excessive amount of CPU time when performing matching. Red Hat would like to thank Maksymilian Arciemowicz for reporting this issue. All apr users should upgrade to these updated packages, which contain a backported patch to correct this issue. Applications using the apr library, such as httpd, must be restarted for this update to take effect.

Commands:
Chapter 1. Introduction 1.1. What is RHEL for SAP Solutions RHEL for SAP Solutions is a Red Hat subscription that consists of Red Hat Enterprise Linux and additional software repositories and services specifically designed for running SAP HANA and/or SAP ABAP Platform, including SAP S/4HANA, on Red Hat Enterprise Linux. For more information, refer to Overview of Red Hat Enterprise Linux for SAP Solutions Subscription . RHEL for SAP Solutions consists of the following repositories: 1.2. Overview of the installation steps Installing Red Hat Enterprise Linux (RHEL) 9 for SAP Solutions consists of the following steps: Install RHEL 9 using one of the standard Red Hat Enterprise Linux 9 installation ISO images. Install additional packages needed for running SAP software, either from another repository source, for example, a Red Hat Satellite system, or from the RHEL 9 for SAP Solutions image, which contains only a set of additional packages needed for SAP. Note There are also ISO images named Red Hat Enterprise Linux for SAP Solutions, but those only contain the additional software packages required to be installed on top of Red Hat Enterprise Linux. It is not possible to install RHEL for SAP Solutions from these ISO images. The recommended and easiest way is to install Red Hat Enterprise Linux 9, attach it to a repository source, and then use the RHEL System Roles for SAP for: installing additional software packages and configuring the system according to the requirements of the SAP software.

Commands:
21.6. Sample Parameter File and CMS Configuration File To change the parameter file, begin by extending the shipped generic.prm file. Example of generic.prm file: Example of redhat.conf file configuring a QETH network device (pointed to by CMSCONFFILE in generic.prm ):

Commands:
ro ramdisk_size=40000 cio_ignore=all,!condev CMSDASD="191" CMSCONFFILE="redhat.conf" vnc inst.repo=http://example.com/path/to/repository
NETTYPE="qeth" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" PORTNO="0" LAYER2="1" MACADDR="02:00:be:3a:01:f3" HOSTNAME="foobar.systemz.example.com" IPADDR="192.168.17.115" NETMASK="255.255.255.0" GATEWAY="192.168.17.254" DNS="192.168.17.1" SEARCHDNS="systemz.example.com:example.com" DASD="200-203"
Chapter 1. Introducing .NET 8.0 .NET is a general-purpose development platform featuring automatic memory management and modern programming languages. Using .NET, you can build high-quality applications efficiently. .NET is available on Red Hat Enterprise Linux (RHEL) and OpenShift Container Platform through certified containers. .NET offers the following features: The ability to follow a microservices-based approach, where some components are built with .NET and others with Java, but all can run on a common, supported platform on RHEL and OpenShift Container Platform. The capacity to more easily develop new .NET workloads on Microsoft Windows. You can deploy and run your applications on either RHEL or Windows Server. A heterogeneous data center, where the underlying infrastructure is capable of running .NET applications without having to rely solely on Windows Server. .NET 8.0 is supported on RHEL 8.9 and later, RHEL 9.3 and later, and supported OpenShift Container Platform versions.

Commands: