From Fedora Project Wiki
< Features
No edit summary |
No edit summary |
||
| Line 47: | 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 Getting Started Guide | * To test the feature, the Heat community recommends running through the [https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst#readme Getting Started Guide]. | ||
* The | * The [https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst#readmegetting started guide] explains the expected results of the feature. | ||
[https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst# | |||
== 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 work well with Essex. We will also work well with Folsom when it becomes more stable. | |||
The full list of packages Heat depends upon are: | |||
* python-crypto | |||
* 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 | |||
== 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 == | ||
Revision as of 20:03, 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.
- The 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 work well with Essex. We will also work well with Folsom when it becomes more stable.
The full list of packages Heat depends upon are:
- python-crypto
- 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
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.