|
Is it possible to have something like :
virtual v-server {
address = 1.2.3.4 eth0
address = 2.3.4.5 eth0:1
....
}
and yes, i am currently using red hat.. so if someone knows that yes,
lvs can generically do this, but i dont know if red hat could parse it,
i would be interested in hearing that as well...
basically, i want to setup a fully redundant connection over two
physical internet connections...
here's the game plan :
1 - setup dns for www.somedomain.com to point to :
1.2.3.4
2.3.4.5
2 - put two physical nics in the load balancer machine and setup two
virtual addresses for the www.somedomain.com VIP
3 - balance to the real servers as normal
now here's my snags (?) in the idea ...
1 - can you have multiple addresses for a VIP ?
2 - would i need to use direct routing to take advantage of this setup /
make it work
3 - would cookies / persistance work properly ... this last one may be
off topic slightly, but i think it is a yes or no answer...
if i set a cookie say :
www.somedomain.com cookiename=username value=someuser
do cookies reference JUST the fully qualified domain (if available) and
dont care what IP it resolves to, or am I out of luck, or does it
resolve to the IP ... If it does, would getting a result of 1.2.3.4 one
time and getting a result of 2.3.4.5 hurt the validity of that cookie?
thanks ahead of time.
-ed
|
