14:00:01 #startmeeting cinder 14:00:01 Meeting started Wed Nov 2 14:00:01 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:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'cinder' 14:00:03 #topic roll call 14:00:08 hi 14:00:21 o/ 14:00:33 o/ 14:00:47 hi 14:00:51 hi 14:01:02 hello 14:01:48 hi 14:02:11 #link https://etherpad.opendev.org/p/cinder-antelope-meetings 14:03:28 Welcome everyone back after the PTG 14:03:44 it was a good week of useful discussions 14:03:52 and that is related to my first announcement 14:03:56 #topic announcements 14:04:05 PTG Summary 14:04:14 #link https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031049.html 14:04:21 #link https://wiki.openstack.org/wiki/CinderAntelopePTGSummary 14:04:39 I've created a summary of all the topics we've discussed with links to the etherpad and recordings 14:05:03 to all the people who couldn't make it to the PTG, they can watch the sessions they're interested in 14:05:35 (since i don't expect anyone watching 16 hours of video meeting) 14:05:56 moving on 14:05:58 Did I get all the recordings posted? 14:05:59 next, Antelope schedule 14:06:10 jungleboyj, yes, as far as i checked 14:06:18 jungleboyj, thank you for uploading them! 14:06:29 Ok. Good. Just wanted to make sure I was caught up. 14:07:10 I calculated the total time of all the parts of a particular day and they added up to 3-4 hours so it looks good 14:07:25 Great! 14:07:43 ok moving on then 14:07:44 next, Antelope schedule 14:07:51 #link https://review.opendev.org/c/openstack/releases/+/862815 14:07:58 #link https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_8dd/862815/1/check/openstack-tox-docs/8ddc61d/docs/antelope/schedule.html 14:08:24 please check the second link above ^ it contains the cinder specific cycle schedule of antelope 14:08:42 the idea is to check for dates of deadlines and see if it has any conflicts 14:08:59 I've moved some deadlines since they overlap with the year end break 14:09:19 but more eyes on it would be useful 14:09:37 look in the "Project-specific events" column 14:12:11 One thing I see is that the Mid Cycle is the week after Thanksgiving. Not sure if anyone is planning to be out the week after ... 14:12:18 midcycle-1 date looks good, but midcycle-2 may be a holiday in Brazil ... i think most of our netapp people are there? 14:12:37 rosmaita: ++ 14:13:14 ack, this cycle is short so we've only so much weeks spare that the deadlines don't overlap 14:13:26 but good feedback, maybe we can move it one week before or after 14:13:58 Looking at things I think the Mid-Cycle 1 is probably best where it is before we get into December. 14:14:12 i will remove midcycle 2 from my current review and we can decide later on the date 14:14:34 jungleboyj, yep, tried to keep it before the year end holidays 14:15:02 ++ and most people do vacation before Thanksgiving if they are going to take extra time off. 14:15:06 and it will be a good checkpoint for spec reviews and status 14:15:35 ack, good feedback, will keep in mind 14:16:05 if you remember some more conflicts later, please leave a comment on my proposed patch 14:16:06 #link https://review.opendev.org/c/openstack/releases/+/862815 14:17:49 guess we can move on with the final announcement 14:18:00 Wallaby moving to EM 14:18:23 there is a patch proposed in releases project to move wallaby into EM 14:18:25 #link https://review.opendev.org/c/openstack/releases/+/862313 14:18:30 actually there is a patch for every project 14:19:04 since Jon had a patch to release wallaby, it seemed like a good idea to get that one done first before moving into EM 14:19:10 #link https://review.opendev.org/c/openstack/releases/+/848842 14:19:27 so this will be the final wallaby release and after that we wallaby will be moved to EM 14:20:24 that's all the announcements from my side 14:20:27 anyone has anything else? 14:21:34 guess not, so we can move to the next segment 14:21:39 #topic PTG Follow-up 14:21:47 rosmaita, i think you added it? 14:22:17 yeah, just wanted to say i did send in the revised user survey questions 14:22:39 the other thing is the 'service' role 14:22:59 the policy-pop-up team wants to get it implemented by M-1 14:23:02 yep, thanks for following up on that and mentioning it in the etherpad, I've added that in the PTG summary as well - DONE 14:23:04 which is coming up fast 14:23:33 the spec hasn't been approved yet, so if you have any interest, might be worth leaving a +1 to help push it along 14:23:41 #link https://review.opendev.org/c/openstack/keystone-specs/+/818616 14:24:12 abhishek from the glance team has volunteered to implement it 14:24:24 so it's really a matter at this point to get the spec approved 14:24:51 rosmaita, the assignee is still mentioned as lbragstad, would be good if Abhishek takes a look and revises it 14:25:07 good point 14:25:29 i'll mention it on the glance agenda for tomorrow 14:25:43 ack 14:25:44 i think reviewing the spec would be good to understand more about how/where to use it, I will take a look 14:27:12 that's all from me 14:27:29 great, thanks for bringing it up 14:27:36 moving on to next topic 14:27:42 #topic Outreachy update 14:27:53 is Sofia around? 14:28:19 i think not 14:28:23 can't find her with nick 14:28:24 ok 14:28:46 Since I'm co-mentoring with her, i can take this topic 14:29:13 this friday is the deadline for proposing the first patch and then an outreachy candidate can be considered for internship 14:29:29 we haven't seen much contribution but one contributor has been actively working on a patch 14:29:43 and it is related to our outreachy intern project as well 14:29:51 so would be good to keep some eyes on 14:29:53 #link https://review.opendev.org/c/openstack/cinder/+/861491 14:31:20 i think that's all she wanted to mention 14:31:28 let's move to the next topic 14:31:30 #topic EOL-ing older stable branches 14:31:34 rosmaita, that's you again 14:31:58 yeah, there has been some discussion on the ML 14:32:10 the release team wants to EOL Queens across all projects 14:32:33 nova and ironic (and maybe neutron?) want to EOL rocky and stein as well 14:32:53 so i was wondering if we would want to also EOL rocky and stein 14:33:16 so to be clear about what this means 14:33:36 each branch will be tagged with an -eol tag, and then the stable branch will be deleted 14:33:46 so no one can propose changes to it 14:33:58 but, if someone needs it for some reason, they can check out the git tag 14:34:39 the reason for us to stay in sync with nova is that if we run into problems in stable/rocky or stable/stein tempest tests, they won't be fixing anything 14:34:54 so we might have to EOL at that point, anyway 14:35:04 this way, we just get the branches out of our lives right now 14:35:22 ... and i will shut up and see if anyone wants to say anything 14:35:53 I think I'm OK with this change since i don't even see people proposing backports after train 14:36:10 even maintaining CI on these branches is extra burden for us 14:36:45 yeah, there hasn't been much action on those branches at all recently 14:38:08 train is the last branch that supports python 2.7 iirc, so if there's some kind of security fix needed, it would be py27 compatible, and people could backport it themselves from train to whatever locally 14:38:23 maybe Jon would have some feedback since he's our release maintainer but not sure 14:38:25 I support doing this. :-) 14:38:51 anyway, I'm in favor of it 14:39:07 (just checked, i am correct about py27 on train: https://governance.openstack.org/tc/reference/runtimes/train.html ) 14:39:52 rosmaita: If i may ask. From a third party cinder CI maintainer perspective. What would be the impact? I don't suspect any but thought I'd ask. 14:41:06 well, we don't require third-party CI on the stable branches, just a statement on any backport patches that you have tested it on the stable branch and it's ok 14:41:25 so i don't think there's much impact for CI 14:41:29 Sounds good. 14:42:07 but if you have customers on any of those old releases, you'll have to fix them privately 14:42:32 because there won't be an upstream branch to merge the changes to 14:42:57 whoami-rajat: maybe ask jon to send something to the ML and see if there are any objections? 14:43:05 he can use the nova email as a model 14:43:12 Understood. In such cases, we have a strong case to get them to upgrade. 14:43:21 abdi: exactly! 14:43:28 ++ 14:43:34 rosmaita, sure, will do 14:44:09 sounds like all of us here are in favor 14:44:43 +1 14:45:03 No concerns from me. Most of the people I have heard of are on Train as the oldest release. 14:47:10 rosmaita, anything else on this? 14:47:19 nothing from me 14:47:32 cool, let's move to the next few topics there 14:47:35 (sorry, sort of left you hanging there) 14:47:39 there are a bunch of review requests 14:47:42 oh no problem 14:47:55 #topic request for review of https://review.opendev.org/c/openstack/cinder/+/812685 14:48:09 ganso, anything you would like to say about it apart from requesting reviews? 14:48:17 I've reviewed it btw 14:48:23 whoami-rajat: no, not really 14:48:30 just that we've been waiting for this fix for a while 14:48:36 I see no reason to delay it further 14:48:46 it would be nice to have some attention 14:49:06 yeah, glance is kind of moving towards multi store and we will start seeing these failures more often 14:49:11 if there is anything pending, please post to the gerrit patch, like test-coverage, improvements,e tc 14:49:52 rosmaita, maybe you could take a look from glance perpspective? ^ 14:49:57 perspective 14:50:00 whoami-rajat: thanks for reviewing =) 14:50:01 ganso: i will review today 14:50:16 great, thanks ganso and rosmaita 14:50:22 i think i did the nova patch it's based on 14:50:41 then this would be familiar code changes, there are a bunch of things i don't understand 14:50:48 would be good to get some clarity on them 14:51:02 ok 14:51:34 cool, moving on to the next review request 14:51:41 #topic Request for review of https://review.opendev.org/c/openstack/cinder/+/815582 14:51:54 abdi, i see it's introducing a new HPE driver, anything you would like to say about it? 14:51:55 This one is mine. 14:51:59 Yes. 14:52:13 cool, stage is yours 14:53:01 The iSCSI tests consistently run into 2 volume swap test failures. We believe to have root caused it to a potential race condition between os-brick and nova. 14:53:14 So, I'd like to get a review and acceptance of the driver. 14:54:10 The bug in question #link https://bugs.launchpad.net/tempest/+bug/1989232. 14:54:49 ack, we target all drivers for M2, would be a good discussion topic for midcycle 1 as well 14:55:43 Ok. I'd love to get an early accept on this so I don't worry about it making it into the next release. 14:56:26 yes, will try to do that 14:56:35 abdi, anything else on this? 14:56:49 rosmaita: There are a few comments on the patch it would be good for you to resolve after you've reviewed my comments. 14:57:25 Other than that. Nothing else from me. 14:57:37 I'll monitor the patch for your acceptance. Thanks. 14:57:54 ack, great 14:57:56 let's quickly go over the last review request 14:58:05 #topic Request for review of https://review.opendev.org/c/openstack/cinder/+/849143 14:58:08 aneeeshp1, that's you 14:58:12 abdi: ack 14:58:15 Hi all 14:58:28 Yes. i have addressed the comments received 14:58:29 rosmaita: Thx. 14:58:35 Thank you for reviewing 14:58:49 Ci setup is now running and the driver passed tempest 14:59:04 I would like to request further review on the patch 14:59:31 i remember there were CI issues due to which it couldn't get into Zed, good to know things are good now 14:59:37 Just to get it reviewed earlier to avoid missing the next release 14:59:54 whoami-rajat yes the CI is up now 15:00:35 Nothing else from me other than this request 15:00:42 aneeeshp1, great, I will review and keep an eye on it 15:00:48 and we're out of time 15:00:53 whoami-rajat thank you 15:00:54 thanks everyone for joining! 15:00:57 #endmeeting