LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Multiple Clusters for Multiple Sites

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Multiple Clusters for Multiple Sites
From: "Victor" <victord@xxxxxxxx>
Date: Thu, 10 Jan 2002 19:14:57 -0500
Also, could someone explain how Piranha fits into this? On RH site, it says
Piranha only supports NAT (is this outdated text)? Since it's based on LVS,
why can't it support DR or TUN?

> I would like to find out if LVS supports the config of multiple clusters
for
> multiple sites:
>
>         ROUTER
>           |
>        FIREWALL
>           |
>    +------+------+
>    |             |
> +--+--+       +--+--+
> | LD1 |       | LD2 |
> +--+--+       +--+--+
>    |             |
>    +-----+  +----+
>          |  |
>         SWITCH
>      /   |   |   \
>   WWW1 WWW2 WWW3 WWW4
>
> Would it be possible to setup multiple clusters
>
> Cluster1
>    www1
>    www2
>    www3
> /Cluster1
>
> Cluster2
>    www2
>    www4
> /Cluster2
>
> And then set up multiple sites
>
> Domain1.com
>    cluster1
> /Domain1.com
>
> Domain2.com
>    cluster2
> /Domain2.com
>
> Also, would it be possible to dynamically modify the ClusterX modes by
> adding/removing servers? Scheduling changes?
>
> I was not completely clear on section 23.16 of the howto. Is having two
load
> balancer directors where "if one fails, the other transparently takes
over"
> not supported at this time? If it is, how is this handled? The whole point
> of having load balancing is to eliminate single point of failure (as well
as
> performance) so introduing SPOF at the director would be unacceptable for
> me.
>
> In your "deployment" page, you list a couple sites that use LVS. Any word
on
> what they are using to overcome these issues? How do they maintain
redundant
> Controllers?
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>



<Prev in Thread] Current Thread [Next in Thread>