mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Viewing your reports on Red Hat Ansible Automation Platform The reports feature on the Red Hat Ansible Automation Platform provides users with a visual overview of their automation efforts across different teams using Ansible. Each report is designed to help users monitor the status of their automation environment, be it the frequency of playbook runs or the status of hosts affected by various job templates. For example, you can use your reports to: View the number of hosts affected by a job template View the number changes made to hosts by a job template View the frequency of a job template run, and the rate of job templates that succeed or fail to run 1.1. Reviewing your reports To view reports about your Ansible automation environment, proceed with the following steps: Procedure Log in to console.redhat.com and navigate to the Ansible Automation Platform. Click Reports on the side navigation panel. Select a report from the results to view it. Each report presents data to monitor your Ansible automation environment. Use the filter toolbar on each report to adjust your graph view. Note We are constantly adding new reports to the system. If you have ideas for new reports that would be helpful for your team, please contact your account representative or log a feature enhancement for Insights for Ansible Automation Platform.

Commands:
Chapter 4. Performance impact of alt-java The alt-java binary contains the SSB mitigation, so the SSB mitigation performance impact no longer exists on java . Note Using alt-java might significantly reduce the performance of Java programs. You can find detailed information of some Java performance issues that might exist with using alt-java by selecting any of the Red Hat Bugzilla links listed in the Additional resources section. Additional resources (java-11-openjdk) Seccomp related performance regression in RHEL8 . (java-1.8.0-openjdk) Seccomp related performance regression in RHEL8 . CVE-2018-3639 Detail . CVE-2018-3639 hw: cpu: speculative store bypass . CVE-2018-3639 java-1.8.0-openjdk: hw: cpu: speculative store bypass (rhel-7.6) Revised on 2024-05-09 14:52:38 UTC

Commands:
4.62. fipscheck 4.62.1. RHEA-2011:1733 - fipscheck enhancement update Updated fipscheck packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The fipscheck library is used to verify the integrity of modules validated under FIPS-140-2. The fipscheck package provides helper binaries for creating and verifying HMAC-SHA256 checksum files. Enhancement BZ# 727277 Prior to this update, the fipscheck library was linked without support for read-only relocations (RELRO) flags. The updated fipscheck packages are now provided with partial RELRO support. Users of fipscheck are advised to upgrade to these updated packages, which add this enhancement.

Commands:
14.22. Virtual Networking Commands The following commands manipulate virtual networks. libvirt has the capability to define virtual networks which can then be used by domains and linked to actual network devices. For more detailed information about this feature see the documentation at libvirt's website . Many of the commands for virtual networks are similar to the ones used for domains, but the way to name a virtual network is either by its name or UUID. 14.22.1. Autostarting a Virtual Network This command will configure a virtual network to be started automatically when the guest virtual machine boots. To run this command: This command accepts the --disable option which disables the autostart command.

Commands:
virsh net-autostart network [ --disable ]
Chapter 9. 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:
Chapter 3. Using the JFrog Artifactory plugin The JFrog Artifactory plugin displays information about your container images within the Jfrog Artifactory registry. Important The JFrog Artifactory plugin is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. Prerequisites Your Developer Hub application is installed and running. You have enabled the JFrog Artifactory plugin. Procedure Open your Developer Hub application and select a component from the Catalog page. Go to the Image Registry tab. The Image Registry tab contains a list of container images within your Jfrog Artifactory repository and related information, such as Version , Repositories , Manifest , Modified , and Size .

Commands:
8.2. Mounting an XFS File System An XFS file system can be mounted with no extra options, for example: XFS also supports several mount options to influence behavior. XFS allocates inodes to reflect their on-disk location by default. However, because some 32-bit userspace applications are not compatible with inode numbers greater than 2 32 , XFS will allocate all inodes in disk locations which result in 32-bit inode numbers. This can lead to decreased performance on very large filesystems (that is, larger than 2 terabytes), because inodes are skewed to the beginning of the block device, while data is skewed towards the end. To address this, use the inode64 mount option. This option configures XFS to allocate inodes and data across the entire file system, which can improve performance: Write Barriers By default, XFS uses write barriers to ensure file system integrity even when power is lost to a device with write caches enabled. For devices without write caches, or with battery-backed write caches, disable the barriers by using the nobarrier option: For more information about write barriers, refer to Chapter 22, Write Barriers .

Commands:
mount /dev/ device /mount/point
mount -o inode64 /dev/device /mount/point
mount -o nobarrier /dev/device /mount/point
3.18. RHEA-2011:1640 - new packages: sgabios New sgabios packages are now available for Red Hat Enterprise Linux 6. The sgabios packages provide the Google Serial Graphics Adapter BIOS (SGABIOS) for legacy 86-bit software to communicate with an attached serial console. This enhancement update adds the new sgabios packages to Red Hat Enterprise Linux 6. (BZ# 725832 ) All users who require SGABIOS are advised to install these new packages.

Commands:
Preface Standalone Manager installation is manual and customizable. You must install a Red Hat Enterprise Linux machine, then run the configuration script ( engine-setup ) and provide information about how you want to configure the Red Hat Virtualization Manager. Add hosts and storage after the Manager is running. At least two hosts are required for virtual machine high availability. In a remote database environment, you must create the Manager database manually before running engine-setup . You can create the Data Warehouse database manually, or let the Data Warehouse configuration script ( ovirt-engine-dwh-setup ) create it automatically if you are installing the Data Warehouse service on the same machine. See the Planning and Prerequisites Guide for information on environment options and recommended configuration. Table 1. Red Hat Virtualization Key Components Component Name Description Red Hat Virtualization Manager A service that provides a graphical user interface and a REST API to manage the resources in the environment. The Manager is installed on a physical or virtual machine running Red Hat Enterprise Linux. Hosts Red Hat Enterprise Linux hosts (RHEL hosts) and Red Hat Virtualization Hosts (image-based hypervisors) are the two supported types of host. Hosts use Kernel-based Virtual Machine (KVM) technology and provide resources used to run virtual machines. Shared Storage A storage service is used to store the data associated with virtual machines. Data Warehouse A service that collects configuration information and statistical data from the Manager. Standalone Manager Architecture The Red Hat Virtualization Manager runs on a physical server, or a virtual machine hosted in a separate virtualization environment. A standalone Manager is easier to deploy and manage, but requires an additional physical server. The Manager is only highly available when managed externally with a product such as Red Hat's High Availability Add-On. The minimum setup for a standalone Manager environment includes: One Red Hat Virtualization Manager machine. The Manager is typically deployed on a physical server. However, it can also be deployed on a virtual machine, as long as that virtual machine is hosted in a separate environment. The Manager must run on Red Hat Enterprise Linux 7. A minimum of two hosts for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1. Standalone Manager Red Hat Virtualization Architecture

Commands:
20.7. Memory tuning <domain> ... <memtune> <hard_limit unit='G'>1</hard_limit> <soft_limit unit='M'>128</soft_limit> <swap_hard_limit unit='G'>2</swap_hard_limit> <min_guarantee unit='bytes'>67108864</min_guarantee> </memtune> ... </domain> Figure 20.9. Memory Tuning Although all are optional, the components of this section of the domain XML are as follows: Table 20.6. Memory tuning elements Element Description <memtune> Provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. The parameters are applied to the process as a whole therefore when setting limits, one needs to add up guest virtual machine RAM, guest virtual machine video RAM, and allow for some memory overhead. The last piece is hard to determine so one use trial and error. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory> . For backwards compatibility, output is always in KiB. <hard_limit> This is the maximum memory the guest virtual machine can use. The unit for this value is expressed in kibibytes (blocks of 1024 bytes) <soft_limit> This is the memory limit to enforce during memory contention. The unit for this value is expressed in kibibytes (blocks of 1024 bytes) <swap_hard_limit> This is the maximum memory plus swap the guest virtual machine can use. The unit for this value is expressed in kibibytes (blocks of 1024 bytes). This has to be more than <hard_limit> value provided <min_guarantee> This is the guaranteed minimum memory allocation for the guest virtual machine. The units for this value is expressed in kibibytes (blocks of 1024 bytes)

Commands:
<domain> <memtune> <hard_limit unit='G'>1</hard_limit> <soft_limit unit='M'>128</soft_limit> <swap_hard_limit unit='G'>2</swap_hard_limit> <min_guarantee unit='bytes'>67108864</min_guarantee> </memtune> </domain>
16.3.2. Control Flag All PAM modules generate a success or failure result when called. Control flags tell PAM what do with the result. Since modules can be stacked in a particular order, control flags decide how important the success or failure of a particular module is to the overall goal of authenticating the user to the service. There are four predefined control flags: required - The module result must be successful for authentication to continue. If a required module result fails, the user is not notified until results on all modules referencing that interface are completed. requisite - The module result must be successful for authentication to continue. However, if a requisite module result fails, the user is notified immediately with a message reflecting the first failed required or requisite module. sufficient - The module result is ignored if it fails. However, if a sufficient flagged module result is successful and no required flagged modules above it have failed, then no other results are required and the user is authenticated to the service. optional - The module result is ignored. A module flagged as optional only becomes necessary for successful authentication when there are no other modules referencing the interface. Important The order in which required modules are called is not critical. The sufficient and requisite control flags cause order to become important. A newer control flag syntax which allows for more precise control is now available for PAM. Please see the PAM documentation located in the /usr/share/doc/pam- <version-number> / directory for information on this new syntax (where <version-number> is the version number for PAM).

Commands:
9.5. Displaying the Encryption Protocols Enabled in Directory Server To display the enabled encryption protocols in Directory Server: The sslVersionMin and sslVersionMax parameter control which encryption protocol versions Directory Server uses. The default of sslVersionMin depends on the system-wide crypto policy you use.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com security get sslversionmin: TLS1.2 sslversionmax: TLS1.3
Chapter 3. Creating an IBM Power Virtual Server workspace Important IBM Power(R) Virtual Server using installer-provisioned infrastructure is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 3.1. Creating an IBM Power Virtual Server workspace Use the following procedure to create an IBM Power(R) Virtual Server workspace. Procedure To create an IBM Power(R) Virtual Server workspace, complete step 1 to step 5 from the IBM Cloud(R) documentation for Creating an IBM Power(R) Virtual Server . After it has finished provisioning, retrieve the 32-character alphanumeric Globally Unique Identifier (GUID) of your new workspace by entering the following command: USD ibmcloud resource service-instance <workspace name> 3.2. steps Installing a cluster on IBM Power(R) Virtual Server with customizations

Commands:
ibmcloud resource service-instance <workspace name>
2.4.2. Sharing NFS and CIFS volumes By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS volumes. In common policies, this default context uses the nfs_t type. Also, by default, Samba shares mounted on the client side are labeled with a default context defined by policy. In common policies, this default context uses the cifs_t type. Depending on policy configuration, services may not be able to read files labeled with the nfs_t or cifs_t types. This may prevent file systems labeled with these types from being mounted and then read or exported by other services. Booleans can be enabled or disabled to control which services are allowed to access the nfs_t and cifs_t types. Enable the httpd_use_nfs Boolean to allow httpd to access and share NFS volumes (labeled with the nfs_t type). Run the setsebool command as the root user to enable the Boolean: Enable the httpd_use_cifs Boolean to allow httpd to access and share CIFS volumes (labeled with the cifs_t type). Run the setsebool command as the root user to enable the Boolean: Note Do not use the -P option if you do not want setsebool changes to persist across reboots.

Commands:
~]# setsebool -P httpd_use_nfs on
~]# setsebool -P httpd_use_cifs on
Chapter 5. Tags 5.1. Using Tags to Customize Interactions with Red Hat Virtualization After your Red Hat Virtualization platform is set up and configured to your requirements, you can customize the way you work with it using tags. Tags allow system resources to be arranged into groups or categories. This is useful when many objects exist in the virtualization environment and the administrator wants to concentrate on a specific set of them. This section describes how to create and edit tags, assign them to hosts or virtual machines and search using the tags as criteria. Tags can be arranged in a hierarchy that matches a structure, to fit the needs of the enterprise. To create, modify, and remove Administration Portal tags, click the Tags icon ( ) in the header bar.

Commands:
Chapter 6. Adjusting the search size and time limit Some queries, such as requesting a list of IdM users, can return a very large number of entries. By tuning these search operations, you can improve the overall server performance when running the ipa *-find commands, such as ipa user-find , and when displaying corresponding lists in the Web UI. Search size limit Defines the maximum number of entries returned for a request sent to the server from a client's CLI or from a browser accessing the IdM Web UI. Default: 100 entries. Search time limit Defines the maximum time (in seconds) that the server waits for searches to run. Once the search reaches this limit, the server stops the search and returns the entries discovered in that time. Default: 2 seconds. If you set the values to -1 , IdM will not apply any limits when searching. Important Setting search size or time limits too high can negatively affect server performance. 6.1. Adjusting the search size and time limit in the command line The following procedure describes adjusting search size and time limits in the command line: Globally For a specific entry Procedure To display current search time and size limits in CLI, use the ipa config-show command: To adjust the limits globally for all queries, use the ipa config-mod command and add the --searchrecordslimit and --searchtimelimit options. For example: To temporarily adjust the limits only for a specific query, add the --sizelimit or --timelimit options to the command. For example: 6.2. Adjusting the search size and time limit in the Web UI The following procedure describes adjusting global search size and time limits in the IdM Web UI. Procedure Log in to the IdM Web UI. Click IPA Server . On the IPA Server tab, click Configuration . Set the required values in the Search Options area. Default values are: Search size limit: 100 entries Search time limit: 2 seconds Click Save at the top of the page.

Commands:
ipa config-show Search time limit: 2 Search size limit: 100
ipa config-mod --searchrecordslimit=500 --searchtimelimit=5
ipa user-find --sizelimit=200 --timelimit=120
Chapter 1. Developing for Red Hat JBoss Data Virtualization 1.1. Developing for Red Hat JBoss Data Virtualization Red Hat JBoss Data Virtualization provides several translators and resource adapters to enable communication with various datasources. If none of the included translators and resource adapters meet your requirements, you can extend them or create your own. One of the most common examples of custom translator development is the extension of the JDBC translator for new JDBC drivers and database versions.

Commands:
5.141. libbonobo 5.141.1. RHBA-2012:0908 - libbonobo bug fix update Updated libbonobo packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libbonobo packages contain the libraries for bonobo, which is a component system based on CORBA, used by the GNOME desktop. Bug Fix BZ# 728458 Prior to this update, the activation server handled parse errors incorrectly, for example as incorrectly nested tags, in server files. As a consequence, the activation server could, under certain circumstances, unexpectedly terminate with an abort signal upon encountering invalid server files in the activation path. This update modifies the underlying code so that invalid files no longer cause unexpected termination. All users of libbonobo are advised to upgrade to these updated packages which fix this bug.

Commands:
Chapter 4. System report test The Red Hat system report test, is also known as openstack/sosreport , and captures the basic system report. The system report test ensures that the SOS tool captures a basic report and performing operations as expected on the image or system. The sosreport command is a tool that collects configuration details, system and diagnostic information from a RHEL system and assists you in troubleshooting their systems. Success criteria A basic sosreport can be captured from the system under test. The test status will be PASS, if a valid rpm version captures and collects the openstack data and the openstack plugins (manila, cinder, neutron) are enabled. Additional resources For more information about sosreport, see What is an sosreport and how to create one in Red Hat Enterprise Linux? .

Commands: