Comment 14 for bug 1474332

Reviewed: https://review.fuel-infra.org/9897
Submitter: Vitaly Sedelnik <email address hidden>
Branch: openstack-ci/fuel-5.1-updates/2014.1.1

Commit: 8b90f6c853edda18f24a220358191b18b7464e14
Author: yanyanhu <email address hidden>
Date: Mon Jul 27 21:30:33 2015

ASG scaling account for cooldown timestamp & in-progress

There are cases where it takes a long time to create a new resource as
requested by the scaling operation on an ASG resource, for instance, a
nova server creation followed by a complex SoftwareDeployment. During
this process, additional alarms may come in but failed to be blocked
by the current cooldown checking mechanism because the very first
timestamp has yet to be generated. This is leading to unexpected size
adjustment to the ASG.

This patch augments the existing cooldown checking mechanism with a
scaling-in-progress test so that additional alarms arriving during
the very first scaling operation will be ignored.

Closes-Bug: #1474332
Co-Authored-By: yanyanhu <email address hidden>

Conflicts:
 heat/engine/resources/openstack/heat/scaling_policy.py
 heat/scaling/cooldown.py
 heat/tests/autoscaling/test_heat_scaling_group.py
 heat/tests/autoscaling/test_heat_scaling_policy.py
 heat/tests/autoscaling/test_scaling_group.py
 heat/tests/autoscaling/test_scaling_policy.py

(cherry-picked from Ib8aa83eed366df7097c9cbb9247eca866ae4b620)
Change-Id: Ib8aa83eed366df7097c9cbb9247eca866ae4b620