Book Image

Network Automation with Go

By : Nicolas Leiva, Michael Kashin
Book Image

Network Automation with Go

By: Nicolas Leiva, Michael Kashin

Overview of this book

Go’s built-in first-class concurrency mechanisms make it an ideal choice for long-lived low-bandwidth I/O operations, which are typical requirements of network automation and network operations applications. This book provides a quick overview of Go and hands-on examples within it to help you become proficient with Go for network automation. It’s a practical guide that will teach you how to automate common network operations and build systems using Go. The first part takes you through a general overview, use cases, strengths, and inherent weaknesses of Go to prepare you for a deeper dive into network automation, which is heavily reliant on understanding this programming language. You’ll explore the common network automation areas and challenges, what language features you can use in each of those areas, and the common software tools and packages. To help deepen your understanding, you’ll also work through real-world network automation problems and apply hands-on solutions to them. By the end of this book, you’ll be well-versed with Go and have a solid grasp on network automation.
Table of Contents (18 chapters)
1
Part 1: The Go Programming Language
6
Part 2: Common Tools and Frameworks
10
Part 3: Interacting with APIs

Streaming telemetry

Traditionally, network engineers have relied on the Simple Network Management Protocol (SNMP) to gather state information from network devices. Devices encode this information in a binary format using the Abstract Syntax Notation One (ASN.1) and send it to a receiver, typically a collector or a Network Management System (NMS). The latter would use one of the Management Information Bases (MIBs) to decode the received information and store it locally for further processing.

This has been the way we’ve done network monitoring for decades, but this approach has room for improvement:

  • The limited number of vendor-neutral data models means that even the basic things require unique MIBs that you may need to update every time you do a major network OS upgrade.
  • MIBs use a notation defined by a subset of ASN.1, which isn’t the best way to structure values. It has no concept of lists or key-value pairs. Instead, you must implement these with indexed...