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.
- Name: Greg DeKoenigsberg
- Targeted release: Fedora 13
- Last updated: (2009-02-05)
- Percentage of completion: 0%
Open Action Items
- ACTION: huff to deliver a first pass base ks with min packageset extra stuff in post for amazon specific stuff. (Oxf13, 20:38:14)
- ACTION: jforbes continues to wrangle a kernel for us to use (Oxf13, 20:38:32)
- ACTION: jforbes will document kernel/initramfs upload process (Oxf13, 21:08:29)
- ACTION: jforbes will share upload credentials with Fedora kernel developers (Oxf13, 21:08:39)
- ACTION: gregdek will ask amazon to host srpms on s3 for fedora akis (gregdek, 21:41:48)
- ACTION: gregdek will ask amazon to host update servers for fedora (gregdek, 21:42:03)
- ACTION: gregdek will handle getting S3 setup in MirrorManager
- ACTION: Get euca2ools approved in Fedora
Completed Action Items
- None yet
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.
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.
Comments and Discussions