The following table summarizes the names of all valid hosts and groups included in the Ansible inventory that is used by hands-on activities in this course.
Table A.1. Valid hosts and groups in the inventory
| Name | Type | Member of |
|---|---|---|
access-layer | group | all |
border-routers | group | all |
cloud-services | group | all |
cs01 | host | access-layer, border-routers, cloud-services, ios |
ftp-server | group | all |
ios | group | network |
leaf01 | host | access-layer, leafs, vyos |
leaf02 | host | access-layer, leafs, vyos |
leafs | group | vyos |
local | group | all |
localhost | host | local |
network | group | all |
server01 | host | servers |
server02 | host | servers, ftp-server |
server03 | host | servers |
servers | group | all |
spine01 | host | border-routers, spines, vyos |
spine02 | host | border-routers, spines, vyos |
spines | group | vyos |
vyos | group | network |
The group all is automatically created by Ansible.
Do not create a group named all in your inventory file.
A sample inventory file will look similar to the following:
[user@host ~]$cat inventory[leafs] leaf[01:02] [spines] spine[01:02] [border-routers] spine01 spine02 cs01 [access-layer] leaf01 leaf02 cs01 [cloud-services] cs01 [ios] cs01 [vyos:children] spines leafs [network:children] vyos ios