LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: OT: Supersparrow

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: OT: Supersparrow
From: Horms <horms@xxxxxxxxxxxx>
Date: Thu, 14 Oct 2004 15:25:57 +0900
On Mon, Aug 09, 2004 at 04:56:12PM +1000, Josh Marshall wrote:
> Hi all,
> 
> I know this probably isn't lvs-related, but I know that Horms reads
> this list and I'm needing some advice. I've been looking into
> implementing something like supersparrow to get high availability /
> fastest connection for our web servers. We have some servers in
> Australia and some in the USA and some in Holland. I'm interested in
> the dns method of getting the closest server for the client connecting
> so that we don't have to do http redirects and have multiple webnames
> configured. That's a bit further along.
> 
> I'm wondering if I need to have a bgp daemon with a public AS number
> to be able to get the information needed to determine the best path
> for the client.  I have done some tests and read loads of
> documentation but am not sure how to get the information without
> having a public AS number. The supersparrow documentation describes
> what appears to be an internal solution so doesn't show whether this
> is possible or not.

The way that supersparrow was designed is that you have access
to BGP information for each site that you have servers located at.
You do not need a public AS number to get this information, however
you do need _read only_ access to your provider's BGP information.
Unfortunately this can be difficult to get your hands on.

> I guess I'm also wondering whether I should be looking at supersparrow
> - I know that the software was written a few years ago, but the idea
> behind it and the amount of processing it needs to do I can imagine it
> doesn't need to be actively maintained.

Yes it does have that apperarence. But I am actually in the process
of sprucing it up a lot. Most of what I have so far is
in the cvs repository[1][2]. About the only thing of note still
missing is the patch for bind 9[3]. But please feel free to play with what
is there.

[1] http://sourceforge.net/cvs/?group_id=10726
[2] http://www.vergenet.net/linux/vanessa/cvs.shtml
[3] http://www.supersparrow.org/download/wip/bind9/

> If anyone has any advice as to what I can do, to get the best path
> information with (or without) bgp without having a public AS number
> I'd really appreciate it.

I have been toying with a few ideas to cope with not being able to get
access to BGP at colocation sites. One of the ideas that I had was to
provide a static list of networks and what site they should map to. I
implimented this as ssrsd which is in the CVS tree now. ssrsd
understands that for instance 10.0.0.0/25 is part of 10.0.0.0/18 and
will choose the site listed for 10.0.0.0/25 over the one for
10.0.0.0/18. Of course you still have to create the list somehow and at
this stage it isn't at all dynamic. But it can work quite well.

-- 
Horms
<Prev in Thread] Current Thread [Next in Thread>
  • Re: OT: Supersparrow, Horms <=