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

## The assemble module

The Ansible **assemble** module is used to combine the smaller, modular, fragmented templates and
build, or assemble, them into a single Jinja2 template. The following lines indicate the source of the
fragments, or Jinja2 templates, and the destination where to compile the assembled template: 
```txt
assemble:
 src: ../../templates/configurations/ios/
 dest: '../../templates/documentation/ios/ios_combined.j2' 
```

Write the following `documentation.yml` Ansible playbook to generate both the configuration file per device and the Markdown documentation, using the template above for the core, distribution, and
access layers. 

Examine and breakdown the following playbook: 

# The assemble module

The Ansible **assemble** module is used to combine the smaller, modular, fragmented templates and
build, or assemble, them into a single Jinja2 template. The following lines indicate the source of the
fragments, or Jinja2 templates, and the destination where to compile the assembled template: 
```txt
assemble:
 src: ../../templates/configurations/ios/
 dest: '../../templates/documentation/ios/ios_combined.j2' 
```

Write the following `documentation.yml` Ansible playbook to generate both the configuration file per device and the Markdown documentation, using the template above for the core, distribution, and
access layers. 

Examine and breakdown the following playbook: 

Let's take a look at the Ansible assemble module and how to use it in playbook tasks.

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

Assemble

The assemble module