14:00:33 <slaweq> #startmeeting networking 14:00:34 <openstack> Meeting started Tue Apr 21 14:00:33 2020 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:37 <openstack> The meeting name has been set to 'networking' 14:00:37 <slaweq> hi 14:00:41 <mlavalle> o/ 14:00:42 <jlibosva> o/ 14:00:47 <amotoki> o/ 14:00:52 <bcafarel> \o 14:01:10 <ralonsoh> hi 14:01:19 <haleyb> hi 14:01:40 <slaweq> ok, lets start 14:01:55 <rubasov> o/ 14:01:56 <slaweq> I hope You are all still good :) 14:01:58 <slaweq> #topic Announcements 14:02:34 <slaweq> according to release calendar https://releases.openstack.org/ussuri/schedule.html we have Ussuri RC1 week now 14:03:12 <slaweq> I was looking at opened patches and bugs today, and I prepared list with bugs targeted for RC1 14:03:14 <slaweq> #link https://launchpad.net/neutron/+milestone/ussuri-rc1 14:03:59 <slaweq> do You have any other bugs/patches which we should include in that list? 14:04:23 <slaweq> or maybe You thnink that some should be removed from that list? 14:04:49 <mlavalle> I have a question... no merging patches to master now, right? 14:05:01 <mlavalle> other thatn what is in the rc-1 14:05:19 <njohnston> o/ 14:06:02 <slaweq> mlavalle: IMO we can still merge some bug fixes other than from this list, but we should focus on merge of those listed before we will make rc-1 14:06:16 <lajoskatona> Hi, sorry for being late 14:06:17 <slaweq> we shouldn't merge any requirements changes or new features now 14:06:42 <mlavalle> ack 14:07:04 <haleyb> slaweq: i'd like to add https://bugs.launchpad.net/neutron/+bug/1871355 - it's the OVN provider but falls under neutron bugs 14:07:04 <openstack> Launchpad bug 1871355 in neutron "OVN octavia provider driver should spawn long-living process in driver agent" [High,In progress] - Assigned to Brian Haley (brian-haley) 14:07:38 <haleyb> unless i should create a new bug group to track those going forward 14:08:15 <slaweq> haleyb: it's fine for me but ovn-octavia-provider-driver has "cycle-with-intermediary" model, so I'm not sure if this is needed for this repo 14:08:39 <slaweq> amotoki: what do You think? should we release rc1 of ovn-octavia-driver also this week? 14:09:15 <slaweq> it has version 0.1.0 releases already for ussuri 14:09:18 <amotoki> slaweq: no, we don't need it. we don't release no beta for the intermediary deliverables. 14:09:38 <amotoki> if something should land, we can cut another release. 14:09:49 <slaweq> amotoki: ok, thx for confirmation 14:10:11 <haleyb> amotoki: thanks, when this change merges i'll tag a new release then 14:11:04 <amotoki> note that we already have stable/ussuri for ovn-octavia-provider so we need a backport before a release if any. 14:11:35 <haleyb> amotoki: yes, that is the only one i want to backport for stable/ussuri 14:12:24 <slaweq> if there would be any other bugs which You think are important in rc1, please ping me on irc to set milestone for it too 14:12:43 <slaweq> and at the end of this week I will sync with amotoki to make releases - is that ok for You amotoki? 14:13:05 <amotoki> slaweq: yes of course 14:13:41 <slaweq> thx 14:14:08 <slaweq> also, when we are speaking about new milestone - haleyb, bcafarel: should we do new releases of stable branches maybe? 14:14:54 <bcafarel> for rc times, I am not sure what we had decided 14:15:08 <bcafarel> we can definitely start preparing for a round to go with ussuri final release though 14:16:22 <slaweq> bcafarel: sounds good for me, lets prepare something to release around Ussuri release time 14:16:44 <amotoki> it looks better to discuss it after RC1 is cut. I totally agree that the end of the current dev cycle is a good trigger to visit stable releases :) 14:17:11 <slaweq> ok, bcafarel will You take care of this? 14:17:45 <bcafarel> slaweq: yes, I will start preparing the usual 'would be nice to have these in before release' lists 14:17:52 <slaweq> thx a lot 14:18:00 <slaweq> ok, lets move on 14:18:03 <slaweq> next announcement 14:18:12 <slaweq> Victoria virtual PTG 14:18:14 <slaweq> planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg 14:18:32 <slaweq> More details about how it will looks like is on http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html 14:18:56 <slaweq> basically event will be 1-5 June 14:19:21 <slaweq> there are various time slots available and we need to request some time in those slots 14:19:51 <slaweq> I made doodle https://doodle.com/poll/xcd82ea6svs5dben to see what time slots will be the best for most of people who plans to attend 14:20:22 <slaweq> if You plan to attend our sessions and didn't make this doodle yet, please do before end of this week 14:20:54 <slaweq> next week I will need to try to book some slots 14:21:19 <slaweq> also, if You have any topics which You want to discuss, please add them to etherpad 14:21:28 <mlavalle> so, to be clear, times in the form are in US Chicago time, right? 14:21:45 <bcafarel> should be your local time (I see Europe/Paris at least) 14:21:53 <amotoki> doodle shows your local tme 14:21:53 <slaweq> mlavalle: yes, probably local time 14:21:53 <mlavalle> ahh ok 14:21:53 <ralonsoh> local time for each one 14:21:59 <njohnston> I see the times as US/New York, so I think it is doing some kind of localization 14:22:05 <slaweq> on the top of the page there is info about what TZ is used 14:22:06 <mlavalle> yes 14:22:16 <mlavalle> central for me 14:22:23 <ralonsoh> +1 to the doodle GUI 14:22:40 <bcafarel> I see njohnston is timezone presence champion again (well you had training with Shanghai!) 14:22:52 <njohnston> \o/ 14:22:54 <slaweq> LOL 14:23:43 <slaweq> ok, lets move on 14:23:46 <slaweq> next one 14:23:53 <slaweq> Some info about Virtual OpenDev http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014297.html 14:24:05 <slaweq> just if You missed info on ML :) 14:24:25 <slaweq> and that's all announcements which I have for You today 14:24:35 <slaweq> anything else You want to announce maybe? 14:25:37 <amotoki> while it might be covered in OVN topic, I see an annoucement of networking-ovn master retirement mail from maciejjozefczyk 14:25:38 <amotoki> http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014307.html 14:26:19 <slaweq> amotoki: yes, he proposed this today as we finished BP to move code to neutron repo 14:26:40 <amotoki> I think it just applies to the master brnach and it is not a retirement from the TC governance perspective 14:27:00 <ralonsoh> you are right, only master branch 14:27:06 <njohnston> correct, since stable releases are still valid 14:27:13 <slaweq> amotoki: yes 14:27:15 <amotoki> thanks for the confirmation 14:27:53 <maciejjozefczyk> yes amotoki, I send little correction note about it later in this thread 14:28:09 <maciejjozefczyk> amotoki, In last couple of weeks I saw people sending patches to the networking-ovn instead neutron. So that is mainly why :) 14:28:29 <amotoki> maciejjozefczyk: yeah, it is a good notice :) 14:28:42 <njohnston> +1 14:28:56 <bcafarel> yes cleaned master branch + ussuri release highlight mentioning the merge will hopefully be enough to point people in correct direction 14:29:42 <slaweq> it is mentioned in Ussuri highlights for neutron already :) 14:29:49 <maciejjozefczyk> slaweq++ 14:30:37 <slaweq> ok, lets move on 14:30:41 <slaweq> #topic Blueprints 14:31:06 <slaweq> I don't have too much about BPs for today as we are close to final release and BPs aren't most important thing now :) 14:31:32 <mlavalle> when you have a chance, please review https://review.opendev.org/#/c/717881/ 14:31:42 <slaweq> so I just wanted to mention that I moved: https://blueprints.launchpad.net/neutron/+spec/tagging-on-post and https://bugs.launchpad.net/neutron/+bug/1863113 from Ussuro-3 to new cycle 14:31:42 <openstack> Launchpad bug 1863113 in neutron "[RFE] Introduce new testing framework for Neutron - OVN integration - a.k.a George" [Undecided,New] - Assigned to Jakub Libosvar (libosvar) 14:32:16 <slaweq> in case of https://blueprints.launchpad.net/neutron/+spec/tagging-on-post it's just due to missing clients support which mlavalle already send to review :) 14:32:19 <slaweq> thx mlavalle for that 14:32:57 <mlavalle> and the openstackclient patch is on its way. I discovered amotoki had done most of the work a long time ago. It is just a matter of moving one call 14:33:11 <slaweq> and regarding George framework, I moved it to Victoria-1 just to not forget about it, but as it's test-only thing, I think we can simply continue work on it even now in RC time 14:33:28 <mlavalle> but... in the openstack client there is no port creation in bulk command, correct? 14:34:23 <slaweq> mlavalle: I think there is no support for bulk port creation in OSC 14:34:23 <njohnston> correct, the openstack client doesn't really have a concept of bulk commands AFAIR. I talked to a couple of those guys but there was never any motion on it. 14:34:41 <slaweq> but IMHO if we will add possibility to tag in POST in OSC, this BP will be done 14:35:18 <mlavalle> ok, so I am just moving some code around so the openstack client tags a port on creation, instead of creating the port and then updatin it, as amotoki implemented way nack 14:35:38 <slaweq> mlavalle: thx :) 14:35:56 <mlavalle> that patch will be up for review by tomorrow 14:36:16 <mlavalle> and thanks amotoki for doing the heavy listing ;-) 14:36:23 <mlavalle> lifting^^^^ 14:36:39 <slaweq> amotoki++ 14:37:04 <slaweq> ok, anything else regarding BPs for today? 14:37:08 <slaweq> or can we move on? 14:37:55 * mlavalle stops babbling 14:39:11 <slaweq> nono, mlavalle please go on if You want to say anything else :) 14:39:23 <mlavalle> nothing else to say 14:39:29 <mlavalle> just joking 14:39:44 <slaweq> ok :) 14:39:58 <slaweq> so lets go to the next topic 14:40:00 <slaweq> #topic Community Goals 14:40:39 <slaweq> I don't have anything new regarding IPv6 testing for today 14:40:57 <njohnston> For zuulv3, the change for networking-odl is in the gate now, which would leave networking-midonet as the remaining project 14:41:11 <slaweq> njohnston: great, thx 14:41:46 <slaweq> with networking-midonet may be a bit hard as it's gate is currently broken (at least it was last week when I was checking it( 14:42:16 <njohnston> Thanks and appreciation for our own ralonsoh for taking the challenge to be goal champion for a community goal to move from oslo.rootwrap to oslo.privsep https://review.opendev.org/#/c/718177/ 14:42:26 <ralonsoh> yw! 14:42:30 <slaweq> ralonsoh++ 14:42:59 <slaweq> ok, so lets move on to the next topic 14:43:04 <slaweq> #topic Bugs 14:43:22 <slaweq> tidwellr was bug deputy last week but I didn't saw any email from him 14:43:37 <slaweq> and this week is njohnston's time for being deputy :) 14:43:48 <slaweq> next week will be amotoki 14:44:07 * njohnston is on it 14:44:12 <slaweq> thx njohnston :) 14:44:29 <slaweq> any bugs You would like to discuss today? 14:45:31 <njohnston> I havent been able to reproduce this one yet https://bugs.launchpad.net/neutron/+bug/1873761 14:45:31 <openstack> Launchpad bug 1873761 in neutron "Internal IP leak to physical interface from qrouter in DVR mode" [Undecided,New] 14:46:11 <njohnston> but leaking internal IP addresses is probably a bad thing IMHO 14:46:46 <njohnston> we can probably discuss that in more depth in tomorrow's L3 meeting 14:46:48 <haleyb> njohnston: this looks familiar, but i can't place it yet 14:46:55 <slaweq> yes, I saw this one - it sounds bad for me but I didn't have time to check it 14:47:19 <slaweq> I just adde some l3 related tag, so this will be on list in the L3 meeting :) 14:47:44 <njohnston> thanks, that is it for me 14:48:00 <mlavalle> are we keepiong tidwellr in the rotation? 14:48:26 <slaweq> mlavalle: the week before his deputy time I mailed him and he confirmed me that he will do it 14:48:48 <slaweq> but I will ask him again if we should keep him in this list for next round 14:48:59 <mlavalle> ok, cool with me. Just didn't know whether we had heard of him lately 14:50:14 <slaweq> mlavalle: sure, thx - I'm trying to ping everyone when before his turn :) 14:50:29 <slaweq> especially those who aren't always on the meetings 14:50:55 <slaweq> ok, last topic for today from me 14:50:59 <slaweq> #topic Networking OVN 14:51:07 <mlavalle> so you are not pinging me next time my turn is up? I'm heart broken ;-) 14:51:21 <slaweq> mlavalle: I will :) 14:51:39 <slaweq> I can even send You email remainder if You wish ;) 14:51:57 <mlavalle> ok, I'll bewating full of expectation 14:52:11 <slaweq> LOL 14:52:20 <slaweq> maciejjozefczyk: jlibosva haleyb: anything You want to discuss regarding ovn driver today? 14:52:40 * jlibosva was just eavesdropping :) nothing specific, thanks 14:52:56 <maciejjozefczyk> slaweq, we have little success thanks to ralonsoh, QoS max bandwidth works fine starting from today in Neutron master. 14:52:56 <haleyb> slaweq: it was just the one fix for stable/ussuri i mentioned earlier 14:53:15 <slaweq> maciejjozefczyk++ :) 14:53:24 <slaweq> I have one question about this topic 14:53:41 <slaweq> do we still need to have it as separate topic during the team meeting? 14:53:59 <ralonsoh> qos? ovn? 14:54:02 <slaweq> migration is done, ovn is now part of Neutron code so I'm not sure if we still need it 14:54:06 <maciejjozefczyk> In my opinion, no :) 14:54:12 <slaweq> ralonsoh: I mean "ovn" 14:54:21 <mlavalle> ++ 14:54:57 <haleyb> ++ 14:55:01 <ralonsoh> ++ 14:56:07 <slaweq> jlibosva: maciejjozefczyk: are You ok to remove this topic from weekly meetings? 14:56:17 <maciejjozefczyk> ++ 14:56:26 <bcafarel> most probably not needed anymore, we can add specific topics to agenda when needed (and migrations is done) 14:56:31 <jlibosva> ++ 14:56:34 <slaweq> ok, thx 14:56:41 <slaweq> so I will remove it from the meeting agenda 14:56:52 <slaweq> and that's all what I have for today 14:57:07 <slaweq> I don't see anything in "on demand agenda" for today 14:57:16 <slaweq> so I guess we can finish few minutes earlier 14:57:29 <slaweq> thx for attending and have a great week :) 14:57:31 <slaweq> o/ 14:57:32 <njohnston> o/ 14:57:32 <jlibosva> o/ 14:57:33 <slaweq> #endmeeting