Guys, I'm starting to work on deplying ansible at $WORK to start managing a bunch of existing servers. The goal is to A) get them consistent, B) learn ansible, and C) automate deployments so if I get hit by a bus, they can have a hope of keeping things going. So my first thoughts are about organization. Ansible is a file/directory heavy setup. And I understand how a task has one or more roles. And then a playbook can have one or more tasks. But it's how to manage the overall site or bundles of playbooks that I want to understand. I've looked at: https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.... and I think I can deal with the first layout suggestion, but I'd porbably put playbooks into a playbooks/ directory. But... how to keep them organized as my collection grows. Do I want a new directory structure for each group of playbooks? For example I want to do: - add ssh-keys for logins - make sure right repo(s) are configured - ntp client config - postfix config - NIS config - fstab config - nsswitch.conf config So ideally all of the above would be a playbook each, since for example ntp config, would/could include: - install ntp - install default client config - restart ntpd once configured - etc... Where it all comes down to is keeping all this organized nicely, especially as it grows ever more complicated. All the silly examples of setting up a LAMP stack completely gloss over the actual pushing of content, which is really what we want to do. So, thoughts? Real life experience? Suggestions for good training classes? Unfortunately it would have to be online now, not my preferred in-person training.... John