tnc18 Slides 5 2018-04 - Infinera - OpenLineSystemAndOpenROADM 04
tnc18 Slides 5 2018-04 - Infinera - OpenLineSystemAndOpenROADM 04
SDN-based control
architecture & algorithms
Flex-grid Systems
• Some deployments of
“flex-ready” hardware
The Bad “Flex-ready”
• Software support lagging
• Much work to be done
Mission: “disaggregation and opening up of traditionally proprietary Open ROADM 1.0 Architecture
ROADM systems and SDN-enablement of traditionally fixed ROADMs”
Members:
• SP: AT&T, Deutsche Telekom, KDDI, Orange, Rostelecom, Saudi
Telecom, SK Telecom, Telecom Italia
• Vendor: Ciena, Cisco, Coriant, Fujitsu, Infinera, Juniper, Nokia
History:
• Open ROADM 1.0 (2016): Metro, fixed-grid focus
• Open ROADM 2.0 (2017): Add support for flex-grid, amps, etc.
• Open ROADM 3.0 expected 2018
V1 V2 V3 Future
First release: March 2016 Release: November 2017 Initial release: March 2018 2H 2018 and beyond
Final release: May 2016
OpenConfig
Initiated by Facebook ‣ Google-driven “standard” YANG models
Mission: “disaggregate the traditional network deployment approach”
‣ Started with routers/switches, extending to transport layer
5 areas, 11 projects, dozens of working groups, hundreds of members
ODTN
(Open Disaggregated Transport Network)
Open Optical Packet Transport (OOPT) Project
• Open Line System WG – Infinera Co-chair ‣ Launched 2018 Members
• Physical Simulation Environment WG
• Common API WG ‣ Focus on end-to-end control of open
• Disaggregated Transponders & Chips WG network
• Multi-vendor transponders over
single-vendor OLS
‣ Infinera co-chairs OLS working group (Transponder interop not in scope)
‣ Focusing on SDN control of disaggregated OLS • ONF-developed ONOS controller
‣ Defined and demonstrated proposed standard interfaces ‣ Leverage best existing standard APIs + 10 vendors
and information models: OpenOLS and OpenDevice including Infinera
• TAPI, OpenConfig, TIP OpenOLS…
Watch!
TIP OLS Demo Video
12 | © 2018 Infinera Confidential & Proprietary
2.
What Needs to be Standardized? APIs/SDN
‣ Definitely:
• Target use cases
• Open APIs
• YANG information models (device, span, OLS, network…)
‣ Maybe not:
• SDN control software architectures
• Control algorithms
‣ Why not?
• Customer requirements vary (some planning DIY control)
• Supplier innovation may deliver greater value
Early deployments,
TIP Summit demo
Still one neck to grab. More complex to set up Stated direction for some
Open network is and manage. ICPs.
insurance, used Probably more hands-on Requires deep in-house
selectively. for operator. SW expertise & optical
skill set.