mtpti5iD/redhat-docs_dataset huggingface dataset:
A.6. Logging Performance Data (using pmlogger) PCP allows you to log performance metric values which can replayed at a later date by creating archived logs of selected metrics on the system through the pmlogger tool. These metric archives may be played back at a later date to give retrospective performance analysis. The pmlogger tool provides flexibility and control over the logged metrics by allowing you to specify which metrics are recorded on the system and at what frequency. By default, the configuration file for pmlogger is stored at /var/lib/pcp/config/pmlogger/config.default ; the configuration file outlines which metrics are logged by the primary logging instance. In order for pmlogger to log metric values on the local machine, a primary logging instance must be started. You can use systemctl to ensure that pmlogger is started as a service when the machine starts. The following example shows an extract of a pmlogger configuration file which enables the recording of GFS2 performance metrics. This extract shows that pmlogger will log the performance metric values for the PCP GFS2 latency metrics every 10 seconds, the top 10 worst glock metric every 30 seconds, the tracepoint data every minute, and it will log the data from the glock , glstats and sbstats metrics every 10 minutes. Note PCP comes with a default set of metrics which it will log on the host when pmlogger is enabled. However, no logging of GFS2 metrics occur with this default configuration. After recording metric data, you have multiple options when it comes to the replaying of PCP log archives on the system. You can export the logs to text files and import them into spreadsheets, or you can replay them in the PCP-GUI application using graphs to visualize the retrospective data alongside live data of the system. One of the tools available in PCP for viewing the log files is pmdumptext . This tool allows the user to parse the selected PCP log archive and export the values into an ASCII table. pmdumptext can be used to dump the entire archive log or only select metric values from the log by specifying individual metrics through the command line. For more information on using pmdumptext , see the pmdumptext (1) man page.

Commands:
It is safe to make additions from here on # log mandatory on every 5 seconds { gfs2.latency.grant gfs2.latency.queue gfs2.latency.demote gfs2.glocks } log mandatory on every 10 seconds { gfs2.worst_glock } log mandatory on every 30 seconds { gfs2.tracepoints } log mandatory on every 5 minutes { gfs2.glstats gfs2.sbstats } [access] disallow * : all; allow localhost : enquire;
7.208. redhat-lsb 7.208.1. RHBA-2013:0448 - redhat-lsb bug fix and enhancement update Updated redhat-lsb packages that fix several bugs and add an enhancement are now available for Red Hat Enterprise Linux 6. Linux Standards Base (LSB) provides a set of standards that increases compatibility among Linux distributions. The redhat-lsb packages provide utilities needed for LSB compliant applications. It also contains requirements that ensure that all components required by LSB are installed on the system. Bug Fixes BZ#709016 Previously, the redhat-lsb-core subpackage was missing from the redhat-lsb packages. Consequently, a large number of unnecessary dependencies was pulled in when redhat-lsb was required. This update provides redhat-lsb-core, which has minimal requirements, thus preventing this bug. BZ# 844602 An inaccurate brand name was used in the redhat-lsb package description. This update fixes the description. BZ# 833058 Previously, the /etc/lsb-release file specified in the lsb_release man page was missing from the redhat-lsb packages. This update adds this file, which provides information about LSB modules installed on the system. Enhancement BZ#801158 It is now possible to install LBS subpackages, such as redhat-lsb-core, redhat-lsb-c++, redhat-lsb-graphics, or redhat-lsb-printing, separately without having to install the redhat-lsb package with all dependencies that might be unnecessary on a system. Users of redhat-lsb are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
12.10. Actions 12.10.1. Importing an Existing Storage Domain Note The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disk images, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains. The API provides a user with the ability to remove an ISO or Export storage domain from one Red Hat Virtualization Manager instance without re-formatting the underlying storage and import it into another instance. Importing is achieved similarly to adding a new storage domain, except the name is not specified. Example 12.16. Importing an existing export storage domain 12.10.2. Deleting a Storage Domain A storage_domain reference is passed in the body of a DELETE request for a storage domain. The storage_domain reference is in the following form: OR Format Storage Domain An API user provides a optional format element to specify whether or not to format the storage domain after deletion. Example 12.17. Formatting a storage domain after deletion If no format element is passed, the storage domain remains unformatted. Logical Removal of Storage Domain The API also provides a function for the logical removal of the storage domain. This retains the storage domain's data for import. Use the destroy element to logically remove the storage domain and retain the data. Example 12.18. Logical removal of a storage domain 12.10.3. Refreshing the LUN Size Users can refresh the LUN size after increasing the size of the underlying LUN on the storage server. The refreshluns action forces a rescan of the provided LUNs and updates the database with the new size if required. Example 12.19. Refreshing the LUN Size

