823a80bd44
The placement service is already setup to use UWsgi, we need to move the other Nova services to follow suit as part of our community goal for Pike. Additionally, we need to clean up the nginx configuration as we are moving away from fronting uWSGI with nginx inside the roles. Depends-On: Ib66b9709fb88205eaf3f133c87357a4dbbdde5ae Change-Id: If6c30e00c1c753692c970457b75e3ae7f5cc066c Implements: blueprint goal-deploy-api-in-wsgi
24 lines
995 B
YAML
24 lines
995 B
YAML
---
|
|
features:
|
|
- The ``nova-api``, and ``nova-metadata`` services
|
|
have moved to run as uWSGI applications. You can
|
|
override their uwsgi configuration files using the
|
|
``nova_api_os_compute_uwsgi_ini_overrides``, and
|
|
``nova_api_metadata_uwsgi_ini_overrides`` settings.
|
|
upgrade:
|
|
- The ``nova-placement`` service now runs as a uWSGI
|
|
application that is not fronted by an nginx
|
|
web-server by default. After upgrading, if the
|
|
``nova-placement`` service was running on a host
|
|
or container without any other services requiring
|
|
nginx, you should manually remove nginx.
|
|
deprecations:
|
|
- Settings related to nginx and the placement
|
|
will no longer serve any purpose, and should
|
|
be removed. Those settings are as follows -
|
|
``nova_placement_nginx_access_log_format_extras``,
|
|
``nova_placement_nginx_access_log_format_combined``,
|
|
``nova_placement_nginx_extra_conf``,
|
|
``nova_placement_uwsgi_socket_port``, and
|
|
``nova_placement_pip_packages``.
|