14:00:36 #startmeeting cinder 14:00:36 Meeting started Wed Mar 6 14:00:36 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:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:36 The meeting name has been set to 'cinder' 14:00:40 #topic roll call 14:00:56 o/ 14:01:17 o/ 14:01:17 o/ 14:01:24 o/ 14:01:26 o/ 14:01:41 o/ 14:01:43 o/ 14:02:10 #link https://etherpad.opendev.org/p/cinder-caracal-meetings 14:02:13 o/ 14:03:37 hello everyone 14:03:40 let's get started 14:03:42 #topic announcements 14:03:47 Results of TC and PTL elections 14:03:51 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/OLLRWKP2FSSG5YK5F6M4TOEIHXSLCJ2X/ 14:03:55 #link https://governance.openstack.org/election/#2024.2-ptl-candidates 14:04:01 #link https://governance.openstack.org/election/#2024.2-tc-candidates 14:04:05 the TC and PTL results are out 14:04:19 we already know who the next cinder PTL is so no surprises there 14:04:27 but if you would like to check who is leading other projects 14:04:34 and our newly added TC members 14:04:42 please check the links above 14:05:10 i think there's going to be a TC election, so that one's not finalized yet 14:05:31 hi 14:05:59 oh 14:06:04 i didn't understand this statement in the email 14:06:05 Now begins the campaigning period where candidates and electorate 14:06:06 may debate their statements. 14:06:16 yeah, that's for the TC 14:06:53 so we have 7 people on the TC list but TC only has 6 members right? 14:07:19 9 members total, not sure if we replace 4 or 5 this cycle 14:07:59 you serve for 1 year on the tc, but some people are elected in fall, some in spring 14:08:21 the idea is that way, there's some continuity 14:09:27 okay, i should gather more info on how the TC works before commenting, but glad we have rosmaita to let us know 14:09:38 :D 14:09:59 so that was about the elections 14:10:04 next, Transition victoria -> xena to unmaintained 14:10:14 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/XHN5T4HQHUQYCRVUUCBPMEIMCDOMTXQC/ 14:10:21 #link https://review.opendev.org/c/openstack/releases/+/910409 14:10:34 initially we moved yoga from stable to EOM to test out the process 14:10:45 and now we are moving victoria to xena in EOM 14:10:51 the idea is to remove the stable branches 14:10:54 and create new unmaintained branches 14:11:09 The release team has a patch for each project 14:11:40 for cinder i verified hashes for all projects from victoria to xena but wanted to let cinder team take a look as well 14:11:43 since it's a big change 14:11:53 but as i can see they have merged the patch with my approval ... 14:12:25 makes you feel good as the outgoing PTL, eh... 14:12:59 :D 14:13:55 anyway, so now we will have unmaintained branches from victoria -> yoga and all patches needs to be proposed there 14:15:41 there will be a difference in case of SLURP releases but that won't be until next to next release so we can worry about it later 14:15:50 i noticed that the auto-generated patches to master for the releasenotes have been posted ... they pull from unmaintained/vwx ... i think we want to use the -eom tags instead? 14:16:03 rosmaita, yes 14:16:09 at least thats what we decided for yoga 14:16:16 i can modify those 14:16:16 was there a discussion about it in TC? 14:16:32 no, i didn't bring it up, it's up to the projects to decide 14:16:37 that cinder will be taking a different route than other projects on this? 14:16:42 okay, if that's the case 14:16:44 we are good 14:16:51 well, glance is taking the same route :) 14:17:02 I was worried if something changes and cinder is the only one broken 14:17:03 anyway, don' 14:17:19 t merge them, i'll get the revisions up later today 14:17:36 sure, thanks! 14:18:01 ok, next, Upcoming Deadlines & Dates 14:18:07 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5LVI4E425B3XCXD227NCZOFDWV7BSJLK/ 14:18:14 Cycle Highlights Due: March 7th, 2024 (R-4 week) 14:18:15 RC1 deadline: week of March 11, 2024 (R-3 week) 14:18:15 Final RC deadline: week of March 25, 2024 (R-1 week) 14:18:15 Final 2024.1/Caracal release: April 3, 2024 14:18:15 Dalmatian PTG: April 8-12, 2024 14:18:21 we have cycle highlights deadline this week 14:18:31 but i was planning to get the FFE features in 14:18:38 before proposing that patch 14:18:45 I've added a topic for it 14:19:16 anyone would like to announce anything else? 14:20:49 okay, let's move to topics then 14:20:52 #topic FFE features 14:21:00 1. [NetApp] LUN space-allocation support for iSCSI 14:21:10 #link https://review.opendev.org/c/openstack/cinder/+/893106 14:21:23 i went through it and it looks good 14:21:26 netapp ci is also passing 14:21:38 rosmaita, had some comments on it 14:22:00 if those are addressed, i think we are good on this 14:22:14 i'll look right after the meeting 14:22:29 rosmaita comments are addressed 14:22:29 great, thanks 14:22:52 thank you 14:23:00 thanks jayaanand 14:23:07 moving on 14:23:10 2. Dell EMC: PowerMax - Configurable SRDF snapshots 14:23:17 #link https://review.opendev.org/c/openstack/cinder/+/910320 14:23:33 anyone from dell team here? 14:23:47 yes 14:23:53 so this is waiting on the powermax CI 14:24:01 is there an ETA on when it will be able to report? 14:24:13 need to ping the lab team again 14:24:32 there was an array upgrade in progress 14:24:45 okay, please let them know we are in the feature freeze exception and this needs to merge today or tomorrow else it will be moved to next cycle 14:24:58 understood 14:25:09 also if dell team can confirm that this feature works in their lab, i think that is also a valid reason to merge it 14:25:25 at least that's what we've done in the past, rosmaita can confirm ^ 14:25:58 I'll let them know 14:26:00 yes, i think that's acceptable as long as no one objects 14:26:13 so if anyone has objections, now is the time to state them! 14:27:09 looks like there are no objections 14:27:15 so happystacker please try getting at least one of the two done and we can go ahead and merge the patch 14:27:18 In the past for these types of situations if they can add output from a successful run in their lab we would temporarily accept that. 14:27:26 that would be great! thanks team 14:27:47 ok thks whoami-rajat 14:28:01 as jungleboyj said, running tempest locally and adding output as a comment on the patch is acceptable 14:28:10 :-) 14:28:32 Thank you whoami-rajat & rosmaita for all of the reviews. 14:29:10 np 14:29:17 3. [HPE XP] Support HA 14:29:25 #link https://review.opendev.org/c/openstack/cinder/+/892608 14:29:41 i was reviewing this and i mostly agree with rosmaita's comments 14:29:50 the safe get part makes sense 14:30:07 and also fixing the issues with child drivers could be a separate patch if there are too many of similar issues 14:30:12 and it doesn't affect the current feature 14:31:34 the hitachi team mentioned that they are working on addressing the comments 14:31:43 so probably we can expect an update today or tomorrow? 14:32:26 whoami-rajat: I see. we'll try. 14:33:14 okay, just to mention again, we are in feature freeze exception and all patches should be merged by tomorrow since we need to mention them in cycle highlights and cut branch for 2024.1 14:33:28 after which all patches will go into 2024.2 14:33:34 I see. 14:34:48 so i feel we are good on this 14:35:16 moving on 14:35:17 akawai: please ping me in #openstack-cinder when you post a revision 14:36:39 rosmaia: I see. 14:37:26 4. Dell PowerFlex driver: Add Cinder active-active support 14:37:32 #link https://review.opendev.org/c/openstack/cinder/+/899795 14:37:53 so not an A/A expert but compared the code to pure driver (that has A/A) supported and it looked good 14:37:57 the changes are very minimal 14:38:01 the CI is passing 14:38:07 so i didn't find any issues 14:38:13 requires a second reviewer on it though 14:38:58 thank you whoami-rajat 14:39:04 if geguileo has some time, maybe he can verify the A/A part, but anyone is welcome to review 14:39:14 thank you 14:40:44 since we have less time, we still need a second reviewer though ... 14:41:57 i will review 14:42:01 whoami-rajat: I can look now. I am not an expert but have looked at some of the other patches. 14:42:16 Between rosmaita and I it should be good. 14:42:31 sounds good 14:42:39 oh great, thanks for volunteering! 14:42:49 thanks! 14:42:54 excellent, thank you 14:43:00 i just want to grab another A/A patch and make sure the correct functions are implemented & tested 14:43:14 happystacker: i assume you looked at an already merged dell patch? 14:43:23 yes 14:43:26 Pure is a good example, that's what i looked at 14:43:37 that's what we looked at as well 14:43:44 :D 14:43:45 :D 14:43:46 simondodsley: ^^ hooray! 14:43:59 I'm just looking at the patch as well 14:44:04 Pure is setting an example for A/A implementation 14:44:09 this patch is getting a lot of looks! 14:44:35 ;-) 14:45:51 okay, this looks sorted out 14:46:05 last one 14:46:07 5. Ceph: Add option to keep only last n snapshots per backup 14:46:15 #link https://review.opendev.org/c/openstack/cinder/+/810457 14:46:26 zaitcev, had a comment to which Chrsitian has replied 14:47:07 i haven't taken a look and honestly the ceph backup driver scares me 14:47:35 so i can't guarantee if we will be able to get it in before validating with some ceph experts 14:47:44 I'll take another look. 14:48:13 But I think core members should take a look without regard to my question anyway. 14:48:33 Eric and Gorka at the minimum. 14:50:15 ++ Yeah, for Ceph backup we really need one of those two. 14:50:52 I would be happy to delegate the review responsibility, but let's see if we are able to get it in 14:52:19 there was also a request from Fujitsu but i feel we already have a lot to be reviewed so unfortunately we will target it in next cycle 14:52:37 other than that, I think we are covered on features 14:53:12 maybe we can prioritize fujitsu for immediately after RC-time 14:53:32 get it in really early into Dalmatian 14:53:36 +1 14:53:47 we have Fujitsu and Hitachi that have a long list of patches 14:53:50 #link https://etherpad.opendev.org/p/cinder-2024.1-caracal-features 14:53:57 so better to target them early next cycle 14:54:37 well, if we are short on ptg topics, maybe we can have a fujitsu/hitachi review festival during ptg week 14:55:21 maybe jbernard would like to be reminded about it :D 14:55:45 whoami-rajat: thanks :) 14:55:53 I have no issues with the idea 14:57:37 okay quickly i will go through the next topic 14:57:40 #topic Deprecate python-cinderclient-brick-ext 14:57:44 I was going through the history of changes in this project and found out the last functional change was 3 years ago 14:57:48 #link https://github.com/openstack/python-brick-cinderclient-ext/commit/26495b75bb2ace278214d5961eefbd21014811b9 14:57:51 Recently all patches proposed to this project are maintainance related and I was wondering if we want to maintain this project or just deprecate it and recommend using older versions? 14:57:55 Do we have contributors that actively want to work on it or keep releases ongoing for other reasons? 14:58:09 (good thing i wrote all this before) 14:58:19 the only person i know who really uses it is hemna 14:59:25 okay, but there is no active development on it for a long time so there is maintenance overhead 14:59:42 if hemna- is good with older versions 15:00:07 then we can probably deprecate it 15:01:33 we are out of time, we can get back to it next week or during PTG 15:01:36 thanks everyone for attending 15:01:39 #endmeeting