mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Opening a new certification case by using the Red Hat Certification portal Prerequisites You have established a certification relationship with Red Hat. You have the user login credentials. You have the vendor and products linked to your user login. Procedure Log in to Red Hat Certification Portal . On the homepage, click Open Certification . A new window will display. Click . Select the Partner from the drop-down list. On the Product drop-down list, select your product name. If your product does not appear, create it by entering its name in the Product field. Then, select it. In the What kind of product is this? section, select Hardware . Your product might qualify for more than one ecosystem. Click . Enter the Make . The Model appears automatically based on the inputs. Select Cloud Instance Type under Which category best describes your product? Optional: Enter the Product URL . Optional: Enter the Support URL . Optional: Enter the Specification URL . Click . A new product gets created based on the inputs you provided in the steps. The Partner Product appears by default based on the inputs in the steps. Select Red Hat Certification from the drop-down list, and click . Review the information you provided and click Open . Verification A message displays that a new certification case for your product is created. steps Red Hat will prepare your test plan based on the product specification you provided. In the meantime, see Chapter 4, Setting up the test environment to prepare the systems for running tests.

Commands:
Installation overview OpenShift Container Platform 4.14 Overview content for installing OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
oc get nodes
NAME STATUS ROLES AGE VERSION example-compute1.example.com Ready worker 13m v1.21.6+bb8d50a example-compute2.example.com Ready worker 13m v1.21.6+bb8d50a example-compute4.example.com Ready worker 14m v1.21.6+bb8d50a example-control1.example.com Ready master 52m v1.21.6+bb8d50a example-control2.example.com Ready master 55m v1.21.6+bb8d50a example-control3.example.com Ready master 55m v1.21.6+bb8d50a
oc get machines -A
NAMESPACE NAME PHASE TYPE REGION ZONE AGE openshift-machine-api example-zbbt6-master-0 Running 95m openshift-machine-api example-zbbt6-master-1 Running 95m openshift-machine-api example-zbbt6-master-2 Running 95m openshift-machine-api example-zbbt6-worker-0-25bhp Running 49m openshift-machine-api example-zbbt6-worker-0-8b4c2 Running 49m openshift-machine-api example-zbbt6-worker-0-jkbqt Running 49m openshift-machine-api example-zbbt6-worker-0-qrl5b Running 49m
capabilities: baselineCapabilitySet: v4.11 1 additionalEnabledCapabilities: 2 - CSISnapshot - Console - Storage
Chapter 4. Developer Preview features Important This section describes Developer Preview features in Red Hat OpenShift AI. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA. For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Support Scope . Support for AppWrapper in Kueue AppWrapper support in Kueue is available as a Developer Preview feature. The experimental API enables the use of AppWrapper-based workloads with the distributed workloads feature.

Commands:
Chapter 1. Prerequisites Red Hat Enterprise Linux (RHEL) 9 To obtain the latest version of Red Hat Enterprise Linux (RHEL) 9, see Download Red Hat Enterprise Linux . For installation instructions, see the Product Documentation for Red Hat Enterprise Linux 9 . An active subscription to Red Hat Two or more virtual CPUs 4 GB or more of RAM Approximately 30 GB of disk space on your test system, which can be broken down as follows: Approximately 10 GB of disk space for the Red Hat Enterprise Linux (RHEL) operating system. Approximately 10 GB of disk space for Docker storage for running three containers. Approximately 10 GB of disk space for Red Hat Quay local storage. Note CEPH or other local storage might require more memory. More information on sizing can be found at Quay 3.x Sizing Guidelines . The following architectures are supported for Red Hat Quay: amd64/x86_64 s390x ppc64le 1.1. Installing Podman This document uses Podman for creating and deploying containers. For more information on Podman and related technologies, see Building, running, and managing Linux containers on Red Hat Enterprise Linux 9 . Important If you do not have Podman installed on your system, the use of equivalent Docker commands might be possible, however this is not recommended. Docker has not been tested with Red Hat Quay 3.13, and will be deprecated in a future release. Podman is recommended for highly available, production quality deployments of Red Hat Quay 3.13. Use the following procedure to install Podman. Procedure Enter the following command to install Podman: USD sudo yum install -y podman Alternatively, you can install the container-tools module, which pulls in the full set of container software packages: USD sudo yum module install -y container-tools

Commands:
sudo yum install -y podman
sudo yum module install -y container-tools
B.69. policycoreutils B.69.1. RHSA-2011:0414 - Important: policycoreutils security update Updated policycoreutils packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The policycoreutils packages contain the core utilities that are required for the basic operation of a Security-Enhanced Linux (SELinux) system and its policies. CVE-2011-1011 It was discovered that the seunshare utility did not enforce proper file permissions on the directory used as an alternate temporary directory mounted as /tmp/. A local user could use this flaw to overwrite files or, possibly, execute arbitrary code with the privileges of a setuid or setgid application that relies on proper /tmp/ permissions, by running that application via seunshare. Red Hat would like to thank Tavis Ormandy for reporting this issue. This update also introduces the following changes: * The seunshare utility was moved from the main policycoreutils subpackage to the policycoreutils-sandbox subpackage. This utility is only required by the sandbox feature and does not need to be installed by default. * Updated selinux-policy packages that add the SELinux policy changes required by the seunshare fixes. All policycoreutils users should upgrade to these updated packages, which correct this issue.

Commands:
5.3. Adding Red Hat Gluster Storage Server to the Cluster There are two ways to add hosts. You can either add new hosts or import the existing gluster configuration into a cluster. To import an existing gluster configuration: Select Enable Gluster Service . Select Import existing gluster configuration . With this option you can import the existing Gluster configurations into a cluster. Provide the IP address of one of the hosts. To add new hosts: Use the drop-down lists to select the Data Center and Host Cluster for the new host. Click OK . The new host displays in the list of hosts with a status of Installing . The host is activated and the status changes to Up automatically. You can manage the lifecycle of a volume using hook scripts. Note Install cockpit using # yum install cockpit , before adding the Red Hat Gluster Storage 3.5 node to Red Hat Virtualization Manager 4.3 in 4.3 compatible cluster. Note To add multiple servers to a cluster, you must first add a Red Hat Gluster Storage server to the cluster. An error message appears if you add multiple servers in the first attempt. Figure 5.3. New Host window

Commands:
1.4. Command Line Administration Tools In addition to Conga and the system-config-cluster Cluster Administration GUI, command line tools are available for administering the cluster infrastructure and the high-availability service management components. The command line tools are used by the Cluster Administration GUI and init scripts supplied by Red Hat. Table 1.1, "Command Line Tools" summarizes the command line tools. Table 1.1. Command Line Tools Command Line Tool Used With Purpose ccs_tool - Cluster Configuration System Tool Cluster Infrastructure ccs_tool is a program for making online updates to the cluster configuration file. It provides the capability to create and modify cluster infrastructure components (for example, creating a cluster, adding and removing a node). For more information about this tool, refer to the ccs_tool(8) man page. cman_tool - Cluster Management Tool Cluster Infrastructure cman_tool is a program that manages the CMAN cluster manager. It provides the capability to join a cluster, leave a cluster, kill a node, or change the expected quorum votes of a node in a cluster. cman_tool is available with DLM clusters only. For more information about this tool, refer to the cman_tool(8) man page. gulm_tool - Cluster Management Tool Cluster Infrastructure gulm_tool is a program used to manage GULM. It provides an interface to lock_gulmd , the GULM lock manager. gulm_tool is available with GULM clusters only. For more information about this tool, refer to the gulm_tool(8) man page. fence_tool - Fence Tool Cluster Infrastructure fence_tool is a program used to join or leave the default fence domain. Specifically, it starts the fence daemon ( fenced ) to join the domain and kills fenced to leave the domain. fence_tool is available with DLM clusters only. For more information about this tool, refer to the fence_tool(8) man page. clustat - Cluster Status Utility High-availability Service Management Components The clustat command displays the status of the cluster. It shows membership information, quorum view, and the state of all configured user services. For more information about this tool, refer to the clustat(8) man page. clusvcadm - Cluster User Service Administration Utility High-availability Service Management Components The clusvcadm command allows you to enable, disable, relocate, and restart high-availability services in a cluster. For more information about this tool, refer to the clusvcadm(8) man page.

