14:00:29 #startmeeting cinder 14:00:29 Meeting started Wed Oct 4 14:00:29 2023 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:29 The meeting name has been set to 'cinder' 14:00:36 o/ 14:00:43 #topic roll call 14:00:54 hi 14:00:58 Saikumar: you were slightly early :) 14:01:00 o/ 14:01:01 o/ 14:01:16 o/ 14:01:16 o/ 14:01:18 o/ 14:01:22 o/ 14:01:25 o/ 14:01:53 o/ 14:02:03 o/ 14:02:06 Rajat is caught up in a customer issue (i think i can say that, it's no secret that we have customers and they occasionally have issues) 14:02:21 #link https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:02:33 welcome to the final meeting of the bobcat cycle! 14:02:53 which i guess brings us directly to 14:02:58 #topic announcements 14:03:21 2023.2 (Bobcat) release is tomorrow 14:03:49 but we are already tagged for 23.0.0 from RC 2, i believe 14:04:15 thanks to everyone for their contributions, and for another successful development cycle 14:04:26 and on-time, too 14:05:04 next item 14:05:46 I put up a proposal to make Jon Bernard a stable core for cinder 14:05:55 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-October/035259.html 14:06:09 so obviously i am in favor of the proposal 14:06:19 and i have seen only positive responses on the ML so far 14:06:36 i should say a few things about how openstack operates 14:06:53 when proposals are made on the ML, we have a "lazy consensus" model 14:07:17 so basically, we assume that everything is OK unless someone says otherwise 14:07:53 so probably Rajat will wait for about a week to make sure there are no objections, and then he will make Jon a stable core 14:08:12 ++ 14:08:14 if you are wondering what a "stable core" is, we have a handy guide hidden in the cinder docs 14:08:17 I don't see why not. Jon doesn't seem like having a history of rubber-stamping dubious patches. 14:08:44 (so well hidden that i can't find it) 14:08:54 #link https://docs.openstack.org/cinder/latest/contributor/cinder-groups.html 14:09:02 that explains the various groups ^^ 14:09:33 also, since many of our contributors want to fix stuff and then backport fixes to older branches 14:09:41 here's a reminder of the way that works 14:09:56 #link https://docs.openstack.org/project-team-guide/stable-branches.html 14:10:02 (that's the openstack-wide policy) 14:10:11 #link https://docs.openstack.org/cinder/latest/contributor/backporting.html 14:10:28 (that's cinder-specific info about backports) 14:11:06 one more link, this is the general guide to the cinder project for contributors: 14:11:11 tiny.cc/cinder-info 14:11:59 ok, final announcement 14:12:00 Great to see all these listed in one place at last - now to put this list somewhere permanent 14:12:20 well, it's permanent, just not easily discoverable! 14:12:27 godd idea! 14:12:29 that's really what i meant 14:12:50 which reminds me ... people sometimes ask about easy first contributions 14:13:01 remember that the cinder docs are in the code repository 14:13:17 so fixing documents is just as "real" a contribution as code fixes 14:13:49 and i got off track there, here is the final announcement: 14:13:59 Add topics for 2024.1 (Caracal) PTG 14:14:13 the virtual PTG will be held 23-27 October 14:14:24 #link https://etherpad.opendev.org/p/caracal-ptg-cinder-planning 14:14:32 Rajat is collecting topics ^^ 14:15:20 it might be a good use of time to do a doc review to maybe re-organize them, or to identify holes in our docs 14:15:31 (if anyone wants to lead such a session, add it to the etherpad!) 14:16:05 ok, that's all the official announcements ... anyone got anything else to announce? 14:16:38 oh o/ our outreachy proposal got accepted (osc client gap) 14:16:59 nice! 14:17:11 #link https://www.outreachy.org/outreachy-december-2023-internship-round/communities/openstack/reduce-openstack-client-gap/cfp/ 14:17:33 is there anything we can do to get potential outreachy participants interested? 14:18:04 maybe we need to mention in each meeting how exciting and important it is to address the osc / cinderclient gap 14:18:40 im not sure sure honestly, applications are being accepted, so potential folks are encouraged to reach out 14:18:47 i haven't heard anything yet, but it's only been a day 14:19:58 jbernard: will you be mentoring? do you need help? 14:20:49 i will be, im happy to take it on and will ask for help if needed, you're certainly welcome to co-mentor, everythign helps 14:21:35 ok, so anyone interested in helping out, contact jbernard 14:21:39 thanks! 14:21:49 ok, on to the regular topics 14:22:10 looks like mostly review requests 14:22:22 Increase size of volume image metadata values 14:22:37 #link https://review.opendev.org/c/openstack/cinder/+/868485 14:22:55 i think this one is in good shape, has some excellent tests, not sure what the holdup is 14:23:43 anyone have any questions about the patch? 14:24:41 it's got a +1 from zaitcev and he is not an easy reviewer 14:25:02 i've looked at it a few times, but i'm a bit confused about what's going on there when i look at it today 14:25:26 it doesn't change field lengths in our db model? 14:25:44 no, we already had the right size field 14:25:47 Well. I'm stickler to details but you can easily hoodwink me about the global architecture of Cinder.. 14:25:49 ah right 14:26:01 our schema validation was rejecting the "too long" values 14:26:27 we had discussed the mismatch between character count and byte count for utf-8 14:26:52 yeah, i remember being ok with this whole thing a while back, but it's been long enough that i forgot the details, and the commit message doesn't really spell it out :/ 14:26:53 seems good though 14:26:55 and the author added custom schema validation to make sure the bytes will fit regardless of character count 14:27:50 ok, so eharney can we count on you taking a closer look in the next few days? 14:27:56 yes 14:28:02 excellent 14:28:18 thanks folks! 14:28:21 ok, simondodsley i think you have the next 2 14:28:37 Yep - first is just a bugfix backport 14:29:26 ok, i reviewed the patch to master, so i will take a look 14:29:46 second is more extensive. This one includes work from an abandoned patch by geguileo and a bug fix 14:30:08 it also enables a volume to be sync repl volume to be created during a failover event 14:31:03 We did them all as one as the interlock was a bit messy for multiple dependant patches 14:32:00 ok, sounds reasonable 14:33:22 any questions for Simon? 14:33:37 Thanks guys for the +2s and +W on the backport 14:34:35 next up, 2 patches from Dell ... happystacker is that you? 14:35:34 the patches look pretty straightforward 14:37:06 ok, looks like a job for stable cores since they are both backports 14:37:39 raghavendrat: any helpful comments about your patch? 14:37:42 #link https://review.opendev.org/c/openstack/cinder/+/887559 14:37:46 hi 14:38:16 i have received one +2 ... Rajat had a comment. i replied in code review 14:38:30 waiting for Rajat's response 14:38:42 was just looking, looks like you explained the issue and have some helpful comments in the code also 14:39:33 this patch is one of the patches targeted for RC2 14:39:50 yes two backports 14:40:12 looks like we missed that, but we'll be doing another bobcat release in a month or so, i imagine 14:40:31 ok 14:41:01 since Rajat already reviewed, i'm inclined to let him follow up, especially since you have a +2 from Walt 14:41:23 fine. thanks for having a look 14:41:32 hopefully we can get this knocked out before the next meeting 14:41:51 happystacker: Backports are taken care of. 14:42:01 jungleboyj: thanks! 14:42:07 Welcome. :-) 14:42:15 final item on the list is from eharney 14:42:19 thks guys! 14:42:25 #link https://review.opendev.org/c/openstack/cinder/+/888296 14:43:27 yep 14:44:46 it's a bugfix 14:45:13 looks like an old bug, too 14:45:26 :-) 14:45:29 oslo fix is from 2017! 14:45:37 wow! 14:45:37 there's also a task for someone to work on us not duplicating code out of oslo.db there 14:45:47 but this was the quick fix 14:46:35 ok, i will commit to looking at this one 14:46:56 this is slightly off topic, but the fact that you had to recheck reminded me of something 14:47:12 i have seen a few weird openstack-tox-py310 failures 14:47:24 but they don't seem to be systematic, which is weird 14:47:41 because the error is 14:47:43 oslo_config.cfg.NoSuchOptError: no such option cinder_internal_tenant_project_id in group [DEFAULT] 14:47:55 which you'd think would happen on every run 14:48:04 so i'm not sure what's going on there 14:48:17 just want to give a heads up to anyone about to do a recheck 14:48:41 if you see that error, put a shout in the #openstack-cinder channel so we can keep an eye on it 14:49:20 The bug for that boolean thing makes sense. Even if making the request were pointless, it removes a traceback. 14:50:16 and that brings us to 14:50:21 #topic Open Discussion 14:50:24 the request actually makes sense, it's just that, i guess not too many people are using this functionality 14:52:48 anyone got anything they'd like to discuss? 14:54:11 guess not 14:54:57 ok, thanks for attending everybody ... don't forget to add topics to the PTG etherpad: 14:54:58 https://etherpad.opendev.org/p/caracal-ptg-cinder-planning 14:55:20 next meeting will be the first of the Caracal cycle, see you then! 14:55:29 #endmeeting