Go to file
ricolin 41cc012b34 Allow run tests for both tempest plugin and regression tests
Regression tests will be maintained in-tree. See categries list:
https://etherpad.openstack.org/p/heat-integration-test-categories

We will seperate tests to tempest plugin or in-tree base on conditions
of each tests. So we need to rework on framework for integration tests.
This patch propose following changes:
* This partially reverts commit fff6518e69
* Allow running heat tempest plugin and heat regression tests.
* iniset configs to both heat_integrationtests.conf and tempest.conf

Change-Id: Ief31dc961bc108e2863119598dfb16581a38e9cf
Depends-On: I5e9325766ce166e62c731330c462c030cb1e11fc
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
2018-01-19 13:26:25 -05:00
2018-01-17 16:07:36 +00:00
2017-03-24 11:58:38 +08:00
2017-11-16 18:23:58 -05:00
2012-12-02 17:46:15 +00:00
2017-12-15 12:39:37 +05:30
2017-12-11 14:13:42 +00:00
2012-03-14 09:25:54 +11:00
2017-08-08 12:34:20 +05:30
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

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

References

We have integration with

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