mtpti5iD/redhat-docs_dataset huggingface dataset:
7.266. virt-top 7.266.1. RHBA-2013:0391 - virt-top bug fix and enhancement update Updated virt-top packages that fix two bugs and add three enhancements are now available for Red Hat Enterprise Linux 6. The virt-top utility displays statistics of virtualized domains and uses many of the same keys and command-line options as the top utility. Bug Fixes BZ# 807176 Prior to this update, the "-o" (sort) option was not properly described in the output of the "virt-top --help" command. Four of the possible sort parameters were not mentioned in the description. This bug has been fixed and the full range of sort parameters is now shown in the virt-top --help message. BZ# 834208 Previously, the column names of the virt-top summary table were not explained in the virt-top man page. The manual page has been updated, and the headings are now properly documented in the "COLUMN HEADINGS" section. Enhancements BZ# 825627 The copyright information has been updated in the virt-top man pages and help documents. BZ# 835547 This update adds a separate man page for the processcsv.py script, which was previously documented only in the virt-top man page. BZ#841759 With this update, the "virt-top -1" command has been enhanced to separately display the usage of virtual CPUs. Two numbers are now shown under each domain column; the first is the percentage of the physical CPU used by the domain and the hypervisor together, the second is the percentage used just by the domain. This information is important for performance tuning and other tasks. All users of virt-top are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ JMS in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ JMS, you must install Apache Maven . To use AMQ JMS, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.qpid</groupId> <artifactId>qpid-jms-client</artifactId> <version>1.0.0.redhat-00001</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ JMS can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Clients 2.10.0 JMS Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-clients-2.10.0-jms-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use the git clone command to clone the source repository to a local directory named qpid-jms : USD git clone https://github.com/apache/qpid-jms.git qpid-jms Change to the qpid-jms directory and use the git checkout command to switch to the 1.0.0 branch: USD cd qpid-jms USD git checkout 1.0.0 The resulting local directory is referred to as <source-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.qpid</groupId> <artifactId>qpid-jms-client</artifactId> <version>1.0.0.redhat-00001</version> </dependency>
unzip amq-clients-2.10.0-jms-maven-repository.zip
git clone https://github.com/apache/qpid-jms.git qpid-jms
cd qpid-jms git checkout 1.0.0
Chapter 11. Dashboard (horizon) Parameters You can modify the horizon service with dashboard parameters. Parameter Description HorizonAllowedHosts A list of IP/Hostname for the server OpenStack Dashboard (horizon) is running on. Used for header checks. The default value is * . HorizonCustomizationModule OpenStack Dashboard (horizon) has a global overrides mechanism available to perform customizations. HorizonDomainChoices Specifies available domains to choose from. We expect an array of hashes, and the hashes should have two items each (name, display) containing OpenStack Identity (keystone) domain name and a human-readable description of the domain respectively. HorizonHelpURL On top of dashboard there is a Help button. This button could be used to re-direct user to vendor documentation or dedicated help portal. The default value is http://docs.openstack.org . HorizonHstsHeaderValue Enables HTTP Strict-Transport-Security header in response. HorizonPasswordValidator Regex for password validation. HorizonPasswordValidatorHelp Help text for password validation. HorizonSecret Secret key for the webserver. HorizonSecureCookies Set CSRF_COOKIE_SECURE / SESSION_COOKIE_SECURE in OpenStack Dashboard (horizon). The default value is false . HorizonSessionTimeout Set session timeout for horizon in seconds. The default value is 1800 . HorizonVhostExtraParams Extra parameters for OpenStack Dashboard (horizon) vhost configuration. The default value is {'add_listen': 'true', 'priority': '10', 'access_log_format': '%a %l %u %t \\"%r\\" %>s %b \\"%%{}{Referer}i\\" \\"%%{}{User-Agent}i\\"', 'options': ['FollowSymLinks', 'MultiViews']} . MemcachedIPv6 Enable IPv6 features in Memcached. The default value is false . TimeZone The timezone to be set on the overcloud. The default value is UTC . WebSSOChoices Specifies the list of SSO authentication choices to present. Each item is a list of an SSO choice identifier and a display message. The default value is [['OIDC', 'OpenID Connect']] . WebSSOEnable Enable support for Web Single Sign-On. The default value is false . WebSSOIDPMapping Specifies a mapping from SSO authentication choice to identity provider and protocol. The identity provider and protocol names must match the resources defined in keystone. The default value is {'OIDC': ['myidp', 'openid']} . WebSSOInitialChoice The initial authentication choice to select by default. The default value is OIDC .

