Merge "Add support matrix for Delete (Abort) on-going live migration"

api-ref/source/server-migrations.inc

@@ -195,9 +195,11 @@ Abort an in-progress live migration.
 .. note:: With microversion 2.65 or greater, you can abort live migrations
     also in ``queued`` and ``preparing`` status.
 
-.. note:: Not all compute back ends support aborting an in-progress live
+.. note:: Not all `compute back ends`__ support aborting an in-progress live
     migration.
 
+.. __: https://docs.openstack.org/nova/latest/user/support-matrix.html#operation_abort_in_progress_live_migration
+
 Policy defaults enable only users with the administrative role to perform
 this operation. Cloud providers can change these permissions through the
 ``policy.json`` file.

doc/source/user/support-matrix.ini

@@ -510,6 +510,37 @@ driver.libvirt-vz-ct=missing
 driver.powervm=missing
 driver.zvm=missing
 
+[operation.abort-in-progress-live-migration]
+title=Abort an in-progress or queued live migration
+status=optional
+notes=Live migration provides a way to move a running instance to another
+  compute host. But it can sometimes need a large amount of time to complete
+  if an instance has a high rate of memory or disk page access or is stuck in
+  queued status if there are too many in-progress live migration jobs in the
+  queue.
+  This operation provides the user with an option to abort in-progress live
+  migrations.
+  When the live migration job is still in "queued" or "preparing" status,
+  it can be aborted regardless of the type of underneath hypervisor, but once
+  the job status changes to "running", only some of the hypervisors support
+  this feature.
+cli=nova live-migration-abort <server> <migration>
+driver.xenserver=missing
+driver.libvirt-kvm-x86=complete
+driver.libvirt-kvm-aarch64=missing
+driver.libvirt-kvm-ppc64=complete
+driver.libvirt-kvm-s390x=complete
+driver.libvirt-qemu-x86=complete
+driver.libvirt-lxc=missing
+driver.libvirt-xen=complete
+driver.vmware=missing
+driver.hyperv=missing
+driver.ironic=missing
+driver.libvirt-vz-vm=unknown
+driver.libvirt-vz-ct=unknown
+driver.powervm=missing
+driver.zvm=missing
+
 [operation.launch]
 title=Launch instance
 status=mandatory