Open and Disaggregated Transport SDN · nWe are challenging to adopt disaggregated devices and open...

Copyright © NTT Communications Corporation. All rights reserved.

Transform your business, transcend expectations with our technologically advanced solutions.

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


Agenda

① MotivationandObjectivesofOpenandDisaggregatedTransportSDN

② ImplementationofONOS-basedDisaggregatedOpticalTransportNetworks

③ NTTCommunications'FieldTrial

2


Agenda




3


IoT

Data Center Data Center

Service Network

WAN

LAN

Transport Network

EnterpriseCloud

EnterpriseCloud

Clou

d

Horizontal expansion“Software-Defined Exchange Service”

SDN deployment

SDN Deployment Expansion in NTT Communications

SaaS

IaaS

Third Party Cloud Service

Vertical Expansion“Software-Defined Network Service ”“Transport SDN”

4


Software-Defined Exchange Service

5http://www.ntt.com/en/services/cloud/sd-exchange.html


Transport SDN Overview

6

Dynamicandintegratedmanagementoftransportnetworkdevices

Copyright © NTT Communications Corporation. All rights reserved. 7

Transport Network Settings (As-Is)

n Distributednetworkfunctionsdeploymentn Hardware-basedaggregationn IsolatedNMS/EMS

Packet & Optical Transport DomainAccess Domain Access Domain

VLAN/OTN

MPLS

VLAN/OTNOTN / WDM

NMS

BSS/OSS BSS/OSS BSS/OSSIsolatedNMS/EMS

DistributedNF

CLI RPC CLI

Aggregated

NMSNMS


MPLS

8

Transport Network Settings (adopting Transport SDN)

n Centralizednetworkfunctionsdeploymentn Software-baseddisaggregationn APIintegrationwithTransportNWcontroller


VLAN/OTN VLAN/OTNOTN / WDM

VNF

CentralizedNF

Disaggregated

As-IsTo-Be

BSS/OSS/Orchestrator

Transport NW Controller (Model based)

APIintegration

CLI NETCONF REST


Use Cases of Transport SDN

NWvisualization(Multilayer,multidomain)

Analysis&Processautomation

Power consumption

Path latency(RTT)

Autopathallocation(Multilayer,multidomain)

End-to-endfaultrecovery(Multidomain)


Transport NW Controller Architecture


Transport NW Controller

(Model based)

Service/Business Model

Multi domain / multi layerflow/resource optimization

Device specific config

Network config

1

2

3

4

VLAN/OTN

MPLS

OTN / WDM

CLI NETCONFNETCONF

/REST

Driver Driver

RINGNNI

Fabric

PathComputationResourceOptimization

DeviceConfig

NWConfig

Topology

NE

Intent

Service/Businessmodel(e.g.link,Bandwidth,reliability)

1

2

3

4

Driver

Driver


NTT Communications Transport SDN History

2015 2016 2017

NTTCom TransportSDN

PoC1 PoC2 ProductionDeployment

4UseCases VPN/CloudintegrationTestingautomation

Pathconfig:1hour->minutes60%OPEXdown


n Value-addedVNFsn Fullyandadvanced

automation&Visualization- Telemetry- AI/Deeplearning

3n OpenSDNControllern Customizabilityn Fastertimetomarketn Interoperabilityn CAPEX/OPEXreduction

2n Disaggregateddevicesn Speedingup

technicalinnovationn Inventoryoptimization

1

12

Our Challenge (Phase2)


ONOS Packet Optical Use Case / NTT Communications Transport SDN

PoC2 PoC3

2015 2016 2017

ONOSPacketOpticalUseCase

NTTCom TransportSDN

IP-Optical DisaggregatedROADM Resiliency/Monitoring

PoC1 PoC2 ProductionDeployment

LabTrial

FieldTrial

Agenda②

Agenda③

PoC1

Phase1

Phase2





14

#ONOSProject

BW CalendaringSDN-IPVPLS

CarrierEthernet2.0L3VPN

ControlApps Mgmt AppsConfig Apps

ONOS

Logically Centralized Control1. Optimize resource usage2. Dynamic traffic provisioning3. Multi-layer resiliency

Motivation

Optical NetworkOTNWDM

Fiber switching

Packet NetworkIP

