Stein Series Release Notes



Vitrage Stein release contains some significant changes:

  • New and simplified template language! the new templates are shorter and much easier to understand and reuse:

  • Added a Trove datasource and a Zaqar notifier.

  • New APIs for querying Vitrage services and for resource count.

  • Performance improvements and faster data retrieval. The memory signature and processing runtime were significantly reduced.


New Features

  • Datasource end messages previously used to notify the processor that get_all finished successfully. Are no longer used and are removed.

Upgrade Notes

  • Default Cinder API version is changed to v3. It’s fully compatible with API v2. If you need to use Cinder API v2 you need to cinder_version=’2’ in the Vitrage configuration file.

Deprecation Notes

  • Config option initialization_interval is deprecated and no longer used, due to the removal of datasource end messages.

  • Config option initialization_max_retries is deprecated and no longer used, due to the removal of datasource end messages.


New Features

  • Added a new API to list all vitrage services present in the system.

  • A new zaqar notifier was added, in order to send alrmas from Vitrage to zaqar messaging framework.

  • Added support for a yaml configuration file that maps the Prometheus alert labels to a corresponding Vitrage resource with specific properties (id or other unique properties).

  • Added support for get_all alerts from Prometheus Alertmanager.

  • Added support for parameters in Vitrage templates. A template may contain one or more parameters that are assigned with actual values upon template creation. This enables easy reuse of common templates.

  • Introduced template version 3, a shorter, more fluent template language. Overall template yaml appearance improvements. condition definitions were revised, relationships declarations removed.



Added new tool vitrage-status upgrade check.

New Features

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

  • Collector service removal to simplify and enhance scale performance. vitrage-collector service was removed and vitrage-graph is responsible to execute the drivers. Allowing drivers to take advantage of python yield generators and conserve memory.

  • Use Nova versioned notifications instead of the legacy, unversioned ones. This bahavior is controlled by the use_nova_versioned_notifications configuration option.

  • Resource count new API with support for queries and group-by. Allows retrieving quick summaries of graph nodes.

  • Resource list API now supports using a query

  • A new Trove Datasource has been introduced to include Trove entities (database instances and clusters) in Vitrage Entity Graph. Trove is Database as a Service solution offering database lifecycle management (automated provisioning, configuration, backups, clustering etc.). Adding the datasource to Vitrage enables detecting problems at lower levels of infrastructure that may affect functioning of running databases, and react in response to identified issues e.g. scale the database up/out or live-migrate virtual machines from failed compute. This change is the first stage of integration with Trove. At this point, Trove entities are extracted using PULL approach, based on periodical snapshot-query to Trove API for the current list of Trove entities. In the future, PUSH approach based on Trove notifications will be implemented.

Upgrade Notes

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

Deprecation Notes

  • The static_physical datasource was removed. Please use the static datasource instead.

  • Resource list GET is deprecated, use POST instead.