November 22, 2026

Systems Approach Founders Discuss the Evolution of Network Operations and the Shift Toward Reality-Based Design

The conversation touched on the tension between vendor-specific "value-adds" and the operator’s need for consistency. When vendors differentiate their products through unique management interfaces, it often creates "operational silos" that hinder automation efforts. Reality-based operations, therefore, require a commitment to finding common ground and leveraging tools that can normalize data across the entire infrastructure.

Designing for Operations: A Paradigm Shift

Perhaps the most significant takeaway from the discussion was the argument that networks must be designed for operations from the very beginning. Historically, network design has prioritized metrics like throughput, latency, and hardware cost. While these remain important, the authors suggested that "operability" should be a first-class citizen in the design phase.

Designing for operations involves asking hard questions during the architectural stage: How will this network be monitored? How will we verify that a configuration change achieved the intended result? How easily can an automated system detect a failure in this specific topology?

Peterson and Davie emphasized that many operational headaches are actually "self-inflicted" by complex designs that do not account for the limitations of human operators or the current state of automation tools. By simplifying the architecture and focusing on "intent-based" models—where the operator defines what the network should do rather than how each device should do it—organizations can significantly reduce the risk of outages and improve agility.

The Role of Automation and Verification

As the discussion moved into the practicalities of modern management, the focus shifted to the tools that enable reality-based operations. Two specific projects were highlighted as essential components of the modern toolkit: OpenConfig and NAPALM.

OpenConfig, an informal working group of network operators, has been instrumental in developing vendor-neutral data models based on YANG. The authors noted that OpenConfig represents a "bottom-up" approach to standardization, driven by the needs of large-scale operators rather than the dictates of a formal standards body. By providing a consistent way to manage devices from different vendors, OpenConfig is a key enabler of the reality-based operations the authors advocate for.

Similarly, NAPALM (Network Automation and Programmability Abstraction Layer with Multivendor support) was discussed as a vital tool for engineers working in the trenches. NAPALM provides a unified API for interacting with different network operating systems, allowing engineers to write automation scripts that work across a diverse fleet of hardware.

Beyond simple configuration, the guests also stressed the importance of verification. It is no longer enough to "push" a configuration and hope for the best. Modern operations require closed-loop systems that can verify the state of the network in real-time. This involves using telemetry to ensure that the actual state of the network matches the intended state defined by the operator.

Democratizing Knowledge Through Open Source

The discussion concluded with a look at the future of networking education. The "Systems Approach" project has expanded to include specialized resources like Edge Cloud Operations: A Systems Approach and a dedicated chapter on operating networks in the main text.

By making these resources available for free online, Davie and Peterson are aiming to democratize the high-level knowledge that was once the exclusive domain of a few elite institutions or large-scale cloud providers. They expressed a belief that the next generation of network engineers needs to be as comfortable with Python and APIs as their predecessors were with serial cables and the command line.