[Pacemaker] Routing-Ressources on a 2-Node-Cluster

[Andrew Beekhof]

On 23/04/2013, at 6:05 PM, T. <nospam at godawa.de> wrote:

> Hi Devin,
> 
> thank you very much for your answer.
> 
>> If you insist on trying to do this with just the Linux-HA cluster,
>> I don't have any suggestions as to how you should proceed.
> I know that the "construct" we are building is quite complicated.
> 
> The problem is, that the active network (10.20.10.x) is too small to
> cover both locations (in real we only have a /26 subnet available) and
> we can not change/move this (public) addresses to an other range.
> 
> In addition a NAT-translation over a router is not possible, the servers
> have to be accessible directly via their public ip-address, that has to
> be the cluster-ip.
> 
> So we have to deal with two different networks in the two locations
> (10.20.11.x/10.20.12.x) and create an "overlay" for the current
> ip-addresses :-(

Did you try corosync's udpu feature?
It's basically the same as ucast from ha.cf but I don't recall if that feature made it into 6.4

> 
> 
> The current status is, that I added a modified the
> heartbeat-Route2-script that also allows the "metric" as parameter and
> with this it works as expected.
> 
> But I am really fighting with the new corosync/pacemaker, for me the old
> heartbeat (1) was much easier and gave me all functionality I needed. So
> I make progress, but quite/too slow ...
> -- 
> To Answer please replace "invalid" with "de" !
> Zum Antworten bitte "invalid" durch "de" ersetzen !
> 
> 
> Chau y hasta luego,
> 
> Thorolf
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org