Red Hat Ansible Automation Platform operations guide

Procedures

1. Enter your Red Hat username and password.

2. Click Get Subscriptions.

   Note

   You can also use your Satellite username and password if your cluster nodes are registered to Satellite through Subscription Manager.

3. Review the End User License Agreement and select I agree to the End User License Agreement.
4. Click Submit.
5. Once your subscription has been accepted, the license screen displays and navigates you to the Dashboard of the Ansible Automation Platform interface. You can return to the license screen by clicking the Settings icon ⚙ and selecting the License option from the Settings screen.

Uploading with the interface

1. Complete steps to generate and download the manifest file
2. Log in to Red Hat Ansible Automation Platform.
3. If you are not immediately prompted for a manifest file, go to Settings and select the License option.
4. Make sure the Username and Password fields are empty.
5. Click Browse and select the manifest file.
6. Click Next.
7. Review the End User License Agreement and select I agree to the End User License Agreement.
8. Click Submit.
9. Once your subscription has been accepted, the license screen displays and navigates you to the Dashboard of the Ansible Automation Platform interface. You can return to the license screen by clicking the Settings icon ⚙ and selecting the License option from the Settings screen.

Procedure

1. From the Subscription Allocations page, click New Subscription Allocation.
2. Enter a name for the allocation so that you can find it later.
3. Select Type: Satellite 6.8 as the management application.
4. Click Create.

Procedure

1. From the Subscription Allocations page, click on the name of the Subscription Allocation to which you would like to add a subscription.
2. Click the Subscriptions tab.
3. Click Add Subscriptions.
4. Enter the number of Ansible Automation Platform Entitlement(s) you plan to add.
5. Click Submit.

Procedure

1. From the Subscription Allocations page, click on the name of the Subscription Allocation to which you would like to generate a manifest.
2. Click the Subscriptions tab.
3. Click Export Manifest to download the manifest file.

Procedure

1. Go to the directory that contains setup.sh

2. Create ./group_vars/automationcontroller by running the following command:

   touch ./group_vars/automationcontroller

   Copy to Clipboard Toggle word wrap

3. Paste the following content into ./group_vars/automationcontroller. Adjust the settings to fit your environment:

   # Automation Hub Registry
   registry_username: 'your-automation-hub-user'
   registry_password: 'your-automation-hub-password'
   registry_url: 'automationhub.example.org'
   registry_verify_ssl: False
   
   ## Execution Environments
   control_plane_execution_environment: 'automationhub.example.org/ee-supported-rhel8:latest'
   
   global_job_execution_environments:
     - name: "Default execution environment"
       image: "automationhub.example.org/ee-supported-rhel8:latest"
     - name: "Minimal execution environment"
       image: "automationhub.example.org/ee-minimal-rhel8:latest"

   Copy to Clipboard Toggle word wrap

4. Run the ./setup.sh script

   $ ./setup.sh

   Copy to Clipboard Toggle word wrap

Verification

1. Log in to Ansible Automation Platform as a user with system administrator access.
2. Go to Administration → Execution Environments.
3. In the Image column, confirm that the execution environment image location has changed from the default value of <registry url>/ansible-automation-platform-<version>/<image name>:<tag> to <automation hub url>/<image name>:<tag>.

Procedure

1. On your automation controller, navigate to Settings.
2. Select Miscellaneous System settings from the list of System options.

3. In the REMOTE_HOST_HEADERS field, enter the following values:

   [
     "HTTP_X_FORWARDED_FOR",
     "REMOTE_ADDR",
     "REMOTE_HOST"
   ]

   Copy to Clipboard Toggle word wrap

Procedure

1. On your automation controller, navigate to Settings and select Miscellaneous System settings from the list of System options.

2. In the REMOTE_HOST_HEADERS field, enter the following values:

   [
     "HTTP_X_FORWARDED_FOR",
     "REMOTE_ADDR",
     "REMOTE_HOST"
   ]

   Copy to Clipboard Toggle word wrap
3. Add the lines below to /etc/tower/conf.d/custom.py to ensure the application uses the correct headers:

Procedure

1. On your automation controller node, run the following:

   # awx-manage shell_plus

   Copy to Clipboard Toggle word wrap

2. Then run the following from the python prompt:

   >>> from awx.main.utils import encrypt_value, get_encryption_key \
   >>> postgres_secret = encrypt_value('$POSTGRES_PASS') \
   >>> print(postgres_secret)

   Copy to Clipboard Toggle word wrap
   Note

   Replace the $POSTGRES_PASS variable with the actual plain text password you want to encrypt.

   The output should resemble the following:

   $encrypted$UTF8$AESCBC$Z0FBQUFBQmtLdGNRWXFjZGtkV1ZBR3hkNGVVbFFIU3hhY21UT081eXFkR09aUWZLcG9TSmpndmZYQXFyRHVFQ3ZYSE15OUFuM1RHZHBqTFU3S0MyNEo2Y2JWUURSYktsdmc9PQ==

   Copy to Clipboard Toggle word wrap

3. Copy the full values of these hashes and save them.

   • The hash value begins with $encrypted$, and is not just the string of characters, as shown in the following example:

     $encrypted$AESCBC$Z0FBQUFBQmNONU9BbGQ1VjJyNDJRVTRKaFRIR09Ib2U5TGdaYVRfcXFXRjlmdmpZNjdoZVpEZ21QRWViMmNDOGJaM0dPeHN2b194NUxvQ1M5X3dSc1gxQ29TdDBKRkljWHc9PQ==

     Copy to Clipboard Toggle word wrap

     Note that the $*_PASS values are already in plain text in your inventory file.

Procedure

1. Edit /etc/tower/conf.d/postgres.py using:

   $ vim /etc/tower/conf.d/postgres.py

   Copy to Clipboard Toggle word wrap

2. Add the following line to the top of the file.

   from awx.main.utils import decrypt_value, get_encryption_key

   Copy to Clipboard Toggle word wrap

3. Remove the password value listed after 'PASSWORD': and replace it with the following line, replacing the supplied value of $encrytpted.. with your own hash value:

   decrypt_value(get_encryption_key('value'),'$encrypted$AESCBC$Z0FBQUFBQmNONU9BbGQ1VjJyNDJRVTRKaFRIR09Ib2U5TGdaYVRfcXFXRjlmdmpZNjdoZVpEZ21QRWViMmNDOGJaM0dPeHN2b194NUxvQ1M5X3dSc1gxQ29TdDBKRkljWHc9PQ=='),

   Copy to Clipboard Toggle word wrap
   Note

   The hash value in this step is the output value of postgres_secret.

4. The full postgres.py resembles the following:

   # Ansible Automation platform controller database settings. from awx.main.utils import decrypt_value, get_encryption_key DATABASES = { 'default': { 'ATOMIC_REQUESTS': True, 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'awx', 'USER': 'awx', 'PASSWORD': decrypt_value(get_encryption_key('value'),'$encrypted$AESCBC$Z0FBQUFBQmNONU9BbGQ1VjJyNDJRVTRKaFRIR09Ib2U5TGdaYVRfcXFXRjlmdmpZNjdoZVpEZ21QRWViMmNDOGJaM0dPeHN2b194NUxvQ1M5X3dSc1gxQ29TdDBKRkljWHc9PQ=='), 'HOST': '127.0.0.1', 'PORT': 5432, } }

   Copy to Clipboard Toggle word wrap

Procedure

1. When encryption is completed on all nodes, perform a restart of services across the cluster using:

   # automation-controller-service restart

   Copy to Clipboard Toggle word wrap
2. Navigate to the UI, and verify you are able to run jobs across all nodes.

Procedure

1. Add aap_service_regen_cert=true to the inventory file in the [all:vars] section:

   [all:vars]
   aap_service_regen_cert=true

   Copy to Clipboard Toggle word wrap
2. Run the installer.