RETIRED, further work has moved to Debian project infrastructure
0c50b7d23f
Heat had fallen behind the evolution of the Ceilometer API. The full generality of the Ceilometer API for creating alarms was not available through Heat templates. In particular, the template author could stipulate only matching metadata in the query for Samples; other very interesting attributes, such as resource_id, could not be referenced in alarm properties. This change introduces a new property for OS::Ceilometer::Alarm, namely "query". The template can now specify a query property instead of a matching_metadata property, and can thus reference anything that can be referenced in a Ceilometer query. The old matching_metadata property remains, and its constraints on which samples to accept are combined with those from the query (if any). Note also that the python-ceilometerclient has a lot of backward compatibility logic --- including accepting matching_metadata. This change adds all that logic into OS::Ceilometer::Alarm, so that it becomes a proper client of the current Ceilometer API. Closes-Bug: #1326721 Change-Id: I0667db868c6f827867a5a20e4a3fa22fcad1a6a1 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc/heat | ||
heat | ||
heat_integrationtests | ||
rally-scenarios | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
install.sh | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
uninstall.sh |
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)