Red Hat Customer Portal

Pre-installation checks:

• Red Hat Insights is supported in Satellite 5.7 and later.

• Satellite Organizations with Insights must be running in Connected mode. Any firewalls or proxies through which the Satellite server communicates to Red Hat must allow https communications to https://access.redhat.com . If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy?

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

2Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

3Install the Red Hat access plugin for Satellite 5.

​[root@server ~]# yum install redhat-access-plugin-sat5

4Restart Satellite.

​[root@server ~]# rhn-satellite restart

5Enable Red Hat Insights.

Log in to the Satellite administrator account. Navigate to Admin --> Insights. Before enabling Insights, click Test Conection to Red Hat Insights API. If the test is successful, a circled green checkmark appears. If unsuccessful, a red circle and a log appear. When the test is successful, select Enable Insights Service then click Update. The Red Hat Insights GUI pieces now appear in Satellite.

6Install RPM and register to Red Hat Insights.

An additional step is required for systems registered with RHN classic. For more information, refer to Registering Red Hat Insights with RHN Classic on the Customer portal.

There are multiple ways to automate this process. We've provided several options for popular configuration management tools below:

• Puppet
• Chef
• Ansible

To install and register a system manually:

[root@server ~]# yum install redhat-access-insights

​​[root@server ~]# redhat-access-insights --register

If you have a web based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy .

To install and register a system through Red Hat Satellite:

Navigate to Systems > Insights > Setup as an Organization Administrator. Select the systems to install the redhat-access-insights RPM onto, then click "Apply."

Check the status of the RPM installation by navigating to Schedule > Pending Actions.

The RPM installation will be shown on the Completed Actions page when finished.

See your results.

Shortly after you execute redhat-access-insights --register on at least one machine, navigate to Systems > Overview in Satellite. Find the system you registered. The status should either be a green check or a red exclamation symbol.

If you see a red exclamation symbol, click it to see reports about your system.

To see an overview of all system reports, navigate to Systems > Insights.

Pre-installation checks:

• Red Hat Insights is supported in Satellite 6.1 and later.

• Ensure that you’ve synchronized the latest RHEL 6.7 and RHEL 7.1.z RPMs to your Satellite, and made them available to your clients.

• To make the Red Hat Satellite Server an Insights client, follow the Customer Portal registration instructions and run the following command prior to installing the redhat-access-insights client:

  ​[root@server ~]# yum update python-requests

• A manifest must be downloaded and imported into the Satellite Organization in which Insights will be enabled. For more information on managing manifests, refer to the Creating a Subscription Manifest chapter in the official Satellite 6 Installation Guide.

• Satellite Organizations with Insights must be running in Connected mode. Any firewalls or proxies through which the Satellite server communicates to Red Hat must allow https communications to https://cert-api.access.redhat.com .

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

Verify connection to Red Hat Insights.

Verify that the Satellite server can successfully communicate with Red Hat Insights. In the Satellite UI, navigate to Insights > Manage. Verify that the engine connection status is "Connected" and the account number displayed is correct for your organization.

Install the Insights RPM and register your system to Red Hat Insights.

There are multiple ways to automate this process. We've provided several options for popular configuration management tools below:

• Puppet
• Chef
• Ansible

If you are using Red Hat Satellite’s configuration management provided by Puppet this process can be automated by applying the preinstalled Puppet class access_insights_clients. This class can be imported from the Puppet Master into the appropriate Puppet environment and applied to hosts that you wish to subscribe to Red Hat Insights. For more information on this topic, refer to the Creating a Host Group chapter in the official Satellite 6 User Guide .

To install and register a system manually:

[root@server ~]# yum install redhat-access-insights

​​[root@server ~]# redhat-access-insights --register

Note: If your system is registered with RHN Classic, an additional step must be taken to register to Red Hat Insights. For more information, refer to Registering Red Hat Insights with RHN Classic .

Note: If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy?

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .

Assign Red Hat Insights roles to users.

By default, only administrators can view Insights Report and Configuration screens. However, you can give non-admin users access to the Insights screens by assigning them the appropriate roles as follows:

• To give users access to all Insights screens, including the Manage screen, assign them the Insights Admin role. Users must also be granted the view_content_host permission.

• To give users Insights report and rule viewing access, assign them the Insights Viewer role. These users must also be granted the view_content_host permission.

For more information on roles, refer to the official Satellite 6 documentation .

Pre-installation checks:

• Red Hat Insights is supported in Red Hat CloudForms version 4.0 and later.

• The CloudForms appliance must either be registered to a Satellite Server, version 6.1.5 or later, or to the Customer Portal Subscription Management hosted subscription service.

• Smart State Analysis capability is enabled for Red Hat Enterprise Linux virtual machines.

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

Verify CloudForms appliance registration.

All appliances configured for the UI role to view Red Hat Insights reports must be registered for Red Hat updates. In the CloudForms Management Engine UI, navigate to Configure > Configuration. Select a zone and verify that the appropriate appliance is registered.

Note: The Satellite Server organization to which the CloudForms appliance is registered must have Insights enabled.

Configure Smart State Analysis.

