[Engine-devel] 3.3 scratch or upgraded installation must use Apache proxy (https://bugzilla.redhat.com/905754)

Alon Bar-Lev alonbl at redhat.com
Thu May 23 15:07:31 UTC 2013



----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Barak Azulay" <bazulay at redhat.com>, "engine-devel" <engine-devel at ovirt.org>, "Alex Lourie" <alourie at redhat.com>
> Sent: Thursday, May 23, 2013 5:26:19 PM
> Subject: Re: [Engine-devel] 3.3 scratch or upgraded installation must use Apache	proxy
> (https://bugzilla.redhat.com/905754)
> 
> Il 23/05/2013 16:19, Alon Bar-Lev ha scritto:
> >
> > ----- Original Message -----
> >> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> >> To: "Alon Bar-Lev" <alonbl at redhat.com>
> >> Cc: "Barak Azulay" <bazulay at redhat.com>, "engine-devel"
> >> <engine-devel at ovirt.org>, "Alex Lourie" <alourie at redhat.com>
> >> Sent: Thursday, May 23, 2013 5:01:58 PM
> >> Subject: Re: [Engine-devel] 3.3 scratch or upgraded installation must use
> >> Apache	proxy
> >> (https://bugzilla.redhat.com/905754)
> > <snip>
> >
> >> I think I was missing something.
> >> I don't know if other distro do the same, but on Fedora 18
> >> freeipa-server has a package conflict with mod_ssl.
> >> So it is not possible having both IPA and the oVirt engine on the same
> >> host.
> >> This should answer also for post IPA installation for Fedora.
> >>
> >> I think the best thing to do here is just warn that we are requiring
> >> mod_ssl when enabling SSL support so any service that has conflicts like
> >> freeipa-server will have issues
> >> and let the administrator decide what to do.
> > We cannot warn... we attempt to configure it... and we do depend on it...
> > So either it is installed before we run setup or we install it during(?!?!)
> > setup.
> >
> > Alon
> 
> So let me try to revert the logic.
> Can't we drop the dependency on mod_ssl and warn that if you want SSL
> support you've to install mod_ssl allowing the user to abort, install
> the module and run engine-setup again?

Right... this is just for 3.3...

This matches the logic of multiple execution of setup to add new components :)

Not sure this will be acceptable by those who like 'simple-on-click' installation.

Regards.
Alon



More information about the Engine-devel mailing list