From Fedora Project Wiki

Visible Cloud


With Fedora 19's First Class Cloud Images feature, we have Amazon EC2 and downloadable cloud images (in qcow2 and raw.xz format) produced and released together with the traditional desktop installer and and livecd images. Now, let's go to the next level and present the cloud images as equal options.


  • Name: Matthew Miller
  • Email: mattdm at fedoraproject org
  • Release notes owner:

Current status

Detailed Description

This involves three key changes. They are not significant changes to other packages, but since this has implications for the distribution as a whole, I thought it best considered as bigger than a self-contained change.

  1. Refactoring of the Fedora web site to put the cloud image on equal footing with the desktop image download. The new F19 cloud images page is very nice thanks to the hard work of the web team, but unfortunately, in order to find it, one has to go down into the cellar, into a disused lavatory with a sign on the door saying Beware of the Leopard. Let's put it on display in the metaphorical front lobby.
  2. Creating specific release criteria and tests for basic cloud image functionality in, at least, Amazon EC2 and OpenStack. (Tests for smaller public cloud services could be added once those services gain the ability for us to provide official images directly. Tests for Eucalyptus and other IaaS software could be added as well.)
  3. Building images in Koji using virtualization and Anaconda, rather than using a chroot-based appliance-creator. This will ensure that the cloud image is more in line with The Real Fedora.

Benefit to Fedora

The IT world is in the middle of a significant shift to cloud-based infrastructure. We've put significant work into making the cloud image a solid technical base, and we'd like to reflect that in how we present it to users.

The rapidly-moving startup companies and developers focused on building in the cloud are a natural userbase for Fedora. Presenting the cloud image as a top-level part of Fedora will accelerate our growth in an area that is already rapidly growing.


  • Proposal owner: Coordination; working with web designers and documentation writers to develop the new presentation, working with QA to develop criteria and tests, and working with release engineering to land the changes to image building. I plan to be actively involved in all of these.
  • Other developers: This will probably require a overhaul of the Get Fedora website, as that is current primarily focused on the desktop download.
  • Release engineering: Yes, Jay Greguske, Andrew Thomas, and I are working on the improvements to the image build system and coordinating with Dennis Gilmore. Additionally, current ad hoc process for producing updated images for security updates will be codified.
  • Policies and guidelines: As noted, QA guidelines will need to be updated. Will work with Fedora security team to establish a security policy for updates.

Upgrade/compatibility impact

Not applicable.

How To Test

  1. New web site presents cloud image as prominently as the desktop download
  2. Release criteria reflect cloud image requirements
  3. New image works according to those requirements.

User Experience

Fedora user experience will not change, but the way Fedora is presented will.



Contingency Plan

Same as we currently do things. Additionally, the three elements are severable; any one can fail and fall back independently without affecting the others.

  • Contingency mechanism: Simply, things stay the status quo.
  • Contingency deadline: Final release. Of course, the strength of the release criteria developed for final depend on those for Alpha and Beta and will likely be less strict if not made early.
  • Blocks release? No.


None but this web page currently.

Release Notes

None required, as this change affects the project but not the distribution itself.