Hands-on Lab·Ansible
Ansible Collections and Fully Qualified Collection Names
Since Ansible 2.10 almost everything ships in collections, and a module's real name has three parts. Short names still work, which is why the long ones look like pedantry until two collections define the same short name. This shows what is installed, how the name resolves, and where Ansible looks.
Roles and Collections Guide 28 of 45 Beginner
- OSUbuntu 26.04 LTS
- ansible-core2.20.1
- Python3.14.4
- TimeAbout 13 min
- Reviewed23 August 2026
Written against the versions above. `ansible.builtin` is special: it is part of ansible-core rather than a separately installable collection, and its short names will always resolve. Everything else is a collection that can be installed, upgraded and removed independently of Ansible itself.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| ANS-CTL01 | 192.168.0.36 | Ubuntu 26.04 LTS | Ansible Control Node | 2 Core | 3 GB | 50 GB |
| ANS-A01 | 192.168.0.37 | Ubuntu 26.04 LTS | Managed Node (group: web) | 2 Core | 3 GB | 50 GB |
Before you start
- A control node configured as shown in the first step.
- Nothing is changed - the one module that would change something is run with
--check.
-
The configuration this guide assumes
-
What a collection contains
-
The name has three parts
-
Short names still resolve
-
The collections keyword
-
Where collections are searched for