|
> - Can a Linux Director deal with multiple IP addresses? For example,
> suppose that I want to run many instances of our app on the realservers,
> for different customers. Basically I want the Director to answer to:
>
> 192.168.200.001:8001
> 192.168.200.002:8001
> 192.168.200.003:8001
> ...
> 192.168.200.00n:8001
>
> and for each of these addresses forward the requests to the same 2
> realservers that each will have n instances of the app server bound to a
> specific IP address:
>
> 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
understanding you correctly it shouldn't be very hard either. Once you get
your systems setup that is..;) It would simply be a matter of configuring
your IPVSADM rules to direct the traffic accordingly. By this I mean you
would have 1 rule per external IP that you wished to have your clients
connecting to. This rule would point each external IP to the two internal
IPs and app instances that you wanted to correspond to that particular
client connection.
For example:
Rule 1:
192.168.200.001:8001 would go to 192.168.100.101:8001 or
192.168.100.201:8001
Rule 2:
192.168.200.002:8001 would go to 192.168.100.102:8001 or
192.168.100.202:8001
I am fairly new to alot of this stuff as well so if it doesn't make any
sense then I'm sure you can count on somebody else here to explain it
better. And if I'm completely wrong feel free to tell me to shut up guys!..
;)
-Billy Olson
|
