[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-115) Requirements Capabilities to provide interfaces
[ http://tools.oasis-open.org/issues/browse/TOSCA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33735#action_33735 ]
Thomas Spatzier commented on TOSCA-115:
----------------------------------------
So on the duplicate hierarchies of NodeTypes vs. Req/Cap types, I agree: we have to sort out how we design the typing system and not have too many redundant types. Recent discussions in the SC seemed to be going in a direction that Req/Cap types are the more important thing. I am all open for this discussion.
Regarding the question where interfaces get defined, I still have to make up my mind. I think we should allocate some time to talk, either in the TC or SC or in a small group of interested folks.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]