14:00:32 #startmeeting glance 14:00:32 Meeting started Thu Feb 20 14:00:32 2025 UTC and is due to finish in 60 minutes. The chair is mrjoshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:32 The meeting name has been set to 'glance' 14:00:56 #topic roll call 14:00:56 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:58 o/ 14:00:58 o/ 14:04:50 we have a short agenda for today 14:04:58 let's start 14:05:21 #topic release/periodic job updates 14:05:37 M3 next week 14:05:56 periodic jobs: all tips failing with "No package matching 'python3.13-dev' is available" 14:06:30 Is that issue across project or just for us? 14:08:30 yeah I'm confused about this 14:08:42 didn't we push an change because it failed with an **old** version of Python? 14:08:59 I think so 14:09:18 @pdeore has pushed that change i guess 14:09:26 0addd1a99b1be32cc11301730e86234ddfb3c3c1 14:09:28 we did , for py3.11 14:09:28 yes ^ 14:09:37 so now it should use py3.13 14:09:48 and it is indeed trying to install the right package 14:09:52 but why is it not available? 14:09:56 What version of Ubuntu is that? 14:10:24 currently it's using ubuntu-noble 14:10:31 Not sure but it should be nobel 14:11:25 May be we need to ask in infra channel for help if it’s confusing 14:11:58 oh 14:12:03 just trying ubuntu 24.04 in a container 14:12:09 and they got 3.12 by default apparently 14:12:39 So there should be another way to change the default? 14:13:04 python 3.13 does not seem to be in the default repositories :/ 14:13:36 Ack, so need to shift tips job to run against 3.12? 14:13:49 but we merged the patch that moved the tips job from 3.11 to 3.13, how did the CI pass? 14:13:59 Does it not run on the same Ubuntu version as the periodic jobs? 14:14:55 Not sure, i think safe to change it to 3.12 for time being and then troubleshoot 14:15:11 yeah 14:15:14 oh but we still merge stuff 14:15:20 so current patches run on something different 14:15:54 I think that’s still 3.11 14:18:30 oh but we're not running tips 14:18:31 ok ok 14:18:37 that's why we see no failures in teh CI 14:18:42 Yes 14:18:48 so yeah we should have gone from 3.11 to 3.12, not 3.13 14:19:00 Right 14:19:24 ok, moving on then 14:19:31 Ack 14:19:48 moving ahead 14:19:56 #topic Reviews 14:20:16 Deprecate the glance-cache-{cleaner,prefetcher,pruner} commands - https://review.opendev.org/c/openstack/glance/+/933755 14:20:17 Standardization of encrypted images - https://review.opendev.org/c/openstack/glance/+/926295 14:20:17 Modified create_image - https://review.opendev.org/c/openstack/openstacksdk/+/910218 14:20:17 Updating image upload - https://review.opendev.org/c/openstack/openstacksdk/+/881939 14:20:17 Adding SDK support for glance md-tags - https://review.opendev.org/c/openstack/openstacksdk/+/897276 14:20:19 Add SDK support for ``glance image-tasks`` - https://review.opendev.org/c/openstack/openstacksdk/+/926231 14:20:47 1st two 14:20:53 Lets move them 14:21:00 To next cycle 14:21:05 ack 14:21:44 Either of us need to pick encrypted image work as original authors are no more around to take care of this 14:22:10 we should focus on SDK 14:22:19 I feel we've done 99% of the work to move to OSC 14:22:24 So better discuss the work in PTG, assign it to volunteer and get it done in next cycle 14:22:32 ++ 14:22:37 and we should be able to drop glanceclient (not as a library) soonish 14:22:46 yes 14:22:48 agree 14:22:50 I hate having to maintain both 14:23:22 I think you need to discuss with stephenfin to get a look at it 14:25:33 ack 14:25:47 that's all from me today 14:25:56 moving to Open Discussion 14:26:05 #topic Open Discussion 14:26:43 o/ 14:26:44 Nothing from me 14:26:49 I have something 14:27:27 hooray \o/ 14:27:46 I'm frustrated that this has not gotten the review it needs: https://review.opendev.org/q/topic:%22bp/glance-as-defender%22+status:open 14:27:59 and I'm not sure if we should just -W it for this cycle, given the timing 14:28:18 it needs critical review, and I think from someone with a reasonable understanding of cinder workflows 14:28:34 but I have gotten nothing from rosmaita and whoamirajat 14:28:42 Should we ignore the WIP patch? 14:29:02 I really would like to land at least the framework of that for E, but it's getting down to the wire 14:29:13 croelandt: the WIP is just glance-manage tooling at the end 14:29:15 I mean, is it truly work in progress or do you need more eyes on it? 14:29:35 ok, so you'd need rosmaita to look at it basically? 14:30:05 that's what I want, and he has promised almost weekly since last year when I bug him, but I'm tired of it 14:30:25 also asked rajat but got no response 14:30:36 and I know asking someone else close to FF is unlikely given everyone is busy 14:31:11 I think that at the very least, the safety check and format match patches should be glance-only 14:31:19 and those are pretty important, IMHO 14:31:33 the GPT stuff is more involved with the other projects 14:31:54 ok so first two patches are the "easiest" to review 14:32:05 croelandt: if you could at least look at the bottom two that would be helpful, but also happy if you want to test and review the upper ones for sure 14:32:27 yeah my thought was that maybe I review at least those 14:32:43 and once they're merged there might be more of an incentive for Cinder people to help review the "hard" ones 14:32:49 that would be appreciated 14:33:00 as in "only N patches to review" instead of "N+2 patches to review" 14:33:19 perhaps :) 14:33:23 one can dream 14:33:46 croelandt: thanks 14:33:58 abhishekk_: if you have any other ideas for reviewers, that would be great too :) 14:35:05 Lately I am also not able to put time in reviews:/ 14:35:28 Will try to take out some time for it 14:35:46 Unfortunately it is only cyril and me as of now 14:36:01 abhishekk_: you've reviewed the bottom ones already 14:36:24 but yeah, okay 14:36:25 whoami-rajat: is lot busy in escalation, so not much optimistic about his inputs 14:36:33 ack 14:37:16 sorry, i started looking at the spec and got caught up in some other issue 14:37:20 when do we have the deadline? 14:37:36 So we have rc1 as well so we can definitely target this till then 14:38:42 whoami-rajat: we are approaching m3 so we are almost near the deadline:) 14:40:15 yeah, this is why I'm bringing this up.. seems very close to review that and land the bits necessary, which is unfortunate given it's been sitting since last year 14:40:31 but, at least the bottom couple/few would help set the stage 14:41:00 Ack 14:44:34 thanks dansmith, for highlighting this 14:44:43 mrjoshi: thanks for letting me complain :) 14:45:20 :D 14:45:28 anyone has anything else to highlight , or shall we wrap up? 14:45:49 Nothing from me 14:46:14 Just to inform, croelandt will be our new deputy 14:46:37 All the best cyril and thank you Pranali 14:47:54 All the best Cyril; Thank you Pranali 14:48:11 let's wrap up then! 14:48:34 Thanks everyone for joining, Have a great weekend! 14:48:43 #endmeeting