Re: Service names for Debian mirrors in cloud infrastructure
Le Mon, Jan 11, 2016 at 09:05:46AM +0100, Martin Zobel-Helas a écrit :
> On Mon Jan 11, 2016 at 15:52:05 +0900, Charles Plessy wrote:
> > just for the sake of comparison: in the case of the Amazon cloud, the mirror
> > is accessible from inside and outside at <https://cloudfront.debian.net/>.
> > On Azure, would the mirror be accessible from outside ? If not, what would
> yes, it is accessable from the outside but should not be used.
Thanks for the clarification. So altogether it is a very similar situation as for
https://cloudfront.debian.net/ and https://gce_debian_mirror.storage.googleapis.com.
It looks like the statement "should not be used" is making people nervous.
Maybe if you reword it in a softer way like "not meant to be used from
outside", you will avoid some misunderstandings. Anyway, the whole point of
Debian's network of mirrors would be defeated if a significant amount of people
would get a such a better service from the Azure CDN that they would start to
perfer it to our primary or secondary mirrors.
> > As a side note, it would be nice if http://httpredir.debian.org/ would point at
> > the Azure mirror when ran from inside Azure.
> This will generate outgoing traffic, which users will have to pay for,
> at least to get the 302 which then should send you to the internal
> mirror. This is not the prefered option, but we could try to get that
> set up.
Good point, I did not think about it, and it is a good reason for not using it
in this case.
There is one last point that I do not understand: why are you asking for
something in "mirrors.debian.[org|net]", instead of "ftp.azure.debian.org" or
something similar ? The name "debian.mirrors.debian.org" in Bastian's original
email does not resolve, the Google query 'site:debian.org
"debian.mirrors.debian.org"' does not return an answer, so I do not get the