From Fedora Project Wiki
No edit summary
m (internal link cleaning)
 
(15 intermediate revisions by 5 users not shown)
Line 10: Line 10:
== Current status ==
== Current status ==
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Last updated: 2011-12-20
* Last updated: 2012-02-27
* Percentage of completion: 01%
* Percentage of completion: 100%


== Detailed Description ==
== Detailed Description ==
Line 28: Line 28:
== How To Test ==
== How To Test ==


TBD.  We have booked a test day.
We are organizing a complete test of OpenStack Essex on the [[Test_Day:2012-03-08_OpenStack_Test_Day|OpenStack test day, 2012-03-08]].


<!-- 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.  
<!-- 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.  
Line 45: Line 45:


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
Users will be able to deploy OpenStack Essex release on Fedora 17 hosts with a single <code>yum install</code> command.


== Dependencies ==
== Dependencies ==
Line 51: Line 52:
This feature is an overview, but as well as this upgrade (which is not simple in itself) we are also planning to make significant upstream contributions and package those for Fedora.  The following features are planned:
This feature is an overview, but as well as this upgrade (which is not simple in itself) we are also planning to make significant upstream contributions and package those for Fedora.  The following features are planned:


* [[Features/OpenStack Horizon]]
* [[Features/OpenStack Quantum]]
* [[Features/OpenStack using libguestfs]]
* [[Features/OpenStack using libguestfs]]
* [[Features/OpenStack using Oz for image building]]
* [[Features/OpenStack using virtual watchdog]]
* [[Features/OpenStack using Qpid]]
* [[Features/OpenStack using Qpid]]
* more to come ...


Note that these are not all strictly dependencies on this feature, in that if they are not all completed, then we should still be able to complete this feature.
Note that these are not all strictly dependencies on this feature, in that if they are not all completed, then we should still be able to complete this feature.


== Contingency Plan ==
== Contingency Plan ==
The parts of OpenStack that are ready will be included in Fedora.  There is no special contingency plan required.
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
* http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17
* http://docs.openstack.org


== Release Notes ==
== 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/ -->
<!-- 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/ -->
<!-- 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 feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
<!-- 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 feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
* http://wiki.openstack.org/ReleaseNotes/Essex


== Comments and Discussion ==
== Comments and Discussion ==
Line 75: Line 79:




[[Category:FeaturePageIncomplete]]
[[Category:FeatureAcceptedF17]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
[[Category:OpenStack]]

Latest revision as of 20:44, 19 September 2016

OpenStack Essex

Summary

OpenStack will be upgraded to the next major stable release, called "Essex".

Owner

Current status

  • Targeted release: Fedora 17
  • Last updated: 2012-02-27
  • Percentage of completion: 100%

Detailed Description

OpenStack is an open source cloud computing platform. It lets you set up your own cloud infrastructure, similar to public clouds like Amazon EC2, Azure, etc.

In Fedora 15 & 16 there was a small effort to get OpenStack "Diablo" packaged for Fedora. For Fedora 17 we aim to get OpenStack "Essex" packaged, and make many upstream improvements (see the Dependencies section below).

Essex is not released yet, but is scheduled to be released roughly over the same development period as Fedora 17, and we are working closely with upstream to ensure this happens.

Benefit to Fedora

Fedora users will be able to deploy OpenStack clouds based on the latest version (Essex). Plus they will get many improvements, see Dependencies below.

Scope

This is mainly packaging work. The other features we aim to implement will involve both significant upstream changes and packaging work for Fedora.

How To Test

We are organizing a complete test of OpenStack Essex on the OpenStack test day, 2012-03-08.


User Experience

Users will be able to deploy OpenStack Essex release on Fedora 17 hosts with a single yum install command.

Dependencies

This feature is an overview, but as well as this upgrade (which is not simple in itself) we are also planning to make significant upstream contributions and package those for Fedora. The following features are planned:

Note that these are not all strictly dependencies on this feature, in that if they are not all completed, then we should still be able to complete this feature.

Contingency Plan

The parts of OpenStack that are ready will be included in Fedora. There is no special contingency plan required.


Documentation

Release Notes

Comments and Discussion