You can try heartbeart...
:)
DS
------Original Message------ From: avi@myphonebook.co.in Sender: centos-bounces@centos.org To: centos@centos.org ReplyTo: CentOS mailing list Subject: [CentOS] Apache/Cluster issue -- Single public IP address Sent: Jan 8, 2010 11:28 PM
I want to set up a cluster that is used for web hosting (RHCS cluster). Recently, I experimented with a 2 node cluster and was able to run it successfully. However, I have started facing some issues with Apache, which I had configured as a service using the Cluster configuration tool. To do this Apache needs a floating IP address. This address is in addition to the network interface IP address. For example if my NIC IP is 192.168.1.1, then I need 192.168.1.2 as a floating IP address, and this has to be bound to apache. At least this is what I understood after several hours of experimentation. I also figured that if I configured 192.168.1.1 as a cluster resource and bound it to apache, the cluster manager failed to start apache and the NIC was put "off". ( In effect 192.168.1.1 was removed from the NIC ).
However, the Apache service ran fine when bound to the ADDITIONAL IP i.e. 192.168.1.2 ( the floating IP ).
The above example was just a lab setup to test the cluster.
My problem is that I only have a single public IP address, to serve my web server and my question is this:
Is this the end of the road, for installing apache as a service with ONE public IP address??
I am willing to give further info, if required.
My problem is that I only have a single public IP address, to serve my web server and my question is this:
Is this the end of the road, for installing apache as a service with ONE public IP address??
a cluster like that typically needs THREE IP addresses. one for cluster node 1, one for cluster node 2 and one for the shared service, this last IP will be assigned to the currently active host and will be the one clients use to connect. the other two addresses are used for administration and management.
in addtion, a robust cluster has one or more dedicated networks (these can be crossover cables, and can/should use private addressing) for redundant heartbeats