1. You require a Red Hat Enterprise Linux operating system. Each node in the mesh requires a static IP address, or a resolvable DNS hostname that automation controller can access.
2. Ensure that you have the minimum requirements for the RHEL virtual machine before proceeding. For more information, see the Red Hat Ansible Automation Platform system requirements.

3. Deploy the RHEL instances within the remote networks where communication is required. For information about creating virtual machines, see Creating Virtual Machines in the Red Hat Enterprise Linux documentation. Remember to scale the capacity of your virtual machines sufficiently so that your proposed tasks can run on them.

   • RHEL ISOs can be obtained from access.redhat.com.
   • RHEL cloud images can be built using Image Builder from console.redhat.com.

Procedure

1. SSH into each of the RHEL instances and perform the following steps. Depending on your network access and controls, SSH proxies or other access models might be required.

   Use the following command:

   ssh [username]@[host_ip_address]

   For example, for an Ansible Automation Platform instance running on Amazon Web Services.

   ssh ec2-user@10.0.0.6

2. Create or copy an SSH key that can be used to connect from the hop node to the execution node in later steps. This can be a temporary key used just for the automation mesh configuration, or a long-lived key. The SSH user and key are used in later steps.

3. Enable your RHEL subscription with baseos and appstream repositories. Ansible Automation Platform RPM repositories are only available through subscription-manager, not the Red Hat Update Infrastructure (RHUI). If you attempt to use any other Linux footprint, including RHEL with RHUI, this causes errors.

   sudo subscription-manager register --auto-attach

   If Simple Content Access is enabled for your account, use:

   sudo subscription-manager register

   For more information about Simple Content Access, see Getting started with simple content access.

4. Enable Ansible Automation Platform subscriptions and the proper Red Hat Ansible Automation Platform channel:

   # subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms for RHEL 8
   
   # subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms for RHEL 9

5. Ensure the packages are up to date:

   sudo dnf upgrade -y

6. Install the ansible-core packages:

   sudo dnf install -y ansible-core

Procedure

1. From the navigation panel of automation controller, select Instances.

2. On the Instances list page, click Add. The Create new Instance window opens.

   

   An instance requires the following attributes:

   • Host Name: (required) Enter a fully qualified domain name (public DNS) or IP address for your instance. This field is equivalent to hostname for installer-based deployments.

     Note

     If the instance uses private DNS that cannot be resolved from the control cluster, DNS lookup routing fails, and the generated SSL certificates is invalid. Use the IP address instead.

   • Optional: Description: Enter a description for the instance.
   • Instance State: This field is auto-populated, indicating that it is being installed, and cannot be modified.
   • Listener Port: This port is used for the receptor to listen on for incoming connections. You can set the port to one that is appropriate for your configuration. This field is equivalent to listener_port in the API. The default value is 27199, though you can set your own port value.

   • Instance Type: Only execution and hop nodes can be created. Operator based deployments do not support Control or Hybrid nodes.

     Options:

     • Enable Instance: Check this box to make it available for jobs to run on an execution node.
     • Check the Managed by Policy box to enable policy to dictate how the instance is assigned.

     • Check the Peers from control nodes box to enable control nodes to peer to this instance automatically. For nodes connected to automation controller, check the Peers from Control nodes box to create a direct communication link between that node and automation controller. For all other nodes:

       • If you are not adding a hop node, make sure Peers from Control is checked.
       • If you are adding a hop node, make sure Peers from Control is not checked.
       • For execution nodes that communicate with hop nodes, do not check this box.

     • To peer an execution node with a hop node, click the icon next to the Peers field.

       The Select Peers window is displayed.

       Peer the execution node to the hop node.

3. Click Save.

   

4. To view a graphical representation of your updated topology, see Topology viewer.

   Note

   Execute the following steps from any computer that has SSH access to the newly created instance.

5. Click the icon next to Install Bundle to download the tar file that includes this new instance and the files necessary to install the created node into the automation mesh.

   

   The install bundle contains TLS certificates and keys, a certificate authority, and a proper Receptor configuration file.

   receptor-ca.crt
   work-public-key.pem
   receptor.key
   install_receptor.yml
   inventory.yml
   group_vars/all.yml
   requirements.yml

6. Extract the downloaded tar.gz Install Bundle from the location where you downloaded it. To ensure that these files are in the correct location on the remote machine, the install bundle includes the install_receptor.yml playbook. The playbook requires the Receptor collection. Run the following command to download the collection:

   ansible-galaxy collection install -r requirements.yml

7. Before running the ansible-playbook command, edit the following fields in the inventory.yml file:

   all:
     hosts:
       remote-execution:
         ansible_host: 10.0.0.6
         ansible_user: <username> # user provided
     ansible_ssh_private_key_file: ~/.ssh/<id_rsa>

   • Ensure ansible_host is set to the IP address or DNS of the node.
   • Set ansible_user to the username running the installation.
   • Set ansible_ssh_private_key_file to contain the filename of the private key used to connect to the instance.
   • The content of the inventory.yml file serves as a template and contains variables for roles that are applied during the installation and configuration of a receptor node in a mesh topology. You can modify some of the other fields, or replace the file in its entirety for advanced scenarios. For more information, see Role Variables.

8. For a node that uses a private DNS, add the following line to inventory.yml:

    ansible_ssh_common_args: <your ssh ProxyCommand setting>

   This instructs the install-receptor.yml playbook to use the proxy command to connect through the local DNS node to the private node.

9. When the attributes are configured, click Save. The Details page of the created instance opens.
10. Save the file to continue.

11. The system that is going to run the install bundle to setup the remote node and run ansible-playbook requires the ansible.receptor collection to be installed:

    ansible-galaxy collection install ansible.receptor

    or

    ansible-galaxy install -r requirements.yml

    • Installing the receptor collection dependency from the requirements.yml file consistently retrieves the receptor version specified there. Additionally, it retrieves any other collection dependencies that might be needed in the future.
    • Install the receptor collection on all nodes where your playbook will run, otherwise an error occurs.

12. If receptor_listener_port is defined, the machine also requires an available open port on which to establish inbound TCP connections, for example, 27199. Run the following command to open port 27199 for receptor communication:

    sudo firewall-cmd --permanent --zone=public --add-port=27199/tcp

13. Run the following playbook on the machine where you want to update your automation mesh:

    ansible-playbook -i inventory.yml install_receptor.yml

    After this playbook runs, your automation mesh is configured.

    

Procedure

1. From the navigation panel, select Administration → Instance Groups.
2. Click Add → Add instance group.

3. Enter the appropriate details into the following fields:

   • Name: Names must be unique and must not be named "controller".
   • Policy instance minimum: Enter the minimum number of instances to automatically assign to this group when new instances come online.

   • Policy instance percentage: Use the slider to select a minimum percentage of instances to automatically assign to this group when new instances come online.

     Note

     Policy instance fields are not required to create a new instance group. If you do not specify values, then the Policy instance minimum and Policy instance percentage default to 0.

   • Max concurrent jobs: Specify the maximum number of forks that can be run for any given job.

   • Max forks: Specify the maximum number of concurrent jobs that can be run for any given job.

     Note

     The default value of 0 for Max concurrent jobs and Max forks denotes no limit. For more information, see Instance group capacity limits in the Automation controller Administration Guide.

4. Click Save.

Procedure

1. Select the Instances tab of the Instance Groups window.
2. Click Associate.

3. Click the checkbox next to one or more available instances from the list to select the instances you want to associate with the instance group:

   

4. In the following example, the instances added to the instance group displays along with information about their capacity:

   

Procedure

1. The Templates list view shows job templates that are currently available. From this screen you can launch , edit , and copy a workflow job template.
2. Select the job you want and click the icon.
3. Select the Instance Group on which you want to run the job. Note that a System Administrator must grant you or your team permissions to be able to use an instance group in a job template. If you select multiple jobs templates, the order in which you select them sets the execution precedence.
4. Click Next.
5. Click Launch.

Procedure

1. Create a secret using the following command:

   oc create secret generic ee-pull-secret \
        --from-literal=username=<username> \
        --from-literal=password=<password> \
        --from-literal=url=registry.redhat.io
   
   oc edit automationcontrollers <instance name>

2. Add ee_pull_credentials_secret and ee-pull-secret to the specification using:

   spec.ee_pull_credentials_secret=ee-pull-secret

3. To manage instances from the automation controller UI, you must have System Administrator or System Auditor permissions.