Commands:
Chapter 1. Overview of Insights for Red Hat Enterprise Linux tasks Tasks is part of the Automation Toolkit for Insights for Red Hat Enterprise Linux. Tasks offer predefined playbooks that help you maintain the health of your infrastructure by simplifying and solving complex problems using automated tasks. Tasks solve specific problems and are typically executed one time on your systems to accomplish things such as, detecting a high-profile vulnerability on your systems or preparing systems for a major upgrade. You can find tasks in Red Hat Hybrid Cloud Console > Red Hat Insights > RHEL > Automation Toolkit > Tasks . Insights for Red Hat Enterprise Linux anticipates your need to solve problems and get things done in your infrastructure, and continuously adds specific tasks to the Automation Toolkit. Tasks include the following: RHEL pre-upgrade analysis utility task Pre-conversion analysis utility task Convert to RHEL from CentOS Linux 7 Some important information you will need to get started with executing a task are: User Access settings in the Red Hat Hybrid Cloud Console . Find out what role or level of user access you need to complete tasks. Registering and connecting systems to Red Hat Insights to execute tasks . Using tasks requires you to register and connect systems to Insights. Executing Tasks using Red Hat Insights . Understand how to find and execute tasks. Note System requirements to execute different tasks might vary. 1.1. User Access settings in the Red Hat Hybrid Cloud Console All users on your account have access to most of the data in Insights for Red Hat Enterprise Linux. 1.1.1. Predefined User Access groups and roles To make groups and roles easier to manage, Red Hat provides two predefined groups and a set of predefined roles. 1.1.1.1. Predefined groups The Default access group contains all users in your organization. Many predefined roles are assigned to this group. It is automatically updated by Red Hat. Note If the Organization Administrator makes changes to the Default access group its name changes to Custom default access group and it is no longer updated by Red Hat. The Default admin access group contains only users who have Organization Administrator permissions. This group is automatically maintained and users and roles in this group cannot be changed. 1.1.2. User Access roles for Insights Tasks users The following role enables enhanced access to remediations features in Insights for Red Hat Enterprise Linux: Tasks administrator. The Tasks administrator role permits access to all Tasks capabilities to remotely execute Tasks on Insights-connected systems. Note All members of the Default Admin Access group can also execute Tasks. A Tasks viewer role does not exist.

Commands:
Chapter 11. Reviewing test results and completing certifications 11.1. Red Hat review of test results After you submit your results, the review team will analyze their contents and award credit for each passing test that is part of the test plan. As they verify each passing test, the team sets each test plan item to Confirmed on the certification site's test plan, which you can see under the Results tab on the catalog. This allows you to see at a glance which tests are outstanding and which have been verified as passing. If any problems are found, the review team will update the certification request with a question, which will automatically be emailed to the person who submitted the cert. You can see all the discussion, and respond to or ask any questions, on the Dialog tab of the certification. 11.2. Completing certifications A certification is complete after Red Hat confirms that all the items in the test plan have passed. At this point, you can choose whether to close and publish the certification or to close and leave the certification unpublished. Supplemental certifications always remain unpublished. System and component certifications can be left unpublished if you do not want to advertise the certification status or the existence of the system or component. The system information and the discussions between you and the Red Hat review team will not be visible to the public in the published certification. If these publication options do not meet your requirements, submit a request for an exception while the certification is open, or a case if it is already closed.

Commands:
Part IV. Interacting with Red Hat Decision Manager using KIE APIs As a business rules developer or system administrator, you can use KIE APIs to interact with KIE Servers, KIE containers, and business assets in Red Hat Decision Manager. You can use the KIE Server REST API and Java client API to interact with KIE containers and business assets (such as business rules, processes, and solvers), the Process Automation Manager controller REST API and Java client API to interact with KIE Server templates and instances, and the Knowledge Store REST API to interact with spaces and projects in Business Central. REST API endpoints for KIE Server and the Process Automation Manager controller The lists of REST API endpoints for KIE Server and the Process Automation Manager controller are published separately from this document and maintained dynamically to ensure that endpoint options and data are as current as possible. Use this document to understand what the KIE Server and Process Automation Manager controller REST APIs enable you to do and how to use them, and use the separately maintained lists of REST API endpoints for specific endpoint details. For the full list of KIE Server REST API endpoints and descriptions, use one of the following resources: Execution Server REST API on the jBPM Documentation page (static) Swagger UI for the KIE Server REST API at http://SERVER:PORT/kie-server/docs (dynamic, requires running KIE Server) For the full list of Process Automation Manager controller REST API endpoints and descriptions, use one of the following resources: Controller REST API on the jBPM Documentation page (static) Swagger UI for the Process Automation Manager controller REST API at http://SERVER:PORT/CONTROLLER/docs (dynamic, requires running Process Automation Manager controller) Prerequisites Red Hat Decision Manager is installed and running. For installation and startup options, see Planning a Red Hat Decision Manager installation . You have access to Red Hat Decision Manager with the following user roles: kie-server : For access to KIE Server API capabilities, and access to headless Process Automation Manager controller API capabilities without Business Central (if applicable) rest-all : For access to Business Central API capabilities for the built-in Process Automation Manager controller and for the Business Central Knowledge Store admin : For full administrative access to Red Hat Decision Manager Although these user roles are not all required for every KIE API, consider acquiring all of them to ensure that you can access any KIE API without disruption. For more information about user roles, see Planning a Red Hat Decision Manager installation .

