Introduction to Inventories

You already have a way of inventorying your infrastructure. It might be:

• By mentally remembering hostnames.
• By grouping them by a standard naming convention.
• With a custom database that stores specific properties about the hosts.
• With a full-blown CMDB (configuration management database) that has entries for all the hosts.

Ansible codifies this information by using an inventory.

Inventories describe your infrastructure by listing hosts and groups of hosts. Using an inventory gives you the ability to share standard variables among groups. Inventories are also parsable with host patterns, giving you the ability to broadly or narrowly target your infrastructure with Ansible automation. In its simplest form, an Ansible inventory is a file.

Let’s suppose that, within an infrastructure, there are three web servers and a database server. The Ansible inventory might look like this.

Each host or group can be used for pattern matching or to define one or more variables.

The above command creates a host variable named database_name with the value of customerdb. This variable is scoped to the host db01.

The above snippet creates a group variable named http_port with the value of 8080, and it is shared among all three web servers.

The above snippet uses the host pattern webserver to target all four web servers with the ping command.

Destroyed Infrastructure
In case you deleted the Ansible development environment, make sure to re-deploy the infrastructure for AWS and Azure by following the links.

Create an inventory#

Converting the ad-hoc ping command to a playbook makes the task more repeatable. However, there are still some points of friction.

1. Code duplication.

Each playbook contains the same set of variables used to connect to a Linux host.

2. Passing the hostname or IP address to the -i option.

Both of these points of friction are eliminated by using an inventory.

Use an Ansible INI file as an inventory source#

Let’s create an Ansible INI inventory for your Ansible development environment.

1. Create a file named hosts; no file extension is required.

2. Obtain the DNS name of the Linux virtual machine or EC2 instance.

   • The IP address can also be used.

3. Add the DNS or IP name to the hosts file.

Replace the example entry with the DNS name of your virtual machine or ec2 instance.

4. Review and Run the ping.yml playbook using the hosts file.

Provide the actual DNS and IPs names for the Linux EC2 or VM instance below in the environment variables and the hosts file.

Click on the Run button, wait for the environment to be set up, and execute the following command in the terminal:

Ansible uses the host pattern of all in the playbook to match all the hosts in the hosts INI inventory and to execute the ping task against them.

Using an inventory makes running the playbook easier by eliminating the need to input the DNS name or IP address. However, the variables are still stored within the playbook.

Use host variables in an inventory#

You will move the playbook variables to the hosts file.

1. Open the hosts inventory.
2. Add the ansible_user variable as a host var, replace the hostname.domain.com with your DNS name.

Add a space after the DNS name, followed by the variable name. The variable is set by using an equal sign and the value of the variable.

3. Add the ansible_password variable as a host var, replace <Password> with your password.

4. Add the ansible_ssh_common_args variable as a host var.

5. Create a playbook called ping_novars.yml.

Review the hosts and ping_novars.yml files below:

Provide the actual DNS and IPs names for the Linux EC2 or VM instance below in the environment variables and the hosts file.

6. Run the ping_novars.yml playbook using the hosts file.

Click on the Run button, wait for the environment to be set up, and execute the following command:

Try it now#

Add the Windows virtual machine or EC2 instance to the hosts file.

1. Open the hosts file.
2. Obtain the DNS names for the Windows virtual machine or EC2 instance.
3. Add the DNS name to a new line within the hosts file.
4. Define hosts variables for connecting to the Windows host. Replace the <password> with the actual password.

5. Create a playbook called win_ping_novars.yml.

6. Run the win_ping_novars.yml playbook using the hosts file.

7. Try adding the Linux host’s DNS name in the hosts file, re-execute the playbook, and observe.

MODULE FAILURE
fatal: [vm-linux*] MODULE FAILURE: /bin/sh: powershell: command not found.

Running the win_ping task against the Linux host fails because it is the wrong operating system.

8. Run the win_ping_novars.yml with a limit, replace <WindowsHostDNSname>.

Solution
The solution to this challenge is provided in the Solution directory. Try it yourself first and compare your solution with the provided solution.

In this lesson, we introduced inventories, you created the INI inventory files, and refactored your playbooks to remove code duplication.