into trademark issues §Designed to provide “Network-as-a-Service” functionality §Supplies a consistent API for provisioning network services §Uses a plugin architecture to allow a variety of backend providers §Leverages a number of open source technologies (network namespaces, Linux bridges, Open vSwitch, dnsmasq) Wednesday, April 24, 13
virtual switch §Supports OpenFlow, 802.1Q VLANs, LACP, STP §Supports KVM and Xen §OVS serves as the basis for a number of different SDN/network virtualization platforms §Currently the default networking stack for XenServer and Xen Cloud Platform (XCP) §More information available at http://openvswitch.org or http://blog.scottlowe.org/tag/ovs Wednesday, April 24, 13
§Leverages OVS across hypervisor platforms § Uses OVSDB API to communicate with the controllers § Receives flow configuration from controllers via OpenFlow §Leverages multiple network encapsulation protocols § Uses STT and GRE for encapsulation § Supports IPSec with STT/GRE for certain use cases §Supplies both L2 (switched) and L3 (routed) gateway services Wednesday, April 24, 13
flat network §Use case #2: Multiple flat networks §Use case #3: Mixed flat and private networks §Use case #4: Provider router with private networks §Use case #5: Per-tenant routers with private networks Wednesday, April 24, 13