14:00:44 <jlibosva> #startmeeting networking
14:00:45 <openstack> Meeting started Tue Jan 16 14:00:44 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:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:46 <jlibosva> hi everyone
14:00:49 <openstack> The meeting name has been set to 'networking'
14:00:52 <mlavalle> o/
14:00:52 <amotoki> hi
14:01:05 <jlibosva> #topic Announcements
14:01:11 <slaweq> hi
14:01:18 <annp> hi
14:01:19 <jlibosva> we're approaching milestone 3, which is due Jan 25
14:01:23 <hichihara> hi
14:01:24 <jlibosva> #link https://releases.openstack.org/queens/schedule.html#q-3
14:01:26 <mlavalle> next week !
14:01:45 <jlibosva> yeah, scary :) but we will manage
14:01:53 <haleyb> hi
14:01:59 <jlibosva> I guess we'll talk more about bugs and blueprints in a dedicated topic
14:02:29 <annp> jilibosva, slaweq, mlavalle, thanks for your great help on logging.
14:02:36 <jlibosva> so about a month after the q3, there will be the PTG event in Dublin and I hope a lot of people will come :)
14:02:48 <bcafarel> hi
14:02:50 <slaweq> I will be there :)
14:02:51 <mlavalle> jlibosva: you going?
14:03:09 <jlibosva> mlavalle sent a mail to ML with a link to the etherpad to collect topics we want to discuss
14:03:11 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126055.html
14:03:21 <jlibosva> mlavalle: unfortunately I can't :( because of family reasons
14:03:34 <mlavalle> jlibosva: will miss you :-(
14:03:40 <jlibosva> but I'll be able to join remotely if possible
14:03:57 <jlibosva> and I'll buy some Guinesses I'll be drinking in the evening :)
14:04:13 <jlibosva> mlavalle: thanks :)
14:04:14 <amotoki> remote beer party :)
14:04:22 <jlibosva> anyways - here is the link to the etherpad
14:04:23 <jlibosva> #link https://etherpad.openstack.org/p/neutron-ptg-rocky
14:04:24 <annp> :)
14:04:25 <jlibosva> amotoki++
14:05:21 <jlibosva> also related to the Rocky planning topic, there is an ongoing discussion thread about community goals for Rocky. I think it's worth reading
14:05:23 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126090.html
14:05:32 <mlavalle> ++
14:05:54 <jlibosva> and the last thing I wanted to mention is that the Rocky release planning has been merged a few days ago
14:05:56 <jlibosva> #link https://review.openstack.org/#/c/528772/
14:06:27 <jlibosva> there was a discussion about making development cycles longer
14:06:34 <reedip_> o/
14:06:37 <jlibosva> but conclusion is that Rocky will still be a 6 months long
14:06:48 <jlibosva> that's all from my side
14:06:53 <jlibosva> anybody has anything to announce?
14:07:25 <mlavalle> nope, you were pretty thorough, jlibosva . thanks :-)
14:07:36 <jlibosva> cool, let's jump to blueprints then
14:07:40 <jlibosva> #topic Blueprints
14:07:53 <jlibosva> #link https://launchpad.net/neutron/+milestone/queens-3
14:09:13 <mlavalle> On the nova port bindings information for live migration I made great progress up until Tuesday of last week
14:09:22 <mlavalle> Then I slowed down a bit
14:09:39 <mlavalle> I will continuw pushing this week. But it looks tight
14:09:59 <annp> jlibosva, mlavalle, slaweq: thanks for your help on logging. There are 2 remmaining patch related to fullstack and tempest.
14:10:23 <jlibosva> mlavalle: do you need any help?
14:10:26 <mlavalle> annp: but the main funtionality is in, right?
14:10:40 <jlibosva> it is
14:10:58 <mlavalle> cool
14:11:08 <mlavalle> jlibosva: I can use some help
14:11:16 <jlibosva> annp: perhaps we could split the tempest patch into scenario and api as the api part is voting
14:11:26 <jlibosva> it would be great to get the api part in first
14:11:36 <jlibosva> I just think the split could speed up the process :)
14:11:49 <jlibosva> mlavalle: ok, we can sync after the meeting
14:11:56 <mlavalle> jlibosva: :-)
14:11:57 <annp> jlibosva, thanks, I will do that as your suggest.
14:12:22 <annp> that's all from me
14:12:34 <mlavalle> https://blueprints.launchpad.net/neutron/+spec/floating-ip-rate-limit
14:12:44 <mlavalle> is mostly in
14:13:13 <mlavalle> the remaining pieces are two:
14:13:14 <amotoki> IIRC OSC patch landed. the remaining one is doc?
14:13:31 <mlavalle> docs, which last time I looked wasn't far
14:13:46 <mlavalle> and an api tempest test
14:14:16 <mlavalle> amotoki: thanks for your help with the OSC patch :-)
14:14:22 <amotoki> no problem
14:14:34 <amotoki> regarding policy-in-code, it cannot land in Queens as it needs neutron-lib support.
14:15:08 <mlavalle> what kind of support?
14:15:11 <amotoki> I was requested from the assignee to investigate the detail but I failed due to my busy time on internal affairs.
14:15:53 <amotoki> neutron stadium projects need to inform their in-code policies to the neutron API layer
14:16:23 <mlavalle> ok
14:16:25 <amotoki> I posted neutron-lib patch but it turned out the policy loading code is now spread into neutorn-lib (context) and neutron main tree.
14:17:05 <mlavalle> thanks for the update
14:17:29 <mlavalle> as far as FWaaS V2, I don't have the latest status but I think it's done
14:17:44 <mlavalle> xgerman_: you around?
14:18:25 <jlibosva> there appears to be 3 patches still on review: https://review.openstack.org/#/q/topic:bp/fwaas-api-2+(status:open)
14:18:37 <xgerman_> O/
14:18:55 <annp> hi xgerman_\
14:19:00 <mlavalle> xgerman_: we wanted to see the status of FWaaS v2.0
14:19:02 <xgerman_> We are
14:19:17 <mlavalle> will it get finished by Q-3?
14:19:29 <xgerman_> Yes
14:19:45 <annp> xgerman_ +1
14:19:58 <xgerman_> We have enough but like some more patches to get in…
14:20:04 <amotoki> nice
14:20:07 <amotoki> if they are not critical to FWaaS v2.0 we can split them into separate blueprint(s)
14:20:29 <hichihara> I guess that FWaas v2 has L2 port in milestones but it seems abandoned https://review.openstack.org/#/c/361071/
14:20:43 <mlavalle> xgerman_: so at this point, can we consider FWaaS v2 done?
14:20:49 <xgerman_> We will do so if they slip Q-3
14:21:23 <xgerman_> Yeah
14:21:29 <mlavalle> cool!
14:21:32 <amotoki> xgerman_: what about hichihara's point?
14:21:46 <annp> hichihara, the patch regarding to iptables based implementation.
14:22:18 <xgerman_> Yes
14:22:25 <xgerman_> We are if’s
14:22:28 <hichihara> I understand. It's not in v2 scope, right?
14:22:42 <xgerman_> No, it’s all OVS
14:22:52 <xgerman_> As suggested in Atlanta
14:22:53 <hichihara> Ah, I got it.
14:22:55 <annp> xgerman_, yeah.
14:23:04 <amotoki> hmm... isn't ovs support required to make fwaas v2 work?
14:23:13 <amotoki> I am confused
14:23:14 <xgerman_> Yes
14:23:21 <mlavalle> xgerman_: congrats to you and all the fwaas team !
14:23:37 <xgerman_> We are 100% OVS
14:23:44 <xgerman_> Thanks
14:23:51 <annp> mlavalle, thanks
14:24:19 <amotoki> ah.... I got it. It is iptables-based impl. ovs-native support has been implemented.
14:24:37 <xgerman_> +1
14:24:49 <hichihara> xgerman_: thanks
14:25:12 <mlavalle> annp: you've been working hard this cycle :-)
14:25:29 <annp> mlavalle, :)
14:25:34 <hoangcx_> mlavalle: indeed :)
14:25:38 <xgerman_> +1
14:25:40 <jlibosva> annp++
14:25:52 <hichihara> annp++
14:26:05 <annp> folks++
14:26:09 <annp> :)
14:26:41 <hichihara> How about other bp?
14:26:45 <hichihara> amotoki: https://blueprints.launchpad.net/neutron/+spec/neutron-in-tree-api-ref ?
14:27:03 <jlibosva> mlavalle: I have a question regarding blueprints - if a bp misses q3, does it automatically flip to Rocky or driver team discusses it first and treats it as a new bp?
14:27:32 <jlibosva> "new" in terms of planning
14:27:39 <mlavalle> I think we are going to flip it to Rocky
14:27:46 <jlibosva> ok, thanks
14:27:47 <amotoki> re: neutron-in-tree-api-ref, I am thinking to convert the remaining todos into bugs and close it.
14:27:57 <xgerman_> Thanks
14:27:59 <mlavalle> expecially if there is sigificant progress achieved
14:28:03 <amotoki> somehow I dropped it from my todo list
14:28:08 <hichihara> amotoki: +1
14:28:28 <amotoki> my busy time on internal affairs got over today, so I can promise to clean them up.
14:28:44 <mlavalle> thanks amotoki :-)
14:28:50 <hichihara> cool
14:29:22 <amotoki> i don't know the status of https://blueprints.launchpad.net/neutron/+spec/subnet-onboard
14:29:27 <amotoki> reedip: around?
14:30:07 <jlibosva> it has this patch attached that's been untouched for a while: https://review.openstack.org/#/c/348080/
14:31:04 <mlavalle> yeah, doesn't look very promising for q-3
14:31:06 <jlibosva> I have a feeling it won't meet the q3 :)
14:31:45 <amotoki> yeah, indeed
14:32:20 <amotoki> re versioned object, i think we can check the status to ihar in the next week meeting
14:33:02 <jlibosva> sounds good
14:33:13 <jlibosva> anything else BPs related?
14:33:35 <jlibosva> let's move on then
14:33:37 <jlibosva> #topic Bugs
14:34:31 <jlibosva> the bug deputy was hichihara
14:34:35 <hichihara> I was bug deputy last week
14:34:52 <jlibosva> he sent an email with report
14:34:53 <hichihara> I reported some bugs in ML http://lists.openstack.org/pipermail/openstack-dev/2018-January/126206.html
14:34:54 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126206.html
14:35:03 <jlibosva> ah, thanks :)
14:35:09 <hichihara> jlibosva: thanks
14:35:38 <hichihara> Three high priority bugs
14:35:40 <hichihara> https://bugs.launchpad.net/neutron/+bug/1741954
14:35:42 <openstack> Launchpad bug 1741954 in neutron "create_and_list_trunk_subports rally scenario failed with timeouts" [High,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)
14:35:46 <hichihara> https://bugs.launchpad.net/neutron/+bug/1742401
14:35:47 <openstack> Launchpad bug 1742401 in neutron "Fullstack tests neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork fails often" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)
14:35:53 <hichihara> https://bugs.launchpad.net/neutron/+bug/1741889
14:35:55 <openstack> Launchpad bug 1741889 in neutron "functional: DbAddCommand sometimes times out after 10 seconds" [High,New]
14:36:27 <hichihara> There was no critical bug.
14:36:49 <jlibosva> the first one already has a fix that got almost merge
14:36:58 <jlibosva> I think it only failed because of conflict
14:37:24 <jlibosva> and the last two seem like caused by the same thing
14:37:55 <jlibosva> oh, sorry, ignore me :)
14:37:59 <jlibosva> I clicked on a wrong link
14:38:50 <hichihara> Last one is no assignee
14:38:51 <jlibosva> maybe otherwiseguy can help us with the last one 1741889
14:39:07 <hichihara> good
14:39:18 <slaweq> about 1742401 I didn't have too much time to check it yet
14:39:22 <mlavalle> it was mentioned during last week's CI meeting
14:39:36 <slaweq> but I will work on it
14:39:55 <jlibosva> worth to mention that sometimes the last one causes functional job to get stuck and then it times out on a global timeout
14:40:31 <jlibosva> slaweq: ok, thanks :)
14:40:36 <jlibosva> I'll talk to otherwiseguy
14:40:53 <mlavalle> thanks jlibosva
14:40:54 <jlibosva> garyk is the bug deputy for this week
14:41:09 <jlibosva> I saw an email that he'd like to get a backup on Friday
14:41:27 <hichihara> mlavalle: Could you check a bug https://bugs.launchpad.net/neutron/+bug/1742093 ? It's about vm-without-l3-address.
14:41:28 <openstack> Launchpad bug 1742093 in neutron "ip_allocation attribute is not accessible over REST requests" [Wishlist,Confirmed]
14:41:28 <amotoki> jlibosva: i just sent a mail
14:41:35 <jlibosva> amotoki: cool, thanks :)
14:41:49 <amotoki> i will cover from this friday
14:41:50 <mlavalle> hichihara: will do
14:42:02 <mlavalle> amotoki: thanks
14:42:02 <hichihara> mlavalle: Thanks :)
14:42:45 <jlibosva> we're quite short on time so let's move on
14:42:48 <jlibosva> #topic Starter Approved RFEs
14:43:03 <jlibosva> we still have the one rfe there so please consider it, probably for Rocky :)
14:43:08 <jlibosva> #link https://bugs.launchpad.net/neutron/+bug/1653932
14:43:09 <openstack> Launchpad bug 1653932 in neutron "[rfe] network router:external field not exported" [Wishlist,Triaged]
14:43:20 <jlibosva> #topic Docs
14:43:31 <jlibosva> I don't see boden around, amotoki do you want to give any updates?
14:43:44 <amotoki> nothing from me on docs
14:43:56 <jlibosva> ok, let's move on unless anybody has anything docs related
14:44:08 <jlibosva> #topic Transition to OSC
14:44:10 <jlibosva> amotoki: hello again :)
14:44:20 <jlibosva> any updates here?
14:44:29 <amotoki> OSC VPNaaS integration has been merged :)
14:44:33 <jlibosva> \o/
14:44:52 <amotoki> in addition, several patches are close to merge.
14:45:15 <amotoki> it is nice if some of you look at them https://review.openstack.org/#/q/status:open+project:openstack/python-neutronclient+branch:master
14:45:18 <amotoki> with +2 patch
14:46:03 <amotoki> that's all from me.
14:46:08 <mlavalle> amotoki: I will take a look
14:46:18 <amotoki> is there anything else to raise?
14:47:00 <jlibosva> amotoki: thanks for updates, I think we're good to move on
14:47:04 <amotoki> slaweq: sorry for my late. I will check you OSC patch https://review.openstack.org/515401
14:47:13 <slaweq> amotoki: thx
14:47:16 <mlavalle> hoangcx_: so the VPNaaS patch was taken care of while I was sleeping
14:47:17 <slaweq> no problem
14:47:37 <hoangcx_> mlavalle: Yeah, yamamoto took care
14:48:50 <mlavalle> he probably read our conversation of last nigh (my time)
14:49:54 <jlibosva> ok, we have 10 minutes left
14:50:21 <jlibosva> anything else to osc related?
14:50:37 <jlibosva> moving on
14:50:39 <jlibosva> #topic Neutron-lib
14:50:52 <jlibosva> as boden is around, does anybody have any updates or anything related to the lib?
14:51:04 <mlavalle> I have something to say, hang on a sec
14:52:37 <mlavalle> boden has a group of neutron-lib patches classified as requiring neutron core input:
14:52:45 <mlavalle> #link https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
14:52:56 <mlavalle> I took a stab at them over the past few days
14:53:12 <mlavalle> but if other cores have time, please give feedback
14:53:47 * mlavalle doesn't want to lead boden off the rails alone :-)
14:53:55 <hichihara> will do
14:54:28 <mlavalle> that's all I have on this regard
14:54:35 <jlibosva> mlavalle: thanks :)
14:55:00 <amotoki> note that neutron-lib freeze is this week
14:55:17 <amotoki> just FYI
14:55:32 <jlibosva> amotoki: do you know exact date?
14:55:40 <jlibosva> or day :)
14:55:48 <mlavalle> amotoki: we released last week
14:56:04 <amotoki> jlibosva: i don't know the exact day but it is usually Thursday
14:56:05 <mlavalle> and I don't think we need another one
14:56:14 <jlibosva> aha, ok, thanks
14:56:20 <amotoki> mlavalle: yes, I agree
14:56:39 <mlavalle> however, point take amotoki and I will check again with boden
14:58:12 <jlibosva> I don't see any topic in the on demand agenda section on the wiki page
14:58:17 <jlibosva> and we're running out of time
14:58:39 <jlibosva> so maybe if there is something needed to be discussed, we could do it in the #openstack-neutron channel?
14:58:53 <jlibosva> #topic Free discussion
14:58:54 <mlavalle> amotoki: do we release neutron python client this week?
14:59:25 <amotoki> mlavalle: I am okay with either, but it seems better to release it
14:59:41 <amotoki> I can prepare it
14:59:42 <mlavalle> amotoki: ok, let's coordinate with armax this week
14:59:51 <amotoki> mlavalle: sure
14:59:55 <mlavalle> :-)
14:59:58 <mlavalle> that's all
15:00:05 <jlibosva> aaaand we're out of time :) thanks everybody for coming
15:00:07 <jlibosva> #endmeeting