Mastering Network Operations: The Power of Abstraction in Automation#

Jaakko Rautanen — Rautanen

• Why: Network automation done as a layered abstraction pipeline — the exact discipline the PM needs for cloud-native/fabric automation, presented as a transferable method rather than a product.
• What: A consultant's automation stack built around NetBox (with a custom "Ninja" plugin): abstract service models at the top, detailed network state in the middle, vendor-specific configurations at the bottom, with a configuration pipeline translating between layers. A worked example models a virtual network both as a detailed per-site entity and as a generic abstract service. A four-step design process is laid out — split the service into parts, design each data model (fields, types, references, create/edit/delete logic), implement and test as a NetBox plugin in Python, deploy with data migrations.
• How: Declarative, model-driven state in NetBox as the single source of truth, with code generation down the stack; lessons learned are: eliminate arbitrary rules, follow the declarative model, keep models generic.
• Where applicable: Broadly applicable to any shop that can run NetBox — this is a method, not a product. Caveat: the deck is high-level and conceptual; there are no metrics, scale figures, or postmortem detail, so treat it as a design pattern rather than a case study.