14:00:18 #startmeeting cinder 14:00:18 Meeting started Wed Jul 31 14:00:18 2024 UTC and is due to finish in 60 minutes. The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:18 The meeting name has been set to 'cinder' 14:00:23 #topic roll call 14:00:28 o/ 14:00:35 o/ 14:00:43 o/ 14:02:11 o/ 14:02:21 o/ 14:02:21 o/ 14:02:44 hey 14:02:53 o/ 14:03:14 #link https://etherpad.opendev.org/p/cinder-dalmatian-meetings 14:03:40 #link https://releases.openstack.org/dalmatian/schedule.html 14:03:49 o/ 14:05:25 This is will a quick one I think, mostly a few moments for open discussion 14:05:33 we have about 1 month until feature freeze 14:06:13 What I need to do to have my patches reviewed? 14:06:21 I am starting to worry 14:06:27 the review requests that have been on the list for a while - a few have been reviewed and the remaining are on my short list 14:07:05 yuval: i will increase the review priority so others may see them 14:07:38 Thanks 14:07:38 yuval: i could also be helpful to trade reviews with someone, offer to review there patches in exchange - that sometimes can get things moving for both 14:08:07 I am up for reviews if anybody need my 2 eyes 14:09:34 rosmaita: is there anything we should note regarding the recents CVE and fixes? 14:10:18 just that a few regression bugs have been filed, seem to affect nfs based backends 14:10:33 or drivers that are subclasses of the remotefs driver, to be more specific 14:11:24 i looked into some of the bugs with whoami-rajat, i think we have an idea of how to fix, should have patches up soon 14:11:38 awesome, thanks 14:11:45 Thanks 14:12:03 would be good for quobyte and virtuozzo to get their CIs fixed so they can run full tempest suites 14:12:38 rosmaita: aren't they both deprecated? or am i thinking of something else? 14:13:08 they are, but they haven't been removed yet, and there may be some people still using them 14:13:37 ok 14:13:46 but yeah, deprecated driver + no CI + CVE issue can mean driver removal 14:14:46 what is the time window? should we set a time to make that decision? 14:15:06 did we check with dell team, i remember they also have a dell NFS driver inheriting from our generic driver 14:15:18 if they are also facing similar issue 14:15:26 yes, they have filed a bug 14:15:35 ok 14:15:38 https://bugs.launchpad.net/bugs/2073503 14:15:55 i should list the bugs we know about in the etherpad, will do that now 14:17:24 thanks 14:17:26 are we using qcow2 images for dell? 14:17:44 sorry, qcow2 volumes 14:18:11 do we understand what was the root issue? 14:18:24 but since it's a bootable volume, whenever we attach it, it will report a qcow2 volume 14:18:37 so it's the same 14:18:43 the dell issue has to do with backup/restore, so i assume qcow2 is involved 14:19:25 yeah, when they restore the volume (containing the image), and we attach it (to launch the VM), it does the virtual size check and thinks it's a qcow2 volume (whereas it's a raw volume with a qcow2 image) 14:19:28 but it's also backup of a volume containing a bootable image, so definitely qcow2 14:19:43 correct 14:20:18 so it affects all operations involving attaching a bootable volume, which are most of our use cases ... 14:21:06 but why the size is not the same? parsing of the result is different? or the qcow have a different size? 14:22:30 the size is same, the issue is with the format inspector (or the qemu-img tool) detecting a raw volume as qcow2 when it has a qcow2 image inside it 14:22:43 because of the header 14:22:54 whoami-rajat has an analysis on https://bugs.launchpad.net/cinder/+bug/2073146 that explains in more detail 14:23:05 Thanks will check it out 14:24:57 on a general note, does anyone have any blockers or need something that I might be able to help with? 14:24:59 I see so we checked image size vs volume size 14:25:02 (reviews aside) 14:25:45 yuval, yes 14:26:39 zaitcev, can you take a look at my reply on my patch, it blocks adding OSC and SDK support for default types 14:26:41 #link https://review.opendev.org/c/openstack/cinder/+/920308 14:30:08 #topic open discussion 14:30:13 Hi all, I need quick glance on small PR of storpool #link https://review.opendev.org/c/openstack/cinder/+/847132 14:31:37 kpdev: ill review this today 14:31:42 it's also on my list 14:32:07 jbernard: thanks 14:32:14 jbernard: did you get my e-mail about core resignation? 14:32:33 Please can someone take a look https://review.opendev.org/c/openstack/manila-ui/+/923597 14:33:22 zaitcev: i see it, but i haven't had a chance to responde yet 14:34:04 zaitcev: there is group one can be added/removed 14:34:39 how one's become a core reviewer? 14:35:00 yuval: Do normal reviews with good comments for a cycle or two. 14:35:04 yuval: consistent and helpful reviews 14:35:19 I see 14:35:33 yuval: if you feel you're already there but just haven't been considered, feel free to reach out 14:36:15 the process is less defined than it probably should be 14:36:29 I am quite dependent on my company regarding availability but I can discuss it with my superiors 14:36:38 jbernard :) 14:38:10 alright, anything else? 14:38:40 Is someone seeing a surge in openstack usage in the last few months? 14:38:56 i am - lots of requests for information and POCs 14:39:42 vmware stuff my guess 14:39:44 I've had a number of large enterprises say they are dumping VMware and are moving to OpenStack 14:40:01 AWS was putting screws to people a little bit. Dropping services left and right. And then VMware jacked up prices too. 14:40:08 A large Telco just got screwed with a 5x license cost 14:40:24 the new skype 14:40:30 they had 30 days notice so they had to pay 14:41:24 the only issues from a convertion perspective is DRS equivalence. 14:41:40 I'm loooking at Masakari and Watcher to see how they can compete 14:42:47 interesting 14:43:15 ccokeke[m]: wrong link? (that's for manilla-ui) or possibly wrong meeting? 14:44:33 I think we are done 14:44:42 alright everyone, thanks and please reach out if something is blocking or needed, have a good week and "see" you all next week 14:44:45 #endmeeting