14:00:01 #startmeeting cinder 14:00:01 Meeting started Wed Jul 19 14:00:01 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:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'cinder' 14:00:03 #topic roll call 14:00:24 o/ 14:00:40 o/ 14:00:46 o/ 14:00:54 o/ 14:01:04 o/ 14:01:11 o? 14:01:15 o/ 14:01:43 o/ 14:01:50 #link https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:02:48 o/ 14:02:59 o/ 14:03:31 o/ 14:04:34 good turnout today 14:04:37 let's get started 14:04:41 #topic announcements 14:04:50 starting out with a sad news 14:04:51 Sofia will be leaving cinder 14:05:16 A great loss 14:05:43 indeed 14:05:45 :( 14:06:03 oh :( 14:06:03 she has a great presence upstream and holds the followings responsibilities 14:06:04 Core reviewer 14:06:04 Stable core 14:06:04 Bug Deputy 14:06:04 Outreachy mentor 14:06:22 the absence will surely be felt 14:06:34 yes, sorry to see you go Sofia 14:06:35 enriquetaso, thanks for all your contributions! 14:06:53 :d 14:06:55 :D 14:07:08 I'll miss the team too! 14:07:26 Next week will be the last bug email from me 14:07:59 I'll send a email later this week :) 14:08:24 thank you all! 14:08:36 thanks again Sofia 14:08:56 as enriquetaso mentioned, if anyone is up to take one of her responsibilities i.e. bug deputy 14:09:25 please contact me or sofia ? and we will brief you up about the role 14:10:33 i've created a stupid script to do the report easily https://github.com/enriquetaso/launchpad-bug-reporter 14:12:31 wow, that's convenient 14:12:58 very nice! 14:13:56 ok, moving on from this news 14:13:57 next up is Driver status 14:14:01 #link https://etherpad.opendev.org/p/cinder-2023-2-bobcat-drivers 14:14:12 The yadro CI wasn't reporting last week 14:14:19 but it started reported just hours after the deadline 14:14:34 I left an open comment on the patch for the cinder team to look and respond on my decision 14:15:03 I didn't see much merit in postponing the driver given the CI was ready before deadline and the vendor team were having infra issues due to which it didn't report for sometime 14:15:09 #link https://review.opendev.org/c/openstack/cinder/+/876743/9#message-a14d8071cc080b308abfe2d21d8aad35739d8585 14:15:15 3 of the cores have agreed on the patch 14:15:24 and jungleboyj agreed with the decision on IRC 14:15:31 so I've approved it 14:15:38 \o/ 14:15:47 so right now we had 2 drivers this cycle that were merged 14:15:58 1) Yadro FC Driver 14:16:05 2) TOYOU NetStor iSCSI driver 14:16:41 thanks everyone for your reviews and getting the drivers in 14:17:26 o/ 14:17:45 next, EM Discussion Update 14:17:51 #link https://review.opendev.org/c/openstack/governance/+/888771 14:18:04 after multiple discussions, the TC team has proposed an update on the EM discussion 14:18:14 if you don't have much time, you can go through the commit message 14:18:22 it summarizes the changes 14:18:36 basically it's the same thing that rosmaita briefed us about last week 14:18:54 1. EM is rename to Unmaintained. 14:18:54 2. Branch deletion and creation under unmaintained/. 14:18:54 3. New Gerrit group responsible for the branch. 14:18:54 4. Mention of TC maintaining a checklist and process. 14:18:58 here it is 14:19:12 i wrote up a quick summary because the workflow wasn't entirely clear to me: https://etherpad.opendev.org/p/openstack-unmaintained-workflow 14:19:22 i do have a question for people, though 14:20:04 as far as the "unmaintained" branches, there's a proposal that they should only be SLURP branches 14:20:07 rosmaita, always has an easier way to explain the TC decisions :D 14:21:24 wasn't there a point that we can't move a branch to unmaintained unless it's previous branches are in unmaintained status? how does that fit in with non-SLURP branches? 14:22:56 i think you have the time directionality backwards there? 14:23:15 anyway, maybe it's not a big deal ... the stable branches will work the way they do now 14:23:33 you will only be able to get "holes" in the series once you hit Unmaintained 14:24:05 i was thinking this could be problematic for backporting stuff 14:24:09 but maybe not 14:24:19 (does my concern make any sense?) 14:25:35 sorry if i wasn't clear, let me take an example, if we put CC to unmaintained and Bobcat is still in extended maintenance, should we have allowed moving CC to unmaintained when it's previous branch (Bobcat) is still EM? 14:26:35 yeah, i don't know about how the transition is supposed to work from existing EM branches into unmaintained 14:26:48 there's a patch up for that but i don't understand it 14:27:06 https://review.opendev.org/c/openstack/governance/+/887969 14:29:43 For every release that exits the maintained phase, the last 3 branches under 14:29:44 extended maintenance are moved to the new extended maintenance policy 14:30:21 this won't be the case always right? if 1 branch moving from maintained to EM transitions 3 EM branches to unmaintained, we won't have enough EM branches to transition 14:30:32 or maybe it's just until all current EM branches are moved to unmaintained 14:30:35 not sure either 14:30:54 I will wait for the final resolution 14:31:13 yeah, i will push for some clarity on that one 14:31:43 that would be good 14:33:07 ok, moving on 14:33:09 next, OpenStack C release name results 14:33:19 from the latest email, the poll ended on 18th July 14:33:26 but I was still able to vote 14:33:38 not sure what's going on with the poll but here are the results that i can see 14:33:42 Caracal (Condorcet winner: wins contests with all other choices) 14:33:42 Cashew loses to Caracal by 163–1253. 14:33:43 Celine loses to Caracal by 174–114, loses to Cashew by 152–119 14:33:57 so our next release name seems to be Caracal 14:34:12 Cool 14:36:25 ok, final announcement 14:36:28 Festival of XS reviews this wek 14:36:33 This friday, 21 July, 1400-1600 UTC 14:36:39 #link https://etherpad.opendev.org/p/cinder-festival-of-reviews 14:36:52 I haven't done any changes to the structure yet 14:37:03 so it will again be a 2 hour meeting where we will review extra small patches 14:37:23 cool 14:37:43 keep the wild animal theme going... 14:38:22 :D 14:38:37 that's all the announcements for today 14:38:54 anyone has anything else to announce that i missed? 14:40:42 stable-only patch to fix victoria gate: https://review.opendev.org/c/openstack/cinder/+/888698 from Elod needs reviews 14:40:55 (in case it wasn't mentioned before) 14:43:24 thanks jbernard 14:45:40 until the EM branches get a resolution, good to get the gate fixed :) 14:46:05 let's move to open discussion 14:46:09 #topic open discussion 14:46:22 Hi, I want to bring a patch attention here. 14:46:25 we don't have any topics for today but if anyone would like to discuss anything 14:46:28 they can go ahead 14:46:33 Our driver has a patch: https://review.opendev.org/c/openstack/cinder/+/703770. But I'm unable to access the account of the patch owner. 14:46:49 So I created a new patch to replace it: https://review.opendev.org/c/openstack/cinder/+/847730. Since I cannot manage the old patch, would it be possible for you to abandon the old patch(703770)? 14:47:13 inori, sure i can do that 14:47:30 done 14:47:55 Got it. Thank you. 14:48:24 np 14:48:31 And the patch https://review.opendev.org/c/openstack/cinder/+/847730 already has one +2, so it need one more +2 to be merged, right? Could you please review it at your earliest convenience? 14:48:59 sure, will take a look 14:49:25 In fact, our driver has a lot of patches: https://review.opendev.org/q/owner:inori. The code of our driver in RHOSP base image is too old, so that we want to make the patches be merged ASAP. 14:49:29 Thank you. 14:49:34 hi.. i am trying to rebase the patch : https://review.opendev.org/c/openstack/cinder/+/870006 14:50:00 but when i am uploading the new patch i am getting an error : ! [remote rejected] HEAD -> refs/for/master%topic=bug/2003300 (commit a159754: you are not allowed to upload merges) 14:50:07 any ideas? 14:51:00 your rebasing procedure must have created a merge commit, which can't be there 14:52:00 oh ok. let me check. can we discuss on personal window? 14:52:38 get a clean cinder clone from master and do "git review -x 870006", and resolve the conflict while cherry-picking, is the easy route 14:53:11 ok i'll try that 14:59:33 we're out of time 14:59:38 thanks everyone for attending 14:59:44 #endmeeting