Bug 1042159

Summary: [RFE][heat]: Provide translation layer for TOSCA Service Template to Heat native DSL
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/tosca-support
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:53:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:14:09 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/tosca-support.

Description:

Heat orchestration is currently based on AWS CloudFormation (CFN) templates, but work is in progress to define a neutral, native Heat Template format / DSL [1] that over time will become only format processed by the core Heat engine. Definition of this DSL is currently driven at [2]; more links are also provided in [1].
It is envisioned that this DSL [1] will be designed in a way that other formats such as TOSCA can be mapped to it, so translation modules can be implemented to translate from other formats into the native DSL. A corresponding future architecture for Heat is currently being discussed at [3].

The current BP proposed to build a translation tool to translate from TOSCA to native Heat DSL so TOSCA templates can be deployed on OpenStack Heat. This translator can be built as an add-on component outside core Heat intially. Later on, a pluggable translation layer could be built more closely into Heat and the TOSCA translation component could be refactored as a module into that pluggable layer.

This BP has BP [1] as a pre-req.

[1] https://blueprints.launchpad.net/heat/+spec/open-api-dsl
[2] https://wiki.openstack.org/wiki/Heat/DSL
[3] https://wiki.openstack.org/wiki/Heat/Vision

Specification URL (additional information):

None