OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [tosca] Groups - Example of Imperative Workflows supporting custom workflow language uploaded


Shitao,

 

Apologies for the delay. As promised, find attached a write-up that elaborates the problem statement and also outlines the possible approaches for addressing the issue as discussed in simple profile meeting.

 

Regards,

Priya


From: Lishitao <lishitao@huawei.com>
Sent: Wednesday, June 19, 2019 11:16:02 PM
To: Priya T G; tosca@lists.oasis-open.org
Subject: RE: [tosca] Groups - Example of Imperative Workflows supporting custom workflow language uploaded

 

Hi Priya and all

 

I think the issue you want to solve is related to this example in clause 6.7.1.5 of SOL001, that the script_input_1 and script_input_2 are used as the input parameters to the instantiate-script in the implementation.

 

topology_template:

substitution_mappings:

  node_type: MyCompany.SunshineDB.1_0.1_0

  ..

 

node_templates:

  SunshineDB:

   type: MyCompany.SunshineDB.1_0.1_0

   ..

  interfaces:

   Vnflcm:

    instantiate:

     implementation: instantiate-script

     inputs:

      script_input_1: value_1

      script_input_2: value_2

  artifacts:

   instantiate-script:

    description: Instantiate workflow script

    type: tosca.artifacts.Implementation.Python

    file: instantiate.py

    #repository: ..

    #deploy_path: ..

    ..

 

So my question is that is the above example correct from TOSCA grammar perspective, if it is correct, can we follow the similar way to describe the input for the implementation in a workflow?

 

Regards

shitao

发件人: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] 代表 Priya TG
发送时间: 2019618 19:40
收件人: tosca@lists.oasis-open.org
主题: [tosca] Groups - Example of Imperative Workflows supporting custom workflow language uploaded

 

Document Name: Example of Imperative Workflows supporting custom workflow language


Description
Example of 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-06-18 04:39:21

 

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
 

Attachment: TOSCA Imperative workflows.docx
Description: TOSCA Imperative workflows.docx



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]