mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 19. Authenticating third-party clients through RH-SSO To use the different remote services provided by Business Central or by KIE Server, your client, such as curl, wget, web browser, or a custom REST client, must authenticate through the RH-SSO server and have a valid token to perform the requests. To use the remote services, the authenticated user must have the following roles: rest-all for using Business Central remote services. kie-server for using the KIE Server remote services. Use the RH-SSO Admin Console to create these roles and assign them to the users that will consume the remote services. Your client can authenticate through RH-SSO using one of these options: Basic authentication, if it is supported by the client Token-based authentication 19.1. Basic authentication If you enabled basic authentication in the RH-SSO client adapter configuration for both Business Central and KIE Server, you can avoid the token grant and refresh calls and call the services as shown in the following examples: For web based remote repositories endpoint: For KIE Server:

Commands:
curl http://admin:password@localhost:8080/business-central/rest/repositories
curl http://admin:password@localhost:8080/kie-server/services/rest/server/
17.5. Establishing an xDSL Connection DSL stands for Digital Subscriber Lines . There are different types of DSL such as ADSL, IDSL, and SDSL. The Network Administration Tool uses the term xDSL to mean all types of DSL connections. Some DSL providers require that the system is configured to obtain an IP address through DHCP with an Ethernet card. Some DSL providers require you to configure a PPPoE (Point-to-Point Protocol over Ethernet) connection with an Ethernet card. Ask your DSL provider which method to use. If you are required to use DHCP, refer to Section 17.2, "Establishing an Ethernet Connection" to configure your Ethernet card. If you are required to use PPPoE, follow these steps: Click the Devices tab. Click the New button. Select xDSL connection from the Device Type list, and click Forward . If your Ethernet card is in the hardware list, select the Ethernet Device from the pulldown menu from the page shown in Figure 17.8, "xDSL Settings" . Otherwise, the Select Ethernet Adapter window appears. Note The installation program detects supported Ethernet devices and prompts you to configure them. If you configured any Ethernet devices during the installation, they are displayed in the hardware list on the Hardware tab. Figure 17.8. xDSL Settings If the Select Ethernet Adapter window appears, select the manufacturer and model of the Ethernet card. Select the device name. If this is the system's first Ethernet card, select eth0 as the device name; if this is the second Ethernet card, select eth1 (and so on). The Network Administration Tool also allows you to configure the resources for the NIC. Click Forward to continue. Enter the Provider Name , Login Name , and Password . If you have a T-Online account, instead of entering a Login Name and Password in the default window, click the T-Online Account Setup button and enter the required information. Click Forward to continue. On the Create DSL Connection page, click Apply . After configuring the DSL connection, it appears in the device list as shown in Figure 17.7, "Modem Device" . Figure 17.9. xDSL Device Be sure to select File => Save to save the changes. After adding the xDSL connection, you can edit its configuration by selecting the device from the device list and clicking Edit . For example, when the device is added, it is configured not to start at boot time by default. Edit its configuration to modify this setting. When the device is added, it is not activated immediately, as seen by its Inactive status. To activate the device, select it from the device list, and click the Activate button. If the system is configured to activate the device when the computer starts (the default), this step does not have to be performed again.

