Jason Dunsmore 5d1b4ab3e9 Move API parameter parsing from OpenStack API to engine
In commit 4169c1bd8ce4db0a794e22471994ea401b77b9c0, the API parameter
parsing was moved to the OpenStack API.  Since then, inputs to the CFN
API were not being validated, creating a security hole.

Change-Id: I21920591075bcefbe695316dab6605afd6f4ec64
Closes-Bug: #1317667
2014-05-19 20:53:15 -04:00
2014-05-09 07:16:47 +10:00
2014-05-08 10:11:28 +08: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
2013-08-06 22:08:27 -07:00
2014-04-25 21:13:12 -07:00
2014-05-09 02:42:01 +00:00
2014-05-08 10:11:28 +08: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%