Heat template resource porting across openstack version

Registered by Kanagaraj Manickam on 2015-05-08

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

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/heat-template-port,n,z

Addressed by: https://review.openstack.org/228424
    heat template-port --template file

Gerrit topic: https://review.openstack.org/#q,topic:template-upgrade,n,z

Addressed by: https://review.openstack.org/333259
    Heat template migrate mechanism

Gerrit topic: https://review.openstack.org/#q,topic:template-migrate,n,z

Addressed by: https://review.openstack.org/370153
    Initial implementation template migrate mechanism

Addressed by: https://review.openstack.org/373373
    Add parameters and outputs template migrate

Addressed by: https://review.openstack.org/373374
    Add resource keys translation in template migrate

Addressed by: https://review.openstack.org/373375
    Add function migration to template migrate

Addressed by: https://review.openstack.org/373376
    Add migrate version to actual HOT template version

Addressed by: https://review.openstack.org/373377
    Add check for unsupported resource to tmpl migrate

Addressed by: https://review.openstack.org/374119
    [WIP] Add API call for template migrate

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.