Revision as of 21:05, 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

Name: Matthew Miller

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

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).

Will also need procedure for producing, testing, and blessing the official images for test and final releases.

How To Test

Do the images exist?
Do they boot in
- OpenStack?
- Eucalyptus?

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion

See Talk:Features/Your_Feature_Name

@@ Line 32: / Line 32: @@
 == How To Test ==
-<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+* Do the images exist?
+* Do they boot in
-Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
+** OpenStack?
+** Eucalyptus?
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this feature? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the feature is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
 == User Experience ==

Search

Features/FirstClassCloudImages: Difference between revisions