13:59:36 #startmeeting cinder 13:59:36 Meeting started Wed Sep 13 13:59:36 2023 UTC and is due to finish in 60 minutes. The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:59:36 The meeting name has been set to 'cinder' 13:59:40 #topic roll call 14:00:44 o/ 14:00:46 o/ 14:00:48 o/ 14:00:49 o/ 14:00:50 o/ 14:00:51 o/ 14:00:56 o/ 14:00:56 o/ 14:01:08 o/ 14:01:43 o/ 14:02:14 o/ 14:02:17 o/ 14:02:21 o/ 14:02:25 o/ 14:02:43 #link https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:03:16 o/ 14:03:26 hello everyone 14:03:35 let's get started 14:03:39 #topic announcements 14:03:45 first, Cycle highlights for 2023.2 (Bobcat) 14:03:53 #link https://releases.openstack.org/bobcat/highlights.html#cinder 14:04:04 the highlights for cinder (and other projects) is up 14:04:53 hello 14:05:09 we have a good amount of features, fixes, etc this cycle 14:05:10 thanks everyone for all your contributions 14:05:42 next, RC1 for cinder 14:05:46 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-September/035027.html 14:06:04 the patch for RC1 is up, I've updated the hash to point it to the latest commit 14:06:23 I don't think we have any release critical patches as of now 14:06:41 the release seems pretty stable and bug fixes after RC1 can be backported 14:06:44 so not an issue there 14:06:58 #link https://review.opendev.org/c/openstack/releases/+/894649 14:07:35 o/ 14:07:41 We do have a few patches pending approval for bobcat, would it be possible to have them into Bobcat still? 14:07:49 same here 14:08:24 happystacker, simondodsley is it in the review request section? 14:08:48 Yes it is 14:08:56 yes 14:12:36 happystacker, simondodsley ack, I've created this etherpad and added one patch as a sample, please add the ones you would like to prioritize 14:12:39 #link https://etherpad.opendev.org/p/cinder-bobcat-rc-patches 14:12:55 it seems hard to make it into RC1 but we can surely target it for RC2 14:14:19 ok 14:14:41 thanks for bringing that up 14:14:46 so moving on 14:14:52 next, 2024.1 (Caracal) PTG Planning 14:15:01 #link https://etherpad.opendev.org/p/caracal-ptg-cinder-planning 14:15:14 I've created this planning etherpad for the upcoming 2024.1 (Caracal) PTG 14:15:36 it's going to be held from 23-27 October 14:15:54 we still have more than a month left but no harm in starting the planning early 14:16:09 if you have topics for the upcoming PTG, please add it to the planning etherpad 14:16:41 after that i will arrange them into our main etherpad day wise 14:17:53 i will send an email later today or tomorrow but this is just a heads up to start planning for the PTG 14:18:09 next, PTL/TC Elections 14:18:37 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034995.html 14:18:51 so now the poll is open for PTL/TC elections 14:19:03 last date to vote is 20th september so please cast your vote before that 14:19:12 voting link 14:19:13 #link https://civs1.civs.us/cgi-bin/opt_in.pl 14:20:07 finally we have some upcoming milestones 14:20:14 RC1 deadline: September 14 (R-3 week) 14:20:14 Final RC deadline: September 28 (R-1 week) 14:20:14 Final 2023.2 Bobcat release: October 4 14:20:55 that's all from my side for the announcements 14:21:09 anyone has anything else to announce? 14:22:41 guess not 14:22:49 let's move to topics 14:23:03 #topic What ever happended to the "new" quota system? 14:23:17 I guess crohmann is not around this week as well 14:23:35 a quick update on that would be, I'm planning to work on it next cycle 14:23:50 but the effort could span across to more than 1 cycle 14:24:11 so it's not guaranteed that we will be able to close it in caracal but hopefully make some progress there 14:24:14 if that's helpful 14:24:16 cool 14:24:25 awesome 14:24:39 If I can be of any help, let me know 14:25:10 sure, thanks! 14:25:41 i guess that was it for the topic 14:25:50 next one is again by crohmann 14:25:54 #topic Implementation of merged spec to externalize backup_status 14:26:18 The ask here is if anyone is planning to work on it during the 2024.1 (Caracal) cycle 14:26:23 any takers? 14:27:15 Not me. I need to focus on backup performance with S3 and backup backends used together. 14:27:47 zaitcev, sounds good, does that have an existing spec or you are planning to propose a new spec? 14:29:16 anyway, i think that was also an ask from crohmann but we can evaluate that later in the PTG 14:29:22 For performance, I'm using this: https://bugs.launchpad.net/cinder/+bug/1918119 14:29:38 it's not a feature, so no spec 14:29:55 for two back-ends I am not sure. 14:30:11 ok 14:31:06 sounds good, thanks for your efforts on cinder backups 14:31:23 let's see if we get any takers during PTG 14:31:33 for now i guess no one in this meeting is planning to work on that feature 14:31:49 that feature = Spec to introduce new backup_status field for volume 14:32:02 whoami-rajat: what is the link? 14:32:11 jbernard, https://review.opendev.org/c/openstack/cinder-specs/+/868761 14:32:29 #link https://review.opendev.org/c/openstack/cinder-specs/+/868761 14:33:11 whoami-rajat: im interested possibly, count me as a maybe 14:34:28 If I can help in any way, you can count on me as a maybe as well 14:34:52 jbernard, great, I've added your name to the topic (as a maybe), you can contact crohmann for more info around this (as he has mentioned in the topic itself) 14:34:55 happystacker: maybe we can work on it together, will sync later 14:35:07 ok jbernard 14:36:56 i think that's all for this topic 14:37:00 last topic for today 14:37:02 #topic Patches for a current round of stable release is posted and awaiting review 14:37:25 I've already reviewed the patches and it also has a +2 from a release core 14:37:39 since it doesn't concern the team, i guess i can consider it resolved? 14:38:08 i think so, i just wanted to raise awareness in case someone needed a patch considered for a stable release 14:38:33 jbernard, ah ok, got it 14:38:52 We still have Zuul complaining for a few patches 14:38:56 i was thinking in terms of reviewing the stable branch patches, but looks like it does concern the team 14:39:05 I kept on rechecking but no success so far 14:39:20 so anyone has pending stable branch patches that they would like to get in into the stable releases 14:39:29 happystacker, is that happening on stable branches? 14:39:54 yes 14:39:59 this one for example https://review.opendev.org/c/openstack/cinder/+/887081 14:40:13 I saw a few more yesterday 14:40:50 that patch is in master 14:40:52 but haven't the time yet to recheck 14:40:59 oh yes master sorry 14:41:05 so we can discuss the gate failures in open discussion 14:41:10 ok 14:41:11 right now the topic is about stable branches 14:41:33 jbernard, wanted to know if someone has any patches they would like to get in into the proposed stable releases 14:43:14 if there are, leaving a comment on the release patches proposed 14:43:23 else we can go ahead with releasing the branches as it is 14:44:14 that's all the topics we had for today 14:44:18 let's move to open discussion 14:44:22 #topic open discussion 14:44:54 happystacker, we have an on going problem with gate failures due to certain jobs OOMing or timing out 14:45:07 Indeed 14:45:27 887081 is an nfs fix and the nfs job is the only one that failed... 14:45:28 I remember we proposed a patch to reduce concurrency in tempest, not sure if tosky has any luck on that one 14:45:35 I'd like a review on https://review.opendev.org/c/openstack/cinder/+/868485, I think it needs another +2 14:46:07 ok so no other solution than rechecking it? 14:46:12 the tempest test that failed is one i'm not too familiar with, but it looks related 14:46:14 whoami-rajat: that received some pushback (also a related patch in glance) so I'm thinking about abandoning them and it will be sadly someone's else problem 14:46:32 i think we need to verify that the patch isn't causing a real failure... 14:46:58 I don't see any error related directly to the patch or at least it's not obvious 14:47:02 tosky, oh, that's bad, we might need another way to tackle the issue then, which I'm not sure what is ... 14:49:45 How are the patches, which have not merged yet are in Bobcat's feature lists? Do the patches still have a chance to merge into Bobcat by Sep 14th? 14:51:33 akawai, sorry but there is no way to include them in the current cycle, they will be moved to the next cycle 14:51:42 surely we can target them for early next cycle 14:52:05 I see. 14:53:11 I'm planning to improve the review situation so we don't face similar bandwidth issues in future (hopefully) 14:53:52 nice 14:59:33 we are out of time 14:59:38 thanks everyone for joining 14:59:41 #endmeeting