[Yum-devel] Selecting mirrors on the "freshness" of their repomd, not just their speed

[Willem Riede]

On 12/04/2005 08:57:48 PM, Willem Riede wrote:
> In  
> https://www.redhat.com/archives/fedora-test-list/2005-November/msg00610.html  
> Seth told me that submitting code was the only way to help make the subject  
> happen, so I created a variant of the fastestmirror plugin that also checks  
> the age of repomd.xml on the site.
> 
> A non-up-to-date mirror, however fast, is not going to get the most recent  
> updates to me, so it is of less use than a slightly slower, but up-to-date  
> mirror.

Observing "bestmirror" in action, I realized that just because a certain host  
is fast, and has a copy of the latest content for one mirrored site, doesn't  
mean it is up to date for all sites it mirrors, so the file "timedhosts"  
that's written out needs to have separate ages for all host-repo=mirror  
combinations. Also, someone pointed out, that if you move from "fastestmirror"  
to "bestmirror" reading in the file causes an exception, so I'm now catching  
that. New version of "bestmirror.py" attached.

Comments very much appreciated, and also advise about next steps.

Regards, Willem Riede.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bestmirror.py
Type: text/x-python
Size: 8031 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum-devel/attachments/20051211/5fa10ad8/attachment.py