14:00:08 #startmeeting cinder 14:00:08 Meeting started Wed Dec 21 14:00:08 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 The meeting name has been set to 'cinder' 14:00:12 #topic roll call 14:00:36 hi 14:00:37 hi 14:00:40 hi 14:00:49 o/ 14:00:50 o/ 14:00:59 \o 14:01:30 #link https://etherpad.opendev.org/p/cinder-antelope-meetings 14:01:53 hi 14:02:25 Hi 14:03:11 good turnout today, let's get started 14:03:17 hi 14:03:29 but before that, thanks rosmaita for running last week's meeting and festival of XS reviews! 14:03:40 :) 14:04:01 #topic announcements 14:04:05 first, Cinderlib Zed released! 14:04:13 #link https://review.opendev.org/c/openstack/releases/+/864504 14:04:19 #link https://pypi.org/project/cinderlib/5.0.0/ 14:04:21 woohoo!! 14:04:41 thanks rosmaita and everyone else for making this possible 14:04:47 we were very close to missing it 14:05:05 right now we've already opened cinderlib for Antelope to avoid any last minute issues 14:05:16 I assume the patch is merged 14:05:24 \o/ 14:05:56 so we're good on this one 14:06:04 next, Extended spec deadline to 23rd December 14:06:10 #link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031542.html 14:06:24 I've extended the spec freeze deadline to this week 14:06:37 which also is in 2 days 14:06:54 there are 2 specs that are good candidates to get included 14:06:59 1) Encrypted backups 14:07:07 #link https://review.opendev.org/c/openstack/cinder-specs/+/862601 14:07:23 geguileo, started working on it but he's on leave now and will be back next year 14:07:44 I'm hoping if anyone else is interested in taking it up and addressing the feedback? 14:08:23 Christian wanted to have this feature but not sure if he's interested to take it up, also we're pretty close to deadline 14:09:07 If someone takes it up, we can probably extend the deadline for this one 14:09:13 but let's see 14:09:27 2) Extend in-use FS volumes 14:09:33 #link https://review.opendev.org/c/openstack/cinder-specs/+/866718 14:10:17 kgube proposed an original spec which was abandoned based on nova feedback but he has another spec up 14:10:26 I just finished reviewing it few minutes ago 14:11:03 overall the idea looks good, all the cases in my mind have already been mentioned there like if nova-cinder loses connectivity, we will have a os-reset-state call for it 14:11:06 and other things 14:11:19 so it looks pretty good apart from few suggestions/questions I've on the spec 14:11:33 please review this one as this is very close 14:11:54 kgube, if you're around, can you update with the status of nova spec? 14:12:23 yeah 14:13:12 sean mooney had some suggestions but said it would be ready to merge if I addressed them 14:13:36 I did, but he hasn't reviewed them yet 14:14:03 ok, then it looks good from nova side as well 14:14:04 overall feedback was good 14:14:13 cool, thanks for the update 14:15:06 there was another feature we discussed during midcycle but there is no spec up for it so we will leave it for next cycle 14:15:26 with that we can move to next announcement 14:15:29 next, 2023 PTGs + Virtual Team Signup 14:15:36 We will be having 2 PTGs: one virtual (March 27 -31, 2023) and one in-person (June 14 -15th, 2023) along with summit 14:15:46 to be honest, I'm not really sure of the purpose of second PTG 14:15:59 since we would already have discussed everything in the first one 14:16:20 first one is a virtual one which we've been conducted for few cycles now 14:16:34 second is an in-person along with summit 14:17:12 #link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031512.html 14:17:23 I get the whole "we hate Elon" thing at the moment, but forcing a Mastadon username as a mandatory field is a bit much. If anything should be mandatory, it should be your IRC handle. 14:17:24 there are 2 registrations, 1 team and 1 individual 14:17:48 I've registered our team for virtual PTG 14:18:01 you can register yourself for the eventbrite one, it's free and only used as a head count 14:18:14 #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 14:18:16 simondodsley++ 14:18:27 simondodsley, yeah, I had issues with that as well 14:18:42 though i just mentioned my IRC handle and got away with it but that field seems to be a problem 14:18:54 I just put "." 14:19:08 that also works 14:19:20 mayne we should all put "elon" 14:19:35 lol 14:20:51 that's all i had for the announcement, let's see what they're planning for in the second PTG 14:20:58 next, Election dates finalized 14:21:04 #link https://governance.openstack.org/election/ 14:21:16 the TC have finalized election dates for PTL and TC 14:21:20 Drinks and canopes 14:21:33 :D 14:21:54 so keep a look if you've planning to nominate yourself for any of those 14:22:54 next, Next week meeting (28th December) 14:23:07 I figured most of the people will be on year end break so asking here 14:23:12 Will enough people be around to conduct the meeting or should we cancel it? 14:23:17 I will be here 14:23:31 i won't 14:23:48 not me 14:23:52 I won't 14:24:26 looks like the majority isn't going to be here and some of the people have already left 14:24:48 "voting with their feet" 14:24:48 so let's cancel it and meet next year directly on 4th January 14:25:03 okie 14:25:39 I will send out an email regarding this 14:25:53 that's all I had for my announcements 14:25:57 but rosmaita has added some 14:26:07 so i will hand it over to him to mention them 14:26:19 just some general info for awareness 14:26:27 gates start using tox 4 by default starting tomorrow 14:26:37 #link https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/3NNATSUTSIGP5FE2MDY5X2KJ5X4NB4PT/ 14:26:44 fingers crossed! 14:26:54 i am hoping we will be ok, but some stuff is beyond our control 14:27:02 i will discuss more later 14:27:15 next, 2023.2 release name voting open until 4 January 14:27:25 #link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031551.html 14:27:37 it's the "B" release 14:27:48 so get your vote in if you have a preference 14:27:58 next, zuul project to switch from tox to nox 14:28:09 #link https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-12-20.log.html#t2022-12-20T17:29:07 14:28:16 they will still support the tox role 14:28:25 so theoretically it should not impact tox users 14:28:37 but it could mean that we could switch to nox ourselves 14:28:41 phew 14:28:48 (though i am certainly not going to do that!) 14:29:15 and then last thing, reminder: CFP for the OpenInfra Summit Vancouver (June 13-15, 2023) ends 11 Jan 2023 at 07:59 UTC 14:29:49 #link https://cfp.openinfra.dev/app/vancouver-2023/19/presentations 14:30:05 clarkb has points regarding it's easier than tox but I've no idea about it, also tox is working fine (until they move to 4 tomorrow) 14:30:08 some employers won't send you unless you have a presentation accepted, so there's your chance 14:30:44 yeah, my worry is that they may stop full-heartedly supporting tox 14:30:56 so we may have to migrate eventually 14:31:09 but hopefully not until the K release 14:31:18 ok, that's all from me 14:31:47 lol, we've enough time until K 14:31:55 thanks rosmaita for the announcements/updates 14:32:06 anyone has anything else for announcements? 14:33:11 guess not 14:33:15 let's move to topics then 14:33:22 #topic tox 4 14:33:25 rosmaita, that's you again 14:33:29 ok 14:33:54 i've got patches up that we'll need to merge real soon 14:33:58 (like today) 14:34:08 #link https://review.opendev.org/q/topic:tox-4-ready 14:34:28 isn't that always the case? 14:34:44 the ones that don't have a +1 from zuul yet have passed all the jobs that use *our* tox.ini file 14:34:46 They all look pretty simple and logical to me 14:35:00 so hopefully tempest is ready with working tox.ini files 14:35:10 yeah, there is some weirdness 14:35:20 so what I did is make us use tox 4 14:35:32 so we are running tox 4 in the gate even if zuul isn't 14:35:49 because tox has the ability to update itself 14:36:06 anyway, i tested these the best i could locally 14:36:16 but you may have different experiences 14:36:22 depending on what your system python is 14:36:28 mine is 3.10 14:36:48 that's because some of our environments just ask to use "python3" 14:36:57 not that there's anything wrong with that 14:36:58 well I guess us vendors will see what happens when we move to 4 but it shouldn't be too much of a hardship 14:37:03 thanks rosmaita for all the changes, I think we still have an option to keep it to tox 3 even if they upgrade to v4 14:37:15 but we need to move some time so better now 14:37:52 anyway, my suggestion is to merge these, and if we get weird local problems, we can fix those later 14:38:16 sounds like a good plan 14:38:25 I will take a look but need another core to merge it 14:38:36 i can review as well 14:38:44 thanks! 14:38:48 great! 14:39:17 i tried to be specific in the commit message about what changes are made and why 14:39:28 but i won't pretend to completely understand the workings of tox 14:39:44 final point 14:39:53 i don't know what we're supposed to do about the stable branches 14:40:04 i will ask at the TC meeting later today 14:40:37 i thought this was a change only for master 14:40:59 yes, but there was some discussion that zuul should run tox 4 for everything 14:41:19 ok 14:41:54 yeah, i will get details later, hopefully we won't need to do that immediately 14:42:10 ok, sounds good 14:42:12 that's all from me 14:42:17 again thanks for all the work 14:42:26 cool, let's move to next topic then 14:42:34 #topic SVf bug fix review 14:42:41 #link https://review.opendev.org/c/openstack/cinder/+/853126 14:42:43 harsh, that's you 14:42:46 yes 14:42:58 i addressed the UT comments given by rosmiata 14:43:04 i remember reviewing it, maybe there were changes after that 14:43:12 yes 14:43:25 earlier code had a logical error in the loops 14:43:53 ok this is a different one 14:43:59 even if it fixed the issues, there was a redundency, 14:44:35 yea, you reviewed the feature for flashcopy, where you gave a +1 and said that once the IBM-CI passes then you will give a +2 14:44:46 https://review.opendev.org/c/openstack/cinder/+/852364 14:45:28 The review in the etherpad is regarding mkhost failure because of incorrect IP assignment in the storage_nodes dict. 14:46:09 as rosmiata asked to write a UT which will fail in the older code but will pass in the fixed code. so about 2 hours ago i pushed the UT. 14:46:49 requesting rosmiata and enriquetaso to please verify if all of their comments are now addressed. 14:46:56 harsh: thanks for updating the test, that's exactly what i was looking for 14:47:04 awesome. 14:48:49 once zuul is passed, please give +2's so that it can be merged as the RedHat customer is waiting on this. 14:49:27 thanks 14:49:53 thanks rosmaita 14:50:20 great, looks like we're covered on this then 14:50:47 I'll review again! 14:51:00 yes. also whoami-rajat if you could please address the flashcopy change it would be really great : https://review.opendev.org/c/openstack/cinder/+/852364 14:51:13 thanks enriquetaso :) 14:51:24 ack will take another look 14:51:31 thank you :) 14:51:43 np 14:51:52 anything else on this topic? 14:52:16 no thats all from my side. 14:52:24 great 14:52:34 so please review the changes 14:52:40 moving to next topic 14:52:43 #topic request core reviews of Pure driver patches 14:52:50 #link https://review.opendev.org/c/openstack/cinder/+/855060 14:52:57 #link https://review.opendev.org/c/openstack/cinder/+/862365 14:52:59 simondodsley, that's you 14:53:06 yep. still looking for those final elusive core reviews... 14:53:18 it would be a nice Xmas present to get those in... 14:54:05 that's all - you can move on to the next topic (after reveiwing of course...) 14:54:51 cool, reviewers please take a note of these patches ^ 14:55:02 ok final topic which also looks like a review request 14:55:10 #topic SVf bug fix review 14:55:15 #link https://review.opendev.org/c/openstack/cinder/+/848418 14:55:20 Mounika, that's you 14:55:22 yes 14:55:33 Got +2 from whoami-rajat on this patch. Requesting one more review for this patch to get merge. 14:56:25 it's a pretty straightforward patch, keeping extra info in their backend stats for replication 14:56:33 yes 14:57:05 again, reviewers please take a look at this one as well 14:57:30 I feel I should start keeping a review request section in meetings 14:57:57 yea that would be good i guess 14:58:36 ok, let's start it from next year 14:58:43 :) 14:58:44 which is in 2 weeks 14:58:48 ok 14:59:09 anyway, that's all the topics for today 15:00:03 and we're out of time as well 15:00:08 thanks everyone for attending 15:00:21 merry christmas and a happy new year 15:00:26 #endmeeting