<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 20, 2016 at 1:44 PM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It seems to me we still need a way to provide the WTG ISOs. Maybe<br>
include an option in engine to upload them to the an ISO domain the<br>
user creates?<br>
Or perhaps find a way to make them available for use without defining<br>
an explicit ISO domain?<br></blockquote><div><br></div><div>Here the issue is different.</div><div>when running engine-setup the WGT iso is injected while the iso domain is not yet active.</div><div>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.</div><div><br></div><div>If you run engine-setup, create your own iso domain, and then on upgrade you run again engine-setup, WGT is not uploaded there.</div><div><br></div><div>So the existing WGT upload mechanism already is limited to only those installations born with iso domain creation on the same host.</div><div><br></div><div>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.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5"><br>
On 20 May 2016 at 14:32, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>> wrote:<br>
> Hi,<br>
> I'd like to get comments on removing ISO domain creation from engine-setup.<br>
><br>
> ISO domain creation was included in 3.2 for allowing to finish the setup<br>
> with ISO domain ready to serve Windows Guest Tools which is injected into<br>
> the iso domain if the rpm is installed.<br>
> The NFS share was created *(rw) in 3.2.<br>
> In later releases we first restricted access, then asked the user to provide<br>
> access policy during setup and now we moved the default to not create the<br>
> ISO domain.<br>
><br>
> We have several issues with iso domain creation:<br>
><br>
> Bug 1302745 - [engine-setup] creation of iso domain path is not rolled back,<br>
> a next attempt leaves an empty domain<br>
><br>
> Bug 1332813 - Hosted engine should not allow iso domain to be configured in<br>
> the RHEV-M VM<br>
><br>
> Having ISO domain within hosted engine leads to really bad issues and we're<br>
> streamlining the hosted engine installation with NGN, cockpit and appliance<br>
> so HE will be the most easy way to have oVirt installed making ISO domain<br>
> not useful and even dangerous in engine-setup.<br>
><br>
> For this reason the bug has ben changed in: Deprecate the ISO domain setup<br>
> on the RHEV-M machine (hide it in 4.0)<br>
> Meaning that using answer file you'll be able to create it anyway in 4.0 but<br>
> the question won't be exposed in interactive setup.<br>
><br>
> Any concern about this change? Any comment?<br>
> Thanks,<br>
><br>
><br>
> --<br>
> Sandro Bonazzola<br>
> Better technology. Faster innovation. Powered by community collaboration.<br>
> See how it works at <a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a><br>
><br>
</div></div>> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHEV-CI Team<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>