mtpti5iD/redhat-docs_dataset huggingface dataset:
3.4. Search Result Type Options The result type allows you to search for resources of any of the following types: Vms for a list of virtual machines Host for a list of hosts Pools for a list of pools Template for a list of templates Events for a list of events Users for a list of users Cluster for a list of clusters DataCenter for a list of data centers Storage for a list of storage domains As each type of resource has a unique set of properties and a set of other resource types that it is associated with, each search type has a set of valid syntax combinations. You can also use the auto-complete feature to create valid queries easily.

Commands:
4.5.4. Configuring Redundant Ring Protocol As of Red Hat Enterprise Linux 6.4, the Red Hat High Availability Add-On supports the configuration of redundant ring protocol. When using redundant ring protocol, there are a variety of considerations you must take into account, as described in Section 8.6, "Configuring Redundant Ring Protocol" . Clicking on the Redundant Ring tab displays the Redundant Ring Protocol Configuration page. This page displays all of the nodes that are currently configured for the cluster. If you are configuring a system to use redundant ring protocol, you must specify the Alternate Name for each node for the second ring. The Redundant Ring Protocol Configuration page optionally allows you to specify the Alternate Ring Multicast Address , the Alternate Ring CMAN Port , and the Alternate Ring Multicast Packet TTL for the second ring. If you specify a multicast address for the second ring, either the alternate multicast address or the alternate port must be different from the multicast address for the first ring. If you specify an alternate port, the port numbers of the first ring and the second ring must differ by at least two, since the system itself uses port and port-1 to perform operations. If you do not specify an alternate multicast address, the system will automatically use a different multicast address for the second ring.

Commands:
5.124. java-1.7.0-ibm 5.124.1. RHSA-2012:1467 - Critical: java-1.7.0-ibm security update Updated java-1.7.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. IBM Java SE version 7 includes the IBM Java Runtime Environment and the IBM Java Software Development Kit. Security Fix CVE-2012-1531 , CVE-2012-1532 , CVE-2012-1533 , CVE-2012-1718 , CVE-2012-3143 , CVE-2012-3159 , CVE-2012-3216 , CVE-2012-4820 , CVE-2012-4821 , CVE-2012-4822 , CVE-2012-4823 , CVE-2012-5067 , CVE-2012-5069 , CVE-2012-5070 , CVE-2012-5071 , CVE-2012-5072 , CVE-2012-5073 , CVE-2012-5074 , CVE-2012-5075 , CVE-2012-5076 , CVE-2012-5077 , CVE-2012-5079 , CVE-2012-5081 , CVE-2012-5083 , CVE-2012-5084 , CVE-2012-5086 , CVE-2012-5087 , CVE-2012-5088 , CVE-2012-5089 This update fixes several vulnerabilities in the IBM Java Runtime Environment and the IBM Java Software Development Kit. Detailed vulnerability descriptions are linked from the IBM Security alerts page . All users of java-1.7.0-ibm are advised to upgrade to these updated packages, containing the IBM Java SE 7 SR3 release. All running instances of IBM Java must be restarted for the update to take effect. 5.124.2. RHSA-2012:1289 - Critical: java-1.7.0-ibm security update Updated java-1.7.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. IBM Java SE version 7 includes the IBM Java Runtime Environment and the IBM Java Software Development Kit. Security Fix CVE-2012-0547 , CVE-2012-0551 , CVE-2012-1682 , CVE-2012-1713 , CVE-2012-1716 , CVE-2012-1717 , CVE-2012-1719 , CVE-2012-1721 , CVE-2012-1722 , CVE-2012-1725 , CVE-2012-1726 , CVE-2012-3136 , CVE-2012-4681 This update fixes several vulnerabilities in the IBM Java Runtime Environment and the IBM Java Software Development Kit. Detailed vulnerability descriptions are linked from the IBM Security alerts page . All users of java-1.7.0-ibm are advised to upgrade to these updated packages, containing the IBM Java SE 7 SR2 release. All running instances of IBM Java must be restarted for the update to take effect.

Commands:
Chapter 7. Known issues This section lists known issues in Red Hat Developer Hub 1.3. 7.1. Entities of repositories under a configured org in catalog-backend-module-github-org plugin are not deleted from the catalog when the imported repository is deleted from bulk imports Repositories might be added to Developer Hub from various sources (like statically in an app-config file or dynamically when enabling GitHub discovery). By design, the bulk import plugin will only track repositories that are accessible from the configured GitHub integrations. When both the Bulk Import and the GitHub Discovery plugins are enabled, the repositories the latter discovers might be listed in the Bulk Import pages. However, attempting to delete a repository added by the discovery plugin from the Bulk Import Jobs may have no effect, as any entities registered from this repository might still be present in the Developer Hub catalog. There is unfortunately no known workaround yet. Additional resources RHIDP-5284 7.2. OIDC refresh token behavior When using Red Hat Single-Sign On or Red Hat Build of Keycloak as an OIDC provider, the default access token lifespan is set to 5 minutes, which corresponds to the token refresh grace period set in Developer Hub. This 5-minute grace period is the threshold used to trigger a new refresh token call. Since the token is always near expiration, frequent refresh token requests will cause performance issues. This issue will be resolved in the 1.5 release. To prevent the performance issues, increase the lifespan in the Red Hat Single-Sign On or Red Hat Build of Keycloak server by setting Configure > Realm Settings > Access Token Lifespan to a value greater than five minutes (preferably 10 or 15 minutes). Additional resources RHIDP-4695 7.3. Bulk Import: Added repositories count is incorrect Only the first 20 repositories (in alphabetical order) can be displayed at most on the Bulk Import Added Repositories page. Also, the count of Added Repositories displayed might be wrong. In future releases, we plan to address this with proper pagination. Meanwhile, as a workaround, searching would still work against all Added Repositories. So you can still search any Added Repository and get it listed on the table. Additional resources RHIDP-4067 7.4. Topology plugin permission is not displayed in the RBAC front-end UI Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology ( topology.view.read ), Tekton ( tekton.view.read ), ArgoCD ( argocd.view.read ), and Quay ( quay.view.read ). Additional resources RHIDP-3396

Commands:
Chapter 11. Authorization for Enrolling Certificates (Access Evaluators) This chapter describes the authorization mechanism using access evaluators. 11.1. Authorization Mechanism In addition to the authentication mechanism, each enrollment profile can be configured to have its own authorization mechanism. The authorization mechanism is executed only after a successful authentication. The authorization mechanism is provided by the Access Evaluator plug-in framework. Access evaluators are pluggable classes that are used for evaluating access control instructions (ACI) entries. The mechanism provides an evaluate method that takes a predefined list of arguments (that is, type , op , value ), evaluates an expression such as group='Certificate Manager Agents' and returns a boolean depending on the result of evaluation.