Commands:
POST /ovirt-engine/api/storagedomains HTTP/1.1 Accept: application/xml Content-Type: application/xml <storage_domain> <type>export</type> <storage> <type>nfs</type> <address>172.31.0.6</address> <path>/exports/RHEVX/export-domain</path> </storage> <host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"/> </storage_domain> HTTP/1.1 201 Created Content-Type: application/xml <storage_domain id="fabe0451-701f-4235-8f7e-e20e458819ed" href="/ovirt-engine/api/storagedomains/fabe0451-701f-4235-8f7e-e20e458819ed"> <name>export1</name> </storage_domain>
<storage_domain> <host id="..."/> </storage_domain>
<storage_domain> <host> <name>...</name> </host> </storage_domain>
<storage_domain> <host id="..."/> <format>true</format> </storage_domain>
<storage_domain> <host id="..."/> <destroy>true</destroy> </storage_domain>
POST /ovirt-engine/api/storagedomains/262b056b-aede-40f1-9666-b883eff59d40/refreshluns HTTP/1.1 Accept: application/xml Content-type: application/xml <action> <logical_units> <logical_unit id="1IET_00010001"/> <logical_unit id="1IET_00010002"/> </logical_units> </action>
B.49. logwatch B.49.1. RHSA-2011:0324 - Important: logwatch security update An updated logwatch package that fixes one security issue is now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. Logwatch is a customizable log analysis system. Logwatch parses through your system's logs for a given period of time and creates a report analyzing areas that you specify, in as much detail as you require. CVE-2011-1018 A flaw was found in the way Logwatch processed log files. If an attacker were able to create a log file with a malicious file name, it could result in arbitrary code execution with the privileges of the root user when that log file is analyzed by Logwatch. Users of logwatch should upgrade to this updated package, which contains a backported patch to resolve this issue.

Commands:
4.4. Logical Volume Backup Metadata backups and archives are automatically created on every volume group and logical volume configuration change unless disabled in the lvm.conf file. By default, the metadata backup is stored in the /etc/lvm/backup file and the metadata archives are stored in the /etc/lvm/archive file. How long the metadata archives stored in the /etc/lvm/archive file are kept and how many archive files are kept is determined by parameters you can set in the lvm.conf file. A daily system backup should include the contents of the /etc/lvm directory in the backup. Note that a metadata backup does not back up the user and system data contained in the logical volumes. You can manually back up the metadata to the /etc/lvm/backup file with the vgcfgbackup command. You can restore metadata with the vgcfgrestore command. The vgcfgbackup and vgcfgrestore commands are described in Section 5.3.13, "Backing Up Volume Group Metadata" .

Commands:
Installation overview OpenShift Container Platform 4.13 Overview content for installing OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
oc get nodes
NAME STATUS ROLES AGE VERSION example-compute1.example.com Ready worker 13m v1.21.6+bb8d50a example-compute2.example.com Ready worker 13m v1.21.6+bb8d50a example-compute4.example.com Ready worker 14m v1.21.6+bb8d50a example-control1.example.com Ready master 52m v1.21.6+bb8d50a example-control2.example.com Ready master 55m v1.21.6+bb8d50a example-control3.example.com Ready master 55m v1.21.6+bb8d50a
oc get machines -A
NAMESPACE NAME PHASE TYPE REGION ZONE AGE openshift-machine-api example-zbbt6-master-0 Running 95m openshift-machine-api example-zbbt6-master-1 Running 95m openshift-machine-api example-zbbt6-master-2 Running 95m openshift-machine-api example-zbbt6-worker-0-25bhp Running 49m openshift-machine-api example-zbbt6-worker-0-8b4c2 Running 49m openshift-machine-api example-zbbt6-worker-0-jkbqt Running 49m openshift-machine-api example-zbbt6-worker-0-qrl5b Running 49m
capabilities: baselineCapabilitySet: v4.11 1 additionalEnabledCapabilities: 2 - CSISnapshot - Console - Storage
Chapter 66. request This chapter describes the commands under the request command. 66.1. request token authorize Authorize a request token Usage: Table 66.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 66.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 to show multiple columns Table 66.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 66.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 66.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. 66.2. request token create Create a request token Usage: Table 66.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 66.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 to show multiple columns Table 66.8. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 66.9. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 66.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>]
Chapter 42. Milestones Milestones are a special service task that can be configured in the case definition designer by adding the milestone node to the process designer palette. When creating a new case definition, a milestone configured as AdHoc Autostart is included on the design palette by default. Newly created milestones are not set to AdHoc Autostart by default. Case management milestones generally occur at the end of a stage, but they can also be the result of achieving other milestones. A milestone always requires a condition to be defined in order to track progress. Milestones react to case file data when data is added to a case. A milestone represents a single point of achievement within the case instance. It can be used to flag certain events, which can be useful for Key Performance Indicator (KPI) tracking or identifying the tasks that are still to be completed. Milestones can be in any of the following states during case execution: Active : The condition has been defined on the milestone but it has not been met. Completed : The milestone condition has been met, the milestone has been achieved, and the case can proceed to the task. Terminated : The milestone is no longer a part of the case process and is no longer required. While a milestone is available or completed it can be triggered manually by a signal or automatically if AdHoc Autostart is configured when a case instance starts. Milestones can be triggered as many times as required, however, it is directly achieved when the condition is met. 42.1. Configuring and triggering milestones Case milestones can be configured to start automatically when a case instance starts or they can triggered using a signal, which is configured manually during the case design. Prerequisites A case project has been created in Business Central. A case definition has been created. Procedure From the predefined node panel located on the left side of the diagram editor, drag and drop a Milestone object onto the palette. With the milestone selected, click to open the Properties panel on the right side of the designer. Expand Data Assignments to add a completion condition. Milestones include a Condition parameter by default. To define the completion condition for the milestone, select Constant from the Source list. The condition must be provided using the Drools syntax. Expand Implementation/Execution to configure the AdHoc Autostart property. Click the check box to set this property to true for milestones that are required to start automatically when a case instance starts. Leave the check box empty to set this property to false for milestones that are to be triggered by a signal event. Optional: Configure a signal event to trigger a milestone once a case goal has been reached. With the signal event selected in the case design palette, open the Properties panel on the right. Set the Signal Scope property to Process Instance . Open the SignalRef expression editor and type the name of the milestone to be triggered. Click Save .

Commands:
2.2. On-premises Architecture Red Hat Gluster Storage for On-premises enables enterprises to treat physical storage as a virtualized, scalable, and centrally managed storage pool by using commodity storage hardware. It supports multi-tenancy by partitioning users or groups into logical volumes on shared storage. It enables users to eliminate, decrease, or manage their dependence on high-cost, monolithic and difficult-to-deploy storage arrays. You can add capacity in a matter of minutes across a wide variety of workloads without affecting performance. Storage can also be centrally managed across a variety of workloads, thus increasing storage efficiency. Figure 2.2. Red Hat Gluster Storage for On-premises Architecture Red Hat Gluster Storage for On-premises is based on glusterFS, an open source distributed file system with a modular, stackable design, and a unique no-metadata server architecture. This no-metadata server architecture ensures better performance, linear scalability, and reliability.

Commands:
Chapter 7. Run Red Hat JBoss Data Grid in Remote Client-Server Mode 7.1. Prerequisites The following is a list of prerequisites to run Red Hat JBoss Data Grid in Remote Client-Server mode for the first time: Ensure an appropriate version of OpenJDK is installed. For more information, see Section 2.3, "Install OpenJDK on Red Hat Enterprise Linux" Download and install the latest version of JBoss Data Grid. For more information, see Section 2.4.1, "Download Red Hat JBoss Data Grid" Report a bug

Commands:
Chapter 14. The kie-camel component The kie-camel component is an Apache Camel endpoint provided by Red Hat Fuse that integrates Fuse with Red Hat Decision Manager. It enables you to specify a Red Hat Decision Manager module by using a Maven group ID, artifact ID, and version (GAV) identifier which you can pull into the route and execute. It also enables you to specify portions of the message body as facts. You can use the kie-camel component with embedded engines or with KIE Server. Embedded engines In this scenario, KIE engines run in the same container as the Fuse integration project and you can communicate with engines using KIE commands. To create the Camel producer, use the following URI: For example, enter the following command to initialize a Camel route in Spring: KIE Server In this scenario, the kie-camel component connects to KIE Server using the KIE Server REST API. This enables users to communicate with KIE Server using the KIE Server API. To create a producer, use the following URI: For example, enter the following command to initialize a Camel route in Spring: The message has the following headers: Table 14.1. Message headers and descriptions Header Description CamelKieClient KIE Server client (mandatory) CamelKieOperation KIE Server client (mandatory) CamelKieParameterName The value of the client method parameter (optional) CamelKieBodyParam The method parameter where the message body is stored (optional)

Commands:
kie-local:kie-session-name?action=execute
<from uri="direct:runCommand" /> <to uri="kie-local:kie-session1?action=execute"/>
kie:http://username:password@kie-server-url`
<from uri="direct:runCommand" /> <to uri="kie:http://user:psswd@localhost:8080/kie-server-services/services/rest/server"/>
4.269. rgmanager 4.269.1. RHBA-2011:1595 - rgmanager bug fix and enhancement update An updated rgmanager package that fixes various bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The rgmanager package contains the Red Hat Resource Group Manager, which provides the ability to create and manage high-availability server applications in the event of system downtime. The rgmanager package has been upgraded to upstream version 3.0.12.1, which provides a number of bug fixes and enhancements over the version. Note that this update requires the resource-agents package in version 3.9.2 or later. (BZ# 707118 ) Bug Fixes BZ# 673167 When handling failed services, the "clusvcadm -d" command now operates consistently. BZ# 690191 Exclusive prioritization now operates on service failures instead of only on node failures. BZ# 692895 The rgmanager service no longer terminates unexpectedly with a segmentation fault when a resource agent provides invalid or corrupted metadata. BZ# 709398 Reference count handling of resources with multiple instances has been corrected. BZ# 716231 An error in handling of independent subtree failures, which caused more resources to be disabled than necessary, has been fixed. BZ# 697446 , BZ# 741607 The rgmanager service no longer terminates unexpectedly on startup/shutdown or during service relocation. Enhancement BZ# 723925 The rgmanager service can now be disabled in the cluster.conf configuration file. All users of rgmanager are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
21.2. Tuning Considerations This section describes several factors to consider when configuring settings that may affect SSD performance. I/O Scheduler Any I/O scheduler should perform well with most SSDs. However, as with any other storage type, Red Hat recommends benchmarking to determine the optimal configuration for a given workload. When using SSDs, Red Hat advises changing the I/O scheduler only for benchmarking particular workloads. For more information about the different types of I/O schedulers, refer to the I/O Tuning Guide (also provided by Red Hat). The following kernel document also contains instructions on how to switch between I/O schedulers: /usr/share/doc/kernel- version /Documentation/block/switching-sched.txt Virtual Memory Like the I/O scheduler, virtual memory (VM) subsystem requires no special tuning. Given the fast nature of I/O on SSD, it should be possible to turn down the vm_dirty_background_ratio and vm_dirty_ratio settings, as increased write-out activity should not negatively impact the latency of other operations on the disk. However, this can generate more overall I/O and so is not generally recommended without workload-specific testing. Swap An SSD can also be used as a swap device, and is likely to produce good page-out/page-in performance.

Commands: