Our Journey to a self-healing network
summary
Red Hat IT moves from golden configs and copy/paste to a code-defined network using Ansible and an abstraction layer, delivering a working pipeline in under 12 months that pushes Jinja2 templates via dynamic inventory and a console server. The demo deploys a DC-like fabric of six devices in about six minutes and auto-registers them with monitoring (Kapacitor/Telegraf), but the final link—alert→Ansible Tower automated remediation—is not yet active. Key tools: Ansible Tower, dynamic inventory, 6 devices deployed in ~6 minutes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:12Agenda
- 1:54Milestones
- 2:42Manual deployment
- 10:18Current status
- 10:57Vendors
- 15:20Network Automation
- 18:07Demo
- 37:06QA
- 39:46Team
- 41:21People
- 42:41BGP
- 43:26What we are using
- 45:26Alerts
- 47:36Example
- 48:56Dynamic Inventory
related talks
44mAnsible powered Network automation
01h 55mNetwork Automation using Ansible and Python
50mJust Enough Network Automation to Get You Started
30mIntroduction to Ansible for Network Automation
25mNetwork Automation Tools & Technology
41mHow to Build a Network Automation Stack From The Ground Up
27mNetwork as Code
36mSelf-service Network Automation Using Slack
