Go to file
tengqm d130a726cd api-ref doc for stack (2)
This patch continues the fix to the api-ref doc for stack resource. To
ensure upcoming patches are not messing up the parameter defintions,
this patch is cleansing up the parameters that appear both in URLs and
request/response bodies: 'stack_id', 'stack_name', 'resource_name',
'event_id', 'snapshot_id', etc. These parameters sometimes are playing
different roles although the name is the same.
Other fixes included in this patch:

- added back the stack-outputs and stack-snapshots into index
- split resource-types out of stack-templates and add reference to it
  into index (git misunderstood this as a renaming, :))

Change-Id: I2b486a9b85d23d3225a5701c2265ecea2f4712f7
2016-08-18 05:58:24 -04:00
2016-08-18 05:58:24 -04:00
2016-05-16 07:38:46 +00:00
2016-06-30 16:06:53 +00:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2015-07-08 09:13:35 -04:00
2015-06-23 08:30:39 +02:00
2016-06-24 09:07:51 +00:00
2015-09-22 10:40:48 +00:00
2016-07-29 17:18:45 +00:00
2016-01-17 05:20:40 +00: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 https://git.openstack.org/openstack/heat

Python client

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with

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