mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 10. Creating a Bare Metal supplemental certification The Red Hat OpenShift Bare Metal Certification is a supplemental certification. It might have already been created for you as part of the Red Hat Enterprise Linux System certification. If it was not automatically created for you, or if you need to apply for the certification at a later date, perform the following steps: Prerequisites Your server must have already earned the following certifications: Red Hat Enterprise Linux System Red Hat OpenShift Container Platform You must create individual supplemental certifications for each type, IPI or AI. However, if you intend to certify both IPI and AI, create a single supplemental certification request. For more information about creating the Red Hat OpenShift Container Platform layered certification, see Certifying layered products . Procedure Log in to the Red Hat Partner Connect portal. Click the Red Hat Enterprise Linux System certification that is related to the assisted installer certification you want to open. Click the Related Certifications tab on the upper left side of the table. Click the Red Hat OpenShift Container Platform certification that is related to the assisted installer certification you want to open. Click the Related Certifications tab on the upper left side of the table. At the top of the certifications table, click Add Related Certification . The Create Related Certification window appears. Select Supplemental and click . Review the certification information and click Open . The supplemental certification is created. Leave a comment to the Red Hat certification team to specify that you want either or both of the following components added to the test plan: Bare Metal Management Assisted Installer After you get the new test plan, start testing.

Commands:
5.371. yum-utils 5.371.1. RHBA-2012:0858 - yum-utils bug fix and enhancement update Updated yum-utils packages that fix four bugs and add three enhancements are now available for Red Hat Enterprise Linux 6. The yum-utils packages provide a collection of utilities and examples for the Yum package manager. Bug Fixes BZ# 701096 Prior to this update, The reposync utility wrongly set the exit code "0" if a package was not downloaded. This update modifies the underlying code so that reposync now sets the exit code "1" if a package is either not correctly signed or fails to download. BZ# 711767 Prior to this update, the yumdownloader tool tried to download a package from all repositores that provided that particular package. As a result, after the first download a message was displayed that the file already existed. This update modifies the yumdownloader so that duplicated download attempts are now avoided. BZ# 737597 Prior to this update, the yum-debug-restore tool recognized only that the latest version of a package was installed. As a consequence, older kernel packages were not restored. This update adds support for "installonly" packages, so the whole set of installed kernel packages is restored. BZ# 782338 Prior to this update, the man page for the package-cleanup tool did not mention the changed semantics of the "--count" option. This update modifies the man page so that the "--count" option is now correctly documented. Enhancements BZ# 684925 Prior to this update, yum could not list the dependencies and the already installed packages in the repositories that satisfy these dependencies. This update adds the "show-changed-rco" command to give a compact description of the changes to Requires, Conflicts, and Obsoletes data from installed or old files. BZ# 710579 Prior to this update, the repodiff tool only compared packages based on their name. This update adds the "--compare-arch" option to the repodiff tool to compare also the architecture. BZ# 769775 Prior to this update, the package-cleanup tool did not correctly handle kernel-PAE and kernel-xen packages. This update adds support for kernel-PAE and kernel-xen packages. All users of yum-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 14. Installing on Oracle Cloud Infrastructure (OCI) From OpenShift Container Platform 4.14 and later versions, you can use the Assisted Installer to install a cluster on an Oracle Cloud Infrastructure virtual machine (VM) by using infrastructure that you provide. Oracle Cloud Infrastructure provides services that can meet your needs for regulatory compliance, performance, and cost-effectiveness. You can access OCI Resource Manager configurations to provision and configure OCI resources. From OpenShift Container Platform 4.16 and later versions, the integration between OpenShift Container Platform and Oracle Cloud Infrastructure is certified on both virtual machines (VMs) and bare metal (BM) machines. Bare-metal installations using iSCSI boot drives require a secondary vNIC that is automatically created in the Terraform stack provided by Oracle. For details and installation instructions, see Installing a cluster on Oracle Cloud Infrastructure by using the Assisted Installer in the OpenShift Container Platform documentation.

