Going Beyond Vendor Zero Touch Provisioning

on YouTube ↗12m

" summary

Vendor ZTP stays as the bootstrap but an orchestration layer takes over: a lightweight Flask HTTP endpoint served by an event engine (StackStorm) accepts device HTTP boot requests (DHCP options), runs a sensor to collect facts via napalm, queries a source of truth for intended role and IPs, renders templates (or calls Ansible), and pushes config and images (SCP to a central image store). Multi‑vendor support uses separate HTTP endpoints per platform; the system generates configs on the fly and is proven to scale beyond tens of devices.

AI-written summary · about

" chapters (8)

1. 0:00Introduction to talk
2. 1:23Limitations of vendor ZTP
3. 3:07System architecture overview
4. 4:11Initial device boot workflow
5. 6:24Source of truth integration
6. 7:47Configuration rendering process
7. 8:53Vendor-neutral ZTP benefits
8. 10:41Scaling and transition strategies

" related talks

• 23mA GitOps approach to Zero Touch Provisioning for the 5G vRAN Ed...Yolanda Robla Mota, Ian Jolliffe · Kubernetes on Edge Day Europe 2021
• 25mNetwork Automation Tools & TechnologyCristian Sirbu · Network Automation Summit at Interop 2020
• 40mZero Trust, Zero Pain: A Practical Implementation with Intrinsic SecurityPere Monclus, Shawn Bass · RSAC 2021
• 01h 55mNetwork Automation using Ansible and PythonMatt Oswalt · PyOhio 2015
• 15mA carrier approach to efficient CPE managementMarco Marinello · SFSCON 2025
• 40mClarifying Zero Trust: The Model, the Philosophy, the EthosEvan Gilman, Doug Barth · LISA17
• 32mBuilding Zero Trust with EnvoyFlorin Coras, Pradheep Shrinivasan · EnvoyCon NA 2024
• 31mNetwork Automation Architecture: Platform vs Power ToolsDamien Garros · Network Automation Summit at Interop 2020