Revision as of 17:50, 12 July 2013

Visible

Summary

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.

Owner

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

Current status

Targeted release: Fedora 20
Last updated: July 12, 2013
Tracker bug: <will be assigned by the Wrangler>

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.

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

Scope

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.

Policies and guidelines: As noted, QA guidelines will need to be updated.

Upgrade/compatibility impact

Not applicable.

How To Test

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

User Experience

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

Dependencies

None

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.

Documentation

None but this web page currently.

Release Notes

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

@@ Line 3: / Line 3: @@
 == Summary ==
 With Fedora 19's [[Features/FirstClassCloudImages | 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.
-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.
-. Refactoring of the Fedora web site to put the cloud image on equal footing with the desktop image download. The new [http://fedoraproject.org/en/get-fedora-options#clouds 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.
-. 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.)
-. 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.
 == Owner ==
@@ Line 15: / Line 9: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:mattdm| Matthew Miller]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
+* Email: mattdm at fedoraproject org
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
 * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
-<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
-* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
--->
 == Current status ==
-* Targeted release: [[Releases/<number> | Fedora <number> ]]
+* Targeted release: [[Releases/20 | Fedora 20]]
-* Last updated: (DATE)
+* Last updated: July 12, 2013
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 Bugzilla states meaning as usual:
@@ Line 37: / Line 28: @@
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+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.
+# Refactoring of the Fedora web site to put the cloud image on equal footing with the desktop image download. The new [http://fedoraproject.org/en/get-fedora-options#clouds 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.
+# 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.)
+# 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 ==
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+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.
 == Scope ==
-<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Proposal owners:
+* 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.
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: This will probably require a overhaul of the Get Fedora website, as that is current primarily focused on the desktop download.
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: Yes, Jay Greguske, Andrew Thomas, and I are working on the improvements to the image build system and coordinating with Dennis Gilmore.
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
-* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines: As noted, QA guidelines will need to be updated.
-<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Not applicable.
-N/A (not a System Wide Change)
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation 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.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+# New web site presents cloud image as prominently as the desktop download
+# Release criteria reflect cloud image requirements
+# New image works according to those requirements.
-A good "how to test" should answer these four questions:
+== User Experience ==
-. What special hardware / data / etc. is needed (if any)?
+Fedora user experience will not change, but the way Fedora is presented will.
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+== Dependencies ==
-N/A (not a System Wide Change)
+None
-== User Experience ==
+== Contingency Plan ==
-<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
-== Dependencies ==
+Same as we currently do things. Additionally, the three elements are severable; any one can fail and fall back independently without affecting the others.
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change 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 change)? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: Simply, things stay the status quo.
-N/A (not a System Wide Change)
+* 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.
-== Contingency Plan ==
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+None but this web page currently.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+None required, as this change affects the project but not the distribution itself.
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
-Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
--->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeReadyForWrangler]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 120: / Line 91: @@
 <!-- Select proper category, default is Self Contained Change -->
-[[Category:SelfContainedChange]]
+[[Category:SystemWideChange]]
 <!-- [[Category:SystemWideChange]] -->

Search

Changes/VisibleCloud: Difference between revisions