Wednesday, 2023-06-07

*** chuanm2 is now known as chuanm08:24
*** chuanm4 is now known as chuanm08:58
*** chuanm1 is now known as chuanm09:21
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'cinder'14:00
whoami-rajat#topic roll call14:00
simondodsleyo/14:00
thiagoalvoravelo/14:00
jbernardo/14:00
rosmaitao/14:00
harsho/14:00
toskyo/14:01
eharneyo/14:01
raghavendrathi14:02
whoami-rajat#link https://etherpad.opendev.org/p/cinder-bobcat-meetings14:02
jungleboyjo/14:03
whoami-rajatgood turnout14:04
whoami-rajatlet's get started14:04
whoami-rajat#topic Announcements14:04
whoami-rajatfirst, Forum session Etherpads14:04
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033989.html14:05
whoami-rajatKendall created this wiki for collecting etherpads for forum session14:05
whoami-rajat#link https://wiki.openstack.org/wiki/Forum/Vanvouver202314:05
keerthivasansuresho/14:05
nahimsouza[m]o/14:05
whoami-rajatso i created an etherpad for the cinder forum session and added to the wiki14:05
whoami-rajat#link https://etherpad.opendev.org/p/cinder-vancouver-forum-202314:05
whoami-rajatrosmaita, 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:06
rosmaitaon the etherpad, you mean?14:07
whoami-rajati mean in the schedule14:07
whoami-rajatrosmaita, https://vancouver2023.openinfra.dev/a/schedule14:08
rosmaitaThat is really weird, i thought i saw you there yesterday14:08
whoami-rajatok i think it doesn't matter, just wanted to make sure there wasn't another forum session for cinder14:09
rosmaitaI am positive there were 3 people listed yesterday, because i had to scroll to see myself14:09
whoami-rajatCinder, the OpenStack Block Storage service ... how are we doing?14:09
whoami-rajatBy Eric Harney, Brian Rosmaita14:09
rosmaitaweird14:09
rosmaitayes, that's the session14:09
whoami-rajatthat's what it says on the schedule but as i said, it shouldn't matter14:09
whoami-rajatas long as we don't have another session we are forgetting about :D14:10
rosmaitanope, that's the only one I know about for cinder14:10
whoami-rajatok, we should be good then14:10
whoami-rajatso I've created the etherpad and added to the wiki, feel free to make any changes to it as needed14:11
whoami-rajatrosmaita, eharney ^14:11
rosmaitathanks!14:12
whoami-rajatok moving on14:12
whoami-rajatnext, Spec review day14:12
whoami-rajatI've decided the following date and time for the spec review day14:13
whoami-rajat09 June - 1400-1500 UTC14:13
whoami-rajatjust wanted to confirm here first before i send out an email14:13
simondodsleyfine by me14:13
rosmaitaworks for me too14:13
whoami-rajatcool, will send out an email after the meeting14:14
whoami-rajatnext, Upcoming Vancouver summit (13-15 June)14:15
whoami-rajat#link https://vancouver2023.openinfra.dev/a/schedule14:15
whoami-rajat#link https://openinfra.dev/summit/vancouver-2023/14:15
whoami-rajatthere is no announcement, just the summit is upcoming so a reminder14:15
whoami-rajatthat's all the announcements from my side14:17
whoami-rajatanyone has anything else?14:17
rosmaitaI've got a question about the PTG14:17
whoami-rajatsure14:18
rosmaitanamely, what are we doing?14:18
rosmaitaseems like not too many Argonauts will be there14:18
whoami-rajatgood question14:18
whoami-rajatI created this etherpad14:18
whoami-rajat#link https://etherpad.opendev.org/p/vancouver-ptg-june-202314:18
whoami-rajatso far there has only been one topic by simondodsley 14:18
simondodsleywell that means I get my way then???14:19
rosmaitaas long as you do the implementation and all the reviews!14:19
rosmaitai think let's schedule Simon's session and an operator hour, and maybe one more placeholder slot for general discussion?14:20
simondodsleyself reviewing - nice14:20
simondodsleygive me +2 for os-brick... lol14:20
whoami-rajatwe do have to book slots but so far i don't think we need a big chunk of time14:21
whoami-rajati like rosmaita's suggestion14:21
whoami-rajat2 hours should be good including operator hour14:22
whoami-rajatwe need feedback for the EM discussion as well14:22
rosmaitayeah, i think we will get a lot of that at the forum14:22
rosmaitabut we could schedule a followup session in "our" time at the PTG14:23
rosmaitahow many Argonauts do we think will be attending the PTG?14:23
enriquetaso2I’ll attend remote14:24
simondodsleydo we have a room for the cinder session yet? I don't see it on the schedule14:24
rosmaitanot for the PTG yet14:24
rosmaitajust for the Forum14:24
* jungleboyj is in Shanghai all next week14:24
simondodsleyjungleboyj don't bring back COVID-2214:25
harshCan i also attend PTG ?14:26
whoami-rajatsimondodsley, i can book it, just couldn't decide how much time we need and when would everyone be available14:26
rosmaitaharsh: will you be in  Vancouver?  not sure there will be remote options14:26
simondodsleypounds like there are only going to be 4 of us in person??14:26
whoami-rajatpersonally speaking, i think i won't be able to make it but i can do all the arrangements necessary14:26
harshNo. I am in India. not sure what the process is.14:27
simondodsleyok - 3 now... and counting14:27
rosmaitayeah, whoami-rajat why don't I put together a doodle poll and then we can book rooms on friday14:27
whoami-rajatrosmaita, sounds like a great idea14:28
rosmaitashouldn't be too hard to find good times since there's only 3 of us14:28
rosmaitaok, eharney and simondodsley i will ping you later in the cinder channel when i have it together14:29
rosmaitai will also send to the ML just in case14:29
whoami-rajat++14:30
whoami-rajatharsh, there are various steps involved but i guess it's too late to attend now, at least from India14:31
harsh:(14:33
harshNext time probably 14:34
whoami-rajatyep14:34
rosmaitahope so!14:34
whoami-rajatso if there are no other announcements, we will move to topics14:34
whoami-rajat#topic EOL the EM branches follow up14:35
whoami-rajatrosmaita, that's us but i guess you can explain better14:35
rosmaitamaybe14:35
rosmaitamostly this is for awareness14:35
rosmaitawhoami-rajat sent out the announcement to the ML:14:36
rosmaita#link https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html14:36
rosmaitasome interesting responses in the thread so far14:36
rosmaitapretty good agreement i think that the current EM process is not working14:36
rosmaitain addition to the thread, there was some similar discussion in  the TC channel yesterday:14:37
rosmaita#link https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2023-06-06.log.html#t2023-06-06T19:06:0314:37
rosmaitaand 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 that14:37
rosmaitathat's all14:38
simondodsleyseems that cinder and nova are the projects with the most to say on this subject14:38
whoami-rajatlooking at the responses, i think there is agreement to how the EM model was expected to work and it's not working as expected14:39
whoami-rajatI'm hopeful that our argument has good amount of support14:39
rosmaitai think it does14:40
rosmaitathere may be some pushback on EOLing Xena14:40
rosmaitabut it think we are ultimately OK for the others14:40
whoami-rajati don't know what Gorka thinks about it but he's not around today :D14:41
rosmaitabtw, 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
rosmaita#link https://review.opendev.org/q/topic:cinder-eol-june202314:41
simondodsleyI think the issue may be that RHOSP 17.1 will be based on wallaby and some xena backports. EOLing could cause RH issues14:41
whoami-rajati think leaving xena should be fine, we just don't want to keep more branches in EM than the active stable branches14:41
rosmaitait would be a small compromise14:42
rosmaitasimondodsley: it will make more work for Red Hat maybe, but we have pretty wide latitude to do what's good for the upstream community14:43
rosmaitai mean, speaking as a Red Hatter for the minute14:43
whoami-rajati 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 correct14:44
rosmaitai think tosky said exactly that last week or maybe the week before14:44
rosmaitaok, well this fits in well with the next topic14:45
rosmaitastatus of backports to stable/wallaby and older14:45
whoami-rajat#topic status of backports to stable/wallaby and older14:45
whoami-rajatwe can continue now14:45
rosmaitaso part of our reason for EOLing those branches is that they will not get a fix for CVE-2023-208814:45
rosmaitaso we don't want people to use them without knowing what they are getting into14:46
rosmaitaso we will EOL and delete the branches14:46
rosmaitabut, there are still some outstanding patches14:46
rosmaitaan example is this one:14:46
rosmaita#link https://review.opendev.org/c/openstack/cinder/+/87190614:46
rosmaitamy 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
toskyyeah, sorry, the point is that we can make decisions if they are in the interest of the community regardless of the internal decisions14:47
rosmaitaand 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:47
rosmaitathanks tosky14:48
simondodsleyrosmaita ++14:49
rosmaitasimondodsley: is that for the README or continuing to merge stuff?14:49
simondodsleyREADME14:49
whoami-rajatrosmaita, 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 patches14:50
rosmaitaok, so to be clear14:50
rosmaitathe consensus is14:50
rosmaita1. we will update the README in the EM branches (except xena) to indicate that the fix for CVE-2023-2088 is missing14:51
rosmaita2. we will continue to accept patches into the EM branches before they go EOL14:52
rosmaita(which will happen around 21 June or so)14:52
rosmaita3. there is *no* number 314:52
harsh++14:52
whoami-rajat#3 is new to me14:53
whoami-rajatsounds like a plan14:53
whoami-rajatdo we want to send something out to ML regarding this?14:53
rosmaitayou mean, hurry up and get stuff proposed and merged?14:54
rosmaitabtw, i'll take an action item to update the READMEs14:54
whoami-rajatit's less likely people will propose patches if the CVE is also not there but yeah like review the existing changes14:55
whoami-rajatbut maybe not needed14:55
whoami-rajatwe already have ongoing discussion about the EM thing14:55
simondodsleyi think we just do the README and wait to see the outcome of the ongoing EM discussions14:56
simondodsleyPut a hold on all EM patches14:56
rosmaitayeah, i think the EOL proposal was a good indicator that you need to get backports in right away14:56
rosmaitahmmm ... i thought we said we would continue to merge EM patches?14:57
whoami-rajatthat's what i understood14:58
whoami-rajatwhy do we want to hold the EM patches?14:58
simondodsleydoes it not depend on what the EM discussion comes up with14:58
simondodsleymight be wasting time on EM patches... potentially. I don't mind though14:58
whoami-rajatI see, i thought of it as a final effort and adios to all the EM branches14:59
rosmaitayeah, 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?14:59
rosmaitabut i don't know ... that's why i wanted to discuss15:00
whoami-rajatwe are out of time15:00
whoami-rajatwe can continue the discussion in cinder channel after the BS meeting15:01
whoami-rajatthanks everyone for joining15:01
whoami-rajat#endmeeting15:01
opendevmeetMeeting ended Wed Jun  7 15:01:07 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-07-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-07-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-07-14.00.log.html15:01
jungleboyjThanks!15:01
*** chuanm53 is now known as chuanm19:26

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!