|
> -----Original Message-----
> Here are a few questions to put me in the right direction if you don't
> mind
> (it's more logistical than technical stuff really...)
>
> Can you confirm that i should follow these steps in order:
> 1- Build the machines with completely bare OS installs
> 2- Configure the director
> 3- Configure each realserver
Doesn't really matter in which order you do it, but ye, you need
realservers, and you need a director. Only thing to 'configure' on the
realservers (if you use them in LVS nat) is to use the director as gateway,
and have an 'internal' network.
> One thing i'm not sure of is: if the 2.6 kernel is already patched to
> support ipvs, do i simply need to install ipvsadm (i checked and
If you use debian, it is simply 'apt-get install ipvsadm iptables' on the
director and you have all you need
> Also, since i'm gonna go for a LVS-NAT forwarding method i understand i
> won't have to deal with the arp issue. Is that right?
Unless you want to failover the director.
> In the above setup, can i use my debian gateway server as the client to
> test
> from ? I'm not too familiar with routing stuff or iptables rules and am
> a
> bit worried that my lack of knowledge in this domain will screw my
> tests if
> i try to test from an outside client.
As long as the realservers are on a seperate internal network it should not
be a problem.
If you do a request from .1 to .205 which gets handled by .206 than .206
will try to reply to .1, but .1 never requested anything from .206, so the
connection will fail.
What you need to do is give server1 another IP/network beside .205, lets say
192.168.1.1 (eth0:I or some alias if you do not have enough network cards),
and give the realservers only an 192.168.1.x IP and have them use
192.168.1.1 as gateway.
Anyway, by far the best way to learn IPVS is to just do it and test it. If
you use VM's or a some testservers you cannot go wrong. And read up on
iptables / ipvsadm, and just test :)
-kees
|
