17:00:09 #startmeeting tc 17:00:09 Meeting started Tue Oct 14 17:00:09 2025 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:09 The meeting name has been set to 'tc' 17:00:23 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:34 #topic Roll Call 17:00:36 O/ 17:00:40 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 17:00:50 o/ 17:00:50 o/ 17:02:26 courtesy-ping: cardoe 17:02:26 noted absence: to ny b, bau zas, sp ot z, fri ckl er 17:02:37 hello sorry 17:03:03 hey there, lets get started 17:03:19 #topic Last Week's AIs 17:03:46 we took one on Venus and Vitrage governance changes 17:04:19 #link https://review.opendev.org/c/openstack/governance/+/963227 (Mark Vitrage project-team inactive) 17:04:38 #link https://review.opendev.org/c/openstack/governance/+/963228 (Mark Venus project-team inactive) 17:05:07 these could use some more RC votes 17:05:53 we still don't have any update on the Monasca retirement, but, a current maintainer needs a release 17:06:12 the discussion is happening here: 17:06:20 #link https://review.opendev.org/c/openstack/governance/+/953671 (Retire Monasca project) 17:06:40 i was under the impression that this was possible by proposing a change to the releases repo 17:07:43 this totally should be possible 17:07:57 or well, technically at least 17:08:09 the last release was in 2023, i'm not sure what release tooling is missing for it 17:08:20 As then releases team need to sign-off under the relase request coming from non-PTL or release liason 17:08:27 yes 17:08:30 elodilles: could you please take a look at the change and comment? 17:09:19 ideally thuvh would request the release themselves - but probably hasn't done one so far, so might need some help with the process 17:11:07 the next AI was about scheduling the APAC/EU friendly meeting, lets discuss that in a separate ytopic 17:11:28 we had an AI about refreshing the TC liaison for Freezer, Oslo, Release Management, and Requirements 17:11:46 didn't have any volunteers so far, but i can propose a change and throw in some names 17:12:24 the next one was around the skyline self-nomination 17:12:56 Michal Nasiadka proposed openstack/governance master: Propose mnasiadka as tc-liaison for requirements and release https://review.opendev.org/c/openstack/governance/+/963989 17:13:04 gouthamr: I forgot to run ‘git review’ ;-) 17:13:05 \o/ mnasiadka 17:13:13 Thank you for reminding 17:13:14 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/LQM6KZMD5BXJL477HODHYZ77RNDEIEKH/ 17:13:25 ^ cardoe are you familiar with this contributor 17:13:43 A little bit. 17:13:59 isn't that up to project PTL to decide on this one? 17:14:22 He works at Rackspace. I've spoken with Sowmya much more. 17:14:22 as I can recall they were asking for help with reviews lately? 17:14:24 yeah, the only thing i was thinking about doing was asking the PTL/existing cores to respond 17:14:41 ++ yes, makes sense then 17:15:00 I've told anyone that wants to join that they need to start reviewing patches. 17:15:33 I'd also say that 3 month is quite a short term... 17:15:43 But still would expect at least some feedback from PTL 17:15:55 yeah, lets bump the thread 17:16:12 that's all the AIs i was tracking 17:16:22 was anyone else working on anything/ 17:17:10 #topic TC Meeting Preferences 17:17:41 ty for filling out the survey 17:18:07 pending fr i ckler's opinion, we have some data to help us with the new meeting slot 17:19:15 for one, this meeting will continue to stay at 1700 UTC on Tuesdays.. except, at a regular cadence, we'll move to a different time that's friendlier to EU/APAC attendance 17:19:29 from the survey, The single most preferred time slot is Tuesdays 0800-0900 UTC. 17:19:48 the only people that can't make it there are spo tz, myself and cardoe 17:19:56 which, is understandable 17:21:05 and in terms of cadence, seem to be okay with a monthly or a bi-weekly slot - it was hard to tell.. mnasiadka is okay with running the meeting either case; noonedeadpunk prefers that we stick to a monthly meeting 17:21:23 (at this "alternate" time) 17:21:43 only downside is that we can't "meet" with tonyb more than a handful of times 17:22:05 As long http://tiny.cc/os-tc-dash continues to track patches and changes we need to converse over I think its fine. 17:22:59 gouthamr: I think I didn't mind much the cadence 17:23:33 https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2025-10-14.log.html#openstack-tc.2025-10-14.log.html#t2025-10-14T07:48:00 17:24:15 wow my client missed a lot of chatter there 17:24:26 I voted for be-weekly originally though 17:24:41 honestly I did not understood the scope for such meeting 17:26:03 +1 on the thought that we'd start with something and adjust 17:26:29 gtema: it's so that folks on the eastern hemisphere can also have a sync meeting 17:26:40 ^ 17:27:07 okay, i'll work with mnasiadka and we'll propose changes to the irc-meetings repo and the wiki 17:27:10 and encourage participation in comminuty life 17:27:12 I mean is that as a replacement for the regular meeting, a "yet another meeting", or meeting to improve personal relations, ... 17:27:35 I think yet another meeting to improve personal relations? 17:27:43 lol :P 17:27:59 Meetings improve personal relations? 17:28:23 Well, anyway 17:28:24 especially the ones at 9:00 :-) 17:28:27 gtema: this meeting will occur in a EU/APAC friendly timezone some weeks - so a replacement, no new slot 17:28:40 i'll note that last time this challenge directly led to the tc not holding meetings and going completely async 17:29:11 So, let me get this straight - by biweekly we mean we use sort of the existing slot every 2 week, and the EU/APAC friendly on the alternate week? 17:29:13 but then iirc anything stopped happening at all? 17:29:29 gtema: its always coffee time somewhere, and tea time someplace else, beer time elsewhere, and night cap time everywhere else.. as long as you're hydrated 17:29:36 mnasiadka: yes 17:29:48 fungi: I have a feeling there will be these two meeting slots and some async, but if full async ended badly - probably this is what we should try out 17:29:53 aha, ok, I thought it'll be another one 17:29:57 on top of existing 17:30:06 no sir, no more meetings :D 17:30:15 noonedeadpunk: two meetings on the same day? Oh come on... 17:31:09 okay, looks like we can continue this discussion after the meeting and make some changes, ty everyone 17:31:24 oh, on the question of whether we need to continue our video meetings 17:31:31 we had no "Yes" answers 17:31:40 there were two of you that said "No" 17:31:51 and the rest said it didn't matter to you 17:32:27 so, i think with the alternate meeting slot kicking in, we can sunset video meetings and bring them back ad-hoc/on-demand 17:32:31 any objections there? 17:32:49 no objections from me 17:33:03 * gouthamr will not miss video converting, thumbnail crafting, uploading, linking minutes, tracking youtube stats :D 17:33:22 * gouthamr heh, will have to do that for PTG anyway 17:33:50 Seems like a job for video editor ;-) 17:34:05 haha, welp 17:34:09 #topic A call for PTG Topics (gouthamr) 17:34:12 #link https://etherpad.opendev.org/p/oct2025-ptg-os-tc 17:34:26 ^ this is my periodic call out for topics please :) 17:34:44 and please do look at the slots, if you have objections, let me know.. 17:35:20 we're meeting on Tuesday and Friday between 1600 and 1800 UTC 17:35:59 hoping there's little to no overlap there, but i get nervous any time i see nova, neutron, ironic sessions overlapping :D 17:36:44 and the eventlet-removal hour is at 1500 UTC 17:36:48 on Tuesday 17:37:23 if you have any concerns with these, now's the time to scramble and fix it - after this week, it'll be unlikely to make any changes 17:37:58 anything else to note for $topic 17:38:57 #topic Runtime / job changes for Gazpacho 17:38:57 we've made a few demands through our runtime update: 17:38:57 #link https://governance.openstack.org/tc/reference/runtimes/2026.1.html 17:39:18 tl;dr: 17:39:18 python 3.13 job should be voting 17:39:18 python 3.14 job should be created, non-voting 17:39:18 grenade skip-level should be active, "grenade" job base updates 17:40:19 you can get 3.13 from debian trixie nodes. 3.14 will probably require using pyenv to build a python currently 17:40:56 i see, but, we currently have 3.13 running on ubuntu-noble 17:41:04 just non-voting 17:41:46 #link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958617 (Prepare the job template for 2026.1 testing runtime) 17:41:50 I wonder if that is using pyenv too. Thats fine if it works 17:41:58 you'd do something similar for 3.14 17:42:00 #link https://review.opendev.org/c/openstack/grenade/+/961913 17:42:08 #link https://review.opendev.org/c/openstack/grenade/+/961914 17:42:26 #link https://review.opendev.org/c/openstack/tempest/+/961916 17:42:46 ^ some relevant changes 17:43:26 yeah, I will be checking those today if anything (rebase, recheck) needed to merge those 17:43:44 ++ ty, no rush gmaan 17:44:12 gmaan: was there anything that needed attention from the TC this week? 17:44:58 no, I removed the -W from job template so that is ready to merge 17:45:58 frickler is already +2 there and fungi or clarkb can merge it https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958617 17:46:13 perfect, ty.. 17:46:25 #topic Old changes in TC repos 17:46:40 tonyb wanted us to look through some old code changes in TC repos: 17:47:35 #link https://tiny.cc/os-tc-dash (nifty TC Dashboard) 17:47:52 #link 17:47:52 https://review.opendev.org/q/is:open+before:2024-01-01+(project:openstack/api-site+OR+project:openstack/openstack-manuals+OR+project:openstack/project-team-guide+OR+project:openstack/service-types-authority+OR+project:openstack/constellations%252BOR%252Bproject:openstack/goal-tools+OR+project:openstack/ideas+OR+project:openstack/openstack+OR+project:openstack/governance+OR+project:openstack/governance-website+OR+project:openstack/gov 17:47:52 ernance-sigs) 17:48:25 ^ grr, the link broke, but please see it on the agenda 17:48:28 https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda 17:49:52 i think we could post a generic comment that these changes are stale and abandon them 17:50:39 and i think we've been wanting to do something about the SIGs 17:51:16 tonyb had a question at the end: 17:51:16 I'd appreciate ideas on splitting up 'Misc' into a more useful grouping. (note a dashbaord can have a max of 10 groups) 17:51:49 i think, there are some TC repos with frequent updates: project team guide, openstack-manuals for example 17:52:22 and some others where there aren't: api-site, governance-website, constellations, ideas 17:53:02 if we clean up old/stale reviews, we could have a more meaningful dashboard 17:53:46 What are constellations? The readme points to a 404 URL and the updates in that repo look that it’s not really used? 17:54:07 "Reference configurations of OpenStack services" 17:54:34 you'd probably want to check fi they are published anywhere 17:54:43 hmmm, mayybe we meant to work on community sourced versions of https://www.openstack.org/software/sample-configs/ 17:54:46 but ya the idea was you run this set of services to accomplish this use case and this other set to do this different use case 17:55:15 Docs in that repo look a bit empty 17:56:46 yeah, think it was meant to be kick started with https://review.opendev.org/c/openstack/constellations/+/586212 17:57:24 Sample-configs also look a bit outdated, with Kuryr in container optimised config and Sahara in Big Data 17:57:48 yeah, its ancient history now, i do think we could use newer "user stories" and reference architectures, and possibly discover/highlight these evolving use cases 17:58:08 something a past TC probably was keen on doing, and is something we can revive if there's interest 17:58:26 for one, the foundation staff's work on white papers is in a similar vein 17:59:20 time check: 1 minute 17:59:38 if there's any feedback to tonyb, please do provide it after the meeting 17:59:46 #topic Open Discussion 17:59:55 anything to note in the minutes today? 18:00:16 is anyone else in Paris besides noonedeadpunk mnasiadka spotz[m]? 18:00:31 me 18:00:35 w00t 18:01:00 with 4 talks this time 18:01:06 oh boy 18:01:19 hope you have a great meet-and-greet in addition to this, i'll call on you to share your take on the summit next week (or the week after) 18:01:25 all the best! 18:01:41 There was a discussion before the meeting on TC in the Open Source Pavillion 18:02:03 Seems noonedeadpunk was happy to be available for a Sunday pre-lunch spot 18:02:13 I can do that as well 18:02:25 spotz[m]: ^ (if you're reading) 18:02:34 lets wrap it up here, thank you everyone! 18:02:37 #endmeeting