Hi, On 10/9/24 9:36 AM, Herve Beraud wrote:
Hey there,
@Arnaud: Mistral is already in our list of identified deliverables: https://wiki.openstack.org/wiki/Eventlet- removal#Map_of_the_Impacted_Deliverables <https://wiki.openstack.org/ wiki/Eventlet-removal#Map_of_the_Impacted_Deliverables>. But thanks for the heads up.
By the way, was this list compiled based on a text search? It lists a few *-specs repositories which are unlikely to be impacted. The mentions of puppet are also suspicious. From the ironic side, I suspect we won't be migrating ironic-inspector and its client as they are deprecated. I haven't discussed it with the team though. Dmitry
@engineer2024: I'll let the Nova team answer your question.
Le mar. 8 oct. 2024 à 22:56, Arnaud Morin <arnaud.morin@gmail.com <mailto:arnaud.morin@gmail.com>> a écrit :
Hey Herve,
Please add mistral to your list. I havn't dig into code for this yet, but it's in requirements and it seems to be used by some of the services.
Regards, Arnaud.
On 04.10.24 - 17:08, Herve Beraud wrote: > We’re excited to share the latest updates on our ongoing efforts to phase > out Eventlet across our various OpenStack projects. Below you’ll find a > summary of our progress, key milestones, and important dates to keep in > mind as we move forward with this critical initiative. > > ## Current Status > > We’ve completed the initial analysis phase across more than 120 OpenStack > projects. This includes identifying the various patterns where Eventlet is > currently in use and evaluating where it can be safely removed or disabled. > Here are some highlights: > > - Completed Analysis: Projects where Eventlet is used include (but are not > limited to): Aodh, Barbican, Nova, Neutron, Tacker, Taskflow, Trove, Venus, > Watcher, and Zun. > > - Eventlet Optional: Several projects have been identified where Eventlet > seems to be optional and can be disabled with minimal impact. For these > projects, we will move forward the discussion with teams to try > deactivating Eventlet in upcoming updates. Once done, projects of this kind > would be able to start their migration with more serenity. > > - Eventlet Required: Some projects still rely heavily on Eventlet for core > functionality. For these, we are going to develop specific migration plans. > > ## Migration Plans in Progress > > - oslo.db: Preparing its Asyncio based engine facade; > - oslo.service: Refactoring plans being discussed to minimize disruption > during the migration; > - glance: Refactoring code to use native thread model rather than Eventlet > > More details can be found here: > https://review.opendev.org/q/topic:%22eventlet-removal%22 <https://review.opendev.org/q/topic:%22eventlet-removal%22> > > ## Latest Updates > > - Community Goal Transition: The ongoing community goal for removing > Eventlet is now in the process of becoming an official "selected" goal, > https://review.opendev.org/c/openstack/governance/+/931254 <https://review.opendev.org/c/openstack/governance/+/931254>. > > - Pattern Identification Completed: We’ve identified key patterns related > to Eventlet usage, including its common integration with monkey_patch(), > eventlet.Timeout, eventlet.GreenPool, and eventlet.wsgi.server(). Visit the > official wiki to get more details > https://wiki.openstack.org/wiki/Eventlet- removal#Identifying_Common_Pattern <https://wiki.openstack.org/wiki/ Eventlet-removal#Identifying_Common_Pattern> > > ## Important Dates > > - October 21st: cross PTG session. > - October 23rd: cross PTG session (Q&A session and Open Discussion session) > > ## Call to Action > > We need your involvement to accelerate the progress of this initiative! If > your project is affected by Eventlet, now is the time to start planning > your migration. Teams are encouraged to take immediate steps in assessing > how to deactivate Eventlet or to transition to alternative solutions. > > We defined key roles and responsibilities. Those will help us to lower the > cost of the migration for our community. Teams are invited to assign them > now. Being ready as soon as possible will allow you to better take > advantage of the coming PTG sessions. > > Please find more details about these roles and their short terms tasks: > https://wiki.openstack.org/wiki/Eventlet- removal#Roles_and_Responsibilities <https://wiki.openstack.org/wiki/ Eventlet-removal#Roles_and_Responsibilities> > > ## Final Thoughts > > This is a significant step forward for improving the stability, > scalability, and maintainability of our projects. With your continued > support, we’re confident that this migration will bring substantial > benefits to the OpenStack community. > > If there are any questions or if you need assistance with your project’s > transition away from Eventlet, please join the discussion on the > #eventlet-removal channels (OpenStack irc, RedHat slack, mailing list). > > Thank you for your dedication and hard work! > > -- > Hervé Beraud > Senior Software Engineer at Red Hat > irc: hberaud > https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>