From Fedora Project Wiki
< Features
No edit summary |
(fix link to getting started) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= Heat = | = Heat = | ||
| Line 16: | Line 14: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/18 | Fedora 18 ]] | * Targeted release: [[Releases/18 | Fedora 18 ]] | ||
* Last updated: | * Last updated: October 16, 2012 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 27: | Line 25: | ||
== 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?--> | <!-- 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?--> | ||
Heat provides a standardized method for OpenStack users to launch multiple applications in an OpenStack cloud from a template file describing the cloud application. | Heat provides a standardized method for OpenStack users to launch multiple applications in an OpenStack cloud from a template file describing the cloud application. This feature improves the cloudiness of Fedora by providing a stronger OpenStack feature set. | ||
== 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?--> | <!-- 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?--> | ||
The feature is currently going through package review. | The feature is currently going through [https://bugzilla.redhat.com/show_bug.cgi?id=840619 package review]. | ||
The Heat implementation is high quality and secure. | |||
== How To Test == | == How To Test == | ||
| Line 49: | Line 47: | ||
--> | --> | ||
* Install and configure Folsom OpenStack on the system. | * Install and configure Folsom OpenStack on the system. | ||
* To test the feature, the Heat community recommends running through the | * To test the feature, the Heat community recommends running through the [https://github.com/openstack/heat/blob/master/docs/GettingStarted.rst#readme getting started guide]. | ||
* The [https://github.com/openstack/heat/blob/master/docs/GettingStarted.rst#readme getting started guide] explains the expected results of the feature. | |||
[ | |||
== 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. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
The user will notice an AWS CloudFormation API available via the heat CLI command. | * The user will notice an AWS CloudFormation API available via the heat CLI 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)? --> | <!-- 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)? --> | ||
Heat does not have any dependencies, so no negative user change will be noticed. | |||
Heat depends on a functional OpenStack implementation, but currently is stable when tested with Essex. We will also work well with Folsom when it is packaged. | |||
The full list of packages which are all available in Fedora Rawhide Heat depends upon are: | |||
* python-eventlet | |||
* python-glance | |||
* python-greenlet | |||
* python-httplib2 | |||
* python-iso8601 | |||
* python-keystoneclient | |||
* python-kombu | |||
* python-lxml | |||
* python-memcached | |||
* python-migrate | |||
* python-novaclient | |||
* python-paste | |||
* python-qpid | |||
* python-routes | |||
* pysendfile | |||
* python-sqlalchemy | |||
* python-webob | |||
Note: python-crypto was previously listed as a dependency. The code using this dependency was imported from a different project (glance) and not used in heat. The dependency has been removed from heat based upon feedback from FESCo but was dead code and removed entirely as a dependency by removing the dead code. | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- 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. --> | ||
The feature could be removed entirely as a contingency plan. | The feature could be removed entirely as a contingency plan if there are packaging or dependency problems with no ill effects. | ||
== 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. --> | ||
* All documentation is in the Heat project's | * All documentation is in the Heat project's [https://github.com/heat-api/heat/wiki Wiki]. | ||
== Release Notes == | == Release Notes == | ||
| Line 78: | Line 98: | ||
[[Category: | [[Category:FeatureAcceptedF18]] | ||
<!-- 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 --> | ||
Latest revision as of 22:31, 6 January 2013
Heat
Summary
Heat provides an AWS CloudFormation API for OpenStack. The CloudFormation API allows the orchestration of cloud applications using file or web based templates.
Owner
- Name: Steven Dake
- Email: <sdake@redhat.com>
Current status
- Targeted release: Fedora 18
- Last updated: October 16, 2012
- Percentage of completion: 100%
Detailed Description
Heat provides orchestration of composite cloud applications using the CloudFormation API and templates for OpenStack. Heat has requested OpenStack incubation and is currently an OpenStack related project.
Benefit to Fedora
Heat provides a standardized method for OpenStack users to launch multiple applications in an OpenStack cloud from a template file describing the cloud application. This feature improves the cloudiness of Fedora by providing a stronger OpenStack feature set.
Scope
The feature is currently going through package review. The Heat implementation is high quality and secure.
How To Test
- Install and configure Folsom OpenStack on the system.
- To test the feature, the Heat community recommends running through the getting started guide.
- The getting started guide explains the expected results of the feature.
User Experience
- The user will notice an AWS CloudFormation API available via the heat CLI command.
Dependencies
Heat does not have any dependencies, so no negative user change will be noticed.
Heat depends on a functional OpenStack implementation, but currently is stable when tested with Essex. We will also work well with Folsom when it is packaged.
The full list of packages which are all available in Fedora Rawhide Heat depends upon are:
- python-eventlet
- python-glance
- python-greenlet
- python-httplib2
- python-iso8601
- python-keystoneclient
- python-kombu
- python-lxml
- python-memcached
- python-migrate
- python-novaclient
- python-paste
- python-qpid
- python-routes
- pysendfile
- python-sqlalchemy
- python-webob
Note: python-crypto was previously listed as a dependency. The code using this dependency was imported from a different project (glance) and not used in heat. The dependency has been removed from heat based upon feedback from FESCo but was dead code and removed entirely as a dependency by removing the dead code.
Contingency Plan
The feature could be removed entirely as a contingency plan if there are packaging or dependency problems with no ill effects.
Documentation
- All documentation is in the Heat project's Wiki.
Release Notes
- Heat was added to provide an AWS CloudFormation API for OpenStack.