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

## Steps to organize repository
The organization of the repository includes a combination of necessary
Ansible framework files and folders, as well as user-defined files and
folders. Create a repository that scales, is easily navigated, and
supports the Ansible framework. Build a
folder structure that's best suited to the reflects the environment being automated.


Build the structure using empty folders and empty placeholder files that
suit the environment. Build a repository suitable for an enterprise
campus environment consisting of Cisco Catalyst devices running IOS, and
an enterprise data center consisting of Cisco Nexus devices running
NX-OS. Remember there are many Ansible modules available from other
vendors, if not running a Cisco network.

> **Important Note:** Git will not track or provide version control
for empty folders. When creating each folder in the repository, create an
empty file called `.gitignore`. This ensures the folder structure ends
up in the repository. If this file is not created and the folder is left
empty, the folder will not end up in the repository until a file is
present. Once files are added to these folders, the `.gitignore` file
can be deleted.


Create the base folder structure with `hosts`, and a `README.md` file, so that the repository looks like the following:
```bash
    .
    |-- configuration
    |-- documentation
    |-- filter_plugins
    |-- group_vars
    |-- host_vars
    |-- playbooks
    |-- tasks
    |-- templates
    |-- README.md
     -- hosts
```


# Steps to organize repository
The organization of the repository includes a combination of necessary
Ansible framework files and folders, as well as user-defined files and
folders. Create a repository that scales, is easily navigated, and
supports the Ansible framework. Build a
folder structure that's best suited to the reflects the environment being automated.


Build the structure using empty folders and empty placeholder files that
suit the environment. Build a repository suitable for an enterprise
campus environment consisting of Cisco Catalyst devices running IOS, and
an enterprise data center consisting of Cisco Nexus devices running
NX-OS. Remember there are many Ansible modules available from other
vendors, if not running a Cisco network.

> **Important Note:** Git will not track or provide version control
for empty folders. When creating each folder in the repository, create an
empty file called `.gitignore`. This ensures the folder structure ends
up in the repository. If this file is not created and the folder is left
empty, the folder will not end up in the repository until a file is
present. Once files are added to these folders, the `.gitignore` file
can be deleted.


Create the base folder structure with `hosts`, and a `README.md` file, so that the repository looks like the following:
```bash
    .
    |-- configuration
    |-- documentation
    |-- filter_plugins
    |-- group_vars
    |-- host_vars
    |-- playbooks
    |-- tasks
    |-- templates
    |-- README.md
     -- hosts
```


Let's learn about the folder structure of our repository and the steps involved in its organization.

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

Organization of the Repository

Steps to organize repository