>> "3-node cluster" is much easier to say than to configure,
>> apparently. :-)
> It really isn't :)
Encouraged by your "it really isn't," I now press forward. :-)
Based on what I'm hearing, this is what I think I have learned...
It is possible to build a 3-node cluster with redundant heartbeat paths,
but I need to use two switches, something like this:
-------------SWITCHED NET #1------(192.168.10.0/24)-----------------
| | |
| | |
|-----------------| |-----------------| |---------------------|
| | | | | | | | |
| |--bond0--| | | |--bond0--| | | |--bond0--| |
| eth0 eth1 | | eth0 eth1 | | eth0 eth1 |
| | | | | |
| SERVER_A | | SERVER_B | | SERVER_C |
| | | | | |
| eth2 | | eth2 | | eth2 |
| | | | | | | | |
|-----------------| |-----------------| |---------------------|
| | |
| | |
-------------SWITCHED NET #2-------(192.168.20.0/24)-----------------
That way, if something happens to switched network #1, Corosync can
still track node status through switched net #2.
Once this configuration is built, I can use Pacemaker with resource
constraints to ensure that resource R1 can only run on SERVER_A or
SERVER_C (usually A) and resource R2 can only run on SERVER_B and
SERVER_C (usually C) and SERVER_C acts as a failover for both resources.
Is this correct?
--
Eric Robinson
Disclaimer - October 23, 2010
This email and any files transmitted with it are confidential and intended
solely for General Linux-HA mailing list. If you are not the named addressee
you should not disseminate, distribute, copy or alter this email. Any views or
opinions presented in this email are solely those of the author and might not
represent those of Physicians' Managed Care or Physician Select Management.
Warning: Although Physicians' Managed Care or Physician Select Management has
taken reasonable precautions to ensure no viruses are present in this email,
the company cannot accept responsibility for any loss or damage arising from
the use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
