Files
watcher/releasenotes/notes/host-maintenance-strategy-disable-migration-options-a2b72e32736e5446.yaml
Quang Ngo cc26b3b334 Add options to disable migration in host maintenance
This change enhances the Host Maintenance strategy by introducing
two new input parameters: `disable_live_migration` and
`disable_cold_migration`. These parameters allow cloud
administrators to control whether live or cold migration should be
considered during host maintenance operations.

If `disable_live_migration` is set, active instances will be cold
migrated if `disable_cold_migration` is not set, otherwise
active instances will be stopped. If `disable_cold_migration` is set,
inactive instances will not be cold migrated.
If both are set, only stop actions will be performed on instances.

The strategy logic and action plan generation have been updated to
reflect these behaviors. A new "stop" action is introduced and
registered, and the weight planner is updated to handle new action.

Documentation for the Host Maintenance strategy is updated to
describe the new parameters and their effects.

Test Plan:
- Unit tests for HostMaintenance strategy with new parameters
- Integration tests for action plan generation with stop action

This implements the specification:
Spec: https://review.opendev.org/c/openstack/watcher-specs/+/943873

Change-Id: I201b8e5c52e1bc1a74f3886a0e301e3c0fa5d351
Signed-off-by: Quang Ngo <quang.ngo@canonical.com>
2025-08-20 22:32:33 +10:00

18 lines
781 B
YAML

---
features:
- |
The Host Maintenance strategy now supports two new input parameters:
``disable_live_migration`` and ``disable_cold_migration``. These
parameters allow cloud administrators to control whether live, cold or
no migration should be considered during host maintenance operations.
* If ``disable_live_migration`` is set, active instances will be cold
migrated if ``disable_cold_migration`` is not set, otherwise active
instances will be stopped.
* If ``disable_cold_migration`` is set, inactive instances will not be
cold migrated.
* If both are set, only stop actions will be applied on active instances.
A new `stop` action has been introduced and registered to support
scenarios where migration is disabled.