| *** bauzas_ is now known as bauzas | 03:44 | |
| *** bauzas_ is now known as bauzas | 04:09 | |
| *** bauzas_ is now known as bauzas | 04:22 | |
| *** bauzas_ is now known as bauzas | 05:27 | |
| *** elodilles_pto is now known as elodilles | 07:26 | |
| *** bauzas_ is now known as bauzas | 07:46 | |
| opendevreview | James Page proposed openstack/governance master: Appoint James Page as OpenStack Charms PTL https://review.opendev.org/c/openstack/governance/+/921731 | 08:25 |
|---|---|---|
| *** bauzas_ is now known as bauzas | 09:17 | |
| slaweq | hi gouthamr, just FYI I will not be able to attend today's TC meeting due to some personal commitments. Sorry for late notice about it | 13:29 |
| slaweq | I just wanted to update meeting agenda page but I got 503 from the login.ubuntu.com now | 13:30 |
| fungi | slaweq: yeah, i've already reported it in the #launchpad and #canonical-sysadmins on libera | 13:35 |
| fungi | seems to be down hard | 13:35 |
| slaweq | thx fungi | 13:36 |
| fungi | slaweq: try again, it's back up now | 13:59 |
| slaweq | it works now, thx | 13:59 |
| *** bauzas_ is now known as bauzas | 15:25 | |
| gouthamr | slaweq: np; thank you for adding it to the wiki! | 16:08 |
| gouthamr | tc-members: we’ll have our weekly meeting here in ~14 minutes | 17:46 |
| *** bauzas_ is now known as bauzas | 17:46 | |
| gouthamr | #startmeeting tc | 18:00 |
| opendevmeet | Meeting started Tue Jun 11 18:00:54 2024 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| opendevmeet | The meeting name has been set to 'tc' | 18: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 | 18:01 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 18:01 |
| gouthamr | #topic Roll Call | 18:01 |
| gmann | o/ | 18:01 |
| dansmith | o/ | 18:01 |
| gtema | o/ | 18:01 |
| frickler | \o | 18:01 |
| JayF | o/ | 18:01 |
| gouthamr | #chair frickler | 18:01 |
| opendevmeet | Current chairs: frickler gouthamr | 18:01 |
| gouthamr | noted absence: slaweq | 18:01 |
| gouthamr | courtesy ping noonedeadpunk spotz[m] | 18:02 |
| spotz[m] | o/ | 18:03 |
| noonedeadpunk | o/ | 18:04 |
| noonedeadpunk | sorry, was a bit late | 18:04 |
| gouthamr | thanks and hello! lets get started | 18:04 |
| gouthamr | #topic AIs from last week | 18:04 |
| gouthamr | frickler: we missed you in the meeting last week, and by tradition assigned all AIs to you :D | 18:05 |
| * noonedeadpunk failed to look through zuul failures for freezer | 18:05 | |
| frickler | well I by tradition do not participate in video meetings | 18:05 |
| gouthamr | kidding, but would you like to share progress about the PyPi cleanup effort? | 18:05 |
| frickler | the pypi cleanup is done, I did the remaining projects earlier today | 18:05 |
| fungi | thanks for taking care of all of that! | 18:06 |
| frickler | I found some repos not covered yet, like those assigned to the tact sig | 18:06 |
| gouthamr | nice; thank you very much frickler.. | 18:06 |
| frickler | I'll look into extending the script to check those, too | 18:06 |
| gouthamr | ty; i thought the deb packages would figure here: | 18:09 |
| gouthamr | #link https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L415 (Repositories in a state with inconsistent pypi/package metadata) | 18:10 |
| frickler | not sure what that has to do with deb pkgs | 18:11 |
| frickler | most of those repos are not python projects though or not published to pypi | 18:11 |
| frickler | as one example diskimage-builder though is, which is listed under tact sig | 18:12 |
| frickler | (and it does have one extra maintainer) | 18:13 |
| frickler | anyway I think we can continue discussion that outside the meeting | 18:14 |
| frickler | s/on/ng/ | 18:14 |
| gouthamr | ack thanks; was extra-polating from your post earlier on #opendev | 18:14 |
| fungi | for the record, that maintainer is also on board with being removed, so there's no real dilemma in that particular case anyway | 18:14 |
| gouthamr | +1 | 18:14 |
| fungi | just a matter of looking for similar ones we may have missed | 18:14 |
| gouthamr | alright; i'll defer the AI on the zuul config errors to next week; i noticed some patches from elodilles helping monasca repos lose their incorrect zuul config | 18:16 |
| gouthamr | we've some stale jobs that were being dropped as well.. | 18:16 |
| noonedeadpunk | I do have freezer in todo list, but we;ve failed dramatically with osa trailing release | 18:16 |
| noonedeadpunk | so all my time went there :( | 18:16 |
| gouthamr | monasca's project team seems active though; the most recent patches having merged on June 4th.. so this is looking good for our M-2 tracking | 18:17 |
| gouthamr | noonedeadpunk: ty; no problem.. | 18:17 |
| gmann | yes, they are in Inactive list porject | 18:17 |
| gmann | but there were reply in ML about working on the gate fixes, let me find the link | 18:17 |
| frickler | gouthamr: I don't agree, lot's of issues with the CI still last time I checked | 18:18 |
| frickler | so IMO not in a form that could get released | 18:18 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/JVQB3SKN25FE7NHUETFYZI6HV432WYYC/ ([tc][all][monasca] Monasca Inactive projects status) | 18:19 |
| gmann | yes this one, thanks | 18:19 |
| gmann | Inactive project do not get release anyways, I think they were not released in Caracal | 18:20 |
| noonedeadpunk | no, monasca wasn't | 18:20 |
| frickler | yes, but the options iiuc are either to make active again after a cycle or to retire? | 18:20 |
| noonedeadpunk | I think it can be inactive for longer | 18:21 |
| gmann | #link https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects | 18:21 |
| gmann | yes, since last cycle | 18:21 |
| noonedeadpunk | as long as there's someone volunteer to keep development | 18:21 |
| noonedeadpunk | and align project with the bar | 18:22 |
| spotz[m] | ++ | 18:22 |
| gouthamr | ack; i'll need some background reading on what is keeping the project from being release ready.. perhaps the project team's aware through the discussion that happened on that thread ^ | 18:22 |
| gouthamr | the recent fixes relate to the urgent gate bug/s and sqlalchemy2.0 compatibility | 18:23 |
| noonedeadpunk | exit from inactive is literally same link as gmann posted | 18:23 |
| fungi | "In the case where an inactive project still does not become active during the next cycle after the cycle they entered the inactive state, the TC will discuss with the team if project will be retired before the release milestone-2 of the cycle." | 18:23 |
| fungi | #link https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#timeline | 18:23 |
| gmann | I can ping in that thread about the status as we are closure to m-2 | 18:23 |
| noonedeadpunk | though it's kinda... vague... | 18:23 |
| gmann | there is no hard deadline for retirement of inactive project instead it is matter of if there are maintainers and effort to make it active. if so we can give team more time | 18:24 |
| noonedeadpunk | as requirements for new openstack project are not applicable in many cases to inactive projects | 18:24 |
| fungi | so basically, the tc will check in if it looks like it will stay inactive, and decide whether or not it should be retired or remain inactive, is how i interpret that | 18:24 |
| gmann | they are inactive so there is no release which mean no change in situation/impact on users from what is there | 18:24 |
| noonedeadpunk | or maybe it's fine.... | 18:24 |
| gmann | as someone is already working on monasca, we should not be in hurry to retire it. instead give them more time if they need | 18:25 |
| gouthamr | +1 | 18:25 |
| noonedeadpunk | I think that still there should be PTL/DPL for inactive project happening | 18:25 |
| noonedeadpunk | if that's not a case - then retirement next cycle | 18:25 |
| gmann | noonedeadpunk: ++, yes | 18:25 |
| gouthamr | related link: | 18:25 |
| noonedeadpunk | (at least how I read that) | 18:26 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/917516 (Add TC liaison in DPL model implementation) | 18:26 |
| gmann | if no leader then it is another trigger for retirement and inactive is one separate thing | 18:26 |
| gouthamr | looks like we have next steps wrt monasca; we'll ping the maintainers on the thread again and assess if the project meets exit criteria for 2024.2 | 18:27 |
| spotz[m] | If they’re doing work I agree they should a PTL or go DPL | 18:28 |
| gmann | ++, I will reply today on ML | 18:28 |
| gouthamr | thanks gmann | 18:28 |
| gmann | spotz[m]: we have PTL for Monasca | 18:28 |
| spotz[m] | I miss read noonedeadpunk then | 18:30 |
| noonedeadpunk | yeah, I was answering fungi about `if it looks like it will stay inactive, and decide whether or not it should be retired or remain inactive` | 18:31 |
| gouthamr | this is good discussion; but lets check on other ongoing things as well | 18:31 |
| gouthamr | #topic 2024.2 TC Tracker | 18:31 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker) | 18:31 |
| gouthamr | can i request some more eyes on: | 18:32 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/917516 (Add TC liaison in DPL model implementation) | 18:32 |
| gouthamr | ^ i resolved gmann's note calling for any TC members to sign up as liaisons along with him.. but you're welcome to comment on the patch as some have already done | 18:34 |
| gouthamr | we did get an ack (thanks jamespage) on the situation with charms | 18:34 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/921731 (Appoint James Page as OpenStack Charms PTL) | 18:34 |
| gouthamr | the discussion regarding eventlet is getting some prime time on the ML | 18:36 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PQE7ALJ4NXYD4DH5XG3566FGJVNYAKEQ/ ([oslo] Remove eventlet from openstack) | 18:36 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/MBQ4NVRS4GHA3PGGYXVSYJ6PEBVKCU2T/ ([all][tc][ptls] Eventlet: Python 3.13 - Attach your seatbelt) | 18:36 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/4KOGIDNM2SWJDBBFCTCJC3ZSITLMVMDL/ ([all][tc] Eventlet migration: Call to action) | 18:37 |
| noonedeadpunk | So, should we maybe ping jamespage to update Charms PTL list? | 18:37 |
| noonedeadpunk | *path to amend list instead of replacing it | 18:37 |
| gouthamr | hberaud has revised his eventlet migration proposal as well | 18:37 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/902585 (Remove Eventlet From Openstack) | 18:38 |
| * noonedeadpunk needs to catch up on this one | 18:38 | |
| gouthamr | noonedeadpunk: yes; we've flagged it to jamespage on the gerrit change.. but probably he'll catch up with the pings here as well and make that update | 18:39 |
| noonedeadpunk | ++ | 18:39 |
| noonedeadpunk | (we just long overdue with this one) | 18:39 |
| gmann | yeah | 18:39 |
| gouthamr | anything to discuss here wrt to these chages? | 18:40 |
| noonedeadpunk | I bet there's smth to discuss in this 1.3k lines goal :D | 18:41 |
| noonedeadpunk | but probably we shouldn't go this rabbit hole in IRC | 18:42 |
| JayF | I think there's value in putting a comment on that eventlet change | 18:42 |
| gouthamr | agreed +1 | 18:42 |
| JayF | even if you have little concrete to contribute | 18:42 |
| JayF | just to ensure it stays active and we show appreciation for the research done | 18:42 |
| gouthamr | JayF++ | 18:43 |
| noonedeadpunk | +1 | 18:43 |
| gouthamr | perfect; lets move on.. | 18:45 |
| gouthamr | i think this proposal from slaweq is on topic: | 18:45 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/921500 (Update criteria for the inactive projects to become active again) | 18:45 |
| gmann | I opened it but forgot to review it, will do today | 18:46 |
| noonedeadpunk | aha | 18:47 |
| gtema | yeah, that's the problem of too many open tabs | 18:47 |
| gmann | :) | 18:47 |
| gouthamr | alright anything else to discuss wrt ongoing activities that we're tracking? | 18:48 |
| spotz[m] | Did your repo patch ever go through? | 18:49 |
| gouthamr | spotz[m]: ah no :( i haven't updated it post gmann's review | 18:50 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/918488 (Show TC and SIG repos in projects page) | 18:50 |
| gmann | yeah, Ieft some comment there mainly for keeping the SIG informations in single place | 18:50 |
| gouthamr | seems like easy fixes; except the one about the SIG website.. i'll try to knock it off today | 18:50 |
| gmann | ++ | 18:51 |
| spotz[m] | ++ | 18:51 |
| gouthamr | ty for reviewing and suggesting it | 18:51 |
| gouthamr | #topic Open Discussion | 18:51 |
| JayF | I can give a short update from the OpenInfra Days and BM SIG meetups at CERN here. | 18:51 |
| gmann | one question, did we stopped tracking/discussion the gate status in meeting? I think it was there in agenda sometime back | 18:51 |
| JayF | There was a very healthy attendance of several dozen (I think approximately 80) and attendees were extremely engaged. I also personally spoke with several people who were exploring use of OpenStack and not just current operators. | 18:52 |
| gouthamr | gmann: good point; i can bring it back for next week | 18:52 |
| gouthamr | JayF: \o/ | 18:52 |
| gmann | gouthamr: thanks, that was very useful even though there might not be any update/discussion in that particular week but keeping eyes on gate is important. | 18:53 |
| JayF | I would strongly suggest if there's an OIF Days event happening near you, please attend. It was very invigorating to have that many engaged people around. Sometimes easy to forget I think from the other side of git/irc/mailing list :) | 18:53 |
| JayF | I posted about the BM SIG, and the notes from that meetup, on the mailing list and will not repeat that here. | 18:53 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/FCUIHORVNH4RV7RJ7RZIUM5LTWB3EBJS/ ([ironic] Notes from Baremetal SIG, June 5 2024) | 18:54 |
| spotz[m] | The talks were really great at CERN and I've heard at the other locations though that was the only one I attended. Possibility of a NA one in October | 18:54 |
| gouthamr | #link https://indico.cern.ch/event/1376907/contributions/ (OpenInfra Days / User Group Meeting at CERN; collection of presentation material) | 18:56 |
| gouthamr | "Monumental to Mundane and back again" | 18:56 |
| gouthamr | :D the title is fire JayF | 18:57 |
| gouthamr | thanks for sharing | 18:57 |
| spotz[m] | It was a great talk | 18:57 |
| JayF | You'll have to ask spotz[m] if it was any good, I was on the wrong side of the stage to tell lol | 18:57 |
| JayF | I think the comment I got about it I've hung on to the most is "this is like a TEDx talk at OpenInfra" | 18:57 |
| spotz[m] | We enjoyed it, it's similar in some ways to my Why you should join a community talk | 18:58 |
| gouthamr | very nice; the buzzer goes off in ~ 1 minute; any last-minute additions to the meeting log? | 18:59 |
| gouthamr | thank you all for attending; we'll reprise this here in a week.. | 19:00 |
| gouthamr | #endmeeting | 19:00 |
| opendevmeet | Meeting ended Tue Jun 11 19:00:07 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2024/tc.2024-06-11-18.00.html | 19:00 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-06-11-18.00.txt | 19:00 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2024/tc.2024-06-11-18.00.log.html | 19:00 |
| spotz[m] | Thanks all | 19:01 |
| *** bauzas_ is now known as bauzas | 19:44 | |
| *** bauzas_ is now known as bauzas | 19:57 | |
| *** bauzas_ is now known as bauzas | 20:05 | |
| *** bauzas_ is now known as bauzas | 20:50 | |
| *** bauzas_ is now known as bauzas | 20:58 | |
| *** bauzas_ is now known as bauzas | 21:06 | |
| *** bauzas_ is now known as bauzas | 23:22 | |
| *** bauzas_ is now known as bauzas | 23:55 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!