14:06:30 <jbernard> #startmeeting cinder
14:06:30 <opendevmeet> Meeting 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:30 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:06:30 <opendevmeet> The meeting name has been set to 'cinder'
14:06:35 <jbernard> #topic roll call
14:06:41 <jbernard> o/ hello everyone, sorry for the delay
14:06:55 <jbernard> jungleboyj 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 reminder
14:07:25 <whoami-rajat> hi
14:07:32 <agalica> o/
14:07:40 <rosmaita> o/
14:07:42 <nileshthathagar> hi
14:07:44 <anthonygamboa> o/
14:08:10 <Luzi> o/
14:08:37 <jbernard> #link https://etherpad.opendev.org/p/cinder-flamingo-meetings
14:11:09 <Sai> o/
14:11:24 <jbernard> #topic annoucments
14:11:30 <jbernard> hello everyone
14:11:37 <jbernard> os-brick release is tomorrow
14:11:56 <jbernard> i have a few remaining tasks (small), we reviewed and merge quite a few yesterday
14:12:06 <jbernard> looking at the dashboard, i think things are in good shape currently
14:12:33 <jbernard> if there are any last-minute os-brick items to raise, now is the time
14:13:58 <Vivekk_> o/
14:15:23 <rosmaita> the silence is deafening, which is good in this cawe
14:15:26 <rosmaita> *case
14:15:34 <jbernard> client stuff releases next week
14:17:49 <jbernard> we'll likley have another review sprint for that patch set
14:18:19 <jbernard> thanks again to everyone that attended and participated in the midcycle meeting on monday
14:18:24 <jbernard> i think it was productive
14:18:48 <jbernard> #link https://etherpad.opendev.org/p/cinder-flamingo-midcycles
14:19:08 <jbernard> those reviews, along with the request etherpad remain on my list
14:20:32 <jbernard> reviews will be my highest priority for this and next week
14:20:42 <jbernard> #link https://releases.openstack.org/flamingo/schedule.html
14:20:53 <jbernard> m-3 is the end of next week, so there is much to do
14:21:06 <jbernard> please help if you can
14:21:16 <jbernard> that's all for annoucments
14:21:22 <jbernard> #topic open discussion
14:22:04 <agalica> Question 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:48 <jbernard> if it doesn't require code changes, we should be able to update the support list
14:23:00 <agalica> Ok, thank you
14:23:45 <jbernard> the 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 present
14:24:27 <rosmaita> agalica: do you have 3rd party ci running?
14:24:47 <agalica> I don’t believe so
14:25:56 <rosmaita> that is sort of a requirement for your own protection in case the code (that is not yours) changes
14:27:20 <agalica> We 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:37 <flelain> o/
14:28:11 <rosmaita> the "third party" part is that it is your CI running with your backend hardware
14:29:06 <agalica> Gotcha, yes we do
14:29:24 <flelain> Question 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:31:14 <flelain> I 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:34:14 <anthonygamboa> I 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:44 <jbernard> flelain: im not sure about needs, but it's something we'd definately like to have finished
14:35:29 <jbernard> flelain: im not clear on the current state, but i think there are some items remaining to be done
14:35:31 <rosmaita> anthonygamboa: feature freeze is next week; for bugs, the freeze is RC1 which is R-3
14:36:13 <flelain> jbernard: 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:14 <rosmaita> after that, only release-critical patches are accepted
14:36:50 <daksh> Rejoined as daksh due to some issue
14:37:36 <anthonygamboa> rosmaita: got it, thanks
14:38:29 <rosmaita> flelain: 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-issues
14:41:07 <Vivekk_> Hello Jon/Brian
14:41:36 <flelain> rosmaita: 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:43:19 <jbernard> flelain: great, eric (eharney) may be a source of information too, he was working on that effort a while back if i recall
14:44:03 <Luzi> Hi 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:22 <jbernard> cores: ^^
14:44:54 <flelain> jbernard: thx for the advice. Will chat with Eric about it.
14:45:43 <rosmaita> Luzi: i will put it on my list for today
14:45:51 <Luzi> thank you rosmaita
14:45:52 <flelain> and btw, when and where is held cinder bugs review? Is it here during this meeting?
14:46:18 <jbernard> i guess it's here (as it isn't anywhere else ;))
14:46:33 <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:45 <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:46 <jbernard> flelain: or ad hoc in the cinder channel
14:48:34 <flelain> jbernard: 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:49:31 <jbernard> Vivekk_: os version, you mean kernel version and patch level?
14:51:22 <Vivekk_> jbernard: nope, just os_name from cat /etc/*release command and picking the PRETTY_NAME field.
14:54:59 <anthonygamboa> There'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:55:10 <jbernard> flelain: i suspect that's a valid bug
14:55:24 <anthonygamboa> jbernard: thanks for the help last week. Are you available to advise on this?
14:55:56 <jbernard> anthonygamboa: i can work with you just after the meeting
14:56:41 <anthonygamboa> jbernard: awesome, thank you!
14:58:48 <jbernard> almost at the top of the hour, last call
15:00:26 <jbernard> #endmeeting