Use Case: Sharing Nodes (e.g. a Database) between two separate (deployed) service templates

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Interop
    • None
    • Environment:

      Use case for development against TOSCA-v1.0-cs01.

    • Hide

      Diagram link: TBD
      Proposal: TBD

      Show
      Diagram link: TBD Proposal: TBD

      Desire to have one service template reference nodes or artifacts in another (already deployed) service template.

      Example:
      Sugar_eCard service template wishes to share an existing DB Node (instance) with already deployed SugarCrm service template.

      Notes:
      Aaron: High Level Suggestion: Extend TOSCA ServiceTemplate to support referencing to existing nodes.
      Derek: generic deployed component to ref. an instance already deployed, need access credentials and simply need to connect (you own it or don't own).
      Aaron: If you want to ref. an existing node, the intent was the node was owned by the same customer.
      Matt: Perhaps there is a relationship with one of Derek's use cases involving access (control) to access a DB. That is the 2nd service template would need to know/pass credentials.

      References:
      https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48504/New%20Scenarios%20for%20TOSCA%20from%20Huawei.pptxx

            Assignee:
            Aaron Zhang (Inactive)
            Reporter:
            Matthew Rutkowski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: