February 4, 2020

358 words 2 mins read

Network Automation: Do I Need Expensive Tools To Do Meaningful Automation?

Network Automation: Do I Need Expensive Tools To Do Meaningful Automation?

This talk will focus on: 1 - Automation Domains 2 - Use Cases for Consideration 3 - Open Source Tooling used in Network Automation Case Studies 4 - Case Studies: - …

Talk Title Network Automation: Do I Need Expensive Tools To Do Meaningful Automation?
Speakers Patrick Moore, Itential
Conference NANOG72
Conf Tag
Location Atlanta, GA
Date Feb 19 2018 - Feb 21 2018
URL Talk Page
Slides Talk Slides
Video Talk Video

This talk will focus on: 1 - Automation Domains 2 - Use Cases for Consideration 3 - Open Source Tooling used in Network Automation Case Studies 4 - Case Studies:

  • Config Backup
  • Config Differential and Restore
  • MOP Automation Example: Sub Interface Configuration There are 3 primary levels of automation: Device, Service, Operational. Each of these levels builds upon the other, with each one being a prerequisite to effectively accomplishing the next. At the Device level, there are many open source tools in place that allow for high value automation work. This level can leverage templates and scripting tools highly effective automation. At the Service level, you begin to need a model-based approach to really achieve high value that is also scalable. There are aspects of the Operational level that reach into each of the lower levels. In this case, workflow and orchestration are implemented to leverage multiple templates, scripts, and/or models to achieve more sophisticated automation. In this presentation, we will focus on the Device level, as well as some simple examples of applying Operational level techniques. This discussion will revolve around configuration management use cases involved in device maintenance and MOP automation. An architecture will be covered that will be used in the cases studies to be presented. This architecture will include open source tools such as Ansible, Salt, NAPALM, and others. This should be enough detail to allow attendees to attempt similar implementations with a minimum of investment, outside of the servers the software will need to run on. We will then cover an overview of 4 common activities: config backups, config dif comparisons, restoration of a previous config, and automation of a simple MOP scenario such as a sub interface configuration activity.
comments powered by Disqus