Learn the concepts that are required for automating our network.

Fundamentals of DevOps

This module starts with automating network reconnaissance. We'll accomplish this by gathering important information from network devices while building a library of dynamic on-demand utilities and generating living documentation. Starting small, the module exhibits the simplicity and elegance of network automation.
We'll then 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 becoming comfortable with these new tools, we’ll be able to fully transform any network configuration management into an automated, intent-based, self-documenting system.
In the end, we'll learn how to migrate to a continuous integration/continuous delivery (CI/CD) pipeline, thereby fully automating the network.

Automate Your Network

## Methodology in automation
The new
methodology available after the network becomes application-like
and comprises standard human-readable code is among the biggest challenges brought by network automation. There is no need for network
engineers to draft configuration changes and for network operations to
deploy production at the CLI. Instead, they can now follow a CI/CD pipeline
with change management, version control, and a branching strategy. Also, documentation moves to TFS as it becomes automated alongside the configurations of the
devices.

Reviewing pull requests and Git commits becomes routine for network engineers as they peer
review and approve changes to the master branch. The SDLC approach to
software development should already exist in the organization. An
opportunity exists to bridge IT with software development that adopts
already existing code standards and development policies for the new
network automation code. Initially, network engineers write Ansible
playbooks that execute as a one-line command at an
approved schedule. Eventually, these steps become automated through the CI/CD pipeline.


# Methodology in automation
The new
methodology available after the network becomes application-like
and comprises standard human-readable code is among the biggest challenges brought by network automation. There is no need for network
engineers to draft configuration changes and for network operations to
deploy production at the CLI. Instead, they can now follow a CI/CD pipeline
with change management, version control, and a branching strategy. Also, documentation moves to TFS as it becomes automated alongside the configurations of the
devices.

Reviewing pull requests and Git commits becomes routine for network engineers as they peer
review and approve changes to the master branch. The SDLC approach to
software development should already exist in the organization. An
opportunity exists to bridge IT with software development that adopts
already existing code standards and development policies for the new
network automation code. Initially, network engineers write Ansible
playbooks that execute as a one-line command at an
approved schedule. Eventually, these steps become automated through the CI/CD pipeline.


Let's quickly learn about the new methodology that is used in network automation.

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

Methodology

Methodology in automation