First-Class Cloud Images
This feature expands Fedora's current cloud image deliverables beyond just EC2, and overhauls how they are produced. A goal is to produce cloud images for EC2 and other cloud deployments for the Alpha, Beta, and Final compose process and distribute them on the mirror network. There will also be nightly or weekly image builds for Rawhide to assist with early development. All images should be constructed using a newer generation of tools.
- Name: Matthew Miller
- Email: mattdm at fedoraproject dot org
- Targeted release: Fedora 19
- Last updated: January 20, 2013
- Percentage of completion: 0%
- New images that can be used in other cloud deployments (such as OpenStack, CloudStack, or Eucalyptus) will be produced. They will be in a qcow2 format and lack the EC2-specific customization. Images for this feature would ideally work for all cloud deployments and there will be i686 and x86_64 versions of both image types. In total and "image drop" will have 4 images: 2 arches for 2 different types (EC2, not-EC2).
- An image drop will be produced for Alpha, Beta, and Final composes.
- Scratch build image drops will be produced on a weekly basis for Fedora 19.
- Scratch build image drops will be produced on a weekly basis for Rawhide as well to enable early testing.
- The Fedora Koji instance needs to be updated to a future release that will integrate with ImageFactory and Oz from the Aeolus Project. This future release is not implemented yet.
- The EC2 images will be automatically uploaded and registered in EC2. The Final AMIs for Fedora 19 will be available in the Amazon marketplace.
Benefit to Fedora
- Cloud images more easily available to users
- Cloud images available for better testing
- Constant building of images provides better platform for testing in general
Updates to Koji are a fairly major infrastructure change. We'll need bare-metal builders (or nested virt). ImageFactory/Oz will grow the ability to take kickstarts in addition to xml templates. Creating LiveCDs with the same system will also require some changes to ImageFactory/Oz.
Release engineering will produce images weekly (in an automated way). These will need to be easily discoverable (from the Cloud SIG web page, for example).
Will also need procedure for producing, testing, and blessing the official images for test and final releases. These will be released using the current Fedora mirroring system, alongside the install images.
Approximate dates to be added shortly.
- Out-of-Koji test implementation
- Code landed in Koji
- Builders updated
- Test-builds are functional
- Scripting for automatic weeklies
- Weeklies hitting alt
- Actual builds for alpha, beta, final on the mirrors
How To Test
- Do the images exist?
- In EC2
- Weekly in wherever those will go
- On the mirrors for Alpha, Beta, and Final
- in qcow2
- in raw.tar.xz
- Do the downloadable images boot in
- Installed image should appear similar to one installed by Anaconda
Official cloud images downloadable from mirror system.
None outside those identified in the scope.
Livemedia-creator could be used instead of Oz.
Failing that, continue to use appliance-creator for EC2 images and to generate images for download outside of official channels. Feel sad.
If the Koji integration work is not completed before Fedora 19 Alpha, consider updating Fedora Koji to the 1.7.1 release, which tracks images using the same data model as RPMs. This will at least improve the manageability if the images produced.
Possibly a small readme file should go alongside the images. Primary documentation on Cloud SIG web page.