Tuesday, 2025-05-06

gibihberaud[m]: I see a bit of a problem with the worker process forking. https://review.opendev.org/c/openstack/oslo.service/+/945720/comments/fb5d6632_f0eaf102 I can try to patch oslo.config to see if that helps but this can easily get complicated12:17
hberaud[m]ack12:20
hberaud[m]friendly reminder, our bi-monthly meeting will start in~20 mins14:37
hberaud[m]#startmeeting openstack-eventlet-removal15:00
opendevmeetMeeting started Tue May  6 15:00:05 2025 UTC and is due to finish in 60 minutes.  The chair is hberaud[m]. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'openstack_eventlet_removal'15:00
hberaud[m]Ping list: amorin, JayF, gouthamr, ralonsoh15:00
ralonsohsorry, this is too late for me, I need to leave in a couple of mins15:00
hberaud[m]Here is our new meeting tracker for flamingo https://etherpad.opendev.org/p/flamingo-eventlet-tracking15:00
hberaud[m]ralonsoh: no problem15:01
hberaud[m]lets wait 1 or 2 mins for other people15:01
hberaud[m]#topic sharing updates15:02
hberaud[m]1. the new backend of oslo.service is almost there https://review.opendev.org/c/openstack/oslo.service/+/945720, I think we are now close from the truth15:03
hberaud[m]2. Bad news: our upstream CI (on https://github.com/eventlet/eventlet/) is broke by pypy jobs and unfortunatelly, I don't enough power on the upstream repo to make this job non voting. I initiated a discussion with the previous repo owners to get all the full power on the setting of this repo, I'm waiting for news (see the discussion here https://github.com/eventlet/eventlet/pull/1035)15:06
hberaud[m]The problem is that this job block all the other pull requests15:06
hberaud[m]Without update from previous maintainers, I'll be forced to commit directly on the repo to disable this job without passing through reviews. I think it will unlock the situation15:08
hberaud[m]there is pending reviews about SSL fixes etc, and we have to finish our workaround about Py3.13, and we have to start working on the integration with Py3.14, so at some point we will be forced to manually disable this job by one way or another15:10
hberaud[m]anyway15:10
hberaud[m]Else, I see excellent progress on Nova, Neutron, and Glance since the PTG (our last meeting)15:11
hberaud[m]For those who are interested, gibi is tracking Nova's advancement/strategy here https://gibizer.github.io/categories/eventlet/ Please take a look that's an interesting reading15:12
hberaud[m]And I think that's all for me15:12
hberaud[m]do you have updates that you want to share with us?15:13
hberaud[m]#topic Open Discussion15:15
hberaud[m]Anything else that you want to discuss today?15:15
hberaud[m]Thanks everyone, next meeting is on May 20, see you there15:17
hberaud[m]#endmeeting15:17
opendevmeetMeeting ended Tue May  6 15:17:16 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:17
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_eventlet_removal/2025/openstack_eventlet_removal.2025-05-06-15.00.html15:17
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_eventlet_removal/2025/openstack_eventlet_removal.2025-05-06-15.00.txt15:17
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_eventlet_removal/2025/openstack_eventlet_removal.2025-05-06-15.00.log.html15:17
JayFhberaud[m]: I would not have an expectation of being able to get in touch with the previous maintainer. Especially given the geopolitical situation, he seemed to be in during the handover15:19
JayFI am plus one to you doing what you need to do to get that repo back in good shape and I'm happy to act as a human reviewer as you take the action if it'd make you feel better15:20
hberaud[m]JayF: the good news is that Sergey (the main former maintainer) gave us short updates, but now we are waiting the actions.15:22
hberaud[m]That's not the first time I request these additional ownership rights, I would prefer to get them once and for all15:23
JayFOh nice15:23
hberaud[m]I do not love to harass people each 6 months due to a admin problem on the repo...15:24
hberaud[m]That would solve that15:24
JayFIt's one of those things where if we don't have the master key, are we really the maintainers15:24
hberaud[m]Well we have the writing rights... but some configurations remains hidden to us15:25
hberaud[m]and jobs voting permission is one of them15:26
hberaud[m]given the time left to live for eventlet, I'd argue that we could continue to live without that, but I prefer to not leave a chance to Murphy's law15:28
JayFwell we also said we'd give keys over to someone if they wanted to keep it alive too15:30
JayFwe can't fulfill that promise without the access to do so15:30
JayF(not that I think it's likely someone will be clamoring for eventlet in 2026)15:30
hberaud[m]indeed, that's true15:31
hberaud[m](the keys transmition)15:32
hberaud[m](and the 2026 too :) )15:32
hberaud[m]and without that, won't be able to archive that project properly on github15:33
hberaud[m]*neither15:34
* gibi updated his calender so next time he won't miss the meeting16:54

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