Zane Bitter b46a4ad442 Let resources decide when to update
Previously, the StackUpdate code decided when an update was necessary for a
resource. However, all of the information required to make this decision is
available to the resource, so push this decision into the resource so that
it can implement custom behaviour if necessary.

Change-Id: If098424cf2502c02bad4194d509393d198d8745f
2013-11-27 12:27:06 +01:00
2013-10-29 08:26:40 +11:00
2013-11-22 12:36:29 +00:00
2013-11-27 12:27:06 +01:00
2012-12-02 17:46:15 +00:00
2013-04-30 13:51:07 -07:00
2012-03-14 09:25:54 +11:00
2013-05-25 08:46:32 +02:00
2013-10-24 11:03:11 -10:00
2013-08-06 22:08:27 -07:00
2013-10-02 17:11:30 +02:00
2013-10-01 16:13:02 +00:00
2013-10-14 21:11:56 -04:00
2012-06-23 22:41:30 -04:00

HEAT

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

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone git@github.com:openstack/heat.git

Python client

https://github.com/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 212 MiB
Languages
Python 99.5%
Shell 0.5%