Commands:
Chapter 6. Capabilities The capabilities collection provides information about the capabilities that versions of Red Hat Virtualization support. These capabilities include active features and available enumerated values for specific properties. To retrieve a full list of the capabilities for all versions of Red Hat Enterprise Virtualization from 3.2 to the latest version, submit the following request: 6.1. Version-Dependent Capabilities The capabilities element contains any number of version elements that describe capabilities dependent on a compatibility level. The version element includes attributes for major and minor version numbers. This indicates the current version level. The following representation shows capabilities specific to Red Hat Enterprise Virtualization Manager 3.5 , 3.6 , and 4.0 respectively: Each version contains a series of capabilities dependent on the version specified.

Commands:
GET /ovirt-engine/api/capabilities/ HTTP/1.1 Content-Type: application/xml Accept: application/xml
<capabilities> <version major="3" minor="5"> </version> <version major="3" minor="6"> </version> <version major="4" minor="0"> </version> </capabilities>
Chapter 18. Define the LDAP login domain When you are setting up Red Hat Process Automation Manager to use LDAP for authentication and authorization, define the LDAP login domain because the Git SSH authentication may use another security domain. To define the LDAP login domain, use the org.uberfire.domain system property. For example, on Red Hat JBoss Enterprise Application Platform, add this property in the standalone.xml file as shown: Ensure that the authenticated user has appropriate roles ( admin , analyst , reviewer ) associated with it in LDAP.

Commands:
<system-properties> <!-- other system properties --> <property name="org.uberfire.domain" value="LDAPAuth"/> </system-properties>
5.4. Generating Manual Pages: sepolicy manpage The sepolicy manpage command generates manual pages based on the SELinux policy that document process domains. As a result, such documentation is always up-to-date. Each name of automatically generated manual pages consists of the process domain name and the _selinux suffix, for example httpd_selinux . The manual pages include several sections that provide information about various parts of the SELinux policy for confined domains: The Entrypoints section contains all executable files that need to be executed during a domain transition. The Process Types section lists all process types that begin with the same prefix as the target domain. The Booleans section lists Booleans associated with the domain. The Port Types section contains the port types matching the same prefix as the domain and describes the default port numbers assigned to these port types. The Managed Files section describes the types that the domain is allowed to write to and the default paths associated with these types. The File Contexts section contains all file types associated with the domain and describes how to use these file types along with the default path labeling on a system. The Sharing Files section explains how to use the domain sharing types, such as public_content_t . See the sepolicy-manpage (8) manual page for further information about sepolicy manpage .

Commands:
function::user_string2 Name function::user_string2 - Retrieves string from user space with alternative error string Synopsis Arguments addr the user space address to retrieve the string from err_msg the error message to return when data isn't available Description Returns the null terminated C string from a given user space memory address. Reports the given error message on the rare cases when userspace data is not accessible.

Commands:
user_string2:string(addr:long,err_msg:string)
probe::netfilter.arp.forward Name probe::netfilter.arp.forward - - Called for each ARP packet to be forwarded Synopsis netfilter.arp.forward Values ar_hln Length of hardware address nf_stop Constant used to signify a 'stop' verdict outdev_name Name of network device packet will be routed to (if known) ar_tha Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address nf_accept Constant used to signify an 'accept' verdict ar_data Address of ARP packet data region (after the header) indev_name Name of network device packet was received on (if known) arphdr Address of ARP header outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict length The length of the packet buffer contents, in bytes nf_stolen Constant used to signify a 'stolen' verdict ar_pln Length of protocol address pf Protocol family -- always " arp " ar_sha Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address indev Address of net_device representing input device, 0 if unknown nf_drop Constant used to signify a 'drop' verdict ar_pro Format of protocol address ar_sip Ethernet+IP only (ar_pro==0x800): source IP address ar_tip Ethernet+IP only (ar_pro==0x800): target IP address ar_hrd Format of hardware address nf_queue Constant used to signify a 'queue' verdict ar_op ARP opcode (command)

Commands:
17.6. Retrieving Current Volume Option Settings Red Hat Gluster Storage allows storage administrators to retrieve the value of a specific volume option. You can also retrieve all the values of the volume options and all global options associated to a gluster volume. To retrieve the value of volume options, use the gluster volume get command. If a volume option is reconfigured for a volume, then the same value is displayed. If the volume option is not reconfigured, the default value is displayed. The syntax is # gluster volume get <VOLNAME|all> <key|all> 17.6.1. Retrieving Value of a Specific Volume Option To fetch the value of a specific volume option, execute the following command: Where, VOLNAME: The volume name key: The value of the volume option For example: 17.6.2. Retrieving all Options of a Volume To fetch the values of all the volume options, execute the following command: Where, VOLNAME: The volume name For example: 17.6.3. Retrieving all Global Options To fetch the values of all global options, execute the following command: For example:

Commands:
gluster volume get <VOLNAME> <key>
gluster volume get test-vol nfs.disable Option Value ------ ----- nfs.disable on
gluster volume get <VOLNAME> all
gluster volume get test-vol all Option Value ------ ----- cluster.lookup-unhashed on cluster.lookup-optimize on cluster.min-free-disk 10% cluster.min-free-inodes 5% cluster.rebalance-stats off cluster.subvols-per-directory (null) .
gluster volume get all all
gluster volume get all all Option Value ------ ----- cluster.server-quorum-ratio 51 cluster.enable-shared-storage disable cluster.op-version 70200 cluster.max-op-version 70200 cluster.brick-multiplex disable cluster.max-bricks-per-process 250 cluster.daemon-log-level INFO
Chapter 15. Subscription Management Red Hat Enterprise Linux 7 is available using the Red Hat Subscription Management services. The following Knowledge Base article provides a brief overview and instructions on how to register your Red Hat Enterprise Linux 7 system with Red Hat Subscription Management. Certificate-Based Entitlements Red Hat Enterprise Linux 7 supports new certificate-based entitlements through the subscription-manager tool. Legacy entitlements are also supported for Satellite users to provide a transition for users using Red Hat Enterprise Linux 5 and 6. Note that registering to Red Hat Network Classic using the rhn_register or rhnreg_ks tools will not work on Red Hat Enterprise Linux 7. You can use the mentioned tools to register to Red Hat Satellite or Proxy versions 5.6 only.

Commands:
8.4. Remediating the System to Align with a Specific Baseline Use this procedure to remediate the RHEL 7 system to align with a specific baseline. This example uses the Protection Profile for General Purpose Operating Systems (OSPP). Warning If not used carefully, running the system evaluation with the Remediate option enabled might render the system non-functional. Red Hat does not provide any automated method to revert changes made by security-hardening remediations. Remediations are supported on RHEL systems in the default configuration. If your system has been altered after the installation, running remediation might not make it compliant with the required security profile. Prerequisites The scap-security-guide package is installed on your RHEL 7 system. Procedure Use the oscap command with the --remediate option: Restart your system. Verification Evaluate compliance of the system with the OSPP profile, and save scan results in the ospp_report.html file: Additional Resources scap-security-guide(8) and oscap(8) man pages

Commands:
~]USD sudo oscap xccdf eval --profile ospp --remediate /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
~]USD oscap xccdf eval --report ospp_report.html --profile ospp /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
Chapter 2. Customizing your Red Hat Developer Hub base URL You can change the default Red Hat Developer Hub base URL. Prerequisites You know your desired Developer Hub external URL: https:// <my_developer_hub_url> , and have configured DNS to point to your Red Hat OpenShift Container Platform cluster. Custom Developer Hub configuration . Procedure In your custom app-config.yaml file, enter your Developer Hub external URL, such as https:// <my_developer_hub_url> . app-config.yaml excerpt app: baseUrl: https:// <my_developer_hub_url> backend: baseUrl: https:// <my_developer_hub_url> cors: origin: https:// <my_developer_hub_url>

