| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Add devstack-plugin-lustre to QA https://review.opendev.org/c/openstack/governance/+/987314 | 03:28 |
|---|---|---|
| mnasiadka | I found https://review.opendev.org/c/openinfra/ansible-role-refstack-client/+/962128 which is part of retire-refstack and is blocking https://review.opendev.org/c/openstack/project-config/+/962116 | 06:51 |
| mnasiadka | spotz[m], gouthamr: I think you’re part of refstack-core Gerrit group and could merge this? | 06:52 |
| spotz[m] | I can when I stop for gas | 13:58 |
| gouthamr | mnasiadka: ack, done | 14:48 |
| mnasiadka | gouthamr: thanks | 16:15 |
| gouthamr | tc-members: a (late) gentle reminder that our weekly IRC meeting will be hosted here in ~30 minutes: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting | 16:29 |
| cardoe | it's been a week already? | 16:30 |
| cardoe | I haven't even caught up from last week's todos | 16:30 |
| cardoe | I need you to pump the brakes on the speed of time.... kthxbai | 16:30 |
| gouthamr | :D i wish | 16:31 |
| mnasiadka | Hmm, the refstack retirement is one thing, but openinfra/python-tempestconf needs to be rehomed to some other group - did we ever discuss that and found that group? | 16:41 |
| gouthamr | not that i recall | 16:45 |
| gouthamr | that tool is widely used outside of refstack, but i don't know how much it matters to be under the openstack-qa team, maybe gmaan has an opinion.. | 16:47 |
| gouthamr | an advantage if it is rehomed is that it can get the same release treatment and github mirroring that others have under the openstack/* namespace | 16:47 |
| mnasiadka | I have a feeling that it was renamed from openstack/python-tempestconf to openinfra/python-tempestconf in the past (cc: clarkb) | 16:49 |
| clarkb | yes I think it was openstack/python-tempestconf and got renamed to openinfra/python-tempestconf | 16:51 |
| clarkb | I can probably find the change for that | 16:51 |
| mnasiadka | But I agree openstack-qa sounds like a good home to that, if gmaan agrees | 16:52 |
| mnasiadka | (Too many agreements in one line) | 16:52 |
| clarkb | https://opendev.org/opendev/project-config/src/branch/master/renames/20200612.yaml#L6-L7 then https://opendev.org/opendev/project-config/src/branch/master/renames/20211015.yaml#L34-L35 | 16:52 |
| clarkb | we've already renamed it twice do we really need to rename it a third time back to its original name? | 16:53 |
| clarkb | (I get the sense that no one really cares about it, maybe it is better off being retired than continuing to pass it around like a hot potatoe creating more work for the infra team. Just today I spent qutie some time trying to determine if the repo was broken in Gerrit) | 16:54 |
| gouthamr | it's fairly active afaict | 16:55 |
| clarkb | it can be active while no one cares enough to actually "own" it | 16:56 |
| gouthamr | not seeking more work for infra, but, the hot potato thing here was interop | 16:56 |
| gouthamr | it was a board program, not the TC's | 16:56 |
| gouthamr | so we're trying to get things cleaned up for the board? | 16:57 |
| clarkb | (as an aside I wonder if the openstack/python-tempestconf -> openinfra/python-tempestconf redirect will handle being renamed back to openstack/python-tempestconf may be something we need to test first if we go down that path) | 16:58 |
| mnasiadka | Well, I just wanted to get refstack cleaned up before somebody asks me another time about it ;) | 16:58 |
| clarkb | gitea does that for us so depends on whether gitea can handle it I think | 16:58 |
| gouthamr | sorry to pause this, | 17:00 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue May 5 17:00:54 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 |
| dansmith | o/ | 17:01 |
| gouthamr | courtesy-ping: noonedeadpunk, frickler, spotz[m], cardoe, mnasiadka, bauzas | 17:02 |
| bauzas | o/ | 17:02 |
| frickler | \o | 17:02 |
| cardoe | o/ | 17:03 |
| mnasiadka | o/ | 17:03 |
| gouthamr | alright, no noted absences.. let's get started | 17:05 |
| gouthamr | #topic Last Week's Action Items | 17:05 |
| gouthamr | mnasiadka cardoe: you had one around updating the Ansible SIG's chairs | 17:06 |
| gouthamr | through an email notification to openstack-discuss | 17:06 |
| noonedeadpunk | o/ | 17:06 |
| cardoe | Yes. I haven't done that. | 17:06 |
| cardoe | That was one of the things that was still on my todo from last week. | 17:06 |
| mnasiadka | I have just sent that | 17:07 |
| gouthamr | wow | 17:07 |
| mnasiadka | A very long mail | 17:07 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/NOK24Z4VKHH4XCVD5A7NYKZT3NH3WMDJ/ | 17:07 |
| gouthamr | thank you for starting that | 17:08 |
| noonedeadpunk | ++ awesome, thanks for it! | 17:08 |
| cardoe | Thank you! | 17:09 |
| gouthamr | good stuff, we can discuss this again next week | 17:09 |
| gouthamr | there were a couple more items on cardoe's pile.. the question about importlib.metadata vs pbr - don't know if you needed to start a thread on the ML for this | 17:09 |
| cardoe | I will. | 17:09 |
| gouthamr | and you meant to discuss "manager" role doc in Keystone.. guess that happened in the policy_group meeting yesterday | 17:10 |
| gouthamr | somewhat related was the thread that gmaan started on a global 'reader' persona.. | 17:10 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ZEKOWEMLY6F2RFFXVD37QRQPMB35H5PR/ ([policy][tc] RBAC global auditor (reader)) | 17:11 |
| gouthamr | the discussion will continue on the thread, the last update was seeking clarity on the use cases and direction | 17:12 |
| noonedeadpunk | global reader is amazing thing I was annoying gmann with in Vancouver :D | 17:12 |
| noonedeadpunk | happy to see some traction and that there're other orgs looking for it as well | 17:12 |
| cardoe | Yeah I think this is also in my court to submit something to the ML and patches to keystone | 17:12 |
| gouthamr | from the policy_group meeting yesterday, the original design with scopes tried to address these different use cases.. | 17:13 |
| gouthamr | ack, ty both.. it'd make sense to flush out the design on gerrit | 17:13 |
| gouthamr | this will not be a part of the SRBAC goal however, because like gmaan noted to the ML yesterday, that goal is heading towards wrapping up the "project" scoping correctly.. | 17:15 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/NYJOVFQ6FTXL7DKSOFIQJMOMX7R7CXLE/ ([policy][cinder][tacker][aetos][aodh][barbican] Removal of enforce_scope impact) | 17:15 |
| gouthamr | any concerns there? | 17:15 |
| gouthamr | next up we have the venus and vitrage transitions | 17:18 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/981959 (Retire Venus Project) | 17:19 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/PGT5EUDSNEILHHA2GY6DOQ7FRFIXHTC7/ ([venus][tc] Retirement of the Venus project) | 17:19 |
| gouthamr | it's been a month since the post went out, and we haven't heard any concerns on the ML | 17:19 |
| gouthamr | noonedeadpunk: think we can proceed with the patches now | 17:19 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/982869 (Deprecate vitrage project) | 17:20 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/QS3TFDCMT5ZBSNFXUVYGLXTKPKIOQDOZ/ ([vitrage][tc] Deprecation of the Vitrage project) | 17:20 |
| gouthamr | ^ same with vitrage's deprecation | 17:20 |
| gmaan | noonedeadpunk: i know, sadly we did not progress on that. | 17:20 |
| noonedeadpunk | gmaan: to be fair, I also lacked time to push this forward afterwards... | 17:21 |
| gouthamr | anything to note regarding venus, vitrage? | 17:21 |
| noonedeadpunk | I think it's time to proceed with deprecation/retriement | 17:22 |
| gouthamr | ack, thank you.. | 17:22 |
| gouthamr | #link https://review.opendev.org/q/topic:%22retire-venus%22 (Venus cleanup patches) | 17:23 |
| gouthamr | ^ guess these would need reviews | 17:23 |
| * gouthamr will take a look after the meeting | 17:23 | |
| mnasiadka | I reviewed the project-config and openstack-manuals ones, so needs another core | 17:24 |
| gouthamr | ty mnasiadka | 17:24 |
| gouthamr | next, we had: | 17:24 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/982062 (Add PQC Migration popup team) | 17:24 |
| gouthamr | just needs more eyes ^ | 17:25 |
| dansmith | just added my RC+1 | 17:26 |
| gouthamr | ty | 17:26 |
| bauzas | RC+1 dittpo | 17:26 |
| gouthamr | i still need to update irc-meetings repo to drop APAC slot | 17:26 |
| gouthamr | missed this from last week | 17:26 |
| gouthamr | ty bauzas | 17:26 |
| gouthamr | that's all the Action Items I was tracking from last week, did anyone else want to note anything? | 17:27 |
| dansmith | yes | 17:27 |
| dansmith | you had an action item to stop calling them AIs, which as far as I can tell you're smashing. thank you :D | 17:28 |
| gouthamr | hahaha, :P i tried | 17:28 |
| gouthamr | #topic TaCT SIG approval for agentic-workflows (bauzas) | 17:28 |
| gouthamr | floor is yours, bauzas | 17:28 |
| * gouthamr added the hashtag on the review, clearly missed it | 17:29 | |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/984958 (Add agentic-workflows to TaCT SIG) | 17:29 |
| gouthamr | bauzas ? | 17:30 |
| bauzas | well, I don't know what to say | 17:30 |
| bauzas | I just want to know whether we would accept this project or not | 17:31 |
| bauzas | any concerns, questions ? | 17:31 |
| gouthamr | no concerns from me i think, but, it looks like the contentious parts would be regarding the contents of this repository | 17:32 |
| gouthamr | from what i recall, your intention is to make it abundantly clear that this isn't imposing rules on the community, but serves to assist use of agentic tools in code development | 17:33 |
| bauzas | at the moment, we have some a lot of https://review.opendev.org/q/project:openstack/agentic-workflows+status:open | 17:34 |
| gouthamr | #link https://review.opendev.org/c/openstack/agentic-workflows/+/985082/1/README.md | 17:35 |
| bauzas | I also provided https://review.opendev.org/c/openstack/governance/+/986765 but given the concerns, I'll abandon it | 17:36 |
| gouthamr | we'll talk about that one separately? | 17:36 |
| dansmith | I just RC+1d the repo one | 17:36 |
| bauzas | okay thanks | 17:37 |
| gouthamr | speaking for myself, i feel the TaCT SIG needs to adopt this and feel liable towards: | 17:37 |
| gouthamr | (a) what the project does (b) how it is governed | 17:37 |
| bauzas | that's good questions | 17:38 |
| bauzas | if we agree this, then we would discuss about those by #openstack-agentic-workflows | 17:38 |
| gmaan | I might have missed the discussion but it is also good fit as TC repo | 17:39 |
| gouthamr | that said, i don't think i've a TC objection towards it.. my suggestion would be to try hard at every juncture to note that this isn't imposing new workflows on the community. It's about "consider this if it helps" | 17:39 |
| dansmith | gouthamr: the SIG chair +1d right? | 17:39 |
| gouthamr | yes | 17:39 |
| dansmith | I think having it be not under the TC helps it be viewed as "a resource but not a mandate" personall | 17:39 |
| bauzas | this project would only be for having some skills | 17:39 |
| bauzas | dansmith: correct | 17:39 |
| gmaan | yeah, that is good point | 17:40 |
| bauzas | but I'd rather prefer that we have a project for discuss those | 17:40 |
| clarkb | bauzas: it might also be useful to document pitfalls and traps. Things like considering whether you actualyl want copilot cli to have access to all of your github orgs when you think you're running it locally. And agent sandboxing etc | 17:40 |
| gmaan | bauzas: ++ | 17:40 |
| clarkb | basically one portion to capture practical considerations for doing agentic work safely and another how to do it effectively | 17:40 |
| gouthamr | i'd love to work on the agent sandboxing thing, personal itch to scratch | 17:40 |
| bauzas | instead of each of each trying to see to use LLMs | 17:40 |
| bauzas | clarkb: that's a good point too, indeed | 17:41 |
| clarkb | (I think both pieces are important as only one of the other is an incomplete set of tooling) | 17:41 |
| bauzas | (I mean, having some way to have a sandbox) | 17:41 |
| bauzas | anything else to discuss ? | 17:43 |
| gouthamr | nope, tc-members: please vote there.. i've added a "project-update" hashtag on this | 17:44 |
| gouthamr | https://governance.openstack.org/tc/reference/house-rules.html#other-project-team-updates | 17:44 |
| gouthamr | so it can merge as it gains the necessary votes, but, i'd hate to do it early if there are disagreements that we want to air out.. | 17:45 |
| gouthamr | bauzas: do you want to chat about your goal proposal? | 17:46 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/986765 (Add AGENTS.md community goal proposal) | 17:46 |
| bauzas | gouthamr: given all the concerns, I'll abandon it | 17:46 |
| gouthamr | ack, thanks for proposing it, and giving people food for thought.. | 17:46 |
| bauzas | instead of a governance TC goal, we could find a way to get our projects to be discussing with the SIG if they want | 17:47 |
| bauzas | (I mean, the TaCT SIG, or at least the agentic-workflows community if they want) | 17:47 |
| bauzas | do people would prefer to create another SIG instead of this goal ? | 17:48 |
| gouthamr | nah, looks like you have an IRC channel? | 17:48 |
| bauzas | or, as I said, just discussing with the agentic-workflows community ? | 17:48 |
| gouthamr | oh not an official channel | 17:49 |
| bauzas | we have #openstack-agentic-workflows at the moment, but as I said, I'll make sure that we have logs for it | 17:49 |
| bauzas | yeah, this is not a official channel atm because https://review.opendev.org/c/openstack/governance/+/984958 isn't yet accepted | 17:49 |
| bauzas | we could create another channel or discussing as a SIG, I don't know exactly | 17:50 |
| gouthamr | hmm, i think for something that's expected to promote informal collaboration, we don't need too much of a formality - that's my view.. | 17:50 |
| bauzas | if we don't have a TC goal, I'm fine but I don't want our service projects to create wrong AGENTS.md or CLAUDE.md | 17:50 |
| bauzas | (that was why I proposed a goal, but I agree, this shouldn't be mandatory) | 17:51 |
| gouthamr | :P my view, at one point during the review was that the project shipping one would be wrong | 17:51 |
| gouthamr | it'd break my workflow for one.. and i'd shake my fist at you.. | 17:52 |
| bauzas | yeah I saw your questions | 17:52 |
| bauzas | gouthamr: oh wait, really ? :( | 17:52 |
| gouthamr | but, as someone trying to learn nova's code base, conventions etc, i can't thank you enough for sharing more of the sausage making | 17:52 |
| bauzas | gouthamr: yeah, the context is more important than skills honesltu | 17:53 |
| bauzas | having a way for our contributors to know about our tribal knowledge | 17:53 |
| gouthamr | guess we should do more of this... and a good takeaway seemed to be in improve contributor docs for humans and tools | 17:54 |
| bauzas | anyway, we're late for the meeting | 17:54 |
| bauzas | so let's discuss this in the TaCT SIG gerrit proposal | 17:54 |
| gouthamr | ack, thank you | 17:54 |
| bauzas | or after the meeting | 17:54 |
| gouthamr | anything else for $topic from anyone else? | 17:54 |
| gouthamr | i guess we don't have time today for standing topics.. but, we can roll them into: | 17:55 |
| gouthamr | #topic Open Discussion | 17:55 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2026.2-tracker (2026.2 TC tracker) | 17:56 |
| gouthamr | please do take a look at this, you'll find items moved from the old tracker, and assigned to various folks | 17:56 |
| gouthamr | do post updates on the tracker with anything you'd like to share.. it'd be useful for async catch up | 17:57 |
| mnasiadka | I started work on https://review.opendev.org/q/hashtag:%22inactive-projects-badge%22+(status:open%20OR%20status:merged) - because that was somewhere assigned to me | 17:57 |
| gouthamr | w00t | 17:57 |
| mnasiadka | But I’d probably need guidance for properly testing this :) | 17:57 |
| gouthamr | if only we had a project to mark inactive? :P | 17:57 |
| mnasiadka | Well, it’s going to come | 17:58 |
| gouthamr | :( | 17:58 |
| mnasiadka | Zun has merged my enginefacade patch | 17:58 |
| mnasiadka | But it’s still a one person project... | 17:58 |
| gouthamr | ack, that hurts | 17:58 |
| gouthamr | anything to note regarding the gate? | 17:59 |
| gouthamr | ty for fixing up gerrit yesterday | 17:59 |
| bauzas | - about gater | 18:00 |
| mnasiadka | Somehow Gerrit always gets OOMed by the hypervisor on the EU timezone shift :) | 18:00 |
| gouthamr | launchpad and all other Canonical services have gone back online after a weekend outage - but can be flaky occasionally. | 18:00 |
| bauzas | ooof | 18:01 |
| gouthamr | alright we're over the hour, let's wrap this up | 18:01 |
| gouthamr | thank you all for participating | 18:01 |
| gouthamr | see you here next week! | 18:01 |
| gouthamr | #endmeeting | 18:01 |
| opendevmeet | Meeting ended Tue May 5 18:01:58 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-05-05-17.00.html | 18:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-05-05-17.00.txt | 18:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-05-05-17.00.log.html | 18:01 |
| bauzas | ++ thanks gouthamr | 18:02 |
| gouthamr | clarkb: o/ jlarriba tried to transfer https://launchpad.net/~telemetry-drivers to ~openstack-admins, could you check if you received any notification? | 18:03 |
| clarkb | gouthamr: I did | 18:04 |
| gouthamr | awesome, does he need to do anything else to get openstack-admins to own the group? | 18:04 |
| clarkb | gouthamr: I guess with fungi out this week I should go do that? Let me get logged into launchpad | 18:04 |
| clarkb | gouthamr: I don't think so. I think an openstack-admins member has to go and accept the change | 18:05 |
| gouthamr | yes please, sorry to bother you with it.. we may have a security bug that we're not able to get properly routed to the VMT | 18:05 |
| clarkb | ack I'll get logged in now and see if I can approve that change | 18:05 |
| gouthamr | ++ ty | 18:06 |
| clarkb | gouthamr: I'm comparing to say nova-drivers and in that case openstack administrators is the owner not a member | 18:12 |
| clarkb | this invite is to make openstack administrators a member | 18:12 |
| clarkb | is it possible that we have to be members first? | 18:12 |
| clarkb | I don't do a lot of launchpad stuff and want to avoid accidental disclosures via email for example and want to amke sure it is done right | 18:13 |
| clarkb | I think the risk is low though | 18:13 |
| clarkb | looking at prior emails and https://launchpad.net/~cyborg-team/+members#active I think that fungi accepted openstack-admins as a member of cyborg-team then maybe made openstack-admins the owner then deactivated the membership? | 18:14 |
| clarkb | gouthamr: anyway do you know if there is a process written down or an expected end state? | 18:15 |
| clarkb | ya I see a comment from fungi in the emails for cyborg-team that openstack-admins can readd itself at any time if necessary as it is the owner | 18:16 |
| clarkb | so I think the process must be get added as a member, then escalate to owner, then drop the membership. I'll proceed under that assumption | 18:17 |
| clarkb | gouthamr: ok that is done. I don't appear to have the ability to change the owner to openstack admins | 18:19 |
| clarkb | I think because openstack-admins is merely an approved member not an administator | 18:20 |
| gmaan | yeah, that is flow we followed in past. once openstack-admins is owner then we can remove it from membership. but yes it needs to be administration to change the owner | 18:27 |
| gmaan | it seems tkajinam_ is administration there so he can also change openstack-admins to administration ? | 18:29 |
| gouthamr | oh, :( sorry for being the noisy filter between folks here.. will get have jlarriba check again if he followed: https://documentation.ubuntu.com/launchpad/user/how-to/projects/transfer-project-ownership/ | 18:32 |
| gouthamr | ty clarkb | 18:33 |
| gouthamr | yeah gmaan tkajinam_ could help too, but expect this to be quite late in the day for both of them | 18:34 |
| gouthamr | clarkb: gmaan: the ownership transfer is done now, OpenStack-admins can drop off of that group | 19:46 |
| clarkb | gmaan: do you want to do that? I'm busy with the opendev team meeting currently | 19:46 |
| gouthamr | no rush :) | 19:48 |
| gouthamr | i suspect tkajinam_ jlarriba will take care of the sharing settings to set private security bugs to be routed through the VMT | 19:49 |
| clarkb | gouthamr: gmaan I have deactivated openstack-admins membership in telemetry-drivers now that it is the owner | 20:02 |
| gouthamr | thank you clarkb! | 20:02 |
| gouthamr | interesting: https://www.mirantis.com/blog/a-new-chapter-for-mirantis | 20:58 |
| opendevreview | Goutham Pacha Ravi proposed openstack/project-team-guide master: Add project tracker management guide https://review.opendev.org/c/openstack/project-team-guide/+/987433 | 21:22 |
| opendevreview | Goutham Pacha Ravi proposed openstack/project-team-guide master: Add project tracker management guide https://review.opendev.org/c/openstack/project-team-guide/+/987433 | 21:24 |
| gouthamr | noonedeadpunk: looking at the venus retirement patches | 21:42 |
| gouthamr | noonedeadpunk: i can't +2 any of them.. because we haven't updated the gerrit config to retired.config.. | 21:43 |
| gouthamr | frickler helped me with the monasca repos using his infra core status | 21:44 |
| gouthamr | but, i'm thinking another option is to just adjust the gerrit config to set retired.config in the first step of the retirement process: https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#step-1-end-project-gating | 21:45 |
| gouthamr | doing that will give "tech-committee" +2 powers | 21:45 |
| clarkb | gouthamr: I think the reason for not doing it early is then you're responsible for removing the repo content rather than the project maiantiners | 21:48 |
| clarkb | I guess if those individuals aren't around anymore then that makes sense | 21:48 |
| clarkb | so depends on the specific project retirement if one approach is less work than another | 21:48 |
| gouthamr | yeah :( probably do this only when the TC initiates the retirements | 21:49 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!