mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Resource optimization for OpenShift optimization reports Access resource optimization for OpenShift from the Red Hat Hybrid Cloud Console to see detailed recommendations for how to optimize your Red Hat OpenShift clusters. 3.1. Enabling optimization To receive resource optimization recommendations for your namespaces, you must first enable each namespace. To enable a namespace, label it with insights_cost_management_optimizations='true' . In the CLI, run: oc label namespace NAMESPACE insights_cost_management_optimizations="true" --overwrite=true 3.2. Viewing optimization reports Prerequisites You added an OpenShift integration to Red Hat Hybrid Cloud Console . You uploaded at least 24 hours of data from the operator. You logged in to the Red Hat Hybrid Cloud Console . Procedure In cost management, click the tab Optimizations . Search for an optimization or use the filter. Click the link to the optimization that you selected. View details about the recommendation and toggle between Cost optimizations and Performance optimizations . For more information, see Optimizing for cost or for performance . 3.3. Optimizing for cost or for performance After you select an optimization, you can toggle between two tabs called Cost optimizations and Performance optimizations . Optimizing for cost uses less resources and is useful when you are performing tests where there is no impact to users. Optimizing for performance provides all the resources possible and is helpful for apps running in a production cluster. In Cost optimizations , recommendations get generated when CPU usage is at or above the 60th percentile and memory usage is at the 100th percentile. In Performance optimizations , recommendations get generated when CPU usage is at or above the 98th percentile and when memory usage is at the 100th percentile. 3.4. Understanding box plots On the Optimizations page, there are two box plots for your Current CPU utilization and your Current memory utilization . These visualizations can help you understand resource distribution and identify outliers in your data. You can export the data in CSV and JSON format. The box plots display the following data points in millicpu (m) for CPU and in mebibytes (Mi) for memory: Minimum Maximum Median First quartile (Q1): value where 25% of data points are when they are arranged in increasing order Third quartile (Q3): value where 75% of data points are when they are arranged in increasing order Recommended limit Recommended request The data points are based on the time period that you selected: 1 day = 4 data points 7 days = 7 data points 14 days = 14 data points

Commands:
2.11. Uninstalling All Software Collection Directories Keep in mind that the yum remove command does not uninstall directories provided by those Software Collection packages and subpackages that are removed after the Software Collection runtime subpackage is removed. To ensure that all directories are uninstalled, make those packages and subpackages depend on the runtime subpackage. To do so, add the following line with the %scl_runtime macro to the spec file of each of those packages and subpackages: %{?scl:Requires: %scl_runtime} Adding the above line ensures that all directories provided by those packages and subpackages are removed correctly as long as the runtime subpackage does not depend on any of those packages and subpackages.

Commands:
%{?scl:Requires: %scl_runtime}
5.4.2.2. Adding the New Physical Volume to the Volume Group Add /dev/sdd1 to the existing volume group myvg .

Commands:
vgextend myvg /dev/sdd1 Volume group "myvg" successfully extended pvs -o+pv_used PV VG Fmt Attr PSize PFree Used /dev/sda1 myvg lvm2 a- 17.15G 7.15G 10.00G /dev/sdb1 myvg lvm2 a- 17.15G 15.15G 2.00G /dev/sdc1 myvg lvm2 a- 17.15G 15.15G 2.00G /dev/sdd1 myvg lvm2 a- 17.15G 17.15G 0
Appendix A. Revision History Revision History Revision 7-6 Tue Oct 30 2018 Vladimir Slavik Release for Red Hat Enterprise Linux 7.6 GA. Revision 7-5 Tue Jan 09 2018 Vladimir Slavik Release for Red Hat Enterprise Linux 7.5 Beta. Revision 7-4 Wed Jul 26 2017 Vladimir Slavik Release for Red Hat Enterprise Linux 7.4. Revision 1-4 Wed Oct 19 2016 Robert Kratky Release for Red Hat Enterprise Linux 7.3. Revision 1-2 Thu Mar 10 2016 Robert Kratky Async release for Red Hat Enterprise Linux 7.2. Revision 1-2 Thu Nov 11 2015 Robert Kratky Release for Red Hat Enterprise Linux 7.2.

Commands:
Part I. Getting started with decision services in Red Hat Process Automation Manager As a business rules developer, you can use Business Central in Red Hat Process Automation Manager or the Red Hat Process Automation Manager DMN modeler in VS Code to design a variety of decision services. Red Hat Process Automation Manager provides example projects with example business assets directly in Business Central as a reference. This document describes how to create and test an example traffic violation project based on the Traffic_Violation sample project included in Business Central. This sample project uses a Decision Model and Notation (DMN) model to define driver penalty and suspension rules in a traffic violation decision service. You can follow the steps in this document to create the project and the assets it contains, or open and review the existing Traffic_Violation sample project. For more information about the DMN components and implementation in Red Hat Process Automation Manager, see Designing a decision service using DMN models . Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For installation information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Red Hat Process Automation Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Process Automation Manager installation .

Commands:
8.78. grubby 8.78.1. RHBA-2014:1575 - grubby bug fix update Updated grubby packages that fix two bugs are now available for Red Hat Enterprise Linux 6. grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), yaboot (powerpc) and zipl (s390) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment. Bug Fixes BZ# 1098846 Prior to this update, the Trusted Boot (tboot) module incorrectly used the tboot.gz multiboot image to search for a grub configuration file. As a consequence, running the "yum update" command led to grubby corrupting the grub.conf file when tboot was enabled and two or more kernels were updated. With this update, tboot uses specific kernel names to search for grub configuration, and corruption of grub.conf no longer occurs in the described scenario. BZ# 997934 Previously, enabling tboot caused the kernel configuration to not be displayed properly when running the "grubby --info=DEFAULT" command. With this update, multiboot module parameters have been included in the output of "grubby --info", and the configuration displays as expected when tboot is running. Users of grubby are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.157. pcsc-lite 7.157.1. RHBA-2015:1369 - pcsc-lite bug fix update Updated pcsc-lite packages that fix two bugs are now available for Red Hat Enterprise Linux 6. PC/SC Lite provides a Windows SCard compatible interface for communicating with smart cards, smart card readers, and other security tokens. Bug Fixes BZ# 956530 Previously, after a card reader went offline when the user entered the settings menu, the pcsc-lite client could under certain circumstances enter a deadlock state and never recover from it. The underlying source code has been modified so that the client does not wait for an unreleased mutex. As a result, the client does not enter a deadlock state in the described situation, and the reader is accessible again after it returns online. BZ# 1171118 On systems with the pcsc-lite-openct package uninstalled, if the pcscd service terminated unexpectedly or was killed, restarting or stopping and starting pcscd failed. This update modifies pcscd to remove the pcscd.comm and pcscd.pub files after pcscd terminates unexpectedly or is killed. As a result, pcscd can be restarted or stopped and started again as expected in the described situation. Users of pcsc-lite are advised to upgrade to these updated packages, which fix these bugs.

Commands:
15.2.3. Uninstalling Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt: Note Notice that we used the package name foo , not the name of the original package file foo-1.0-1.i386.rpm . To uninstall a package, replace foo with the actual package name of the original package. You can encounter a dependency error when uninstalling a package if another installed package depends on the one you are trying to remove. For example: To cause RPM to ignore this error and uninstall the package anyway, which may break the package depending on it, use the --nodeps option.

Commands:
-e foo
error: Failed dependencies: foo is needed by (installed) bar-2.0.20-3.i386.rpm
9.5. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below). Once you have made your selection, click to continue. Figure 9.3. Keyboard Configuration Red Hat Enterprise Linux includes support for more than one keyboard layout for many languages. In particular, most European languages include a latin1 option, which uses dead keys to access certain characters, such as those with diacritical marks. When you press a dead key, nothing will appear on your screen until you press another key to "complete" the character. For example, to type e on a latin1 keyboard layout, you would press (and release) the ' key, and then press the E key. By contrast, you access this character on some other keyboards by pressing and holding down a key (such as Alt-Gr ) while you press the E key. Other keyboards might have a dedicated key for this character. Note To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool . Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool . If you are not root, it prompts you for the root password to continue.

Commands:
Chapter 4. The DM Multipath Configuration File By default, DM Multipath provides configuration values for the most common uses of multipathing. In addition, DM Multipath includes support for the most common storage arrays that themselves support DM Multipath. For information on the default configuration values, including supported devices, run either of the following commands. You can override the default configuration values for DM Multipath by editing the /etc/multipath.conf configuration file. If necessary, you can also add a storage array that is not supported by default to the configuration file. Note You can run set up multipathing in the initramfs file system. If you run multipath from the initramfs file system and you make any changes to the multipath configuration files, you must rebuild the initramfs file system for the changes to take effect. For information on rebuilding the initramfs file system with multipath, see Section 3.4, "Setting Up Multipathing in the initramfs File System" . This chapter provides information on parsing and modifying the multipath.conf file. It contains sections on the following topics: Configuration file overview Configuration file blacklist Configuration file defaults Configuration file multipaths Configuration file devices In the multipath configuration file, you need to specify only the sections that you need for your configuration, or that you wish to change from the default values. If there are sections of the file that are not relevant to your environment or for which you do not need to override the default values, you can leave them commented out, as they are in the initial file. The configuration file allows regular expression description syntax. Further information about the configuration file can be found on the multipath.conf (5) man page. 4.1. Configuration File Overview The multipath configuration file is divided into the following sections: blacklist Listing of specific devices that will not be considered for multipath. blacklist_exceptions Listing of multipath candidates that would otherwise be blacklisted according to the parameters of the blacklist section. defaults General default settings for DM Multipath. multipaths Settings for the characteristics of individual multipath devices. These values overwrite what is specified in the defaults and devices sections of the configuration file. devices Settings for the individual storage controllers. These values overwrite what is specified in the defaults section of the configuration file. If you are using a storage array that is not supported by default, you may need to create a devices subsection for your array. When the system determines the attributes of a multipath device, first it checks the multipath settings, then the devices settings, then the multipath system defaults.

Commands:
multipathd show config multipath -t
Appendix B. virt-sysprep Operations The virt-sysprep command removes system-specific details. Only operations marked with * are performed during the template sealing process.

Commands:
virt-sysprep --list-operations abrt-data * Remove the crash data generated by ABRT bash-history * Remove the bash history in the guest blkid-tab * Remove blkid tab in the guest ca-certificates Remove CA certificates in the guest crash-data * Remove the crash data generated by kexec-tools cron-spool * Remove user at-jobs and cron-jobs customize * Customize the guest dhcp-client-state * Remove DHCP client leases dhcp-server-state * Remove DHCP server leases dovecot-data * Remove Dovecot (mail server) data firewall-rules Remove the firewall rules flag-reconfiguration Flag the system for reconfiguration fs-uuids Change filesystem UUIDs kerberos-data Remove Kerberos data in the guest logfiles * Remove many log files from the guest lvm-uuids * Change LVM2 PV and VG UUIDs machine-id * Remove the local machine ID mail-spool * Remove email from the local mail spool directory net-hostname * Remove HOSTNAME in network interface configuration net-hwaddr * Remove HWADDR (hard-coded MAC address) configuration pacct-log * Remove the process accounting log files package-manager-cache * Remove package manager cache pam-data * Remove the PAM data in the guest puppet-data-log * Remove the data and log files of puppet rh-subscription-manager * Remove the RH subscription manager files rhn-systemid * Remove the RHN system ID rpm-db * Remove host-specific RPM database files samba-db-log * Remove the database and log files of Samba script * Run arbitrary scripts against the guest smolt-uuid * Remove the Smolt hardware UUID ssh-hostkeys * Remove the SSH host keys in the guest ssh-userdir * Remove ".ssh" directories in the guest sssd-db-log * Remove the database and log files of sssd tmp-files * Remove temporary files udev-persistent-net * Remove udev persistent net rules user-account Remove the user accounts in the guest utmp * Remove the utmp file yum-uuid * Remove the yum UUID
Chapter 3. Understanding the ROSA with STS deployment workflow Before you create a Red Hat OpenShift Service on AWS (ROSA) cluster, you must complete the AWS prerequisites, verify that the required AWS service quotas are available, and set up your environment. This document provides an overview of the ROSA with STS deployment workflow stages and refers to detailed resources for each stage. 3.1. Overview of the ROSA with STS deployment workflow The AWS Security Token Service (STS) is a global web service that provides short-term credentials for IAM or federated users. You can use AWS STS with Red Hat OpenShift Service on AWS (ROSA) to allocate temporary, limited-privilege credentials for component-specific IAM roles. The service enables cluster components to make AWS API calls using secure cloud resource management practices. You can follow the workflow stages outlined in this section to set up and access a ROSA cluster that uses STS. Complete the AWS prerequisites for ROSA with STS . To deploy a ROSA cluster with STS, your AWS account must meet the prerequisite requirements. Review the required AWS service quotas . To prepare for your cluster deployment, review the AWS service quotas that are required to run a ROSA cluster. Set up the environment and install ROSA using STS . Before you create a ROSA with STS cluster, you must enable ROSA in your AWS account, install and configure the required CLI tools, and verify the configuration of the CLI tools. You must also verify that the AWS Elastic Load Balancing (ELB) service role exists and that the required AWS resource quotas are available. Create a ROSA cluster with STS quickly or create a cluster using customizations . Use the ROSA CLI ( rosa ) or Red Hat OpenShift Cluster Manager to create a cluster with STS. You can create a cluster quickly by using the default options, or you can apply customizations to suit the needs of your organization. Access your cluster . You can configure an identity provider and grant cluster administrator privileges to the identity provider users as required. You can also access a newly-deployed cluster quickly by configuring a cluster-admin user. Revoke access to a ROSA cluster for a user . You can revoke access to a ROSA with STS cluster from a user by using the ROSA CLI or the web console. Delete a ROSA cluster . You can delete a ROSA with STS cluster by using the ROSA CLI ( rosa ). After deleting a cluster, you can delete the STS resources by using the AWS Identity and Access Management (IAM) Console. 3.2. Additional resources For information about using the ROSA deployment workflow to create a cluster that does not use AWS STS, see Understanding the ROSA deployment workflow .

Commands:
3.11. Enhanced Graphics Power Management Red Hat Enterprise Linux 6 saves power on graphics and display devices by eliminating several sources of unnecessary consumption. LVDS reclocking Low-voltage differential signaling (LVDS) is a system for carrying electronic signals over copper wire. One significant application of the system is to transmit pixel information to liquid crystal display (LCD) screens in notebook computers. All displays have a refresh rate - the rate at which they receive fresh data from a graphics controller and redraw the image on the screen. Typically, the screen receives fresh data sixty times per second (a frequency of 60 Hz). When a screen and graphics controller are linked by LVDS, the LVDS system uses power on every refresh cycle. When idle, the refresh rate of many LCD screens can be dropped to 30 Hz without any noticeable effect (unlike cathode ray tube (CRT) monitors, where a decrease in refresh rate produces a characteristic flicker). The driver for Intel graphics adapters built into the kernel used in Red Hat Enterprise Linux 6 performs this downclocking automatically, and saves around 0.5 W when the screen is idle. Enabling memory self-refresh Synchronous dynamic random access memory (SDRAM) - as used for video memory in graphics adapters - is recharged thousands of times per second so that individual memory cells retain the data that is stored in them. Apart from its main function of managing data as it flows in and out of memory, the memory controller is normally responsible for initiating these refresh cycles. However, SDRAM also has a low-power self-refresh mode. In this mode, the memory uses an internal timer to generate its own refresh cycles, which allows the system to shut down the memory controller without endangering data currently held in memory. The kernel used in Red Hat Enterprise Linux 6 can trigger memory self-refresh in Intel graphics adapters when they are idle, which saves around 0.8 W. GPU clock reduction Typical graphical processing units (GPUs) contain internal clocks that govern various parts of their internal circuitry. The kernel used in Red Hat Enterprise Linux 6 can reduce the frequency of some of the internal clocks in Intel and ATI GPUs. Reducing the number of cycles that GPU components perform in a given time saves the power that they would have consumed in the cycles that they did not have to perform. The kernel automatically reduces the speed of these clocks when the GPU is idle, and increases it when GPU activity increases. Reducing GPU clock cycles can save up to 5 W. GPU powerdown The Intel and ATI graphics drivers in Red Hat Enterprise Linux 6 can detect when no monitor is attached to an adapter and therefore shut down the GPU completely. This feature is especially significant for servers which do not have monitors attached to them regularly.

Commands:
2.8.9.7.2. Related Documentation Red Hat Linux Firewalls , by Bill McCarty; Red Hat Press - a comprehensive reference to building network and server firewalls using open source packet filtering technology such as Netfilter and iptables . It includes topics that cover analyzing firewall logs, developing firewall rules, and customizing your firewall using various graphical tools. Linux Firewalls , by Robert Ziegler; New Riders Press - contains a wealth of information on building firewalls using both 2.2 kernel ipchains as well as Netfilter and iptables . Additional security topics such as remote access issues and intrusion detection systems are also covered.

Commands:
4.4. Authentication Apache Modules for External Authentication A set of Apache modules has been added to Red Hat Enterprise Linux 6.6 as a Technology Preview. The mod_authnz_pam , mod_intercept_form_submit , and mod_lookup_identity Apache modules in the respective packages can be used by Web applications to achieve tighter interaction with external authentication and identity sources, such as Identity Management in Red Hat Enterprise Linux. Simultaneous maintaining of TGTs for multiple KDCs Kerberos version 1.10 added a new cache storage type, DIR:, which allows Kerberos to maintain Ticket Granting Tickets (TGTs) for multiple Key Distribution Centers (KDCs) simultaneously and auto-select between them when negotiating with Kerberized resources. Red Hat Enterprise Linux 6.4 and later includes SSSD enhanced to allow the users to select the DIR: cache for users that are logging in via SSSD. This feature is introduced as a Technology Preview. Package: sssd-1.9.2-129

Commands:
Chapter 3. Using SAML to secure applications and services This section describes how you can secure applications and services with SAML using either Red Hat build of Keycloak client adapters or generic SAML provider libraries. 3.1. Red Hat build of Keycloak Java adapters Red Hat build of Keycloak comes with a range of different adapters for Java application. Selecting the correct adapter depends on the target platform. 3.1.1. Red Hat JBoss Enterprise Application Platform 3.1.1.1. 8.0 Beta Red Hat build of Keycloak provides a SAML adapter for Red Hat Enterprise Application Platform 8.0 Beta. However, the documentation is not currently available, and will be added in the near future. 3.1.1.2. 6.4 and 7.x Existing applications deployed to Red Hat JBoss Enterprise Application Platform 6.4 and 7.x can leverage adapters from Red Hat Single Sign-On 7.6 in combination with the Red Hat build of Keycloak server. For more information, see the Red Hat Single Sign-On documentation .

Commands: