[ClusterLabs] How to configure my ocf_heartbeat_iscsi resource(s) such that I have both paths to the LUN?

[Dejan Muhamedagic]

Hi,

On Thu, Feb 23, 2017 at 02:29:46PM -0500, Scott Greenlese wrote:
> 
> Refreshing this post in case anyone might have missed it...   still trying
> to figure out some way to have multiple iscsi paths managed
> by a single ocf_heartbeat_iscsi resource.  Any ideas?
> 
> Thanks!
> 
> Scott Greenlese ... KVM on System Z - Solutions Test, IBM Poughkeepsie,
> N.Y.
>   INTERNET:  swgreenl at us.ibm.com
> 
> 
> 
> 
> From:	Scott Greenlese/Poughkeepsie/IBM at IBMUS
> To:	users at clusterlabs.org
> Cc:	Si Bo Niu <niusibo at cn.ibm.com>, Michael
>             Tebolt/Poughkeepsie/IBM at IBMUS
> Date:	02/15/2017 12:18 PM
> Subject:	[ClusterLabs] How to configure my ocf_heartbeat_iscsi resource
>             (s) such that I have both paths to the LUN?
> 
> 
> 
> Hi folks,
> 
> I'm running some test scenarios with an ocf_heartbeat_iscsi pacemaker
> resource,
> using the following XIV multipath'ed configuration:
> 
> I created a single XIV iscsi host definition containing all the pacemaker
> host (cluster node) 'Initiator's:
> 
> XIV 7812475>>host_list_ports host=pacemaker_iscsi
> Host Type Port Name
> pacemaker_iscsi iSCSI iqn.2005-03.org.open-iscsi:6539c3daf095
> pacemaker_iscsi iSCSI iqn.2005-03.org.open-iscsi:11d639c0976c
> pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:74ca24d6476
> pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:ea17bebd09a
> pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:b852a67852c
> 
> Here is the XIV Target IP:port / IQN info:
> 
> 10.20.92.108:3260
> Target: iqn.2005-10.com.xivstorage:012475
> 
> 10.20.92.109:3260
> Target: iqn.2005-10.com.xivstorage:012475
> 
> I mapped a single 17Gb Lun to the XIV host: 20017380030BB110F
> 
> 
> From ocf_heartbeat_iscsi man page, it didn't seem obvious to me how I might
> specify multiple
> IP Portals (i.e. both the .108 and .109 IPs) to a single
> ocf_heartbeat_iscsi resource. So,
> I went ahead and configured my resource using just the .108 IP path, as
> follows:
> 
> Using the above XIV definitions, I created a single iscsi pacemaker
> resource using only one of the two IP
> paths to the XIV LUN:
> 
> [root at zs95kj VD]# pcs resource show iscsi_r4
> 
> Resource: iscsi_r4 (class=ocf provider=heartbeat type=iscsi)
> Attributes: portal=10.20.92.108:3260
> target=iqn.2005-10.com.xivstorage:012475
> Operations: start interval=0s timeout=120 (iscsi_r4-start-interval-0s)
> stop interval=0s timeout=120 (iscsi_r4-stop-interval-0s)
> monitor interval=120 timeout=30 (iscsi_r4-monitor-interval-120)
> 
> I'm looking for suggestions as to how I should configure my iscsi resource
> (s) such that I have both paths (.108 and .109)
> to the LUN available to my application? Do I need to create a second iscsi
> resource for the .109 path, and colocate
> them so that they move about the cluster together?

Yes, you may do that. Then you'll get two devices. For that you
should then use dm-multipath.

> As an aside, I have run into situations where the second IP (.109) comes
> online to where my iscsi_r4 resource is running (how or why,
> I'm not sure), which introduces problems because iscsi_r4 only manages
> the .108 connection.

What does "comes online to where..." exactly mean?

Thanks,

Dejan

> 
> Thanks in advance...
> 
> Scott Greenlese ... KVM on System Z - Solutions Test, IBM Poughkeepsie,
> N.Y.
> INTERNET: swgreenl at us.ibm.com
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 
> 



> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org