Plugpoint for stack lifecycle events
A heat provider may have a need for custom code to examine stack requests prior to performing the operations to create or update a stack. Some applications may also need code to run after operations on a stack complete. The blueprint describes a mechanism whereby providers may easily add pre-operation calls from heat to their own code, which is called prior to performing the stack work, and post-operation calls which are made after a stack operation completes or fails.
Blueprint information
- Status:
- Complete
- Approver:
- Thomas Spatzier
- Priority:
- Medium
- Drafter:
- William C. Arnold
- Direction:
- Approved
- Assignee:
- William C. Arnold
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Thomas Spatzier
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
randallburt: Couldn't this be achieved by simply emitting more granular events using the standard notification mechanism?
billarnold: No. Use cases involving operations that could influence further heat template processing, e.g. validation or holistic scheduling, could not be satisfied just with more granular events. (Events could be helpful for logging or other record keeping.)
(thomas-spatzier) Updated bp since spec was merged. Set juno-3 as target since there already is code that should be able to land in time.
Gerrit topic: https:/
Addressed by: https:/
lifecycle plugin support
Addressed by: https:/
Spec for stack lifecycle plugpoint
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
