1. Open vSwitch: Extending Networking into the Virtualization Layer Ben Pfaff Justin Pettit Teemu Koponen Keith Amidon Martin Casado Nicira Networks, Inc. Scott Shenker UC Berkeley, Computer Science Division

2. Outline ● Virtualization and Networking ● Open vSwitch approach ● Applications ● Implementation

3. Virtualization Will Be Pervasive Gartner: 12% of workloads are virtual today. 61% by 2013. Intel: All end hosts should be virtualized.

4. Networking in Virtual Environments is Important One cloud is planning to run 128 VMs per host. That's 2+ full racks in one machine.

5. Networking in Virtual Environments is Different Challenges ● Scalability (10 5 VMs) ● Isolation ● Mobility ●... Conveniences ● Hypervisor info ● Introspection ● Leaf nodes ●...

6. Networking in Virtual Environments is Different Challenges ● Scalability (10 5 VMs) ● Isolation ● Mobility ●... Conveniences ● Hypervisor info ● Introspection ● Leaf nodes ●... Open vSwitch Distribute the Switch Centralized Control Take Advantage

7. Basic Design (Xen) NIC Control domain (Dom0) VM 1VM 2VM 3 VNI C Virtual machines (DomUs) Xen host (physical machine) Controller ovs-vswitchd Adminstrative CLI/GUI...other Xen hosts... XAPI

8. Open vSwitch ● Controller: ● - Configuration ● - OpenFlow ● Features: ● - VLAN ● - Port mirroring ● - ACLs ● - NetFlow ● - Bonding ● - QoS ● - Anything*

9. Open vSwitch Application: Single Distributed Switch VM host 1 VM host n... Controller

10. Open vSwitch Application: Multiple Distributed Switches VM host 1 VM host n... Physical vSwitch GRE Controller Physical VM 1VM n... Logical Tenant #1 (switched) VM 1VM n... Tenant #2 (routed)

11. Open vSwitch Application: Extending Data Center into Cloud VM host 1 VM host n... “Cloud access server” GRE Customer Data Center Controller Managed Cloud GRE/ IPSEC/ SSL

12. Implementation (Xen) Fast Path ovs-vswitchd NIC Xen hypervisor Control domain (Dom0) use r kerne l VM 1VM 2VM 3 VNI C Virtual machines (DomUs) Physical machine Controller XAPI

13. Open vSwitch is Fast Bandwidth Fast Path: > 1 Gbps ovs-vswitchd: 100 Mbps Controller: 10 Mbps Latency Fast Path: < 1 µs ovs-vswitchd: < 1 ms Controller: ms As fast as Linux bridge with same CPU usage

14. Open vSwitch is Fast vswitc h Linux bridge

15. Hardware Acceleration ● Inevitable ● Netronome: right approach ● VN-Tag: wrong approach ● VEPA: powerless

16. ● Physical switches ● Upstream kernel integration ● Anything* Future Directions

17. Questions?