Open and Converged Multi-Layer Networking with ONOS - PoC and future field trial plan -

At ONOS Build 2016:
https://onosbuild2016.sched.com/event/8PKO/onos-community-showcase-field-trial-plan-of-disaggregated-transport-network-in-ntt-communications

Transcript

1. #ONOSProject Open and Converged Multi-Layer Networking with ONOS PoC and future field trial plan Toru Furusawa NTT Communications
2. #ONOSProject Outline Context & Problem Statement Past Demonstrations Next PoC and NTT Communications’ Field Trial Summary 2
3. #ONOSProject BW Calendaring SDN-IP VPLS Carrier Ethernet 2.0 L3VPN Control Apps Mgmt Apps Config Apps ONOS Optical Network OTN WDM Fiber switching Packet Network IP MPLS VLAN Centralized control 1.  Optimize resource usage 2.  Dynamic traffic provisioning 3.  Multi-layer resiliency Multi-Layer SDN Control
4. #ONOSProject Outline Context & Problem Statement Past Demonstrations Next PoC and NTT Communications’ Field Trial Summary 4
5. #ONOSProject On#Demand) Op+cal)Bandwidth)) Advanced)Mul+#Layer) Restora+on) Fujitsu'TL1'provider' OF'provider' Ciena'TL1'provider' Huawei'PCEP'provider' Menlo'Park,'CA' Richardson,'TX' Plano,'TX' OBawa,'Ontario' ONOS) OpCcal'layer' IP'Layer' Domain)A) Domain)B) Domain)C) Mul+#Layer)Network) Op+miza+on) https://youtu.be/gsfYwJyYfI4 Multi-Layer, Multi-Vendor (June 2015)
6. #ONOSProject https://youtu.be/nXAZ3d8d4ZM L2VPN over WDM (March 2016)
7. #ONOSProject Disaggregated ROADM transponder muxponder WSS WSS To op%cal transport X To packet layer Backplane •  1x20 WSS, 1U •  8x2 transponder, 1U •  160x160 backplane, 7U ONOS OpenFlow, SNMP, NETCONF, REST Power Management Alarm Handling Bandwidth On Demand Op%cal Restora%on Vertical integration Disaggregated Vendor lock-in Multi vendor One size fits all Rightsize Forklift upgrade Piece-wise upgrade System integration Software-driven integration
8. #ONOSProject Outline Context & Problem Statement Demonstrations Next PoC and NTT Communications’ Field Trial Summary 8
9. #ONOSProject NTT Communications’ Expectations for Disaggregated Transport Networks and ONOS •  Expectation for disaggregated-transport NW •  Agility and CAPEX/OPEX reduction •  Expectation for ONOS •  Community influence •  Cost reduction •  Programmability of northbound on top of ONOS Transform our transport network operation with disaggregated-transport NW and ONOS
10. #ONOSProject Long Term Vision for Commercial Deployment 10 2016 2017 2018 Market Carriers ON.Lab •  Initial appearance of disaggregated ROADM product •  PoC of disaggregated ROADM •  Plan and start next development of ONOS for disaggregated ROADM •  Providing requirements •  Increase of disaggregated ROADM vendors •  Appearance of disaggregated Packet-Transport products •  ONOS Development •  Next PoC of Packet-Optical use case •  Field trial (NTT Comm) •  Step1 Q1 •  Step2 Q2-3 (if step1 successful) •  Step3 Q4 and beyond (if step2 successful) •  Commoditization •  Continuous ONOS development •  ONOS will be the de fact controller for disaggregated transport NW •  Continuous field trial •  Commercial service deployment (to be decided according to both the technical evaluation through the field trial and business strategy)
11. #ONOSProject Transport Network Controller Architecture 11 VLAN/OTN MPLS OTN / WDM BSS/OSS/Orchestrator CLI NETCONF NETCONF /REST SDN Controller (Model based) Service/Business Model Multi domain / multi layer flow/resource optimization Driver Driver Device specific config Network config RING NNI Fabric Path ComputaIon Resource OpImizaIon Device Config NW Config Topology NE Intent Service / Business model ( e.g. link, Bandwidth, reliability)
12. #ONOSProject Transport Network Controller Architecture 12 VLAN/OTN MPLS OTN / WDM BSS/OSS/Orchestrator CLI NETCONF NETCONF /REST SDN Controller (Model based) Service/Business Model Multi domain / multi layer flow/resource optimization Driver Driver Device specific config Network config EMS NMS Product Scope ONOS NSO tail-f PCE
13. #ONOSProject Controller Requirements 13 Strength of ONOS Our Requirements for ONOS Type Item Nodal Control Multiple southbound driver with minimum additional implementation Transaction & rollback of node configuration Configuration synchronization between controller and device Network Control Network topology model of multiple layer and technology (WDM, ROADM, Ethernet, LSP, PW, Protection, ...) Transaction & rollback of network configuration across multiple nodes End-End path provisioning with automatic path computation within a single network Multi-domain Network Control End-End path provisioning with automatic path computation across multi-domain networks Transaction & rollback of multi-domain network configuration Impact analysis across multiple layers and domains Protection modeling Layered Intent Monitoring/Alarm Handling Open-IF Expansion Expected to be developed Transaction & rollback
14. #ONOSProject Gaps towards Commercial Deployment 14 Next PoC Field Trial Switch ONOS Trans/muxponder WSS WSS WSS Optical amp Trans/muxponder Trans/muxponder WSS WSS WSS Trans/muxponder Device expansion Switch E-LINE Control with open IF Monitoring Packet-layer protection Optical amp Layer visualization Function Development Open-IF Expansion (Open ROADM, ...) Protection modeling Monitoring and alarm handling Layered Intent Transaction management & rollback etc... Device Expansion Open ROADM device Optical amplifier, etc Performance and stability evaluation
15. #ONOSProject Open ROADM Multi-vendor data plane interoperability Common model for Single wavelength Multi wavelength Service Alignment between ONOS & Open ROADM Functional decomposition NETCONF/YANG Source: http://openroadm.org/home.html
16. #ONOSProject Open ROADM in ONOS OpenROADM NB Service defini%on CRUD service opera%ons Service reconfigura%on: reroute, roll, … ONOS OpenROADM device & network SB Device Link Intent ONOS op%cal informa%on model Flow Protec%on Monitoring Device- specific SNMP Device- specific TL1 OpenFlow Intent types & compilers Cross connects Op%cal signals, data types, etc. Resource ONOS subsystem In progress Looking for contributions
17. #ONOSProject Protection Modeling 17 Most of transport network have protection mechanism High-speed switching (< 50ms) Automatic protection switching initiated by devices Controller is informed after the fact ONOS Intent Framework will work with protection Pre-compute and configure alternate path Visibility into current working path
18. #ONOSProject Layered Intent 18 Carrier’s transport network consists of multi-layer network Need to represent relationships across multiple layers’ intent Analyze impact across layers for monitoring and trouble shooting Utilize (third-party) multi-layer PCE apps Lambda link Optical layer switch Optical layer switch Lambda link Optical layer switch Lambda path ODU link ODU link Lambda link Optical layer switch Lambda link Lambda path Optical layer switch ODU layer switch ODU layer switch ODU layer switch Packet layer ink packet layer switch packet layer switch ODU path An example of hierarchical relationships of multi-layer transport network
19. #ONOSProject NTT Communications Field Trial Plan Step 1 (Q1 2017) Deploy disaggregated transport network (packet switch & transponder) Evaluate SDN controllers including ONOS (basic functions) Step 2 (Q2-3 2017) Deploy disaggregated transport network (ROADM, optical amplifier) Evaluate SDN controllers including ONOS (functions, performance, stability) Step 3 (Q4 2017) Integrate the disaggregated transport network with production environment 19 Optical fiber Legacy ROADM (already deployed) ONOS Otemachi CO Tamachi office Makuhari CO Chiba Minato CO Testbed network Testbed network Testbed network Otemachi Tamachi Makuhari Chiba Minato Disaggregated transport device (to be deployed)
20. #ONOSProject Development Roadmap in ON.Lab 20 2016 2017 2018 Q3 Q4 Q1 Q2 Q3 Q4 * ONS2017(April) Step1 Layered Intents Transaction & rollback NTT Comm Field trial Open-IF (Open ROADM) Device model Service model Protection Step2 Step3 Event Monitoring * OFC (March) Design Implementation Design Implementation
21. #ONOSProject Call for Contributions 21 ONOS Software Development Open source device drivers (OpenROADM, OpenFlow or other open protocols) Protection mechanism Monitoring subsystem Layered intents Transaction management & rollback etc... Build Disaggregated Transport POD* ROADM components (OXC, WSS, trans/muxponder, amplifier) Packet switches Demonstrations at OFC (March 2017) and ONS (April 2017) * Rack to be used for development purposes, physical location is at ON.Lab or partner lab
22. #ONOSProject Outline Context & Problem Statement Demonstrations Next PoC and NTT Communications’ Field Trial Summary 22
23. #ONOSProject Summary •  ON.Lab has shown use cases of carriers’ transport network disaggregation •  NTT Communications expect ONOS as disaggregated transport network controller •  We plan a next PoC and field trial
24. #ONOSProject Thank you 24