Thursday, 2026-10-22

croelandt#startmeeting glance14:01
opendevmeetMeeting started Thu Oct 22 14:01:18 2026 UTC and is due to finish in 60 minutes.  The chair is croelandt. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'glance'14:01
croelandt#topic roll call14:01
croelandt#link https://etherpad.opendev.org/p/glance-team-meeting-agenda14:01
croelandtabhishekk: ?14:03
croelandtpdeore_: ?14:03
abhishekko/14:03
pdeore_o/14:03
abhishekksorry was busy in other stuff14:04
croelandtnp np14:04
croelandtshort agenda today but we've been in meeting all week last week so it's fine :)14:05
croelandt#topic Release/periodic job updates14:05
croelandt#link https://zuul.opendev.org/t/openstack/builds?project=openstack%2Fglance&project=openstack%2Fglance_store&project=openstack%2Fpython-glanceclient&pipeline=periodic14:05
croelandtit's all good except for FIPS14:05
croelandtand FIPS job has been abandonned a loooooong time ago14:05
croelandteveryone ok with me removing it?14:05
abhishekksounds good14:05
pdeore_+114:05
croelandt#topic stable patches14:06
croelandt#link https://review.opendev.org/c/openstack/glance/+/996357 seems important14:06
croelandtI have not had time to take a second look at it but it appears to fix a perforamnce issue in 2026.114:06
croelandtI'll review it and ideally someone else would do it too :14:07
croelandt:)14:07
abhishekkack, as per our stable policy you can Ninja it if it looks all ok14:07
croelandtyeah but I'd like a second pair of eyes because it has the potential to break stuff, I think :)14:07
croelandtbut anyway, regarding specs, abhishekk you have the mic14:08
abhishekkYes, all those need reviews14:08
abhishekkThe upload format is simple and easy to get in 14:08
abhishekkRegarding s3 work we need to prioritise it as our Nova work is depends on that14:09
croelandtso do we call it multipart or multistream?14:09
croelandtI feel something else was multipart 14:09
abhishekkyes multistream 14:09
abhishekkbut we have glance temp url  as well14:10
abhishekkthe important stuff I want to talk about is Tasks API removal14:10
croelandtok14:11
abhishekkI have sent mail as discussed14:11
abhishekk https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/GVSCNKJ37HDEQVNDLVYKN7KATAU4D4CP/14:11
abhishekkI got reply that we need to follow API-SIG guideline and instead of increasing minor version we should opt for /v314:11
croelandthow much do we hate that?14:12
croelandtI mean, when you think about it, removing an API, that is a big hcange14:12
croelandtso this might be a major one14:12
abhishekkI think this is going to be a major work which needs lots of cross project dicssions14:12
abhishekkI still remember we needed 2-3 years of discussion for planning for /v214:12
abhishekkYes this is going to be major headache14:13
croelandtDO we have consumers for that API? We should not, but...14:13
mklejnwasn't glance /v3 api already existing somewhere in the past, which got later separated into Glare?14:14
abhishekkI am not sure anyone is using that API14:14
abhishekkyeah that was ages ago14:15
abhishekkI think glare is also now history?14:15
croelandtyeah glare is history14:16
croelandthave we ever removed an API before?14:16
abhishekkSo if we have weekly meetings for TC then I think @croelandt you need to take this matter there and fight for us to save us from /v3 war14:16
abhishekkI think no14:16
croelandthm14:16
croelandtso what is the actual issue with v3? Consumers would have to update their code to call v3 instead of v2?14:16
mklejnalso, regarding 'temp url' -- ongoing, my draft is under internal review in attempt to catch anything stupid14:16
abhishekkyes14:17
croelandtyou'd figure it's not that hard :p14:17
croelandtbut it would mean some kind of transition period14:17
abhishekkexaclty, we need to bring all the consumers onboard 1st with this effort14:18
abhishekkmklejn: ack, we will discuss more if needed in open discussion for the same14:18
croelandtso maybe we should figure out who the consumers are, first14:18
croelandtI think the SDK is there14:19
abhishekkTempest, Ironic, Nova, Cinder14:19
abhishekkSupport in python-glanceclient as well14:20
croelandtglanceclient we control :)14:20
abhishekkyep14:20
croelandtmaybe we should discuss with Dan & Brian?14:20
croelandtto figure out how hard it would be to switch to v3 in their projects14:20
abhishekkI can prepare a plan for v3 migration if required and we can discuss next week again14:20
croelandtI think Artem made sense 14:21
croelandt(unfortunately for us)14:21
croelandtand while it's true others are breaking the API versioning contract...14:21
abhishekkwhen probably dansmith and rosmaita around?14:22
croelandta bit later than this :)14:22
abhishekkSo either move to v3 or keep deprecated tasks API forever until we are ready to move to v314:23
rosmaitai think we should only do a v3 if we rewrite glance in rust14:23
dansmith@omg please don't rev the api to remove an unused thing14:23
croelandtso we don't remove it, but is it disabled by default?14:24
dansmithno, we remove it14:24
abhishekkhow?14:25
dansmith"every OpenStack service violated this X times"14:25
abhishekk:D14:25
croelandthm14:25
croelandtnot a bad point either :)14:25
dansmithand also, I bet the SDK doesn't even have support for this, so he's just making a point with no reasoning for this specific thing14:25
croelandtI'm wondering what actual issues it would cause14:25
croelandtdansmith: is there no support for task API at all?14:25
dansmithin sdk? I bet not, it's probably been deprecated since before SDK existed no/14:26
croelandtwe have image task list/show in OSC14:26
croelandtglance image-tasks is not implemented (get tasks associated with an image)14:26
abhishekkthat is not related to old taks api14:26
croelandtglance task-create is WONTFIX14:26
croelandtoh is it only task-create?14:27
abhishekkprobably14:27
croelandthm, that changes everything14:27
abhishekkOk, so action plan would be to check SDK and then revert to mail accordingly and proceed as per plan?14:28
dansmithhere's a list of apis nova removed in a single shot for reference: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#microversion14:28
dansmithand we're far more stable with our APIs than glance is14:28
dansmithabhishekk: anything that SDK actually hits, just always return "409 Gone" and move on, IMHO14:28
croelandtabhishekk: sounds good14:29
abhishekkack, so we should continue with our work then14:29
croelandtlet's discuss the SDK after the meeting 14:29
croelandtmklejn: you wanted to discuss your spec?14:30
abhishekkSo tempest change is already posted, https://review.opendev.org/c/openstack/tempest/+/101126314:30
abhishekkyeah, we can move to open-discussion14:30
mklejncroelandt: I'll first post a refreshed draft and if there are questions that require higher bandwidth than gerrit comments I'll happily answer them next week14:31
croelandtok, please ping us when you're ready for reviews14:32
croelandtAnything else?14:33
abhishekkmklejn: also related to multipart download work14:33
abhishekkshould we discuss it next week, who is going to work on that?14:33
abhishekkI think we can conclude for the day 14:35
croelandtok, let's end this14:36
croelandtlonger than expected14:36
croelandt#endmeeting14:36
opendevmeetMeeting ended Thu Oct 22 14:36:05 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2026/glance.2026-10-22-14.01.html14:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2026/glance.2026-10-22-14.01.txt14:36
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2026/glance.2026-10-22-14.01.log.html14:36
croelandtabhishekk: so there is a create_task() method in openstack/image/v2/_proxy.py14:40
abhishekkack14:41
abhishekkbut do we really need to worry now about this?14:43
dansmithAFAIK, nobody can reasonably be using this, which means that there is no client/sdk behavior to salvage here14:45
dansmithso we can leave the URL and return a 409 if we want, but actually preserving it or bumping the entire API version for this is insanity, IMHO14:45
dansmithit's not like the offered example of cinder v2 and v3 where we were going from one supported widely-used thing to another14:45
abhishekkright14:47
* abhishekk thinking that sending mail was a mistake 14:49
croelandtabhishekk: too late now15:19
abhishekk;/15:21
tkajinammaybe 403 forbidden or 410 gone can be better because the response does not depend on status of the target resource.15:40
tkajinamafair 401 is what nova used to shut down all apis for nova-net/xen15:40
tkajinams/401/410/15:40
dansmithtkajinam: sorry I meant 410 above15:44
dansmith"gone" is what I wanted, I just forgot the code ;D15:44
dansmithabhishekk: ^15:45
tkajinamdansmith, oh, ok15:45
tkajinamthen I totally agree15:45
abhishekkdansmith: ack15:46
abhishekkSo we will keep endpoints and return 410 and remove the internal code15:46
dansmithyup15:47
abhishekkack, sounds good15:48
croelandtdansmith: does Nova even use that Glance endpoint?16:15
dansmithno16:16
*** zseguin is now known as Guest357419:13

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