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-API] PATCH: fix support for multiple target's IPs for ISCSI-based S

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] PATCH: fix support for multiple target's IPs for ISCSI-based SR's with multipathing
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Thu, 19 May 2011 02:00:21 +0400
Delivery-date: Wed, 18 May 2011 15:00:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:content-type:date:message-id :mime-version:x-mailer; bh=4h24VMF4zf/MfKzdpfh3dcJ1g7v2kvFvB/gzJ9MYBlY=; b=BaShvsP06spxlUCXpSjs1hzgFTX8pHAF8MNEkPx9MhFom/DukMN70mLuYLE8v5zkxK wsQO2gxYxMxFIGNz9vdF99ob6JamIj4zoj7TlVIepPW6jIlhYxbedo9f7f/IuDrDMFYi 2BpasQONNqHrdUfRyDHlbmrPClZmLgmEQXfFY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer; b=Oq934nB4rJB/U4+FEcpdV77neIiDTRmjGLA2Dl30VOUoU+OUclyOVP7eQ4NAYVZz7D tyR6bELi0PxFLP+l2zERxZfHJ7AprE1YWCSOekRwoXoeeH7YIEpqLHNDVWWQPoOY5fLE HNBu76qYIg8AF1otBfu66DVQobO2pbwu8RLrM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Good day.

Few days ago I have found strange behavior: LVMoISCSI SR with
multipathing and two target's IPs  does not login to second portal
target - only 1st target's IP was processed. This problem was confirmed
in XCP 0.5 and XCP 1.0 (and, I believe is XCP 0.1.1 if someone still
using it).

I dig a little and with help from this maillist found strange code in
ISCSISR.py. Patch to fix this behavior in attachment. (We simply iterate
targetlist instead using a one target portal we succeeded to test

More about configuration where this problem appear:

                                    iscsi (ip1)
           +------- HOST1(TARGET1)-----------------+
BLOCK-DEVICE                                      XCP_host(initiator)
           +------- HOST2(TARGET2)-----------------+
                                    iscsi (ip2)

in this case we have TWO different portals, announcing same IQN with
same serial and so on.

If we put them both to device-config:target, only first one will be
used, this patch add support for both of them.

sample command to see difference:

 xe sr-create type=lvmoiscsi \
 device-config:target=, \ 
 device-config:multihomed=true \
 device-config:targetIQN=iqn.2011-05.test:test.test \

PS patch is against XCP 1.0, but shall works fine with XCP 0.5 too.

PPS This problem appear only if we have a DIFFERENT target hosts. Single
target with few available paths will send all it addresses via single
discovery process, so if target is single host, problem will not appear.

Attachment: xcp-iscsisr-multipath-multiaddress-support.patch
Description: Text Data

xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>