Wednesday, 2024-05-22

jbernard#startmeeting cinder14:01
opendevmeetMeeting started Wed May 22 14:01:30 2024 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'cinder'14:01
eharneyhi14:01
jbernard#topic roll call14:01
jbernardo/14:01
simondodsleyo/14:01
Luzio/14:01
akawaio/14:01
rosmaitao/14:01
jbernard#link https://etherpad.opendev.org/p/cinder-dalmatian-meetings14:01
msaravanHi 14:03
ccokeke[m]O/14:03
whoami-rajathey14:03
bryanneumannHi all14:05
zaitcevo/14:05
jbernardwelcome everyone14:05
jungleboyjo/14:05
jbernard#topic annoucements14:06
jbernardquick annoucements14:06
jbernard#link https://releases.openstack.org/dalmatian/schedule.html14:06
jbernard^ this is the release schedule for all projects14:06
jbernardive posted our proposed cinder-specific dates here14:06
jbernard#link https://review.opendev.org/c/openstack/releases/+/91990814:07
jbernardive set the midterm to be wednesday june 1214:07
jbernardand the remaining freezes/checkpoints I tried to follow existing precedence14:08
jbernardtake a look, let me know if there are any comments or concerns14:08
jbernardif not, ill address jens' comments and push to get that merged14:08
jbernardyou can reach out after the meeting too, we can keep moving for now14:09
jbernard#topic backports needing attention14:10
jbernardrosmaita: that's you14:10
rosmaitahello14:10
rosmaitayes, this started out as a begging request for someone to please look at some patches of mine14:10
rosmaitanamely14:10
rosmaitahttps://review.opendev.org/c/openstack/cinder/+/91081514:10
rosmaitaand14:10
rosmaitahttps://review.opendev.org/c/openstack/cinder/+/89235214:10
rosmaitabut i notice that we have some antelope patches piling up14:11
rosmaitaso, stable cores, please use our handy dashboard to check them out:14:11
rosmaitahttp://tiny.cc/cinder-maintained14:11
jbernardnice14:11
rosmaitathat's all from me14:11
jbernard#action backport reviews14:11
jbernard#topic re-addressing simon's bug14:12
jungleboyjOn it.  :-)14:12
jbernard#link https://bugs.launchpad.net/cinder/+bug/190628614:12
simondodsleyhi14:12
zaitcevThis is not a backport that needs attention really, but I suspect Brian didn't realize it was a backport and replied as if it were on master: https://review.opendev.org/c/openstack/cinder/+/90868914:12
simondodsleycustomer has deployed using kolla and has 5 controllers - when the service moves across controllers it messes up14:13
simondodsleykolla are addressing the lack of `cluster_name` in their code, but that still doesn't alter the underlying issue14:13
simondodsleythe customer has proposed a small patch in the bug but this is deeper into core code than I care to delve14:13
simondodsleycan one of the cores have a look?14:14
simondodsleymaybe this needs something t change in glance as well if A/A is enabled and there is a cluster name14:14
jbernard#link https://bugs.launchpad.net/cinder/+bug/1906286/comments/414:14
jbernardi think it would be good to at least post the change to have CI input while we take a closer look14:15
simondodsleyif that is the case i can raise a patch for the simple change they suggest14:15
simondodsleyand see what happens14:15
simondodsleybut the CIs don't address HA do they?14:16
simondodsleynor do they address cinder as a glance backend14:16
jbernardi don't think so, it would have to be tested manually14:17
whoami-rajatwe do have a job running cinder as glance backend but I'm not aware about any HA jobs14:17
simondodsleyI don't have a CI currently - ongoing infra issue14:17
simondodsleyanyone else have the ability to test it? One of the other vendrs?14:17
whoami-rajatthis is a case of optimized volume creation from image where we are not considering clusters14:18
simondodsleyexactly14:18
whoami-rajatand the suggested code change isn't correct since that isn't doing any filtering14:18
whoami-rajatwe need to do filtering based on host or cluster depending on the environment14:19
zaitcevI'm trying to imagine what's the worst that can happen. Where previously Cinder reported and error with "No accessible image volume", it will try to clone from an off-host volume.14:19
simondodsleythat is what is happening, but as there are 5 controllers the backend can get 5 images created per image which is a waste of resources, especially when there are multiple base images14:19
whoami-rajatzaitcev, the only issue here is performance, with the optimized path we do a clone volume which is very fast whereas in the normal workflow we download the image from glance and write into the volume14:20
simondodsleyit also slows down the deployment times each time a new image needs to be created14:20
simondodsleyin a prod environment these random slowdowns are not acceptable14:21
simondodsleyas i say, not just performance but also physical space resources on the backend14:21
whoami-rajati can take a look at that but don't have HA env to test it14:22
simondodsleyif you could come up with a better patch to address the cluster environment that would be good. I'm sure the customer will be willing to test it14:23
zaitcevI suspect HA is a misnomer. The real issue is if it's okay to clone a volume that belongs to another host or not.14:23
zaitcevSome kind of SAN, Ceph, or iscsi thing has be there.14:24
simondodsleywhen its a single backend acting as the glance store  - yes14:24
simondodsleythis is why their little patch drops the host filtering14:24
simondodsleybut it is caused by A/A controllers for c-vol14:24
geguileoI think the proposed fix is not good enough14:26
simondodsleyagreed, hence wh ythe customer didn't raise the patch and came to me as the vendor of the storage they use (and this is NVMe-TCP as the dataplane, not that that makes any difference)14:27
simondodsleyif whoami-rajat is going to take a look, that is good for me  and I'm done with this topic14:29
jbernardok14:30
jbernard#topic image encryption cinder spec14:30
jbernardLuzi: that's you14:30
jbernard#link https://review.opendev.org/c/openstack/cinder-specs/+/91949914:30
Luziyeah I wrote a Cinder spec for the Image encryption, so you can look at what will actually be affected14:31
Luziand I removed the container_type encrypted from both specs, as eharney mentioned that cinder also uses the compressed container type14:31
Luziand it would be less headache when upgrading14:32
jbernardexcellent14:33
LuziI really need a good look through the spec to check, that I have considered all possible interactions of Cinder with encrypted images14:33
jbernard#action image encryption spec review14:34
Luziif there is no question from you to me, than it was all from my side14:35
jbernardok, hopefully you'll get some feedback soon14:36
jbernard#topic review requests14:36
jbernardthere are a few14:36
jbernardhitachi14:37
jbernard#link https://review.opendev.org/c/openstack/cinder/+/91672414:37
jbernardbring your own keys14:37
jbernard#link https://review.opendev.org/c/openstack/cinder-specs/+/91451314:37
jbernardand assertion calls14:37
jbernard#link https://review.opendev.org/c/openstack/cinder/+/90350314:37
jbernardthat's all for the adjenda14:39
jbernard#topic open discussion14:39
zaitcevI think we need to scan old reviews from 2016 and force-abandon them.14:41
zaitcevit's impossible to look that far back14:42
zaitcevI have browser UI issues dealing with it.14:42
jbernardthat sounds fair, how far back do we cut off?14:43
jbernardanything pre 2020?14:43
eharneywe were reviewing a patch the other day in the review meeting that was from before 202014:44
jbernardok, so maybe on a per-case basis is better than a general approach14:45
NotTheEvilOneHi. Seems like I've a bad connection today. Just wanted to give feedback that I've integrated the feedback for the BYOD spec (https://review.opendev.org/c/openstack/cinder-specs/+/914513) and are open for new one :) 14:46
jbernardzaitcev: if you want to create a list of patches you think are appropriate, that might help14:49
jbernardNotTheEvilOne: no worries14:49
jbernardNotTheEvilOne: i included your link in the review topic14:49
NotTheEvilOneThank you :)14:50
zaitcevjbernard: you mean candidates for abandonment?14:51
jbernardzaitcev: yeah, if they're old /and/ no longer relevant, those would be good candidates14:53
jbernardi know the list is quite long, some pruning would probably be good, but i dont want us to throw out old but still-useful ones14:53
jbernardok, thanks everyone!14:55
jbernard#endmeeting14:55
opendevmeetMeeting ended Wed May 22 14:55:14 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:55
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-05-22-14.01.html14:55
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-05-22-14.01.txt14:55
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-05-22-14.01.log.html14:55
jungleboyjThank you!14:55
whoami-rajatthanks!14:56

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