[openstack-dev] [nova] [searchlight] Difference in nova notifications versus API

Tripp, Travis S travis.tripp at hpe.com
Wed Oct 28 16:03:33 UTC 2015

Thank, Gibi!

A key aspect for notifications for Searchlight would be able to have the notification produce the same data that you’d get from the API.  So, with micro versions, it would probably need to be configurable for the notifications emitted on perhaps a certain topic to be able to be emitted according to a specified API version.

Like most summits, there is a timing conflict for me, but at least a couple of us Searchlighters should be able to make that time.


From: Balázs Gibizer <balazs.gibizer at ericsson.com<mailto:balazs.gibizer at ericsson.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, October 28, 2015 at 6:50 PM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [nova] [searchlight] Difference in nova notifications versus API


There is a spec up [3] in nova to version notifications and also there will be a half session [4] tomorrow aftrenoon on the nova track to discuss it.


[3] https://review.openstack.org/#/c/224755/
[4] https://mitakadesignsummit.sched.org/mobile/#session:2bbda0e5e052e5249fa1a118e906df46

Sent from my iPad
On 2015. okt. 28., at 15:10, McLellan, Steven <steve.mclellan at hpe.com<mailto:steve.mclellan at hpe.com>> wrote:


One of our questions this summit for Searchlight is whether we can reduce the time and effort required to index resources by getting as much information from notifications as possible.

Nova's API and notifications provide data in different formats; some information is missing and some is in different formats (1). In addition, notification information isn't versioned and can change at will. Currently we've taken the approach of treating the notification as a sign that something has happened and that we should get current state from the API.

We'd love to be able to process notifications directly, and have some assurance that the format won't change drastically without warning. Michael suggested i start a mailing thread, but we also have a session tomorrow set aside for these kinds of discussions with other projects (2). If anyone's available to join us that would be splendid.

Steve (apologies if this ends up getting sent twice)

(1) For instance, 'accessIPv4' vs 'access_ip_v4', 'name' vs 'displayname'; extension information and some networking info like security groups generally isn't in notifications; notifications return more image information than the API

(2) http://mitakadesignsummit.sched.org/event/1d1ef3b50d8d8607834697f0ef6d70d9#.VjBRWK4rJE4

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe

More information about the OpenStack-dev mailing list