I've done about zero research into this, but perhaps you could run two separate daemon instances, one listening on each IP.<br><br><div class="gmail_quote">On Tue, May 11, 2010 at 8:55 AM, Bart Coninckx <span dir="ltr"><<a href="mailto:bart.coninckx@telenet.be">bart.coninckx@telenet.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On Tuesday 11 May 2010 12:58:45 Michael Iverson wrote:<br>
> I'd be quite interested as well, obviously. So this is what we would<br>
> end up with:<br>
><br>
> Host A is primary for drbd volume 1, and secondary for drbd volume 2.<br>
> It acts as an iSCSI target for whatever's on volume 1.<br>
><br>
> Host B is primary for volume 2, and secondary for volume 1. It acts as<br>
> a target for whatever's on volume 2.<br>
><br>
> If either node fails, the opposite node takes over the secondary<br>
> volume, and exports its fallen comrade's iSCSI targets.<br>
><br>
> This idea could possibly be extended with Ben's approach of one DRBD<br>
> volume per iSCSI target. (Except that it would be in a<br>
> primary/secondary role, instead of primary/primary.) This would make<br>
> the process of rebalancing the load between the two nodes fairly<br>
> trivial.<br>
><br>
> Mike<br>
><br>
> On Tue, May 11, 2010 at 5:09 AM, Bart Coninckx <<a href="mailto:bart.coninckx@telenet.be">bart.coninckx@telenet.be</a>><br>
wrote:<br>
> >> It is. I'm planning to showcase this in one of our upcoming webinars.<br>
> >><br>
> >> Cheers,<br>
> >> Florian<br>
> ><br>
> > Excellent, any timeframe on this? As it happens I'm dealing with a setup<br>
> > now that could definitely benefit from this.<br>
> ><br>
> > B.<br>
> > _______________________________________________<br>
> > drbd-user mailing list<br>
> > <a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
> > <a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
><br>
<br>
</div></div>Agreed, but what might be less trivial is to convince a running IETD target to<br>
have the config for the "other" targets merged to the existing targets and at<br>
the same time bind to the new secondary IP address, preferably while not<br>
breaking running operation. This all should be taken care of by Heartbeat.<br>
<br>
I'm going to try to dive into the challenge and report back to the list,<br>
unless the webinar would happen fairly soon.<br>
<div><div></div><div class="h5"><br>
<br>
B.<br>
_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dr. Michael Iverson<br>Director of Information Technology<br>Hatteras Printing<br>