14:00:12 #startmeeting glance 14:00:12 Meeting started Thu Feb 8 14:00:12 2024 UTC and is due to finish in 60 minutes. The chair is pranali. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 The meeting name has been set to 'glance' 14:00:12 #topic roll call 14:00:12 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:22 o/ 14:01:00 o/ 14:01:11 o/ 14:01:12 * abhishekk in different meeting but here if i required 14:01:25 ok, let's start then 14:01:32 #topic release/periodic jobs updates 14:01:39 M3 is just 3 weeks from now 14:01:57 and glance_store release will be a week before that, so can we have review party next week if everyone is available 14:02:37 * croelandt is available 14:02:39 so that we can get time to address the review comments before final release 14:03:18 cool, let's have it next week then 14:03:50 Periodic jobs are all green except intermittent TIME_OUTs on fips jobs 14:04:00 moving to next 14:04:03 #topic other release-related stuff 14:04:13 Transition Yoga to Unmaintained 14:04:13 #link https://review.opendev.org/c/openstack/releases/+/906584 14:04:30 open reviews: #link https://review.opendev.org/q/(project:openstack/glance+or+project:openstack/glance_store+or+project:openstack/python-glanceclient)+AND+status:open+AND+branch:stable/yoga 14:05:02 so, the deadline for final release from yoga was actually November 2023 14:05:07 I think we should have these 2 patches in before the branch moves to unmaiantain 14:05:22 but, the release team is allowing people to do them late 14:05:24 (i think) 14:06:07 ohh ok 14:06:30 ok, then we need to merge them, propose a final yoga release (which is really going to piss off the release team, because a library release affects requirements (upper-constraints) 14:06:47 i think the backports are allowed in unmaintained branches as well, right? 14:06:58 or we could drop those backports :) 14:07:00 and then update the yoga->Unmaintained patch with the correct hashes 14:07:05 Do we have distros depending on Yoga? 14:07:21 croelandt: yes, the other option is just to abandon those 14:07:53 pranali, yes, there is a global unmaintained core team that can merge stuff into unmaintained/yoga 14:08:09 so we can split the difference: 14:08:31 abandon now, then re-propose to unmaintained/yoga after it's created 14:09:09 croelandt: that patch seems more of a nice to have than a necessity, security-wise ... is that right? 14:09:46 Well it's not optimal to show access keys even in DEBUG logs 14:09:57 I think some people would consider it a critical issue 14:09:59 we decided not to 14:10:26 That's why I wonder whether distros are based on yoga 14:12:01 well, we need to decide if it's worth burning a bunch of good will with the release team to do a late yoga release 14:12:26 I don't know, but i do know that some distro is based on victoria 14:12:40 and there are unmaintainers for that branch 14:12:50 so, they will want to have this fix in victoria 14:13:01 and hence, they will backport it 14:13:23 so i think if we re-propose for unmaintained/yoga, that will be sufficient for distros 14:13:43 if that means less stress for the release team, I'm all for it 14:13:48 amen! 14:13:49 then i think abandoning now and then re-propose to unmaintained/yoga after it's created would be better 14:14:22 ok, cool, then pranali you just need to check that the hashes are correct on that patch and then +1 it 14:14:42 yes I will do that right after the meeting 14:14:47 cool 14:15:08 and for ussuri to EOL as well, #link https://review.opendev.org/c/openstack/releases/+/903311 14:15:08 that will break the glance release notes job, btw 14:15:24 (when they delete stable/yoga) 14:15:34 there will be bot-generated patches for all deliverables 14:15:51 but, we decided to go with different patches in cinder 14:15:57 ohh ok 14:16:17 https://review.opendev.org/c/openstack/cinder/+/907836 14:16:42 the base path on that review is the bot-proposed one 14:16:53 *patch 14:17:08 no, that's incorrect to 14:17:12 *too 14:17:18 PS1 is what the bot proposed 14:17:27 PS3 is what we decided to go with 14:17:46 either one will work, just a matter of what the project prefers 14:18:28 but my reason for mentioning is that someone needs to be ready to merge the change after stable/yoga is deleted to unbreak the release job 14:18:50 ok 14:19:10 anyone want me to explain the difference between the patches? 14:19:11 so what glance should prefer ? 14:19:20 same as cinder ? :) 14:19:29 that would be my preference! 14:19:32 so the issue is 14:19:48 the bot generated patch will look for releasenotes in unmaintained/yoga 14:20:08 so our release notes will include changes merged by people not on the glance team 14:20:44 the cinder-style patch looks for release notes before yoga-eom tag, which are the release notes for stuff we (glance team) merged 14:21:27 i think ironic wants to go with the bot patch, but they are also creating an ironic-unmaintained-core 14:21:42 so they are going to active in the unmaintained branches 14:21:52 (i am assuming that we don't want to be) 14:22:07 so that's the difference and the implications 14:23:10 Thanks for sharing this :) 14:23:24 np 14:23:49 let's move ahead 14:23:55 btw, i wanted to mention 2 dashboards i added to the "spotlight links" on the agenda 14:24:12 one for release patches, one for bot-generated patches 14:24:31 hopefully they will make it easier for us to do these things faster 14:25:48 yeah, that would be really helpful, Thanks again ! 14:25:51 ok, sorry for hijacking 14:26:14 np :) 14:26:16 we were supposed to be talking about ussuri EOL 14:26:31 looks like there are no open reviews, so that's good 14:26:44 just need to verify the hashes on the patch and give it a +1 14:26:53 https://review.opendev.org/c/openstack/releases/+/903311 14:26:58 yeah as i mentioned that above, I will check that too 14:27:08 great! 14:27:35 that's all from me 14:27:43 cool, let's move ahead 14:27:46 #topic Important Reviews 14:27:57 Centralized cache DB - #link https://review.opendev.org/q/topic:%22centralized-cache-db%22 14:27:57 New Location APIS - #link https://review.opendev.org/q/topic:%22New-Location-Apis%22 14:28:35 So, these are the possible targets for this cycle, just waiting for reviews, so kindly please have a look on priority 14:29:30 we can target these for review party as well, but it would be better if we can do it before that :) 14:29:41 Support for Image Encryption - #link https://review.opendev.org/c/openstack/glance/+/902648 14:30:00 There are few comments from abhishekk on this since quite a long time which are not addressed, I will try to reach out to the owner for the same so we will get clear idea whether we can have this in this cycle or not 14:30:29 that's it from me 14:31:21 moving to open discussions 14:31:23 #topic Open Discussion 14:31:52 anyone has anything else to highlight ? 14:32:07 just about the scrubber 14:32:23 no response to my email proposing to remove it 14:32:29 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/33F37CL4NUE3QI6GYBWG5BL5UNBK4L5U/ 14:32:49 tbh, i don't know how to interpret that 14:33:04 yeah 14:33:19 "does nobody use that, or are people just not reading that mailing list" 14:33:20 although, the scrubber is really only helpful for swift 14:33:31 and i think more people are using ceph? 14:34:20 or maybe we improved the swift glance_store ? 14:34:53 it used to be that the call to swift to delete an image did not return until all the segments making up the image had been deleted on the swift side 14:35:00 and that could take a really long time 14:35:06 I think we should mention the timeline of few weeks, if we no response till then we will assume that it's a go forward signal 14:35:09 but maybe that's not an issue any more? 14:37:05 i'm not sure about this 14:37:36 me neither 14:39:08 Lets wait for two more weeks, anyway we are going to remove it next cycle 14:39:44 I think we need to deprecate delayed_delete config option? 14:41:49 I think restore 14:44:32 abhishekk, ^ 14:44:37 both 14:44:45 ohh ok 14:44:55 delayed_delete is not useful if scrubber will be removed 14:45:39 ack 14:46:31 so let's wait for few more weeks as abhishekk mentioned, 14:46:44 yep 14:47:59 ok, anyone has anything else to discuss ? 14:49:02 abhishekk: good point, we need to deprecate delayed_delete 14:49:12 yes 14:49:23 we can deprecate it this cycle I guess 14:49:53 ok, maybe the thing to do is i will follow up that email with a reply to myself with a link to the patch deprecating delayed_delete 14:49:59 then people will know we mean business 14:50:42 :D 14:50:45 ++ 14:50:50 +1 14:51:21 #action rosmaita - post delayed_delete deprecation patch and send email to ML 14:52:08 great ! 14:52:21 let's conclude for the day then 14:52:40 Thanks everyone for joining !! 14:52:46 bye 14:52:54 bye 14:52:56 #endmeeting