Jump to: navigation, search

Heat/Blueprints/alarm-triggers-update

< Heat
Revision as of 23:38, 7 February 2013 by Asalkeld (talk)
  • Launchpad Entry: HeatSpec:update-on-alarm-action
  • Created: 08 Feb 2013
  • Contributors:

Summary

To make templates more powerful (like what the loadbalancer resource does internally) we need to automatically trigger a stackupdate after a cloudwatch alarm action (one that causes changes to the stack).

The idea is that anything that might cause a change in a Ref() or GetAttr() will cause an update and therefore you could run hook scripts on your instance.

This is similar to juju signals (I believe).

Release Note

Rationale

User stories

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarizing what was discussed and note any options that were rejected.