mtpti5iD/redhat-docs_dataset huggingface dataset:
3.3. Example: List Host Cluster Collection Red Hat Virtualization Manager creates a Default host cluster on installation. This example uses the Default cluster to group resources in your Red Hat Virtualization environment. The following request retrieves a representation of the cluster collection: Example 3.3. List host clusters collection Request: cURL command: Result: Note the id code of your Default host cluster. This code identifies this host cluster in relation to other resources of your virtual environment. The Default cluster is associated with the Default data center through a relationship using the id and href attributes of the data_center element. The networks sub-collection contains a list of associated network resources for this cluster. The section examines the networks collection in more detail.

Commands:
GET /ovirt-engine/api/clusters HTTP/1.1 Accept: application/xml
curl -X GET -H "Accept: application/xml" -u [USER:PASS] --cacert [CERT] https:// [RHEVM Host] :443/ovirt-engine/api/clusters
HTTP/1.1 200 OK Content-Type: application/xml <clusters> <cluster id="99408929-82cf-4dc7-a532-9d998063fa95" href="/ovirt-engine/api/clusters/99408929-82cf-4dc7-a532-9d998063fa95"> <name>Default</name> <description>The default server cluster</description> <link rel="networks" href="/ovirt-engine/api/clusters/99408929-82cf-4dc7-a532-9d998063fa95/networks"/> <link rel="permissions" href="/ovirt-engine/api/clusters/99408929-82cf-4dc7-a532-9d998063fa95/permissions"/> <cpu id="Intel Penryn Family"/> <data_center id="01a45ff0-915a-11e0-8b87-5254004ac988" href="/ovirt-engine/api/datacenters/01a45ff0-915a-11e0-8b87-5254004ac988"/> <memory_policy> <overcommit percent="100"/> <transparent_hugepages> <enabled>false</enabled> </transparent_hugepages> </memory_policy> <scheduling_policy/> <version minor="0" major="4"/> <error_handling> <on_error>migrate</on_error> </error_handling> </cluster> </clusters>
Chapter 47. Configuring 802.3 link settings Auto-negotiation is a feature of the IEEE 802.3u Fast Ethernet protocol. It targets the device ports to provide an optimal performance of speed, duplex mode, and flow control for information exchange over a link. Using the auto-negotiation protocol, you have optimal performance of data transfer over the Ethernet. Note To utilize maximum performance of auto-negotiation, use the same configuration on both sides of a link. 47.1. Configuring 802.3 link settings using the nmcli utility To configure the 802.3 link settings of an Ethernet connection, modify the following configuration parameters: 802-3-ethernet.auto-negotiate 802-3-ethernet.speed 802-3-ethernet.duplex Procedure Display the current settings of the connection: You can use these values if you need to reset the parameters in case of any problems. Set the speed and duplex link settings: This command enables auto-negotiation and sets the speed of the connection to 10000 Mbit full duplex. Reactivate the connection: Verification Use the ethtool utility to verify the values of Ethernet interface enp1s0 : Additional resources nm-settings(5) man page on your system

Commands:
nmcli connection show Example-connection 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: no
nmcli connection modify Example-connection 802-3-ethernet.auto-negotiate yes 802-3-ethernet.speed 10000 802-3-ethernet.duplex full
nmcli connection up Example-connection
ethtool enp1s0 Settings for enp1s0: Speed: 10000 Mb/s Duplex: Full Auto-negotiation: on Link detected: yes
3.14. Partial Results Warnings For each source that is excluded from the query, a warning will be generated describing the source and the failure. These warnings can be obtained from the Statement.getWarnings() method. This method returns a SQLWarning object, but in the case of partial results warnings this object will be an instance of the org.teiid.jdbc.PartialResultsWarning class. This class can be used to obtain a list of all the failed sources by name and to obtain the specific exception thrown by each resource adaptor. Note Since JBoss Data Virtualization supports cursoring before the entire result is formed, it is possible that a data source failure will not be determined until after the first batch of results have been returned to the client. This can happen in the case of unions, but not joins. To ensure that all warnings have been accumulated, the statement should be checked after the entire result set has been read. The following is an example of how to obtain partial results warnings:

