21:00:04 <mlavalle> #startmeeting networking
21:00:05 <openstack> Meeting started Mon Apr 16 21:00:04 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:08 <openstack> The meeting name has been set to 'networking'
21:00:19 <mlavalle> Hi there!
21:00:26 <slaweq> hi
21:00:38 <haleyb> hi
21:01:32 <mlavalle> Agenda for today is here:
21:01:39 <mlavalle> #link https://wiki.openstack.org/wiki/Network/Meetings
21:01:52 <mlavalle> Let's get rolling
21:02:00 <mlavalle> #topic Announcements
21:02:38 <mlavalle> First of all, this week we are going to be cutting Rocky-1
21:03:17 <mlavalle> amotoki has voluntereed to be our release team liaison going forward
21:03:52 <mlavalle> #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129358.html
21:04:21 <mlavalle> We thank armax for all the help he gave us on this topic over the past few cycles
21:04:55 <armax> amotoki+++++++++++
21:05:01 <mlavalle> I will keep bugging him for guidance on many topics
21:05:53 <mlavalle> In updating the the liaisons page I came across some positions that needed to be updated
21:06:23 <mlavalle> Specifically, we are looking for a volunteer to be our liaison with the QA team
21:06:57 <mlavalle> I put my name in that slot for the time being, while a we wait for a brave sould to volunteer for the position
21:07:53 <mlavalle> We ended up proposing four Neutron related topics for the Vancouver Forum. Links are in the meeting wiki
21:09:20 <mlavalle> I started an etherpad for people attending the Vancouver Summit to register, so we know the team members that will be there:
21:09:27 <mlavalle> #link  https://etherpad.openstack.org/p/YVR-neutron-atendees
21:09:52 <mlavalle> The plan is also to have a social event on Tuesday 22nd
21:10:20 <mlavalle> Traditionally we have our social event on Thursday, but on this ocassion the Summit ends Thursday evening
21:10:40 <mlavalle> So I assumed a lot of people might not stick around that night
21:11:20 <mlavalle> Any other annoouncements from the team?
21:12:24 <mlavalle> ok, moving on
21:12:31 <mlavalle> #topic Blueprints
21:13:17 <mlavalle> These are the blueprints and bugs that we are targeting for Rocky-1:
21:13:30 <mlavalle> #link https://launchpad.net/neutron/+milestone/rocky-1
21:14:09 <mlavalle> This week I will be chacking status with the assignees to see progress and roll over what was not finished to R-2
21:14:54 <mlavalle> Does anyone want to bring any blueprint for discussion today?
21:16:31 <mlavalle> boden: in regards to the decoupling of the DB layer to neutron-lib, I want to mention that last night I merged https://review.openstack.org/#/c/509564/ and https://review.openstack.org/#/c/473531/
21:16:32 <patchbot> patch 509564 - neutron-specs - decouple neutron db models and ovo for neutron-lib (MERGED)
21:16:33 <patchbot> patch 473531 - neutron-specs - rehome db api and utils into neutron-lib (MERGED)
21:16:59 <boden> mlavalle ack and thanks.. the lib (code) patches are out there too
21:17:38 <mlavalle> for the other memebers of the team, this is the gerrit topic for the decoupling of the DB layer:
21:17:45 <mlavalle> #link https://review.openstack.org/#/q/topic:bp/neutronlib-decouple-db,n,z
21:18:12 <mlavalle> I encourage the team to take a look and help reviewing this
21:19:07 <mlavalle> Does anyone else have any other blueprints to bring up?
21:20:11 <mlavalle> In regards to https://blueprints.launchpad.net/neutron/+spec/adopt-oslo-versioned-objects-for-db
21:20:36 <mlavalle> we have a subsection of the agenda to track the progress and pending work
21:21:31 <mlavalle> The OVO sub-team keeps a very detailed spreadsheet of what work is left to be done in the adoption of OVO in Neutron:
21:21:38 <mlavalle> #link https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
21:21:59 <mlavalle> As you will see there, there is good chunk left to be done
21:22:15 <mlavalle> So make your pick and help with this topic
21:23:09 <mlavalle> This subteam holds a weekly IRC meeting. These are the meeting details:
21:23:15 <slaweq> great list - thx
21:23:28 <mlavalle> #link http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting
21:24:12 <mlavalle> so if you are interested in helping with OVO, join lujinluo and her gang. They will welcome you with open arms ;-)
21:24:46 <mlavalle> ok, moving on
21:25:00 <mlavalle> #topic Community goals
21:25:48 <mlavalle> Does anybody have updates on community goals?
21:26:17 <slaweq> I just wanted to mention that https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html can be IMO consider as done
21:27:12 <mlavalle> slaweq: you read my mind. I was going to ask exactly that
21:27:23 <slaweq> mlavalle: :D
21:28:02 <boden> and there is no impact to decoupled plugin projects as part of that?
21:28:18 <mlavalle> slaweq: so I will update the storyboard and indicate we are done
21:28:35 <slaweq> I think that storyboard is updated automatically
21:28:53 <slaweq> if You are talking about this one: https://storyboard.openstack.org/#!/story/2001545 :)
21:29:01 <mlavalle> you are are right, it shows merged
21:29:06 <slaweq> it's marked as "merged" for neutron and neutron-dynamic-routing
21:29:28 <mlavalle> slaweq: any answer to boden ^^^^
21:29:31 <mlavalle> ?
21:29:57 <slaweq> boden: only neutron-dynamic-routing required such change
21:30:10 <slaweq> there is no impact for other plugins AFAIK
21:30:21 <boden> slaweq: did you only check stadium plugins?
21:30:51 <slaweq> boden: do You mean if I looked for stadium plugins if same change is required there?
21:31:02 <slaweq> like for midonet for example?
21:31:16 <mlavalle> he is concerned about projects outside the stadium
21:31:24 <boden> slaweq: what I’m trying to understand is if I’m a non-stadium plugin, should there be any TODOs for me as part of this?
21:31:51 <slaweq> AFAIK non-stadium projects are not official OpenStack projects right?
21:32:05 <boden> slaweq: you’re talking politics now
21:32:11 <slaweq> if so, then they don't have to do it - they can if they want
21:32:12 <mlavalle> They are OpenStack projects
21:32:25 <slaweq> ok, so what I did was:
21:32:32 <mlavalle> but they are not in the Stadium
21:32:55 <slaweq> I checked via http://codesearch.openstack.org for all "neutron-X" or "networking-X" projects if such change would be necessary there
21:33:05 <mlavalle> boden: let's assume you need to dig in regards to the specific non stadium project you are concerned about
21:33:33 <boden> mlavalle: sure, would’ve been nice to see a note or something though with some pointers and such
21:34:09 <slaweq> I didn't found any projects which required such change there except neutron-dynamic-routing and neutron-lbaas
21:34:16 <slaweq> but I might missed something
21:34:39 <boden> I will dig, there are projects that don’t have networking or neutron in the name
21:35:03 <slaweq> boden: so sorry if I missed them
21:35:05 <mlavalle> slaweq: would you send a message to ML with the current status, what you found in your code search and what would be the steps if a non Stadium project needs to take care of this?
21:35:16 <boden> I think my point is we need to try and think broader than just stadium projects; we have non-stadium projects that are coupled with neutron and used in production
21:35:28 <boden> I’m done ranting now
21:35:35 <slaweq> mlavalle: sure, I will send such email
21:35:48 <mlavalle> boden: you point is well taken
21:36:16 <mlavalle> will the message to the ML be useful, boden?
21:36:56 <boden> mlavalle if there’s potential for impact, then IMHO yes
21:37:41 <mlavalle> slaweq: thanks for your work, the update and the message to the ML :-). Good job
21:37:57 <slaweq> no problem :)
21:38:01 <boden> slaweq yes thanks! I’m just trying not to be broken over here :)
21:38:24 <slaweq> boden: I fully understand. Thanks for taking care of it :)
21:38:50 <mlavalle> ++
21:38:59 <mlavalle> ok, let's move on
21:39:14 <mlavalle> #topic Bugs
21:39:27 <mlavalle> I was the bugs deputy last week
21:39:38 <mlavalle> It was a more or less quite week
21:40:21 <mlavalle> I spent time exchanging messages in several bugs where I ended up providing installation support
21:41:17 <mlavalle> We had one critical bug: https://bugs.launchpad.net/neutron/+bug/1762414
21:41:18 <openstack> Launchpad bug 1762414 in neutron "Unable to create a FIP when L2GW is enabled" [Critical,In progress] - Assigned to Gary Kotton (garyk)
21:41:36 <mlavalle> It is being taken care by garyk
21:42:30 <mlavalle> I also asked slaweq help triaging https://bugs.launchpad.net/neutron/+bug/1762736
21:42:31 <openstack> Launchpad bug 1762736 in neutron "Iptables firewall driver adds forward rules for trusted ports only in the ingress direction" [Undecided,In progress] - Assigned to Nikita Gerasimov (nikita-gerasimov)
21:42:41 <mlavalle> Which he is doing, thanks :-)
21:43:07 <slaweq> Your welcome
21:43:20 <mlavalle> Are there any other bugs that we should discuss in the meeting?
21:44:26 <mlavalle> ok
21:45:09 <mlavalle> Our bugs deputy calendar says that I will be on duty this week. But I exchanged my duty with yamamoto, because he was travelling last week
21:45:30 <mlavalle> so yamamoto is this week's deputy
21:46:01 <mlavalle> I will also be rolling over the calendar, so please watch out for your next duty week
21:46:40 <mlavalle> #topic Bugs
21:46:56 <mlavalle> #undo
21:46:57 <openstack> Removing item from minutes: #topic Bugs
21:47:07 <mlavalle> #topic Docs
21:48:41 <boden> hi so it might be worth mentioning http://lists.openstack.org/pipermail/openstack-dev/2018-April/129394.html  some projects sphinx doc builds are likely failing
21:48:47 <mlavalle> I am trying to keep up with the patches submitted by Michal, hongbin_ and boden
21:49:05 <boden> ^^ for stable builds
21:49:42 <mlavalle> boden: thanks for bringing it up
21:50:11 <mlavalle> boden: please also tell Michal he is doing a good job documenting all those missing APIs
21:50:24 <boden> mlavalle will do
21:50:53 <mlavalle> boden: are you and he aware that the multiprovider network api is missing?
21:51:41 <boden> mlavalle I wasn’t and I don’t see it here https://bugs.launchpad.net/neutron/+bugs?field.tag=api-ref
21:52:09 <mlavalle> boden: I can file a bug and assign it to her if that helps
21:52:27 <boden> mlavalle if you don’t mind; just easier to track
21:52:34 <mlavalle> will do
21:52:46 <mlavalle> #topic neutron lib
21:53:45 <mlavalle> any updates boden ?
21:53:59 <boden> I just quickly want to mention that for most projects you can no longer run py27/pep8 etc locally with master branches due to neutron and others now being versioned
21:54:35 <boden> so this has been impacting my local testing of lib changes
21:54:54 <Straemer> is this a linux based routing channel?
21:55:04 <mlavalle> Straemer: no
21:55:51 <mlavalle> boden thanks
21:56:03 <mlavalle> moving on
21:56:18 <mlavalle> #topic CLI / SDK
21:56:25 <mlavalle> amotoki: you around?
21:57:07 <mlavalle> ok
21:57:14 <mlavalle> #topic Open Agenda
21:57:23 <mlavalle> Does any one have any other topic?
21:57:29 <Straemer> are we talking Computer IP networking
21:58:31 <mlavalle> ok, Thanks for attending the meeting. Have a nice week!
21:58:36 <mlavalle> #endmeeting