17:00:04 #startmeeting nova notification 17:00:05 Meeting started Tue Jan 10 17:00:04 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:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:08 The meeting name has been set to 'nova_notification' 17:00:28 hi 17:00:58 o/ 17:01:41 let's wait a minute or two for the others 17:01:50 hi 17:03:14 OK, let's get started. 17:03:24 two important things first 17:03:39 1) Tomorrow there will be a code review sprint 17:04:10 so if you have outstanding reviews then it is a good day to ask for a review on IRC 17:04:36 and also try to be in IRC to be able to respond and discuss issues with the reviewers 17:05:57 2) feature freeze is around the corner so it is important to focuse on finishing things 17:06:20 so please focus more on outstanding reviews than for example starting new notification transformation task 17:07:39 after the feature freeze we can still push bug fixes, release notes updates, refactors and test updates 17:08:16 I will do the release note for the notification transformation bp so you don't have to worry about that 17:09:00 all the other bp owner that got content merged needs to add release notes 17:09:14 but as I said we have plenty of time to do that, no worries 17:09:35 OK 17:09:54 anything bp specific to discuss? 17:10:00 anything about flavor notifications? 17:10:48 I take it as a no :) 17:10:52 gibi, I've question on adding auto_disk_config field 17:11:09 sneti_: that is in the additional-notification-fields-for-searchlight, right? 17:11:18 yes 17:11:24 then shoot :) 17:12:05 for searchlight BP as of now only one patch is merged, do we still need to add release notes, if that is the only patch merged before feature freeze? 17:12:51 aunnam: yes, please mention that what field is added and that the related payload version is bumped 17:13:09 aunnam: but as I said this is not have to be done right now, you can propose it after the feature freeze 17:13:37 ok, cool 17:13:41 any update on what to send enum or boolean for auto_disk_config. There is a comment on this: https://bugs.launchpad.net/nova/+bug/1637634 17:13:41 Launchpad bug 1637634 in OpenStack Compute (nova) "Missing fields in compute.end and compute.update notifications" [Undecided,Incomplete] 17:14:16 sneti_: checking... 17:15:54 sneti_: do searchlight needs the AUTO / MANUAL values in that field of the notification? 17:16:20 or it is OK to them to have true / false? 17:17:03 Gibi, they didn't reply for that question, but the api returns AUTO / MANUAL values 17:17:13 gibi, not sure. I've seen any update from them 17:17:56 OK just to be able to go forward with this I suggest to propose the change in the notification with an Enum 17:18:22 and that Enum can coerce the Enum value from a boolean 17:18:42 this way the conversion can be quite automatic when the notification payload is created 17:18:55 based on the instance.auto_disk_config boolean value 17:19:03 ok 17:19:27 anything else regarding the searchlight bp? 17:20:17 I take it as a no :) 17:20:24 I have one 17:20:34 aunnam: OK, just ask :) 17:20:35 Looks like the patch you have https://review.openstack.org/#/c/415857/ is ready now, I have reviewed it. So now can I add keypairs patch on top of this patch? 17:21:15 the lazy loading is handled in your patch by removing that line 17:22:09 aunnam: could you give me a link to your patch? 17:23:06 aunnam: or the patch where we discussed the keypairs lazy-load issue? 17:23:23 I don't have it right now, my question is as keypair is also lazy-loaded you suggested me to wait until the patch you are working on it is ready 17:23:32 yes the same one 17:24:10 aunnam: you can move that top of my bugfix yes 17:24:34 ok, thanks 17:25:02 anything else on the searchlight bp? 17:25:18 nothing from my side 17:25:21 OK 17:25:22 nope 17:26:06 on the json-schema-for-versioned-object bp I think syjulian made some progress and the basic tool is up for review 17:26:32 however we identified some bugs in the schema generation regarding enum values so that needs an ovo fix 17:27:04 as the last ovo lib release for Ocata is next week this might not fitt into Ocata 17:27:47 any questions comments on this bp? 17:28:51 I take it as a no 17:28:51 :) 17:29:06 and last but not least the notification transformation bp 17:29:37 we have quite many patches up waiting for core review so tomorrow I will try to ping the cores :) 17:29:52 any question on the transformation bp? 17:30:40 any question on anything? 17:31:17 if no then let's close the meeting 17:31:21 thanks for joining 17:31:28 bye 17:31:33 bye 17:31:40 #endmeeting