Commands:
statement.execute("set partialResultsMode true"); ResultSet results = statement.executeQuery("SELECT Name FROM Accounts"); while (results.next()) { //process the result set } SQLWarning warning = statement.getWarnings(); if(warning instanceof PartialResultsWarning) { PartialResultsWarning partialWarning = (PartialResultsWarning)warning; Collection failedConnectors = partialWarning.getFailedConnectors(); Iterator iter = failedConnectors.iterator(); while(iter.hasNext()) { String connectorName = (String) iter.next(); SQLException connectorException = partialWarning.getConnectorException(connectorName); System.out.println(connectorName + ": " + connectorException.getMessage()); } }
Chapter 9. Configuring Secure Connections By default, clients and users connect to the Red Hat Directory Server over a standard connection. Standard connections do not use any encryption, so information is sent back and forth between the server and client in the clear. Directory Server supports TLS connections, STARTTLS connection, and SASL authentication, which provide layers of encryption and security that protect directory data from being read even if it is intercepted. 9.1. Requiring Secure Connections Directory Server provides the following ways of using encrypted connections: LDAPS When you use the LDAPS protocol, the connection starts using encryption and either succeeds or fails. However, no unencrypted data is ever send over the network. For this reason, prefer LDAPS instead of using STARTTLS over unencrypted LDAP. STARTTLS over LDAP Clients establish an unencrypted connection over the LDAP protocol and then send the STARTTLS command. If the command succeeds, all further communication is encrypted. Warning If the STARTTLS command fails and the client does not cancel the connection, all further data, including authentication information, is sent unencrypted over the network. SASL Simple Authentication and Security Layer (SASL) enables you to authenticate a user using external authentication methods, such as Kerberos. For details, see Section 9.10, "Setting up SASL Identity Mapping" .

Commands:
Installing Red Hat Virtualization as a standalone Manager with local databases Red Hat Virtualization 4.3 ALTERNATIVE method - Installing the Red Hat Virtualization Manager and its databases on the same server Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a standalone Manager environment - where the Red Hat Virtualization Manager is installed on either a physical server or a virtual machine hosted in another environment - with the Manager database and the Data Warehouse service and database installed on the same machine as the Manager. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
5.10. Configuring Fencing for Redundant Power Supplies When configuring fencing for redundant power supplies, the cluster must ensure that when attempting to reboot a host, both power supplies are turned off before either power supply is turned back on. If the node never completely loses power, the node may not release its resources. This opens up the possibility of nodes accessing these resources simultaneously and corrupting them. Prior to Red Hat Enterprise Linux 7.2, you needed to explicitly configure different versions of the devices which used either the 'on' or 'off' actions. Since Red Hat Enterprise Linux 7.2, it is now only required to define each device once and to specify that both are required to fence the node, as in the following example.

Commands:
pcs stonith create apc1 fence_apc_snmp ipaddr=apc1.example.com login=user passwd='7a4D#1j!pz864' pcmk_host_map="node1.example.com:1;node2.example.com:2" pcs stonith create apc2 fence_apc_snmp ipaddr=apc2.example.com login=user passwd='7a4D#1j!pz864' pcmk_host_map="node1.example.com:1;node2.example.com:2" pcs stonith level add 1 node1.example.com apc1,apc2 pcs stonith level add 1 node2.example.com apc1,apc2
Chapter 8. Running the certification tests RHCert CLI is the supported method to run tests. Procedure Run tests The non-interactive tag is an RHCert flag used to run all certification-related mandatory tests. Save the test result file By default, the result file is saved as /var/rhcert/save/rhcert-results-<host-name>-<timestamp>.xml .

Commands:
rhcert run
rhcert-save
2.3. Metadata Models Metadata model represents a collection of metadata information that describes a complete structure of data. In a example we described the field ZIPCode as a metadata object in an address book database. This meta object represents a single distinct bit of metadata information. We alluded to its parent table, StreetAddress. These meta objects, and others that would describe the other tables and columns within the database, would all combine to form a Source Metadata model for whichever enterprise information system hosts all the objects. You can have Source Models within your collection of metadata models. These represent physical data storage locations. You can also have View Models, which model the business view of the data. Each contains one type of metadata or another. For more information about difference between Source and View metadata, see Section Source and View Metadata.

Commands:
Chapter 14. The CarMart Quickstarts Red Hat JBoss Data Grid includes a transactional and non-transactional CarMart quickstart. The CarMart quickstart is a simple web application that uses JBoss Data Grid instead of a relational database. Information about each car is stored in a cache. Caches are configured declaratively or programmatically depending on the usage mode. Features The CarMart quickstart offers the following features: List all cars Add new cars Remove cars View statistics for caches, such as hits, stores, and retrievals Usage Modes The CarMart quickstart can be used in the following JBoss Data Grid usage modes: Remote Client-Server Mode, where the application includes the Hot Rod client to communicate with a remote JBoss Data Grid server. Library Mode, where all libraries are bundled with the application in the form of jar files. Location JBoss Data Grid's CarMart quickstart is available at the following location: jboss-datagrid-{VERSION}-quickstarts/ Report a bug 14.1. About the CarMart Transactional Quickstart The transactional version of the CarMart quickstart is a simple web application that uses Red Hat JBoss Data Grid instead of a relational database. Information about each car is stored in a cache. Caches are configured declaratively or programmatically (depending on the usage mode) and run in the same Java Virtual Machine (JVM) as the web application. Features The Transactional CarMart Quickstart offers the following features: List all cars Add new cars Add new cars with rollback Remove cars View statistics for caches, such as hits, stores, and retrievals Usage Modes The Transactional CarMart Quickstart can only be used in JBoss Data Grid's Library mode. A standalone transaction manager from JBoss Transactions is used when the Transactional CarMart Quickstart is run in Red Hat JBoss Enterprise Web Server 2.x. Location JBoss Data Grid's Transactional CarMart Quickstart can be found at the following location: jboss-datagrid-{VERSION}-quickstarts/carmart-tx Report a bug

Commands:
Chapter 1. Red Hat OpenShift Service on AWS CLI tools overview A user performs a range of operations while working on Red Hat OpenShift Service on AWS (ROSA) such as the following: Managing clusters Building, deploying, and managing applications Managing deployment processes Developing Operators Creating and maintaining Operator catalogs ROSA offers a set of command-line interface (CLI) tools that simplify these tasks by enabling users to perform various administration and development operations from the terminal. These tools expose simple commands to manage the applications, as well as interact with each component of the system. 1.1. List of CLI tools The following set of CLI tools are available in ROSA: OpenShift CLI ( oc ) : This is one of the more commonly used developer CLI tools. It helps both cluster administrators and developers to perform end-to-end operations across ROSA using the terminal. Unlike the web console, it allows the user to work directly with the project source code using command scripts. Knative CLI (kn) : The Knative ( kn ) CLI tool provides simple and intuitive terminal commands that can be used to interact with OpenShift Serverless components, such as Knative Serving and Eventing. Pipelines CLI (tkn) : OpenShift Pipelines is a continuous integration and continuous delivery (CI/CD) solution in Red Hat OpenShift Service on AWS, which internally uses Tekton. The tkn CLI tool provides simple and intuitive commands to interact with OpenShift Pipelines using the terminal. opm CLI : The opm CLI tool helps the Operator developers and cluster administrators to create and maintain the catalogs of Operators from the terminal. Operator SDK : The Operator SDK, a component of the Operator Framework, provides a CLI tool that Operator developers can use to build, test, and deploy an Operator from the terminal. It simplifies the process of building Kubernetes-native applications, which can require deep, application-specific operational knowledge. ROSA CLI ( rosa ) : Use the rosa CLI to create, update, manage, and delete ROSA clusters and resources.

Commands:
7.168. openssl 7.168.1. RHBA-2013:0443 - openssl bug fix update Updated openssl packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The openssl packages provide a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library. Bug Fixes BZ# 770872 Prior to this update, the pkgconfig configuration files of OpenSSL libraries contained an invalid libdir value. This update modifies the underlying code to use the correct libdir value. BZ#800088 Prior to this update, the openssl function "BIO_new_accept()" failed to listen on IPv4 addresses when this function was invoked with the "*:port" parameter. As a consequence, users failed to connect via IPv4 to a server that used this function call with the "*:port" parameter. This update modifies this function to listen on IPv4 address with this parameter as expected. BZ# 841645 Prior to this update, encrypted private key files that were saved in FIPS mode were corrupted because the PEM encryption uses hash algorithms that are not available in FIPS mode. This update uses the PKCS#8 encrypted format to write private keys to files in FIPS mode. This file format uses only algorithms that are available in FIPS mode. BZ# 841645 The manual page for "rand", the pseudo-random number generator, is named "sslrand" to avoid conflict with the manual page for the C library "rand()" function. This update provides the "openssl" manual page update to reflect this. All users of openssl are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. Adding RHEL metering to an AWS integration If you converted from a compatible third-party Linux distribution to Red Hat Enterprise Linux (RHEL) and purchased the RHEL for third party migration listing in Amazon Web Services (AWS), you can add RHEL metering to an AWS integration. With RHEL metering, Red Hat processes your bill to meter your hourly RHEL usage associated with a Red Hat offering in AWS. Procedure In AWS, tag your instances of RHEL that you want to meter. For more information about tagging your instances of RHEL in AWS, see Adding tags to an AWS resource . From Red Hat Hybrid Cloud Console , click Settings . Click Integrations . Click the more options menu for your integration. Click Edit . In Metered Product , select Red Hat Enterprise Linux from the drop-down to activate metering.

Commands:
6.4. User Private Groups Red Hat Enterprise Linux uses a user private group ( UPG ) scheme, which makes UNIX groups easier to manage. A UPG is created whenever a new user is added to the system. A UPG has the same name as the user for which it was created and that user is the only member of the UPG. UPGs make it safe to set default permissions for a newly created file or directory which allow both the user and that user's group to make modifications to the file or directory. The setting which determines what permissions are applied to a newly created file or directory is called a umask and is configured in the /etc/bashrc file. Traditionally on UNIX systems, the umask is set to 022 , which allows only the user who created the file or directory to make modifications. Under this scheme, all other users, including members of the creator's group , are not allowed to make any modifications. However, under the UPG scheme, this "group protection" is not necessary since every user has their own private group. 6.4.1. Group Directories Many IT organizations like to create a group for each major project and then assign people to the group if they need to access that project's files. Using this traditional scheme, managing files has been difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it is difficult to associate the right files with the right group. Using the UPG scheme, however, groups are automatically assigned to files created within a directory with the setgid bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group which owns the directory. Lets say, for example, that a group of people work on files in the /usr/lib/emacs/site-lisp/ directory. Some people are trusted to modify the directory, but certainly not everyone is trusted. First create an emacs group, as in the following command: To associate the contents of the directory with the emacs group, type: Now, it is possible to add the proper users to the group with the gpasswd command: To allow users to create files within the directory, use the following command: When a user creates a new file, it is assigned the group of the user's default private group. , set the setgid bit, which assigns everything created in the directory the same group permission as the directory itself ( emacs ). Use the following command: At this point, because each user's default umask is 002, all members of the emacs group can create and edit files in the /usr/lib/emacs/site-lisp/ directory without the administrator having to change file permissions every time users write new files.

Commands:
/usr/sbin/groupadd emacs
chown -R root.emacs /usr/lib/emacs/site-lisp
/usr/bin/gpasswd -a <username> emacs
chmod 775 /usr/lib/emacs/site-lisp
chmod 2775 /usr/lib/emacs/site-lisp
Chapter 98. DockerOutput schema reference Used in: Build The type property is a discriminator that distinguishes use of the DockerOutput type from ImageStreamOutput . It must have the value docker for the type DockerOutput . Property Property type Description image string The full name which should be used for tagging and pushing the newly built image. For example quay.io/my-organization/my-custom-connect:latest . Required. pushSecret string Container Registry Secret with the credentials for pushing the newly built image. additionalKanikoOptions string array Configures additional options which will be passed to the Kaniko executor when building the new Connect image. Allowed options are: --customPlatform, --custom-platform, --insecure, --insecure-pull, --insecure-registry, --log-format, --log-timestamp, --registry-mirror, --reproducible, --single-snapshot, --skip-tls-verify, --skip-tls-verify-pull, --skip-tls-verify-registry, --verbosity, --snapshotMode, --use-new-run, --registry-certificate, --registry-client-cert. These options will be used only on OpenShift where the Kaniko executor is used. They will be ignored on OpenShift. The options are described in the Kaniko GitHub repository . Changing this field does not trigger new build of the Kafka Connect image. type string Must be docker .

Commands:
Chapter 3. Deployment methods You can deploy Streams for Apache Kafka on OpenShift 4.14 and later using one of the following methods: Installation method Description Deployment files (YAML files) Download the deployment files to manually deploy Streams for Apache Kafka components. For the greatest flexibility, choose this method. OperatorHub Deploy the Streams for Apache Kafka Cluster operator through the OperatorHub, then deploy Streams for Apache Kafka components using custom resources. This method provides a standard configuration and allows you to take advantage of automatic updates.

Commands:
Chapter 3. Recovering multiple servers with replication If multiple servers are lost at the same time, determine if the environment can be rebuilt by seeing which one of the following five scenarios applies to your situation. 3.1. Recovering from losing multiple servers in a CA-less deployment Servers in a CA-less deployment are all considered equal, so you can rebuild the environment by removing and replacing lost replicas in any order. Prerequisites Your deployment uses an external Certificate Authority (CA). Procedure See Recovering from losing a regular replica . 3.2. Recovering from losing multiple servers when the CA renewal server is unharmed If the CA renewal server is intact, you can replace other servers in any order. Prerequisites Your deployment uses the IdM internal Certificate Authority (CA). Procedure See Recovering from losing a regular replica . 3.3. Recovering from losing the CA renewal server and other servers If you lose the CA renewal server and other servers, promote another CA server to the CA renewal server role before replacing other replicas. Prerequisites Your deployment uses the IdM internal Certificate Authority (CA). At least one CA replica is unharmed. Procedure Promote another CA replica to fulfill the CA renewal server role. See Recovering from losing the CA renewal server . Replace all other lost replicas. See Recovering from losing a regular replica .

Commands: