4349e4156e
Ironic, like most openstack services these days, needs to have it's wsgi module referenced as a module, and used under something like uwsgi or gunicorn instead of with Apache mod_wsgi. Assisted-by: claude code Change-Id: I6a2c2688f73b71f94103622a9e821cab67be053e Signed-off-by: Jay Faulkner <jay@jvf.cc>
27 lines
1021 B
YAML
27 lines
1021 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``wsgi_scripts`` entry point ``ironic-api-wsgi`` has been removed
|
|
from ``setup.cfg``. WSGI servers should now use the module path
|
|
``ironic.wsgi:application`` directly instead of the generated script.
|
|
This change aligns with the OpenStack goal to migrate from WSGI scripts
|
|
to module paths and is compatible with modern Python packaging tools.
|
|
|
|
For example, with gunicorn::
|
|
|
|
gunicorn ironic.wsgi:application
|
|
|
|
Or with uwsgi::
|
|
|
|
[uwsgi]
|
|
module = ironic.wsgi:application
|
|
- |
|
|
The Apache mod_wsgi sample configuration has been removed. Operators
|
|
should use modern WSGI servers like uWSGI or Gunicorn instead, which
|
|
provide better performance and are simpler to configure. See the
|
|
updated deployment documentation for examples.
|
|
deprecations:
|
|
- |
|
|
While the legacy ``ironic.api.wsgi:initialize_wsgi_app()`` function
|
|
remains available for backward compatibility, new deployments should
|
|
use ``ironic.wsgi:application`` instead. |