14:00:37 #startmeeting cinder 14:00:37 Meeting started Wed Mar 2 14:00:37 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:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:37 The meeting name has been set to 'cinder' 14:00:44 #topic roll call 14:00:47 o/ 14:00:56 hi 14:00:56 Hi 14:01:00 hi 14:01:01 hi everyone 14:01:02 e0ne: !!!!! 14:01:06 hi 14:01:23 hi! 14:01:38 hi 14:01:53 hi 14:02:06 hello everyone, let's get started 14:02:08 #link https://etherpad.openstack.org/p/cinder-yoga-meetings 14:02:10 hi 14:02:15 #topic announcements 14:02:17 o/ 14:02:32 first: we are now in Yoga Feature Freeze 14:02:43 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027433.html 14:03:11 ohy 14:03:17 let's take a quick look at that email 14:03:53 you will see several Feature Freeze Exceptions 14:04:03 those are our review priorities 14:04:23 we especially need reviews on the "complete transition to Alembic" effort 14:04:52 for TusharTgite's "reset state robustification" effort, i believe that the base patch has merged 14:05:11 so we can concentrate on its children patches 14:05:27 for the driver features 14:05:33 #3 has merged 14:06:16 we need eyes on the hitachi stuff (#4 and #5 plus the parent patch https://review.opendev.org/c/openstack/cinder/+/827259/ ) 14:06:41 as far as the Questionable stuff goes 14:07:01 #3 applied for a FFE and it was granted 14:07:16 it's now passing third party CI, etc, so looks ready 14:07:23 #2 did not apply for an FFE 14:07:46 #1 is part of a community goal, so we will be doing something with that 14:07:56 probably a stripped-down version 14:08:22 anyway, my main concern is the alembic patches 14:08:30 so please take some time to look them over 14:08:54 next item: Yoga RC-1 is Thursday 10 March 14:09:31 that's when the stable/yoga branch will be cut, and after that only release-critical bugs can be included in Yoga 14:09:47 the final RC is scheduled for Thursday 24 MArch 14:10:21 after that, no changes are allowed into yoga unless the release team agrees (it will no longer be up to us) 14:10:42 after that, we have the Zed PTG 4-8 April 14:10:48 whoami-rajat is organizing it 14:10:56 as usual, please add topics to the etherpad 14:11:05 #link https://etherpad.opendev.org/p/zed-ptg-cinder-planning 14:11:28 i had a question: is there interest in a special driver maintainers' session? 14:11:34 as rosmaita said, please do ^ 14:11:57 we have a bunch of new driver contributors, and I'm not sure everyone understands our processes, what the deadlines are, etc 14:12:26 so, if you would be interested in such a session, please leave a note on the etherpad 14:12:39 also, we need input on videoconf software to use 14:12:49 we'll use bluejeans by default 14:13:03 so if you have a different suggestion, please communicate it to whoami-rajat 14:13:09 that would be a good idea, I've thoughts about emphasizing on the driver contribution documentation which surely some vendors missing while adding a new driver 14:13:39 i guess we could schedule something and then publicize on the ML 14:13:47 rosmaita: Nice to have new contributors. Been a long time since we have had to do an education session like that. :-) 14:13:48 ++ 14:13:57 though i learned earlier this week that some maintainers don't subscribe to openstack-discuss 14:14:01 :( 14:14:09 :( 14:14:14 although, at least one driver maintainer now does! 14:14:17 whoami-rajat: ++ We used to do something like that back when I was PTL and we had more new people. 14:14:42 zoom was a potential candidate but BlueJeans is more tried and tested with out past PTGs so that seems to be the best default choice 14:14:45 I would love that 14:14:54 educational session 14:14:58 ok, at least one vote! 14:15:21 ok that's all the announcements 14:15:32 very light agenda today 14:15:35 we intend to bring an overview of NetApp's CI for the ptg, goal would be to demonstrate software factory and advantages in its adoption.. 14:15:50 now that is something I would like to see! 14:16:01 would that be relevant for new maintaners? 14:16:18 i think yes, but also think it should be its own session 14:16:22 simon is here? 14:16:30 sfernand: That is awesome! 14:16:40 :) 14:16:50 yeah, i think simondodsley will be interested in that! 14:17:05 yes, me to 14:17:34 at one PTG we had a "drivers day", so maybe we can do that for Zed PTG 14:18:01 #topic  "artificially inflated requirements in os-brick" 14:18:13 just want to give a quick update since i brought this up last week 14:18:25 the tc discussed this last week 14:18:27 #link https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-24-15.00.log.html#l-132 14:18:43 there will be more discussion at the PTG ... the tl;dr is 14:19:05 the brick changes are fine, but i was asked to be more conservative with cinderclient (which i was) and cinder 14:19:45 but there's going to be some rethinking about what info exactly the requirements.txt file is meant to convey 14:20:08 possibly removing minimum versions altogether, and just relying on upper-constraints 14:20:21 but we can worry about that later 14:20:28 #topic PTG timings 14:20:31 whoami-rajat: that's you 14:20:39 hey 14:21:02 so I didn't receive any feedback on the timings so i guess everyone is fine with it 14:21:25 but again i didn't send out an ML (my bad) so I'm thinking will do that before confirming the timings as 1300-1700 UTC 14:21:39 that sounds good 14:21:59 again, if anyone has any concerns regarding timings, do let me know 14:22:16 we need to add a reminder to the "silence is assent" assumption when people are asked to look at things at meetings, or on the ML 14:22:28 also we can schedule the topic timing as per the author's TZ convenience (in the booked time slot) so it shouldn't be an issue 14:22:30 (for the new driver maintainers PTG session, i mean) 14:23:03 agreed 14:23:20 ok, great 14:23:24 that's all from my side 14:23:33 #topic Open Discussion 14:24:11 i want to say Hi to e0ne who's been off irc to conserve power 14:24:31 rosmaita: thanks Brian! 14:24:32 o/ 14:24:39 I'm still safe and alive 14:24:59 i don't know if everyone knows e0ne is physically located in Ukraine 14:25:22 so it is very nice to see him here today 14:25:25 Kharkiv, east of Ukraine :( 14:25:45 :-( You neighborhood has avoided bombing? 14:25:46 i have a question my base patch is merged but in related chain section all other patches shows (not current) and i rebased them already is a issue or a normal thing https://review.opendev.org/c/openstack/cinder/+/773985 14:25:56 e0ne: stay safe 14:26:05 yuval: will try, thanks 14:26:24 stay safe enriquetaso 14:26:37 oops, e0ne :P 14:27:19 e0ne: We are all keeping Ukraine in our thoughts and prayers here. Stay safe buddy. 14:27:31 jungleboyj ++ 14:27:49 Stay safe. Take care. 14:27:54 e0ne: glad you are safe!! 14:28:03 TusharTgite, rebase looks right from the dependency chain in this patch https://review.opendev.org/c/openstack/cinder/+/804735 14:28:07 e0ne: stay safe ,sry to interupt conversation in beetween. take care 14:28:46 e0ne, take care and stay safe 14:28:50 whoami-rajat: ok 14:28:52 TusharTgite, think looks fine and they share the same Topic 14:29:32 as long as the patches that need review aren't showing Merge Conflict, don't worry about it 14:29:46 tbh, i am not sure what you usually see on the parent patch after it merges 14:31:18 rosmaita: ok 14:32:03 ok, well if there's no more to discuss, we can end early 14:32:20 and use the free 1/2 hour to review the alembic completion patches! 14:32:58 e0ne: best wishes to you and your family, and hope you all stay safe 14:33:06 ++ 14:33:07 #endmeeting