Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-32

Action transfer between source nodes and target nodes

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: CSD04
    • Fix Version/s: CSD04
    • Component/s: Spec
    • Labels:
      None
    • Proposal:
      Hide

      Therefore, I suggest adding a sub-element <ActionTransfers> to Relationship Type to cover all cases mentioned above.
      < ActionTransfers >?
      < ActionTransfer direction="forward|reverse|bidirectional" targetAction="anyURL" sourceAction="anyURL">+
      </ ActionTransfers >
      The ActionTransfer element has the following properties:
       targetAction: This attribute specifies the action of the target instance of a Relationship Template of this Relationship Type.
       sourceAction: This attribute specifies the action of the source instance of a Relationship Template of this Relationship Type.
       direction: If set to "forward", the targetAction of the target instance is automatically performed when the sourceAction of the source instance is performed. If set to "reverse", the sourceAction of the source instance is automatically performed when the targetAction of the target instance is performed. If set to "bidirectional", one action (either targetAction or sourceAction) is performed, another one is automatically performed.
      An example is given as follows.
      <RelationshipTypes>
      <RelationshipType id="processIntegratedWith"
      name="process is integrated with"
      semantics="www.example.com/RelSemantics/processIntegratedWith"
      >

      <RelationshipTypeProperties element="ProcessIntegratedWithProperties"/>

      < ActionTransfers >
      < ActionTransfer direction="bidirectional"
      targetAction=" www.example.com/actions/suspend "
      sourceAction=" www.example.com/actions/suspend ">
      < ActionTransfer direction="forward"
      targetAction="www.example.com/actions/deletion"
      sourceAction="www.example.com/actions/deletion ">
      </ActionTransfers >

      </RelationshipType>

      </RelationshipTypes>
      In the example, the property cascadingDeletion is described by the second <ActionTransfer> element.

      Show
      Therefore, I suggest adding a sub-element <ActionTransfers> to Relationship Type to cover all cases mentioned above. < ActionTransfers >? < ActionTransfer direction="forward|reverse|bidirectional" targetAction="anyURL" sourceAction="anyURL">+ </ ActionTransfers > The ActionTransfer element has the following properties:  targetAction: This attribute specifies the action of the target instance of a Relationship Template of this Relationship Type.  sourceAction: This attribute specifies the action of the source instance of a Relationship Template of this Relationship Type.  direction: If set to "forward", the targetAction of the target instance is automatically performed when the sourceAction of the source instance is performed. If set to "reverse", the sourceAction of the source instance is automatically performed when the targetAction of the target instance is performed. If set to "bidirectional", one action (either targetAction or sourceAction) is performed, another one is automatically performed. An example is given as follows. <RelationshipTypes> <RelationshipType id="processIntegratedWith" name="process is integrated with" semantics="www.example.com/RelSemantics/processIntegratedWith" > <RelationshipTypeProperties element="ProcessIntegratedWithProperties"/> < ActionTransfers > < ActionTransfer direction="bidirectional" targetAction=" www.example.com/actions/suspend " sourceAction=" www.example.com/actions/suspend "> < ActionTransfer direction="forward" targetAction="www.example.com/actions/deletion" sourceAction="www.example.com/actions/deletion "> </ActionTransfers > </RelationshipType> </RelationshipTypes> In the example, the property cascadingDeletion is described by the second <ActionTransfer> element.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              PaulZhang Paul Zhang
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: