Introduction
In this document we describe a possible naming convention, based on experience in larger environments. At first when you start creating playbooks, there seems to be no reason to have a naming convention.
This is a pittfall a lot of companies fall into.
You use desciptive names and all plays are easily found in the repository.
But when the complexity grows, you might lose oversight and new colleagues might get lost in the woods of the playbook repositories. Documentation is also an issue where some organizations struggle with, where to document the code and where to doument for the usage (user doc). We will give you some pointers, but as every orginization is different in its requirements, we will not tell you this is the only way.
We expect you to have some experience with ansible, because we will not explain the inner workings of ansible here, but will explain how to keep your code manageble, even in larger setups. Not only repository naming is important, also variables, tags and templates. There are possibly many more, but we will get there when we get there.
In the next chapters we will dig in deeper on each subject.
Ansible_Organization_best_practice
Ansible_Organization_best_practice