mtpti5iD/redhat-docs_dataset huggingface dataset:
14.5. Archiving File Systems With ACLs Warning The tar and dump commands do not backup ACLs. The star utility is similar to the tar utility in that it can be used to generate archives of files; however, some of its options are different. Refer to Table 14.1, "Command Line Options for star " for a listing of more commonly used options. For all available options, refer to the star man page. The star package is required to use this utility. Table 14.1. Command Line Options for star Option Description -c Creates an archive file. -n Do not extract the files; use in conjunction with -x to show what extracting the files does. -r Replaces files in the archive. The files are written to the end of the archive file, replacing any files with the same path and file name. -t Displays the contents of the archive file. -u Updates the archive file. The files are written to the end of the archive if they do not exist in the archive or if the files are newer than the files of the same name in the archive. This option only work if the archive is a file or an unblocked tape that may backspace. -x Extracts the files from the archive. If used with -U and a file in the archive is older than the corresponding file on the file system, the file is not extracted. -help Displays the most important options. -xhelp Displays the least important options. -/ Do not strip leading slashes from file names when extracting the files from an archive. By default, they are striped when files are extracted. -acl When creating or extracting, archive or restore any ACLs associated with the files and directories.

Commands:
Chapter 2. Managing your cluster resources You can apply global configuration options in OpenShift Container Platform. Operators apply these configuration settings across the cluster. 2.1. Interacting with your cluster resources You can interact with cluster resources by using the OpenShift CLI ( oc ) tool in OpenShift Container Platform. The cluster resources that you see after running the oc api-resources command can be edited. Prerequisites You have access to the cluster as a user with the cluster-admin role. You have access to the web console or you have installed the oc CLI tool. Procedure To see which configuration Operators have been applied, run the following command: USD oc api-resources -o name | grep config.openshift.io To see what cluster resources you can configure, run the following command: USD oc explain <resource_name>.config.openshift.io To see the configuration of custom resource definition (CRD) objects in the cluster, run the following command: USD oc get <resource_name>.config -o yaml To edit the cluster resource configuration, run the following command: USD oc edit <resource_name>.config -o yaml

Commands:
oc api-resources -o name | grep config.openshift.io
oc explain <resource_name>.config.openshift.io
oc get <resource_name>.config -o yaml
oc edit <resource_name>.config -o yaml
5.46. db4 5.46.1. RHBA-2012:0452 - db4 bug fix update An updated db4 package that fixes one bug is now available for Red Hat Enterprise Linux 6. The Berkeley Database (Berkeley DB) is a programmatic toolkit that provides embedded database support for both traditional and client/server applications. The Berkeley DB includes B+tree, Extended Linear Hashing, Fixed and Variable-length record access methods, transactions, locking, logging, shared memory caching, and database recovery. The Berkeley DB supports C, C++, Java, and Perl APIs. It is used by many applications, including Python and Perl, so this should be installed on all systems. Bug Fix BZ# 784662 The db4 spec file incorrectly stated that the "License" is simply "BSD", whereas it is in fact licensed under both the BSD and Sleepycat licenses, the latter of which differs from the Berkeley Software Distribution (BSD) license by including a redistribution clause. This update corrects the spec file so it correctly states that the db4 software is provided under the "Sleepycat and BSD" license. Users of db4 are advised to upgrade to this updated package which fixes this bug. 5.46.2. RHBA-2013:1444 - db4 bug fix update Updated db4 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Berkeley Database (Berkeley DB) is a programmatic toolkit that provides embedded database support for both traditional and client/server applications. The Berkeley DB includes B+tree, Extended Linear Hashing, Fixed and Variable-length record access methods, transactions, locking, logging, shared memory caching, and database recovery. The Berkeley DB supports C, C++, Java, and Perl APIs. It is used by many applications, including Python and Perl, so this should be installed on all systems. Bug Fix BZ# 1012586 Due to an incorrect order of the mutex initialization calls, the rpm utility became unresponsive under certain circumstances, until it was terminated. With this update, the order of the mutex initialization calls has been revised. As a result, the rpm utility no longer becomes unresponsive. Users of db4 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 72. KafkaExporterTemplate schema reference Used in: KafkaExporterSpec Property Property type Description deployment DeploymentTemplate Template for Kafka Exporter Deployment . pod PodTemplate Template for Kafka Exporter Pods . service ResourceTemplate The service property has been deprecated. The Kafka Exporter service has been removed. Template for Kafka Exporter Service . container ContainerTemplate Template for the Kafka Exporter container. serviceAccount ResourceTemplate Template for the Kafka Exporter service account.

Commands:
Appendix B. Revision History Revision History Revision 2.2-2 Wed Mar 15 2017 Marie Dolezelova Version for 6.9 GA publication. Revision 2.2-1 Tue May 10 2016 Jana Heves Version for 6.8 GA release Revision 1.0-36 Sat Feb 27 2016 Jana Heves Version for 6.8 Beta release Revision 1.0-35 Fri Oct 10 2014 Yoana Ruseva Version for 6.6 GA release Revision 1.0-34 Fri Aug 8 2014 Yoana Ruseva Version for 6.6 Beta release Revision 1.0-33 Wed Sep 25 2013 Yoana Ruseva Version for 6.5 GA release Revision 1.0-25 Tue Feb 19 2013 Jack Reed Version for 6.4 GA release Revision 1.0-18 Tue Oct 30 2012 Jack Reed Added cpupower related admonitions, and updated function of --policy option Revision 1.0-15 Thu Oct 18 2012 Jack Reed Added CPU Monitors and CPU Power Saving Policies sections Revision 1.0-14 Fri Feb 10 2012 Jack Reed Added new tuned profiles Revision 1.0-0 Thu Oct 7 2010 Rudiger Landmann Version for 6.0 GA release

Commands:
Chapter 3. Installing the all-in-one Red Hat OpenStack Platform environment Before you can begin configuring, deploying, and testing your all-in-one environment, you must configure a non-root user and install the necessary packages and dependencies: Procedure Create a non-root user on the all-in-one host: Set the password for the stack user: Disable password requirements for the sudo command for stack user: Log in as the non-root user on the all-in-one host: Register the machine with Red Hat Subscription Manager. Enter your Red Hat subscription credentials at the prompt: Attach your Red Hat subscription to the entitlement server: Note The --auto option might not subscribe you to the correct subscription pool. Ensure that you subscribe to the correct pool, otherwise you might not be able to enable all of the necessary repositories for this installation. Use the subscription-manager list --all --available command to identify the correct pool ID. Lock the undercloud to Red Hat Enterprise Linux 8.4: Enter the following commands to install dnf-utils , disable all default repositories, and then enable the necessary repositories: Note The all-in-one environment is a Technology Preview feature in Red Hat OpenStack Platform 16. Set the container-tools module version: Update the base operating system and reboot the system: Log back in to the host after the reboot. Install the TripleO command line interface (CLI):

Commands:
useradd stack
passwd stack
echo "stack ALL=(root) NOPASSWD:ALL" | tee -a /etc/sudoers.d/stack chmod 0440 /etc/sudoers.d/stack
ssh stack@<all-in-one>
[stack@all-in-one]USD sudo subscription-manager register
[stack@all-in-one]USD sudo subscription-manager attach --auto
sudo subscription-manager release --set=8.4
[stack@all-in-one]USD sudo dnf install -y dnf-utils [stack@all-in-one]USD sudo subscription-manager repos --disable=* [stack@all-in-one]USD sudo subscription-manager repos --enable=rhel-8-for-x86_64-baseos-eus-rpms --enable=rhel-8-for-x86_64-appstream-eus-rpms --enable=rhel-8-for-x86_64-highavailability-eus-rpms --enable=ansible-2.9-for-rhel-8-x86_64-rpms --enable=openstack-16.2-for-rhel-8-x86_64-rpms --enable=fast-datapath-for-rhel-8-x86_64-rpms
[stack@all-in-one]USD sudo dnf module disable -y container-tools:rhel8 [stack@all-in-one]USD sudo dnf module enable -y container-tools:3.0
[stack@all-in-one]USD sudo dnf update [stack@all-in-one]USD sudo reboot
[stack@all-in-one]USD sudo dnf install -y python3-tripleoclient
Chapter 1. Support policy for Red Hat build of OpenJDK Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these are the same versions that Oracle designates as long-term support (LTS) for the Oracle JDK. A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy . Note RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration.

Commands:
Chapter 9. Logging 9.1. Configuring logging AMQ JavaScript uses the JavaScript debug module to implement logging. For example, to enable detailed client logging, set the DEBUG environment variable to rhea* : Example: Enabling detailed logging USD export DEBUG=rhea* USD <your-client-program> 9.2. Enabling protocol logging The client can log AMQP protocol frames to the console. This data is often critical when diagnosing problems. To enable protocol logging, set the DEBUG environment variable to rhea:frames : Example: Enabling protocol logging USD export DEBUG=rhea:frames USD <your-client-program>

Commands:
export DEBUG=rhea* <your-client-program>
export DEBUG=rhea:frames <your-client-program>
8.51. gegl 8.51.1. RHBA-2013:1021 - gegl bug fix update Updated gegl packages that fix one bug are now available for Red Hat Enterprise Linux 6. GEGL (Generic Graphics Library) is a graph-based image processing framework. Bug Fix BZ#620378 Documentation files were installed executable. As a consequence, testing tools failed due to that configuration. To fix this bug, executable bits were removed from documentation files and testing tools now work as expected in the described scenario. Users of gegl are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.2.3. Qt The qt package provides the Qt (pronounced "cute") cross-platform application development framework used in the development of GUI programs. Aside from being a popular "widget toolkit", Qt is also used for developing non-GUI programs such as console tools and servers. Qt was used in the development of notable projects such as Google Earth, KDE, Opera, OPIE, VoxOx, Skype, VLC media player and VirtualBox. It is produced by Nokia's Qt Development Frameworks division, which came into being after Nokia's acquisition of the Norwegian company Trolltech, the original producer of Qt, on June 17, 2008. Qt uses standard C++ but makes extensive use of a special pre-processor called the Meta Object Compiler (MOC) to enrich the language. Qt can also be used in other programming languages via language bindings. It runs on all major platforms and has extensive internationalization support. Non-GUI Qt features include SQL database access, XML parsing, thread management, network support, and a unified cross-platform API for file handling. Distributed under the terms of the GNU Lesser General Public License (among others), Qt is free and open source software. The Red Hat Enterprise Linux 6 version of Qt supports a wide range of compilers, including the GCC C++ compiler and the Visual Studio suite. 2.2.3.1. Qt Updates Some of the improvements the Red Hat Enterprise Linux 6 version of Qt include: Advanced user experience Advanced Graphics Effects: options for opacity, drop-shadows, blur, colorization, and other similar effects Animation and State Machine: create simple or complex animations without the hassle of managing complex code Gesture and multi-touch support Support for new platforms Windows 7, Mac OSX 10.6, and other desktop platforms are now supported Added support for mobile development; Qt is optimized for the upcoming Maemo 6 platform, and will soon be ported to Maemo 5. In addition, Qt now supports the Symbian platform, with integration for the S60 framework. Added support for Real-Time Operating Systems such as QNX and VxWorks Improved performance, featuring added support for hardware-accelerated rendering (along with other rendering updates) Updated cross-platform IDE For more details on updates to Qt included in Red Hat Enterprise Linux 6, see the following links: http://doc.qt.nokia.com/4.6/qt4-6-intro.html http://doc.qt.nokia.com/4.6/qt4-intro.html

