On 12/14/2010 11:06 AM, Jeremy Katz wrote:
appliance-tools is using python-imgcreate as well. But
a) Creates a whole disk image vs the weird partition only type of thing
that ec2 expects. ec2-converter tries to then convert the image after
the fact, but is in serious need of love
You can boot disk images in EC2, you just have to bundle/register with
the right options to ensure the device is exposed as a disk rather than
a partition. No argument that appliance-tools development has been
b) Doesn't really know about the fact that you can boot custom
via pvgrub now. This opens up whole new worlds (yay not running the
Fedora 8 kernel!) but you actually have to know about it to set up the
initrd and grub correctly
It doesn't have to, and pvgrub does not add any extra requirements on
the image that AKIs don't already. You need to build in the xennet and
xenblk drivers into the initrd regardless.
appliance-creator is perfect for the case that you want to have a disk
image that you can load into virt-manager, vmware or the like. There
are just different needs.
The beauty is that the same kickstart config can get used for
appliance-creator, livecd-tools, ami-creator and also to install to your
actual physical hardware.
I'm all for common tool sets. Koji has already been integrated with
appliance-tools, so you can build EC2-worthy images in Koji with the
right kickstart file. Fedora Rel-Eng is looking at integrating this
functionality to their existing process too.
To get to my point, if this work was in appliance-tools, then both Koji
and BoxGrinder could have benefited from it.
On Tue, Dec 14, 2010 at 9:24 AM, Jay Greguske <jgregusk(a)redhat.com
How is this different from appliance-tools? Can this do anything
appliance-tools can't with the right ks file?
On 12/13/2010 09:34 PM, Jeremy Katz wrote:
> Hey everyone --
> After fighting with too many different tools where none of them acted
> like I wanted last week, I've gone ahead and put together a
> that uses all of the python-imgcreate stuff to generate an image
> that's usable for an AMI in EC2. Very simple: kickstart file in,
> image out. I still need to put in the pieces to auto-bundle and
> the image if desired, but at this point, it's already very useful
> at least. If others find it useful, I can take the next steps of
> packaging it up for Fedora, etc.
> git repo at
> announcement blog post at
> - Jeremy
>  Same base pieces as livecd-creator and lives in the same
> cloud mailing list
> cloud(a)lists.fedoraproject.org <mailto:firstname.lastname@example.org>
cloud mailing list
cloud mailing list