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