Networking.com

5 phases to build a network automation architecture

By Terry Slattery

Most network managers are naturally interested in network automation. But how should they plan their network automation architecture, and which elements should they tackle first?

The number of network automation architectures in the world might be on par with the number of networks. The trick is to create an architecture that's independent of any particular product, whether it's commercial or open source. In this article, we present an architecture and a suggested order in which to implement the elements.

Start with a set of requirements that reflect architectural functions, such as the automation engine. Each of those functions has inputs and outputs that determine how the various elements interact. Then, follow a phased approach that increases automation capabilities as the new technology and processes in the preceding phase are integrated and adopted.

The architectural functions and phases

Like so much else in life, most network automation implementations follow a "crawl, walk, run, fly" progression. The early phases provide basic capabilities that perform read-only operations on the network devices. Later phases begin modifying device configurations. The final phases automate complete processes, including tests on virtual instances of the production network prior to final rollout. Some functions might be moved to other phases to match the needs of the organization.

Phase 1: Start read-only processes

Phase 1 provides basic functionality through three functions: the automation orchestration system, the UI and the device abstraction layer. This phase starts with automated, read-only processes that archive configurations, collect troubleshooting data and validate network configurations against templates.

The elements in Phase 1 include the following:

Phase 2: Add a network source of truth

Phase 2 adds a network source of truth (NSoT) database and an interface to a trouble-ticketing system. The elements in this phase include the following:

Phase 3: Store configuration templates and scripts

Phase 3 begins the transition to an infrastructure-as-code operational model. The elements in this phase include the following:

Phase 4: Implement network feedback

Phase 4 provides a feedback mechanism from the network. Up to this point, the network has provided little feedback, except for validation checks against the NSoT data. The elements in Phase 4 include the following:

Phase 5: Automate change testing and validation

Phase 5, the last phase in the architecture, is to automate change testing and validation. Here's what's involved:

The end goal

The network automation architecture described in this article is a framework. Network teams can modify it to fit their organization's needs and to accommodate the capabilities of the tools they select.

The eventual goal is to build a continuous integration, continuous delivery and continuous deployment process in which small, well-defined network changes are automatically deployed only after passing stringent tests. This practice, known as NetOps or NetDevOps, enables teams to migrate their network to infrastructure as code using many of the same concepts and techniques as successful software development methods.

Editor's note: This article was updated to improve the reader experience.

Terry Slattery is an independent consultant who specializes in network management and network automation. He founded Netcordia and invented NetMRI, a network analysis appliance that provides visibility into the issues and complexity of modern router- and switch-based IP networks.

05 Dec 2023

All Rights Reserved, Copyright 2000 - 2024, TechTarget | Read our Privacy Statement