14:00:40 #startmeeting cinder 14:00:40 Meeting started Wed Nov 1 14:00:40 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:00:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:40 The meeting name has been set to 'cinder' 14:00:45 #topic roll call 14:03:08 hi 14:03:12 o/ 14:03:17 Hi! 14:03:40 o/ 14:05:10 o/ 14:05:38 either we have few people around or people are shying away from the roll call 14:05:53 i think it's a holiday in a lot of countries today 14:06:05 oh 14:06:16 i wasn't aware ... 14:06:58 Yes, holidays in India. 14:07:21 Happy Kannada Rajyothsava 14:07:58 I had a few things to discuss but would be better if we have good team strength 14:08:26 yes, it's a holiday in certain parts of India (sadly not for me) 14:08:47 let's continue with the meeting and we can reiterate it in the next meeting as well 14:09:01 #topic announcements 14:09:05 first, 2024.1 Caracal PTG Summary 14:09:26 I've prepared the summary for the 2024.1 PTG we had last week 14:09:34 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/SRW5QAGEZ7UY4FC62RGY2XGGAGSCOW7U/ 14:09:38 #link https://wiki.openstack.org/wiki/CinderCaracalPTGSummary 14:09:55 please take a look at the #action sections of each topic 14:10:15 and plan your action items accordingly 14:10:21 next, 2024.1 Caracal Cinder specific release schedule 14:10:27 #link https://review.opendev.org/c/openstack/releases/+/899847 14:10:47 I've proposed the cinder specific release schedule for 2024.1 cycle 14:10:55 there were 2 things i needed some discussion around 14:10:59 Midcycle 1 : Wednesday 6th December 2023 (1400-1600 UTC) 14:10:59 Midcycle 2 : Wednesday 14th February 2024 (1400-1600 UTC) 14:11:08 if the above dates are conflicting with any other major event 14:11:54 let's get back to this next week when we have the whole team back 14:12:16 that was all for the announcements 14:12:26 anyone has anything else to announce? 14:14:00 ok, let's move to topics 14:14:10 #topic Unassigned Work items from PTG 14:14:34 there were 2 items from PTG discussions that were unassigned 14:14:44 1) fixing RBD retype regressed in Wallaby 14:14:45 2) Encryption retype 14:15:31 if anyone is interested, feel free to work on it 14:15:48 but please make the team aware before doing it else 2 people might end up working on same thing 14:17:07 that's all for this topic, moving on 14:17:14 #topic Review priorities for M-1 14:17:39 there are 2 things that we should review on priority (one of them at least) 14:17:44 1. SqlAlchemy 2.0 support 14:17:53 #link https://review.opendev.org/c/openstack/cinder/+/880657 14:18:03 there are 5 patches in the relation chain on the right side 14:18:16 Mostly S or XS patches so should be a quick review 14:18:54 ++ 14:18:55 we need to get this support in before M1 so OpenStack can start using sqlalchemy 2.0 14:19:10 as per stephen, only cinder and manila projects are remaining 14:19:21 i'm working on "fixing RBD retype regressed in Wallaby" 14:19:22 so that also doesn't reflect good on our project! 14:19:55 whoami-rajat: i can look at / test the sqlalchemy patches 14:19:57 eharney, oh ok, i thought you mentioned that you will find someone to work on it 14:20:07 good to know 14:20:12 so we have only one item unassigned 14:20:17 jbernard, great, thanks! 14:21:26 ok next is 14:21:29 2. NFS extend in-use volume support spec 14:21:40 this has been dragging for past 2 releases 14:21:57 the nova team and the author are not happy that it's been on hold from cinder side 14:22:24 so I've planned to prioritize this feature to get it in early since it also requires nova side changes 14:22:38 for now the spec is a reproposal with minor edits 14:22:49 so we can get that in faster 14:23:14 i was anyway going through the whole spec to see if i missed something there but if people have the context about it 14:23:29 they can go ahead and vote on it 14:24:28 any doubts/concerns on this topic? 14:26:54 okay, let's move to the next topic then 14:27:07 #topic New structure for review request section 14:27:31 so we discussed during the PTG that the current way of requesting reviews is not so good 14:28:00 the long list of patches demotivates reviewers from taking a look 14:28:16 Heck I didn't even know review requests existed, I always re-scan everything 14:28:42 zaitcev, it's on the etherpad, right after announcements and Topics 14:28:55 so the new structure is as follows 14:28:57 One author can only add one patch for review 14:28:57 The patch should be based on the approaching deadling 14:28:57 Eg: If M-2 is upcoming, driver reviews is a priority but if M-3 is upcoming, features are a priority. 14:28:57 There should be a comment regarding the patch being added 14:28:57 This could be a simple explanation of what the patch is doing or the current status of the patch 14:29:31 that pretty much addresses all the concerns we had with it during the PTG 14:29:41 but if not, happy to modify it 14:29:51 that sounds reasonable 14:30:14 is akawai around? 14:30:18 Sounds good. 14:30:21 yes 14:31:02 akawai, i can see you have added patches to the review request section, can you go through the above guidelines and update your review request? 14:31:26 i see. 14:31:49 this will help reviewers focus on what is important and can plan their review bandwidth accordingly 14:32:36 rosmaita, jungleboyj thanks for going through it 14:33:05 that's all from my side 14:33:21 we don't have any more topics 14:33:25 so let's move to open discussion 14:33:28 #topic open discussion 14:36:03 i guess we can end early today 14:36:15 thanks everyone for joining 14:36:28 Thank you! 14:36:30 Thank you! 14:36:35 don't forget to follow up on the PTG action items 14:36:38 #endmeeting