d7b5e0eaa9
1. Unpublish the current arch-design and temporarily relocate it to a "to archive" directory until the archiving structure is available 2. Publish the arch-design-draft to docs.openstack.org 3. Unpublish arch-design-draft from https://docs.openstack.org/draft/ Change-Id: Ida5f237d2edce7a83a24c376c355e2c220bc8c28 Implements: blueprint arch-design-pike
1.9 KiB
Choosing a hypervisor
A hypervisor provides software to manage virtual machine access to the underlying hardware. The hypervisor creates, manages, and monitors virtual machines. OpenStack Compute (nova) supports many hypervisors to various degrees, including:
An important factor in your choice of hypervisor is your current organization's hypervisor usage or experience. Also important is the hypervisor's feature parity, documentation, and the level of community experience.
As per the recent OpenStack user survey, KVM is the most widely adopted hypervisor in the OpenStack community. Besides KVM, there are many deployments that run other hypervisors such as LXC, VMware, Xen and Hyper-V. However, these hypervisors are either less used, are niche hypervisors, or have limited functionality based on the more commonly used hypervisors. This is due to gaps in feature parity.
In addition, the nova configuration reference below details feature support for hypervisors as well as ironic and Virtuozzo (formerly Parallels).
The best information available to support your choice is found on the Hypervisor Support Matrix and in the configuration reference.
Note
It is also possible to run multiple hypervisors in a single deployment using host aggregates or cells. However, an individual compute node can run only a single hypervisor at a time.