Learning paths › Automation › Roles and zero-touch provisioning for Linux switches
Roles and zero-touch provisioning for Linux switches
Provisioning Linux-based switches whose configuration is files on the box: agentless change over SSH, push weighed against pull, zero-touch provisioning from DHCP with an SSH key installed on the way, and a project laid out so its dependencies show — then growth into roles, an interface file rendered from a template, a variable traced from the play through to the rendered output, common settings separated from routing into two roles applied to a leaf group, and each leaf's bonds, bridges and SVIs described as data. Explanation and understanding checks only; this course carries no written exercises.
Lessons
- Manage a Linux switch through its config files
- Automate over SSH with no agent installed
- Decide whether the controller pushes or the device pulls
- Recognise each tool's name for its config artifact
- Provision a switch from DHCP with zero touch
- Choose where your Ansible version comes from
- Install an SSH key during provisioning
- Lay out a project so its dependencies show
- Point ansible.cfg at the right inventory and library
- Group leaf switches into a reusable target
- Read a module's parameters before you call it
- Know when a saved playbook beats a one-off run
- Grow from one command to a role-based project
- Render an interface file from a template
- Run the playbook and gather facts first
- Trace a variable through to the rendered file
- Split a growing playbook into roles
- Use role conventions so Ansible finds your files
- Separate common settings from routing in two roles
- Follow the chain from play to rendered config
- Apply two roles to the leaf group
- Describe each leaf's bonds, bridges and SVIs as data
- Read the per-host recap after a multi-role run
- Plan a two-leaf build: loopbacks, bond, routing
More in Automation
- First scripts that configure devices
- NAPALM: structured data across vendors
- Concurrency, and the Python types device output returns
- Parsing show output and testing conditions
- Readable code, branching and loops
- Build the workstation and the toolchain
- Files, CSV, JSON and pickle
- Paramiko: SSH to devices from Python
- Netmiko at fleet scale
- Tuples, sets and dictionaries for device records
- Exceptions and your first classes
- Plan and build the automation lab
- Files, formatting and regular expressions
- Addresses, functions, modules and classes
- CSV inventories, logging and scheduling
- Netmiko, SCP and structured parsing
- Agents, async and model-driven workflows
- NETCONF, YANG and RESTCONF
- NX-API, pyATS and Genie
- A small GenAI app, end to end
- macOS, Linux and the virtual lab
- Agile delivery and Python fundamentals
- REST APIs, authentication and requests
- Flask, Docker and Jenkins
- Managing a router with NETCONF and RESTCONF
- Ansible: inventory, ad-hoc commands and first playbooks
- Installing the controller and applying a project
- Setting up Python 3
- The Ansible lab and the controller
- Vault, variables and config changes
- Parsing output and knowing which variable wins
- Jinja filters and PAN-OS automation
- Loops, callbacks, strategy and run control
- Roles, imports and writing your own module
- Running playbooks from AWX