| opendevreview | Slawek Kaplonski proposed openstack/election master: Add configuration for 2027.1/"I" elections https://review.opendev.org/c/openstack/election/+/988238 | 13:17 |
|---|---|---|
| opendevreview | Merged openstack/election master: Add configuration for 2027.1/"I" elections https://review.opendev.org/c/openstack/election/+/988238 | 13:59 |
| gouthamr | tc-members: a gentle reminder that our weekly IRC meeting will be hosted here in ~1 hour | 16:00 |
| gouthamr | the agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 16:00 |
| * noonedeadpunk having a public holiday today, so not at the laptop | 16:24 | |
| bauzas | gouthamr: permission to skip the meeting | 16:27 |
| gouthamr | ack noonedeadpunk bauzas | 16:31 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Jun 2 17:00:26 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://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 17:01 |
| gouthamr | #topic Roll Call | 17:01 |
| dansmith | o/ | 17:01 |
| frickler | \o | 17:01 |
| spotz[m] | o/ | 17:01 |
| gouthamr | noted absence: c a r d o e, b a u z a s | 17:01 |
| mnasiadka | o/ | 17:01 |
| gouthamr | noted absence: n o o n e d e a d p u n k | 17:01 |
| gouthamr | that's everyone then! let's get this meeting started | 17:02 |
| gouthamr | i did note that i'd send out an email to deal with extended absence last week, but, i was stuck gathering data | 17:03 |
| gouthamr | i'll try and share that with you folks soon.. i don't know if we can make any progress there apart from nudging and waiting.. but whatever we do, we'll try and make a concerted effort | 17:04 |
| gouthamr | #topic Last Week's Action Items | 17:04 |
| gouthamr | i guess venus/vitrage changes are progressing | 17:05 |
| gouthamr | #link https://review.opendev.org/q/topic:%22retire-venus%22 | 17:05 |
| gouthamr | #link https://review.opendev.org/c/openstack/project-config/+/989144 | 17:06 |
| gouthamr | needs some changes from n o onedeadpunk | 17:06 |
| gouthamr | hmm, nothing really depends on this.. the release team has already removed these from hibiscus | 17:06 |
| gouthamr | but, i am hoping we'll get all this cleaned up by M-2 | 17:07 |
| gouthamr | next, the PTI series has a few tangents.. but we made a lot of progress in the past couple of weeks | 17:07 |
| gouthamr | i am hoping to close out on the remaining this week: | 17:08 |
| gouthamr | #link https://review.opendev.org/q/project:openstack/governance+status:open+owner:stephenfin@redhat.com | 17:08 |
| gouthamr | start here if you haven't looked at this series: https://review.opendev.org/c/openstack/governance/+/988438 | 17:09 |
| gouthamr | it needs at least a few more acks from you spotz[m] dansmith frickler tonyb and no onedeadpunk | 17:10 |
| spotz[m] | looking | 17:11 |
| gouthamr | ty! | 17:11 |
| spotz[m] | Should have them all now | 17:12 |
| gouthamr | \o/ | 17:13 |
| gouthamr | we took an action item to review/merge the release liaison data to projects.yaml last week.. this was done right after the meeting | 17:13 |
| gouthamr | and i asked PTLs/DPL teams to look through and update the data | 17:13 |
| gouthamr | i'll take an action item to review our own docs referring to this, and update anything incorrect or missing there | 17:14 |
| gouthamr | and follow up on the Security liaison additions as well | 17:14 |
| fungi | one of the outstanding questions at this point is how and when they'll be renewed | 17:14 |
| gouthamr | ack, i'll propose the change that PTLs must renew this information often; especially at the start of a cycle. If they don't have accurate information there, the project team's release deliverables, security issues and CI/test configuration changes will stall | 17:16 |
| gouthamr | for DPL teams this is already an expectation.. but, we'll not be removing liaisons when we go through a leadership change. | 17:17 |
| gouthamr | s/leadership/leadership type | 17:17 |
| gouthamr | we can discuss this further on gerrit.. the goal is to make this less painful for everyone | 17:19 |
| gouthamr | that's a wrap on the action items that i see | 17:20 |
| gouthamr | was there anything else you were working on that you'd like to note? | 17:20 |
| gouthamr | alright no new topics today | 17:21 |
| gouthamr | #topic A check on gate health | 17:21 |
| gouthamr | anything worth noting for CI today? | 17:22 |
| mnasiadka | Jammy tempest jobs on 2025.1 got a hit after https://review.opendev.org/c/openstack/requirements/+/990790 was merged - gmaan is working on tagging a version of tempest that should be used for these branches - there’s a discussion on #openstack-qa for those interested | 17:23 |
| gmaan | yeah, I am working on that. sending email about not to do recheck | 17:23 |
| gmaan | tempest gate is also blocked for same reason, python 3.10 testing | 17:24 |
| frickler | requirements dropped py3.10 testing and constraints some time ago already, this seems to be the first that affects tempest | 17:25 |
| gouthamr | ack, so we'll be running with a pin of tempest if there are any 3.10 jobs | 17:26 |
| gouthamr | i.e., stable/2025.1 | 17:26 |
| gmaan | yeah, I try to keep supporting in tempest as long as it is green but once broken then we drop it in tempest and test the jobs with compatible tag | 17:26 |
| gmaan | gouthamr: that only impact jammy jobs on 2025.1 which is additional testing due to SLURP release | 17:26 |
| gmaan | rest all CI on 2025.1 works on ubuntu noble and that works fine | 17:27 |
| gouthamr | ah, true | 17:27 |
| gouthamr | and grenade jobs are broken anyway and you asked project teams to drop those or fix them if necessary: | 17:27 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/O6BSP3MDWOL7JQL7PN3LSBITIQ6MNUQX/ | 17:27 |
| gmaan | just sent email | 17:27 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ONCJY4H64SQZWHJ6CXCVVJFFS6OGYDPC/ | 17:28 |
| gouthamr | ty gmaan | 17:28 |
| gouthamr | #undo | 17:28 |
| opendevmeet | Removing item from minutes: #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ONCJY4H64SQZWHJ6CXCVVJFFS6OGYDPC/ | 17:28 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ONCJY4H64SQZWHJ6CXCVVJFFS6OGYDPC/ ([qa][stable] Tempest master and stable/2025.1 ubuntu jammy jobs are broken) | 17:28 |
| gmaan | yeah, that is removed from the integrated template now so it should not be running on 2025.1 or 2025.2 until they are explicitly added in those branch zuul file | 17:28 |
| gouthamr | ack, ty for working on this.. | 17:29 |
| gmaan | in qa, we discussed and agreed not to support/test the upgrade testing for EOL releases so removing jobs is agreed approach | 17:29 |
| gouthamr | yeah | 17:29 |
| gmaan | i want to remove the greande jobs testing from unmaintained branches but as long as they green I am ok to keep them in integrated template | 17:30 |
| gouthamr | you mean the one testing unmaintained/2024.1 --> stable/2025.1? | 17:30 |
| gmaan | yes | 17:31 |
| gouthamr | okay, noted.. | 17:31 |
| gmaan | they are green so still in integrated template but once broken I will go with remove them instead of fixing them, | 17:31 |
| gmaan | if unmaintained branch team fix them then they can always add it as explicit in zuul yaml and per project basis | 17:32 |
| gouthamr | +1 | 17:32 |
| gmaan | that is the kind of policy we follow in QA but many times expectation is to keep them green and running as integaretd testing | 17:32 |
| gouthamr | it's a good one to note and agree upon.. because it's at the edge of the project teams' concerns in addition to being at the edge of the python lifecycle | 17:34 |
| gouthamr | alright, anything else to note regarding the gate/ | 17:34 |
| frickler | nova is testing a new cirros version, just in case someone sees anything weird there | 17:35 |
| gouthamr | neat | 17:36 |
| clarkb | frickler: did we cache that new version yet or is that still a todo once we're happy with it? | 17:36 |
| frickler | #link https://review.opendev.org/c/openstack/nova/+/990728 | 17:36 |
| frickler | it is not an official build yet | 17:36 |
| clarkb | oh got it | 17:36 |
| frickler | we could add it to our cache anyway if we do see download failures | 17:37 |
| gouthamr | alright, let's skip past the tracker and move to open discussion | 17:38 |
| gouthamr | #topic Open Discussion | 17:38 |
| gouthamr | please note any tracker updates here if you'd like | 17:39 |
| gouthamr | a few neutron dashboard/stadium projects could head towards deprecation: | 17:41 |
| gouthamr | #link #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DNFIZK3KR4JI7ZLHYSC5OW27AE74245Y/ (Maintainers needed for bgpvpn, vpnaas, fwaas dashboards) | 17:41 |
| gouthamr | neutron maintainers are okay waiting until M-3 for volunteers to help, but, that might be a release team concern | 17:42 |
| gouthamr | and a TC concern, since we'd ideally have this sorta heads-up around M-2 | 17:42 |
| fungi | is there any release process impact from those? | 17:43 |
| fungi | oh, you called that out already | 17:43 |
| gouthamr | yeah, these are all cycle-with-rc | 17:44 |
| fungi | doesn't look like any of them have 2026.2/hibiscus releases tagged yet | 17:44 |
| frickler | yeah, we might consider dropping them for m-2 unless there is some feedback earlier | 17:45 |
| frickler | at least if it looks like the plugins will be broken by the end of this cycle (we = release team in this case) | 17:46 |
| gouthamr | horizon changes are still ongoing.. and plenty of "maintained" dashboards need attention | 17:46 |
| fungi | this week is the release membership freeze, so technically the release managers are supposed to know which deliverables will be included in 2026.2/hibiscus by friday | 17:48 |
| fungi | #link https://releases.openstack.org/hibiscus/schedule.html 2026.2/Hibiscus cycle release schedule | 17:48 |
| gouthamr | all these cycles, and #TIL | 17:49 |
| gouthamr | ty for that call out | 17:49 |
| frickler | fungi: isn't that 4 weeks from now? | 17:49 |
| frickler | R-13 | 17:49 |
| fungi | oh! yes, that's 4 weeks from now | 17:49 |
| gouthamr | alongside M-2 | 17:50 |
| fungi | i read it as june 3, sorry! | 17:50 |
| gouthamr | PANIC | 17:50 |
| fungi | yes, so we have 4 weeks left to decide those | 17:50 |
| gouthamr | okay, worth letting neutron folks know in case they're not aware of this.. | 17:51 |
| gouthamr | since a number of you either wear operator hats or are speaking to operators, I did want to raise attention to a thread regarding security advisories and patching | 17:52 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/XWR6T4KERQXH2HWKUBBUSYCUWDVRXIAW/ (Security patch updates regarding OpenStack on Debian) | 17:52 |
| gouthamr | this was written by zigo, and concerning his work on the debian packages.. but the theme is cross cutting | 17:53 |
| gouthamr | every distro/package maintainer shares the pain.. | 17:54 |
| gouthamr | so if you'd like to chime in, please do.. it'll be good data for fungi/JayF/the security-SIG to know and be aware | 17:54 |
| JayF | I'll note that even Ironic wasn't backporting to Zed anyway :) | 17:55 |
| gouthamr | for class A bugs, project teams provide fixes to all maintained/stable branches | 17:55 |
| frickler | also note that the keystone team is struggling to even get the fixes for stable branches merged | 17:55 |
| fungi | yeah, i'm quite sure there's pain all around, and not just what i can see directly | 17:56 |
| gouthamr | but, we do see the community creating/sharing fixes for unmaintained and EOL branches too.. because, reality - hopefully this season of vulnerabilities is motivation to upgrade | 17:56 |
| fungi | and it's not just our community either, as a loose anecdotal data point the oss-security mailing list had almost 5x as many posts last month as they did in the same month one year ago | 17:56 |
| clarkb | it has been a very busy year for operators of software | 17:57 |
| fungi | opendev sysadmins have been spending a lot, if not most, of their time just evaluating and applying security updates for the servers and services we operate too | 17:57 |
| gouthamr | ++ that's "hidden" work.. | 17:58 |
| gouthamr | time check for this meeting | 17:59 |
| gouthamr | does anyone want to add anything to the minutes? | 17:59 |
| gouthamr | thank you all for participating! | 18:01 |
| gouthamr | this meeting will return next week, with a note.. i need help running it :) | 18:01 |
| gouthamr | will follow up on that | 18:01 |
| gouthamr | #endmeeting | 18:01 |
| opendevmeet | Meeting ended Tue Jun 2 18:01:47 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-06-02-17.00.html | 18:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-06-02-17.00.txt | 18:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-06-02-17.00.log.html | 18:01 |
| gouthamr | mnasiadka: i'm away next Tuesday.. are you around? and would you able to run this meeting next week? | 18:02 |
| mnasiadka | gouthamr: sorry for that, but that week I’m in full day meetings whole week (my employers internal design summit) and I just bought some concert tickets and it starts in the duration of that meeting :) | 18:04 |
| mnasiadka | So we’d need someone else to run that | 18:05 |
| gouthamr | :D haha, good reason | 18:05 |
| dansmith | wait, wait | 18:05 |
| dansmith | what concert? | 18:05 |
| dansmith | reserve judgment before you let them off the hook.. could be something unjusified | 18:05 |
| gouthamr | hahaha | 18:05 |
| mnasiadka | dansmith: Voivod ;-) | 18:05 |
| dansmith | uh | 18:06 |
| * dansmith googles | 18:06 | |
| spotz[m] | hehe | 18:06 |
| fungi | they're good enough to be a valid excuse | 18:06 |
| gouthamr | i went here: https://en.wikipedia.org/wiki/Rock_music_in_Poland | 18:06 |
| dansmith | "Voivod is a Canadian heavy metal band" -> approved | 18:06 |
| mnasiadka | Thank you for your approval ;-) | 18:06 |
| gouthamr | hope you survive the mosh pits | 18:07 |
| fungi | the openstack technical and music critic committee | 18:07 |
| gouthamr | OSTCMCC, i like the ring of that | 18:08 |
| spotz[m] | No one likes my music though! | 18:09 |
| gouthamr | oh, i pictured you're an SXSW vet.. | 18:10 |
| gouthamr | so, wouldn't imagine :D | 18:10 |
| spotz[m] | I went up once for Garth Brooks, it's crazy up there! | 18:10 |
| gouthamr | "Blame it all on my roots, I misconfigured the routes, and completely ruined the cloud migration..." | 18:12 |
| spotz[m] | hehe | 18:14 |
| gouthamr | okay, marking mnasiadka away for the next meeting.. that's four known absences.. might be a light crowd/light agenda sorta day.. let me know if anyone's comfortable running the meeting :) | 18:25 |
| dansmith | if it helps I can "be busy" and shoot the quorum | 18:28 |
| fungi | sadly, lack of quorum doesn't prevent meeting, merely means you can't have a binding vote | 18:29 |
| dansmith | dangit fungi | 18:30 |
| spotz[m] | I can run it but don't mind canceling either | 18:30 |
| fungi | i mean, it might still be a good excuse not to hold a meeting, i don't know | 18:30 |
| fungi | certainly no volunteers to chair the meeting would be a good excuse to cancel it | 18:31 |
| spotz[m] | Oh then I rescind the offer:) | 18:31 |
| gouthamr | haha, the TC is observing an early midsummer break - it does look like the heat's turned on early in some places | 18:32 |
| fungi | only 64f/18c here at the moment, with 20mph/32kph winds. quite pleasant. i may even get some yardwork done after my meetings | 18:35 |
| opendevreview | Dr. Jens Harbott proposed openstack/governance master: Retire Venus Project https://review.opendev.org/c/openstack/governance/+/981959 | 19:14 |
| frickler | rebased ^^ since it had a merge conflict. all project cleanup patches should be merged | 19:14 |
| fungi | similar to the neutron deliverable deprecations, the release team also has concerns about some barbican deliverables that haven't been getting any new changes: https://review.opendev.org/c/openstack/releases/+/984402 | 19:39 |
| gouthamr | mharley[m] ^ | 20:46 |
| mharley[m] | Hello! | 20:47 |
| mharley[m] | Hum, OK. Homework for the PTL here to take a look at. Thanks, gouthamr. I’ll put down a note to check that this week. | 20:48 |
| fungi | thanks mharley[m]! | 20:48 |
| gouthamr | it's possible these are either feature complete, or obselete.. cycle-with-rc seems like the wrong release model for this | 20:49 |
| gouthamr | you may want to set that to independent or none, depending on what the barbican team would like | 20:49 |
| fungi | yeah, right now the release team expects to continue releasing them every cycle, which is more work for us if they're misclassified | 20:51 |
| mharley[m] | Anytime, gouthamr. | 20:55 |
| mharley[m] | And fungi. | 20:55 |
| gouthamr | yep.. mharley[m] perhaps loop in dmendiza[m] and ack the release change; you'll need to update the governance repo too if you choose to change things | 20:55 |
| mharley[m] | Gotcha. | 20:55 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0097: Horizon RC file shell metacharacter injection https://review.opendev.org/c/openstack/security-doc/+/991235 | 22:29 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0097: Horizon RC file shell metacharacter injection https://review.opendev.org/c/openstack/security-doc/+/991235 | 22:35 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0096: oslo.messaging RabbitMQ TLS hostname verification https://review.opendev.org/c/openstack/security-doc/+/989478 | 22:35 |
| opendevreview | Merged openstack/security-doc master: Updated from openstack-manuals https://review.opendev.org/c/openstack/security-doc/+/989926 | 22:39 |
| opendevreview | Merged openstack/security-doc master: Add OSSN-0096: oslo.messaging RabbitMQ TLS hostname verification https://review.opendev.org/c/openstack/security-doc/+/989478 | 22:55 |
| opendevreview | Merged openstack/security-doc master: Add OSSN-0097: Horizon RC file shell metacharacter injection https://review.opendev.org/c/openstack/security-doc/+/991235 | 22:56 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!