22:00:48 <armax> #startmeeting neutron_drivers
22:00:49 <openstack> Meeting started Thu Dec  1 22:00:48 2016 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:00:52 <openstack> The meeting name has been set to 'neutron_drivers'
22:00:56 <ihrachys> hola!
22:02:28 <armax> we’re a couple of weeks away from O-2
22:02:37 <armax> in case you have not noticed
22:02:38 <armax> :)
22:03:27 <armax> #link https://releases.openstack.org/ocata/schedule.html
22:03:34 <armax> O-2 is the week of Dec 12
22:04:09 <armax> I wanted to take a few minutes of this meeting to do some sanity checking on our backlog
22:04:12 <armax> #link https://launchpad.net/neutron/+milestone/ocata-2
22:05:32 <armax> I am wondering if there are a few iitems in tehre that are no longer relevant
22:06:33 <armax> BPs like diagnostics, routed networks catch my attention as specs that are potentially understaffed
22:06:50 <armax> because both carl_baldwin and amuller have moved to greener pastures
22:07:18 <ihrachys> also sec group logging is still in spec discussion mode; and probably flow management for l2 extensions?
22:07:24 <armax> I was also wondering if it’s still relevant to track fwaas_v2 for this cycle
22:07:30 <kevinbenton> I think mlavalle is moving along on routed networks well
22:07:49 <carl_baldwin> ++
22:07:50 <armax> kevinbenton: my understanding is that his focus is mostly nova-side this cycle
22:08:04 <kevinbenton> Isn't that all that's left?
22:08:07 <armax> but the neutron side that carl_baldwin had in mind is effectively unstaffed
22:08:17 <kevinbenton> Oh, the floating ip stuff?
22:08:21 <carl_baldwin> Yes.
22:08:23 <armax> kevinbenton: no, there was making external networks routed aware
22:08:26 <armax> so to speak
22:08:38 <carl_baldwin> I've been talking with a few folks, mainly john_davidge about that stuff.
22:08:43 <carl_baldwin> Going to meet with him Monday.
22:08:51 <kevinbenton> I think we should do a different blueprint to track that
22:08:57 <carl_baldwin> I agree
22:09:02 <armax> carl_baldwin: ok
22:09:21 <armax> let me get togetehr with mlavalle and john-davidge
22:09:30 <armax> and we’ll reassess
22:09:37 <boden> armax: understaffed meaning not enough cores to help drive, correct?
22:09:39 <armax> boden: have you got in touch with amuller?
22:09:55 <boden> armax: yes, he’s looking for someone to help drive the diagnostics spec/work
22:09:58 <armax> boden: pretty much yeah
22:10:27 <armax> ihrachys: as for the logging spec, rossella said she was still keen to help
22:10:42 <armax> but if it tooks us 4 cycles to get the spec in order
22:10:52 <boden> armax: … and we are back to square 1 with a new spec
22:11:03 <armax> I am not gonna speculate on how long it’s gonna take to agree on the code
22:11:39 <boden> armax: if we can’t get the spec closed soon, then it’ll surely be difficult to contain in Ocata
22:11:58 <boden> so go review it! ;)
22:12:02 <armax> boden: if we can at least agree on the specification, that would be a big step forward
22:12:17 <boden> armax: spec is ready.. grab a beverage and enjoy
22:12:26 <armax> boden: you’re funny :)
22:12:46 <armax> come my side of the screen and I’ll show you my backlog :)
22:12:57 <boden> armax: IMO its ready for some core feedback… I’m hoping its a bit simpler, but who knows
22:13:22 <armax> boden: I am not the only core in the room ;)
22:13:31 <armax> anyone else has anything in mind?
22:13:35 <boden> armax: understand; theres no lack of work.. I’m hoping we can progress with the spec anyway
22:13:54 <armax> I am going to take a pass at the milestone dashboard and clean it up a bit
22:13:59 <armax> it’s been neglected lately
22:14:00 <johnsom> FYI, I moved the one LBaaS bug out if you refresh you screen.
22:14:15 <armax> johnsom: only one?
22:14:17 <armax> lazy
22:14:40 <johnsom> The *only* lbaas bug that was on your O-2 list, because we are cool
22:15:22 <armax> johnsom: understood
22:16:00 <johnsom> I'm still working on the other 60 I just inherited...  lol
22:16:38 <armax> ihrachys, kevinbenton: how’s the stuff assigned to you going?
22:17:09 <ihrachys> for ovo, I think we are making good progress, and we got rossella_s helping us lately with reviews, which is nice.
22:17:10 <kevinbenton> armax: ok. should still be able to get the l2 agent done for push notifications by end of cycle
22:18:01 <ihrachys> for no-downtime-upgrades, we landed the patch that guards against contract scripts; and we are looking at port binding spec for live migration, giving suggestions on how to make model changes in the new world.
22:18:15 <armax> ihrachys: that’s great
22:18:24 <ihrachys> as for push-notifications, I tend to review when kevinbenton has something for me
22:18:25 <armax> in fact I wanted to bring up the next topic I had in mind
22:18:41 <armax> #link https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs
22:18:45 <armax> open specs
22:19:13 <armax> the high profile ones I can think of are: diagnostics, port status, and port binding
22:19:33 <kevinbenton> port status i think is pretty close
22:19:45 <ihrachys> https://review.openstack.org/#/c/392023/ <- this should not exist, rfe is postponed
22:19:51 <armax> anything else come to mind that require some focus and attention?
22:20:36 <kevinbenton> armax: what is the timeline for these if they get ready?
22:20:41 <brianstajkowski> port binding we just need to nail down the model changes, if any, everything else is shaping up and should be close soon
22:20:42 <kevinbenton> armax: can we start landing stuff in ocata
22:21:08 <armax> kevinbenton: land what type of stuff?
22:21:19 <kevinbenton> armax: like if port status gets approved for example
22:21:25 <kevinbenton> armax: can we merge code this cycle?
22:21:31 <armax> if the code is ready, sure
22:21:44 <kevinbenton> ack
22:21:51 <armax> I hope I can get time by today and tomorrow to have a pass to the ones I mentioned
22:22:22 <armax> hoping no gate fire preempts me from thi
22:22:23 <armax> s
22:22:24 <armax> :)
22:23:34 <armax> anything else that comes to mind about this list of specs?
22:24:20 <brianstajkowski> the rfe
22:24:46 <armax> brianstajkowski: can you be more precise?
22:24:51 <brianstajkowski> the rfe's in o-2, are those open to spec work as well
22:24:58 <brianstajkowski> sorry hit enter too quickly
22:25:10 <brianstajkowski> specifically the subnetpool rfe
22:25:36 <armax> brianstajkowski: bug 1558812?
22:25:36 <openstack> bug 1558812 in neutron "[RFE] Enable adoption of an existing subnet into a subnetpool" [Wishlist,Triaged] https://launchpad.net/bugs/1558812 - Assigned to Ryan Tidwell (ryan-tidwell)
22:26:21 <armax> I should have taken the RFE bug out of Ocata
22:26:26 <armax> when I took the blueprint out
22:26:37 <armax> because Ryan and Carl had no cycles this...cycle
22:26:52 <armax> brianstajkowski: is this what you’re referring to?
22:27:03 <brianstajkowski> yes
22:27:33 <armax> though I saw you and Ryan chatted recently
22:27:53 <kevinbenton> carl_baldwin, the big issue with that spec was worrying about all of the race conditions, right?
22:28:01 <kevinbenton> s/spec/rfe
22:28:02 <armax> not sure if the interest is related to a recent surge in staffing
22:28:25 <armax> kevinbenton: something along those lines, iirc
22:29:29 <carl_baldwin> kevinbenton: Yes. I wanted an atomic adoption of all subnets on a network.
22:30:02 <kevinbenton> carl_baldwin: can you comment on the RFE what race conditions you can think of?
22:30:11 <kevinbenton> carl_baldwin: just so we have them recorded
22:30:22 <kevinbenton> carl_baldwin: and know what to watch out for if someone picks it up in th future
22:30:35 <carl_baldwin> kevinbenton: sure, I can do that.
22:30:42 <kevinbenton> carl_baldwin: thx
22:31:59 <mlavalle> armax: ping
22:32:53 <kevinbenton> mlavalle: he's in shock :)
22:32:54 <armax> mlavalle: I was wondering if we should move blueprint routed-networks out of O
22:33:12 <armax> at least the neutron-side of it that carl_baldwin had in mind to work on
22:33:23 <armax> unless you and john davidge have a handle on it
22:33:40 <mlavalle> we can handle it
22:33:45 <armax> in any case we’d need to update assignee/approver on the blueprint
22:34:11 <mlavalle> the only piece missing is the interaction with Nova
22:34:13 <armax> mlavalle: how’s the nova side going?
22:34:20 <mlavalle> and I am working on that
22:34:29 <mlavalle> it is pretty advanced
22:34:29 <armax> mlavalle: that’s not what this spec should be tracking though
22:34:55 <kevinbenton> armax: so then we should mark it as done for neutron IMO
22:35:03 <kevinbenton> armax: and open a new one for floating IP stuff
22:35:13 <armax> kevinbenton: ok, that’s what I am leaning on too
22:35:15 <mlavalle> yes, the Neutron side is done
22:35:37 <mlavalle> except the floatingip stuff
22:35:40 <armax> ok
22:35:43 <haleyb_> i can be approver
22:35:47 <mlavalle> and I will have the Nova side done
22:35:56 <mlavalle> this cycle
22:36:01 <armax> at this point this is pike material
22:36:28 <mlavalle> sorry, what is pike material?
22:36:43 <armax> deferred to PIke the floatingip stuff you referred to
22:36:49 <mlavalle> yes
22:36:55 <armax> ok
22:37:17 <mlavalle> how do you want to track the nova side piece for this cycle?
22:37:26 <armax> mlavalle: I don’t :)
22:37:45 <armax> I trust you you get it done unsupervised :)
22:37:59 <mlavalle> ok, let's do something
22:38:00 <armax> jokes aside, is there a spec/bp on the nova side of the fence?
22:38:21 <mlavalle> No, because it's really code I am writing on the Neutron side
22:38:33 <mlavalle> that integrates with Nova
22:38:42 <armax> OK, do you have a patch # handy?
22:39:12 <mlavalle> yes, hang on
22:39:19 <ihrachys> https://review.openstack.org/#/c/358658/
22:39:25 <armax> are you getting enough nova core attention?
22:39:34 <mlavalle> https://review.openstack.org/#/c/358658/
22:39:46 <mlavalle> yes, I am getting nova core attention
22:40:13 <mlavalle> kevinbenton reviewed that patchset a few days ago
22:40:22 <mlavalle> and we agreed on a the next step
22:40:36 <kevinbenton> ugh my memory is bad
22:40:43 <kevinbenton> i forgot there is still neutron side stuff to do
22:40:47 <armax> mlavalle: ok, let’s keep the blueprint open for this cycle, I’ll update the whiteboard to reflect the scope of the work for ocata
22:40:48 <kevinbenton> that should fall under the blueprint then
22:41:05 <mlavalle> armax: cool
22:41:23 <mlavalle> I'll make sure I update you every weekly meeting
22:41:49 <armax> kevinbenton the enginefacade-switch blueprint has lost its approver
22:42:04 <armax> on https://blueprints.launchpad.net/neutron/ocata/+assignments
22:42:08 <kevinbenton> armax: i can be approver for that
22:42:14 <armax> we should really get the defectors to pass the baton
22:42:16 <kevinbenton> armax: because i understand what is required
22:42:22 <armax> HenryG, carl_baldwin, amuller ^
22:42:28 <kevinbenton> armax: and have been reviewing some of Ann's patches already
22:42:35 <armax> kevinbenton: ok
22:44:36 <armax> ok, I have some work to do with this dashboard and the various backlogs
22:44:49 <armax> any other item that comes to mind?
22:44:58 <kevinbenton> can we change this meeting time?
22:45:13 <kevinbenton> since the TZ switch it conflicts with another one i have
22:45:18 <armax> kevinbenton: what do you have in mind?
22:45:32 <kevinbenton> an hour earlier or later :)
22:45:58 <armax> kevinbenton: an hour later should work for me
22:46:07 <armax> it’ll probably not work for ihrachys
22:46:12 * ihrachys becomes grumpy
22:46:15 <armax> but I guess it’s a matter of weeks
22:46:20 <ihrachys> it will work, anything will
22:46:27 <armax> kevinbenton: can you put up for one more week?
22:46:31 <ihrachys> yes, in a month, I will be in a better place
22:46:33 <kevinbenton> armax: yep
22:46:36 <armax> ihrachys: but I won’t :)
22:46:46 <ihrachys> ptls gonna suffer
22:46:48 <mlavalle> ihrachys: are you moving?
22:47:01 <ihrachys> mlavalle: yes, always on the move
22:47:13 <ihrachys> I can also live next time with +1h
22:47:37 <armax> +1 means 11pm CET
22:47:39 <kevinbenton> well my meeting that conflicts is every other week
22:47:46 <armax> ok
22:47:47 <kevinbenton> so we can certainly wait two weeks to start the new time
22:47:57 <armax> so your conflict is this week or the next?
22:48:00 <kevinbenton> this week
22:48:04 <armax> ok
22:48:12 <armax> we can move it sooner too
22:48:21 <armax> and that actually works better for me and ihrachys
22:48:29 <kevinbenton> i think sooner is harder on amotoki isn't it?
22:48:34 <armax> true
22:48:44 <armax> it would be 6am
22:49:00 <armax> let me also get also of amotoki to see where he’s at
22:49:06 <kevinbenton> ack
22:49:07 <armax> we have 2 weeks to sort this out
22:49:23 <armax> by then there won’t be a neutron project anymore so the problem will solve itself out
22:49:40 <kevinbenton> dramatic
22:49:52 <armax> as always
22:49:55 <armax> ok, anything else?
22:49:59 <armax> other request?
22:50:03 <armax> I am in the christmas spirit
22:50:18 <armax> no money requests please
22:50:26 <ihrachys> I accept gift cards
22:50:36 <mlavalle> first day of December. time to be in the Christmas spirit
22:50:36 <armax> I can get you a christmas card
22:50:49 <armax> all the gift cards I had I gave them to dougwig
22:51:01 <armax> but he claims he has never received them
22:51:50 <dougwig> nope, never did.
22:52:01 <armax> if theres’ nothing else that can be discussed in 10 mins I’d say let’s get 10 mins back
22:52:08 <armax> 8 now
22:52:18 <ihrachys> took 2 minutes to type it?
22:52:23 <armax> dougwig: I am still waiting on the nginx fix!
22:52:34 <armax> ihrachys: I type like a sloth
22:52:56 <dougwig> armax: and i'm still waiting on my gift cards.  mutually assured destruction.
22:53:04 <kevinbenton> armax: there is a patch isn't there?
22:53:07 <armax> dougwig: if that is not THE definition of passive aggressive I don’t know what is!
22:53:07 <armax> :)
22:53:23 <armax> kevinbenton: yes
22:53:25 <armax> in merge conflict
22:53:35 <armax> kevinbenton: but to your point
22:53:37 <dougwig> ha. that's a -2 for you, somewhere down the road.
22:53:39 <armax> we did move forward a bit
22:53:55 <armax> so I can’t complain too much
22:55:00 <armax> ok folks
22:55:12 <armax> thanks for joining
22:55:15 <armax> #endmeeting