From Fedora Project Wiki
Line 49: Line 49:


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
None outside those identified in the scope.


== Contingency Plan ==
== Contingency Plan ==

Revision as of 21:13, 19 January 2013

First-Class Cloud Images

Summary

Cloud images for EC2 and for generic use (download and use in any cloud environment, like OpenStack, CloudStack, or Eucalyptus) will be produced as part of the Alpha, Beta, and Final compose process, and distributed on the mirror network. We'll also have automatic nightly builds of Rawhide and of the development version.

Owner

  • Email: mattdm at fedoraproject dot org

Current status

  • Targeted release: Fedora 19
  • Last updated: January 19, 2013
  • Percentage of completion: 0%

Detailed Description

  • Koji updated to support image creation under visualization using Factory/Oz
  • Scratch images built weekly
  • "Blessed" built for Alpha, Beta, and Final
  • As-similar-as-possible images uploaded to EC2 (and ideally 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

Scope

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.

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
    • OpenStack?
    • Eucalyptus?
  • Installed image should appear similar to one installed by Anaconda

User Experience

Official cloud images downloadable from mirror system.

Dependencies

None outside those identified in the scope.

Contingency Plan

Documentation

Release Notes

Comments and Discussion