[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] PATCH: fix support for multiple target's IPs for ISCSI-based SR's with multipathing


  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • 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
  • 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=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

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
early).

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=10.0.0.1,10.0.0.2 \ 
 device-config:multihomed=true \
 device-config:targetIQN=iqn.2011-05.test:test.test \
 device-config:SCSIid=1494554000000000031000000000000000000000000000000
name-label=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
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.