21:00:02 #startmeeting networking 21:00:03 Meeting started Mon Apr 1 21:00:02 2019 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:06 The meeting name has been set to 'networking' 21:00:34 hi 21:00:46 hi 21:01:25 how are y'all? 21:01:50 slowly thawing from winter 21:01:58 little bit sleepy but fine :) 21:02:12 yeah, you guys are buried in snow, right, tidwellr? 21:02:24 any danger of floding around you? 21:02:47 o/ 21:02:54 mlavalle: we were, but it all melted in a fairly orderly fashion so it wasn't a big deal 21:03:14 I have 1 tiny pile of snow left in my yard 21:03:26 cool, I think the problem might be for the states down stream the Mississipi 21:03:41 as all that snow melts 21:04:04 let's run all downstream now so I can boat this summer without no-wake restrictions :) 21:04:25 As always, our agenda is here: https://wiki.openstack.org/wiki/Network/Meetings 21:04:37 #topic Announcements 21:05:02 This week is the last one to propose a release candidate 21:05:17 which as we decided that week, we are not going to do 21:05:30 so for all practical purposes, we are in Train 21:06:11 Spealing of which, I want to remind everybody that we 4 weeks away from the Summit and a few days more from the PTG 21:06:15 I even sent today patch https://review.openstack.org/#/c/649067/ to add Stein jobs for our tempest plugin :) 21:06:46 Please remember to porpose topics in https://etherpad.openstack.org/p/openstack-networking-train-ptg 21:07:05 In about a week I'll start grouping the topics in sessions 21:07:10 so we have an agenda 21:08:08 o/ 21:08:09 For those of you who may remember him, I pinged carl_baldwin last week, who lives about 1 hour North of Denver 21:08:42 he will be joining us for the team dinner on May 3rd 21:08:50 I added his name to the etherpad 21:09:17 Any other announcements I might have missed? 21:09:54 ok, moving on 21:10:01 #topic Blueprints 21:10:38 All I want to say here that at the end of RC-1 this is what our dashboard looked like: https://launchpad.net/neutron/+milestone/stein-rc1 21:11:12 Pretty good job. Congratulations and thanks to the entire team for all your hard work 21:11:45 anything else that we should talk about in blueprints? 21:12:28 #topic Community goals 21:12:54 Since tomorrow we won't have CI meeting, is there any updates on our progress with python3 21:12:56 ? 21:13:13 I don't have anything 21:13:14 I know we met the community goal, but we are doing some additional things 21:13:31 we still have stadium projects to move to py3 21:13:52 https://etherpad.openstack.org/p/neutron_stadium_python3_status 21:13:52 here is the etherpad for it 21:14:33 so if someone wants, You can add Your name to some job and propose patch :) 21:14:51 great. that's what I wanted to get at 21:15:20 ok, let's move on 21:15:57 #topic Bugs 21:16:17 rubasov was our bugs deputy last week 21:16:34 as customary with him, he did a pretty thorough job: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004371.html 21:17:09 We have no critical bugs this week 21:17:21 and two high priority 21:17:36 The first one is https://bugs.launchpad.net/neutron/+bug/1821912 21:17:37 Launchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed] 21:18:21 mlavalle: there was also today's update from rubasov http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004411.html 21:19:08 slaweq: thanks 21:19:39 slaweq: but if I understand correctly, that critical one is due to a devstack issue 21:19:42 right? 21:19:53 mlavalle: yes, and patch on our side is already merged 21:19:59 so we are good with this one 21:20:22 cool 21:20:58 so going back to the ssh failures, these are failures where we haven't identified a common pattern 21:21:44 there is one common thing IMO there 21:21:46 it is meant to be a team effort. So if you have bandwidth and interest, please use the logstash query in the description, find a failure and traige / debug away 21:21:57 slaweq: shoot 21:22:11 in all (or almost all) cases, vm had access to metadata so I assume that connectivity Vm -- router was fine 21:22:26 and failure is probably somewhere between tempest -- router 21:22:40 or security groups for instance 21:22:51 or something inside router's namespace 21:23:09 slaweq: it would be good to leave a comment indicating this 21:23:20 I did few minutes ago :) 21:23:25 ++ 21:24:18 The other high importance one is https://bugs.launchpad.net/neutron/+bug/1822256 21:24:19 Launchpad bug 1822256 in neutron "Ip segments lost when restart ovs-agent with openvswitch firewall" [High,New] 21:25:27 what does he mean by ip segment? packets? 21:25:55 I think he means packets 21:26:30 there is tcpdump in bug report 21:26:32 192.168.100.19 192.168.100.5 SSH 16478 Server: [TCP ACKed unseen segment] [TCP Previous segment not captured] , Encrypted packet (len=16412) 21:26:44 so I guess that he is talking about those packets exactly :) 21:26:56 yeah, that must be it 21:27:34 I'll try to reproduce it 21:28:40 slaweq: since we won't have CI meeting tomorrow, is there anythiong we should be paying attention? 21:29:05 mlavalle: I don't have anything new on my list 21:29:38 I think that our main problem is this issue with ssh failures now 21:30:01 there were some errors with grenade jobs, but not related to neutron directly 21:30:02 so we pass the RC rush and the gate stops mis-behaving. it must be doing it on purpose ;-) 21:30:11 and I know that mriedem is on it 21:30:39 one thing only 21:30:41 https://review.openstack.org/#/c/648924/ 21:30:49 I proposed today to make fullstack voting again 21:31:04 I think that we fixed main problems and it should be good to go IMO 21:31:24 it is probably a good moment to do this 21:31:39 slaweq: fyi on those grenade py3 issues https://review.openstack.org/#/q/topic:bug/1820892+status:open 21:33:26 mriedem: thanks! 21:33:42 mriedem: thx a lot :) 21:34:29 slaweq: I just pushed the revert 21:34:41 mlavalle: thx 21:34:58 ok, any other bugs we should discuss this week? 21:35:50 cool 21:36:06 our bugs deputy for this week is bcafarel 21:36:34 please note that I rolled over the duty schedule 21:36:45 so take note of your next duty week 21:37:02 mlavalle: well I know when mine is at least :) 21:37:35 slaweq: pasuder is scheduled next week. Would you ping him to make sure he will do it? 21:37:49 mlavalle: sure, I will ask him tomorrow 21:38:21 * mlavalle will ping hongbin, since he is scheduled the week of April 15th 21:38:44 #topic neutron-lib 21:39:05 boden: any updates? 21:39:09 hi 21:39:39 not a ton to report; we are back to landing py code in neutron-lib 21:40:09 when do you think it'll be safe to release a new lib so we can start to consume? 21:40:25 should. we wait until Stein is officially out the door? 21:41:02 boden: yeah, let's wait 21:41:36 the official release is next week 21:41:45 ack 21:42:01 I don't have any other topics, unless others have comments 21:42:16 did you see rnoriega's email about l2gw, boden? 21:42:24 he cut the branch 21:42:27 mlavalle yes and spoke on IRC earlier 21:42:38 thanks 21:42:39 great, we are good there right? 21:42:46 as far as I know 21:42:47 yes 21:42:51 cool 21:43:19 moving on 21:43:28 #topic On demand agenda 21:43:41 anythiong else we should discuss today? 21:44:01 nope 21:44:36 ok, 15 minutes are returned to your agendas 21:44:41 Have a great week! 21:44:47 #endmeeting