14:01:40 #startmeeting networking 14:01:40 Meeting started Tue Mar 26 14:01:40 2019 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:43 The meeting name has been set to 'networking' 14:01:57 hi 14:02:02 hi 14:02:03 hi 14:02:03 Hi 14:02:09 o/ 14:02:10 o/ 14:02:20 hi 14:02:20 how are you all! 14:02:27 howdy 14:02:34 splendid, and you? 14:03:03 as usual, you will find updated agenda here: https://wiki.openstack.org/wiki/Network/Meetings 14:03:16 #topic Announcements 14:03:36 late o/ 14:05:00 First of all, we cut RC-1 over the weekend 14:05:17 https://review.openstack.org/#/c/644339/ 14:06:03 We have until April 5th in case we need to cut another RC 14:06:08 opr several 14:07:07 And please remember that the etherpad for the PTG is up for topics suggestions: https://etherpad.openstack.org/p/openstack-networking-train-ptg 14:07:43 I can see that a healthy number of you all will be in attendance 14:07:51 Looking forward to see you there 14:07:55 \o/ 14:08:29 and without train horns in the night :) 14:08:45 that's right :-) 14:09:05 any other annoucements I might have missed? 14:10:11 ok, let's move on 14:10:27 #topic Blueprints 14:10:51 These were the blueprints we were targeting for our RC-1: https://launchpad.net/neutron/+milestone/stein-rc1 14:11:33 As you can all see, we merged almost everything we targeted for RC-1 14:11:47 \o/ 14:12:04 yeah, lots of green in that list 14:12:43 liuyulong: this was assigned to you: https://bugs.launchpad.net/neutron/+bug/1813787 14:12:45 Launchpad bug 1813787 in neutron "[L3] DVR router in compute node was not up but nova port needs its functionality" [Medium,In progress] - Assigned to LIU Yulong (dragon889) 14:13:12 do you have a status report on it? 14:13:33 Yes 14:14:27 For the new approach slaweq and me mentioned in the patch set, I met some refactor problem. 14:14:43 It will become much more complicated. 14:15:06 liuyulong: thanks for the follow up! 14:15:15 But, FYI, our local environment is running the current approach, everything works fine. 14:16:00 We've tested concurrently boot 10/20/30 VM under different DVR router. 14:16:40 It can work, all VM get the metadata. But indeed, some retry can be seen during the boot time. 14:17:12 ok. here's what I propose then. when it is ready, we can merge it in master and then backport to Stein 14:17:26 that way we don't have to rush against the calendar 14:17:33 OK 14:17:41 and we have time to review it properly 14:17:49 does that work for everybody? 14:19:06 The current approach is here: https://review.openstack.org/#/c/633871/, maybe we can get it in first then, I'll try refactor it to the new style. 14:19:06 ok, I'll take that as a yes 14:19:19 liuyulong: that works 14:20:25 so next question..... 14:20:29 to the team 14:20:47 is there anything critical that we should include in a potential RC-2? 14:21:57 not that I know of, but better check with slaweq 14:23:22 I also think we don't need another RC 14:23:58 if there are bugs that show up over the next few weeks, we can always backport to Stein 14:24:10 right? 14:24:34 makes sense to me 14:24:46 and to me too 14:25:12 so let's take this as good and we can start merging code into master freely again 14:25:18 so merge away! 14:25:24 mlavalle and neutron-lib master too right? 14:25:34 boden: correct 14:25:41 flood gates open 14:25:51 :) 14:26:11 ok, let's move on 14:26:40 #topic Community Goals 14:26:56 is there anything to be said about py3? 14:27:38 We remain in compliance with the community py3 goal 14:27:44 yes all good for this cycle, maybe some minor changes here and there but I think we are in great shape py3-wise 14:28:03 thank so much! 14:28:10 and I will keep slowly plugging away at the stadium jobs that are above and beyond the basic py3 Stein goal so we are well set up for T and U 14:28:51 Thanks to the hard work of several of you, this cycle we have caught up with all the community goals 14:28:54 \o/ 14:29:16 * mlavalle taking a pause to let that sink in 14:29:40 \o/ 14:30:13 ok, let's move on 14:30:31 #topic Bugs 14:31:56 This past week yours truly was the bugs deputy 14:32:33 Here's the report http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004235.html 14:33:10 We have two critical bugs: https://bugs.launchpad.net/neutron/+bug/1821384 14:33:11 Launchpad bug 1821384 in neutron "Customization of ubuntu image fails before upload to devstack" [Critical,Fix released] - Assigned to Slawek Kaplonski (slaweq) 14:33:58 The fix was merged yesterday: https://review.openstack.org/#/c/645883/ 14:34:27 and the other critical was https://bugs.launchpad.net/neutron/+bug/1820865 14:34:28 Launchpad bug 1820865 in neutron "Fullstack tests are failing because of "OSError: [Errno 22] failed to open netns"" [Critical,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez) 14:34:35 that I was working on 14:34:47 but I see ralonsoh proposed a fix this morning 14:34:49 I have a possible solution 14:34:52 yes, one sec 14:35:01 #link https://review.openstack.org/#/c/647721/ 14:35:33 in one line: to check if the namespace is accesible (aka: we can open it) 14:36:04 yeap 14:36:40 so the name space can exist but not ready to be opened, is that it? 14:37:17 exactly, I saw it a couple of times in the CI: the namespace was still open when the test tried to open it 14:37:49 yes, I saw that this weekend as well 14:38:02 I took network_namespace_exists as goof, that is why I was trying to change pyroutes2 version 14:38:15 cool, 14:38:29 thanks for the fix ralonsoh 14:38:43 np! 14:39:13 haleyb: would you have a chance to take a look at https://bugs.launchpad.net/neutron/+bug/1821299? 14:39:14 Launchpad bug 1821299 in neutron "Associating Floating IP with a port can result in duplicate Floating IPs, due to the original FIP not being removed from the SNAT namespace." [Undecided,New] 14:39:30 mlavalle: yes, will look. did your downgrade of pyroute2 show anything? 14:39:46 oh, sorry, still on old topic 14:39:57 yes, i'll look at that too 14:40:20 haleyb: the downgrade has been succesful so far. but let's see if ralonsoh fix is the good one 14:40:25 it looks like it 14:40:35 it makes sense 14:41:15 I would also like someone to take a look at https://bugs.launchpad.net/neutron/+bug/1821357 14:41:16 Launchpad bug 1821357 in neutron "VRRP vip on VM not reachable from other network on DVR setup" [Undecided,New] 14:41:55 any other bugs we should discuss today? 14:42:31 hi, one small thing 14:43:03 https://bugs.launchpad.net/neutron/+bug/1813703 14:43:04 Launchpad bug 1813703 in neutron "[L2] [summary] ovs-agent issues at large scale" [High,Fix released] - Assigned to LIU Yulong (dragon889) 14:43:19 https://review.openstack.org/#/c/638641/ this one change for it. 14:43:39 I'd like to raise this change to our meeting as slaweq suggested. 14:43:50 It changes ovs-agent iteration log level from DEBUG to INFO. 14:44:03 (I would like to have this patch merged) 14:44:17 The reason is obvious. Operators may need to detect the ovs-agent LOG status. 14:44:38 And more useful thing is it can be used to estimate port processing time. My OP colleagues love this. 14:45:03 But the most noteworthy concern is the log size now. 14:45:22 I'm in favor of this, balancing log verbosity can be an art. I think this is useful 14:45:27 I think it is very valuable, my only thought is that perhaps a release note warning operators that provide very little extra space on the partition where they store their logs that they may need to increase that space as an upgrade concern. 14:45:41 After some estimating and local debug, it's about 26Mb or compressed size 1Mb per day. 14:47:21 If that is the size differential then I think there is no concern, but when in use in an active environment with a lot of ephemeral instances my gut feeling is that the size impact would be greater. 14:47:45 liuyulong: thanks. for the sake of time let's continue the conversation in gerrit 14:47:48 liuyulong: are operators really looking at this level of detail in the agent? it still seems like more of a debugging thing to me 14:48:27 i know in the past we had reduced log levels because infra said our logs were too big (and they still are) 14:48:29 haleyb, some LOG monitor can be set on these log 14:49:01 please post your comment in the patch 14:49:16 The deputy for this week is rubasov 14:49:18 OK, let's move to the gerrit. 14:49:30 who has started triaging already 14:49:34 ack, started triaging yesterday 14:49:46 tidwellr, njohnston, haleyb, thanks for the comments. 14:49:46 and also please note that I updated the calendar 14:50:07 please take note of your next duty week 14:50:17 #topic neutron-lib 14:50:22 boden: you are up 14:51:07 hi.. now that master branches are back open, pls be looking for neutron-lib and consumption patches... I have a few (read 10s) ready 14:51:10 that's it 14:51:42 boden: LOL 14:51:46 great! 14:53:08 #topic On demand agenda 14:53:24 anything else we should discuss today? 14:54:01 * mlavalle points out that he just had an out of bad chat with tidwellr, who will be added to the bugs deputy rotation 14:54:10 out of band^^^ 14:54:20 tidwellr++ 14:54:27 mlavalle: never a bad chat with you :) 14:54:30 welcome in the band then :) 14:54:58 ok team. Thanks for attending 14:55:05 enjoy the rest of your week! 14:55:10 #endmeeting