SDN-IP - Open Networking Research Center

Report
ONOS Use Cases
Tom Tofigh
AT&T
Service
NFaaS
Provider
in Network
Central Office
ofinthe
Multilayer
packet-optical
theFuture
Core
Core
Packet-Optical
PoP
Built like a
Data Center
Network Interface
Network Interface
Network Interface
Network Interface
Metro
Packet-Optical
NFaaS in Central
Office
Built like a
Data Center
Access
Wired
Access
Network Interface
Network Interface
Network Interface
Network Interface
Network Interface
Network Interface
Wireless
Access
Enterprise
Access
Wireless
Access
Wired
Access
Wireless
Access
Wired
Access
Wireless
Access
Enterprise
Access
Wireless
Access
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
Multi-layer SDN
control of
Packet-optical
Segment
Routing
SDN-IP
NFaaS in CO
North-bound abstraction
Policies
Application Intent Framework
ONOS
Southbound
Interface B
Southbound
Interface A
South-bound abstraction
OpenFlow
SDN based WAN Control with Segment routing
Routing
Service
Discovery
Forwarding
Service
Service
Requests
Requests
Routing,
Recovery,
Label imposition
ONOS
OpenFlow
SR Labels
imposed by
controller
OSR FIB built by
controller
This use case has been developed in collaboration with ONF.
Open
Segment
Routers
(OSR)
SDN Control of Multi Layer Networks:
Packet Optical
Praseed Balakrishnan
Fujitsu Network Communication
Todays Multi-Layer Network:
Without Converged Control Plane
E
C
A
Controlled and managed
independently
MPLS Tunnels
B
Packet networks over
provisioned to deal with
traffic bursts and P
failures
IP Routers
ROADMs
P3
1
R
1
D
P5
P4
Optical networks over
provisioned independently
P2
R
2
Slow to react
R to BW
demands 7
R4
R5
R6
Lack of agility and significant R3
capex & opex inefficiencies
With Converged Control Plane
E
C
A
Enable new services
with SDN control
plane
B
D
P3
P5
Reduce overprovisioning
of resources with a combined control plane
P
1
P2
Fast wavelength allocation of
bandwidth in transport
network for packet traffic
R
1
P4
R
2
Rapid recovery from
R7
transport
failures
R4
R3
R5
R6
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 view
o
•
•
•
•
Enables multi-layer PCE
Multi-layer aware service APIs
Southbound abstraction for multi-layer
Listening and reacting to failure
Northbound APIs
Implementation on ONOS
ONOS 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 - OVS
Optical Emulator (LINC-OE)
Planned BW of Demand Demo
Customer Portal
ONOS
10G Connection from NodeA:PortA
to NodeZ:Port Z with latency
less<10ms
DC1
DC2
OVS3
OVS5
IP
OVS1
IP
OVS4
OVS2
IP
IP
IP
Re-Route
optical circuit
optical
circuit
OE1
R7
OE7
OE4
OE2
ROADM
ROADM
ROADM
ROADM
ROADM
OE3
ROADM
OE5
ROADM
OE6
Seamless Interworking of
SDN and IP
Luca Prete
ON.Lab
ONOS and SDN-IP
SS
DD
NN
ONOS
ONOS
ONOS used to be confined in his wonderful world,but
wasn’t able to communicate with the outside
ONOS and 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
IP
IP
ONOS started to communicate with IP components
similar to it, speaking a widely used old language, called
BGP.
ONOS and SDN-IP
ONOS “Clusters” started also to “peer” together to be
more efficient and scalable using BGP
SDN-IP for external networks
SDN-IP to connect ONOS clusters
What has changed from last ONRC?
Old SDN-IP
New SDN-IP
BGPd
BGP
speaker
BGP
speaker
BGP
speaker
SDNIP
SDN-IP
SDN-IP
SDN-IP
ONOS
1
ONOS
2
ONOS
n
ONOS
1
ONOS
2
...
ONOS
n
• Single-instance
• No SDN-IP Application HA
• Able to speak with a single, dedicated
BGP speaker
• Stateless protocol (dedicated REST API)
...
• 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)
ARP
Before
Intent framework - NB
BgpSessionManager
SdnIpService
RouteListener
ArpService
After
Configuration
PeerConnectivityManager
SdnIpConfigReader
Router
PeerConnectivity
SDN-IP
IntentService
BGP architecture
SDN-IP: single instance focus
BGP
Speaker 2
BGP
Speaker n
iBGP
iBGP
iBGP
BGP
Speaker 1
SDN-IP boundary
BGP Session
1
BGP Session
2
BGP Session
Manager
RouteListener
...
BGP Session
3
Demo on December 5th?
ONOS Cluster
Communication
between SDN
network and
external network
ONOS/SDN-IP HA
External BGP
router/connection
HA
Communication
between external
networks
SDNIP
SDNIP
SDNIP
ONOS
1
ONOS
2
ONOS
n
...
BGP speaker HA
Planned Internet2 deployment
● Provide L3 connectivity between 6 universities around US
o SDN switches in the core
o 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

similar documents