| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Drop expired extra-acs, re-propose election officials https://review.opendev.org/c/openstack/governance/+/1014853 | 06:37 |
|---|---|---|
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Add SIG chairs as extra-acs https://review.opendev.org/c/openstack/governance/+/1014854 | 06:37 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Archive the First Contact SIG https://review.opendev.org/c/openstack/governance/+/1014855 | 06:37 |
| opendevreview | Artem Goncharov proposed openstack/governance master: Add Rust use case for a new IAM service https://review.opendev.org/c/openstack/governance/+/998652 | 09:51 |
| gouthamr | tc-members: our weekly irc meeting will be hosted here in ~30 minutes | 16:31 |
| gouthamr | the agenda is here: https://etherpad.opendev.org/p/openstack-technical-committee-meeting | 16:32 |
| cardoe | I'll be running this week's meeting | 16:37 |
| cardoe | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Nov 10 17:00:12 2026 UTC and is due to finish in 60 minutes. The chair is cardoe. 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 |
| cardoe | 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 |
| cardoe | Today's meeting agenda can be found at https://etherpad.opendev.org/p/openstack-technical-committee-meeting | 17:00 |
| cardoe | #topic Roll Call | 17:00 |
| gouthamr | o/ hello :) | 17:00 |
| dansmith | o/ | 17:01 |
| cardoe | noted absence: g o u t h a m r, s p o t z, m n a s i a d k a | 17:01 |
| gouthamr | cardoe: ty for getting us started - i was asking for help with next week though - not today's meeting .. but happy to sit in :D | 17:01 |
| ChristianBerendt[m] | o/ | 17:01 |
| cardoe | Whelp. Practice run for me! | 17:01 |
| frickler | \o | 17:01 |
| gouthamr | context: OpenInfra Day NA is next week (Nov 17) | 17:02 |
| gouthamr | all good cardoe; ty for doing it! | 17:02 |
| cardoe | courtesy-ping: gtema, noonedeadpunk | 17:02 |
| gtema | o/ | 17:03 |
| noonedeadpunk | o/ | 17:03 |
| cardoe | #topic Last week's action items | 17:03 |
| cardoe | None have really carried over | 17:04 |
| cardoe | #topic New OpenInfra AI policy | 17:04 |
| cardoe | #link https://openinfra.org/legal/ai-policy | 17:05 |
| cardoe | Anyone have any comments they would like to bring up? | 17:06 |
| cardoe | It's been a recent hot topic so surprised that there's no concerns. | 17:07 |
| gouthamr | i think there are several concerns | 17:07 |
| gouthamr | from prior comments, and some agreed-upon aspects that are not yet in that resolution | 17:08 |
| frickler | worth to mention https://review.opendev.org/c/openstack/governance/+/1012080 in that context | 17:08 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1012080 | 17:08 |
| cardoe | That's the link I was looking for. | 17:09 |
| gouthamr | (that was supposed to be associated with the topic) | 17:09 |
| gouthamr | JayF: got us started with this | 17:09 |
| gouthamr | and i plan to take a stab at adding the missing bits | 17:09 |
| cardoe | One thing I think worth mentioning is that folks using LLMs with security bugs. As soon as you run that issue through a non-local LLM. You've effectively disclosed that vulnerability. | 17:10 |
| fungi | yes, we've gone back and forth on that point with people | 17:11 |
| dansmith | TBH, I think it's going to be hard to not do that | 17:11 |
| dansmith | like I agree, but there's also a lot of "fight fire with fire" talk about addressing the tidal wave with the "best tools available" | 17:12 |
| fungi | using a remote llm service to compose a vulnerability report or with an mcp integrated into your ide when developing patches effectively discloses the details to a third party | 17:12 |
| fungi | if we're going to allow it, we need to be clear that we're okay with that risk | 17:12 |
| dansmith | it totally is disclosing, what I'm saying is: | 17:13 |
| fungi | as well as the risk that some llm services may effectively disclose things they know to other users of the service (e.g. get trained on the things they're prompted by) | 17:13 |
| dansmith | I think that whether we're okay with it or not, and whether we bless it or not, it is and will happen | 17:13 |
| cardoe | With every new technological invention, it's own pandoras box is opened. | 17:13 |
| noonedeadpunk | I'd say that'r aroudn 90% chance that this vulnarability was found with online LLM | 17:13 |
| noonedeadpunk | So it was not private to begin with... | 17:14 |
| cardoe | Yeah I agree with dansmith. It's going to happen. What I think is worth doing is pointing that out explicitly in our AI doc. | 17:14 |
| fungi | and 50% of those are "did you know that if you obtain someone's login credentials you can boot a vm in their account, up to their allowed quota?!?" | 17:14 |
| dansmith | I also think it's fine if we officially don't allow it for a CYA reason, as long as we're clear that it will happen anyway | 17:14 |
| dansmith | and I think it will be hard to track down such a disclosure to a person or tool that was used | 17:15 |
| JayF | fungi: dansmith: cardoe: Where I want clarity is for contract/internal LLMs | 17:15 |
| JayF | I can agree that public LLM + security vuln is a form of disclosure | 17:15 |
| dansmith | noonedeadpunk: right, that's why I mean by the "fire with fire"... most of these are coming from an LLM somewhere anyway :) | 17:15 |
| JayF | but if someone has an internal, but shared, cluster (as I understand IBM may have?), this seems like a middle ground that is more okay | 17:15 |
| clarkb | one thing to keep in mind is that people have gotten fairly confrontational over onerous reporting requirements or lack of feedback on reported issues. To the point of dropping rce 0 days against software | 17:15 |
| clarkb | so if you say "you cannot use these tools" then people are probably just as likely to 0 day you as they are to report it the way you want them to | 17:16 |
| dansmith | clarkb: yeah, good point | 17:16 |
| cardoe | clarkb: So to me it's more of a "be aware that using a third-party LLM is equivalent to discussing the vulnerability with a third-party" | 17:17 |
| noonedeadpunk | that's fair note to have | 17:17 |
| fungi | we effectively can't prevent "researchers" from using whatever tools they like when reporting suspected vulnerabilities to us, any guidance we provide is going to be to our project maintainers and downstream users/distributors later in the process anyway | 17:18 |
| dansmith | I think there is also a nuance here: | 17:19 |
| dansmith | pasting the content of the private bug into a chat tool and saying "fix it" is different than giving it specific directions like "change operation Y to ensure that condition X is met before proceeding" | 17:20 |
| JayF | ++ (oh no, not again) | 17:21 |
| cardoe | Well two random atoms decided to collide in the universe... aka jay and dan agreed and the convo has slowed | 17:22 |
| cardoe | so let's move on | 17:22 |
| frickler | but is it really? afaict we treat the proposed fix with the same confidentiality as the bug report? | 17:22 |
| cardoe | frickler: I waited a bit to see if more came in but will move on | 17:23 |
| cardoe | #topic Gate Health | 17:23 |
| cardoe | Anyone have a good check on that? | 17:25 |
| cardoe | #link https://github.com/tox-dev/tox/issues/4357 | 17:26 |
| cardoe | Was closed which was the tox regression | 17:26 |
| cardoe | We've moved past that but I know a number of projects pinned | 17:26 |
| cardoe | There's a lot of things running right now and not much of an uptick in issues I've seen | 17:27 |
| clarkb | from the infrastructure side of things we've got ~2-3 issues of varying annoyance impacting jobs. One is a cloud region (you may be able to help with that cardoe I pinged Dan With on Matrix but haven't heard back yet) that seems to lose networking post boot for ~2 minutes which causes jobs to retry when ansible can't gather facts. ANother is same cloud another region we may have | 17:27 |
| clarkb | evidence of occasional disk image corruption causing the git repo cache to be invalid for some repos occasionally. Both are weird and I think we're sort of running out of idaes for how we can debug this as users. | 17:27 |
| clarkb | There is also the centos 10 stream zswap issue that got "fixed" by disabling zswap on that platform in devstack | 17:27 |
| cardoe | I've raised your comments to folks. | 17:29 |
| cardoe | Alright well moving on then. | 17:30 |
| cardoe | #topic TC Tracker | 17:30 |
| cardoe | #link https://tinyurl.com/os-tc-dash | 17:31 |
| cardoe | So we've got a few things still out there. | 17:31 |
| cardoe | #link https://review.opendev.org/c/openstack/governance/+/998652 | 17:31 |
| cardoe | gtema's proposal has been reborn for a new IAM service | 17:32 |
| cardoe | #link https://review.opendev.org/c/openstack/governance/+/992765 | 17:32 |
| cardoe | We've been discussing tested runtimes for clients and libraries | 17:32 |
| cardoe | And there's a few where we are refreshing the SIG chairs and membership | 17:33 |
| cardoe | #link https://etherpad.opendev.org/p/tc-2027.1-tracker | 17:34 |
| *** gmaan is now known as gmaan_afk | 17:34 | |
| cardoe | Along those lines with the SIGs, we're looking this cycle to refresh them and their status | 17:34 |
| cardoe | #link https://governance.openstack.org/tc/reference/technical-vision.html | 17:34 |
| cardoe | clarkb and gouthamr are spearheading an update to the technical vision document which I'm sure they'd appreciate feedback on | 17:35 |
| gouthamr | barely; but, that's a good call out for me to get back to that work | 17:35 |
| cardoe | #link https://governance.openstack.org/tc/goals/proposed/remove-eventlet.html | 17:35 |
| gouthamr | on the SIGs especially, we need someone to do some light dusting, and sunset SIGs that are inactive | 17:36 |
| cardoe | Good call out. | 17:36 |
| JayF | Honestly, we might want to sunset the security sig or more clearly integrate it with the VMT | 17:37 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/1014855 (Archive the First Contact SIG) | 17:37 |
| JayF | two separate stacks of security org made more sense when we had more people milling around doing security work "unofficially" | 17:37 |
| gouthamr | diablo_rojo could use your eyes on the FCG change above ^ | 17:37 |
| fungi | JayF: the vmt was considered part of the security sig, but yes now the vmt is essentially the whole of the active security sig participants most of the time | 17:38 |
| gouthamr | but, wouldn't we want to keep it separate so we can encourage folks joining and helping with guidelines? | 17:38 |
| gouthamr | and any non-embargo related activities | 17:38 |
| fungi | those would be my questions: do we want to encourage security efforts outside the vmt's activities, and if so do we think keeping a sig around is too much effort if it doesn't actually bring them in? | 17:39 |
| JayF | TBH, I think those are theoretical questions. The reality is that there's been minimal engagement outside of VMT folks. I am not saying we shouldn't have an entrypoint, but if it's the same people, just call it one thing instead of two | 17:40 |
| JayF | I think of the work Sofia did to migrate OSSNs: that could probably have been considered technically under security sig or something, but reality is it was just a thing that needed doing, so I asked someone to do it | 17:40 |
| JayF | I just want less empty front doors for people to knock on and be disappointed; and that's kinda how I view inactive SIGs | 17:41 |
| fungi | we also have a separate problem, wherein the vmt's authority is implicit not explicitly delegated from the tc. we made it part of a sig to sort of try to ignore that | 17:41 |
| gouthamr | VMT's front door is like a speakeasy | 17:41 |
| fungi | being in a sig makes the vmt's activities at least an official part of openstack | 17:42 |
| gouthamr | i kinda like that framing: VMT is a specialized part of the wider security effort | 17:42 |
| JayF | Again I point at: what wider security effort? Activities not happening in VMT are generally happening at project team level | 17:43 |
| JayF | the structure we have should reflect us, rather than us trying to maintain a structure for what we wish we were | 17:43 |
| gouthamr | i was hoping that we'd do the threat modeling, writing guidelines, documenting RBAC etc through the SIG, publicly, and loosely organizing from volunteers that are interested in these various efforts | 17:43 |
| fungi | in the past the security sig has engaged in goals like secure rbac and privsep, or pop-up efforts like image encryption | 17:43 |
| gouthamr | i couldn't think of any other logical place for that sort of work | 17:43 |
| gouthamr | cardoe: i pinged ralonsoh again in the past week to get an update on the privsep goal | 17:46 |
| cardoe | It's a lot of overlap and would the membership be different? | 17:46 |
| cardoe | #link https://governance.openstack.org/tc/goals/selected/migrate-to-privsep.html | 17:47 |
| cardoe | Did we get any updates? | 17:47 |
| gouthamr | nah :| i'm struggling with this | 17:47 |
| gouthamr | i'm kinda wondering if we should change goals to require a group of people | 17:47 |
| fungi | tie them more explicitly to the pop-up team concept? | 17:48 |
| gouthamr | yes. it feels unreasonable to expect a single goal champion to always be available and caring/feeding for a monstrously large effort sometimes | 17:48 |
| gouthamr | i'll propose that, and see if you think it is reasonable | 17:49 |
| cardoe | That makes sense | 17:50 |
| cardoe | I'll move us along. | 17:50 |
| cardoe | #topic Open Discussion | 17:50 |
| cardoe | The only item here is to be aware of elections coming up and shorter time lines | 17:51 |
| gouthamr | yes; i haven't had a chance to catch slaweq/ianychoi and check if they'd like to continue as election officials | 17:52 |
| gouthamr | ChristianBerendt[m]: i proposed https://review.opendev.org/c/openstack/election/+/1014592 | 17:52 |
| gouthamr | ^ it sets up directories for the elections for all the PTL lead teams that exist today | 17:53 |
| gouthamr | i think we ought to get started with the election config and put up the dates asap so we can let people plan.. | 17:53 |
| gouthamr | we can chat about this on #openstack-election if you'd like | 17:54 |
| gouthamr | if there are any other volunteers to help coordinate elections, please join that channel | 17:54 |
| fungi | #link 2027 OpenInfra Foundation Individual Member Representative nominations are open. https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thread/3GWDHFR6VX56EZYVLE6ISIWP5ZPKI4WP/ | 17:55 |
| fungi | those too | 17:55 |
| gouthamr | (i'll put out a call for election official volunteers on the ML as well) | 17:55 |
| gouthamr | ah; sorta close in timeline | 17:56 |
| gouthamr | 2027 Board elections will "be held Monday, January 11, 2027 at 00:01 UTC through Friday, January 15, 2027 at 23:59 UTC" | 17:56 |
| gouthamr | lets plan this further in #openstack-election | 17:58 |
| gouthamr | next week is OpenInfra NA | 17:59 |
| gouthamr | cardoe has graciously agreed to run the meeting on Nov 17th | 18:00 |
| gouthamr | is anyone here planning to be at the event? | 18:00 |
| fungi | i think diablo_rojo is? | 18:00 |
| gouthamr | ah neat | 18:00 |
| cardoe | Well we're at time as well. | 18:01 |
| cardoe | #endmeeting | 18:01 |
| opendevmeet | Meeting ended Tue Nov 10 18:01:21 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-11-10-17.00.html | 18:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-11-10-17.00.txt | 18:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-11-10-17.00.log.html | 18:01 |
| cardoe | Thanks all. | 18:01 |
| gouthamr | thanks cardoe! | 18:01 |
| fungi | s p o t z was planning to be there as well, i thought | 18:02 |
| fungi | ah, yeah during last week's meeting in #openinfra-diversity she confirmed as much | 18:03 |
| *** gmaan_afk is now known as gmaan | 19:04 | |
| opendevreview | Brian Haley proposed openstack/governance master: Deprecate networking-sfc https://review.opendev.org/c/openstack/governance/+/1014968 | 20:01 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!