How eazytraining/ansible-training works
Project type and purpose
• This is not a web‐app or microservice suite but a training repository for “Ansible Pour DevOps” exercises.
• It contains two parallel tracks:
• TPs-eazylab – labs run against real/cloud hosts (AWS, AWX)
• TPs-vagrant – the same labs but run in a local Vagrant environment
• Each “TP” directory is a self-contained Ansible project illustrating a concept (ad-hoc commands, inventories, roles, templates, Vault, AWX, etc.).
File‐structure analysis
• Top level:
• README.md – course title
• TPs-eazylab/ – lab projects against real or cloud VMs
• TPs-vagrant/ – lab projects on Vagrant VMs
• Under each TP directory (0 through 10, plus mini-projet):
• ansible.cfg – project configuration
• hosts*.yml or hosts.ini – static inventory
• group_vars, host_vars – variable definitions
• deploy*.yml – playbooks (sometimes multiple versions)
• roles or webapp subdirs – templating, tasks, defaults, files, vault secrets
• Special labs:
• TP10 integrates AWS dynamic inventory and cloud-provisioning
• TP9 uses AWX/Tower as a scheduler/UI
• mini-projet demonstrates a complete role with tests
Key README insights
• The labs themselves (corrige.md, note.md) often comment on pitfalls and best practices.
Detail but keep it high-level
• Don’t overcrowd with every file—group by category (inventories, playbooks, roles)
• One representative “TP” project and annotate that all numbered TPs follow the same pattern
• Call out the mini-projet role structure in a sidebar to illustrate best-practice role anatomy