in NTT Com 4 Packet & Optical Transport Domain Access Domain VLAN/OTN IP/MPLS OTN / WDM Transport NW Controller CLI NETCONF SNMP Telemetry Streaming Telemetry Data Center User Site Orchestrator DC NW Ctrl Cloud Ctrl SD-WAN Ctrl OSS/BSS Machine Learning DC NW Ctrl SR/EVPN NW Controller
& Optical Transport Domain Access Domain VLAN/OTN IP/MPLS OTN / WDM Transport NW Controller CLI NETCONF Data Center User Site Orchestrator DC NW Ctrl Cloud Ctrl SD-WAN Ctrl OSS/BSS DC NW Ctrl SR/EVPN NW Controller NSO - Now we Transport SDN team use NSO in production Vendor EMS/NMS Vendor EMS/NMS Vendor Solutions Vendor Solutions Vendor EMS/NMS In-source - API Orchestration - Global transaction management After 2016
& Optical Transport Domain Access Domain VLAN/OTN IP/MPLS OTN / WDM CLI NETCONF Data Center User Site Orchestrator DC NW Ctrl Cloud Ctrl SD-WAN Ctrl OSS/BSS DC NW Ctrl SR/EVPN NW Controller NSO - Share our good experiences with NSO to other teams/domains - To break down the silos Vendor EMS/NMS Vendor EMS/NMS Vendor Solutions Vendor Solutions Vendor EMS/NMS In-source - API Orchestration - Global transaction management Our Recent Activity Transport NW Controller
In-source Development Development & Unit Test Requirement Design Developer Reviewer Review Verify propose QA Task Management Documentation Integration push Deploy CI Web hook Build Automation + Automation Release Test management Process Infrastructure Communication Virtual Environment File Sharing API First Development Environment
Fabric 1 (NETCONF NED) over 1000 Green Field Service, OSS Orchestrator, OSS Frontend Core VPLS 2 (CLI NED) over 300 Green Field CLI NED Service, Orchestrator, OSS Metro Ether Ring 1 (CLI NED) over 150 Green Field CLI NED, Service Orchestrator, OSS Frontend Dev Experiences with NSO 11 2016 2018 2017 Prod Domain: Device types: Num. of Devices: Field Out-source: In-source: SR/EVPN(Testbed) 1 (NETCONF NED) 6 Green Field N/A, all in-source 2016 2018 2017 PoC Domain: Device types: Num. of Devices: Field: Out-source: Disaggregated Transport 15 (NETCONF NED) 25 Green Field N/A, all in-source VPLS(Testbed) 1 (CLI NED) 12 Brown field N/A, all in-source
Network 12 From all-in-one ROADM to disaggregated optical components - Expecting CAPEX reduction, but need northbound integration - We’d integrated 10 vendors’ devices in our lab using NSO AWG AWG Vendor D Vendor C Vendor B Vendor A Vendor D Vendor C Vendor B Vendor A WSS/ EDFA WSS/ EDFA L2SW L2SW NETCONF/YANG AWG AWG WSS/ EDFA WSS/ EDFA Transport SDN Controller C driver D driver E driver B driver A driver F driver Vendor EMS Proprietary CLI Proprietary YANG
13 Well-created multi-vendor network solution - Really easy implementation / integration with orchestrator - Definitely enhance the network operation quality Useful not only for production but also incubation - Especially for multi-vendor network like transport dis-aggregation Have enough capability to support brownfield deployment - Service Discovery, Re-deploy, Reconciliation, Ref-count check
14 It might be difficult to create perfect NETCONF/YANG - Almost half of YANGs we tried have some problems and cannot compiled - We have to dissect whether the root cause is in device or in NSO - Debug tool or detailed error log might be helpful Some vendor have higher priority to support gRPC than NETCONF - gRPC is easier to implement and is extensively used recently - Hopefully all vendors support NETCONF/YANG, but we don’t want to give up to adopt good and low cost devices due to lack of protocol support - Ideally, controller platform should support all major protocols Compile succeeded: 9 Have issues to compile: 7 Support gRPC before NETCONF: 1 Disaggregated Transport Lab Trial Result
15 Expand domains where to install NSO - Transport → Switching → Forwarding Expand operation use cases - Currently we focus the field to apply NSO on provision / state check - Provision / state check → telemetry → closed loop Lecture and increase model-driven SDN engineer and team - Now we are very minority, it is our critical mission