mtpti5iD/redhat-docs_dataset huggingface dataset:
2.4. Installing Red Hat Gluster Storage Server on Red Hat Enterprise Linux (Layered Install) Layered install involves installing Red Hat Gluster Storage over Red Hat Enterprise Linux. For more information regarding supported Red Hat Enterprise Linux version for a particular Red Hat Gluster Storage release, see Section 1.7, "Red Hat Gluster Storage Support Matrix" . Important Virtual Data Optimizer (VDO) volumes, which are supported in Red Hat Enterprise Linux 7.5, are not currently supported in Red Hat Gluster Storage. VDO is supported only when used as part of Red Hat Hyperconverged Infrastructure for Virtualization 2.0. See Understanding VDO for more information. Important It is recommended to create a separate /var partition that is large enough (50GB - 100GB) for log files, geo-replication related miscellaneous files, and other files. Perform a base install of Red Hat Enterprise Linux Server Red Hat Gluster Storage is supported on Red Hat Enterprise Linux 7 (RHEL 7) and Red Hat Enterprise Linux 8 (RHEL 8). We highly recommend you to choose the latest RHEL versions. Important Red Hat Gluster Storage is not supported on Red Hat Enterprise Linux 6 (RHEL 6) from 3.5 Batch Update 1 onwards. See, Table 1.3, "Version Details" Register the System with Subscription Manager To register the system with subscription manager, refer Section 2.3, "Subscribing to the Red Hat Gluster Storage Server Channels" Kernel Version Requirement Red Hat Gluster Storage requires the kernel-2.6.32-431.17.1.el6 version or higher to be used on the system. Verify the installed and running kernel versions by running the following command: Update all packages Ensure that all packages are up to date by running the following command. Important If any kernel packages are updated, reboot the system with the following command. Install Red Hat Gluster Storage Run the following command to install Red Hat Gluster Storage: To install Samba, see Chapter 3, Deploying Samba on Red Hat Gluster Storage To install NFS-Ganesha, see Chapter 4, Deploying NFS-Ganesha on Red Hat Gluster Storage Reboot Reboot the system.

Commands:
rpm -q kernel kernel-2.6.32-431.el6.x86_64 kernel-2.6.32-431.17.1.el6.x86_64
uname -r 2.6.32-431.17.1.el6.x86_64
yum update
shutdown -r now
yum install redhat-storage-server
22.16.2. Configure Rate Limiting Access to an NTP Service To enable rate limiting access to the NTP service running on a system, add the limited option to the restrict command as explained in Section 22.16.1, "Configure Access Control to an NTP Service" . If you do not want to use the default discard parameters, then also use the discard command as explained here. The discard command takes the following form: discard [ average value ] [ minimum value ] [ monitor value ] average - specifies the minimum average packet spacing to be permitted, it accepts an argument in log 2 seconds. The default value is 3 ( 2 3 equates to 8 seconds). minimum - specifies the minimum packet spacing to be permitted, it accepts an argument in log 2 seconds. The default value is 1 ( 2 1 equates to 2 seconds). monitor - specifies the discard probability for packets once the permitted rate limits have been exceeded. The default value is 3000 seconds. This option is intended for servers that receive 1000 or more requests per second. Examples of the discard command are as follows: discard average 4 discard average 4 minimum 2

Commands:
5.3. Displaying Device-Specific Fencing Options Use the following command to view the options for the specified STONITH agent. For example, the following command displays the options for the fence agent for APC over telnet/SSH. Warning For fence agents that provide a method option, a value of cycle is unsupported and should not be specified, as it may cause data corruption.

