Zane Bitter e37d9fab8f Corrected max secs for concurrent trans retries
This was most likely meant as a max 2s delay here, not a max 2ms
delay.

Also includes a related change: when retries for metadata updates are
attempted, make sure we do not have a stale value of the atomic_key
(otherwise we'll just inevitably hit the ConcurrentTransaction issue).

Co-Authored-By: Crag Wolfe <cwolfe@redhat.com>
Partial-Bug: #1651768
Change-Id: Ie56e0e4ff93633db1f4752859d2b2a9506922911
2017-05-04 12:32:22 -04:00
2017-03-25 17:11:50 +08:00
2017-03-25 17:11:50 +08:00
2017-01-11 20:11:49 +00: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-01-18 11:50:52 +08:00
2017-04-26 08:36:18 +00:00
2017-03-02 17:42:22 +00:00
2017-04-06 11:42:05 -07: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%