Difference between revisions of "Heat"
(Updated with next release information.) |
|||
| Line 50: | Line 50: | ||
April 4, 2012 - Launching a [[WordPress]] template with [https://github.com/heat-api/heat/tarball/v1-POC.release POC]. See Heat's [https://github.com/heat-api/heat/wiki/HeatGettingStartedPOC getting started guide]. | April 4, 2012 - Launching a [[WordPress]] template with [https://github.com/heat-api/heat/tarball/v1-POC.release POC]. See Heat's [https://github.com/heat-api/heat/wiki/HeatGettingStartedPOC getting started guide]. | ||
| − | April 23, 2012 - Multiple Instance [[WordPress]] template [https://github.com/heat-api/heat/tarball/v2-M1.release | + | April 23, 2012 - Multiple Instance [[WordPress]] template [https://github.com/heat-api/heat/tarball/v2-M1.release v2-M1]. See Heat's [https://github.com/heat-api/heat/wiki/Getting-Started-with-Heat-v2-M1 getting started guide]. |
---- | ---- | ||
[[Category:RelatedProjects]] | [[Category:RelatedProjects]] | ||
Revision as of 01:47, 23 April 2012
<<TableOfContents()>>
Heat
Heat provides a REST API to orchestrate multiple composite cloud applications implementing the AWS CloudFormation API.
Why heat? It makes the clouds rise!
Architecture
The developers are focused on creating an OpenStack style project using OpenStack design tenants implemented in Python. We have started with full integration with Keystone. We have three components.
An overview of the architecture is available. More details of the heat implementation can be found here. As the developers have only started development in March 2012, the architecture is in a rapid change.
heat
The heat tool is a CLI which communicates with the heat-api to execute AWS CloudFormation APIs. End developers could also use the heat REST API directly.
heat-api
The heat-api component provides a REST API that processes API requests by sending them to the heat-engine.
heat-engine
The heat engine connects to the heat-api over RPC to process API operations. The heat engine's main responsibility is to orchestrate the launching of templates and provide events back to the API consumer.
The templates integrate well with Puppet and Chef
Links
GitHub Repository: https://github.com/heat-api
Web Site: http://www.heat-api.org
Mailing List: here
Milestones: here
Open Issues: here
IRC
The developers use IRC on #heat on freenode for development discussion.
Status of implementation
March 16, 2012 - Code base started.
April 4, 2012 - Launching a WordPress template with POC. See Heat's getting started guide.
April 23, 2012 - Multiple Instance WordPress template v2-M1. See Heat's getting started guide.
