22:01:34 <armax> #startmeeting neutron_drivers 22:01:35 <openstack> Meeting started Thu Oct 6 22:01:34 2016 UTC and is due to finish in 60 minutes. The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:01:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:01:38 <openstack> The meeting name has been set to 'neutron_drivers' 22:01:42 <amuller> hiho 22:01:52 <ihrachys> o/ 22:01:56 <dougwig> o/ 22:02:09 <armax> kevinbenton, carl_baldwin, HenryG: ping 22:02:19 <kevinbenton> o/ 22:02:20 <carl_baldwin> o/ 22:02:20 <armax> I guess this is ihrachys’ first meeting as driver member 22:02:24 <armax> welcome! 22:02:26 <ihrachys> armax: nope 22:02:29 <armax> no? 22:02:31 <armax> damn 22:02:33 <ihrachys> but thanks :) 22:02:39 <armax> so I guess hazing doesn’t apply 22:03:10 <armax> my memory is not as sharp as it used to be 22:03:24 <armax> effect of too much neutron radiations 22:03:56 <armax> the agenda for today’s meeting won’t be (again) the convential one we’re used to 22:04:15 <dasm> o/ 22:04:33 <armax> I’d like to talk respectively of a) design summit schedule; b) ocata priorities 22:04:38 <dasm> armax: even tho, if it's not first one for ihrachys, it's still pretty late back in Europe. so, i believe, it's still achievement 22:04:41 <armax> and there was something else but I can’t remember 22:04:50 <armax> as proof of the fact that I am becoming senile 22:05:32 <johnsom> Was it a no-confidence vote? 22:05:38 <johnsom> grin 22:05:46 <ihrachys> AARP membership card on its way 22:06:12 <armax> oh yes 22:06:14 <armax> I remember 22:07:03 <armax> I was reading 22:07:05 <armax> #link http://lists.openstack.org/pipermail/openstack-dev/2016-October/105213.html 22:07:27 <armax> and it reminded me to nuke some folks 22:07:51 <armax> so c) seek for blood 22:08:15 <armax> and d) kick off the stadium consolidation’s final stage 22:08:23 <ihrachys> that's packed for 1h 22:08:31 <amuller> a bit :) 22:09:16 <armax> it’s fine 22:09:26 <armax> ihrachys. amuller: time me 22:09:41 <armax> #topic Design summit schedule 22:10:03 <armax> #link there’s an early draft avaiable at 22:10:04 <armax> #link https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Neutron%3A 22:10:42 <johnsom> typo: chair: dougwig/johnsonm 22:10:56 <armax> ack 22:11:00 <armax> I noticed there’s a bug in cheddar 22:11:10 <armax> in that swapping sessions doesn’t swap the content by the looks of it 22:11:15 <armax> so bear with me while I chase this down 22:11:40 <armax> in the meantime, I have reached out individually the people I expect to participate as chairs 22:12:13 <armax> thanks for those of you who have already replied 22:12:56 <armax> what I would like from you is the link to the etherpad belonging to your session and a brief abstract so that I feel it up in cheddar 22:13:13 <kevinbenton> feel it up? 22:13:16 <dougwig> 'feel it up'. oh my. 22:13:17 <armax> in the process I’ll work with each of you to brainstorm and agree on the content overall 22:13:18 <armax> fill 22:13:33 * armax has the mind somewhere else 22:13:40 <dougwig> we know where. 22:14:02 <armax> I’d love to be done by next team meeting 22:14:35 <armax> so that ihrachys can divulgate further 22:14:36 <amuller> ack 22:14:52 <armax> divulge 22:14:59 <ihrachys> tiny thing that HenryG raised today; expected etherpad prefix, is it still neutron-newton? 22:15:00 <armax> again, my mind somewhere else 22:15:18 <armax> did I say that in the email? 22:15:23 <armax> then I am an idiot 22:15:29 <ihrachys> yeah 22:15:32 <ihrachys> I mean, you said :) 22:15:39 <armax> that’s clearly meant to be ocata-neutron 22:15:42 <armax> my bad 22:15:51 <ihrachys> ack 22:15:52 <amuller> armax: please update the link for the testing session to https://etherpad.openstack.org/p/ocata-neutron-testing 22:16:03 <armax> amuller: :) 22:16:05 <amuller> I'll fill in the abstract tomorrow 22:16:09 <armax> I just noticed that you played along : 22:16:11 <armax> :) 22:16:29 <armax> but johnsom didn't 22:16:54 <armax> please double check time conflicts 22:17:02 <johnsom> Yeah, well, we are the rebels 22:17:22 <amuller> armax: thanks for moving my session to Thu btw 22:17:25 <armax> also when you go through your etherpad 22:17:36 <dougwig> i edited the email to ocata before i forwarded it to johnsom. 22:18:00 <armax> please cross/strike content in https://etherpad.openstack.org/p/ocata-neutron-summit-ideas if it’s going to be included in your etherpad 22:18:24 <armax> dougwig: but you didn’t tell me, did you? 22:18:32 <armax> wanted to make me look like a fool, uh? 22:18:35 <armax> amuller: no problemo 22:18:38 <dougwig> armax: someone had already brought it up in a reply. 22:18:43 <armax> they did? 22:19:01 <armax> oh well, my legacy is casted 22:19:14 <armax> I screwed up my last design summit organization 22:19:16 <armax> everything is ruined 22:19:44 <armax> bear in mind that this cycle we’ll start off our summit with a nova/neutron session 22:19:49 <dougwig> i don't see it now. maybe i imagined it. 22:20:00 <armax> the time is immutable so please don’t ask to move it 22:20:16 <armax> because that’s the only slot we don’t conflcit with the nova sessions 22:20:26 <armax> but please do strive to join if you are a core or a driver memeber 22:20:54 <armax> so if you have a talk, well…figure out how to split yourself or something equivalent 22:22:01 <armax> besides, we’ll most likely have gluon folks joining the room and dougwig would be pleased to hear that at least some controversy will come up 22:22:13 <armax> amotoki: I have not heard from you 22:22:15 <dougwig> yes, this summit looks too tame. 22:22:35 <armax> dougwig: hang in there, you won’t be disappointed 22:22:40 <ihrachys> dougwig: ack. I will try to fill in my session with scary shit. 22:22:45 <ihrachys> for your amuzement 22:22:46 <amotoki> armax: I will be at the summit. I took PTO and offline these two days. 22:22:51 <armax> ok, anything anyone wants to raise? 22:22:59 <dougwig> container NFV chained ports 22:23:02 <armax> amotoki: ok, thanks 22:23:18 <amuller> throw in some flavors in there and it's golden 22:23:22 <armax> if not, I’ll move on to prove to amuller and ihrachys that I can complete the agenda on time 22:23:36 <dougwig> amuller: that's not implied? 22:23:37 <carl_baldwin> armax: I owe you a follow up. I'll send email today. 22:23:38 <armax> and I’ll even through some minutes to spare 22:23:44 <armax> carl_baldwin: thanks 22:23:49 <armax> next topic coming uo 22:23:50 <armax> up 22:23:59 <armax> #topic Ocata priorities 22:24:33 <armax> we all know that setting priorities in open source and openstack development is hard and virtually impossible 22:24:50 <kevinbenton> so next topic then? 22:24:52 <kevinbenton> :D 22:24:59 <armax> wait 22:24:59 <armax> :) 22:25:13 <armax> now, if you are not familiar with the published Ocata schedule 22:25:15 <armax> #link https://releases.openstack.org/ocata/schedule.html 22:25:30 <armax> you can see that feature freeze is the week of Jan 24 22:26:01 <armax> this means that between now, the pre summit rush, the post summit cool off, thanksgiving and christmas 22:26:20 <kevinbenton> we get 1 feature? 22:26:23 <armax> practically, time is tight 22:26:27 <dougwig> that's barely enough time to change my socks. 22:26:36 <amuller> I assume people will be finishing up unfinished work from Newton 22:26:39 <amotoki> only 12 weeks after the summit including them :p 22:26:50 <armax> amuller: in a nutshell, yes 22:27:16 <armax> we need not only close in on the newton backlog 22:27:32 <armax> but also fix all the bugs that kevinbenton has introduced and will introduce when finishing push notifications 22:27:48 <armax> included ihrachys’ and carl_baldwin’s 22:27:56 <carl_baldwin> My bugs? 22:28:12 <carl_baldwin> Kevin was going to fix those, I thought. :) 22:28:24 <armax> carl_baldwin: that’s between you too :) 22:28:50 <amuller> armax: my team will primarily focus on finishing up Newton work, and perhaps starting spec/design work throughout the cycle targeting P 22:28:52 <armax> plus, there’s the usual testing and CI side of the house to improve 22:29:08 <amuller> that's the high level plan... 22:29:31 <armax> one thing to consider is that the Nova team is committed to devote some time and effort into the Nova/Neutron integration layer 22:29:56 <sbelous> os-vif? 22:30:01 <armax> it would be nice to align with them 22:30:15 <armax> sbelous related but not only 22:30:57 <armax> so I am thinking that we are pretty much in feature freeze already and we’ll squeeze only a few high visibility targets between now and Ocata 22:31:30 <armax> to be worked out once we got hold of the outstanding RFE list/open specs lists we got 22:31:54 <ihrachys> armax: do we have a list of targets to squeeze, or it's anything incomplete from newton? 22:31:59 <armax> I don’t think it’s a bold move circumstances considered 22:32:13 <amuller> IMO it's a good idea to continue spec/design work throughout O for stuff we'd like to see in P 22:32:18 <amuller> while we continue work items from N 22:32:25 <armax> ihrachys: we’ll have to scan the newton backlog to assess what can/must be pruned 22:32:31 <armax> and if there’s anything new that can be added 22:32:33 <dougwig> it could be "bugs only" and we'd still have too much content. 22:32:46 <armax> amuller: even spec review is time consuming 22:32:52 <amuller> certainly is 22:32:53 <ihrachys> that's a reasonable move; even with alternative schedule, having a stabilization cycle once in a while is good. 22:33:02 <armax> and I personally think that if I can devote time to code review of stuff we already agreed on 22:33:21 <armax> I’d rather do that 22:33:27 <armax> but it’s a judgement call 22:33:38 <amotoki> I agree this cycle focuses on bug and high priority features. 22:34:18 <armax> ok, anything anyone wants to bring up? 22:34:40 <armax> we’ll talk in more detail about this during the backlog session 22:34:44 <armax> at the summit 22:34:44 <carl_baldwin> Seems wise to me. There has been so going on lately. Keeping some focus on stabilizing it a bit will be good. 22:35:16 <armax> but w’ll do some work between now and then of course 22:35:28 <armax> ok next topic coming up 22:36:35 <armax> #topic membership cleanup 22:36:51 <armax> in neutron we have two key teams 22:36:55 <armax> #link https://review.openstack.org/#/admin/groups/150,members drivers 22:37:04 <armax> #link https://review.openstack.org/#/admin/groups/38,members cores 22:37:27 <armax> while the former is tasked with reviewing RFEs and specs and bikeshed once a week 22:37:53 <dougwig> i don't think the time i've been putting in is up to snuff, so i'm stepping down from the drivers team. 22:37:53 <armax> the latter is tasked with reviewing the code that lands into our trees 22:38:16 <armax> dougwig: ok, let me finish first :) 22:39:17 <johnsom> I think your first link was wrong, isn't it this one? 22:39:20 <armax> what I wanted to add is that I personally think that is reasonable to expect membership to continue if the individual shows some regularity in fullfilling their duties 22:39:20 <johnsom> #link https://review.openstack.org/#/admin/groups/464,members 22:39:39 <armax> johnsom: yes 22:39:39 <carl_baldwin> ^ That looks better 22:39:43 <armax> johnsom: thanks 22:39:49 <armax> :’( 22:39:54 <armax> I am failing left and right 22:40:24 <armax> anyhoo 22:42:16 <armax> all I am trying to say is that someone belongs to that list and feels like he/she cannot keep up with the project flow nearly on a daily basis, then that person should probably consider stepping down 22:42:59 <dougwig> !! 22:43:00 <openstack> dougwig: Error: "!" is not a valid command. 22:43:03 <armax> to either list, I mean 22:43:05 <dougwig> !! 22:43:11 <armax> now dougwig, your turn :) 22:43:17 <armax> it sucks to see you step down 22:43:50 <armax> nonetheless I appreciate the time and energy you spent so far 22:44:03 <dougwig> if my commitments change, we'll see what happens. else maybe i'll be in a corner with salv and a beer. 22:44:30 * ihrachys thanks dougwig for his service 22:45:09 <armax> the team always welcome people who love to bikeshed 22:45:10 <amuller> dougwig++ 22:45:16 <armax> erm, work hard 22:46:23 <armax> anything anyone wants to add? 22:46:37 <armax> if not, racing towards the next and final topic 22:46:59 <armax> #topic stadium consolidation - final stage 22:47:51 <armax> nearly all of you are aware that I have been made this my crusade 22:48:26 <armax> during last cycle I did not quite finish all I wanted to do, but I feel like I am pretty close 22:48:44 * johnsom feels the pull on the ropes tied to his arms.... 22:49:09 <armax> in the coming week, I’ll be sending out an update 22:49:29 <armax> in spec 22:49:30 <armax> #link http://specs.openstack.org/openstack/neutron-specs/specs/newton/neutron-stadium.html 22:49:50 <ihrachys> armax: you mean a patch to the spec? 22:49:52 <armax> it’s stated that the first milestone of a cycle is the one where project membership is assessed 22:50:08 <armax> ihrachys: no, it’s probably gonna be in a form of email 22:50:14 <armax> I will need to tweak the devref 22:50:29 <armax> once I finalize patch https://review.openstack.org/#/c/353131/ 22:52:03 <armax> I’ll prepare a template where we can objectively and transparently assess how projects meet the criteria 22:52:23 <armax> and we’ll judge during the forthcoming drivers meeting who gets to stay in or who gets to go out 22:53:02 <armax> for this cycle, we don’t accept inclusions 22:53:13 <armax> should there be any 22:53:30 <armax> we’ll wait until Pike for that 22:53:49 <armax> anything anyone else would like to add? 22:53:56 <armax> if not, I finished with 7 minutes to spare 22:54:02 <armax> ihrachys, amuller: how about that? 22:54:05 <ihrachys> like a boss 22:54:07 <armax> 6 now 22:54:49 <amuller> Most impressive. 22:55:29 <armax> ok 22:55:31 <armax> folks 22:55:35 <carl_baldwin> Nice work. 22:55:47 <armax> thanks for joining 22:55:56 <armax> Today is the day Newton is officially out 22:56:07 <armax> be proud (or not) of what you achieved 22:56:11 <armax> I certainly am 22:56:13 <dougwig> so now we can merge all those rebase breakers? 22:56:15 <armax> …somewhat :) 22:56:16 * ihrachys slowly claps 22:56:28 <armax> bye 22:56:30 <armax> #endmeeting