Victoria Series Release Notes

10.0.0

New Features

• The admin user can fetch alarms of all the projects, e.g. curl -X GET "${aodh_prefix}/v2/alarms?q.field=all_projects&q.op=eq&q.value=true" X-Auth-Token:$token

• Support to deploy aodh-evaluator in active/active mode by leveraging database non-locking mechanism. With this feature, there could be multiple aodh-evaluator processes running without dependency of etcd or zookeeper.

• Aodh Quota API is aiming for multi-tenancy support. By default, only the admin user is able to change or delete the resource quota for projects as defined by the default policy rule ‘telemetry:update_quotas’ and ‘telemetry:delete_quotas’. User alarm quota and alarm action quota are not supported in Quota API.

Upgrade Notes

• Python 2.7 support has been dropped. Last release of Aodh to support py2.7 is OpenStack Train. The minimum version of Python now supported by Aodh is Python 3.6.

9.0.0

Prelude

Added new tool aodh-status upgrade check.

New Features

• New framework for aodh-status upgrade check command is added. This framework allows adding various checks which can be run before a Aodh upgrade to ensure if the upgrade can be performed safely.

• Added a new notifier(trust+heat) that works together with loadbalancer_member_health evaluator for auto-healing purpose.

• Added a new evaluator for the alarms of type loadbalancer_member_health which evaluates the alarm by checking the operating status of the members in a given load balancer pool.

Upgrade Notes

• Operator can now use new CLI tool aodh-status upgrade check to check if Aodh deployment can be safely upgraded from N-1 to N release.

6.0.0

New Features

• Aodh now support policy in code, which means if users didn’t modify any of policy rules, they can leave policy file (in json or yaml format) empty or not deploy it at all. Because from now, Aodh keeps all default policies under aodh/api/policies module. Users can still modify/generate policy.yaml file which will override policy rules in code if those rules show in policy.yaml file.

Deprecation Notes

• The deprecated ‘threshold’ alarm type has been removed.

Other Notes

• Default policy.json file is now removed as Aodh now generate the default policies from code. Please be aware that when using that file in your environment.

5.0.0

New Features

• The reason of the state change is now part of the API as “state_reason” field of the alarm object.

Deprecation Notes

• Ceilometer’s API is deprecated in Ocata. Therefore, threshold alarms are now deprecated as well. Threshold rules will be removed when Ceilometer’s API is also removed. Similar functionality is provided through Gnocchi alarm rules: gnocchi_resources_threshold, gnocchi_aggregation_by_metrics_threshold, or gnocchi_aggregation_by_resources_threshold.

• The deprecated combination alarms support have been removed.

Bug Fixes

• When an unprivileged user want to access to Gnocchi resources created by Ceilometer, that doesn’t work because the filter scope the Gnocchi query to resource owner to the user. To fix we introduce a new configuration option “gnocchi_external_project_owner” set by default to “service”. The new filter now allow two kind of Gnocchi resources:

  • owned by the user project

  • owned by “gnocchi_external_project_owner” and the original project_id of the resource is the user project.

4.0.0

New Features

• A healthcheck endpoint is provided by default at /healthcheck. It leverages oslo_middleware healthcheck middleware. It allows to retrieve information about the health of the API service.

Upgrade Notes

• The api.pecan_debug option has been removed.

• All the deprecated non-SQL drivers have been removed.

Other Notes

• Gnocchi aggregation capabilities are now cached to minimise redundant calls to Gnocchi when validating aggregation methods. The cache is stored in-memory for an hour. If additional aggregations are added to Gnocchi, they will not be proprogated to Aodh’s API service for at most an hour or unless the service is restarted.

• Aodh now leverages microseconds timestamps available since MySQL 5.6.4, meaning it is now the minimum required version of MySQL.

3.0.0

New Features

• Enable aodh services, including aodh-evaluator, aodh-listener and aodh-notifier to run in multiple worker mode. New options are introduced corresponsively as [evaluator]workers, [listener]workers and [notifier]workers. They all default to 1.

• Add support for batch processing of messages from queue. This will allow the aodh-listener to grab multiple event messages per thread to enable more efficient processing.

• A new option “rest_notifier_ca_bundle_certificate_path” has been added in the configuration file, set None as default value. If this option is present and SSL is used for alarm action the certificate path provided will be used as value of verify parameter in action request.

• Allow to extends the alarm evaluation windows to compensate the reporting/ingestion lag. An new option is introduced additional_ingestion_lag defaulted to 0. It represents the number of seconds of the window extension.

• Add support for batch processing of messages from queue. This will allow the aodh-notifier to grab multiple messages per thread to enable more efficient processing.

Upgrade Notes

• Add a tool for migrating alarm and alarm history data from NoSQL storage to SQL storage. The migration tool has been tested OK in devstack environment, but users need to be cautious with this, because the data migration between storage backends is a bit dangerous.

• batch_size and batch_timeout configuration options are added to [listener] section of configuration. The batch_size controls the number of messages to grab before processing. Similarly, the batch_timeout defines the wait time before processing.

• batch_size and batch_timeout configuration options are added to [notifier] section of configuration. The batch_size controls the number of messages to grab before processing. Similarly, the batch_timeout defines the wait time before processing.

• Add a tool for converting combination alarms to composite alarms, since we have deprecated the combination alarm support and recommend to use composite alarm to perform multiple conditions alarming.

Deprecation Notes

• The combination alarms are officially deprecated and disabled by default. Set api.enable_combination_alarms to True to enable them. Existing alarms will still be evaluated, but access to them via the API is linked to whether that configuration option is turned on or off. It’s advised to use composite alarms instead.

Bug Fixes

• [bug 1582131] Fix an issue with adding CA_BUNDLE certificate parth as value of “verify” parameter in SSL requests.

• [bug 1575530] Patch was added to fix and improve the partition coordinator, make sure the input tasks can be correctly distributed to partition members.

Other Notes

• Alarm name unique constraint for each project has been removed.

2.0.0

New Features

• Add a new composite type alarm, which allow users specifying a composite rule to define an alarm with multiple triggering conditions, using a combination of and, or relationships. The composite rule is composed of multiple threshold rules or gnocchi rules.

• Gnocchi dispatcher now uses client rather than direct http requests

• Add support for Keystone v3 authentication

• Support for queue based communication between alarm evaluator service and alarm notifier services was added. Original implementation involved using RPC but there is significant overhead involved with using RPC. Work queues provided required functionality with better performance.

• Remove eventlet from Aodh in favour of threaded approach

Upgrade Notes

• A new default policy.json is provided to properly handle RBAC control. Existing policy.json files may not grant the appropriate access.

• gnocchiclient library is now a requirement if using ceilometer+gnocchi.

• Queue based communication is the new default IPC protocol. RPC can still be used by choosing rpc as ipc_protocol option. Only one protocol can be run at any given time.

Deprecation Notes

• Drop support for NoSQL backends in Aodh. SQL is a prefectly sufficient backend for handling the scope of alarms. To maximise available resources, NoSQL backends are deprecated so developers do not need to worry about adding features to multiple backends.

• Because queues provide the equivalent functionality. RPC support is deprecated and will be removed after Mitaka.

Security Issues

• Patch was added to address inconsistent RBAC policy handling. Certain rules may not have been given appropriate access.

Bug Fixes

• [bug 1540395] Fix reason string to properly handle transitions when one sample is outside of defined threshold.

• [bug 1518447] Fix to ensure ceilometerclient is properly initialised on startup.

• [bug 1511252] Fix an issue with combination alarms where it fails to evaluate all issues in the chain of alarms.

• [bug 1539069] Fix to handle scenario where no valid statistics exist for specified period.

• [bug 1513738] Fix an issue where alarms using Gnocchi aggregations are not being evaluated.

• [bug 1504495] Patch was added to address inconsistent RBAC policy handling. Certain rules may not have been given appropriate access.