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-257) Create operation default to shell script


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

Luca Gioppo commented on TOSCA-257:
-----------------------------------

We need more elements to allow the orchestrator to have a proper interoperable behaviour.
In this moment we have an artifact that is a shell script and we could:
1) just copy it somewhere
2) execute in the orchestrator sandbox
3) execute in the node

We need some more tags to represent what to do with it and where and maybe when (whitin the same operation).

Also we need to be more prescriptive like:
artifact typeX has to be used in this way: i.e. just copy
or copu and execute
or just execute
or unzip
or untar

This way w will find out all the different tosca.artifact.implementation.something we need to have the chance to have interoperable orchestrators.
At the moment we have orchestrators defining their own type using TOSCA notation, but doing things their way and there is no chance that another orchestrator will be able to process the TOSCA file with any chance of success

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


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