Re: [mirrorbrain] RFC: geographic distance ordering for finer mirror selection

Hi,

On Fri, Dec 11, 2009 at 09:04:12PM +0100, Peter Poeml wrote:
> I entered a feature request into the issue tracker today:
> http://mirrorbrain.org/issues/issue34
> 
> It needs some discussion. See below. What do you think, how this
> should best be integrated with the other criteria for mirror
> selection?

Today, I realized that there *are* already latitude and longitude fields
in the mirror records, from earlier experiments. They are just not shown
in the "editing mirrors" template. 

Thus, no database migrations would be required to play with the above
idea. That's cool, and I spent a few minutes on the "mb new" and "mb
update" commands to add support to automatically fill out the fields.

If you haven't used mb update yet, it's a bit neglected so far - it was
created mainly to update mirror metadata that existed before "mb new"
would fill in network prefix and stuff. It makes sense though to run the
mb update command periodically, as it will warn about DNSrr sites, and
it can update the AS number, prefix and geograhical coordinates now.
Those rarely change, but it makes sense to keep them updated. The
command could be further improved, but it's not unuseful in the current
state. 

A useful command to be run through cron once in a while would be:
mb update -c -a -p --all-mirrors

There should probably a way to prevent overwriting manually edited data,
therefore I'm hesitant to put it into the documentation in this state.


Anyway, trunk now has support for this:

poeml_at_doozer ~ % mb update -c --all-mirrors
updating geographical coordinates for ftp.udc.es (0.000 0.000 -> 40.4 -3.683)
updating geographical coordinates for ftp.rhnet.is (0.000 0.000 -> 64.15 -21.95)
updating geographical coordinates for openoffice.mirrors.tds.net (0.000 0.000 -> 43.074 -89.527)
updating geographical coordinates for ftp.idilis.ro (0.000 0.000 -> 44.433 26.1)
updating geographical coordinates for ftp.sunet.se (0.000 0.000 -> 59.85 17.633)
updating geographical coordinates for ooorg.mirror.testserver.li (0.000 0.000 -> 47.0 8.0)
updating geographical coordinates for ftp.openoffice.skynet.be (0.000 0.000 -> 50.833 4.333)
updating geographical coordinates for ftp.tpnet.pl (0.000 0.000 -> 50.05 22.0)
updating geographical coordinates for mirrors.ctn1.net (0.000 0.000 -> 46.317 0.917)
updating geographical coordinates for hex1a4.net (0.000 0.000 -> 43.15 -79.5)
updating geographical coordinates for openoffice.dcc.fc.up.pt (0.000 0.000 -> 41.15 -8.617)
updating geographical coordinates for ftp.uasw.edu (0.000 0.000 -> 52.267 10.533)
updating geographical coordinates for openoffice.mirrors.ilisys.com.au (0.000 0.000 -> -33.883 151.1)
updating geographical coordinates for openoffice.patan.com.ar (0.000 0.000 -> -31.633 -60.7)
updating geographical coordinates for files.akl.lt (0.000 0.000 -> 54.683 25.317)
updating geographical coordinates for ftp.piotrkosoft.net (0.000 0.000 -> 51.417 21.15)
updating geographical coordinates for mirror.csclub.uwaterloo.ca (0.000 0.000 -> 43.467 -80.533)
updating geographical coordinates for ftp.ntua.gr (0.000 0.000 -> 37.983 23.733)
updating geographical coordinates for ftp.proxad.net (0.000 0.000 -> 48.883 2.467)
updating geographical coordinates for openoffice.mirror.rafal.ca (0.000 0.000 -> 43.25 -79.833)
updating geographical coordinates for linorg.usp.br (0.000 0.000 -> -23.533 -46.617)
updating geographical coordinates for ftp.tu-chemnitz.de (0.000 0.000 -> 50.833 12.917)
updating geographical coordinates for ftp.sh.cvut.cz (0.000 0.000 -> 50.083 14.467)
updating geographical coordinates for ftp.bayanat.com.sa (0.000 0.000 -> 25.0 45.0)
updating geographical coordinates for mirrors.evolva.ro (0.000 0.000 -> 44.433 26.1)
updating geographical coordinates for ftp.kr.freebsd.org (0.000 0.000 -> 37.566 127.0)
updating geographical coordinates for mirror.lupaworld.com (0.000 0.000 -> 39.929 116.388)
updating geographical coordinates for ftp.iasi.roedu.net (0.000 0.000 -> 44.433 26.1)
[... and so on.]

So, there's not much missing to make use a bit of geographic awareness
in some mirror selection scenarios.

Peter


_______________________________________________
mirrorbrain mailing list
Archive: http://mirrorbrain.org/archive/mirrorbrain/

Note: To remove yourself from this mailing list, send a mail with the content
 	unsubscribe
to the address mirrorbrain-request_at_mirrorbrain.org