Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/ceilometer-alarm-level. Description: Currently alarms in ceilometer have no concept of an importance level. This makes it hard from auditing stand point to figure out which alarm is a low priority vs critical. The goal of this blueprint is to incorporate the alarm_level into the alarm object so we can set a criticality. Specification URL (additional information): https://github.com/openstack/ceilometer-specs/blob/master/specs/kilo/ceilometer-alarm-level.rst
Eoghan, could you please review the above test plan and provide your comments? Thank you in advance. Regards, Yurii
Verified according test plan.
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. https://access.redhat.com/errata/RHEA-2015:1548