Update http deploy docs to be a bit more explicit
There have been some lessons learned on how to best deploy glance from using uwsgi in the gate. This commit updates the docs a bit to explain some pitfalls to avoid. This also adds a glossary at th end of the docs to explain common terms. There are several very similar terms with related meanings used in the doc so to clear up confusing the glossary should be helpful. Change-Id: I255d2049a5d519909c88101833ddd259328fcee7
This commit is contained in:
Matthew Treinish
parent
4731910f94
commit
e6219582c8
|
|
@ -7,21 +7,22 @@ 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
|
||||
deploying Glance with Apache HTTPD.
|
||||
|
||||
uwsgi
|
||||
-----
|
||||
uWSGI Server HTTP Mode
|
||||
----------------------
|
||||
|
||||
This is the current recommended way to deploy Glance with a real web server.
|
||||
In this deployment method we use uwsgi as a web server bound to a random local
|
||||
port. Then we configure apache using mod_proxy to forward all incoming requests
|
||||
on the specified endpoint to that local webserver. This has the advantage of
|
||||
letting apache manage all inbound http connections, but letting uwsgi manage
|
||||
running the python code. It also means when we make changes to Glance code
|
||||
or configuration we don't need to restart all of apache (which may be running
|
||||
other services too) and just need to restart the local uwsgi daemon.
|
||||
This is the current recommended way to deploy Glance with Apache HTTP and it is
|
||||
how we deploy Glance for testing every proposed commit to OpenStack. In this
|
||||
deployment method we use the uWSGI server as a web server bound to a random
|
||||
local port. Then we configure apache using mod_proxy to forward all incoming
|
||||
requests on the specified endpoint to that local webserver. This has the
|
||||
advantage of letting apache manage all inbound http connections, but letting
|
||||
uWSGI manage running the python code. It also means when we make changes to
|
||||
Glance code or configuration we don't need to restart all of apache (which may
|
||||
be running other services too) and just need to restart the local uWSGI daemon.
|
||||
|
||||
The httpd/ directory contains sample files for configuring HTTPD to run Glance
|
||||
under uwsgi in this configuration. To use the sample configs simply copy
|
||||
`httpd/uwsgi-glance-api.conf` to the appropriate location for your Apache
|
||||
under the uWSGI server in this configuration. To use the sample configs simply
|
||||
copy `httpd/uwsgi-glance-api.conf` to the appropriate location for your Apache
|
||||
server. On Debian/Ubuntu systems it is::
|
||||
|
||||
/etc/apache2/sites-available/uwsgi-glance-api.conf
|
||||
|
|
@ -40,12 +41,23 @@ Hat based systems)::
|
|||
|
||||
Start or restart HTTPD to pick up the new configuration.
|
||||
|
||||
Now we need to configure and start the uwsgi service. Copy the
|
||||
.. NOTE::
|
||||
|
||||
Be careful when setting up other proxies/endpoints in the same VirtualHost
|
||||
on Apache HTTPD using. If any are using ``SetEnv proxy-sendcl 1`` then
|
||||
Apache HTTPD will buffer the incoming request to local disk before sending
|
||||
it to glance. This will likely cause problems when running in this
|
||||
configuration and is not necessary. (However, it is necessary if using
|
||||
mod_proxy_uwsgi.) For more details, see the section on
|
||||
:ref:`mod_proxy_uwsgi` below.
|
||||
|
||||
|
||||
Now we need to configure and start the uWSGi service. Copy the
|
||||
`httpd/glance-api-uwsgi.ini` file to `/etc/glance`. Update the file to match
|
||||
your system configuration (for example, you'll want to set the number of
|
||||
processes and threads).
|
||||
|
||||
Install uwsgi and start the glance-api server using uwsgi::
|
||||
Install the uWSGI server and start the glance-api server using uWSGI::
|
||||
|
||||
sudo pip install uwsgi
|
||||
uwsgi --ini /etc/glance/glance-api-uwsgi.ini
|
||||
|
|
@ -56,6 +68,7 @@ Install uwsgi and start the glance-api server using uwsgi::
|
|||
just a randomly selected number. This is not a contract on the port used
|
||||
for the local uwsgi daemon.
|
||||
|
||||
.. _mod_proxy_uwsgi:
|
||||
|
||||
mod_proxy_uwsgi
|
||||
'''''''''''''''
|
||||
|
|
@ -64,18 +77,20 @@ mod_proxy_uwsgi
|
|||
|
||||
Running Glance under HTTPD in this configuration will only work on Python 2
|
||||
if you use ``Transfer-Encoding: chunked``. Also if running with Python 2
|
||||
apache will be buffering the chunked encoding before passing the request
|
||||
on to uwsgi. See bug: https://github.com/unbit/uwsgi/issues/1540
|
||||
Apache will be buffering the chunked encoding before passing the request
|
||||
on to uWSGI. See bug: https://github.com/unbit/uwsgi/issues/1540
|
||||
|
||||
Instead of running uwsgi as a webserver listening on a local port and then
|
||||
Instead of running uWSGI as a webserver listening on a local port and then
|
||||
having Apache HTTP proxy all the incoming requests with mod_proxy. The
|
||||
normally recommended way of deploying uwsgi with Apache HTTPD is to use
|
||||
mod_proxy_uwsgi and set up a local socket file for uwsgi to listen on. Apache
|
||||
will send the requests using the uwsgi protocol over this local socket
|
||||
file. However, there are issues with doing this and using chunked-encoding.
|
||||
normally recommended way of deploying the uWSGI server with Apache HTTPD is to
|
||||
use mod_proxy_uwsgi and set up a local socket file for uWSGI to listen on.
|
||||
Apache will send the requests using the uwsgi protocol over this local socket
|
||||
file. However, there are issues with doing this and using chunked-encoding, so
|
||||
this is not recommended for use with Glance.
|
||||
|
||||
You can work around these issues by configuring your apache proxy to buffer the
|
||||
chunked data and send the full content length to uwsgi. You do this by adding::
|
||||
You can work around these issues by configuring your Apache proxy to buffer the
|
||||
chunked data and send the full content length to the uWSGI server. You do this
|
||||
by adding::
|
||||
|
||||
SetEnv proxy-sendcl 1
|
||||
|
||||
|
|
@ -83,6 +98,16 @@ to the apache config file using mod_proxy_uwsgi. For more details on using
|
|||
mod_proxy_uwsgi see the official docs:
|
||||
http://uwsgi-docs.readthedocs.io/en/latest/Apache.html?highlight=mod_uwsgi_proxy#mod-proxy-uwsgi
|
||||
|
||||
There are some additional considerations when doing this though. Having Apache
|
||||
locally buffer the chunked data to disk before passing it to uWSGI means you'll
|
||||
need to have sufficient disk space in /tmp (or whatever you set TMPDIR to) to
|
||||
store all the disk files. The other aspect to consider is that this buffering
|
||||
can take some time to write the images to disk. To prevent random failures
|
||||
you'll likely have to increase timeout values in the uWSGI configuration file
|
||||
to ensure uWSGI will wait long enough for this to happen. (Depending on the
|
||||
uploaded image file sizes it may be necessary to set the timeouts to multiple
|
||||
minutes.)
|
||||
|
||||
mod_wsgi
|
||||
--------
|
||||
|
||||
|
|
@ -91,3 +116,46 @@ protocol does not support ``Transfer-Encoding: chunked`` and therefore makes it
|
|||
unsuitable for use with Glance. However, you could theoretically deploy Glance
|
||||
using mod_wsgi but it will fail on any requests that use a chunked transfer
|
||||
encoding.
|
||||
|
||||
.. _uwsgi_glossary:
|
||||
|
||||
Glossary
|
||||
--------
|
||||
|
||||
.. glossary::
|
||||
|
||||
uwsgi
|
||||
The native protocol used by the uWSGI server. (The acronym is written in
|
||||
all lowercase on purpose.)
|
||||
|
||||
https://uwsgi-docs.readthedocs.io/en/latest/Protocol.html
|
||||
|
||||
uWSGI
|
||||
A project that aims at developing a full stack for building hosting
|
||||
services. It produces software, the uWSGI server, that is exposed in
|
||||
Python code as a module named ``uwsgi``.
|
||||
|
||||
https://uwsgi-docs.readthedocs.io/en/latest/index.html
|
||||
|
||||
https://pypi.python.org/pypi/uWSGI
|
||||
|
||||
https://github.com/unbit/uwsgi
|
||||
|
||||
mod_wsgi
|
||||
An Apache 2 HTTP server module that supports the Python WSGI
|
||||
specification. (It is not recommended for use with Glance.)
|
||||
|
||||
https://modwsgi.readthedocs.io/en/develop/
|
||||
|
||||
mod_proxy_uwsgi
|
||||
An Apache 2 HTTP Server module that provides a uwsgi gateway for
|
||||
mod_proxy. It communicates to the uWSGI server using the uwsgi protocol.
|
||||
|
||||
http://httpd.apache.org/docs/trunk/mod/mod_proxy_uwsgi.html
|
||||
|
||||
WSGI
|
||||
Web Server Gateway Interface, a Python standard published as `PEP 3333`_.
|
||||
|
||||
https://wsgi.readthedocs.io/en/latest/index.html
|
||||
|
||||
.. _PEP 3333: https://www.python.org/dev/peps/pep-3333
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
[uwsgi]
|
||||
socket-timeout = 10
|
||||
http-auto-chunked = true
|
||||
http-chunked-input = true
|
||||
http-raw-body = true
|
||||
|
|
@ -13,5 +14,5 @@ exit-on-reload = true
|
|||
die-on-term = true
|
||||
master = true
|
||||
processes = 4
|
||||
http = 127.0.0.1:60999
|
||||
http-socket = 127.0.0.1:60999
|
||||
wsgi-file = /usr/local/bin/glance-wsgi-api
|
||||
|
|
|
|||
|
|
@ -1,2 +1,3 @@
|
|||
KeepAlive Off
|
||||
SetEnv proxy-sendchunked 1
|
||||
ProxyPass "/image" "http://127.0.0.1:60999" retry=0
|
||||
|
|
|
|||
Loading…
Reference in New Issue