14:00:02 <whoami-rajat> #startmeeting cinder
14:00:02 <opendevmeet> Meeting started Wed Aug 30 14:00:02 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:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:02 <opendevmeet> The meeting name has been set to 'cinder'
14:00:05 <whoami-rajat> #topic roll call
14:00:07 <jbernard> o/
14:00:12 <rosmaita> o/
14:00:15 <Saikumar> o/
14:00:37 <eharney> o/
14:00:40 <Dessira> o/
14:00:41 <tosky> o/
14:00:58 <toheeb> o/
14:01:03 <thiagoalvoravel> o/
14:01:10 <caiquemello[m]> o/
14:01:16 <simondodsley> o/
14:02:12 <keerthivasansuresh> o/
14:02:14 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-bobcat-meetings
14:02:19 <msaravan> Hi
14:03:03 <whoami-rajat> hello everyone
14:03:06 <whoami-rajat> let's get started
14:03:12 <whoami-rajat> #topic announcements
14:03:24 <whoami-rajat> first, Nominated myself for Cinder PTL during 2024.1 Cycle
14:03:32 <whoami-rajat> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034902.html
14:03:54 <simondodsley> :+1
14:03:55 <rosmaita> \o/
14:04:01 <jungleboyj> o/
14:04:19 <whoami-rajat> I've nominated for the cinder PTL for 2024.1 (Caracal) cycle and if no one else nominates themselves, I will be your PTL again for next cycle :)
14:05:11 <whoami-rajat> good to see people happy after 3 cycles :D
14:05:20 <whoami-rajat> that does add some motivation for the next cycle
14:05:38 <jungleboyj> whoami-rajat: Thank you for continuing!
14:06:16 <whoami-rajat> :)
14:06:25 <whoami-rajat> ok moving on
14:06:28 <whoami-rajat> next, os-brick 6.4.0 released
14:06:34 <whoami-rajat> #link https://review.opendev.org/c/openstack/releases/+/892213
14:06:39 <whoami-rajat> #link https://pypi.org/project/os-brick/6.4.0/
14:06:49 <whoami-rajat> last week was non-client library release
14:07:04 <whoami-rajat> so os-brick was part of that release cycle
14:07:20 <whoami-rajat> the patch was merged on monday but proposed last week so technically we were on time
14:07:32 <whoami-rajat> anyway, os-brick is released with it's latest version 6.4.0
14:08:10 <whoami-rajat> finally we have some upcoming deadlines
14:08:16 <whoami-rajat> Bobcat-3 milestone (feature freeze): August 31st (R-5 week)
14:08:16 <whoami-rajat> RC1 deadline: September 14th (R-3 week)
14:08:17 <whoami-rajat> Final RC deadline: September 28th (R-1 week)
14:08:17 <whoami-rajat> Final 2023.2 Bobcat release: October 4th, 2023
14:08:30 <whoami-rajat> We are going to discuss the feature freeze as a topic
14:08:52 <whoami-rajat> that were all the announcements, I couldn't find any other thing of interest on the mailing list
14:09:03 <whoami-rajat> but i remember we had a gate issue with tox that rosmaita was referring to
14:09:18 <whoami-rajat> which seems to be fixed now, but if you would like to highlight it? rosmaita
14:09:47 <rosmaita> there was an issue with a dependency of tox, got fixed by a new release of that dependency and a new release of tox
14:09:55 <rosmaita> so 4.11.0 should be good
14:10:09 <whoami-rajat> thanks!
14:10:20 <whoami-rajat> so if you see any gate failures due to tox, you can recheck and it should be good
14:12:38 <whoami-rajat> also I'm working on the mid cycle summary, it should be up today or tomorrow, I will update on the mailing list
14:14:04 <whoami-rajat> and a reminder that if you haven't registered for the virtual PTG in October, here is the link
14:14:06 <whoami-rajat> #link https://openinfra.dev/ptg/
14:15:08 <whoami-rajat> that's all for the announcements
14:15:19 <whoami-rajat> anyone has anything else?
14:15:25 <whoami-rajat> for the announcements i mean
14:17:36 <whoami-rajat> ok, let's move to topics
14:17:44 <whoami-rajat> #topic Feature Discussion
14:17:52 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-2023.2-bobcat-features
14:18:15 <whoami-rajat> it would have been easier in the video meeting that was planned for today but since we met last week for midcycle, I thought of skipping this week's video meeting
14:18:37 <whoami-rajat> anyway, let's get started with discussing the features one by one
14:18:39 <whoami-rajat> first, Add the os-extend_volume_completion volume action
14:18:48 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder/+/873557
14:19:13 <whoami-rajat> The reason I've held reviews on this is that cinder calls Nova to extend the volume (in case of FS drivers)
14:19:22 <whoami-rajat> last time i checked this morning, nova side changes haven't merged yet
14:19:37 <whoami-rajat> so I'm skeptical of merging the cinder changes since the extend operation might start failing
14:19:54 <whoami-rajat> is the author of this feature around?
14:20:21 <whoami-rajat> i think he just disconnected ...
14:21:39 <whoami-rajat> here is the nova patch
14:21:41 <whoami-rajat> #link https://review.opendev.org/c/openstack/nova/+/873560
14:22:16 <kgube> sorry, i disconnected just at the wrong moment
14:22:25 <whoami-rajat> kgube, no worries
14:22:42 <whoami-rajat> kgube, I was pointing out the dependency on nova for this feature which is still not merged
14:22:53 <kgube> so the nova change is actually dependent on the first cinder change
14:23:06 <kgube> the cinder change is multi-part
14:23:56 <kgube> the first one just adds the new volume action
14:24:15 <kgube> then there is the nova change that depends on that
14:24:56 <kgube> and then there is the second cinder change that relies on the new behavior of nova: https://review.opendev.org/c/openstack/nova/+/873560
14:25:34 <kgube> this is reflected in the gerrit dependencies
14:26:17 <kgube> and Nova actually held back reviews because the first cinder change was still open :/
14:28:00 <whoami-rajat> ok, thanks for clarifying that
14:28:15 <kgube> So I guess I should have tried to communicate this more clearly
14:28:54 <whoami-rajat> kgube, another question is, if we merge the first change, will it impact the current workflow we have? I haven't gone through the code yet so not sure if it's making any functional changes in the extend workflow
14:30:12 <kgube> It won't impact the current workflow, as far as I can tell
14:31:01 <kgube> but it adds dead code for now
14:31:16 <whoami-rajat> ok, a related question is, how flexible is nova on granting an FFE for the nova changes?
14:31:44 <whoami-rajat> looks like there is only one change from nova side
14:32:02 <kgube> I don't think it's a priority feature for them
14:33:45 <whoami-rajat> hmm, we could grant an FFE but it would be useless until nova is also willing to do the same
14:34:01 <whoami-rajat> we will be just adding a microversion and an API call that is never made
14:34:15 <kgube> they told me last week that either the dependencies needs to merged asap, or they aren't going to allocate review time to it
14:34:59 <whoami-rajat> ok, i wasn't aware but last week's midcycle was a good place for this discussion
14:35:29 <kgube> Yeah, I couldn't make it, unfortunately
14:35:34 <whoami-rajat> not denying the fact that we lack review bandwidth and that also needs to be addressed, but that's a separate topic for now
14:36:39 <whoami-rajat> at this moment, even if we merge the first cinder change (given it doesn't require changes to be made), we need commitment from nova that they will merge their side of changes in this cycle
14:36:49 <whoami-rajat> that's my thought on it at least
14:37:08 <whoami-rajat> would like to see if the team has other comments on it
14:38:29 <rosmaita> i think we need at least one +2 on the patch before nova will take it seriously
14:42:34 <whoami-rajat> I can commit on reviewing it, since mostly it's just adding a new action
14:43:11 <whoami-rajat> if bauzas is around, he can provide us the nova team's thought on the feature
14:43:52 * bauzas scrolling up
14:44:12 <whoami-rajat> bauzas, thanks for joining, i will summarize the discussion
14:44:15 <bauzas> well, we haven't defined any FFE period
14:44:27 <bauzas> and we don't plan it
14:44:45 <whoami-rajat> we're discussion about the feature https://review.opendev.org/c/openstack/nova/+/873560
14:45:13 <bauzas> the nova consensus is more about letting the feature to be merged in Cinder ideally during the Bobcat release so we can merge it quickly on Caracal on our side
14:46:12 <whoami-rajat> hmm, the problem i see is that will introduce a new microversion on the cinder side in the bobcat release that is unused ...
14:46:33 <whoami-rajat> maybe it's not a big issue, but i would avoid having that in our cycle highlights
14:48:07 <whoami-rajat> kgube, if the feature is going to be used in Caracal by nova, would you mind if the cinder changes are also part of the same cycle?
14:49:11 <kgube> whoami-rajat, I mean, its not ike we can use the feature, when only half of it is merged
14:49:33 <kgube> so, no, I guess not
14:50:02 <kgube> but It would be nice if we can avoid keeping it to the last minute, next cycle
14:50:08 <bauzas> thanks kgube
14:50:13 <whoami-rajat> sure
14:50:17 <whoami-rajat> so I will plan on getting this reviewed and merged by milestone-1 of Caracal
14:50:41 <bauzas> kgube: will you be able to repropose the feature as soon as I'm opening the dev cycle on Caracal ?
14:50:51 <bauzas> this won't be long, a matter of 2.5 weeks
14:51:00 <kgube> bauzas: sure!
14:51:28 <bauzas> maybe you don't know, but Caracal feature development cycle opens as soon as we deliver Bobcat RC1
14:51:29 <whoami-rajat> thanks bauzas and kgube for the discussion
14:52:02 <whoami-rajat> ah, that's good to know
14:52:12 <bauzas> https://releases.openstack.org/bobcat/schedule.html#rc1-target-week
14:52:19 <bauzas> which is planned Sep 11th
14:52:45 <bauzas> after that, I'll shortly create the specs directory for caracal and the blueprint release tag name
14:53:14 <whoami-rajat> ack, I will carry out the similar work for cinder
14:53:30 <whoami-rajat> would be good if kgube can provide some reminders if we miss out on anything :)
14:53:57 <kgube> whoami-rajat, I will try to be less shy about it :)
14:54:19 <whoami-rajat> thanks again
14:54:22 <bauzas> kgube: thanks and yeah, don't feel you offense ourselves
14:54:40 <whoami-rajat> thanks for your time bauzas , really appreciate it
14:54:42 <bauzas> we just have a reasonable amount of different priorities and somehow communication helps sorting them
14:55:40 <whoami-rajat> ++
14:56:02 <whoami-rajat> so i would quickly like to go through some of the other features
14:56:14 <whoami-rajat> Fujitsu Driver: Add QoS support
14:56:21 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder/+/847730
14:56:38 <whoami-rajat> I've already reviewed it previously, just need to go through the latest update
14:56:55 <whoami-rajat> but we require another reviewer to take a look at this
14:57:17 <inori1> Here I am. Previously, rajat provided some comments on it, and I have addressed those comments and passed both Zuul and our CI tests.
14:57:40 <whoami-rajat> thanks for updating it inori1 , I will take a look shorty after this meeting
14:57:52 <whoami-rajat> please add your name as a second reviewer here
14:57:55 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-2023.2-bobcat-features#L13
14:58:15 <whoami-rajat> next, NetApp ONTAP: Added support to Active/Active mode in NFS driver
14:58:24 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder/+/886869
14:58:31 <whoami-rajat> it has 2 +2s
14:58:37 <whoami-rajat> but has a dependency on 2 other patches
14:58:40 <inori1> Thank you. whoami-rajat
14:58:52 <whoami-rajat> no problem
14:59:01 <msaravan> yes, the main patch got +2, and one of the dependent patch has zull failure and its not related. I re-triggered it now. It'll go through.
14:59:33 <whoami-rajat> msaravan, ack, thanks for the update, I will take a look at the dependent patches
14:59:52 <msaravan> thank you Rajat. Much appreciated.
15:00:17 <whoami-rajat> np
15:00:20 <whoami-rajat> so we are out of time
15:00:29 <msaravan> can we  have a possible FFE for this, if this is not closed tomorrow.
15:00:45 <whoami-rajat> but I would like to provide a 1 week extension for all the remaining features
15:00:59 <msaravan> thank you
15:02:38 <whoami-rajat_> sorry i got disconnected
15:02:54 <whoami-rajat_> these were my last messages
15:02:56 <whoami-rajat_> <whoami-rajat> but I would like to provide a 1 week extension for all the remaining features
15:02:58 <whoami-rajat_> <whoami-rajat> since we have too many and too less reviews on it
15:03:02 <whoami-rajat_> <whoami-rajat> I will send out a mail tomorrow regarding this
15:03:04 <whoami-rajat_> <whoami-rajat> thanks everyone for joining
15:03:06 <whoami-rajat_> #endmeeting