---- On Fri, 13 Jun 2025 08:33:25 -0700 Jay Faulkner <jay@gr-oss.io> wrote ---
On 6/13/25 5:08 AM, Balazs Gibizer wrote:
Hi Stackers!
I would like to sync about the planned timeline of dropping eventlet support from OpenStack / Oslo.
Nova definitely needs at least the full 2026.1 cycle to have a chance to transform the nova-compute service. But this plan already feels stretched based on the progress in the current cycle. So being conservative means we need the 2026.2 cycle as a buffer.
Nova would like to keep a release where we support both eventlet and threading in parallel. So that operators can do the switching from eventlet to threading outside of the upgrade procedure. (This was an explicit request from them during the PTG). So 2026.2 could be that version where nova fully supports both concurrency mode, while eventlet can be marked deprecated. Then the 2027.1 release could be the first release dropping eventlet.
However we need to align with the SLURP upgrade as well. 2026.1 is a SLURP. But in that release Nova might not be ready to have all services running in threading mode. So the 2026.1 - 2027.1 SLURP upgrade would force the operators to change the concurrency mode during the upgrade itself.
I see two ways forward: * A) We say that operators who want to do the concurrency mode change outside of an upgrade could not skip the 2026.2 release, i.e. they cannot do SLURP directly from 2026.1. to 2027.1.
This has a big impact on upgrades and breaks our SLURP model.
* B) We keep supporting the eventlet mode in the 2027.1 release as well and only dropping support in 2028.1.
I am in favour of this option. I was reading the goal doc about the timeline and found something in 'Completion Criteria' section[1] which says: - (2027.1) Get usage of Eventlet in oslo deliverables removed; - "(2027.2) Get Eventlet retired from OpenStack;" Again, 2027.2 (non-SLURP) is mentioned as eventlet retirement, I do not know if any technical reason to do it in non-SLURP or it can be moved to SLURP release. Maybe hberaud knows. Anyway, thanks gibi for bringing this. There are many projects that have not started the work yet (Nova might have more work compared to others), but I think we should discuss/re-discuss the timelines considering all projects/challenges. Accordingly, update the goal doc for the exact timelines and what the impact will be for projects that do not finish work as per the timelines (for example upgrade issue, workaround etc). [1] https://governance.openstack.org/tc/goals/selected/remove-eventlet.html#comp... -gmaan
Keeping eventlet running for that long is not something that is a worthy investment of time. The oslo libraries are showing a deprecation of 2026.2, I've been using that date as the target for all Ironic work as well.
Beyond the oslo team (who I don't speak for), there are folks -- like Itamar on behalf of GR-OSS -- who are doing work behind the scenes to keep eventlet running - barely. I do not expect the GR-OSS investment in this work to extend much past the midpoint of 2026.
My $.02,
Jay Faulkner Open Source Developer G-Research Open Source Software