Can it be a proposal for a new feature in ovirt 3.4?
I think that is rasonable to have one place in ovirt where you can
configure your targets and alias as every host that may need to access
those targets should have the same config.
Regards,
On 31/10/13 19:58, Dan Kenigsberg wrote:
On Thu, Oct 31, 2013 at 02:29:53PM -0200, Juan Pablo Lorier wrote:
> Hi,
>
> I've an ovirt 3.2 install and I use iscsi targets for the disks. The
> thing is that if I use ovirt to access the iscsi targets, it fails
> because it doesn't get the right config deployed to the hosts. Thus I
> had to do this manually and add the "private" header to the
> multipath.conf file so ovirt doesn't overwrite it's contents. I also use
> alias for the luns and they also get wiped out.
> Is there a file I can set in the engine so my config can be centralized
> again and don't have to propagate every change manually to every host?
No such centralized mechanism exists within ovirt. However you could use
the likes of puppet to do that, or write a short before_vdsm_start hook
that pulls multipath.conf from a well-known location.