The automation code that you will create to be run by Ansible is broken down into hierarchical layers. Envision a pyramid with its multiple levels of elevation. We will start at the top and discuss playbooks first.
Imagine that a playbook is the very topmost triangle of a pyramid. A playbook takes on the role of executing all of the lower level codes contained in a role. It can also be seen as a wrapper to the roles created; we will cover the roles in the next section.
The playbooks also contain other high level runtime parameters, such as the host(s) to run the playbook against, the root user to use, and/or if the playbook needs to be run as a
sudo user. These are just a few of the many playbook ...