14:00:53 #startmeeting networking 14:00:54 Meeting started Tue Mar 30 14:00:53 2021 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:57 The meeting name has been set to 'networking' 14:00:59 o/ 14:01:17 hi 14:01:32 hi 14:01:35 hi 14:02:04 o/ 14:02:51 o/ 14:02:54 #topic announcements 14:03:12 Wallaby release calendar https://releases.openstack.org/wallaby/schedule.html 14:03:19 Last week we cut RC1 for almost all projects now, master is effectively opened for Xena development now 14:03:44 for neutron repo there are some patches which I think would be good to backport this week and make rc2 14:03:58 I will propose it later this week 14:04:14 o/ 14:05:04 if You have any patches like that, please propose backport to stable/wallaby and ping me on irc 14:05:21 also, it seems that we will need to deprecate networking-midonet project 14:05:26 thread http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021376.html 14:05:34 patches proposed today https://review.opendev.org/q/topic:%22deprecate-networking-midonet%22+(status:open%20OR%20status:merged) 14:06:12 TL;DR amotoki had concern that this project is currently broken and it shouldn't be released in such state 14:06:43 today, after I sent all those patches to deprecate it, sorrison replied to one of my emails 14:06:55 but I'm not sure if it still should be in the neutron stadium 14:07:11 IMO sorrison can keep it in x/ namespace if they still run it 14:07:24 but I would also like to know Your opinions about it 14:07:49 I think it's best to have it in the x/ namespace 14:07:59 I was thinking about x/ namespace too, it's a nice middle ground 14:07:59 Moving things to x/ is terrible but can work 14:08:20 lajoskatona: why it's terrible? 14:08:42 Being in the stadium means the broader Neutron team has a responsibility to networking-midonet to help keep it updated, which I think we can recognize we are not in a position to do. 14:08:46 a lot of patches to different repos, with headache, and discussions with infra :-) 14:08:59 If we move it to x/, does it means we'll still have a W release for this project? 14:09:16 ralonsoh: nope 14:09:16 ok then to move it to x/ 14:09:27 with my patches linked above we will not release it anymore 14:09:34 no their is no nice automate scripts, so there is release if you do it manually or do your scripts 14:09:47 and in x/ maintainers will be able to release whenever want 14:11:16 if we cannot live up to our responsibility to keep the project in good shape, we shouldn't pretend we do. It should be removed from the Stadium 14:11:40 mlavalle: that's also mine opinion about it 14:13:52 ok, so I will continue with that deprecation of it 14:13:55 thx 14:14:04 ok, lets move on 14:14:07 next reminder 14:14:21 Virtual PTG 19-23th April 14:14:27 etherpad https://etherpad.opendev.org/p/neutron-xena-ptg 14:14:34 please add Your topic there :) 14:14:52 according to doodle I choosen time slots for our sessions 14:15:00 details are in the http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021263.html 14:15:05 and in the etherpad as well 14:15:24 we will have sessions for 4 days 14:15:36 Wednesday is "no neutron day" in the ptg :) 14:16:08 kids=="no neutron"? 14:16:19 (as Wednesday is kids day too) 14:16:27 kids day? 14:16:29 where? 14:16:34 :) 14:17:33 do You have any other announcements for today? 14:19:45 ok, lets move on then 14:19:49 next topic 14:20:01 #topic Community goals 14:20:10 ralonsoh: any updates? 14:20:30 slaweq, not yet, still investigating the issue with os.kill 14:21:27 k 14:21:49 btw. do we know if there are any new goals for Xena cycle? 14:22:03 not that I recall 14:22:16 but checking governance repo 14:22:45 that will be discussed at ptg no? 14:23:34 bcafarel: idk really 14:23:36 IIRC the plan was for there to be no goal for Xena, to give the projects a break, calling it a 'stabilization' goal. But I have been out of the loop a bit. 14:23:36 just asking 14:23:59 njohnston: thx, I thought I heard something like that somewhere but I wasn't sure 14:24:11 oh true that sounds familiar 14:25:07 ok, thx for the info 14:25:12 I think we can move on 14:25:16 #topic bugs 14:25:23 lajoskatona was bug deputy, report: http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021375.html 14:25:35 lajoskatona: any bugs You want to highlight? 14:25:45 just a sec I check it 14:26:36 as I remember all bugs has somebody to push, or even was merged the solution workaround for it 14:27:11 so except the critical "before-release" bugs it was a usual week 14:27:57 thx, I saw from Your report that most bugs are assigned and in good shape 14:28:50 exactly 14:29:02 I wanted to talk about one bug today 14:29:04 https://bugs.launchpad.net/neutron/+bug/1921713 14:29:06 Launchpad bug 1921713 in neutron "Strings in tags field is limited to 60 chars" [Undecided,New] - Assigned to Harald Jensås (harald-jensas) 14:29:13 Patch https://review.opendev.org/c/openstack/neutron/+/783647 14:29:19 can we still make it to wallaby? 14:29:32 it has db upgrade script so in theory we shouldn't backport it 14:29:45 but we are before release still 14:29:47 so wdyt? 14:30:43 hmm db changes (even small ones) between RCs scare me a bit 14:31:00 bcafarel: that's why I'm asking here :) 14:31:45 I asked him to move the DB change to Xena for this reason... 14:31:57 ralonsoh: yes, it will be in Xena 14:32:01 is there any reason to keep it in W? 14:32:07 side note if we want to have this one slaweq you should probably stop https://review.opendev.org/c/openstack/neutron/+/783671/1 from merging 14:32:22 right 14:32:27 I'll -W for now 14:32:51 I'm not really sure if it's good idea to backport it 14:32:57 it may hit us later 14:33:06 in some unpredicatble way 14:33:07 no, we should not backport a DB change 14:33:13 and we will not have way to fix it 14:33:18 lets not do it now 14:33:20 but we can force the release process accepting it 14:33:24 just from branch view stable/wallaby is out and exists 14:33:26 it can land in Xena and that's all 14:33:50 so it should probably not get DB changes (even if created 4 days ago) 14:34:02 slaweq, is there a hard requirement to have it in W? 14:34:50 i think it was just because some tripleo changes merges in W that need it 14:35:15 i.e. they can fail with large tag names 14:36:23 I think it is better not to backport it to W 14:36:38 mlavalle, and merge it today into W? 14:36:59 ralonsoh: we can't merge it into W without merging it first to master 14:38:36 I would say like mlavalle - lets just merge it to master and not backport it 14:38:47 yeap 14:38:53 there are rules regarding backports and we should follow them 14:41:11 and that was last thing which I had for today 14:41:22 do You have any other bugs to discuss today? 14:41:25 or any other topics? 14:43:07 ok, if not, then I will give You some time back 14:43:11 thx for attending the meeting 14:43:14 o/ 14:43:16 o/ 14:43:16 bye 14:43:17 #endmeeting