Commands:
Chapter 64. request This chapter describes the commands under the request command. 64.1. request token authorize Authorize a request token Usage: Table 64.1. Command arguments Value Summary -h, --help Show this help message and exit --request-key <request-key> Request token to authorize (id only) (required) --role <role> Roles to authorize (name or id) (repeat option to set multiple values) (required) Table 64.2. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 64.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 64.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 64.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 64.2. request token create Create a request token Usage: Table 64.6. Command arguments Value Summary -h, --help Show this help message and exit --consumer-key <consumer-key> Consumer key (required) --consumer-secret <consumer-secret> Consumer secret (required) --project <project> Project that consumer wants to access (name or id) (required) --domain <domain> Domain owning <project> (name or id) Table 64.7. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 64.8. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 64.9. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 64.10. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack request token authorize [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --request-key <request-key> --role <role>
openstack request token create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --consumer-key <consumer-key> --consumer-secret <consumer-secret> --project <project> [--domain <domain>]
4.9. Emerson Network Power Switch (SNMP interface) Table 4.10, "Emerson Network Power Switch (SNMP interface) (Red Hat Enterprise Linux 6.7 and later)" lists the fence device parameters used by fence_emerson , the fence agent for Emerson over SNMP. Table 4.10. Emerson Network Power Switch (SNMP interface) (Red Hat Enterprise Linux 6.7 and later) luci Field cluster.conf Attribute Description Name name A name for the Emerson Network Power Switch device connected to the cluster. IP Address or Hostname ipaddr The IP address or host name assigned to the device. UDP/TCP Port (optional) udpport UDP/TCP port to use for connections with the device; the default value is 161. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. SNMP Version snmp_version The SNMP version to use (1, 2c, 3); the default value is 1. SNMP Community community The SNMP community string. SNMP Security Level snmp_sec_level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv). SNMP Authentication Protocol snmp_auth_prot The SNMP authentication protocol (MD5, SHA). SNMP Privacy Protocol snmp_priv_prot The SNMP privacy protocol (DES, AES). SNMP privacy protocol password snmp_priv_passwd The SNMP Privacy Protocol Password. SNMP Privacy Protocol Script snmp_priv_passwd_script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Port (Outlet) Number port Physical plug number or name of virtual machine. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0.

Commands:
Chapter 7. Your responsibilities The subscriptions service and the features that make up this service are new and are rapidly evolving. During this rapid development phase, you have the ability to view, and more importantly contribute to, the newest capabilities early in the process. Your feedback is valued and welcome. Work with your Red Hat account team, for example, your technical account manager (TAM) or customer success manager (CSM), to provide this feedback. You might also be asked to provide feedback or request features from within the subscriptions service itself. As you use the subscriptions service, note the following agreements and contractual responsibilities that remain in effect: Customers are responsible for monitoring subscription utilization and complying with applicable subscription terms. The subscriptions service is a customer benefit to manage and view subscription utilization. Red Hat does not intend to create new billing events based on the subscriptions service tooling, rather the tooling will help the customer gain visibility into utilization so it can keep track of its environment.

Commands:
4.27. RHEV-M REST API Table 4.28, "RHEV-M REST API (RHEL 6.2 and later against RHEV 3.0 and later)" lists the fence device parameters used by fence_rhevm , the fence agent for RHEV-M REST API. Table 4.28. RHEV-M REST API (RHEL 6.2 and later against RHEV 3.0 and later) luci Field cluster.conf Attribute Description Name name Name of the RHEV-M REST API fencing device. IP Address or Hostname ipaddr The IP address or host name assigned to the device. IP Port (optional) ipport The TCP port to use for connection with the device. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Use SSL ssl Use SSL connections to communicate with the device. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Port (Outlet) Number port Physical plug number or name of virtual machine. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Figure 4.20, "RHEV-M REST API" shows the configuration screen for adding an RHEV-M REST API device Figure 4.20. RHEV-M REST API The following command creates a fence device instance for an RHEV-M REST API device: The following is the cluster.conf entry for the fence_rhevm device:

