[OASIS Issue Tracker] Commented: (TOSCA-32) Action transfer between source nodes and target nodes

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/TOSCA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30825#action_30825 ] 

Derek Palma commented on TOSCA-32:
----------------------------------

This kind of action flow conflicts with the original design in that such semantics can already be expressed declaratively with RelationshipTypes or imperatively with plans. The uses cases described are very common and multiple implementations have already been able to support them declaratively using the semantic expressiveness of relationships. The original design sought to separate declarative and imperative semantics to avoid many challenging complexities. This proposal combines them. Is there any reason you can't express the semantics using the existing mechanisms? Maybe we just need to clarify the intended usage.

Also, cascadingDelete is removed in an upcoming proposal since lifecycle scoping and dependencies can be inferred from the node model or handled imperatively in plans.

> Action transfer between source nodes and target nodes
> -----------------------------------------------------
>
>                 Key: TOSCA-32
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-32
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>            Reporter: Paul Zhang
>
> cascadingDeletion is used to indicate that if the target instance is deleted automatically with the deletion of the source instance. 
> There may be some other cases that one action of the target instance leads to one action of the source instance, where the actions may be not restricted to the deletion action. For example, two Node Templates describing an AppServer and a DBServer are associated by a Relationship Template with the relationship type "Integrated with", where the DBServer is the target node and the AppServer is the source node. Developers may want to indicate in Relationship Type that the DBServer is suspended automatically when the AppServer is suspended. Furthermore, in some cases, suspending a target instance can also lead to the action of suspending the source instance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira