ramishra 22c48f57bb Use constraints when creating tempest venv
When running tempest we run in-tree tests as well. Lots of these
tests including tempest tests may not work with new client
libraries. Let's use the relevant branch upper constraints when
running functional tests.

Change-Id: I6a8cffdc86c895eebe4269c5cd37841325566c54
2022-06-07 12:59:35 +05:30
2020-04-16 06:43:27 +00:00
2022-05-31 10:35:53 +02:00
2020-04-30 18:49:55 +02:00
2019-04-22 09:36:50 +05:30
2020-09-10 14:19:03 -04:00
2019-04-19 19:33:28 +00:00
2017-12-15 12:39:37 +05:30
2022-06-03 16:36:40 +09:00
2012-03-14 09:25:54 +11:00
2019-06-26 17:48:15 +02:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2020-04-09 14:14:38 +08:00
2022-02-08 23:06:14 +09:00
2021-01-06 16:28:32 +08: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://opendev.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 212 MiB
Languages
Python 99.5%
Shell 0.5%