Re: [ovirt-devel] RFC - dropping ISO domain creation from engine-setup

> > 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

Re: [ovirt-devel] RFC - dropping ISO domain creation from engine-setup

On Fri, May 20, 2016 at 1:44 PM, Barak Korren 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

Re: [ovirt-devel] RFC - dropping ISO domain creation from engine-setup

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? On 20 May 2016 at 14:32, Sandro Bonazzola

[ovirt-devel] RFC - dropping ISO domain creation from engine-setup

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