Heat template resource porting across openstack version
Heat is being released inline with each openstack release and there are chances for resources properties and attributes might have changed and/or deprecated across these releases. Here when user create template for say Juno and want to use the same template in Kilo version, heat will fail those template.
so user may wants to port their template from lower version to higher version.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Kanagaraj Manickam
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Review
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
heat template-port --template file
Gerrit topic: https:/
Addressed by: https:/
Heat template migrate mechanism
Gerrit topic: https:/
Addressed by: https:/
Initial implementation template migrate mechanism
Addressed by: https:/
Add parameters and outputs template migrate
Addressed by: https:/
Add resource keys translation in template migrate
Addressed by: https:/
Add function migration to template migrate
Addressed by: https:/
Add migrate version to actual HOT template version
Addressed by: https:/
Add check for unsupported resource to tmpl migrate
Addressed by: https:/
[WIP] Add API call for template migrate