14:00:02 #startmeeting glance 14:00:02 Meeting started Thu Feb 3 14:00:02 2022 UTC and is due to finish in 60 minutes. The chair is abhishekk. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:02 The meeting name has been set to 'glance' 14:00:05 #topic roll call 14:00:17 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:23 o/ 14:00:30 o/ 14:00:48 Lets wait couple of minutes for others 14:01:06 o/ 14:01:47 Small agenda, lets start and finish this early 14:01:58 ++ 14:02:00 #topic release/periodic jobs update 14:02:10 Milestone-3 3 weeks from now 14:02:23 Possible targets for M3 14:02:24 Cache API 14:02:24 Stores detail API 14:02:24 Unified limits usage API 14:02:24 Append existing metadef tags 14:03:05 We are good for non client release, nothing is pending from store side 14:03:17 Periodic jobs all green 14:03:58 #topic Review priorities this week 14:04:17 This week we have two feature reviews on priority list 14:04:32 cache api work 14:04:35 #link https://review.opendev.org/q/topic:bp%252Fcache-api 14:04:48 All patches are listed here 14:05:11 we also have a tempest coverage to verify that we can cache image on different glance node 14:05:26 2nd on priority list is 14:05:27 Unified limits usage API 14:05:43 #link https://review.opendev.org/q/topic:bp/glance-unified-quotas+status:open 14:05:54 Just two patches, one for API and one for client 14:06:07 Kindly put some time in reviewing above patches 14:06:20 That's all for today 14:06:26 #topic Open discussion 14:06:33 Glance db migration constant check 14:06:44 I have put a WIP patch to modify this check 14:06:51 #link https://review.opendev.org/c/openstack/glance/+/827587 14:07:03 kk I'll try to give another round on the cache 14:07:08 This will work if release version is less than current release 14:07:14 cool, thank you 14:07:40 and will pass if release name is equal to or next release 14:08:00 means it will work if version is xena, yoga or z 14:08:17 but will break if it is wallaby and less 14:08:36 Other than this I am not able to think of better way to tackle this 14:09:50 need to look into that unless rosmaita feels it still fulfils it's purpose ... kind of feels by your description that it's kind of not doing the check why that test was introduced 14:10:29 looking at your patch now 14:10:38 there is a readme file in tests/gate repo to explain what is it doing 14:11:00 * glance/tests/gate repo 14:11:09 rosmaita, thanks 14:12:08 jokke_, Before my change it was givng error if release is > or < x 14:13:13 yeah, the problem with this is that what happens is: test is passing fine, next release is cut (or SemVer patch is landed), test breaks, fix the code ... wait for next release 14:13:31 yeh, the whole point was to ensure it was correct for the migrations being recognized, 14:13:48 yeah 14:13:50 so the test doesn't break until the release is cut, but before the release happens, it will fail if we fix it early 14:13:58 rosmaita: yeah kind of just forcing us to do what we do now but cycle later? 14:14:10 ah 14:14:12 ok 14:14:56 so can we make the test pass on milestone release but break if the latest tag is anything else (like RC)? 14:14:59 also we need to find out how we should use this logic post 'z' 14:15:12 abhishekk: ++++++++++ 14:15:15 that way it will not block the gate on milestones but makes sure we do update it before final 14:16:13 I have hackish logic in mind :D 14:16:17 yeah, i think it only pays attention to the major version number 14:16:25 yes 14:16:51 jokke_: i think you are right, maybe only look for the b1 suffix or rc1 14:17:34 we'll have the same situation though that the test will only break after the release 14:17:48 yep 14:17:54 rosmaita: that's what I'm thinking ... that way we still need to do the change like before but we don't jam the gate right on first milestone tag 14:17:56 and if we wait for rc1, then we will definitely have an rc2 14:18:13 as it gets the version from pbr which updates when the tag hits the repo 14:18:51 well, we can force the version change with a patch that has a 'SemVer' tag in the commit message 14:19:01 without actually doing a release 14:19:27 it's still manual, we land the semver patch, then have to land the constant change patch 14:19:32 but we could do it at any time 14:19:47 i can't figure out how to do this simultaneously 14:20:06 yeah 14:20:13 smcginnis would be good to ask about this 14:20:15 I don't think you can as pbr looks what's merged in the repo 14:20:32 when he was release ptl, he put up the SemVer patches 14:20:40 i dont think Elod does that anymore 14:21:54 I am not able to see any patches recently doing it 14:22:17 i am trying to remember where i saw docs about this, it was recent, but i can't remember what i was looking for 14:23:25 Ok, I will also keep digging for it 14:23:35 anything else you guys have to put here? 14:23:49 not me 14:24:05 hang on 14:24:59 ack 14:25:49 https://review.opendev.org/c/openstack/glance/+/809404 14:27:30 ok 14:27:34 so ... looks like it didn't work 14:27:40 ooh yeah there was that ... the renos rendered weird too 14:28:35 in glance master i see: 14:28:35 [master] wha'ppen? python setup.py --version 14:28:35 23.1.0.dev40 14:28:46 and 23.x is the xena series 14:28:52 yes 14:30:04 same thing in cinder, python setup.py --version is giving me xena series (19.x) 14:30:49 because cinder also haven't tagged anything yet 14:31:10 right, but i think we had the Sem-Ver thing also 14:31:29 aah, got it 14:31:32 give me the action item to ask about this at the release team meeting tomorrow 14:31:40 it's 1400 utc 14:31:48 i don't mind going 14:32:02 if you do, please 14:32:19 because I will not be around tomorrow :( 14:32:37 np, i will also ask if they have a better idea for how to do this test 14:32:52 great, thank you 14:33:12 I think we should call it now 14:33:27 thank you rosmaita and jokke_ 14:33:39 sure np 14:33:47 thanks 14:33:49 have a good day all 14:33:49 have a nice weekend!! 14:34:01 #endmeeting