11571e1f86bbfd78ac604b8e2f1ca4c9052f78c8
The problem is that the timeout for running any action (i.e. create or update) on stack is not passed from parent stack to nested stack. All heat resources which are internally implemented as StackResource are affected. For example AutoScalingGroup always using default timeout (60 minutes). If creating any of the instances will take more that it will fail no matter what timeout you will pass creating stack. Changes: * removes hardcoded timeout (60 minutes) * adds new config option to specify timeout for stack action * if timeout was not specified for nested stack then timeout from parent is used * adds test for StackResource and parser.Stack Change-Id: I39494b75774988c625cb22cc7873d628c04d3228 Closes-Bug: 1287719
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
- Wiki: http://wiki.openstack.org/Heat
- Developer docs: http://docs.openstack.org/developer/heat
Python client
https://github.com/openstack/python-heatclient
References
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
- http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca
We have integration with
Description
Languages
Python
99.5%
Shell
0.5%