14:00:06 #startmeeting cinder 14:00:06 Meeting started Wed May 5 14:00:06 2021 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:09 The meeting name has been set to 'cinder' 14:00:14 #topic roll call 14:00:34 hi 14:00:41 hi (around a bit, I may have to drop) 14:01:11 Hi 14:02:00 Hello. 14:02:08 hello everyone 14:02:21 #link https://etherpad.opendev.org/p/cinder-xena-meetings 14:02:27 hi 14:02:32 #topic announcements 14:03:00 i posted a summary of our discussions at the PTG 14:03:04 #link https://wiki.openstack.org/wiki/CinderXenaPTGSummary 14:03:21 👍 14:03:22 you should take a look at your discussion and check it for accuracy 14:03:33 hi 14:03:34 it's a wiki, so you should be able to make correctinos 14:03:54 (that's a typo, i'm not trying to be cute) 14:04:00 :P 14:04:08 LOL 14:04:21 i was a bit consistent about using irc nicks and real first names throughout the doc 14:04:40 one thing i do want to point out are the cycle priorities 14:04:50 #link https://wiki.openstack.org/wiki/CinderXenaPTGSummary#Xena_Cycle_Priorities 14:05:21 there are some priorities addressing stability that don't really have a deadline 14:05:34 and those tend to get lost 14:05:47 but they can be done in small pieces 14:06:18 what i'd like you to do is to use the gerrit topic listed so we can keep visibility on them 14:06:30 that is, so you can get quick review of your patches 14:07:21 that's all from me, anyone else have an announcement? 14:08:21 guess not 14:08:30 #topic midcycle meeting times 14:08:56 last week i asked you to check on whether the dates are ok 14:09:05 i haven't heard anything 14:09:20 Oops. :-( 14:09:25 so i am assuming that wednesday 2 june and wednesday 4 august are unobjectionable? 14:09:26 sorry about that.. 14:09:53 well, it won't hurt to wait one more week to schedule these 14:09:56 so 14:10:01 At the usual cinder meeting time plus an hour? 14:10:07 the timing and dates work for me 14:10:10 or minus an hour 14:10:19 rosmaita: was there a poll for this? 14:10:32 no we were going to vote in the meeting 14:10:36 Yeah. That is as good a time as any for me. 14:10:42 that is, this meeting 14:11:00 ok cool 14:11:55 so, to summarize, the midcycle will be on a wednesday and will overlap with the normal cinder meeting time 14:12:22 so the only question is whether people are planning to be on vacation those weeks, or if there is a major opensource/python event those weeks 14:12:33 i don't know of any major events 14:13:22 so my question right now is, are people ready to vote to pick the times for those days? 14:13:39 maybe we need to vote on that! 14:14:13 Are you ready to vote on the time for the midcycles today? 14:14:20 #startvote yes, no 14:14:21 Unable to parse vote topic and options. 14:14:26 :D 14:15:05 #startvote Are you ready to vote on the time for the midcycles today? yes, no 14:15:06 Begin voting on: Are you ready to vote on the time for the midcycles today? Valid vote options are yes, no. 14:15:07 Vote using '#vote OPTION'. Only your last vote counts. 14:15:16 #vote yes 14:15:17 #vote yes 14:15:19 #vote yes 14:15:22 #vote maybe 14:15:23 eharney: maybe is not a valid option. Valid options are yes, no. 14:15:26 #vote yes 14:15:32 #vote yes 14:15:41 #vote yes 14:16:33 i thought i was committed to democracy, so it's kind of disconcerting to see that i don't know how to use the voting feature of the meetbot 14:16:52 #fail 14:16:56 ;-) 14:17:25 that seems to be everyone, will close the vote in 20 seconds 14:17:53 #endvote 14:17:54 Voted on "Are you ready to vote on the time for the midcycles today?" Results are 14:17:55 yes (6): enriquetaso, walshh_, whoami-rajat, jungleboyj, rosmaita, eharney 14:18:03 ok, guess we are ready 14:18:40 the R-18 midcycle will be held on Wednesday 2 June 2021 14:18:40 we need to pick a time 14:18:40 options are: 14:18:40 A 1300-1500 UTC 14:18:40 B 1400-1600 UTC 14:18:41 C need more options 14:18:47 #startvote time for the 2 June midcycle? A, B, C 14:18:48 Begin voting on: time for the 2 June midcycle? Valid vote options are A, B, C. 14:18:49 Vote using '#vote OPTION'. Only your last vote counts. 14:19:22 #vote B 14:19:33 #vote A, B 14:19:34 whoami-rajat: A, B is not a valid option. Valid options are A, B, C. 14:19:44 #vote B 14:19:48 #vote A 14:19:48 #vote B 14:19:54 #vote B 14:20:03 #vote B 14:21:29 i think that's everyone ... will wait 20 sec 14:21:57 (I always vote "it will conflict with something anyway") 14:22:06 #endvote 14:22:07 Voted on "time for the 2 June midcycle?" Results are 14:22:08 A (1): whoami-rajat 14:22:09 B (5): jungleboyj, enriquetaso, eharney, rosmaita, walshh_ 14:22:22 ok 1400-1600 it is 14:22:29 next one 14:22:46 the R-9 midcycle will be held on Wednesday 4 August 2021 14:22:46 let's pick a time 14:22:46 options are: 14:22:46 A 1300-1500 UTC 14:22:46 B 1400-1600 UTC 14:22:47 C either one of the above 14:22:47 D need more options 14:22:55 #startvote time for the 4 August midcycle? A, B, C, D 14:22:56 Begin voting on: time for the 4 August midcycle? Valid vote options are A, B, C, D. 14:22:57 Vote using '#vote OPTION'. Only your last vote counts. 14:23:13 #vote C 14:23:20 #vote C 14:23:23 #vote C 14:23:27 #vote B 14:23:32 #vote C 14:23:42 #vote C 14:23:47 #vote C 14:24:27 i think that's everyone .... will close the vote in 20 sec 14:25:07 #endvote 14:25:08 Voted on "time for the 4 August midcycle?" Results are 14:25:09 C (6): tosky, eharney, walshh_, whoami-rajat, rosmaita, enriquetaso 14:25:10 B (1): jungleboyj 14:25:23 OK, that makes 1400-1600 the winner 14:25:55 ok, thanks everyone, i will send out an email for the benefit of people who weren't here 14:26:10 #action rosmaita announce midcycle date/times 14:26:26 #topic final train release status 14:26:39 whoami-rajat: you have the floor 14:26:48 #link https://etherpad.opendev.org/p/train-final-release 14:27:18 So rosmaita updated the tracker with patches to be included in final train release (thanks!) 14:27:30 We currently only have open patches in cinder train 14:27:38 os-brick patches merged 14:28:07 and other branch doesn't have new patches, we did a release recently so no need to release them this time 14:28:24 someone (tosky?) put a question about the stabilization fix 14:28:39 that is, backport https://review.opendev.org/c/openstack/cinder/+/785970 to train 14:28:52 we should do that, i'll propose it 14:29:04 rosmaita: there's one patch from SVF failing because of other patch dependency, I've backported the other one so we can review it and fix the gate on first one? 14:29:08 i have no objection 14:29:33 sounds good 14:29:36 whoami-rajat: sure, i was hoping that the SVF team would do it 14:29:51 my "no objection" was in response to eharney 14:30:15 rosmaita: they haven't responded to my comment since a long time so i wasn't sure they're going to do it 14:30:17 that was me, yes, thanks 14:30:27 whoami-rajat: i agree about your proposal, though, it is probably better to have both fixes together 14:31:01 do we have any contact for that team? Maybe a direct email? 14:31:26 well, they are usually making pests of themselves asking for reviews :P 14:31:41 rosmaita: i didn't understand, the second one needs to be merged to pass gate on first one? then we can merge first one 14:31:43 so i'm kind of surprised that they've gone silent 14:32:11 whoami-rajat: i meant it is better to have both those fixes in train 14:32:26 rosmaita: yes, agree 14:33:01 so what you said .... we merge the patch you just proposed first, which will allow us to rebase the current failing patch 14:33:16 yes 14:33:34 atleast that's what we did in other branches 14:34:07 IMO we should also get https://review.opendev.org/c/openstack/cinder/+/783204 in which is currently languishing on stable/ussuri review 14:34:49 eharney: ++ Have a few things languishing. 14:35:21 can anyone propose the backports (or i can do) and we can add them to the etherpad 14:35:29 i'll propose that one 14:35:39 ok thanks 14:36:05 ok, i just approved https://review.opendev.org/c/openstack/cinder/+/783204 14:36:38 i think it makes sense to get it into train, too 14:37:17 anything else anyone is aware of? 14:37:33 that's all from me 14:38:28 ok, thanks 14:38:35 tosky: are you available now? 14:39:09 should we backport to train this https://review.opendev.org/c/openstack/cinder/+/785223 too? 14:39:53 rosmaita: zep 14:40:13 enriquetaso: we could, but i don't know that it's too crucial since it seems to mostly only hit CI jobs and not users 14:40:22 just moved you up in the agenda 14:40:30 sure, thanks 14:41:03 eharney: but we've faced consistent lvm-lio job failures on train gate before 14:41:34 whoami-rajat: iirc that fix is for the LVM version in focal, which is only supported in victoria and newer releases 14:41:48 will there still be lvm-lio train jobs..? 14:42:05 until we support train, yes (but based on bionic) 14:42:23 ++ 14:42:26 stein, train and ussuri (maybe also rocky, don't remember) are bionic 14:42:51 ok, well, i'm not opposed to backporting it, for sure 14:43:03 ok, we can always backport it later if necessary, doesn't really affect the release 14:43:25 (unless we're seeing gate failures that prevent other stuff from merging) 14:43:52 #topic some gate-related issues 14:44:05 very quick, two fixes for jobs: 14:44:14 #link https://review.opendev.org/c/openstack/cinder/+/789717 14:44:24 i think that one looks fine 14:44:53 #link https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/786755 14:45:08 i wasn't sure where to see this one is affecting stein? 14:45:43 iirc because we haven't submitted new stein patch recently 14:46:35 I've noticed while working on https://review.opendev.org/c/openstack/os-brick/+/786737 (which is worth considering too, low prio as it's stein) 14:47:00 the first revision of the patch failed because of that; the current revision works because it depends on the cinder-tempest-plugin fix 14:47:53 ok, i was looking at a brick patch, not cinder 14:48:15 all stable cores: give ^^ some attention 14:48:21 thanks, Luigi 14:48:35 #topic interop guidelines review 14:48:47 hopefully we can get through this really quick 14:49:08 this is what we are talking about: 14:49:10 #link https://wiki.openstack.org/wiki/CinderXenaPTGSummary#The_Interoperability_Working_Group 14:49:24 "Cinder team: will review mv changes between 3.0 and 3.64 to see if any "advisory" tests should be added" 14:49:40 just so you know where to look 14:49:48 this is the next set of capabilities: 14:50:02 #link https://opendev.org/osf/interop/src/branch/master/next.json#L151-L163 14:50:04 rosmaita: IIRC these are only related to third party CI ? 14:50:23 no, kind of a separate issue 14:50:50 this is the specification of what we think must be included for a cloud to be running OpenStack 14:50:55 whoami-rajat: guidelines/testing for interoperability of (vendored) openstack implementation 14:51:20 we also get indirectly included in this nova capability: 14:51:25 ok 14:51:29 #link https://opendev.org/osf/interop/src/branch/master/next.json#L133 14:51:55 and here's where you can see what that capability "means", in terms of what tempest tests it matches to: 14:52:04 #link https://opendev.org/osf/interop/src/branch/master/next.json#L1103-L1130 14:52:33 the volumes-* capability definitions start here (and go on and on): 14:52:41 i'm curious to know what tests exist for "volumes-v3-readonly" 14:52:44 #link https://opendev.org/osf/interop/src/branch/master/next.json#L2378 14:53:25 ah, https://opendev.org/osf/interop/src/branch/master/next.json#L2830 14:53:35 yeah that test doesn't validate that readonly actually works 14:54:00 yeah, these will only be API tests 14:54:23 by the way, that stuff you can't read in the description of all these tests says: 14:54:32 "This is being added as advisory to highlight the transitition from v2 to v3." 14:54:49 i will put up a patch to remove that sentence 14:55:09 #action rosmaita interop patch removing transition v2->v3 language 14:55:21 ok, so i looked over our microversions 14:55:30 #link https://docs.openstack.org/cinder/latest/contributor/api_microversion_history.html 14:55:39 i only found two candidates 14:55:48 well, actually 3 14:55:58 mv 3.3, User Messages 14:56:12 i forgot to check whether there are existing tempest tests for ^^ 14:56:21 because if they aren't we will need to write them 14:56:43 the second is mv 5.55, 3.57, "New Transfer API" 14:56:48 i don't recall any user message tests existing 14:56:51 from the quick find, i can't find anything saying message there 14:56:55 use /volume-transfers instead of /os-volume-transfer in the URL 14:57:32 i started looking into this one, but got lost in the tempest clients and couldn't figure out whether they are using the os- version or not when making the calls 14:57:41 because transfers actually are tested 14:58:19 the tests can set the specific microversion used by the tempest client (if that's the question) 14:58:36 a quick grep says that tempest is probably only testing the old one 14:58:46 ok, thanks 14:58:59 so if we care about this, we can update the tempest tests first 14:59:07 probably worth doing anyway? 14:59:11 yes 14:59:52 so this is only an issue if we intend on removing the os-volume-transfer urls 15:00:00 rosmaita: what about default volume types? (I'm trying to write tests for it but lacking the endpoint support for the unique url) 15:00:35 well, i don't know if we want to require that people make those accessible to end users 15:00:41 actually , i guess we don't 15:01:10 ok, we are out of time, i will pick this up next week 15:01:19 thanks! 15:01:26 sorry about no open discussion, we spent all our time voting 15:01:47 #endmeeting