Thursday, 2022-02-03

*** hemna8 is now known as hemna07:37
*** dasm|off is now known as dasm|rover13:14
abhishekk#startmeeting glance14:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'glance'14:00
abhishekk#topic roll call14:00
abhishekk#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
abhishekko/14:00
rosmaitao/14:00
abhishekkLets wait couple of minutes for others14:00
jokke_o/14:01
abhishekkSmall agenda, lets start and finish this early14:01
jokke_++14:01
abhishekk#topic release/periodic jobs update14:02
abhishekkMilestone-3 3 weeks from now14:02
abhishekkPossible targets for M314:02
abhishekkCache API14:02
abhishekkStores detail API14:02
abhishekkUnified limits usage API14:02
abhishekkAppend existing metadef tags14:02
abhishekkWe are good for non client release, nothing is pending from store side 14:03
abhishekkPeriodic jobs all green14:03
abhishekk#topic Review priorities this week14:03
abhishekkThis week we have two feature reviews on priority list14:04
abhishekkcache api work14:04
abhishekk#link https://review.opendev.org/q/topic:bp%252Fcache-api14:04
abhishekkAll patches are listed here14:04
abhishekkwe also have a tempest coverage to verify that we can cache image on different glance node 14:05
abhishekk2nd on priority list is14:05
abhishekkUnified limits usage API14:05
abhishekk#link https://review.opendev.org/q/topic:bp/glance-unified-quotas+status:open14:05
abhishekkJust two patches, one for API and one for client14:05
abhishekkKindly put some time in reviewing above patches14:06
abhishekkThat's all for today14:06
abhishekk#topic Open discussion14:06
abhishekkGlance db migration constant check14:06
abhishekkI have put a WIP patch to modify this check14:06
abhishekk#link https://review.opendev.org/c/openstack/glance/+/82758714:06
jokke_kk I'll try to give another round on the cache14:07
abhishekkThis will work if release version is less than current release14:07
abhishekkcool, thank you14:07
abhishekkand will pass if release name is equal to or next release14:07
abhishekkmeans it will work if version is xena, yoga or z14:08
abhishekkbut will break if it is wallaby and less14:08
abhishekkOther than this I am not able to think of better way to tackle this14:08
jokke_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 introduced14:09
rosmaitalooking at your patch now14:10
abhishekkthere is a readme file in tests/gate repo to explain what is it doing14:10
abhishekk* glance/tests/gate repo14:11
abhishekkrosmaita, thanks14:11
abhishekkjokke_, Before my change it was givng error if release is > or < x14:12
rosmaitayeah, 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
jokke_yeh, the whole point was to ensure it was correct for the migrations being recognized, 14:13
abhishekkyeah14:13
rosmaitaso the test doesn't break until the release is cut, but before the release happens, it will fail if we fix it early14:13
jokke_rosmaita: yeah kind of just forcing us to do what we do now but cycle later?14:13
jokke_ah14:14
jokke_ok14:14
jokke_so can we make the test pass on milestone release but break if the latest tag is anything else (like RC)?14:14
abhishekkalso we need to find out how we should use this logic post 'z'14:14
rosmaitaabhishekk: ++++++++++14:15
jokke_that way it will not block the gate on milestones but makes sure we do update it before final14:15
abhishekkI have hackish logic in mind :D14:16
rosmaitayeah, i think it only pays attention to the major version number14:16
abhishekkyes14:16
rosmaitajokke_: i think you are right, maybe only look for the b1 suffix or rc114:16
rosmaitawe'll have the same situation though that the test will only break after the release14:17
abhishekkyep14:17
jokke_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 tag14:17
rosmaitaand if we wait for rc1, then we will definitely have an rc214:17
jokke_as it gets the version from pbr which updates when the tag hits the repo14:18
rosmaitawell, we can force the version change with a patch that has a 'SemVer' tag in the commit message14:18
rosmaitawithout actually doing a release14:19
rosmaitait's still manual, we land the semver patch, then have to land the constant change patch14:19
rosmaitabut we could do it at any time14:19
rosmaitai can't figure out how to do this simultaneously14:19
abhishekkyeah14:20
rosmaitasmcginnis would be good to ask about this14:20
jokke_I don't think you can as pbr looks what's merged in the repo14:20
rosmaitawhen he was release ptl, he put up the SemVer patches14:20
rosmaitai dont think Elod does that anymore14:20
abhishekkI am not able to see any patches recently doing it14:21
rosmaitai am trying to remember where i saw docs about this, it was recent, but i can't remember what i was looking for14:22
abhishekkOk, I will also keep digging for it14:23
abhishekkanything else you guys have to put here?14:23
jokke_not me14:23
rosmaitahang on14:24
abhishekkack14:24
rosmaitahttps://review.opendev.org/c/openstack/glance/+/80940414:25
abhishekkok14:27
rosmaitaso ... looks like it didn't work14:27
jokke_ooh yeah there was that ... the renos rendered weird too14:27
rosmaitain glance master i see: 14:28
rosmaita[master] wha'ppen? python setup.py --version14:28
rosmaita23.1.0.dev4014:28
rosmaitaand 23.x is the xena series14:28
abhishekkyes14:28
rosmaitasame thing in cinder,  python setup.py --version is giving me xena series (19.x)14:30
abhishekkbecause cinder also haven't tagged anything yet14:30
rosmaitaright, but i think we had the Sem-Ver thing also14:31
abhishekkaah, got it14:31
rosmaitagive me the action item to ask about this at the release team meeting tomorrow14:31
rosmaitait's 1400 utc14:31
rosmaitai don't mind going14:31
abhishekkif you do, please14:32
abhishekkbecause I will not be around tomorrow :(14:32
rosmaitanp, i will also ask if they have a better idea for how to do this test14:32
abhishekkgreat, thank you14:32
abhishekkI think we should call it now14:33
abhishekkthank you rosmaita and jokke_ 14:33
jokke_sure np14:33
jokke_thanks14:33
rosmaitahave a good day all14:33
abhishekkhave a nice weekend!!14:33
abhishekk#endmeeting14:34
opendevmeetMeeting ended Thu Feb  3 14:34:01 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:34
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2022/glance.2022-02-03-14.00.html14:34
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2022/glance.2022-02-03-14.00.txt14:34
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2022/glance.2022-02-03-14.00.log.html14:34
*** dasm|rover is now known as dasm|off22:02

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!