Well, the best things would be that an interworx member explain exactly how their Cluster solution works.
From my point of view :
They use LVS.
LVS is a virtual server. That means all the clients see only 1 IP (by services).
In fact there is a director (called cluster manager by interworx) that does the loadbalancing, then route the requests to one realserver : The client send a request to the LVS IP on a specific port (say 80), the director receive this request, look at this routage table, do loadbalancing and route the request to a realserver on the same port.
Normaly the director is not itself a realserver. So if you have only 2 boxes, one director and one realserver, it isn’t possible to have loadbalancing.
But It is possible to have the director acting as a realserver (called localnode). In this last case 2 boxes are suffisant to do Load Balancing (each boxes act as a director and a realserver, like ultramomkey).
I think the Interworx cluster solution works like this (to be confirmed by an interworx member)
But I’m also a little confused.
My problem is about what services are LoadBalanced. All ? (ssh, ftp, imap, pop, http, https, …)
Indeed, in the Interworx cluster doc, they said that you may choose to give to your client the IP you want.
Ok, but in this case, if you don’t give the IP of the LVS, the request of a client will be route directly to the realserver without go trhough the cluster manager, so the request wont be Load Balanced.
The other point is about SSL certificates on dedicated IP. If the dedicated IP is not the LVS IP, so does it means that all requests to this website also won’t be load balanced ?
I’m sure an interworx member may easily answer to these points. And sorry if I completly wrong and confused you (and me)