Commands:
1.8. Driver Connection URL Format URLs used when establishing a connection using the driver class have the following format: Given this format, the following table describes the variable parts of the URL: Table 1.1. URL Entities Variable Name Description VDB-NAME The name of the virtual database (VDB) to which the application is connected. Important VDB names can contain version information; for example, myvdb.2 . If such a name is used in the URL, this has the same effect as supplying a version=2 connection property. Note that if the VDB name contains version information, you cannot also use the version property in the same request. mm[s] The JBoss Data Virtualization JDBC protocol. mm is the default for normal connections. mms uses SSL for encryption and is the default for the AdminAPI tools. HOSTNAME The server where JBoss Data Virtualization is installed. PORT The port on which JBoss Data Virtualization is listening for incoming JDBC connections. [prop-name=prop-value] Any number of additional name-value pairs can be supplied in the URL, separated by semi-colons. Property values must be URL encoded if they contain reserved characters, for example, ? , = , and ; .

Commands:
jdbc:teiid: VDB-NAME @ mm[s] :// HOSTNAME : PORT ; [prop-name=prop-value;] *
20.21. Example Domain XML Configuration QEMU emulated guest virtual machine on AMD64 and Intel <domain type='qemu'> <name>QEmu-fedora-i686</name> <uuid>c7a5fdbd-cdaf-9455-926a-d65c16db1809</uuid> <memory>219200</memory> <currentMemory>219200</currentMemory> <vcpu>2</vcpu> <os> <type arch='i686' machine='pc'>hvm</type> <boot dev='cdrom'/> </os> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='cdrom'> <source file='/home/user/boot.iso'/> <target dev='hdc'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/home/user/fedora.img'/> <target dev='hda'/> </disk> <interface type='network'> <source network='default'/> </interface> <graphics type='vnc' port='-1'/> </devices> </domain> Figure 20.70. Example domain XML config KVM hardware accelerated guest virtual machine on i686 <domain type='kvm'> <name>demo2</name> <uuid>4dea24b3-1d52-d8f3-2516-782e98a23fa0</uuid> <memory>131072</memory> <vcpu>1</vcpu> <os> <type arch="i686">hvm</type> </os> <clock sync="localtime"/> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/demo2.img'/> <target dev='hda'/> </disk> <interface type='network'> <source network='default'/> <mac address='24:42:53:21:52:45'/> </interface> <graphics type='vnc' port='-1' keymap='de'/> </devices> </domain> Figure 20.71. Example domain XML config

Commands:
<domain type='qemu'> <name>QEmu-fedora-i686</name> <uuid>c7a5fdbd-cdaf-9455-926a-d65c16db1809</uuid> <memory>219200</memory> <currentMemory>219200</currentMemory> <vcpu>2</vcpu> <os> <type arch='i686' machine='pc'>hvm</type> <boot dev='cdrom'/> </os> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='cdrom'> <source file='/home/user/boot.iso'/> <target dev='hdc'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/home/user/fedora.img'/> <target dev='hda'/> </disk> <interface type='network'> <source network='default'/> </interface> <graphics type='vnc' port='-1'/> </devices> </domain>
<domain type='kvm'> <name>demo2</name> <uuid>4dea24b3-1d52-d8f3-2516-782e98a23fa0</uuid> <memory>131072</memory> <vcpu>1</vcpu> <os> <type arch="i686">hvm</type> </os> <clock sync="localtime"/> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/demo2.img'/> <target dev='hda'/> </disk> <interface type='network'> <source network='default'/> <mac address='24:42:53:21:52:45'/> </interface> <graphics type='vnc' port='-1' keymap='de'/> </devices> </domain>
1.3. GFS Software Subsystems Table 1.1, "GFS Software Subsystem Components" summarizes the GFS Software subsystems and their components. Table 1.1. GFS Software Subsystem Components Software Subsystem Components Description GFS gfs.ko Kernel module that implements the GFS file system and is loaded on GFS cluster nodes. gfs_fsck Command that repairs an unmounted GFS file system. gfs_grow Command that grows a mounted GFS file system. gfs_jadd Command that adds journals to a mounted GFS file system. gfs_mkfs Command that creates a GFS file system on a storage device. gfs_quota Command that manages quotas on a mounted GFS file system. gfs_tool Command that configures or tunes a GFS file system. This command can also gather a variety of information about the file system. lock_harness.ko Implements a pluggable lock module interface for GFS that allows for a variety of locking mechanisms to be used (for example, the DLM lock module, lock_dlm.ko ). lock_dlm.ko A lock module that implements DLM locking for GFS. It plugs into the lock harness, lock_harness.ko and communicates with the DLM lock manager in Red Hat Cluster Suite. lock_gulm.ko A lock module that implements GULM locking for GFS. It plugs into the lock harness, lock_harness.ko and communicates with the GULM lock manager in Red Hat Cluster Suite. lock_nolock.ko A lock module for use when GFS is used as a local file system only. It plugs into the lock harness, lock_harness.ko and provides local locking.

Commands: