I've tested the new patch on fedora 18 vdsm host (created iscsi storage domain, 
attached, activated) and it works well.
Even though multipath.conf no longer uses getuid_callout to recognize the 
device's wwid,
it still knows how to deal with the attribute's existence in the conf file when 
running multipath command (only output is to stdout which we don't use anyway, 
stderr empty and rc=0). 
The relevant patch is: http://gerrit.ovirt.org/#/c/10824/


----- Original Message -----
> From: "Ayal Baron" <aba...@redhat.com>
> To: "Gianluca Cecchi" <gianluca.cec...@gmail.com>
> Cc: "users" <users@ovirt.org>, "Dan Kenigsberg" <dan...@redhat.com>, "Yeela 
> Kaplan" <ykap...@redhat.com>
> Sent: Wednesday, January 23, 2013 7:51:28 PM
> Subject: Re: [Users] default mutipath.conf config for fedora 18 invalid
> ----- Original Message -----
> > On Wed, Jan 23, 2013 at 4:41 PM, Yeela Kaplan  wrote:
> > > Yes, you need a different DC and host for iSCSI SDs.
> > 
> > Possibly I can test tomorrow adding another host that should go
> > into
> > the same DC but I can temporarily put it in another newly created
> > iSCSI DC for testing.
> > What is the workflow when I have a host in a DC and then I want to
> > put
> > it into another one, in general and when the two DCs have
> > configured
> > different SD types?
> > 
> As long as the host has visibility to the target storage domains, all
> you need to do is put the host in maintenance and then edit it and
> change the cluster/dc it belongs to.
Users mailing list

Reply via email to