Chapter 2. Installing and configuring the resource-optimization components Installing resource optimization involves installing packages, configuring settings and enabling local services. This can be done manually, or with an Ansible playbook provided by Red Hat. Note Pay as you go (PAYG) customers need to register the Insights client with subscription-manager (RHSM). There are two ways to register with subscription-manager: Using activation keys (recommended) Using your user name and password For more information about how to register the Insights client, refer to Client Configuration Guide for Red Hat Insights . Table 2.1. Compatibility information RHEL Versions Cloud Provider Resource Optimization Compatibility 8.x-9.x AWS Yes (x86_64 and ARM 64-bit) 7.7-7.9 AWS Yes (x86_64 and ARM 64-bit) 7.0-7.6 AWS No 6.x AWS No Prerequisites The following applications and configurations need to be installed or confirmed before the resource optimization service can be used: Cloud marketplace RHEL instance is configured. The Insights client is installed on the system and is operational. If you want to use Ansible to install or uninstall the resource optimization service: The Ansible repository is enabled and the Ansible client is installed on each system. The system administrator can run Ansible Playbooks. 2.1. Installing resource-optimization components There are a few options for installing resource-optimization components. Choose whichever works with your Ansible workflow. 2.1.1. Installing Ansible and running the resource-optimization installation playbook The use of Ansible is recommended to expedite the installation process. This procedure installs the Ansible client and runs the Ansible Playbook on your system. Cloud marketplace images on Amazon Web Services (AWS) are configured to use repositories hosted by the cloud provider. Currently, these repositories do not contain the Ansible client, so you must perform the following steps to enable the Ansible repository on your cloud marketplace - managed RHEL system. Note On RHEL 8.6 and later, and RHEL 9.0, Red Hat recommends using Ansible Core. For more information, see Updates to using Ansible in RHEL 8.6 and 9.0 . Prerequisites On RHEL 8, the Ansible repository is enabled. Procedure on RHEL 8 Install Ansible: Procedure on RHEL 7 Enable the Subscription-Manager repository and register the system Optionally, attach your system to a subscription pool Enable the required Ansible repository. Install Ansible: If you are using RHEL PAYG and want to use RHUI update servers only, disable the Subscription-Manager repository: 2.1.2. Installing resource optimization when Ansible is already installed Once Ansible is installed, proceed to complete the installation of the resource optimization service. Procedure Download the Ansible Playbook with the following command: Set localhost in Ansible inventory by appending the line localhost to /etc/ansible/hosts . Run the Ansible Playbook: The system will show in Insights immediately in a "Waiting for data" state, and data and suggestions will be available the day after registering. Verification step Data files with a timestamp will appear under /var/log/pcp/pmlogger/ros and after a few minutes, you can verify metrics are being collected: 2.1.3. Installing resource optimization without installing or using Ansible Procedure If you choose not to use Ansible for installation, use the following manual installation procedure: . Ensure the latest version of insights-client is installed. Set core_collect=True in /etc/insights-client/insights-client.conf Install the Performance Co-Pilot (PCP) toolkit. Create the PCP configuration file /var/lib/pcp/config/pmlogger/config.ros with this content: To configure pmlogger to gather the metrics required by resource optimization, add this line to /etc/pcp/pmlogger/control.d/local : Note In versions of this procedure, this line began with LOCALHOSTNAME n y . The procedure now advises that you use LOCALHOSTNAME n n , which disables the usage of pmsocks . For more information about pmsocks , refer to the man page for pmsocks . Start and enable the required PCP services. Re-register insights-client and upload the archive. The system will show in Insights immediately in a "Waiting for data" state, and data and suggestions will be available the day after registering. Verification step Data files with a timestamp will appear under /var/log/pcp/pmlogger/ros and after a few minutes, you can verify metrics are being collected: 2.2. Enabling Kernel Pressure Stall Information (PSI) PSI provides a canonical way to see resource pressure increases as they develop. There are pressure metrics for three major resources: memory, CPU, and input/output (I/O). PSI is available on RHEL 8 and newer versions, and is disabled by default. When PSI is enabled, the resource optimization service can augment its findings and provide more details and better suggestions. Enabling PSI is strongly recommended to identify peaks. Procedure Edit the /etc/default/grub file and append psi=1 at the end of the GRUB_CMDLINE_LINUX line (mind the quotes). Regenerate the grub configuration file. Reboot the system. Note Enabling PSI incurs in a slight (<1%) performance hit. Verification step When PSI is enabled, files for CPU, memory and IO appear under /proc/pressure . 2.3. Enabling notifications and integrations in the resource optimization service You can enable the notifications service on Red Hat Hybrid Cloud Console to send notifications whenever the resource optimization service detects an issue and generates a suggestion. Using the notifications service frees you from having to continually check the Red Hat Insights for Red Hat Enterprise Linux dashboard for recommendations. For example, you can configure the notifications service to automatically send an email message whenever the resource optimization service generates a suggestion. Enabling the notifications service requires three main steps: First, an Organization Administrator creates a User access group with the Notifications administrator role, and then adds account members to the group. , a Notifications administrator sets up behavior groups for events in the notifications service. Behavior groups specify the delivery method for each notification. For example, a behavior group can specify whether email notifications are sent to all users, or just to Organization administrators. Finally, users who receive email notifications from events must set their user preferences so that they receive individual emails for each event. In addition to sending email messages, you can configure the notifications service to pull event data in other ways: Using an authenticated client to query Red Hat Insights APIs for event data. Using webhooks to send events to third-party applications that accept inbound requests. Integrating notifications with applications such as Splunk to route resource optimization recommendations to the application dashboard. Additional resources For more information about how to set up notifications for resource optimization recommendations, see Configuring notifications on the Red Hat Hybrid Cloud Console and Integrating the Red Hat Hybrid Cloud Console with third-party applications .

Commands:
yum install ansible-core -y
subscription-manager config --rhsm.manage_repos=1 subscription-manager register
subscription-manager attach --pool xxxxxxxx
subscription-manager repos --enable=rhel-7-server-ansible-2.9-rpms
yum install ansible -y
subscription-manager config --rhsm.manage_repos=0
curl -O https://raw.githubusercontent.com/RedHatInsights/ros-backend/v2.0/ansible-playbooks/ros_install_and_set_up.yml
ansible-playbook -c local ros_install_and_set_up.yml
ls -l /var/log/pcp/pmlogger/ros pmlogsummary /var/log/pcp/pmlogger/ros/
yum update insights-client
sudo yum install pcp
log mandatory on default { hinv.ncpu mem.physmem mem.util.available disk.dev.total kernel.all.cpu.idle kernel.all.pressure.cpu.some.avg kernel.all.pressure.io.full.avg kernel.all.pressure.io.some.avg kernel.all.pressure.memory.full.avg kernel.all.pressure.memory.some.avg } [access] disallow .* : all; disallow :* : all; allow local:* : enquire;
LOCALHOSTNAME n n PCP_LOG_DIR/pmlogger/ros -r -T24h10m -c config.ros -v 100Mb
sudo systemctl enable pmcd pmlogger sudo systemctl start pmcd pmlogger
sudo insights-client --register
ls -l /var/log/pcp/pmlogger/ros pmlogsummary /var/log/pcp/pmlogger/ros/
sudo grub2-mkconfig -o /boot/grub2/grub.cfg