Move non-heat resources into a new heat stack
Following are couple of use cases that this blueprint could solve;
1. Transitioning from non-heat orchestration system to heat
2. Moving resources that were created manually into a heat stack by creating a matching template
3. During the deployment re-use one or more existing resources(resources that were created manually or using some automation scripts etc...) instead of creating all new resources
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- Vijendar Komalla
- Direction:
- Approved
- Assignee:
- Vijendar Komalla
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Vijendar Komalla
- Completed by
- Vijendar Komalla
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Move non-heat resources into a new heat stack
Addressed by: https:/
Move non-heat resources into a new heat stack
Addressed by: https:/
Move non-heat resources into a new heat stack
24Jan2014:
Marking this blueprint as completed, because use cases described in this blueprint were implemented as part of stack-adopt and stack-convergence.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
