listen to versioned notifications

Bug #1665449 reported by gordon chung on 2017-02-16
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Hanxi Liu
OpenStack ceilometer charm
gordon chung (chungg) on 2017-02-16
Changed in ceilometer:
status: New → Triaged
importance: Undecided → Wishlist
Jeffrey Zhang (jeffrey4l) wrote :

is ceilometer going to support this? seems there is no consumer for versioned_notfication pushed by nova.

Changed in ceilometer:
status: Triaged → Confirmed
gordon chung (chungg) wrote :

this is the point of this entry. it's a placeholder that anyone can work on.

Changed in ceilometer:
status: Confirmed → Triaged
Dmitrii Shcherbakov (dmitriis) wrote :

I can confirm the problem:

rabbitmqctl list_queues -p openstack | grep 0 62

I think that for a given deployment this can be configured to a certain extent via "topics" option in oslo.messaging, however, there are caveats.
"By default, the ceilometer.conf file is as follows::
   topics = notifications"

Also, it is possible to control which types of notifications are emitted on the nova side (unversioned, versioned, both):

event_definitions.yaml on the ceilometer side will need to be written to properly handle versioned events as they seem to have different field names:

Hanxi Liu (hanxi-liu) on 2017-12-15
Changed in ceilometer:
assignee: nobody → Hanxi Liu (hanxi-liu)
James Page (james-page) on 2017-12-19
Changed in charm-ceilometer:
status: New → Triaged
importance: Undecided → Wishlist
Hanxi Liu (hanxi-liu) wrote :

thanks gordc for this track in ML.

Hanxi Liu (hanxi-liu) wrote :

this track the versioned notification transformation task of all projects:
see the part: 'Convert from legacy to versioned notifications'

Xav Paice (xavpaice) wrote :

Just deployed a fresh cloud with charms 18.02, Ceilometer and Gnocchi. Nothing is listening to and so the queue keeps growing.

Also see LP: #1659943 for a similar issue with

tags: added: canonical-bootstack
Balazs Gibizer (balazs-gibizer) wrote :

If the deployment only consumes nova legacy notifications then I suggest to set notification_format to 'legacy' in the nova.conf [1]. This will make sure nova only emits the legacy notifications and not the new versioned ones.


Matt Riedemann (mriedem) wrote :

Correction for comment 8, there is no notification_format value of "legacy", I think gibi meant "unversioned".

Matt is correct in #9

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers