Fwd: Debian Images on Amazon Web Services (resent)
> Regarding this, and answering to the relevant point in Anders' mail, what's the status of packaging it?
> Has anyone started doing that or is interested in it?
Provided I understand this correctly, you want to sign the EBS
snapshots. This is going to be a problem:
You can't access these snapshots directly, which means you'd have to
create volumes from them and mount them. I am not sure where to go
If we were talking instance store images, we could sign the archive.
But my bootstrapper does not support instance store root volumes
Automating the publishing process would be a piece of cake I think.
On 11 November 2012 16:32, Stefano Zacchiroli <email@example.com> wrote:
> On Fri, Nov 09, 2012 at 06:39:40AM +0800, James Bromberger wrote:
> > > 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).
> OK, good to know. We then "just" need to document the AMI location. To
> that end, and more general about documentation, feel free to start using
> the wiki. We can use either subpages of the wiki.d.o/Teams/Cloud page
> I've just created (for team-specific information) or (for user facing
> information) the other pages that already existed, like wiki.d.o/Clouds
> and its subpages.
> I guess both you and Charles are already familiar with those pages,
> given you've been working on them recently.
> > > 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.
> Good. (That's something who could use a bug report to track, see my
> other mail on the matter.)
> > > 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...
> Regarding this, and answering to the relevant point in Anders' mail,
> what's the status of packaging it? Has anyone started doing that or is
> interested in it? Anders: the license is not a problem, Apache's license
> is compatible with the DFSG.
> Stefano Zacchiroli . . . . . . . firstname.lastname@example.org . . . . o . . . o . o
> Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
> Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o .
> « the first rule of tautology club is the first rule of tautology club »