BuildTheNet

Opening your workspace

Your learning content and tools are loading.

Learning paths › Automation › The Ansible lab and the controller

The Ansible lab and the controller

Standing up the control node a longer Ansible series runs from — what the lab must provide, a hosted vendor sandbox instead of local devices, why the controller is Linux rather than Windows, SSH negotiated with an older device, playbooks edited over a remote connection and versioned to a repository — then Ansible itself installed in a virtual environment, the right command picked for the job, defaults set in a project ansible.cfg, hosts and groups named in an inventory, YAML's mappings, sequences and scalars read, a playbook structured into plays and tasks and checked with ansible-lint, and Vault encrypting one secret or a whole variables file. Explanation and checks; four written exercises.

Lessons

More in Automation