Open Stack

mod_wsgi is compiled to a specific python for Apache. It's a single process
(with multiple forks). It looks like the upstream solution to running
different pythons with mod_wsgi is to either use mod_wsgi-express to launch
a new apache+mod_wsgi per-application, or to modify wsgi script (
https://github.com/openstack/keystone/blob/master/keystone/server/wsgi.py )
to load a virtualenv at the top with execfile()

Neither of these are very good options.


- jlk

On Mon, Nov 30, 2015 at 12:41 PM, Robert Collins <robertc at robertcollins.net>
wrote:

> On 1 December 2015 at 09:36, Jesse Keating <jlk at bluebox.net> wrote:
> > I have an objection to eventlet going away. We have problems with running
> > Apache and mod_wsgi with multiple python virtual environments. In some of
> > our stacks we're running both Horizon and Keystone. Each get their own
> > virtual environment. Apache mod_wsgi doesn't really work that way, so
> we'd
> > have to do some ugly hacks to expose the python environments of both to
> > Apache at the same time.
> >
> > I believe we spoke about this at Summit. Have you had time to look into
> this
> > scenario and have suggestions?
>
> mod_wsgi with separate process definitions should work - Graham
> Dumpleton, the mod_wsgi maintainer, works for Red Hat - I'm fairly
> sure they'd be amenable to us roping him in to help you sort things
> out :)
>
> -Rob
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151130/7554ea2f/attachment.html>