On Fri, May 20, 2016 at 1:44 PM, Barak Korren <bkorren@redhat.com> wrote:
It seems to me we still need a way to provide the WTG ISOs. Maybe
include an option in engine to upload them to the an ISO domain the
user creates?
Or perhaps find a way to make them available for use without defining
an explicit ISO domain?

Here the issue is different.
when running engine-setup the WGT iso is injected while the iso domain is not yet active.
At engine setup done, you'll have the engine, the inactive iso domain and the iso within it but only if you create the iso domain with engine-setup.

If you run engine-setup, create your own iso domain, and then on upgrade you run again engine-setup, WGT is not uploaded there.

So the existing WGT upload mechanism already is limited to only those installations born with iso domain creation on the same host.

Since we have iso-uploader and we'll have in 4.1 the ISO uploaded from web ui, I really think this mechanism can be dropped since it covers only what it seems to be a corner case.





 

On 20 May 2016 at 14:32, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
> Hi,
> I'd like to get comments on removing ISO domain creation from engine-setup.
>
> ISO domain creation was included in 3.2 for allowing to finish the setup
> with ISO domain ready to serve Windows Guest Tools which is injected into
> the iso domain if the rpm is installed.
> The NFS share was created *(rw) in 3.2.
> In later releases we first restricted access, then asked the user to provide
> access policy during setup and now we moved the default to not create the
> ISO domain.
>
> We have several issues with iso domain creation:
>
> Bug 1302745 - [engine-setup] creation of iso domain path is not rolled back,
> a next attempt leaves an empty domain
>
> Bug 1332813 - Hosted engine should not allow iso domain to be configured in
> the RHEV-M VM
>
> Having ISO domain within hosted engine leads to really bad issues and we're
> streamlining the hosted engine installation with NGN, cockpit and appliance
> so HE will be the most easy way to have oVirt installed making ISO domain
> not useful and even dangerous in engine-setup.
>
> For this reason the bug has ben changed in: Deprecate the ISO domain setup
> on the RHEV-M machine (hide it in 4.0)
> Meaning that using answer file you'll be able to create it anyway in 4.0 but
> the question won't be exposed in interactive setup.
>
> Any concern about this change? Any comment?
> Thanks,
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> _______________________________________________
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel



--
Barak Korren
bkorren@redhat.com
RHEV-CI Team



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com