Because we haven't heard any objection, I've proposed the backport and a new 2025.1 release to announce the deprecation. As mentioned earlier, we'll drop these standalone services during this cycle. On 6/20/25 3:53 PM, Takashi Kajinami wrote:
Hello,
Historically heat has provided two methods to deploy api services (native heat api and heat CFN api). 1. standalone script based on eventlet 2. wsgi application run by server framework like apache or uwsgi
Now the heat team is trying to get rid of eventlet following the global effort to replace it, and the current blocker is 1 because we have no good alternative to re-implement the standaloe service. The global migration strategy is to remove standalone api services using eventlet and provide only wsgi application.
So I'm now sending an email to ask for any input, in case if any operator has concern about our current plan below. - Backport deprecation of standalone api scripts to 2025.1 - Remove these scripts during 2025.2 This means that any operators should use 3rd party server framework like uwsgi and apache+mod_wsgi to run heat api from 2025.2 .
I understand backporting deprecation is something we won't accept usually, but I've seen this pattern was done in the past for a few exceptions like Hyper-V support removal.
If we hear no objections/concerns for a week then, we aim to merge the removal during this cycle.
Thank you, Takashi