Appreciate the info, but indeed what we need is HA.
I need to perhaps request if a cluster developer would be willing to add
a new configuration item to the IP xtag within the cluster.conf
configuration that would allow one to specify IP an IP label to apply
the IP resource to.
This /could/ be done via a cluster resource script - but then we'd lose
the ability to have the cluster software monitor the link and relocate
the service should the link be lost.
Kit Gerrits wrote:
Hello,
What you want sounds more like Load Balancing than HA Clustering.
I would suggest building a lvs load balancing cluster with 10.1.1.x as
front-end IP and 10.1.2 as backend IP.
Make the LVS the default gateway for your 'cluster servers'
(realservers), then configure 1-.1.1.50 on your LVS cluster as Virtual
IP with the 10.1.2.x realservers as backend using NAT routing.
Documentation isa vailable at:
http://www.austintek.com/LVS/LVS-HOWTO/
or, more specifically:
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-NAT.html
LVS should be included in Red Hat Advanced Platform.
Yes, running a LoadBalancing cluster means 2 more servers and 2 more
subscriptions, but it will allow for highly-available Load Balancing.
(implicitly allowing you to take realservers offline for maintenance)
Regards,
Kit Gerrits
--
Linux-cluster mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-cluster
