Managing Enterprise Automation with Red Hat Ansible Automation Platform

Use the automation controller web UI to identify the variable names for the settings that you intend to modify.

1. Navigate to https://controller.lab.example.com and log in as the admin user with redhat as the password.

2. Navigate to https://controller.lab.example.com/api/v2/settings/all/ and search for forks. Automation controller uses the MAX_FORKS variable to set the maximum number of forks per job.

3. Navigate to https://controller.lab.example.com/api/v2/settings/all/ and search for either cookie or 1800. Automation controller uses the SESSION_COOKIE_AGE variable to set the maximum number of seconds of inactivity before a user needs to log in again.

   Note

   Identifying the name of this variable can be difficult because possible keywords in the description of the variable do not appear in the variable name. One approach to identifying the name of a variable like the SESSION_COOKIE_AGE variable is to manually set the variable with a unique value using the web UI. You can then search the https://controller.lab.example.com/api/v2/settings/all/ page for the value that you used and identify the variable that has that value.

   You can manually change the SESSION_COOKIE_AGE variable by navigating to Settings and clicking the Miscellaneous Authentication settings link. Click Edit, enter a unique value in the Idle Time Force Log Out field, and then click Save.

4. Navigate to https://controller.lab.example.com/api/v2/settings/all/ and search for sessions. Automation controller uses the SESSIONS_PER_USER variable to set the maximum number of logged in sessions that a user is allowed.

Clone the https://git.lab.example.com/git/comp_api.git repository to the /home/student/git-repos directory.

1. From a terminal, create the /home/student/git-repos directory if it does not exist, and then change into it.

   [student@workstation ~]$ mkdir -p ~/git-repos/
   [student@workstation ~]$ cd ~/git-repos/

2. Clone the https://git.lab.example.com/git/comp_api.git repository and then change into the cloned repository.

   [student@workstation git-repos]$ git clone \
   > https://git.lab.example.com/git/comp_api.git
   Cloning into 'comp_api'...
   ...output omitted...
   [student@workstation git-repos]$ cd comp_api

3. Use the tree command to display the files in the repository.

   [student@workstation comp_api]$ tree
   .
   ├── modify_settings.yml
   └── vars
       ├── auth.yml
       └── settings.yml
   
   1 directory, 3 files

Configure the local repository with new settings for your automation controller. When finished, push the changes to the remote Git repository.

1. Modify the /home/student/git-repos/comp_api/vars/settings.yml file using the keys and values in the following table.

   Key	Value
   ANSIBLE_FACT_CACHE_TIMEOUT	7200
   MAX_FORKS	100
   SESSION_COOKIE_AGE	3600
   SESSIONS_PER_USER	2

   After you edit the /home/student/git-repos/comp_api/vars/settings.yml file, the file should have the following content:

   ---
   controller_settings:
     - key: ANSIBLE_FACT_CACHE_TIMEOUT
       value: 7200
     - key: MAX_FORKS
       value: 100
     - key: SESSION_COOKIE_AGE
       value: 3600
     - key: SESSIONS_PER_USER
       value: 2

2. Add, commit, and push your changes to the remote repository. Use the commit message: Changes to controller settings

   [student@workstation comp_api]$ git add vars/settings.yml
   [student@workstation comp_api]$ git commit -m "Changes to controller settings"
   ...output omitted...
   [student@workstation comp_api]$ git push
   ...output omitted...

Apply the changes made to the Git repository using the automation controller web UI.

1. Navigate to Resources → Projects. For the Controller Settings Comp-API project, click the Sync Project icon. Wait until the project displays the Successful status.

2. Navigate to Resources → Templates. For the Compreview_API job template, click the Launch Template icon. The job succeeds and output from the job indicates changes for each key defined in the settings.yml file.

   Figure 12.19: Compreview_API job output

3. From the https://controller.lab.example.com/api/v2/settings/all/ page, search for each key in the following table and verify that it has the expected value.

   Key	Value
   ANSIBLE_FACT_CACHE_TIMEOUT	7200
   MAX_FORKS	100
   SESSION_COOKIE_AGE	3600
   SESSIONS_PER_USER	2