Hi, On Wed, Oct 05, 2011 at 05:43:45PM +0000, Warnke, Eric E wrote: > I made some customizations to the iscsi RA that I tried to post back > upstream but never made it into the git. Since we have not moved forward > with the project I just have not gotten back around to repackaging and > resending the alterations. > > I will presume that multipath is configured and working and this is not > some weird Dell multipath via device driver setup. > > Since the iscsi RA queries by IP for sendtarget it was just then a matter > of changing open_iscsi_add and open_iscsi_remove to remove the IP address > "-p $1".
Perhaps that can be added then as an option to the upstream RA. Thanks, Dejan > OpenISCSI then does the right thing and binds to all targets > regardless of IP. Then you have 1 iscsi device managed by HA and it will > "just work" assuming that querying one target will return both IP > addresses. To query multiple IP's should be a rather simple rewrite of > the open_iscsi_discovery function. The limitation in discovery means the > primary needs to be up when the system comes up or it will be unable to > discover the secondary path(s). > > If you want I can forward along the specific RA that we use. > > Cheers, > Eric > > [root@cluster-1 heartbeat]# crm status > ============ > Last updated: Wed Oct 5 13:34:16 2011 > Stack: cman > Current DC: cluster-3 - partition with quorum > Version: 1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe > 3 Nodes configured, unknown expected votes > 7 Resources configured. > ============ > > Online: [ cluster-3 cluster-1 cluster-2 ] > > RadonVG (ocf::heartbeat:LVM): Started cluster-3 > RadonFS (ocf::heartbeat:Filesystem): Started cluster-3 > XenonFS (ocf::heartbeat:Filesystem): Started cluster-2 > XenonVG (ocf::heartbeat:LVM): Started cluster-2 > Clone Set: iscsi > Started: [ cluster-3 cluster-1 cluster-2 ] > Clone Set: ClusterFS > Started: [ cluster-3 cluster-1 cluster-2 ] > Monitor (ocf::pacemaker:ClusterMon): Started cluster-3 > > > [root@cluster-1 heartbeat]# multipath -ll > mpathc (3600144f076f08c0000004dda8d820004) dm-4 OI,COMSTAR > size=5.0G features='0' hwhandler='0' wp=rw > `-+- policy='round-robin 0' prio=1 status=active > |- 2:0:0:2 sdf 8:80 active ready running > `- 3:0:0:2 sdd 8:48 active ready running > mpathb (3600144f076f08c0000004dc5faec0003) dm-3 OI,COMSTAR > size=1.0T features='0' hwhandler='0' wp=rw > `-+- policy='round-robin 0' prio=1 status=active > |- 2:0:0:1 sde 8:64 active ready running > `- 3:0:0:1 sdc 8:32 active ready running > mpatha (3600144f076f08c0000004dc5fae70002) dm-2 OI,COMSTAR > size=1.0T features='0' hwhandler='0' wp=rw > `-+- policy='round-robin 0' prio=1 status=active > |- 3:0:0:0 sda 8:0 active ready running > `- 2:0:0:0 sdb 8:16 active ready running > > > > > > On 10/5/11 10:44 AM, "Vadym Chepkov" <[email protected]> wrote: > > > > >On Oct 5, 2011, at 9:38 AM, Florian Haas wrote: > > > >> On 2011-10-05 14:59, Vadym Chepkov wrote: > >>> Hi, > >>> > >>> It looks like iscsi multipath IO is not supported by iscsi RA. > >>> What would be the proper way to configure iSCSI MPIO in a pacemaker > >>>cluster? > >> > >> OK, so first of all are you absolutely positive you _must_ use MPIO? > >> Most users find it much easier to just run their iSCSI initiator over a > >> bonded network interface if all you want to protect against is network > >> failure. > >> > > > >This could start a holy war, but this is configuration which is > >recommended by Dell and, furthermore , not all storages have bonding > >capabilities, but, usually, they do have multiple ethernet interfaces. > > > > > >> Secondly, you can always define two iscsi resources that Pacemaker > >> manages via ocf:heartbeat:iscsi. Then as soon as those come online, > >> provided the SCSI target sets consistent serial numbers and SCSI IDs, > >> multipathd should happily put them together as one mpath device. In your > >> configuration, does it not do that? > >> > > > >This would create a very complicated configuration. You have to colocate > >both resources and you can't use inf: in colocation because it would > >break redundancy (all or nothing) > >I guess lsb:iscsi RA is the only option. > > > > > >Regards, > >Vadym > > > >_______________________________________________ > >Linux-HA mailing list > >[email protected] > >http://lists.linux-ha.org/mailman/listinfo/linux-ha > >See also: http://linux-ha.org/ReportingProblems > > > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
