|
> > realserver1:
> > Instance 1 listens only on: 192.168.100.101:8001
> > Instance 2 listens only on: 192.168.100.102:8001
> > Instance 3 listens only on: 192.168.100.103:8001
> > ...
> > Instance n listens only on: 192.168.100.10n:8001
> >
> > realserver2:
> > Instance 1 listens only on: 192.168.100.201:8001
> > Instance 2 listens only on: 192.168.100.202:8001
> > Instance 3 listens only on: 192.168.100.203:8001
> > ...
> > Instance n listens only on: 192.168.100.20n:8001
> >
> > Is this feasible?
> >From what I understand of your proposed setup this is very
> feasible. If I'm
Yes, but you should start to use standard terminology. What you call an
instance we call a VIP or Virtual IP. Realservers are the application
servers. Directors are the machines running IPVS. In your case it is a
little confusing since you have your machines doing both ;-).
Anyway.. there are reports of users configuring thousands (or more) VIPs.
E.g., here is a part of my ldirectord.cf:
# maps.sidestep.com
virtual=64.211.248.13:80
real=64.211.248.143:80 gate 1
real=64.211.248.144:80 gate 1
# images.sidestep.com
virtual=64.211.248.14:80
real=64.211.248.143:80 gate 1
real=64.211.248.144:80 gate 1
This shows up as:
#ipvsadm -L -n
TCP 64.211.248.13:80 rr persistent 10
-> 64.211.248.144:80 Route 1 7 11
-> 64.211.248.143:80 Route 1 1 16
TCP 64.211.248.14:80 rr persistent 10
-> 64.211.248.144:80 Route 1 241 783
-> 64.211.248.143:80 Route 1 184 487
Hope it helps
P
---
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.563 / Virus Database: 355 - Release Date: 1/17/2004
|
