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

Bug#698477: Do we really need mirror in AWS?

Le Wed, Jul 20, 2016 at 03:48:23PM +0100, Marcin Kulisz a écrit :
> do you think that there is still need for mirror on AWS once we have CloudFront
> CDN which is working quite nicely from within AWS?

Hi Marcin,

I think that http(s)://cloudfront.debian.net/ is exactly what we need.

And I am not recommending to add it to the list of official geographic mirrors,
because it is not a geographic service.

Providers of geographic mirrors know that they will never bear the full cost of
the whole Debian users downloading packages, given that - obvisouly - users at
a far distance from their mirror will use a different one.  But CloudFront or
Azure (if open to the outside; I do  not remember) are available worldwide.  If
presented together with the geographic mirrors, and in absence of the official
Debian CDN that is to come but is not ready for prime time yet, then there is a
risk that through blogs, forums, mail lists, magazine articles etc, one of
these cloud-based mirrors start to become over-popular and attract a lot of
outside traffic, just because it works well from any geographic location.  In
that situation we should be prepared to be told that the provided never
intended to pay for so much non-cloud traffic, and shuts down the service or
asks for financial contribution.  For that reason, I think that we should
refrain from presenting these mirrors in a similar context as the geographical
official ones.

Of course, if there are good plans to have cloudfront.debian.net served from
"debian.org" instead, there would be no reason to refrain from doing so.  But
if it is too much work for everybody, I think that the current situation is
already very good.  In the end, instead of scaring people away from debian.net
domains, we should remind to our users that for every debian.net domain they
can be absolutely sure that there was one GPG-identified DD who created it
and who is therefore responsible for it. (https://wiki.debian.org/DebianNetDomains)

Probably the most important improvement, as requested anyway for .debian.net
domains, would be to add a link to the source code of the scripts generating
the site and doing the mirroring work.

PS: I would argue that cloudfront.debian.net is even better than regular
mirrors, since it offers HTTPS, but surprisingly this turns to be highly
controversial...  (And people please read the archive of the list and RFC7258
before quickly firing an answer explaining how idiotic I am to not understand
that packages have fixted size and encryption will not ...).

Have a nice day,

Charles Plessy
Tsurumi, Kanagawa, Japan

Reply to: