375226ecff
All attributes are retrieved (including ones referenced in the output). In our functional test there is a bug where a nested stack did not have an output that was referenced from the output. This didn't effect the stack creation as: - outputs are not normally required in the stack creation - if the output is used by a TemplateResource it *may* be used The way outputs are used currently is that they do not fail on the first output that doesn't work as it is useful to get the ones that do work. To help with this errors are placed alongside the value (in a key "error_msg"). This is somewhat problematic in convergence as we now *require* all attributes (including those based off of outputs). Note: if you have an outer resource referencing a non-existent template resource output it *will* fail, but when the outer stack's output references the inner stack's output then it is not validated. Change-Id: Id07c617a19eae56543f92ee21aea58cd38fa3606 |
||
|---|---|---|
| bin | ||
| contrib | ||
| devstack/upgrade | ||
| doc | ||
| etc/heat | ||
| heat | ||
| heat_integrationtests | ||
| heat_upgradetests | ||
| rally-scenarios | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| bandit.yaml | ||
| config-generator.conf | ||
| install.sh | ||
| openstack-common.conf | ||
| py3-testlist | ||
| pylintrc | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| uninstall.sh | ||
README.rst
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
- https://github.com/openstack/python-novaclient (instance)
- https://github.com/openstack/python-keystoneclient (auth)
- https://github.com/openstack/python-swiftclient (s3)
- https://github.com/openstack/python-neutronclient (networking)
- https://github.com/openstack/python-ceilometerclient (metering)
- https://github.com/openstack/python-cinderclient (storage service)
- https://github.com/openstack/python-glanceclient (image service)
- https://github.com/openstack/python-troveclient (database as a Service)
- https://github.com/openstack/python-saharaclient (hadoop cluster)