Network to Code Networking Summit at Interop 2019
2019-05-20..2019-05-23
Las Vegas, United States
| title | author | length |
|---|---|---|
| Opening Remarks & The State of the Industry | Jason Edelman | 29m |
Network automation progresses from proofs of concept to messy production reality: early SDN/OpenFlow demos mostly stall while NSX and SDKs show viable paths… | ||
| Beyond Configuration Management | Daryn Johnson, Jere Julian | 59m |
Live demo shows how configuration management becomes actionable: code goes to Git, a CI job runs a battery of tests using the open library mint to catch errors… | ||
| Efficient Navigation for Modern Networks | Ritesh Mukherjee | 13m |
128 Technology builds a session‑based routing system that keeps per‑flow state and routes by service identity rather than IP topology, claiming faster… | ||
| Principles of Network Automation | Ken Celenza, Jere Julian | 58m |
Starts from concrete questions: who uses the automation and what is the current lead time, then targets the slow parts (ticket copying and approvals) to cut a… | ||
| The New Network Engineer’s CLI: Network APIs, Data Structures & Data Models | Jason Belk | 43m |
Clear comparisons of APIs and models: NETCONF over SSH uses XML and continuous sessions while RESTCONF/REST with JSON uses HTTP verbs and stateless requests… | ||
| Practices to Improve the Performance, Scale and Efficiency of Your Ansible Playbooks | Ajay Chenampara | 31m |
Ansible controller load comes from pushing modules and executing them on endpoints, so size controllers by CPU and memory (roughly 100 MB per fork and default… | ||
| A Practical Look at NetDevOps | Hank Preston | 56m |
Live demo builds a full NetDevOps pipeline on a laptop: a netsim-based dev network synced to Cisco NSO, configs edited as YAML, pushed with Ansible + NSO, and… | ||
| Network Automation Transformation Phase 0: Source of Truth | John Anderson, Jeremy Stretch | 51m |
Argues that a single authoritative source of truth per data domain (for example device inventory or IPAM) is required for reliable automation, using NetBox as… | ||
| How to Build a Network Automation Stack From The Ground Up | Damien Garros | 41m |
Goes from zero automation to two data centers, a global backbone and multiple PoPs in months by building a concrete stack: NetBox as source of truth feeding an… | ||
| Engineering Panel Finale: A Tale of Different Network Automation Perspectives | Peter Allocca, Nick Russo, Kirk Byers, Matt Davy, Ken Celenza | 01h 01m |
Starts with low‑risk, high‑return work: read‑only collection, validation checks and small automation for things like ACL churn—one team prototypes ACL… | ||
| Going Beyond Vendor Zero Touch Provisioning | John Anderson | 12m |
Vendor ZTP stays as the bootstrap but an orchestration layer takes over: a lightweight Flask HTTP endpoint served by an event engine (StackStorm) accepts… | ||
| Self-service Network Automation Using Slack | Jeremy Schulman | 36m |
A Slack-based self‑service portal runs production Ansible playbooks via Ansible Tower, reads inventory from netbox as source of truth, and kicks off tasks like… | ||
| Network Automation: A Journey, Not a Destination | Matt Davy | 32m |
Argues that start with validation first because fifteen–twenty show commands often catch ~75% of regressions and you need answers faster than ten minutes… | ||
| Just Enough Network Automation to Get You Started | Claudia de Luna | 50m |
Automation rescues a six‑month rollout with only two months left by replacing manual config changes with scripted collection and templating. The demo compares… | ||
| Automation for Bureaucracies | Nick Russo | 42m |
Claims an automation pipeline that generates a deployable zip packet per site containing configs, a PDF installation packet, auto-generated diagrams and… | ||
| Shareable Working Environments | Damien Garros | 09m |
Shows how to use Docker as a reproducible working environment: a Dockerfile with a base image and pip requirements produces identical Python setups… | ||
| ServiceNow Integration | Jason Edelman | 13m |
ServiceNow maps directly to automation systems and triggers Ansible playbook runs based on ticket fields (network domain, inventory lookup like NetBox)… | ||
| A Journey or There and Back Again | Neil Bredski | 14m |
Seven-month migration that moves legacy databases and services into a new anycast-style fabric, constrained by no budget and IOPS limits. Team consolidates… | ||
| Closing Remarks | Jason Edelman | 06m |
Emphasizes that teams document manual workflows before automating, because common processes hide 20–30 decision points that break naive scripts; recommends… | ||
| Highlighting Network Automation Bright Spots with NRE Labs | Matt Oswalt | 45m |
Platform demonstrates an open source, browser‑based lab for network automation that runs per‑user isolated topologies in Docker images scheduled by Kubernetes… | ||
| Move Fast and Don’t Break Things: Pre-Deployment Validation | Samir Parikh | 36m |
An offline, config-driven validator called Batfish analyzes normalized device configs and builds routing, forwarding and abstract behavior models to prove… | ||
| nothing matches | ||