14:01:04 <croelandt> #startmeeting glance
14:01:04 <opendevmeet> Meeting started Thu Oct 23 14:01:04 2025 UTC and is due to finish in 60 minutes.  The chair is croelandt. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:04 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:04 <opendevmeet> The meeting name has been set to 'glance'
14:01:07 <croelandt> #topic roll call
14:01:13 <croelandt> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
14:02:05 <rosmaita> o/
14:02:12 <mhen> o/
14:02:26 <dansmith> o/ (but multistasking)
14:02:45 <croelandt> #topic Release/periodic job updates
14:02:52 <croelandt> ALl good \o/ Except the fips one we know about
14:03:00 <croelandt> #topic Important stable patches
14:03:11 <croelandt> #topic https://review.opendev.org/c/openstack/glance_store/+/961870
14:03:36 <croelandt> There is a weird install issue for this one. This is annoying because it prevents us from merging the same patch in stable/2024.1 and the deadline is tomorrow :-(
14:03:59 <croelandt> I think I should probably ask someone, but not sure who can help with these kind of install issues
14:04:31 <croelandt> We're trying to install both glance-store===4.8.2 from the upper constraints, and 4.8.3dev1 from... the repo itself, I guess
14:04:39 <croelandt> If anyone has input on how to fix this, I'm all ears :)
14:04:46 <croelandt> (well, eyes since this is IRC)
14:05:00 <rosmaita> this is just for that cross-glance-tox-functional job?
14:05:47 <croelandt> yes
14:05:57 <croelandt> and just on 2024.2
14:08:28 <croelandt> so, moving on, we can come back to this after the meeting
14:08:47 <croelandt> #topic One easy patch per core dev
14:08:58 <croelandt> #link https://review.opendev.org/c/openstack/glance/+/932768
14:09:12 <croelandt> I could probably Ninja approve this doc/sample patch, but always good to have more eyes on a patch :)
14:09:21 <croelandt> #topic Glance specs
14:09:28 <croelandt> #link https://review.opendev.org/q/project:openstack/glance-specs
14:09:34 <croelandt> we can always review these before next week :)
14:09:40 <croelandt> #topic Open Discussion
14:09:45 <croelandt> Mostly about PTG this week
14:09:51 <croelandt> #link https://etherpad.opendev.org/p/oct2025-ptg-glance
14:09:56 <croelandt> #link https://etherpad.opendev.org/p/2026.1-ptg-glance-planning
14:10:16 <croelandt> The proposed agenda. Please ping me if I missed anything, if a session should last longer, etc.
14:10:31 <croelandt> After Friday EOD (my time) it'll be too late and you'll have to wait 6 months :D
14:10:36 <croelandt> Anything else?
14:11:55 <mhen> regarding image encryption, we have two sessions now correct?
14:12:27 <rosmaita> sorry, i am in another meeting, will look at the functional test failure in 20 min or so
14:12:38 <mhen> Thursday @ 18 UTC Glance+Nova
14:13:00 <mhen> and the other one (Glance+Cinder) does not have a fixed time slot yet or did I miss something?
14:13:16 <croelandt> mhen: there is one big Nova/Glance/Cinder session, for an hour
14:13:25 <croelandt> did you want an hour with Nova and an hour with Cinder?
14:13:38 <croelandt> and it's 16:00 UTC
14:13:55 <croelandt> not sure where you see 18UTC
14:13:58 <mhen> oh yea 16 sorry, messed up time conversion
14:14:18 <mhen> I'm fine with a combined session with all teams, that's even better
14:14:36 <mhen> I wonder if 1h is enough then though
14:15:08 <rosmaita> yeah, we ususally lose some time with everybody showing up, getting into the right meeting room, etc
14:15:20 <croelandt> More than an hour you usually lose people, I'd say
14:15:42 <croelandt> We're going to spend between 10 and 20 hours in technical meetings this week
14:15:45 <croelandt> it's draining
14:15:48 <rosmaita> yeah, but you can say, we can have two 1 hour sessions, or 1 combined 90 min session
14:16:00 <croelandt> I'd say if you need more than one hour to explain your topic, it's already not great
14:16:08 <croelandt> Is there no way to discuss the main ideas in one hour
14:16:24 <croelandt> and refine the details during the cycle, with specs & patches?
14:17:10 <mhen> Josephine (Luzi) did already meet a bunch of people and had some early discussions last week so maybe we have enough of a headstart going into the discussion
14:17:23 <rosmaita> ok, stick with an hour then
14:18:29 <croelandt> I'm really worried spending more than an hour is going to lead to people being fed up with the topic and not fully engaged mentally
14:18:35 <croelandt> but mhen knows better than me
14:18:56 <croelandt> mhen: if more than an hour is needed, we need to make this happen *now*
14:19:45 <mhen> the thing is: I actually don't know - up until recently this has been mostly between us, Glance and Cinder for the longest time
14:20:31 <croelandt> I know :) It is tough to chair a session, especially on a super technical topic like yours
14:20:38 <mhen> now Nova is joining the discussions more actively again (which is good)
14:21:21 <mhen> but I don't know how many things will be brought up or how controversial the discussion will get now that we have 3 projects discussing it and maybe 3 different perspectives on it
14:21:35 <croelandt> If this is such a huge topic, one of the key points to discuss is going to be "how do we keep in touch during the cycle?" and maybe that means we need someone from Nova and Cinder to join this meeting every week (not necessarily rosmaita and dansmith )
14:21:58 <croelandt> otherwise we'll discuss it once every 6 months at PTG and it might go stale
14:22:44 <mhen> we did a weekly popup team IRC meeting for a year or two in the past but it slowly lost participants
14:22:50 <mhen> maybe we can revive that
14:22:57 <mhen> I will try to discuss this in the session briefly
14:24:19 <croelandt> I think you can also prepare a detailed description of the topic to make it easier to follwo along and so everyone has a rough idea of how we're doing timewise
14:24:44 <croelandt> Anyway, I think we can wrap up, unless there are any other topics?
14:24:56 <rosmaita> release patches
14:25:26 <croelandt> oh yeah
14:25:30 <croelandt> patcheS, plural?
14:25:39 <croelandt> I see https://review.opendev.org/c/openstack/releases/+/964227
14:25:48 <croelandt> which is soft-blocked by the failure discussed above
14:26:44 <rosmaita> so, this situation is that one needs to be revised (update the hash)
14:26:51 <croelandt> yes
14:27:04 <croelandt> I would ideally manage to merge the stable/2024.2 and stable/2024.1 patch, and then change the hash
14:27:19 <rosmaita> the more recent releases only need to include stuff that is being included in Caracal but hasn't been released yet in the newer branches
14:27:45 <croelandt> I don't follow
14:28:15 <rosmaita> we don't have to release from HEAD of the more recent stable branches
14:28:34 <rosmaita> though for 2024.2 it looks like we do
14:29:53 <rosmaita> ok, let me back up
14:30:09 <rosmaita> this looks ready: https://review.opendev.org/c/openstack/releases/+/964240
14:30:28 <rosmaita> and so does this one: https://review.opendev.org/c/openstack/releases/+/964241
14:30:50 <rosmaita> so even if the 2024.2 gate is broken right now, we can still release
14:31:24 <croelandt> yes
14:31:27 <croelandt> my concern is more Caracal
14:31:42 <croelandt> https://review.opendev.org/c/openstack/releases/+/964227
14:31:53 <croelandt> this is the *last* release for Caracal, right?
14:32:00 <rosmaita> right
14:32:08 <croelandt> so if we don't merge the patches in the 2024.1 branch, they will never be part of a release
14:32:09 <rosmaita> what else did you want to get into it?
14:32:17 <croelandt> the patch above that failed to merge for 2024.2
14:32:28 <croelandt> https://review.opendev.org/q/I436d56d0489b081822ed55108e10d43cc38512bb
14:36:46 <abhishekk_> @dansmith: o/ i have pushed new changes for s3 as per suggestions, please have a look when you get time
14:37:06 <dansmith> abhishekk_: I know,  I have it open...just keep getting interrupted :/
14:37:55 <croelandt> rosmaita: ok let's end the meeting and look at the failure "offline", ok?
14:38:02 <rosmaita> ok
14:38:14 <abhishekk_> no problem, thanks for the inputs, it was better and covering all the scenarios
14:38:38 <croelandt> #endmeeting