mtpti5iD/redhat-docs_dataset huggingface dataset:
21.4. Roles Permits Sub-Collection 21.4.1. Roles Permits Sub-Collection Each role contains a set of allowable actions, or permits , which the API lists in capabilities . A role's permits are listed as a sub-collection: Example 21.5. Listing a role's permits 21.4.2. Assign a Permit to a Role Assign a permit to a role with a POST request to the permits sub-collection. Use either an id attribute or a name element to specify the permit to assign. Example 21.6. Assign a permit to a role 21.4.3. Remove a Permit from a Role Remove a permit from a role with a DELETE request to the permit resource. Example 21.7. Remove a permit from a role

Commands:
GET /ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9/permits HTTP/1.1 Accept: application/xml HTTP/1.1 200 OK Content-Type: application/xml <permits> <permit id="1" href="/ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9/permits/1"> <name>create_vm</name> <administrative>false</administrative> <role id="b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9" href="/ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9"/> </permit> </permits>
POST /ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9/permits HTTP/1.1 Accept: application/xml Content-Type: application/xml <permit id="1"/> HTTP/1.1 201 Created Content-Type: application/xml <permits> <permit id="1" href="/ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9/permits/1"> <name>create_vm</name> <administrative>false</administrative> <role id="b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9" href="/ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9"/> </permit> </permits>
DELETE /ovirt-engine/api/roles/b67dfbe2-0dbc-41e4-86d3-a2fbef02cfa9/permits/1 HTTP/1.1 HTTP/1.1 204 No Content
4.6. Transaction Wrapping Modes You can set your transaction wrapping to one of the following modes: ON This mode always wraps every command in a transaction without checking whether it is required. This is the safest mode. OFF This mode never automatically wraps a command in a transaction or checks whether it needs to wrap a command. This mode can be dangerous as it will allow multiple source updates outside of a transaction without an error. This mode has best performance for applications that do not use updates or transactions. DETECT This mode assumes that the user does not know how to execute multiple source updates in a transaction. JBoss Data Virtualization checks every command to see whether it is a multiple source update and wraps it in a transaction. If it is single source then it uses the source level command transaction.

Commands:
Chapter 2. Admin REST API Red Hat build of Keycloak comes with a fully functional Admin REST API with all features provided by the Admin Console. To invoke the API you need to obtain an access token with the appropriate permissions. The required permissions are described in the Server Administration Guide . You can obtain a token by enabling authentication for your application using Red Hat build of Keycloak; see the Securing Applications and Services Guide. You can also use direct access grant to obtain an access token. 2.1. Examples of using CURL 2.1.1. Authenticating with a username and password Note The following example assumes that you created the user admin with the password password in the master realm as shown in the Getting Started Guide tutorial. Procedure Obtain an access token for the user in the realm master with username admin and password password : curl \ -d "client_id=admin-cli" \ -d "username=admin" \ -d "password=password" \ -d "grant_type=password" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" Note By default this token expires in 1 minute The result will be a JSON document. Invoke the API you need by extracting the value of the access_token property. Invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the master realm: curl \ -H "Authorization: bearer eyJhbGciOiJSUz..." \ "http://localhost:8080/admin/realms/master" 2.1.2. Authenticating with a service account To authenticate against the Admin REST API using a client_id and a client_secret , perform this procedure. Procedure Make sure the client is configured as follows: client_id is a confidential client that belongs to the realm master client_id has Service Accounts Enabled option enabled client_id has a custom "Audience" mapper Included Client Audience: security-admin-console Check that client_id has the role 'admin' assigned in the "Service Account Roles" tab. curl \ -d "client_id=<YOUR_CLIENT_ID>" \ -d "client_secret=<YOUR_CLIENT_SECRET>" \ -d "grant_type=client_credentials" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" 2.2. Additional resources Server Administration Guide Securing Applications and Services Guide API Documentation

Commands:
curl -d "client_id=admin-cli" -d "username=admin" -d "password=password" -d "grant_type=password" "http://localhost:8080/realms/master/protocol/openid-connect/token"
curl -H "Authorization: bearer eyJhbGciOiJSUz..." "http://localhost:8080/admin/realms/master"
curl -d "client_id=<YOUR_CLIENT_ID>" -d "client_secret=<YOUR_CLIENT_SECRET>" -d "grant_type=client_credentials" "http://localhost:8080/realms/master/protocol/openid-connect/token"
2.7. Managing the glusterd Service After installing Red Hat Gluster Storage, the glusterd service automatically starts on all the servers in the trusted storage pool. The service can be manually started and stopped by using the glusterd service commands. For more information on creating trusted storage pools, see the Red Hat Gluster Storage 3.5 Administration Guide . Use Red Hat Gluster Storage to dynamically change the configuration of glusterFS volumes without restarting servers or remounting volumes on clients. The glusterFS daemon glusterd also offers elastic volume management. Use the gluster CLI commands to decouple logical storage volumes from physical hardware. This allows the user to grow, shrink, and migrate storage volumes without any application downtime. As storage is added to the cluster, the volumes are distributed across the cluster. This distribution ensures that the cluster is always available despite changes to the underlying hardware. 2.7.1. Manually Starting and Stopping glusterd Use the following instructions to manually start and stop the glusterd service. Manually start glusterd as follows: or Manually stop glusterd as follows: or

Commands:
/etc/init.d/glusterd start
service glusterd start
/etc/init.d/glusterd stop
service glusterd stop
3. More to Come The Reference Guide is part of Red Hat's commitment to provide useful and timely support to Red Hat Enterprise Linux users. Future editions feature expanded information on changes to system structure and organization, new and powerful security tools, and other resources to help you extend the power of the Red Hat Enterprise Linux system - and your ability to use it. That is where you can help. 3.1. We Need Feedback! If you find an error in the Reference Guide , or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla ( http://bugzilla.redhat.com/bugzilla/ ) against the component rhel-rg . Be sure to mention the manual's identifier: If you mention the manual's identifier, we know exactly which version of the guide you have. If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

Commands:
rhel-rg
5.150. libhbaapi 5.150.1. RHBA-2012:0847 - libhbaapi bug fix update Updated libhbaapi packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The libhbaapi library is the Host Bus Adapter (HBA) API library for Fibre Channel and Storage Area Network (SAN) resources. It contains a unified API that programmers can use to access, query, observe and modify SAN and Fibre Channel services. The libhbaapi build environment has been upgraded to upstream version 2.2.5, which provides a number of bug fixes over the version. (BZ# 788504 ) Bug Fix BZ# 806731 Prior to this update, the hba.conf file was not marked for exclusion from verification in the libhbaapi specification file. As a consequence, the file verify function "rpm -V libhbaapi" reported an error in the hba.conf file if the file was changed. This update marks hba.conf in the spec file as "%verify(not md5 size mtime)". Now, the hba.conf file is no longer incorrectly verified. All users of libhbaapi are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.113. libhugetlbfs 8.113.1. RHBA-2014:1485 - libhugetlbfs bug fix and enhancement update Updated libhugetlbfs packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libhugetlbfs library interacts with the Linux Huge TLB file system to make large pages available to applications in a transparent manner. Note The libhugetlbfs packages have been upgraded to upstream version 2.16.0, which provides a number of bug fixes and enhancements over the version, including support for the IBM System z architecture. (BZ# 823006 ) Users of libhugetlbfs are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 23. Installation and Booting BFS installation fails on VV when automatic LVM partitioning is selected When attempting installation using Boot From SAN (BFS) with an HP StoreServ 3PAR Storage Volume (VV), the installation fails during disk partitioning and LVM volume group activation with the message: The failure is seen across all StoreServ volume types (Std VV, TPVV, TDVV). To work around this problem, if using LVM, select the Custom Partition Layout option and reduce the swap and /home partition size by 1-2 GB. If not using LVM, Select the Standard Partition option. (BZ#1190264) Using the --nocore option in the %packages section of a kickstart file may result in a broken system If the --nocore option is used in the %packages section of a kickstart file, core system packages and libraries will not be installed, which may result in the system being unable to perform essential tasks such as user creation, and may render the system unusable. To avoid this problem, do not use --nocore . (BZ#1191897) The zipl boot loader requires target information in each section When calling the zipl tool manually from a command line using a section name as a parameter, the tool was previously using the target defined in the default section of the /etc/zipl.conf file. In the current version of zipl the default sections' target is not being used automatically, resulting in an error. To work around the problem, manually edit the /etc/zipl.conf configuration file and copy the line starting with target= from the default section to every section. (BZ#1203627) The installer displays the number of multipath devices and number of multipath devices selected incorrectly Multipath devices are configured properly, but the installer displays the number of devices and number of selected devices incorrectly. There is no known workaround at this point. (BZ#914637) The installer displays the amount of disk space within multipath devices incorrectly Multipath devices are configured properly, but the installer displays disk space and number of devices incorrectly. There is no known workaround at this point. (BZ#1014425)

Commands:
Volume group "VolGroup" has insufficient free space.
Chapter 64. Placing custom tasks When a custom task is registered in Red Hat Process Automation Manager it appears in the process designer palette. The custom task is named and categorized according to the entries in its corresponding WID file. Prerequisites A custom task is registered in Red Hat Process Automation Manager. For more information, see Chapter 63, Registering custom tasks . The custom task is named and categorized according to the corresponding WID file. For more information about WID file locations or formatting, see Chapter 61, Work item definitions . Procedure In Business Central, go to Menu Design Projects and click a project. Select the business process that you want to add a custom task to. Select the custom task from the palette and drag it to the BPMN2 diagram. Optional: Change the custom task attributes. For example, change the data output and input from the corresponding WID file. Note If the WID file is not visible in your project and no Work Item Definition object is visible in the Others category of your project, you must register the custom task. For more information about registering a custom task, Chapter 63, Registering custom tasks .

Commands:
3.3. NFS Share Setup The following procedure configures the NFS share for the NFS daemon failover. You need to perform this procedure on only one node in the cluster. Create the /nfsshare directory. Mount the ext4 file system that you created in Section 3.2, "Configuring an LVM Volume with an ext4 File System" on the /nfsshare directory. Create an exports directory tree on the /nfsshare directory. Place files in the exports directory for the NFS clients to access. For this example, we are creating test files named clientdatafile1 and clientdatafile2 . Unmount the ext4 file system and deactivate the LVM volume group.

Commands:
mkdir /nfsshare
mount /dev/my_vg/my_lv /nfsshare
mkdir -p /nfsshare/exports mkdir -p /nfsshare/exports/export1 mkdir -p /nfsshare/exports/export2
touch /nfsshare/exports/export1/clientdatafile1 touch /nfsshare/exports/export2/clientdatafile2
umount /dev/my_vg/my_lv vgchange -an my_vg
Chapter 5. steps After completing the tutorial, consider the following steps: Explore the tutorial further. Use the MySQL command line client to add, modify, and remove rows in the database tables, and see the effect on the topics. Keep in mind that you cannot remove a row that is referenced by a foreign key. Plan a Debezium deployment. You can install Debezium in OpenShift or on Red Hat Enterprise Linux. For more information, see the following: Installing Debezium on OpenShift Installing Debezium on RHEL Revised on 2023-11-17 04:10:18 UTC

Commands:
2.4. Battery Life Tool Kit Red Hat Enterprise Linux 7 introduces the Battery Life Tool Kit ( BLTK ), a test suite that simulates and analyzes battery life and performance. BLTK achieves this by performing sets of tasks that simulate specific user groups and reporting on the results. Although developed specifically to test notebook performance, BLTK can also report on the performance of desktop computers when started with the -a . BLTK allows you to generate very reproducible workloads that are comparable to real use of a machine. For example, the office workload writes a text, corrects things in it, and does the same for a spreadsheet. Running BLTK combined with PowerTOP or any of the other auditing or analysis tool allows you to test if the optimizations you performed have an effect when the machine is actively in use instead of only idling. Because you can run the exact same workload multiple times for different settings, you can compare results for different settings. Install BLTK with the command: Run BLTK with the command: For example, to run the idle workload for 120 seconds: The workloads available by default are: -I , --idle system is idle, to use as a baseline for comparison with other workloads -R , --reader simulates reading documents (by default, with Firefox ) -P , --player simulates watching multimedia files from a CD or DVD drive (by default, with mplayer ) -O , --office simulates editing documents with the OpenOffice.org suite Other options allow you to specify: -a , --ac-ignore ignore whether AC power is available (necessary for desktop use) -T number_of_seconds , --time number_of_seconds the time (in seconds) over which to run the test; use this option with the idle workload -F filename , --file filename specifies a file to be used by a particular workload, for example, a file for the player workload to play instead of accessing the CD or DVD drive -W application , --prog application specifies an application to be used by a particular workload, for example, a browser other than Firefox for the reader workload BLTK supports a large number of more specialized options. For details, see the bltk man page. BLTK saves the results that it generates in a directory specified in the /etc/bltk.conf configuration file - by default, ~/.bltk/ workload .results. number / . For example, the ~/.bltk/reader.results.002/ directory holds the results of the third test with the reader workload (the first test is not numbered). The results are spread across several text files. To condense these results into a format that is easy to read, run: The results now appear in a text file named Report in the results directory. To view the results in a terminal emulator instead, use the -o option:

Commands:
~]# yum install bltk
~]USD bltk workload options
~]USD bltk -I -T 120
~]USD bltk_report path_to_results_directory
~]USD bltk_report -o path_to_results_directory
Chapter 3. Custom Inventory Scripts Note Inventory scripts have been discontinued. For more information, see Export old inventory scripts in the Automation controller User Guide . If you use custom inventory scripts, migrate to sourcing these scripts from a project. For more information, see Inventory File Importing , and Inventory sources in the Automation controller User Guide . If you are setting up an inventory file, see Editing the Red Hat Ansible Automation Platform installer inventory file and find examples specific to your setup. If you are migrating to execution environments, see: Upgrading to execution environments . Creating and consuming execution environments . Automation mesh design patterns . Mesh Topology in the Ansible Automation Platform Upgrade and Migration Guide to validate your topology. For more information about automation mesh on a VM-based installation, see the Red Hat Ansible Automation Platform automation mesh guide for VM-based installations . For more information about automation mesh on an operator-based installation, see the Red Hat Ansible Automation Platform automation mesh for operator-based installations . If you already have a mesh topology set up and want to view node type, node health, and specific details about each node, see Topology Viewer .

