Current Series Release Notes

14.0.0-22

New Features

  • A new module, watcher.wsgi, has been added as a place to gather WSGI application objects. This is intended to ease deployment by providing a consistent location for these objects. For example, if using uWSGI then instead of:

    [uwsgi]
 wsgi-file = /bin/watcher-api-wsgi

    You can now use:

    [uwsgi]
module = watcher.wsgi.api:application

    This also simplifies deployment with other WSGI servers that expect module paths such as gunicorn.

Upgrade Notes

  • The default value of [keystone_client] interface has been changed from admin to public.

Deprecation Notes

  • The watcher-api-wsgi console script is deprecated for removal in a future release. This artifact is generated using a setup-tools extension that is provide by PBR which is also deprecated. due to the changes in python packaging this custom extensions is planned to be removed form all OpenStack projects in a future PBR release in favor of module based wsgi applications entry points.

  • Noisy Neighbor strategy is deprecated and will be removed in a future release. This strategy relies on Last Level Cache metrics that are not available in Nova since Victoria release.

Bug Fixes

  • When using prometheus datasource and more that one target has the same value for the fqdn_label, the driver used the wrong instance label to query for host metrics. The instance label is no longer used in the queries but the fqdn_label which identifies all the metrics for a specific compute node. see Bug 2103451: https://bugs.launchpad.net/watcher/+bug/2103451 for more info.

  • When trying to do volume migration using the zone migration strategy, the keystone service is reached, by default through the admin endpoint. The default value of [keystone_client] interface has been fixed. see Bug https://bugs.launchpad.net/watcher/+bug/2109494 for more info.

  • Host maintenance strategy should migrate servers based on backup node if specified or rely on nova scheduler. It was enabling disabled hosts with watcher_disabled reason and migrating servers to those nodes. It can impact customer workload. Compute nodes were disabled for a reason.

    Host maintenance strategy is fixed now to support migrating servers only on backup node or rely on nova scheduler if no backup node is provided.