Wednesday, 2025-08-20

*** mhen_ is now known as mhen01:20
jbernard#startmeeting cinder14:06
opendevmeetMeeting started Wed Aug 20 14:06:30 2025 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:06
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:06
opendevmeetThe meeting name has been set to 'cinder'14:06
jbernard#topic roll call14:06
jbernardo/ hello everyone, sorry for the delay14:06
jbernardjungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney jbernard hemna fabiooliveira yuval tobias-urdin adiare happystacker dosaboy hillpd msaravan sp-bmilanov Luzi sfernand simondodsley: courtesy reminder14:06
whoami-rajathi14:07
agalicao/14:07
rosmaitao/14:07
nileshthathagarhi14:07
anthonygamboao/14:07
Luzio/14:08
jbernard#link https://etherpad.opendev.org/p/cinder-flamingo-meetings14:08
Saio/14:11
jbernard#topic annoucments14:11
jbernardhello everyone14:11
jbernardos-brick release is tomorrow14:11
jbernardi have a few remaining tasks (small), we reviewed and merge quite a few yesterday14:11
jbernardlooking at the dashboard, i think things are in good shape currently14:12
jbernardif there are any last-minute os-brick items to raise, now is the time14:12
Vivekk_o/14:13
rosmaitathe silence is deafening, which is good in this cawe14:15
rosmaita*case14:15
jbernardclient stuff releases next week14:15
jbernardwe'll likley have another review sprint for that patch set14:17
jbernardthanks again to everyone that attended and participated in the midcycle meeting on monday14:18
jbernardi think it was productive14:18
jbernard#link https://etherpad.opendev.org/p/cinder-flamingo-midcycles14:18
jbernardthose reviews, along with the request etherpad remain on my list14:19
jbernardreviews will be my highest priority for this and next week14:20
jbernard#link https://releases.openstack.org/flamingo/schedule.html14:20
jbernardm-3 is the end of next week, so there is much to do14:20
jbernardplease help if you can14:21
jbernardthat's all for annoucments14:21
jbernard#topic open discussion14:21
agalicaQuestion on new storage devices: If a new storage device comes out that does not require any changes to the driver code can we get it added to the support list when it comes out, or do we need to submit an empty (no changes) patch?14:22
jbernardif it doesn't require code changes, we should be able to update the support list14:22
agalicaOk, thank you14:23
jbernardthe only thing i can think of is if the driver listed/documented supported backends, that might need to be updated in the code if it's present14:23
rosmaitaagalica: do you have 3rd party ci running?14:24
agalicaI don’t believe so14:24
rosmaitathat is sort of a requirement for your own protection in case the code (that is not yours) changes14:25
agalicaWe do have CI running, but maybe I misunderstand the third party part.  In this case, the storage would definitely not require changes unless the driver itself did across the board.14:27
flelaino/14:27
rosmaitathe "third party" part is that it is your CI running with your backend hardware14:28
agalicaGotcha, yes we do14:29
flelainQuestion related to encryption: do you guys know whether there were recent needs among the community to implement encrypted volumes retyping for shared storage backends? (e.g. rbd on Ceph)14:29
flelainI only came across that: https://review.opendev.org/c/openstack/os-brick/+/726467 - which states the issue and tries to explicit it in the logs.14:31
anthonygamboaI wanted to double check the code freeze dates for flamingo. We can still submit changes that can make it into the release until R-1, so september 26?14:34
jbernardflelain: im not sure about needs, but it's something we'd definately like to have finished14:34
jbernardflelain: im not clear on the current state, but i think there are some items remaining to be done14:35
rosmaitaanthonygamboa: feature freeze is next week; for bugs, the freeze is RC1 which is R-314:35
flelainjbernard: I'm implementing something, rather close to what was suggested in this change. I'll submit it upstream when testes out on my end then.14:36
rosmaitaafter that, only release-critical patches are accepted14:36
dakshRejoined as daksh due to some issue14:36
anthonygamboarosmaita: got it, thanks14:37
rosmaitaflelain: this has been the big problem with retyping to an encrypted volume: https://docs.openstack.org/cinder/latest/configuration/block-storage/volume-encryption.html#known-issues14:38
Vivekk_Hello Jon/Brian14:41
flelainrosmaita: true, I had read this too. Now, speaking of remote shared storage, we may have bigger challenges to tackle, like computing somewhere (cinder node most probably) encryption/decryption before writing it to remote backend. Is this interpretation right / relevant?14:41
jbernardflelain: great, eric (eharney) may be a source of information too, he was working on that effort a while back if i recall14:43
LuziHi I just wanted to ask, if there is another core reviewer, who can look into the image encryption: https://review.opendev.org/c/openstack/cinder/+/926298 ?14:44
jbernardcores: ^^14:44
flelainjbernard: thx for the advice. Will chat with Eric about it.14:44
rosmaitaLuzi: i will put it on my list for today14:45
Luzithank you rosmaita 14:45
flelainand btw, when and where is held cinder bugs review? Is it here during this meeting?14:45
jbernardi guess it's here (as it isn't anywhere else ;))14:46
Vivekk_Apologies for the persistent follow-ups regarding the register plugin patch. As this patch is critical for the Flamigo release, I wanted to ensure everything is on track. Please let me know the dates for ML discussion.14:46
Vivekk_ Additionally, we've confirmed that including the OS version in the metadata is necessary, as it will assist the support team with troubleshooting and diagnostics.14:46
jbernardflelain: or ad hoc in the cinder channel14:46
flelainjbernard: ok thx! I created this bug https://bugs.launchpad.net/cinder/+bug/2117265 in July. I wanted to know whether it could be tackled in some kind of triage process.14:48
jbernardVivekk_: os version, you mean kernel version and patch level?14:49
Vivekk_jbernard: nope, just os_name from cat /etc/*release command and picking the PRETTY_NAME field.14:51
anthonygamboaThere's a merge that's been giving us trouble. https://review.opendev.org/c/openstack/cinder/+/869991 I was working with jbernard last week on it; we resolved the network issues we were facing but still getting an error when trying to push a new patch set: CONFLICT (add/add): Merge conflict in releasenotes/notes/hitachi-fix-gad-vol-compatibility-e9c62c18f7a12bc7.yaml 14:54
jbernardflelain: i suspect that's a valid bug14:55
anthonygamboajbernard: thanks for the help last week. Are you available to advise on this?14:55
jbernardanthonygamboa: i can work with you just after the meeting14:55
anthonygamboajbernard: awesome, thank you!14:56
jbernardalmost at the top of the hour, last call14:58
jbernard#endmeeting15:00
opendevmeetMeeting ended Wed Aug 20 15:00:26 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-20-14.06.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-20-14.06.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-20-14.06.log.html15:00
jbernardthank you everyone15:00

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