3928511919
This change gives the keystone role the ability to deploy keystone using only uWSGI, which eliminates Apache and all of its dependencies from the environment. While this capability is not as feature rich as the apache based deployment, which is still the default, it does offer a signficant reduction in process overhead targeting minimal deployment usec-ases, for deployments which do not need or want advanced keystone features this is a huge benefit. Signed-off-by: Kevin Carter <kevin@cloudnull.com> Change-Id: I5a8484082f6331d2c5a452af2760c8e79d44fab8
16 lines
705 B
YAML
16 lines
705 B
YAML
---
|
|
features:
|
|
- |
|
|
The keystone role now supports the option `keystone_use_uwsgi`, which will
|
|
allow deployers the ability to run keystone via uWSGI without needing the
|
|
apache webserver. When the `keystone_use_uwsgi` option is enabled, it will
|
|
setup the uWSGI process on port 5000.
|
|
other:
|
|
- |
|
|
The keystone role can now has the ability to run a minimal uWSGI process
|
|
for keystone when the option `keystone_use_uwsgi` is set **true**. This
|
|
feature provides operators the ability to run a minimal install without
|
|
apache. While the minimal deployment is functional, it is not featureful.
|
|
Things like modshib and oath are not supported when running the minimal
|
|
setup.
|