Journey Map approach to implementing network automation with Ansible

No video selected

Select a video type in the sidebar.

 It’s a fact that traditional network engineers are used to maintaining and managing large network deployments with some form of automation and standardized configuration templates. Along with this, you will find that they are all facing the same set of use cases such as new site provisioning, configuration management, firmware management and etc.

Despite that you will find that one of the biggest problems seen regarding large scale network deployments is configuration drift. This would be defined as the incident where local administrators do ad-hoc changes that are not reflected in the templates. The change only exists on the device.

In this session we will discuss how we have come up with a journey based approach to implement network automation using Ansible. We will discuss modeling, it's benefits and how it can be used to maintain configuration and execute auditing and remediation to avoid configuration drift.

Attendees will walk away learning more about:

1) Discover the various required phases with clearly identifiable milestones and deliverables

2) The framework needed to be successful with network automation

3) What is a viable MVP (minimal viable product)

4) Identify which phase would be the best starting point for you to embark on the network automation journey

Slides here



Piyush Patel, Red Hat


Walter Bentley, Red Hat