7489126d83
The [nova_client]/api_version defaults to 2.56 since change Idd6ebc94f81ad5d65256c80885f2addc1aaeaae1. There is compatibility code for that change but if 2.56 is not available watcher_non_live_migrate_instance will still fail if a destination host is used. Since 2.56 has been available since the Queens version of nova it should be reasonable to require at least that version of nova is running for using Watcher. This adds code which enforces the minimum version along with a release note and "watcher-status upgrade check" check method. Note that it's kind of weird for watcher to have a config option like nova_client.api_version since compute API microversions are per API request even though novaclient is constructed with the single configured version. It should really be something the client (watcher in this case) determines using version discovery and gracefully enables features if the required nova API version is available, but that's a bigger change. Change-Id: Id34938c7bb8a5ca934d997e52cac3b365414c006
9 lines
272 B
YAML
9 lines
272 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The minimum required version of the ``[nova_client]/api_version`` value
|
|
is now enforced to be ``2.56`` which is available since the Queens version
|
|
of the nova compute service.
|
|
|
|
A ``watcher-status upgrade check`` has been added for this.
|