14:01:02 <whoami-rajat> #startmeeting cinder
14:01:02 <opendevmeet> Meeting started Wed Apr 12 14:01:02 2023 UTC and is due to finish in 60 minutes.  The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:02 <opendevmeet> The meeting name has been set to 'cinder'
14:01:08 <whoami-rajat> #topic roll call
14:01:10 <tosky> o/
14:01:12 <eharney> hello
14:01:15 <rosmaita> o/
14:01:38 <nahimsouza[m]> o/
14:01:55 <kgube> o/
14:02:03 <caiquemello[m]> hi
14:02:59 <simondodsley> o/
14:03:20 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-bobcat-meetings
14:03:44 <HelenaDantas[m]> hi
14:04:13 <luizsantos[m]> o/
14:05:03 <whoami-rajat> hello everyone
14:05:05 <whoami-rajat> let's get started
14:05:09 <whoami-rajat> #topic announcements
14:05:14 <whoami-rajat> first, 2023.2 Bobcat PTG summary
14:05:24 <whoami-rajat> the summary is ready now, you can see it on the wiki page
14:05:29 <whoami-rajat> #link https://wiki.openstack.org/wiki/CinderBobcatPTGSummary
14:06:04 <whoami-rajat> do check out the relevant topics and action items that are assigned to you
14:06:33 <whoami-rajat> next, 2023.2 Bobcat Cinder specific schedule
14:06:56 <whoami-rajat> I proposed the cinder specific schedule for 2023.2 and it is also merged
14:06:59 <whoami-rajat> #link https://releases.openstack.org/bobcat/schedule.html#cinder
14:07:20 <whoami-rajat> you can check out cinder related deadlines on the page
14:07:48 <whoami-rajat> if you scroll up, you will also see the deadlines date wise
14:07:58 <whoami-rajat> in the Project-specific events section
14:08:24 <whoami-rajat> one thing related to the schedule is, we conduct 2 midcycles
14:08:44 <whoami-rajat> for midcycle-1, I've proposed the date 31 May 2023, does it work for everyone?
14:09:20 <whoami-rajat> it's 2 weeks before spec freeze and 4 weeks before driver merge deadline
14:09:40 <rosmaita> looks like there are no holidays anywhere on that day
14:09:51 <whoami-rajat> so it will act as a good checkpoint (according to me)
14:10:01 <whoami-rajat> great
14:10:34 <whoami-rajat> let me know if anyone still has issues/conflicts and we can discuss again
14:11:10 <whoami-rajat> so, coming to midcycle-2
14:11:26 <whoami-rajat> I haven't added it to the schedule since it's far away and we might have conflicts
14:11:33 <whoami-rajat> but i have two good date candidates for it
14:11:38 <whoami-rajat> 1) 02 August, 2023 -- week of Cinder New Feature Status Checkpoint (4 weeks from M3)
14:11:42 <whoami-rajat> 2) 09 August, 2023 -- week of Cinder Driver Features Declaration (3 weeks from M3)
14:13:23 <whoami-rajat> I can bring this up again later but just letting the team know we've a choice between the two dates
14:13:34 <whoami-rajat> whichever suits the majority
14:14:23 <simondodsley> either are fine for me
14:15:21 <whoami-rajat> cool
14:16:20 <whoami-rajat> this is a far fetched date so let's discuss this in 1 month but for safe bet, I will go with 2nd August as default
14:16:43 <whoami-rajat> next, Xena EM on 20th April
14:16:47 <whoami-rajat> #link https://review.opendev.org/c/openstack/releases/+/878882
14:17:03 <whoami-rajat> so we've entered 2023.2 Bobcat cycle and it's time to move the last active stable branch to EM
14:17:05 <whoami-rajat> which is Xena
14:17:28 <whoami-rajat> we are planning to do a final release before cutting the EM branch
14:17:52 <whoami-rajat> we still have some active patches in xena that i think we would like to get in
14:17:55 <whoami-rajat> #link https://review.opendev.org/dashboard/?title=Cinder+Stable+Release+Branches&foreach=%28project%3Aopenstack%2Fcinder+OR%0Aproject%3Aopenstack%2Fpython%2Dcinderclient+OR%0Aproject%3Aopenstack%2Fos%2Dbrick+OR%0Aproject%3Aopenstack%2Fcinderlib+OR%0Aproject%3Aopenstack%2Fpython%2Dbrick%2Dcinderclient%2Dext%29%0Astatus%3Aopen&2023.1=branch%3A%5Estable%2F2023.1&Zed=branch%3A%5Estable%2Fzed&Yoga=branch%3A%5Estable%2Fyoga&Xena=branch%3A
14:17:55 <whoami-rajat> %5Estable%2Fxena
14:18:08 <whoami-rajat> ok, you can go to the etherpad for the link
14:19:11 <whoami-rajat> there is one patch i would like to get into the final xena release which is the multiattach fix we did last cycle
14:19:13 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder/+/874865
14:20:05 <whoami-rajat> once the backports are proposed, I would need one more core to assist me in merging this
14:20:47 <rosmaita> i can do that
14:21:35 <whoami-rajat> great, thanks!
14:21:49 <whoami-rajat> will ping you once the backports are ready :D
14:22:09 <whoami-rajat> so stable cores, please focus on the xena open patches
14:22:24 <whoami-rajat> and if anyone wants their patch to be included in the final release, please start the backport process
14:22:51 <whoami-rajat> moving on to the final announcement
14:22:53 <whoami-rajat> In person PTG team list
14:22:59 <whoami-rajat> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033291.html
14:23:16 <whoami-rajat> you can find the list of teams going to visit the Vancouver PTG in June
14:24:26 <whoami-rajat> that's all the announcements I had, anyone would like to add anything?
14:25:53 <whoami-rajat> guess not, let's move to topics!
14:25:57 <whoami-rajat> #topic PTG follow-up: EOL rocky and stein
14:26:01 <whoami-rajat> rosmaita, that's you
14:26:10 <rosmaita> hi
14:26:44 <rosmaita> i was reading the PTG summary and noticed that there's the action item about proposing EOL for rocky & stein to the mailing list
14:27:17 <rosmaita> i put our proposal into an etherpad to make sure we agreed on how to express this before sending
14:27:38 <rosmaita> #link https://etherpad.opendev.org/p/cinder-EOL-rocky-stein
14:28:14 <rosmaita> next question is, i thought whoami-rajat would send this out as PTL?
14:28:56 <whoami-rajat> sorry i forgot about that before, I've added a minor correction and one comment on the etherpad regarding the increasing number of EM branches
14:29:16 <rosmaita> i think about the EM branches, we can keep them as few as we want
14:29:31 <whoami-rajat> rosmaita, oh, I don't have any issue but you've already written the response so ...
14:29:54 <whoami-rajat> yeah, right now there are 6
14:30:13 <whoami-rajat> after stein/rocky are gone there will be 4
14:30:25 <whoami-rajat> and after xena EM will be 5
14:30:44 <whoami-rajat> my concern basically is we EOL less frequently but EM branches every 6 months
14:30:56 <whoami-rajat> so EM will keep on increasing unless we EOL timely
14:30:59 <rosmaita> 3 is a better number, but once train is gone, no py2 (which is good or bad, depending on how you look at it)
14:32:08 <whoami-rajat> 3 sounds good, 3 EM, 3 active stable, 1 development
14:33:39 <rosmaita> i guess let's get rocky and stein closed first, then we can figure out what to do with t, u, v
14:35:00 <whoami-rajat> you mean t, u because v, w, x will be EM? but yeah let's take one step at a time
14:35:47 <rosmaita> ok
14:35:49 <whoami-rajat> do you want me to send this out? I understand the reasoning but the mail coming from former PTL should be equally good enough
14:37:11 <rosmaita> either way
14:37:46 <rosmaita> the text says "we" so it should be clear enough that it's on behalf of the team
14:38:13 <whoami-rajat> yes, ok, we can decide after the meeting
14:38:26 <rosmaita> sounds like no one has any objections, so looks like it's good to go with your correction
14:39:01 <whoami-rajat> and other people who were part of the PTG discussion, please take a look at the email since multiple people contributed to the points written in the email
14:39:22 <whoami-rajat> works for me but still saying out loud ^
14:40:31 <simondodsley> looks ok to me
14:44:17 <whoami-rajat> rosmaita, if you're good with this, should we move to the next topic?
14:44:24 <rosmaita> sure
14:44:51 <whoami-rajat> cool
14:44:57 <whoami-rajat> #topic Status of openstack-on-windows
14:44:59 <whoami-rajat> rosmaita, that's you again
14:45:36 <rosmaita> yeah, so cloudbase has pulled back on supporting openstack on windows
14:45:46 <rosmaita> looking like the project will be retired
14:45:47 <whoami-rajat> :(
14:46:11 <rosmaita> we use os-win in a few places
14:46:31 <rosmaita> but the big problem is that cloudbase ran all the windows CI
14:46:35 <simondodsley> i wonder if Microsoft would be interested, especially as they have adopted OpenStack as a service offering for Telcos.
14:47:35 <rosmaita> i wonder whether Microsoft is more interested in just having openstack be able to run windows VMs
14:47:48 <rosmaita> not necessarily using hyperv for virtualization, i mean
14:48:39 <rosmaita> at this point, i'm just bringing this up for awareness
14:48:44 <simondodsley> i'd be interested in how many Hyper-V OpenStack deployments there are globally?
14:48:48 <whoami-rajat> that would be great if they step in
14:48:55 <rosmaita> 2% of openstack
14:49:21 <rosmaita> (jamespage found that number during the TC meeting yesterday)
14:49:34 <rosmaita> so it's a pretty small user base
14:49:52 <simondodsley> but still disenfranchising a number of people
14:50:03 <rosmaita> that's true
14:50:12 <simondodsley> they should be canvassed to see if they are interested
14:50:17 <rosmaita> so the plan is for the TC to publicize this and see if anyone cares
14:50:46 <rosmaita> i guess we can bring it up with the Foundation, i think Microsoft has someone on the board
14:50:53 <simondodsley> if it gets killed, do we have to remove all that os_win code from cinder and os_brick master branches?
14:51:19 <rosmaita> i think nova will remove hyper-v support
14:51:36 <rosmaita> we will probably have to remove it eventually as the library ages
14:52:38 <rosmaita> i'm really sad to see the CI go away ... Lucien was really good about watching it and putting up patches when we did something that inadvertently broke openstack on windows
14:53:15 <rosmaita> that's all from me
14:53:53 <whoami-rajat> IIRC we stopped removing the in-tree drivers, we just mark them supported if their driver/CI isn't maintained
14:54:07 <whoami-rajat> s/supported/unsupported
14:55:17 <rosmaita> there are the drivers, but there's also some windows compatibility code in cinder
14:55:47 <whoami-rajat> ok
14:56:03 <whoami-rajat> pretty bad we've one less maintainer now
14:56:04 <rosmaita> anyway, i like simon's idea to reach out to microsoft, i will ask the TC to do that
14:56:15 <whoami-rajat> +1
14:57:17 <whoami-rajat> we've few minutes left, let's move to open discussion
14:57:20 <whoami-rajat> #topic open discussion
14:58:46 <inori> Excuse me, I'd like to bring attention in this patch here. https://review.opendev.org/c/openstack/cinder/+/847730
14:58:55 <inori> This patch is already have one +2, and I've added this patch into the review request.
14:59:02 <inori> So could you please review it at your earliest convenience?
15:00:07 <whoami-rajat> IIUC this is a feature and the priority of features (at least for me) is towards M-3 but that shouldn't stop anyone from reviewing merging these changes ^
15:00:41 <whoami-rajat> please take a look at the review request section
15:00:43 <whoami-rajat> and we're out of time
15:00:48 <whoami-rajat> thanks everyone for joining
15:00:50 <whoami-rajat> #endmeeting