post-copy and auto-converge are mutually exclusive
Bug #1877470 reported by
Andrea Ieri
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
live_migration_
I think the charm should go in a blocked state if both are set to true, because although it is a valid configuration, the resulting behavior is not obvious, and has bitten us several times in the past.
Changed in charm-nova-compute: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
On second thought, I have a better suggestion: since live_migration_ permit_ post_copy and live_migration_ permit_ auto_converge effectively implement a three-way switch, it would be more idiomatic to deprecate them in favor of a new setting. For example:
live- migration- force-strategy: permit- post-copy and migration- permit- auto-converge options are unset migration- permit- post-copy: force-strategy instead migration- permit- auto-converge: force-strategy instead
type: string
default: stop
description: |
Selects which strategy will be used when migrations are force-completed.
Valid options: stop, post-copy, auto-converge
Only used if the deprecated live-migration-
live-
live-
type: boolean
default: False
description: |
DEPRECATED: use live-migration-
If live-migration is enabled, this option allows Nova to switch an on-
going live migration to post-copy mode.
live-
type: boolean
default: False
description: |
DEPRECATED: use live-migration-
If live-migration is enabled, this option allows Nova to throttle down
CPU when an on-going live migration is slow.
WARNING: auto-converge will only be used if post-copy is disabled