[CentOS-devel] setting up an emergency update route

On 02/03/2015 07:08 PM, Manuel Wolfshant wrote:
> On 3 februarie 2015 20:59:39 EET, Stephen John Smoogen <smooge at gmail.com> wrote:
>> On 3 February 2015 at 07:56, Nux! <nux at li.nux.ro> wrote:
>>
>>> How about a variation on A:
>>> - ask some of the main mirrors for push access, put those in order
>> and
>>> make a new [centos-security] repo with a mirrorlist pointing just at
>> them.
>>>
>>> Lucian
>>>
>>
>> Speaking from working on the Red Hat/Fedora side of mirroring for a
>> while... mirrors do not like to be pushed to. They also do not like
>> having
>> to run software that would initiate a pull if notified of new content.
>> For
>> most of them, this is a spare time, feel good item. They have no time
>> and
>> usually have to spend a good portion of the year explaining to their
>> bosses
>> why they even have a mirror to the internet since that costs someone a
>> lot
>> of money somewhere. So anything which adds to that workload is a minus.
> 
> With my mirror admin hat on, even if we do not accept pushes/notifications we'll gladly poll any designated upstream mirror with any frequency considered suitable by you . And we'll also host any additional repo (if needed) with any (decent) size. The Debian mirror is already larger. Much larger :)
> 

repeated polling is counter productive. for the 6 times the high-prio
push was needed in the last year, its a waste to destroy mirror cache's
every 10 min through the entire year.

having dedicated nodes to just push rsync targets is also bad - since
those machines then dont deliver any user facing service ( or bandwdith
) for most of the time.


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc