Import existing, don't try to create one. Tal - maybe instead of error we should detect and ask user for ISO domain if they meant to import. On Nov 5, 2015 9:03 AM, Robert Story <rstory@tislabs.com> wrote:

On Wed, 4 Nov 2015 19:16:58 -0500 Itamar wrote: IH> On 11/02/2015 10:14 AM, Robert Story wrote: IH> > On Fri, 30 Oct 2015 18:58:33 -0400 Liam wrote: IH> > LC> Tried setting up NFS ISO domain which works on one host/local IH> > LC> datacenter. I do not want to have to have multiple copies of iso IH> > LC> files on all hosts. If I try to import pre-existing ISO domain, I IH> > LC> either get an error that storage path exists or the dialog just IH> > LC> does nothing. IH> > IH> > I had the same goal, but for multiple independent ovirt installs. My IH> > work-around is to deal with it outside ovirt. IH> > IH> > - create generic nfs export for my iso mirrors IH> > - create iso export points for each install IH> > - add iso mount to each install IH> > - manually (or using puppet, etc) add mirror mount on each host node IH> > - run a script that creates a symlink in each ovirt iso mirror for IH> > all the isos in the mirror export IH> >    - 3.5 handles iso images in subdirectories, but 3.4 does not [1], IH> > so the script creates symlinks for every iso image in the top level IH> > of the iso export for 3.4, while only needing a symlnk to the distro IH> > directory fro 3.5. IH> > IH> > It's a hack, but it works. IH> IH> This should work without any hacks. An ISO domain can be shared between IH> multiple DCs or Engines. IH> Tal?

When I try and create an iso domain with the same NFS path as another domain I get 'the selected storage path is not empty[...] Either remove the existing Storage Domain from this path, or change the storage path.'

Robert

-- Senior Software Engineer @ Parsons