Commands:
app: baseUrl: https:// <my_developer_hub_url> backend: baseUrl: https:// <my_developer_hub_url> cors: origin: https:// <my_developer_hub_url>
Chapter 2. Enable Basic authentication Enable Basic authentication for your Quarkus project and allow users to authenticate with a username and password. 2.1. Prerequisites You have installed at least one extension that provides an IdentityProvider based on username and password. For example: Quarkus Security Jakarta Persistence extension ( quarkus-security-jpa ) Elytron security properties file extension (quarkus-elytron-security-properties-file) Elytron security JDBC extension (quarkus-elytron-security-jdbc) The following procedure outlines how you can enable Basic authentication for your application by using the elytron-security-properties-file extension. 2.2. Procedure In the application.properties file, set the quarkus.http.auth.basic property to true . quarkus.http.auth.basic=true Optional: In a non-production environment only and purely for testing Quarkus Security in your applications: To enable authentication for the embedded realm, set the quarkus.security.users.embedded.enabled property to true . quarkus.security.users.embedded.enabled=true You can also configure the required user credentials, user name, secret, and roles. For example: quarkus.http.auth.basic=true quarkus.security.users.embedded.enabled=true quarkus.security.users.embedded.plain-text=true quarkus.security.users.embedded.users.alice=alice 1 quarkus.security.users.embedded.users.bob=bob 2 quarkus.security.users.embedded.roles.alice=admin 3 quarkus.security.users.embedded.roles.bob=user 4 1 3 The user, alice , has alice as their password and admin as their role. 2 4 The user, bob , has bob as their password and user as their role. For information about other methods that you can use to configure the required user credentials, see the Configuring User Information section of the Quarkus "Security Testing" guide. Important Configuring user names, secrets, and roles in the application.properties file is appropriate only for testing scenarios. For securing a production application, it is crucial to use a database to store this information. 2.3. steps For a more detailed walk-through that shows you how to configure Basic authentication together with Jakarta Persistence for storing user credentials in a database, see the Getting started with Security by using Basic authentication and Jakarta Persistence guide. 2.4. References Quarkus Security overview Identity Providers Configuring User Information in application.properties Basic authentication

Commands:
quarkus.http.auth.basic=true
quarkus.security.users.embedded.enabled=true
quarkus.http.auth.basic=true quarkus.security.users.embedded.enabled=true quarkus.security.users.embedded.plain-text=true quarkus.security.users.embedded.users.alice=alice 1 quarkus.security.users.embedded.users.bob=bob 2 quarkus.security.users.embedded.roles.alice=admin 3 quarkus.security.users.embedded.roles.bob=user 4
Appendix E. Revision History Revision History Revision 5.0-9 Thu Sep 14 2017 Steven Levine Update to version for 6.9 GA publication. Revision 5.0-3 Wed Mar 8 2017 Steven Levine Version for 6.9 GA publication. Revision 5.0-2 Fri Dec 16 2016 Steven Levine Version for 6.9 Beta publication. Revision 4.0-10 Fri Jun 24 2016 Steven Levine Republish for 6.8. Revision 4.0-9 Wed Apr 27 2016 Steven Levine Preparing document for 6.8 GA Publication. Revision 4.0-3 Wed Mar 9 2016 Steven Levine Initial Revision for Red Hat Enterprise Linux 6.8 Beta release Revision 3.0-9 Tue Sep 29 2015 Steven Levine Republished version for Red Hat Enterprise Linux 6.7 Revision 3.0-6 Wed Jul 8 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Revision 3.0-4 Fri Apr 17 2015 Steven Levine Initial Revision for Red Hat Enterprise Linux 6.7 Beta release Revision 2.0-5 Thu Oct 9 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Revision 2.0-2 Wed Aug 7 2014 Steven Levine Initial Revision for Red Hat Enterprise Linux 6.6 Beta release Revision 1.1-2 Wed Nov 20 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5

