custom (ebs backed) Fedora 14 AMIs
robyn.bergeron at gmail.com
Mon Dec 6 20:20:15 UTC 2010
On Mon, Dec 6, 2010 at 11:35 AM, John Poelstra <poelstra at redhat.com> wrote:
> Brian LaMere said the following on 12/03/2010 04:28 PM Pacific Time:
>> Greetings all - just wanted to let you know I made a couple tweeks to
>> the very very simple, very non-professional, non-bulletproof
>> "createfedorabootebs.sh" script. You can find slightly longer
>> instructions here:
>> The steps are relatively simple.
>> 1) create an instance from the official AMI (or anywhere else, really)
>> 2) create a new volume, whatever size (at least 2g or so) and mount it
>> at /dev/sdf
>> 3) run the createfedorabootebs.sh script
>> 4) snapshot the volume
>> 5) register an AMI with the snapshot and the pvgrub hd0 aki
>> It's a simple script; even a novice can tell what is going on. The
>> sources are all from Fedora, and nothing funny is happening. This is
>> the low-speed, "I don't know boxgrinder, I don't have a machine I can
>> run xen on anyway, I want to know what is on the image" approach.
>> That said, I *heartily* recommend using jforbes' AMIs instead; he'll
>> have EBS-backed AMIs soon, I'm sure. This is only for those who want to
>> play, or need an ebs image today. Or, if you're really crazy, it's for
>> people who want to look at getting rawhide on ec2!
> What are the plans and timeline for moving this function to the Fedora
> Release Engineering team?
> All "official Fedora content" should be produced and staged by Release
> Engineering, and tested before release by QA too.
We discussed this briefly at the cloud SIG meeting last week. Jared
proposed that we do a FAD around this, probably within a few weeks of
FUDCon. We can likely use FUDCon to hash out some of the details, and
then hack out the implementation, plus docs and test plans, at the
FAD. Jared was planning on mailing the list this week with some
Allow me to play devil's advocate for a moment here: We are, in
essence, doing for Amazon, what some other cloud providers do for us.
Fedora 14 on Rackspace's Cloud Servers and Slicehost products, for
example, required no intervention, or even asking from the Cloud SIG
- they just put it up. Where do we draw the line on what should be
produced and staged by rel-eng? Is it simply because *we* are the ones
doing the heavy lifting with EC2, and not Amazon?
> cloud mailing list
> cloud at lists.fedoraproject.org
More information about the cloud