Book Image

Mastering Python Networking - Third Edition

By : Eric Chou
Book Image

Mastering Python Networking - Third Edition

By: Eric Chou

Overview of this book

Networks in your infrastructure set the foundation for how your application can be deployed, maintained, and serviced. Python is the ideal language for network engineers to explore tools that were previously available to systems engineers and application developers. In Mastering Python Networking, Third edition, you’ll embark on a Python-based journey to transition from traditional network engineers to network developers ready for the next-generation of networks. This new edition is completely revised and updated to work with Python 3. In addition to new chapters on network data analysis with ELK stack (Elasticsearch, Logstash, Kibana, and Beats) and Azure Cloud Networking, it includes updates on using newer libraries such as pyATS and Nornir, as well as Ansible 2.8. Each chapter is updated with the latest libraries with working examples to ensure compatibility and understanding of the concepts. Starting with a basic overview of Python, the book teaches you how it can interact with both legacy and API-enabled network devices. You will learn to leverage high-level Python packages and frameworks to perform network automation tasks, monitoring, management, and enhanced network security followed by Azure and AWS Cloud networking. Finally, you will use Jenkins for continuous integration as well as testing tools to verify your network.
Table of Contents (18 chapters)
Other Books You May Enjoy

Ansible 2.8 playbook example

We have briefly talked about the addition of network connection changes in Ansible playbooks, starting with version 2.5 and beyond. Along with the changes, Ansible also released a network best practices document: Let's build an example based on the best practices guide. Since there are multiple files involved in this example, the files are grouped into a subdirectory named ansible_2-8_example with the course code files.

Either use the system installed version or switch back to Ansible version 2.8 using the Git source code as illustrated before:

$ ansible --version
ansible 2.8.5

In our previous examples, we mainly used just the inventory host file to contain both the inventory information as well as the associated variables. In this example, we will offload the variables to a separate directory named host_vars:

$ tree.