huangtianhua 4a79f7ca53 Migrate to aodh for OS::Ceilometer::Alarm
This changes:
1. use aodhclient to manage OS::Ceilometer::Alarm
resource, including create, update, delete, check, suspend,
resume and show.
2. rename OS::Ceilometer::Alarm to OS::Aodh::Alarm
3. considering to compatible with old templates with resource
OS::Ceilometer::Alarm, set resource_registry to map Ceilometer alarm
to Aodh alarm

Blueprint migrate-to-use-aodh-for-alarms

Change-Id: I6e2d14f15a345b927b53adc237cf2bf4010842f0
2016-06-29 02:50:27 +00:00
2016-05-16 07:38:46 +00:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2015-07-08 09:13:35 -04:00
2015-06-23 08:30:39 +02:00
2016-06-24 09:07:51 +00:00
2016-06-24 09:07:51 +00:00
2015-09-22 10:40:48 +00:00
2016-06-07 17:31:20 +00:00
2016-01-17 05:20:40 +00:00

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 https://git.openstack.org/openstack/heat

Python client

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 212 MiB
Languages
Python 99.5%
Shell 0.5%