Go to file
Luigi Toscano 2b580f4258 Allow users to disable the tests run by Grenade
Setting RUN_HEAT_INTEGRATION_TESTS=False disables the Heat
integration tests which are normally executed by Grenade
after the deployment of the base environment and after the upgrade.
This is useful when Heat is used in a Grenade job of another
component, where the focus of the testing is not Heat itself,
thus shortening the run-time of the overall Grenade job.

The default behavior is unchanged.

Change-Id: I47b258fecd45ebc08c82df179625bcfb57a32894
2019-03-01 22:47:28 +01:00
2018-01-28 09:11:17 +05:30
2018-07-26 14:57:58 +07:00
2018-02-01 15:38:25 +00:00
2012-12-02 17:46:15 +00:00
2017-12-15 12:39:37 +05:30
2012-03-14 09:25:54 +11:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2018-11-12 10:02:46 +08:00
2017-03-02 17:42:22 +00:00
2016-01-17 05:20:40 +00:00

Team and repository tags

image

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

Report a Story (a bug/blueprint)

If you'd like to report a Story (we used to call a bug/blueprint), you can report it under Report a story in Heat's StoryBoard. If you must report the story under other sub-project of heat, you can find them all in Heat StoryBoard Group. if you encounter any issue.

References

We have integration with

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