Changes/VisibleCloud

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Change announced on 2013-07-15)
(Add tracker bug)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Visible =
+
= Visible Cloud =
  
 
== Summary ==
 
== Summary ==
Line 15: Line 15:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/20 | Fedora 20]]  
 
* Targeted release: [[Releases/20 | Fedora 20]]  
* Last updated: July 12, 2013
+
* Last updated: July 16, 2013
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
Bugzilla states meaning as usual:
 
Bugzilla states meaning as usual:
Line 24: Line 24:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=998582 #998582]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 45: Line 45:
 
* Other developers: This will probably require a overhaul of the Get Fedora website, as that is current primarily focused on the desktop download.  
 
* 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.
+
* 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.  
+
* 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 ==
 
== Upgrade/compatibility impact ==
Line 80: Line 80:
 
None required, as this change affects the project but not the distribution itself.
 
None required, as this change affects the project but not the distribution itself.
  
[[Category:ChangeAnnounced]]
+
[[Category:ChangeAcceptedF20]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 14:33, 19 August 2013

Contents

[edit] Visible Cloud

[edit] 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.

[edit] Owner

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

[edit] Current status

[edit] 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.

[edit] 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.

[edit] 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. 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.

[edit] Upgrade/compatibility impact

Not applicable.

[edit] 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.

[edit] User Experience

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

[edit] Dependencies

None

[edit] 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.

[edit] Documentation

None but this web page currently.

[edit] Release Notes

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