Tuesday, 2025-01-07

gouthamrtc-members: o/ Happy New Year! A gentle reminder that our first weekly meeting of 2025 is in an hour in this channel and on Zoom: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee17:00
spotz[m]Be 2 minutes late meeting running over17:59
gouthamrack spotz[m] 18:00
gouthamr#startmeeting tc18:00
opendevmeetMeeting started Tue Jan  7 18:00:28 2025 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
opendevmeetThe meeting name has been set to 'tc'18:00
gouthamr#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:00
gouthamr#link https://www.youtube.com/channel/UCBuGwBXOmWHydSE09RM84wQ18:00
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.18:00
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee18:00
gouthamr#topic Roll Call18:00
noonedeadpunk  o/18:01
gouthamron the video bridge: slaweq cardoe noonedeadpunk gtema gmann spotz[m] 18:01
gouthamrfungi and clarkb too, ty for joining everyone.. 18:01
spotz[m]o/18:02
gouthamrcourtesy ping: bauzas 18:02
gouthamrnot in today: f r i c k l e r18:02
bauzasarriving18:02
gouthamr#topic Last Week's Action Items 18:04
gouthamrwe had some AIs on Unmaintained Branches.. we'll follow up on a separate topic for this one18:05
gouthamrelection dates have been proposed; we'll chat about that in a bit too18:06
gouthamrnoonedeadpunk took an AI to figure out addressing blocked documentation changes18:08
noonedeadpunk++18:08
gouthamrhe'll summarize here since we're having technical difficulties on the Zoom call18:08
gouthamrwe did have other AIs pertaining to Ubuntu Noble jobs 18:09
gouthamrwe'll address those in a separate topic too18:09
gouthamr#topic Update on unmaintained branches (frickler)18:09
gouthamras of the last meeting, we know elodilles's company would like to maintain Victoria18:10
gouthamr#link https://review.opendev.org/c/openstack/releases/+/937515 (Transition unmaintained/victoria to EOL)18:10
gouthamrThe deadline for the opt-in process was 30 Jan 202518:11
noonedeadpunkyup, last meeting a poor state of openstackdocstheme has been raised along with nobody being around on voting on changes there. while we can drop own theming, alternative would be to find way of landing proposed changes to such generic repos by tc, without having maintenance obligation due to rolling nature of tc members18:11
gouthamrnext step, elodilles can update the patch directly to exclude the projects being left in unmaintained state18:11
gouthamrlets continue the discussion on the gerrit patch18:12
gouthamrwe are unsure if elodilles intends to volunteer to maintain W, X, Y, Z branches of the same repos18:14
gouthamrgmann followed up on the gerrit change 18:14
gouthamrwe'll keep this topic through the next meeting so we can chat with   f r i c k l e r   as well 18:15
gouthamrlets move on to the next topic18:15
gouthamr#topic Update on election and changes18:15
gouthamr 18:15
gouthamr#link https://review.opendev.org/c/openstack/election/+/937408 18:16
gouthamr^ election officials have kick-started the next election18:16
gmann#link https://governance.openstack.org/election/18:16
gouthamr#link https://review.opendev.org/c/openstack/governance/+/937741 (Allow more than 2 weeks for elections)18:17
gouthamr^ we are yet to merge this18:17
gouthamrwe have published the election dates already, we are unsure if we can make this charter change for this election without causing any confusion18:18
gouthamrspotz[m] points out if we checked for holidays during the election period18:18
gouthamrwe may have an overlap with the Chinese New Year holidays 18:20
gouthamrmaybe we can allow early nominations in lieu of this18:21
funginote that nomination check jobs will fail (or at least used to) if pushed prior to the open date for the nomination period, and so may need rechecking18:21
gouthamr++18:22
gmann++18:22
fungithe main blocker is when the configuration with the precreated directories for teams hasn't been added to the repo yet18:22
gouthamrwe have a couple of things to set up elections:18:22
gouthamr- kickoff email to the mailing list18:22
gouthamr- schedule updates to https://releases.openstack.org/epoxy/schedule.html 18:22
gmannfungi: yeah, we need to create that in advance. 18:23
gouthamrsorry the third item, election officials creating the nomination directories18:23
fungiyes, the candidates/2025.2 directory and team subdirectories are missing at the moment, so need creating first18:24
gouthamr#action follow up on these three election todos in next week's meeting18:24
fungiafter that, nominations are technically possible18:24
clarkbmaybe go ahead and create a couple years worth of directories?18:25
fungithere is an openinfra newsletter going out in a week or two, if the schedule can be confirmed before then i can include a mention of the dates there18:25
gouthamrthanks fungi18:25
gouthamrclarkb: true, we don't really need the names anyway do we18:26
gouthamrrelease names18:26
gouthamr#topic Status on migrate CI to Ubuntu Noble18:26
gouthamr#link https://etherpad.opendev.org/p/migrate-to-noble (Etherpad tracking the goal) 18:26
fungiwe still need to tag a pbr release18:26
fungibut it's not altering how pbr does pyproject.toml support, it was more us proving it works18:27
fungii have a change proposed to update the docs too18:27
gouthamra set of changes to pbr occurred in the past couple of weeks:18:27
gouthamr#link https://review.opendev.org/q/project:openstack/pbr+status:merged 18:28
fungi#link https://review.opendev.org/938585 Clarify PEP 517 implementation for users18:28
gouthamrplan is to tag a beta release, and have projects test this 18:28
fungiwe've been proving it all out with a series of changes to bindep, in case anyone wants to see a real world example18:28
gouthamrthere are three projects with failing noble jobs still: 18:29
gouthamr#link https://etherpad.opendev.org/p/migrate-to-noble#L17218:29
gouthamrwe may be blocked by inactive project teams, or its unclear if project maintainers have stepped away for the holidays18:30
gouthamrgmann has raised the issue on irc channels, the openstack-discuss mailing list 18:30
gouthamrthe concern is how the release would go for these project teams that won't follow the runtime testing guideline in time 18:31
gouthamrwe18:31
gouthamrwill follow up next week with updates18:31
gouthamranything else for $topic?18:32
gouthamr#topic A check on gate health18:32
gouthamrwe haven't identified anything new/specific show up in the new year 18:33
gouthamrbauzas notes that nova jobs in december were flaky with VM networking issues18:34
gouthamrclarkb notes that dockerhub rate limits affect openstack-helm CI jobs 18:34
gouthamrthe project teams chatted with opendev-infra over the holidays18:35
gouthamrthey've been told that opendev-infra can't control these rate limits, and a migration is teh best course of actioon18:35
fungiwe kept the lights on18:36
gouthamr++18:36
gouthamrgerrit stores cache files on disk that inflated over the holidays18:37
gouthamrthis led to a bunch of timeouts and mess; manual intervention was required 18:38
gouthamr#topic PTG AIs and the TC Tracker18:38
gouthamr 18:38
gouthamr#link https://etherpad.opendev.org/p/tc-2025.1-tracker (Technical Committee activity tracker - 2025.1)18:39
gouthamr^ any thing that we'd like to share an update about today?18:39
gouthamrwe'll are getting back into full momentum now, so we can go over each item next week18:40
gouthamr#topic Open Discussion and Reviews18:40
gouthamrspotz[m] announced that there'd be a celebration of OpenStack 15th Birthday at FOSDEM 202518:41
gouthamrthere'll also be a BOF session on OpenStack, spotz[m] will update us soon18:41
gouthamrslaweq will be at FOSDEM 2025, and eat some cake on our behalf18:41
gouthamrfungi mentions that there were some ML regarding lack of review attention in octavia18:43
gouthamrcardoe pointed out that octavia might not be the only case where core reviewers aren't paying attention to reviews from new folks or individuals that don't contribute often18:46
gouthamrslaweq mentions that he can check with the core team, he says the team is pretty small and might be stretched thin18:46
gouthamrgmann says he's had to ping them a few times to get SRBAC patches merged18:46
gouthamr#link https://meetings.opendev.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2024-12-25.log.html 18:47
gouthamr^ a message on Dec 25 that wasn't ack'ed on IRC, but, the patch got some reviews when folks came back by the looks of it18:48
gouthamrbauzas notes that new contributors may be expecting sync conversations over IRC18:49
gouthamrwe may have folks getting confused between IRC channels for #openstack-lbaas (official channel for octavia discussions) and #openstack-octavia (unregistered) 18:52
gouthamrsomeone from the octavia team may need to park in the channel and actively drive discussion away, or register the channel and set a topic/redirect message18:52
gouthamrwe're at M-2, the check point for any released projects to be tagged inactive if the project's momentum has stalled18:56
gouthamrMonasca's CI jobs have been failing for months, and there is no activity on the various repos18:56
gouthamrmonasca is tagged "inactive" though.. no coordinated releases have occurred since 2023.2 18:57
gouthamr#action start an ML thread copying the PTL and ask to retire the project18:58
gouthamrduring this cycle, the ubuntu-noble migration effort was a good check on the health of project teams 19:01
gouthamrmost teams were responsive, monasca and skyline remain the concern.. 19:02
gouthamrhberaud brought up an issue with masakari and eventlet on the ML: 19:02
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/4RWJH7L7QWVO3SJ64MIGPUQ6Z4Q7HMYD/ ([masakari] failures with new version of Eventlet) 19:02
fungii do wonder what can be done to attract a more global maintainer base to skyline, with it posed as the successor to horizon19:03
gouthamrwe'll follow up next week regarding this concern, its possible the issue was fixed19:03
gouthamrfungi: it'd be the case if that plan was official.. i.e., if horizon was on a retirement path19:04
gouthamrwe wrapped up the meeting on Zoom19:04
gouthamrsorry for running on here, wanted to make sure we had minutes :D 19:04
gouthamrthank you all for attending today, next week's meeting is back on IRC19:05
gouthamr#endmeeting19:05
opendevmeetMeeting ended Tue Jan  7 19:05:07 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-07-18.00.html19:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-07-18.00.txt19:05
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-07-18.00.log.html19:05
fungiwrt skyline succeeding horizon, the hope i had was that it was a possible escape route for horizon being stuck on an eol/abandoned web framework without sufficient contributors for the needed overhaul19:05
fungiand that the remaining horizon contributors might help out on skyline as a path forward19:06
fungibut that doesn't seem to have happened19:06
gouthamryeah, there's still active feature development on horizon 19:10

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