mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Overview Red Hat OpenShift Data Foundation is software-defined storage that is optimized for container environments. It runs as an operator on OpenShift Container Platform to provide highly integrated and simplified persistent storage management for containers. Red Hat OpenShift Data Foundation is integrated into the latest Red Hat OpenShift Container Platform to address platform services, application portability, and persistence challenges. It provides a highly scalable backend for the generation of cloud-native applications, built on a technology stack that includes Red Hat Ceph Storage, the Rook.io Operator, and NooBaa's Multicloud Object Gateway technology. Red Hat OpenShift Data Foundation is designed for FIPS. When running on RHEL or RHEL CoreOS booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries submitted to NIST for FIPS Validation on only the x86_64, ppc64le, and s390X architectures. For more information about the NIST validation program, see Cryptographic Module Validation Program . For the latest NIST status for the individual versions of the RHEL cryptographic libraries submitted for validation, see Compliance Activities and Government Standards . Red Hat OpenShift Data Foundation provides a trusted, enterprise-grade application development environment that simplifies and enhances the user experience across the application lifecycle in a number of ways: Provides block storage for databases. Shared file storage for continuous integration, messaging, and data aggregation. Object storage for cloud-first development, archival, backup, and media storage. Scale applications and data exponentially. Attach and detach persistent data volumes at an accelerated rate. Stretch clusters across multiple data-centers or availability zones. Establish a comprehensive application container registry. Support the generation of OpenShift workloads such as Data Analytics, Artificial Intelligence, Machine Learning, Deep Learning, and Internet of Things (IoT). Dynamically provision not only application containers, but data service volumes and containers, as well as additional OpenShift Container Platform nodes, Elastic Block Store (EBS) volumes and other infrastructure services. 1.1. About this release Red Hat OpenShift Data Foundation 4.16 ( RHSA-2024:4591 ) is now available. New enhancements, features, and known issues that pertain to OpenShift Data Foundation 4.16 are included in this topic. Red Hat OpenShift Data Foundation 4.16 is supported on the Red Hat OpenShift Container Platform version 4.16. For more information, see Red Hat OpenShift Data Foundation Supportability and Interoperability Checker . For Red Hat OpenShift Data Foundation life cycle information, refer to the layered and dependent products life cycle section in Red Hat OpenShift Container Platform Life Cycle Policy .

Commands:
C.12. LockManager org.infinispan.util.concurrent.locks.LockManagerImpl The LockManager component handles MVCC locks for entries. Table C.21. Attributes Name Description Type Writable concurrencyLevel The concurrency level that the MVCC Lock Manager has been configured with. int No numberOfLocksAvailable The number of exclusive locks that are available. int No numberOfLocksHeld The number of exclusive locks that are held. int No 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 27. Use Red Hat JBoss Data Grid with Amazon Web Services 27.1. The S3_PING JGroups Discovery Protocol S3_PING is a discovery protocol that is ideal for use with Amazon's Elastic Compute Cloud (EC2) because EC2 does not allow multicast and therefore MPING is not allowed. Each EC2 instance adds a small file to an S3 data container, known as a bucket. Each instance then reads the files in the bucket to discover the other members of the cluster. Report a bug

Commands:
Chapter 5. Changes in Rust 1.75.0 Toolset Rust Toolset has been updated from version 1.71.1 to 1.75.0 on RHEL 8 and RHEL 9. Notable changes include: Constant evaluation time is now unlimited Cleaner panic messages Cargo registry authentication async fn and opaque return types in traits For detailed information regarding the updates, see the series of upstream release announcements: Announcing Rust 1.72.0 . Announcing Rust 1.73.0 . Announcing Rust 1.74.0 . Announcing Rust 1.75.0 .

Commands:
Appendix A. Automation execution environments precedence Project updates will always use the control plane automation execution environments by default, however, jobs will use the first available automation execution environments as follows: The execution_environment defined on the template (job template or inventory source) that created the job. The default_environment defined on the project that the job uses. The default_environment defined on the organization of the job. The default_environment defined on the organization of the inventory the job uses. The current DEFAULT_EXECUTION_ENVIRONMENT setting (configurable at api/v2/settings/jobs/ ) Any image from the GLOBAL_JOB_EXECUTION_ENVIRONMENTS setting. Any other global execution environment. Note If more than one execution environment fits a criteria (applies for 6 and 7), the most recently created one is used.

Commands:
7. Technology Previews Technology Preview features are currently not supported under Red Hat Enterprise Linux 4.8 subscription services, may not be functionally complete, and are generally not suitable for production use. However, these features are included as a customer convenience and to provide the feature with wider exposure. Customers may find these features useful in a non-production environment. Customers are also free to provide feedback and functionality suggestions for a technology preview feature before it becomes fully supported. Erratas will be provided for high-severity security issues. During the development of a technology preview feature, additional components may become available to the public for testing. It is the intention of Red Hat to fully support technology preview features in a future release. For more information on the scope of Technology Previews in Red Hat Enterprise Linux, please view the Technology Preview Features Support Scope page on the Red Hat website. OpenOffice 2.0 OpenOffice 2.0 is now included in this release as a Technology Preview. This suite features several improvements, including ODF and PDF functionalities, support for digital signatures and greater compatibility with open suites in terms of format and interface. In addition to this, the OpenOffice 2.0 spreadsheet has enhanced pivot table support, and can now handle up to 65,000 rows. For more information about OpenOffice 2.0 , please refer to http://www.openoffice.org/dev_docs/features/2.0/index.html .

Commands:
Chapter 4. Technology preview This section describes Technology Preview features in AMQ Broker 7.8. Important Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them for production. For more information, see Red Hat Technology Preview Features Support Scope . AMQP server connections In AMQ Broker 7.8, a broker can initiate connections to other endpoints using the AMQP protocol. This means, for example, that the broker can connect to other AMQP servers (not necessarily instances of AMQ Broker) and create elements on those connections. For more information, see Broker Connections in the Apache ActiveMQ Artemis documentation. Viewing brokers in Fuse Console You can configure an Operator-based broker deployment to use Fuse Console for OpenShift instead of AMQ Management Console. When you have configured your broker deployment appropriately, Fuse Console discovers the brokers and displays them on a dedicated Artemis tab. For more information, see Viewing brokers in Fuse Console in Deploying AMQ Broker on OpenShift . Note Viewing brokers in Fuse Console is a Technology Preview feature for Fuse 7.8 .

Commands:
Appendix D. Host parameter hierarchy You can access host parameters when provisioning hosts. Hosts inherit their parameters from the following locations, in order of increasing precedence: Parameter Level Set in Satellite web UI Globally defined parameters Configure > Global parameters Organization-level parameters Administer > Organizations Location-level parameters Administer > Locations Domain-level parameters Infrastructure > Domains Subnet-level parameters Infrastructure > Subnets Operating system-level parameters Hosts > Provisioning Setup > Operating Systems Host group-level parameters Configure > Host Groups Host parameters Hosts > All Hosts

