c4105464e6
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
21 lines
870 B
YAML
21 lines
870 B
YAML
---
|
|
features:
|
|
- The ``heat-api``, ``heat-api-cfn``, and
|
|
``heat-api-cloudwatch`` services have moved to run
|
|
as a uWSGI applications. You can set the max number
|
|
of WSGI processes, the number of processes, threads,
|
|
and buffer size utilizing the
|
|
``heat_wsgi_processes_max``,
|
|
``heat_wsgi_processes``, ``heat_wsgi_threads``,
|
|
and ``heat_wsgi_buffer_size``.
|
|
Additionally, you can override any settings in the
|
|
uWSGI ini configuration file using the
|
|
``heat_api_uwsgi_ini_overrides``,
|
|
``heat_api_cfn_uwsgi_ini_overrides``, and
|
|
``heat_api_cloudwatch_uwsgi_ini_overrides`` settings.
|
|
The uWSGI applications will listen on the addresses
|
|
specified by ``heat_api_uwsgi_bind_address``,
|
|
``heat_api_cfn_uwsgi_bind_address``, and
|
|
``heat_api_cloudwatch_uwsgi_bind_address``
|
|
respectively. Which all default to ``0.0.0.0``.
|