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

## Configuration
The configuration folder should have subfolders by platform or operating
system to scale, and should hold more than just one type of configuration
file. The configuration folder holds dynamically generated output that
is the result of the `documentation.yml` playbook. Think of these files as intent-driven sources of
truth, and the result of the data models and templates being compiled.
Using a folder to hold these files means having an offline version of
the configurations that can be referenced. It also means having
automated documentation that is updated after every change. It is another way to validate the syntax of the commands before pushing commands to a device.

```bash
configuration
|
 ---- ios
      |
       ---- ACCESS01.cfg
       ---- ACCESS02.cfg
       ---- ACCESS03.cfg
       ---- DIST01.cfg
       ---- DIST02.cfg
       ---- CORE.cfg
 ---- nxos
```


# Configuration
The configuration folder should have subfolders by platform or operating
system to scale, and should hold more than just one type of configuration
file. The configuration folder holds dynamically generated output that
is the result of the `documentation.yml` playbook. Think of these files as intent-driven sources of
truth, and the result of the data models and templates being compiled.
Using a folder to hold these files means having an offline version of
the configurations that can be referenced. It also means having
automated documentation that is updated after every change. It is another way to validate the syntax of the commands before pushing commands to a device.

```bash
configuration
|
 ---- ios
      |
       ---- ACCESS01.cfg
       ---- ACCESS02.cfg
       ---- ACCESS03.cfg
       ---- DIST01.cfg
       ---- DIST02.cfg
       ---- CORE.cfg
 ---- nxos
```


Let's take a look at the configuration and documentation folders in the repository.

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

Configuration and Documentation

Configuration