Virtual Networks/Overlays

The Virtual Networks/Overlays Working Group stemmed out of the ONUG Spring 2014 meeting, where users prioritized this use case as one of the top three. Since spring of 2014, the working group has published a white paper with detailed top 10 requirements, completed feature verification testing, and showcased proof of concept demonstrations based on the requirements.

The work being done in the group is based upon the original use case, included below, but has been expanded to include additional focuses around containers and virtual routed networks.

Virtual Networks/Overlays

Problem Being Solved: Hard to extend L2 net domains & migrate workload

  • Suboptimal asset utilization & availability due to physical rack limited cluster scope(s)
  • Workload migration is time consuming & complex

Open Networking Components:

  • Open SDN Controllers, OVSDB, multiple tunneling protocol options e.g., VxLAN, GENEVE, open provisioning APIs, neutron, etc.
  • Create an open approach to virtual networking/Overlays
  • Terminate endpoints on hypervisors + ToR
  • Integrated tunneled traffic management

Gap: Lack of standards and/or a standard. VLAN stretching not a solution

Benefits: Extend L2 domains & decouple net config policies independent of underlay

  • Business unit self-service delivery
  • Lower OpEx cost

Virtual Networks_Overlays