Zane Bitter 79cc0cc7b9 Don't attempt to update tmpl ID when resource in progress
If we attempt to do a convergence update on a resource and find it already
locked by another traversal, don't try to update the resource's current
template ID or requirements data. Doing so will usually fail with the same
exception, but it is unnecessary and leaves ERROR-level messages in the
log. However, there is a race which could result in the call succeeding
(i.e. if the other task releases the lock just after we fail to get it),
and that could result in the resource not being updated at all.

Change-Id: I6bde1f9359cd52c99cca092e8abc660bac8b3065
Closes-Bug: #1722371
2017-10-18 16:47:53 -04:00
2017-03-25 17:11:50 +08:00
2017-03-24 11:58:38 +08:00
2017-04-06 11:42:05 -07:00
2017-04-03 09:32:25 +00:00
2012-12-02 17:46:15 +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 212 MiB
Languages
Python 99.5%
Shell 0.5%