[Openstack-operators] [Swift] deploying behind apache?

Joseph Bajin josephbajin at gmail.com
Sat Sep 19 15:13:59 UTC 2015

We don't deploy swift behind apache, but instead we are using NGINX in this
particular case.  The only reason we went with NGINX was it allowed us to
control turning up and down particular services which apache couldn't do.
One day we will move back to apache when we move swift into containers.

The reason we put it behind nginx/apache was for a few different reasons:

1. We needed SSL for all our connections.  The python implementation of SSL
doesn't handle a lot of connectivity and starts to have issues over time.
This has been discussed about other projects as well, so it's not just
related to swift.
2. We had to control our SSL ciphers. Using nginx/apache allows us to have
that control very easily.
3. Python Threading - Most projects are using evenlets and that is all done
in a single thread.  The thought was Web Servers do web serving type of
traffic very well, so hand over web serving to a web serving and allow
scaling as well as getting rid of the single eventlet thread issue.

On Sat, Sep 19, 2015 at 1:42 AM, Adam Lawson <alawson at aqorn.com> wrote:

> Hey everyone,
> What are the advantages to deploying swift storage and/or proxy services
> behind apache versus not? Are there performance improvements that come into
> play at scale? Has this been addressed before and are there any conclusions
> drawn around these considerations I can read up on?
> /adam
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150919/755baf22/attachment.html>

More information about the OpenStack-operators mailing list