|
Once I kick+ban'd Red Hat's crappy HA Server 1.0 off my machines and
installed VA Linux's freely available ISOs, I got LVS to work the way
it's supposed to. (Sad affair when another comapny can do a competing
company's software right)
Anyways, I have set up virtual hosting here. We have like 12 domains
coming in and based on the call to the VIP declaring what domain it wants,
it will hit the apache server(s) and go to the right directory. (This is
the default behavior for Apache's Virtual Hosts). Is this what you are
talking about?
AKA, you have your backend webservers set up (this is done on each of
them) to handle xyz.com, xzy.com, xxx.com, and say zzz.com. Any calls
coming into the VIP will be passed on to the apache servers in the backend
cluster. The destination domain name is carried over in that packet as
well. (It's not the job of the LVS front nodes to handle multi-domain
calls, it's the backend servers that do that)
When the packet reaches one of the backend servers, it will route the
packet to the right virtual host. This must be identical on each of the
backend hosts.
AFAIK, there is nothing available at this time that will allow the FRONT
END nodes (those handling the VIP) to route the traffic to different
backend servers SAVE ONLY the fact that you can declare multiple VIPs in
the lvs.cf file and declare THERE which backend servers will handle each
VIP. But short of those 2 methods there is nothing else *I* know of that
will do it.
On Fri, 8 Sep 2000, Michael McConnell wrote:
> The real question is, has anyone made any headway with getting LVS-NAT to
> work with *REAL* Virtual Web Servers?
>
> Michael McConnell
> Senior Network Engineer
> VocalScape Communications Inc.
> http://www.vocalscape.com/
> --
--
David D.W. Downey
Systems Administrator
RHCE, CUA/CLA
Internet Security Specialist
QIXO.com
|
