322c89d982
In a recent change [1] we modified the database schema for efficacy indicators to use a 'data' column. However, that patch only contained the schema migration and a fallback to be able to read from older databases, and not any kind of data migration. This change introduces a migration on load, so whenever an efficacy indicator without a 'data' column is loaded, the column is populated in the database. The change also modifies the migration test to verify the procedure works well. [1] https://review.opendev.org/c/openstack/watcher/+/945199 Change-Id: Ib0621b0e03451faca803018d6a2f3ad657a25fb5
=======
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/