Commands:
pcs stonith describe stonith_agent
pcs stonith describe fence_apc Stonith options for: fence_apc ipaddr (required): IP Address or Hostname login (required): Login Name passwd: Login password or passphrase passwd_script: Script to retrieve password cmd_prompt: Force command prompt secure: SSH connection port (required): Physical plug number or name of virtual machine identity_file: Identity file for ssh switch: Physical switch number on device inet4_only: Forces agent to use IPv4 addresses only inet6_only: Forces agent to use IPv6 addresses only ipport: TCP port to use for connection with device action (required): Fencing Action verbose: Verbose mode debug: Write debug information to given file version: Display version information and exit help: Display help and exit separator: Separator for CSV created by operation list power_timeout: Test X seconds for status change after ON/OFF shell_timeout: Wait X seconds for cmd prompt after issuing command login_timeout: Wait X seconds for cmd prompt after login power_wait: Wait X seconds after issuing ON/OFF delay: Wait X seconds before fencing is started retry_on: Count of attempts to retry power on
Power Monitoring OpenShift Container Platform 4.17 Configuring and using power monitoring for OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: port: 9103 1 nodeSelector: kubernetes.io/os: linux 2 Tolerations: 3 - key: "" operator: "Exists" value: "" effect: ""
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler status: exporter: conditions: 1 - lastTransitionTime: '2024-01-11T11:07:39Z' message: Reconcile succeeded observedGeneration: 1 reason: ReconcileSuccess status: 'True' type: Reconciled - lastTransitionTime: '2024-01-11T11:07:39Z' message: >- Kepler daemonset "kepler-operator/kepler" is deployed to all nodes and available; ready 2/2 observedGeneration: 1 reason: DaemonSetReady status: 'True' type: Available currentNumberScheduled: 2 2 desiredNumberScheduled: 2 3
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: redfish: secretRef: <secret_name> required 1 probeInterval: 60s 2 skipSSLVerify: false 3
<your_kubelet_node_name>,<redfish_username>,<redfish_password>,https://<redfish_ip_or_hostname>/
control-plane,exampleuser,examplepass,https://redfish.nodes.example.com worker-1,exampleuser,examplepass,https://redfish.nodes.example.com worker-2,exampleuser,examplepass,https://another.redfish.nodes.example.com
oc -n openshift-power-monitoring create secret generic redfish-secret --from-file=redfish.csv
apiVersion: v1 kind: Secret metadata: name: redfish-secret data: redfish.csv: YmFyCg== #
function::sprint_syms Name function::sprint_syms - Return stack for kernel addresses from string Synopsis Arguments callers String with list of hexadecimal (kernel) addresses Description Perform a symbolic lookup of the addresses in the given string, which are assumed to be the result of a prior calls to stack , callers , and similar functions. Returns a simple backtrace from the given hex string. One line per address. Includes the symbol name (or hex address if symbol couldn't be resolved) and module name (if found), as obtained from symdata . Includes the offset from the start of the function if found, otherwise the offset will be added to the module (if found, between brackets). Returns the backtrace as string (each line terminated by a newline character). Note that the returned stack will be truncated to MAXSTRINGLEN, to print fuller and richer stacks use print_syms .

Commands:
sprint_syms(callers:string)
6.2. Order Constraints Order constraints determine the order in which the resources run. You can configure an order constraint to determine the order in which resources start and stop. Use the following command to configure an order constraint. Table 6.2, "Properties of an Order Constraint" . summarizes the properties and options for configuring order constraints. Table 6.2. Properties of an Order Constraint Field Description resource_id The name of a resource on which an action is performed. action The action to perform on a resource. Possible values of the action property are as follows: * start - Start the resource. * stop - Stop the resource. * promote - Promote the resource from a slave resource to a master resource. * demote - Demote the resource from a master resource to a slave resource. If no action is specified, the default action is start . For information on master and slave resources, see Section 8.2, "Multi-State Resources: Resources That Have Multiple Modes" . kind option How to enforce the constraint. The possible values of the kind option are as follows: * Optional - Only applies if both resources are starting and/or stopping. For information on optional ordering, see Section 6.2.2, "Advisory Ordering" . * Mandatory - Always (default value). If the first resource you specified is stopping or cannot be started, the second resource you specified must be stopped. For information on mandatory ordering, see Section 6.2.1, "Mandatory Ordering" . * Serialize - Ensure that no two stop/start actions occur concurrently for a set of resources. symmetrical options If true, which is the default, stop the resources in the reverse order. Default value: true 6.2.1. Mandatory Ordering A mandatory constraints indicates that the second resource you specify cannot run without the first resource you specify being active. This is the default value of the kind option. Leaving the default value ensures that the second resource you specify will react when the first resource you specify changes state. If the first resource you specified resource was running and is stopped, the second resource you specified will also be stopped (if it is running). If the first resource you specified resource was not running and cannot be started, the second resource you specified will be stopped (if it is running). If the first resource you specified is (re)started while the second resource you specified is running, the second resource you specified will be stopped and restarted.

Commands:
pcs constraint order [ action ] resource_id then [ action ] resource_id [ options ]
Chapter 3. Reviewing automation execution environments with automation content navigator As a content developer, you can review your automation execution environment with automation content navigator and display the packages and collections included in the automation execution environments. Automation content navigator runs a playbook to extract and display the results. 3.1. Reviewing automation execution environments from automation content navigator You can review your automation execution environments with the automation content navigator text-based user interface. Prerequisites Automation execution environments Procedure Review the automation execution environments included in your automation content navigator configuration. USD ansible-navigator images Type the number of the automation execution environment you want to delve into for more details. You can review the packages and versions of each installed automation execution environment and the Ansible version any included collections. Optional: pass in the automation execution environment that you want to use. This becomes the primary and is the automation execution environment that automation content navigator uses. USD ansible-navigator images --eei registry.example.com/example-enterprise-ee:latest Verification Review the automation execution environment output.

Commands:
ansible-navigator images
ansible-navigator images --eei registry.example.com/example-enterprise-ee:latest
Chapter 2. Admin REST API Red Hat Single Sign-On comes with a fully functional Admin REST API with all features provided by the Admin Console. To invoke the API you need to obtain an access token with the appropriate permissions. The required permissions are described in Server Administration Guide . A token can be obtained by enabling authenticating to your application with Red Hat Single Sign-On; see the Securing Applications and Services Guide . You can also use direct access grant to obtain an access token. For complete documentation see API Documentation . 2.1. Example using CURL Obtain access token for user in the realm master with username admin and password password : curl \ -d "client_id=admin-cli" \ -d "username=admin" \ -d "password=password" \ -d "grant_type=password" \ "http://localhost:8080/auth/realms/master/protocol/openid-connect/token" Note By default this token expires in 1 minute The result will be a JSON document. To invoke the API you need to extract the value of the access_token property. You can then invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the master realm: curl \ -H "Authorization: bearer eyJhbGciOiJSUz..." \ "http://localhost:8080/auth/admin/realms/master"

Commands:
curl -d "client_id=admin-cli" -d "username=admin" -d "password=password" -d "grant_type=password" "http://localhost:8080/auth/realms/master/protocol/openid-connect/token"
curl -H "Authorization: bearer eyJhbGciOiJSUz..." "http://localhost:8080/auth/admin/realms/master"
Appendix H. Using Your Subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Registering Your System for Packages To install RPM packages on Red Hat Enterprise Linux, your system must be registered. If you are using zip or tar files, this step is not required. Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. To learn more see How to Register and Subscribe a System to the Red Hat Customer Portal . Revised on 2021-06-10 08:59:29 UTC

Commands:
4.225. perl-Test-Spelling 4.225.1. RHBA-2011:1093 - perl-Test-Spelling bug fix update An updated perl-Test-Spelling package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-Test-Spelling package allows users to check spelling of a POD file. Bug Fix BZ# 636835 Prior to this update, the perl-Test-Spelling package erroneously required the aspell package instead of the hunspell package at runtime. This update fixes the problem by correcting perl-Test-Spelling's runtime dependencies so that the hunspell package is now required, as expected. All users of perl-Test-Spelling should upgrade to this updated package, which fixes this bug.

Commands:
Chapter 21. Artifact management You can manage artifacts from the Artifacts page in Business Central. The artifact repository is a local Maven repository and there is only one Maven repository for each installation. Business Central recommends using Maven repository solutions like Sonatype NexusTM , Apache ArchivaTM , or JFrog ArtifactoryTM . The Artifacts page lists all the artifacts in the Maven repository. You can upload artifacts to the Maven repository. Note You can only upload JAR, KJAR, and pom.xml files to the Artifacts repository. 21.1. Viewing an artifact You can view all the content of the local maven repository from the Artifacts page. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Open to view the artifact details. Click Ok to go back to the Artifacts page. 21.2. Downloading an artifact You can download and save an artifact from Business Central repository to the local storage of a project. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Download . Browse to the directory where you want to save the artifact. Click Save . 21.3. Uploading an artifact You can upload an artifact from the local storage to a project in Business Central. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Upload . Click Choose File and browse to the directory from where you want to upload the artifact. Click Upload . Note If you are using a non-Maven artifact, first deploy the artifact to the Maven repository using the mvn deploy command and then refresh the artifact list in Business Central.

Commands:
Chapter 5. File Systems Support of Btrfs File System The Btrfs (B-Tree) file system is supported as a Technology Preview in Red Hat Enterprise Linux 7.1. This file system offers advanced management, reliability, and scalability features. It enables users to create snapshots, it enables compression and integrated device management. OverlayFS The OverlayFS file system service allows the user to "overlay" one file system on top of another. Changes are recorded in the upper file system, while the lower file system remains unmodified. This can be useful because it allows multiple users to share a file-system image, for example containers, or when the base image is on read-only media, for example a DVD-ROM. In Red Hat Enterprise Linux 7.1, OverlayFS is supported as a Technology Preview. There are currently two restrictions: It is recommended to use ext4 as the lower file system; the use of xfs and gfs2 file systems is not supported. SELinux is not supported, and to use OverlayFS, it is required to disable enforcing mode. Support of Parallel NFS Parallel NFS (pNFS) is a part of the NFS v4.1 standard that allows clients to access storage devices directly and in parallel. The pNFS architecture can improve the scalability and performance of NFS servers for several common workloads. pNFS defines three different storage protocols or layouts: files, objects, and blocks. The client supports the files layout, and since Red Hat Enterprise Linux 7.1, the blocks and object layouts are fully supported. Red Hat continues to work with partners and open source projects to qualify new pNFS layout types and to provide full support for more layout types in the future. For more information on pNFS, refer to http://www.pnfs.com/ .

Commands:
20.3. Adding a Group from a Directory Service The API adds existing directory service groups to the Red Hat Virtualization Manager database with a POST request to the groups collection. Example 20.2. Adding a group from a directory service

Commands:
POST /ovirt-engine/api/group HTTP/1.1 Content-Type: application/xml Accept: application/xml <group> <name>www.example.com/accounts/groups/mygroup</name> <domain> <name>example.com</name> </domain> </group>
Chapter 1. JFR creation options for Cryostat With Cryostat, you can create a JDK Flight Recorder (JFR) recording that monitors the performance of your JVM in your containerized application. Additionally, you can take a snapshot of an active JFR recording to capture any collected data, up to a specific point in time, for your target JVM application. Cryostat supports all of the following different ways to create JFR recordings: You can use the Cryostat web console to create JFR recordings manually for target JVMs that are using a JMX or agent HTTP connection. The Cryostat server can send on-demand requests over JMX or an agent HTTP connection to start JFR recordings dynamically based on automated rules. The Cryostat agent can start JFR recordings automatically at agent startup based on a given event template as part of the agent harvester feature. From Red Hat build of Cryostat 2.4 onward, the Cryostat agent can start JFR recordings dynamically based on MBean custom triggers and a given event template. The rest of this document describes how to create a JFR recording manually in the Cryostat web console. Additional resources Using automated rules on Cryostat Enabling dynamic JFR recordings based on MBean custom triggers

Commands:
4.5.2. Managing Disk Quotas If quotas are implemented, they need some maintenance - mostly in the form of watching to see if the quotas are exceeded and making sure the quotas are accurate. Of course, if users repeatedly exceed their quotas or consistently reach their soft limits, a system administrator has a few choices to make depending on what type of users they are and how much disk space impacts their work. The administrator can either help the user determine how to use less disk space or increase the user's disk quota. You can create a disk usage report by running the repquota utility. For example, the command repquota /home produces this output: To view the disk usage report for all (option -a ) quota-enabled file systems, use the command: While the report is easy to read, a few points should be explained. The -- displayed after each user is a quick way to determine whether the block limits have been exceeded. If the block soft limit is exceeded, a + appears in place of the first - in the output. The second - indicates the inode limit, but GFS2 file systems do not support inode limits so that character will remain as - . GFS2 file systems do not support a grace period, so the grace column will remain blank. Note that the repquota command is not supported over NFS, irrespective of the underlying file system.

Commands:
*** Report for user quotas on device /dev/mapper/VolGroup00-LogVol02 Block grace time: 7days; Inode grace time: 7days Block limits File limits User used soft hard grace used soft hard grace ---------------------------------------------------------------------- root -- 36 0 0 4 0 0 kristin -- 540 0 0 125 0 0 testuser -- 440400 500000 550000 37418 0 0
repquota -a
5.345. vim 5.345.1. RHBA-2012:0454 - vim bug fix update Updated vim packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. Vim (Vi IMproved) is an updated and improved version of the vi editor. Bug Fixes BZ# 594997 Previously, when using the VimExplorer file manager with the locale set to Simplified Chinese (zh_CN), the netrw.vim script inserted an unwanted "e" character in front of file names. The underlying code has been modified so that file names are now displayed correctly, without unwanted characters. BZ# 634902 The spec file template that was used when new spec files were edited contained outdated information. With this update, the spec file template is updated to adhere to the latest spec file guidelines. BZ# 652610 When using the file explorer in a subdirectory of the root directory, the "vim .." command displayed only part of the root directory's content. A patch has been applied to address this issue, and the "vim .." command now lists the content of the root directory properly in the described scenario. BZ# 663753 Due to a typographic error in the filetype plug-in, the vim utility could display the httpd configuration files with incorrect syntax highlighting. This update corrects the errors in the filetype plug-in, and the httpd configuration files are now displayed with the correct syntax highlighting. All users of vim are advised to upgrade to these updated packages, which fix these bugs.

Commands: