Re: [tosca-comment] RE: TOSCA workflows

Hi Adam,

We have developed something similar where we could declare arbitrary workflow fragments (including deploy and undeploy) to each node type and we are weaving these workflow fragments according to the node templates and relationships.

A+

Philippe

De: "Adam Souzis" <>
Ã: "Chris Lauwers" <>
Cc: "Philippe Merle" <>, "tosca-comment" <>
EnvoyÃ: Lundi 28 FÃvrier 2022 21:07:34
Objet: Re: [tosca-comment] RE: TOSCA workflows

Hi Phillipe,

I missed your message the first time around (thanks Chris for getting this in my inbox again). To answer your question: Unfurl supports TOSCA workflows. I extended the spec in a couple of ways:

* workflows can be imported

* workflow's âtargetâ keyword also accepts type names

Together these extensions enable workflows to be associated with node types much like interfaces, enabling them to be used to define custom workflow for "day 2" operations, like back-up and restore.

Cheers,

Adam

On Mon, Feb 28, 2022 at 11:54 AM Chris Lauwers <> wrote:

Hi Philippe, 

I'm curious about your use case for imperative workflows. We have had discussions about removing support for imperative workflows from the language and generalizing support for declarative ("automatically generated") workflows. We have also looked at supporting a more general "state/event" model where topology-wide behavior "emerges" as a result of state/event transition tables defined locally on each node and/or relationship.

Thanks,

Chris

-----Original Message-----

From:  <> On Behalf Of Philippe Merle

Sent: Sunday, February 13, 2022 6:39 AM

To: 

Subject: [tosca-comment] TOSCA workflows

Hello,

I am conducting a research work around TOSCA imperative workflows.

Could one point me to freely available TOSCA imperative workflow examples?

Which TOSCA orchestrators could execute TOSCA imperative workflows?

Thank you in advance for your replies.

Philippe Merle

Inria researcher

--

This publicly archived list offers a means to provide input to the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: 

Unsubscribe: 

List help: 

List archive: http://lists.oasis-open.org/archives/tosca-comment/

Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf

List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Committee: http://www.oasis-open.org/committees/tosca

Join OASIS: http://www.oasis-open.org/join/