mtpti5iD/redhat-docs_dataset huggingface dataset:
2.8.8. IPv6 The introduction of the -generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses, and carrier networks that are IPv6 aware are therefore able to address a larger number of routable addresses than IPv4. Red Hat Enterprise Linux supports IPv6 firewall rules using the Netfilter 6 subsystem and the ip6tables command. In Red Hat Enterprise Linux 6, both IPv4 and IPv6 services are enabled by default. The ip6tables command syntax is identical to iptables in every aspect except that it supports 128-bit addresses. For example, use the following command to enable SSH connections on an IPv6-aware network server: For more information about IPv6 networking, see the IPv6 Information Page at http://www.ipv6.org/ .

Commands:
~]# ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
5.64. febootstrap 5.64.1. RHEA-2012:0775 - febootstrap bug fix and enhancement update Updated febootstrap packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The febootstrap packages provide a tool to create a basic Red Hat Enterprise Linux or Fedora filesystem, and builds initramfs (initrd.img) or filesystem images. The febootstrap packages have been upgraded to upstream version 3.12, which provides a number of bug fixes and enhancements over the version. (BZ# 719877 ) All febootstrap users are advised upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix A. Initialization script for provisioning examples If you have not followed the examples in Managing content , you can use the following initialization script to create an environment for provisioning examples. Procedure Create a script file ( content-init.sh ) and include the following: Set executable permissions on the script: Download a copy of your Red Hat Subscription Manifest from the Red Hat Customer Portal and run the script on the manifest: This imports the necessary Red Hat content for the provisioning examples in this guide.

Commands:
#!/bin/bash MANIFEST=USD1 Import the content from Red Hat CDN hammer organization create --name "ACME" --label "ACME" --description "My example organization for managing content" hammer subscription upload --file ~/USDMANIFEST --organization "ACME" hammer repository-set enable --name "Red Hat Enterprise Linux 7 Server (RPMs)" --releasever "7Server" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer repository-set enable --name "Red Hat Enterprise Linux 7 Server (Kickstart)" --releasever "7Server" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer repository-set enable --name "Red Hat Satellite Client 6 (for RHEL 7 Server) (RPMs)" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer product synchronize --name "Red Hat Enterprise Linux Server" --organization "ACME" Create your application lifecycle hammer lifecycle-environment create --name "Development" --description "Environment for ACME's Development Team" --prior "Library" --organization "ACME" hammer lifecycle-environment create --name "Testing" --description "Environment for ACME's Quality Engineering Team" --prior "Development" --organization "ACME" hammer lifecycle-environment create --name "Production" --description "Environment for ACME's Product Releases" --prior "Testing" --organization "ACME" Create and publish your content view hammer content-view create --name "Base" --description "Base operating system" --repositories "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server,Red Hat Satellite Client 6 for RHEL 7 Server RPMs x86_64" --organization "ACME" hammer content-view publish --name "Base" --description "My initial content view for my operating system" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Development" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Testing" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Production" --organization "ACME"
chmod +x content-init.sh
./content-init.sh manifest_98f4290e-6c0b-4f37-ba79-3a3ec6e405ba.zip
probe::socket.aio_write.return Name probe::socket.aio_write.return - Conclusion of message send via sock_aio_write Synopsis socket.aio_write.return Values state Socket state value success Was receive successful? (1 = yes, 0 = no) family Protocol family value protocol Protocol value name Name of this probe type Socket type value size Size of message received (in bytes) or error code if success = 0 flags Socket flags value Context The message receiver. Description Fires at the conclusion of sending a message on a socket via the sock_aio_write function

Commands:
Chapter 9. Submitting the test results file You can submit the test results file to Red Hat using either RHCert CLI or the Red Hat Certification Tool . Using the RHCert CLI Tool: Procedure Log in to authenticate your device. Note Logging in is mandatory to submit the test results file. Open the generated URL in a new browser window or tab. Enter the login and password and click Log in . Click Grant access . Device log in successful message displays. Return to the terminal and enter yes to the Please confirm once you grant access prompt. Submit the result file. When prompted, enter your Certification ID. Using Red Hat Certification Tool Procedure Log in to Red Hat Certification portal . On the homepage, enter the product case number in the search bar. Select the case number from the list that is displayed. On the Summary tab, under the Files section, click Upload . steps Red Hat will review your submitted results file and suggest the steps to grant certification. Visit the Red Hat Certification portal for more information. Once certified, the product is listed on the Red Hat Ecosystem Catalog .

Commands:
rhcert-cli login
rhcert-submit
10.6. References For more information on cachefilesd and how to configure it, refer to man cachefilesd and man cachefilesd.conf . The following kernel documents also provide additional information: /usr/share/doc/cachefilesd- version-number /README /usr/share/man/man5/cachefilesd.conf.5.gz /usr/share/man/man8/cachefilesd.8.gz For general information about FS-Cache, including details on its design constraints, available statistics, and capabilities, refer to the following kernel document: /usr/share/doc/kernel-doc- version /Documentation/filesystems/caching/fscache.txt

Commands:
5.9.3.2. Seeing What is Mounted In addition to mounting and unmounting disk space, it is possible to see what is mounted. There are several different ways of doing this: Viewing /etc/mtab Viewing /proc/mounts Issuing the df command 5.9.3.2.1. Viewing /etc/mtab The file /etc/mtab is a normal file that is updated by the mount program whenever file systems are mounted or unmounted. Here is a sample /etc/mtab : Note The /etc/mtab file is meant to be used to display the status of currently-mounted file systems only. It should not be manually modified. Each line represents a file system that is currently mounted and contains the following fields (from left to right): The device specification The mount point The file system type Whether the file system is mounted read-only ( ro ) or read-write ( rw ), along with any other mount options Two unused fields with zeros in them (for compatibility with /etc/fstab [24] ) [24] Refer to Section 5.9.5, "Mounting File Systems Automatically with /etc/fstab " for more information.

Commands:
/dev/sda3 / ext3 rw 0 0 none /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 /dev/sda1 /boot ext3 rw 0 0 none /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/sda4 /home ext3 rw 0 0 none /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
Chapter 3. Getting started with OpenShift Virtualization You can explore the features and functionalities of OpenShift Virtualization by installing and configuring a basic environment. Note Cluster configuration procedures require cluster-admin privileges. 3.1. Planning and installing OpenShift Virtualization Plan and install OpenShift Virtualization on an OpenShift Container Platform cluster: Plan your bare metal cluster for OpenShift Virtualization . Prepare your cluster for OpenShift Virtualization . Install the OpenShift Virtualization Operator . Install the virtctl command line interface (CLI) tool . Planning and installation resources About storage volumes for virtual machine disks . Using a CSI-enabled storage provider . Configuring local storage for virtual machines . Installing the Kubernetes NMState Operator . Specifying nodes for virtual machines . Virtctl commands . 3.2. Creating and managing virtual machines Create virtual machines (VMs) by using the web console: Quick create a VM . Customize a template to create a VM . Connect to VMs: Connect to the serial console or VNC console of a VM by using the web console. Connect to a VM by using SSH . Connect to a Windows VM by using RDP . Manage VMs: Stop, start, pause, and restart a VM by using the web console . Manage a VM, expose a port, or connect to the serial console by using the virtctl CLI tool . Export VMs . 3.3. steps Connect the VMs to secondary networks: Connect a VM to a Linux bridge network . Connect a VM to an SR-IOV network . Note VMs are connected to the pod network by default. You must configure a secondary network, such as Linux bridge or SR-IOV, and then add the network to the VM configuration. Live migrate VMs . Back up and restore VMs . Tune and scale your cluster

Commands:
8.26. ccid 8.26.1. RHBA-2014:1531 - ccid bug fix update Updated ccid packages that fix one bug are now available for Red Hat Enterprise Linux 6. Chip/Smart Card Interface Devices (CCID) is a USB Smart Card reader standard followed by most modern Smart Card readers. The ccid package provides a Generic, USB-based CCID driver for readers that follow this standard. Bug Fix BZ# 1071366 Smart Card readers have multiple modes, some of which have limitations on the size of commands that can be sent to the Smart Card. Previously, OmniKey 3121 supported the modes of operation that allowed longer commands, but not in the standard CCID way. As a consequence, the user received an unrecoverable error message when running a long command. This update recognizes OmniKey 3121 and enables the longer modes so that longer commands are successfully executed on the Smart Card. Users of ccid are advised to upgrade to these updated packages, which fix this bug.

Commands:
Preface The Red Hat build of Cryostat is a container-native implementation of JDK Flight Recorder (JFR) that you can use to securely monitor the Java Virtual Machine (JVM) performance in workloads that run on an OpenShift Container Platform cluster. You can use Cryostat 2.3 to start, stop, retrieve, archive, import, and export JFR data for JVMs inside your containerized applications by using a web console or an HTTP API. Depending on your use case, you can store and analyze your recordings directly on your Red Hat OpenShift cluster by using the built-in tools that Cryostat provides or you can export recordings to an external monitoring application to perform a more in-depth analysis of your recorded data. Important Red Hat build of Cryostat is a Technology Preview feature only. 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 in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope .

Commands:
Chapter 2. Add-on services available for Red Hat OpenShift Service on AWS You can add services to your existing Red Hat OpenShift Service on AWS (ROSA) cluster using the Red Hat OpenShift Cluster Manager console . These services can also be installed using the rosa CLI . 2.1. Amazon CloudWatch Amazon CloudWatch forwards logs from Red Hat OpenShift Service on AWS (ROSA) to the AWS console for viewing. You must first install the ROSA cluster-logging-operator using the ROSA CLI ( rosa ) before installing the Amazon CloudWatch service through Red Hat OpenShift Cluster Manager console. Additional resources Amazon CloudWatch product information 2.2. Red Hat OpenShift API Management The Red Hat OpenShift API Management (OpenShift API Management) service is available as an add-on to your Red Hat OpenShift Service on AWS on AWS cluster. OpenShift API Management is a managed API traffic control and API program management solution. It is based on the 3scale API Management platform and implements single sign-on for Red Hat solutions to secure and protect your APIs. This OpenShift API Management entitlement provides: Availability to any cluster that meets the resource requirements listed in the Red Hat OpenShift API Management service definition. Full production-level support. No time limits on usage. 100K quota, or calls per day. Customers have the option to pay for an OpenShift API Management subscription with higher quotas. Additional resources Red Hat OpenShift API Management documentation 2.3. Red Hat OpenShift AI Red Hat OpenShift AI enables users to integrate data and AI and machine learning software to run end-to-end machine learning workflows. It provides a collection of notebook images with the tools and libraries required to develop and deploy data models. This allows data scientists to easily develop data models, integrate models into applications, and deploy applications using Red Hat OpenShift. OpenShift AI is available as an add-on to Red Hat managed environments such as OpenShift Dedicated and Red Hat OpenShift Service on AWS (ROSA). Additional resources Red Hat OpenShift AI documentation Red Hat OpenShift AI product page

Commands:
Chapter 11. Accessing the RHOSO cloud You can access your Red Hat OpenStack Services on OpenShift (RHOSO) cloud to perform actions on your data plane by either accessing the OpenStackClient pod through a remote shell from your workstation, or by using a web browser to access the Dashboard service (horizon) interface. 11.1. Accessing the OpenStackClient pod You can execute Red Hat OpenStack Services on OpenShift (RHOSO) commands on the deployed data plane by using the OpenStackClient pod through a remote shell from your workstation. The OpenStack Operator created the OpenStackClient pod as a part of the OpenStackControlPlane resource. The OpenStackClient pod contains the client tools and authentication details that you require to perform actions on your data plane. Prerequisites You are logged on to a workstation that has access to the Red Hat OpenShift Container Platform (RHOCP) cluster as a user with cluster-admin privileges. Procedure Access the remote shell for the OpenStackClient pod: Run your openstack commands. For example, you can create a default network with the following command: Exit the OpenStackClient pod: Additional resources Creating and managing instances Configuring networking services 11.2. Accessing the Dashboard service (horizon) interface You can access the Dashboard service (horizon) interface by providing the Dashboard service endpoint URL in a web browser. Prerequisites The Dashboard service is enabled on the control plane. For information about how to enable the Dashboard service, see Enabling the Dashboard service (horizon) interface in Customizing the Red Hat OpenStack Services on OpenShift deployment . You need to log into the dashboard as the admin user. Procedure Retrieve the admin password from the AdminPassword parameter in the osp-secret secret: Retrieve the Dashboard service endpoint URL: Open a web browser. Enter the Dashboard endpoint URL. Log in to the dashboard by providing the username of admin and the admin password.

Commands:
oc rsh -n openstack openstackclient
openstack network create default
exit
oc get secret osp-secret -o jsonpath='{.data.AdminPassword}' | base64 -d
oc get horizons horizon -o jsonpath='{.status.endpoint}'
Chapter 1. CLI tools introduction You can use different command-line interface (CLI) tools to build, deploy, and manage a MicroShift cluster and workloads. With CLI tools, you can complete various administration and development operations from the terminal to manage deployments and interact with each component of the system. CLI tools available for use with MicroShift are the following: Kubernetes CLI ( kubectl ) The OpenShift CLI ( oc ) tool with an enabled subset of commands Built-in microshift command types Note Commands for multi-node deployments, projects, and developer tooling are not supported by Red Hat build of MicroShift. 1.1. Additional resources Getting started with the OpenShift CLI About the OpenShift CLI (OpenShift Container Platform documentation) Red Hat Enterprise Linux (RHEL) documentation for specific use cases Cluster access with kubeconfig

Commands:
Chapter 4. Uninstalling a cluster on Nutanix You can remove a cluster that you deployed to Nutanix. 4.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with user-provisioned infrastructure clusters. There might be resources that the installation program did not create or that the installation program is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure On the computer that you used to install the cluster, go to the directory that contains the installation program, and run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
7.138. nfs4-acl-tools 7.138.1. RHBA-2015:1340 - nfs4-acl-tools bug fix update Updated nfs4-acl-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The nfs4-acl-tools packages provide utilities for managing NFSv4 Access Control Lists (ACLs) on files and directories mounted on ACL-enabled NFSv4 file systems. Bug Fix BZ# 1161164 Previously, the nfs4_setfacl and nfs4_getfacl commands ignored the DENY access control entry (ACE) for the DELETE, WRITE_OWNER, and NAMED_ATTRS permissions. A patch has been applied to fix this bug, and setting or viewing DENY ACE is no longer ignored. Users of nfs4-acl-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.2. Language Selection Use the arrow keys on your keyboard to select a language to use during the installation process (refer to Figure 8.3, "Language Selection" ). With your selected language highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. To add support for additional languages, customize the installation at the package selection stage. For more information, refer to Section 9.17.2, " Customizing the Software Selection " . Figure 8.3. Language Selection Once you select the appropriate language, click to continue.

Commands:
Chapter 9. Removing Windows nodes You can remove a Windows node by deleting its host Windows machine. 9.1. Deleting a specific machine You can delete a specific machine. Note You cannot delete a control plane machine. Prerequisites Install an OpenShift Container Platform cluster. Install the OpenShift CLI ( oc ). Log in to oc as a user with cluster-admin permission. Procedure View the machines that are in the cluster and identify the one to delete: USD oc get machine -n openshift-machine-api The command output contains a list of machines in the <clusterid>-worker-<cloud_region> format. Delete the machine: USD oc delete machine <machine> -n openshift-machine-api Important By default, the machine controller tries to drain the node that is backed by the machine until it succeeds. In some situations, such as with a misconfigured pod disruption budget, the drain operation might not be able to succeed in preventing the machine from being deleted. You can skip draining the node by annotating "machine.openshift.io/exclude-node-draining" in a specific machine. If the machine being deleted belongs to a machine set, a new machine is immediately created to satisfy the specified number of replicas.

Commands:
oc get machine -n openshift-machine-api
oc delete machine <machine> -n openshift-machine-api
Chapter 17. Using the Multicloud Object Gateway's Security Token Service to assume the role of another user Multicloud Object Gateway (MCG) provides support to a security token service (STS) similar to the one provided by Amazon Web Services. To allow other users to assume the role of a certain user, you need to assign a role configuration to the user. You can manage the configuration of roles using the MCG CLI tool. The following example shows role configuration that allows two MCG users ( assumer@mcg.test and assumer2@mcg.test ) to assume a certain user's role: Assign the role configuration by using the MCG CLI tool. Collect the following information before proceeding to assume the role as it is needed for the subsequent steps: The access key ID and secret access key of the assumer (the user who assumes the role) The MCG STS endpoint, which can be retrieved by using the command: The access key ID of the assumed user. The value of the role_name value in your role configuration. A name of your choice for the role session After the configuration role is ready, assign it to the appropriate user (fill with the data described in the step) - Note Adding --no-verify-ssl might be necessary depending on your cluster's configuration. The resulting output contains the access key ID, secret access key, and session token that can be used for executing actions while assuming the other user's role. You can use the credentials generated after the assume role steps as shown in the following example:

Commands:
'{"role_name": "AllowTwoAssumers", "assume_role_policy": {"version": "2012-10-17", "statement": [ {"action": ["sts:AssumeRole"], "effect": "allow", "principal": ["assumer@mcg.test", "assumer2@mcg.test"]}]}}'
mcg sts assign-role --email <assumed user's username> --role_config '{"role_name": "AllowTwoAssumers", "assume_role_policy": {"version": "2012-10-17", "statement": [ {"action": ["sts:AssumeRole"], "effect": "allow", "principal": ["assumer@mcg.test", "assumer2@mcg.test"]}]}}'
oc -n openshift-storage get route
AWS_ACCESS_KEY_ID=<aws-access-key-id> AWS_SECRET_ACCESS_KEY=<aws-secret-access-key1> aws --endpoint-url <mcg-sts-endpoint> sts assume-role --role-arn arn:aws:sts::<assumed-user-access-key-id>:role/<role-name> --role-session-name <role-session-name>
AWS_ACCESS_KEY_ID=<aws-access-key-id> AWS_SECRET_ACCESS_KEY=<aws-secret-access-key1> AWS_SESSION_TOKEN=<session token> aws --endpoint-url <mcg-s3-endpoint> s3 ls