OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (TOSCA-244) Need to add clarity around orchestrator's copy behavior for script


Sahdev Zala  created TOSCA-244:
----------------------------------

             Summary: Need to add clarity around orchestrator's copy behavior for script
                 Key: TOSCA-244
                 URL: https://issues.oasis-open.org/browse/TOSCA-244
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Task
            Reporter: Sahdev Zala 
             Fix For: CSD04


Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting:

(Luc) : 
Default behavior: Assumed that orchestrators execute relative to the CSAR and removes on completion.

Now that we have get_artifact() function which allows template author to control placement and persistence of an artifact if they want to control it directly.

Luc: Perhaps we do not want to copy on every compute node if for example we have 5 compute nodes.  

Note: orchestrators should only copy artifacts for that node to that compute not all artifacts to all nodes.
(keep wordpress scripts on its compute and mysql on its compute).

Needs to reference the 'hosting' (or containment) hirarachy. 



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]