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