Support versioned resource implementations
Registered by
Randall Burt
Resources should be versioned to help users determine the portability of their templates across various providers. Heat should also allow for running multiple versions of the same resource in a given installation. The HOT syntax should be extended to allow the user to specify a specific desired version of a resource. If no version is specified, Heat should select the latest supported version of the resource.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Randall Burt
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Randall are you going to raise this as a spec?
RB-20150219: I had not planned on creating a spec until we were farther along on the road to v2. Its not a huge priority afaik.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