Commands:
Chapter 5. Installing and uninstalling JBoss EAP using archive installation method 5.1. Downloading and installing JBoss EAP using archive installation method You can download and install JBoss EAP using the archive installation method on Red Hat Enterprise Linux RHEL and on Microsoft Windows server. Prerequisites You are on a supported operating system. You have set up an account on the Red Hat Customer Portal. You have Installed a supported Java Development Kit (JDK). You have reviewed the JBoss EAP 8 supported configurations and have ensured that your system is supported. Microsoft Windows only: You have set the JAVA_HOME and PATH environment variables. Note If you do not set up the environment variables the shortcuts will not work. Procedure Log in to the Red Hat Customer Portal. Click Downloads Select Red Hat JBoss Enterprise Application Platform from the Product Downloads list. In the Version drop-down list, select 8.0 . Find Red Hat JBoss Enterprise Application Platform 8.0.0 in the list and click the Download link. Optional: Move the archive file to the server and location where you want to install JBoss EAP. Depending on your operating system, choose one of the following options: For Red Hat Enterprise Linux, extract the archive file by entering the following command in the management CLI: USD unzip jboss-eap-8.0.0.zip For Windows Server, right-click the archive file and select Extract All . Note EAP_HOME is the top-level directory for the JBoss EAP installation. Create the directory by extracting the archive file. Additional resources For more information about configuring your JBoss EAP server, see our configuration guide. 5.2. Uninstalling JBoss EAP archive installation Depending on your work environment, the archive installation method might not meet the needs of your environment. You can remove the instance of JBoss EAP and any services associated with it. Thereafter, you can install JBoss EAP using a suitable installation method. Prerequisites You have archived any modified configuration files and deployments that you can reuse at a later stage. Procedure Delete the installation directory to uninstall JBoss EAP. Delete any scripts that depend on JBoss EAP being installed on your machine.

Commands:
unzip jboss-eap-8.0.0.zip
15.6.2. Useful Websites http://vsftpd.beasts.org/ - The vsftpd project page is a great place to locate the latest documentation and to contact the author of the software. http://slacksite.com/other/ftp.html - This website provides a concise explanation of the differences between active and passive mode FTP. http://war.jgaa.com/ftp/?cmd=rfc - A comprehensive list of Request for Comments ( RFCs ) related to the FTP protocol.

Commands:
14.12.6.2. Downloading the contents from a storage volume This command command downloads the contents of local-file from a storage volume. It requires a --pool pool-or-uuid which is the name or UUID of the storage pool that the volume is in. It also requires vol-name-or-key-or-path which is the name or key or path of the volume to wipe. Using the option --offset dictates the position in the storage volume at which to start reading the data. --length length dictates an upper limit for the amount of data to be downloaded.

Commands:
vol-download --pool pool-or-uuid --offset bytes --length bytes vol-name-or-key-or-path local-file
Preface Red Hat Enterprise Linux (RHEL) minor releases are an aggregation of individual security, enhancement, and bug fix errata. The Red Hat Enterprise Linux 7.6 Release Notes document describes the major changes made to the Red Hat Enterprise Linux 7 operating system and its accompanying applications for this minor release, as well as known problems and a complete list of all currently available Technology Previews. Capabilities and limits of Red Hat Enterprise Linux 7 as compared to other versions of the system are available in the Red Hat Knowledgebase article available at https://access.redhat.com/articles/rhel-limits . Packages distributed with this release are listed in Red Hat Enterprise Linux 7 Package Manifest . Migration from Red Hat Enterprise Linux 6 is documented in the Migration Planning Guide. For information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 16. General Updates A new module helping to upgrade the Tomcat server from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 This update adds a new module to the preupgrade-assistant-el6toel7 package as a Technology Preview. The module helps to upgrade from Tomcat version 6.0.24 in Red Hat Enterprise Linux 6 to Tomcat version 7.0.x in Red Hat Enterprise Linux 7 and provides information about incompatibilities found in the system configuration. When using the module, which is recommended only on non-production machines, several automatic changes are made to the Tomcat configuration files during the postupgrade phase to prevent certain known issues. Note that in the supported scenario, users should remove the tomcat6 packages before upgrading. A new module helping to upgrade Java OpenJDK 7 and Java OpenJDK 8 from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 The preupgrade-assistant-el6toel7 package provides a new module that handles upgrades of Java OpenJDK 7 and Java OpenJDK 8 from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. The module, available as a Technology Preview, informs users about possible requested actions and installs the expected equivalents of the original Java OpenJDK packages on the target system. Note that Java OpenJDK 6 and earlier versions are not handled by the in-place upgrade, but the module informs users about expected risks and required manual actions.

Commands:
Chapter 5. Deleting OpenShift Serverless custom resource definitions After uninstalling the OpenShift Serverless, the Operator and API custom resource definitions (CRDs) remain on the cluster. You can use the following procedure to remove the remaining CRDs. Important Removing the Operator and API CRDs also removes all resources that were defined by using them, including Knative services. 5.1. Removing OpenShift Serverless Operator and API CRDs Delete the Operator and API CRDs using the following procedure. Prerequisites Install the OpenShift CLI ( oc ). You have cluster administrator permissions on OpenShift Container Platform, or you have cluster or dedicated administrator permissions on Red Hat OpenShift Service on AWS or OpenShift Dedicated. You have uninstalled Knative Serving and removed the OpenShift Serverless Operator. Procedure To delete the remaining OpenShift Serverless CRDs, enter the following command: USD oc get crd -oname | grep 'knative.dev' | xargs oc delete

Commands:
oc get crd -oname | grep 'knative.dev' | xargs oc delete
15.4. Configuration Examples 15.4.1. Labeling Gluster Bricks A Gluster brick is an export directory on a server in the trusted storage pool. In case that the brick is not labeled with the correct SELinux context, glusterd_brick_t , SELinux denies certain file access operations and generates various AVC messages. The following procedure shows how to label Gluster bricks with the correct SELinux context. The procedure assumes that you previously created and formatted a logical volume, for example /dev/rhgs/gluster , to be used as the Gluster brick. For detailed information about Gluster bricks, see the Red Hat Gluster Storage Volumes chapter in the Administration Guide for Red Hat Gluster Storage. Procedure 15.1. How to Label a Gluster Brick Create a directory to mount the previously formatted logical volume. For example: Mount the logical volume, in this case /dev/vg-group/gluster , to the /mnt/brick1/ directory created in the step. Note that the mount command mounts devices only temporarily. To mount the device permanently, add an entry similar as the following one to the /etc/fstab file: For more information, see the fstab (5) manual page. Check the SELinux context of /mnt/brick1/ : The directory is labeled with the unlabeled_t SELinux type. Change the SELinux type of /mnt/brick1/ to the glusterd_brick_t SELinux type: Use the restorecon utility to apply the changes: Finally, verify that the context has been successfully changed:

Commands:
~]# mkdir /mnt/brick1
~]# mount /dev/vg-group/gluster /mnt/brick1/
/dev/vg-group/gluster /mnt/brick1 xfs rw,inode64,noatime,nouuid 1 2
~]USD ls -lZd /mnt/brick1/ drwxr-xr-x. root root system_u:object_r:unlabeled_t:s0 /mnt/brick1/
~]# semanage fcontext -a -t glusterd_brick_t "/mnt/brick1(/.*)?"
~]# restorecon -Rv /mnt/brick1
~]USD ls -lZd /mnt/brick1 drwxr-xr-x. root root system_u:object_r:glusterd_brick_t:s0 /mnt/brick1/
4.2. Removing Servers from the Trusted Storage Pool Warning Before detaching a peer from the trusted storage pool, make sure that the clients are not using the node. If backup servers were not set at mount time using the backup-volfile-servers option, remount the volume on the client using the IP address or FQDN of another server in the trusted storage pool to avoid inconsistencies. Run gluster peer detach server to remove a server from the storage pool. Removing One Server from the Trusted Storage Pool Remove one server from the Trusted Storage Pool, and check the peer status of the storage pool. Prerequisites The glusterd service must be running on the server targeted for removal from the storage pool. See Chapter 22, Starting and Stopping the glusterd service for service start and stop commands. The host names of the target servers must be resolvable by DNS. Run gluster peer detach [server] to remove the server from the trusted storage pool. Verify the peer status from all servers using the following command:

Commands:
gluster peer detach (server) All clients mounted through the peer which is getting detached needs to be remounted, using one of the other active peers in the trusted storage pool, this ensures that the client gets notification on any changes done on the gluster configuration and if the same has been done do you want to proceed? (y/n) y peer detach: success
gluster peer status Number of Peers: 2 Hostname: server2 Uuid: 5e987bda-16dd-43c2-835b-08b7d55e94e5 State: Peer in Cluster (Connected) Hostname: server3 Uuid: 1e0ca3aa-9ef7-4f66-8f15-cbc348f29ff7
A.2.6. ElGamal Encryption In cryptography, the ElGamal encryption system is an asymmetric key encryption algorithm for public-key cryptography which is based on the Diffie-Hellman key agreement. It was described by Taher Elgamal in 1985. ElGamal encryption is used in the free GNU Privacy Guard software, recent versions of PGP, and other cryptosystems. [22] [22] "ElGamal encryption" Wikipedia. 24 February 2010 http://en.wikipedia.org/wiki/ElGamal_encryption

Commands:
4.4. Variable Tracking at Assignments Variable Tracking at Assignments (VTA) is a new infrastructure included in GCC used to improve variable tracking during optimizations. This allows GCC to produce more precise, meaningful, and useful debugging information for GDB, SystemTap, and other debugging tools. When GCC compiles code with optimizations enabled, variables are renamed, moved around, or even removed altogether. As such, optimized compiling can cause a debugger to report that some variables have been <optimized out>. With VTA enabled, optimized code is internally annotated to ensure that optimization passes to transparently keep track of each variable's value, regardless of whether the variable is moved or removed. The effect of this is more parameter and variable values available, even for the optimized ( gcc -O2 -g built) code. It also displays the <optimized out> message less. VTA's benefits are more pronounced when debugging applications with inlined functions. Without VTA, optimization could completely remove some arguments of an inlined function, preventing the debugger from inspecting its value. With VTA, optimization will still happen, and appropriate debugging information will be generated for any missing arguments. VTA is enabled by default when compiling code with optimizations and debugging information enabled (that is, gcc -O -g or, more commonly, gcc -O2 -g ). To disable VTA during such builds, add the -fno-var-tracking-assignments . In addition, the VTA infrastructure includes the new gcc option -fcompare-debug . This option tests code compiled by GCC with debug information and without debug information: the test passes if the two binaries are identical. This test ensures that executable code is not affected by any debugging options, which further ensures that there are no hidden bugs in the debug code. Note that -fcompare-debug adds significant cost in compilation time. See man gcc for details about this option. For more information about the infrastructure and development of VTA, see A Plan to Fix Local Variable Debug Information in GCC , available at the following link: http://gcc.gnu.org/wiki/Var_Tracking_Assignments A slide deck version of this whitepaper is also available at http://people.redhat.com/aoliva/papers/vta/slides.pdf .

Commands:
Chapter 7. Supported integration products AMQ Streams 1.6 supports integration with the following Red Hat products. Red Hat Single Sign-On 7.4 and later for OAuth 2.0 authentication and OAuth 2.0 authorization Red Hat 3scale API Management 2.6 and later to secure the Kafka Bridge and provide additional API management features Red Hat Debezium 1.0 and later for monitoring databases and creating event streams Service Registry 2020-Q4 and later as a centralized store of service schemas for data streaming For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the AMQ Streams 1.6 documentation.

Commands:
Chapter 1. Introduction A virtual machine is a software implementation of a computer. The Red Hat Virtualization environment enables you to create virtual desktops and virtual servers. Virtual machines consolidate computing tasks and workloads. In traditional computing environments, workloads usually run on individually administered and upgraded servers. Virtual machines reduce the amount of hardware and administration required to run the same computing tasks and workloads. 1.1. Audience Most virtual machine tasks in Red Hat Virtualization can be performed in both the VM Portal and Administration Portal. However, the user interface differs between each portal, and some administrative tasks require access to the Administration Portal. Tasks that can only be performed in the Administration Portal will be described as such in this book. Which portal you use, and which tasks you can perform in each portal, is determined by your level of permissions. Virtual machine permissions are explained in Section 6.8, "Virtual Machines and Permissions" . The VM Portal's user interface is described in the Introduction to the VM Portal . The Administration Portal's user interface is described in the Administration Guide . The creation and management of virtual machines through the Red Hat Virtualization REST API is documented in the REST API Guide .

Commands: