14:01:09 #startmeeting networking 14:01:09 Meeting started Tue Jan 30 14:01:09 2018 UTC and is due to finish in 60 minutes. The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:13 The meeting name has been set to 'networking' 14:01:16 hello everyone 14:01:17 o/ 14:01:19 hi 14:01:20 hello 14:01:21 o/ 14:01:24 o/ (on and off) 14:01:32 #topic Announcements 14:01:41 o/ 14:01:49 hi 14:01:50 we're now in the rc-1 phase 14:01:53 #link https://launchpad.net/neutron/+milestone/queens-rc1 14:02:06 which means only those bugfixes that are marked as such should be merged 14:03:10 next one is that the PTL self-nomination is now open: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126700.html 14:03:26 mlavalle are you gonna be our precious PTL for the next cycle? :) 14:03:48 I intend to submit my candidacy this week 14:04:00 \o/ yay 14:04:05 :) 14:04:11 :-) 14:04:12 :) 14:04:22 +1 14:04:39 oh, one more thing regarding the RC - the planned end is at 5 February 2018 as per https://releases.openstack.org/queens/schedule.html#q-rc1 14:04:48 that's all announcements I got 14:04:54 does anybody have anything to announce? 14:05:30 neutron-vpnaas release in queens is in question. 14:05:42 perhaps it will be cycle-with-intermediate 14:06:03 but i don't think it is a problem. we can release it. 14:06:14 amotoki: thanks for updates 14:06:41 I think we can move on 14:06:44 #topic Blueprints 14:07:06 as we're in RC, all blueprints should be either finished or rescheduled 14:07:37 the main focus should now on bugfixes that we intend to merge in Queens 14:07:54 ++ 14:07:59 so the questions are: are there any FFE requests? what is the official process of FFEs? 14:08:15 i might miss things as I failed to join the last drivers meeting 14:08:47 in the last drivers meetings we reviewed FFEs submitted 14:08:57 and other things the drivers thought required FFE 14:09:15 that is how we came up with https://launchpad.net/neutron/+milestone/queens-rc1 14:09:47 amotoki: doeas that answer the question? 14:09:49 mlavalle: so are there any features with FFE? or those are all bugfixes? 14:10:00 mlavalle: yeah of course 14:10:04 no features with FFE 14:10:44 ok, thanks 14:11:00 I will rollover the features in q-3 this week 14:11:10 to Rocky 14:12:11 ok, jumping to bugs then unless anybody has anything to add 14:12:26 it will be appropriate to review that features list in the next drivers meeting 14:12:40 in case wee need to do adjustments 14:13:30 * jlibosva nods 14:13:49 #topic Bugs 14:14:02 amotoki was the bug deputy for the last week 14:14:03 I was the bug deputy of the last week. I just sent a report. 14:14:12 #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126700.html 14:14:20 there are several interesting reports. 14:14:32 #undo 14:14:40 #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126731.html 14:14:51 that one :) 14:14:53 amotoki: ^^ :) 14:14:53 LOL 14:15:20 how do we proceed? 14:16:00 anyway I would like to say thanks to slaweq to address the tricky eventlet bug first 14:16:22 amotoki: You welcome :) 14:16:33 slaweq++ 14:16:38 ++ 14:16:51 slaweq++ 14:17:03 so the ones under the [need attention] fix are triaged but have no asignee? 14:17:38 I see the first one has an assignee 14:17:41 some of them have assignee(s) but I think they need to be verified 14:17:43 yeah 14:17:51 ah ok 14:17:59 do we look through them? 14:18:38 the first one https://bugs.launchpad.net/neutron/+bug/1745642 is critical to FWaaS v2 perspective 14:18:39 Launchpad bug 1745642 in neutron "SG hybrid iptables driver and FWaaS OVS driver create overlapping conntrack zones " [High,In progress] - Assigned to chandan dutta chowdhury (chandanc) 14:19:31 I think most deployments upgraded from past releases use hybrid dirver, so it means FWaaS v2 ovs impl does not work in their deployments. 14:19:36 i think there was a change sent for htat? 14:20:25 i just added a review link to the bug 14:20:28 https://review.openstack.org/#/c/538154/ ? 14:20:46 yes 14:20:47 yes, it used CT and i was searching for ocnntrack 14:21:10 query "message:1745642" helps us :) 14:21:25 I searched for "zone" :) 14:21:41 you are all smarter than i :) 14:22:29 i think it is worth landed in RC1 14:22:39 yeah, I was about to ask 14:22:46 the second topic is related to MTU. 14:22:53 i've been following the review, think it's ok, follow-on to move range constants to neutron-lib 14:23:17 which one haleyb? 14:23:31 mlavalle: the conntrack one 14:23:35 ok 14:23:54 sorry for too fast movigg 14:23:54 the OVS FWaaS driver was introduced in Q? 14:24:09 jlibosva, yes 14:24:10 yes, it landed in Q 14:24:40 annp_: thanks. I was just thinking whether we might need to fix existing deployments that could be affected 14:24:59 yeah, good question 14:25:21 I understand that only trunk-chasers could be hit 14:25:42 so imho the patch is fine 14:26:09 jlibosva: i think it hits existing deployments which is upgraded to queens and enable fwaas v2 in queens 14:26:31 amotoki: not if we get the patch to rc, right? 14:26:44 jlibosva: exactly 14:26:59 ok, we will add it to the RC1 list 14:28:01 actually amotoki has done it already :-) 14:28:24 hehe. i think it is the only one I targettd to RC1 14:28:37 that's ok, good call 14:29:36 the second topic is about MTU on ovs-agent. 14:29:37 are there any other bugs that require special attention during the meeting? 14:30:06 I am not sure it was introduced in queens or it exists from the past release. 14:30:43 I could not have time to check it in my local env. some input would be appreciated. 14:32:10 I'm linking the mtu bugs here so we're on the same page 14:32:12 #link https://bugs.launchpad.net/neutron/+bug/1744101 14:32:13 Launchpad bug 1744101 in neutron "vxlan interfaces doesn't get MTU" [Medium,Confirmed] 14:32:18 #link https://bugs.launchpad.net/neutron/+bug/1745150 14:32:19 Launchpad bug 1745150 in neutron "neutron doesn't set MTU on ovs" [Undecided,Incomplete] 14:32:36 jlibosva: thanks 14:32:41 maybe folk familiar with mtu can have a peak and we can move on with the topic 14:32:53 yeap 14:32:56 the bug deputy for this week is me 14:33:04 it's good to know :) 14:33:24 jlibosva: i only quickly looked at those mtu bugs, could re-visit 14:33:24 oh yeah 14:33:42 haleyb: thanks 14:34:14 I will look into the bugs I listed as "needs-attention" in the rest of this week 14:34:15 I also see haleyb is looking at the other bug mentioned in the list, related to slow conntrack entries deletion :) 14:35:01 amotoki: do you think there is any other bug worth discussing here or shall we move on? 14:35:11 i think we can move on 14:35:13 thanks 14:35:18 #topic docs 14:35:21 thanks for the report amotoki 14:35:24 boden: hi, are you around? 14:35:33 he might not be around 14:35:35 jlibosva yes for a short bit 14:35:39 he is 14:36:05 boden: do you have any updates related to docs? 14:36:23 I don’t have anything worth mentioning on the doc front other than FYI we have someone picking away at the api-ref bugs 14:37:09 perhaps we will need to check our installation guide a couple of weeks later. 14:37:40 the responsibility on the install guide is now individual teams (from pike) 14:37:55 but we can discuss it a few week later. 14:38:10 ok, thanks 14:38:22 thanks 14:38:33 it could actually be a topic in Dublin 14:38:42 while we have boden around, we can jump to the next topic quickly 14:38:50 according to docs 14:38:55 I want to ask for review of https://review.openstack.org/#/c/538585/ 14:39:07 I made some cleaning of parameters in api-ref 14:39:17 but that's not urgent of course :) 14:39:17 slaweq: thanks a lot 14:39:18 slaweq will make a pass today 14:39:27 me too 14:39:37 thx 14:39:56 I would like to see your command :) 14:40:09 amotoki: I forgot to paste it yesterday 14:40:15 it would be useful for a while. 14:40:19 I will give it to You later today 14:40:24 thanks 14:41:05 I thought how it can be done as part of os-api-ref but there is no progress so far... 14:41:50 we lost slaweq 14:42:16 jlibosva: why? 14:42:20 slaweq: hi! 14:42:29 sorry, it was slaweq_ :) 14:42:34 I misrea 14:42:37 misread 14:42:49 ah, so maybe my computer at home was connected for a while 14:42:50 sorry 14:43:09 anything else to be added to docs? 14:43:26 jlibosva: Is this topic also include doc change in neutron or only for neutron-lib? 14:43:35 both 14:43:37 both 14:43:57 it's docs in general 14:43:58 I have one for vpnaas in flight for a while need attention https://review.openstack.org/#/c/482510/ 14:44:09 mlavalle: jlibosva thanks :-) 14:44:36 amotoki: I addressed all of your comments :) 14:44:51 there is no feature freeze on docs. we can land docs patch anytime. 14:45:07 hoangcx_: I will take a look today 14:45:08 hoangcx_: will check it 14:45:33 Thanks a lot, Sirs :) 14:46:00 good, anybody has anything else? 14:46:30 we can move on then 14:46:33 #topic neutron-lib 14:46:34 boden: hi, still around? 14:46:46 hi, for 1 min 14:46:56 so quickly FYIs 14:47:01 boden: do you have a 1 min update regarding neutron-lib? :) 14:47:13 holding off on code changes in lib and neutron until queens is solid.. but will review the api-ref ones in lib since they are not tied to releases of lib 14:47:39 also will be re-kicking the policy work in lib which is currently 1/2 baked for queens, so you may see that work start to pop up and I hope to have someone new on my team work on it 14:47:42 that’s what I have 14:47:45 I will do the same regarding api-ref 14:47:47 boden: thanks 14:48:02 I am pretty late .... 14:48:22 welcome to the new team member! 14:48:29 I just resumed the policy work.... hopefully we can land the policy-in-code in early Rocky 14:48:39 I need to step away now, sorry… ping me on openstack-neutron if any questions. thanks 14:48:54 amotoki I think someone from my team reached out ot you on that 14:48:57 mlavalle: i am an old member :) 14:49:15 amotoki: I will be getting patch for neutron-lib to get policy working soon too 14:49:17 LOL 14:49:17 boden: yeah, I discussed 14:49:21 ok thx 14:50:16 anybody has anything else to add to neutron-lib? 14:51:02 #topic Transition to OSC 14:51:05 amotoki: hi 14:51:35 i think we don't have topics on this due to the lib freeze. 14:52:16 ack, thanks :) 14:52:28 #topic Open Agenda 14:52:35 we have 8 minutes left 14:52:46 there is no topic written at the wiki page 14:52:50 does anybody have a topic to discuss? 14:53:10 how about PTG planning? 14:53:28 we have an etherpad out there 14:53:51 https://etherpad.openstack.org/p/neutron-ptg-rocky 14:54:01 I found it in the wiki page https://wiki.openstack.org/wiki/PTG/Rocky/Etherpads 14:54:27 correct 14:54:36 so the idea is that we add topic there 14:54:55 thanks. I just would like to remind it :) 14:55:39 yeah, baed on the input we can start discussing an agenda starting next week 14:55:50 let's focus on the RC-1 this one 14:56:37 thinking of it, I will send a reminder of the etherpad this week to the ML 14:56:39 let's put pending items to the etherpad and focus on stabilizing queens :) 14:57:00 what amotoki said 14:57:04 :-) 14:58:00 :) 14:58:14 so I guess unless there is nothing else to be added 14:58:27 we can end a minute earlier and get that minute back :) 14:58:35 thanks everyone for showing up! 14:58:38 thx 14:58:44 thanks 14:58:45 #endmeeting