Steve Baker 395cfbd1dd Adopt tempest plugin config namespace
As a transition strategy to running heat_integrationtests as a
tempest plugin, this change puts the test config values in the
"heat_plugin" section. This will allow for either test runner
to be used during the transition.

blueprint tempest-plugin-support

Change-Id: I2eab50be92c998aeb1ee98011908a9828a7efe6c
2016-08-03 01:59:46 +00:00
2016-05-16 07:38:46 +00:00
2016-06-30 16:06:53 +00:00
2016-08-02 11:50:33 +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
2015-09-22 10:40:48 +00:00
2016-07-29 17:18:45 +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 217 MiB
Languages
Python 99.5%
Shell 0.5%