Commands:
ccs -f cluster.conf --addfencedev rhevmtest1 agent=fence_rhevm ipaddr=192.168.0.1 login=root passwd=password123 power_wait=60 ssl=on
<fencedevices> <fencedevice agent="fence_rhevm" ipaddr="192.168.0.1" login="root" name="rhevmtest1" passwd="password123" power_wait="60" ssl="on"/> </fencedevices>
23.4. Stacking I/O Parameters All layers of the Linux I/O stack have been engineered to propagate the various I/O parameters up the stack. When a layer consumes an attribute or aggregates many devices, the layer must expose appropriate I/O parameters so that upper-layer devices or tools will have an accurate view of the storage as it transformed. Some practical examples are: Only one layer in the I/O stack should adjust for a non-zero alignment_offset ; once a layer adjusts accordingly, it will export a device with an alignment_offset of zero. A striped Device Mapper (DM) device created with LVM must export a minimum_io_size and optimal_io_size relative to the stripe count (number of disks) and user-provided chunk size. In Red Hat Enterprise Linux 7, Device Mapper and Software Raid (MD) device drivers can be used to arbitrarily combine devices with different I/O parameters. The kernel's block layer will attempt to reasonably combine the I/O parameters of the individual devices. The kernel will not prevent combining heterogeneous devices; however, be aware of the risks associated with doing so. For instance, a 512-byte device and a 4K device may be combined into a single logical DM device, which would have a logical_block_size of 4K. File systems layered on such a hybrid device assume that 4K will be written atomically, but in reality it will span 8 logical block addresses when issued to the 512-byte device. Using a 4K logical_block_size for the higher-level DM device increases potential for a partial write to the 512-byte device if there is a system crash. If combining the I/O parameters of multiple devices results in a conflict, the block layer may issue a warning that the device is susceptible to partial writes and/or is misaligned.

Commands:
12.3.3. Creating a Directory-based Storage Pool with virsh Create the storage pool definition Use the virsh pool-define-as command to define a new storage pool. There are two options required for creating directory-based storage pools: The name of the storage pool. This example uses the name guest_images . All further virsh commands used in this example use this name. The path to a file system directory for storing guest image files. If this directory does not exist, virsh will create it. This example uses the /guest_images directory. Verify the storage pool is listed Verify the storage pool object is created correctly and the state reports it as inactive . Create the local directory Use the virsh pool-build command to build the directory-based storage pool for the directory guest_images (for example), as shown: Start the storage pool Use the virsh command pool-start to enable a directory storage pool, thereby allowing allowing volumes of the pool to be used as guest disk images. Turn on autostart Turn on autostart for the storage pool. Autostart configures the libvirtd service to start the storage pool when the service starts. Verify the storage pool configuration Verify the storage pool was created correctly, the size is reported correctly, and the state is reported as running . If you want the pool to be accessible even if the guest virtual machine is not running, make sure that Persistent is reported as yes . If you want the pool to start automatically when the service starts, make sure that Autostart is reported as yes . A directory-based storage pool is now available.

Commands:
virsh pool-define-as guest_images dir - - - - " /guest_images " Pool guest_images defined
virsh pool-list --all Name State Autostart ----------------------------------------- default active yes guest_images inactive no
virsh pool-build guest_images Pool guest_images built ls -la / guest_images total 8 drwx------. 2 root root 4096 May 30 02:44 . dr-xr-xr-x. 26 root root 4096 May 30 02:44 .. virsh pool-list --all Name State Autostart ----------------------------------------- default active yes guest_images inactive no
virsh pool-start guest_images Pool guest_images started virsh pool-list --all Name State Autostart ----------------------------------------- default active yes guest_images active no
virsh pool-autostart guest_images Pool guest_images marked as autostarted virsh pool-list --all Name State Autostart ----------------------------------------- default active yes guest_images active yes
virsh pool-info guest_images Name: guest_images UUID: 779081bf-7a82-107b-2874-a19a9c51d24c State: running Persistent: yes Autostart: yes Capacity: 49.22 GB Allocation: 12.80 GB Available: 36.41 GB ls -la /guest_images total 8 drwx------. 2 root root 4096 May 30 02:44 . dr-xr-xr-x. 26 root root 4096 May 30 02:44 .. #
28.2. Enabling Remote Access to the Installation System You may access either graphical or text interfaces for the installation system from any other system. Access to a text mode display requires telnet , which is installed by default on Red Hat Enterprise Linux systems. To remotely access the graphical display of an installation system, use client software that supports the VNC (Virtual Network Computing) display protocol. Note Red Hat Enterprise Linux includes the VNC client vncviewer . To obtain vncviewer , install the tigervnc package. The installation system supports two methods of establishing a VNC connection. You may start the installation, and manually login to the graphical display with a VNC client on another system. Alternatively, you may configure the installation system to automatically connect to a VNC client on the network that is running in listening mode . 28.2.1. Enabling Remote Access with VNC To enable remote graphical access to the installation system, enter two options at the prompt: The vnc option enables the VNC service. The vncpassword option sets a password for remote access. The example shown above sets the password as qwerty . Note The VNC password must be at least six characters long. Specify the language, keyboard layout and network settings for the installation system with the screens that follow. You may then access the graphical interface through a VNC client. The installation system displays the correct connection setting for the VNC client: You may then login to the installation system with a VNC client. To run the vncviewer client on Red Hat Enterprise Linux, choose Applications Accessories VNC Viewer , or type the command vncviewer in a terminal window. Enter the server and display number in the VNC Server dialog. For the example above, the VNC Server is computer.mydomain.com:1 .

