b1fe866f42
As part of the Pike goals we are moving api services to run as WSGI apps. octavia-api service is set up as a wsgi app, and this patch moves it over to uWSGI. Since this is just a drop in replacement for the existing eventlet service, operators an deployers should notice no difference. Additionally, fix bug whereby git_install_branch was set to "stable/ocata" for testing. Change-Id: I0c473977e015015bd252a486c7191a95781b38a4 Implements: blueprint goal-deploy-api-in-wsgi
16 lines
624 B
YAML
16 lines
624 B
YAML
---
|
|
features:
|
|
- The ``octavia-api`` service has moved to run as a
|
|
uWSGI application. You can set the max number of
|
|
WSGI processes, the number of processes, threads,
|
|
and buffer size utilizing the
|
|
``octavia_wsgi_processes_max``,
|
|
``octavia_wsgi_processes``, ``octavia_wsgi_threads``,
|
|
and ``octavia_wsgi_buffer_size``.
|
|
Additionally, you can override any settings in the
|
|
uWSGI ini configuration file using the
|
|
``octavia_api_uwsgi_ini_overrides`` setting.
|
|
The uWSGI application will listen on the address
|
|
specified by ``octavia_uwsgi_bind_address`` which
|
|
defaults to ``0.0.0.0``.
|