1. Building Open Source-Based Cloud Solutions with OpenDaylight
Colin Dixon, Brocade/OpenDaylight
Lisa Caywood, OpenDaylight

2. Part of a New OPEN Networking Stack
Custom HW
VMs / Cont.
Legacy
Optical
BGP
OVSDB
Netconf
OpenFlow
ORCHESTRATION
(NFVO, ...)
Networking Apps
Mgmt / Analytics App
Rest API
Open NOS
SDN Platform
YANG
ECOMP
OpenDaylight has always been about connecting devices (physical or virtual)
Increasingly, OpenDaylight is also about connecting projects acting as open source glue
ECOMP, OPNFV, OpenStack, OVS, FD.io, …
As a result, it’s the center of building open source clouds
Generic OpenStack Networking
CORD/vCO with OpenDaylight (this is the above + reality + service chaining)
Agile & programmable
Modular and interoperable
Greenfield AND brownfield
Heavily leverages virtualization & cloud
Incorporates flexible orchestration
Facilitates increasing levels automation

3. OpenDaylight Now
“OpenDaylight fundamentally changed the Linux Foundation’s world. It’s been wildly successful. It’s the de facto standard open source SDN controller for the industry today.”
- Dave Ward, Cisco CTO
Mature, Open Governance
800+ Contributors
Over 100 deployments
Leading use cases identified
Dozens of ODL-based solutions
Mature code base
Focus on performance, scale and extensibility
*SDxCentral, 9/7/16

4. Boron Features and Capabilities
Integration - industry frameworks
OPNFV
OpenStack enhancement
CORD/vCO
ECOMP
ONF/Atrium
Common SDN toolchains
Net Virtualization + SFC:
OF + OVSDB + OVS/FD.io
Mgmt plane programmability:
BGP + PCEP + MPLS + NETCONF
Operational tooling
Cardinal health monitoring
Data analytics (TSDR & Centinel)
OCP (Open radio I/F)
Documentation
App developer tooling
YANG-IDE toolkit
NetIDE for cross-OSS controller interoperability
NeXt UI toolkit
“Singleton app” HA
App developer tooling
YANG-IDE toolkit
NetIDE for cross-OSS controller interoperability
NeXt UI toolkit
“Singleton app” HA

5. OpenDaylight Boron in Open Clouds
The glue that holds together L2-7 networking functions
Coordinates physical and virtual resources
Network, compute, storage
Network virtualization with service function chaining
OpenStack-based network virtualization
Virtualized Central Office (vCO; AKA CORD)

6. OpenDaylight with OpenStack

7. OpenDaylight Boron
Boron Diagram, September 21st, 2016

8. OpenStack/OpenDaylight Integration
Multiple Neutron implementations
Target different use cases, southbound drivers
FD.io/VPP
OVS
Open Overlay Router (née LISPmob)
Provide distributed implementations of scalable network virtualization for OpenStack
FD.io, OVS, OpenOverlayRouter/LISPMob

9. OpenStack/OpenDaylight Integration
L2: ML2 plugin
L3: ODL L3 plugin
services
FWaaS
L2Gateway
QoS
LBaaS
BGPVPN
networking-sfc
trunk
Neutron Server
ML2 Plugin
ODL L3
Plugin
Service
Plugins
Type Manager
Mechanism Manager
FWaaS
L2GW
QoS
...
GRE TypeDriver
VLAN TypeDriver
VXLAN TypeDriver
ODL mech driver
SR-IOV
ODL driver
ODL driver
ODL driver
...
...
...
...
...
networking-odl

10. OpenStack and OpenDaylight Integration
Network/Control Node
Neutron
ML2 DB
ML2 Plugin
Networking-odl
Controller node
OpenDaylight*
Neutron Northbound
ovsdb/NetVirt
Yang
Model
Management Network
Compute Node
Networking Node
Internet
Data Network VM VM VM
OVS
DHCP Agent
OVS
Public Network
Router

11. OpenDaylight in vCO and ROBO

12. What does Central Office do?
Subscriber management capabilities: Gateway, authentication and authorization, event and subscriber information logging
Optical Line Termination (OLT) for PON/GPON (Passive Optical Net.)
Service functions: self-service portals, NAT, FW, routing, IP addr mgmt, QoS, quotas, video caching, mail and file stores
A Virtualized Central Office (vCO):
Uses general-purpose compute, storage and network capabilities to deliver the above services
Added agility (spin up VMs vs. rack and stack hardware)
Cost savings (via increased automation and commodity servers)

13. vCO Data Center Architecture
Physical elements are divided into
Network: provides fabric/underlay
Servers: provides computer/storage for VNFs
North- South
Fabric/Underlay (Network) VM
Servers/VNFs (Compute, Storage) VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
WAN
East West
WAN

14. vCO Data Center Architecture
Controllers and orchestrators use overlay networks to form service chains of VNFs
North- South
VNF VM VM VM VM
VNF VM VM VM VM
VNF VM VM VM VM VM VM VM
VNF VM VM VM
VNF VM VM VM VM VM VM
WAN
East West
WAN

15. vCO Data Center Software Architecture
OSS/BSS
Policy (NIC, NEMO, GBP, Neutron)
VNFO (ECOMP, Open-O, OSM, …)
Service
Chaining
Overlay
Network
Fabric
VNF Spec (TOSCA)
VNF Catlog
VNFM (Tacker, Cloudify, …)
SDN Controller (OpenDaylight)
VIM (OpenStack, Kubernetes, …)
Fabric/Underlay (Network)
VNF VM
Servers/VNFs (Compute, Storage) VM VM VM VM VM VM
VNF VM
VNF VM VM VM VM VM VM VM
VNF VM VM VM
VNF VM VM VM VM VM VM

16. ROBO: Using vCO Blueprint in Enterprises
vCO for Enterprises to provide for Remote/Branch offices
Maybe offered by ISPs as a service
Integrating with public cloud will likely involved some form of vCO (either aaS or Enterprise-deployed)
Hybrid Cloud will almost certainly involve vCO
Private
Cloud
Branch Office
Public
vCOaaS
from ISP
Remote Office
Main Office
vCO to connect backends
ROBO = Remote office/Branch office

17. Think Beyond the Controller
Product
Enabling solution component

18. Thank you