[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:comment-tabpanel&focusedCommentId=59759#comment-59759 ] 

Luca Gioppo commented on TOSCA-250:
-----------------------------------

Should this be business of the orchestrator?
We should not rely on the actual path of the files unless are well known files (ie. "/etc/hosts") that we can work on.
The orchestrator should work in its own sandbox.
We create a folder for all the "current" template that the orchestrator is elaborating and than clear it in the end.

> 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)