mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Installation This chapter describes the prerequisites for installing the AMQ Broker plug-in and the process for obtaining and installing it. 2.1. Prerequisites Before you can install the AMQ Broker plug-in, the following components must be installed, configured, and running: JBoss ON Server AMQ Broker JON Agent Related information Getting Started with AMQ Broker Configuring AMQ Broker Managing AMQ Broker JON 3.3 Installation Guide Configuring JON Servers and Agents 2.2. Downloading and Installing the AMQ Broker Plug-in JON uses plug-ins to handle specific JBoss resources, such as AMQ or EAP, and other applications. JON resource plug-ins are distributed in "plug-in packs" that are distributed separately from the JON Server and JON Agents. Plug-in packs may also require a separate subscription to download them. When you install a plug-in pack on the JON server, its contents are available for download by JON agents. As a result, JBoss resources can be discovered and imported into the inventory to be managed. To download and install the plug-in pack, complete the following steps: Log in to the Red Hat Customer Portal and navigate to the Software Download page. Select JBoss ON for AMQ from the Product drop-down menu. The Software Downloads page reloads and displays available releases. Select Download . A dialog prompts you to open or save the zip archive file. Save the zip archive and extract the files to a temporary directory, for example: This creates a subdirectory with the name jon-plugin-pack-3.3 . Copy the extracted plug-in JAR files from the jon-plugin-pack-plugin_3.3/ directory to the JBoss ON server plug-in directory. For example: 2.3. Updating the Plug-ins on the JON Server On stand-alone platforms, prompt the JBoss ON server to update its plug-ins by either restarting the server or by using the JON web interface, as follows: Click Administration > Configuration > Agent Plugins . Click Scan For Updates in the bottom left corner. Locate Red Hat JBoss AMQ 7 in the list of agent plug-ins and verify that the Last Updated timestamp is current. On managed platforms, you can prompt agents to manually reload their plug-ins by using the plugins command: Alternatively, if the agents are imported into the JON inventory, this can be done in the JON GUI by scheduling an update plugins operation for an agent or a group of agents. To do so, select the agent resource entry in the inventory, open the Operations tab, and schedule the update plug-ins operation. Related information JON 3.3 Installation Guide

Commands:
[smith@server rhq-agent]USD unzip jon-plugin-pack-3.3.zip -d /tmp
cp /tmp/jon-plugin-pack-plugin_3.3/*.jar /opt/jon/jon-server-3.3.GA/plugins
[jsmith@server ~]USD agentRoot/rhq-agent/bin/rhq-agent.sh > plugins update
Chapter 2. About the History Database 2.1. History Database Overview Red Hat Virtualization includes a comprehensive management history database, which can be used by reporting applications to generate reports at data center, cluster and host levels. This chapter provides information to enable you to set up queries against the history database. Red Hat Virtualization Manager uses PostgreSQL 10.x as a database platform to store information about the state of the virtualization environment, its configuration and performance. At install time, Red Hat Virtualization Manager creates a PostgreSQL database called engine . Installing the ovirt-engine-dwh package creates a second database called ovirt_engine_history , which contains historical configuration information and statistical metrics collected every minute over time from the engine operational database. Tracking the changes to the database provides information on the objects in the database, enabling the user to analyze activity, enhance performance, and resolve difficulties. Warning The replication of data in the ovirt_engine_history database is performed by the Red Hat Virtualization Manager Extract Transform Load Service, ovirt-engine-dwhd . The service is based on Talend Open Studio, a data integration tool. This service is configured to start automatically during the data warehouse package setup. It is a Java program responsible for extracting data from the engine database, transforming the data to the history database standard and loading it to the ovirt_engine_history database. The ovirt-engine-dwhd service must not be stopped. The ovirt_engine_history database schema changes over time. The database includes a set of database views to provide a supported, versioned API with a consistent structure. A view is a virtual table composed of the result set of a database query. The database stores the definition of a view as a SELECT statement. The result of the SELECT statement populates the virtual table that the view returns. A user references the view name in PL/PGSQL statements the same way a table is referenced.

Commands:
5.269. qpid 5.269.1. RHSA-2012:1269 - Moderate: qpid security, bug fix, and enhancement update Updated qpid packages that fix one security issue, multiple bugs, and add various enhancements are now available for Red Hat Enterprise Linux 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. Apache Qpid is a reliable, cross-platform, asynchronous messaging system that supports the Advanced Message Queuing Protocol (AMQP) in several common programming languages. Security Fix CVE-2012-2145 It was discovered that the Qpid daemon (qpidd) did not allow the number of connections from clients to be restricted. A malicious client could use this flaw to open an excessive amount of connections, preventing other legitimate clients from establishing a connection to qpidd. To address CVE-2012-2145, new qpidd configuration options were introduced: max-negotiate-time defines the time during which initial protocol negotiation must succeed, connection-limit-per-user and connection-limit-per-ip can be used to limit the number of connections per user and client host IP. Refer to the qpidd manual page for additional details. In addition, the qpid-cpp, qpid-qmf, qpid-tools, and python-qpid packages have been upgraded to upstream version 0.14, which provides support for Red Hat Enterprise MRG 2.2, as well as a number of bug fixes and enhancements over the version. (BZ# 840053 , BZ# 840055 , BZ# 840056 , BZ# 840058 ) All users of qpid are advised to upgrade to these updated packages, which fix these issues and add these enhancements.

Commands:
18.4. Routed Mode When using Routed mode , the virtual switch connects to the physical LAN connected to the host physical machine, passing traffic back and forth without the use of NAT. The virtual switch can examine all traffic and use the information contained within the network packets to make routing decisions. When using this mode, all of the virtual machines are in their own subnet, routed through a virtual switch. This situation is not always ideal as no other host physical machines on the physical network are aware of the virtual machines without manual physical router configuration, and cannot access the virtual machines. Routed mode operates at Layer 3 of the OSI networking model. Figure 18.5. Virtual network switch in routed mode

Commands:
21.2. Mounting NFS File Systems Use the mount command to mount a shared NFS directory from another machine: Warning The mount point directory on the local machine ( /misc/local in the above example) must exist before this command can be executed. In this command, shadowman.example.com is the hostname of the NFS file server, /misc/export is the directory that shadowman is exporting, and /misc/local is the location to mount the file system on the local machine. After the mount command runs (and if the client has proper permissions from the shadowman.example.com NFS server) the client user can execute the command ls /misc/local to display a listing of the files in /misc/export on shadowman.example.com . 21.2.1. Mounting NFS File Systems using /etc/fstab An alternate way to mount an NFS share from another machine is to add a line to the /etc/fstab file. The line must state the hostname of the NFS server, the directory on the server being exported, and the directory on the local machine where the NFS share is to be mounted. You must be root to modify the /etc/fstab file. The general syntax for the line in /etc/fstab is as follows: The mount point /pub must exist on the client machine before this command can be executed. After adding this line to /etc/fstab on the client system, type the command mount /pub at a shell prompt, and the mount point /pub is mounted from the server.

Commands:
mount shadowman.example.com:/misc/export /misc/local
server:/usr/local/pub /pub nfs rsize=8192,wsize=8192,timeo=14,intr
Appendix F. Reference Table for ext4 and XFS Commands XFS replaces ext4 as the default file system in Red Hat Enterprise Linux 7. This table serves as a cross reference listing common file system manipulation tasks and any changes in these commands between ext4 and XFS. Table F.1. Reference Table for ext4 and XFS Commands Task ext4 XFS Creating a file system mkfs.ext4 mkfs.xfs Mounting a file system mount mount Resizing a file system resize2fs xfs_growfs [a] Repairing a file system e2fsck xfs_repair Changing the label on a file system e2label xfs_admin -L Reporting on disk space and file usage quota quota Debugging a file system debugfs xfs_db Saving critical file system metadata to a file e2image xfs_metadump [a] The size of XFS file systems cannot be reduced; the command is used only to increase the size.

Commands:
Chapter 4. Flavors for instances An instance flavor is a resource template that specifies the virtual hardware profile for the instance. You select a flavor when you launch instances to specify the virtual resources to allocate to the instance. Flavors define the number of virtual CPUs, the amount of RAM, the size of the root disk, and the size of the virtual storage, including secondary ephemeral storage and swap disk, to create the instance with. You select the flavor from the set of available flavors defined for your project within the cloud.

Commands:
Chapter 18. scheduler 18.1. scheduler:list 18.1.1. Description List scheduled jobs 18.1.2. Syntax scheduler:list [options] 18.1.3. Options Name Description --help Display this help message 18.2. scheduler:reschedule 18.2.1. Description Update scheduling of an existing job 18.2.2. Syntax scheduler:reschedule [options] name 18.2.3. Arguments Name Description name The job name 18.2.4. Options Name Description --help Display this help message --period Time during executions (in seconds) --at Absolute date in ISO format (ex: 2014-05-13T13:56:45) --times Number of times this job should be executed --concurrent Should jobs run concurrently or not (defaults to false) --cron The cron expression 18.3. scheduler:schedule 18.3.1. Description Schedule a script execution 18.3.2. Syntax scheduler:schedule [options] script 18.3.3. Arguments Name Description script The script to schedule 18.3.4. Options Name Description --help Display this help message --period Time during executions (in seconds) --at Absolute date in ISO format (ex: 2014-05-13T13:56:45) --times Number of times this job should be executed --name Name of this job --concurrent Should jobs run concurrently or not (defaults to false) --cron The cron expression 18.4. scheduler:trigger 18.4.1. Description Manually trigger a scheduled job 18.4.2. Syntax scheduler:trigger [options] name 18.4.3. Arguments Name Description name Name of the job to trigger 18.4.4. Options Name Description --help Display this help message -b, background schedule the trigger in the background 18.5. scheduler:unschedule 18.5.1. Description Unschedule a job 18.5.2. Syntax scheduler:unschedule [options] [name] 18.5.3. Arguments Name Description name 18.5.4. Options Name Description --help Display this help message

Commands:
Chapter 6. Container Images Based on Red Hat Software Collections 3.5 Component Description Supported architectures Application Images rhscl/python-38-rhel7 Python 3.8 platform for building and running applications x86_64, s390x, ppc64le Daemon Images rhscl/varnish-6-rhel7 Varnish Cache 6.0 HTTP reverse proxy x86_64, s390x, ppc64le Red Hat Developer Toolset Red Hat Developer Toolset Images rhscl/devtoolset-9-toolchain-rhel7 Red Hat Developer Toolset toolchain (EOL) x86_64, s390x, ppc64le rhscl/devtoolset-9-perftools-rhel7 Red Hat Developer Toolset perftools (EOL) x86_64, s390x, ppc64le Legend: x86_64 - AMD64 and Intel 64 architectures s390x - 64-bit IBM Z ppc64le - IBM POWER, little endian All images are based on components from Red Hat Software Collections. The images are available for Red Hat Enterprise Linux 7 through the Red Hat Container Registry. For detailed information about components provided by Red Hat Software Collections 3.5, see the Red Hat Software Collections 3.5 Release Notes . For more information about the Red Hat Developer Toolset 9.1 components, see the Red Hat Developer Toolset 9 User Guide . For information regarding container images based on Red Hat Software Collections 2, see Using Red Hat Software Collections 2 Container Images . EOL images are no longer supported.

Commands:
Chapter 1. Red Hat build of OpenJDK applications in containers Red Hat build of OpenJDK images have default startup scripts that automatically detect application JAR files and launch Java. The script's behavior can be customized using environment variables. For more information, see /help.md in the container. The Red Hat build of OpenJDK applications in the /deployments directory of the Red Hat build of OpenJDK image are run when the image loads. Note Containers that contain Red Hat build of OpenJDK applications are not automatically updated with security updates. Ensure that you update these images at least once every three months. Application JAR files can be fat JARs or thin JARs. Fat JARs contain all of the application's dependencies. Thin JARs reference other JARs that contain some, or all, of the application's dependencies. Thin JARs are only supported if: They have a flat classpath. All dependencies are JARs that are in the /deployments directory.

Commands:
Chapter 48. Getting started with DPDK The data plane development kit (DPDK) provides libraries and network drivers to accelerate packet processing in user space. Administrators use DPDK, for example, in virtual machines to use Single Root I/O Virtualization (SR-IOV) to reduce latencies and increase I/O throughput. Note Red Hat does not support experimental DPDK APIs. 48.1. Installing the dpdk package To use DPDK, install the dpdk package. Procedure Use the dnf utility to install the dpdk package: 48.2. Additional resources Network Adapter Fast Datapath Feature Support Matrix

Commands:
dnf install dpdk
7.31. cpuspeed 7.31.1. RHBA-2013:0490 - cpuspeed bug fix update Updated cpuspeed packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cpuspeed packages contain a daemon that dynamically changes speed of processors depending upon their current workload. This package also supports enabling CPU frequency scaling via in-kernel CPUfreq governors on Intel Centrino and AMD Athlon64/Opteron platforms. Bug Fix BZ#876738 Previously, the cpuspeed daemon used a naive method of getting the highest available scaling frequency. Consequently, on certain platforms, cpuspeed did not set the CPU to the correct maximum limit. A patch has been provided to address this issue and cpuspeed now sets the maximum speed correctly. Users of cpuspeed are advised to upgrade to these updated packages, which fix this bug. 7.31.2. RHBA-2012:1404 - cpuspeed bug fix update Updated cpuspeed packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The cpuspeed packages provide a daemon to manage the CPU frequency scaling. Bug Fixes BZ#642838 Prior to this update, the PCC driver used the "userspace" governor was loaded instead of the "ondemand" governor when loading. This update modifies the init script to also check the PCC driver. BZ# 738463 Prior to this update, the cpuspeed init script tried to set cpufrequency system files on a per core basis which was a deprecated procedure. This update sets thresholds globally. BZ# 616976 Prior to this update, the cpuspeed tool did not reset MIN and MAX values, when the configuration file was emptied. As a consequence, the MIN_SPEED or MAX_SPEED values were not reset as expected. This update adds conditionals in the init script to check these values. Now, the MIN_SPEED or MAX_SPEED values are reset as expected. BZ#797055 Prior to this update, the init script did not handle the IGNORE_NICE parameter as expected. As a consequence, "-n" was added to command options when the IGNORE_NICE parameter was set. This update modifies the init script to stop adding the NICE option when using the IGNORE_NICE parameter. All users of cpuspeed are advised to upgrade to these updated packages, which fix these bugs. 7.31.3. RHBA-2013:1153 - cpuspeed bug fix update Updated cpuspeed packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cpuspeed packages provide a daemon to manage the CPU frequency scaling. Bug Fix BZ# 990474 The cpuspeed init script relied on the presence of the scaling_available_frequencies sysfs file to get the maximum possible scaling frequency for the system. Certain platforms did not provide the scaling_available_frequencies sysfs file, which caused the attempt to set the maximum scaling frequency to fail. With this update, the init script now reads the frequency from cpuinfo_max_speed, and setting the maximum scaling frequency now works on all platforms. Users of cpuspeed are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 9. File Systems SMB 2 and SMB 3 now support DFS Distributed File System (DFS), which was previously supported only with the Server Message Block (SMB) protocol version 1, is now also supported in SMB 2 and SMB 3. With this update, you can now mount DFS shares using the SMB 2 and SMB 3 protocols. (BZ#1481303) File system DAX now performs better when mapping a large amount of memory Prior to this enhancement, the Direct Access (DAX) feature mapped only 4KiB entries into application address space. This had a negative performance impact on workloads that mapped large amounts of memory, because it increased Translation Lookaside Buffer (TLB) pressure. With this update, the kernel supports 2MiB Page Middle Directory (PMD) faults in persistent memory mappings. This significantly reduces TLB pressure, and file system DAX now performs better when mapping a large amount of memory. (BZ#1457572) quotacheck is now faster on ext4 The quotacheck utility now directly scans ext4 file system metadata instead of analyzing each individual file for occupied disk size. If the file system contains many files, quota initialization and quota check are now significantly faster. (BZ#1393849) The CephFS kernel client is fully supported with Red Hat Ceph Storage 3 The Ceph File System (CephFS) kernel module enables Red Hat Enterprise Linux nodes to mount Ceph File Systems from Red Hat Ceph Storage clusters. The kernel client in Red Hat Enterprise Linux is a more efficient alternative to the Filesystem in Userspace (FUSE) client included with Red Hat Ceph Storage. Note that the kernel client currently lacks support for CephFS quotas. The CephFS kernel client was introduced in Red Hat Enterprise Linux 7.3 as a Technology Preview, and since the release of Red Hat Ceph Storage 3, CephFS is fully supported. For more information, see the Ceph File System Guide for Red Hat Ceph Storage 3: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/ceph_file_system_guide/ . (BZ#1626526)

Commands:
Chapter 8. Advanced Guest Virtual Machine Administration This chapter covers advanced administration tools for fine tuning and controlling system resources as they are made available to guest virtual machines. 8.1. Control Groups (cgroups) Red Hat Enterprise Linux 6 provides a new kernel feature: control groups , which are often referred to as cgroups . Cgroups allow you to allocate resources such as CPU time, system memory, network bandwidth, or a combination of these resources among user-defined groups of tasks (processes) running on a system. You can monitor the cgroups you configure, deny cgroups access to certain resources, and even reconfigure your cgroups dynamically on a running system. The cgroup functionality is fully supported by libvirt . By default, libvirt puts each guest into a separate control group for various controllers (such as memory, cpu, blkio, device). When a guest is started, it is already in a cgroup. The only configuration that may be required is the setting of policies on the cgroups. Refer to the Red Hat Enterprise Linux Resource Management Guide for more information on cgroups.

Commands:
Chapter 6. Uninstalling a cluster on Nutanix You can remove a cluster that you deployed to Nutanix. 6.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with User Provisioned Infrastructure (UPI) clusters. There might be resources that the installer did not create or that the installer is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure From the directory that contains the installation program on the computer that you used to install the cluster, run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
Chapter 10. Viewing and managing Quartz Schedules Quartz ( http://www.quartz-scheduler.org/ ) is a richly featured, open source job scheduling library that you can integrate within most Java applications. You can use Quartz to create simple or complex schedules for executing jobs. A job is defined as a standard Java component that can execute virtually anything that you program it to do. The Fuse Console shows the Quartz tab if your Camel route deploys the camel-quartz2 component. Note that you can alternately access Quartz mbeans through the JMX tree view. Procedure In the Fuse Console, click the Quartz tab. The Quartz page includes a treeview of the Quartz Schedulers and Scheduler , Triggers , and Jobs tabs. To pause or start a scheduler, click the buttons on the Scheduler tab. Click the Triggers tab to view the triggers that determine when jobs will run. For example, a trigger can specify to start a job at a certain time of day (to the millisecond), on specified days, or repeated a specified number of times or at specific times. To filter the list of triggers select State , Group , Name , or Type from the drop-down list. You can then further filter the list by selecting or typing in the fill-on field. To pause, resume, update, or manually fire a trigger, click the options in the Action column. Click the Jobs tab to view the list of running jobs. You can sort the list by the columns in the table: Group , Name , Durable , Recover , Job ClassName , and Description .

Commands: