Go to file
Ghanshyam Mann 604111b0ba Fix setting the tempest virtual env constraints env var
Heat upgrade script set the env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE
which are used to use the constraints during Tempest virtual env
installation. Those env var are set to non-master constraint when
we need to use non-master constraints but when we need to use the
master constraints we do not set/reset them point to master constraints.

This create the issue when this grenade script install the tempest with
stable constraints but with master Tempest and as there is mismatch of
constraints now with fasteners of stable branches. Below is failure
of heat greande job on stable/yoga

- https://zuul.opendev.org/t/openstack/build/3aaec4d59bb84068bb4d4428ea747cbd/log/controller/logs/grenade.sh_log.txt#3245

Similar way, role should set stable constraints only for the stable EM branch
not for all otherwise it fail when constraints/requirements are bumped.

- https://zuul.opendev.org/t/openstack/build/74f86b8097f44c35acaffdcfe41d9693

We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.

Closes-Bug: #2003993
Change-Id: I024cd134577338fc1075e7742df7f006dc914646
2023-02-21 16:05:09 +00:00
2020-04-16 06:43:27 +00: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
2012-03-14 09:25:54 +11:00
2022-06-10 20:27:28 +03: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-03-29 01:15:03 +10: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 214 MiB
Languages
Python 99.5%
Shell 0.5%