14:00:07 #startmeeting cinder 14:00:07 Meeting started Wed Jul 27 14:00:07 2022 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:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:07 The meeting name has been set to 'cinder' 14:00:12 #topic roll call 14:00:20 hi 14:00:23 here - but can't join on video 14:00:30 hi! 14:00:33 o/ 14:00:34 today's meeting is in video+IRC format so join here https://redhat.bluejeans.com/556681290 14:00:42 o/ 14:01:08 simondodsley, ack np 14:01:20 o/ 14:01:20 Hi 14:01:30 o/ 14:01:51 o/ 14:02:51 #link https://etherpad.openstack.org/p/cinder-zed-meetings 14:04:39 hi 14:05:49 hi 14:06:23 Is Antelope, OR or is this the animal? 14:07:21 #topic announcements 14:07:33 OpenStack next release name is out and it's Antelope 14:07:47 HappyStacker, i think it is 14:07:56 next, Driver merge deadline this week 14:08:01 oh great 14:13:14 is the pure driver being looked at with the associated dependencies? 14:14:35 simondodsley, do you mean the os-brick dependencies? 14:14:51 there is also a tempest patch dependency which in itself is dependent on a small cinder patch 14:16:50 added those to the etherpad 14:17:20 #link https://review.opendev.org/c/openstack/tempest/+/849841 14:17:50 simondodsley, will take a look at the tempest patch but QA team can merge it so good to ask them for reviews 14:17:58 and for the driver, geguileo and I have agreed to review it 14:18:15 thery have already seen it and are waiting on the cinder patch 14:18:59 so we need the cinder driver In first and tempest is dependent on it? 14:19:20 cinder patch, then tempest, then os-brick then the driver 14:19:40 ack 14:19:41 sorry for the deep dependencies, but this is a new protocol we are messing with here... 14:19:59 1) https://review.opendev.org/c/openstack/cinder/+/849690 14:20:01 2) https://review.opendev.org/c/openstack/tempest/+/849841 14:20:15 3) https://review.opendev.org/c/openstack/cinder/+/799871 14:20:26 sorry, 3) os-brick patches (MERGED) 14:20:27 4) https://review.opendev.org/c/openstack/cinder/+/799871 14:20:33 yep 14:21:21 we're discussing it right now 14:30:43 next, Cinder midcycle-2 planning 14:31:43 simondodsley, not sure i remember correctly but did you have a conflict on 10th august -- related to midcycle-2 14:34:39 #topic os-brick CI follow-up 14:36:32 #topic Ceph: add option to keep only last n snapshots per backup 14:36:40 jhartkopf that's you 14:36:54 yes 14:37:08 So there was an issue with incremental backups when base backups were deleted by the new feature, but this should be resolved now. I pushed that patch some months ago. 14:37:37 Is it realistic to get this merged before Zed releases? 14:37:43 do we have any tempest tests that exercise this functionality? (just for risk assessment) 14:37:56 #link https://review.opendev.org/c/openstack/cinder/+/810457 14:38:16 jhartkopf: there's still time to merge it 14:38:28 I don't see any link to the blueprint, as it seems to be a new feature 14:38:49 Well, maybe more of a refinement instead of a new feature 14:39:41 ok, so we're good if no blueprint is provided? 14:39:54 it has a related bug linked https://bugs.launchpad.net/cinder/+bug/1703011 14:39:58 jhartkopf: we definitely don't have this covaered by tempest 14:41:59 enriquetaso: Yep I saw it. thanks 14:42:03 jhartkopf, the releasenote mentions it's a new feature, we need some clarity on it since deadlines for features and bug fixes are different 14:42:51 jhartkopf, we discussed that a tempest test is needed, even if it doesn't cover the whole feature, it will make sure we're not breaking anything 14:44:00 whoami-rajat: Ok, so should I add another test to tempest? Or what would be the best way going forward with this? 14:45:05 jhartkopf: probably best to add it to the cinder tempest tests and not tempest itself 14:45:13 (that's what I think) 14:46:55 i.e https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/791921 14:47:22 enriquetaso_: thanks for the link :-) 14:48:05 let's move to open discussion 14:48:08 #topic open discussion 14:48:16 Hi, i have created a third party CI setup for Fungible driver. Would like to request permission to test against the Cinder repo. Shall I enable commenting on Cinder patches? The setup is validated using ci-sandbox and look good. 14:48:36 cinder-mypy (non-voting) is failing on all patches until we merge https://review.opendev.org/c/openstack/cinder/+/851032 14:48:51 aneeeshp1, we allow third party CIs to comment on patches but it should be non voting 14:49:05 geguileo, enriquetaso_: Thanks, will look into this 14:49:28 whoami-rajat okay thank you. I will enable it only after removing the voting. 14:49:55 eharney: I added a comment 14:50:15 jhartkopf: thank you for working on it 14:50:43 aneeeshp1, thanks, but I'm afraid we're too close to the deadline that fungible driver might not be able to make it into this release 14:51:20 whoami-rajat I understand that. I too think it will slip to the next release. 14:52:11 aneeeshp1, ack, good to know, we can start reviewing it early next release 14:52:29 whoami-rajat great thank you 14:52:39 thanks! 14:53:47 thanks everyone for attending 14:53:48 #endmeeting