[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: TOSCA workflows
Thanks Philippe. This approach could have value for Version 1.3, but would no longer work for Version 2.0 where TOSCA no longer defines any normative types. Because of this:
To deal with these issues, we have explored the following:
What needs to be investigated further is how interface operations on relationships interweave with interface operations on nodes. We need language support for defining this as well. Thanks, Chris From: Philippe Merle <philippe.merle@univ-lille.fr> Hi Chris,
To validate this tool, we are currently generating both correct and incorrect imperative workflows automatically. But to go a step beyond, we are searching concrete imperative workflows.
This will be a big feature removal! But the removal could be justify if no TOSCA orchestrator implements imperative workflows. > generalizing support for declarative ("automatically generated") workflows. We are developing a generator to automatically generate imperative workflows from a topology template. > 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. In our approach, we are defining a finite state machine where transitions are labelled by workflow activities (e.g. set_state: created, call_operation: Standard.create).
A+ Philippe Merle De:
"Chris Lauwers" <lauwers@ubicity.com> Hi Philippe,
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]