Update Queens info about Glance and uWSGI
Adds a "Known Issues" releasenote and updates the "running glance under httpd" documentation. Change-Id: Ifc315b40cea23af95fc969a9c3a9479e8692792c
This commit is contained in:
parent
6033bad62f
commit
3d5f33f2b3
@ -7,6 +7,15 @@ enables you to run it with a real web server like Apache HTTPD or nginx. To
|
|||||||
deploy this there are several patterns. This doc shows two common ways of
|
deploy this there are several patterns. This doc shows two common ways of
|
||||||
deploying Glance with Apache HTTPD.
|
deploying Glance with Apache HTTPD.
|
||||||
|
|
||||||
|
.. warning::
|
||||||
|
As pointed out in the Pike and Queens release notes (see the "Known Issues"
|
||||||
|
section of each), the Glance project team recommends that Glance be run in
|
||||||
|
its normal standalone configuration, particularly in production
|
||||||
|
environments. The full functionality of Glance is not available when Glance
|
||||||
|
is deployed in the manner described in this document. In particular, the
|
||||||
|
interoperable image import functionality does not work under such
|
||||||
|
configuration. See the release notes for details.
|
||||||
|
|
||||||
uWSGI Server HTTP Mode
|
uWSGI Server HTTP Mode
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
|
31
releasenotes/notes/queens-uwsgi-issues-4cee9e4fdf62c646.yaml
Normal file
31
releasenotes/notes/queens-uwsgi-issues-4cee9e4fdf62c646.yaml
Normal file
@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
issues:
|
||||||
|
- |
|
||||||
|
The Pike release notes pointed out that although support had been added to
|
||||||
|
run Glance as a WSGI application hosted by a web server, the Glance team
|
||||||
|
recommended that Glance be run in its normal standalone configuration,
|
||||||
|
particularly in production environments.
|
||||||
|
|
||||||
|
We renew that recommendation for the Queens release. In particular, Glance
|
||||||
|
tasks (which are required for the interoperable image import functionality)
|
||||||
|
do not execute when Glance is run under uWSGI (which is the OpenStack
|
||||||
|
recommended way to run WSGI applications hosted by a web server).
|
||||||
|
|
||||||
|
This is in addition to the chunked transfer encoding problems addressed by
|
||||||
|
`Bug 1703856`_ and will be more difficult to fix. (Additionally, as far as
|
||||||
|
we are aware, the fix for `Bug 1703856`_ has never been tested at scale.)
|
||||||
|
Briefly, Glance tasks are run by the API service and would have to be split
|
||||||
|
out into a different service so that API alone would run under uWSGI. The
|
||||||
|
Glance project team did not have sufficient testing and development
|
||||||
|
resources during the Queens cycle to attempt this (or even to discuss
|
||||||
|
whether this is in fact a good idea).
|
||||||
|
|
||||||
|
The Glance project team is committed to the stability of Glance. As part
|
||||||
|
of OpenStack, we are committed to `The Four Opens`_. If the ability to run
|
||||||
|
Glance under uWSGI is important to you, feel free to participate in the
|
||||||
|
Glance community to help coordinate and drive such an effort. (We gently
|
||||||
|
remind you that "participation" includes providing testing and development
|
||||||
|
resources.)
|
||||||
|
|
||||||
|
.. _`Bug 1703856`: https://bugs.launchpad.net/glance/+bug/1703856
|
||||||
|
.. _`The Four Opens`: https://governance.openstack.org/tc/reference/opens.html
|
Loading…
Reference in New Issue
Block a user