No edit summary |
(Moved to FeatureReadyForFesco, ticket #909) |
||
Line 97: | Line 97: | ||
[[Category: | [[Category:FeatureReadyForFesco]] | ||
<!-- 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 --> |
Revision as of 13:05, 20 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. 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-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.