Jump to: navigation, search

Difference between revisions of "Heat"

(unindented getting started guides)
(updated link style a bit)
Line 61: Line 61:
 
May 14, 2012 - High Availability [https://github.com/heat-api/heat/tarball/v3.release v3].  See Heat's [https://github.com/heat-api/heat/wiki/Getting-Started-with-Heat-v3 getting started guide].
 
May 14, 2012 - High Availability [https://github.com/heat-api/heat/tarball/v3.release v3].  See Heat's [https://github.com/heat-api/heat/wiki/Getting-Started-with-Heat-v3 getting started guide].
  
June 27, 2012 - Ubuntu Support, High Availability improvements, more templates - https://github.com/heat-api/heat/tarball/v4.release.
+
June 27, 2012 - Ubuntu Support, High Availability improvements, more templates [https://github.com/heat-api/heat/tarball/v4.release v4].  See Heat's [[[https://github.com/heat-api/heat/wiki |wiki] for documentation to get started.
 
----
 
----
 
[[Category:RelatedProjects]]
 
[[Category:RelatedProjects]]

Revision as of 17:26, 27 June 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. As the developers have only started development in March 2012, the architecture is evolving rapidly.

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

Getting Started Guides

Getting started on Fedora 16 & 17 https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst

Getting started on Ubuntu Precise https://github.com/heat-api/heat/wiki/Getting-Started-with-Heat-using-Master-on-Ubuntu.

Links

GitHub Repository: https://github.com/heat-api

Wiki Documentation: https://github.com/heat-api/heat/wiki

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.

May 14, 2012 - High Availability v3. See Heat's getting started guide.

June 27, 2012 - Ubuntu Support, High Availability improvements, more templates v4. See Heat's [[|wiki for documentation to get started.