14:00:27 #startmeeting cinder 14:00:27 Meeting started Wed Aug 16 14:00:27 2023 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:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:27 The meeting name has been set to 'cinder' 14:00:29 #topic roll call 14:00:56 o/ 14:01:03 o/ 14:01:04 o/ 14:01:05 o/ 14:01:08 o/ 14:01:10 o/ 14:01:16 hi 14:01:19 o/ 14:01:37 hi 14:01:51 o/ 14:01:59 o/ 14:02:04 Hi Everyone 14:02:04 o/ 14:02:47 #link https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:03:28 good turnout, let's get started 14:03:32 #topic announcements 14:03:37 first, Midcycle 2 on 23rd August 1400-1600 UTC 14:03:43 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034748.html 14:04:14 as discussed last week, we are planning to conduct midcycle-2 next week 14:04:37 till now i haven't received any concerns but if there are, feel free to reply on the mailing thread 14:04:48 else we will continue to go with the scheduled date and time 14:04:51 need review for 890818: [NetApp] LUN space allocation support for iSCSI | https://review.opendev.org/c/openstack/cinder/+/890818 14:04:58 updated etherpad 14:05:40 jayaanand, we can discuss that in the open discussion part of the meeting (towards the end) 14:05:55 sure, Thank you! 14:05:58 np 14:06:10 #link https://etherpad.opendev.org/p/cinder-bobcat-midcycles 14:06:18 this is the etherpad for the midcycle 14:06:26 ok 14:06:27 please add your topics, we still have a week's time 14:06:56 another thing related to this is Festival of XS reviews 14:07:34 Not sure if this impacts anyone else, but next week is VMware Explore. 14:07:50 But if no one has said anything, I am guessing it is just me then. :-) 14:08:11 ah, anyone here planning to attend the VMware Explore event? 14:09:45 guess not, sorry jungleboyj for the conflict if you are planning to attend it 14:10:06 Yeah, I have to be at that event. So, sorry for the conflict. 14:10:21 jungleboyj: we blame VMware 14:10:32 LOL 14:11:17 it is going to be recorded so we should be good 14:12:28 so a lot of redhatters (which has a big overlap with the upstream group) are not going to be around this friday 14:12:43 also the midcycle agenda as of now is looking very light 14:12:52 so we are planning to combine the two events 14:13:33 so this friday we won't have the festival of reviews 14:13:51 I will reply the same to the midcycle thread after the meeting 14:15:25 moving to the next announcement 14:15:27 PTL + TC nominations 14:15:32 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034744.html 14:16:11 the nomination for PTL and TC candidates has started from today 14:16:12 PTL + TC nomination starts @ Aug 16, 2023 23:45 UTC 14:16:12 PTL + TC nomination ends @ Aug 30, 2023 23:45 UTC 14:16:21 it will go on for 2 weeks 14:16:47 It's still not finalized from my end if I'm going to run again but if anyone feels like running for the PTL, feel free to contact me 14:17:25 I can share my experience and guide you through the responsibilities 14:18:45 next, 2024.1 proposed runtimes 14:18:51 #link https://492c0e14580207d3137a-fae58b9e5b5334364b7bbd906acbdb71.ssl.cf5.rackcdn.com/891225/2/check/openstack-tox-docs/e628821/docs/reference/runtimes/2024.1.html 14:19:06 the patch is still not merged so sharing the generated html link 14:19:18 major changes in runtime is 14:19:19 Debian 12 - py3.11 14:19:19 Ubuntu 22.04 - py3.10 14:20:23 next, Releasenotes for non-SLURP and SLURP releases 14:20:28 #link https://docs.openstack.org/project-team-guide/release-management.html#release-notes-for-slurp-releases 14:21:18 rosmaita proposed this document for the SLURP and non-SLURP releasenotes which is easy to follow along 14:21:44 i think it's intended for the PTL but just so others know what to look for in the upcoming release notes 14:22:02 as i understand from the document, here are the changes required for slurp and non-slurp releases 14:22:02 non-SLURP: create a static file right after the release (2023.2) 14:22:03 SLURP: Add a link to the previous non-SLURP release notes (static file) in the prelude section 14:22:33 yeah, i am supposed to be working on automating that, but haven't got anything together yet 14:24:04 i think the efforts required are pretty minimal and needs to be done once a release 14:24:18 the main thing is we should not forget to do it, else everything looks good 14:24:43 yeah, if i don't get the automation done, i will at least send out reminders! 14:26:09 that would be great 14:26:32 final announcement, Upcoming deadlines 14:26:38 os-brick release: August 24th, 2023 (R-6 week) 14:26:38 cinderclient release: August 31st, 2023 (R-5 week) 14:26:38 Feature freeze (M-3): August 31st, 2023 (R-5 week) 14:26:38 Final 2023.2 Bobcat release: October 4th, 2023 14:26:53 so please finalize your os-brick, cinderclient and feature changes 14:27:00 since those are the main review targets for next couple of weeks 14:28:14 we have a couple of patches in os-brick that would benefit from reviews 14:28:15 https://review.opendev.org/q/project:openstack/os-brick+status:open+branch:master 14:28:27 i will try to create an etherpad for the patches that we should target for the release 14:30:29 that's all the announcements 14:30:34 let's move to topics 14:30:42 #topic cinder-plugin-ceph-tempest job failing since 11 August 14:30:44 rosmaita, that's you 14:30:59 ok, topic title says it all 14:31:12 i believe this patch to cinderlib will fix it: 14:31:21 #link https://review.opendev.org/c/openstack/cinderlib/+/891513 14:32:13 the gates are in a terrible state these days 14:33:16 rosmaita, thanks for fixing that, do we know how this dependency got introduced? 14:34:01 no, i looked at our handy requirements dashboard (line 83 on the agenda etherpad) but nothing changed since 11 august 14:34:37 must be that one of our requirements requirements changed something and etcd3gw isn't loaded any more 14:35:09 cinderlib mostly relies on cinder's requirements.txt 14:35:18 and cinder doesn't ask for the tooz extra 14:36:16 or something changed in devstack maybe, because this only shows up in the devstack-based jobs, the straight cinderlib-functional tests don't run into this issue 14:39:18 ok, yeah i think it was being indirectly installed from somewhere which isn't the case now so good to have it in cinderlib's requirements 14:39:29 +2ed, need another core to merge 14:39:48 whoami-rajat: I will do. 14:39:55 thanks! 14:39:57 is etcd3gw the only lock backend used for the tests? 14:40:01 thanks jungleboyj 14:40:23 or, is it used at all? 14:40:38 eharney: i don't really know 14:42:08 seems like we should be using file locks and this shouldn't cause a failure, but whatever gets it to pass for now is fine 14:43:08 not sure either 14:43:27 that's all the topics we had for today 14:43:31 let's move to open discussion 14:43:35 #topic open discussion 14:45:30 @rajat and others - do we need a blue print for this patch ? https://review.opendev.org/c/openstack/cinder/+/886869 14:46:27 There was one blueprint present long back, and we have implemented it for NetApp only now. https://blueprints.launchpad.net/cinder/+spec/cinder-volume-active-active-support 14:46:37 blueprints are generally good to have for tracking changes 14:46:38 So, wanted to know whether we need a new blueprinit for active-active support for netapp data ontap systems. 14:47:15 Okay, its very driver specific. Will register a blueprint for this; 14:47:17 thank you; 14:47:41 this change is pretty minimal and driver specific so maybe we can give it a pass 14:47:56 thank you :-) 14:47:56 would like to know what others think about it 14:49:02 whoami-rajat: I think given that it is pretty small and driver specific we don't have to have the blueprint. 14:49:19 i think the contained nature of adding support for an already defined feature, it's okay for no blueprint (personally) 14:49:56 Also it has reference to a spec for the implementation in the commit. 14:50:00 It should be good. 14:50:14 ok, thanks for the inputs 14:50:23 msaravan, looks like the patch is good and doesn't require a BP 14:50:57 Okay, thank you whoami-rajat jungleboyj jbernard 14:55:25 Any concerns with me just merging that whoami-rajat then? 14:56:33 jungleboyj, do you mean the netapp patch? no concerns just it's dependent on a bunch of other fixes 14:57:18 Ah, I missed that. Ok. I added my +2. :-) 14:57:40 thanks jungleboyj 14:57:59 thank you jungleboyj whoami-rajat 14:58:04 we are almost at the end of the hour 14:58:18 we need help in other pending reviews as well, they are captured at https://etherpad.opendev.org/p/cinder-bobcat-meetings 14:58:32 sure msaravan 14:58:37 please take a look at the review requests 14:59:13 thanks everyone for joining 14:59:17 #endmeeting