Commands:
linux vnc vncpassword= qwerty
Starting VNC The VNC server is now running. Please connect to computer.mydomain.com:1 to begin the install Starting graphical installation Press <enter> for a shell
Chapter 2. Supported architectures The first version of Red Hat Enterprise Linux 9 for SAP Solutions to include E4S and EUS repositories as well as packages for SAP was RHEL 9.0, which is available for the following architectures: Intel 64-bit architecture (x86_64) IBM Power, Little Endian (ppc64le) For more information, see Red Hat Enterprise Linux Technology Capabilities and Limits .

Commands:
Introduction This document provides information about installing, configuring, and managing the Load Balancer Add-On components. The Load Balancer Add-On provides load balancing through specialized routing techniques that dispatch traffic to a pool of servers. The audience of this document should have advanced working knowledge of Red Hat Enterprise Linux and understand the concepts of clusters, storage, and server computing. This document is organized as follows: Chapter 1, Load Balancer Add-On Overview Chapter 2, Initial Load Balancer Add-On Configuration Chapter 3, Setting Up Load Balancer Add-On Chapter 4, Configuring the Load Balancer Add-On with Piranha Configuration Tool Appendix A, Using the Load Balancer Add-On with the High Availability Add-On For more information about Red Hat Enterprise Linux 6, see the following resources: Red Hat Enterprise Linux Installation Guide - Provides information regarding installation of Red Hat Enterprise Linux 6. Red Hat Enterprise Linux Deployment Guide - Provides information regarding the deployment, configuration and administration of Red Hat Enterprise Linux 6. For more information about the Load Balancer Add-On and related products for Red Hat Enterprise Linux 6, see the following resources: High Availability Add-On Overview - Provides a high-level overview of the High Availability Add-On, Resilient Storage Add-On, and the Load Balancer Add-On. Configuring and Managing the High Availability Add-On Provides information about configuring and managing the High Availability Add-On (also known as Red Hat Cluster) for Red Hat Enterprise Linux 6. Logical Volume Manager Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. Global File System 2: Configuration and Administration - Provides information about installing, configuring, and maintaining the Red Hat Resilient Storage Add-On (also known as Red Hat Global File System 2). DM Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux 6. Release Notes - Provides information about the current release of Red Hat products. This document and other Red Hat documents are available in HTML, PDF, and RPM versions online at https://access.redhat.com/documentation/en/red-hat-enterprise-linux/ . 1. Feedback If you spot a typo, 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 Product Red Hat Enterprise Linux 6 and the component doc-Load_Balancer_Administration . If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.

Commands:
15.3. Installation Method Use the arrow keys on your keyboard to select an installation method (refer to Figure 15.4, "Installation Method" ). With your selected method highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. Figure 15.4. Installation Method 15.3.1. Beginning Installation 15.3.1.1. Installing from a DVD To install Red Hat Enterprise Linux from a DVD, place the DVD your DVD drive and boot your system from the DVD. Even if you booted from alternative media, you can still install Red Hat Enterprise Linux from DVD media. The installation program then probes your system and attempts to identify your DVD drive. It starts by looking for an IDE (also known as an ATAPI) DVD drive. If your DVD drive is not detected, and it is a SCSI DVD, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most drivers detect your SCSI adapter automatically. If the DVD drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support. From the media check dialog, continue to the stage of the installation process (refer to Section 16.5, "Welcome to Red Hat Enterprise Linux" ).

Commands: