heat/heat/engine/resources/aws
rabi c89a17bfe3 Refactor CooldownMixin
The present way of comparing timestamp in metadata
+ cooldown with current timestamp can be wrong, if
the policy cooldown is updated in between scaling
activity.

Set metadata with the expected cooldown end timestmap
rather than the current timestamp when scaling is finished
and compare it with current timestamp.

Change-Id: I50ddba4c8da3c6ec8b34ebb4768017cb1a446f5f
2017-11-17 17:21:09 +05:30
..
autoscaling Refactor CooldownMixin 2017-11-17 17:21:09 +05:30
cfn Avoid creating two Stacks when loading Resource 2017-07-21 10:44:51 -04:00
ec2 Fix python-novaclient 8.0.0 related issues 2017-05-16 16:12:04 +02:00
iam Remove log translations 2017-03-25 17:11:50 +08:00
lb Remove log translations 2017-03-25 17:11:50 +08:00
s3 Sync context with oslo.context 2016-06-17 11:46:00 +10:00
__init__.py Split scaling policy into separate files 2014-08-27 20:27:19 +08:00