[OASIS Issue Tracker] (TOSCA-240) Ch 6. How are artifacts referenced from CSAR file? Automatic copy/delete?

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

    [ https://issues.oasis-open.org/browse/TOSCA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59764#comment-59764 ] 

Luca Gioppo commented on TOSCA-240:
-----------------------------------

My opinion is that we need to define various potentia behaviour.
There could be artifacts that get placed in the remote host others that stay in the orchestrator machine.

Either we think that all implementors will build a similar orchestrator or we have to leave to it the strategy of the placement we need to clearly state where the final place has to be (usually on the remote) but from the csar to the remote cannot be done just in one step.

> Ch 6. How are artifacts referenced from CSAR file? Automatic copy/delete?
> -------------------------------------------------------------------------
>
>                 Key: TOSCA-240
>                 URL: https://issues.oasis-open.org/browse/TOSCA-240
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Matthew Rutkowski 
>             Fix For: CSD03
>
>
> We can reference the CSAR file section as a first step, but do we describe the default treatment by the TOSCA orchestrator, that is is the artifact copied to the actual machine automatically?  Is it deleted after?  We added a get_artifact function to explicitly place artifacts, but in some cases is this assumed?



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