Commands:
8.241. xorg-x11-drv-qxl 8.241.1. RHBA-2013:1650 - xorg-x11-drv-qxl bug fix update Updated xorg-x11-drv-qxl packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-qxl packages provide an X11 video driver for the QEMU QXL video accelerator. This driver makes it possible to use Red Hat Enterprise Linux 6 as a guest operating system under the KVM kernel module and the QEMU multi-platform emulator, using the SPICE protocol. Bug Fixes BZ# 929037 When the user tried to start a guest with Red Hat Enterprise Linux 6 on a host with Red Hat Enterprise Linux 5, the QEMU QXL video accelerator failed with a segmentation fault. As a consequence, the guest was not able to start the system GUI. This update applies a patch to fix this bug and the guest now starts correctly. BZ# 951000 When using multiple QXL devices with the Xinerama extension, or multiple QXL devices while each being a separate screen, an attempt to set a resolution higher than 1024 x 768 pixels in the xorg.conf file failed with an error. With this update, the underlying source code has been modified and the resolution can now be set as expected. Users of xorg-x11-drv-qxl are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Edge clusters Edge clusters are a solution for cost-efficient object storage configurations. Red Hat supports the following minimum configuration of an Red Hat Ceph Storage cluster: A three node cluster with two replicas for SSDs. A four-node cluster with three replicas for HDDs. A four-node cluster with EC pool with 2+2 configuration. A four-node cluster with 8+6 CRUSH MSR configuration With smaller clusters, the utilization goes down because of the amount of usage and the loss of resiliency.