Commands:
Chapter 1. Remote caches Deploy multiple Data Grid Server instances to create remote cache clusters that give you a fault-tolerant and scalable data tier with high-speed access from Hot Rod and REST clients. 1.1. Remote cache tutorials To run these tutorials you need at least one locally running instance of Data Grid Server. Each tutorial will try to connect to a running server in localhost:11222 with admin/password credentials. However, if a Docker instance is found, and the server is not running, tutorials will spin up a local server with Testcontainers . You can download the distribution and run the following commands: USD ./bin/cli.sh user create admin -p "password" USD ./bin/server.sh Note Data Grid Server enables authentication and authorization by default. Creating a user named admin gives you administrative access to Data Grid Server. Building and running remote cache tutorials You can build and run remote cache tutorials directly in your IDE or from the command line as follows: USD mvn -s /path/to/maven-settings.xml clean package exec:exec 1.2. Hot Rod Java client tutorials Data Grid requires Java 11 at a minimum. However, Hot Rod Java clients running in applications that require Java 8 can continue using older versions of client libraries. Tutorial link Description Remote cache use example The simplest code example that demonstrates how a remote distributed cache works. Per cache configuration Demonstrates how to configure caches dynamically when we connect to the Data Grid Server. Near caches Demonstrates how configure near caching to improve the read performance in remote caches. Cache Admin API Demonstrates how to use the Administration API to create caches and cache templates dynamically. Encoding Demonstrates how encoding of caches work. Client listeners Detect when data changes in a remote cache with Client Listeners. Query Demonstrates how to query remote cache values. Continuous query Demonstrates how to use Continuous Query and remote caches. Transactions Demonstrates how remote transactions work. Secured caches Demonstrates how to configure caches that have authorization enabled. TLS authorization Demonstrates how to connect to Data Grid Server with TLS authorization. Counters Demonstrates how remote counters work. Multimap Demonstrates how remote multimap works. Task execution Demonstrates how to register server tasks and how to execute them from the Hot Rod client. JUnit 5 and Testcontainers Demonstrates how to use the Data Grid and JUnit 5 extension. Persistence Demonstrates how to use the Data Grid and persistent caches. Redis Client Demonstrates how to use the Data Grid and Redis client to read and write using the Resp protocol. Reactive API Demonstrates how to use the Data Grid with the reactive API based on Mutiny. Data Grid documentation You can find more resources for Hot Rod Java clients in our documentation at: Hot Rod Java client guide Marshalling and Encoding Data Guide Querying Data Grid caches REST API Resp Protocol Smallrye Mutiny

Commands:
./bin/cli.sh user create admin -p "password" ./bin/server.sh
mvn -s /path/to/maven-settings.xml clean package exec:exec
Chapter 3. Technology Previews Important Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Technology Preview features in production environments. This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope . 3.1. Kafka Static Quota plugin configuration Use the Kafka Static Quota plugin to set throughput and storage limits on brokers in your Kafka cluster. You enable the plugin and set limits by configuring the Kafka resource. You can set a byte-rate threshold and storage quotas to put limits on the clients interacting with your brokers. Example Kafka Static Quota plugin configuration apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: kafka: # ... config: client.quota.callback.class: io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce: 1000000 client.quota.callback.static.fetch: 1000000 client.quota.callback.static.storage.soft: 400000000000 client.quota.callback.static.storage.hard: 500000000000 client.quota.callback.static.storage.check-interval: 5 See Setting limits on brokers using the Kafka Static Quota plugin . 3.2. Cruise Control for cluster rebalancing You can deploy Cruise Control and use it to rebalance your Kafka cluster using optimization goals - defined constraints on CPU, disk, network load, and more. In a balanced Kafka cluster, the workload is more evenly distributed across the broker pods. Cruise Control is configured and deployed as part of a Kafka resource. You can use the default optimization goals or modify them to suit your requirements. Example YAML configuration files for Cruise Control are provided in examples/cruise-control/ . When Cruise Control is deployed, you can create KafkaRebalance custom resources to: Generate optimization proposals from multiple optimization goals Rebalance a Kafka cluster based on an optimization proposal Other Cruise Control features are not currently supported, including anomaly detection, notifications, write-your-own goals, and changing the topic replication factor. See Cruise Control for cluster rebalancing .

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: kafka: # config: client.quota.callback.class: io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce: 1000000 client.quota.callback.static.fetch: 1000000 client.quota.callback.static.storage.soft: 400000000000 client.quota.callback.static.storage.hard: 500000000000 client.quota.callback.static.storage.check-interval: 5
A.8. Setting Virtual Machine Custom Properties Once custom properties are defined in the Red Hat Virtualization Manager, you can begin setting them on virtual machines. Custom properties are set on the Custom Properties tab of the New Virtual Machine and Edit Virtual Machine windows in the Administration Portal. You can also set custom properties from the Run Virtual Machine(s) dialog box. Custom properties set from the Run Virtual Machine(s) dialog box will only apply to the virtual machine until it is shutdown. The Custom Properties tab provides a facility for you to select from the list of defined custom properties. Once you select a custom property key an additional field will display allowing you to enter a value for that key. Add additional key/value pairs by clicking the + button and remove them by clicking the - button.

