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

# Build repository folder structure 
The first step in building the automation ecosystem is setting up the
first repository for the selected environment the organization has
decided to automate. The repository is the foundation for the NDLC and
the source of truth. Thus, it is very important to create a structure that
scales and imposes rigid standards. RBAC should be configured limiting
access to the code base as appropriate.

Distribute the link to the network developers once the security and
workflows are in place. Create the first branch(the master branch)which includes the base folder structure and inventory `hosts`
file. A recommended folder structure is covered later.

Lock the master branch once populated.

# Ansible inventory file

Once ready to start populating the repository, begin with the
foundational `hosts` file. A considerable amount of time should be
spent creating a hierarchical model for the `hosts` file, building
natural logical groups of devices where applicable. These groups are
more than just a list of hosts. The group name itself becomes a key
accessible to create a `group_vars` YAML file as a data model for all
the hosts is listed under a group. 

Organize the `hosts` file to
reflect the logical network topology. Ansible can execute playbooks
against different technologies at the same time. 

For example:



Let's learn about the importance of the repository folder structure and how to create the Ansible hosts file.

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

Create Ansible Inventory File

Build repository folder structure