An Organization is a logical collection of Inventories, Teams (and users), Projects, and Jobs, and is the highest level in the Tower object hierarchy.
Access the Organizations page by clicking the Organizations icon from the left navigation bar. The Organizations page displays all of the existing organizations for your installation of Tower. Organizations can be searched by Name or Description. Modify and remove organizations using the Edit and Delete buttons.
Inventories
An Inventory is a collection of hosts against which jobs may be launched, the same as an Ansible inventory file. Inventories are divided into groups and these groups contain the actual hosts. Groups may be sourced manually, by entering host names into Tower, or from one of Ansible Tower’s supported cloud providers.
This tab displays a list of the inventories that are currently available :
When the cloud icon is green that indicates successful syncs in the inventory, red indicates failed syncs, grey indicate no sync.
The dot icon shows the status of recent jobs for this inventory.
Hosts
This tab displays a list of hosts in the selected inventory :
Groups
You can add a group of hosts in a specified inventory. You ahve to first create a new group and add some hosts in it.
Teams
A Team is a subdivision of an organization with associated :
- users
- projects
- credentials
- permissions
Teams provide a means to implement role-based access control schemes and delegate responsibilities across organizations. For instance, permissions may be granted to a whole Team rather than each user on the Team.
You can create as many Teams of users as make sense for your Organization. Each Team can be assigned permissions, just as with Users. Teams can also scalably assign ownership for Credentials, preventing multiple Tower interface click-throughs to assign the same Credentials to the same user.
Projects
A Project is a logical collection of Ansible playbooks, represented in Tower.
You can manage playbooks and playbook directories by either placing them manually under the Project Base Path on your Tower server in /var/lib/awx/projects, or by placing your playbooks into a source code management (SCM) system supported by Tower, including Git, Subversion, Mercurial, and Red Hat Insights.
By default, the Project Base Path is /var/lib/awx/projects and it is configured in /etc/tower/conf.d/custom.py.
This menu displays the list of the projects that are currently available :
This displays the details of a selected project :
SCM URL :
- Example URLs for GIT SCM include :
- https://github.com/ansible/ansible.git
- git@github.com:ansible/ansible.git
- git://servername.example.com/ansible.git
SCM Branch :
- Branch to checkout. In addition to branches, you can input tags, commit hashes, and arbitrary refs. Some commit hashes and refs may not be availble unless you also provide a custom refspec.
SCM Refspec :
- A refspec to fetch (passed to the Ansible git module). This parameter allows access to references via the branch field not otherwise available. Examples include: refs/:refs/remotes/origin/, refs/pull/62/head:refs/remotes/origin/pull/62/head
Job Templates
This displays a selected job template in a project :
This displays the details of a selected job template. You can see you can selected the inventory (list of hosts) and a Ansible playbook :
Playbooks
An Ansible playbook : https://n0tes.fr/categories/Automatisation/Ansible/
Jobs
A job is an instance of Tower launching an Ansible playbook against an inventory of hosts.
The Jobs link displays a list of jobs and their statuses–shown as completed successfully or failed, or as an active (running) job.
You can re-run a job (rocket icon) on all hosts in the specified inventory, even though some of them already had a successful run. This allows you to re-run the job without running the Playbook on them again. You can also re-run the job on all failed hosts.
The relaunch operation only applies to relaunches of playbook runs and does not apply to project/inventory updates, system jobs, workflow jobs, etc.
This displays the details of a job :
Documentation
https://docs.ansible.com/ansible-tower/latest/html/userguide/organizations.html
https://docs.ansible.com/ansible-tower/3.8.6/html/installandreference/glossary.html