Ansible Automation Controller is a web-based solution where you can centralize and control your IT infrastructure with a visual dashboard, role-based access control, job scheduling, integrated notifications and graphical inventory management. Ansible Automation Controller includes a REST API and CLI in addition to the web UI.
In this lab, you will log in and perform some basic configurations that will be used in later labs to perform automation tasks against your F5 BIG-IP device. This exercise will cover:
Automation mesh is an overlay network intended to ease the distribution of work across a large and dispersed collection of workers. Mesh nodes establish peer-to-peer connections with each other across your existing networks bringing automation closer to the endpoints that need it.
Automation mesh is already configured and ready to use in your workshop environment.
Learning about automation mesh falls outside the scope of this workshop. However, please try our hands-on, interactive labs to learn more about automation mesh and other Ansible Automation Platform features.
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-workshopthe link would be:
This login information has been provided by the instructor at the beginning of class.
After logging in the Job Dashboard will be the default view as shown below.
Click on the ? information button on the top right of the user interface and then click About.
A window will pop up similar to the following:
Take note that the Ansible Automation Controller version is provided here.
An inventory is required for Red Hat Ansible Controller 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 Controller can make use of an existing configuration management database (cmdb) such as ServiceNow or Infoblox DDI.
More info on Inventories in respect to Ansible Controller can be found in the documentation here
Click on the Inventories button under RESOURCES on the left menu bar.
Under Inventories, Click on the
Workshop Inventory, click the HOSTS button at the top. There will be hosts configured here. Click on one of the devices.
Click on the
Workshop Inventory link at the top of the page to return the top level menu.
Click on GROUPS. This is where you can configure Group of hosts
A project is how Ansible Playbooks are imported into Red Hat Ansible Automation Controller. 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 Controler, including Git, Subversion, and Mercurial etc.
For more information on Projects in Controller, please refer to the documentation
Click on the Projects button under RESOURCES on the left menu bar.
Under PROJECTS there will be one pre-configured projects,
Ansible official demo project. Open it up by clicking on the object.
Git is listed for this project. This means this project is using
Git for SCM.
Ansible official demo project click the SCM TYPE drop down menu
Note that Git, Mercurial and Subversion are some of the choices. Return the choice to Git so that the Project continues to function correctly.
Credentials are utilized by the Red Hat Ansible Automation Platform 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 Automation Controller please refer to the documentation.
Click on the Credentials button under RESOURCES on the left menu bar.
Under CREDENTIALS there will be two pre-configured credential,
Workshop Credential. Click on the
Workshop Credential examine the following:
blank. This credential is using a key instead of a password.
Templates or Job Templates define the parameters that will be used when executing an Ansible playbook. These parameters include previously mentioned features such as which project and inventory will be used. Additionally, parameters such as logging level and process forks allow for additional granularity on how playbooks are ran.
Click on the Templates button under RESOURCES on the left menu bar.
Under TEMPLATES there will be at least one pre-configured Job Template
INFRASTRUCTURE / Turn off IBM Community Grid. Open it up by clicking on the object.
You have completed lab exercise 4.0
You have now examined all three components required to get started with Ansible Automation Controller. A credential, an inventory and a project. In the next exercise we will create a job template.