Zane Bitter c85cae58bf Fix test_update_restricted timeouts due to timestamp resolution
Updating a stack where the only resource needs replacement but is
restricted from being replaced is *very* fast. Since the test framework
relies on seeing a change in the updated_time timestamp, which has only 1s
resolution, it can easily be missed causing the test to timeout. This adds
a 1s sleep between updates that have the same expected status to ensure
that the timestamp changes.

Change-Id: Ief845a21108e925325b1b3e8f090038ccdf73b8e
Closes-Bug: #1554375
Related-Bug: #1583630
2016-06-14 18:39:51 +00:00
2016-05-16 07:38:46 +00:00
2016-05-17 23:57:43 +08:00
2016-05-27 13:55:55 +08: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-06-23 08:30:39 +02:00
2015-09-22 10:40:48 +00:00
2016-06-07 17:31:20 +00:00
2016-01-17 05:20:40 +00: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 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 216 MiB
Languages
Python 99.5%
Shell 0.5%