#eventlet-removal - Progress & Updates - Flamingo milestone 1
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash. ## OpenStack Updates Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime. Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https://review.opendev.org/c/openstack/devstack/+/948436. Everybody will be able to benefit from these adaptations. Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in threading mode. oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/oslo.service/+/945720 ## Eventlet Updates Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews. Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed. The Python 3.13 issues are still not solved and require further work. ## Call to Action Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative! If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ and are encouraged to join the #openstack-eventlet-removal IRC channel to get help. You'll benefit quickly from the advantages of running your deliverables without using Eventlet. ## Final Thoughts Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent this from happening to you. We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo. The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience. Your journey start here https://removal.eventlet.org/ Thanks for reading. -- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
Hi! Thank you for the update, here is the etherpad I created for Ironic: https://etherpad.opendev.org/p/ironic-eventlet-removal Dmitry On 5/20/25 6:44 PM, Herve Beraud wrote:
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash.
## OpenStack Updates
Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime.
Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ <https://gibizer.github.io/categories/eventlet/>
Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https:// review.opendev.org/c/openstack/devstack/+/948436 <https:// review.opendev.org/c/openstack/devstack/+/948436>. Everybody will be able to benefit from these adaptations.
Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in threading mode.
oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/ oslo.service/+/945720 <https://review.opendev.org/c/openstack/ oslo.service/+/945720>
## Eventlet Updates
Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews.
Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed.
The Python 3.13 issues are still not solved and require further work.
## Call to Action
Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative!
If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ <https://removal.eventlet.org/> and are encouraged to join the #openstack-eventlet-removal IRC channel to get help.
You'll benefit quickly from the advantages of running your deliverables without using Eventlet.
## Final Thoughts
Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent this from happening to you.
We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo.
The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience.
Your journey start here https://removal.eventlet.org/ <https:// removal.eventlet.org/>
Thanks for reading.
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
Le mar. 20 mai 2025 à 18:47, Dmitry Tantsur <dtantsur@protonmail.com> a écrit :
Hi!
Thank you for the update, here is the etherpad I created for Ironic: https://etherpad.opendev.org/p/ironic-eventlet-removal
Thank you Dimitry, that looks pretty amazing, kudos! Let me add it to our collection of efforts.
Dmitry
On 5/20/25 6:44 PM, Herve Beraud wrote:
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash.
## OpenStack Updates
Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime.
Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ <https://gibizer.github.io/categories/eventlet/>
Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https:// review.opendev.org/c/openstack/devstack/+/948436 <https:// review.opendev.org/c/openstack/devstack/+/948436>. Everybody will be able to benefit from these adaptations.
Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in threading mode.
oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/ oslo.service/+/945720 <https://review.opendev.org/c/openstack/ oslo.service/+/945720>
## Eventlet Updates
Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews.
Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed.
The Python 3.13 issues are still not solved and require further work.
## Call to Action
Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative!
If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ <https://removal.eventlet.org/> and are encouraged to join the #openstack-eventlet-removal IRC channel to get help.
You'll benefit quickly from the advantages of running your deliverables without using Eventlet.
## Final Thoughts
Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent this from happening to you.
We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo.
The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience.
Your journey start here https://removal.eventlet.org/ <https:// removal.eventlet.org/>
Thanks for reading.
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
Hi hberaud o/ Thanks for the updates. The Watcher team also started investigating eventlet usage in the code and proposed some initial actions. We started to follow up this effort in our weekly meeting too. Our etherpad is the following: https://etherpad.opendev.org/p/watcher-eventlet-removal BR, On Tue, May 20, 2025 at 3:51 PM Herve Beraud <hberaud@redhat.com> wrote:
Le mar. 20 mai 2025 à 18:47, Dmitry Tantsur <dtantsur@protonmail.com> a écrit :
Hi!
Thank you for the update, here is the etherpad I created for Ironic: https://etherpad.opendev.org/p/ironic-eventlet-removal
Thank you Dimitry, that looks pretty amazing, kudos! Let me add it to our collection of efforts.
Dmitry
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash.
## OpenStack Updates
Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime.
Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ <https://gibizer.github.io/categories/eventlet/>
Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https:// review.opendev.org/c/openstack/devstack/+/948436 <https:// review.opendev.org/c/openstack/devstack/+/948436>. Everybody will be able to benefit from these adaptations.
Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in
mode.
oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/ oslo.service/+/945720 <https://review.opendev.org/c/openstack/ oslo.service/+/945720>
## Eventlet Updates
Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews.
Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed.
The Python 3.13 issues are still not solved and require further work.
## Call to Action
Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative!
If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ <https://removal.eventlet.org/> and are encouraged to join the #openstack-eventlet-removal IRC channel to get help.
You'll benefit quickly from the advantages of running your deliverables without using Eventlet.
## Final Thoughts
Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent
On 5/20/25 6:44 PM, Herve Beraud wrote: threading this
from happening to you.
We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo.
The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience.
Your journey start here https://removal.eventlet.org/ <https:// removal.eventlet.org/>
Thanks for reading.
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
-- Douglas Viroel - dviroel
Thanks Douglas. I also added your etherpad into the teams efforts tracker https://wiki.openstack.org/wiki/Eventlet-removal#Teams_efforts Le mar. 20 mai 2025 à 21:02, Douglas Viroel <viroel@gmail.com> a écrit :
Hi hberaud o/
Thanks for the updates. The Watcher team also started investigating eventlet usage in the code and proposed some initial actions. We started to follow up this effort in our weekly meeting too. Our etherpad is the following: https://etherpad.opendev.org/p/watcher-eventlet-removal
BR,
On Tue, May 20, 2025 at 3:51 PM Herve Beraud <hberaud@redhat.com> wrote:
Le mar. 20 mai 2025 à 18:47, Dmitry Tantsur <dtantsur@protonmail.com> a écrit :
Hi!
Thank you for the update, here is the etherpad I created for Ironic: https://etherpad.opendev.org/p/ironic-eventlet-removal
Thank you Dimitry, that looks pretty amazing, kudos! Let me add it to our collection of efforts.
Dmitry
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash.
## OpenStack Updates
Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime.
Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ <https://gibizer.github.io/categories/eventlet/>
Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https:// review.opendev.org/c/openstack/devstack/+/948436 <https:// review.opendev.org/c/openstack/devstack/+/948436>. Everybody will be able to benefit from these adaptations.
Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in
mode.
oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/ oslo.service/+/945720 <https://review.opendev.org/c/openstack/ oslo.service/+/945720>
## Eventlet Updates
Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews.
Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed.
The Python 3.13 issues are still not solved and require further work.
## Call to Action
Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative!
If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ <https://removal.eventlet.org/> and are encouraged to join the #openstack-eventlet-removal IRC channel to get help.
You'll benefit quickly from the advantages of running your deliverables without using Eventlet.
## Final Thoughts
Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent
On 5/20/25 6:44 PM, Herve Beraud wrote: threading this
from happening to you.
We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo.
The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience.
Your journey start here https://removal.eventlet.org/ <https:// removal.eventlet.org/>
Thanks for reading.
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
-- Douglas Viroel - dviroel
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
Hello all: This is the Neutron etherpad: https://etherpad.opendev.org/p/neutron-eventlet-deprecation (we used "deprecation" because we didn't have the tag "eventlet-removal" when we created it) So far, we have achieved the following tasks: * Remove the usage of eventlet in the Neutron API (not the maintenance method, periodic or RPC). Right now, the API only works with WSGI module. * MIgrate the following agents: ** OVN agent ** OVN metadata agent ** Metadata agent ** SRIOV agent The OVS agent, L3 agent and DHCP are the next ones to be migrated and are very close. We are actually expecting the oslo.service new backend ("threading") to continue with these agents removal. Regards. On Wed, May 21, 2025 at 10:20 AM Herve Beraud <hberaud@redhat.com> wrote:
Thanks Douglas. I also added your etherpad into the teams efforts tracker https://wiki.openstack.org/wiki/Eventlet-removal#Teams_efforts
Le mar. 20 mai 2025 à 21:02, Douglas Viroel <viroel@gmail.com> a écrit :
Hi hberaud o/
Thanks for the updates. The Watcher team also started investigating eventlet usage in the code and proposed some initial actions. We started to follow up this effort in our weekly meeting too. Our etherpad is the following: https://etherpad.opendev.org/p/watcher-eventlet-removal
BR,
On Tue, May 20, 2025 at 3:51 PM Herve Beraud <hberaud@redhat.com> wrote:
Le mar. 20 mai 2025 à 18:47, Dmitry Tantsur <dtantsur@protonmail.com> a écrit :
Hi!
Thank you for the update, here is the etherpad I created for Ironic: https://etherpad.opendev.org/p/ironic-eventlet-removal
Thank you Dimitry, that looks pretty amazing, kudos! Let me add it to our collection of efforts.
Dmitry
TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash.
## OpenStack Updates
Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime.
Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ <https://gibizer.github.io/categories/eventlet/>
Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https:// review.opendev.org/c/openstack/devstack/+/948436 <https:// review.opendev.org/c/openstack/devstack/+/948436>. Everybody will be able to benefit from these adaptations.
Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in
mode.
oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/ oslo.service/+/945720 <https://review.opendev.org/c/openstack/ oslo.service/+/945720>
## Eventlet Updates
Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews.
Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed.
The Python 3.13 issues are still not solved and require further work.
## Call to Action
Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of
initiative!
If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ <https://removal.eventlet.org/> and are encouraged to join the #openstack-eventlet-removal IRC channel to get help.
You'll benefit quickly from the advantages of running your deliverables without using Eventlet.
## Final Thoughts
Postponing the beginning of the migration will put additional
related to growing runtime failures of Eventlet. We want to prevent
On 5/20/25 6:44 PM, Herve Beraud wrote: threading this pressure this
from happening to you.
We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo.
The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience.
Your journey start here https://removal.eventlet.org/ <https:// removal.eventlet.org/>
Thanks for reading.
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
-- Douglas Viroel - dviroel
-- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/
participants (4)
-
Dmitry Tantsur
-
Douglas Viroel
-
Herve Beraud
-
Rodolfo Alonso Hernandez