Signaling and Coordination
Overview
Provide an API or signaling mechanism that will allow resources(
For example, by simply defining a depends_on relation in a HOT template, appropriate signaling should be performed at runtime so that a component A that depends on another component B is processed after component B has been configured.
What is missing/what are we trying to solve:
Currently in Heat there is a gap in configuring complex and larger software systems. For example sharing a username, password, or database dynamically at deploy time does not exist in Heat right now. It is possible to accomplish this with cfn signaling but it is messy and complex. We wish to simply this.
Blueprint information
- Status:
- Complete
- Approver:
- Steven Hardy
- Priority:
- Undefined
- Drafter:
- Jeff Sloyer
- Direction:
- Needs approval
- Assignee:
- JunJie Nan
- Definition:
- Superseded
- Series goal:
- Accepted for future
- Implementation:
- Started
- Milestone target:
- None
- Started by
- JunJie Nan
- Completed by
- Thomas Herve
Related branches
Related bugs
Sprints
Whiteboard
https:/
(shardy) Is this BP really describing a resource implementation for Marconi?
Work Items
Dependency tree
* Blueprints in grey have been implemented.