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.
*** Bug 1258887 has been marked as a duplicate of this bug. ***
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.
Verified according test plan in ceilometer*-5.0.2-2.el7ost.noarch
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.