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

Re: Debian Images on Amazon Web Services (resent)




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
On 9/11/2012 5:14 AM, Stefano Zacchiroli wrote:
> On Thu, Nov 08, 2012 at 11:18:41PM +0800, James Bromberger wrote:
>> However, we could make a EBS volume from the snapshot, and then 'dd'
>> the image of the volume, compress up the image, and push that onto a
>> public bucket where the world could download it.
>
> That would be a nice alternative to piggyback it onto the mirror
> network. Would there be no bandwidth/traffic limits on how many people,
> outside AWS, download them?

No restrictions if it is in a bucket and marked as public; traffic charges should be absorbed so long as its not going to be excessive (I doubt it would be).

> Any reason not to use something like http.debian.net or the GeoIP
> redirector? Maybe that wouldn't work within AWS? No matter the matter of
> distributing the AMIs themselves, that sounds like a useful
> simplification in the preparation/upload process, no?

Yeah, that sounds like it could be useful.
>> We (Debian) can generate a digest of the snapshot (via the EBS volume we make from the snapshot), sign and publish this.
>
> ACK. Although we'll still need to investigate with the archive people
> how to actually do the signing (e.g. would anyone need to get extra
> access to the signing keys? would they do that? etc.). Any takers?


I'll pause the signing until after we stablise *what* we're signing. ;)

This potentially could be a plugin into ec2debian-build-ami that, post creating the ami, does the previously mentioned tasks of generating the signature...

  James

- --
/Mobile:/ +61 422 166 708, /Email:/ james_AT_rcpt.to
PLUG President 2012: http://www.plug.org.au <http//www.plug.org.au>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
 
iQIcBAEBAgAGBQJQnDSsAAoJEK7IKHSdhcU8yOcP/jSarCNbN/Pssxwdn0qYPGD2
bO0uW/PdbdSSZHWJ6MEDLrb3hmkolC57rw4WjU+QhzzNtVCQfcjm3VN8cMt22Trl
QvLyQ8Xit74WFwW2RcLyZCW1opSHkWlMF2BW97nnxzic7hI8dEqYb+2G/Xk+ADPk
UUOtXcwhakH5Bc6FMhqJCgZ60sGu3huCG6d34aUyZ14+L17Sl65A6YdCt0zfffYl
yM/9svGZUG/VpN3WAD8BjowOi7aumUWcy9fwaVHfZ0zanibaaTcCOlPp/yAs4ORP
JAcmC7inu2WUhBeXC/jlhR/7E9Zm86F1KAYxXTzCEf8gyd1FeDVLsK/Wj/CpF7Hi
+/jQUNHONLdo9K6erhevs9mwhawu7LrtCf5swu7z+smYwouqajuM821JvH4xxyDs
zADS/CcqaoDp8T0G2vTUsbz9oZYDPEKYKP9uWMKAiY9VraK5qwz83TTkRXL+W8b8
mhR5L9Cl3cQ7eb8J/aN4ZZ8JHDV9btmIKLzwoLkHsKz2M7gpJ5KIPyB5SLGPGZ9g
hv+XBY5ChAy3KdzWGkcDxMKiOYNcQVUBWPpqV2JhZO1GAwPgTYK0LxXLsKd7LTGR
HglBYtGwTFPqu7KYPCKnn/lHsMZ+zlr+EAHMjRvPQb4t+Sq7VflS804Ix9TtH/e5
qCEKCWTrp+6CcmsbFCKk
=xPT0
-----END PGP SIGNATURE-----


Reply to: