Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1258888 - [RFE] Allow notification handling to be described in a declarative fashion
[RFE] Allow notification handling to be described in a declarative fashion
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ceilometer (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
medium Severity high
: beta
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
Yurii Prokulevych
upstream_milestone_liberty-3 upstream...
: FutureFeature, OtherQA
: 1258887 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2015-09-01 09:08 EDT by Eoghan Glynn
Modified: 2016-04-07 17:05 EDT (History)
5 users (show)

See Also:
Fixed In Version: openstack-ceilometer-5.0.0-1.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-04-07 17:05:54 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0603 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-07 20:53:53 EDT

  None (edit)
Description Eoghan Glynn 2015-09-01 09:08:14 EDT
Consuming new notifications, or selecting specific topics/exchanges, should not require explicit python code additions as it does currently in ceilometer.

Instead all this should be driven from a single source of configuration in an easily readable format such as YAML.

To facilitate ease of upgrades, if the configuration file is missing, we should fallback to the out-of-the-box defaults in-code.
Comment 3 Yurii Prokulevych 2015-09-04 07:32:22 EDT
*** Bug 1258887 has been marked as a duplicate of this bug. ***
Comment 4 Pradeep Kilambi 2015-09-09 13:33:12 EDT
The goal of this feature is to be able to define meters as part of a declarative yaml file without having to write notification handlers. Things to verify:

* Installation. Make sure the yaml file is deployed and accessible under /etc/ceilometer/meter.yaml and fallsback to ceilometer/meter/data/meter.yaml.

* Verify multi meter notifications

* Verify definitions which involve volume computation having an expression

* Verify definitions with combination strings 

* Validate error handling:
  - syntax handling
  - required fields in yaml (name, event_type, volume, type)
  - missing config
  - duplicate entries
  - types of meters

* By default, event meters with volume =1 are disabled, to enable these set store_notifications enabled and verify volume=1 meters and vice-versa.

* exchange control shouldnt change much.. just moved it to a central location

*  Overall we need to make sure the default meters in meters.yaml are generating samples as expected.

Please let me know if you need any clarification.
Comment 6 Yurii Prokulevych 2016-02-24 08:21:51 EST
Verified according test plan in ceilometer*-5.0.2-2.el7ost.noarch
Comment 8 errata-xmlrpc 2016-04-07 17:05:54 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.