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

# Ansible tower
__Ansible Tower__ is a commercially available, GUI-based, playbook
orchestration system that provides the ability to scale network
automation solutions to even larger deployments. Role-Based Access
Control (RBAC), playbook scheduling, reporting, and inventory management
are all key components of Ansible Tower. Ansible Tower can make it easier to integrate Ansible in the organization. It provides a more familiar GUI-based approach and includes some key components most
organizations require such as RBAC, reporting, and playbook scheduling.
Ansible Tower can also be integrated into some source control CI/CD pipelines. An
open-source version, AWX, is also available.

<br>

# Source control

After a successful transition from a collection of configurations to
code, source control needs to be implemented. The organization's
development team likely has source control implemented which can be
leveraged with best practices and processes for changes to source
code. Source control is a vital component of the new NDLC for network
engineers and operations.

Treating the network as code implies strong source controls. Network
configurations stored as code benefit greatly from these source controls
as the given state of the network, or individual components of the
network, are known at all times. Changes that are tracked using source
control display the exact changes and the pre-change/post-change state
of the network device's intended configuration. Strong source control
means that when problems occur on the network, it is extremely easy to answer the standard "what
changed?" question.

## Git

__Git__ is a free, open-source, and distributed version control system
created by Linus Torvalds in 2005 for the development of the Linux kernel.

Consider Git is the glue that holds the NDLC lifecycle together by tracking
all changes to files using commits. These tracked changes are included
in the history of all Git repositories. These changes can be rolled back to
any point in time.





Let's learn about the roles of Ansible tower and source control in the network automation process.

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

Ansible Tower

Ansible tower