An Ansible automation controller Project is a logical collection of Ansible playbooks. You can manage your playbooks by placing them into a source code management (SCM) system supported by automation controller such as Git or Subversion.
This exercise covers:
For this demonstration we will use playbooks stored in a Git repository:
A playbook to install the Apache web server has already been committed to the directory rhel/apache,
--- - name: Apache server installed hosts: web tasks: - name: latest Apache version installed yum: name: httpd state: latest - name: latest firewalld version installed yum: name: firewalld state: latest - name: firewalld enabled and running service: name: firewalld enabled: true state: started - name: firewalld permits http service firewalld: service: http permanent: true state: enabled immediate: yes - name: Apache enabled and running service: name: httpd enabled: true state: started
Note the difference to other playbooks you might have written! Most importantly there is no
hostsis set to
To configure and use this repository as a Source Control Management (SCM) system in automation controller you have to create a Project that uses the repository
|Default Execution Environment||Default execution environment|
|Source Control Credential Type||Git|
Enter the URL into the Project configuration:
|Source Control URL||
|Options||Select Clean, Delete, Update Revision on Launch to request a fresh copy of the repository and to update the repository when launching a job.|
The new project will be synced automatically after creation. But you can also do this manually: Sync the Project again with the Git repository by going to the Projects view and clicking the circular arrow Sync Project icon to the right of the Project.
After starting the sync job, go to the Jobs view: there is a new job for the update of the Git repository.
A job template is a definition and set of parameters for running an Ansible job. Job templates are useful to execute the same job many times. So before running an Ansible Job from automation controller you must create a Job Template that pulls together:
Inventory: On what hosts should the job run?
Credentials What credentials are needed to log into the hosts?
Project: Where is the playbook?
What playbook to use?
Okay, let’s just do that: Go to the Resources -> Templates view, click the Add button and choose Add job template.
Remember that you can often click on magnfying glasses to get an overview of options to pick to fill in fields.
|Execution Environment||Default execution environment|
|Options||tasks need to run as root so check **Privilege Escalation**|
You can start the job by directly clicking the blue Launch button, or by clicking on the rocket in the Job Templates overview. After launching the Job Template, you are automatically brought to the job overview where you can follow the playbook execution in real time:
Since this might take some time, have a closer look at all the details provided:
All details of the job template like inventory, project, credentials and playbook are shown.
Additionally, the actual revision of the playbook is recorded here - this makes it easier to analyse job runs later on.
Also the time of execution with start and end time is recorded, giving you an idea of how long a job execution actually was.
Selecting Output shows the output of the running playbook. Click on a node underneath a task and see that detailed information are provided for each task of each node.
After the Job has finished go to the main Jobs view: All jobs are listed here, you should see directly before the Playbook run an Source Control Update was started. This is the Git update we configured for the Project on launch!
Time for a little challenge:
You have already been through all the steps needed, so try this for yourself.
systemctl status httpd?
Go to Resources → Inventories → Workshop Inventory
In the Hosts view select
node3 and click Run Command
Within the Details window, select Module
command, in Arguments type
systemctl status httpd and click Next.
Within the Execution Environment window, select Default execution environment and click Next.
Within the Machine Credential window, select Workshop Credential and click Launch.
The output of the results is displayed once the command has completed.