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-220) get_artifact function

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

Matthew Rutkowski  commented on TOSCA-220:

Hi Luc, I decided to adopt your proposal in whole for this function (preserving the first parameter).  This is because although we have no use cases today to have this parm., it is conceivable that the same artifact might be shared between more than one node.  In addition, people are used to the pattern of parameters from our other get_XXX APIs and so removing the first parm. also can be confusing to a person who becomes used to having there for most other APIs.


> get_artifact function
> ---------------------
>                 Key: TOSCA-220
>                 URL: https://issues.oasis-open.org/browse/TOSCA-220
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>            Reporter: Luc Boutier
>            Assignee: Luc Boutier
> Currently the specification allows to define functions like get_attribute or get_input to be used as input parameters of an operation.
> Actually we may have scenarios where we want also to provide an artifact as an input:
> Let's consider that I want to host 2 database on a single RDBMS or 2 war on a container.
> I want to define a script that is generic so it can handle an artifact based on any location (let's consider the type is file). In order to do so I expect the orchestrator to provide me the actual location of the artifact "db_content" for example. Just like attribute of a node I should be able to access it through an environment variable set by the orchestrator.
> syntax is the same as get_attribute but the value set to the environment variable is the actual artifact location.

This message was sent by Atlassian JIRA

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