14:00:00 <whoami-rajat> #startmeeting cinder
14:00:00 <opendevmeet> Meeting started Wed Mar 20 14:00:00 2024 UTC and is due to finish in 60 minutes.  The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:00 <opendevmeet> The meeting name has been set to 'cinder'
14:00:02 <whoami-rajat> #topic roll call
14:00:04 <happystacker> o/
14:00:06 <Luzi> o/
14:00:08 <zaitcev> o/
14:00:13 <Dessira> o/
14:00:30 <eharney> o/
14:00:32 <simondodsley> 0/
14:00:41 <rosmaita> o/
14:01:14 <crohmann> o/
14:01:21 <msaravan> Hi
14:01:26 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-caracal-meetings
14:01:41 <cuiyeliu> o/
14:02:06 <jungleboyj> o/
14:02:06 <whoami-rajat> we have a good number of people around today
14:03:01 <whoami-rajat> let's get started
14:03:07 <whoami-rajat> #topic announcements
14:03:13 <whoami-rajat> Proposing Pete Zaitcev as core
14:03:17 <whoami-rajat> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/NRYTHQY5GV6H6IDW2YFNJVUZNEBWTPYB/
14:03:21 <whoami-rajat> Given all the details mentioned in my mail, I feel Pete is a good candidate for the cinder core team
14:03:25 <whoami-rajat> Please add your opinion on the thread if you feel strongly (positive/negative) about it
14:03:31 <whoami-rajat> The thread will be open for a week, If there are no objections, I will add Pete to the cinder core group
14:04:24 <whoami-rajat> next, 2024.2 Dalmatian vPTG
14:04:24 <zaitcev> Remember guys, it's like the reviews. -1 is okay!
14:04:44 <whoami-rajat> :D
14:04:49 <zaitcev> ^_^
14:05:07 <jungleboyj> :-)
14:05:14 <simondodsley> can i do that in the Novemebr US elections?
14:05:27 <jungleboyj> Sounds like an unwilling candidate.  ;-)
14:06:35 <whoami-rajat> okay moving on
14:06:41 <whoami-rajat> next, 2024.2 Dalmatian vPTG
14:06:50 <whoami-rajat> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/HYHKKI3PCBIIGOVW3HGXO2GW26ARURPR/
14:07:19 <whoami-rajat> the vPTG is in 3 weeks
14:07:26 <whoami-rajat> if you haven't registered yet, register here
14:07:28 <whoami-rajat> #link http://ptg2023.openinfra.dev/
14:07:44 <whoami-rajat> also this time the PTG will be in meetpad
14:07:45 <crohmann> https://ptg2024.openinfra.dev/ ?
14:08:51 <whoami-rajat> it should be 2024 right
14:09:07 <whoami-rajat> looks like Kendall had a typo in her email which i didn't double check
14:09:10 <whoami-rajat> thanks crohmann
14:09:18 <whoami-rajat> #link https://ptg2024.openinfra.dev/
14:09:48 <whoami-rajat> so this time the PTG will be in meetpad
14:09:56 <whoami-rajat> since we are promoting open source tools
14:10:12 <whoami-rajat> my past experience hasn't been great with it, but maybe they've improved the tool since then
14:11:08 <whoami-rajat> anyways, something Jon needs to be careful about, and plan alternatives if something goes wrong
14:11:41 <jungleboyj> Yeah, the e-mail had the old ptg info linked.  :-(
14:12:31 <whoami-rajat> yes
14:13:50 <whoami-rajat> I've replied to Kendall's email correcting it
14:13:56 <whoami-rajat> so others don't make the mistake I did
14:14:15 <whoami-rajat> okay moving on
14:14:17 <whoami-rajat> next, Releases
14:14:25 <whoami-rajat> first, RC1
14:14:32 <whoami-rajat> #link https://review.opendev.org/c/openstack/releases/+/912386
14:14:41 <whoami-rajat> the RC1 release for 2024.1 is done
14:14:46 <whoami-rajat> master is now 2024.2 and you should see a stable/2024.1 branch for Caracal
14:14:53 <whoami-rajat> any release critical bugs should be added to the following etherpad
14:14:57 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-caracal-rc-bugs
14:15:17 <whoami-rajat> I see 2 have been added
14:15:39 <whoami-rajat> I reviewed the dell one but it didn't have CI running
14:16:16 <whoami-rajat> given the reply on my comment, the dell patch seems really important as it's affecting 7 cinder operations
14:16:17 <crohmann> What's the policy of adding bugs to that Etherpad? I have a few bugfixes for cinder-backup queued up (pending final review + merge)
14:16:54 <bryanneumann> whoami-rajat, I will bring this up today with my other colleagues
14:16:55 <yian> the dell pachset 4 has passed CI on Mar 12
14:17:06 <whoami-rajat> crohmann, if the bugs really need to be in the Caracal release, like a regression or security vulnerability, we add them to the etherpad
14:17:15 <whoami-rajat> if they are release independent then we can push them to next cycle
14:17:27 <whoami-rajat> bryanneumann, ack thanks
14:17:51 <whoami-rajat> yian, if the CI is inactive, is it possible to get a local tempest run results posted on the patch?
14:18:37 <crohmann> Well all but one are fixes for bugs. Would not call them release critical, but nice to have fixed.
14:19:12 <whoami-rajat> okay, we can merge them in master as well, the purpose of the etherpad is to track their backports and do a RC2 release
14:19:19 <whoami-rajat> anything going into master is acceptable
14:19:36 <happystacker> I think there's one patch missing about SRDF
14:19:43 <yian> rajat, the latest patchset passed CI on Mar 12
14:20:05 <whoami-rajat> happystacker, i think it was a feature and that was merged?
14:20:29 <whoami-rajat> yian, oh, it was on latest PS? then i think we can consider the results
14:20:54 <happystacker> You're right it's merged whoami-rajat
14:20:55 <crohmann> K. My concern is getting them reviewed and merged to master and not have them dangling more than to target a certain release. I'd argue though that for some a backport might make sense.
14:21:06 <happystacker> we probably need to cherry-pick it
14:21:31 <yian> rajat, yes, thanks!
14:22:11 <whoami-rajat> crohmann, we can do backports anytime and do a stable branch release, just right now I'm targeting the stability of caracal release
14:22:48 <whoami-rajat> happystacker, it was merged in Caracal before RC1 so we won't need that, also feature backports aren't allowed as per Cinder backport policy
14:23:24 <happystacker> awesome, yes I forgot about feature backport
14:24:26 <whoami-rajat> anyways, my point was to list the bug fixes that are critical for the release
14:24:31 <whoami-rajat> and we can plan backports and RC2 accordingly
14:25:40 <whoami-rajat> next is the cinder-tempest-plugin release
14:25:44 <crohmann> right. I kept myself from placing all of them in the "request for review" section again :-)
14:25:59 <whoami-rajat> #link https://review.opendev.org/c/openstack/releases/+/913538
14:26:58 <whoami-rajat> The release patch looks good to me but if anyone is interested in the cinder-tempest-plugin release, please take a look
14:28:24 <whoami-rajat> next, Recheck analysis
14:28:30 <whoami-rajat> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/7L6DSFN6GB65FBVHQATTLSQ7HWGBZJHM/
14:28:57 <whoami-rajat> they ran the recheck numbers for all projects and cinder seems to be in a good spot
14:29:00 <whoami-rajat> it's for last 30 days
14:29:05 <whoami-rajat> bare recheck: 15
14:29:05 <whoami-rajat> all recheck: 77
14:29:05 <whoami-rajat> bare recheck %age: 19.48%
14:29:13 <whoami-rajat> It is a good percentage but still would like to promote people to avoid bare rechecks
14:29:19 <whoami-rajat> check the job that is failing
14:29:19 <whoami-rajat> check the logs why it's failing
14:29:19 <whoami-rajat> recheck providing the reason of failure
14:29:52 <whoami-rajat> even if the failure is unrelated to your patch, if it's reoccuring in gate, we can report a bug for it and try to fix it
14:30:02 <whoami-rajat> s/reoccuring/recurring
14:31:54 <whoami-rajat> next, RBAC discussion at PTG
14:32:02 <whoami-rajat> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DUNYNB2AVKAZBYLIZDZUWZ4622QSIRNO/
14:32:09 <whoami-rajat> #link https://etherpad.opendev.org/p/rbac-2024.2-ptg
14:32:31 <whoami-rajat> there will be a RBAC discussion during PTG, if you are interested in attending it, here are the details
14:32:32 <whoami-rajat> Folsom, Tuesday, April 9 15:00 UTC - 16:00 UTC
14:32:32 <tosky> ooooh, so maybe we can have those cinder-tempest-plugin reviewed and merged in time for that :D
14:33:27 <whoami-rajat> hopefully someone would be excited enough to review them :D
14:34:18 <whoami-rajat> last announcement, Upcoming Deadlines & Dates
14:34:22 <whoami-rajat> Final RC deadline: March 28th, 2024 (R-1 week)
14:34:22 <whoami-rajat> Final 2024.1 Caracal release: April 3rd, 2024
14:34:22 <whoami-rajat> Dalmatian PTG: April 8-12, 2024
14:34:40 <whoami-rajat> that's all we had for announcements
14:35:13 <whoami-rajat> anything else in the community news that i might have missed?
14:36:06 <rosmaita> tc election polling ends in 5.5 hours
14:36:19 <whoami-rajat> oh right
14:36:31 <whoami-rajat> here are the steps
14:36:32 <whoami-rajat> Go to https://civs1.civs.us/cgi-bin/opt_in.pl
14:36:32 <whoami-rajat> Request Activation link and enter the code received on your registered email address
14:36:32 <whoami-rajat> You will receive an email with the subject "Poll: OpenStack 2024.2 Cycle Technical Committee Election Poll"
14:36:32 <whoami-rajat> There are 7 TC proposals that you can arrange in order or preference
14:36:52 <whoami-rajat> s/or/of
14:38:31 <whoami-rajat> if that's all we can move to topics
14:38:44 <whoami-rajat> #topic Pypi maintainers cleanup
14:38:52 <whoami-rajat> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/64IDNMRS6AUC7T3NBAHF3A7RUCXZUFAG/
14:38:55 <whoami-rajat> We have already done this and just for an update
14:38:58 <whoami-rajat> For Cinder, we have 7 repos out of which 5 have been cleaned up. The ones that require cleanup are:
14:39:04 <whoami-rajat> os-brick Maintainer: thingee (Mike Perez)
14:39:04 <whoami-rajat> python-brick-cinderclient-ext Maintainer: e0ne (Ivan Kolodyazhny)
14:39:11 <whoami-rajat> They haven't been active for years and I tried reaching out to the maintainers but they haven't responded so we can safely remove them from the maintainers list.
14:40:20 <whoami-rajat> that was my reply to TC, hopefully we won't have any concerns from Mike or Ivan if they show up
14:40:47 <whoami-rajat> and that's all for this topic
14:41:02 <jungleboyj> ++
14:42:10 <whoami-rajat> IIRC the general idea was to just keep only openstackci as the maintainer of projects so individual contributors cannot do releases outside of the standard openstack release model
14:42:18 <whoami-rajat> which was happening for some project ^
14:42:56 <whoami-rajat> now that was all (really)
14:43:07 <whoami-rajat> moving on to the next topic
14:43:16 <whoami-rajat> #topic Missing indexes in backups database table
14:43:22 <whoami-rajat> #link https://bugs.launchpad.net/cinder/+bug/2048396
14:43:24 <whoami-rajat> crohmann, that's you
14:44:31 <crohmann> This is a bug about the lack of any DB indices in the backups table. Since the "C" release is coming up and schema changes only coming with releases I wanted to nag about this once more
14:47:08 <whoami-rajat> okay, we don't have a patch up for that as of now right?
14:47:37 <whoami-rajat> also i think schema changes will be again part of 2024.2 release since master is Dalmatian now
14:47:38 <eharney> right -- is there any chance this would be landed in Caracal at this point?
14:48:11 <crohmann> That is really unfortunate.
14:48:14 <whoami-rajat> nope, i don't think so
14:48:34 <whoami-rajat> we cannot backport DB schema related changes or migrations
14:49:02 <crohmann> That is why I was nagging about this a few weeklys.
14:52:30 <whoami-rajat> as i can see, there is another topic about re-submission of a spec
14:52:50 <crohmann> So adding indices is not something that could happing in RCs anymore as the "db sync" might not be run on the install?
14:54:06 <whoami-rajat> the master is 2024.2 and we cannot backport any schema related changes so even if we merge the patch it will part of 2024.2 and cannot be backported to 2024.1
14:54:42 <crohmann> right. eharney could we maybe work together on getting this done on master then?
14:56:12 <crohmann> Yes whoami-rajat. That spec is about moving the backup status out of the volume status. This was already merged, but for another release (2023.02).
14:56:32 <crohmann> I just wanted to know if it makes sense to re-submit this for the next release.
14:56:59 <whoami-rajat> if there is bandwidth to implement it, do we have any volunteers for it?
14:57:23 <whoami-rajat> else i think we have an untargeted folder where we can move this spec, is my understanding correct rosmaita ?
14:57:49 <rosmaita> yes
14:58:02 <whoami-rajat> great
14:58:05 <crohmann> see https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-01-03-14.00.log.html#l-37
14:58:42 <crohmann> jon and happystacker were apparently interested
14:59:00 <whoami-rajat> I don't see Jon around, happystacker are you interested in implementing this feature in the next cycle?
14:59:33 <happystacker> unfortunately I'm busing as hell on other activities for the next couple of months
15:00:29 <crohmann> Even if someone or myself were to write the patch ... there needs to be review bandwidth.
15:01:30 <crohmann> Writing this big of a patch and not getting any feedback / review has the potential to be somewhat frustrating.
15:02:17 <whoami-rajat> we might have a new core by next week and Jon might have good strategies for getting changes in on time
15:02:22 <whoami-rajat> but i cannot guarantee that
15:02:30 <whoami-rajat> anyways, we are out of time
15:02:36 <whoami-rajat> thanks everyone for attending
15:02:43 <whoami-rajat> we can continue the discussion on cinder channel
15:02:46 <whoami-rajat> #endmeeting