Configure the Smart State Analysis profile for your appliances to collect the contents of the file / etc/redhat-access-insights/machined-id .

Install the Insights RPM and register your system to Red Hat Insights.

Important: All virtual machines must be registered to the same Red Hat account as the CloudForms appliance.

There are multiple ways to automate this process. We've provided several options for popular configuration management tools below:

• Puppet
• Chef
• Ansible

To install and register a system manually:

[root@server ~]# yum install redhat-access-insights

​​[root@server ~]# redhat-access-insights --register

Note: If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy?

Run Smart State Analysis on RHEL virtual machines.

A Smart State Analysis must be run once on all RHEL virtual machines you have registered to Red Hat Insights. This step is only required once. If a new virtual machine is created afterward, then a Smart State Analysis need only be run on that new virtual machine after it has been registered to Insights.

For more information on how to configure and run Smart State Analysis, see the official CloudForms documentation .

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .

Assign Red Hat Insights to user roles.

By default, only super administrators can view Insights Report and Configuration screens. You can give non-admin users access to the Insights screens by assigning the appropriate features to their roles.

In addition to the feature controls above, a user can only view Insights reports on those virtual machines to which the user has permission to view in CloudForms.

Pre-installation checks:

• The RHV deployment must be Red Hat Virtualization (RHV) 3.5 or later, and the RHV Manager must be running on Red Hat Enterprise Linux 6.7 or later.

• Firewall rules must allow Red Hat Insights to make outbound connections to https://api.redhat.com:443 and https://cert-api.access.redhat.com:443 .

• Ensure that the RHV Manager can SSH into all individual hypervisor nodes and that the SSH fingerprints have been accepted for all hypervisor nodes. The RHV Manager must have access to all of the individual hypervisors via public key access (defined in the configuration files, or by running --configure .

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

Install the repositories.

Run the following commands in the RHV Manager to access the Red Hat Insights repositories:

sudo yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/insights/insights-client/repo/epel-7/insights-insights-client-epel-7.repo

sudo yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/insights/insights-coordinator-rhev/repo/epel-7/insights-insights-coordinator-rhev-epel-7.repo

Install the Red Hat Insights client.

The following command installs Red Hat Insights in the RHV Manager, which will collect information from all the virtualization hosts in the environment.

​​sudo yum install insights-coordinator-rhev --nogpgcheck

Note: If your system is registered with RHN Classic, an additional step must be taken to register to Red Hat Insights. For more information, refer to Registering Red Hat Insights with RHN Classic .

Note: If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy?

Register your system to Insights.

When configuring the RHV Manager for Red Hat Insights, be sure to have your RHV Manager API and hypervisor SSH information ready. Red Hat Insights will guide you through the configuration.

​​[root@server ~]# insights-coordinator-rhev --configure

Once configured, install Red Hat Insights on the RHV Manager and all of the hypervisor nodes.

​​[root@server ~]# insights-coordinator-rhev --verbose

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface.

The initial analysis results will be available shortly thereafter.

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .

Pre-installation checks:

• The OpenStack deployment must be Red Hat OpenStack Platform (OSP) 7 or later and be set up with the OSP Director.

• The OSP Director node (also referred to as the Undercloud in these directions) must have the rhel-7-server-rh-common-rpms repository added.

• Firewall rules must allow the Insights Coordinator for OpenStack to make outbound connections to https://api.access.redhat.com:443 and https://cert-api.access.redhat.com:443 .

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

Install the Red Hat Insights for OpenStack private beta repositories on the Undercloud.

To start the installation, the Red Hat Insights for OpenStack private beta repositories must be installed on the OSP Director node.

​​[root@undercloud ~]# yum-config-manager --add-repo http://copr.fedorainfracloud.org/coprs/insights/insights-client/repo/epel-7/insights-insights-client-epel-7.repo

​​[root@undercloud ~]# yum-config-manager --add-repo http://copr.fedorainfracloud.org/coprs/insights/insights-coordinator-rhosp/repo/epel-7/insights-insights-coordinator-rhosp-epel-7.repo

Install the Red Hat Insights for OpenStack private beta components.

The following command will install the Insights Coordinator for OpenStack on the Undercloud node:

​​[root@undercloud ~]# yum install insights-coordinator-rhosp --nogpgcheck -y

The following command will install the client on the Undercloud and Overcloud nodes and register the stack with Red Hat Insights:

​​[root@undercloud ~]# redhat-access-insights --register --no-schedule --no-upload --silent

The client cron job and coordinator cron jobs cannot be symlinked simultaneously or conflicts will occur. The following command will remove the symlink that will have been created for the client in /etc/cron.daily :

​​[stack@undercloud ~]# redhat-access-insights --no-schedule

Edit /etc/redhat-access-insights/redhat-access-insights.conf and add no_schedule=True . This value should already exist at the bottom of the file so it will need to be uncommented and changed to True, but should it not exist, it will need to be added.

The following command will configure the coordinator and client installations:

​​[root@undercloud ~]# insights-coordinator-rhosp --configure

The coordinator will attempt to auto-configure the communication to Red Hat based on the subscription-management information on the Undercloud node. However, you can also connect using a proxy and/or using Red Hat Network Classic credentials is available but requires additional configuration steps .

If issues arise with these commands, examine /etc/redhat-access-insights/redhat-access-insights.conf and ensure that everything is set properly.

Lastly, run the following command to complete the installation and view any messages from the coordinator during the execution and upload of the archive:

​​[root@undercloud ~]# insights-coordinator-rhosp --verbose

When the command finishes, the Insights Coordinator will have uploaded the initial deployment information to Red Hat Insights. You should be able to immediately see your stack in the Insights user interface.

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .

Pre-installation checks:

• The Red Hat Enterprise Linux (RHEL) 7.0 or later host must be configured to run containers.

• RHEL firewall rules must allow Red Hat Insights to make outbound connections to https://api.access.redhat.com:443 and https://cert-api.access.redhat.com:443 .

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Register all systems for updates in order to resolve software dependencies.

​[root@server ~]# subscription-manager register --auto-attach

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic?

Enable the Red Hat Insights repository.

To start the installation, enable the Red Hat Insights repository:

​​[root@server ~]# yum-config-manager --add-repo http://copr.fedorainfracloud.org/coprs/insights/insights-client-test/repo/epel-7/insights-insights-client-test-epel-7.repo

Install the Red Hat Insights client.

The following command will install the Red Hat Insights client:

​​[root@server ~]# install insights-client -y --nogpgcheck

Note: System registration with Red Hat Network Classic follows a different procedure. For more information, refer to How to register a system with RHN classic? .

Note: If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy? .

Run and register the Red Hat Insights client.

The following command will run and register the Insights client:

​​[root@server ~]# insights-client --container --register

Note: If your system is registered with RHN Classic, an additional step must be taken to register to Red Hat Insights. For more information, refer to Registering Red Hat Insights with RHN Classic .

After running the Insights client, it will upload initial system and image information to Red Hat Insights. You should be able to immediately see your system and image information in the Insights user interface.

The initial analysis results will be available shortly thereafter.

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .

Pre-installation checks:

Before installing Red Hat Insights, the following prerequisites must be met:

OpenShift deployment must be version 3.2 or later.

Firewall rules must allow Red Hat Insights to make outbound connections to https://api.redhat.com:443 and https://cert-api.access.redhat.com:443 .

Activate your evaluation.

Note: If you have purchased an Insights subscription, skip this step and proceed to the next step.

To begin evaluating Red Hat Insights, visit https://access.redhat.com/insights/evaluation to activate any available evaluations associated with your account. This step must be completed prior to any system registration with Insights.

Enable the Insights repositories.

To start the installation, run the following RHEL version-specific commands on the OpenShift master to obtain the required Insights repositories:

• For RHEL 6:

​[root@server ~]$ sudo yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/insights/insights- client/repo/epel-6/insights-insights-client-epel-6.repo

​[root@server ~]$ sudo yum-config-manager --add-repo http://copr.fedorainfracloud.org/coprs/insights/insights-coordinator-ocp/repo/epel-6/insights-insights-coordinator-ocp-epel-6.repo

• For RHEL 7:

​[root@server ~]$ sudo yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/insights/insights-client/repo/epel-7/insights-insights-client-epel-7.repo

​[root@server ~]$ sudo yum-config-manager --add-repo http://copr.fedorainfracloud.org/coprs/insights/insights-coordinator-ocp/repo/epel-7/insights-insights-coordinator-ocp-epel-7.repo

Install the Insights client.

Install the Insights client using the following command:

[root@server ~]$ sudo yum install insights-coordinator-ocp --nogpgcheck

Note: If your system is registered with RHN Classic, an additional step must be taken to register to Red Hat Insights. For more information, refer to Registering Red Hat Insights with RHN Classic .

Note: If you have a web-based proxy between your system and the Internet, you can configure the Insights client to connect through it. For more information, refer to How to access Red Hat Insights through a firewall/Proxy?

Configure and register the Insights client.

The following command will configure and register the Insights client:

​​[root@server ~]$ sudo insights-coordinator-ocp --configure

The Insights OpenShift coordinator relies on an Ansible playbook to gather information from the nodes in your OpenShift deployment. This playbook uses the Ansible inventory file, usually `/etc/ansible/hosts`, to identify the nodes. You will need to copy your Ansible inventory file to `/etc/ansible/hosts`, if necessary. For instance, if you configured OpenShift using the `atomic-openshift-installer` quick installation interactive CLI utility as the ‘root’ user, the inventory file will be located in `~root/.config/openshift/hosts`. However, if you chose a more advanced configuration route, the inventory file could be located elsewhere. Regardless of where the inventory file resides, it must get copied to `/etc/ansible/hosts` on the OpenShift master.

Once the coordinator is configured and registered, use the following command to run Insights and gather data for you OpenShift deployment:

​​[root@server ~]$ sudo insights-coordinator-ocp --verbose

See your results.

After registration, the Insights client will upload initial system metadata to Red Hat Insights. You should be able to immediately see your system in the Insights user interface at https://access.redhat.com/insights/ .