Concepts / Automation and APIs

Automation and APIs

Configuration management

Also called Ansible, Puppet, Chef, Terraform, infrastructure as code, IaC, playbook, inventory, Jinja2, template, agentless, push, pull

Writing the wanted configuration down as files and letting a tool make every device match it.

Ansible keeps an inventory (devices and groups), variables (what each should have), Jinja2 templates (how variables become config) and playbooks (the tasks, in YAML). It logs in over SSH and needs nothing installed on the device: agentless, and the control node pushes. Puppet (manifests) and Chef (Ruby cookbooks) install an agent on each device that pulls its config from a server. Terraform (HCL) creates infrastructure through providers' APIs from a declared end state and records what it built in a state file. Kept in version control, the files are infrastructure as code: reviewed, repeatable, and the record of what the network should be.

See it on real machines

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Start with a free account: Google or email, no card.

Open this lab