I spent most of last year developing SDN-related content, resulting in pretty successful 2-day workshop and 20+ hours of online content. However, I fully agree with Matt Oswalt that network automation matters even more than lofty centralized ideas, so it was time to focus on that area.
Introduction to network automation – what is it, why should we use it, and what tools are available if you want to get started.
Hierarchy of network needs based on an excellent post by Jeremy Stretch. We’ll start with how we can improve the operations of existing networks, how you can slowly introduce abstracted network state, use it for automated network provisioning, and finally what can be done in the area of automatic remediation.
Network automation tools – when and how would you use Puppet, Ansible, Git, Gerrit and Jenkins.
After the introductory section we’ll focus on one of the most common entry-level automation tasks: generating and deploying device configurations using tools better than Excel and Putty. After describing the big picture we’ll go deeper into:
- Generating network state data models and encoding them in YAML;
- Using Jinja2 to generate network device configurations;
- Using Ansible for network automation.
In the Ansible section we’ll explore a few other rabbit trails, including:
- Executing commands on network devices and getting usable data back from them;
- Pushing configurations into devices using SCP and NAPALM.
Finally, we’ll briefly visit NETCONF, see what it’s all about, what YANG is, and whether they are useful in network automation scenarios.
Interested? There are only a few places left, so hurry up and register ASAP.