Chapter 1. Getting Started with Ansible in Satellite

Use this guide to configure Satellite to use Ansible for remote execution.

1.1. Supported Ansible Versions

Satellite uses Ansible as provided by the base operating system of Satellite Server or any Capsules for remote execution. Therefore, the supported version of Ansible depends on your base OS configuration.

1.2. Configuring Your Satellite to Run Ansible Roles

In Satellite, you can import Ansible roles to help with automation of routine tasks. Ansible is enabled by default on Satellite Server.

Ansible paths

Satellite imports Ansible roles and variables from paths based on configuration in /etc/ansible/ansible.cfg. Satellite then runs imported roles from paths based on configuration in /etc/foreman-proxy/ansible.cfg. In both cases, Satellite reads the paths from roles_path and collections_paths directives. Keep these two cfg files in sync, otherwise you might import roles that cannot be run or you will not see roles you can run.

If none of the paths are specified in the configuration files, the following default paths are used:

  • /etc/ansible/roles
  • /usr/share/ansible/roles
  • /etc/ansible/collections
  • /usr/share/ansible/collections

Procedure

  1. Configure your Ansible paths on the Satellite Server and all Capsule Servers where you want to use the roles.
  2. Add the roles to a directory in an Ansible path on the Satellite Server and all Capsule Servers from where you want to use the roles. If you want to use custom or third party Ansible roles, ensure to configure an external version control system to synchronize roles between Satellite Server and Capsule Servers.

  3. On all Capsule Servers that you want to use to run Ansible roles on hosts, enable the Ansible plug-in: 

    # satellite-installer --scenario capsule \
--enable-foreman-proxy-plugin-ansible
  4. Distribute SSH keys to enable Capsules to connect to hosts using SSH. For more information, see Distributing SSH Keys for Remote Execution in Managing Hosts. Satellite runs Ansible roles the same way it runs remote execution jobs.
  5. Import the Ansible roles into Satellite.
  6. Proceed to Chapter 2, Using Ansible Roles to Automate Repetitive Tasks on Clients.

1.3. Enabling Ansible Integration with Satellite

Perform the following procedure to enable the Ansible plug-in on your Satellite Server.

Procedure

  • Enable the Ansible plug-in on your Satellite Server: 

    # satellite-installer \
--enable-foreman-plugin-ansible \
--enable-foreman-proxy-plugin-ansible

1.4. Importing Ansible Roles and Variables

You can import Ansible roles and variables from the Ansible paths on Satellite Server or Capsule that has Ansible enabled.

Note that some roles take longer to import than others.

Prerequisite

  • Ensure that the roles and variables that you import are located in the Ansible paths on all Capsules from where you want to use the roles.

Procedure

  1. In the Satellite web UI, navigate to Configure > Roles.
  2. Click Import to select the Capsule from which you want to import.
  3. Select the roles that you want to import.
  4. Click Submit.

1.5. Overriding Ansible Variables in Satellite

If you run Ansible roles in Satellite, you can use Satellite to override Ansible variables for those roles.

The following procedure refers to hosts and host groups. For more information, see Managing Hosts.

Precedence in Overriding Variables

If you use an Ansible role to run a task as a user that is not the Effective User, there is a strict order of precedence for overriding Ansible variables. To ensure the variable that you override follows the correct order of precedence, see Variable precedence: Where should I put a variable?

Prerequisite

Procedure

  1. In the Satellite web UI, navigate to Configure > Variables.
  2. Select the Ansible variable that you want to override and manage with Satellite.
  3. In the Default Behavior area, select the Override checkbox.
  4. In the Parameter Type field, select the value type for validation such as string or boolean. The types array and hash have further options for handling upon a variable match. For more information, see the Prioritize Attribute Order area below.
  5. In the Default Value field, enter the default value that you want to use if there is no match for the variable.
  6. Optional: If you do not want to display the value of the variable as plain text in the Satellite web UI, select the Hidden Value checkbox to display the content of the variable as asterisks. This is useful for sensitive values such as passwords or secret tokens.

  7. Optional: Expand the Optional Input Validator area and specify conditions that will be used to validate concrete values of the variable:

    • Select Required if you want to enforce users to fill in this variable.

    • In the Validator Type field, select how the value will be validated:

      • list – The value will be validated against an enumeration of allowed values.
      • regex – The value will be validated against a regular expression pattern.

  8. Optional: In the Prioritize Attribute Order area, specify the order of priority to match an override with a host by host attributes. Order at the top takes higher precedence. The first match wins.

    You can combine multiple attributes into a single matcher key using a comma as the AND operation. For example, the matcher key of hostgroup, environment would expect matchers such as hostgroup = "web servers" AND environment = production.

    If you use the parameter type array or hash, you can further set:

    • Merge Overrides – Merges members of the arrays/hashes instead of replacing the whole array or hash. If the hashes contain the same key, the value is overwritten by the value of the host.
    • Merge Default – Adds the default value to the array or hash.
    • Avoid Duplicates – Ensures that the values in the array or hash are unique.
  9. Optional: Expand the Specify Matchers area and specify criteria for selecting hosts on which the variable overrides.
  10. To save the override settings, click Submit.

To use the Ansible variable, add the variable as a parameter to your host or host group, or add the variable as a global parameter.

Adding the Variable to a Host

  1. In the Satellite web UI, navigate to Hosts > All Hosts and select the host that you want to use.
  2. Click the Ansible tab, and in the Variables area, click the pencil icon to edit the value of the variable.
  3. Click the tick icon to accept the value of the changed variable or the cross icon to cancel the change.

Adding the Variable to a Host Group

  1. In the Satellite web UI, navigate to Configure > Host Groups, and select the host group that you want to use.
  2. Click the Parameters tab, and in the Host Group Parameters area, click Add Parameter.
  3. In the Name field, add the Ansible variable name.
  4. From the Type list, select the type of the variable for validation.
  5. In the Value field, enter the value for the variable.

Adding the Variable as a Global Parameter

  1. In the Satellite web UI, navigate to Configure > Global Parameters, and click Create Parameter.
  2. In the Name field, add the Ansible variable name.
  3. From the Type list, select the type of the variable for validation.
  4. In the Value field, enter the value for the variable.
  5. Optional: If you do not want to display the Ansible variable in plain text, select the Hidden Values checkbox to display the content of the variable as asterisks in the Satellite web UI.

1.6. Adding Red Hat Enterprise Linux System Roles

Red Hat Enterprise Linux System Roles is a configuration interface to remotely manage Red Hat Enterprise Linux servers. You can use Red Hat Enterprise Linux System Roles to add Ansible roles in Satellite. Using Ansible Roles in Satellite can make configuration faster and easier.

Support levels for some of the Red Hat Enterprise Linux System Roles might be in Technology Preview. For up-to-date information about support levels and general information about Red Hat Enterprise Linux System Roles, see Red Hat Enterprise Linux System Roles.

Before subscribing to the Extras channels, see the Red Hat Enterprise Linux Extras Product Life Cycle article.

Procedure

  1. Ensure that the following repository is enabled:

    • On Red Hat Enterprise Linux 8, ensure that the Appstream repository is enabled: 

      # subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms

      You must enable an Appstream repository that is designated for your architecture. For more information, see RHEL 8 repositories.

    • On Red Hat Enterprise Linux 7, ensure that the Extras repository is enabled: 

      # subscription-manager repos --enable=rhel-7-server-extras-rpms

  2. Install the rhel-system-roles package: 

    # satellite-maintain packages install rhel-system-roles

    The rhel-system-roles package downloads to /usr/share/ansible/roles/. You can view and make any modifications that you want to the files before you import.

  3. In the Satellite web UI, navigate to Configure > Roles and click the Capsule that contains the roles that you want to import.
  4. From the list of Ansible roles, select the checkbox of the roles you want to import, and then click Update.

You can now assign Ansible roles to hosts or host groups. For more information, see Section 2.1, “Assigning Ansible Roles to an Existing Host”.

You can also add the modules contained in these roles to your Ansible playbooks by adding them to Ansible Job Templates. You must include the hosts:all line in the job template. For more information, see Red Hat Enterprise Linux (RHEL) System Roles.

1.7. 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

  1. In the Satellite web UI, navigate to Content > Products.
  2. Select the required product name.
  3. In the Products window, select the name of a product that you want to create a repository for.
  4. Click the Repositories tab, and then click New Repository.

  5. In the Name field, enter a name for the repository.

    The Label field is populated automatically based on the name.

  6. From the Type list, select ansible collection.

  7. 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/.

  8. 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 Install multiple collections with a requirements file in Galaxy User Guide.

  9. Authenticate.

    1. 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.

    2. 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.

    3. To sync Satellite from Satellite, leave both authentication fields blank.
  10. Click Save.
  11. Navigate to the Ansible Collections repository.
  12. From the Select Action menu, select Sync Now.