Ansible control node is the server where Ansible is installed. It centrally connects to managed devices and pushes configuration changes without requiring an agent on those devices. section 25.2.1 section 25.3
Its operational model includes:
- Using SSH to connect to managed devices, normally over TCP port 22; NETCONF is also supported for device configuration. section 25.2.1
- Following a push model: the control node sends configurations instead of waiting for devices to retrieve them. section 25.2.1
- Executing procedural tasks defined in playbooks, using inventories, templates, variables, modules, and tasks. section 25.3
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.
Trace how inventory, template, and variable files support playbook actions before the control node connects to devices and pushes configurations. section 25.2.1
