Datacenter Network Virtualization in Multi-Tenant Environments€¦ · 06/09/2015 · Datacenter...

Chair for Network Architectures and Services

Technische Universität München

Datacenter Network Virtualization in

Multi-Tenant Environments

8. DFN-Forum Kommunikationstechnologien

Viktor Goldberg, Leibniz-Rechenzentrum, TU München

Florian Wohlfart, TU München

Daniel Raumer, TU München

09.06.2015 1

Network Functions Virtualization

09.06.2015 Viktor Goldberg 2

Applications

x86 Hardware

COMPUTE VIRTUALIZATION LAYER DECOUPLED

Network Functions Virtualization

•

•

•

•

•

•

•

•


Building the Network Virtualized Datacenter

•

•

•

•

•

•

•

•

Overlay Network Architecture

09.06.2015 4Viktor Goldberg

Network Virtualization Overlays

VXLAN creates logical L2 domains over standard L3 infrastructure.

• VM traffic encapsulated inside a UDP/IP frame plus VNI identifier

• VNI defines the L2 domain

• encapsulation performed by a VTEP node

• VTEP is a software or physical switch (at the ToR)

Encapsulated frames are routed to the remote VTEP.

• remote VTEP strips the IP/UDP header

• forwards original frame to the local VM

• transparent to the network core, not aware of the VXLAN overlay

• only edge VTEP nodes need to be VXLAN aware

VXLAN - How does it work?


Open vSwitch (OVS)


Design and Architecture

•

•

•

•

controller

running in userspace

slowpath

datapath

running in kernel

fastpath

Data Plane Control Plane

Open vSwitch (OVS)


A Deep Dive

Open vSwitch (OVS)


A Deep Dive

KERNEL

Open vSwitch (OVS)


A Deep Dive

Datapath

KERNEL

Open vSwitch (OVS)

09.06.2015

Viktor Goldberg 7

A Deep Dive

Datapath

vswitchd

USERSPACE

KERNEL

Open vSwitch (OVS)


A Deep Dive

Datapath

vswitchd ovsdb-srv

USERSPACE

KERNEL

Open vSwitch (OVS)


A Deep Dive

Datapath

vswitchd ovsdb-srv

OpenFlow

USERSPACE

KERNEL

Open vSwitch (OVS)


A Deep Dive

Datapath

vswitchd ovsdb-srv

OpenFlow

USERSPACE

KERNEL

MGMT

Open vSwitch (OVS)


A Deep Dive

Datapath

vswitchd ovsdb-srv

ovs-dpctl ovs-vsctl

ovsdb-tool

OpenFlow

ovs-ofctl

USERSPACE

KERNEL

MGMT


• routed traffic at the top of rack

• proven and trusted protocol for scale

• mature open standards for interoperability

• standard scalable model for virtualized and non-virtualized solutions

• minimized size of the L2 domain

• no VLAN scaling issues

Physical Infrastructure



Scaling an L3 network for East to West traffic



Mininet

• “an instant virtual network on your laptop“

• running real kernel, switch and application code in a VM

• supports Open vSwitch

Motivation

• multi-tenant environment with two tenants T1 and T2

• overlapping IP networks and addresses

• completly transparent tunneling, even broadcast traffic (like ARP, DHCP)




Mininet VM Mininet VM




DEMOSYS1

IP: 172.16.116.135

DEMOSYS2

IP: 172.16.116.136




DEMOSYS1

IP: 172.16.116.135

DEMOSYS2

IP: 172.16.116.136

00:00:00:00:00:01 00:00:00:00:00:02




DEMOSYS1

IP: 172.16.116.135

DEMOSYS2

IP: 172.16.116.136

00:00:00:00:00:01

00:00:00:00:00:01

00:00:00:00:00:02

00:00:00:00:00:02




DEMOSYS1

IP: 172.16.116.135

DEMOSYS2

IP: 172.16.116.13610 10

00:00:00:00:00:01

00:00:00:00:00:01

00:00:00:00:00:02

00:00:00:00:00:02




DEMOSYS1

IP: 172.16.116.135

DEMOSYS2

IP: 172.16.116.13610 10

00:00:00:00:00:01

00:00:00:00:00:01

00:00:00:00:00:02

00:00:00:00:00:02

10

20


S1 – 172.16.116.135

sh ovs-vsctl add-port s1 vtep -- set interface vtep type=vxlan

option:remote_ip=172.16.116.136 option:key=flow ofport_request=10

S2 – 172.16.116.136

sh ovs-vsctl add-port s2 vtep -- set interface vtep type=vxlan

option:remote_ip=172.16.116.135 option:key=flow ofport_request=10

Demo - Interface Configuration



flows1.txt

table=0,in_port=1,actions=set_field:10->tun_id,resubmit(,1)

table=0,in_port=2,actions=set_field:20->tun_id,resubmit(,1)

table=0,actions=resubmit(,1)

table=1,tun_id=10,dl_dst=00:00:00:00:00:01,actions=output:1




...

Demo - Flow configuration excerpt




Demo



Demo Setup VXLAN Tunneling

T1_1 ping 10.0.0.1

T2_1 ping 10.0.0.2

tcpdump –i eth0

[icmp type {0,8}]

tcpdump –i eth0

[icmp type {0,8}]

tcpdump –i eth0

[icmp type {0,8}]

Conclusion

• simple design of physical environment to provide IP end-to-end connectivity only

• logic should be placed into “Intelligent Edges“, ToR switches like OVS

• logical tenant separation through VXLAN tunneling technologies

Future Work

• identification of services and tenants with specific needs

• deployment of a test environment

• long term goal: NFV rollout and optimization of physical underlay


Chair for Network Architectures and Services

Technische Universität München


Thank You.

Questions?

Datacenter Network Virtualization in Multi-Tenant Environments€¦ · 06/09/2015 · Datacenter...

Documents

Transcript of Datacenter Network Virtualization in Multi-Tenant Environments€¦ · 06/09/2015 · Datacenter...