Commands:
Chapter 11. Overview of object storage endpoints To ensure correct configuration of object storage in OpenShift AI, you must format endpoints correctly for the different types of object storage supported. These instructions are for formatting endpoints for Amazon S3, MinIO, or other S3-compatible storage solutions, minimizing configuration errors and ensuring compatibility. Important Properly formatted endpoints enable connectivity and reduce the risk of misconfigurations. Use the appropriate endpoint format for your object storage type. Improper formatting might cause connection errors or restrict access to storage resources. 11.1. MinIO (On-Cluster) For on-cluster MinIO instances, use a local endpoint URL format. Ensure the following when configuring MinIO endpoints: Prefix the endpoint with http:// or https:// depending on your MinIO security setup. Include the cluster IP or hostname, followed by the port number if specified. Use a port number if your MinIO instance requires one (default is typically 9000 ). Example: Note Verify that the MinIO instance is accessible within the cluster by checking your cluster DNS settings and network configurations. 11.2. Amazon S3 When configuring endpoints for Amazon S3, use region-specific URLs. Amazon S3 endpoints generally follow this format: Prefix the endpoint with https:// . Format as <bucket-name>.s3.<region>.amazonaws.com , where <bucket-name> is the name of your S3 bucket, and <region> is the AWS region code (for example, us-west-1 , eu-central-1 ). Example: Note For improved security and compliance, ensure that your Amazon S3 bucket is in the correct region. 11.3. Other S3-Compatible Object Stores For S3-compatible storage solutions other than Amazon S3, follow the specific endpoint format required by your provider. Generally, these endpoints include the following items: The provider base URL, prefixed with https:// . The bucket name and region parameters as specified by the provider. Review the documentation from your S3-compatible provider to confirm required endpoint formats. Replace placeholder values like <bucket-name> and <region> with your specific configuration details. Warning Incorrectly formatted endpoints for S3-compatible providers might lead to access denial. Always verify the format in your storage provider documentation to ensure compatibility. 11.4. Verification and Troubleshooting After configuring endpoints, verify connectivity by performing a test upload or accessing the object storage directly through the OpenShift AI dashboard. For troubleshooting, check the following items: Network Accessibility : Confirm that the endpoint is reachable from your OpenShift AI cluster. Authentication : Ensure correct access credentials for each storage type. Endpoint Accuracy : Double-check the endpoint URL format for any typos or missing components. Additional resources Amazon S3 Region and Endpoint Documentation: AWS S3 Documentation

Commands:
http://minio-cluster.local:9000
https://my-bucket.s3.us-west-2.amazonaws.com
2.2. Consistent Multipath Device Names in a Cluster When the user_friendly_names configuration option is set to yes , the name of the multipath device is unique to a node, but it is not guaranteed to be the same on all nodes using the multipath device. Similarly, if you set the alias option for a device in the multipaths section of the multipath.conf configuration file, the name is not automatically consistent across all nodes in the cluster. This should not cause any difficulties if you use LVM to create logical devices from the multipath device, but if you require that your multipath device names be consistent in every node it is recommended that you not set the user_friendly_names option to yes and that you not configure aliases for the devices. By default, if you do not set user_friendly_names to yes or configure an alias for a device, a device name will be the WWID for the device, which is always the same. If you want the system-defined user-friendly names to be consistent across all nodes in the cluster, however, you can follow this procedure: Set up all of the multipath devices on one machine. Disable all of your multipath devices on your other machines by running the following commands: Copy the /etc/multipath/bindings file from the first machine to all the other machines in the cluster. Re-enable the multipathd daemon on all the other machines in the cluster by running the following command: If you add a new device, you will need to repeat this process. Similarly, if you configure an alias for a device that you would like to be consistent across the nodes in the cluster, you should ensure that the /etc/multipath.conf file is the same for each node in the cluster by following the same procedure: Configure the aliases for the multipath devices in the in the multipath.conf file on one machine. Disable all of your multipath devices on your other machines by running the following commands: Copy the /etc/multipath.conf file from the first machine to all the other machines in the cluster. Re-enable the multipathd daemon on all the other machines in the cluster by running the following command: When you add a new device you will need to repeat this process.

Commands:
service multipathd stop multipath -F
service multipathd start
service multipathd stop multipath -F
service multipathd start
Chapter 4. Updating the Red Hat Virtualization Manager Prerequisites The data center compatibility level must be set to the latest version to ensure compatibility with the updated storage version. Procedure On the Manager machine, check if updated packages are available: Update the setup packages: # yum update ovirt\*setup\* rh\*vm-setup-plugins Update the Red Hat Virtualization Manager with the engine-setup script. The engine-setup script prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service. When the script completes successfully, the following message appears: Note The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and might not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup . Important The update process might take some time. Do not stop the process before it completes. Update the base operating system and any optional packages installed on the Manager: Important If you encounter a required Ansible package conflict during the update, see Cannot perform yum update on my RHV manager (ansible conflict) . Important If any kernel packages were updated, reboot the machine to complete the update.

