17:00:11 <gibi> #startmeeting nova notification
17:00:12 <openstack> Meeting started Tue Jul 25 17:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:16 <openstack> The meeting name has been set to 'nova_notification'
17:00:45 <gibi> hi
17:03:13 <mriedem> oops
17:03:16 <mriedem> i am hither
17:03:47 <gibi> mriedem: no worries
17:03:48 <gibi> this week I was late with a whole day with my status mail
17:04:22 <gibi> let's start with the update_at bugs
17:05:04 <gibi> I think the original bugfix on the notification side looks good
17:05:04 <gibi> https://review.openstack.org/#/c/475276/
17:05:06 <mriedem> that one needs to be rebased
17:05:29 <gibi> ohh great
17:05:34 <gibi> I will do that still today
17:06:14 <gibi> are you happy with my analysis on the subsequent bug https://bugs.launchpad.net/nova/+bug/1704928
17:06:14 <openstack> Launchpad bug 1704928 in OpenStack Compute (nova) "updated_at field is set on the instance only after it is scheduled" [Undecided,In progress] - Assigned to Balazs Gibizer (balazs-gibizer)
17:06:41 <gibi> I mean is the current analysis enough to land the original notification bugfix?
17:07:13 <mriedem> yeah i think so, it's an issue in how instance_update_and_get_original works
17:07:14 <gibi> I think I proved that it is not notification related
17:07:20 <gibi> yeah
17:07:21 <mriedem> as it returns a stale copy (the original)
17:07:57 <gibi> yes, it is sort of partiall stale
17:07:57 <gibi> partially
17:08:02 <gibi> moving on
17:08:30 <gibi> thanks for the +A on the publisher_id bug https://bugs.launchpad.net/nova/+bug/1702667
17:08:30 <openstack> Launchpad bug 1702667 in OpenStack Compute (nova) "publisher_id of the versioned instance.update notification is not consistent with other notifications" [Low,Fix released] - Assigned to Balazs Gibizer (balazs-gibizer)
17:08:30 <gibi> there is subsequent patches top of that fix
17:09:03 <gibi> #link https://review.openstack.org/#/c/487126/ and #link https://review.openstack.org/#/c/476538/
17:09:26 <gibi> both connected to the bug #link https://bugs.launchpad.net/nova/+bug/1696152
17:09:26 <openstack> Launchpad bug 1696152 in OpenStack Compute (nova) "nova notifications use nova-api as binary name instead of nova-osapi_compute" [Low,In progress] - Assigned to Balazs Gibizer (balazs-gibizer)
17:10:05 <gibi> is it feel relevant for the Pike release or let this overflow to Queens?
17:11:09 <mriedem> i don't think we need that for pike
17:13:20 <gibi> this is basicly the replacement of the service binary names with enum values
17:13:20 <gibi> in the notification code path
17:13:37 <gibi> OK
17:13:53 <gibi> moving on
17:14:02 <gibi> thanks for closing the searchlight bp
17:14:25 <mriedem> np
17:14:41 <gibi> I will propose a new one for queens to have the follow up patches covered
17:15:05 <gibi> the BDM optimization and the 'status' field addition
17:15:28 <mriedem> ok
17:16:16 <gibi> and last but no least I just saw your comment on the assertJsonEqual improvement patch
17:16:30 <gibi> I will provide the data tomorrow
17:17:12 <gibi> ah I just realized I have one more item
17:17:44 <gibi> I think we can soon close the notification-transformation bp for pike as well
17:18:22 <gibi> there is only one patch with core review there https://review.openstack.org/#/c/486537/
17:18:34 <gibi> that still has a chance
17:18:59 <mriedem> ok
17:19:08 <gibi> that was all from my side
17:19:15 <gibi> do you have anything else to discuss?
17:19:27 <mriedem> nope, i'll leave a tab open for that one that sylvain was +2 on
17:19:42 <gibi> thanks!
17:19:46 <gibi> and thanks for the meeting
17:19:56 <gibi> #endmeeting