-
Type:
Bug
-
Status: New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: V1.1_CSD01, V1.1_CSD02
-
Fix Version/s: None
-
Component/s: Profile-YAML
-
Labels:None
-
Proposal:
I notice that the draft of "TOSCA Simple Profile in YAML Version 1.1" is trying to define a new workflow DSL inside TOSCA instead of using existing standards such as BPMN/BPEL which is recommended in the Topology and Orchestration Specification for Cloud Applications Version 1.0[1].
Below is the description of plan(workflow) in the V1.0 Spec:
--------------------------------------------------------
planLanguage: This attribute denotes the process modeling language (or metamodel) used to specify the plan. For example, “http://www.omg.org/spec/BPMN/20100524/MODEL” would specify that BPMN 2.0 has been used to model the plan.
TOSCA does not specify a separate metamodel for defining plans. Instead, it is assumed that a process modelling language (a.k.a. metamodel) like BPEL [BPEL 2.0] or BPMN [BPMN 2.0] is used to define plans. The specification favours the use of BPMN for modelling plans.
--------------------------------------------------------
Since many open source and property orchestration implementation have already adopted TOSCA and used the BPMN/BPEL as the process modelling language, this incompatible change may force them to refactor their implementation to adapt to the new Spec, wich will definitely cost a lot of time and work. As far as I know, OPEN-O[2], Open-TOSCA[3] and some of the internal projects of ZTE will encounter this problem.
[1] http://docs.oasis-open.org/tosca/TOSCA/v1.0/TOSCA-v1.0.html
[2]http://www.open-o.org
[3]http://www.iaas.uni-stuttgart.de/OpenTOSCA/