| jovial | Just reading: https://docs.openstack.org/project-team-guide/deprecation.html. Is the guidance for tock depecation still current (4b) or should we only deprecate in a SLURP release as per https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html#details? | 11:19 |
|---|---|---|
| frickler | IMO deprecating in non-SLURP is still possible and valid, we should just fix the wording in the deprecation doc. like deprecate in 2025.2, keep deprecation in 2026.1, remove in 2026.2 is a valid timeline | 12:15 |
| fungi | right, the important part is that someone doing a slurp upgrade doesn't jump straight from supported to removed with no version that has the deprecation | 13:17 |
| fungi | also projects can (and many do) employ longer deprecations, sometimes years long, depending on the nature of the feature being phased out | 13:18 |
| jovial | Thanks. I think the confusing bit is "Since the deprecation, waiting, and removal can only happen in “SLURP” releases, the result is also that the minimum length of time that things may be deprecated before removal will increase as well" and we do link to the resolution from https://docs.openstack.org/project-team-guide/deprecation.html. But agree, the guidance in 4b does mean that operators get a least on deprecation notice before removal. | 14:58 |
| fungi | maybe the point that needs to be made is that it has to be deprecated for at least one slurp release (so if you start deprecation in a not-slurp then you're stuck keeping it deprecated for two releases) | 15:06 |
| fungi | it *minimally* must be deprecated in a slurp release | 15:06 |
| fungi | but doesn't have to *only* be deprecated in a slurp release | 15:07 |
| mnasiadka | Yes, so if you deprecate in 2026.2 - you can’t drop in 2027.1 | 15:34 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/governance master: Deprecate vitrage project https://review.opendev.org/c/openstack/governance/+/982869 | 15:59 |
| *** gibi_ is now known as gibi | 16:16 | |
| gouthamr | tc-members: a gentle reminder that our weekly meeting will be hosted here in ~45 minutes | 16:17 |
| gouthamr | the agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 16:17 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/governance master: Deprecate vitrage project https://review.opendev.org/c/openstack/governance/+/982869 | 16:51 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Mar 31 17:00:28 2026 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
| opendevmeet | The meeting name has been set to 'tc' | 17:00 |
| gouthamr | Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 17:00 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 17:00 |
| gouthamr | #topic Roll Call | 17:00 |
| noonedeadpunk | o/ | 17:01 |
| gouthamr | courtesy-ping: frickler, spotz[m], cardoe, mnasiadka, bauzas | 17:02 |
| cardoe | o/ | 17:02 |
| frickler | \o | 17:02 |
| mnasiadka | o/ | 17:02 |
| bauzas | I'm here but mostly off | 17:02 |
| bauzas | \o | 17:02 |
| gouthamr | noted absence: d a n s m i t h | 17:02 |
| gouthamr | hmm, we haven't seen tonyb in weeks, hopefully things are alright.. let's discuss any ongoing work that needs help when we get to the TC tracker | 17:03 |
| gouthamr | and unsure if spotz[m] is still traveling... | 17:04 |
| gouthamr | so let's get started | 17:04 |
| gouthamr | #topic Last week's AIs | 17:04 |
| gouthamr | we made good progress on the "leaderless" teams. i see proposals from noonedeadpunk to retire venus and deprecate vitrage: | 17:06 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/981959 | 17:06 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/982869 | 17:06 |
| gouthamr | besides these, all other teams have been addressed: | 17:06 |
| gouthamr | #link https://etherpad.opendev.org/p/2026.2-leaderless (leaderless teams in 2026.2) | 17:06 |
| gouthamr | ty for the proposals noonedeadpunk ... will you be doing the ML updates too? | 17:07 |
| noonedeadpunk | I am still in progress with vitrage though | 17:08 |
| noonedeadpunk | as I kinda realized that there's a bunch of xstatic repos belonging to it | 17:08 |
| gouthamr | oh, not under horizon's governance? | 17:08 |
| noonedeadpunk | but the only user of them seems to be Venus | 17:08 |
| noonedeadpunk | (except of vitrage) | 17:08 |
| gouthamr | ah i see.. i think if these are the only consumers, they can be deprecated/retired together | 17:09 |
| noonedeadpunk | at least I haven't found any more with codesearch | 17:09 |
| gouthamr | but i'd call this out to the ML in case there's any external users out there | 17:09 |
| noonedeadpunk | and yeah, will write up a ML | 17:09 |
| gouthamr | thanks noonedeadpunk | 17:10 |
| spotz[m] | I’m here though on a plane/) | 17:10 |
| gouthamr | o/ spotz[m] | 17:10 |
| gouthamr | noonedeadpunk: another one was the os_monasca revert patch, frickler found some issues on the project-config change that it depends on | 17:10 |
| gouthamr | #link https://review.opendev.org/c/openstack/project-config/+/974773 (Properly re-retire OSA Monasca roles) | 17:11 |
| noonedeadpunk | riiiight | 17:11 |
| * noonedeadpunk wonders how missed the review for so long | 17:12 | |
| gouthamr | thanks for looking at it | 17:13 |
| gouthamr | we got some reviews from folks on the requestsexception retirement, but that's also blocked with a project-config change: | 17:13 |
| gouthamr | #link https://review.opendev.org/c/openstack/project-config/+/979807 (Initiate retirement of requestsexceptions) | 17:13 |
| gouthamr | maybe fungi / clarkb can help with this? | 17:14 |
| fungi | yeah, i was probably waiting for a dependency to merge. looking | 17:14 |
| gouthamr | ah, yes, there was another project-config chain that's the parent and needs attention | 17:15 |
| gouthamr | thanks fungi | 17:15 |
| gouthamr | after the long discussion around gerrit metadata / tagging that occured here last week, i updated this change: | 17:15 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/981832 (Classify gov changes by hashtag, not topic) | 17:15 |
| gouthamr | could use some more eyes here | 17:16 |
| gouthamr | the last AI was around reviews for openstack-manuals | 17:17 |
| gouthamr | i think the release precursor changes have merged | 17:17 |
| gouthamr | #link https://review.opendev.org/c/openstack/openstack-manuals/+/981757 ([www] Setup 2026.2 and add project data to 2026.1 Gazpacho) | 17:18 |
| gouthamr | this was one of them | 17:18 |
| fungi | the one i reminded folks about in here did merge, at least, i double-checked a few minutes ago | 17:18 |
| fungi | thanks! | 17:18 |
| gouthamr | tomorrow, the team will get this in: | 17:19 |
| gouthamr | #link https://review.opendev.org/c/openstack/openstack-manuals/+/981758 ([www] Set 2026.1 Gazpacho as released) | 17:19 |
| frickler | getting some +2s ahead of time wouldn't hurt I think | 17:19 |
| gouthamr | +1 | 17:19 |
| mnasiadka | Done :) | 17:19 |
| gouthamr | perfect, we can forget about this cold soup and smell some flowers | 17:20 |
| fungi | we're not done slurping gazpacho just yet | 17:20 |
| gouthamr | haha, i get ahead of myself | 17:20 |
| gouthamr | in all seriousness, thank you release team for all the hard work! I'm hoping things go smoothly | 17:21 |
| spotz[m] | Done | 17:21 |
| fungi | our release will be the best april fools prank ever | 17:21 |
| spotz[m] | Hehe | 17:21 |
| gouthamr | the last AI i see on here is the one about "reviving" skyline, cardoe any further updates from you/your downstream team regarding this? | 17:22 |
| mnasiadka | Cold soup for April fools day | 17:22 |
| cardoe | So I've spoken to Somwya and she's going to do more reviews. | 17:22 |
| cardoe | I spoke to her manager and her manager as well to ensure she gets the time to do that. | 17:22 |
| gouthamr | wow, you've gone up the flag pole | 17:23 |
| gouthamr | thanks! i think it'd be awesome to have a PTG session about skyline - even if it's just an hour or so.. i think getting airtime at the PTG would be useful to locate other interested parties | 17:23 |
| gouthamr | and maybe operators too | 17:24 |
| gouthamr | since you're our conduit, i'll ask that you relay this to sowmya/others.. the challenge would be to get the existing maintainers participate. | 17:25 |
| gouthamr | i tried getting them to do that on a couple of occasions, but, they prefer to work async and use written communication - they are not comfortable speaking on calls in english | 17:25 |
| gouthamr | which is fine, PTG discussions can still occur with this constraint. we've done it all over the projects.. and we employ creative ways to still collaborate | 17:26 |
| cardoe | Yep will do. | 17:26 |
| gouthamr | thanks clarkb | 17:26 |
| gouthamr | ugh | 17:26 |
| gouthamr | tab | 17:27 |
| gouthamr | thanks cardoe | 17:27 |
| gouthamr | that's a wrap on the AIs i see, was anyone else working on anything to note here? | 17:27 |
| cardoe | Well her manager's manager is on the board (or whatever the board is called now). So it felt like something I should share. | 17:27 |
| fungi | still the board | 17:28 |
| spotz[m] | Still board just governing board vs board of directors | 17:28 |
| fungi | it's now the openinfra governing board rather than the board of directors, yeah | 17:28 |
| fungi | (though we still call the governors "directors" in most places) | 17:29 |
| gouthamr | ack, speaking of the board, i did see a discussion on AI usage proposed at the PTG.. i am hoping to collab with TheJulia (or find the moderator) and make sure the TC is involved.. | 17:29 |
| spotz[m] | Probably Julia or Eoghan | 17:30 |
| gouthamr | ack | 17:30 |
| gouthamr | alright, speaking of the PTG: | 17:31 |
| gouthamr | #link https://etherpad.opendev.org/p/apr2026-ptg-os-tc (TC PTG Etherpad) | 17:31 |
| gouthamr | ^ this is starting to fill up slowly | 17:31 |
| spotz[m] | That reminds me still need to grab a time slot | 17:31 |
| gouthamr | please don't wait to add topics, it'd help us plan time for discussions and for folks to plan their presence between video bridges | 17:32 |
| * gouthamr that was supposed to be its own topic, but who's keeping tab | 17:33 | |
| gouthamr | #topic A check on gate health | 17:33 |
| gouthamr | #link https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/thread/WXKGKK4L2E57K3OBCAEYLBDERA2POFGV/ (Upgrading Gerrit on review.opendev.org to 3.12 on April 12, 2026) | 17:33 |
| gouthamr | some more detail on what fungi/clarkb were telling us about breaking changes that the infra team's planning after tomorrow | 17:34 |
| gouthamr | any other gate related issues to bring up? | 17:34 |
| fungi | i don't think so. we did have a brief incident with one of our job log providers but they've recovered | 17:35 |
| gouthamr | ++ | 17:35 |
| fungi | also quay had a major outage for a good chunk of yesterday impacting some jobs, though that's sorted itself out today | 17:35 |
| clarkb | right we're trying to save the more potentially impactful stuff for after the release | 17:36 |
| gouthamr | thank you | 17:36 |
| clarkb | There is a plan to drop bionic after the release too | 17:36 |
| clarkb | I don't think openstack proper really depends on that at this point with the zanata job updates that i think noonedeadpunk did | 17:36 |
| gouthamr | ack, all testing on Ubuntu 18.04 should have been dropped in victoria release | 17:38 |
| gouthamr | ancient history at this point.. | 17:38 |
| gouthamr | alright, ty for the updates | 17:38 |
| gouthamr | #topic TC Tracker | 17:39 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2026.1-tracker (Technical Committee activity tracker - 2026.1) | 17:39 |
| gouthamr | some big ticket items on here that we need to make progress on | 17:39 |
| gouthamr | but i think if there are contentious, long standing items, we could make progress on them by: | 17:40 |
| gouthamr | 1) Making a concrete proposal that weighs any/all alternatives and have discussions on the ML and/or gerrit | 17:40 |
| gouthamr | 2) Bring that up at the PTG | 17:40 |
| gouthamr | i'll do that with the Technical Vision Document updates | 17:41 |
| gouthamr | any others like this? | 17:41 |
| gouthamr | we need a volunteer to take on "Reviving SIGs". We moved all the governance docs earlier in the cycle and made very few updates since | 17:42 |
| gouthamr | we posted a couple of SIG chair updates | 17:42 |
| gouthamr | but, i think some other SIGs have slowly decayed or folks still need direction/help to re-organize | 17:43 |
| gouthamr | at the last PTG, we asked if someone had the bandwidth to tackle these SIGs one at a time , it'd be useful | 17:44 |
| gouthamr | most recently, the RDO RPM retirement announcement revived interest in an RPM packaging SIG | 17:44 |
| gouthamr | and every now and then someone still cares about ansible-collections-openstack which the Ansible SIG maintain/ed | 17:45 |
| gouthamr | tl;dr: rot, send help | 17:45 |
| spotz[m] | Working on the RDO issue will need to find help with infra even after everyone learns how to build RPMs | 17:48 |
| opendevreview | Merged openstack/openstack-manuals master: Update project data template https://review.opendev.org/c/openstack/openstack-manuals/+/981766 | 17:49 |
| gouthamr | yeah, that's just an example of where the community could use from sharing and working with each other rather than in siloes.. which is kinda what the SIGs were targeting | 17:49 |
| gouthamr | tonyb had a couple of work items on the tracker: | 17:51 |
| gouthamr | 1) figure out a way to represent cross project liaisons more formally than in wiki.o.o. | 17:51 |
| gouthamr | 2) Update guidance on "unmaintained" branches - i.e., clarify the opt-in guideline/process | 17:51 |
| fungi | once upon a time people experimented with building rpms and debs in opendev's zuul/gerrit. also fedora builds at least some rpms with their own zuul | 17:51 |
| gouthamr | ack, i'm not sure on the latest on this if someone's volunteered to tackle the infra or needs help/ideas... tbf, the scientific sig would probably have to stretch themselves thin to tackle this by themselves | 17:53 |
| gouthamr | please do claim or add notes to the tracker etherpad if you're interested in the work items that were assigned to tonyb.. | 17:54 |
| gouthamr | let's switch topics | 17:54 |
| gouthamr | #topic Open Discussion | 17:54 |
| gouthamr | alright, i apologize to the few of you that took the last TC meeting poll | 17:55 |
| gouthamr | the tool was inflexible for me to change the options, and folks wanted to see UTC rather than the "convert to my timezone" thingy that was happening automatically | 17:56 |
| gouthamr | so here it is | 17:56 |
| spotz[m] | There’s volunteers next step is where and how. At one point To y had mentioned moving the builds into opendev but not sure how far he got | 17:56 |
| gouthamr | #link https://app.rallly.co/invite/yycMVUsXThVC (poll for OpenStack TC Weekly IRC meetings) | 17:56 |
| gouthamr | so could you please take this new one? | 17:57 |
| gouthamr | the times are in UTC now | 17:57 |
| gouthamr | ack sean-k-mooney | 17:58 |
| gouthamr | ugh! tab complete gets me again | 17:58 |
| gouthamr | ack spotz[m] | 17:59 |
| gouthamr | alright, before we wrap.. any other items to slide into the minutes today? | 17:59 |
| sean-k-mooney | :) | 17:59 |
| sean-k-mooney | well times are alwasy in utc | 17:59 |
| sean-k-mooney | for mettings and events | 17:59 |
| sean-k-mooney | but i guess you mean in the poll above | 18:00 |
| gouthamr | The release is tomorrow, break out your soup spoons and then watch the OpenInfra Live episode on Thursday: | 18:00 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/NCQV5SK7NA53TXN7IF5T6IGBBY46YZEW/ | 18:00 |
| gouthamr | sean-k-mooney: haha, sorry i brought you over for that | 18:00 |
| gouthamr | thank you all for participating today | 18:01 |
| gouthamr | hopefully we'll nail a good time for next week's meeting | 18:01 |
| gouthamr | #endmeeting | 18:01 |
| opendevmeet | Meeting ended Tue Mar 31 18:01:31 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:01 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2026/tc.2026-03-31-17.00.html | 18:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-03-31-17.00.txt | 18:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-03-31-17.00.log.html | 18:01 |
| sean-k-mooney | gouthamr: on the unminated brnach topic 2024.2 is not eligabel so tha twill go direct to EOL shortly form stable/2024.2 once the 2026.1 release happens | 18:04 |
| sean-k-mooney | for 2024.1 if it exist then yes there shoudl be a explcit opt in to keep it for another release | 18:05 |
| sean-k-mooney | but there shoudl only be 1 unmaintede branch form 2023.1 on so 2023.1 should generally be eol already and 2024.1 shoudl be eold once 2025.1 move to unmaintaiend/2025.1 | 18:06 |
| gouthamr | we moved stable/2024.1 exists to unmaintained/2024.1 and i don't think we really made it opt-in | 18:11 |
| gouthamr | we wanted to define this process better prior to the transition of stable/2025.1 to unmaintained/2025.1 | 18:13 |
| gouthamr | like we have big gaps. How does one opt-in? | 18:13 |
| gouthamr | we have some language here: https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained | 18:16 |
| gouthamr | but it's a bit unclear - the liaisons are never formally documented, so as a contributor i don't really know who does the work and what the current state of an unmaintained branch is | 18:16 |
| gouthamr | gmaan: question for you regarding the PTI that we published earlier. do you know if there's been a volunteer to do the 3.14 testing? Ubuntu 26.04 LTS/Resolute will have this version by default.. so it'll save us a bunch of CI time if we began onboarding it in CI and use it for unit tests.. | 18:20 |
| gmaan | we have non voting job for 3.14 unit testing via generic template | 18:22 |
| gmaan | Nova made it voting after fixing the issue, other project can do the same | 18:22 |
| gouthamr | yes, i meant we discussed the optimization | 18:22 |
| gouthamr | when we were writing the PTI | 18:22 |
| gouthamr | gmaan: oh i see, i think its worth telling project teams that.. because the default tox jobs template will indeed run it as non-voting | 18:23 |
| gmaan | yes, it should be running in all projects now | 18:23 |
| gouthamr | to tack on, it'd be super helpful to test noble devstack jobs on resolute too .. don't know if you or anyone was planning to start on that | 18:24 |
| gouthamr | the last time you drove this as a community goal | 18:24 |
| gouthamr | last couple of times: https://governance.openstack.org/tc/goals/completed/2025.1/migrate-ci-jobs-to-ubuntu-noble.html, https://governance.openstack.org/tc/goals/completed/2024.2/migrate-ci-jobs-to-ubuntu-jammy.html | 18:25 |
| gmaan | its not very bad though | 18:25 |
| gmaan | #link https://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-py314&skip=0 | 18:25 |
| gouthamr | yes, not a lot of failures | 18:26 |
| gmaan | gouthamr: in past (since xena cycle) the distro transition was done by me, i remember noonedeadpunk helped in one transition | 18:26 |
| gmaan | gouthamr: but I am not sure I will have bandwidth to do that this time. I think we need some volunteer for that | 18:27 |
| gouthamr | ack i know you're trying to bring more contributors into the qa team | 18:27 |
| gouthamr | i wonder if one of them would like to take on this challenging task | 18:27 |
| gmaan | not sure, I do not think we have many in QA but I will say not limit it to QA team instead open it for anyone would like to help | 18:28 |
| gmaan | and QA team can help in review the devstack/other tooling changes | 18:28 |
| gouthamr | yes, ofcourse.. | 18:28 |
| gmaan | will be happy to do the transition if we will have voliunteer | 18:29 |
| gouthamr | i can put out a call for help with the TC email, i think this will be connected to other tech-debt removal goals we already have.. | 18:30 |
| gmaan | ++ | 18:30 |
| fungi | also ubuntu-resolute nodes for zuul are in progress, and that will have python 3.14 by default | 18:30 |
| gouthamr | \o/ nice to know fungi | 18:30 |
| fungi | https://review.opendev.org/c/opendev/zuul-providers/+/982182 | 18:30 |
| gmaan | that will be helpful for eventlet removal also so that integration jobs in threading mode can run on 3.14. Nova fixed some tests related to that | 18:31 |
| fungi | mnasiadka took care of the dib side https://review.opendev.org/c/openstack/diskimage-builder/+/982231 | 18:31 |
| fungi | for mirroring, that's part of why we want to drop bionic nodes is so we can clean up the package mirrors | 18:32 |
| gouthamr | neat | 18:33 |
| gouthamr | on the python 3.14 unit testing so far, the dashboard-related repos (horizon, watcher-dashboard, manila-ui, trove-dashboard, grian-ui) are perma-failing | 18:34 |
| gouthamr | out: likely a shared dependency issue.. | 18:34 |
| fungi | our ubuntu and ubuntu-ports mirror volumes in afs are close to their quotas at the moment | 18:34 |
| gouthamr | python-openstackclient, zaqar, and watcher are the other repos where py3.14 is permafailing | 18:34 |
| fungi | https://grafana.opendev.org/d/9871b26303/afs | 18:34 |
| gouthamr | yeah good time to get rid of bionic.. the i18n call out made me realize we must track how much further we've gotten on dropping antiquated tooling | 18:36 |
| gouthamr | will reach out to ianychoi so he can share his (super helpful) update | 18:36 |
| fungi | i want to say the zanata jobs got converted to run the client in containers on newer nodes | 18:39 |
| gouthamr | ++ | 18:40 |
| fungi | but worth confirming | 18:40 |
| gouthamr | ack | 18:44 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!