Book Image

Mastering Python Networking

Book Image

Mastering Python Networking

Overview of this book

This book begins with a review of the TCP/ IP protocol suite and a refresher of the core elements of the Python language. Next, you will start using Python and supported libraries to automate network tasks from the current major network vendors. We will look at automating traditional network devices based on the command-line interface, as well as newer devices with API support, with hands-on labs. We will then learn the concepts and practical use cases of the Ansible framework in order to achieve your network goals. We will then move on to using Python for DevOps, starting with using open source tools to test, secure, and analyze your network. Then, we will focus on network monitoring and visualization. We will learn how to retrieve network information using a polling mechanism, ?ow-based monitoring, and visualizing the data programmatically. Next, we will learn how to use the Python framework to build your own customized network web services. In the last module, you will use Python for SDN, where you will use a Python-based controller with OpenFlow in a hands-on lab to learn its concepts and applications. We will compare and contrast OpenFlow, OpenStack, OpenDaylight, and NFV. Finally, you will use everything you’ve learned in the book to construct a migration plan to go from a legacy to a scalable SDN-based network.
Table of Contents (22 chapters)
Title
Humble Bundle
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
12
OpenStack, OpenDaylight, and NFV

Physical switch selection


Physical switch selection is always an interesting question to ask when building your network. The term 'switch' in this context should be broadly interpreted as both L2 and L3 devices. In the SDN world, where we separate the control and data plane, any network function, such as routing, switching, firewall, monitoring, or firewall function, are software function while we reduce the physical packet transport into flows. The line between software-based versus hardware switch is almost non-existent when it comes to management and control plane constructs. However, we still need to be concerned with hardware capacity when it comes to building our network infrastructure.

If you draw a comparison between network engineering and systems engineering when purchasing servers, a system engineer would consider hardware specifications, such as CPU, memory, and storage, while separating the software aspects of operating system and software packages. The two sides of hardware...