Scaling Network Operations with Modular Ansible: A Multi-Environment Automation Framework#

Joseph Nicholson — NTT DATA, Global IP Network (AS2914)

• Why: A Tier-1 transit backbone operator's playbook for scaling Ansible across a multi-vendor WAN including DWDM — backbone routers across three vendors, optical across two — which matches the PM's WAN and interconnect focus.
• What: Six years of evolving an Ansible repository into a modular, multi-environment automation framework serving GIN's 800+ network elements (250+ backbone routers, 100+ DWDM elements across 5 continents, 40+ countries, 90+ PoPs), covering software upgrades, maintenance snapshots, traffic updates, and circuit testing — run from CLI and AWX.
• How: Dynamic inventory is a Python script pulling all device data (platform, vendor, OS, location, monitoring status) from GUMS, their in-house change-management system with 25+ years of lineage (started as Verio tooling in the late 1990s) — groups are built per vendor/platform/device-type on every playbook run. CI/CD pipeline gates merges on #FIXME tags and syncs revision vars to AWX hourly; task files are shared across playbooks with a careful include (dynamic) vs import (static) discipline; folder structure is per-playbook, subdivided per NOS.
• Where applicable: NTT GIN-specific in its dependence on GUMS and org history, but the transferable lessons are explicit: adopt pipeline and AWX APIs earlier, enforce repository naming policy, use dynamic inventory from your existing change system rather than maintaining static files, and understand include/import semantics before sharing task files. Honest about the trade-off: shared task files update many playbooks at once — and break many at once.