Configuring the Automation controller

Create a file /home/lab-user/casc_lab/group_vars/all/settings.yml with the below content.

---
controller_settings:
  settings:
    GALAXY_IGNORE_CERTS: true
...

Further documentation are provided below for those who are interested to learn more:

Create a file /home/lab-user/casc_lab/group_vars/all/execution_environments.yml and add the required information to the list controller_execution_environments to include a new EE (that we will show how to create with code in the next module) called config_as_code with image path {{ aap_hostname }}/config_as_code that is pull always and uses the credential cr_ah.

Figure 1. Config Execution Environment

Figure 2. Minimal Execution Environment

Figure 3. Supported Execution Environment

Further documentation for those who are interested to learn more see:

Create a file /home/lab-user/casc_lab/group_vars/all/credential_types.yml where we will create a list called controller_credential_types that has 5 variables per item defined below:

Further documentation for those who are interested to learn more see:

Create a file /home/lab-user/casc_lab/group_vars/all/credentials.yml and add the required information to the list controller_credentials to configure the UI to look like the screenshot. Make it to look like the screenshot, but make sure to use parameters for the values. DO NOT PASTE YOUR PASSWORD IN CLEARTEXT FOR CREDENTIALS!

---
controller_credentials:
  - name: aap_admin
    credential_type: Red Hat Ansible Automation Platform
    organization: config_as_code
    description: aap admin account
    inputs:
      host: "{{ aap_hostname }}"
      username: "{{ aap_username }}"
      password: "{{ aap_password }}"
      verify_ssl: false

  - name: hub_service_account
    credential_type: automation_hub
    organization: config_as_code
    description: automation hub api account
    inputs:
      hostname: "{{ aap_hostname }}"
      username: "{{ aap_service_account_username }}"
      token: "{{ ah_token }}"
      verify_ssl: false

  - name: hub_certified
    credential_type: "Ansible Galaxy/Automation Hub API Token"
    organization: config_as_code
    inputs:
      url: "https://{{ aap_hostname }}/pulp_ansible/galaxy/rh-certified/"
      token: "{{ ah_token }}"

  - name: hub_published
    credential_type:  "Ansible Galaxy/Automation Hub API Token"
    organization: config_as_code
    inputs:
      url: "https://{{ aap_hostname }}/pulp_ansible/galaxy/published/"
      token: "{{ ah_token }}"

  - name: hub_community
    credential_type:  "Ansible Galaxy/Automation Hub API Token"
    organization: config_as_code
    inputs:
      url: "https://{{ aap_hostname }}/pulp_ansible/galaxy/community/"
      token: "{{ ah_token }}"

  - name: hub_community_infra_repo
    credential_type:  "Ansible Galaxy/Automation Hub API Token"
    organization: config_as_code
    inputs:
      url: "https://{{ aap_hostname }}/pulp_ansible/galaxy/community-infra-repo/"
      token: "{{ ah_token }}"

  - name: cr_ah
    credential_type: Container Registry
    organization: config_as_code
    inputs:
      host: "{{ aap_hostname }}"
      username: "{{ aap_username }}"
      password: "{{ aap_password }}"
      verify_ssl: false

  - name: vault
    credential_type: Vault
    organization: config_as_code
    description: vault password
    inputs:
      vault_password: "{{ vault_pass }}"
...

Figure 4. Credential

Further documentation for those who are interested to learn more see:

Update the file /home/lab-user/casc_lab/group_vars/all/organizations.yml and add the required information to the list aap_organizations to configure the UI to look like the screenshot. Here we are adding the credentials that we created above to the Organization so we can pull collections from Automation Hub.

Figure 5. Config as Code Organization

---
aap_organizations:
...

Further documentation for those who are interested to learn more see:

Create a file /home/lab-user/casc_lab/group_vars/all/projects.yml and add the required information to the list controller_projects to configure the UI to look like the screenshot. The project you want to use is

https://github.com/redhat-cop/aap_configuration_template

---
controller_configuration_projects_async_delay: 5
controller_projects:

...

Figure 6. Project

Further documentation for those who are interested to learn more see:

Create a file /home/lab-user/casc_lab/group_vars/all/inventories.yml and add the required information to the list controller_inventories to configure the UI to look like the screenshot

---
controller_inventories:
...

Figure 7. Inventory

Further documentation for those who are interested to learn more see:

Add to file /home/lab-user/casc_lab/group_vars/all/inventory_sources.yml and a new variable with the required information to the list controller_inventory_sources to configure the UI to look like the screenshot

---
controller_inventory_sources:
...

Figure 8. Inventory Sources

Further documentation for those who are interested to learn more see:

Create a file /home/lab-user/casc_lab/group_vars/all/job_templates.yml and add the required information to the list controller_templates to configure the UI to like the screenshot.

---
controller_templates:

...

Figure 9. AAP Config Template

Figure 10. Build EE Template

Further documentation for those who are interested to learn more see:

Run /home/lab-user/casc_lab/playbooks/aap_config playbook.

ansible-playbook playbooks/aap_config.yml -i inventory.yml -l execution

If you run into problems, look back at the section that failed, and check the documentation for that role that was linked. If the output was hidden, look for 'Secure logging variables' on the controller_credentials role documentation.

After the playbook is complete you should be able to navigate to the controller and see all the changes.

Once you’ve completed the above tasks we will move towards building Execution Environment.