[OASIS Issue Tracker] Commented: (TOSCA-115) Requirements Capabilities to provide interfaces

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/TOSCA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33621#action_33621 ] 

Frank Leymann  commented on TOSCA-115:
--------------------------------------

To help me understanding the issue:

Different interfaces would be supported by different node types extending more abstract node types.  E.g. a DB2 Node Type or a MySQL Node Type would inherit from the RDBMS Node Type, adding specifics of the vendors' implementations.

Furthermore, we support different Node Type Implementations for one and the same Node Type. E.g. we can create a DB2zOS Node Type Implementation and a DB2Linux Node Type Implementation of the DB2 Node Type. The Node Type Implementations will provide artifacts that are environment specific (i.e. specific to zOS or specific to Linux).  

But the DB2 Node Type may support the DBServer requirement.  If the requirements need to be refined you inherit from the DBServer requirement. 

Is this going towards the direction you have in mind?

> Requirements Capabilities to provide interfaces
> -----------------------------------------------
>
>                 Key: TOSCA-115
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-115
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>    Affects Versions: V1.1_CSD01
>            Reporter: Kevin Wilson
>
> Requirements and capabilities should provide specific interface definitions. So that the designer of a app can depend on a contract set of public properties that are to be provided and a contracted set method/interfaces that are provided by the requirement. 
> For example:
> If I have a dependency on a DB Server, and need to run SQL on that server, at design time, I would like to know the methods supported by the DBServer requirement so that I can leverage that in my component scripting. 
> On the implementation side providing the component, the script/method to execute the script may be different for each DBServer type. IE commands to run SQL on MySQL are not the same commands that would be used for Oracle. However, the SQL may the same in some cases. 
> Similar methods/use cases exist for J2EE server deploy methods etc. 
> By providing a interface on the Requirement/Capability we can leverage the workflows specific to the capability in a generic way. And the designer would be able to identify the contracted calls that are made available. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira