18:00:49 #startmeeting tc 18:00:49 Meeting started Tue Oct 3 18:00:49 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:49 The meeting name has been set to 'tc' 18:00:56 #info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel, where the recording will be uploaded soon. 18:01:02 #link https://www.youtube.com/channel/UCBuGwBXOmWHydSE09RM84wQ 18:01:13 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. 18:01:16 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee. 18:01:20 #topic Roll Call 18:01:24 o/ 18:01:30 o/ 18:01:30 o/ 18:01:31 o/ 18:01:56 o/ 18:02:04 * slaweq will join zoom call in a minute or two 18:02:15 we will wait until :05 for you 18:03:43 o/ 18:04:14 #topic Follow up on action items 18:04:31 #link https://etherpad.opendev.org/p/2024.1-leaderless 18:06:21 Thanks gmann for following up on that action item. 18:07:25 #action knikolla to complete documentation for unmaintained branch policy in releases.openstack.org; carryover from 2023-09-26 18:12:57 #info TC will take a agenda item for next meeting around the future of TripleO if/when we retire wallaby under new unmaintained branch policy 18:14:32 #topic Gate Health Check 18:17:43 #info Concerns continue about heavy db usage in keystone; investigation is planned. 18:19:03 #action knikolla (or delegate) by PTG will investigate DB usage patterns in Keystone. Progress to be tracked during intermediate TC meetings. 18:25:11 #action JayF to ensure we have a cross-project performance session at the PTG centered around DB usage patterns; ensure SQLAlchemy and oslo.db maintainers and invested parties are invite. Specific focus on strangely-high query counts from Keystone and Neutron reported during devstack jobs. 18:25:35 #topic Leaderless projects 18:25:47 #link https://etherpad.opendev.org/p/2024.1-leaderless 18:36:39 #action slaweq to propose a patch to openstack/governance for TC consideration to mark monasca inactive 18:37:05 #info Monasca is identified as a project with low (5) user counts, failing gate, and inactive through last cycle. TC to consider marking inactive. 18:37:42 #topic Call for Volunteers for Vice-Chair 18:43:59 JayF: as for what the charter requires, it states that you will *seek* for a vice chair. but no, it doesn't say what happens if nobody volunteers 18:44:17 #action JayF to appoint rosmaita as vice chair 18:44:36 "The elected TC chair will seek another TC member to volunteer to serve as vice chair until the next chair election is held." 18:44:59 #info Other interested parties are still welcome to volunteer as an additional vice-chair to learn about chair duties. 18:45:08 #topic Open Discussion and Reviews 18:48:16 #info Proposed times & Topics for TC PTG sessions are in https://etherpad.opendev.org/p/tc-ptg-october-2023 18:48:23 Will email about ^ that after the TC. 18:51:28 #action spotz[m] to take ownership of planning Operator Hour sessions for vPTG 18:53:26 spotz[m]: I think for practical purposes it might have been aprice who had an etherpad with times/etherpads for the operator hours that was sent out afterwards? 18:54:07 one thing Iv'e thought may be helpful is prompting the folks you want to participate (in this case operators) with a specific task or interaction you want from them 18:54:38 spotz[m]: looks like https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030301.html is from last year 18:54:38 "bring a bug. we'll triage it together than pair you with a developer so that you can work together to fix it" 18:58:38 not wanting to interrupt, but the ptg coordinators are talking about switching to jitsi-meet by default 18:58:45 nice! 18:59:11 the main concern is that announcing it this close to the event would be disruptive for some teams 18:59:41 Yeah it probably would be; but it's nice to see the technology is to that point. 18:59:43 and there are some changes needed to ptgbot to make that just a magical default 19:00:41 google meet is not accessible in mainland china, as a data point 19:02:02 #action JayF to see upsides/downsides to proposing jitsi-meet as technology for TC video meetings 19:04:13 #endmeeting