[Systems] What happened to the mirror? (Was [Systems-logs] Cron <root at sunjammer> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))

[Bernie Innocenti]

I was thinking: we've been running without Mirrorbrain for several weeks
and nothing bad happened. Clearly, we have enough bandwidth to manage
all downloads from sunjammer.

There may be benefits in offloading downloads to locations closer to the
user, but mirror redirection was a pretty complex and fragile system
which should justify itself.

Samuel, could you please download the same large file from
download.sugarlabs.org and from each of the mirrors to see if there is a
substantial benefit?

I suspect that, for large files, the reduced latency won't matter... and
for small files, the extra HTTP redirect from sunjammer to the mirror
may even make things a bit *worse* :-)


On 03/06/2016 08:22 PM, Samuel Cantero wrote:
> Hi Sam,
> 
> I would go for the 2nd approach. Apparently it all fit correctly and we
> can continue moving our services to docker containers.
> 
> Best regards,
> 
> Samuel C.
> 
> 
> 
> On Sun, Mar 6, 2016 at 6:56 AM, Sam Parkinson <sam.parkinson3 at gmail.com
> <mailto:sam.parkinson3 at gmail.com>> wrote:
> 
> 
>     On Sun, Mar 6, 2016 at 5:47 PM, Cron Daemon <root at sugarlabs.org
>     <mailto:root at sugarlabs.org>> wrote:
>>     /etc/cron.weekly/mirrorbrain: bash: asn_import: command not found
> 
>     This cron error message hides that mirrorbrain isn't running at all
>     now.  See this in
> 
>     1) appending ".mirrorlist" to a download.sugarlabs.org
>     <http://download.sugarlabs.org> URL now gives a 404 (should show a
>     list of mirrors and file metadata)
>     2) our MirrorMon [1] (which uses data from mirrorbrain) now shows
>     that there are no mirrors.  This is a lie, arrnet's still mirroring
>     us [2]
> 
>     Upon further investigation, it doesn't seem to be even set up properly:
> 
>     1)  "sudo -u mirrorbrain mb" (mb is mirrorbrain config tool) ->
>     "sudo: mb: command not found"
>     2) from apt.sources.list "#bernie: mirrorbrain no longer supported
>     on trusty :-("
> 
>     So, any preferences for a plan of action?  So far, I can think of:
> 
>     1)  Compile it from source.  MirrorBrain moves slowly, so my old tut
>     about this is still up to date [3].  But this feels so dirty and bad.
>     2)  Use a Debian 8 docker container.  The mirror brain repos [4]
>     include packages for it, so it is just a package manager install in
>     that respect.  We can base it off the official docker apache
>     images[5], which use debian jessie.
> 
>     Thanks,
>     Sam
> 
>     [1]  https://mirrors.sugarlabs.org/
>     [2]  http://mirror.aarnet.edu.au/pub/sugarlabs/
>     [3]
>      https://www.digitalocean.com/community/tutorials/how-to-set-up-a-mirror-director-with-mirrorbrain-on-ubuntu-14-04
>     [4]  http://download.opensuse.org/repositories/Apache:/MirrorBrain/
>     [5]  https://github.com/docker-library/httpd/blob/master/2.4/Dockerfile
>>     _______________________________________________ Systems-logs
>>     mailing list Systems-logs at lists.sugarlabs.org
>>     <mailto:Systems-logs at lists.sugarlabs.org>
>>     http://lists.sugarlabs.org/listinfo/systems-logs 
> 
>     _______________________________________________
>     Systems mailing list
>     Systems at lists.sugarlabs.org <mailto:Systems at lists.sugarlabs.org>
>     http://lists.sugarlabs.org/listinfo/systems
> 
> 
> 
> 
> _______________________________________________
> Systems mailing list
> Systems at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/systems
> 


-- 
 _ // Bernie Innocenti
 \X/  http://codewiz.org