Inventory and SSH Connectivity
Define managed hosts, connection settings, inventory groups, and safe connectivity checks.
What an Inventory Does
An inventory tells Ansible which machines it can manage. The Ansible lab uses an INI inventory named hosts.ini with a group called servers.
[servers]
worker-node-1 ansible_host=203.0.113.10 ansible_user=ubuntu
worker-node-2 ansible_host=203.0.113.11 ansible_user=ubuntu
[all:vars]
ansible_ssh_private_key_file=/home/ubuntu/.ssh/ansible-key
ansible_python_interpreter=/usr/bin/python3
The example addresses use the documentation-only 203.0.113.0/24 range. Replace them with real private addresses, public addresses, or DNS names for your environment.
Understanding the Inventory Values
[servers]creates a group that a playbook can target withhosts: servers.worker-node-1is a friendly inventory alias.ansible_hostis the real IP address or DNS name used for SSH.ansible_useris the remote operating-system user.[all:vars]applies its variables to every inventory host.ansible_ssh_private_key_fileselects the SSH private key.ansible_python_interpreterselects Python on each managed node.
Keep private keys outside the repository. Only the path belongs in configuration, never the key content.
Inspecting the Inventory
Before changing a server, check how Ansible understands the inventory:
ansible-inventory -i hosts.ini --graph
ansible-inventory -i hosts.ini --list
The graph view makes group membership easy to verify:
@all:
|--@ungrouped:
|--@servers:
| |--worker-node-1
| |--worker-node-2
Testing Connectivity
The Ansible ping module checks whether Ansible can connect, authenticate, find Python, and execute a small module:
ansible servers \
-i hosts.ini \
-m ansible.builtin.ping
A successful response looks similar to:
worker-node-1 | SUCCESS => {
"changed": false,
"ping": "pong"
}
This is not an ICMP network ping. It is an Ansible module executed over the normal SSH connection.
Troubleshooting a Failed Connection
Check the connection in this order:
- Confirm the host address and SSH user.
- Confirm the private key exists and has restrictive permissions.
- Test SSH directly.
- Confirm Python 3 exists on the managed node.
- Retry Ansible with verbose output.
chmod 600 ~/.ssh/ansible-key
ssh -i ~/.ssh/ansible-key ubuntu@203.0.113.10
ansible servers -i hosts.ini -m ansible.builtin.ping -vvv
If direct SSH fails, fix that first. Ansible cannot work until its underlying SSH path works.
Key takeaway Use aliases to keep playbooks readable, keep environment-specific addresses in inventory, and verify connectivity before running configuration changes.