OpenStack Orchestration (Heat)
Go to file
ramishra 05708d9d95 Don't create deployment when changing transport
Earlier when changing software config transport we used to
create a dummy deployment to push the metadata. However
this would not work with convergence as we take
resource lock for the update which updates the config
transport (another engine would try to update the resource
metadata for deployment when one engine has locked it).

Currently it works when updating transport as we ignore
the error in creating dummy deployment, but if there are
any new depoyments for the server they would fail.

We don't need to push the metadata as it would be pushed
when the there is a new/updated deployment.

Few additional changes in the patch:

- We don't need to ignore the error as servers are now
not replaced if the resource is in ERROR when nova server
is good/ACTIVE.
- Delete the existing tempurls and zaqar queues when
  changing transport.

Task: 41744
Change-Id: Id592b29df36320d8697bd370252ada02612ba7d0
(cherry picked from commit 79fb6509a9)
2021-10-10 22:03:06 +00:00
api-ref/source Bump the openstackdocstheme extension to 1.20 2019-08-01 09:43:50 +08:00
bin Remove CloudWatch API 2018-01-28 09:11:17 +05:30
contrib/heat_docker Update devel info: mailing list 2018-12-05 09:02:33 +08:00
devstack Configure the Tempest venv upper constraints properly 2021-04-11 10:08:18 +00:00
doc Use Block Storage API v3 instead of API v2 2021-10-08 11:40:02 +05:30
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Don't create deployment when changing transport 2021-10-10 22:03:06 +00:00
heat_integrationtests Use Block Storage API v3 instead of API v2 2021-10-08 11:40:02 +05:30
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack/functional Add native grenade zuul v3 jobs 2021-04-04 15:10:48 +05:30
rally-scenarios Switch to use opendev.org 2019-04-22 09:36:50 +05:30
releasenotes Merge "Add SOURCE_IP_PORT to LB_ALGORITHM allowed values" into stable/train 2021-04-19 08:45:11 +00:00
tools Merge "Switch to review.opendev.org" 2019-09-26 04:43:36 +00:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-11-12 09:21:05 +05:30
.gitignore include sample config file in docs 2018-02-01 15:38:25 +00:00
.gitreview Update .gitreview for stable/train 2019-09-29 19:52:02 +00:00
.stestr.conf Use stestr for unit tests 2017-12-15 12:39:37 +05:30
.zuul.yaml Use Block Storage API v3 instead of API v2 2021-10-08 11:40:02 +05:30
CONTRIBUTING.rst Update http links for doc migration 2018-05-11 09:32:14 +08:00
HACKING.rst Clean up test requirements 2018-07-27 13:38:27 +00:00
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
README.rst Update readme 2019-07-31 17:19:40 +08:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
bindep.txt Add local bindep.txt 2019-06-26 17:48:15 +02:00
config-generator.conf Remove SSLMiddleware from oslo.config namespace 2017-11-27 13:05:00 +05:30
install.sh Remove use of heat_watch_server_url 2018-01-28 09:11:18 +05:30
lower-constraints.txt Replace Fedora test image with F32 2021-01-29 12:10:33 +00:00
requirements.txt Replace Fedora test image with F32 2021-01-29 12:10:33 +00:00
setup.cfg Remove designate v1 support 2019-09-26 10:04:03 +05:30
setup.py Updated from global requirements 2017-03-02 17:42:22 +00:00
test-requirements.txt Replace Fedora test image with F32 2021-01-29 12:10:33 +00:00
tox.ini Update TOX/UPPER_CONSTRAINTS_FILE for stable/train 2019-09-29 19:52:24 +00:00
uninstall.sh use stderr for error echo message 2016-01-17 05:20:40 +00:00

README.rst

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