21:00:45 <mlavalle> #startmeeting networking 21:00:46 <openstack> Meeting started Mon Oct 29 21:00:45 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:47 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:49 <openstack> The meeting name has been set to 'networking' 21:01:27 <hongbin> o/ 21:01:32 <haleyb> hi 21:01:34 <tidwellr> hi 21:01:37 <slaweq> hi 21:01:42 <mlavalle> hi everybody 21:02:08 <mlavalle> #topic Announcements 21:04:06 <mlavalle> So I want to talk about the release ccyle 21:04:08 <mlavalle> cycle 21:04:34 <mlavalle> first, the normal annnouncement, our next milestone is Stein-2 on January 7 - 11 21:04:37 <njohnston> o/ 21:05:10 <mlavalle> I want to draw the team's attention, though, to http://lists.openstack.org/pipermail/openstack-dev/2018-September/135088.html 21:05:33 * mlavalle will give the team a couple of minutes to read that 21:05:35 <manjeets> o/ 21:07:29 <mlavalle> To summarize, milestones will contnue to exist as a way to gieve cadence to the development effort 21:07:37 <njohnston> makes sense 21:07:50 <mlavalle> But we don't have to release anything during the milestones 21:07:52 <njohnston> and it works for us since we release neutron-lib on more of a monthly basis now 21:07:54 <mlavalle> unless we want to 21:08:32 <mlavalle> The release team will even generate the release patch during the rc windoes 21:09:36 <mlavalle> So going forward, I propose that during the milestones, we release 3 things: 21:09:47 <mlavalle> 1) Stable branches 21:09:54 <mlavalle> 2) neutron-lib 21:10:27 <mlavalle> 3) Subprojects who might want to release a beta before the rc period 21:10:40 <mlavalle> Thoughts> 21:10:42 <mlavalle> ? 21:11:10 <haleyb> +1 from me 21:11:21 <slaweq> +1 21:11:48 <boden> I'm probably slow here, but are you saying we will cut a stable branch on each milestone boundry? 21:11:51 <njohnston> +1 seems eminently reasonable 21:12:13 <mlavalle> boden: yes 21:12:23 <boden> mlavalle for neutron too right? not just for neutron-lib 21:12:51 <mlavalle> I was thinking only for neutron-lib 21:13:48 <boden> ok I guess I'm just confused as to what item 1 really means, but I'm sure you'll clarify in an email after the fact :) 21:14:16 <mlavalle> 1 means Neutron stable branches 21:14:31 <mlavalle> we were probably talking about the same thing, boden 21:15:11 <mlavalle> makes sense now? 21:15:24 <boden> I would just ask that you communicate this clearly sometime after the fact so we are all on teh same page 21:15:36 <mlavalle> ok 21:16:28 <mlavalle> slaweq: so that brings us to the topic you added to the on demand agenda. since we are already talking about stable branches 21:16:37 <mlavalle> we will cut stable branches this week 21:16:51 <mlavalle> I already had this conversation with amotoki on Friday 21:17:11 <mlavalle> and I'll make sure it happens this week 21:17:34 <mlavalle> anything else you want to add? 21:17:34 <slaweq> mlavalle: thx 21:18:11 <slaweq> I just wanted to say about frickler's proposal that for Pike maybe we should have 11.1.0 instead of 11.0.x version 21:18:49 <mlavalle> why is that? 21:18:58 * mlavalle just curious 21:19:33 <slaweq> he said that because of fix for https://bugs.launchpad.net/neutron/+bug/1775797 21:19:33 <openstack> Launchpad bug 1775797 in neutron "The mac table size of neutron bridges (br-tun, br-int, br-*) is too small by default and eventually makes openvswitch explode" [Medium,Fix released] - Assigned to Slawek Kaplonski (slaweq) 21:19:43 <slaweq> I don't have strong opinion about it 21:19:51 <mlavalle> ack 21:19:53 <slaweq> but maybe You will have 21:20:05 <mlavalle> No, I don't 21:20:22 <mlavalle> I'll probably check with the release guys 21:20:28 <mlavalle> and frickler himnself 21:20:32 <slaweq> ok, thx mlavalle 21:20:47 <mlavalle> any other announcements? 21:21:09 <mlavalle> ok, mving on 21:21:15 <mlavalle> #topic Blueprints 21:22:51 <mlavalle> I will continue rolling over the blueprints to next milestone dashboard 21:23:24 <mlavalle> Does anyone has any updates on blueprints? 21:24:08 <mlavalle> in regards to https://blueprints.launchpad.net/neutron/+spec/subnet-onboard 21:24:10 <tidwellr> I talked with bcafarel and I will be helping out with subnet onboard, I spent the day today looking at it and will have a new patch set for review in the next day or 2 21:24:31 <mlavalle> ahhh, you guys read my mind 21:24:33 <mlavalle> LOL 21:24:58 <mlavalle> I was going to ask you if you were still open to help there :-) 21:25:17 <tidwellr> yeah, I left this mess so I guess I should clean it up :) 21:25:26 <mlavalle> Should I assign the blueprint to you? 21:25:41 <tidwellr> sure 21:26:22 <mlavalle> that's great. surprising how we were thinking of the same thing ;-) 21:26:55 <mlavalle> ok, let/s move on 21:27:20 <mlavalle> #topic Community goals 21:27:47 <mlavalle> njohnston: any updates on py3 21:27:51 <mlavalle> ? 21:28:23 <njohnston> Regarding the python 3 goal, we agreed that this should be an item we track in the neutron CI meeting, so we'll be having more detailed discussions there as well as about the ubuntu version upgrade 21:29:12 <njohnston> I'll report back the overall results here in summary form, if you like. 21:29:13 <mlavalle> that's good 21:29:27 <mlavalle> yeap, that would be helpful 21:29:35 <mlavalle> thanks 21:29:42 <njohnston> Sounds good. 21:30:14 <slaweq> regadring the upgrade checker, base tool patch is in the gate now: https://review.openstack.org/#/c/608444/ - now I will add support for checks loaded with stevedore and we can then start thinging about some real checks to add 21:31:12 <mlavalle> slaweq: at what point can we claim that we have fulfilled the comunity goal? 21:31:50 <slaweq> IIUC this first patch is enough to have community goal completed as we will have neutron-status upgrade check CLI tool already done 21:32:29 <mlavalle> yes, that's what I thought. We of course want real checks 21:32:35 <slaweq> https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html#completion-criteria 21:32:50 <slaweq> yes, that will be enough for community goal 21:33:07 <mlavalle> cool 21:33:14 <mlavalle> thanks! 21:33:55 <mlavalle> #topic Bugs 21:34:24 <mlavalle> So our deputy last week was armax 21:34:36 <mlavalle> He indicated that he didn't find anything major 21:34:51 <mlavalle> the team does a great job triaging bugs 21:35:00 <mlavalle> I was looking at few, though 21:35:25 <mlavalle> First one is https://bugs.launchpad.net/neutron/+bug/1799924 21:35:25 <openstack> Launchpad bug 1799924 in neutron "tempest api test test_list_extensions_includes_all fails in Rocky branch" [Critical,In progress] - Assigned to Slawek Kaplonski (slaweq) 21:35:36 <mlavalle> We can marke this one fixed, right? 21:35:44 <slaweq> yes 21:35:54 <slaweq> I will do it right now 21:36:09 <slaweq> done 21:36:31 <mlavalle> Thanks 21:37:05 <mlavalle> I was also looking at this one: https://bugs.launchpad.net/neutron/+bug/1798690 21:37:06 <openstack> Launchpad bug 1798690 in OpenStack Compute (nova) "Live migrate of iscsi-backed VM loses internal network connectivity" [Undecided,New] 21:37:26 * haleyb has to leave early, will look at minutes 21:37:39 <mlavalle> it mentions DVR. haleyb could you give it a first pass? 21:38:06 <slaweq> he knew when to leave :P 21:38:13 <haleyb> i can look tomorrow 21:38:41 <mlavalle> haleyb: thanks 21:39:13 <mlavalle> slaweq: he has a lot of celebrations to attend. The Red Sox wan the World Series last night 21:39:36 <mlavalle> ask him about the 18 innings game Friday night 21:39:37 <slaweq> ahh, congrats haleyb :) 21:40:20 <mlavalle> any other bugs we should sicuss today? 21:40:54 <mlavalle> ok, let's move on 21:41:06 <mlavalle> Our deputy this week is Zhaobo 21:41:33 <mlavalle> I already confirmed by email that he will be taking care of bugs triaging this week 21:42:02 <mlavalle> #topic neutron-lib 21:42:16 <mlavalle> boden: you are up 21:42:17 <boden> hi 21:42:48 <boden> first I want to say thanks for the help landing a few patches last week.. In particular that simple yet large patch to switch the context manager... so thanks! 21:44:05 <boden> also I'm not sure anyone is one from Bigswitch, but I will mention https://bugs.launchpad.net/networking-bigswitch/+bug/1800186 that could impact our ability to land neutron-lib consumption patches in the future... just hoping we can get it taken care of 21:44:05 <openstack> Launchpad bug 1800186 in networking-bigswitch "Add support for python 3 and other TC goals" [Undecided,New] - Assigned to Aditya Vaja (wolverine-av) 21:44:55 <boden> other than that; business as usual; more db consumption patches coming soon 21:44:58 <boden> nothing else 21:45:31 <mlavalle> boden: ok, will keep an eye on those patches 21:45:44 <mlavalle> #topic os-ken 21:45:51 <mlavalle> Hi hongbin 21:45:56 <hongbin> o/ 21:46:25 <hongbin> we are still waiting for the inclusion of os-ken in requirements 21:46:26 <hongbin> #link https://review.openstack.org/#/c/609018/ 21:46:39 <hongbin> to address the comment there, we need this patch 21:46:46 <hongbin> #link https://review.openstack.org/#/c/613365/ 21:47:12 <hongbin> then, i will ping the reviewer to take a look at the requirement patch again 21:47:27 <hongbin> mlavalle: ^^ 21:47:50 <mlavalle> yeap, I was looking at it. added to my pile. I'll review it tomorrow 21:48:01 <hongbin> thanks 21:48:23 <hongbin> that is all from my side 21:48:31 <mlavalle> cool 21:48:48 <mlavalle> Thanks for the update 21:48:55 <mlavalle> #topic On demand agenda 21:49:07 <mlavalle> anything else we should sicuss today? 21:49:14 <mlavalle> discuss^^^^ 21:50:16 <mlavalle> ok, thanks for attending 21:50:21 <mlavalle> Have a great week! 21:50:26 <mlavalle> #endmeeting