Good point Jay, And yes, BoxGrinder supports it in the way you described (with /etc/fstab changes, etc) with one small change - we do the build on EC2 - that avoids uploading the image itself to EC2.
--Marek On 2010-11-04, at 18:58, Jay Greguske wrote: > Jan, > > Personally I would avoid snapshotting a running instance. Doing so brings in > a bunch of run-time caches and temporary data that you really don't want if > you're trying to produce a fresh, pristine image. Of course if you're doing > this for personal fun then you can ignore me. :) > > But for releasing future Fedora AMIs though I'd suggest a procedure as > follows: > > 1. Build the disk image like usual* > 2. Upload the disk image to a running instance > 3. From within the instance dd your disk image to an EBS volume > 4. Snapshot and register that volume as an AMI > > That way you've got an EBS-backed, pristine, never-before-booted image in EC2. > > - Jay > > * There may be some changes to the image to support EBS backing, specifically > in fstab and grub.conf so you're mounting and booting from the right > volume(s). > > > ----- "Jan Pazdziora" <[email protected]> wrote: > >> On Wed, Nov 03, 2010 at 04:16:56PM +0100, Marek Goldmann wrote: >>> >>> Attach EBS volume, say on /dev/sdf and it'll be available in >> instance under /dev/xvdf. >>> >> >> Great, thanks. >> _______________________________________________ cloud mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/cloud
