Video recording and production done by OpenStack Foundation.
Abstract: Based on the results of OpenStack user surveys, KVM is the de facto hypervisor used to underpin OpenStack clouds and Open vSwitch the most common network plug-in. However, as OpenStack matures to run production workloads and broadens its reach beyond the core users, it is inevitable that additional hypervisors, containers, bare metal workload will gain a foothold.
The whole notion of supporting a multi-hypervisor OpenStack environment is need driven. To illustrate, imagine that some databases in a business are virtualized on ESXi while the corresponding web servers are virtualized using KVM. In addition to the diversity, it is highly likely all these hypervisors and Docker container will be running concurrently in the same OpenStack cluster. As a result, a different approach to interconnecting is required to provide common network substrate.
We’ll discuss how multi-hypervisor networking in OpenStack can be achieved. This session will cover the technology options, the benefits of each and dive into various use cases where a multi-hypervisor OpenStack environment is desirable.