22:03:55 <armax> #startmeeting neutron_drivers
22:03:56 <openstack> Meeting started Thu Nov  3 22:03:55 2016 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:03:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:03:58 <kevinbenton> code of conduct violation
22:03:59 <openstack> The meeting name has been set to 'neutron_drivers'
22:04:01 <ihrachys> is it neutron drivers or neutron kindergarten meeting? couldn't deduce
22:04:26 <HenryG> is there a difference?
22:04:43 <armax> probably not
22:05:02 <armax> ok guys, let’s be quick for ihrachys’ sake
22:05:10 <armax> despite him gaining back an hour
22:05:15 <armax> he’s still pretty sleepy
22:05:36 * ihrachys closes his webcam with a sticker just in case
22:05:50 <armax> for our US folks, next week we switch back from daylight saving
22:06:00 <armax> so this meeting we’ll start an hour earlier
22:06:19 <armax> so the team meeting, for instance is 6am PST
22:06:27 <armax> if I didn’t join at 7am, imagine what happens now
22:06:28 <armax> anyhoo
22:06:30 <armax> I digress
22:06:30 <kevinbenton> well at least it's not too early
22:07:17 <armax> let’s talk about the stadium assessment really quick
22:07:22 <armax> right now we have these pending patches:
22:07:27 <armax> https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs+branch:master+topic:stadium-implosion
22:07:46 <armax> those that are good to go I believe are
22:07:50 <armax> https://review.openstack.org/#/c/383908/
22:07:54 <armax> https://review.openstack.org/#/c/383882/
22:08:24 <armax> I have not seem much activity on https://review.openstack.org/#/c/383907/
22:08:27 <armax> so that’s probably good too
22:08:36 <armax> I’ll respin the others
22:08:43 <armax> by the end of today
22:08:53 <armax> if you guys can keep an eye on them
22:08:58 <HenryG> I tried to ping neil, no response today
22:09:13 <armax> HenryG: he and I had a chat at the summit
22:09:27 <armax> he’ll be working on some of the feedback
22:09:36 <ihrachys> last time I heard from neil was on Fri at the summit, asking about some gaps to close
22:09:40 <armax> but time and resources are tight
22:09:55 <armax> we’ll support him the best way we can
22:10:10 <armax> as things stand, it’s unlikely calico is gonna make the cut
22:10:18 <ihrachys> the question is, will he be able to deliver much in next week. I doubt.
22:10:20 <armax> but miracles do happen
22:10:29 <armax> ihrachys: you’re not a man of faith?
22:10:54 <ihrachys> armax: doesn't seem you are; I am just copying from the best
22:11:18 <armax> ihrachys: I used to be
22:11:20 <armax> ihrachys: :)
22:11:48 <armax> anyhoo, I’ll refresh these, then I’ll make sure that the summary capture an updated snapshot of where things stand
22:12:30 <armax> I started with revisiting the governance list
22:12:31 <armax> https://review.openstack.org/#/c/392010/
22:12:48 <armax> as you can see, the projects don’t disappear
22:13:40 <armax> and assumed someone pulls the right weight behind them again, there’s no reason why the patch can’t be reverted
22:14:08 <ihrachys> that retirement is reversible right? they just propose a patch on top, either moving under tent, or into stadium, again
22:14:22 <armax> ihrachys: correct
22:14:36 <armax> a tangential effort I am poking at slowly is this
22:14:37 <armax> https://review.openstack.org/#/c/391594/
22:14:52 <armax> this is another area to which I would like to bring some sanity too
22:15:17 <armax> of all the gazillion drivers we have in neutron, in tree, out of tree and those that rely on 3rd party
22:15:20 <armax> ci
22:15:41 <armax> there’s no common standard to use as a comparative measure
22:16:27 <armax> if I get some blessing from the tempest folks in the direction
22:16:40 <armax> then I would like to extend these to our internal API tests too
22:17:10 <armax> I talked to thingee a few times in the past about this and I also look forward to his feedback
22:17:53 <thingee> armax can you point me to any discussion or patch?
22:18:04 <armax> https://review.openstack.org/#/c/391594/
22:18:07 <thingee> thanks
22:18:17 <armax> we had a verbal discussion last week
22:18:47 <armax> plus a few emails way back
22:19:20 <ihrachys> I may easily miss the point, so sorry for that; but that seems more like redefining extensions and/or defcore, which is suspicious. but I need to have a closer look (I will tomorrow)
22:20:04 <armax> ihrachys: not quite, but if I was unable to convey my message clearly I obviosuly need to work on it
22:20:10 <armax> the patch is just a start
22:20:29 <ihrachys> well, it may well be me not being able to grasp the idea in 1 minute of reading the commit message :P
22:20:33 <armax> I did not want to put an awful lot of work into it without having an initial feedback
22:20:39 <armax> ihrachys: sure
22:20:50 <armax> as to your specific point
22:21:02 <armax> today when we look at the list of neutron extensions
22:21:06 <armax> the list is flat
22:21:15 <thingee> armax thanks for starting this
22:21:17 <armax> we don’t know which plugins implement which extensions
22:22:13 <armax> ihrachys: there’s probably a few ways to skin this cat, but give it some thought and we can talk at a better time of your day :)
22:22:31 <ihrachys> ofc
22:23:37 <armax> as soon as next week I’d like to resume reviewing some RFEs
22:23:42 <armax> I appreciate the cycle is tight
22:23:51 <armax> and we most likely won’t be able to tackle any
22:24:04 <armax> but at least we can give some feedback to submitters
22:24:13 <armax> on whether they are on the right track or not
22:25:06 <armax> so if you guys can spare a few momemnts out of your week to look at the usual lists
22:25:08 <armax> https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.tag=rfe
22:25:13 <armax> https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=Confirmed&field.tag=rfe
22:25:17 <armax> https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=Triaged&field.tag=rfe
22:25:29 <armax> that would be good
22:25:57 <armax> I usually carve some time to screen the lists before the meeting anyway
22:26:40 <HenryG> Did you see this? https://bugs.launchpad.net/bugs/1638399
22:26:40 <openstack> Launchpad bug 1638399 in neutron "EC2 networking driver for Neutron" [Undecided,New]
22:26:46 <armax> yes
22:26:55 <armax> it was filed as blueprint to start off
22:27:05 <ihrachys> HenryG: I think it was at a keynote
22:27:30 <ihrachys> oh right, that's what it says in the desc
22:28:03 <ihrachys> I don't believe we need to have it in scope of neutron itself do we?
22:28:16 <armax> I haven’t given it any thought yet
22:29:52 <HenryG> About neutron-lib
22:30:11 <armax> ihrachys: it doesnt’ have to be, but I suppose we can also look at it from the perspective of stadium inclusion criteria and judge that way
22:30:15 <armax> HenryG: shoot
22:30:53 <ihrachys> armax: it would need to first move to our infra and apply significant effort to get to that point where we could judge it
22:31:07 <armax> ihrachys: agreed
22:31:10 <HenryG> How do we make it official about the new policy for rehoming and (not) deprecating code?
22:31:28 <armax> HenryG: make official what exactly?
22:31:33 <armax> oh
22:31:56 <armax> HenryG: I added a section here:
22:31:57 <armax> https://wiki.openstack.org/wiki/Network/Meetings#Neutron-lib_and_planned_breakages
22:32:17 <armax> I was going to use the latest neutron-lib release as a way to trial the process a bit
22:32:21 <armax> so bear with me
22:32:32 <armax> I’ll probably tweak the title
22:32:41 <HenryG> OK. Will we need an entry in policies.rst?
22:32:55 <armax> what for?
22:33:28 <HenryG> To make it official. I guess I am not seeing how we can defend ourselves when we break others.
22:33:39 <armax> understood
22:33:57 <armax> would a link to https://review.openstack.org/#/c/331338/ (in whichever shape that is going to merge) suffice?
22:34:11 <armax> we’ll have to announce this on the various media we have at our disposal anyway
22:34:30 <HenryG> Yes, that seems about right
22:34:33 <armax> to make sure the people who pay attention have a chance to absorb the change
22:35:37 <armax> renamed to https://wiki.openstack.org/wiki/Network/Meetings#Neutron-lib_and_planned_neutron_refactoring btw
22:36:13 <armax> btw we have neutron-lib 1.0.0 by the looks of it
22:36:14 <armax> https://review.openstack.org/#/c/392009/
22:36:22 <HenryG> yep, cool
22:36:45 <armax> I don’t see it here yet
22:36:45 <armax> https://review.openstack.org/#/q/project:openstack/requirements+status:open
22:37:02 <armax> but I recall from an email from dhellmann that the process is changing slightly
22:37:10 <HenryG> Are we missing something?
22:37:23 <HenryG> Or is it just the usual latency?
22:38:07 <armax> http://lists.openstack.org/pipermail/openstack-dev/2016-November/106593.html
22:38:12 <ihrachys> release-post job still running for the release
22:38:22 <ihrachys> 4:31 already
22:38:26 <armax> point * Updating upper-constraints.txt for a release
22:38:48 <ihrachys> so pypi does not really have a tarball
22:38:54 <ihrachys> so nothing to update from
22:40:10 <ihrachys> another release-post job is hanging for 7hours already.
22:40:12 <ihrachys> it will take time
22:40:30 <armax> ouch
22:40:47 <armax> I was hoping I could use my bulldozzer straight away
22:42:19 <armax> ok
22:42:30 <armax> I don’t think I have much else on my plate
22:42:40 <armax> and I promised I’d get ihrachys off the hook sooner
22:42:43 <armax> than usual
22:42:58 <armax> we could have him stick another hour though since he’s already back to standard time
22:43:19 <ihrachys> :)
22:43:39 <armax> anything else that comes to mind from everyone?
22:43:59 <armax> words of praise/despair/dislike/anger/joy?
22:45:54 <armax> ok it looks like you guys have lost the will to live
22:46:13 * ihrachys waves
22:46:14 <HenryG> ARMAX IS THE GREATEST
22:46:26 <armax> I’ll let you swim in your silence
22:46:40 <armax> HenryG: I didn’t say to use words of derision
22:46:54 <armax> anyhoo :)
22:47:03 <armax> have a good weekend when it comes
22:47:05 <armax> cheers everyone
22:47:09 <armax> #endmeeting