Open and Disaggregated Transport SDN - from PoC to Field Trial - Dai Kashiwa, Director, NTT Communications / Board member of ONOS/CORD Marc De Leenheer, MTS, ON.Lab Toru Furusawa, Chief Engineer, NTT Communications Transform your business, transcend expectations with our technologically advanced solutions.
Agenda 1 Motivation and Objectives of Open and Disaggregated Transport SDN 2 Implementation of ONOS-based Disaggregated Optical Transport Networks 3 NTT Communications' Field Trial 2
Agenda 1 Motivation and Objectives of Open and Disaggregated Transport SDN 2 Implementation of ONOS-based Disaggregated Optical Transport Networks 3 NTT Communications' Field Trial 3
SDN Deployment Expansion in NTT Communications Cloud Data Center Enterprise Cloud SDN deployment Data Center Enterprise Cloud Third Party Cloud Service SaaS IaaS Horizontal expansion Software-Defined Exchange Service Service Network WAN Vertical Expansion Transport Network Software-Defined Network Service Transport SDN LAN IoT 4
Software-Defined Exchange Service http://www.ntt.com/en/services/cloud/sd-exchange.html 5
Transport SDN Overview Dynamic and integrated management of transport network devices 6
Transport Network Settings (As-Is) n Distributed network functions deployment n Hardware-based aggregation n Isolated NMS/EMS Aggregated BSS/OSS BSS/OSS BSS/OSS Isolated NMS/EMS NMS NMS NMS Distributed NF CLI RPC CLI MPLS VLAN/OTN Access Domain OTN / WDM Packet & Optical Transport Domain VLAN/OTN Access Domain 7
Transport Network Settings (adopting Transport SDN) n Centralized network functions deployment n Software-based disaggregation n API integration with Transport NW controller Disaggregated API integration BSS/OSS/Orchestrator Transport NW Controller (Model based) Centralized NF CLI NETCONF REST To-Be As-Is MPLS VNF VLAN/OTN Access Domain OTN / WDM Packet & Optical Transport Domain VLAN/OTN Access Domain 8
Use Cases of Transport SDN Auto path allocation (Multi layer, multi domain) NW visualization (Multi layer, multi domain) End-to-end fault recovery (Multi domain) Analysis & Process automation Power consumption Path latency(rtt) 9
Transport NW Controller Architecture BSS/OSS/Orchestrator 1 Intent Service / Business model ( e.g. link, Bandwidth, reliability) Transport NW Controller (Model based) Driver 1 2 3 4 Service/Business Model Multi domain / multi layer flow/resource optimization Network config specific config Driver Driver 2 Topology 3 NW Config RING Path Computation Resource Optimization NNI Fabric CLI NETCONF NETCONF /REST 4 Config MPLS Driver VLAN/OTN OTN / WDM NE 10
NTT Communications Transport SDN History NTTCom Transport SDN PoC1 PoC2 Production Deployment 4 Use Cases VPN/Cloud integration Testing automation Path config: 1 hour -> minutes 60% OPEX down 2015 2016 2017
Our Challenge (Phase2) n1 Disaggregated devices n2 Open SDN Controller n3 Value-added VNFs n Speeding up technical innovation n Inventory optimization n Customizability n Faster time to market n Interoperability n CAPEX/OPEX reduction n Fully and advanced automation & Visualization - Telemetry - AI / Deep learning 12
ONOS Packet Optical Use Case / NTT Communications Transport SDN ONOS Packet Optical Use Case Agenda2 PoC1 PoC2 PoC3 IP-Optical Disaggregated ROADM Resiliency/Monitoring NTTCom Transport SDN Phase1 PoC1 PoC2 Production Deployment Phase2 Agenda3 Lab Trial Field Trial 2015 2016 2017
1 Motivation and Objectives of Open and Disaggregated Transport SDN 2 Implementation of ONOS-based Disaggregated Optical Transport Networks 3 NTT Communications' Field Trial 14
Motivation BW Calendaring SDN-IP VPLS Carrier Ethernet 2.0 L3VPN Control Apps Config Apps ONOS MgmtApps Logically Centralized Control 1. Optimize resource usage 2. Dynamic traffic provisioning 3. Multi-layer resiliency Packet Network IP MPLS VLAN Optical Network OTN WDM Fiber switching Disaggregated Transport Network 1. Reduces CAPEX & OPEX 2. Eliminates vendor lock-in 3. Allows rightsizing and piece-wise upgrades #ONOSProject
ONOS Distributed Architecture Apps NB Core API Distributed Core (state management, notifications, high-availability & scale-out) SB Core API Providers Providers Providers Providers Protocols Protocols Protocols Protocols #ONOSProject
ONOS Core Subsystems External Apps REST API GUI CLI Mobility Proxy ARP L2 Forwarding SDN IP / BGP Packet / Optical... Application UI Extension Security Cfg. Discovery Network Virt. Tenant... Config Storage Region Driver Path Tunnel Intent Statistics Core Cluster Leadership Mastership Topology Network Cfg. Flow Objective Group Event Messaging Graph Link Host Flow Rule Packet OSGi / Apache Karaf OpenFlow NetConf OVSDB... #ONOSProject
ONOS Building Blocks Applications Bandwidth on-demand, calendaring, optical restoration Power balancing, fault management & correlation Optical information model Northbound Abstractions Intent framework Converged topology graph Apps NB Core API Distributed Core (state management, notifications, high-availability & scale-out) SB Core API ONOS Core: Scale & HA Providers Protocols Providers Protocols Providers Protocols Providers Protocols Modular PCE Scalable resource manager (spectrum, OTN, ) Southbound TL1, PCEP, OpenFlow, NETCONF/YANG, SNMP, REST In progress: Infinera OTSv, Nokia (Alcatel-Lucent), OpenROADM #ONOSProject
Dynamic Config of s *.yang YANG Compiler Certification App JSON / XML Config App Network Function First, ONOS NB receives device config data as JSON or XML, decodes it and stores it in the distributed store. model.jar REST / RESTCONF / NETCONF NB Distributed Config Store YANG Runtime Dynamic Config Subsystem /devices /services model.jar *.yang RESTCONF / NETCONF SB YANG model is registered by (1) operator, or (2) device #ONOSProject JSON / XML Afterwards, ONOS SB receives change notifications and encodes the data to JSON or XML and conveys it to the device.
Dynamic Config of Services YANG Compiler *.yang Service Design Orchestrator JSON / XML Service First, ONOS design NB creates receives a YANG service model for provisioning the service. request as JSON or XML, The decodes model it gets and stores compiled it in and the registered; distributed either store. a priori by the user or at run-time by the application. REST / RESTCONF / NETCONF NB YANG Runtime Distributed Config Store model.jar Dynamic Config Subsystem /devices /services Service Application OpenFlow / P4 / Other SB RESTCONF / NETCONF SB #ONOSProject JSON / XML Afterwards, the service app receives change notifications and interacts with the environment using whatever means are appropriate.
https://youtu.be/gsfywjyyfi4 Multi-Layer, Multi-Vendor (June 2015) On#Demand) Op+cal)Bandwidth)) Advanced)Mul+#Layer) Restora+on) ONOS) Mul+#Layer)Network) Op+miza+on) Menlo'Park,'CA' OF'provider' Ciena'TL1'provider' Fujitsu'TL1'provider' Huawei'PCEP'provider' IP'Layer' OpCcal'layer' #ONOSProject OBawa,'Ontario' Richardson,'TX' Plano,'TX' Domain)A) Domain)B) Domain)C)
https://youtu.be/nxaz3d8d4zm Carrier Ethernet over WDM (2016) #ONOSProject
Disaggregated Optical Networks Bandwidth On Demand Alarm Handling ONOS Power Management Protection Switching X Backplane OpenFlow, SNMP, TL1 NETCONF, REST ROADM ROADM OPS muxponder transponder EDFA To packet layer To optical transport 1x20 WSS, 1U 8x2 transponder, 1U 160x160 backplane, 7U #ONOSProject Vertical integration Vendor lock-in One size fits all Forklift upgrade System integration Disaggregated Multi vendor Rightsize Piece-wise upgrade Software-driven integration
SDN & NFV Solutions Showcase #ONOSProject
Participating Organizations #ONOSProject
Summary ONOS is SDN controller for converged multi-layer networking Scale out, high performance, HA Rich information model, variety of subsystems, proven south bound Growing eco-system and community Component vendors, system vendors, and operators Production ready Commercial versions Trial deployments in service providers and research networks #ONOSProject
1 Motivation and Objectives of Open and Disaggregated Transport SDN 2 Implementation of ONOS-based Disaggregated Optical Transport Networks 3 NTT Communications' Field Trial 27
ONOS Packet Optical Use Case / NTT Communications Transport SDN ONOS Packet Optical Use Case PoC1 PoC2 PoC3 NTTCom Transport SDN PoC1 PoC2 Lab Trial Agenda3 Field Trial Production Deployment 2015 2016 2017
Lab Trial & Field Trial n Lab Trial n Field Trial n Implement R&D results in a closed and small environment n Evaluate functionality and nonfunctionality for each technology n Deploy R&D results to the wide area testbed infrastructure and Integrate with other systems (Cloud, backbone networks, etc) n Provide services with the testbed for all employees of Technology Development Dept. n Confirm the End-to-End operability and stability 2016 2017 2018 2019 Feedback to community Feedback to community
Lab Trial of Disaggregated Transport Networks n Feasibility study n Building out transport networks composed of disaggregated devices n Managing multi-vendor devices in SDN controller BSS/OSS/Orchestrator Dis-aggregation 1 Transport NW Controller 4 CLI NETCONF REST MPLS To-Be VNF As-Is 1 VLAN/OTN Access Domain OTN / WDM Packet & Optical Transport Domain VLAN/OTN Access Domain 1 30
Lab Trial Result BSS/OSS/Orchestrator 1 Intent Service / Business model ( e.g. link, Bandwidth, reliability) Transport NW Controller (Model based) Driver 1 2 3 4 Service/Business Model Multi domain / multi layer flow/resource optimization Network config specific config Driver Driver 2 Topology 3 NW Config RING Path Computation Resource Optimization NNI Fabric CLI NETCONF NETCONF /REST 4 Config MPLS Driver VLAN/OTN OTN / WDM NE 31
Lab Trial Result - BSS/OSS/Orchestrator End-End path provisioning with top intent 1 Service/Business Model - Network topology model of multiple 2 layer and technology Multi domain / multi layer Transport NW - Automatic flow/resource path computation optimization Controller Topology (Model based) 3 Driver Network config Intent - Modeling 4 to describe NW Config specific config & Mapping logic NW Driver Driver Config Service 1/ Business model Service / Business model ( e.g. link, Bandwidth, reliability) ( e.g. link, Bandwidth, reliability) Intent Framework / Web UI Intent Path 2 Computation Resource Optimization Topology 3 Path Computation Resource Optimization Intent Framework / Topology SubSystem NNI NNI RING RING Under development Fabric (Dynamic Fabric Configuration Brigade) NW Config CLI VLAN/OTN - Multiple southbound driver NETCONF NETCONF with minimum implementation /REST (e.g. Auto template generation from YANG model) MPLS - Transactional control across multiple nodes and domains OTN / WDM Config NE 4 Under development (Dynamic Configuration Brigade) Config Driver Driver NE To be developed (New Brigade?) 32
Field Trials on NTT com testbed 20 sites across 6 countries Holding 3 ASs and connecting with other ISPs Covering 33
Otemachi n Step 1 (Q1 2017) : done Makuhari n Deployed packet switches and transponders across 3 sites around Tokyo n Step 2 (Q2-Q4 2017) : WIP Chiba Tamachi n Deploy ROADM, optical amplifier 34
Next Steps of Field Trial n Accumulate the knowledge of Transport-SDN through the field trial n Integrate with the existing Legacy domains and Orchestrator n Expand new domains (Cloud DC, DCI, etc) n Confirm the stability through the long term operation Orchestrator API API Transport NW Controller DC NW Ctrl NETCONF DC NW Switch Domain DC NW Metro Domain (Legacy) OTN / WDM Domain 35
Summary n Transport SDN have matured from PoC to Production. n We are challenging to adopt disaggregated devices and open source SDN controller. n ON.Lab showed the PoC of open and disaggregated optical transport networks and is developing ONOS with the open source community toward commercial quality. n We have started the lab trial and field trial of disaggregated transport networks and continue to feedback the requirements to the ONOS community.
Thank you