No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Heat = | = Heat = | ||
| Line 31: | Line 29: | ||
== 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, but still needs much work before it will be acceptable for incubation by the OpenStack community. | the Heat implementation is high quality and secure, but still needs much work before it will be acceptable for incubation by the OpenStack community. | ||
| Line 51: | Line 49: | ||
* To test the feature, the Heat community recommends running through the Getting Started Guide.we recommend running the quickstart guide. | * To test the feature, the Heat community recommends running through the Getting Started Guide.we recommend running the quickstart guide. | ||
* The getting started guide explains the expected results of the feature. | * The getting started guide explains the expected results of the feature. | ||
[ | [https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst#readme Getting Started Guide] | ||
== User Experience == | == User Experience == | ||
| Line 67: | Line 65: | ||
== 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 == | ||
Revision as of 19:57, 19 July 2012
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: July 19, 2012
- Percentage of completion: 90%
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.
Scope
The feature is currently going through package review. the Heat implementation is high quality and secure, but still needs much work before it will be acceptable for incubation by the OpenStack community.
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.we recommend running the quickstart 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
We depend on a functional OpenStack implementation, but currently work well with Essex. We will also work well with Folsom when it becomes more stable.
Contingency Plan
The feature could be removed entirely as a contingency plan.
Documentation
- All documentation is in the Heat project's Wiki.
Release Notes
- Heat was added to provide an AWS CloudFormation API for OpenStack.