Past, Present, and Future of Network Operations
summary
Argument that networking finally adopts automation, with concrete parts: modern boxes expose Linux/open APIs and streaming telemetry replaces SNMP; infrastructure keeps a canonical backend model of devices and links; Ansible renders that data into device config; changes flow through GitHub branches, a CI pipeline and staging route servers to test a BGP-based SDN route server before pushing global BGP. Runs software services on switches to act as hardware load balancers; approach reports working and prevents human-propagated outages.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:16History
- 2:40The Network
- 3:03Hacks
- 3:55Certifications
- 4:44Metrics
- 5:24Service Providers
- 5:46Enable and Open Config
- 6:22Streaming Telemetry
- 6:47Root Access
- 7:37Use Cases
- 8:01Network Management
- 9:24API Chatups
- 10:32Running Code
- 13:03CI Pipeline
- 13:37Summary
- 15:32Questions
related talks
52mThe role of the Network Engineer in the DevOps era
29mOpening Remarks & The State of the Industry
31mWelcome & State of Network Automation
41mHow to Build a Network Automation Stack From The Ground Up
31mTaming Your Data Networks with the Power of NetDevOps
32mKeys to Success for Enterprise Network Automation
33mSystems Automation: Past, Present and Future
41mImpact of Network Automation