21:01:30 <kevinbenton> #startmeeting networking
21:01:31 <openstack> Meeting started Mon Apr 17 21:01:30 2017 UTC and is due to finish in 60 minutes.  The chair is kevinbenton. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:33 <kevinbenton> hello!
21:01:34 <openstack> The meeting name has been set to 'networking'
21:01:35 <dasm> o/
21:01:36 <mlavalle> o/
21:02:05 <hichihara> o/
21:02:08 <haleyb> hi
21:02:17 <kevinbenton> ihrachys, armax ping
21:02:44 <ihrachys> o/
21:03:27 <kevinbenton> ok, let's get started
21:04:02 <kevinbenton> #topic Announcements
21:04:29 <kevinbenton> the schedule for the Forum at the summit is available
21:04:52 <kevinbenton> #link http://lists.openstack.org/pipermail/openstack-dev/2017-April/115174.html
21:05:10 <kevinbenton> so if you are planning on attending the summit, take a look at that
21:06:20 <kevinbenton> In the bad news area, it sounds like OSIC is not having its funding renewed
21:06:29 <mlavalle> yeap
21:06:53 <dasm> ;_;
21:07:37 <kevinbenton> so please reach out to me if you will no longer be able to work on neutron so we can pick up whatever was assigned to you
21:08:25 <ihrachys> +, no patch left behind
21:08:36 <mlavalle> like the US Marines
21:08:58 <kevinbenton> does anyone have any other announcements?
21:09:24 <dasm> we're past Pike-1. Pike-2 is beginning of June
21:09:43 <dasm> so, ~6-7 weeks
21:10:12 <dasm> and, afaik, kevinbenton you've recognized pike goals, right?
21:10:41 <kevinbenton> dasm: yes
21:10:53 <kevinbenton> #link https://review.openstack.org/#/c/457200/
21:11:04 * dasm was looking for handy link, but couldn't find
21:11:08 <kevinbenton> that shows that we are intending to support both community goals
21:11:42 <ihrachys> there was a etherpad for py3 effort from jlibosva
21:11:45 <ihrachys> I will update the bug
21:11:55 <kevinbenton> ihrachys: thx. i couldn't find that
21:12:10 <ihrachys> https://etherpad.openstack.org/p/py3-neutron-pike
21:12:21 <ihrachys> yeah we never actually advertised it beyond CI team
21:12:26 <ihrachys> and we created it prev week
21:12:30 <ihrachys> it's a stub
21:12:36 <ihrachys> but will have more details
21:12:48 <kevinbenton> ack
21:14:04 <kevinbenton> ok
21:14:17 <kevinbenton> #topic Neutron Review Inbox
21:15:19 <kevinbenton> I went through and looked at all of the old patches against neutron without a WIP -1  and not failing jenkins to provide feedback
21:16:05 <kevinbenton> I want us to get to a point where we don't have any patches waiting for reviewer feedback so stuff doesn't fall between the cracks
21:16:24 <ihrachys> ++, I smashed some of those you +2d into the gate yesterday
21:16:32 <ihrachys> quite a lot of them actually
21:16:41 <ihrachys> it was like 30+ patches stacked in gate
21:17:20 <kevinbenton> if someone is good with gerrit queries, i would like the following query to be checked by cores each day
21:17:36 <kevinbenton> vote from people >=0
21:17:47 <kevinbenton> vote from CI == 1
21:17:54 <kevinbenton> workflow >= 0
21:18:27 <ihrachys> do you have a query handy?
21:18:35 <ihrachys> also, what happened to reviewday dashboard?
21:18:48 <ihrachys> I mean the one linked to from http://status.openstack.org/reviews/
21:19:03 <kevinbenton> that links to here
21:19:04 <kevinbenton> https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fnetworking%2Dbgpvpn+OR+project%3Aopenstack%2Fnetworking%2Dovn+OR+project%3Aopenstack%2Fnetworking%2Dmidonet+OR+project%3Aopenstack%2Fnetworking%2Dbagpipe+OR+project%3Aopenstack%2Fneutron%2Dfwaas+OR+project%3Aopenstack%2Fneutron%2Dlib+OR+project%3Aopenstack%2Fnetworking%2Dsfc+OR+project%3Aopenstack%2Fpython%2Dneutronclient+OR+project%3Aopenstack%2Fneutron%2Dspecs+
21:19:04 <kevinbenton> OR+project%3Aopenstack%2Fnetworking%2Dodl+OR+project%3Aopenstack%2Fovsdbapp+OR+project%3Aopenstack%2Fneutron+OR+project%3Aopenstack%2Fneutron%2Ddynamic%2Drouting%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself+branch%3Amaster&title=Neutron+pike%2D1+Review+Inbox&All+Gate+failure+fixes+neutron=%28message%3A1679775+OR+message%3A1683090+OR+message%3A1683249+OR+message%3A1683256+OR+
21:19:04 <kevinbenton> message%3A1509004+OR+message%3A1540983+OR+message%3A1604115+OR+message%3A1622516+OR+message%3A1627424+OR+message%3A1628886+OR+message%3A1655567+OR+message%3A1660612+OR+message%3A1666731+OR+message%3A1669805+OR+message%3A1672607+OR+message%3A1674517+OR+message%3A1676966+OR+message%3A1683227+OR+message%3A1683369+OR+message%3A1683469+OR+message%3A1669900+OR+message%3A1683365+OR+message%3A1662387+OR+message%3A1664347+OR+message%3A1673531+OR
21:19:04 <kevinbenton> +message%3A1674443+OR+message%3A1681945%29&Approved+RFE+neutron=%28message%3A1458890+OR+message%3A1468366+OR+message%3A1476527+OR+message%3A1492714+OR+message%3A1498987+OR+message%3A1507499+OR+message%3A1516195+OR+message%3A1520719+OR+message%3A1521291+OR+message%3A1560961+OR+message%3A1560963+OR+message%3A1561824+OR+message%3A1563967+OR+message%3A1566520+OR+message%3A1577488+OR+message%3A1578989+OR+message%3A1579068+OR+message%
21:19:04 <kevinbenton> 3A1583184+OR+message%3A1598081+OR+message%3A1630981+OR+message%3A1632877+OR+message%3A1649909+OR+message%3A1650678+OR+message%3A1667329+OR+message%3A1674349%29&High+Bugs+neutron=%28message%3A1375625+OR+message%3A1559920+OR+message%3A1599936+OR+message%3A1610483+OR+message%3A1626010+OR+message%3A1627424+OR+message%3A1634123+OR+message%3A1659175+OR+message%3A1659691+OR+message%3A1661717+OR+message%3A1665215+OR+message%3A1669021+OR+message
21:19:06 <kevinbenton> %3A1674517+OR+message%3A1677729%29&Blueprints+neutron=%28topic%3Abp%2Fadopt%2Doslo%2Dversioned%2Dobjects%2Dfor%2Ddb+OR+topic%3Abp%2Fneutron%2Dlib%2Dnetworking%2Dl2gw+OR+topic%3Abp%2Fneutron%2Dlib%2Dnetworking%2Dovn+OR+topic%3Abp%2Fonline%2Dupgrades+OR+topic%3Abp%2Fpush%2Dnotifications+OR+topic%3Abp%2Fagentless%2Ddriver+OR+topic%3Abp%2Fenginefacade%2Dswitch+OR+topic%3Abp%2Ffwaas%2Dapi%2D2.0+OR+topic%3Abp%2Fl2%2Dapi%2Dextensions+OR+topic%
21:19:08 <kevinbenton> 3Abp%2Flive%2Dmigration%2Dportbinding+OR+topic%3Abp%2Fnative%2Dl2pop+OR+topic%3Abp%2Fneutron%2Din%2Dtree%2Dapi%2Dref+OR+topic%3Abp%2Fport%2Ddata%2Dplane%2Dstatus+OR+topic%3Abp%2Fquota%2Dlimits+OR+topic%3Abp%2Frbac%2Dkeystone%2Dv3+OR+topic%3Abp%2Fsecurity%2Dgroup%2Dlogging+OR+topic%3Abp%2Ftroubleshooting%29
21:19:12 <kevinbenton> whoops
21:19:13 <ihrachys> oh
21:19:30 <kevinbenton> so that's good for deciding what to prioritize
21:19:47 <kevinbenton> but i still want everyone to keep an eye on the general review inbox
21:19:51 <ihrachys> I mean, maybe we can squash your query into existing board and advertise using the board
21:19:53 <kevinbenton> so we all have a good view of what's going on
21:20:00 <kevinbenton> and so we don't miss patches from people less familiar with our process
21:20:17 <trevormc> What I noticed about the reviewday link is that med-low importance bugs fall through the cracks.
21:20:28 <mlavalle> kevinbenton: we have links in this page https://docs.openstack.org/developer/neutron/dashboards/index.html
21:20:43 <mlavalle> not exactly what you stated above, but pretty close
21:21:03 <mlavalle> I find it useful
21:21:05 <kevinbenton> right
21:21:13 <kevinbenton> i might just want to update that page with another link
21:21:19 <kevinbenton> the query is something like this
21:21:45 <kevinbenton> project:openstack/neutron status:open NOT owner:self NOT label:Workflow<=-1 label:Verified>=1,jenkins NOT label:Code-Review>=-1,self
21:22:10 * ihrachys makes notes
21:22:27 <mlavalle> kevinbenton: you plan to do that? if not I can do it over the next couple of days
21:22:28 <trevormc> Thats the "passed jenkins, no negative feedback" table
21:23:00 <kevinbenton> trevormc: ah
21:23:00 <trevormc> https://review.openstack.org/#/q/status:open+NOT+label:Code-Review%253E%253D0%252Cself+label:Verified%253E%253D1%252Cjenkins+NOT+label:Code-Review%253C%253D-1+NOT+label:Workflow%253C%253D-1+project:openstack/neutron
21:23:21 <mlavalle> trevormc, kevinbenton which is the first link in the page I pijnted above
21:23:34 <mlavalle> it is included in there
21:23:38 <kevinbenton> oh perfect
21:23:40 <kevinbenton> ok
21:23:54 <kevinbenton> so i'll just send out an email indicating that I want to keep that list small at all times
21:24:15 <mlavalle> kevinbenton: keep in mind that page has several tables
21:24:18 <mlavalle> all useful
21:24:19 <kevinbenton> then what I want to do is get an IRC bot to harass us for the older stuff
21:24:45 <kevinbenton> ok
21:25:16 <kevinbenton> #topic OVO backwards compatibility
21:25:36 <kevinbenton> ihrachys has a couple of patches dropping the downgrading logic on the OVO objects
21:25:57 <ihrachys> like https://review.openstack.org/456637 or https://review.openstack.org/456665
21:26:54 <ihrachys> which would make sense if we assume that we only run against agents that use latest object as defined. if for some reason there is a component that may want to use older representation in newer versions, we may pull the rug from under them.
21:27:15 <ihrachys> so far we assumed that consumers of RPC callbacks (and hence old object versions) are internal to ml2 and our own agents
21:27:17 <kevinbenton> and what i had suggested is that we may want to keep that logic if we offer OVO through any kind of public interface
21:27:22 <ihrachys> so killing the code would be fine
21:28:11 <ihrachys> I am fine with the direction, just need to advertise that a bit more in devref and ML maybe
21:28:36 <kevinbenton> ihrachys: do you foresee it causing problems
21:28:49 <kevinbenton> ihrachys: can keeping old version compatibility lock us into something?
21:28:56 <ihrachys> I actually started removing the code because slawek had some complications with adopting the tests to his new changes. so I decided to simplify his life. but that shouldn't be a stopgap for him, just a tad more work.
21:29:38 <ihrachys> kevinbenton, I don't think it should. in the end, as long as consumers have old object representation handy somewhere, they should be able to deserialize it independently from us.
21:30:05 <kevinbenton> lets leave them behind for now
21:30:18 <ihrachys> kevinbenton, (which may mean we may want to provide them with some versioned object revisions somewhere in common place, but that's not a must)
21:30:37 <ihrachys> otherwise, they can always work with json as-is.
21:31:13 <ihrachys> ok I will abandon the patches. and make slawek happy. ;)
21:31:27 <kevinbenton> ihrachys: or maybe we can extend the deprecation cycle at least a ways
21:31:39 <kevinbenton> ihrachys: like only drop the downgrade when the original version was released in EOL branch
21:32:18 <ihrachys> that may be a good middle ground
21:32:46 <ihrachys> ok I will have a look if qos would then be eligible for cleanup.
21:32:58 <ihrachys> gotta document that somewhere
21:33:07 <ihrachys> others don't have thoughts on the matter it seems?
21:34:18 <ihrachys> ok
21:34:22 <kevinbenton> moving on :)
21:34:42 <kevinbenton> #topic server_defaults in expand scripts
21:35:25 <kevinbenton> we need to always ensure that an expand script that adds a new column marks it as nullable or defines a server default
21:35:46 <kevinbenton> otherwise when an older version of the server tries to insert a record, it will fail
21:36:03 <ihrachys> were there violations, or is it PSA?
21:36:11 <kevinbenton> ihrachys: two i noticed in patches
21:36:15 <ihrachys> merged?
21:36:17 <kevinbenton> ihrachys: haven't merged yet
21:36:20 <ihrachys> ok
21:36:20 <kevinbenton> ihrachys: just in review
21:36:47 <ihrachys> ideally we would have a gate for that but infra/ops/qa seems to bail out of producing framework in grenade for that
21:37:05 <ihrachys> we may need to have a look at gate setup on our own
21:37:19 <ihrachys> it was for a long time in my (lack of) prio queue
21:37:37 <kevinbenton> ack
21:37:52 <kevinbenton> so for now we just need to closely watch in reviews
21:37:57 <mlavalle> kevinbenton: Ann also commented in my patch to include to declare server default in the model itself
21:38:34 <kevinbenton> mlavalle: yeah, it's good to keep them consistent
21:38:47 <kevinbenton> the only time that's used is creating the in-memory sqlite db
21:38:56 <mlavalle> just sharing with the team :-)
21:39:14 <kevinbenton> i will open a bug
21:39:27 <kevinbenton> we may be able to detect this in our migration validation code
21:39:55 <kevinbenton> ok
21:40:03 <kevinbenton> #topic bugs
21:40:09 <kevinbenton> who was bug deputy?
21:40:46 <trevormc> o/
21:40:48 <trevormc> i was
21:41:01 <trevormc> I just had one bug I thought would need more attention last week.
21:41:03 <kevinbenton> trevormc: any bugs to bring to everyone's attention?
21:41:06 <kevinbenton> ack
21:41:11 <trevormc> https://bugs.launchpad.net/neutron/+bug/1681784
21:41:12 <openstack> Launchpad bug 1681784 in python-neutronclient "neutronclient: incorrect treatment of input parameters" [Undecided,New]
21:41:53 <trevormc> It blocks use of heat, I just didn't know where the fix should land.
21:44:06 <kevinbenton> is this a regression?
21:44:23 <kevinbenton> on the neutron side
21:44:32 <kevinbenton> like did we used to accept None and now we don't?
21:44:46 <kevinbenton> because in that case we broke backwards compability and we should fix it
21:45:30 <trevormc> ok, makes sense.
21:45:52 <kevinbenton> trevormc: i will leave that comment on the bug
21:46:02 <trevormc> thanks
21:46:14 <kevinbenton> do we have a bug deputy for next week?
21:46:30 <trevormc> i thought we had a volunteer last week.
21:47:10 <mlavalle> yes
21:47:11 <hichihara> I guess that jlibosva will be next week
21:47:18 <kevinbenton> ok cool
21:47:20 <mlavalle> correct
21:47:34 <hichihara> sorry it's this week
21:47:51 <hichihara> We don't have it for Apr-24
21:48:18 <kevinbenton> does anyone want to volunteer for Apr 24?
21:48:26 <mlavalle> I can do it
21:48:32 <kevinbenton> mlavalle: thanks
21:48:56 <kevinbenton> #info mlavalle bug deputy for week of apr 24th
21:49:33 <kevinbenton> is anyone around to give us an update on Docs or OSC?
21:50:02 <kevinbenton> #topic neutron-lib
21:50:02 <abhiraut> for osc: we havent had an update on l3 agent and tags patches since last week
21:50:07 <kevinbenton> #undo
21:50:08 <openstack> Removing item from minutes: #topic neutron-lib
21:50:09 <kevinbenton> #topic osc
21:50:17 <abhiraut> but those are the remaining items from core list
21:50:31 <kevinbenton> ack
21:50:40 <kevinbenton> abhiraut: what's our policy on bug fixes for neutronclient?
21:50:44 <abhiraut> i will reach out to reedip and ankur to check progress
21:51:00 <kevinbenton> abhiraut: have we frozen completely at this point?
21:51:11 <abhiraut> anything thats not urgent should be pushed for OSC
21:51:35 <abhiraut> for tags..  we dont have a OSC patch.. so fixes can be allowed in neutronclient
21:51:46 <kevinbenton> abhiraut: ok
21:51:54 <kevinbenton> abhiraut: thanks
21:52:04 <abhiraut> if it exists in osc.. fix should be pushed there
21:52:22 <kevinbenton> ack
21:52:30 <abhiraut> thats it from me
21:52:36 <kevinbenton> #topic neutron-lib
21:52:51 <kevinbenton> oh no, i think we lost boden before i could get to this
21:53:25 <kevinbenton> i think the big impending change is the switch to neutron-lib's callbacks
21:53:55 <dasm> kevinbenton: boden shared his status on #openstack-neutron
21:53:57 <dasm> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2017-04-17.log.html#t2017-04-17T19:47:23
21:54:07 <dasm> "kevinbenton ihrachys others… I won’t be able to make the team meeting today. The only thing I really had to discuss for neutron-lib is the “consumption approach” for neutron-lib callbacks. But I think we can have this discussion on the patch https://review.openstack.org/#/c/439146/"
21:54:18 <kevinbenton> dasm: thanks, was looking for that link
21:54:23 <kevinbenton> #topic open discussion
21:54:30 <kevinbenton> any last minute high priority items?
21:54:42 <dasm> i put my topic on agenda.
21:54:55 <kevinbenton> dasm: u have 5 mins, go :)
21:55:01 <dasm> unfortunately, i won't be able to fulfill release liaison role any longer.
21:55:06 <dasm> so, we need to find someone else
21:55:18 <dasm> or, like united airlines, we can "volunteer" someone to this role
21:55:38 <kevinbenton> dasm: will you be working on neutron at all?
21:55:40 * ihrachys puts a helmet on
21:56:00 <kevinbenton> to help with transition
21:56:10 <dasm> kevinbenton: i don't think so. but i should stick around for some time
21:56:23 <kevinbenton> ok
21:56:44 <kevinbenton> dasm: can you send an email with [neutron] tag to the dev list asking if anyone is interested?
21:56:53 <dasm> kevinbenton: sure, will do
21:56:58 <kevinbenton> dasm: thanks
21:58:04 <ihrachys> dasm, thanks for all the work
21:58:27 <kevinbenton> ++
21:58:30 <kevinbenton> ok
21:58:34 <dasm> next person will have some time to dive into the details. we just released everything, so it should be simpler :)
21:58:57 <mlavalle> dasm: thanks for all your efforts
21:59:23 <hichihara> ++
21:59:26 <kevinbenton> ok, have a good day everyone
21:59:30 <kevinbenton> #endmeeting