Jump to: navigation, search

Difference between revisions of "HypervisorSupportMatrix/Requirements"

(Created page with "{|border="1" cellpadding="2" cellspacing="0" |Feature |Required |Why |- |Launch |Yes |'Cause |- |Reboot |Yes |'Cause |- |Terminate |Yes |'Cause |- |Resize |Yes |'Cause |- |Res...")
 
Line 6: Line 6:
 
|Launch
 
|Launch
 
|Yes
 
|Yes
|'Cause
+
|We don't import running guests, which makes this critical
 
|-
 
|-
 
|Reboot
 
|Reboot
 
|Yes
 
|Yes
|'Cause
+
|It's a pretty core operation that should be supportable everywhere
 
|-
 
|-
 
|Terminate
 
|Terminate
Line 18: Line 18:
 
|Resize
 
|Resize
 
|Yes
 
|Yes
|'Cause
+
|When billed by the minute, ability to shrink/grow is important
 
|-
 
|-
 
|Rescue
 
|Rescue
 
|Yes
 
|Yes
|'Cause
+
|Seems like important user-facing ability
 
|-
 
|-
 
|Pause/Unpause
 
|Pause/Unpause
 
|No
 
|No
|'Cause
+
|Some hypervisors don't support this
 
|-
 
|-
 
|Suspend/Resume
 
|Suspend/Resume
 
|No
 
|No
|'Cause
+
|Some hypervisors don't support this
 
|-
 
|-
 
|Inject networking
 
|Inject networking
 
|No
 
|No
|'Cause
+
|Doesn't make sense everywhere (?)
 
|-
 
|-
 
|Inject files
 
|Inject files
 
|No
 
|No
|'Cause
+
|Trying to move away from this anyway
 
|-
 
|-
 
|Serial Console
 
|Serial Console
 
|No
 
|No
|'Cause
+
|Doesn't make sense everywhere
 
|-
 
|-
 
|VNC Console
 
|VNC Console
 
|No
 
|No
|'Cause
+
|Doesn't make sense everywhere
 
|-
 
|-
 
|SPICE Console
 
|SPICE Console
 
|No
 
|No
|'Cause
+
|Limited to single-hypervisor support
 
|-
 
|-
 
|RDP Console
 
|RDP Console
 
|No
 
|No
|'Cause
+
|Limited to single-hypervisor support
 
|-
 
|-
 
|Attach/Detach Volume
 
|Attach/Detach Volume
|No
+
|Yes
|'Cause
+
|Volumes are the default persistence mechanism
 
|-
 
|-
 
|Live Migration
 
|Live Migration
 
|No
 
|No
|'Cause
+
|Not all hypervisors will support this
 
|-
 
|-
 
|Snapshot
 
|Snapshot
|No
+
|Yes
|'Cause
+
|Basic function for bootstrapping environments
 
|-
 
|-
 
|iSCSI backing
 
|iSCSI backing
 
|No
 
|No
|'Cause
+
|
 
|-
 
|-
 
|FibreChannel Backing
 
|FibreChannel Backing
 
|No
 
|No
|'Cause
+
|
 
|-
 
|-
 
|Set admin password
 
|Set admin password
 
|No
 
|No
|'Cause
+
|Overlaps with rescue, not supported everywhere
 
|-
 
|-
 
|Boot from glance image
 
|Boot from glance image
 
|Yes
 
|Yes
|'Cause
+
|This is basic expected behavior
 
|-
 
|-
 
|Boot from volume
 
|Boot from volume
|No
+
|Yes
|'Cause
+
|If volumes work, this should work too
 
|-
 
|-
 
|Works with nova-network
 
|Works with nova-network
 
|No
 
|No
|'Cause
+
|The (distant) future is neutron
 
|-
 
|-
 
|Works with neutron
 
|Works with neutron
|No
+
|Yes
|'Cause
+
|Neutron is openstack's networking platform, so must be supported
 
|-
 
|-
 
|Supports configdrive
 
|Supports configdrive
 
|Yes
 
|Yes
|'Cause
+
|This is our preferred future file-based configuration mechanism
 
|-
 
|-
 
|Evacuate
 
|Evacuate
 
|No
 
|No
|'Cause
+
|
 
|-
 
|-
 
|Volume Swap
 
|Volume Swap
 
|No
 
|No
|'Cause
+
|Not supported everywhere
 
|}
 
|}

Revision as of 15:39, 11 July 2014

Feature Required Why
Launch Yes We don't import running guests, which makes this critical
Reboot Yes It's a pretty core operation that should be supportable everywhere
Terminate Yes 'Cause
Resize Yes When billed by the minute, ability to shrink/grow is important
Rescue Yes Seems like important user-facing ability
Pause/Unpause No Some hypervisors don't support this
Suspend/Resume No Some hypervisors don't support this
Inject networking No Doesn't make sense everywhere (?)
Inject files No Trying to move away from this anyway
Serial Console No Doesn't make sense everywhere
VNC Console No Doesn't make sense everywhere
SPICE Console No Limited to single-hypervisor support
RDP Console No Limited to single-hypervisor support
Attach/Detach Volume Yes Volumes are the default persistence mechanism
Live Migration No Not all hypervisors will support this
Snapshot Yes Basic function for bootstrapping environments
iSCSI backing No
FibreChannel Backing No
Set admin password No Overlaps with rescue, not supported everywhere
Boot from glance image Yes This is basic expected behavior
Boot from volume Yes If volumes work, this should work too
Works with nova-network No The (distant) future is neutron
Works with neutron Yes Neutron is openstack's networking platform, so must be supported
Supports configdrive Yes This is our preferred future file-based configuration mechanism
Evacuate No
Volume Swap No Not supported everywhere