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

## Overview
The final phase of network automation is to **continuously integrate (CI)** and **continuously deliver (CD)** the Ansible playbooks
into the production network. CI is the software development practice adopted for network automation. CI
allows for teams to collaborate on code, integrate their changes often using Git commits and pull
requests, and create automated builds whenever there are changes made to the master branch. 

CD
expands on the CI capability and automatically releases, the automated builds to the network
on a scheduled release. This schedule could be as frequent as hourly, nightly, or weekly. The general
principle of CI/CD is that developers only need to worry about making changes to the code , and about not how to
document, integrate, or release it. The CI/CD pipeline and the automation engine take care of this for
them. This often has the side-effect of removing network operations from the equation. 

# Overview
The final phase of network automation is to **continuously integrate (CI)** and **continuously deliver (CD)** the Ansible playbooks
into the production network. CI is the software development practice adopted for network automation. CI
allows for teams to collaborate on code, integrate their changes often using Git commits and pull
requests, and create automated builds whenever there are changes made to the master branch. 

CD
expands on the CI capability and automatically releases, the automated builds to the network
on a scheduled release. This schedule could be as frequent as hourly, nightly, or weekly. The general
principle of CI/CD is that developers only need to worry about making changes to the code , and about not how to
document, integrate, or release it. The CI/CD pipeline and the automation engine take care of this for
them. This often has the side-effect of removing network operations from the equation. 

Let's take a high-level overview of the CI/CD process and its relevance to network automation.

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

Overview of CI/CD

Overview