Re: Bug#698477: Re: Bug#698477: Do we really need mirror in AWS?
On 21/07/16 10:07 AM, Marcin Kulisz wrote:
> On 2016-07-21 20:27:53, James Bromberger wrote:
>> On 21/07/2016 3:58 PM, Lucas Nussbaum wrote:
>>
>>> 09:25 <@Mithrandir> lucas: it's not suitable for deb.d.o in its current configuration.
>>> 09:25 <@Mithrandir> as I said whenever somebody last asked about it.
>>> 09:25 < lucas> is this documented somewhere? if it's not suitable for deb.debian.org, it might not be
>>> suitable for the official EC2 images Debian provides
>>> 09:25 < lucas> but it's used there
>>> 09:27 <@Mithrandir> > curl -s -i http://cloudfront.debian.net/debian-security/ | head -n1
>>> 09:27 <@Mithrandir> HTTP/1.1 404 Not Found
>>> 09:28 <@Mithrandir> > curl -s -i http://cloudfront.debian.net/debian-debug/ | head -n1
>>> 09:28 <@Mithrandir> HTTP/1.1 404 Not Found
>>> 09:28 <@Mithrandir> > curl -s -i http://cloudfront.debian.net/debian-ports/ | head -n1
>>> 09:28 <@Mithrandir> HTTP/1.1 404 Not Found
Do we know what is the origin for cloudfront.debian.net ?
why can't we simply point it to the real mirror so it has all of the
above folders ?
> I was actually thinking about writing some cloudformation templates to create
> this cloudfront to keep it in git so we have some kind of tracebility and I
> think it would make DSA happier if they wanted to take it on board.
> Configuration would be just json file and deployment can be scripted to make it
> painless as possible.
> But I'll leave it to DSA if they want to do it or not if they do I'm ok with
> doing this work.
I can help with CloudFormation or Terraform template (which is I think
more flexible) for these distributions.
Reply to: