Mastering Network Operations: The Power of Abstraction#

Jaakko Rautanen

• Why: The concrete "how do I actually build abstract services" talk the design-first theme needs — with a working production stack, an open-sourced plugin, and a demo that goes from three inputs to deployed MPLS L3VPN service.
• What: A layered automation stack in which NetBox-native data is detailed state, and a new top layer of "abstract services" (NetBox plugins) collapses daily operations to a handful of variables per service.
• How: An example "Virtual Network" service (VRF + customer MPLS-site attachments) needs dozens of correctly-allocated details (prefixes, VLANs, loopbacks, route-targets, ASNs); the abstract model reduces user input to name, template, and site attachment, with all other values allocated automatically from template-defined ranges. Config delivery uses NetBox Config Templates (Jinja), deployment varies by vendor, and a diff view against live state precedes a one-click push. The team open-sourced the Ninja NetBox plugin for generating interactive diagrams or any text output from Jinja. Lessons: purge arbitrary encoding rules from IP/VLAN schemes, go declarative (they replace entire device configs each push), keep models generic with templates.
• Where applicable: The implementation is a media-network MPLS/VPN environment, but the pattern (service abstraction layer over NetBox, template-driven allocation, full-config declarative pushes) is directly adoptable by anyone already running NetBox.