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] Custom Declarative workflows


Hi Priya,

 

  1. Let me see if I understood: A possibility that I describe in the proposal is to have is to have âworkflow_typesâ, which we can have like node_types, or datatypes in a declaration specification. Then in the substitution template we can just derive from that, i.e. you donât need to connect that workflow to a node type, then they can be used by any kind of nodes/substitution templates. Just like a datatype.  
  2. We could describe definitions under a ââ steps: declarative_step: â â, keyword, but it will be a little unnecessary, since it will only ever be one step defined in the steps.
  3. TARGET_TO_SOURCE makes sense

 

BR,

/Calin

 

From: <tosca@lists.oasis-open.org> on behalf of Priya T G <priya.g@netcracker.com>
Date: Tuesday, 15 October 2019 at 10:36
To: Calin Curescu <calin.curescu@ericsson.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] Custom Declarative workflows

 

Hi Calin,

 

Thank you for the proposal on custom declarative workflows, I missed the discussions last week on this topic.

Not sure if we are still debating on the need for custom declarative workflows or if  we have deep dived in to the proposal.

We very much support the idea, a few comments/suggestions regarding the proposed approach:

 

 

  1. Can we add the possibility to describe this workflow not only in topology_template->workflows section, but also under node type:

 

node_types:

   tosca.nodes.nfv.NS:

      derived_from: ...

      workflows:

         instantiate:

           description: custom declarative workflow that performs the entire startup sequence

           workflow_type: declarative

           node_types: [tosca.nodes.Root]

           follow_relationships: [tosca.relationships.Root]

           direction: target-to-source

           ....          

 

  topology_template:

  substitution_mappings:

        node_type: tosca.nodes.nfv.NS

 

 

This enables the topology template that substitutes this node type to derive this workflow.

 

 

 

2. Can we describe activities under a step definition instead of directly describing them under workflow definition, as highlighted in the snippet below:  

 

 

workflows:

  startup:

    description: custom declarative workflow that performs the entire startup sequence

    workflow_type: declarative

    node_types: [tosca.nodes.Root]

    follow_relationships: [tosca.relationships.Root]

    direction: target-to-source

    steps:

       declarative_step:

           activities:

               ....

 

 

3. An observation: To align with TOSCA approach, it is more appropriate to describe

direction: target-to-source 

 

as

 

direction: TARGET_TO_SOURCE

 

Regards,

Priya

 

 

From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Chris Lauwers
Sent: Tuesday, October 15, 2019 10:57 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] Agenda for 10/15/19 Language Ad-Hoc Meeting

 

[External Email]


 

  • Discuss feedback on Calinâs âdeclarative workflowâ proposal
  • Language support for âmultiple instancesâ
    • Scaling of nodes
    • Creating multiple node instances from the same node template
    • Multiple requirements

 

Chris

 


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.  



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