296856101f
Currently, when an audit with strategy zone_migration has added at least one volume_migration action, it will not process the instances migrations according to the definition of the `compute_nodes` parameter. This behavior is unexpected according to the documentation of the strategy. This patch is fixing that behavior and making sure that not duplicated actions are added to the solution, to handle the case where instances migration actions are created when analyzing the volumes if the `with_attached_volume` parameter is enabled. The patch is also removing the method `instances_no_attached` which is not longer used. Finally, it's adding some unit tests for the new method and fixing the ones to cover the mixed instances and volumes migration situation. Closes-Bug: #2109722 Change-Id: Ief7386ab448c2711d0d8a94a77fa9ba189c8b7d2 Signed-off-by: jgilaber <jgilaber@redhat.com>
=======
Watcher
=======
.. image:: https://governance.openstack.org/tc/badges/watcher.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
..
Except where otherwise noted, this document is licensed under Creative
Commons Attribution 3.0 License. You can view the license at:
https://creativecommons.org/licenses/by/3.0/
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/