c2ad4b28da2378b7433f7fe54ada87a278b5e1c3

When only running volume migrations, a zone migration strategy audit without setting compute_nodes should work. Before this change, an audit with defined storage_pools, no compute_nodes parameters, and with_attached_volume is set to True would trigger the migration of the instances attached to the volumes being migrated. This patch decouples instance and volume migrations unless the user explicitely asks for both. When migrating attached volumes, the zone migration strategy will check for which instances should be migrated according to the audit parameters, and if the instance the volume is attached to can be migrated, it will be just after the volume. On the other hand, when the attached instances should not be migrated according to user input, only the volumes will be migrated. In an audit that migrates instnaces but not volumes, the with_attached_volume parameter will continue doing nothing. Closes-Bug: 2111429 Change-Id: If641af77ba368946398f9860c537a639d1053f69 Signed-off-by: jgilaber <jgilaber@redhat.com>
Watcher
OpenStack Watcher provides a flexible and scalable resource optimization service for multi-tenant OpenStack-based clouds. Watcher provides a robust framework to realize a wide range of cloud optimization goals, including the reduction of data center operating costs, increased system performance via intelligent virtual machine migration, increased energy efficiency and more!
- Free software: Apache license
- Wiki: https://wiki.openstack.org/wiki/Watcher
- Source: https://opendev.org/openstack/watcher
- Bugs: https://bugs.launchpad.net/watcher
- Documentation: https://docs.openstack.org/watcher/latest/
- Release notes: https://docs.openstack.org/releasenotes/watcher/
- Design specifications: https://specs.openstack.org/openstack/watcher-specs/
Description
Languages
Python
99.7%
Shell
0.3%