RE: [tosca] [OASIS Issue Tracker] (TOSCA-257) Create operation default to shell script

[Chris Lauwers <lauwers@ubicity.com>]

Hi Luca,

I'm not sure that a "default" of shell script is assumed. In my opinion, the orchestrator should determine the proper way to use an artifact based on the type of that artifact. For example, if the artifact is a chef recipe or cookbook, the orchestrator could use this by running chef client on the node. 

The issue therefore isn't that "default" behavior is assumed, but rather that we haven't defined types for all the possible artifacts that may need to be supported.

Chris


-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Thursday, June 11, 2015 7:41 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] [OASIS Issue Tracker] (TOSCA-257) Create operation default to shell script

Luca Gioppo created TOSCA-257:
---------------------------------

             Summary: Create operation default to shell script
                 Key: TOSCA-257
                 URL: https://issues.oasis-open.org/browse/TOSCA-257
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
          Components: Profile-YAML
            Reporter: Luca Gioppo


It seems that the "create" operation defaults to a shell script (that is from the examples we only use shell scripts) and there is no way to specify the type of "create" behaviour we want to apply.
Is not proposable in an echosystem of DevOps not considering the need to "create" using puppet and the orchestrator should not live on bash script also.



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

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php