mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Configure Red Hat Identity Management In this example, IdM is situated externally to the OpenStack Red Hat OpenStack Platform director deployment and is the source of all user and group information. RH-SSO will be configured to use IdM as its User Federation, and will then perform LDAP searches against IdM to obtain user and group information. 2.1. Create the IdM Service Account for RH-SSO Although IdM allows anonymous binds, some information is withheld for security reasons. Some of this information withheld during anonymous binds is essential for RH-SSO user federation; consequently, RH-SSO will need to bind to the IdM LDAP server with enough privileges to successfully query the required information. As a result, you will need to create a dedicated service account for RH-SSO in IdM. IdM does not natively provide a command to do this, but you can use the ldapmodify command. For example: Note You can use the configure-federation script to perform the above step: 2.2. Create a test user You will also need a test user account in IdM. You can either use an existing user or create a new one; the examples in this guide use "John Doe" with a uid of jdoe . You can create the jdoe user in IdM: Assign a password to the user: 2.3. Create an IdM group for OpenStack Users Create the openstack-users group in IdM. Make sure the openstack-users group does not already exist: Add the openstack-users group to IdM: Add the test user to the openstack-users group: Verify that the openstack-users group exists and has the test user as a member:

Commands:
ldap_url="ldaps://USDFED_IPA_HOST" dir_mgr_dn="cn=Directory Manager" service_name="rhsso" service_dn="uid=USDservice_name,cn=sysaccounts,cn=etc,USDFED_IPA_BASE_DN" ldapmodify -H "USDldap_url" -x -D "USDdir_mgr_dn" -w "USDFED_IPA_ADMIN_PASSWD" <<EOF dn: USDservice_dn changetype: add objectclass: account objectclass: simplesecurityobject uid: USDservice_name userPassword: USDFED_IPA_RHSSO_SERVICE_PASSWD passwordExpirationTime: 20380119031407Z nsIdleTimeout: 0 EOF
./configure-federation create-ipa-service-account
ipa user-add --first John --last Doe --email jdoe@example.com jdoe
ipa passwd jdoe
ipa group-show openstack-users ipa: ERROR: openstack-users: group not found
ipa group-add openstack-users
ipa group-add-member --users jdoe openstack-users
ipa group-show openstack-users Group name: openstack-users GID: 331400001 Member users: jdoe
Appendix C. Using AMQ Broker with the examples The Red Hat build of Apache Qpid ProtonJ2 examples require a running message broker with a queue named hello-world-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 hello-world-example . USD <broker-instance-dir> /bin/artemis queue create --name hello-world-example --address hello-world-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 2023-12-08 12:44:53 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 hello-world-example --address hello-world-example --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
17.2. Using IdM and DNS Service Discovery with an Existing DNS Configuration To help create and configure a suitable DNS setup, the IdM installation script creates a sample zone file. During the installation, IdM displays a message similar to the following: If a DNS server is already configured in the network, then the configuration in the IdM-generated file can be added to the existing DNS zone file. This allows IdM clients to find . For example, this DNS zone configuration is created for an IdM server with the KDC and DNS servers all on the same machine in the EXAMPLE.COM realm: Example 17.1. Default IdM DNS File Note If DNS services are hosted by a server outside the IdM domain, then an administrator can add the lines in Example 17.1, "Default IdM DNS File" to the existing DNS zone file. This allows IdM clients and servers to continue to use DNS service discovery to find the LDAP and Kerberos servers (meaning, the IdM servers) that are required for them to participate in the IdM domain.

Commands:
Sample zone file for bind has been created in /tmp/sample.zone.F_uMf4.db
; ldap servers _ldap._tcp IN SRV 0 100 389 ipaserver.example.com. ;kerberos realm _kerberos IN TXT EXAMPLE.COM ; kerberos servers _kerberos._tcp IN SRV 0 100 88 ipaserver.example.com. _kerberos._udp IN SRV 0 100 88 ipaserver.example.com. _kerberos-master._tcp IN SRV 0 100 88 ipaserver.example.com. _kerberos-master._udp IN SRV 0 100 88 ipaserver.example.com. _kpasswd._tcp IN SRV 0 100 464 ipaserver.example.com. _kpasswd._udp IN SRV 0 100 464 ipaserver.example.com.
Chapter 203. Kubernetes Persistent Volume Claim Component Available as of Camel version 2.17 The Kubernetes Persistent Volume Claim component is one of Kubernetes Components which provides a producer to execute kubernetes persistent volume claim operations. 203.1. Component Options The Kubernetes Persistent Volume Claim component has no options. 203.2. Endpoint Options The Kubernetes Persistent Volume Claim endpoint is configured using URI syntax: with the following path and query parameters: 203.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 203.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 203.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.kubernetes-persistent-volumes-claims.enabled Whether to enable auto configuration of the kubernetes-persistent-volumes-claims component. This is enabled by default. Boolean camel.component.kubernetes-persistent-volumes-claims.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean

Commands:
kubernetes-persistent-volumes-claims:masterUrl
Chapter 17. General Updates Matahari Matahari in Red Hat Enterprise Linux 6.2 is fully supported only for x86 and AMD64 architectures. Builds for other architectures are considered a Technology Preview. Automatic Bug Reporting Tool Red Hat Enterprise Linux 6.2 introduces ABRT 2.0. ABRT logs details of software crashes on a local system, and provides interfaces (both graphical and command line based) to report issues to various issue trackers, including Red Hat support. This update provides the following notable enhancements: More flexible configuration with a new syntax. Out-ouf-process plugins (plugins run in separate processes and communicate via inter-process communication with other processes). Advantages of such a design are: bugs in plugins do not break the main daemon, more secure as most of the processing is now done under the normal (non-root) user, plugins can be written in any programming language. Reporting backend is shared across all of Red Hat's issue reporting tools: ABRT , sealert , all users of python-meh ( Anaconda , firstboot ) Because all of the tools above share the same configuration, it only has to be written once. Note For more information on ABRT configuration and its new syntax, refer to the Red Hat Enterprise Linux 6.2 Deployment Guide . Optimized math library for Linux on IBM System z Red Hat Enterprise Linux 6.2 provides an optimized linear algebra math library for Linux on System z which enables the compiler to generate code for high profile functions, taking advantage of the latest hardware functions. Improved tablet support Red Hat Enterprise Linux 6.2 improves support for Wacom devices. It is no longer necessary to reconfigure device settings after a device has been unplugged and plugged back in. Improved wireless detection NetworkManager can now scan wireless networks in the background, providing a better user experience. Increase in CPU support in GNOME The gnome-system-monitor utility can now monitor systems that have more than 64 CPUs.

Commands:
2.2. pcs Usage Help Display You can use the -h option of pcs to display the parameters of a pcs command and a description of those parameters. For example, the following command displays the parameters of the pcs resource command. Only a portion of the output is shown.

Commands:
pcs resource -h Usage: pcs resource [commands] Manage pacemaker resources Commands: show [resource id] [--all] Show all currently configured resources or if a resource is specified show the options for the configured resource. If --all is specified resource options will be displayed start <resource id> Start resource specified by resource_id
Chapter 1. About networking Red Hat OpenShift Networking is an ecosystem of features, plugins and advanced networking capabilities that extend Kubernetes networking with the advanced networking-related features that your cluster needs to manage its network traffic for one or multiple hybrid clusters. This ecosystem of networking capabilities integrates ingress, egress, load balancing, high-performance throughput, security, inter- and intra-cluster traffic management and provides role-based observability tooling to reduce its natural complexities. Note OpenShift SDN CNI is deprecated as of OpenShift Container Platform 4.14. As of OpenShift Container Platform 4.15, the network plugin is not an option for new installations. In a subsequent future release, the OpenShift SDN network plugin is planned to be removed and no longer supported. Red Hat will provide bug fixes and support for this feature until it is removed, but this feature will no longer receive enhancements. As an alternative to OpenShift SDN CNI, you can use OVN Kubernetes CNI instead. The following list highlights some of the most commonly used Red Hat OpenShift Networking features available on your cluster: Primary cluster network provided by either of the following Container Network Interface (CNI) plugins: OVN-Kubernetes network plugin , the default plugin OpenShift SDN network plugin Certified 3rd-party alternative primary network plugins Cluster Network Operator for network plugin management Ingress Operator for TLS encrypted web traffic DNS Operator for name assignment MetalLB Operator for traffic load balancing on bare metal clusters IP failover support for high-availability Additional hardware network support through multiple CNI plugins, including for macvlan, ipvlan, and SR-IOV hardware networks IPv4, IPv6, and dual stack addressing Hybrid Linux-Windows host clusters for Windows-based workloads Red Hat OpenShift Service Mesh for discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring of services Single-node OpenShift Network Observability Operator for network debugging and insights Submariner for inter-cluster networking Red Hat Service Interconnect for layer 7 inter-cluster networking

Commands:
20.3. Input Methods Changes in IBus Red Hat Enterprise Linux 7 includes support for the Intelligent Input Bus (IBus) version 1.5. Support for IBus is now integrated in GNOME. Input methods can be added using the gnome-control-center region command, and the gnome-control-center keyboard command can be used to set input hotkeys. For non-GNOME sessions, ibus can configure both XKB layouts and input methods in the ibus-setup tool and switch them with a hotkey. The default hotkey is Super + space , replacing Control + space in ibus included in Red Hat Enterprise Linux 6. This provides a similar UI which the user can see with the Alt + Tab combination. Multiple input methods can be switched using the Alt + Tab combination. Predictive Input Method for IBus ibus-typing-booster is a predictive input method for the ibus platform. It predicts complete words based on partial input. Users can select the desired word from a list of suggestions and improve their typing speed and spelling. ibus-typing-booster works also with the Hunspell dictionaries and can make suggestions for a language using a Hunspell dictionary. Note that the ibus-typing-booster package is an optional package, and therefore will not be installed as part of the input-methods group by default. For more detailed changes in input methods, see Desktop Migration and Administration Guide .

Commands:
Chapter 13. Red Hat Enterprise Linux Atomic Host 7.6.5 13.1. Atomic Host OStree update : New Tree Version: 7.6.5 (hash: 52bd811e0f47458cebda889283064392251963536748ce94267a59f0fc7b3254) Changes since Tree Version 7.6.4 (hash: a403eb67b418b3fe30ba02a3bf8b00d63a6648baf4bf65457e1ae23f107d6e35) 13.2. Extras Updated packages : buildah-1.8.2-2.gite23314b.el7 container-selinux-2.99-1.el7_6 etcd-3.2.26-1.el7 oci-systemd-hook-0.2.0-1.git05e6923.el7_6 podman-1.3.2-1.git14fdcd0.el7 python-websocket-client-0.56.0-1.git3c25814.el7 13.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.6 Container Image (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux 7.6 Container Image for aarch64 (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Universal Base Image 7 Container Image (rhel7/ubi7) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) Red Hat Universal Base Image 7 Minimal Container Image (rhel7/ubi7-minimal)

Commands:
Chapter 3. Release components Node.js 22 LTS Builder Image for RHEL 8 Node.js 22 LTS Universal Base Image 8 Node.js 22 LTS Minimal Stand-alone Image for RHEL 8 Node.js 22 LTS Minimal Universal Base Image 8 Node.js 22 LTS Builder Image for RHEL 9 Node.js 22 LTS Universal Base Image 9 Node.js 22 LTS Minimal Stand-alone Image for RHEL 9 Node.js 22 LTS Minimal Universal Base Image 9

Commands:
Chapter 10. Revising project versions You can revise the version number of a project in Red Hat Process Automation Manager before you build and deploy a new instance of the project. Creating a new version of a project preserves the old version in case there is a problem with the new one and you need to revert back. Prerequisites KIE Server is deployed and connected to Business Central. Procedure In Business Central, go to Menu Design Projects . Click the project you want to deploy, for example Mortgage_Process . Click Deploy . If there is no container with the project name, a container with default values is automatically created. If an older version of the project is already deployed, go to the project settings and change the project version. When finished, save the change and click Deploy . This will deploy a new version of the same project with the latest changes in place, alongside the older version(s). Note You can also select the Build & Install option to build the project and publish the KJAR file to the configured Maven repository without deploying to a KIE Server. In a development environment, you can click Deploy to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option is disabled and you can click Deploy only to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a corresponding project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode. To review project deployment details, click View deployment details in the deployment banner at the top of the screen or in the Deploy drop-down menu. This option directs you to the Menu Deploy Execution Servers page. To verify process definitions, click Menu Manage Process Definitions , and click . Click in the Actions column and select Start to start a new instance of the process.

Commands:
14.4.3. Using the sftp Utility The sftp utility can be used to open a secure, interactive FTP session. In its design, it is similar to ftp except that it uses a secure, encrypted connection. To connect to a remote system, use a command in the following form: For example, to log in to a remote machine named penguin.example.com with john as a user name, type: After you enter the correct password, you will be presented with a prompt. The sftp utility accepts a set of commands similar to those used by ftp (see Table 14.3, "A selection of available sftp commands" ). Table 14.3. A selection of available sftp commands Command Description ls [ directory ] List the content of a remote directory . If none is supplied, a current working directory is used by default. cd directory Change the remote working directory to directory . mkdir directory Create a remote directory . rmdir path Remove a remote directory . put localfile [ remotefile ] Transfer localfile to a remote machine. get remotefile [ localfile ] Transfer remotefile from a remote machine. For a complete list of available commands, see the sftp (1) manual page.

Commands:
sftp username @ hostname
~]USD sftp john@penguin.example.com john@penguin.example.com's password: Connected to penguin.example.com. sftp>