[OASIS Issue Tracker] (TOSCA-24) Plan Portability API

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

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

Frank Leymann  commented on TOSCA-24:
-------------------------------------

The draft TOSCA Plan Portability API reflects an earlier variant of version 1 of the TOSCA specification: an update of the API spec must reflect the latest work towards TOSCA version 2. Also, the current draft is very much geared towards an imperative style of processing service templates while the actual work in the TC is more focussed on a declarative style: this focus should be reflected in the API. Finally, the Simple Profile strives towards faster adoption of TOSCA by other communities, especially by Openstack. The following document should stimulate a discussion within the TC about if, when and how to revitalize work on the API:
https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/53671 

> Plan Portability API
> --------------------
>
>                 Key: TOSCA-24
>                 URL: https://issues.oasis-open.org/browse/TOSCA-24
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Spec
>            Reporter: Frank Leymann 
>            Priority: Critical
>
> Node types provide interfaces the operations of which represent its local management behavior. But our goal is to enable management of a service template "globally", i.e. to specify management actions that are composed of operations of the individual node templates (and their instances).  For this purpose an API is need that allows access to the instances of service templates, the instances of node templates and relationship templates as well as access to the service definition. Such a standardized API is need that allows to specify global management behavior in a portable manner.  In the cloud domain, APIs are typically build following the REST architectural style, i.e. this API should be a REST-based API



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)