> The recent troubles we've had at kernel.org pretty much highlight the
> issues with having an offsite system with no easy physical access.
> This begs the question if we could establish another primary
> kernel.org site; this would not only reduce the load on any one site
> but deal with any one failure in a much more graceful way.
>
> Anyone have any ideas of some organization who would be willing to
> host a second kernel.org server? Such an organization should expect
> around 25 Mbit/s sustained traffic, and up to 40-100 Mbit/s peak
> traffic (this one can be adjusted to fit the available resources.)
>
> If so, please contact me...
Hello Peter,
I don't know if this could be any real help, but anyway I have a slightly
different suggestion, that may be interesting. Years ago we did a DNS-project
that allows to spread a domain to several _different_ ip locations based on the
dns-_requesting_ ip. You may know such a technique from akamai (MS daughter).
In fact we implemented and test-runned it years ago, but did not find any
customer interested (in fact only real big customers _can_ be interested at
all, and we didn't have the "connections"). Anyway the know-how is still here
and can be used to help kernel.org, if interested. The basic idea is, that this
splits costs in running kernel.org to several locations. These locations can
(e.g.) be providers who may have some strategic interests. You may as well come
up with a GNU project of spreading kernel.org mirrors - meaning every provider
be it small or big can have its own mirror, and _only_ his customers (depending
on their IP or his AS) are using it. So if you have a major breakdown at the
primary server, people will get no _new_ pages, but kernel.org itself looks up
throughout all IP-ranges that have a mirror "attached".
What do you think?
Regards,
Stephan von Krawczynski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/