Discuss ODL virtualization at ODL MiniSummit/Linuxcon Japan on May 20, 2014

1. OpenDaylight Network Virtualization
and its Future Direction
www.opendaylight.org
May 20, 2014
Masashi Kudo
NEC Corporation

2. Table of Contents
SDN Market Overview
OpenDaylight Topics
Network Virtualization
Virtual Tenant Network (VTN)
Open DOVE
Future of Virtualization
Page 2

3. Acknowledgement
We would like to extend our sincere thanks to
Anees Shaikh @Google for his inputs on virtualization in
OpenDaylight project and Open DOVE documents.

4. SDN Market Overview
Page 4

5. www.opendaylight.org
SDN market
SDN market estimation in Japan, 2012- 2017
Note: Sum total of data center, enterprise network and carrier SDN
Source: IDC Japan, 4/2014
5

6. Early
adopter Push type One to Many strategy
www.opendaylight.org
SDN market status
2013 2015～
Main stream
Sales
Product life
Innovator
Chasm

7. Expectations on OpenDaylight
Vendor
B
 OpenDaylight focuses on OSS based controller development
 Allows industry wide focus on application services where
www.opendaylight.org
SDN has competitive advantages
 Overcome the chasm by accelerating SDN deployment.
7
Vendor
A
OpenDaylight code (+Vendor C)
Vendor
D
Vendor
E
Vendor X
Applications
SDN Controller
SDN Hardware

8. OpenDaylight Topics
Page 8

9. Topics
 OpenDaylight Hydrogen accomplished（Feb 4, 2014）
www.opendaylight.org
 OpenDaylight Summit (2/4-5 Santa Clara)
 First ever public event held by OpenDaylight
 About 600 participants
 Hydrogen won Grand Prix at Interop Las Vegas 2014
 Best of Interop Grand Award and SDN Category Winner
9

10. OpenDaylight Sponsors
 Participating Organizations: 36 companies (as of May 12, 2014）
 Steady increase from the eighteen sponsors at the beginning
www.opendaylight.org
10
Platinum Gold
Silver
Nine Two Twenty-five

11. www.opendaylight.org
Virtualization Edition
11

12. Network Virtualization
Page 12

13. System Virtualization
www.opendaylight.org
TVriratduiatiloizneadl System
13
Appliance
virtualization
LB LB FW
Virtual Switch
VM VM
Virtual Switch
SV SV SV SV SV SV
Hypervisor
Hypervisor
OpenFlow Switch
LB LB FW FW
FW FW
Router
Storage
Storage
LB
L2 Switch
LB
L2 Switch
SV
SV
VM
Server
virtualization
Storage
Storage
Virtualization
Engine
Storage
Storage
virtualization
L2 Switch
Appliance
pooling

14. Technology that underpins network virtualization
Domain-level
Virtualization
VM associated to
the same tenant
www.opendaylight.org
Node-level
Virtualization
Virtual appliance
LB LB FW
Virtual Switch
Hypervisor
• Hypervisor/vSwitch
•HW offload (EVB)
• Mobility management
Tenant connectivity
•Overlay network
• Hop by hop network
• Policy management
Path-level
Virtualization
VM connectivity
V
M
V
M
• Tunnel technology
• Hop by hop packet fwd.
• Policy management
•Switch cluster
Network modeling
Physical network control
(Topology detection, isolation of tenants, Traffic control…)
14

15. Network virtualization to hide network variations
 Provide single network interfaces to upper layer applications
or operators by hiding varied physical networks.
www.opendaylight.org
Create tenant
Add appliance
Decouple
15
Network Service Layer
OpenFlow
Fabric
Overlay
network
Other
network
Network Abstraction Layer
OpenFlow
Overlay
(VXLAN, ..)
VLAN
Other
protocol
……..
Traditional
IP network
….
Network Control
Applications
High-Value Added
Applications

16. Virtual Tenant Network (VTN)
Page 16

17. VTN Project at OpenDaylight
 NEC contributed components at Hydrogen release.
VTN Manager
www.opendaylight.org
 VTN Coordinator
 Virtual network model and API
 VTN Manager
 Reactive control over OpenFlow network as underlay control.
(PACKET_IN, PACKET_OUT, FLOW_MODE)
 Based on NEC ProgrammableFlow GA product
REST API
SDN Application
REST API
VTN Manager
Switch Switch
REST API
Switch Switch
17
VTN Coordinator
OpenDaylight Controller
OpenDaylight Controller

18. www.opendaylight.org
VTN summary
 Network orchestration for:
 Multi data center
 Multi controller
 Multi network technology (Data plane independent)
 OpenFlow
 Overlay
 Etc
 VTN (Virtual Tenant Network) based NB-API for:
 OpenStack
 SDN Applications
18

19. VTN virtual network model
 Completely isolated virtual network with virtual abstractions
VTN1
vBridge interface
vBridge vBridge vBridge vtunnel vBridge
vBypass
vBridge vRouter interface
vRouter vLink
www.opendaylight.org
vBypass
vTunnel
vTep
VTN2
vRouter
vTEP vTEP
19
Components Description
Virtual node
(vNode)
vBridge logical representation of L2 switch function.
vRouter logical representation of L3 router function + DHCP relay agent.
vTep logical representation of Tunnel End Point - TEP.
vTunnel logical representation of Tunnel.
vBypass logical representation not coordinated by UNC.
Virtual interface interface representation of end point on the virtual node.
Virtual Link vLink logical representation of connectivity between virtual interfaces.

20. VTN Manager software configuration
 Implemented as OSGI bundle of Controller using AD-SAL
MD-SAL App.
www.opendaylight.org
 Manages OpenFlow switches
 OpenFlow 1.0
VTN Manager
AD-SAL (API-Driven Service Abstraction Layer)
OpenDaylight Controller
OpenFlow plugin
MD-SAL
(Model-Driven Service
Abstraction Layer)
Forwarding
Rules
Manager
OpenFlow Switch (OpenFlow 1.0)
Switch
Manager
Topology
Manager
Routing
NetworkConfig.
Neutron
20

21. www.opendaylight.org
 VTN (Virtual Tenant Network)
 Virtual network environment
 Each VTN network is isolated with each other
 vBridge (Virtual Bridge)
 Virtual L2 switch in VTN
 Construct virtual broadcast domain by associating the physical network
with vBridge
Multi-tenancy
Physical Network
vBridge vBridge
VTN
vBridge vBridge
VTN
Virtual Network
Associating virtual and physical
networks
VTN Manager
OpenDaylight
Controller
21

22. Physical topology detection
2. Transmits LLDP
packets from each port
LLDP packets that are not
transmitted to switch are
dropped.
OpenFlow Switch
Host
www.opendaylight.org
LLDP
LLDP
LLDP
Link status change notification
AD-SAL
OpenFlow plugin
OpenDaylight Controller
PACKET_IN
LLDP
3. LLDP packet received by
each physical switch is
notified to controller
1. OpenFlow plugin instructs each
physical switch to transmit LLDP
packets from the specified ports
PACKET_OUT
LLDP
Routing
Link status change notification
5. Shortest path graph between
switches is updated
4. Link information between
physical switches is
updated
Topology Manager
22

23. 1. Transmits unicast
packets
Port-1
7. Packets are
transmitted and
flow entry is set
2. Notifies unicast packet to
FLOW_MOD
FLOW_MOD
www.opendaylight.org
MAC Address Table
vBridge
Packet forwarding
Port-1
MAC-1
MAC-2
Switch-A
Switch-B
MAC Addr Port VLAN
MAC-1
Switch-A
Port-1
Untagged
MAC-2
Switch-B
Port-1
Untagged
…… …… ……
3. Determines the
vBridge to which the
packet is mapped
VTN Manager
VTN Manager
Forwarding
Rules
Manager
Search path
Routing
OpenDaylight Controller
To: MAC-2
4. Searches MAC address
table to determine the
output destination
To: MAC-2
AD-SAL
PACKET_OUT
transmission
5. Packet forwarding is
instructed to AD-SAL if
physical network path is
present
PACKET_IN
To: MAC-2
PACKET_OUT
To: MAC-2
Flow Entry settings
6. Flow entry
settings are
instructed
OpenFlow plugin
PACKET_IN
notification
23

24. OpenStack (Neutron) integration
Create vBridge Configure VLAN mapping
vBridge
OpenFlow
Switch
www.opendaylight.org
24
provider.network_type=vlan
provider.segmentation_id=1
Modular Layer 2
ML2 Driver for
OpenDaylight
OpenStack Neutron
VTN Manager
Notify network
creation
NetworConfng.Neutron
OpenDaylight Controller
VTN
VLAN Mapping
Create network
Neutron API
Network
Notify
network
creation VLAN: 1

25. Open DOVE
Page 25

26. Open DOVE Summary
System Networking
 Open DOVE is an overlay network virtualization platform for the data center
 logically isolated multi-tenant networks with layer-2 or layer-3 connectivity
www.opendaylight.org
 runs on any IP network in a virtualized data center
 based on IBM SDN-VE GA product and DOVE technology from IBM Research
 Open DOVE features
 full-function, ready for real deployments, incl. HA
 control plane implementation, incl. address, policy, and mobility management
 management interfaces for programmatic configuration, including OpenStack
enablement
 open data plane implementation for Linux/KVM and VxLAN encapsulation
 software gateway for connecting to non-virtualized networks and external
hosts
26
© 2013 IBM Corporation

27. Multi-tenant network with overlays
 provide each data center tenant with a single virtual network
System Networking
www.opendaylight.org
abstraction
 SDN controller uses overlays to virtualize physical network infrastructure
 one-time deployment and configuration of the physical network
 virtual network implemented
purely on end hosts by
software switches and
encapsulation
 overcomes scaling limits of
physical network
virtualization
SDN
VM
controller
VM
Tenant 1
VM
VM
VM
Tenant 2
27
© 2013 IBM Corporation

28. Open DOVE Architecture
System Networking
Virtual Network 3
www.opendaylight.org
Open DOVE
Management
Console
VM VM VM
Existing IP Network
Open DOVE
Gateway Existing IP Network
End
Station
End
Station
VM Virtual Network 1
VM Virtual Network 2
VM Virtual Network 3
OpenDaylight controller
Open DOVE
Connectivity
Server
Hypervisor
RESTful, Quantum
VM VM VM
Hypervisor
VM VM VM
Hypervisor
Virtual Network 1
Virtual Network 2
Virtual Network 3
Open DOVE
virtual overlays
Open DOVE
vSwitch
Open DOVE
vSwitch
Open DOVE
vSwitch
APIs
OpenStack
Cloud/DC
Provisioning
Applications
28
© 2013 IBM Corporation

29. DOVE virtual network model
System Networking
 DOVE virtual networks are modeled as domains, virtual networks, subnets,
Virrtual network 1
www.opendaylight.org
policies, and gateways
subnet
Y
domain A
domain B
subnet
X
subnet
Y
subnet
Z
Virtual network 3
subnet
W
Virtual network 5
Policy
Virtual network 4
gateway
policy
29
© 2013 IBM Corporation

30. DOVE address discovery
System Networking
communicating with a VM
on another Server. DOVE
resolution from the DCS.
Server
VM VM
DOVE
vSwitch
Hypervisor
A VM begins
vSwitch requests
3
4
The DCS responds with
information. VM mapping
information is cached
www.opendaylight.org
30
DCS
Server
VM VM
DOVE
vSwitch
Hypervisor
Server
VM VM
DOVE
vSwitch
Hypervisor
Management
DCS
DCS
On VM activation, DOVE
vSwitch detects VM’s IP /
MAC@ and updates the
DOVE Connectivity
Service (DCS).
The DCS clustered
nodes share the
address mapping
information. 2
Server
VM VM
DOVE
vSwitch
Hypervisor
Clustered DOVE
Console
Connectivity Service
DOVE
1
the VM mapping
locally at the DOVE
vSwitch
30 OpenDaylight mini-summit | September 2013 © 2013 IBM Corporation

31. DOVE packets in virtual and physical networks
R R R R I R R R Reserved (24-bits)
DOVE VNID (24-bits) Reserved (8-bits)
System Networking
www.opendaylight.org
SRC
IP Cloud
DOVE Switch
(DST DS)
DST
Dove Encapsulation
DOVE Switch
(SRC DS)
SRC->DST
SRC DS -> DST DS
DOVE Header:
31
© 2013 IBM Corporation

32. DOVE packet forwarding
VM1 attached to Host 2
vSwitch by a vNIC
VM3 VM4
System Networking
vSwitch2 strips the
encapsulation
headers and delivers
the packet to VM3
www.opendaylight.org
32
Host 1
VM1 VM2
DOVE vSwitch 1
DCN
(Physical Underlay)
DOVE vSwitch 2
VM1 sends data to
VM3 which enters the
vSwitch
vSwitch1 determines
VM3 reachable
through vSwitch2.
vSwitch1
encapsulates the
packets for delivery
to vSwitch 2 using
Physical Network
Physical Network
delivers the
encapsulated packet
to vSwitch2
Physical Network is
aware of vSwitches 1
& 2, but is unaware
of VMs 1..4
vSwitches use
Overlay ID in the
encapsulation
header to keep traffic
isolated
VM1,3 & VM2,4
belong to different
tenants and are
isolated from one
another.
© 2013 IBM Corporation

33. DOVE Gateway
System Networking
 DOVE Gateways allow VMs on a DOVE Network to connect to systems on a non-DOVE
74.125.227.96
(google.com)
www.opendaylight.org
Network.
 Two types of connections are supported:
 DOVE External Gateway
 Connects VMs on a DOVE Network with Systems on an External Network and vice-versa.
 Supports for NAT or Pass-Thru connection to External Networks.
 DOVE VLAN Gateway
 Connects VMs on a DOVE Network to Systems
on a VLAN Segment and vice-versa
129.42.56.158
(ibm.com)
DOVE Gateway
VM VM
DOVE Overlay Network External
DOVE Overlay Network
Connection
VLAN
Connection
DOVE
Encap /
Decap
VM
VM VM VM
External / Physical
Network
Server /
VM
Server /
VM
VLAN Segment
10.1.1.5 10.1.1.7 10.1.1.8
10.1.2.6 10.1.2.3 10.1.2.8 10.1.2.10 10.1.2.13
33
© 2013 IBM Corporation

34. Future of Virtualization
Page 34

35. Overlay & Hop by Hop
www.opendaylight.org
35
Overlay Hop by Hop
Pros Effectively use existing IP network resources
Enable construction of a scalable end-to-end
virtual network
In line with business needs like SLA, it
enables traffic control, including
bandwidth control etc., at a minute level
for each flow
Cons Traffic quality and quantity, using only virtual
switches causes performance bottleneck
Bandwidth control for each node
OpenFlow complaint switch needed
Physical specifications are a limiting
factor in scalability
OpenDaylight Open DOVE VTN
Hop by Hop Approach
Overlay
Approach
TE, QoS
Existing assets,
scalability
Hybrid
Virtualization

36. Hybrid Virtualization Options
Pattern 2 Pattern 3
Horizontal
Integration
VTN VTN
www.opendaylight.org
Pattern 1-2
Vertical
Integration
(VTN as Underlay)
Pattern 1-1
Vertical
Integration
(VTN as Network Model)
Edge overlay Gateway overlay OpenFlow network
Traditional
IP network
Elastic network control by flow control
Gateway
Integration
VTN
VTN
36

37. Virtualization related projects in OpenDaylight
Category Started at Hydrogen Accepted projects for
Helium
www.opendaylight.org
Application Defence4All
Network
Virtualization
VTN
Open DOVE
Affinity
Group Policy Plugin
South-bound OpenFlow
LISP
OVSDB
BGP/PCEP
SNMP4SDN
Packet Cable PCMM
OpFlex
37

38. www.opendaylight.org
Future direction
38
Integration among OpenDaylight projects
Introduction of applications
on virtualized network
Accumulation of user experiences

39. Thank you for your attention.
www.opendaylight.org
39