14:06:20 #startmeeting cinder 14:06:20 Meeting started Wed Oct 8 14:06:20 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:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:06:20 The meeting name has been set to 'cinder' 14:06:33 courtesy ping: 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 zaubea nileshthathagar flelain 14:06:51 note: meeting in #openstack-cinder (here) 14:06:57 #topic roll call 14:06:59 o/ 14:07:45 o/ 14:08:18 hi 14:09:12 #link https://etherpad.opendev.org/p/cinder-gazpacho-meetings 14:09:41 o/ 14:10:00 #topic annoucements 14:10:14 first, welcome to the G release cycle 14:10:20 o/ 14:10:27 the PTG is coming in a few weeks 14:10:37 specifically teh week of October 27 14:10:43 Brian Rosmaita proposed openstack/devstack-plugin-nfs master: DNM: tempest-full plus cinder-tempest-plugin https://review.opendev.org/c/openstack/devstack-plugin-nfs/+/949742 14:10:54 we will likely meet on Tuesday 14:10:59 we have a planning etherpad here 14:11:05 #link https://etherpad.opendev.org/p/2026.1-ptg-cinder-planning 14:11:25 i will be working to populate that this week 14:11:35 please add topics there so that I can plan and schedule time 14:12:53 #topic netapp clone across pools support 14:12:55 rosmaita: ^ 14:14:37 hello 14:15:02 just need someone from NetApp to answer my question on the patch 14:15:24 hopefully there is someone here today 14:15:58 Hello. I am here 14:16:08 great! 14:16:24 please take a look at https://review.opendev.org/c/openstack/cinder/+/958388 14:17:05 yep, we are testing this patch on our side. once we have tested the cross pool caching works, we will respond 14:17:22 thanks, just wanted to make sure you are aware 14:19:13 ok, that's all from me 14:19:39 thanks brian 14:19:53 #topic driver ci 14:20:17 im very much hoping we can get 3rd party ci reporting sorted this cycle 14:20:24 Have a patch: https://review.opendev.org/c/openstack/cinder/+/956221. This needs +2 and is ready for submission once received. Can anyone from core help with this patch? 14:21:25 im happy to use a time slot at the PTG to allow collaboration on CI setups, tips, etc 14:21:50 definately need that 14:21:54 ok 14:23:03 i don't want to have CI exceptions become the majority, and we are definately trending in that direction 14:23:46 so maybe we can share information and help everyone get this sorted at the PTG 14:23:50 hi 14:23:54 we do need some concensus on what should be reported and how/where 14:24:04 if you have a working setup and you have time to document or discuss at the PTG, that would be very helpful 14:24:20 working is a variable term :D 14:24:25 true 14:24:42 did the the novnc issue get fixed as that was causing all sorts of havoc in the CIs 14:25:01 not sure, that would be a good bullet on the planning etherpad 14:28:16 When is the PCG meeting? We might find that CI information useful as well 14:28:28 Oh, Oct 27 14:28:34 week 14:28:34 https://etherpad.opendev.org/p/2026.1-ptg-cinder-planning 14:28:40 see the header there 14:29:00 Super, thank you. 14:29:07 it is the entire week for everyone, but each project will define a schedule what makes sense for them 14:29:13 ok, thank you 14:30:00 it mostly depends on the content of the planning etherpad, i will schedule time to cover those topics and try maximize our time together 14:30:48 historically, we meet on tuesday (and possibly wednesday depending on demand) 14:31:20 we have a cross-project with ironic that i need to coordinate, ill have a concrete schedule by next meeting 14:34:44 May I bring up a patch now? 14:34:44 that is all that I have for annoucments and topics 14:35:10 is there a new etherpad for Gazpacho reviews? 14:35:14 yes - https://etherpad.opendev.org/p/cinder-gazpacho-reviews 14:35:31 haha, guess you just created it 14:35:34 wizardbit, agalica you can put requests there ^ 14:35:45 We have multiple NetApp back porting patches. Can we bring to your attenction 14:36:19 there are manu backport patches out there waiting for stable cores to review 14:36:38 These are critical for ROSHO certification 14:36:41 We are looking for reviews here: https://review.opendev.org/c/openstack/cinder/+/963344 We are willing to review other patches too 14:36:57 im looking here: https://review.opendev.org/q/project:openstack/cinder+branch:stable/2025.2 14:37:03 We also need this for critical backporting 14:37:16 simondodsley: is there a better filter i should be using? 14:37:24 look at 2025.1... 14:37:41 ahh, there we go 14:38:07 https://review.opendev.org/c/openstack/cinder/+/961437 and review.opendev.org/c/openstack/cinder/+/961436 14:38:10 rosmaita: can i filter across multiple branches? what is the query string (do you know?) 14:38:18 there are a lot for 2024.2 as well, which will only increase when the 2025.1 patches are merged 14:40:09 15 open for 2025.1 and 10 for 2024.2 14:41:59 i think maybe we have a dashboard you can use 14:42:12 @simondodsley do you still need a reviewer for https://review.opendev.org/c/openstack/cinder/+/958569 ? 14:42:28 http://tiny.cc/cinder-maintained 14:42:31 I need core reviewers 14:42:35 ok, thanks 14:42:45 I copied the patch from 2025.2 over to 2026.1. Is it fine to have it in both docs? 14:42:47 @wizardbit need a regular reviewer for your patch? 14:43:05 nice @rosmaita 14:43:17 :D 14:43:30 @agalica I believe we just need a code review 14:44:00 I can do that for you. It would be appreciated if you could look at our patch too, but I will review yours regardless 14:44:02 just noticed that it's missing Flamingo 14:44:50 can you get it to ignore the WIPs as well 14:44:54 Thank you @agalica! 14:45:21 @wizardbit are you sure you don't need a core reviewer for +2 here? I see you have two +1s for reviews 14:46:05 simondodsley: not sure, got an example? 14:46:28 there are many in Caracal that are status:WIP 14:46:49 they all look like storpool backports. 14:47:03 Not sure how a backport can be WIP 14:47:05 @agalica Sorry I'm not familiar with the process. I'm here on behalf of Erlon. I think you're right, we just need a core reviewer 14:47:06 oh, i see 14:47:24 Not sure if more reviews would help 14:47:33 @wizardbit - you need two cire reviewers and a workflow 14:47:42 ok, @wizardbit. I'm somewhat new as well and am not a core reviewer. I am pretty sure that's waht you need. If Erlon can review our patch it would be highly appreciated, but I don't think we can review yours as we don't have a core reviewer :( 14:48:11 anyone can review anything. to merge it needs core reviewers 14:48:48 if you review someone elses patch you are more likely to get your patches reviewed. it's a complimentary thing 14:49:20 Yeah simon, that's what I'm trying to do. But there's only 3 patches listed there 14:49:27 you need core and so does he 14:49:37 are there other patches we can review? The problem isn't lack of desire :) 14:49:55 we are at the start of a cycle - so there are very few patches currently. 14:50:05 We just need https://review.opendev.org/c/openstack/os-brick/+/955379 to at least be accepted (not necessarily merged) by the core reviewers, so that we can put it into our packages and expect this to be in a future release 14:51:56 ok, that's all i have; anything else? 14:52:06 you did have one +2 for this but your latest upload (fixing the commit) lost that. You have to start again with the cores 14:52:37 Also you should get @whoamirajat to clarify his previous -1 14:52:39 rajat should circle back for that 14:52:58 other cores will wait for rajat to confirm his concerns have been addressed 14:53:39 Ok. What's the best path forward to alert Rajat? Add him to the patch? Reply int he now-abandoned patch? 14:53:59 he's in IST timezone, 14:54:16 because he reviewed it once, he's in the CC, so a comment on the patch should reach his inbox 14:54:21 ok, thank you 14:55:38 no problem 14:55:41 ok, last call 14:56:01 thanks everyone 14:56:04 #endmeeting