Re: [openstack-dev] [neutron] [searchlight] What do we need in notification payload?

2016-08-03 Thread Hirofumi Ichihara
Thank you for your quick reply. On 2016/08/01 23:31, McLellan, Steven wrote: In our (Searchlight's) ideal world, every notification about a resource would contain the full representation of that resource (for instance, equivalent to the API response for a resource), because it means that each

Re: [openstack-dev] [neutron] [searchlight] What do we need in notification payload?

2016-08-01 Thread McLellan, Steven
In our (Searchlight's) ideal world, every notification about a resource would contain the full representation of that resource (for instance, equivalent to the API response for a resource), because it means that each notification on its own can be treated as the current state at that time without

[openstack-dev] [neutron] [searchlight] What do we need in notification payload?

2016-08-01 Thread Hirofumi Ichihara
Hi, I'm trying to solve a issue[1, 2] which doesn't send a notification when Tag is updated. I'm worried about the payload. My solution just outputs added tag, resource type, and resource id as payload. However, there was a comment which mentioned the payload should have more information.