mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Ansible terminology The chapters in this title use the official Ansible terminology. If you are not familiar with the terminology, read the official Ansible upstream documentation before proceeding, especially the following sections: The Basic concepts in Ansible section provides an overview of the most commonly used concepts in Ansible. The User guide outlines the most common situations and questions when starting to use Ansible, such as using the command line; working with an inventory; interacting with data; writing tasks, plays, and playbooks; and executing playbooks. How to build your inventory offers tips on how to design your inventory. An inventory is a list or a group of lists that Ansible uses to work against multiple managed nodes or hosts in your infrastructure. Intro to playbooks introduces the concept of an Ansible playbook as a repeatable and re-usable system for managing configurations, deploying machines, and deploying complex applications. The Ansible roles section explains how to automate loading variables, tasks, and handlers based on a known file structure. The Glossary explains terms that are used elsewhere in the Ansible documentation.

Commands:
Chapter 6. Migrating business processes to the new process designer The legacy process designer in Business Central is deprecated in Red Hat Decision Manager 7.13.5. It will be removed in a future Red Hat Decision Manager release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. Note The process engine will continue to support the execution and deployment of business processes generated with the legacy designer into KIE Server. If you have a legacy business process that is functioning and that you do not intend to change, it is not mandatory to migrate to the new designer at this time. You can only migrate business processes that contain supported business process nodes in the new designer. More nodes will be added in future versions of Red Hat Decision Manager. Prerequisites You have an existing project that contains a business process asset that was created with the legacy process designer. Procedure In Business Central, click Menu Design Projects . Click the project you want to migrate, for example Mortgages . Click Ok to open the project's asset list. Click the project's Business Process asset to open it in the legacy process designer. Click Migrate Migrate Diagram . Figure 6.1. Migration confirmation message Select Yes or No to confirm if you made changes. This option is only available if you have made changes to your legacy business process. Figure 6.2. Save diagram changes confirmation If the migration is successful, the business process opens in the new process designer and the business process name's extension changes from *.bpmn2 to *.bpmn. If the migration is unsuccessful due to an unsupported node type, Business Central displays the following error message: Figure 6.3. Migration failure message

Commands:
Chapter 3. Accessing the MTR tools You can access the MTR plugin tools in the MTR perspective. Prerequisites You must restart the Eclipse IDE after installing the MTR plugin. Procedure Click Window Perspective Open Perspective Other . Select MTR and click OK . The following components are displayed: Issue Explorer displays the migration issues identified by the MTR plugin. MTR Server is a separate process that analyzes projects, flags migration issues, and generates reports. You can start, stop, and view the status of the MTR server in the Issue Explorer . Issue Details displays detailed information about a selected issue, including the hint, severity, and any additional resources. MTR Report is an HTML report generated by the MTR plugin. From the report landing page you can navigate to detailed reports, such as Application Details, Issues, and Dependencies. Note The report is not generated by default. You must select the Generate Report option in the run configuration.

Commands:
Chapter 3. Using service accounts with services The following information briefly describes how to use service accounts with services and the CLIENT_ID and CLIENT_SECRET variables. It is provided as a reference guideline only. Create a new Service account: Red Hat Hybrid Cloud Console Service accounts Paste the following information on a terminal, replacing the CLIENT_ID and CLIENT_SECRET variables: Get a token for the service account with If you have jq installed (a command-line JSON processor), you can save the token to an env var: Send a request to an application that supports service accounts: The response should be empty, or unprivileged depending on the app. Try adding the service account to an RBAC group, and adding roles to that group. User Access Groups After roles are added to the service account group, repeat step 3 to grab a fresh token and attempt the request again. You should now have more privileges and get proper responses from applications.

Commands:
export HOST='https://sso.redhat.com' CLIENT_ID='<client_id>' CLIENT_SECRET='<client_secret>' SCOPES='openid api.iam.service_accounts'
curl "USD{HOST}/auth/realms/redhat-external/protocol/openid-connect/token" --data-urlencode "grant_type=client_credentials" --data-urlencode "client_id=USD{CLIENT_ID}" --data-urlencode "client_secret=USD{CLIENT_SECRET}" --data-urlencode "scope=USD{SCOPES}"
export ACCESS_TOKEN=USD( curl "USD{HOST}/auth/realms/redhat-external/protocol/openid-connect/token" --data-urlencode "grant_type=client_credentials" --data-urlencode "client_id=USD{CLIENT_ID}" --data-urlencode "client_secret=USD{CLIENT_SECRET}" --data-urlencode "scope=USD{SCOPES}" | jq -r '.access_token')
curl --header "Authorization:Bearer USD{ACCESS_TOKEN}" --location "https://console.redhat.com/api/rbac/v1/access/?application=inventory"
Chapter 2. Subscriptions To install the Red Hat Virtualization Manager and hosts, your systems must be registered with the Content Delivery Network using Red Hat Subscription Management. This section outlines the subscriptions and repositories required to set up a Red Hat Virtualization environment. 2.1. Required Subscriptions and Repositories The packages provided in the following repositories are required to install and configure a functioning Red Hat Virtualization environment. When one of these repositories is required to install a package, the steps required to enable the repository are provided in the appropriate location in the documentation. Table 2.1. Red Hat Virtualization Manager Subscription Pool Repository Name Repository Label Details Red Hat Enterprise Linux Server Red Hat Enterprise Linux Server rhel-8-for-x86_64-baseos-rpms Provides the Red Hat Enterprise Linux 8 Server. Red Hat Enterprise Linux Server Red Hat Enterprise Linux Server rhel-8-for-x86_64-appstream-rpms Provides the Red Hat Enterprise Linux 8 Server. Red Hat Virtualization Red Hat Virtualization rhv-4.4-manager-for-rhel-8-x86_64-rpms Provides the Red Hat Virtualization Manager. Red Hat Virtualization Red Hat JBoss Enterprise Application Platform jb-eap-7.4-for-rhel-8-x86_64-rpms Provides the supported release of Red Hat JBoss Enterprise Application Platform on which the Manager runs. Red Hat Virtualization Red Hat Fast Datapath for RHEL 8 (RPMs) fast-datapath-for-rhel-8-x86_64-rpms Provides Open vSwitch (OVS) packages. Table 2.2. Red Hat Virtualization Host Subscription Pool Repository Name Repository Label Details Red Hat Virtualization Red Hat Virtualization Host rhvh-4-for-rhel-8-x86_64-rpms Provides the redhat-virtualization-host-image-update package, which allows you to update the image installed on the host. Table 2.3. Red Hat Enterprise Linux 8 Hosts Subscription Pool Repository Name Repository Label Details Red Hat Enterprise Linux Server Red Hat Enterprise Linux Server rhel-8-for-x86_64-baseos-rpms Provides the Red Hat Enterprise Linux 8 Server. Red Hat Enterprise Linux Server Red Hat Enterprise Linux Server rhel-8-for-x86_64-appstream-rpms Provides the Red Hat Enterprise Linux 8 Server. Red Hat Virtualization Red Hat Virtualization Management Agents (RPMs) rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms Provides the QEMU and KVM packages required for using Red Hat Enterprise Linux 8 servers as virtualization hosts. Red Hat Advanced Virtualization Red Hat Advanced Virtualization advanced-virt-for-rhel-8-x86_64-rpms Provides packages for advanced virtualization. Red Hat Virtualization Red Hat Fast Datapath for RHEL 8 (RPMs) fast-datapath-for-rhel-8-x86_64-rpms Provides Open vSwitch (OVS) packages.

