Go to file
Rakesh H S 22f11f8812 Convergence: Work on IN_PROGRESS resources once lock acquired
The check in resource update logic to raise ResourceFailure if a
resource is already IN_PROGRESS does not apply for convergence.

- In convergence, before acting on a resource we try to acquire lock,
hence if a worker is already working on a resource(IN_PROGRESS),
another worker cannot start working on this IN_PROGRESS resource.
- The scenario a worker would reach the above check is when the lock
was forcibly acquired(lets say its worker died). But in this case
under convergence, even if the resource status is IN_PROGRESS we
need to act on it.

Hence removing the above check for convergence.

Change-Id: Ic17a3aa53a94b9e9ab5c841388d509b1f97103c9
2015-09-18 19:26:44 +05:30
2015-09-16 19:07:18 +01:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2015-07-08 09:13:35 -04:00
2015-04-28 16:47:07 -04:00
2015-06-23 08:30:39 +02:00
2015-08-28 14:43:37 +05:30
2015-09-03 08:45:49 +08:00
2015-09-07 21:28:44 +03:00
2015-07-15 07:33:24 +00:00
2015-09-08 09:18:36 +05:30
2012-06-23 22:41:30 -04:00

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 git@github.com:openstack/heat.git

Python client

https://github.com/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 219 MiB
Languages
Python 99.5%
Shell 0.5%