Commands:
engine-upgrade-check
yum update ovirt\*setup\* rh\*vm-setup-plugins
engine-setup
Execution of setup completed successfully
yum update --nobest
22.6. Additional Resources For more information on kernel modules and their utilities, refer to the following resources. 22.6.1. Installed Documentation lsmod man page - description and explanation of its output. insmod man page - description and list of command line options. modprobe man page - description and list of command line options. rmmod man page - description and list of command line options. modinfo man page - description and list of command line options. /usr/share/doc/kernel-doc- <version> /Documentation/kbuild/modules.txt - how to compile and use kernel modules. Note you must have the kernel-doc package installed to read this file.

Commands:
2.3. Special Considerations for Public Cloud Operators Public cloud service providers are exposed to a number of security risks beyond that of the traditional virtualization user. Virtual guest isolation, both between the host and guest as well as between guests, is critical due to the threat of malicious guests and the requirements on customer data confidentiality and integrity across the virtualization infrastructure. In addition to the Red Hat Enterprise Linux virtualization recommended practices previously listed, public cloud operators should also consider the following items: Disallow any direct hardware access from the guest. PCI, USB, FireWire, Thunderbolt, eSATA, and other device passthrough mechanisms make management difficult and often rely on the underlying hardware to enforce separation between the guests. Isolate the cloud operator's private management network from the customer guest network, and customer networks from one another, so that: The guests cannot access the host systems over the network. One customer cannot access another customer's guest systems directly through the cloud provider's internal network.

Commands:
4.5. Deploy Web Applications on WebLogic Server (Remote Client-Server Mode) Red Hat JBoss Data Grid supports the WebLogic 12c application server in Remote Client-Server mode. The following procedure describes how to deploy web applications on a WebLogic server. Procedure 4.2. Deploying Web Applications on a WebLogic Server To install the WebLogic server, see http://docs.oracle.com/cd/E24329_01/doc.1211/e24492/toc.htm . Configure JBoss Data Grid in Remote Client-Server mode, define cache, cache container, and endpoint configuration. After configuration, start JBoss Data Grid to confirm that the Hot Rod endpoint is listening on the configured port. For information about configuring JBoss Data Grid in Remote Client-Server, see Chapter 7, Run Red Hat JBoss Data Grid in Remote Client-Server Mode . Create a web application and add the infinispan-remote library as a dependency if Maven is used. Create a weblogic.xml deployment descriptor with the following elements in it: Note The prefer-web-inf-classes class indicates that the libraries and classes in the WEB-INF/lib folder are preferred over the default libraries bundled in the WebLogic server. For example, the commons-pool.jar file in the WebLogic server has version 1.4 and is automatically loaded by the classloader, however the Hot Rod client uses a newer version of this library. Add deployment descriptor file in the WEB-INF folder. Ensure that the infinispan-remote dependency is added to the pom.xml file, then use a Maven plugin to create a web archive. Alternatively, create the web archive manually and add the library manually. Deploy the application in the WebLogic server and verify that the Hot Rod client embedded inside the web application connects to the remote JBoss Data Grid server. Report a bug

Commands:
<?xml version="1.0" encoding="UTF-8"?> <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd"> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app>
Appendix C. Using AMQ Broker with the examples The AMQ Spring Boot Starter examples require a running message broker with a queue named example . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named example . USD <broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-05-07 10:16:47 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
22.16.4. Adding a Server Address To add the address of a server, that is to say, the address of a server running an NTP service of a higher stratum, make use of the server command in the ntp.conf file. The server command takes the following form: server address where address is an IP unicast address or a DNS resolvable name. The address of a remote reference server or local reference clock from which packets are to be received.

Commands:
8.220. tboot 8.220.1. RHBA-2013:1606 - tboot bug fix and enhancement update Updated tboot packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The tboot packages provide the Trusted Boot (tboot) open source pre-kernel/VMM module. This module uses Intel Trusted Execution Technology (Intel TXT) to initialize the launch of operating system kernels and virtual machines. Note The tboot packages have been upgraded to upstream version 1.7.4, which provides a number of bug fixes and enhancements over the version. (BZ# 916046 , BZ# 957158 ) Users of tboot are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: