14:00:21 <jlibosva> #startmeeting networking
14:00:22 <openstack> Meeting started Tue Apr 10 14:00:21 2018 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:26 <openstack> The meeting name has been set to 'networking'
14:00:29 <jlibosva> Hi everybody
14:00:29 <mlavalle> o/
14:00:33 <annp_> hi jlibosva
14:00:34 <hongbin> o/
14:00:36 <slaweq> hi
14:00:38 <lajoskatona_> o/
14:00:44 <annp_> hi
14:00:50 <jlibosva> #topic Announcements
14:01:07 <rubasov> hello
14:01:13 <pasuder> hello
14:01:23 <jlibosva> The Rocky 1 milestone is approaching, should be done in the week of Apr 16
14:01:25 <jlibosva> #link https://releases.openstack.org/rocky/schedule.html#r-1
14:01:51 <amotoki> hello
14:02:14 <jlibosva> and so is Vancouver Summit where will be the usual The Forum, which is still collecting ideas
14:02:15 <jlibosva> #link http://forumtopics.openstack.org/
14:02:29 <jlibosva> The deadline is the end of this week
14:02:41 <jlibosva> so if you have a topic you think should be discussed there, feel free to propose it
14:02:41 <mlavalle> I have a few ideas that I am going to propose
14:03:10 <jlibosva> I also see mlavalle started an etherpad to collect topics Neutron rleated
14:03:13 <jlibosva> #link https://etherpad.openstack.org/p/YVR-neutron-brainstorming
14:03:53 <jlibosva> Next thing I wanted to highlight is this email from openstack-dev ML related to Zuul
14:03:55 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129217.html
14:04:20 <jlibosva> and the last announcement I see on the wikipage is that we're looking for release team liaison
14:05:05 <jlibosva> More information about the role can be found here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management
14:05:08 <mlavalle> yeap, armax will be transiotioning out of that role soon
14:05:22 <jlibosva> :(
14:05:25 <jlibosva> that's all from my side
14:05:29 <mlavalle> he will provide guidance to the new person during the transition
14:05:33 <jlibosva> mlavalle: do you have anything else to announce?
14:05:40 <mlavalle> Nope
14:05:42 <amotoki> I can volunteer it for the release liaison if nobody is interested in it.
14:05:47 <jlibosva> amotoki++
14:06:02 <mlavalle> amotoki: great! Thank you!
14:06:12 <jlibosva> anybody else has anything to announce here?
14:06:33 <jlibosva> ok, let's move on then :)
14:06:40 * mlavalle is happy our releases will be in good hands :-)
14:06:40 <jlibosva> #topic Blueprints
14:06:59 <jlibosva> current blueprints for this milestones can be found here:
14:07:01 <jlibosva> #link #link https://launchpad.net/neutron/+milestone/rocky-1
14:07:03 <jlibosva> #link https://launchpad.net/neutron/+milestone/rocky-1
14:07:10 <jlibosva> way too much #links :)
14:07:18 <mlavalle> LOL
14:08:05 <mlavalle> I want to note that last week I added https://blueprints.launchpad.net/neutron/+spec/neutron-lib-decouple-db
14:08:13 <pasuder> For last few weeks I did not touch this adoption of existing subnet into a subnetpool.. sorry for that.
14:08:20 <mlavalle> per boden's request
14:08:56 <mlavalle> in that blueeprint there is a gerrit topic
14:09:10 <mlavalle> if you click on it you will see the patches under reviw
14:09:25 <mlavalle> at the top you will see a couple of specs
14:09:36 <mlavalle> That I +2ed last week
14:09:45 <mlavalle> if you have time, please check them out
14:09:52 <mlavalle> and give your feedback
14:10:01 <amotoki> .... I forgot to review them after PTG.
14:10:25 <bcafarel> late o/
14:10:30 <jlibosva> bcafarel: \o/
14:10:32 <mlavalle> I also added https://blueprints.launchpad.net/neutron/+spec/extend-logging-to-fwassv2.0
14:10:41 <mlavalle> last week
14:11:05 <mlavalle> annp_: Is that something you care about ^^^?
14:11:29 * mlavalle welcomes bcafarel
14:11:40 <jlibosva> I think it's hoangcx who's working on it, no? ^^
14:12:00 <mlavalle> jlibosva: yesh, I think you are right
14:12:09 <mlavalle> anyway, it is visible now in our dashboard
14:12:14 <jlibosva> cool :)
14:12:35 <jlibosva> I plan to keep an eye on that one as it's related to logging I reviewed last cycle
14:12:37 <mlavalle> pasuder: thanks for the update. let us know if we can help in any way
14:12:46 <annp_> mlavalle, hoangcx and cuongnv who are main responsible for that
14:12:49 <pasuder> mlavalle
14:12:51 <pasuder> ok
14:12:57 <reedip> o/
14:12:57 <amotoki> https://review.openstack.org/#/q/topic:bug/1720727 looks a better link
14:13:01 <toshii> this time it's iptables isn't it. ;)
14:13:11 <amotoki> which includes neutron-fwaas
14:13:29 <mlavalle> I also want to give a quick update on https://blueprints.launchpad.net/neutron/+spec/live-migration-portbinding
14:14:16 <mlavalle> as of last week, I tested in my dev environent activating bindings and moving the port to the activated host
14:14:29 <mlavalle> this was done from ovs to ovs
14:14:42 <mlavalle> and it works fine with the current version of the code
14:15:32 <mlavalle> Yesterday a setup everythin to do the same from OVS to LB and back
14:15:46 <mlavalle> I will be testing it the rest of this week
14:16:13 <amotoki> interesting, you tested from ovs to LB and back before LB to LB :)
14:16:15 <jlibosva> mlavalle: just a personal note that OVS + iptables fw driver to OVS + ovs fw driver would be also an interesting use case :)
14:16:29 <pasuder> I need to leave meeting right now, sorry, bye!
14:16:43 <jlibosva> pasuder: o/
14:16:49 <mlavalle> amotoki: I'll still test LB to LB
14:16:58 <mlavalle> jlibosva: good advice, thanks
14:17:13 <slaweq> mlavalle: what about sr-iov to/from ovs/lb ?
14:17:24 <slaweq> will You test it also or it's not the case here?
14:17:41 <mlavalle> slaweq: yeah, that also needs to be tested. taking bay steps for the time being
14:17:55 <slaweq> k
14:18:00 <mlavalle> moving from ovs to lb will show we can change backend
14:18:20 <mlavalle> pasuder: np, good night!
14:18:44 <amotoki> but it sounds challenging to migrate SR-IOV from/to normal virt driver(s) as it requires VM side support
14:19:03 <mlavalle> yeah, it won't be trivial
14:19:52 <amotoki> perhaps we can focus on migrations among virt drivers like ovs-fw, ovs iptables and LB.
14:20:04 <mlavalle> that is an option
14:20:13 <amotoki> * as first step
14:20:20 <mlavalle> of course
14:20:25 * jlibosva nods
14:20:35 <slaweq> I agree :)
14:21:21 * mlavalle will stop hogging the blueprints topic now
14:21:21 <jlibosva> anything else related to BPs?
14:21:40 <boden> jlibosva hi
14:21:45 <jlibosva> boden: hi
14:21:50 <amotoki> annp_: do you want to share your progress/status on https://blueprints.launchpad.net/neutron/+spec/run-in-wsgi-server ?
14:22:14 <boden> jlibosva a friendly reminder that the decouple db plubming patches are out for review (https://review.openstack.org/#/q/topic:bp/neutronlib-decouple-db+(status:open+OR+status:merged))
14:22:32 <mlavalle> boden: I covered that already
14:22:46 <boden> mlavalle: ack sorry I just joined
14:22:51 <mlavalle> and highlighted the specs
14:23:01 <annp_> amotoki, actually, I'm still get stuck with neutron-rpc-server
14:23:13 <jlibosva> rather to have it highlighted twice than zero :)
14:23:24 <mlavalle> absolutely +++
14:23:40 <boden> my bad.. this meeting time isn’t easy for me so will be  late
14:23:57 <jlibosva> boden: no worries :)
14:24:02 <mlavalle> ++
14:24:05 <annp_> today, I have discussed with amotoki about that. I will dig more the amotoki's point. So I think no worth thing to mention here.
14:24:07 <jlibosva> annp_: do you need any help with the rpc server?
14:24:26 <annp_> This week I will spend more time for this task
14:24:29 <jlibosva> ok, so seems like amotoki is helping out :) nice
14:24:34 <annp_> So please go ahead!
14:24:41 <jlibosva> ok, I think we can move on now
14:24:43 <jlibosva> #topic Community Goals
14:25:30 <jlibosva> is there anything related to community goals that anybody wants to inform us about?
14:25:43 <mlavalle> just highlight the RFE in the wiki
14:26:05 <slaweq> about mutable configs I think we are done
14:26:20 <slaweq> patch is merged to neutron-dynamic-routing and neutron repos
14:26:20 <mlavalle> slaweq: Nice! Thanks!
14:26:45 <mlavalle> the RFE I want to highlight is:  https://bugs.launchpad.net/neutron/+bug/1745192
14:26:46 <openstack> Launchpad bug 1745192 in neutron "Can't create a vlan transparent network in mixed driver environment" [Wishlist,Confirmed]
14:26:46 <slaweq> it wasn't necessary anywhere else, I send patch neutron-lbaas also but I don't know if they will accept it
14:27:12 <mlavalle> itthat RFE is deemed to be good for beginners
14:27:21 <mlavalle> and it's up for grabs
14:27:33 <mlavalle> we have had good success with this section
14:27:50 <mlavalle> all the RFEs that we hav highlighted have been taken
14:28:03 <jlibosva> mlavalle: so I think you're talking now about the starter RFEs, right? :)
14:28:06 <mlavalle> the last one was taken by hongbin, thanks!
14:28:22 <mlavalle> jlibosva: duhhh, yeah
14:28:26 <mlavalle> sorry about that
14:28:31 <annp_> jlibosva, thank you so much. I'll reach out you on neutron channel later. :)
14:28:55 <amotoki> mox removal is good progress. the last one is networking-midonet and we are waiting for the merge.
14:28:57 <mlavalle> so carry on with community goals
14:29:15 <amotoki> policy-in-code is a bit slow-progress due to my busy life...
14:29:39 <jlibosva> I have no updates on py3 front, I was OOO last week but I plan to dig into it. I saw the oslo.rootwrap issue with eventlet is stall
14:29:41 <amotoki> i will to move this forward next two weeks, but if it fails I will raise it here
14:29:59 <amotoki> *will try to move*
14:30:08 <boden> FYI: I think there’s some related discussion on the plumbing for this on https://review.openstack.org/#/c/539281/
14:30:43 <amotoki> boden: yeah, thanks for your comments.
14:30:59 <amotoki> it seems reasonable to move the policy stuff to me now.
14:32:46 <jlibosva> thanks boden for highlighting it here
14:32:53 <jlibosva> anybody else has anything related to community goals?
14:33:23 <jlibosva> I think we can move on then :)
14:33:36 <jlibosva> #topic Starter Approved RFEs
14:33:51 <mlavalle> I already jumped the gun with this topic
14:33:54 <jlibosva> #link https://bugs.launchpad.net/neutron/+bug/1745192
14:33:55 <openstack> Launchpad bug 1745192 in neutron "Can't create a vlan transparent network in mixed driver environment" [Wishlist,Confirmed]
14:34:02 <jlibosva> I'll just leave the link here for the meeting minutes :)
14:34:09 <mlavalle> yeap, thanks!
14:34:41 <jlibosva> is there anything else to be added or shall me move on?
14:34:49 <mlavalle> let's move on
14:34:54 <jlibosva> k
14:34:56 <jlibosva> #topic Bugs
14:35:37 <jlibosva> lujinluo was bug deputy last week
14:35:44 <jlibosva> he sent out a report earlier
14:35:47 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129197.html
14:36:29 <mlavalle> she sent.... ;-)
14:36:39 <jlibosva> oh ... my apologies
14:36:45 * jlibosva blushes
14:36:55 <jlibosva> so I think from the report we should prioritize https://bugs.launchpad.net/neutron/+bug/1760047
14:36:55 <openstack> Launchpad bug 1760047 in neutron "some ports does not become ACTIVE during provisioning" [Undecided,Confirmed]
14:37:28 <mlavalle> yeah
14:37:39 <mlavalle> we should take a look at that one
14:38:18 <jlibosva> it has a good troubleshooting in the comments, I would say this is a high importance?
14:38:31 <mlavalle> Agree
14:39:24 <jlibosva> ok, then we have two bugs that are not triaged: https://bugs.launchpad.net/neutron/+bug/1761555
14:39:25 <openstack> Launchpad bug 1761555 in neutron "[dvr][fast-exit] router add/remove subnet operations are not idempotent" [Medium,New]
14:39:37 <jlibosva> and https://bugs.launchpad.net/neutron/+bug/1761591
14:39:39 <openstack> Launchpad bug 1761591 in neutron "[dvr] enable_snat attribute is ignored - centralized snat port gets created" [Undecided,New]
14:39:47 <jlibosva> Swami is helping there
14:40:18 <mlavalle> we can discuss those two during the L3 meeting on THursday
14:40:30 <mlavalle> they will come up there
14:40:33 <jlibosva> ok, thanks
14:40:54 <jlibosva> all other bugs from the report seem to be triaged well
14:40:57 <mlavalle> and the RFE is actually the result of the Neutron Drivers meeting discussion last Friday
14:41:04 <jlibosva> the bug deputy for this week is yamamoto
14:41:24 <jlibosva> does anybody know if he's aware of it? he's not online now
14:41:25 <mlavalle> mhhhh, amotoki and I know he travelling in Barcelona this week
14:41:31 <jlibosva> oh
14:41:45 <mlavalle> so, I will assume I will do his duty next week
14:41:49 <jlibosva> then maybe he won't have time for triaging?
14:41:52 <mlavalle> and he can do mine next week
14:42:03 <jlibosva> mlavalle: sounds great :) thanks
14:42:23 <jlibosva> anybody has anything else wrt bugs?
14:42:23 <mlavalle> yes, mlavalle is bugs deputy this week
14:42:29 <amotoki> or can we expect he can triage bugs during travelling :p
14:42:51 <jlibosva> I'm sure he'll be jetlagged so he could do that instead of sleeping :-p
14:43:04 <jlibosva> ok, moving on :)
14:43:17 <jlibosva> #topic Docs
14:43:26 <jlibosva> amotoki: boden do you have any updates regarding docs?
14:43:40 <amotoki> none from me
14:43:41 <boden> jlibosva nothing exciting that I’m aware of
14:43:45 <jlibosva> ok, thanks
14:43:56 <jlibosva> jumping to the next topic
14:43:58 <jlibosva> #topic neutron-lib
14:44:34 <boden> that’s me I suppose
14:44:41 <jlibosva> boden: how about neutron-lib beside those decouple db patches :)
14:44:43 <jlibosva> yeah :)
14:45:11 <boden> the only other thing I wanted to mention is that I’d like to rehash the topic of “rehoming neutron.common.rpc” into lib…
14:45:28 <boden> I’ve updated https://review.openstack.org/#/c/319328/  with some comments/code…
14:45:47 <boden> looking for some agreement on this before spending mroe time… so if folks get time please add your 2 cents
14:46:02 <boden> and that’s if from me on the lib topic
14:46:33 <mlavalle> that's an oldie
14:46:42 <boden> mlavalle ya, I’m oldschool man
14:47:14 <boden> mlavalle: IMO it makes sense to rehome it, but interested in what others think
14:47:25 <boden> if you want me to bring it up at drivers meeting I can try to attend when/if needed
14:47:26 <mlavalle> cool, will take a look
14:47:29 <boden> thanks
14:47:41 <jlibosva> thanks boden for updates
14:47:59 <jlibosva> #topic CLI/SDK
14:48:07 <jlibosva> amotoki: hi, do you have any updates here?
14:48:12 <amotoki> let me paste some.
14:48:20 <amotoki> https://etherpad.openstack.org/p/neutron-openstacksdk-migration is not necessarily targeted to Rocky. It is a best-effort topic.
14:48:27 <amotoki> it is a good starter thing. If you are interested in it, feel free to add your name to the etherpad. slaweq and I can help you.
14:48:37 <amotoki> this is just call for volunteers :)
14:48:39 <amotoki> that's all.
14:49:04 <jlibosva> ok, thanks :)
14:49:30 <slaweq> just FYI: trunk support is merged to SDK already
14:49:55 <amotoki> yeah, thanks slaweq. we need to update the etherpad :)
14:50:07 <slaweq> yes, I forgot about it, sorry
14:50:11 <amotoki> np
14:50:14 <slaweq> will do it right now
14:50:50 <slaweq> updated
14:51:24 <jlibosva> thanks guys
14:51:29 <jlibosva> anything else related to CLI or SDK?
14:52:03 <jlibosva> ok, jumping to the open agenda
14:52:07 <jlibosva> #topic Open discussion
14:52:38 <annp_> Regarding to https://blueprints.launchpad.net/neutron/+spec/extend-logging-to-fwassv2.0
14:52:45 <jlibosva> I see toshii left a topic about future plans for ryu that has been discussed at the last meeting but I'd like to bring it back again so people that can't attend US meeting are aware of it
14:52:46 <annp_> I have some update.
14:52:46 <annp_> Currently, I and FwaaS team are focusing to review spec https://review.openstack.org/#/c/509725/. and the spec is targeted to merge in R-1, I think the spec is quite close. However it should get more comment from you So please take a look at this.
14:52:49 <jlibosva> #link https://etherpad.openstack.org/p/neutron-ryu-future-plans
14:52:53 <toshii> I remind you to think about future of the ryu library if you haven't. ;)
14:53:04 <toshii> jlibosva, thanks for bringing this up
14:53:05 <annp_> In addtion,  There are two patch https://review.openstack.org/#/c/534227/ and https://review.openstack.org/#/c/529814/ also need your comments.
14:53:10 <jlibosva> that's all :) sorry annp_, go ahead
14:53:11 <mlavalle> toshii: I will propose this week the topic for the Forum
14:53:12 <jlibosva> toshii: ;)
14:53:19 <jlibosva> that's a good idea
14:53:33 <annp_> jlibosva, that's all from me.
14:54:12 <jlibosva> annp_: I think those rpc patches will need some thought about backward compatibility. I'll comment on it
14:54:21 <annp_> jlibosva, Just my update for extend firewall logging blueprint.
14:54:39 <jlibosva> annp_: thanks for bringing this up
14:55:30 <amotoki> toshii: it would be nice if there are inputs on what kind of knowledges or backgrounds are required /expected on ryu maintenance. it might help discussoins.
14:55:36 <annp_> jlibosva, thanks in advance.
14:56:05 <toshii> ryu is quite stable these days IMO
14:56:19 <toshii> i'll add to the etherpad
14:56:34 <annp_> toshii, +1
14:56:45 <amotoki> transitions in the maintenance team is not surprising. it is nice this kind of thing is raised in the right timing :)
14:57:06 <toshii> dealing with brekage due to  dependency library would be the main maintenance work
14:57:21 <toshii> like pbr or pip as we saw recently
14:57:30 <jlibosva> or adopting new openflow standards? ;)
14:58:18 <jlibosva> any other topic anybody wants to discuss here? we have 2 minutes left
14:58:26 <toshii> standards are not changing. it's just ryu hasn't implemented everything
14:58:32 <amotoki> another topic: did we discuss http://lists.openstack.org/pipermail/openstack-dev/2018-March/128335.html ?
14:58:46 <jlibosva> we didn't
14:58:53 <amotoki> it is related to some release model and neutron-lib.
14:59:13 <amotoki> i think sub project developers need extra steps to run tests.
14:59:21 <amotoki> hopefully we can discuss it after rocky-1.
14:59:34 <jlibosva> ack
14:59:46 <jlibosva> amotoki: we could also put it as the item to open agenda for the next meeting
14:59:51 <jlibosva> to not forget :)
14:59:52 <amotoki> this is just a reminder for coming weeks
14:59:56 <amotoki> jlibosva: sure
14:59:58 <jlibosva> aaaand we're out of time
15:00:05 <jlibosva> thanks everyone for showing up :)
15:00:08 <jlibosva> #stopmeeting
15:00:09 <mlavalle> o/
15:00:16 <jlibosva> eh
15:00:18 <jlibosva> #endmeeting