ONOS Use Cases

Tom TofighAT&T

CorePacket-Optical

MetroPacket-Optical

Service Provider Network of the Future

Wired Access

Wireless Access

Access

NFaaS in Central Office

Built like a Data Center

Network Interface

Network Interface

Enterprise Access

Wireless Access

Wired Access

Wireless Access

Wired Access

Wireless Access

Enterprise Access

Wireless Access

Network Interface

Network Interface

Network Interface

Network Interface

PoPBuilt like a Data Center

Network Interface

Network Interface

Network Interface

Network Interface

Multilayer packet-optical in the Core NFaaS in Central Office

Service Providers are also keen on solving scaling, migration issues with SDN and introducing SDN control in their WAN networks.

We built two other use cases based on these requirements:• SDN-IP • SDN-based WAN control with segment

routing

ONOS Service Provider Use Cases

North-bound abstraction

South-bound abstractionApplication Intent Framework

ONOS Policies

SouthboundInterface B

SouthboundInterface A

OpenFlow

Multi-layer SDN control of

Packet-optical SDN-IPSegment Routing

NFaaS in CO

OpenFlow

Routing,Recovery,Label imposition

Requests

SR Labels imposed by controller OSR FIB built by

controller

Routing Service

Requests

ONOS

Discovery Service

Open Segment Routers (OSR)

Forwarding Service

SDN based WAN Control with Segment routing

Open Segment Routers (OSR)

This use case has been developed in collaboration with ONF.

SDN Control of Multi Layer Networks: Packet Optical

Praseed BalakrishnanFujitsu Network Communication

AE

B

C

D

P3

P1 P

2

P4

P5

R1

R2

R4

R7

R3

R5

R6

Todays Multi-Layer Network: Without Converged Control Plane

ROADMs

IP

Routers

MPLS Tunnels Controlled and managed independently

Slow to react to BW demands

Packet networks over provisioned to deal with traffic bursts and failures

Lack of agility and significant capex & opex inefficiencies

Optical networks over provisioned independently

With Converged Control Plane

Fast wavelength allocation of bandwidth in transport network for packet traffic

AE

B

C

D

P3

P1 P

2

P4

P5

R1

R2

R4

R7

R3

R5

R6

Rapid recovery from transport failures

Enable new services with SDN control plane

Reduce overprovisioning of resources with a combined control plane

Potential Use Cases

Inter Data Center BW on Demand

Optimization

Traffic engineering

Defragmentation

Restoration strategies

Our Goal

Demonstrate SDN control of packet optical networks using ONOS

Add support for multi-layer networks in ONOS

Write core functions to control multi-layer networks

Demonstrate a couple of app scenarios

Target Use Case: Prototype BW on Demand using ONOS Multi layer topology and resource utilization

Multi layer Packet and Optical layer control

Handling of optical layer failures

New Functionality Needed

• Converged multi layer viewo Enables multi-layer PCE

• Multi-layer aware service APIs• Southbound abstraction for multi-layer • Listening and reacting to failure• Northbound APIs

Implementation on ONOSONOS GUI:• Visualization of Intents• Visualization of Topology • Portal Calendaring APP

Topology:• Multi layer abstraction• Resource Utilization

Intents:• Path Computation• Reservation and Resource Management• Path Re-compute on Failure events

SB API• Discovery• OF using experimenter messages

Packet - OVSOptical Emulator (LINC-OE)

Planned BW of Demand Demo

ROADM

ROADM

ROADM

ROADMROADM

ROADM

ROADM

IP

IPIP

IPIP

OVS3

OVS1

OVS2OVS4

OVS5

OE1OE2 OE4

R7

OE3OE5 OE6

ONOSCustomer Portal

DC1 DC2

OE7

optical circuit

Re-Route optical circuit

10G Connection from NodeA:PortA to NodeZ:Port Z with latency less<10ms

Seamless Interworking of SDN and IP

Luca PreteON.Lab

ONOS and SDN-IP

ONOS

ONOS used to be confined in his wonderful world,but wasn’t able to communicate with the outside

S D N

ONOS

S D N

ONOS and SDN-IP

ONOS

SDN-IP

One day, SDN-IP came and gave the ability to ONOS to speak to the rest of the world. ONOS was finally free!

ONOS and SDN-IP

ONOS started to communicate with IP components similar to it, speaking a widely used old language, called BGP.

IPBGPONOS

SDN-IP

IP

ONOS and SDN-IP

BGP

ONOS “Clusters” started also to “peer” together to be more efficient and scalable using BGP

BGP

ONOS ONOS ONOS ONOS

SDN-IP ONOSONOS ONOS ONOS

SDN-IP

SDN-IP for external networks

SDN-IP to connect ONOS clusters

What has changed from last ONRC?

ONOS 1

• Single-instance• No SDN-IP Application HA• Able to speak with a single,

dedicated BGP speaker• Stateless protocol (dedicated REST

API)

...ONOS

2ONOS

n

SDN-IP

BGPd

ONOS 1 ...

ONOS 2

ONOS n

SDN-IP

BGPspeaker

BGPspeaker

SDN-IP

BGPspeaker

SDN-IP

Old SDN-IP New SDN-IP

• Multi-instance• SDN-IP Application HA• Able to speak with generic iBGP

speakers• Stateful protocol (iBGP)

What has changed from last ONRC?

SDN-IP

(SDN-IP, BGP, ARP,Routers Configuration,

NB)

Intent framework - NB

ARP

Router

RouteListenerSdnIpServicePeerConnectivityManager

Arp

Se

rvice

Co

nfig

ura

tion

IntentService

SdnIpConfigReader

BgpSessionManager

PeerConnectivity

SDN-IP

Before

After

BGP architecture

BGP Session Manager

RouteListener

SDN-IP boundary

BGP Session 1

BGP Session 2

BGP Session 3

..

.

BGP Speaker 1

BGP Speaker 2

BGP Speaker n

SDN-IP: single instance focus

iBG

P

iBG

P

iBG

P

Demo on December 5th?

ONOS 1 ...

ONOS 2

ONOS n

SDN-IP

SDN-IP

SDN-IP

ONOS Cluster

BGP speaker HA

ONOS/SDN-IP HA

External BGP router/connection HA

Communicationbetween externalnetworks

Communicationbetween SDN network and external network

Planned Internet2 deployment

● Provide L3 connectivity between 6 universities around USo SDN switches in the coreo ONOS and SDN-IP will control the network

● Universities will advertise through a BGP peer a /32 network to the SDN-IP application

● SDN-IP and ONOS will translate routes into “intents”`

Visit us online at onlab.us