[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Instant Mirror Status...?



On Mon, 2008-09-22 at 22:51 -0500, Les Mikesell wrote:
>   All they should have to do is request the same URLs.
>
> Why can't that happen automatically?  That is, within whatever blocks 
> geoip might consider 'near', arbitrarily select the first-choice mirror 
> based on the source IP range in a repeatable way.  That way everyone 
> behind the same proxy requests the same URL and the caching works 
> automatically.

 MirrorManager gives the clients the URLs to try in a specific order
(and soon with even more data). Yum/urlgrabber will try the URLs in the
order it gets them.
 So what you are saying essentially is: "Why can't MirrorManager decide
what the best URL is for a netblock/geoip and always list it first, just
to make the proxy problem zero-conf"
 And I can guess that the answer to that is basically "Because it
doesn't work", feel free to send Matt patches though if you think
otherwise.

 It is on my TODO to look at trying to get a usable version of
yum-avahi┬╣ that people can use, this should solve your proxy problem in
a generic way ... although it would do so by routing around it.
 I also have a lot of things on my TODO list, so again patches
welcome :)

┬╣ http://users.ecs.soton.ac.uk/rds204/yum-avahi/

-- 
James Antill <james antill redhat com>
Red Hat

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]