Ldirectord and heartbeat with multiple IPs
So I have a question about heartbeat and ldirectord. This may be a simple question, but I don't know the exact answer so if I could get some help with this it would be greatly appreciated.
I am working on a project that has the following servers:
2 Linux directors each running ldirectord and heartbeat
3 web servers which are being load balanced via the Linux directors
Multiple other servers that the client has running for their business
There are 8 public or “virtual” IPs all used to get to various web pages, servers and services.
We will say the IPs range from 188.8.131.52 to 184.108.40.206 with netmask of 255.255.255.0
Internally they are running a standard 192.168.X.X network.
We are running a High Capacity High Availability and Load Balancing model for the setup using ldirectord and heartbeat. The picture below is a general setup
Anyways now down to the real question.
I am wondering if there is anything special we need to do with the /etc/ha.d/haresources file to accommodate for all the extra IPs. Or does the /etc/ha.d/ldirectord.cf file take care of the “virtual” IPs?
This is what the /etc/ha.d/haresources and the /etc/ha.d/ha.cf files currently look like.
bcast eth0 # Linux
mcast eth0 220.127.116.11 694 1 0
respawn hacluster /usr/lib/heartbeat/ipfail
apiauth ipfail gid=haclient uid=hacluster
What I am unsure of is if we need to add more IPs to the /etc/ha.d/haresources file since the client wants to be able to get to all of their servers via a public IP being routed through the linux directors.... PLEASE HELP!
The ha* files are for heartbeat so that each load balancer can see if the others are still up. It's ldirector that handles the virtual IP addresses.
Okay then another quick question. Does it matter if the IP you enter into for the /etv/ha.d/haresources is a public IP or should it be kept a private IP? I know that sounds like a stupid question.
That depends on your network setup. Ideally you have some kind of local network where you can decide yourself which IP addresses to use. In this tutorial: http://www.howtoforge.com/high_avail...apache_cluster I use private IP addresses. If you have your servers in some data center, it might be problematic telling your ISP that you need a virtual public IP address.
This is fine if you only have on webpage. It does not address the problem of you having multiple webpages and IPs running through a router.
I think you can have multiple web sites if you use name-based vhosts: http://httpd.apache.org/docs/2.0/vhosts/name-based.html
|All times are GMT +2. The time now is 15:27.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.