Make Eventlet removal deadlines more acceptable for operators

The current eventlet removal deadlines appear a bit optimistic for multiple
reasons :
 - at least for Nova, the consensus is about supporting both eventlet and
   threading usage during a same SLURP release, so operators could test services
   threading performance and possibly be back using eventlet if they find issues
 - we can't drop eventlet by a non-SLURP release or operators wouldn't be able
   to verify performance before upgrading
 - we don't know the current state of effort for all the projects

I propose then those new deadlines for the goal.

Change-Id: I0ff16e2ff095e20bc1de7ae06010e0658e0aa431
Signed-off-by: Sylvain Bauza <sbauza@redhat.com>
This commit is contained in:
Sylvain Bauza
2025-06-19 16:57:52 +02:00
parent a3cc03b7b5
commit 981727b3d5

View File

@@ -50,9 +50,18 @@ Completion Criteria
#. (2025.2) Get an OpenStack deliverable as reference user project selected to
test Oslo changes related to new Asyncio based drivers;
#. (2025.2) Get non actively maintained OpenStack deliverables retired;
#. (2026.2) Get all other OpenStack deliverables relying on Eventlet migrated;
#. (2027.1) Get usage of Eventlet in oslo deliverables removed;
#. (2027.2) Get Eventlet retired from OpenStack;
#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained
support for running without Eventlet.
#. (2027.1) Deprecate the Eventlet support. To have a SLURP target release
supporting both the old Eventlet and any new concurrency mode, this release
keeps the Eventlet support.
#. (2027.2) Get usage of Eventlet in all OpenStack (including oslo
deliverables) removed;
.. note:: Any project finishing the work before 2026.2 can do the step
mentioned in 2027.1 early but make sure you have a one SLURP cycle to
support both mode and deprecation phase.
References
==========