Answer» - Roles are a way to group multiple tasks together into one container to do the automation in a very effective manner with a PROPER DIRECTORY structure, they are built on the IDEA of include files and combine them to form clean, reusable abstractions.
- Roles provide a framework for fully independent or interdependent, collections of variables, tasks, files, templates, and modules.
- Each role is typically limited to a particular theme or desired end result, with all the necessary steps to reach that result either WITHIN the role itself or in other roles listed as dependencies.
- Roles themselves are not playbooks. There is no way to directly execute a role. Roles have no setting for which host the role will apply to. Top-level playbooks are the glue that BINDS the hosts from your inventory to roles that should be applied to those hosts.
|
