[wishlist] Add config option for live-migration force-completion strategy

Bug #1837884 reported by Drew Freiberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Compute Charm
Triaged
Wishlist
Unassigned

Bug Description

In the openstack documentation for nova live migration, three different strategies for migration completion are provided. The charm should expose this as a variable with the following options:

- pause
- auto-converge
- post-copy

The standard live-migration force completion is to pause the instance while the remaining data is copied, but this can cause havoc for some workloads that rely on time being relatively linear and may be problematic for customers working with regulatory compliance for date-time tracking of transactions.

While this is not a common need, some sites have very large memory segment workloads that require zero downtime and the ability to alter this strategy via standard charm config rather than using config-flags would be quite useful.

https://docs.openstack.org/nova/pike/admin/live-migration-usage.html#addressing-migration-timeouts

description: updated
Changed in charm-nova-compute:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Looks like this is close to the request of lp#1799916 and is part of the charm. the options are:
  live_migration_permit_auto_converge
  live_migration_permit_post_copy

and can be set to true.

These should be mutually exclusive options, and the charm should block if both = True.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.