NETWORK VIRTUALIZATION IMPLEMENTATION IN OPENDAYLIGHT BY THE OVSDB PLUGIN PROJECT: ARCHITECTURE AND OPENSTACK INTEGRATION Brent Salisbury Madhu Venguopal [email protected] [email protected] Red Hat Red Hat January 29, 2014
NETWORK VIRTUALIZATION IMPLEMENTATION IN OPENDAYLIGHT BY THE OVSDB PLUGIN PROJECT:���
ARCHITECTURE AND OPENSTACK INTEGRATION
Brent Salisbury ! ! ! ! ! ! ! ! ! ! Madhu Venguopal [email protected] ! ! [email protected] ! !!Red Hat ! ! ! ! ! ! ! ! ! ! ! ! Red Hat!
January 29, 2014
OVSDB COUPLED WITH A PROGRAMMABLE DATAPATH
MULTI-TENANT NETWORKS • Overlapping IP Address Space • Segment Isolation between tenants
is implemented using flow space on a common bridge/DPID.
• The value are the services not plumbing VIDs or subnets.
• For added isolation the the project can associate a datapath per tenant rather then sharing a common DPID.
• Avoid semantic constraints and the politics of tenant definition.
• Tunnel endpoints have no requirement from the physical network other then IP reachability.
NETWORKS ARE IN THE WAY OF CLOUD ADOPTION Pros: o The SDN value will be services and middlebox eradication. o Developers can be less concerned with DP resources. o Implementation is a code drop, not a pallet drop. o Tunnel End Points can be located anywhere. There are no
geographical constraints. This is Cloud networking if privacy and data protection are of any concern.
o One of the few, if not the only rational brownfield migration paths for software abstracted networks currently.
o It’s really software.
Cons: o No innovation around SLAs. o Solving QoS/disruptive workloads is hard. o Integration with orchestration is required to
realize significant benefit. o Networking needs to avoid reinventing
orchestration but focus on integration.
High Level Workflow