14:00:18 #startmeeting cinder 14:00:18 Meeting started Wed Mar 16 14:00:18 2022 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:18 The meeting name has been set to 'cinder' 14:00:28 o/ 14:00:29 hi 14:00:32 Hi 14:00:33 hi 14:00:40 yough 14:00:55 hi! o/ 14:01:19 hey 14:01:31 hello everyone 14:01:42 #link https://etherpad.opendev.org/p/cinder-yoga-meetings 14:02:24 o/ 14:02:28 light agenda today, so plenty of time for open discussion later 14:02:39 #topic announcements 14:02:49 Festival of XS Reviews on Friday, 1400-1600 UTC 14:03:11 you can find info about the festival here: http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews 14:03:15 o/ 14:03:21 which reminds me that i didn't send out a reminder yet 14:03:35 #action rosmaita festival of reviews reminder to ML 14:03:36 We've a national festival on friday (Holi) so won't be able to attend... 14:03:46 ok, that's a good excuse 14:04:05 (probably anyone from India won't be around on friday) 14:04:10 :) 14:04:12 rosmaita: I am not sure if I will be able to attend. My son has a college visit. 14:04:33 ok, that's also a good excuse, though not as good as Rajat's 14:04:37 :D 14:04:58 :-) 14:04:59 enriquetaso also won't be there 14:05:25 i have the time blocked off, so i am planning to be there 14:05:37 next item 14:05:45 final cinder RC must be released by Thursday next week 14:06:09 not much more to say about that, i think everyone knows what it means 14:06:23 RC-1 was released on Monday 14:06:37 (that's "cinder release candidate #1" 14:06:47 the stable/yoga branch has now been cut 14:06:56 bugfixes must merge to master and then be backported to stable/yoga 14:07:11 ++ 14:07:28 that's the case for everything (cinder, os-brick, cinderclient) other than cinderlib 14:07:39 cinderlib master remains yoga development until it has its yoga release at zed R-15 14:07:58 which reminds me, i could use some eyes on https://review.opendev.org/c/openstack/cinderlib/+/833781 14:08:06 so things we only want in Zed can now be put up in master, correct? 14:08:21 that is correct 14:08:27 cool 14:09:02 so at this point, only release-critical changes will be merged to stable/yoga 14:09:10 so let's take a quick look at what we have 14:09:19 #link https://etherpad.opendev.org/p/cinder-yoga-release-critical-changes 14:09:41 so, first the good news 14:09:54 the transition-to-alembic patches were all merged 14:10:23 I hope that works when upgrading a real deployment :) 14:10:23 we don't have any db migrations for yoga, but probably will soon 14:10:33 so, https://docs.openstack.org/cinder/latest/contributor/database-migrations.html 14:10:45 that explains how to use the new stuff 14:11:18 hemna: me too, i'll be putting up a patch very early in Zed to do a minor migration so we can make sure it works as expected 14:11:46 we have the advantage that nova is about 1.5 cycles ahead of us on this, and the bugs have been mostly shaken out 14:12:12 anyway, i want to thank stephenfin for working on this for cinder 14:12:20 we will declare Stephen Finucane a "Hero of Cinder" at the PTG 14:12:26 ++ 14:12:54 also there's a new grenade job that checks migration from tock -> tock (or it's tick->tick) but it checks skipping one intermediate release 14:12:57 as i mention on the etherpad, stephenfin has also posted a series of patches so that cinder will no longer use a deprecated oslo.db feature 14:13:12 we will aim to merge those into Z quickly after the final RC 14:13:23 ok, now the not-so-good news 14:13:57 there is still some work ongoing for known issues in Xena 14:14:15 the good thing is that i don't think any of them are destabilizing 14:14:25 they are fairly localized 14:14:37 so, we will consider them release-critical 14:15:13 other than that, if anyone finds a bug that looks like it needs to be addressed before release, please put it on the etherpad so we can be aware 14:15:22 and decide whether it really is release-critical or not 14:15:42 any questions? 14:17:10 ok, next item 14:17:21 Zed virtual PTG 4-8 April 14:17:30 #link https://etherpad.opendev.org/p/zed-ptg-cinder-planning 14:17:51 usual deal, you need to register even though it's free 14:18:04 whoami-rajat is doing the organization this time 14:18:19 o/ 14:18:28 if you look at the etherpad, there are a bunch of driver topics that i added 14:18:44 it's looking like maybe we'll have a drivers' day 14:19:02 ah, they weren't there the last time i checked 14:19:03 so if you are a driver maintainer, and have something we should discuss, please add it 14:19:12 looks like a drivers' day is needed 14:19:33 (it could also be called Brian's day) 14:19:41 btw, i will be happy to let anyone else who's interested take those over 14:20:17 the PTG is coming up fast, so please spend a bit of time thinking about it 14:20:23 driver's day++ 14:20:57 hemna: i didn't see your recomputing available space topic on there yet 14:21:36 Oooh, that sounds like an exciting one. 14:22:05 that doesn't necessarily have to be on drivers day, though i imagine there may be some reporting issues that it would be good to get input on 14:22:10 I won't be able to attend, but I'm going to add a topic for discussion if that is ok. 14:22:15 jungleboyj: was that a sarcastic comment? XD 14:22:29 simondodsley: nvme related? 14:22:38 simondodsley: that's fine 14:22:46 No ... I have a feeling that it will be somewhat contentious. :-) 14:22:55 though you'll need to get someone to agree to lead the discussion for you 14:22:59 jungleboyj: probably :-) 14:23:03 Might be interesting. 14:23:58 since we're not in a hurry today, i will pause to give people time to look at the etherpad and add comments 14:24:02 I'll add the topic and if someone want s to lead it that would be great, but if not it can be dropped for another session 14:24:12 #link https://etherpad.opendev.org/p/zed-ptg-cinder-planning 14:25:01 I'll probably add a couple of topics: Current nvme-of connector issues, drivers reporting their storage_protocol, quota update 14:25:49 geguileo: ++ 14:27:31 If you've added a topic and have a preferred time and won't be attending the whole PTG, you can add the time (UTC) suited for your TZ (only in the available time slot) 14:27:47 geguileo++ 14:29:18 simondodsley: are there leftovers on ALL successful runs or just some? 14:29:34 i'd have to check, but it feels like all 14:29:54 just a reminder about the PTG schedule for cinder: the Cinder team will meet in the 13:00-17:00 UTC blocks on Tuesday 5th April through Friday 8th April 2022. 14:31:15 wow, we do have a lot of topics for drivers' day! 14:31:19 simondodsley: that'd be the best case scenario, because going into the system we can tell the test that left it behind 14:31:37 ok, the etherpad is available 24 hours a day, so please add items as they occur to you 14:31:43 and the new field that tells us if it's a temporary resource may help as well 14:32:20 ok, final announcement 14:32:34 reminder about the cinder resource count survey 14:32:43 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027660.html 14:33:16 we are trying to get geguileo some data to determine what direction his quotas improvement plans should take 14:33:22 so please tell your customers 14:33:32 and if you run a cloud, please fill it out yourself! 14:33:48 please, pretty please 14:33:53 that's all from me, anyone else have an announcement? 14:34:10 actually, if sofia were here, she would remind us about outreachy 14:34:26 i believe the deadline for proposals is early next week 14:34:51 i think this email has details: 14:34:54 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027239.html 14:35:29 #topic reminder: no "naked" rechecks 14:35:59 Gorka added some documentation about this: 14:36:07 #link https://docs.openstack.org/cinder/latest/contributor/gerrit.html#ci-job-rechecks 14:36:24 the basic idea is that we want to do a bit of troubleshooting before rechecking 14:36:53 because a failure in any test that has 'volume' in the name is immediately ascribed to cinder, whether it's a cinder failure or not 14:37:53 i guess that's all i have to day about that 14:38:15 geguileo, found out a typo if you would like to fix "without locking at the errors" locking -> looking 14:38:51 * geguileo is the king of typos 14:38:53 that's a good typo given that geguileo is our race conditions expert 14:39:12 :D true 14:39:39 #topic open discussion 14:40:07 :-) 14:43:00 i have this cool patch that just removes a bunch of dead code, if someone wants an easy review: https://review.opendev.org/c/openstack/cinder/+/800704 14:43:28 eharney: that one has a couple of +2 already... 14:43:37 indeed 14:43:48 last week's meeting got it this far, maybe today's can really do it 14:44:51 eharney: i think you should feel free to +W it 14:45:09 or maybe jungleboyj will 14:45:20 eharney: why do we need this change? https://review.opendev.org/c/openstack/cinder/+/800704/3/cinder/volume/drivers/remotefs.py 14:45:30 looks like he and e0ne had a race condition, both thought they were putting the first +2 on it 14:45:38 rosmaita: I can. 14:45:43 ty 14:45:47 geguileo: good question 14:45:54 geguileo: i wrote this last summer, so lemme go find out... 14:46:08 I know how that feels 14:46:50 *sad trombone* 14:47:42 i wonder if that's a pylint thing 14:48:33 I can bring up an idea 14:48:43 eharney: looks like it's irrelevant, it's merging now XD 14:48:59 what about moving out unittest from using tox to use docker 14:49:07 our* 14:49:18 tox works pretty well 14:50:31 yuval: can you say some more about what you're thinking there? 14:50:37 my exp with tox - first was that its not working - every env I had to install it I had to debug certain bug, missing dependency libs 14:51:09 just a docker with the minimum req to run the unittests 14:52:09 zuul running py36 and py39 in my machine I am running py38 14:52:18 I would like to run exactly the same tests 14:52:41 docker solves that 14:53:10 is there someone here which is also active in kolla project? 14:53:20 geguileo, eharney i can see those variables not used anywhere so maybe signifying that those are unused (_ instead of __) 14:53:39 whoami-rajat: makes sense 14:53:41 whoami-rajat: that is the convention of what the leading underscore means, yes -- pylint etc. actually check based on this 14:53:42 thanks 14:54:19 np 14:54:24 ack 14:55:55 yuval: i use pyenv to give me multiple pythons beyond what's available in my operating system distro 14:56:12 don't know if that would help you 14:58:04 ok, two-minute warning ... anyone else have something to mention? 14:59:30 guess not ... thanks for attending, and don't forget about the festival of reviews on friday 14:59:48 #endmeeting