Commands:
Chapter 68. JmxTransOutputDefinitionTemplate schema reference Used in: JmxTransSpec Property Property type Description outputType string Template for setting the format of the data that will be pushed.For more information see JmxTrans OutputWriters . host string The DNS/hostname of the remote host that the data is pushed to. port integer The port of the remote host that the data is pushed to. flushDelayInSeconds integer How many seconds the JmxTrans waits before pushing a new set of data out. typeNames string array Template for filtering data to be included in response to a wildcard query. For more information see JmxTrans queries . name string Template for setting the name of the output definition. This is used to identify where to send the results of queries should be sent.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 8 is distributed with the kernel version 4.18, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, little endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For a list of available subscriptions, see Subscription Utilization on the Customer Portal. Note that all architectures are supported by the standard kernel packages in RHEL 8; no kernel-alt package is needed.

Commands:
Chapter 14. Unique UID and GID Number Assignments An IdM server generates user ID (UID) and group ID (GID) values and simultaneously ensures that replicas never generate the same IDs. The need for unique UIDs and GIDs might even be across IdM domains, if a single organization uses multiple separate domains. 14.1. ID Ranges The UID and GID numbers are divided into ID ranges . By keeping separate numeric ranges for individual servers and replicas, the chances are minimal that an ID value issued for an entry is already used by another entry on another server or replica. The Distributed Numeric Assignment (DNA) plug-in, as part of the back end 389 Directory Server instance for the domain, ensures that ranges are updated and shared between servers and replicas; the plug-in manages the ID ranges across all masters and replicas. Every server or replica has a current ID range and an additional ID range that the server or replica uses after the current range has been depleted. For more information about the DNA Directory Server plug-in, see the Red Hat Directory Server Deployment Guide .

Commands:
Chapter 1. Executive summary Many hardware vendors now offer both Ceph-optimized servers and rack-level solutions designed for distinct workload profiles. To simplify the hardware selection process and reduce risk for organizations, Red Hat has worked with multiple storage server vendors to test and evaluate specific cluster options for different cluster sizes and workload profiles. Red Hat's exacting methodology combines performance testing with proven guidance for a broad range of cluster capabilities and sizes. With appropriate storage servers and rack-level solutions, Red Hat Ceph Storage can provide storage pools serving a variety of workloads-from throughput-sensitive and cost and capacity-focused workloads to emerging IOPS-intensive workloads. Red Hat Ceph Storage significantly lowers the cost of storing enterprise data and helps organizations manage exponential data growth. The software is a robust and modern petabyte-scale storage platform for public or private cloud deployments. Red Hat Ceph Storage offers mature interfaces for enterprise block and object storage, making it an optimal solution for active archive, rich media, and cloud infrastructure workloads characterized by tenant-agnostic OpenStack(R) environments [1] . Delivered as a unified, software-defined, scale-out storage platform, Red Hat Ceph Storage lets businesses focus on improving application innovation and availability by offering capabilities such as: Scaling to hundreds of petabytes [2] . No single point of failure in the cluster. Lower capital expenses (CapEx) by running on commodity server hardware. Lower operational expenses (OpEx) with self-managing and self-healing properties. Red Hat Ceph Storage can run on myriad industry-standard hardware configurations to satisfy diverse needs. To simplify and accelerate the cluster design process, Red Hat conducts extensive performance and suitability testing with participating hardware vendors. This testing allows evaluation of selected hardware under load and generates essential performance and sizing data for diverse workloads-ultimately simplifying Ceph storage cluster hardware selection. As discussed in this guide, multiple hardware vendors now provide server and rack-level solutions optimized for Red Hat Ceph Storage deployments with IOPS-, throughput-, and cost and capacity-optimized solutions as available options. Software-defined storage presents many advantages to organizations seeking scale-out solutions to meet demanding applications and escalating storage needs. With a proven methodology and extensive testing performed with multiple vendors, Red Hat simplifies the process of selecting hardware to meet the demands of any environment. Importantly, the guidelines and example systems listed in this document are not a substitute for quantifying the impact of production workloads on sample systems. [1] Ceph is and has been the leading storage for OpenStack according to several semi-annual OpenStack user surveys. [2] See Yahoo Cloud Object Store - Object Storage at Exabyte Scale for details.

