An Ansible playbook is a YAML file that defines tasks and procedures for managing configuration on devices listed in an inventory. Ansible uses a push model: the control node connects to managed devices over SSH and pushes configuration. section 25.2.1 section 25.3
Place the playbook within Ansible’s related file types and execution terms:
- Inventory lists managed hosts and can organize them into groups with host or group variables. section 25.2.1
- Templates use Jinja2 configuration syntax and variables to produce final configuration files. section 25.2.1
- Variables files store values that templates can use. section 25.3
- A task is one operation in a playbook, while a module is reusable code that performs a specific task. section 25.2.1
Figure 25.5 Basic Ansible operations. Inventory, template, and variable files define configurations, and playbooks define actions. The control node uses SSH to connect and push configurations to managed devices.
Follow the control node, SSH connection, inventory, templates, variables, playbook actions, and managed-device configuration flow. section 25.2.1

