|
Hi all,
I'm currently reading the LVS HOWTO and came to the point where I'm
absolutely unsure if it will do what I need. I will try to explain what I'm
searching for and perhaps you could tell me if it's woth reading on ;)
I'm searching a solution to cluster Gameservers. The solution should make
Gameservers (which are unique through the used TCP/UDP Port) transparent to
end users. Let's say I got 6 Realservers and I notice that Realserver #1 is
under heavy load while Realserver #3 is nearly idle. Then I will stop the
instance on #1 and launch it on #3. I would afterwards "tell" this to the
"Director" and it will send the packtes to #3. Automated load balancing is
out of the scope since the decission is clear. What I mean by this is that
for instance if the client connects to Port 1234 there exists only one
Gameserver on the Realservers which listens on 1234. This information could
be provided to the director by a script or something.
Step by Step I would like to add:
- automated load balancing (check CPU load=>kill the gameserver
process=>start on another realserver)
- failover mechanisms
Is LVS the right solution for me? Is it worth reading on?
Thanks in advance
Thorsten
--
... black holes are where god divided by zero.
|
