14:00:26 #startmeeting cinder 14:00:26 Meeting started Wed Jun 7 14:00:26 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:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:26 The meeting name has been set to 'cinder' 14:00:30 #topic roll call 14:00:43 o/ 14:00:43 o/ 14:00:44 o/ 14:00:48 o/ 14:00:50 o/ 14:01:11 o/ 14:01:30 o/ 14:02:21 hi 14:02:42 #link https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:03:00 o/ 14:04:38 good turnout 14:04:39 let's get started 14:04:48 #topic Announcements 14:04:54 first, Forum session Etherpads 14:05:00 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033989.html 14:05:23 Kendall created this wiki for collecting etherpads for forum session 14:05:31 #link https://wiki.openstack.org/wiki/Forum/Vanvouver2023 14:05:42 o/ 14:05:54 o/ 14:05:56 so i created an etherpad for the cinder forum session and added to the wiki 14:05:59 #link https://etherpad.opendev.org/p/cinder-vancouver-forum-2023 14:06:43 rosmaita, i see your and eharney's name on the session, i thought i got a ticket for the same forum session, is there another one? 14:07:15 on the etherpad, you mean? 14:07:54 i mean in the schedule 14:08:11 rosmaita, https://vancouver2023.openinfra.dev/a/schedule 14:08:31 That is really weird, i thought i saw you there yesterday 14:09:03 ok i think it doesn't matter, just wanted to make sure there wasn't another forum session for cinder 14:09:09 I am positive there were 3 people listed yesterday, because i had to scroll to see myself 14:09:38 Cinder, the OpenStack Block Storage service ... how are we doing? 14:09:39 By Eric Harney, Brian Rosmaita 14:09:43 weird 14:09:48 yes, that's the session 14:09:56 that's what it says on the schedule but as i said, it shouldn't matter 14:10:14 as long as we don't have another session we are forgetting about :D 14:10:35 nope, that's the only one I know about for cinder 14:10:56 ok, we should be good then 14:11:31 so I've created the etherpad and added to the wiki, feel free to make any changes to it as needed 14:11:34 rosmaita, eharney ^ 14:12:05 thanks! 14:12:53 ok moving on 14:12:56 next, Spec review day 14:13:10 I've decided the following date and time for the spec review day 14:13:11 09 June - 1400-1500 UTC 14:13:19 just wanted to confirm here first before i send out an email 14:13:26 fine by me 14:13:52 works for me too 14:14:41 cool, will send out an email after the meeting 14:15:08 next, Upcoming Vancouver summit (13-15 June) 14:15:19 #link https://vancouver2023.openinfra.dev/a/schedule 14:15:23 #link https://openinfra.dev/summit/vancouver-2023/ 14:15:34 there is no announcement, just the summit is upcoming so a reminder 14:17:41 that's all the announcements from my side 14:17:46 anyone has anything else? 14:17:56 I've got a question about the PTG 14:18:08 sure 14:18:12 namely, what are we doing? 14:18:26 seems like not too many Argonauts will be there 14:18:31 good question 14:18:38 I created this etherpad 14:18:42 #link https://etherpad.opendev.org/p/vancouver-ptg-june-2023 14:18:48 so far there has only been one topic by simondodsley 14:19:06 well that means I get my way then??? 14:19:19 as long as you do the implementation and all the reviews! 14:20:02 i think let's schedule Simon's session and an operator hour, and maybe one more placeholder slot for general discussion? 14:20:19 self reviewing - nice 14:20:54 give me +2 for os-brick... lol 14:21:48 we do have to book slots but so far i don't think we need a big chunk of time 14:21:55 i like rosmaita's suggestion 14:22:10 2 hours should be good including operator hour 14:22:30 we need feedback for the EM discussion as well 14:22:47 yeah, i think we will get a lot of that at the forum 14:23:05 but we could schedule a followup session in "our" time at the PTG 14:23:39 how many Argonauts do we think will be attending the PTG? 14:24:02 I’ll attend remote 14:24:06 do we have a room for the cinder session yet? I don't see it on the schedule 14:24:20 not for the PTG yet 14:24:25 just for the Forum 14:24:27 * jungleboyj is in Shanghai all next week 14:25:03 jungleboyj don't bring back COVID-22 14:26:08 Can i also attend PTG ? 14:26:09 simondodsley, i can book it, just couldn't decide how much time we need and when would everyone be available 14:26:46 harsh: will you be in Vancouver? not sure there will be remote options 14:26:52 pounds like there are only going to be 4 of us in person?? 14:26:56 personally speaking, i think i won't be able to make it but i can do all the arrangements necessary 14:27:09 No. I am in India. not sure what the process is. 14:27:11 ok - 3 now... and counting 14:27:59 yeah, whoami-rajat why don't I put together a doodle poll and then we can book rooms on friday 14:28:19 rosmaita, sounds like a great idea 14:28:37 shouldn't be too hard to find good times since there's only 3 of us 14:29:06 ok, eharney and simondodsley i will ping you later in the cinder channel when i have it together 14:29:14 i will also send to the ML just in case 14:30:44 ++ 14:31:12 harsh, there are various steps involved but i guess it's too late to attend now, at least from India 14:33:39 :( 14:34:04 Next time probably 14:34:48 yep 14:34:52 hope so! 14:34:59 so if there are no other announcements, we will move to topics 14:35:15 #topic EOL the EM branches follow up 14:35:34 rosmaita, that's us but i guess you can explain better 14:35:43 maybe 14:35:48 mostly this is for awareness 14:36:02 whoami-rajat sent out the announcement to the ML: 14:36:09 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html 14:36:19 some interesting responses in the thread so far 14:36:39 pretty good agreement i think that the current EM process is not working 14:37:13 in addition to the thread, there was some similar discussion in the TC channel yesterday: 14:37:23 #link https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2023-06-06.log.html#t2023-06-06T19:06:03 14:37:52 and since whoami-rajat mentioned in his email that this could be discussed at the cinder forum session, i think a *lot* of people will take us up on that 14:38:20 that's all 14:38:24 seems that cinder and nova are the projects with the most to say on this subject 14:39:31 looking at the responses, i think there is agreement to how the EM model was expected to work and it's not working as expected 14:39:48 I'm hopeful that our argument has good amount of support 14:40:16 i think it does 14:40:36 there may be some pushback on EOLing Xena 14:40:56 but it think we are ultimately OK for the others 14:41:07 i don't know what Gorka thinks about it but he's not around today :D 14:41:25 btw, i should mention that we have posted the release patches proposing EOL for all EM branches (just to show that we mean business) 14:41:35 #link https://review.opendev.org/q/topic:cinder-eol-june2023 14:41:37 I think the issue may be that RHOSP 17.1 will be based on wallaby and some xena backports. EOLing could cause RH issues 14:41:44 i think leaving xena should be fine, we just don't want to keep more branches in EM than the active stable branches 14:42:15 it would be a small compromise 14:43:25 simondodsley: it will make more work for Red Hat maybe, but we have pretty wide latitude to do what's good for the upstream community 14:43:34 i mean, speaking as a Red Hatter for the minute 14:44:06 i remember tosky making this clear from RH perspective that everything fine by the community is also fine by RH, but maybe I am misquoting him so please correct 14:44:36 i think tosky said exactly that last week or maybe the week before 14:45:11 ok, well this fits in well with the next topic 14:45:24 status of backports to stable/wallaby and older 14:45:31 #topic status of backports to stable/wallaby and older 14:45:39 we can continue now 14:45:54 so part of our reason for EOLing those branches is that they will not get a fix for CVE-2023-2088 14:46:14 so we don't want people to use them without knowing what they are getting into 14:46:22 so we will EOL and delete the branches 14:46:31 but, there are still some outstanding patches 14:46:40 an example is this one: 14:46:49 #link https://review.opendev.org/c/openstack/cinder/+/871906 14:47:26 my question is, does it make sense to continue to merge stuff that could be useful, right up until the branch is EOL'd? 14:47:55 yeah, sorry, the point is that we can make decisions if they are in the interest of the community regardless of the internal decisions 14:47:57 and related, maybe we should put a warning into the README for those branches right now indicating that there is a major security flaw that is not fixed? 14:48:14 thanks tosky 14:49:15 rosmaita ++ 14:49:39 simondodsley: is that for the README or continuing to merge stuff? 14:49:44 README 14:50:30 rosmaita, sounds like a good idea, maybe we can have another festival for merging changes into EM branches? or just ask reviews to pay attention to open patches 14:50:54 ok, so to be clear 14:50:57 the consensus is 14:51:29 1. we will update the README in the EM branches (except xena) to indicate that the fix for CVE-2023-2088 is missing 14:52:00 2. we will continue to accept patches into the EM branches before they go EOL 14:52:10 (which will happen around 21 June or so) 14:52:23 3. there is *no* number 3 14:52:52 ++ 14:53:12 #3 is new to me 14:53:16 sounds like a plan 14:53:23 do we want to send something out to ML regarding this? 14:54:15 you mean, hurry up and get stuff proposed and merged? 14:54:53 btw, i'll take an action item to update the READMEs 14:55:03 it's less likely people will propose patches if the CVE is also not there but yeah like review the existing changes 14:55:40 but maybe not needed 14:55:48 we already have ongoing discussion about the EM thing 14:56:24 i think we just do the README and wait to see the outcome of the ongoing EM discussions 14:56:38 Put a hold on all EM patches 14:56:43 yeah, i think the EOL proposal was a good indicator that you need to get backports in right away 14:57:45 hmmm ... i thought we said we would continue to merge EM patches? 14:58:01 that's what i understood 14:58:08 why do we want to hold the EM patches? 14:58:10 does it not depend on what the EM discussion comes up with 14:58:37 might be wasting time on EM patches... potentially. I don't mind though 14:59:21 I see, i thought of it as a final effort and adios to all the EM branches 14:59:50 yeah, but my thought is that if people know the branches are non-releaseable and are going EOL soon, and they still want to get something merged, they must have a good reason? 15:00:30 but i don't know ... that's why i wanted to discuss 15:00:49 we are out of time 15:01:00 we can continue the discussion in cinder channel after the BS meeting 15:01:04 thanks everyone for joining 15:01:07 #endmeeting