From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...")
 
m (internal link cleaning)
 
(18 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
= OpenStack Essex =
 
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
 
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
 
 
<!-- All fields on this form are required to be accepted by FESCo.
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
 
= Feature Name <!-- The name of your feature --> =


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
OpenStack will be upgraded to the next major stable release, called "Essex".


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:Markmc | Mark McLoughlin]], [[User:Rjones| Richard Jones]]
* Name: [[User:FASAcountName| Your Name]]
* Email: markmc@redhat.com, rjones@redhat.com


<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
== Current status ==
* Email: <your email address so we can contact you, invite you to meetings, etc.>
* Targeted release: [[Releases/17 | Fedora 17 ]]
* Last updated: 2012-02-27
* Percentage of completion: 100%


== Current status ==
== Detailed Description ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]
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.
* Last updated: (DATE)
* Percentage of completion: XX%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
In Fedora 15 &amp; 16 there was a small effort to get OpenStack "Diablo" packaged for Fedora. For Fedora 17 we aim to get OpenStack "Essex" packaged, <b>and</b> make many upstream improvements (see the Dependencies section below).


== Detailed Description ==
Essex is not released yet, but is [http://wiki.openstack.org/EssexReleaseSchedule scheduled to be released] roughly over the same development period as Fedora 17, and we are working closely with upstream to ensure this happens.
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->


== Benefit to 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 feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
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 ==
== Scope ==
<!-- What work do the 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?-->
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 ==
== How To Test ==
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 55: 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 ==
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
 
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 Qpid]]
 
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 ==
* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/OpenStack Essex]]




[[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