[Engine-devel] [Users] base url of ovirt

[Jon Thomas]

On Wed, 2012-09-19 at 10:53 +0200, Juan Hernandez wrote:
> On 09/19/2012 10:19 AM, Alon Bar-Lev wrote:
> > 
> > 
> > ----- Original Message -----
> >> From: "Juan Hernandez" <jhernand at redhat.com>
> >> To: "Jon Thomas" <jthomas at redhat.com>
> >> Cc: engine-devel at ovirt.org, users at ovirt.org
> >> Sent: Wednesday, September 19, 2012 11:08:26 AM
> >> Subject: Re: [Users] base url of ovirt
> >>
> >> Copying engine-devel, as I think this is something we should discuss
> >> and
> >> maybe do.
> >>
> >> On 09/18/2012 10:50 PM, Jon Thomas wrote:
> >>> Is there some config in the engine to set up the web interface base
> >>> url
> >>> so that instead of https://localhost.localdomain/ it is
> >>> https://localhost.localdomain/ovirt ?
> >>
> >> No, there is no such config.
> >>
> >> I think this should be the default, I mean, we should have this
> >> /ovirt
> >> prefix in all our URLs, to make coexistence with other users of the
> >> web
> >> server easy.
> > 
> > Totally agree.
> > 
> > We discussed that, Itamar agreed to go ahead URL change for ovirt-engine-4.0...
> > 
> > Moving namespace out of root provides many advantages including including simpler apache configuration, easier to use proxies, ability to host multiple applications.
> > 
> > Alon.
> 
> Jon, as you see this will probably go in release 4.0, which is the
> future. Meanwhile if what you need is to use the web server with other
> applications you could try to replace the directives in
> /etc/httpd/conf.d/ovirt-engine.conf with the following:
> 
> ProxyPassMatch ^/(ca.crt|engine.ssh.key.txt)$ ajp://localhost:8009/$1
> ProxyPassMatch ^/(api|webadmin|UserPortal|OvirtEngineWeb)(/.*)?$
> ajp://localhost:8009/$1$2
> 
> That will change your configuration so that only the URLs that are
> really required for the engine will be redirected to it. A notable
> exception will be the welcome page, but you probably can live without
> it, just use the following to get to the UI:
> 
> https://whatever.example.com/webadmin
> https://whatever.example.com/UserPortal
> 
> Take into account that ProxyPassMatch directives are processed in the
> order they appear, so if you have another application with conflicting
> ProxyPassMatch directives the result can be unexpected.

Thx, that worked better than what I was trying. BTW, I still get the
welcome page. I also had to add

WSGIScriptAlias /auth/login /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi

to openstack-dashboard.conf for dashboard to work.



>