metadata is cached so if runtime data changes the instance doesn't see it

[Angus Salkeld]

If you use the Restarter resource and and in you second instance have GetAtt("publicIp")
you will never see the change in ip, as it is cached in the db.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/22805
Committed: http://github.com/openstack/heat/commit/06f4f858715f89100644867a1aad95bdb3352e41
Submitter: Jenkins
Branch: master

commit 06f4f858715f89100644867a1aad95bdb3352e41
Author: Angus Salkeld <email address hidden>
Date: Tue Feb 26 09:16:12 2013 +1100

    Make the alarm actions run in one thread

    bug #1131024
    Change-Id: I678d8919a17fc73350ec9061ad2a7234e1d6b9f6

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/22513
Committed: http://github.com/openstack/heat/commit/cca4de0c855f7224902900a0489df322e09a5bf5
Submitter: Jenkins
Branch: master

commit cca4de0c855f7224902900a0489df322e09a5bf5
Author: Angus Salkeld <email address hidden>
Date: Mon Feb 25 11:44:19 2013 +1100

    Update the metadata if an alarm action makes changes

    The point of this change?
    - You have another instances' ip in your metadata and if it
      gets restarted you want cfn-hup to see the new ip.

    How is it achieved?
    - poll for the metadata so you can see these changes (cfn-hup)
    - when ever an alarm action is run we make sure the metadata is refreshed.

    bug #1131024
    Change-Id: I0798c4da9689b126c3c98cafa63138ff2c484ea9