OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

 View Only
Back to discussions
Expand all | Collapse all

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

  • 1.  [OASIS Issue Tracker] (TOSCA-257) Create operation default to shell script

    Posted 06-11-2015 14:41
    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)


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

    Posted 06-16-2015 21:46
    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


Related Content