14:01:11 #startmeeting networking 14:01:12 Meeting started Tue Jul 31 14:01:11 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:14 hi 14:01:16 The meeting name has been set to 'networking' 14:01:16 o/ 14:01:23 o/ 14:01:24 Hey there! 14:01:26 hi 14:01:32 hi 14:01:35 howdy 14:01:46 #topic Announcements 14:02:28 We reached Rocky 3 last week. We are currently working on our rc-1 14:02:54 later, in the blueprints section, we will review the blueprints that we are targeting for rc-1 14:03:50 Today (Jul 31, 2018 23:45 UTC) the community will close the PTL nomination period 14:04:17 Here you can find the current nominations: https://governance.openstack.org/election/#how-to-submit-your-candidacy 14:04:17 o/ 14:04:37 yours truly is running for Neutron PTL 14:04:54 o/ 14:05:18 mlavalle++ 14:05:44 how can I join the neutron meeting currently underway? 14:05:47 mlavalle+100 14:06:17 Thanks :-) 14:06:24 and the Denver PTG will take place on September 10 - 14 in Denver 14:06:32 DeepakT_: you're already in it 14:06:44 ok, so thr is no bridge 14:06:45 yes, mlavalle for president (or PTL)! 14:06:52 It seems this will be the last PTG 14:06:54 DeepakT_: This is the meeting already in progress. There is no video or audio component, if that is what you are thinking. 14:07:03 ok, thanks 14:07:32 we will move back to the previous Summit format 14:07:54 I hope to see many of you in Denver! 14:08:01 I wud like to discuss an agenda item today related to Tap-as-a-service 14:08:20 Later this week I will start the etherpad 14:08:41 DeepakT_: let's discuss it at the end of the meeting, in the Open Agenda section 14:08:46 ok 14:09:15 I m joining for the first time, pls bear with me as I am not aware of the rules and regulations 14:09:25 no problem 14:09:36 Any other announcements from the team? 14:10:14 ok, let's move on 14:10:21 #topic Blueprints 14:11:02 As I mentioned before, this week we are working in our RC-1 14:11:25 which I am hoping to cut by the end of this week 14:11:47 This is what we are targeting for the rc-1: https://launchpad.net/neutron/+milestone/rocky-rc1 14:11:47 mlavalle +1 14:12:58 mlavalle, Regards to logging for firewall, we need your blessing for 3 patches except docs patch in RC1 https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1720727 We really need 3 patches in RC1 before logging patches in neutron-fwaas is getting merge. 14:13:37 annp_: yes, I am looking at those patches 14:13:53 I will go go thorugh them today and tomorrow 14:14:01 slawek, njohnston: thanks for your great reviewing on logging patches. :) 14:14:25 mlavalle, thanks a ton! :) 14:14:57 annp_: as far as wsgi suppprt we only need to merge https://review.openstack.org/#/c/584257/, right? 14:16:19 I will take that as a yes 14:16:20 mlavalle, right. But we still need to get merge devstack's patch : https://review.openstack.org/#/c/473718/ 14:16:38 annp_: I know, I'll bug them later today 14:16:54 but from the Neutron perspective we are only missing the doc 14:17:06 mlavalle and I need some investigate your concerning aslo. 14:17:19 no rush on that 14:17:32 mlavalle, thanks! 14:17:49 The other blueprint that we are targeting is https://review.openstack.org/#/q/topic:bp/port_forwarding+(status:open+OR+status:merged) 14:17:50 mlavalle, that's all from me. please go ahead. 14:18:13 As you can see, we are in pretty good shape there 14:18:32 ++ 14:18:54 haleyb: zhaobo responded to your comments here: https://review.openstack.org/#/c/574673/ 14:19:05 would you take a look and see what you think? 14:19:14 mlavalle: yes, i'll take a look, thanks 14:20:21 He also responded to https://review.openstack.org/#/c/585731 14:20:33 but I don't think he pushed the revision, did he? 14:20:45 no, i don't see any new revisions 14:21:04 * mlavalle pinging him 14:22:10 well, let's see if he is still awake 14:22:59 I am asking the core reviewers not to merger any patches until we finish with rc-1 14:23:17 to keep the gate wide open 14:23:39 in the past we have put -2 in patches not included in the release candidate 14:23:47 I am not going to do it this time around 14:24:05 ack, was just going to ask about the -2 14:24:20 I think we have a very disciplined team so it is not necessary 14:24:43 ok 14:25:50 anything else we should discuss about rc-1? 14:26:36 for stadium, https://review.openstack.org/#/c/584873/ has green everywhere for networking-sfc 14:27:21 bcafarel: thanks for bringing it up. I will take a look at it and encourage other revieiwers to do the same 14:27:26 also I will mentioned https://review.openstack.org/#/c/585559/ which is part of live-migration-portbinding, but is not critical for the release 14:28:55 this one is not a big deal and I think itis a good idea to switch to consume this function from neutron-lib before we generate technical debt with other Stadium projects 14:29:13 haleyb, slaweq: would you take a look at it 14:29:18 ? 14:29:29 #openstack-helm 14:29:36 oops 14:30:07 mlavalle: sure, I will look today 14:30:08 boden: i'll take a look 14:30:16 cool thanks haleyb 14:30:20 Thanks! 14:30:40 ok, moving on 14:30:56 #topic Community goals 14:31:03 we already talked about wsgi 14:31:21 njohnston: anyhting to report on Python 3? 14:31:48 The py35 fullstack job looks stable, and has been moved from the experimental queue to the check queue. It is still non-voting, we can assess it's voting status once we get past Rocky 14:32:15 thanks you for doing that 14:32:15 The py35 functional job still has a number of string parsing errors; I am trying to run those down. http://logs.openstack.org/50/580450/2/experimental/neutron-functional-python35/f8aad48/logs/testr_results.html.gz 14:33:00 I'm not sure what the "subunit.parser" error portends but I am hoping there are just opne or two deeply embedded issues that need to be tracked and fixed. 14:33:44 yes from what I have seen the other tests reported as failed are mostly a side effect of the subunit.parser one 14:34:21 I think that with luck we are on track to make both jobs voting at the start of the S cycle, which would conclude the python 3 goal IIUC 14:34:38 next step, tempest? ;) 14:35:48 it would be great if we can be ahead of the community with his goal 14:36:03 ah yes, tempest. yes, that will be next. 14:36:09 cool 14:36:18 thanks for the update 14:36:23 let's move on 14:36:26 #topic Bugs 14:37:32 Last week's bugs deputy was Yamamoto. He sent a report here: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132599.html 14:38:38 The only high priority one is https://bugs.launchpad.net/neutron/+bug/1783306 14:38:39 Launchpad bug 1783306 in neutron "Invalid auth url" [High,In progress] 14:38:51 and it seems is a docs issue 14:39:13 If nobody wants it, I'll work on it 14:39:17 any takers? 14:39:36 there is patch for it already I think 14:39:39 https://review.openstack.org/#/c/571384/ 14:40:04 a perfect 14:40:19 it needs only Your +2 :) 14:40:48 and a Closes-Bug? 14:41:28 The other two bugs that I want to highlight are https://bugs.launchpad.net/neutron/+bug/1783470 14:41:28 Launchpad bug 1783470 in neutron "get_subnet_for_dvr returns SNAT mac instead of gateway in subnet_info" [Undecided,In progress] - Assigned to Arjun Baindur (abaindur) 14:41:40 and https://bugs.launchpad.net/neutron/+bug/1783654 14:41:41 Launchpad bug 1783654 in neutron "DVR process flow not installed on physical bridge for shared tenant network" [Undecided,New] 14:42:04 yamamoto couldn't triage them. I will take a pass at them 14:42:23 if I get in toruble I'll bug haleyb ;-) 14:42:46 yes, he had sent me an email but i just saw it last night 14:43:08 let's work them over the next few days 14:43:26 any other bugs we should discuss today 14:43:28 ? 14:44:11 ok 14:44:21 This week, yours truly is the bugs deputy 14:44:54 Please note that it is time to rollover the calendar, which I will do today 14:45:07 don't forget to look at your next duty date 14:45:22 #topic neutron-lib 14:45:35 boden anything we should discuss on this topic? 14:45:43 hi. just very quickly 14:46:28 I’ll assume no body has heard of any issues with neutron-lib 1.18.0 (stable/rocky)?? I haven’t yet, so I’ll hope we are good with this version (so far) 14:46:57 I am good so far :-) 14:47:12 haven't heard anything 14:47:31 let's not jinx it and leave it at that 14:47:34 ;-) 14:47:34 and just a reminder that once we get rocky out we can begin to merge py code into neutron-lib as usual… but for now I’ve been holding off just in case we might need to cut a new rocky release 14:47:47 that’s all I have 14:48:15 thanks for holding the neutron-lib fort for us! 14:48:35 #topic Docs 14:48:48 anything to say about docs? 14:49:39 I'd say no, so let's move on 14:49:43 I don’t have anything… 14:49:49 seems like docs are perfect :) 14:49:53 #topic Open Agenda 14:50:08 DeepakT: the microphone is all yours 14:50:19 thanks mlavalle 14:51:03 I was working on adding sriov driver to neutron-taas 14:51:05 I seek to deploy it with openstack-helm 14:51:18 which only supports ocata release as of now 14:51:34 so I am doing changes for both ocata as well as master branch 14:51:59 those change are in what repo? 14:52:06 changes^^^^ 14:52:13 tap-as-a-service 14:52:15 now the main diff between the two branches is that in master branch agent is an L2 extension 14:52:16 hey DeepakT_ is there any patch for the SRIOV support for TaaS ? 14:52:33 tap-as-a-service 14:52:39 yes 14:52:45 I hv committed a patch 14:53:05 while in ocata branch agent runs as an independent process 14:53:08 AFAIK , TaaS would be L2 Agent extension only. 14:53:42 so I would like to propose to backport the change to make agent as L2 extension from master branch to ocata branch 14:54:00 yes, but its not like that in ocata branch 14:54:03 but Tap-as-a-Service is not a part of the Neutron Stadium, IIUC 14:54:17 no, it is not 14:54:35 https://review.openstack.org/#/c/584514/ 14:54:47 there are some missing items in there , some of which were assigned to me , but due to other commitments, missed them . 14:54:47 here is the patch in a very prilimnary stage 14:55:18 so I would like the community to give a go ahead to backport those changes in ocata branch 14:56:02 There are two things to mention here: 14:56:26 Tap-as-a-Service is a different project, and if I am correct, without a Project Lead ( PTL ) because Anil Rao left 14:56:46 1) I see it very difficult that we can merge new functionality into a stable branch. That is why they are stable. Besides, Ocata is not supported anymore 14:57:04 2) like rbanerje said 14:57:33 so let's take this conversation to the channel 14:57:46 I will try to find someone who can help TaaS 14:57:57 yamamoto, ^^ 14:57:58 for the time being, there is little we can do in this meeting 14:57:58 is there a dedicated channel for TaaS? 14:58:08 yamamoto can be a great mentor 14:58:21 DeepakT, the meeting for TaaS is on Wednesday 11:00 AM IST 14:58:28 ok, I will talk to yamamoto 14:58:31 ok 14:58:37 there is no separate channel for Tap-as-a-Service 14:58:41 wud it be same channel here? 14:58:47 Openstack-meeting 14:58:51 Thanks for attending 14:58:55 ok 14:58:59 #endmeeting