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 simple app that uses all of the python-imgcreate stuff[1] to generate an image that's usable for an AMI in EC2. Very simple: kickstart file in, disk image out. I still need to put in the pieces to auto-bundle and upload the image if desired, but at this point, it's already very useful to me at least. If others find it useful, I can take the next steps of packaging it up for Fedora, etc.
git repo at http://fedorapeople.org/gitweb?p=katzj/public_git/ami-creator.git and announcement blog post at http://velohacker.com/fedora-notes/announcing-ami-creator/.
- Jeremy
[1] Same base pieces as livecd-creator and lives in the same source repo.
On Mon, Dec 13, 2010 at 9:34 PM, Jeremy Katz katzj@fedoraproject.org wrote:
If others find > it useful, I can take the next steps of packaging it up for Fedora, etc.
Please do! The easier it is to build AMIs, the better!
-- Jared Smith Fedora Project Leader
How is this different from appliance-tools? Can this do anything appliance-tools can't with the right ks file?
- Jay
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 simple app that uses all of the python-imgcreate stuff[1] to generate an image that's usable for an AMI in EC2. Very simple: kickstart file in, disk image out. I still need to put in the pieces to auto-bundle and upload the image if desired, but at this point, it's already very useful to me at least. If others find it useful, I can take the next steps of packaging it up for Fedora, etc.
git repo at http://fedorapeople.org/gitweb?p=katzj/public_git/ami-creator.git and announcement blog post at http://velohacker.com/fedora-notes/announcing-ami-creator/.
- Jeremy
[1] Same base pieces as livecd-creator and lives in the same source repo.
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
appliance-tools is using python-imgcreate as well. But appliance-creator 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 b) Doesn't really know about the fact that you can boot custom kernels 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
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.
- Jeremy
On Tue, Dec 14, 2010 at 9:24 AM, Jay Greguske jgregusk@redhat.com wrote:
How is this different from appliance-tools? Can this do anything appliance-tools can't with the right ks file?
- Jay
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 simple app that uses all of the python-imgcreate stuff[1] to generate an image that's usable for an AMI in EC2. Very simple: kickstart file in, disk image out. I still need to put in the pieces to auto-bundle and upload the image if desired, but at this point, it's already very useful to me at least. If others find it useful, I can take the next steps of packaging it up for Fedora, etc.
git repo at http://fedorapeople.org/gitweb?p=katzj/public_git/ami-creator.git and announcement blog post at http://velohacker.com/fedora-notes/announcing-ami-creator/.
- Jeremy
[1] Same base pieces as livecd-creator and lives in the same source repo.
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On 12/14/2010 11:06 AM, Jeremy Katz wrote:
appliance-tools is using python-imgcreate as well. But appliance-creator 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 languishing though.
b) Doesn't really know about the fact that you can boot custom kernels 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.
- Jay
- Jeremy
On Tue, Dec 14, 2010 at 9:24 AM, Jay Greguske <jgregusk@redhat.com mailto:jgregusk@redhat.com> wrote:
How is this different from appliance-tools? Can this do anything appliance-tools can't with the right ks file? - Jay 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 simple app > that uses all of the python-imgcreate stuff[1] to generate an image > that's usable for an AMI in EC2. Very simple: kickstart file in, disk > image out. I still need to put in the pieces to auto-bundle and upload > the image if desired, but at this point, it's already very useful to me > at least. If others find it useful, I can take the next steps of > packaging it up for Fedora, etc. > > git repo at > http://fedorapeople.org/gitweb?p=katzj/public_git/ami-creator.git and > announcement blog post at > http://velohacker.com/fedora-notes/announcing-ami-creator/. > > - Jeremy > > [1] Same base pieces as livecd-creator and lives in the same source repo. > > > > _______________________________________________ > cloud mailing list > cloud@lists.fedoraproject.org <mailto:cloud@lists.fedoraproject.org> > https://admin.fedoraproject.org/mailman/listinfo/cloud _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org <mailto:cloud@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/cloud
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On Tue, Dec 14, 2010 at 8:06 AM, Jeremy Katz katzj@fedoraproject.orgwrote:
appliance-tools is using python-imgcreate as well. But appliance-creator a) Creates a whole disk image vs the weird partition only type of thing that ec2 expects.
pv-grub-hd0 versus pv-grub-hd00?
Instances can boot from partitioned EBS volumes fine :)
Brian
On Tue, Dec 14, 2010 at 1:29 PM, Brian LaMere brian@cukerinteractive.comwrote:
On Tue, Dec 14, 2010 at 8:06 AM, Jeremy Katz katzj@fedoraproject.orgwrote:
appliance-tools is using python-imgcreate as well. But appliance-creator a) Creates a whole disk image vs the weird partition only type of thing that ec2 expects.
pv-grub-hd0 versus pv-grub-hd00?
Correct.
Instances can boot from partitioned EBS volumes fine :)
Right, I should clarify that at this point, I'm building images that are just doing the s3 ephemeral backing. The EBS backing has a few warts to make it tricky to get to in an entirely "not on ec2" environment
- Jeremy
-
Brian LaMere -
Jared K. Smith -
Jay Greguske -
Jeremy Katz