mtpti5iD/redhat-docs_dataset huggingface dataset:
6.2. Analysis Successfully tuning storage stack performance requires an understanding of how data flows through the system, as well as intimate knowledge of the underlying storage and how it performs under varying workloads. It also requires an understanding of the actual workload being tuned. Whenever you deploy a new system, it is a good idea to profile the storage from the bottom up. Start with the raw LUNs or disks, and evaluate their performance using direct I/O (I/O which bypasses the kernel's page cache). This is the most basic test you can perform, and will be the standard by which you measure I/O performance in the stack. Start with a basic workload generator (such as aio-stress ) that produces sequential and random reads and writes across a variety of I/O sizes and queue depths. Following is a graph from a series of aio-stress runs, each of which performs four stages: sequential write, sequential read, random write and random read. In this example, the tool is configured to run across a range of record sizes (the x axis) and queue depths (one per graph). The queue depth represents the total number of I/O operations in progress at a given time. The y-axis shows the bandwidth in megabytes per second. The x-axis shows the I/O Size in kilobytes. Figure 6.1. aio-stress output for 1 thread, 1 file Notice how the throughput line trends from the lower left corner to the upper right. Also note that, for a given record size, you can get more throughput from the storage by increasing the number of I/Os in progress. By running these simple workloads against your storage, you will gain an understanding of how your storage performs under load. Retain the data generated by these tests for comparison when analyzing more complex workloads. If you will be using device mapper or md, add that layer in and repeat your tests. If there is a large loss in performance, ensure that it is expected, or can be explained. For example, a performance drop may be expected if a checksumming raid layer has been added to the stack. Unexpected performance drops can be caused by misaligned I/O operations. By default, Red Hat Enterprise Linux aligns partitions and device mapper metadata optimally. However, not all types of storage report their optimal alignment, and so may require manual tuning. After adding the device mapper or md layer, add a file system on top of the block device and test against that, still using direct I/O. Again, compare results to the prior tests and ensure that you understand any discrepancies. Direct-write I/O typically performs better on pre-allocated files, so ensure that you pre-allocate files before testing for performance. Synthetic workload generators that you may find useful include: aio-stress iozone fio

Commands:
Chapter 2. Launching a JBoss EAP instance The following procedures show launching a public JBoss EAP instance from the Amazon Web Services (AWS) marketplace and launching a JBoss EAP instance on Amazon EC2 Console. 2.1. Launching a JBoss EAP Instance from the AWS marketplace The public JBoss EAP Amazon Machine Image (AMI), offered with the pay-as-you-go (PAYG) model, is available at the Amazon Web Services (AWS) marketplace. Prerequisites You have an AWS account. The Amazon Web Services CLI is installed and configured with your account credentials. Procedure Go to AWS marketplace at the URL: https://aws.amazon.com/marketplace . Search for "JBoss EAP" in the search bar. Filter the results by Publisher , selecting Red Hat Limited and Red Hat . Click the image you want to launch. Note If you are based in the European Union, select the image from the publisher " Red Hat Limited ", otherwise select the image from the publisher " Red Hat ". You are redirected to the software subscription page. Select the subscription settings and click Continue to Subscribe . Accept the terms by clicking Accept Terms , click Continue to Configuration . You are redirected to the configuration page. Select the configuration options and click Continue to Launch . You are directed to launch the software page. Review the launch configuration details and launch the instance by clicking Launch . 2.2. Launching JBoss EAP instance from private AMI using AWS EC2 Console You can launch JBoss EAP instance from a private AMI using the AWS EC2 Console. You can also launch an instance using the AWS Command Line Interface. See AWS CLI for more information about AWS CLI. Prerequisites You have a Red Hat subscription. You have an AWS account. The Amazon Web Services CLI is installed and configured with your account credentials. Procedure Open the Amazon EC2 console . From the Amazon EC2 console, click AMIs . Search for jbeap AMI in Private images , located in the Amazon Machine Images (AMIs) panel, and select the AMI. For example, RHEL-7-JBEAP-7.4.0_HVM_GA-20210909-x86_64-0-Access2-GP2 . Choose an instance type. See Supported Amazon EC2 Instance Types for more information on supported Amazon EC2 instance types. In the Configure Instance Details section, configure the instance settings. In the Advanced Details section, User data box, you can paste the sample script to run JBoss EAP when the instance is launched. See Launching JBoss EAP on Amazon EC2 Using Script for information about the sample script. Note If required, specify the storage, tag the instance, and configure the security group details. Click Review and Launch . This takes you directly to the Review Instance Launch page. Click Launch to choose a key pair and launch the instance. Note If you have not selected a key pair, specify a key pair before you launch an instance.

Commands:
Chapter 2. Understanding channels in JBoss EAP The jboss-eap-installation-manager provides a streamlined and controlled pathway to access the most recent supported versions of JBoss EAP components. These streamlined and controlled pathways are called channels. A channel consists of a curated list of component versions (called channel manifest) and a collection of repositories used to resolve and retrieve those components. Each repository has a unique name (id) and a default Maven repository URL. The jboss-eap-installation-manager allows you to manage these channels effectively in both stand-alone and managed domain configurations.

Commands:
Appendix C. Red Hat Virtualization User Interface Plugins C.1. Red Hat Virtualization User Interface Plug-ins Red Hat Virtualization supports plug-ins that expose non-standard features. This makes it easier to use the Red Hat Virtualization Administration Portal to integrate with other systems. Each interface plug-in represents a set of user interface extensions that can be packaged and distributed for use with Red Hat Virtualization. Red Hat Virtualization's User Interface plug-ins integrate with the Administration Portal directly on the client using the JavaScript programming language. Plug-ins are invoked by the Administration Portal and executed in the web browser's JavaScript runtime. User Interface plug-ins can use the JavaScript language and its libraries. At key events during runtime, the Administration Portal invokes individual plug-ins via event handler functions representing Administration-Portal-to-plug-in communication. Although the Administration Portal supports multiple event-handler functions, a plug-in declares functions which are of interest only to its implementation. Each plug-in must register relevant event handler functions as part of the plug-in bootstrap sequence before the plug-in is put to use by the administration portal. To facilitate the plug-in-to-Administration-Portal communication that drives the User Interface extension, the Administration Portal exposes the plug-in API as a global (top-level) pluginApi JavaScript object that individual plug-ins can consume. Each plug-in obtains a separate pluginApi instance, allowing the Administration Portal to control plug-in API-function invocation for each plug-in with respect to the plug-in's life cycle.

Commands:
Chapter 4. Installing Red Hat build of OpenJDK with the MSI installer This procedure describes how to install Red Hat build of OpenJDK 17 for Microsoft Windows using the MSI-based installer. Procedure Download the MSI-based installer of Red Hat build of OpenJDK 17 for Microsoft Windows. Run the installer for Red Hat build of OpenJDK 17 for Microsoft Windows. Click on the welcome screen. Check I accept the terms in license agreement , then click . Click . Accept the defaults or review the optional properties . Click Install . Click Yes on the Do you want to allow this app to make changes on your device? . Verify the Red Hat build of OpenJDK 17 for Microsoft Windows is successfully installed, run java -version command in the command prompt and you must get the following output:

Commands:
openjdk version "17" 2021-09-14 LTS OpenJDK Runtime Environment 21.9 (build 17+35-LTS) OpenJDK 64-Bit Server VM 21.9 (build 17+35-LTS, mixed mode, sharing)
Chapter 5. Known issues This section documents known issues found in this release of Red Hat Ceph Storage. 5.1. Ceph Object Gateway This section documents known issues found in this release of Red Hat Ceph Storage. 5.1.1. Ceph Object Gateway Bucket lifecycle processing might get delayed if the Ceph Object Gateway instances are killed due to a crash or kill Presently, if a Ceph Object Gateway instance is killed (ungraceful shutdown) due to a crash or kill -9 while lifecycle processing for one or more buckets is taking place, processing might not continue on those buckets until two scheduling periods have elapsed, for example, two days. At this point, the buckets are marked stale and reinitialized. There is no workaround for this issue. Bugzilla:2072680

Commands:
Chapter 13. Managing Ansible content You can import Ansible collections from several sources to Satellite Server. For more information about Ansible integration in Satellite, see Managing configurations using Ansible integration . 13.1. Synchronizing Ansible Collections On Satellite, you can synchronize your Ansible Collections from Private Automation Hub, console.redhat.com , and other Satellite instances. Ansible Collections will appear on Satellite as a new repository type in the Satellite web UI menu under Content after the sync. Procedure In the Satellite web UI, navigate to Content > Products . Select the required product name. In the Products window, select the name of a product that you want to create a repository for. Click the Repositories tab, and then click New Repository . In the Name field, enter a name for the repository. The Label field is populated automatically based on the name. From the Type list, select ansible collection . In the Upstream URL field, enter the URL for the upstream collections repository. The URL can be any Ansible Galaxy endpoint. For example, https://console.redhat.com/api/automation-hub/ . Optional: In the Requirements.yml field, you can specify the list of collections you want to sync from the endpoint, as well as their versions. If you do not specify the list of collections, everything from the endpoint will be synced. --- collections: - name: my_namespace.my_collection version: 1.2.3 For more information, see Installing roles and collections from the same requirements.yml file in the Galaxy User Guide . Authenticate. To sync Satellite from Private Automation Hub , enter your token in the Auth Token field. For more information, see Connect Private Automation Hub in Connect to Hub . To sync Satellite from console.redhat.com , enter your token in the Auth Token field and enter your SSO URL in the the Auth URL field. For more information, see Getting started with automation hub . To sync Satellite from Satellite, leave both authentication fields blank. Click Save . Navigate to the Ansible Collections repository. From the Select Action menu, select Sync Now .

Commands:
--- collections: - name: my_namespace.my_collection version: 1.2.3
Chapter 3. Block pools The OpenShift Data Foundation operator installs a default set of storage pools depending on the platform in use. These default storage pools are owned and controlled by the operator and it cannot be deleted or modified. With OpenShift Container Platform, you can create multiple custom storage pools which map to storage classes that provide the following features: Enable applications with their own high availability to use persistent volumes with two replicas, potentially improving application performance. Save space for persistent volume claims using storage classes with compression enabled. Note Multiple block pools are not supported for external mode OpenShift Data Foundation clusters. 3.1. Creating a block pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage OpenShift Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click Create Block Pool . Enter Pool name . Select Data protection policy as either 2-way Replication or 3-way Replication . Select Volume Type . Optional: Select Enable compression checkbox if you need to compress the data. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression will not be compressed. Click Create . 3.2. Updating an existing pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage OpenShift Data Foundation . In the Storage systems tab, select the storage system and then click BlockPools . Click the Action Menu (...) at the end the pool you want to update. Click Edit Block Pool . Modify the form details as follows: Change the Data protection policy to either 2-way Replication or 3-way Replication. Enable or disable the compression option. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression will not be compressed. Click Save . 3.3. Deleting a pool Use this procedure to delete a pool in OpenShift Data Foundation. Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure . Click Storage OpenShift Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click the Action Menu (...) at the end the pool you want to delete. Click Delete Block Pool . Click Delete to confirm the removal of the Pool. Note A pool cannot be deleted when it is bound to a PVC. You must detach all the resources before performing this activity.

Commands:
Creating and Managing Service Accounts Red Hat Customer Portal 1 Create and manage service accounts Red Hat Customer Content Services

Commands:
export HOST='https://sso.redhat.com' CLIENT_ID='<client_id>' CLIENT_SECRET='<client_secret>' SCOPES='openid api.iam.service_accounts'
curl "USD{HOST}/auth/realms/redhat-external/protocol/openid-connect/token" --data-urlencode "grant_type=client_credentials" --data-urlencode "client_id=USD{CLIENT_ID}" --data-urlencode "client_secret=USD{CLIENT_SECRET}" --data-urlencode "scope=USD{SCOPES}"
export ACCESS_TOKEN=USD( curl "USD{HOST}/auth/realms/redhat-external/protocol/openid-connect/token" --data-urlencode "grant_type=client_credentials" --data-urlencode "client_id=USD{CLIENT_ID}" --data-urlencode "client_secret=USD{CLIENT_SECRET}" --data-urlencode "scope=USD{SCOPES}" | jq -r '.access_token')
curl --header "Authorization:Bearer USD{ACCESS_TOKEN}" --location "https://console.redhat.com/api/rbac/v1/access/?application=inventory"
14.5.10. Retrieving Memory Statistics for a Running Domain This command may return varied results depending on the hypervisor you are using. The dommemstat [domain] [--period (sec)][[--config][--live]|[--current]] displays the memory statistics for a running domain. Using the --period option requires a time period in seconds. Setting this option to a value larger than 0 will allow the balloon driver to return additional statistics which will be displayed by subsequent domemstat commands. Setting the --period option to 0, will stop the balloon driver collection but does not clear the statistics in the balloon driver. You cannot use the --live , --config , or --current options without also setting the --period option in order to also set the collection period for the balloon driver. If the --live option is specified, only the running guest's collection period is affected. If the --config option is used, it will affect the boot of a persistent guest. If --current option is used, it will affect the current guest state Both the --live and --config options may be used but --current is exclusive. If no option is specified, the behavior will be different depending on the guest's state.

Commands:
virsh domemstat rhel6 --current
7.94. irssi 7.94.1. RHBA-2012:1171 - irssi bug fix update Updated irssi packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Irssi is a modular IRC client with Perl scripting. Only the text-mode front end is currently supported. Bug Fix BZ# 639258 Prior to this update, when the user attempted to use the "/unload" command to unload a static module, Irssi incorrectly marked this module as unavailable, rendering the user unable to load this module again without restarting the client. This update adapts the underlying source code to ensure that only dynamic modules can be unloaded. BZ# 845047 The version of the irssi(1) manual page documented "--usage" as a valid command line option. This was incorrect, because Irssi no longer supports this option and an attempt to use it causes it to fail with an error. With this update, the manual page has been corrected and no longer documents unsupported command line options. All users of irssi are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.235. spice-vdagent 7.235.1. RHEA-2013:0311 - spice-vdagent enhancement update Updated spice-vdagent packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The spice-vdagent packages provide a SPICE agent for Linux guests. Note The spice-vdagent packages have been upgraded to upstream version 0.12.0, which provides a number of enhancements over the version. (BZ# 842355 ) Enhancements BZ# 747894 The spice-vdagent agent now uses the syslog standard for logging. Syslog provides previously missing information on time stamps and severity marks of the logged events. BZ# 842298 With this update, support for dynamic multiple monitors and arbitrary window resolution has been added to the spice-vdagent agent. All users of spice-vdagent are advised to upgrade to these updated packages, which add these enhancements.

Commands:
Chapter 28. Date and Time Configuration The Time and Date Properties Tool allows the user to change the system date and time, to configure the time zone used by the system, and to setup the Network Time Protocol (NTP) daemon to synchronize the system clock with a time server. You must be running the X Window System and have root privileges to use the tool. There are three ways to start the application: From the desktop, go to Applications (the main menu on the panel) => System Settings => Date & Time From the desktop, right-click on the time in the toolbar and select Adjust Date and Time . Type the command system-config-date , system-config-time , or dateconfig at a shell prompt (for example, in an XTerm or a GNOME terminal). 28.1. Time and Date Properties As shown in Figure 28.1, "Time and Date Properties" , the first tabbed window that appears is for configuring the system date and time. Figure 28.1. Time and Date Properties To change the date, use the arrows to the left and right of the month to change the month, use the arrows to the left and right of the year to change the year, and click on the day of the week to change the day of the week. To change the time, use the up and down arrow buttons beside the Hour , Minute , and Second in the Time section. Clicking the OK button applies any changes made to the date and time, the NTP daemon settings, and the time zone settings. It also exits the program.

Commands:
Chapter 4. Using Spring Session 4.1. Enabling Spring Session Support Data Grid Spring Session support is built on SpringRemoteCacheManager and SpringEmbeddedCacheManager . The Data Grid starter produces those beans by default. Procedure Add this starter to your project. Add Spring Session to the classpath. Add the following annotations to your configuration: @EnableCaching @EnableInfinispanRemoteHttpSession @EnableInfinispanEmbeddedHttpSession Note Data Grid does not provide a default cache. To use Spring Session, you must first create a Data Grid cache.

Commands:
12.6. Creating an Attribute This section describes how to create a attribute using the command line and the web console. 12.6.1. Creating an Attribute Using the Command Line Use the ldapmodify utility to create a new attribute. For example: For further details about attribute definitions, see Section 12.1.3, "Attributes" . 12.6.2. Creating an Attribute Using the Web Console To create an attribute using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Select Schema Attributes . Click Add Attribute . Fill the parameters. Click Add .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com schema attributetypes add dateofbirth --desc="For employee birthdays" --syntax="1.3.6.1.4.1.1466.115.121.1.15" --single-value --x-origin="Example defined"
17.5. Additional Resources Additional information concerning TCP wrappers and xinetd is available from system documentation and on the Internet. 17.5.1. Installed Documentation The bundled documentation on your system is a good place to start looking for additional TCP Wrappers, xinetd , and access control configuration options. /usr/share/doc/tcp_wrappers- <version> / - This directory contains a README file that discusses how TCP wrappers work and the various hostname and host address spoofing risks that exist. /usr/share/doc/xinetd- <version> / - This directory contains a README file that discusses aspects of access control and a sample.conf file with various ideas for modifying service-specific configuration files in the /etc/xinetd.d/ directory. TCP wrappers and xinetd related man pages - There are a number of man pages for the various applications and configuration files involved with TCP wrappers and xinetd . The following lists some of the more important man pages. Server Applications man xinetd - The man page for the xinetd super service daemon. Configuration Files man 5 hosts_access - The man page for the TCP wrappers hosts access control files. man hosts_options - The man page for the TCP wrappers options fields. man xinetd.conf - The man page listing xinetd configuration options.

Commands:
5.5.2.5. Accounting of Space Utilized One constant in a system administrator's life is that there is never enough free space, and even if there is, it will not remain free for long. Therefore, a system administrator should at least be able to easily determine the level of free space available for each file system. In addition, file systems with well-defined user identification capabilities often include the capability to display the amount of space a particular user has consumed. This feature is vital in large multi-user environments, as it is an unfortunate fact of life that the 80/20 rule often applies to disk space -- 20 percent of your users will be responsible for consuming 80 percent of your available disk space. By making it easy to determine which users are in that 20 percent, you can more effectively manage your storage-related assets. Taking this a step further, some file systems include the ability to set per-user limits (often known as disk quotas ) on the amount of disk space that can be consumed. The specifics vary from file system to file system, but in general each user can be assigned a specific amount of storage that a user can use. Beyond that, various file systems differ. Some file systems permit the user to exceed their limit for one time only, while others implement a "grace period" during which a second, higher limit is applied.

Commands: