openstack-ansible/releasenotes/notes/nova_uwsgi-af062fa20317d41c.yaml
Andy McCrae c4105464e6 Pin SHA's for stable/pike rc1
We may need a few more bumps - specifically for some upstream projects
that don't have a stable/pike branch yet. Namely:

swift
magnum
magnum_dashboard
nova-lxd
ceilometer
aodh
dragonflow

We should move to a SHA-bump approach from now to allow us to release
RC1 and further RCs without having to re-pin role SHA's.

Additionally, since the endpoint for placement has changed to / instead
of /placement the healthchk needs to anticipate a "401 - Unauthorized".

Change-Id: Iccc4d4b7aa3a69eb3c87e50aaae9ccb7b4b7135e
2017-08-16 16:20:19 +01:00

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``.