I think you're off by a bit. I've been following the LinuxVSD project
for some time now. It's purpose is the precise reverse of LVS.
Instead of putting one website (or whatever) on many servers. It puts
many websites on one server. However, the twist is that with FreeVSD,
each client has their own Apache (they can even compile their own or run
their own modules), Sendmail, BIND, etc. Each client operates in a
chrooted environment, and each has their own IP--they have an 'admin'
class username with pseudo-root priviledges in their own chrooted
environment. So it's like having a colocated server, but the resources
are shared amongst several websites. Beautiful concept, since most
websites can't even begin to tax the server they run on. Most websites
could be sharing a modest server's resources with ten or twenty or a
hundred similar sites.
The target of this project is obviously colo and hosting
providers...this is the logical in-between step if shared hosting is too
limiting, and colo is too expensive. The only negative I see is that it
requires an IP for each "virtual server". But then again, if you're a
website designed who provides managed services...you could have one of
these virtual servers on a shared server and provide a number of Apache
virtual hosts, as well.
Interesting stuff! And a reasonable mistake to make, regarding what it
does, since you guys are all coming at it from the perspective of
needing a bunch of boxes just to run /one/ website! ;-)
Ed Crotty wrote:
> hahah!
>
> i went through some of the mailing lists trying to piece things
> together... thats the end result i came up with (be it wrong or right).
>
> if it is the case, this is a pretty nifty tool.
>
> if not, it should be started! :)
>
> -ed
>
> ----- Original Message -----
> From: Joseph Mack <mack.joseph@epa.gov>
> Date: Monday, March 5, 2001 4:36 pm
> Subject: Re: Linux PR
>
>
>> Ed Crotty wrote:
>>
>>> i was looking over freevsd stuff... it actually is somewhat
>>> interesting... it seems that the approach is not so much for load
>>> balancing but from a "virtual" server on the front end line..
>>>
>>> for instance :
>>>
>>> virtual server abc
>>> running on public
>>> net - linux
>>> |
>>> | skel layer (?) (i looked at it quick :D)
>>> |
>>> /\
>>> / \
>>> real1 real2
>>>
>>> so if you hit the virtual from lets say a ssh standpoint, you
>>
>> would have
>>
>>> access to work on both reals from the virtual fs at the same time
>>
>> and it
>>
>>> would replicate beyond to the real servers any changes / updates...
>>
>>> am i understanding it correctly or am i giving it too much credit?
>>
>> There's a lot of good ideas and smart people out there and I wouldn't
>> assume that we have the corner on either of those markets
>>
>> I looked through all the press releases looking for info
>> till my eyes glazed over. I don't know how you managed to get this
>> much out of their web site. I'm assuming there's good stuff in there
>> although I don't know what it is yet.
>>
>> Joe
>>
>> --
>> Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
>> contractor to the National Environmental Supercomputer Center,
>> mailto:mack.joseph@epa.gov ph# 919-541-0007, RTP, NC, USA
--
Joe Cooper <joe@swelltech.com>
Affordable Web Caching Proxy Appliances
http://www.swelltech.com