From YANG To YAML: How We Tamed the 5G Configuration Beast
summary
Operator and vendor collaboration produces a working GitOps prototype that converts YANG-derived intent into Kubernetes resources and pushes config to a CNF. A 2.5-day hackathon wires KRM manifests through KRO and SDC operators, uses intermediate resources for dynamic IPAM hydration, and validates YANG while reconciling to gNMI/NETCONF. Outcome: proof of concept succeeds but notes gaps — YAML lacks ordered-list semantics, NETCONF actions are non declarative, and KO is still early for all telco use cases.
AI-written summary · about
chapters (23)
- 0:00Collaboration journey intro
- 1:04Network equipment management evolution
- 2:09YANG and NetConf models
- 3:34Challenges in YANG configs
- 5:41Declarative vs action config
- 6:24Customer-vendor hackathon
- 7:29SDC and KRO tools
- 9:38Abstraction flow with KRO
- 11:43Hackathon outcomes
- 13:05GitOps with KRM benefits
- 14:55Automation in telecom impact
- 15:59Joint problem-solving
- 17:03Software delivery integration
- 18:08Collaboration scaling with CNTF
- 19:12Q&A session
- 20:17Operator CRD responsibility
- 22:01Multi-vendor telecom collaboration
- 23:05Model complexity in ops
- 24:50Open-source telecom future
- 26:35Industry-wide collaboration
- 27:19YANG to YAML status
- 27:46Industry implications
- 30:13Closing remarks
related talks
31mTaming Your Data Networks with the Power of NetDevOps
43mData Networks Neutrality with OpenConfig: Unveiling Challenges and Practical...
43mThe New Network Engineer’s CLI: Network APIs, Data Structures & Data Models
49mTaming Your Data Networks with the Power of NetDevOps
23mA GitOps approach to Zero Touch Provisioning for the 5G vRAN Ed...
47mExtending SDN to the Management Plane
27mFrom Spreadsheets to "Everything as Code"
06mKeynote: Beyond Automation: Kubernetes Success Requires a GitOps Mindset