Impact of Network Automation
summary
Small network team moves internal routing from OSPF to BGP with a reusable Ansible roles workflow (Jinja2 templates, Netconf via Python libs) and automates firewall rules through CI/CD (Bamboo) so non-experts can push changes. Spine‑leaf clusters are entirely provisioned by automation—only racking and cabling remain manual. A BGP route servers setup running bird encodes site/ISP/action in communities to drain links, fail over data centers, or steer traffic into a one‑click DDoS switch; monitoring via OpenNTI/InfluxDB/Fluentd gives ~2s telemetry so changes are observable immediately.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:26Overview
- 8:20Firewall Configuration Automation
- 11:32Pineleaf Network Automation
- 15:40Route Servers
- 18:58Edge Routing
- 24:45Demo
- 31:11Monitoring
- 33:42Questions
related talks
11mRunning BGP in Data Centers at Scale
32mNetwork Automation: A Journey, Not a Destination
18mPast, Present, and Future of Network Operations
25mNetwork Automation Tools & Technology
29mUsing the Internet as Your Load-Balancer
41mHow to Build a Network Automation Stack From The Ground Up
50mJust Enough Network Automation to Get You Started
39mUsing BGP at OpenStack to interconnect workloads across clouds
