SDN and metrics from the SDOs
3 likes384 views
This document discusses SDN and metrics from various standards development organizations (SDOs). It notes that many SDOs are developing YANG data models for network automation using model-driven APIs. There is growth in YANG models at the IETF and other SDOs like BBF, IEEE, MEF, and OpenConfig. However, coordination is needed between SDOs to reduce costs as the data models need to work together to create network services. A YANG catalog is proposed to help organize the industry and provide a common inventory of all YANG modules across SDOs and vendors.
Ad
More Related Content
What's hot (20)
Similar to SDN and metrics from the SDOs (20)
Ad
More from Open Networking Summit (20)
Ad
Recently uploaded (20)
SDN and metrics from the SDOs
- 1. SDN and metrics from the SDOs: Report from Benoit Claise (IETF OPS Area Director) Dave Ward [email protected] 2017.04.06
- 2. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Open Source and SDOs Landscape SvcsManagement&ControlInfrastructure Product, Services & Workloads CI/CD Disaggregated Hardware Network Control Operating Systems Cloud & Virtual Management Orchestration, Management, Policy Application Layer / App Server IO Abstraction & Data Path SystemIntegration&TestAutomation Network Data Analytics Automation of Network + Infrastructure + Cloud + Apps + IOT Standards Linux Foundation Hosted Outside Linux Foundation
- 3. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • APIs derived from the data models: • Data models = definitions and constraints • The protocol: NETCONF, RESTCONF, GRPC • The encoding: JSON, XML, protobuf • The programming language: Python, Ruby, Java, C, Erlang, ... • Industry focusing on YANG as the data modeling language for services and devices Why Data Model-Driven Management? BRKNMS-2032 3
- 4. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Data Models Driven Set of APIs BRKNMS-2032 4
- 5. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • Scripting: easy to create, hard to maintain/clean-up => Data model-driven set of APIs • However, Data Model-Driven Management Data Models = APIs Automation is as good as your data models and your toolchains BRKNMS-2032 5
- 6. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Generation of Model-Driven APIs Using YANG Development Kit (YDK) YAN G YANG YANG Data Models (YANG) API Generator DocsPython C++ : : Ruby go Docs Docs Docs C♯ Docs YDK-gen YDK-Py YDK 6BRKNMS-2032
- 7. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Encoding (serialization) Data Model Language (schema language) Data Modeling (schema) Protocol YANG YANG Data Model XML JSON RESTCONFNETCONF ProtoBuf GRPC (HTTP/2) Thrift Non Standard Possible links YANG Development KitApplication Prog. Language Python C++ Any language 7
- 8. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Data Model Driven Management: Example Acting on resources GET : Gets a resource POST : Creates a resource or invoke operation PUT : Replaces a resource DELETE : Removes a resource Module my-interfaces { { namespace ”com.my-interfaces”; container interfaces { list interface { key name; leaf name { type string; } leaf admin-status { type enum;} rpc flap-interface { input { leaf name { type string; } } output { leaf result { type boolean; } } } POST /restconf/operations/my-interfaces:flap-interface + JSON/XML Form Data (including name) Response will have JSON/XML result GET /restconf/data/my-interfaces:interfaces GET /restconf/data/my-interfaces:interfaces/interface/<some name> PUT /restconf/data/my-interfaces:interfaces/interface/<some name> + JSON/XML Form Data (name, admin-status) DELETE /restconf/data/my- interfaces:interfaces/interface/<some name> BRKNMS-2032 8
- 9. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • RESTCONF: no notion of transaction • RESTCONF: no notion of lock • RESTCONF: no notion of candidate config and commit • RESTCONF: so no notion of two phase commit • RESTCONF: no <copy-config> • RESTCONF: some more granularity for query => "config", "nonconfig“, "all". • RESTCONF: XML or JSON (while NETCONF is XML only) RESTCONF versus NETCONF: Summary NETCONF might be better for router and switches RESTCONF might be better for controller north-bound interface 9
- 10. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public YANG Tsunami in the Industry 10
- 11. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Data Model Location and Type - Native models - Standard models - Proprietary extensions to standard models - Operator defined services draft-ietf-netmod-yang-model-classification-00.txt IETF draft-ietf-netmod-yang-model-classification 11
- 12. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IETF: Timeline of Important Specifications ‘10 ‘11 ‘12 ‘13 ‘14 ‘15 ‘16 YANG 1.0 RFC6020 October 2010 Interface and IP Modules RFC7223, RFC7277 May, June 2014 Common YANG Data Types RFC6991 July 2013 JSON Encoding RFC7951 August 2016 Routing Management RFC8022 November 2016 NETCONF 1.0, SSH Mapping RFC4741, RFC4742 December 2006 NETCONF 1.1 RFC6241 June 2011 NETCONF Access Control RFC6536 March 2012 RESTCONF Protocol RESTCONF January 2017 NETCONF over TLS + x.509 RFC7589 October 2016 12 ‘17
- 13. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IETF: YANG Models Growth http://claise.be/IETFYANGPageCompilation.png New YANG validator Tool: pyang patch pyang 1.6 (YANG 1.1) Active help to authors 13
- 14. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IETF Drafts with YANG Modules 14 Vendors: • Cisco: 74 • Huawei: 71 • Juniper: 46 • Ericsson: 25 • Ciena: 14 • ZTE: 8 • Brocade: 6 • Infinera: 6 • Metaswitch: 5 • Alcatel-Lucent: 4 • Intel: 1 Operators: • Orange: 13 • Telefonica: 6 • DT: 4 • Level 3: 4 • Google: 2 • Verizon: 2 • AT&T: 2 • China Mobile: 2 • China Unicom: 1 • Softbank: 1 “YANG” companies: • Yumarkworks: 6 • Tail-f: 5
- 15. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IETF Focus • YANG language definition • Protocols (NETCONF, RESTCONF) and encoding (JSON, XML) • Data Model-driven Telemetry with Pub Sub • Network elements / technology YANG models • Main focus: routing • Only two service YANG models (by choice): • L3VPN, with RFC 8049 • L2VPN chartered • Location • RFC-based YANG modules • Draft-based YANG modules (extracted from drafts!) 15
- 16. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IETF Focus: Pub/Sub (Telemetry) 16
- 17. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • 802.1 • Two active YANG projects in progress: 802.1Xck (Port-Based Network Access Control Amendment: YANG Data Model) and 802.1Qcp (Bridges and Bridged Networks Amendment: YANG Data Model) • Initial work on a LAG (802.1AX) YANG model has been started as part of the next amendment to 802.1AX. • 802.3: • Approved a study group: Standard for Ethernet YANG Data Model Definitions • Regular IETF/IEEE coordination calls • Location • https://github.com/YangModels/yang/tree/master/standard/ieee IEEE 17
- 18. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • 192 YANG modules • Common: subscriber, interfaces, ethernet, PPPoE, etc. • Fiber to the Distribution Point (FTTdp) Distribution Point Unit (DPU): FastDSL (FAST/VDSL container), G.hs (FAST/VDSL selection), G.fast, VDSL, MELT+SELT (line tests) • Passive Optical Networking (PON): • SDN access node • Participation to the IETF hackathon • Integration with the YANG catalog • Updated their licensing terms: all work-in-progress YANG modules now in github, to be picked up this toolchain • Location:ttps://github.com/YangModels/yang/tree/master/standard/bbf Broadband Forum 18
- 19. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public CableLabs • CCAPv3.1 system configuration and state • RPHY Configuration • Location: • http://mibs.cablelabs.com/YANG/DOCSIS/ • The new YANG Models developed by the VPI WG will also be published at the same location in a couple of weeks. 19
- 20. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • Operators-led YANG models • Google, AT&T, British Telecom, Microsoft, Facebook, Comcast, Verizon, Level3, Cox Communications, Yahoo!, Apple, Jive Communications, Deutsche Telekom / TeraStream, Bell Canada • Focus: 93 network elements YANG models • Routing (BGP, ISIS, rib, network-instance), routing policy, interfaces • Layer2 (vlan, spanning tree), ACL, optical transport, mpls, etc. • Some YANG models not completely aligned with the IETF • Location: • https://github.com/openconfig/public OPENCONFIG www.openconfig.net 20
- 21. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • Streaming Telemetry specifications and configuration • gRPC Network Management Interface (gNMI) • Protocol: gRPC • Encoding: protobuf OPENCONFIG www.openconfig.net 21
- 22. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • Redfish: goal of addressing all the components in the data center with a consistent API • Goal: use the networking YANG models developed in the IETF, convert them to CSDL (common schema definition language: a JSON encoding of Odata • YANG to CSDL specifications, to convert the IETF networking YANG models. • Goal: YANG device profile for data center network switches - top-of- rack switches DMTF 22
- 23. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public MEF • two standard device-level YANG Models (quite old, proposal to update them) • MEF 38 is Service OAM Fault Monitoring (CFM) • MEF 39 is Service OAM Performance Measurement (G.8013/Y.1731 PM) • Open projects to create YANG models for: • Carrier Ethernet services, i.e. API from business apps to service orchestrator ("legato"), for EVC based services as defined in MEF 10.3 and OVC based services as defined in MEF 26.2 • Network Resource Provisioning, i.e. API from Service Orchestrator to Domain Controller ("presto") • IP Services expected to eventually augment IETF L3SM model • Note: YANG for inter-provider APIs also expected. • Location (for MEF members): • https://wiki.mef.net/display/MTA/YANG+Modules+for+MEF+Services • Github 23
- 24. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public MEF Architecture 24
- 25. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Open ROADM • The Open ROADM Multi-Source Agreement (MSA) defines interoperability specifications for Reconfigurable Optical Add/Drop Multiplexers (ROADM). Included are the ROADM switch as well as transponders and pluggable optics. Specifications consist of both Optical interoperability as well as YANG data models. • Open ROADM MSA - Home • YANG modules: GitHub - OpenROADM/OpenROADM_MSA_Public 25
- 26. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public sysrepo • Open-source framework that brings NETCONF/YANG management to any UNIX/Linux application • Ex: dnsmasq mangement via NETCONF using Sysrepo: http://www.sysrepo.org/dnsmasq-demo • Location: • https://github.com/sysrepo/sysrepo 26
- 27. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public SDOs Alignement and Trajectory draft-ietf-netmod-yang-model-classification-00.txt 27
- 28. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Open Source and SDOs Landscape SvcsManagement&ControlInfrastructure Product, Services & Workloads CI/CD Disaggregated Hardware Network Control Operating Systems Cloud & Virtual Management Orchestration, Management, Policy Application Layer / App Server IO Abstraction & Data Path SystemIntegration&TestAutomation Network Data Analytics Automation of Network + Infrastructure + Cloud + Apps + IOT Standards Linux Foundation Hosted Outside Linux Foundation
- 29. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Coordination is Really Required, now! BRKNMS-2032 29
- 30. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Coordination is Really Required, Now! • Previous picture is about the IETF YANG models • New dimensions: different SDOs/Opensource projects • New dimension: versioning • These YANG models must work together to create services • Good problem to have: All YANG models arrive at the same time • As opposed to MIB modules in the past • Standard Development Organizations (SDOs) can’t work in isolation: industry wide coordination is required BRKNMS-2032 30
- 31. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public • With a YANG catalog! • The related metadata regarding implementation, maturity level, model type, etc (based on the openconfig catalog as a starting point) • The inventory of all YANG modules, cross SDOs, cross vendors • SDOs on board: IETF, BBF, IEEE, etc. • Some vendors on board • Just started: Output of the IETF hackathon, two weeks ago How to Organize the industry? www.yangcatalog.org 31
- 32. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public www.yangcatalog.org BRKNMS-2032 32
- 33. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKNMS-2032 33 YANG Catalog: Search
- 34. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKNMS-2032 34 YANG Catalog: Dependency
- 35. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKNMS-2032 35 YANG Catalog: Code Generation
- 36. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Open Source Networking SvcsManagement&ControlInfrastructure Product, Services & Workloads CI/CD Disaggregated Hardware Network Control Operating Systems Cloud & Virtual Management Orchestration, Management, Policy Application Layer / App Server IO Abstraction & Data Path SystemIntegration&TestAutomation Network Data Analytics Automation of Network + Infrastructure + Cloud + Apps + IOT Standards Linux Foundation Hosted Outside Linux Foundation
- 37. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public ETSI NFV BRKNMS-2032 37
- 38. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Summary and Key Messages • Automation and programmability are required these days • Data Modeling-driven set of APIs is key for automation • The key is the data models • YANG is the data modeling language for configuration and monitoring: a full, formal contract language with rich syntax and semantics to build applications on. • Many YANG data model developments • In different standard development organizations (but primarly at the IETF), • In opensource • The SDOs start to align • Time to synchronize to reduce the OPEX BRKNMS-2032 38
- 39. SDN and metrics from the SDOs: Report from Benoit Claise (IETF OPS Area Director) Dave Ward [email protected] 2017.04.06