5d6234ecf6
Currently we log all template resources every time any API call happens which indirectly creates an Environment object, which results in a lot of duplicate bloat in the heat logs (not even at debug level..) So, instead log all environment resources (e.g those from resource plugins and the global environment) only when we start the service, and log user-provided template resources only when we do the template validation on create/update, for only the root stack, because we pass a derived subset environment down to all children. We also switch to using the string representation of the ResourceInfo objects, as this contains a bit more useful info than the current log format. Change-Id: I20007c1ad6bf8b1479c1d60a5c392b8b9e1c06c4 Closes-Bug: #1499330 |
||
---|---|---|
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 | ||
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)
- https://github.com/openstack/python-barbicanclient (key management service)
- https://github.com/openstack/python-designateclient (DNS service)
- https://github.com/openstack/python-magnumclient (container service)
- https://github.com/openstack/python-manilaclient (shared file system service)
- https://github.com/openstack/python-mistralclient (workflow service)
- https://github.com/openstack/python-zaqarclient (messaging service)