Engineering Panel Finale: A Tale of Different Network Automation Perspectives
summary
Starts with low‑risk, high‑return work: read‑only collection, validation checks and small automation for things like ACL churn—one team prototypes ACL management and gets it working in about two weeks. Use practical tools: Ansible, NAPALM, Netmiko, store structured source of truth as YAML/JSON inventory in Git, then move to dynamic inventory and a database. Invest in time‑series DBs, Flask REST endpoints and CI/CD. YANG and unified models remain hard; expect incremental integration, not a single silver bullet.
AI-written summary · about
chapters (12)
- 0:00Introduction and panel setup
- 1:31Starting network automation journey
- 7:42Low-risk automation wins and ROI
- 13:23Coding skills for network engineers
- 21:50Data modeling and YANG challenges
- 27:59Source of truth in automation
- 33:22Getting started with automation
- 42:32Common automation pain points
- 45:01Evolution of automation tools
- 50:12Education and skill gaps
- 57:07Choosing the right tool
- 1:00:02Closing remarks and Q&A
related talks
31mEnterprise Transformation With Network Automation Panel
25mNetwork Automation Tools & Technology
31mWelcome & State of Network Automation
31mNetwork Automation Architecture: Platform vs Power Tools
32mKeys to Success for Enterprise Network Automation
02mNetwork Automation Summit preview
18mPast, Present, and Future of Network Operations
51mOur Journey to a self-healing network