Commands:
Chapter 6. BIOS, firmware, and hardware policies 6.1. Production level BIOS, Firmware, and Hardware versions are required to be production-level (e.g. feature complete without major changes pending and/or upgraded to production equivalent) during testing. Changes subsequent to testing are required to meet the Changes criteria below. The tested or a later revision is required to be available to and without customer interactions in the Instance Type by the posting date of the certification. 6.2. Changes BIOS, Firmware, and Hardware changes that enable or disable features necessitate recertification. Re-certification is not required for changes to correct small flaws and minor bugs and/or alter superficial items like splash screens and silkscreens. Partners are expected to have internal testing of these changes to verify they do not adversely affect customers, Red Hat Enterprise Linux, or the certification status. The results of this testing is not required to be submitted to Red Hat. 6.3. Settings Any required BIOS/Firmware configuration information must be provided in a comment in the certification request. Providing suggested and/or default configuration data is encouraged but not required. Vendor provided configuration information may be provided in the certification listing using an associated Red Hat Knowledge Base Solution. Validating alternate configuration settings do not expose data corruption issues or unexpectedly disrupt functionality is the responsibility of the hardware vendor. Important User configurable BIOS settings that enable/disable hardware features and/or functions must be set such that the feature or function is enabled during testing. 6.4. Configuration limits CCSP Instances available in configurations beyond the Red Hat product limits may still be eligible for certification. Testing will need to be performed demonstrating functionality within the limits and the partner will need to decide if they also want to pursue the features beyond the limits. Like all Red Hat Enterprise Linux feature requests, the required time lines, development, and testing efforts are determined on a case-by-case basis and are considered outside of the certification process. A Red Hat Knowledge Base article can be added to the certification listing for clarity. Important Vendors are encouraged to work with their Hardware Partner Manager and Partner Technical Account Managers (TAMs) on feature requests to raise the relevant Red Hat Enterprise Linux product limits prior to the certification effort. Additional resources For more information about the current supported limits for Red Hat Enterprise Linux, see Red Hat Enterprise Linux technology capabilities and limits . 6.5. Performance limits In general, Red Hat places the responsibility of performance testing on the Partner; however, major performance issues that are deemed to have significant customer impact may delay certification until a resolution is determined.

Commands:
Chapter 106. KafkaUserAuthorizationSimple schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserAuthorizationSimple type from other subtypes which may be added in the future. It must have the value simple for the type KafkaUserAuthorizationSimple . Property Description type Must be simple . string acls List of ACL rules which should be applied to this user. AclRule array

Commands:
Chapter 6. Hardware Enablement Intel Ethernet server adapter X710/XL710 support Red Hat Enterprise Linux 6.7 adds the i40e and i40evf kernel drivers, which enable support for Intel X710 and XL710 family Ethernet adapters. These drivers are provided as Technology Preview only. Realtek 5229 card reader support This update introduces support for the Realtek 5229 card reader. AMD GX-212JC processor support This update introduces support for the AMD GX-212JC processor.

Commands:
Chapter 1. Nagios and Ceph Nagios Core is an open-source solution for monitoring nodes. Large Red Hat Ceph Storage clusters benefit from distributed monitoring systems such as Nagios Core. The Nagios Core checks each node in a cluster, including the health of the underlying operating system, as well as the health of the Red Hat Ceph Storage cluster daemons. To deploy Nagios Core with Ceph requires: A running Red Hat Ceph Storage cluster. Instead of Nagios Core, you can also substitute the more feature-rich commercial version, Nagios XI. Important Red Hat does not provide the Nagios packages. Important Red Hat works with our technology partners to provide this documentation as a service to our customers. However, Red Hat does not provide support for this product. If you need technical assistance with this product, then contact Nagios for support.

Commands: