womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Run nova-api and -metadata in threaded mode

Browse Source 
It turns out that nova-api and nova-metadata only depend on spawning
threads via scatter-gather. The scatter-gather already supports both
eventlet and threading mode so we can switch these services.

Our WSGI services (nova-api, nova-metadata) are not relying on
oslo.service to fork worker processes, but expect the web server to
handle that (uwsgi, apache mod_wsgi). This means we don't need to handle
any forking issues as no nova code runs before the fork.

Change-Id: Id3a339c605dfc730bdb7994c3ca45baafeb5af80
Signed-off-by: Balazs Gibizer <gibi@redhat.com>
This commit is contained in:
Balazs Gibizer
2025-06-06 15:19:31 +02:00
parent 3e33b58092
commit d6a3f86329
3 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/admin/concurrency.rst
+2 -2
View File
@@ -24,8 +24,8 @@ threading mode at service startup via setting the environment variable
.. note::
Since nova 32.0.0 (2025.2 Flamingo) the nova-scheduler can be switched to
native threading mode.
Since nova 32.0.0 (2025.2 Flamingo) the nova-scheduler, nova-metadata, and
nova-api can be switched to native threading mode.
Tunables for the native threading mode