Odl virtualization-20140520

www.opendaylight.org

OpenDaylight Network Virtualization

and its Future Direction

May 20, 2014

Masashi Kudo

NEC Corporation

Table of Contents

SDN Market Overview

OpenDaylight Topics

Network Virtualization

Virtual Tenant Network (VTN)

Open DOVE

Future of Virtualization

Page 2

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.

SDN Market Overview

Page 4


SDN market

Note: Sum total of data center, enterprise network and carrier SDN

Source: IDC Japan, 4/2014

SDN market estimation in Japan, 2012- 2017

5


SDN market status

2013 2015～

Main stream

Sales

Product life

Early

adopter Push type One to Many strategyInnovator

Chasm


Expectations on OpenDaylight

OpenDaylight focuses on OSS based controller development

Allows industry wide focus on application services where

SDN has competitive advantages

Overcome the chasm by accelerating SDN deployment.

7

Vendor

A

OpenDaylight code (+Vendor C)

Vendor

B

Vendor

D

Vendor

E

Vendor X

Applications

SDN Controller

SDN Hardware

OpenDaylight Topics

Page 8


OpenDaylight Hydrogen accomplished（Feb 4, 2014）

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

Topics

9


Participating Organizations: 36 companies (as of May 12, 2014）

Steady increase from the eighteen sponsors at the beginning

OpenDaylight Sponsors

10

Platinum Gold

Nine Two Twenty-five

Silver


Virtualization Edition

11

Network Virtualization

Page 12


Traditional SystemVirtualized System

System Virtualization

13

FW FW

Router

SV SV SV SV SV SVS

tora

ge

Sto

rage

LB

L2 Switch

LB

L2 Switch

SV

Hypervisor

Virtual Switch

SV

VM VM

Hypervisor

Virtual Switch

VM

Server

virtualization

Sto

rage

Sto

rage

Virtualization

EngineS

torage

Storage

virtualization

L2 Switch

Appliance

pooling

OpenFlow Switch

LB LB FW FW

Appliance

virtualization

LB LB FW


Technology that underpins network virtualization

Virtual appliance

Node-level

Virtualization

•Hypervisor/vSwitch

•HW offload (EVB)

•Mobility management

Hypervisor

Virtual Switch

LB LB FW

Tenant connectivity

Domain-level

Virtualization

•Overlay network

•Hop by hop network

•Policy management

VM associated to the same tenant

VM connectivity

Path-level

Virtualization

•Tunnel technology

•Hop by hop packet fwd.

•Policy management

•Switch cluster

VM

VM

Network modeling

Physical network control

(Topology detection, isolation of tenants, Traffic control…)

14


Decouple

Provide single network interfaces to upper layer applications

or operators by hiding varied physical networks.

Network virtualization to hide network variations

15

Network Service Layer

OpenFlow

FabricOverlay

network

Other

network

Network Abstraction Layer

OpenFlowOverlay

(VXLAN, ..)VLAN

Other

protocol……..

Traditional

IP network

Create tenant

Add appliance

….

Network Control

Applications

High-Value Added

Applications

Virtual Tenant Network (VTN)

Page 16


NEC contributed components at Hydrogen release.

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

VTN Project at OpenDaylight

REST API

REST API

SwitchSwitch

REST API

SwitchSwitch

17

VTN Coordinator

OpenDaylight Controller

VTN Manager


VTN Manager

SDN Application


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

VTN summary

18


Completely isolated virtual network with virtual abstractions

VTN virtual network model

vBridge interface

vRouter interfacevBridge

vRouter vLink

vBypass

vTunnel

vTep

VTN2

VTN1vRouter

vBridge vBridgevBridge vBridgevtunnel

vTEP vTEP

vBypass

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.


Implemented as OSGI bundle of Controller using AD-SAL

Manages OpenFlow switches

OpenFlow 1.0

VTN Manager software configuration

OpenDaylight ControllerOpenFlow plugin

AD-SAL (API-Driven Service Abstraction Layer)MD-SAL

(Model-Driven Service

Abstraction Layer)

MD-SAL App.

Forwarding

Rules

Manager

OpenFlow Switch (OpenFlow 1.0)

VTN Manager

Switch

Manager

Topology

ManagerRouting

NetworkConfig.

Neutron

20


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

VTNvBridgevBridge

VTNvBridgevBridge

Virtual Network

OpenDaylight

Controller

VTN Manager

Associating virtual and physical

networks

21


Physical topology detection

OpenFlow Switch

Host

2. Transmits LLDP

packets from each port

LLDP

LLDP

LLDP

LLDP packets that are not

transmitted to switch are

dropped.


OpenFlow plugin

AD-SAL

Link status change notification

3. LLDP packet received by

each physical switch is

notified to controller

PACKET_IN

LLDP

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


vBridge

MAC Address Table

Packet forwarding

Port-1

Port-1

MAC-2

MAC-1

Switch-A

Switch-B

MAC Addr Port VLAN

MAC-1Switch-A

Port-1Untagged

MAC-2Switch-B

Port-1Untagged

…… …… ……


To: MAC-2

1. Transmits unicast

packets

4. Searches MAC address

table to determine the

output destination

To: MAC-2

7. Packets are

transmitted and

flow entry is set

AD-SAL

Forwarding

Rules

ManagerPACKET_OUT

transmission

Routing

Search path

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_MOD

FLOW_MOD

Flow Entry settings

6. Flow entry

settings are

instructed

OpenFlow plugin

VTN Manager

3. Determines the

vBridge to which the

packet is mapped

PACKET_IN

notification

2. Notifies unicast packet to

VTN Manager

23


OpenStack (Neutron) integration

24

OpenFlow

Switch

OpenStack Neutron

Modular Layer 2ML2 Driver for

OpenDaylight


VTN Manager

NetworConfng.Neutron

VTN

VLAN Mapping

Create network

Neutron API

Network

provider.network_type=vlan

provider.segmentation_id=1

Notify

network

creation VLAN: 1

Create vBridge Configure VLAN mapping

Notify network

creation

vBridge

Open DOVE

Page 25


Open DOVE Summary

Open DOVE is an overlay network virtualization platform for the data center

logically isolated multi-tenant networks with layer-2 or layer-3 connectivity

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

System Networking


provide each data center tenant with a single virtual network

abstraction

SDN controller uses overlays to virtualize physical network infrastructure

one-time deployment and configuration of the physical network

Multi-tenant network with overlays

virtual network implemented

purely on end hosts by

software switches and

encapsulation

overcomes scaling limits of

physical network

virtualization

SDNcontroller

VM

VM

Tenant 1VM

VM

VM

Tenant 2

27


System Networking


Open DOVE Architecture

Existing IP Network

Open DOVE Gateway Existing IP Network

End

StationEnd

Station

Virtual Network 3

VM Virtual Network 1



OpenDaylight controller

Open DOVE Management

Console

Open DOVE Connectivity

Server

Hypervisor

VM VM VM

Hypervisor

VM VM VM

Hypervisor

VM VM VM

Virtual Network 1

Virtual Network 2

Virtual Network 3

Open DOVE

virtual overlays

Open DOVE vSwitch

Open DOVE vSwitch

Open DOVE vSwitch

RESTful, Quantum

APIsOpenStack

Cloud/DC Provisioning

Applications

28


System Networking


DOVE virtual network model

DOVE virtual networks are modeled as domains, virtual networks, subnets,

policies, and gateways

domain Adomain B

Virrtual network 1

subnet X

subnet Y

Virtual network 3

subnet Z

Virtual network 5

subnet W

subnet Y

Virtual network 4

Policy

gateway

policy

29


System Networking


DOVE address discovery

30

30 OpenDaylight mini-summit | September 2013 © 2013 IBM Corporation

DCS

DOVE

vSwitch

VM VM

Server

Hypervisor

DOVE

vSwitch

VM VM

Server

Hypervisor

DOVE

vSwitch

VM VM

Server

Hypervisor

DCSDCS

DOVE

vSwitch

VM VM

Server

Hypervisor

Clustered DOVE Connectivity Service

DOVE

Management

Console

On VM activation, DOVE vSwitch detects VM’s IP / MAC@ and updates the

DOVE Connectivity Service (DCS).

1

The DCS clustered nodes share the address mapping

information.2

A VM begins communicating with a VM on another Server. DOVE

vSwitch requests resolution from the DCS.

3

4The DCS responds with

the VM mapping information. VM mapping

information is cached locally at the DOVE

vSwitch

System Networking


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)

SRC

IP Cloud

DOVE Switch (DST DS)

DST

Dove Encapsulation

DOVE Switch (SRC DS)

SRC->DST

SRC DS -> DST DS

DOVE Header:

31


System Networking


DOVE packet forwarding

32

DOVE vSwitch 1

VM1 VM2

Host 1

DCN

(Physical Underlay)

DOVE vSwitch 2

VM3 VM4

Host 2VM1 attached to vSwitch by a vNIC

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

vSwitch2 strips the encapsulation

headers and delivers the packet to VM3

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.


System Networking


DOVE Gateways allow VMs on a DOVE Network to connect to systems on a non-DOVE

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

DOVE Gateway

DOVE Gateway

DOVE Overlay Network

DOVE Overlay Network External

Connection

VLAN

Connection

DOVE

Encap /

Decap

VM

VM VM VM

VM VM

External / Physical

Network

Server /

VM

Server /

VM

VLAN Segment

74.125.227.96

(google.com)

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

129.42.56.158

(ibm.com)

33


System Networking

Future of Virtualization

Page 34


Overlay & Hop by Hop

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

Ov

erla

y

Ap

pro

ach

TE, QoS

Existing assets,

scalabilityHybrid

Virtualization


Hybrid Virtualization Options

Edge overlay Gateway overlay OpenFlow networkTraditional

IP network

Elastic network control by flow control

VTN VTN

Pattern 2 Pattern 3

Horizontal

Integration

Gateway

Integration

VTN

Pattern 1-2

Vertical

Integration

(VTN as Underlay)

VTN

Pattern 1-1

Vertical

Integration

(VTN as Network Model)

36


Category Started at Hydrogen Accepted projects for

Helium

Application Defence4All

Network

Virtualization

VTN

Open DOVE

Affinity

Group Policy Plugin

South-bound OpenFlow

LISP

OVSDB

BGP/PCEP

SNMP4SDN

Packet Cable PCMM

OpFlex

Virtualization related projects in OpenDaylight

37


Future direction

38

Integration among OpenDaylight projects

Introduction of applications

on virtualized network

Accumulation of user experiences


Thank you for your attention.

39

Presentations & Public Speaking

Odl virtualization-20140520