Go to file
Zane Bitter ac87bc7c79 Get ResourceGroup/Chain attributes from nested stack outputs
Since Pike we've generated the templates for various nested stack resource
types with outputs that produce the attribute values that are referenced in
the parent stack, and a previous patch did the same for resource IDs. Use
these output values when available to calculate the attribute values. This
is efficient, because the all of the outputs are fetched together and
cached, and avoids using the grouputils functions that cause the nested
stack to get loaded into memory in the same process.

Fall back to the existing implementation (using grouputils) if the required
output isn't available (generally this would be due to the nested stack
being created on an earlier version of Heat that did not include the
outputs in the generated template, and not updated since).

Change-Id: I9146e1d99f494213daef7d61ae75c92a4ef981a9
Partial-Bug: #1731349
2018-01-19 15:37:10 -05:00
2017-03-24 11:58:38 +08:00
2017-11-16 18:23:58 -05:00
2018-01-10 15:35:54 +00:00
2012-12-02 17:46:15 +00:00
2017-12-15 12:39:37 +05:30
2017-12-11 14:13:42 +00:00
2012-03-14 09:25:54 +11:00
2017-08-08 12:34:20 +05:30
2017-03-02 17:42:22 +00:00
2017-12-15 12:39:37 +05:30
2016-01-17 05:20:40 +00:00

Team and repository tags

image

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 214 MiB
Languages
Python 99.5%
Shell 0.5%