252ce059c7
Currently, the patch does the following: Kicks off workflow from stack.update_or_create: Once the dependency graph is calculated, the leaves of the graph are all casted into the RPC worker bus. Worker RPC check_resource worfklow: Workers will then start working on each resource individually. Once a resource operation is finished, sync points are used to check if the parent resource can be worked on. Resources that finish early will wait for their siblings to finish. The sibling that finishes last will trigger the creation/updation/deletion of it's parent. This process then goes on for all nodes until the roots of the graph are processed. Marks stack as complete when roots have finished. Once the roots of the graph are successfully processed, the previous raw template which was needed for rollback in case something went wrong will now be deleted from the database. The stack is then marked as complete. Largely follows the convergence prototype code in github.com/zaneb/heat-convergence-prototype/blob/resumable/converge/converger.py Implements blueprint convergence-check-workflow Change-Id: I67cfdc452ba406198c96afba57aa4e756408105d |
||
|---|---|---|
| bin | ||
| contrib | ||
| doc | ||
| etc/heat | ||
| heat | ||
| heat_integrationtests | ||
| rally-scenarios | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| config-generator.conf | ||
| install.sh | ||
| openstack-common.conf | ||
| py3-testlist | ||
| pylintrc | ||
| requirements-py3.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements-py3.txt | ||
| 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)