Tuesday, 2025-10-21

mnasiadkatonyb: is the meetings.opendev.org ICS file wrong, and we should be meeting in ~92 minutes, not 32 minutes? ;-)06:28
tonybummmm06:29
tonybI have it for 92mins from now06:29
tonybI also  thought today's meeting was missing from the ics file06:30
mnasiadkaAh right06:30
mnasiadkaDumb me, forgot about timezone change06:30
mnasiadkaThanks06:30
tonybhehe, From Paris to $home?06:31
mnasiadka$home == Poland, so that’s the same timezone06:32
mnasiadkaSo not really jet lagged or something, just forgot we switch to winter timezone (which I hate, because then I get up - it’s dark, I finish work - it’s dark :( )06:32
tonybOh.  I didn't know that the EU did it's TZ shift.06:33
mnasiadkaNot yet - it will be this weekend (25/26 Oct)06:33
tonybI dislike the early dark o'clock :(06:33
mnasiadkaThat’s why I got a bit puzzled with the calendar entry for November - why it’s 9am my time instead of 10am my time :)06:34
*** ralonsoh_ is now known as ralonsoh06:40
mnasiadkatc-members: first APAC-friendly meeting in 59 minutes here07:01
tonyb\o/07:01
gtemaYeah, Dst sucks07:11
fricklerluckily all of the EU agrees to stop doing dst switches ... the sad part is that they cannot agree on when and how to do it ... like keep UTC+1 permanently or UTC+2?07:47
tonybfrickler: The toughest of choices ;P07:49
mnasiadka#startmeeting tc08:00
opendevmeetMeeting started Tue Oct 21 08:00:39 2025 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
opendevmeetThe meeting name has been set to 'tc'08:00
mnasiadkaWelcome 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.08:01
mnasiadkaToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee08:01
mnasiadka#topic Roll Call08:01
mnasiadkaO/08:01
frickler\o yay, mornings ;)08:01
gtemao/, but for next 10 min only partly due to the conflict08:01
tonybo/08:01
tonybYay a time when I'd naturally be awake08:02
mnasiadkacourtesy-ping: noonedeadpunk bauzas08:03
mnasiadka(Although they might be traveling back from the Summit)08:03
tonybnext?08:07
frickler+1, waiting until :05 should be enough generally08:09
mnasiadkaYeah, sorry08:10
mnasiadka#topic Last Week's AIs08:10
mnasiadkaMark Vitrage and Venus project-teams inactive08:11
mnasiadkaThese changes have now merged; we need to be aware that, if activity doesn't resume, these project teams and deliverables can be retired prior to M-2 in the 2026.2 release08:11
mnasiadka#link https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects08:11
mnasiadkaAssist Monasca's one-off release (elodilles)08:13
mnasiadkaElod explained how a release can be requested; except, I (gouthamr) think the TC assumed the process to be more straight-forward for "inactive" project teams to request one-off releases08:13
mnasiadka#link https://review.opendev.org/c/openstack/governance/+/95367108:13
fricklerI haven't seen anyone who would actually do a release. I also don't think it would be releasable in its current state08:14
frickleras commented on that change, I am much in favor of proceeding with the retirement now, this has been dragging on for years08:14
gtema+10008:15
mnasiadkaYes, I think three of us on the meeting are happy with proceeding with retirement, it’s been there for too long08:15
fricklerso we need to find two more tc-members to make that a majority vote :)08:16
mnasiadkatonyb: though had some comments that he knows organisations wanting to pick this up08:17
mnasiadkaBut that hasn’t happened08:17
tonybWell I'm RC-1 on retirement because I'm aware of at least one member that wants to work on it08:17
mnasiadkaOk, so are we persisting limbo state for another cycle then?08:17
fricklerbut "want to" doesn't suffice. also there's no apparent reason they could not do it outside of openstack08:17
tonybI understand that, I'm okay with due process ending up with the project being retired, but my preference would be to keep it inactive for another cycle08:19
tonybof course I'm only 1 vote and expect to be in the minority08:19
fricklertonyb: I'm assuming you are referring to someone else than those who already commented on the gov review? who still wants to stay anonymous for now? that's very weak reasoning IMO08:19
tonyb... unless it needs to be unanimous08:20
mnasiadkaMonasca is inactive since 2024.108:20
mnasiadkaI don’t think it’s an easy job to get it back on track, and if that work hasn’t started yet - they will most likely not make it on time until 2026.1 release08:20
mnasiadkaBut I think enough said - we need more votes on the retirement patch08:21
tonybfrickler: It's not that they want to stay anonymous, it's that they currently unavailable08:21
gtemathis statement doesn't make it more reliable to be honest08:22
fricklerjust to note that the patch is V-1 because the actual content removal patches need to be merged first, no reason to not vote on it already08:22
gtemabe all are well aware of people and companies not willing something to die and promise to spend resources and this never happening because of running business08:22
mnasiadkaOk, let’s go forward08:24
mnasiadkaBump skyline self-nomination discussion thread to get PTL/core feedback (gouthamr)08:24
mnasiadkaThis was done, and the PTL welcomed reetsrivastav but the skyline-core group on gerrit wasn't modified08:25
mnasiadka#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/HVE5SEIXSGA4NTJYHAJQQX4N3GNXN6D5/08:25
mnasiadka#link https://review.opendev.org/admin/groups/1fe65032c39f1d459327b010730627a904d7b793,members08:25
mnasiadkaDo we need to do anything about this?08:25
tonybI guess frickler or I could add them to the group08:26
tonyb(and then say so on the M/L)08:26
mnasiadkaShould we first ask the PTL to do so?08:26
mnasiadkaMaybe he doesn’t know08:26
fricklerI don't think someone should be added as reviewer who hasn't done any actual reviews08:27
fricklerat least that's my state from 2 weeks ago08:27
frickler(as core reviewer)08:27
gtema+1 on that08:27
fricklerso let them do reviews, work on CI issues, then reconsider the application in due time08:28
noonedeadpunko/ sorry, just opened laptop and quite drained from the way back08:28
fricklerno action needed on our side for now, IMO08:28
tonybfrickler: I agree with you but the PTL said "Sure, just be careful", at least that's how I read it08:29
fricklerhmm, it is difficult to really judge this statement for me, from one non-native speaker to another08:30
* bauzas waves super late08:30
mnasiadkaOk, should we wait it out for some time? I agree that a core reviewer without any review history looks super weird08:31
bauzasI wasn't knowing the new cadence started this week :)08:31
noonedeadpunkI also not sure if person without any known review activity should be considered as a core08:31
noonedeadpunkand contribution for 3 month is a flag as well08:31
fricklerIIRC cardoe also agreed with that point and had already mentioned it to the candidate. with no visible followup so far.08:32
fricklerso to me sadly this looks to be close to another instance of a lot of "I want to" without meat. vegan meat if you prefer.08:34
frickleranyway, time for next topic I guess?08:35
gtemalol08:35
mnasiadkaYeah, I can’t see any action from this08:36
mnasiadkaCheck, rebase, or recheck relevant changes for Gazpacho runtime updates (gmaan, others)08:36
mnasiadkafrickler: I think you had a look into that?08:36
fricklerthere is one open patch for grenade that I'm aware of, let me find it08:36
fricklerah, two actually, https://review.opendev.org/c/openstack/grenade/+/961914 is just struggling with CI instability it seems08:37
fricklerthe other one is merged already, there was some discussion due to OSC changes that are a bit non-backwards compatible https://review.opendev.org/c/openstack/grenade/+/96191308:39
fricklerbut unless I'm missing something, no open issues anymore08:39
fricklernext? ;)08:40
mnasiadka#topic A check on gate health08:41
mnasiadkaAnybody wants to comment? All green?08:41
mnasiadka(Apart the grenade instability)08:41
fricklerwell the docker.io and quay.io issues yesterday show once again that more autonomy is good08:42
tonybWe had a gerrit outage on the weekend, which would have impacted reviews but not CI as such08:42
mnasiadkaYeah, quay.io issues basically broke majority of Kolla-Ansible CI - but to achieve more ,,autonomy’’ we would need to probably use some intermediate registry inside OpenDev08:43
fricklertonyb: was there a reason for the outage found? or just "VM shutoff for unknown reasons"?08:43
fricklermnasiadka: or opendev could reconsider running their own registry ... but no easy task I know and not directly a TC topic ... except if anyone wants to organize funding for that :D08:44
tonybfrickler: Yeah the VMs were shutdown.  It was later in my Sunday and fungi dealt with it.08:45
mnasiadka#topic A call for PTG Topics08:46
mnasiadkaHave there been any additions to make since the OpenInfra Summit?08:46
mnasiadkagouthamr would like to request topics to seed the "Maintainers" discussion (a.k.a.: TC+Project Leaders discussion)08:46
* tonyb doesn't really have any for that.08:49
tonybmaybe "getting rid of *really old* libraries from OpenStack $projects we need you help", but that's probably more of a mailing-list/community goal/requirements thing than a TC thing08:50
fricklerwe could ask maintainers to report instances of this for a start08:51
fricklerbut agreed that this doesn't necessarily have to be a PTG discussion08:52
mnasiadkaThere was a crypto libraries topic on the TC ,,shift’’ in the Open Source Pavillon - which gtema was mainly having - majority of them is unmaintained08:52
mnasiadkagtema: did you happen to get that list, or will the author post it to the ML?08:53
noonedeadpunkso I was thinking if we might wanna have some kind of oslo.crypto or smth08:53
gtemait's not that the Keystone is the only thing affected but yes, I had a long chat with JP on that08:53
noonedeadpunkthat might address the question of openstack overall relying on too many external crypto libraries, which are partially unmaintained08:53
gtemaI will try to clarify. We definitely agreed to have a dedicated session in PTG (from Keystone pov)08:53
noonedeadpunkand to remove that maintenance from keystone itself08:54
gtemabut I agree we should raise it wider. I will try to catch JP and discuss it with him08:54
mnasiadkaMaybe that’s a good topic to TC+Project Leaders discussion08:54
mnasiadkas/to/for/08:54
mnasiadkaOk then, next one08:54
gtemayes, would be good fit08:54
mnasiadka#topic OpenStack User Survey Results08:54
mnasiadka#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/IIGG4IQBW3W6PTBT7ASKJKMQDAEGILSB/08:54
tonybgtema: Oh that'd be great.08:54
mnasiadkaDo we need to do anything that? Some data extraction?08:55
tonybplease include me (timewise) moving away from pysaml would help!08:55
fricklerhaving that document not hosted on google would help me08:56
gtema:)08:56
gtemaits hardly consumable honestly08:56
gtemafor me not due to the google fact, but the format08:56
tonybwhere would you like it?   I can move it for you.   I can email you a CSV?08:57
gtemathat's the point - the csv does not make it reasonable to consume08:57
fricklerI'd take that, yes, thx. maybe putting it up on www.openstack.org would also be a good idea08:57
noonedeadpunkI think it's renderred on analyticks page?08:57
gtemaI can myself export-import into oo-calc, but its just so huge and not easy structured08:58
fricklerthe format of the results is another issue, I'm sure constructive ideas will be welcomed08:58
gtemaas PTL I do not really know what to do with it08:58
mnasiadkaI assume that’s the format we get it from foundation08:58
mnasiadkaMaybe we need to work with Jimmy and others to make it more structured next time...08:58
mnasiadkaAny volunteer to pick up that discussion?08:59
noonedeadpunkmean this: https://www.openstack.org/analytics08:59
fricklernoonedeadpunk: that's a good location to add a download for the spreadsheet I guess?09:00
noonedeadpunkyeah, as it already has a download pdf button09:01
noonedeadpunkso no reasdon not to make it a dropdown and have like CSV as well09:01
mnasiadkaOk then, if anybody wants to pick this up - I assume just reply to the thread Jimmy started09:01
mnasiadkaTime is up - thanks for coming, see you next week in the other timeslot.09:02
mnasiadka#endmeeting09:02
opendevmeetMeeting ended Tue Oct 21 09:02:15 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:02
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-21-08.00.html09:02
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-21-08.00.txt09:02
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-21-08.00.log.html09:02
mnasiadka(Of course we can continue the discussion async)09:02
fricklerthx mnasiadka, good job, given it was a first run ;)09:02
noonedeadpunk++09:03
noonedeadpunkI was not expecting it's gonna be today though :p09:03
tonybThanks all!09:03
tonybsee you all next month (for the meeting) and probably/hopefully some during the PTG09:04
gtemanoonedeadpunk - me too, I was surprised today as well09:04
gtemaI think even the calendar does not say it is today09:04
gtemaat least not for me09:04
tonybgtema: Yeah yaml2ical bugs :(09:04
gtemaoki09:05
tonybCan I ask people here do do a pass over https://review.opendev.org/q/is:open+-is:wip+label:Workflow%3E%3D0+(project:openstack/api-site+OR+project:openstack/openstack-manuals+OR+project:openstack/project-team-guide) and clear out some of the low hanging fruit09:06
tonybAnother random note before I sign off.  How does one "formally sign up" as a TC liaison to the Election team?09:36
tonybWe should update: https://governance.openstack.org/tc/reference/working-groups.html#current-list-of-working-groups09:37
opendevreviewTony Breeds proposed openstack/api-site master: [doc] Manully install typing_extensions  https://review.opendev.org/c/openstack/api-site/+/96426209:48
opendevreviewTony Breeds proposed openstack/api-site master: Add links to the Rust SDK/CLI/TUI  https://review.opendev.org/c/openstack/api-site/+/94602509:48
tonybgtema, noonedeadpunk, frickler: ^^ should both be good to go.09:50
gtemathks tonyb - +2ed again09:50
cardoeHello folks13:51
fungitonyb: frickler: we'll need to sync up with someone at vexxhost to get an rca on the gerrit outage, but after talking to sean-k-mooney about it at the summit it sounded like the symptoms were consistent with the host's oom-killer taking out the qemu process for the vm13:55
sean-k-mooneyright. by default if nova notices a vm that shoudl be runnning isn now stop it will mark the vm as power off13:57
sean-k-mooneybecause we assume the tenant did "sudo poweroff" or similar and cant really tell directly why it stoped13:58
sean-k-mooneyso it woudl be good to get vexhost to confrim why the gerrit server stopped13:58
sean-k-mooneyoom-killer sounded plausible but it could be something else. the host journal/dmsg and qemu instance logs would tell them more13:59
opendevreviewMerged openstack/api-site master: [doc] Manully install typing_extensions  https://review.opendev.org/c/openstack/api-site/+/96426214:04
opendevreviewMerged openstack/api-site master: Add links to the Rust SDK/CLI/TUI  https://review.opendev.org/c/openstack/api-site/+/94602514:07
gouthamr> Another random note before I sign off.  How does one "formally sign up" as a TC liaison to the Election team?18:46
gouthamrtonyb: self-nominate, do you want to? https://review.opendev.org/c/openstack/election/+/95430218:46
gouthamrplease replace me when you do :) 18:46
gouthamrmnasiadka: \o/ great job, and ty for running the meeting! 18:47
fungigouthamr: i think you push a change to https://opendev.org/openstack/election/src/branch/master/doc/source/index.rst and get other tc members to review it? i haven't seen any more formal instructions in the governance repo18:50
gouthamrfungi: yep, that'd be it, and i have EAFP added myself to this one before. The Chair needs to nominate someone, and that's done by asking for volunteers... 18:52
gouthamrlooks to me like tonyb is volunteering, and he's been an election official before :) 18:53
fungioh, yep i misread that you were quoting tonyb18:53
gouthamrah, np.. 18:53
gouthamrtc-members: i'll cancel our "regular" meeting next week in lieu of the PTG.. 18:54
gouthamralso, in the past, we indicated we'd like to go through SIGs during the PTG: https://governance.openstack.org/sigs/18:54
gouthamrthere are a lot on that list ^.. do we want to piecemeal this and approach existing sig chairs/members for an update/status?18:54
cardoefrickler: yes I concur about the maintainership19:16
cardoeWe should re-evaluate recommending uWSGI given its maintained state.19:17

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