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

## Summary 
Playbooks for gathering information about the network devices are simple and safe first steps towards network automation. Over time, a library of on-demand or scheduled playbooks will be developed. These playbooks automatically generate important information about each device on the network. 

In addition to automating the repetitive and time-consuming task of documenting the network, the organization starts building a data warehouse of dynamically generated output files in the repository. By collecting output from the entire network on a regular basis, a historical state view in the form of the TFS repository exists. This repository shows the exact location of changes made to the network. The only limitation is creativity and how to use the wealth of information available. 

In the coming chapter, the automation engine begins to make changes to the network. Having the ability to automatically gather and document information about the state of the network is a key step before making automated changes to the network. Now the organization can build playbooks that capture and document the network’s state, execute the changes, and recapture the post-change state, all automatically. Truly revolutionary! 


# Summary 
Playbooks for gathering information about the network devices are simple and safe first steps towards network automation. Over time, a library of on-demand or scheduled playbooks will be developed. These playbooks automatically generate important information about each device on the network. 

In addition to automating the repetitive and time-consuming task of documenting the network, the organization starts building a data warehouse of dynamically generated output files in the repository. By collecting output from the entire network on a regular basis, a historical state view in the form of the TFS repository exists. This repository shows the exact location of changes made to the network. The only limitation is creativity and how to use the wealth of information available. 

In the coming chapter, the automation engine begins to make changes to the network. Having the ability to automatically gather and document information about the state of the network is a key step before making automated changes to the network. Now the organization can build playbooks that capture and document the network’s state, execute the changes, and recapture the post-change state, all automatically. Truly revolutionary! 


Let's summarize what we covered in these chapter.

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

Summary

Summary