Zane Bitter 2ea4bcf506 Pass unresolved template to Resource.update()
Previously the 'after' template passed to Resource.update() was completely
resolved. This led to an odd situation where the contents of a resource's
template snippet were either unresolved (but parsed) or resolved depending
on whether the resource had been updated or not. Resolve (ha!) this
discrepancy by passing a version of the template with the intrinsic
functions unresolved.

Change-Id: I8c11cdc3c28661db689b416833bde34cea12d98a
2014-05-02 21:51:01 -04:00
2014-04-25 21:13:12 -07:00
2014-04-30 23:19:57 +02:00
2014-04-25 21:13:12 -07:00
2014-01-25 13:58:21 +08:00
2012-12-02 17:46:15 +00:00
2014-03-03 10:49:28 -05: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
2014-04-12 10:01:51 +02:00
2013-08-06 22:08:27 -07:00
2014-04-12 10:01:51 +02:00
2014-04-25 21:13:12 -07:00
2013-10-01 16:13:02 +00:00
2014-04-16 20:05:42 +02: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%