The most recent version of the Fedora AKI available to EC2 users is based on the Fedora 8 kernel -- because that's the last one that Amazon uploaded. Which is clearly a problem.

The most recent version of the Fedora AKI available to EC2 users is based on the Fedora 8 kernel -- because that's the last one that Amazon uploaded. Which is clearly a problem.

+

+

Lots of background discussion describing the problems can be found in the [http://meetbot.fedoraproject.org/fedora-cloud/2010-02-04/fedora-cloud.2010-02-04-20.02.log.html log] and [http://meetbot.fedoraproject.org/fedora-cloud/2010-02-04/fedora-cloud.2010-02-04-20.02.html minutes] of the Cloud SIG meeting of 2/4/2010.

(FIXME)

(FIXME)

Line 31:

Line 44:

= Scope =

= Scope =

−

FIXME

+

* Kernels uploaded to EC2 for Fedora 12 and 13

+

* A process to upload kernels for each upcoming release

+

* A process to upload images for default spins for each release

= Test Plan =

= Test Plan =

Line 47:

Line 62:

= Contingency Plan =

= Contingency Plan =

−

FIXME

+

Nothing in this plan stands in the way of the Fedora release itself -- everything is additional tools and processes. Therefore, contingency plan is to slip until we're ready to upload full images of F12 and F13, whenever that happens to be.

= Documentation =

= Documentation =

−

FIXME

+

Documentation and a list of currently supported AMIs are available [https://fedoraproject.org/wiki/Cloud_SIG/EC2_Images on the Cloud SIG EC2 page].

Summary

There's a lot of outdated, ugly Fedora on EC2. Old kernels uploaded by Amazon and forgotten, random images based on that kernel created by folks who don't understand how Fedora works. It's confusing to users and bad for the Fedora brand, and if we want to see Fedora in use on the cloud, we need to step in and take responsibility for Fedora.

The goal of this feature: a process that creates Fedora EC2 images as a part of the regular Fedora release process, starting with Fedora 13.

Completed Action Items

Detailed Description

Here's how EC2 works, in a nutshell: they have kernel images (AKIs) and machine images (AMIs). Anybody can create and upload an AMI, but only approved vendors can upload an AKI.

The most recent version of the Fedora AKI available to EC2 users is based on the Fedora 8 kernel -- because that's the last one that Amazon uploaded. Which is clearly a problem.

Lots of background discussion describing the problems can be found in the log and minutes of the Cloud SIG meeting of 2/4/2010.

(FIXME)

Benefits to Fedora

Having solid, updated, maintained Fedora images on EC2 is essential for our success in the cloud world.

Recent Fedora in EC2 will allow the Fedora Project to begin to run workloads in EC2. Build hosts, for example, could be stood up easily and cheaply in EC2 at times of great load -- mass rebuilds, for example.

Scope

Kernels uploaded to EC2 for Fedora 12 and 13

A process to upload kernels for each upcoming release

A process to upload images for default spins for each release

Test Plan

FIXME

User Experience

FIXME

Dependencies

FIXME

Contingency Plan

Nothing in this plan stands in the way of the Fedora release itself -- everything is additional tools and processes. Therefore, contingency plan is to slip until we're ready to upload full images of F12 and F13, whenever that happens to be.