<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Andreas Ntaflos wrote:
<blockquote cite="mid:201010280236.05504.daff@pseudoterminal.org"
type="cite">
<pre wrap="">Hi,
first time poster, short time Pacemaker user. I don't think this is a
very difficult question to answer but I seem to be feeding Google the
wrong search terms. I am using Pacemaker 1.0.8 and Corosync 1.2.0 on
Ubuntu 10.04.1 Server.
Short version: How do I configure multiple independent two-node clusters
where the nodes are all on the same subnet? Only the two nodes that form
the cluster should see that cluster's resources and not any other.
Is this possible? Where should I look for more and detailed information?
</pre>
</blockquote>
You need to specify different multicast sockets for this to work. Under
the /etc/corosync/corosync.conf you have the interface statements. Even
if all servers are in the same subnet, you can "split them apart" by
defining unique multicast sockets.<br>
An example should be useful. Let's say that you have only one interface
statement in the corosync file.<br>
interface {<br>
ringnumber: 0<br>
bindnetaddr: 192.168.1.0 <br>
mcastaddr: 239.192.168.1 <br>
mcastport: 5405 <br>
}<br>
The multicast socket in this case is 239.192.168.1:5405. All nodes that
should be in the same cluster should use the same multicast socket. In
your case, the first two nodes should use the same multicast socket.
How about the other two nodes? Use another unique multicast socket.<br>
interface {<br>
ringnumber: 0<br>
bindnetaddr: 192.168.1.0 <br>
mcastaddr: 239.192.168.112 <br>
mcastport: 5405 <br>
}<br>
Now the multicast socket is 239.192.168.112:5405. It's unique, the
network address is the same, but you add this config (edit according to
your environment, this is just an example) to your other two nodes. So
you have cluster1 formed out of node1 and node2 linked to
239.192.168.1:5405 and cluster2 formed out of node3 and node4 linked to
239.192.168.112:5405.<br>
<br>
This way, the clusters don't _see_ each other, so you can reuse the
resource ID's and see only two nodes per cluster.<br>
<br>
Regards,<br>
<br>
Dan<br>
<blockquote cite="mid:201010280236.05504.daff@pseudoterminal.org"
type="cite">
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
</pre>
</body>
</html>