Tuesday, 2026-07-14

opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for freezer project  https://review.opendev.org/c/openstack/governance/+/99716406:42
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for ironic project  https://review.opendev.org/c/openstack/governance/+/99716506:42
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for Oslo project  https://review.opendev.org/c/openstack/governance/+/99716606:42
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for Release Management project  https://review.opendev.org/c/openstack/governance/+/99716706:42
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for requirements project  https://review.opendev.org/c/openstack/governance/+/99716806:42
sean-k-mooneygouthamr: so we used to suport postgress an nova technically nver dropped supprot but the only test we have or have had for a very long time is basic schema validation10:13
sean-k-mooneyi.e. we usethe opertunistic oslo test fixture to do some very basic unit testing of the db level10:14
sean-k-mooneybut we have not doen devstack based testing this decade10:14
sean-k-mooneyso applying the standard openstack maxium "if its not tested its broken"10:15
fricklergouthamr: I have to skip the meeting, will be back tomorrow15:27
gouthamrsean-k-mooney: frickler: ack15:39
gouthamrsean-k-mooney: i agree, i'll think about this a bit more, probably meat for the next tc meeting to discuss how to tackle it across the services15:40
gouthamrtc-members: a gentle reminder that our weekly IRC meeting will be hosted here in ~45 minutes16:14
gouthamrThe agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting16:15
gouthamroops17:02
gouthamr#startmeeting tc17:02
opendevmeetMeeting started Tue Jul 14 17:02:22 2026 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
opendevmeetThe meeting name has been set to 'tc'17:02
gouthamrWelcome 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:02
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee17:02
gouthamr#topic Roll Call17:03
noonedeadpunko/17:03
mnasiadkao/17:03
spotz[m]\o/17:03
gouthamrcourtesy-ping: dansmith bauzas cardoe17:03
gouthamrnoted absence: f r i c k l e r17:03
dansmitho/17:04
gouthamralright, let's get started..17:06
gouthamr#topic Last Week's Action Items17:06
gouthamra couple of things are moving along, slowly.. I started a thread on the mailing list regarding the CEWG, asking for volunteers to add their names to the wiki linked in the governance proposal as well17:07
gouthamr#link https://review.opendev.org/c/openstack/governance/+/994046 (Establish Contributor Experience Working Group)17:07
gouthamrdansmith: cardoe bauzas: can you take a look at this proposal as well, please17:08
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/R5SW5H2LWSRKT4QFNI4RABMNGNUXHR25/ (ML post regarding the group)17:08
gouthamrif it gathers enough eyes, my next step is to merge the proposal and proceed with organizing 17:09
cardoeo/17:10
spotz[m]signed up earlier17:10
gouthamrthe RISC-V SIG proposal is moving along as well.. it was good to specifically note what the group will be focusing on.. the details are in this thread:17:10
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UK2YYNPXC3BGZM3IWHYM6XYNQXHPD57C/ ([riscv-sig] Proposal for a New SIG: Accelerating RISC-V Adoption in OpenInfra)17:10
gouthamrand this proposal:17:10
gouthamr#link https://review.opendev.org/c/openstack/governance/+/98889617:10
noonedeadpunkI really hope this will work out on long run ^17:11
gouthamryeah.. the largest impediment i see is language barriers.. i'm hoping there's some drive to bridge that within the group17:12
noonedeadpunkand timezones, and I have some historical conerns when with simmilar affiliation folks were dissapearing as fast as popping up.17:13
fungidifferences in preferred communication channels/venues have also posed similar challenges in the past17:14
mnasiadkaWell, getting arm64 in current state took a lot of time and investment - so risc-v is going to take at least the same17:14
noonedeadpunkand now we're at point when CI for arm barely has resources afaik17:15
fungi(generously donated by a university)17:15
gouthamrack, this SIG proposal comes with a promise of CI testing resources 17:15
noonedeadpunkand there used to be multiple providers for arm, and I won't expect nobody else to step in with risc-v soonish tbh17:15
noonedeadpunkbut dunno17:15
noonedeadpunkSo I am sceptical about prespectives, but still think we should try out and find out...17:17
spotz[m]I wonder if we could get some from Ampere?17:17
gouthamrgood questions to post on the gerrit review though.. i've asked them to organize on IRC and the mailing list... my excuse was that it'll help them meet others in the community than work in silo.. 17:17
spotz[m]I think they have Arm could be wrong17:17
fungithere may also be a chicken-and-egg challenge with the risc-v resource donation, in that opendev can really only consume resources supplied by an openstack cloud api, and if it's not possible to serve risc-v hypervisor hosts with nova yet...17:18
mnasiadkaNot even mentioning any deployment project or devstack supporting risc-v ;-)17:18
gouthamrack.. so they need to chat with you folks to figure out that part17:18
fungispotz[m]: the challenges with arm resources have proven not to be sourcing the hardware, but finding a place to host it and someone to manage an open stack cloud on top of it17:19
spotz[m]ahh17:19
noonedeadpunkwell... if they do some downstream patch to nova17:20
noonedeadpunkwhich once hardware added to CI they can propose upstream....17:20
noonedeadpunkI think this would be the only way to sort out chicken-egg17:20
fungiwhen we lost our other arm providers it was because the company maintaining the cloud lost interest, or the company providing a place to host the hardware decided to stop17:21
fungi(facility space, power, cooling, networking, warm bodies...)17:22
gouthamrworth a discussion with the SIG? i think you folks have context/knowledge on this that we (the TC) can't provide 17:22
fungiyes, though it's likely they've already worked out how to plumb risc-v servers into nova, in which case it may be fine17:23
mnasiadkaIf there’s a company that wants to source the hardware - StackHPC has a cloud in Iceland and we’re willing to accept that hardware (fund rack space and power) and make it available - just FYI17:23
mnasiadka(We have some old aarch64 nodes that I’m planning to make available for OpenDev, but it might not be a speed improvement over the current university resources)17:24
fungimnasiadka: thanks, i'll keep that in mind for sure17:24
fungiampere has offered us hardware in the past and we've had no way to utilize it short of getting them to donate it to osuosl17:24
gouthamrapart from linking this to the governance proposal, what action items can we take to further this?17:26
fungiget the sig request approved and encourage them to get involved in the parts of openstack where it makes sense to them, and separately figure out if there are options to do first-party/upstream testing but that's likely to take a while to sort out17:27
gouthamrack, sounds good17:28
gouthamrnext action item was regarding x/cursive.. fungi/opendev folks managed to do the project rename, and all the patches we needed to put this deliverable under oslo have merged. tkajinam was fixing it up for the better.. thanks, all around!17:29
fungione outstanding need is that since cursive used to be in the openstack/ namespace once upon a time, there's an old redirect in github to an archived project17:30
fungiso github replication isn't working and we're seeing release job failures reported from trying to set it up17:30
gouthamroh; can we manually undo the redirect?17:30
fungiprobably we can just delete it from both orgs17:30
fungiand then let the usual scripts recreate it in the openstack org as if it's a new project17:31
fungiand it'll get all its current history re-replicated17:31
gouthamrah, nice.. yeah, noone should complain :) 17:31
gouthamranything else to note regarding this?17:32
gouthamrnext action item: Barbican UI: noonedeadpunk took an AI to seed a discussion regarding its revival... ivan anfimov reached out to me and i asked him to look into selenium/playright testing like the manila-ui/barbican-ui maintainers are doing. i mentioned that the suggestion here is to make this solid enough that barbican maintainers can gain confidence in merging their changes17:33
gouthamrthat said, we can't really force anyone to do things they don't want to - that's what the ML thread will hopefully hash out17:34
noonedeadpunkI kinda never did a ML as was /o\ with internal workload....17:35
noonedeadpunkBut I think one of proposals on the table was also to form a separate gerrit group for UI part17:35
gouthamrnp, maybe delegate to the folks working on the changes 17:35
noonedeadpunkAnd I think I saw some activity on patches17:35
noonedeadpunklike this does some testing now at least17:36
noonedeadpunk#link https://review.opendev.org/c/openstack/barbican-ui/+/974693/2217:36
noonedeadpunkI don't see any actuil UI tests though17:37
noonedeadpunkbut at least unit tests should be executed17:37
gouthamryeah; they weren't aware of the new "integration" tests that horizon and manila/barbican teams have started doing.. 17:37
noonedeadpunkfrankly....17:38
gouthamrit's probably a high bar to clear.. but unfortunately, that's the barbican team's concern  from our last meeting.. they don't feel like they know this well enough to review, and tests were one way to feel comfortable17:38
mnasiadkagouthamr: manila and watcher probably? Barbican is the one we’re discussing that doesn’t have that ;-)17:38
gouthamrit was a suggestion, not a mandate17:38
gouthamrmnasiadka: gah! yes, sorry manila/watcher17:38
noonedeadpunkmy prespective, is that if they do work, and unit tests are covering good chunk of code, it's anyway way better then fully mulfunctioning code from 7 years ago17:39
noonedeadpunkwhich was just a cookie-cutter17:39
noonedeadpunk#link https://opendev.org/openstack/barbican-ui/commits/branch/master17:39
noonedeadpunklike really17:39
gouthamrhmm, the goal was to earn the team's trust in the process? 17:40
noonedeadpunkI'd say it really depends if they're even interested in maintenance of the project and UI17:41
noonedeadpunkor it should potentially change ownership17:41
noonedeadpunkbecause it's totally fair if they just don't want to deal with horizon plugin17:42
gouthamryeah, share that angle on the ML discussion - not opposed to it17:42
noonedeadpunkas eventually it never existed in a working state17:42
gouthamrif we're putting together a new team, we're starting quite early for the Indri cycle, and it's a good thing to hash out all the paperwork17:43
noonedeadpunk++17:43
noonedeadpunk(or maybe it's a horizon team, dunno)17:43
noonedeadpunkbut will initiate a discussion17:43
gouthamrty noonedeadpunk 17:44
gouthamra final action item itch i want to scratch17:44
gouthamr#link https://review.opendev.org/c/openstack/governance/+/995834 (Update Telemetry release liaison)17:44
gouthamrwe're not as responsive as we meant to be on these sort of changes17:45
gouthamri wonder if you have suggestions here17:45
gouthamra "project-update" thing needs two RC votes.. but this hasnn't been able to gather them for over two weeks17:45
mnasiadkaRC?17:46
fungiroll-call17:46
spotz[m]roll call17:46
dansmithroll call17:46
gouthamrroll call17:46
dansmithoh I thought we were doing the rap song thing17:46
gouthamr:D17:47
mnasiadkaWell, now it has 2, cardoe probably just missed the proper button )17:47
mnasiadka(So it’s like 3)17:47
noonedeadpunklol17:47
noonedeadpunkdoe it work like that ?:D17:47
mnasiadka(I love the abbreviations when my mind just tells me ,,remote control’’ instead of ,,roll call’’)17:48
gouthamrhaha, ty it shouldn't need my ranting though.. :) i don't want this to block the project or release teams as was pointed out when we migrated all the release liaisons to the governance repo17:48
mnasiadkaBut maybe that’s the time of the day to blame17:48
fungii always think "release candidate"17:48
mnasiadkafungi: that’s the second on my list17:48
gouthamrthere's a Indian whiskey brand called RC, just like there's one called Indri17:49
gouthamrit is not the time of day for me to be thinking about that17:49
fungiremind me when we get to indri rc17:49
mnasiadkaWell, it might be in my part of the world ;-)17:49
mnasiadkagouthamr: maybe it’s just me, but such patches really only need PTL/cores of the given project to give their +1s17:51
gouthamrno i agree17:51
gouthamrso, if we need that sorta change, i can propose it to our house rules:17:51
gouthamr#link https://governance.openstack.org/tc/reference/house-rules.html17:51
mnasiadkaMaybe we just need an implementation of PTL-Approved vote from openstack/releases ;-)17:52
gouthamrhaha, eyeballs are usually enough.. that stuff has too many edge cases17:52
gouthamralright, that's a wrap for ongoing stuff17:53
gouthamrwas anyone else working on anything to note today?17:53
gouthamr#topic TC Vision 17:54
gouthamrokay, delayed this a couple of weeks for the lack of time, but, i'd like to kick something off here and follow up outside of this meeting17:54
gouthamryou all are aware of the motivation here.. so i'll get to the specifics:17:55
gouthamra past TC used a visioning framework that TheJulia, fungi and others pointed me to.. and i did some homework with it.. 17:55
gouthamrand i'd like to begin some scatter-gather of thoughts/ideas with you and the rest of the community17:56
gouthamrthe ask is that we reflect on a couple of things:17:57
gouthamr(a) a "prouds" list: What has OpenStack and the TC accomplished that you're proud of? 17:57
gouthamr(b) Hot pen vision: Write as if it's 2031 and you've already arrived. What does OpenStack look like? What has the TC achieved? Be vivid, be specific, be ambitious. Don't self-edit.17:57
gouthamrdoing this should be quick, and not take too long - the idea is for raw ideas to surface, and don't bother self-correcting17:58
fungii'll note that when the past tc did this as an in-person workshop, we scribbled these ideas onto sticky notes and stuck them on a wall/window, then organized and grouped them thematically17:59
gouthamrit'll defeat the purpose if you spent too much time on it honestly :) 17:59
gouthamr_MY_ goal is to collect these thoughts from you (and the community) and distill that for a deeper discussion17:59
gouthamryes, think of this as async/poor mans visioning - "zingtrain goutham" version - we can have high touch/sync calls when we've done this individually18:00
gouthamrwe've just crossed the hour, and i'll have to wrap it up here.. 18:01
gouthamrbut, please look for my email on openstack-discuss, and my goal was to set a bug in your ear18:01
fungithe point of the sticky notes, for me, is that it helped reinforce the ideas should be something you could summarize in a few words/short sentence18:01
gouthamr^ ah, great point18:02
gouthamri expect the "prouds" to be like a bullet list, short and sweet18:02
gouthamr- i'm proud we did DCO18:03
gouthamr- i'm proud we created a SLURP model18:03
gouthamr...18:03
spotz[m]I'm sad we tried to get rid of names:(18:03
gouthamrhaha, we didn't though.. glad we're still polling and seeking names18:04
gouthamrbut i understand what you mean18:04
gouthamralright, we're several minutes over18:05
gouthamranything to add to $topic?18:05
gouthamror for the minutes today?18:05
gouthamralright, thank you all for joining!18:06
gouthamrthis meeting returns next week.. 18:06
gouthamr#endmeeting18:07
opendevmeetMeeting ended Tue Jul 14 18:07:02 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:07
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-14-17.02.html18:07
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-14-17.02.txt18:07
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-14-17.02.log.html18:07
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Allow liaison changes without roll call votes  https://review.opendev.org/c/openstack/governance/+/99728418:30
opendevreviewMerged openstack/governance master: Update Telemetry release liaison to Emma Foley  https://review.opendev.org/c/openstack/governance/+/99583418:56
opendevreviewDouglas Viroel proposed openstack/governance master: Seed security liaison data from VMT wiki  https://review.opendev.org/c/openstack/governance/+/99656319:05

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!