Commands:
Chapter 6. Security 6.1. Connecting with a user and password Red Hat build of Apache Qpid Proton DotNet can authenticate connections with a user and password. To specify the credentials used for authentication, set the Username and Password fields on the ConnectionOptions object Example: Connecting with a user and password ConnectionOptions connectionOptions = new(); connectionOptions.User = "user"; connectionOptions.Password = "pass"; 6.2. Configuring SASL authentication Client connections to remote peers may exchange SASL user name and password credentials. The presence of the user field in the connection URI controls this exchange. If user is specified then SASL credentials are exchanged; if user is absent then the SASL credentials are not exchanged. Various SASL mechanisms are supported, please see SASL Reference 6.3. Configuring an SSL/TLS transport Secure communication with servers is achieved using SSL/TLS. A client may be configured for SSL/TLS Handshake only or for SSL/TLS Handshake and client certificate authentication. See the Managing Certificates section for more information. Note TLS Server Name Indication (SNI) is handled automatically by the client library. However, SNI is signaled only for addresses that use the amqps transport scheme where the host is a fully qualified domain name or a host name. SNI is not signaled when the host is a numeric IP address.

Commands:
ConnectionOptions connectionOptions = new(); connectionOptions.User = "user"; connectionOptions.Password = "pass";
20.5. More Than a Secure Shell A secure command line interface is just the beginning of the many ways SSH can be used. Given the proper amount of bandwidth, X11 sessions can be directed over an SSH channel. Or, by using TCP/IP forwarding, previously insecure port connections between systems can be mapped to specific SSH channels. 20.5.1. X11 Forwarding Opening an X11 session over an established SSH connection is as easy as running an X program on a local machine. When an X program is run from the secure shell prompt, the SSH client and server create a new secure channel, and the X program data is sent over that channel to the client machine transparently. X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session with up2date . To do this, connect to the server using ssh and type: After supplying the root password for the server, you will be allowed to safely update the remote system.

Commands:
up2date &
5.289. rusers 5.289.1. RHBA-2012:0404 - rusers bug fix update Updated rusers packages that fix one bug are now available for Red Hat Enterprise Linux 6. The rusers program allows users to find out who is logged into various machines on the local network. The rusers command produces output similar to output of the who utility, but for the specified list of hosts or for all machines on the local network. Bug Fix BZ# 697862 Previously, no dependency on the rpcbind package was specified in the rstatd and rusers SysV init scripts. In addition, when the rstatd and rusersd services were started, a check to see if networking was enabled was not performed, and an incorrect exit code was returned. This update adds rpcbind dependency to the rusersd and rstatd init scripts. Also, the SysV init scripts have been adjusted to return correct exit codes. Checks are now performed when starting the rstatd and rusersd services to see whether networking is available and binding to rpcbind was successful. All users of rusers are advised to upgrade to these updated packages, which fix this bug.

Commands: