17:00:03 #startmeeting nova notification 17:00:04 Meeting started Tue Jun 21 17:00:03 2016 UTC and is due to finish in 60 minutes. The chair is gibi_. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:07 The meeting name has been set to 'nova_notification' 17:00:14 o/ 17:00:28 hi! 17:00:31 hi 17:00:33 hi! 17:01:37 hi 17:01:38 I'm planning a short meeting so let's get started :) 17:01:52 #topic outstanding reviews 17:02:34 some base commits still waiting for core review 17:02:56 wrap_exception, instance.delete, and instance.update is still on the list 17:03:16 I'm hunting the cores to get them in 17:03:24 wrap_exception got eyes from mriedem 17:03:35 rlrossit_: yep, that is close now 17:03:57 I've been a busy bee this last week, so I haven't looked at any recently 17:04:36 rlrossit_: no worries. when you have time we still appreciate your feedback on any of the outstanding review 17:05:02 mostly instance.delete and update are the hard ones 17:05:53 peole made good progress on proposing transformation patches based on instance.delete 17:06:04 I try to review them daily 17:06:12 but most of them already in good shape 17:06:28 waiting for the parent patches to merge 17:06:43 so thank you! good job! 17:08:14 :) 17:08:23 syjulian: where we are with the json schema stuff? 17:08:38 mostly waiting for reviews 17:08:55 should I get some cores to look at it? 17:09:32 syjulian: last time I checked I liked both patches, so from my perspective it can be pushed for the cores 17:09:39 rlrossit_: do you agree? 17:10:28 gibi_: is there a certain core that works with the notification subteam? or should I just contact any? 17:10:54 syjulian: I think you should ask for reviews on the oslo channel 17:11:17 gibi_: yeah, I think I was getting close to good with it 17:11:25 sure thing 17:11:53 rlrossit_: do you know any oslo core that might be interested about checking it? 17:12:10 gibi_: lemme go hunt down the core list quick 17:13:31 the spec was approved by dims 17:13:56 I would maybe tap jaypipes or dansmith to get a nova-side look on the change, and then ask if dims wants to take a look 17:14:14 sounds like a good plan 17:14:26 rlrossit_: thanks 17:15:11 cool 17:15:14 i'll do that 17:15:18 syjulian: thanks 17:15:46 any other review we have to talk about today? 17:17:27 it seems there isn't any 17:17:43 #topic open discussion 17:18:11 I have one thing 17:18:39 this week nova team meeting is in US time zone 17:18:47 which is quite late for me 17:19:22 I got it if you can't make it gibi_ 17:19:23 rlrossit_: could you take that? If not then I will send and update to mridiem before the meeting 17:19:31 beat you to it :) 17:19:44 rlrossit_: thanks a lot! 17:20:49 OK, any other thing to discuss today? 17:20:54 will the subteam meet up during the midcycle? 17:21:03 ohh good comment 17:21:16 unfortunately I cannot make it to the midcycle this time 17:21:27 I will also not be in attendance 17:21:46 I will send a status report to the ML before the midcycle and sync with the cores if needed 17:22:37 are they any different from the design sessions? 17:22:48 it is like the friday meetup 17:22:53 big round table 17:23:04 and discussion based on a giant etherpoad 17:23:15 gotcha 17:23:22 it tends to be a little less structured as well 17:23:30 they have the etherpad, but they can go off in the weeds sometimes 17:24:17 is that something you guys think newbies should go to? 17:25:02 as with every other openstack event... it wouldn't hurt 17:25:24 good source of information but it is the best if you can contribute to the discussion 17:25:28 but the only midcycle I went to was the one in Rochester last summer, and back then I was about 2 weeks into openstack 17:25:57 I guess I went to the Neutron midcycle in Rochester this winter as well, but it was drastically less structured than the nova midcycle 17:27:21 I think if you can then go it is a good experience anyhow 17:28:32 yeah. hopefully some folks from my team can go 17:30:19 anything else we need to discuss? 17:31:40 then let's close the meeting 17:32:06 thanks! 17:32:08 #endmeeting