Commands:
Chapter 128. KafkaBridgeTemplate schema reference Used in: KafkaBridgeSpec Property Description deployment Template for Kafka Bridge Deployment . DeploymentTemplate pod Template for Kafka Bridge Pods . PodTemplate apiService Template for Kafka Bridge API Service . InternalServiceTemplate podDisruptionBudget Template for Kafka Bridge PodDisruptionBudget . PodDisruptionBudgetTemplate bridgeContainer Template for the Kafka Bridge container. ContainerTemplate clusterRoleBinding Template for the Kafka Bridge ClusterRoleBinding. ResourceTemplate serviceAccount Template for the Kafka Bridge service account. ResourceTemplate initContainer Template for the Kafka Bridge init container. ContainerTemplate

Commands:
B.108. xorg-x11-server-utils B.108.1. RHSA-2011:0433 - Moderate: xorg-x11-server-utils security update An updated xorg-x11-server-utils package that fixes one security issue is now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A 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. The xorg-x11-server-utils package contains a collection of utilities used to modify and query the runtime configuration of the X.Org server. X.Org is an open source implementation of the X Window System. CVE-2011-0465 A flaw was found in the X.Org X server resource database utility, xrdb. Certain variables were not properly sanitized during the launch of a user's graphical session, which could possibly allow a remote attacker to execute arbitrary code with root privileges, if they were able to make the display manager execute xrdb with a specially-crafted X client hostname. For example, by configuring the hostname on the target system via a crafted DHCP reply, or by using the X Display Manager Control Protocol (XDMCP) to connect to that system from a host that has a special DNS name. Red Hat would like to thank Matthieu Herrb for reporting this issue. Upstream acknowledges Sebastian Krahmer of the SuSE Security Team as the original reporter. Users of xorg-x11-server-utils should upgrade to this updated package, which contains a backported patch to resolve this issue. All running X.Org server instances must be restarted for this update to take effect.

Commands:
Chapter 9. Using the Gluster Command Line Interface The Gluster command line interface (CLI) simplifies configuration and management of the storage environment. The Gluster CLI is similar to the LVM (Logical Volume Manager) CLI or the ZFS CLI, but operates across multiple storage servers. The Gluster CLI can be used when volumes are mounted (active) and not mounted (inactive). Red Hat Gluster Storage automatically synchronizes volume configuration information across all servers. Use the Gluster CLI to create new volumes, start and stop existing volumes, add bricks to volumes, remove bricks from volumes, and change translator settings. Additionally, the Gluster CLI commands can create automation scripts and use the commands as an API to allow integration with third-party applications. Note Appending --mode=script to any CLI command ensures that the command executes without confirmation prompts. Running the Gluster CLI Run the Gluster CLI on any Red Hat Gluster Storage Server by either invoking the commands or running the Gluster CLI in interactive mode. The gluster command can be remotely used via SSH. Run commands directly as follows, after replacing COMMAND with the required command: The following is an example using the peer status command: Gluster CLI Interactive Mode Alternatively, run the Gluster CLI in interactive mode using the following command: If successful, the prompt changes to the following: When the prompt appears, execute gluster commands from the CLI prompt as follows: As an example, replace the COMMAND with a command such as peer status to view the status of the peer server: Start Gluster CLI's interactive mode: Request the peer server status: The peer server status displays. The following is another example, replacing the COMMAND with a command such as help to view the gluster help options. Start Gluster CLI's interactive mode: Request the help options: A list of gluster commands and options displays.

