[OASIS Issue Tracker] (TOSCA-250) Determine how to avoid collision of artifacts types installed into node environments

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

     [ https://issues.oasis-open.org/browse/TOSCA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-250:
-------------------------------------

        Fix Version/s: CSD04
    Affects Version/s: CSD03
                           (was: CSD04)
             Due Date: 30/Jun/15
          Component/s: Profile-YAML

> Determine how to avoid collision of artifacts types installed into node environments
> ------------------------------------------------------------------------------------
>
>                 Key: TOSCA-250
>                 URL: https://issues.oasis-open.org/browse/TOSCA-250
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Sahdev Zala 
>            Assignee: Matthew Rutkowski 
>             Fix For: CSD04
>
>
> Chapter A5.5.1
> Derek: We had a similar way to do this (i.e. hardcoded path for scripts.  Could still result in collision.  We SHOULD have a way to perhaps allow for relative paths (build upon a base path) or perhaps parameterize the path.
> Perhaps having a script context (for those that are file oriented). When you copy content, it is copied to some arbitrary location which is passed at runtime to that node.
> Make it a variable the runtime can rely upon.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)