Read this in other languages: English,
日本語.
Explore and understand the lab environment. This exercise will cover
Open up your web browser and type in the Ansible control node’s DNS name
For example if the student was assigned the student1 workbench and the workshop name was
durham-workshop
the link would be:
https://student1.durham-workshop.rhdemo.io
This login information has been provided by the instructor at the beginning of class.
admin
After logging in the Job Dashboard will be the default view as shown below.
Click on the i information button on the top right of the user interface.
A window will pop up similar to the following:
Take note that both the Ansible Tower version and the Ansible Engine version are provided here.
An inventory is required for Red Hat Ansible Tower to be able to run jobs. An inventory is a collection of hosts against which jobs may be launched, the same as an Ansible inventory file. In addition, Red Hat Ansible Tower can make use of an existing configuration management data base (cmdb) such as ServiceNow or Infoblox DDI.
More info on Inventories in respect to Ansible Tower can be found in the documentation here
Click on the Inventories button under RESOURCES on the left menu bar.
Under Inventories there will be two inventories, the Demo Inventory
and the Workshop Inventory
. Click on the Workshop Inventory
.
Under the Workshop Inventory
click the HOSTS button at the top. There will be four hosts here, rtr1 through rtr4 as well as the ansible control node. Click on one of the devices.
Take note of the VARIABLES field. The host_vars
are set here including the ansible_host
variable.
Click on the Workshop Inventory
link at the top of the page to return the top level menu.
Click on GROUPS. There will be multiple groups here including routers
and cisco
. Click on one of the groups.
Take note of the VARIABLES field. The group_vars
are set here including the ansible_connection
and ansible_network_os
variable.
Here is a walkthrough:
Prefer Youtube? Click Here
A project is how Ansible Playbooks are imported into Red Hat Ansible Tower. You can manage playbooks and playbook directories by either placing them manually under the Project Base Path on your Ansible Tower server, or by placing your playbooks into a source code management (SCM) system supported by Tower, including Git, Subversion, and Mercurial.
For more information on Projects in Tower, please refer to the documentation
Click on the Projects button under RESOURCES on the left menu bar.
Under PROJECTS there will be two pre-configured projects, Demo Project
and the Workshop Project
. Click on the Workshop Project
.
Note that GIT
is listed for this project. This means this project is using Git for SCM.
Under the Workshop Project
click the SCM TYPE drop down menu
Note that Git, Mercurial and Subversion are choices. Return the choice to Git so that the Project continues to function correctly.
Prefer Youtube? Click Here
Credentials are utilized by Tower for authentication when launching Jobs against machines, synchronizing with inventory sources, and importing project content from a version control system. For the workshop we need a credential to authenticate to the network devices.
For more information on Credentials in Tower please refer to the documentation.
Click on the Credentials button under RESOURCES on the left menu bar.
Under CREDENTIALS there will be three pre-configured credentials, Demo Credential
, Tower Credential
and the Workshop Credentials
. Click on the Workshop Credential
.
Under the Workshop Credential
examine the following:
ec2-user
.
Prefer Youtube? Click Here
You have completed lab exercise 5
You have now examined all three components required to get started with Ansible Tower. A credential, an inventory and a project. In the next exercise we will create a job template.
Click here to return to the Ansible Network Automation Workshop