Jump to: navigation, search

Difference between revisions of "Heat"

m (Status of implementation)
(Links)
Line 53: Line 53:
 
* [http://wiki.openstack.org/Heat/DevelopmentProcess Developer Process]
 
* [http://wiki.openstack.org/Heat/DevelopmentProcess Developer Process]
 
* [http://wiki.openstack.org/Heat/ReleaseProcess Release Process]
 
* [http://wiki.openstack.org/Heat/ReleaseProcess Release Process]
 +
* [http://wiki.openstack.org/Heat/BotoCompatibility Boto Compatibility Matrix]
  
 
== Getting Started Guides ==
 
== Getting Started Guides ==

Revision as of 06:57, 5 April 2013

Summary:

Heat is a service to orchestrate multiple composite cloud applications using the AWS CloudFormation template format, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API.

Detailed Description:

What is the purpose of the project and vision for it?

  • Heat provides an AWS CloudFormation implementation for OpenStack that orchestrates an AWS CloudFormation template describing a cloud application by executing appropriate OpenStack API calls to generate running cloud applications.

Describe the relevance of the project to other OpenStack projects and the OpenStack mission to provide a ubiquitous cloud computing platform:

  • The software integrates other core components of OpenStack into a one-file template system. The templates allow creation of most OpenStack resource types (such as instances, floating ips, volumes, security groups, users, etc), as well as some more advanced functionality such as instance high availability, instance autoscaling, and nested stacks. By providing very tight integration with other OpenStack core projects, all OpenStack core projects could receive a larger user base.
  • Currently no other CloudFormation implementation exists for OpenStack. The developers believe cloud developers have a strong desire to move workloads from AWS to OpenStack deployments. Given the missing gap of a well-implemented and integrated CloudFormation API in OpenStack, we provide a high quality implementation of this gap improving the ubiquity of OpenStack.

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 tenets, implemented in Python. We have started with full integration with Keystone. We have a number of components.

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 an OpenStack-native REST API that processes API requests by sending them to the heat-engine over RPC.

heat-api-cfn

The heat-api-cfn component provides an AWS Query API that is compatible with AWS CloudFormation and processes API requests by sending them to the heat-engine over RPC.

heat-engine

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

Getting Started Guides

HOWTO Guides

IRC

The developers use IRC in #heat on freenode for development discussion.

Meetings

The Heat IRC meeting is held on Wednesday at 2000 UTC

Status of implementation

November, 2012 - Heat has been incubated!

October 23, 2012 - OpenStack-native API support, authenticated metric collection via CloudWatch-compatible API v7.

September 20, 2012 - Automated functional testing, many bug fixes, improved CloudWatch-compatible API, more templates v6.

July 31, 2012 - Access scoping by tenant in Keystone, CloudWatch-compatible API for metrics, more templates v5.

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

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

April 23, 2012 - Multiple Instance WordPress template v2-M1. See Heat's getting started guide.

April 4, 2012 - Launching a WordPress template with POC. See Heat's getting started guide.

March 16, 2012 - Code base started.