| zigo | clarkb: I've been waiting for something to be released just to catch a ref-update event and get an example payload with ref/tags in it, but it's not comming. Would you have handy an example of this type of payload? | 07:34 |
|---|---|---|
| elodilles | zigo: there will be 2 or 3 RC2 releases hopefully today o:) | 08:29 |
| zigo | elodilles: Issue is, I constantly get disconnected from ssh to gerrit, not sure why. If it was a python program, that'd be ok, but it's just a command: | 09:54 |
| zigo | ssh -p 29418 thomas-goirand@review.opendev.org "gerrit stream-events -s ref-updated" | tee -a gerrit_events_$(date +%Y%m%d_%H%M).log | 09:54 |
| zigo | Maybe I should run this in a loop? :) | 09:54 |
| zigo | Did this: | 09:54 |
| zigo | while [ 1 ] ; do ssh -p 29418 thomas-goirand@review.opendev.org "gerrit stream-events -s ref-updated" | tee -a gerrit_events_$(date +%Y%m%d_%H%M).log ; done | 09:54 |
| zigo | :) | 09:54 |
| opendevreview | Merged openstack/releases master: Release manila RC2 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/962283 | 10:10 |
| zigo | Oh ... Got one ! :) | 10:24 |
| zigo | {"submitter":{"name":"OpenStack Release Bot","email":"infra-root@openstack.org","username":"release"},"refUpdate":{"oldRev":"0000000000000000000000000000000000000000","newRev":"7305ef564003cbedc78499b9b8673886cce65be4","refName":"refs/ta | 10:25 |
| zigo | gs/21.0.0.0rc2","project":"openstack/manila"},"type":"ref-updated","eventCreatedOn":1758881635} | 10:25 |
| zigo | Problem: this doesn't contain the release name ... :/ | 10:26 |
| zigo | Would it be possible to add it? | 10:27 |
| tonyb | I don't believe so as that's coming from gerrit | 10:27 |
| tonyb | zigo: I guess you'd need to look at the project git repo to see which branch that rev/SHA is in? | 10:30 |
| tonyb | zigo: Or perhaps the zuul API? | 10:30 |
| elodilles | or maybe ref-updated is too narrow? | 11:36 |
| elodilles | i mean there might be more events that contain more details | 11:38 |
| tonyb | zigo, elodilles: what exactly are you trying to get to. I gather it's to see when a new release is made. | 11:52 |
| * frickler needs to skip the meeting today, will check later for open todos. will also be offline starting next Friday for about 2 weeks | 12:12 | |
| elodilles | frickler: ACK, thanks for notifying us | 12:13 |
| elodilles | tonyb: zigo explains here what he wants to do: https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2025-09-22.log.html#openstack-release.2025-09-22.log.html#t2025-09-22T14:23:57 | 12:14 |
| tonyb | Well I think the easy option is to collect that data from the event-stream use that as a trigger to update the releases repo and then iterate over the deliverables looking for (SHA, project, tag) combination. | 12:31 |
| tonyb | Better that cron | 12:31 |
| tonyb | I guess you might also be able to monitor the event-stream for merged changes to the releases repo and squirel that data away but that seems fragile | 12:32 |
| zigo | tonyb: I'm trying to get https://osbpo.debian.net/deb-status/ to refresh the versions of a matching when an artifact is released. | 13:01 |
| zigo | Currently, it runs on a cron job, which is not optimal. | 13:01 |
| zigo | It already already refreshes using events when I build a new package. | 13:01 |
| zigo | I'd like to do the same thing with the upstream tags: trigger a webhook for the matching release. | 13:02 |
| zigo | Example: when upstream releases somthing in Epoxy, I'll refresh bookworm+epoxy, trixie+epoxy and trixie (that will be defined in a config file). | 13:03 |
| zigo | So, I need to know, when something is tagged, to what release it belongs. | 13:04 |
| zigo | Then I'll hook it to my webhook, and make my cron job run only once a day or something, rather than every hour. | 13:04 |
| zigo | tonyb: Makes sense? | 13:04 |
| zigo | FYI, here's the source of my tooling: https://salsa.debian.org/openstack-team/debian/openstack-debian-release-manager | 13:05 |
| tonyb | zigo: Okay. I think what I described is the "easy" way to do it. monitor the event stream instead of cron and then grovel around in the releases data to determine the appropriate release | 13:05 |
| zigo | tonyb: Monitoring the event stream, I know how to do it. What I don't know is the reconciliation with the refs/tags event with the appropriate release. | 13:06 |
| tonyb | zigo: Actually the ref-updated event arrives, and then you can pull the impacted repo and just scrape the release name from the metadata in the tag | 13:06 |
| zigo | tonyb: I already use https://opendev.org/openstack/releases though how do I know what release a give tag matches? | 13:07 |
| zigo | A tag event is like this: | 13:08 |
| zigo | {"submitter":{"name":"OpenStack Release Bot","email":"infra-root@openstack.org","username":"release"},"refUpdate":{"oldRev":"000000000000000000000000000000000 | 13:08 |
| zigo | 0000000","newRev":"7305ef564003cbedc78499b9b8673886cce65be4","refName":"refs/tags/21.0.0.0rc2","project":"openstack/manila"},"type":"ref-updated","eventCreate | 13:08 |
| zigo | dOn":1758881635} | 13:08 |
| zigo | It doesn't tell the release name ... | 13:08 |
| tonyb | You have the SHA, and the project so look at the deliverables data for that project, sha and tag | 13:09 |
| tonyb | https://opendev.org/openstack/releases/src/branch/master/deliverables/flamingo/manila.yaml#L29 | 13:09 |
| zigo | Wll, that's the problem: 7305ef564003cbedc78499b9b8673886cce65be4 from the event doesn't match d4e94d474de84df92254c60188f812c525a4d665 from the manila.yaml ! | 13:09 |
| tonyb | Actually the SHA isn't helpful as it's the SHA for the tag not the commit | 13:10 |
| tonyb | Or git -C /path/to/openstack/manila remote update; git -C /path/to/openstack/manila show 7305ef564003cbedc78499b9b8673886cce65be4 | grep meta:series | 13:12 |
| tonyb | where obviously "openstack/manila" and "7305ef564003cbedc78499b9b8673886cce65be4" are the values you got from the stream | 13:13 |
| tonyb | OR instead of the SHA lookup the tag in the deliverable data | 13:13 |
| zigo | Hum... that would mean having a git repo locally for each and every dliverable... | 13:14 |
| tonyb | Unfortunately You're going to need at least 2 data-sources to get what you want | 13:14 |
| zigo | Right. | 13:15 |
| tonyb | zigo: Or, I suspect you could do a shallow clone as needed | 13:15 |
| zigo | Yes, something like this. | 13:15 |
| zigo | Thanks for your help. | 13:15 |
| elodilles | (this shows all the metadata fwiw (in manila repo): git show refs/tags/21.0.0.0rc2 ) | 13:15 |
| tonyb | That's neater I forgot I could use refs/tags/ ! | 13:18 |
| elodilles | it's the same as simply 'git show 21.0.0.0rc2', but then it requires less stream editing from the event o:) | 13:23 |
| tonyb | git clone --bare --depth 1 --branch 21.0.0.0rc2 https://opendev.org/openstack/manila ; git clone --bare --depth 1 --branch 21.0.0.0rc2 https://opendev.org/openstack/manila | 13:24 |
| tonyb | 3.9M manila.git/ | 13:24 |
| tonyb | git -C manila.git tag -l --format='%(contents)' 21.0.0.0rc2 | 13:27 |
| tonyb | gives you *only* the tag contents not all the pretty/helpful stuff that git wants to show you | 13:27 |
| ttx | #startmeeting releaseteam | 14:00 |
| opendevmeet | Meeting started Fri Sep 26 14:00:48 2025 UTC and is due to finish in 60 minutes. The chair is ttx. 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 'releaseteam' | 14:00 |
| ttx | Hi everyone, welcome to the release meeting | 14:01 |
| ttx | Ping list: release-team elod | 14:01 |
| ttx | Our agenda lives at: | 14:01 |
| ttx | #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L431 | 14:01 |
| elodilles | o/ | 14:01 |
| ttx | #topic Review task completion | 14:02 |
| ttx | - Process any remaining stable branching exception (all) | 14:02 |
| ttx | I think we have none left? | 14:02 |
| elodilles | i think so, too | 14:02 |
| ttx | - Notify the Technical Committee that it should be safe to apply the Documentation Release process to create the new release series landing pages for docs.openstack.org. (elod) | 14:03 |
| elodilles | yep, so, instead of notifyint the TC i just proposed the needed changes | 14:04 |
| elodilles | #link https://review.opendev.org/q/topic:www-flamingo-final | 14:04 |
| ttx | alright, looks good | 14:04 |
| ttx | - On the day before the deadline for final release candidates, propose last-minute RCs where needed. (elod) | 14:05 |
| elodilles | this should be merged as soon as possible: https://review.opendev.org/c/openstack/openstack-manuals/+/961925/4 | 14:05 |
| elodilles | frickler: ^^^ | 14:05 |
| elodilles | when you get back | 14:05 |
| ttx | #link https://review.opendev.org/q/topic:flamingo-final-rc | 14:05 |
| ttx | and | 14:05 |
| ttx | #link https://review.opendev.org/c/openstack/releases/+/962286 | 14:05 |
| ttx | I would drop https://review.opendev.org/c/openstack/releases/+/962284 | 14:06 |
| ttx | since we should not push a RC2 last minute without PTl approval, I think | 14:06 |
| elodilles | ttx: i was thinking the same. let's drop it | 14:06 |
| ttx | unless it's super critical fixes | 14:06 |
| ttx | That leaves the Cinder one | 14:07 |
| elodilles | i don't see it as super critical | 14:07 |
| elodilles | so we definitely have to wait for cinder as the team haven't updated yet the release patch | 14:07 |
| ttx | would be good to have it in today though | 14:08 |
| elodilles | and until that is not updated we cannot move on with the 'propose-final-releases' task | 14:08 |
| elodilles | ttx: yepp. best would be to have it today | 14:08 |
| ttx | Let's wait until Monday and do the propose-final-releases task with what we have then | 14:08 |
| elodilles | +1 | 14:08 |
| ttx | I'll drop a comment on the Cinder RC2 patch | 14:09 |
| elodilles | thanks! | 14:09 |
| ttx | ok done | 14:10 |
| ttx | - Send countdown email (ttx) | 14:10 |
| ttx | will do in a minute | 14:10 |
| ttx | and... | 14:10 |
| ttx | - After the email is sent, use propose-final-releases to tag the existing most recent release candidates as the final release for projects using the cycle-with-rc model. (elod) | 14:10 |
| ttx | This one should be copied over to be done first thing Monday morning | 14:10 |
| elodilles | +1 | 14:11 |
| ttx | after we proceed any RC2 leftover | 14:11 |
| ttx | #topic Assign R+0 week tasks | 14:12 |
| elodilles | (thanks for the UTC time, I'm more aware of that than CT timezone o:)) | 14:14 |
| ttx | #topic Review weekly countdown email | 14:15 |
| ttx | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:15 |
| elodilles | looking | 14:15 |
| elodilles | LGTM | 14:16 |
| ttx | ok will send after the meeting | 14:17 |
| elodilles | ++ | 14:18 |
| ttx | #topic Open Discussion | 14:18 |
| elodilles | no topic from me this time | 14:19 |
| ttx | doing a few checks, but we seem to be ready | 14:20 |
| elodilles | yepp | 14:20 |
| fungi | i'm planning to be awake and online by 10:00 utc on wednesday | 14:20 |
| fungi | just in case i'm needed for anything and to keep an eye on zuul/gerrit | 14:20 |
| elodilles | cool, thanks | 14:20 |
| ttx | Looks like we have releases ready for everything, all stable-branched | 14:22 |
| ttx | process worked alright | 14:22 |
| ttx | OK, anything else to discuss? | 14:22 |
| elodilles | - | 14:22 |
| ttx | #endmeeting | 14:23 |
| opendevmeet | Meeting ended Fri Sep 26 14:23:47 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:23 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-26-14.00.html | 14:23 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-26-14.00.txt | 14:23 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-26-14.00.log.html | 14:23 |
| ttx | Let's get some rest before the big week! | 14:23 |
| elodilles | let's do that :) | 14:24 |
| elodilles | thanks ttx o/ | 14:24 |
| fungi | zigo: tonyb: frickler: you don't need a copy of the repository in order to fetch tag info, gerrit has a rest api: https://review.opendev.org/Documentation/rest-api-projects.html#get-tag | 14:24 |
| fungi | wget -qO- 'https://review.opendev.org/projects/openstack%2Fmanila/tags/21.0.0.0rc2' | sed /"^)]}'$"/d | jq -r .message | grep ^meta:series: | 14:24 |
| fungi | meta:series: flamingo | 14:25 |
| fungi | for example | 14:25 |
| fungi | if you're pulling it with something like python requests and feeding it into json.loads() you just have to remember to strip the )]}'\n leader from the beginning of the response (they think that's a security measure to break cross-site scripting attacks) | 14:27 |
| fungi | i agree that cloning an entire repository just to get tag info is overkill, but thankfully it's also unnecessary | 14:28 |
| opendevreview | Elod Illes proposed openstack/releases master: Add release note links for 2025.2 Flamingo (#3) https://review.opendev.org/c/openstack/releases/+/962364 | 14:40 |
| elodilles | i gave this another shot ^^^ i think this can be merged right away. if this merges, then we'll have to add less release notes links on release day | 14:41 |
| clarkb | zigo: from that event data you know the project name and the release version. From that data you can determine where the package data lives (either on pypi, on tarballs.opendev.org, or in the git repo itself) | 14:44 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!