Gain insights into automating network reconnaissance, orchestrating repetitive changes, and transforming network configuration management. Discover CI/CD pipeline migration for full network automation.

ansibleFinal1.tar.gz

gitjob

CIPhosts

CIPhosts-copy

gather_info

gather_important_facts

facts_to_md

facts_to_csv_html

tools

frr01

frr02

first_gather_important_facts

​​Network automation begins with automating network reconnaissance. This is accomplished by gathering important information from network devices while building a library of dynamic on-demand utilities and generating living documentation. Starting small, the course exhibits the simplicity and elegance of network automation.

Next, you will learn how to automate larger changes that require a high number of repetitive steps. These changes will be executed serially in a specific orchestrated order, making them perfect for an automated solution. After gaining comfort with the new tools, you can fully transform network configuration management to an automated, intent-based, self-documenting system.

The final step is learning how to migrate to a continuous integration/continuous delivery (CI/CD) pipeline, thereby fully automating the network.

Automate Your Network

# NetDevOps
__NetDevOps__ builds on the DevOps model from the application world but is applied to the networking functions of an organization. The network __“developers”__ (i.e senior network engineers, architects, designers etc.) and the network __“operators”__ (i.e network administrators, network support staff, day-to-day network operations etc.) are blended under a new framework. The senior developers are empowered to deliver into production directly through release management using pull requests. 

The operations team updates the data models and executes playbooks for routine network changes. Operations most likely will not write or update the dynamic templates. The templates will be developed by the senior network staff. 

In the case of NetDevOps, having software developers join this new team to help create the data models and templates with the input from the network team can be beneficial.

However, blending IT teams may lead to questions of where authorized changes come from. Fortunately, the automation engine itself makes the changes. Approvals should now look like peer reviews of code and traditional quality assurance (QA) as changes are now code based. 

The impact of this on network operators is tangible. Operators learn to write playbooks to help run the network, identify problems, and troubleshoot. Most network changes are automated to much easier tasks, such as running an Ansible playbook as a single-line command. The operations team can now have version control in the form of pull requests and Git commit information. Change approvals are built directly into the pipeline allowing for automated delivery of solutions.


Let's learn how automation can extend the DevOps model to incorporate the network "developers" and "operators" under a single framework.

Introduction

What Is Network Automation?

Why Automate the Network?

How to Automate the Network

Where to Start with Network Automation

Repository Structure

Network Reconnaissance

Tactical Playbooks

Data Models and Dynamic Templates

Dynamic Intent-Based Documentation

Configuration Management

Continuous Integration/Continuous Delivery

Conclusion

NetDevOps

NetDevOps