Commands:
gluster COMMAND
gluster peer status
gluster
gluster>
gluster> COMMAND
gluster
gluster> peer status
gluster
gluster> help
Chapter 13. The Infinispan CDI Module Infinispan includes Context and Dependency Injection (CDI) in the infinispan-cdi module. The infinispan-cdi module offers: Configuration and injection using the Cache API. A bridge between the cache listeners and the CDI event system. Partial support for the JCACHE caching annotations. Report a bug 13.1. Using Infinispan CDI 13.1.1. Infinispan CDI Prerequisites The following is a list of prerequisites to use the Infinispan CDI module with Red Hat JBoss Data Grid: Ensure that the most recent version of the infinispan-cdi module is used. Ensure that the correct dependency information is set. Report a bug 13.1.2. Set the CDI Maven Dependency The CDI module is included in the Infinispan jar for each deployment type, and no additional dependencies are required. Library Mode In Library mode the infinispan-embedded artifact contains the CDI module, and should be added as a dependency as seen in the below example: Remote Client-Server Mode In Remote Client-Server mode the infinispan-remote artifact contains the CDI module, and should be added as a dependency as seen in the below example: Report a bug

Commands:
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded</artifactId> <version>USD{infinispan.version}</version> </dependency>
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-remote</artifactId> <version>USD{infinispan.version}</version> </dependency>
Chapter 4. tuned and tuned-adm This chapter covers using the tuned daemon for tuning system settings in virtualized environments. tuned is a tuning profile delivery mechanism that adapts Red Hat Enterprise Linux for certain workload characteristics, such as requirements for CPU-intensive tasks, or storage/network throughput responsiveness. It provides a number of tuning profiles that are pre-configured to enhance performance and reduce power consumption in a number of specific use cases. Edit these profiles or create new profiles to create performance solutions tailored to your environment. The virtualization-related profiles provided as part of tuned include: virtual-guest Based on the throughput-performance profile, virtual-guest also decreases the swappiness of virtual memory. The virtual-guest profile is automatically selected when creating a Red Hat Enterprise Linux 7 guest virtual machine. It is the recommended profile for virtual machines. This profile is available in Red Hat Enterprise Linux 6.3 and later, but must be manually selected when installing a virtual machine. virtual-host Based on the throughput-performance profile, virtual-host also enables more aggressive writeback of dirty pages. This profile is the recommended profile for virtualization hosts, including both KVM and Red Hat Virtualization (RHV) hosts. By default in a Red Hat Enterprise Linux 7 installation, the tuned package is installed and the tuned service is enabled. To list all available profiles and identify the current active profile, run: It is also possible to create custom tuned profiles to encapsulate a set of tuning parameters. For instructions on creating custom tuned profiles, see the tuned.conf man page. To only display the currently active profile, run: To switch to one of the available profiles, run: For example, to switch to the virtual-host profile, run: Important After setting a tuned profile in Red Hat Enterprise Linux 7.1 and above, make sure the tuned service is enabled for the configured profile to be applied after a reboot: In some cases, it is preferable to disable tuned to use parameters set manually. To disable all tuning for the current session, run: To permanently disable tuned and revert all changes it performed, run: Note For further information about tuned , see the Red Hat Enterprise Linux 7 Performance Tuning Guide .

Commands:
tuned-adm list Available profiles: - balanced - desktop - latency-performance - network-latency - network-throughput - powersave - sap - throughput-performance - virtual-guest - virtual-host Current active profile: throughput-performance
tuned-adm active
tuned-adm profile profile_name
tuned-adm profile virtual-host
systemctl enable tuned
tuned-adm off
tuned-adm off; systemctl disable tuned
1.3.5. Viewing Changes Viewing the Status To determine the current status of a working copy, change to the directory with the working copy and run the following command: cvs status This displays detailed information about each file that is under revision control, including its current status (such as Up-to-date , Locally Added , Locally Removed , or Locally Modified ) and revision. However, if you are only interested in what has changed in your working copy, you can simplify the output by typing the following at a shell prompt: cvs status 2> /dev/null | grep Status: | grep -v Up-to-date Example 1.20. Viewing the status of a working copy Imagine that the directory with your working copy of a CVS repository has the following contents: With the exception of ChangeLog , which is scheduled for addition to the CVS repository, all files and directories within this directory are already under revision control. The TODO file, which is also under revision control, has been scheduled for removal and is no longer present in the working copy. Finally, Makefile contains local changes. To display the status of such a working copy, type: Viewing Differences To view differences between a working copy and the checked out content, change to the directory with the working copy and run the following command: cvs diff [ file ... ] This displays changes to all files in the working copy. If you are only interested in changes to a particular file, supply the file name on the command line. Example 1.21. Viewing changes to a working copy Imagine that the directory with your working copy of a CVS repository has the following contents: All files in this directory are under revision control and Makefile contains local changes. To view these changes, type:

Commands:
project]USD ls AUTHORS ChangeLog CVS doc INSTALL LICENSE Makefile README src
project]USD cvs status 2>/dev/null | grep Status: | grep -v Up-to-date File: ChangeLog Status: Locally Added File: Makefile Status: Locally Modified File: no file TODO Status: Locally Removed
project]USD ls AUTHORS ChangeLog CVS doc INSTALL LICENSE Makefile README src
project]USD cvs diff cvs diff: Diffing . cvs diff: ChangeLog is a new entry, no comparison available Index: Makefile =================================================================== RCS file: /home/john/cvs/project/Makefile,v retrieving revision 1.1.1.1 diff -r1.1.1.1 Makefile 156c156 < -rm -f USD(MAN1) --- > -rm -f USD(MAN1) USD(MAN7) cvs diff: TODO was removed, no comparison available cvs diff: Diffing doc
Chapter 7. Deploying SSSD Containers With Different Configurations As a system administrator, you can deploy multiple unprivileged SSSD containers that each use a specific identity provider, such as Identity Management or Active Directory. This enables other application containers to use only their preferred identity source. 7.1. Prerequisites To use the services provided by the SSSD container from other containers, the client container's rhel7 base image must include the sssd-client package. However, the default rhel7 base image does not include this package. If you need to use the SSSD services from other containers, create your own image for the client container based on the default rhel7 base image and include sssd-client . For details, see Creating Docker images . 7.2. Starting the SSSD Container and Joining It to an Identity Resource To start an SSSD container and join it to an identity resource, such as Active Directory: Start the SSSD container by using the atomic install command. For example: The example creates an SSSD application container named ad_sssd . Pass the DNS server IP address, search domain, host name, and realm join command to atomic install to automatically join SSSD running in the container to the Active Directory domain. Repeat this step for each identity provider for which you want to provide an SSSD container. Start the container. For example: 7.3. Passing the SSSD Cache to an Application Container To use the SSSD cache in an application container, pass the relevant directories to the docker run command when you start the application container: This maps the directories of the SSSD container to the corresponding directory inside the application container. The application running in the container is now able to authenticate using, for example, the kinit utility or the mod_auth_gssapi module.

Commands:
atomic install --opt1='--dns=192.0.2.1 --dns-search=idm.example.com --hostname=server.ad.example.com -e SSSD_CONTAINER_TYPE=application --net=default' --name=ad_sssd rhel7/sssd realm join -v ad.example.com
atomic run ad_sssd
docker run --rm --name=<container_name> -v=/var/lib/sssd_container/<sssd-container-name>/client/etc/krb5.conf.d:/etc/krb5.conf.d -v=/var/lib/sssd_container/<sssd-container-name>/client/var/lib/sss/pipes/:/var/lib/sss/pipes/ <image_name>
4.7. apr 4.7.1. RHBA-2012:0740 - apr bug fix update An updated apr package that fixes one bug is now available for Red Hat Enterprise Linux 6. The Apache Portable Runtime (APR) is a portability library used by the Apache HTTP Server and other projects. It provides a free library of C data structures and routines. Bug Fix BZ# 830265 Previously, a bug in the handling of IPv6 sockets was present in the apr_mcast_hops() function. This bug could have prevented applications from successfully using multicast with IPv6 sockets. With this update, this bug has been fixed so that the applications now operate correctly. All APR users are advised to install this newly released package, which fixes this bug.

Commands: