20:00:13 #startmeeting nova notification 20:00:14 Meeting started Tue Dec 1 20:00:13 2015 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:18 The meeting name has been set to 'nova_notification' 20:00:27 hi! 20:00:38 hi gibi! 20:00:45 hi rlrossit 20:01:17 was the turkey good? 20:01:33 it was 20:01:36 and there was a lot of it 20:01:56 good and lot is a nice combination :) 20:02:52 OK, lets start 20:02:59 #topic actions from previous meeting 20:03:30 There was only a single action to make sure that we can talk about notifications in the midcycle 20:03:43 and I found out that there is no need to register a sessions 20:03:52 as there will be meetup style discussion 20:03:58 there is a common etherpad for it 20:04:03 but it is still empty 20:04:06 yeah it was pretty free-flowing at the last midcycle 20:04:07 #link https://etherpad.openstack.org/p/mitaka-nova-midcycle 20:04:56 also in the meantime I got my travel approved so I will be Bristol 20:05:17 good. you'll probably have to do the talking for both of us :) 20:05:34 I will try :) 20:05:58 Ok so moving forward 20:05:59 #topic open reviews 20:06:24 as we agreed I updated the commit chain based on the white-list idea 20:06:57 while you were eating turkey :) 20:07:44 yup. I stuck a review on the infra patch to change over how you handle the fingerprint generation in the version checker subclass 20:07:49 btw thanks for the comment regarding the version checker, I agree that it is hackish 20:08:11 I'm actually working on updating the version checker in o.vo, but before I update that, I want tests around the fixture so I know I don't break anything 20:08:30 rlrossit: great! 20:08:32 it'll allow you to stick in custom stuff to generate the fingerprint from 20:08:41 sounds perfekt 20:08:47 so I definitely found something to work on :) 20:09:01 good to hear that you are happy :) 20:09:32 just put me in the review. 20:10:09 that'll take a bit to put up... 20:10:11 how does it work between oslo and nova? Does nova uplifts to new oslo o.vo automatically or it is a painful process? 20:10:12 lots of tests 20:10:26 it's pretty easy 20:11:08 Ok, then I will change the current hack to a less awful one based on your suggestion and that can live in the review until you enhance o.vo 20:11:10 get the stuff in o.vo, update openstack/releases to bump the release of o.vo, update openstack/requirements to require the new version of o.vo, wait for proposalbot to send that update to requirements.txt to nova 20:11:46 and I'm totally fine with getting the less hacky version in, and then update it when o.vo gets updated 20:12:01 then it is agreed! :) 20:12:19 (It is so easy to agree if it is only two of us) 20:12:40 there as a bit bigger concern in the ML thread 20:13:17 Sean suggested to reuse the REST API schemas for the notifications 20:13:28 but I have concernss 20:13:36 #link http://lists.openstack.org/pipermail/openstack-dev/2015-December/080956.html 20:13:36 I have no idea how that works, so I'm going to stay out of that one... 20:14:30 I feel that Sean's problem is that we now creating yet another model defines the schema of the Notification payload, but we already have a bit similar schema for the REST responses 20:14:56 which seems to be a duplicate thing 20:15:31 but It think the intent and in lot of cases the content of the notification is different from the REST respons 20:15:47 so it is hard to cleanly reuse the existing schema 20:16:01 anyhow I state my issues in the ML 20:16:12 let's see where that discussion goes 20:17:27 besides that I' waiting for reviews before I feel confident to move forward to transform the next notification into versioned format 20:18:57 thats is all from my side regarding the open reviews 20:19:17 yeah for now I'm concentrating on just getting the bottom patch done 20:19:36 which is a good thing 20:20:18 anything else on the reviews? 20:20:26 nope 20:20:33 #topic open discussion 20:20:59 anything else? 20:21:06 * gibi feels we will close soon :) 20:21:13 nnnnnnnnnnnnnnope 20:21:19 pretty calm on my end 20:21:41 then, thanks for the effort 20:21:52 and lets close this early 20:21:58 sounds good 20:22:11 #endmeeting