OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

 View Only

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

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

    Posted 06-20-2019 03:16
    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 ???? : 2019 ? 6 ? 18 ? 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