Brian states things the way we define them.
I broke things up that way for a few reasons:
- Development process: Our dev team works in a similar fashion with their
code base, and objectifying the infrastructure Ansible is controlling in a
similar way lets the dev team use my Ansible work on thei
playbook => contains plays
play => maps hosts to tasks
roles => reusable content, can be vars, templates, files, tasks, etc
task => action to perform on a host
playbook does get overloaded as it is both an object and a file that
contains plays, but files that contain just tasks (task lists) ar
I was reading the thread "VMware - convert template to virtual
machines" and when I saw Nick's structure I realized I do have a lot
to learn conceptually about ansible. Specifically having playbooks and
roles separated. I always thought that the tasks inside roles were
considered playbooks.
