| opendevreview | Merged openstack/election master: Exclude TC from PTL leaderless projects https://review.opendev.org/c/openstack/election/+/1002531 | 07:29 |
|---|---|---|
| opendevreview | Merged openstack/election master: [election-tool] Fix on tc/ptl announcement rendering https://review.opendev.org/c/openstack/election/+/1006069 | 07:31 |
| opendevreview | Merged openstack/election master: Update tc-election-summary.py: reflect 2027.1 results https://review.opendev.org/c/openstack/election/+/1006073 | 07:31 |
| opendevreview | Elod Illes proposed openstack/openstack-manuals master: [www] Setup 2027.1 Indri and add project data to Hibiscus https://review.opendev.org/c/openstack/openstack-manuals/+/1006577 | 08:51 |
| croelandt | zigo: so, do you think https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/CP7BTNWGYHSAKZ6HB4PBGPWPQU2LRKTZ/ should be discussed at PTG? I see nothing in https://etherpad.opendev.org/p/oct2026-ptg-os-tc yet, but I feel this issue (that already hit Debian) will hit everybody soon enough | 13:35 |
| zigo | Yeah, we may talk about this indeed. | 13:42 |
| zigo | Also about pkg_resources that's gone from setuptools >= 82, and that I had to patch everywhere ! | 13:43 |
| croelandt | yeah that is the main issue with Paste* | 13:43 |
| croelandt | it seems "easy" to fork it but long term we might have to move awayfrom it | 13:43 |
| croelandt | zigo: do you think you will take part in the PTG and be there to discuss that? | 13:44 |
| zigo | I hope so. When's the PTG ? | 13:44 |
| zigo | Octobre, that I know. | 13:44 |
| zigo | Have you noticed that absolutely *ALL* XStatic packages are using pkg_resources ? | 13:45 |
| croelandt | 12th to 16th | 13:45 |
| croelandt | I *think* the TC usually has sessions on Monday/Friday | 13:46 |
| croelandt | zigo: can you link to one of your patches for an Xstatic package? | 13:46 |
| zigo | Sure. | 13:47 |
| fungi | it looks like xstatic itself relied on pkg_resources up until https://github.com/xstatic-py/xstatic/commit/391413a merged a year ago, but the latest release of xstatic (1.0.3) is 3 years old | 13:50 |
| fungi | so until there's a new xstatic release, we're stuck with requirements/constraints pointing at a version that relies on pkg_resources | 13:52 |
| zigo | Lucky, the patches are almost all the time the same, and I was able to ask our local AI to write a script to automate fixing all of this. So it took me an afternoon for all of them. | 13:52 |
| zigo | For XStatic, it's fairly easy to fix. | 13:52 |
| zigo | Though as fungi just wrote: it would need a release for all packages. | 13:53 |
| fungi | some of which we don't control | 13:53 |
| zigo | zigo@k:zbuz>_ ~/salsa/openstack/xstatic $ ls | wc -l | 13:53 |
| zigo | 47 | 13:53 |
| fungi | (of note in this case, xstatic is not an openstack deliverable) | 13:53 |
| zigo | That's not a small amount of packages we're talking about. | 13:53 |
| zigo | Also to some worries: all of the Angular stuff must go, at some point. | 13:54 |
| zigo | It has unadressed security issues. | 13:54 |
| croelandt | fungi: no commits in a year for xstatic | 13:55 |
| croelandt | I think for all these packages, we want to figure out whether they are maintained/active | 13:55 |
| TheJulia | zigo: ++ | 13:55 |
| croelandt | and what we should do with them | 13:55 |
| croelandt | if Paste is no longer maintained and we want to move away, what should be the replacement? etc. | 13:55 |
| croelandt | same for xstatic and angular | 13:56 |
| fungi | moving horizon off xstatic and angular is probably close to a from-scratch rewrite | 13:56 |
| zigo | Well, moving away from xstatic, I'm not sure. What will you replace it with? npm ? That's even worse ! | 13:57 |
| zigo | I think it's ok to continue on XStatic, it has served us well so far. | 13:57 |
| zigo | Just Angular, they know about it, but it's a LOT of work. | 13:58 |
| TheJulia | Maybe in a consistent way though? | 13:58 |
| zigo | The only thing that could help would be throwing more hands at it. | 13:58 |
| fungi | i have other concerns with xstatic, in that we've entrenched shipping vendored copies of javascript libraries we didn't create, in many cases old versions of them with known security vulnerabilities we don't/can't track | 13:59 |
| TheJulia | Vision perhaps may be first thing to reach before “throwing more hands at it” | 13:59 |
| croelandt | so maybe the web stuff should be a topic of its own | 13:59 |
| croelandt | Paste/PasteDeploy does affect ~20 projects and could be another topic | 14:00 |
| fungi | the idea was that downstream distributors would replace the vendored example versions with their own packaged securely-patched versions of those libs instead, but in practice that rarely happens | 14:00 |
| zigo | fungi: I very much agree. It's even worse for Angular: I used to rely on a patched version in Debian, ie: libjs-angularjs, though it has been removed from Debian because no upstream. So I had to re-embbed and use the unpatched version from XStatic, otherwise Horizon would have been kicked away from Debian. | 14:01 |
| croelandt | zigo: so maybe this should be part of the Horizon PTG topics | 14:01 |
| croelandt | and we'd keep cross-project issues for the TC PTG? | 14:02 |
| zigo | For Angular and XStatic ? Maybe. But the pkg_resources is not only about XStatic and Horizon though. | 14:02 |
| croelandt | yeah | 14:02 |
| zigo | There's countless of that shit everywhere. | 14:02 |
| croelandt | so pkg_resources is about 20 projects | 14:02 |
| croelandt | that definitely should be TC | 14:02 |
| TheJulia | Tc likely still needs to engage to convey across the captured issues and challenges it sees | 14:02 |
| croelandt | but "hey Angular is one of the 83238 dead JS frameworks" might be more of a Horizon-only thing | 14:03 |
| TheJulia | Otherwise horizon is going to think “don’t rock the boat, and keep on keeping on” | 14:03 |
| * croelandt is just trying who should talk about what when and where | 14:03 | |
| TheJulia | yes and ?everywhere? | 14:03 |
| zigo | Many sphinx projects: | 14:04 |
| zigo | - sphinxcontrib.apidoc | 14:04 |
| zigo | - sphinxcontrib-programoutput | 14:04 |
| zigo | - sphinxcontrib-actdiag | 14:04 |
| fungi | zigo: i started trying to add warnings to the readme files, like you see at https://pypi.org/project/XStatic-JQuery-Migrate/ but that effort stalled and needs to be revived | 14:04 |
| zigo | - sphinxcontrib-blockdiag/ | 14:04 |
| zigo | - sphinxcontrib-nwdiag | 14:04 |
| zigo | - sphinxcontrib-seqdiag | 14:04 |
| croelandt | see, you're probably one of the most informed people on this topic :) | 14:07 |
| croelandt | so you should definitely have a bit of time to explain the issue at PTG | 14:07 |
| zigo | I wrote referenced all the patches I could find on my laptop's filesystem ... :) | 14:09 |
| TheJulia | Just putting this out there, it wouldn't be bad for the TC to discuss web-ey stuff early on and try to assert vision. The reason I note that is we whipped up an python/npm hybrid adminy-web ui for Ironic, which has a specific base use case, "operator on the data center floor" or "operator in the NOC" sort of use case. And to attest to how advanced some AI's now are, another contributor raised just the idea to their prompt's to | 14:19 |
| TheJulia | brainstorm and it argued with them and made them a semi-working proof of concept as well. It would get us dangerously close to a perception of vibe coding because agents are so good at it, but its a direct human application layer interface, its not stable long lived APIs sort of interactions, so the overall use case and even human interaction modeling likely shouldn't tried to be kept as software for humans != software. | 14:19 |
| opendevreview | Grzegorz Grasza proposed openstack/security-doc master: Add OSSN-0111: Keystone MFA enforcement gaps and replay weaknesses https://review.opendev.org/c/openstack/security-doc/+/1006742 | 14:37 |
| JayF | I mean, we haven't even reached consensus in Ironic that it even fits within our scope. It might be early for the TC to get involved. | 16:06 |
| clarkb | there is already a baseline of expectations in the supported platform doc too (though I have no idea if they remain relevant in the js/web space) | 16:07 |
| gouthamr | tc-members: a gentle reminder that this week's IRC meeting will be hosted here in ~45 minutes | 16:15 |
| gouthamr | agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 16:15 |
| TheJulia | JayF: Oh, yes, there is still discussion to have there, but there is a wider discussion regarding webapps there which the tc ought to have. I'm saying they ought to be mindful of the latter, ironic is just an example of where we've got one wip posted and someone else has another wip they have created which likely follows the python bits + npm stuffs for the actual user interaction. | 16:33 |
| TheJulia | To that point, the npm stuff at least got initially charted by ?mkrotscek? ages and ages and ages ago. | 16:34 |
| JayF | yeah, I think there is potentially room for that, but bluntly I'm a little more careful of gathering scope given how many teams we have near minimum levels of maintenance | 16:35 |
| TheJulia | The other aspect, is the world is evolving, its okay that it is but to say the status-quo with angular/xstatic is... not really working for the end user side of it | 16:35 |
| TheJulia | yeah, the reality is to address some things, we're going to have to become more comfortable with evolving forward because we can't really "just do nothing" or "try to keep the tech debt because that is easier", because in the end, its a huge cost | 16:36 |
| fungi | but also, openstack was built by the people who wanted to use it, unless that continues i don't think it can be sustainable | 16:37 |
| fungi | naive recommendaitons to "evolve" aren't actionable, sadly | 16:38 |
| TheJulia | Built by people who wanted to use it, but now we're in a diffrent age of usage where users are no longer creators/maintainers | 16:39 |
| fungi | evolution is an uncontrolled reaction to changing conditions, so by definition we can't choose to evolve | 16:39 |
| TheJulia | Well, I'm broadly trying to champion evolution becuase I've had people double down on just piling techdebt as the needful thing to do when in reality, its really not from a big picture standpoint. | 16:40 |
| fungi | we will either evolve or perish, but evolution is messy and not designed | 16:40 |
| TheJulia | fair | 16:40 |
| TheJulia | and very true | 16:40 |
| JayF | I kinda disagree with this framing? | 16:40 |
| JayF | We're literally in the technical committee chat room -- we can't pretend like the community can't have directionality put on it | 16:41 |
| JayF | if I were to extend the metaphor I might say the TC are intelligent designers, but I really would prefer not | 16:41 |
| fungi | what we design isn't evolution though, they're different things. we will evolve, hopefully in ways compatible with what we design | 16:42 |
| gouthamr | the TC can set an aspiration and endorse community initiatives... skyline is/was one such thing - didn't pan out because the biggest backer dropped out and its now truly someone's hobby work | 16:43 |
| JayF | gouthamr: that's my big concern, and in context of the stuff TheJulia has proposed in ironic, it's extra scary because that's being proposed in-tree | 16:44 |
| gouthamr | #TIL about ironic's web ui... is this something in the works? | 16:44 |
| JayF | gouthamr: ironic-ui is a horizon plugin that's existed a long time | 16:44 |
| TheJulia | Maybe more to the point, there are efforts/thoughts/ideas on the periphery based upon use case challenges where existing tools/patterns may not match. That itself is evolution happening, the key is build consensus | 16:44 |
| JayF | gouthamr: I'd call it barely maintained | 16:44 |
| TheJulia | gouthamr: And there was also ironic-webui ages ago as a pure js api client assembly | 16:44 |
| JayF | The openapi push, if we can get it across a finish line, will help with these kinda problems too | 16:45 |
| fungi | did/does bifrost also have a webui? | 16:45 |
| TheJulia | gouthamr: but use case wise, one thing doesn't always solve all use cases or patterns so we've got a few people going "hey, maybe we do something with a targeted use case" | 16:45 |
| JayF | fungi: bifrost is ansible in a dress, more or less | 16:45 |
| fungi | i hope it's a sequined dress at least | 16:45 |
| JayF | fungi: so not really, but you COULD install horizon+ironic-ui and point it at ironic, assuming you deployed with keystone | 16:45 |
| TheJulia | A frosty bridge of ansible | 16:45 |
| JayF | fungi: they're a bunch of sparkly red sequins that if you put under a microscope are fedora shaped (/s) | 16:45 |
| fungi | ouch | 16:45 |
| gouthamr | ack, which is the state with all of horizon unfortunately, because we've been limping along with old dependencies and are limping along while upstream packages keep going out of support. we could probably ask what the team's plans are - but likely they're to KTLO rather than an ambitious rewrite | 16:46 |
| TheJulia | But to the point, digging through horizon is not the needful for DC ops who are doing inventory or breakfix activities either. We could, but do they really need to tie it in, and even then we would want to do it in a modern form so we can engage with the camera and do things like barcode/information capture | 16:46 |
| TheJulia | so it boils down to different groups of users, and thats not a defect, that is an artifact of success | 16:47 |
| TheJulia | JayF: hey now, bifrost got started at HPE ;) | 16:48 |
| JayF | TheJulia: to be clear: my questions are shaped "does this belong in tree in ironic?" (with my answer being "oh I hope not"), and "does this belong in openstack?" (with my primary concern being bus factor for contributors) | 16:48 |
| JayF | TheJulia: that was more a nod to the control over ansible ;) | 16:48 |
| TheJulia | So if anything, it whatever the hplinux logo was | 16:48 |
| JayF | if bifrost is ironic in a dress, the dress is ansible, and almost certainly you'd have to call that an RH design ;) | 16:48 |
| mnasiadka | I’d say one thing is what horizon team is doing, second thing is that mostly the $project teams have no clue what to do with their -ui deliverable and they just merge translation patches and try to make sure the ui plugin doesn’t get awfully broken cycle to cycle | 16:49 |
| JayF | mnasiadka: that's what I'm counting for "barely maintained" for ironic-ui | 16:49 |
| ChristianBerendt[m] | Hi, everyone. Just a quick test to see if the Matrix bridge is working properly on my site. | 16:51 |
| clarkb | I'm old enough to remember when you'd be shown the door immediately for taking a camera into the datacenter. Doesn't matter if that camera was on company issued hardware either | 16:51 |
| TheJulia | I think part of the issue which gets dug to the surface is horizon sort of takes a different model on rbac and interactions, and we basically ignore that and I'm not sure how we *really* reconcile that back to reality as well or even give the dependency issues... where does one even really get started anyway. | 16:51 |
| fungi | ChristianBerendt[m]: it's working great! | 16:51 |
| clarkb | ChristianBerendt[m]: yes your test message came through | 16:51 |
| ChristianBerendt[m] | Thanks | 16:51 |
| gouthamr | w00t, welcome, ChristianBerendt[m] | 16:51 |
| TheJulia | clarkb: blame vendors encoding passwords in 3d barcodes | 16:52 |
| gouthamr | o.O | 16:52 |
| JayF | clarkb: I'm pretty sure $downstream here operates similarly :) | 16:52 |
| fungi | clarkb: i remember having to hunt high and low to find a cell phone that didn't include a camera so i wouldn't violate our data center policies | 16:52 |
| JayF | clarkb: the idea of using a mobile app to manage DC issues is mildly hilarious given our security model :P | 16:52 |
| JayF | fungi: hate to tell you but I brought camera phones into HS more than a dozen times, but maybe they were nicer to customers ;) | 16:53 |
| JayF | (you did work there, right? I'm not misremembering) | 16:53 |
| clarkb | to be clear I'm sure it is useful to some orgs. I'm just surprised given my background. We had hdd shredders accessible in the DC too because those were not allowed to exit the doors either | 16:53 |
| fungi | JayF: yes, though i think the camera policy there got relaxed in later years | 16:53 |
| clarkb | one door was a turnstile and the bay doors required multiple people to authorize opening (or you'd set off the fire alarms) | 16:54 |
| TheJulia | fungi: yeah, In my last DC job, that challenge is why we tossed the requirement. Cabinets kept locked/restricted access controls + a trusted dc ops team were good enough mitigating controls for our auditors. And... then when we needed photos for cooling warranty/repairs... it just made life easier. | 16:54 |
| fungi | it was also my job to maintain the iso/iec mapping for our facility security policy documents, so i probably followed them more closely than other staff members | 16:56 |
| fungi | at least if i didn't know about people violating policies, i didn't have to lie to the auditors | 16:57 |
| TheJulia | heh, Similar role of meeting with all the auditors. I remember an auditor asking me about details of why and I think he gave up on the question realizing how stupid it was when I was at the 45 minutes of a process ) | 16:58 |
| clarkb | outside of the DC was an entirely different story. We would occasionally dumpster dive the hardware dev locations and you'd often get your hands on a brand new unreleased CPU you could stick in a workstation that lived at your desk | 16:58 |
| gouthamr | (in 2 minutes, you folks will be interrupted) | 16:58 |
| gouthamr | :P sorry | 17:00 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Sep 22 17:00:46 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:01 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 17:01 |
| gouthamr | #topic Roll Call | 17:01 |
| mnasiadka | o/ | 17:01 |
| ChristianBerendt[m] | o/ | 17:01 |
| noonedeadpunk | o/ | 17:01 |
| gouthamr | courtesy-ping: spotz[m] frickler cardoe mnasiadka gtema | 17:03 |
| gouthamr | grr, sorry mnasiadka | 17:03 |
| cardoe | o/ | 17:03 |
| mnasiadka | gouthamr: no worries, I’m always late :) | 17:03 |
| cardoe | I'm always on time and then ADHD kicks in and I switch to another tab | 17:03 |
| gtema | Sorry, I am on PTO till end of the month | 17:04 |
| noonedeadpunk | :D same for me | 17:04 |
| gouthamr | ah, ack both of you.. i thought summer's wrapped up here in the Northern Hemisphere :) | 17:05 |
| gouthamr | but that's some well deserved break from the release no doubt | 17:05 |
| frickler | \o | 17:05 |
| gouthamr | ty for joining, let's get started.. | 17:05 |
| gouthamr | (notes spotz[m] had mentioned being on a plane elsewhere) | 17:06 |
| gouthamr | #topic Last Week's Action Items | 17:06 |
| gouthamr | first off, i'd like to welcome ChristianBerendt[m] to the TC! thanks for signing up to serve, congratulations on your election | 17:06 |
| ChristianBerendt[m] | ty happy to be here | 17:07 |
| gouthamr | i'd also like to welcome back frickler cardoe and gtema.. gtema returns to the TC after a year away.. | 17:07 |
| gouthamr | thank you all for nominating yourself, and congratulations on your re-election | 17:08 |
| gouthamr | (missed dansmith in the courtesy ping) | 17:08 |
| cardoe | Speaking of which... Great work this past cycle at chair gouthamr | 17:08 |
| gouthamr | ty cardoe, also a good segue into that topic | 17:09 |
| gouthamr | we're on the third business day since we merged the election results per my math | 17:09 |
| * cardoe put the ball on the t-ball stand for gouthamr | 17:09 | |
| gouthamr | :P | 17:09 |
| gouthamr | if anyone's interested to nominate themselves, today's the final day.. | 17:10 |
| gouthamr | get your nomination into this folder: | 17:10 |
| gouthamr | #link https://opendev.org/openstack/governance/src/branch/master/reference/tc-chair-candidates/2027.1 | 17:10 |
| gouthamr | #link https://governance.openstack.org/tc/reference/tc-chair-elections.html | 17:11 |
| cardoe | where's your name in there? :D | 17:11 |
| mnasiadka | I think cardoe wanted to ask - gouthamr are you willing to continue? | 17:12 |
| gouthamr | i was hoping someone would volunteer :) | 17:13 |
| * noonedeadpunk does not see much hands | 17:13 | |
| gouthamr | hah :) if you're still thinking, take your time.. | 17:14 |
| gouthamr | since we'll be decision-pending, we'll hash out the rest of the tc-chair election process outside this meeting... we can discuss on this channel and gerrit. i'm hoping we'll get folks running/winning/nominated asap | 17:14 |
| gouthamr | we've got some work to do when we have a chair, but do think through a liaison role or two if you'd like | 17:15 |
| gouthamr | we need a VMT liaison | 17:15 |
| gouthamr | all the existing DPL "tc-liaison"s are on the TC | 17:16 |
| gouthamr | so there's no need to replace them, unless there is interest to do so | 17:16 |
| gouthamr | #link https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml (search "tc-liaison") | 17:17 |
| gouthamr | another liaison role is here: | 17:18 |
| gouthamr | #link https://opendev.org/openstack/governance/src/branch/master/reference/popup-teams.rst (search "TC Liaison") | 17:18 |
| gouthamr | for this though, the liaison doens't have to be a TC member | 17:18 |
| gouthamr | i think with that, we're done talking about elections | 17:19 |
| gouthamr | and related action items | 17:19 |
| gouthamr | oh, i forgot, we also need an election team liaison, and if we can help, it should be someone other than spotz[m] | 17:20 |
| gouthamr | we can nominate all of these next week | 17:21 |
| gouthamr | as we close this out, let me thank ianychoi, slaweq, spotz[m] and fungi for all the great job on the 2027.1 elections! | 17:21 |
| fungi | <- supporting cast | 17:22 |
| gouthamr | we had an action item regarding recapping security work that happened during this release | 17:23 |
| gouthamr | JayF took an action item yesterday to share a blurb with aprice[m] on behalf of the VMT, and I am working on a list of contributors (bug reporters, fixers, reviewers) that contributed. fungi is working on the contributor list for this release, and i was suggesting incorporating this data into that | 17:24 |
| fungi | yeah, i spoke with aprice about it today too | 17:25 |
| gouthamr | ++ | 17:25 |
| fungi | we're still working out how to incorporate it, but should be able to include that in some form | 17:25 |
| gouthamr | ty fungi | 17:25 |
| fungi | (the security contributors thanks list i mean) | 17:25 |
| gouthamr | i don't know if we saw any other project team specific highlights in the meantime after our call last week.. but, the message we'll be sharing across these should capture the mood | 17:25 |
| gouthamr | fungi was sharing some of the release contribution stats here earlier, and you can poke him if you have questions | 17:26 |
| fungi | yeah, i was asked by the staff to pinpoint what parts of openstack the recent increases in contributor and merged change counts came from, so working on that now | 17:27 |
| gouthamr | great | 17:28 |
| gouthamr | for a release recap, tune into an episode of OpenInfra Live's new podcast that look at this through the lens of the project maintainers and the community leads on Oct 1st: | 17:28 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/22VSNDEOVFJVALUOJTDUJ4Q63K3FLSVU/ | 17:28 |
| gouthamr | other than that: | 17:30 |
| gouthamr | I did notice some action on a past AI: | 17:30 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/TZ3B7CXWJHE7T5UVIS6RUC4TL6QQ2QLP/ ([tc][barbican][horizon] Reviving barbican-ui: proposing a dedicated core reviewer group) | 17:30 |
| gouthamr | mharley[m]: ty for starting that thread; noonedeadpunk was any TC action required on this? | 17:30 |
| gouthamr | guess not, your questions were relevant, ty for posing them.. and you'll probably brainstorm on the biweekly meeting of the barbican team next week | 17:33 |
| gouthamr | #link https://etherpad.opendev.org/p/barbican-weekly-meeting (barbican meeting on Sep 28) | 17:33 |
| gouthamr | alright, that's a wrap on action items... anything else to mention here? | 17:33 |
| noonedeadpunk | I don't think it was needed at the moment | 17:34 |
| noonedeadpunk | (TC attention) | 17:34 |
| gouthamr | ++ | 17:34 |
| gouthamr | #topic TC PTG | 17:35 |
| gouthamr | it's time to plan our agenda for the Indri/2027.1 PTG (Oct 12-16 2026) | 17:36 |
| gouthamr | the schedule website is live as of today: | 17:36 |
| gouthamr | #link https://ptg.opendev.org/ptg.html (PTG Schedule) | 17:36 |
| gouthamr | #link https://etherpad.opendev.org/p/oct2026-ptg-os-tc (TC PTG Etherpad) | 17:37 |
| gouthamr | ^ please add your topics there between now and early Oct | 17:37 |
| gouthamr | we'll try and schedule our sessions as we've done in the past - beginning and end of the PTG period so we can seed discussions and reflect on what project teams, SIGs, pop up teams, working groups have done through the week | 17:39 |
| gouthamr | if there are any other ideas, let me know. we do have a good amount of time to inform and draw audiences that we'd like | 17:39 |
| gouthamr | for example, operators. In the last ptg, we tried a session with the Operators' Radio Hour folks... i was hoping that project teams could find themes there to drive into their own PTG sessions.. think we should encourage that again - it'll need some organizing from PTLs/liaisons | 17:41 |
| gouthamr | i'll suggest this on the ML | 17:42 |
| cardoe | yeah good idea | 17:42 |
| gouthamr | feel free to use the etherpad as a placeholder while you gather thoughts too ^ | 17:43 |
| ildikov | gouthamr: I'm about to send an email to openstack-discuss to collect questions and discussions topics for Ops discussions at the PTG | 17:44 |
| gouthamr | as usual, we'll remind project organizers to be mindful and schedule cross project sessions at the beginning of the week | 17:44 |
| gouthamr | ildikov: nice! would you have a common ops hour like last time? lmk if you see any cross-cutting themes to push into the TC's time | 17:45 |
| gouthamr | anything else about the PTG for this week? | 17:46 |
| ildikov | gouthamr: I've been chatting with Chris Morgan about this and also brought up the question on the OpenStack Ops Matrix channel. The current thinking is to decide based on what topics people want to discuss. As if there are more questions specific to particular project teams, then it might be easier to schedule time with them during their sessions. | 17:46 |
| gouthamr | ++ | 17:46 |
| ildikov | Having an Ops Radio Hour session/common Ops session is also an option | 17:47 |
| ildikov | or folks might end up with the combination of the above | 17:47 |
| mnasiadka | Kolla is only planning to schedule an operator hour this PTG - but happy to schedule something together with Ops community instead/in addition to | 17:48 |
| ildikov | In either case, input from the developer community on what topics/questions they're interested in would be very helpful and highly appreciated! | 17:48 |
| ildikov | mnasiadka: noted, thank you for pointing that out! | 17:48 |
| gouthamr | yeah, it might need some prep to bring something to a project team directly - a bug, an ML discussion or a well articulated topic in their etherpad is welcome.. | 17:49 |
| gouthamr | i picked up some feedback from nova maintainers last cycle - they were hoping for concrete takeaways.. i think its someone's burden to connect people when teams expect folks to just come to them with a flushed out idea | 17:49 |
| gouthamr | s/idea/problem | 17:50 |
| ildikov | yeah, we'll be doing our best to circulate the questions and topics in advance to the PTG | 17:51 |
| gouthamr | ++ | 17:51 |
| ildikov | I think some of the disconnect is the scope, operators see OpenStack clouds as a whole, and not every challenge can be mapped to a single OpenStack project/service | 17:51 |
| ildikov | while teams would like to understand how to make their projects better specifically | 17:52 |
| gouthamr | ack, that's indeed where the TC can help | 17:52 |
| ildikov | so I hope a bit more time spent on prepping will help with bridging that | 17:52 |
| ildikov | gouthamr: that would be great! | 17:52 |
| gouthamr | ack, and ty for that coordination.. its so much hard work and feels like herding cats, but its very valuable eventually and i'm very glad to see your energy for it :) | 17:53 |
| gouthamr | as the ideas fill up, please use this channel to brainstorm - we'll help with organizing the topics | 17:54 |
| ildikov | Of course! I'm happy to help and please always feel encouraged to give me feedback and ideas on what we could/should try next to improve things, including communication. | 17:54 |
| gouthamr | ty, anything else for $topic? | 17:55 |
| gouthamr | i'll skip the "Continuing the discussion on Keystone situation" topic - it's being bounced across meetings, and is probably good to keep simmering on this so we can bring it to the PTG (i've added the topic there) | 17:56 |
| gouthamr | #topic A check on gate health | 17:56 |
| mnasiadka | I don’t know if the earlier horizon plugins discussion should land in the TC slots or Horizon slots, but with my Magnum PTL hat I’d assume that it’s important to think about managing that properly :) | 17:56 |
| gouthamr | ack, please do add it to the etherpad mnasiadka, tmazur will probably help refine thoughts for it | 17:57 |
| clarkb | over the weekend one of the zuul executors filled its root disk which caused it to fail jobs before they even started in a tight loop. YOu may haev noticed this as jobs failing with RETRY_LIMIT statuses. I pulled the executor out of the cluster and it has since been cleaned up and readded. Anyway if you see RETRY_LIMITS from late firday/early saturday pacific time then you can | 17:57 |
| clarkb | recheck | 17:57 |
| gouthamr | ++ ty cardoe | 17:57 |
| gouthamr | grr | 17:58 |
| gouthamr | tab complete, ty clarkb | 17:58 |
| cardoe | I'll take free credit. :D | 17:58 |
| gouthamr | maybe it was an executor on Rackspace :) | 17:58 |
| gouthamr | #link https://review.opendev.org/q/topic:%222027-1-testing-runtime%22 (2027.1 runtime update) | 17:59 |
| clarkb | it was but rackspace wasn't at fault. It appears that podman can leak layers in its storage system | 17:59 |
| clarkb | and for whatever reason this particular executor leaked enough layers for it to become a problem | 17:59 |
| clarkb | we're going to mitigate by resetting all of the podman system state during the next weekend restarts | 17:59 |
| gouthamr | ouch, if there's a podman bug you'd raise, let me know.. | 18:00 |
| gouthamr | ^ gmaan hope this runtime update is going well - this would mean that we start seeing py3.14 jobs be voting on master | 18:01 |
| gouthamr | we're a bit over, any other notes for the minutes today? | 18:01 |
| gmaan | yeah, I removed the WIP from this and it is good to go https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/1001704 | 18:02 |
| gouthamr | ++ | 18:02 |
| gouthamr | ty for working on that | 18:02 |
| mnasiadka | So off it goes, I’ll ignore the super-nit ;-) | 18:02 |
| gouthamr | haha, it's in bold, and hard to ignore | 18:02 |
| gouthamr | let's wrap it up here.. ty all for attending! | 18:03 |
| gouthamr | #endmeeting | 18:03 |
| opendevmeet | Meeting ended Tue Sep 22 18:03:10 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-09-22-17.00.html | 18:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-09-22-17.00.txt | 18:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-09-22-17.00.log.html | 18:03 |
| mnasiadka | Tell that to my Asperger ;-) | 18:03 |
| dansmith | gouthamr: sorry forgot to tell you I was out, my bad | 18:49 |
| gouthamr | dansmith: ack, np! | 18:51 |
| ildikov | gouthamr: mnasiadka: I just sent out my email to openstack-discuss on the Ops sessions. Sharing the etherpad to collect sessions here too for additional visibility: https://etherpad.opendev.org/p/ops-devs-qanda-2026 | 20:01 |
| ildikov | It has instructions on how to "fill it out", but please let me know if any of it reads unclear | 20:01 |
| gouthamr | ty ildikov, format seems fine.. i'll keep checking the pad | 22:06 |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily while we upgrade to a new patch release, but should return within a few minutes | 23:02 | |
| ildikov | gouthamr: awesome, thank you! | 23:36 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!