c89a17bfe3
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 |
||
---|---|---|
.. | ||
aws | ||
openstack | ||
__init__.py | ||
alarm_base.py | ||
scheduler_hints.py | ||
server_base.py | ||
signal_responder.py | ||
stack_resource.py | ||
stack_user.py | ||
template_resource.py | ||
volume_base.py | ||
wait_condition.py |