MPLSVLAN Disaggregated Transport Network

1. Reduces CAPEX & OPEX2. Eliminates vendor lock-in3. Allows rightsizing and

piece-wise upgrades

#ONOSProject

ONOS Distributed Architecture

NB Core API

Distributed Core(state management, notifications, high-availability & scale-out)

SB Core API

Protocols

Providers

Protocols

Providers

Protocols

Providers

Protocols

Providers

AppsApps

#ONOSProject

ONOS Core Subsystems

Device Link Host

Topology

Flow Rule

Path

Packet

StatisticsIntent

Application

Leadership

Messaging

Storage Region

Mastership

Driver

Group

Security

Flow Objective

Event

OpenFlow NetConf OVSDB

Core Cluster

. . .

Proxy ARPMobility L2 Forwarding

REST API GUI CLI

Network Cfg.

SDN IP / BGP Packet / Optical

Tunnel

. . .

OSGi / Apache Karaf

Network Virt.Device Cfg.

Config

UI Extension

External Apps

Graph

Discovery Tenant . . .

#ONOSProject

ONOS Building BlocksApplicationsBandwidth on-demand, calendaring, optical restorationPower balancing, fault management & correlationOptical information model

Northbound AbstractionsIntent frameworkConverged topology graph

ONOS Core: Scale & HAModular PCEScalable resource manager (spectrum, OTN, …)

SouthboundTL1, PCEP, OpenFlow, NETCONF/YANG, SNMP, RESTIn progress: Infinera OTSv, Nokia (Alcatel-Lucent), OpenROADM

NB Core API

Distributed Core(state management, notifications, high-availability & scale-out)

SB Core API

ProtocolsProviders

ProtocolsProviders

ProtocolsProviders

ProtocolsProviders

AppsApps

#ONOSProject

Distributed Config Store

YANG Runtime

*.yangYANG

Compiler

model.jar

RESTCONF / NETCONF SB

REST / RESTCONF / NETCONF NB

Device

Dynamic Config Subsystem

DeviceDevice Device

Device Certification App

model.jar *.yang

Device ConfigApp

NetworkFunction

DeviceDevice

Device DeviceDevice

/services/devices

JSON / XML

JSON / XML

First, ONOS NB receives device config data as JSON or XML, decodes it and stores it in the distributed store.

Afterwards, ONOS SB receives change notifications and encodes the data to JSON or XML and conveys it to the device.

YANG model is registered by (1) operator, or (2) device

Dynamic Config of Devices

#ONOSProject

YANG Runtime

*.yangYANG

Compiler

RESTCONF / NETCONF SB

Device

Dynamic Config Subsystem

DeviceDevice Device

Service Design Orchestrator

DeviceDevice

DeviceDevice

Service Application

model.jar

OpenFlow / P4 / Other SB

DeviceDevice

DeviceDevice

Distributed Config Store

/services/devices

JSON / XML

JSON / XML

REST / RESTCONF / NETCONF NB

First, ONOS NB receives service provisioning request as JSON or XML, decodes it and stores it in the distributed store.

Afterwards, the service app receives change notifications and interacts with the environment using whatever means areappropriate.

Service design creates a YANG model for the service.The model gets compiled and registered; either a priori by the user or at run-time by the application.

Dynamic Config of Services

#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)

#ONOSProject

https://youtu.be/nXAZ3d8d4ZMCarrier Ethernet over WDM (2016)

#ONOSProject

Disaggregated Optical Networks

transpondermuxponder

ROADMROADM Tooptical

transportXTopacketlayer

Backplane

• 1x20 WSS, 1U• 8x2 transponder, 1U• 160x160 backplane, 7U

ONOS

OpenFlow, SNMP, TL1NETCONF, REST

PowerManagementAlarmHandlingBandwidth

OnDemandProtectionSwitching

Vertical integration Disaggregated

Vendor lock-in Multi vendor

One size fits all Rightsize

Forklift upgrade Piece-wise upgrade

System integration Software-driven integration

EDFA

OPS

#ONOSProject

SDN & NFV Solutions Showcase

#ONOSProject

Participating Organizations

#ONOSProject

SummaryONOS is SDN controller for converged multi-layer networkingScale out, high performance, HARich information model, variety of subsystems, proven south bound

Growing eco-system and communityComponent vendors, system vendors, and operators

Production readyCommercial versionsTrial deployments in service providers and research networks





27


ONOS Packet Optical Use Case / NTT Communications Transport SDN

PoC2 PoC3

2015 2016 2017

ONOSPacketOpticalUseCase

NTTCom TransportSDN

PoC1 PoC2

ProductionDeployment

LabTrial

FieldTrialAgenda③

PoC1


Lab Trial & Field Trial

n LabTrialn ImplementR&Dresultsinaclosedand

smallenvironmentn Evaluatefunctionalityandnon-

functionalityforeachtechnology

n FieldTrialn DeployR&Dresultstothewideareatestbed

infrastructureandIntegratewithothersystems(Cloud,backbonenetworks,etc)

n Provide”services”withthetestbedforallemployeesofTechnologyDevelopmentDept.

n ConfirmtheEnd-to-Endoperabilityandstability

2016 2017 2018 2019〜

Feedbacktocommunity Feedbacktocommunity


Lab Trial of Disaggregated Transport Networks

n Feasibilitystudyn Buildingouttransportnetworkscomposedofdisaggregateddevicesn Managingmulti-vendor devicesinSDNcontroller


VLAN/OTN

MPLS

VLAN/OTNOTN / WDM



VNF

Dis-aggregation

As-IsTo-Be

CLI NETCONF REST4

1

1

1


Lab Trial Result



(Model based)




Network config

1

2

3

4

VLAN/OTN

MPLS

OTN / WDM

CLI NETCONFNETCONF

/REST

Driver Driver

RINGNNI

Fabric


DeviceConfig

NWConfig

Topology

NE

Intent


1

2

3

4

Driver

Driver




(Model based)




Network config

1

2

3

4

VLAN/OTN

MPLS

OTN / WDM

CLI NETCONFNETCONF

/REST

Driver Driver

RINGNNI

Fabric


DeviceConfig

NWConfig

Topology

NE

Intent


1

2

3

4

Driver

- Multiplesouthbounddriverwithminimumimplementation(e.g.AutotemplategenerationfromYANG model)

- Transactionalcontrolacrossmultiplenodesanddomains

- End-Endpathprovisioningwithtopintent

- ModelingtodescribeNWConfig&Mappinglogic

- Networktopologymodelofmultiplelayerandtechnology

- Automaticpathcomputation

Driver

Lab Trial Result

RINGNNI

Fabric


DeviceConfig

NWConfig

Topology

NE

Intent


Driver

✔

✔

Under development (Dynamic Configuration Brigade)

To be developed (New Brigade?)

Intent Framework / Topology SubSystem

Intent Framework / Web UI

Under development (Dynamic Configuration Brigade)


Covering20 sitesacross6 countries

Holding3 ASsandconnectingwithotherISPs

Field Trials on NTT com testbed


Otemachi

Tamachi

Makuhari

Chiba

n Step1(Q12017):donen Deployedpacketswitches

andtranspondersacross3sitesaroundTokyo

n Step2(Q2-Q42017):WIPn DeployROADM,optical

amplifier


Next Steps of Field Trial

n AccumulatetheknowledgeofTransport-SDNthroughthefieldtrialn IntegratewiththeexistingLegacy domainsandOrchestratorn Expandnewdomains(CloudDC,DCI,etc)n Confirmthestabilitythroughthelongtermoperation

Metro Domain (Legacy)

NETCONF

API

DC NW Ctrl

Orchestrator

DC NW

OTN / WDM Domain

Switch Domain

API

DC NW



Summary

n TransportSDNhavematuredfromPoC toProduction.n WearechallengingtoadoptdisaggregateddevicesandopensourceSDNcontroller.

n ON.Lab showedthePoC ofopenanddisaggregatedopticaltransportnetworksandisdevelopingONOSwiththeopensourcecommunitytowardcommercialquality.

n WehavestartedthelabtrialandfieldtrialofdisaggregatedtransportnetworksandcontinuetofeedbacktherequirementstotheONOScommunity.


Thank you

3

Open and Disaggregated Transport SDN · nWe are challenging to adopt disaggregated devices and open...

Documents

Transcript of Open and Disaggregated Transport SDN · nWe are challenging to adopt disaggregated devices and open...