Multi-Hypervisor Management

When it comes to hypervisors, one size may not fit all. vSphere may be a great fit for some workloads, KVM for others. Platform9 acts as a multi-hypervisor manager, allowing you to manage both without duplicating cost or effort.

Freedom of Hypervisor Choice

In the 2000s, VMware vSphere was the dominant hypervisor. Today, 90% of the public cloud runs on Linux-based virtualized infrastructure, and nearly 50% of enterprises leverage non-VMware hypervisors such as Linux/KVM and Hyper-V. In addition, there is growing interest and maturity in containers (especially Docker) as a newer alternative to traditional system virtualization.

As these trends evolve, your private cloud must be able to keep pace and help accelerate innovation with newer technologies – not lock you out from leveraging them.

Platform9 enables this freedom of choice, making it possible by providing a true single pane of glass across these virtualization platforms. Platform9 also enables an easy migration path for vSphere users looking to reduce virtualization licensing costs and mitigate vendor lock-in as they migrate VMware to KVM.

Easily Manage Mixed Hypervisor Environments

Single Pane of Glass Across Hypervisors

With Platform9, you can easily manage both KVM and VMware vSphere resources within a single private cloud platform, giving you a true single pane of glass across mixed environments while reducing IT management overhead.

Common Resource Consumption Model

Since both vSphere and KVM are fully supported, it is very easy to allocate capacity to a group of users from one or both of these platforms. The consumption experience is again consistent: a tenant receives a quota of capacity and access to certain networks in an “OpenStack region.” A region represents a physical domain of locally-networked servers running a supported hypervisor platform.

Designed to Manage Multiple Hypervisors

Platform9’s ability to manage mixed environments goes much deeper than the single pane visible in the user interface. The core of Platform9’s design is that regardless of the hypervisor platform, infrastructure and workloads are represented and managed using the OpenStack API. By extension, the UI, CLI and other API clients all see a consistent representation of the underlying infrastructure and resources. The table below illustrates this by mapping of core private cloud concepts to both vSphere and KVM.