[Maas-devel] Replacing Apache

Christian Robottom Reis kiko at canonical.com
Thu Nov 27 16:00:14 UTC 2014


On Thu, Nov 27, 2014 at 03:56:17PM +0000, Gavin Panella wrote:
> >         * having the region and cluster connect on another port (yuck)
> >         * continue using mod_wsgi for that situation (yuck yuck)
> >         * proxying over to Twisted using mod_proxy, which is included in
> >           the stock Apache install and is what Gavin
> >           has in his lp:~allenap/maas/regiond branch. However, as with
> >           the mod_wsgi solution this would require Twisted to be running
> >           on another port.
> >         * disallow vhosting altogether on the region, which would be
> >           visible change in behaviour
> 
> There's another tricky aspect: the user may have configured Apache to
> use TLS. We'd need to migrate that over to Twisted.
> 
> That's why leaving Apache in, but switching it to a very simple
> static-files-and-proxy-for-the-rest configuration might be an okay
> compromise. We wouldn't need to ask people to restart Apache, we
> wouldn't have to ask users to debug using Apache's logs too (or much
> much less), but we'd still have native handling for static files, and we
> wouldn't rock the TLS boat.

Could that be provided as a legacy option? In other words, new installs
would run Apache-less on port 80/443, but old installs would leave
Apache in-place with a proxy entry.
-- 
Christian Robottom Reis   | [+1] 612 888 4935    | http://launchpad.net/~kiko
Canonical VP Hyperscale   | [+55 16] 9 9112 6430 | http://async.com.br/~kiko




More information about the Maas-devel mailing list