OpenStack Orchestration (Heat)
Go to file
Rabi Mishra 9e80518b90 Handle OS::Mistral::Workflow resource replacement properly
OS::Mistral::Workflow resource creates a mistral workflow with
a unique name (resource_id). We replace FAILED resources by
default and replace wont work in this case as it will try to
use the same workflow name for the replacement resouce, if the
'name' property is provided.

If the workflow does not exist/deleted using mistral api directly,
it would create a replacement resource, but it would delete the
workflow when cleaning up the old resource. So we would endup
with a replacement resource without any backing workflow.

This adds a new resource attribute ``always_replace_on_check_failed``
and overrides needs_replace_failed() for OS::Mistral::Workflow.

Task: 38855
Change-Id: Ia0812b88cae363dfa25ccd907ecbe8b86f5b1a23
2020-02-25 08:37:16 +05:30
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 Remove image upload dependency on g-reg 2020-01-17 21:41:05 +05:30
doc Migrate doc path to contributor 2020-02-22 14:16:50 +08:00
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Handle OS::Mistral::Workflow resource replacement properly 2020-02-25 08:37:16 +05:30
heat_integrationtests Merge "Check task_state of instance before volume actions" 2020-02-20 04:42:20 +00:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
rally-scenarios Switch to use opendev.org 2019-04-22 09:36:50 +05:30
releasenotes Merge "Use resource_id instead of phy res name `OS::Heat::AutoScalingGroup`" 2020-02-21 00:04:18 +00:00
roles/run-heat-tests Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
tools Dashboard: Add stable branch reviews 2019-12-23 18:48:35 +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 OpenDev Migration Patch 2019-04-19 19:33:28 +00:00
.stestr.conf Use stestr for unit tests 2017-12-15 12:39:37 +05:30
.zuul.yaml Migrate heat-functional-non-apache to zuul v3 2020-01-08 09:02:15 +00:00
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 Added a Vitrage client 2019-12-19 15:25:30 +00: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 Merge "New resource OS::Neutron::ExtraRouteSet" 2020-01-22 07:50:45 +00:00
requirements.txt Merge "New resource OS::Neutron::ExtraRouteSet" 2020-01-22 07:50:45 +00:00
setup.cfg [ussuri][goal] Finish dropping python 2.7 support 2020-02-06 18:58:12 +01:00
setup.py [ussuri][goal] Finish dropping python 2.7 support 2020-02-06 18:58:12 +01:00
test-requirements.txt Blacklist bandit 1.6.0 and cap Sphinx on Python2 2019-05-14 16:50:24 -04:00
tox.ini [ussuri][goal] Finish dropping python 2.7 support 2020-02-06 18:58:12 +01: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