This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: OT: Re: multiple iscsi targets on bonding interface

To: Christopher Chen <muffaleta@xxxxxxxxx>
Subject: [Xen-users] Re: OT: Re: multiple iscsi targets on bonding interface
From: Ferenc Wagner <wferi@xxxxxxx>
Date: Wed, 06 May 2009 11:24:21 +0200
Cc: Jeff Williams <jeffw@xxxxxxxxxxxxxx>, Xen mailinglist <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 06 May 2009 02:25:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7bc80d500905052222k1bcf1551n220c4a4dac8bd462@xxxxxxxxxxxxxx> (Christopher Chen's message of "Tue, 5 May 2009 22:22:28 -0700")
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <Pine.GSO.4.58.0904051750050.21575@xxxxxxxxxxxxxxxxx> <877i1xmllf.fsf@xxxxxxxxxxxxx> <alpine.DEB.2.00.0904070957560.6289@xxxxxxxxxxxxxxxxxxxx> <87ws9sh73x.fsf@xxxxxxxxxxxxx> <4A00F779.60905@xxxxxxxxxxxxxx> <7bc80d500905052222k1bcf1551n220c4a4dac8bd462@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
Christopher Chen <muffaleta@xxxxxxxxx> writes:

> My idea for next time is to use dm-multipath on the Dom0 that uses
> friendly names associated with scsiSN set on IET on the target --
> namely, I provision a lun on the target, give it a unique scsiSN,
> then with dm-multipath friendly name mapping, I associate that
> scsiSN with, for instance, /dev/mpath/target.guest.root for whatever
> you want, that way I can refer to the friendly names in my DomU
> configs and all I have to do is manage a single list that gets
> propagated via cfengine or whatever.

We do something very similar with our FC based domUs: the multipath
config chooses aliases based on the wwid of the LUN; the corresponding
aliases are extracted by an EMC specific utility from the SAN and
massaged into a multipath config by a home-made one-liner.

For our iSCSI the redundancy is provided by the network level, so
multipath isn't necessary, and udev achieves a convenient persistent
naming by default.

Xen-users mailing list