Hi Tal,
Your proposal could be interesting when one wants to use TOSCA to <<program>> business workflows but I don't see how this could be useful to program topology management workflows (like deploy, undeploy, backup, etc.).
A+
Philippe
De: "Tal Liron" <>
Ã: "Philippe Merle" <>
Cc: "Adam Souzis" <>, "Chris Lauwers" <>, "tosca-comment" <>
EnvoyÃ: Mardi 1 Mars 2022 02:13:07
Objet: Re: [tosca-comment] RE: TOSCA workflows
Philippe (and others),
Have you considered creating imperative workflows using TOSCA node templates and types? Each template could be a "task" on the workflow DAG, and could have special relationships to "actual" node templates on which they work. In short they would be very well integrated with TOSCA. You would essentially have an importable TOSCA profile just for DAGs, and you could then have various tools (workflow engines) to execute them. (Or they can inherit the basic types and add implement-specific properties for implementation-specific features.)
I've done some work on this. If there's interest we could possibly arrange a "TOSCA hackathon" or similar where we try to build a profile like this together. I'm confident it's better than having specialized grammar for it in TOSCA. DAGs are, of course, graphs and easy to represent in TOSCA.
On Mon, Feb 28, 2022 at 2:52 PM Philippe Merle <> wrote:
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/
