AutoScalingTest has issues with timing and memory reporting values

[Steve Baker]

AutoScalingTest has issues which will require rethinking how this test is implemented, including:
- the optimal ConsumeStopSeconds will depend on the overhead of boot time, which varies greatly between bare metal and virt-on-virt
- every combination of distro/release/flavor will result in a different baseline memory usage, making it difficult to determine the ScaleDownThreshold to set

I recommend that this test be skipped until other tests in heat-slow are passing in gate during check experimental, then it can be implemented as a more robust scenario.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/59887

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/59887
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=ace4e6d3b0b1d29cdf21a7ad73e0780ef1066e7d
Submitter: Jenkins
Branch: master

commit ace4e6d3b0b1d29cdf21a7ad73e0780ef1066e7d
Author: Steve Baker <email address hidden>
Date: Wed Dec 4 15:56:45 2013 +1300

    Skip autoscaling test until more reliable

    AutoScalingTest has issues which will require rethinking how
    this test is implemented, including:
    - the optimal ConsumeStopSeconds will depend on the overhead
      of boot time, which varies greatly between bare metal and
      virt-on-virt
    - every combination of distro/release/flavor will result in a
      different baseline memory usage, making it difficult to
      determine the ScaleDownThreshold to set

    This change skips this test and tracks against the bug:
    Partial-Bug: #1257575

    Change-Id: I0695a7efacdbeab39c895a97cb45496fcaf97e35

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve Baker (<email address hidden>) on branch: master
Review: https://review.openstack.org/44967
Reason: moving to heat functional test

[Yaroslav Lobankov (ylobankov)]

This test was moved from Tempest to Heat functional tests. Moreover, Tempest doesn't have any Heat scenario tests now. Marking this bug as "Invalid".