| *** M00SE7 is now known as M00SE | 12:53 | |
| opendevreview | Jeremy Stanley proposed openstack/election master: Update OpenInfra member API endpoint https://review.opendev.org/c/openstack/election/+/1013909 | 14:58 |
|---|---|---|
| fungi | is https://opendev.org/openstack/goal-tools/src/branch/master/goal_tools/foundation.py used for anything these days? | 15:08 |
| fungi | looks like dhellmann added it 8 years ago and it hasn't been touched since then | 15:08 |
| opendevreview | Elod Illes proposed openstack/openstack-manuals master: [www] Set 2025.1 Epoxy state to Unmaintained https://review.opendev.org/c/openstack/openstack-manuals/+/1013916 | 15:11 |
| fungi | https://opendev.org/openstack/governance/src/branch/master/tools/validate_acs.py was also added by dhellmann around the same time, but has been updated by a few other people until about 3 years ago, and gets run as part of the non-voting `openstack-tox-validate_acs` job (as recently as a week ago) | 15:16 |
| opendevreview | Jeremy Stanley proposed openstack/governance master: Update OpenInfra member API endpoint https://review.opendev.org/c/openstack/governance/+/1013920 | 15:19 |
| gtema | gouthamr: cberendt and myself are on the conference now and will not join the meeting today | 16:02 |
| gouthamr | hey gtema, ack - ty for letting me know | 16:02 |
| gouthamr | tc-members: a gentle reminder that our weekly IRC meeting will be hosted here in ~55 minutes | 16:05 |
| gouthamr | agenda is here: https://etherpad.opendev.org/p/openstack-technical-committee-meeting | 16:05 |
| dansmith | gouthamr: I have a conflict, so I will be distracted | 16:06 |
| gouthamr | dansmith: ack | 16:15 |
| * gouthamr counts | 16:24 | |
| * frickler is around, just afk for a moment now | 16:58 | |
| gouthamr | ack frickler | 17:00 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Nov 3 17:00:13 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://etherpad.opendev.org/p/openstack-technical-committee-meeting | 17:00 |
| gouthamr | #topic Roll Call | 17:00 |
| noonedeadpunk | o/ | 17:00 |
| cardoe | o/ | 17:01 |
| gouthamr | noted absence: m n a s i a d k a, d a n s m i t h, g t e m a, C h r i s t i a n B e r e n d t | 17:02 |
| gouthamr | frickler will be around | 17:02 |
| gouthamr | courtesy ping: spotz [m] | 17:02 |
| spotz[m] | o/ | 17:02 |
| frickler | \o | 17:02 |
| gouthamr | great, that's everyone! thank you for joining, let's get started | 17:03 |
| spotz[m] | Beat you! | 17:03 |
| gouthamr | :P | 17:03 |
| gouthamr | #topic Last week's action items | 17:03 |
| gouthamr | we had a big one: the rust proposal needed our collective attention | 17:03 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/998652 (Add Rust use-case analysis for Keystone) | 17:04 |
| gouthamr | the timebox worked i think, most of us have some thoughts expressed on the proposal | 17:04 |
| gouthamr | thanks for taking the time to do that.. artem's set the patch to WIP; lets give him some time to address comments, and this topic can reprise here when the gerrit patch needs attention | 17:05 |
| gouthamr | would you like to note anything here wrt this change? | 17:06 |
| gouthamr | #topic A check on gate health | 17:07 |
| frickler | tox break it, tox make it again ;) | 17:08 |
| gouthamr | ah! ty for https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/1013477 frickler | 17:08 |
| fungi | classic weekend release | 17:09 |
| frickler | ah, I need to revert that again, too, yes | 17:09 |
| gouthamr | #link https://github.com/tox-dev/tox/issues/4357 | 17:10 |
| frickler | well the developer apologized for the trouble after the issue was fixed, what more can you expect? :) | 17:10 |
| frickler | also, not directly gate related, but 2025.1 is now eom. may affect upgrade jobs for 2025.2 and 2026.1, though | 17:11 |
| gouthamr | ack :) CI wastage on our end.. but thanks for catching the issue, and for the upstream conversation | 17:11 |
| frickler | credit to the upstream action goes to stephenfin | 17:12 |
| gouthamr | on 2025.1 going eol, projects will need to drop grenade jobs in 2025.2 and SLURP ones on 2026.1, correct? | 17:12 |
| fungi | and the weird llm agent auto-proposing pull requests for filed bug reports within minutes | 17:13 |
| gouthamr | i don't remember if there's any other way out of this | 17:13 |
| frickler | well either that or base them on the unmaintained branches | 17:13 |
| fungi | gouthamr: eom not eol, but yes | 17:13 |
| gouthamr | fungi: you're awarding "weird" to an LLM agent now. i thought you had to show proof of life to earn that tag | 17:13 |
| gouthamr | ah yeah, eom | 17:14 |
| fungi | fair enough, i've earned my own weirdness fair and square | 17:14 |
| frickler | also regarding unmaintained branches in general, someone volunteering to do some housekeeping on the older eom branches would be great. not sure if elodilles planned to do anything in that regard | 17:14 |
| frickler | like https://review.opendev.org/q/topic:%22create-2024.1%22+status:open would be a good list of branches to shut down IMO | 17:14 |
| frickler | or some zuul config errors like https://zuul.opendev.org/t/openstack/config-errors?branch=unmaintained%2Fyoga&skip=0 | 17:15 |
| gouthamr | ack... worth another effort to kill these branches and save our resources (and perceptions) - because of the automatic opt-in, this cleanup also needs someone's time and effort | 17:17 |
| gouthamr | fungi has a related topic for later | 17:19 |
| gouthamr | was there anything further regarding the gate to discuss? | 17:19 |
| gouthamr | oh, fungi mentioned that m nasia dka has taken on the wiki.openstack.org revival | 17:20 |
| fungi | no current timeline on restoration still | 17:20 |
| gouthamr | ++ | 17:20 |
| gouthamr | i think project teams are using this as an opportunity to clean up their docs pointing to the wiki - in some cases, they never meant to | 17:21 |
| gouthamr | meeting agendas can totally use etherpad i think, i plan to do that permanently with the TC's meeting, any objections there? | 17:21 |
| frickler | do you plan to create a new entry each week? otherwise we'll lose a bit of the history | 17:22 |
| gouthamr | we have the meeting logs and the summaries on the discuss list | 17:22 |
| fungi | i guess the timeslider in etherpad doesn't count | 17:22 |
| clarkb | with opendev I hadn't planned to make a new list every week and instead rely on the timeslider and emailed agendas to serve as the historical record | 17:23 |
| gouthamr | i could hit the star and create a time-stamped revision too | 17:23 |
| frickler | maybe then include the agenda in the weekly mail instead of linking it? that would suffice for me | 17:23 |
| frickler | s/instead/in addition to/ | 17:23 |
| fungi | yeah, opendev's meeting announcements just carry a verbatim copy of the agenda, and don't even mention the url to an editable version | 17:24 |
| gouthamr | i can do that.. helps me enforce the discipline to not squeeze something in that 24-hour window :D | 17:24 |
| fungi | there's always "any other business/open discussion" for anything that doesn't make it in time | 17:25 |
| gouthamr | ++ | 17:25 |
| gouthamr | alright, let's move to the next topic | 17:26 |
| gouthamr | #topic TC Tracker, PTG Follow up | 17:26 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2027.1-tracker (Technical Committee activity tracker - 2027.1) | 17:26 |
| gouthamr | goals need cleanup.. | 17:29 |
| gouthamr | if you're haven't looked at these proposals, please do: | 17:29 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1009912 (SRBAC goal completion) | 17:29 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1009913 (Disband pop up team) | 17:29 |
| gouthamr | i intend to workflow them this week, but can wait a couple of days if anyone needs time to | 17:29 |
| gouthamr | hberaud told me that he'd like to bring in damani as the goal champion for the remainder of the eventlet-removal goal; and i've poked ralonsoh for an update on the rootwrap->privsep migration goal.. I'll try and capture the conversation here regarding memory management strategies for privsep implementations | 17:30 |
| gouthamr | that currently looks to me like bugs and fixes to each service that uses privsep, and does something wrong.. | 17:31 |
| gouthamr | but like mikal documented (thanks for doing it!), i think profiling and identifying the import tax would point to "bad" implementations to fix | 17:32 |
| gouthamr | #link https://www.madebymikal.com/chasing-openstack-memory-usage-the-memory-your-python-services-spend-on-code-they-never-run/ (privsep memory consumption notes) | 17:32 |
| gouthamr | besides the other issue of using very broad capabilities, like the initial goal also called out: | 17:34 |
| gouthamr | #link https://governance.openstack.org/tc/goals/selected/migrate-to-privsep.html | 17:34 |
| gouthamr | besides these, there are new goal proposals. I'd like to get them past the first "proposal" phase through reviews: | 17:36 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1001777 (Add PQC Readiness as a proposed community goal) | 17:36 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1009958 (document core reviewer processes) | 17:36 |
| gouthamr | ^ both of these got some airtime at the PTG | 17:37 |
| gouthamr | mharley and cardoe both had some comments from there to address perhaps? | 17:37 |
| gouthamr | nevertheless, please do add this to your review backlog.. goal proposal != goal selected | 17:38 |
| gouthamr | so this first phase is an evaluation, and mostly documentation: | 17:39 |
| gouthamr | "Goal definitions should use the provided template so they are all formatted consistently. The goal definition does not take the place of any blueprints, spec documents, or other planning tools used within a project to track its work, but can be referenced from those documents." | 17:39 |
| gouthamr | #link https://governance.openstack.org/tc/goals/#defining-goals | 17:39 |
| gouthamr | so in that regard, these two seem fine to me; i need one/two more pair/s of eyes to confirm | 17:41 |
| gouthamr | that's a good rollcall on the tracker topics for today.. please do move any task you're working on to the tracker if it doesn't exist | 17:42 |
| cardoe | I'll work on updates | 17:43 |
| gouthamr | ty cardoe | 17:43 |
| gouthamr | alright anything else to chat about the tracker/ptg? | 17:43 |
| gouthamr | #topic Stable and unmaintained branch transitions for retired deliverables (fungi) | 17:44 |
| fungi | while processing the 2025.1 eom transition recently, the release team hit a snag with venus because openstack's "retired" acl in gerrit prevents our automation from proposing .gitreview/tox.ini updates | 17:44 |
| fungi | this led to the observation that we probably shouldn't be transitioning stable branches of retired projects to unmaintained, but also raised related questions like should existing unmaintained (and even stable) branches transition directly to eol at deliverable retirement? | 17:44 |
| gouthamr | at retirement? | 17:45 |
| fungi | did irc cut off the end of the sentence? | 17:45 |
| gouthamr | no, i was thinking out aloud | 17:46 |
| gouthamr | hmmm, that's a fair thought given these retirements were motivated by the project team disbanding | 17:46 |
| fungi | anyway, if the tc has a preference on these topics, maybe we can get some guidance encoded in the unmaintained policy and/or retirement workflow documentation | 17:46 |
| gouthamr | but, will that always be the case? | 17:46 |
| fungi | it's been policy that to land changes on older branches you have to backport from newer branches. if the newer branches are skipped we've considered that a blocker (e.g. tripleo's deprecation) | 17:47 |
| frickler | so currently for retired repos we leave stable branches in place untouched forever, right? I meant to check that, but didn't get to that yet | 17:47 |
| fungi | that seems to be what's been happening, right | 17:48 |
| gouthamr | yeah: https://opendev.org/openstack/tripleo-ansible/src/branch/stable/zed/ | 17:48 |
| fungi | we empty the master branch, but don't do anything to the stable branches while they rot indefinitely, but for non-retired projects we do close those branches down over time | 17:48 |
| frickler | I think before the unmaintained policy those may also have gotten closed down when the stable branch goes eol? but I'd need to check that, too | 17:49 |
| fungi | i guess part of the question is whether you foresee a team resurrecting a retired project as likely to revive its old stable branches from prior to retirement | 17:50 |
| fungi | or to work with a clean slate going forward, starting only from the restored master branch | 17:50 |
| frickler | another part is whether we need to keep the stable branches supported for their usual lifetime if they weren't deprecated before already | 17:51 |
| fungi | in most cases, we didn't retire deliverables until they had been inactive long enough that all existing stable branches reached end of maintenance, instead we'd hold them in a "deprecated" state waiting for those to age out first | 17:51 |
| frickler | and that would also be the policy change - if that is needed - that I'd suggest: eol the stable branches when their time has come (like for 2025.1 right now), don't transition to unmaintained | 17:52 |
| gouthamr | ^ i think that's simple enough | 17:52 |
| gouthamr | but, i don't really like this automatic transition either :( | 17:52 |
| gouthamr | i really think "unmaintained" needs to be opt-in | 17:52 |
| gouthamr | per branch, per project | 17:53 |
| fungi | i guess that's what's different about the venus case wrt existing stable branches, retiring the deliverables with branches under maintenance (rather than deprecating) is not a typical workflow | 17:53 |
| fungi | which is why this hasn't caused problems in recent history | 17:54 |
| gouthamr | i see | 17:54 |
| fungi | so maybe that's the other hole in policy and/or process | 17:55 |
| gouthamr | monasca was in the same position as venus - i.e., the project team disappeared | 17:56 |
| gouthamr | #link https://opendev.org/openstack/monasca-api | 17:56 |
| gouthamr | ^ we've deleted all the branches | 17:56 |
| gouthamr | and my memory may be mushy here, frickler helped with this by actually cleaning up the older branches during the retirement process | 17:57 |
| gouthamr | (not after) | 17:57 |
| fungi | was it inactive for long enough before retirement that the branches had aged out without creating new ones? | 17:57 |
| gouthamr | could be; venus spent some time being "inactive" too.. but maybe we limped along differently | 17:59 |
| frickler | https://review.opendev.org/c/openstack/releases/+/958076 | 17:59 |
| fungi | yes, venus skipped two releases | 17:59 |
| frickler | yes, needed to do that by "hand" ... well script ;) | 17:59 |
| gouthamr | fungi: would you be able to propose your thought as a resolution? or would you want one of us to? | 18:00 |
| fungi | i can propose a resolution amending the unmaintained policy | 18:00 |
| gouthamr | we're at the hour, and i don't expect resistance to your idea.. you're right that this is a gap in our policy | 18:00 |
| fungi | like the prior amendment | 18:00 |
| gouthamr | ack | 18:01 |
| gouthamr | ty for bringing the topic here, and for the cleanup! | 18:01 |
| gouthamr | alright, we're past the hour. Is there anything else you'd like to add to the minutes today | 18:02 |
| fungi | my pleasure | 18:02 |
| gouthamr | if not, i hope, after all the DST changes, that the time for this meeting still works in your calendars. If you have an issue, please let me know | 18:03 |
| gouthamr | thank you all for participating today | 18:03 |
| gouthamr | #endmeeting | 18:03 |
| opendevmeet | Meeting ended Tue Nov 3 18:03:40 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:03 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2026/tc.2026-11-03-17.00.html | 18:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-11-03-17.00.txt | 18:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-11-03-17.00.log.html | 18:03 |
| dansmith | gouthamr: sorry, I watched most of that delayed, but I'm _still_ on my conflict | 18:10 |
| gouthamr | dansmith: no problem at all :) | 18:34 |
| *** elodilles is now known as elodilles_pto | 20:24 | |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!