Commands:
Providing feedback on Red Hat documentation We appreciate your input on our documentation. Please let us know how we could make it better. To do so: For simple comments on specific passages: Make sure you are viewing the documentation in the HTML format. In addition, ensure you see the Feedback button in the upper right corner of the document. Use your mouse cursor to highlight the part of text that you want to comment on. Click the Add Feedback pop-up that appears below the highlighted text. Follow the displayed instructions. For submitting more complex feedback, create a Bugzilla ticket: Go to the Bugzilla website. As the Component, use Documentation . Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. Click Submit Bug .

Commands:
Chapter 5. Network connections 5.1. Connection URIs This section describes the standard format of the Connection URI string used to connect to an AMQP remote peer. scheme amqp - connection uses TCP transport and sets the default port to 5672. scheme amqps - connection uses SSL/TLS transport and sets the default port to 5671. user - optional connection authentication user name. If the user name is present then the client initiates an AMQP SASL user credential exchange during connection startup. password - optional connection authentication password. host - network host to which the connection is directed. port - optional network port to which the connection is directed. The default port value is determined by the AMQP transport scheme. Connection URI Examples 5.2. Reconnect and failover AMQ .NET does not offer reconnect and failover, but it can be implemented in your application by intercepting connection errors and reconnecting. For example code, see the ReconnectSender.cs example .

Commands:
scheme = ( "amqp" | "amqps" ) host = ( <fully qualified domain name> | <hostname> | <numeric IP address> ) URI = scheme "://" [user ":" [password] "@"] host [":" port]
amqp://127.0.0.1 amqp://amqpserver.example.com:5672 amqps://joe:somepassword@bigbank.com amqps://sue:secret@test.example.com:21000
Chapter 3. Cluster Expansion To expand an existing Gluster cluster already imported and managed by the Web Administration environment, perform the following sequence of actions: Create New Nodes Before initiating cluster expansion in the Web Administration interface, create new Gluster storage nodes to be imported in Web Administration. For detailed instructions, see the Expanding Volumes section in the Red Hat Gluster Storage Administration Guide . New Alert After successfully expanding the cluster with new nodes, an alert is generated in the Notifications panel of the Web Administration interface as displayed in the following screen: In this screen, new peers represents new storage nodes that were created in the cluster expansion process. New Event Additionally, a new Event is also generated about the availability of new storage nodes for expansion as displayed in the following screen: Run Tendrl-ansible installation for new nodes After the storage nodes are identified by Web Administration, run tendrl-ansible installation by adding the new hosts in the inventory file. For detailed installation instructions, see the Installing Web Administration chapter in the Red Hat Gluster Storage Web Administration Quick Start Guide. Important If you have implemented TLS-based client-server authentication, install and deploy TLS encryption certificates on the new nodes before running tendrl-ansible installation to avoid cluster expansion failure. For detailed information on configuring TLS encryption, see the TLS Encryption Configuration chapter of the Red Hat Gluster Storage Web Administration Quick Start Guide. Expand Cluster in Web Administration Environment After tendrl-ansible is executed, the expand cluster option becomes available in the Web Administration interface. Follow these instructions to expand the cluster: Procedure. Expanding Cluster Log in to the Web Administration interface and click All Clusters interface from the interface selector drop-down. In the Clusters view, locate the cluster to be expanded. It will be labelled as Expansion required . At the far right of the cluster row, click the vertical ellipsis and then click Expand . The available hosts to be added are listed. Click Expand . The cluster expansion task is submitted. The cluster is successfully expanded and ready for use. 3.1. Troubleshooting Cluster Expansion Scenario: Cluster Expansion task failed In this scenario, the cluster explansion task fails. Resolution If cluster expansion fails, check if tendrl-ansible was executed successfully and ensure the node agents are correctly configured. If cluster expansion failed due to errors, resolve the errors on affected nodes and re-initiate the Expand Cluster action. To verify tendrl-ansible execution steps, see the Web Administration Installation section of the Red Hat Gluster Storage Web Administration Quick Start Guide. For detailed instructions on expanding cluster, navigate to the Cluster Expansion section of this Guide.

Commands: