Ocata Series Release Notes¶
The main focus of Vitrage in the Ocata version was to enhance the integration with external projects, to support more use cases, and to give more value to the user.
Collectd Datasourcewas added, to handle notifications coming from collectd. collectd is a fast system statistics collection daemon, with plugins that collect different metrics. We tested the DPDK plugin, that can trigger alarms such as interface failure or noisy neighbors.
Doctor Datasourcewas added in order to support the OPNFV Doctor Inspector requirements. This datasource handles notifications sent from the Doctor monitor. If a
compute.host.downnotification arrives, the Doctor datasource will create an alarm on the host in Vitrage, call nova force-down API and create deduced alarms on the relevant instances and applications.
Static Datasourceis meant to define in a yaml file cloud resources that cannot be retrieved dynamically. Switches are a good example, as currently no OpenStack project provides information about them. In Newton, only switches could be defined in the static yaml files. In Ocata the file definition was enhanced, so the user can define practically everything. The new schema is subset of the Vitrage evaluator templates schema, to make it easier to use and maintain.
Aodh Datasourceis used to collect alarms from Aodh and pass them to Vitrage, so Vitrage can correlate them with other alarms in the system. In Ocata we added support for receiving immediate notifications on alarm state changes from Aodh. This allows Vitrage to act immediately in case Aodh detects a problem and there is a need to trigger new alarms (e.g. on an application) or modify the states of resources.
static_physicalfile format is deprecated. Please use the new
staticfile format instead.