The role of the Network Engineer in the DevOps era
summary
Claims that network teams largely close the DevOps gap by 2022 and that network automation drives better design and faster ops, illustrated by a working architecture: source of truth (NetBox / tobot), an orchestrator (AWX + Ansible / Terraform), Telemetry (Telegraph → Grafana) and user frontends (ChatOps Mattermost). Examples include automated on‑prem-to‑cloud firewall changes with pre/post validation and rollback, deployments across 500 routers, an 80‑person network automation team, and a 24,000‑member community — all reported as implemented for customers.
AI-written summary · about
chapters (9)
- 0:00Introduction and goals
- 5:20Networking in 2022
- 9:34Why networking is special
- 13:29Network abstraction levels
- 17:24Bridging DevOps and networking
- 23:56Network automation architecture
- 29:19Automation implementation example
- 37:21Learning path for engineers
- 44:54Q&A and concluding thoughts
related talks
31mWelcome & State of Network Automation
18mPast, Present, and Future of Network Operations
49mTaming Your Data Networks with the Power of NetDevOps
32mKeys to Success for Enterprise Network Automation
31mTaming Your Data Networks with the Power of NetDevOps
29mOpening Remarks & The State of the Industry
41mHow to Build a Network Automation Stack From The Ground Up
43mThe DevOps of Everything