Merge "List support for force-completing a live migration in Feature support matrix"
This commit is contained in:
commit
0f103797e9
@ -269,6 +269,37 @@ driver-impl-ironic=missing
|
||||
driver-impl-libvirt-vz-vm=missing
|
||||
driver-impl-libvirt-vz-ct=missing
|
||||
|
||||
[operation.force-live-migration-to-complete]
|
||||
title=Force live migration to complete
|
||||
status=optional
|
||||
notes=Live migration provides a way to move a running instance to another
|
||||
compute host. But it can sometimes fail to complete if an instance has
|
||||
a high rate of memory or disk page access.
|
||||
This operation provides the user with an option to assist the progress
|
||||
of the live migration. The mechanism used to complete the live
|
||||
migration depends on the underlying virtualization subsystem
|
||||
capabilities. If libvirt/qemu is used and the post-copy feature is
|
||||
available and enabled then the force complete operation will cause
|
||||
a switch to post-copy mode. Otherwise the instance will be suspended
|
||||
until the migration is completed or aborted.
|
||||
cli=nova live-migration-force-complete <server> <migration>
|
||||
driver-impl-xenserver=missing
|
||||
driver-impl-libvirt-kvm-x86=complete
|
||||
driver-notes-libvirt-kvm-x86=Requires libvirt>=1.3.3, qemu>=2.5.0
|
||||
driver-impl-libvirt-kvm-ppc64=complete
|
||||
driver-notes-libvirt-kvm-ppc64=Requires libvirt>=1.3.3, qemu>=2.5.0
|
||||
driver-impl-libvirt-kvm-s390x=complete
|
||||
driver-notes-libvirt-kvm-s390x=Requires libvirt>=1.3.3, qemu>=2.5.0
|
||||
driver-impl-libvirt-qemu-x86=complete
|
||||
driver-notes-libvirt-qemu-x86=Requires libvirt>=1.3.3, qemu>=2.5.0
|
||||
driver-impl-libvirt-lxc=missing
|
||||
driver-impl-libvirt-xen=missing
|
||||
driver-impl-vmware=missing
|
||||
driver-impl-hyperv=missing
|
||||
driver-impl-ironic=missing
|
||||
driver-impl-libvirt-vz-vm=missing
|
||||
driver-impl-libvirt-vz-ct=missing
|
||||
|
||||
[operation.launch]
|
||||
title=Launch instance
|
||||
status=mandatory
|
||||
|
Loading…
Reference in New Issue
Block a user