<div class="gmail_quote">On Tue, Dec 14, 2010 at 1:29 PM, Brian LaMere <span dir="ltr"><<a href="mailto:brian@cukerinteractive.com">brian@cukerinteractive.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Tue, Dec 14, 2010 at 8:06 AM, Jeremy Katz <span dir="ltr"><<a href="mailto:katzj@fedoraproject.org" target="_blank">katzj@fedoraproject.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
appliance-tools is using python-imgcreate as well. But appliance-creator<div>a) Creates a whole disk image vs the weird partition only type of thing that ec2 expects.</div></blockquote><div><br></div></div><div>pv-grub-hd0 versus pv-grub-hd00? </div>
</div></blockquote><div><br></div><div>Correct.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div>Instances can boot from partitioned EBS volumes fine :)</div>
</div></blockquote><div><br></div><div>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</div>
<div><br></div><div>- Jeremy</div></div>