listen to versioned notifications

[gordon chung]

https://docs.openstack.org/developer/nova/notifications.html#existing-versioned-notifications

[Jeffrey Zhang (jeffrey4l)]

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

[gordon chung (chungg)]

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

[Dmitrii Shcherbakov (dmitriis)]

I can confirm the problem:

rabbitmqctl list_queues -p openstack | grep notifications.info
notifications.info 0
versioned_notifications.info 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.

https://github.com/openstack/oslo.messaging/blob/stable/pike/oslo_messaging/notify/notifier.py#L48-L55

https://github.com/openstack/ceilometer/blame/stable/pike/doc/source/contributor/install/custom.rst#L39-L60
"By default, the ceilometer.conf file is as follows::
   [oslo_messaging_notifications]
   topics = notifications"

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

https://github.com/openstack/nova/blob/stable/pike/nova/conf/notifications.py#L88-L105

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:

https://github.com/openstack/ceilometer/blob/stable/pike/ceilometer/pipeline/data/event_definitions.yaml

[gordon chung (chungg)]

we can track coverage here: http://burndown.peermore.com/nova-notification/

http://lists.openstack.org/pipermail/openstack-dev/2018-January/126736.html

[Hanxi Liu (hanxi-liu)]

thanks gordc for this track in ML.

[Hanxi Liu (hanxi-liu)]

this track the versioned notification transformation task of all projects: https://etherpad.openstack.org/p/community-goals
see the part: 'Convert from legacy to versioned notifications'

[Xav Paice (xavpaice)]

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

Also see LP: #1659943 for a similar issue with notifications_designate.info

[Balazs Gibizer (balazs-gibizer)]

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.

[1] https://docs.openstack.org/nova/latest/configuration/sample-config.html

[Matt Riedemann (mriedem)]

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

[Balazs Gibizer (balazs-gibizer)]

Matt is correct in #9