Re: [tosca] Groups - TOSCA Imperative Workflows supporting custom workfl

Hi Priya,

I think that the best way to solve this problem, that already works with TOSCA v1.3 specification is to use an imperative workflow, where the input is received from the outside and in its only step uses the âinlineâ activity to inline an external (i.e. Mistral) workflow. The inline activity should have the new form we introduced in v1.3 where we provide inputs to the called workflow. Since it is inside the pther workflow, both the inputs from outside and inputs that are taken from the nodes can be freely mixed.

For example the following snippet:

workflows:

wf2_external_mistral:

inputs:

wf2in1:

type: string

wf2in2:

type: string

outputs:

wf2out:

type: string

wf1_called_from_outside_api:

inputs:

wf1in1:

type: string

wf1in2:

type: string

steps:

main:

target: vnfNode

activities:

- inline:

workflow: wf2

inputs:

wf2in1: { get_input: wf1in1}

wf2in2: { get_property: [ vnfNode, property1 ] }

BR,

/Calin

From: <tosca@lists.oasis-open.org> on behalf of Priya TG <priya.g@netcracker.com>
Date: Monday, 1 July 2019 at 13:39
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] Groups - TOSCA Imperative Workflows supporting custom workflow language uploaded

Submitter's message
Revision highlighting an example from ETSI NFV illustrating the need for passing parameters from service template to scripts.
-- Ms. Priya TG

Document Name: TOSCA Imperative Workflows supporting custom workflow language

Description
This contribution attempts to highlight the gaps in current v1.3 grammar of
TOSCA Imperative workflows supporting custom workflow language.
Download Latest Revision
Public Download Link

Submitter: Ms. Priya TG
Group: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
Folder: Working Documents
Date submitted: 2019-07-01 04:38:25
Revision: 1

tosca message