Commands:
4.260. qpid-tools 4.260.1. RHBA-2011:1668 - qpid-tools bug fix update An updated qpid-tools package that fixes various bugs and adds an enhancement is now available for Red Hat Enterprise Linux 6. The qpid-tools package provides management and diagnostic tools for Apache Qpid brokers and clients. The qpid-tools package has been upgraded to upstream version 0.12, which provides a number of bug fixes and enhancements over the version. (BZ# 706992 ) Bug Fixes BZ# 688163 Prior to this update, the qmf-tool utility did not have options to select an authentication method. Consequently users could not connect to the qpid console securely. With this update the qmf-tool has been improved to allow extended command line options for selecting an authentication method. As a result command line options can now be used to select an authentication method and users can connect to the qpid console securely. BZ# 711180 Prior to this update, when attempting to stop a node in a cluster by specifying the ID number with the command "qpid-cluster -s [ID]", qpid-cluster terminated unexpectedly, the requested node was not stopped, and the error message "'NoneType' object has no attribute 'split'" was displayed. With this update qpid-tools no longer crashes and the nodes can be stopped by specifying their IDs in the scenario described. All users of qpid-tools are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
Chapter 10. Distributed tracing The client offers distributed tracing based on the Jaeger implementation of the OpenTracing standard. 10.1. Enabling distributed tracing Use the following steps to enable tracing in your application: Procedure Add the Jaeger client dependency to your POM file. <dependency> <groupId>io.jaegertracing</groupId> <artifactId>jaeger-client</artifactId> <version>USD{jaeger-version}</version> </dependency> USD{jaeger-version} must be 1.0.0 or later. Add the jms.tracing option to your connection URI. Set the value to opentracing . Example: A connection URI with tracing enabled Register the global tracer. Example: Global tracer registration import io.jaegertracing.Configuration; import io.opentracing.Tracer; import io.opentracing.util.GlobalTracer; public class Example { public static void main(String[] args) { Tracer tracer = Configuration.fromEnv(" <service-name> ").getTracer(); GlobalTracer.registerIfAbsent(tracer); // ... } } Configure your environment for tracing. Example: Tracing configuration USD export JAEGER_SAMPLER_TYPE=const USD export JAEGER_SAMPLER_PARAM=1 USD java -jar example.jar net.example.Example The configuration shown here is for demonstration purposes. For more information about Jaeger configuration, see Configuration via Environment and Jaeger Sampling . To view the traces your application captures, use the Jaeger Getting Started to run the Jaeger infrastructure and console.

Commands:
<dependency> <groupId>io.jaegertracing</groupId> <artifactId>jaeger-client</artifactId> <version>USD{jaeger-version}</version> </dependency>
amqps://example.net? jms.tracing=opentracing
import io.jaegertracing.Configuration; import io.opentracing.Tracer; import io.opentracing.util.GlobalTracer; public class Example { public static void main(String[] args) { Tracer tracer = Configuration.fromEnv(" <service-name> ").getTracer(); GlobalTracer.registerIfAbsent(tracer); // } }
export JAEGER_SAMPLER_TYPE=const export JAEGER_SAMPLER_PARAM=1 java -jar example.jar net.example.Example
Chapter 4. Upgrading Red Hat JBoss Web Server using this Service Pack To install this service pack: Go to the Software Downloads page for Red Hat JBoss Web Server 6.0 . Note You require a Red Hat subscription to access the Software Downloads page. Download the Red Hat JBoss Web Server 6.0 Service Pack 2 archive file that is appropriate to your platform. Extract the archive file to the Red Hat JBoss Web Server installation directory. If you have installed Red Hat JBoss Web Server from RPM packages on Red Hat Enterprise Linux, you can use the following yum command to upgrade to the latest service pack:

Commands:
yum upgrade
Chapter 15. Registering RHEL by using Subscription Manager Post-installation, you must register your system to get continuous updates. 15.1. Registering RHEL 8 using the installer GUI You can register a Red Hat Enterprise Linux 8 by using the RHEL installer GUI. Prerequisites You have a valid user account on the Red Hat Customer Portal. See the Create a Red Hat Login page . You have a valid Activation Key and Organization id. Procedure From the Installation Summary screen, under Software , click Connect to Red Hat . Authenticate your Red Hat account using the Account or Activation Key option. Optional: In the Set System Purpose field select the Role , SLA , and Usage attribute that you want to set from the drop-down menu. At this point, your Red Hat Enterprise Linux 8 system has been successfully registered. 15.2. Registration Assistant Registration Assistant is designed to help you choose the most suitable registration option for your Red Hat Enterprise Linux environment. Additional resources For assistance with using a username and password to register RHEL with the Subscription Manager client, see the RHEL registration assistant on the Customer Portal. For assistance with registering your RHEL system to Red Hat Insights, see the Insights registration assistant on the Hybrid Cloud Console. 15.3. Registering your system using the command line You can register your Red Hat Enterprise Linux 8 subscription by using the command line. For an improved and simplified experience registering your hosts to Red Hat, use remote host configuration (RHC). The RHC client registers your system to Red Hat making your system ready for Insights data collection and enabling direct issue remediation from Insights for Red Hat Enterprise Linux. For more information, see RHC registration . Prerequisites You have an active, non-evaluation Red Hat Enterprise Linux subscription. Your Red Hat subscription status is verified. You have not previously received a Red Hat Enterprise Linux 8 subscription. You have successfully installed Red Hat Enterprise Linux 8 and logged into the system as root. Procedure Open a terminal window as a root user. Register your Red Hat Enterprise Linux system by using the activation key: When the system is successfully registered, an output similar to the following is displayed: Additional resources Using an activation key to register a system with Red Hat Subscription Manager Getting Started with RHEL System Registration

Commands:
subscription-manager register --activationkey= <activation_key_name> --org= <organization_ID>
The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
Chapter 33. Printer Configuration Printer Configuration Tool allows users to configure a printer. This tool helps maintain the printer configuration file, print spool directories, print filters, and printer classes. Red Hat Enterprise Linux 4 uses the Common Unix Printing System ( CUPS ). If a system was upgraded from a Red Hat Enterprise Linux version that used CUPS, the upgrade process preserves the configured queues. Using Printer Configuration Tool requires root privileges. To start the application, select Applications (the main menu on the panel) => Administration => Printing , or type the command system-config-printer at a shell prompt. Figure 33.1. Printer Configuration Tool The following types of print queues can be configured: AppSocket/HP JetDirect - a printer connected directly to the network through HP JetDirect or Appsocket interface instead of a computer. Internet Printing Protocol (IPP) - a printer that can be accessed over a TCP/IP network via the Internet Printing Protocol (for example, a printer attached to another Red Hat Enterprise Linux system running CUPS on the network). LPD/LPR Host or Printer - a printer attached to a different UNIX system that can be accessed over a TCP/IP network (for example, a printer attached to another Red Hat Enterprise Linux system running LPD on the network). Networked Windows (SMB) - a printer attached to a different system which is sharing a printer over an SMB network (for example, a printer attached to a Microsoft Windows TM machine). Networked JetDirect - a printer connected directly to the network through HP JetDirect instead of a computer. Important If you add a new print queue or modify an existing one, you must apply the changes for them to take effect. Clicking the Apply button prompts the printer daemon to restart with the changes you have configured. Clicking the Revert button discards unapplied changes. 33.1. Adding a Local Printer To add a local printer, such as one attached through a parallel port or USB port on your computer, click the New Printer button in the main Printer Configuration Tool window to display the window in Figure 33.2, " Adding a Printer " . Figure 33.2. Adding a Printer Click Forward to proceed. Enter a unique name for the printer in the Printer Name field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it must not contain any spaces. You can also use the Description and Location fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces. Click Forward to open the New Printer dialogue (refer to Figure 33.3, "Adding a Local Printer" ). If the printer has been automatically detected, the printer model appears in Select Connection . Select the printer model and click Forward to continue. If the device does not automatically appear, select the device to which the printer is connected (such as LPT #1 or Serial Port #1 ) in Select Connection . Figure 33.3. Adding a Local Printer , select the printer type. Refer to Section 33.5, "Selecting the Printer Model and Finishing" for details.

Commands: