Difference between revisions of "HypervisorSupportMatrix"
(corrected typo) |
(Documenting the XenAPI caveat) |
||
| Line 91: | Line 91: | ||
|- | |- | ||
| Inject Networking | | Inject Networking | ||
| − | | ✔* | + | | ✔*(1)(2) |
| − | | ✔* | + | | ✔*(1) |
| − | | ✔* | + | | ✔ *(1) |
| | | | ||
| ✔* | | ✔* | ||
| Line 231: | Line 231: | ||
|- | |- | ||
| Config Drive | | Config Drive | ||
| − | | ✗* | + | | ✗*(3) |
| ✔ | | ✔ | ||
| ✔ | | ✔ | ||
| Line 238: | Line 238: | ||
|- | |- | ||
| Auto configure disk | | Auto configure disk | ||
| − | | ✔ | + | | ✔ |
| | | | ||
| | | | ||
| Line 245: | Line 245: | ||
|} | |} | ||
| − | + | # Inject Networking only works with nova-network in Flat mode, and only with Debian/Ubuntu based virtual machines | |
| + | # [[XenServer]] integration also supports using a guest agent to inject networking settings | ||
| + | # XenAPI Config drive support is [https://blueprints.launchpad.net/nova/+spec/xenapi-config-drive planned to be added in Grizzly] | ||
== Description of features == | == Description of features == | ||
Revision as of 17:09, 7 January 2013
Hypervisor support matrix
This is an attempt to help new users decide on a hypervisor based on features that can be controlled through compute.
Most OpenStack development is done with the KVM and XEN hypervisors. This means that (currently at least) you are more likely to find community support for issues with these hypervisors. All features that are currently supported in KVM are also supported in QEMU.
As far as the Xen hypervisor is concerned, it is worth noting the following definitions:
- XenServer: Commercial, supported product from Citrix.
- Xen Cloud Platform (XCP): Open-source equivalent of XenServer (and the development project for the toolstack). Everything said about XenServer below applies equally to XCP.
- XenAPI: The management API exposed by XenServer and XCP.
- XAPI: The primary daemon on XenServer and Xen Cloud Platform; the one that exposes the XenAPI.
Nova has support for XenServer and XCP through the XenAPI virt layer. Note that this does not imply support for other Xen-based platforms such as those shipped with RHEL 6 or SUSE, which is provided via the libvirt layer.
Please help keep this list up-to-date.
Legend: ✔ indicates support, ✗ indicates the feature is not supported, G indicates the feature will be added in Grizzly, * indicates there is a caveat to the functionality (caveats need to be documented!), and a blank cell generally indicates more testing is needed to make a judgment.
| Feature | XenServer/XCP | KVM | QEMU | LXC | ESXi |
| Launch | ✔ | ✔ | ✔ | ✔ | ✔ |
| Reboot | ✔ | ✔ | ✔ | ✔ | ✔ |
| Terminate | ✔ | ✔ | ✔ | ✔ | ✔ |
| Resize | ✔ | ✔ | ✔ | ✗ | |
| Rescue | ✔ | ✔ | ✔ | ✗ | |
| Pause | ✔ | ✔ | ✔ | ✗ | |
| Un-pause | ✔ | ✔ | ✔ | ✗ | |
| Suspend | ✔ | ✔ | ✔ | ✔ | |
| Resume | ✔ | ✔ | ✔ | ✔ | |
| Inject Networking | ✔*(1)(2) | ✔*(1) | ✔ *(1) | ✔* | |
| Inject File | ✔ | ✔* | ✔* | ||
| Serial Console | ✗ | ✔ | ✔ | ✗ | ✔ |
| VNC Console | ✔* | ✔* | ✔* | ✗ | |
| Attach Volume | ✔ | ✔ | ✔ | ✗ | ✗ |
| Detach Volume | ✔ | ✔ | ✔ | ✗ | ✗ |
| Live Migration | ✔ | ✔ | ✔ | ✗ | |
| Snapshot | ✔ | ✔ | ✔ | ✔ | |
| iSCSI | ✔ | ✔ | |||
| Set Admin Pass | ✔ | ✗ | ✗ | ✗ | |
| Get Guest Info | ✔ | ✔ | ✔ | ||
| Get Host Info | ✔ | ✔ | ✔ | ||
| Glance Integration | ✔ | ✔ | ✔ | ✔ | |
| Service Control | ✔ | ✔ | ✔ | ||
| VLAN Networking | ✔ | ✔ | ✔ | ✔ | ✔ |
| Flat Networking | ✔ | ✔ | ✔ | ✔ | ✔ |
| Security Groups | ✔ | ✔ | ✔ | ✔ | ✗ |
| Firewall Rules | ✔ | ✔ | ✔ | ✗ | |
| Routing | ✔ | ✔ | ✔ | ||
| nova diagnostics | ✔ | ✔ | ✔ | ||
| Config Drive | ✗*(3) | ✔ | ✔ | ✔ | |
| Auto configure disk | ✔ |
- Inject Networking only works with nova-network in Flat mode, and only with Debian/Ubuntu based virtual machines
- XenServer integration also supports using a guest agent to inject networking settings
- XenAPI Config drive support is planned to be added in Grizzly
Description of features
nova diagnostics
The `nova diagnostics` command will provide some information about resource use associated with an instance. See the OpenStack Compute admin guide for more details.
Auto configure disk
Automatically reconfigure the size of the partition to match the size of the flavor's root drive before booting.
