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] Commented: (TOSCA-14) Policy Language(s)


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

Derek Palma commented on TOSCA-14:
----------------------------------

Even with a policy language agnostic approach, it seems we would need to do the following:
Support Packaging and referencing of arbitrary policy types in a TOSCA service template. (Making policies root objects will make this easier, avoiding the need to search the entire document for all policies which may be applicable in specific contexts.)
Ensure that a policy processor can efficiently determine the TOSCA entities a policy should be applied to (targeting) and access the necessary entity values (state evaluation)
Ensure that policy semantics are preserved across a well defined set of Service Template edits/transformations. I.e. a policy that applies to all EJBs should still behave correctly if new EJBs are added or existing ones removed.

Although our objective is to be policy language agnostics, we should select a few policy languages as use cases to design and assess the Service Template expressiveness.


> Policy Language(s)
> ------------------
>
>                 Key: TOSCA-14
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-14
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Sub-task
>          Components: Spec
>            Reporter: Frank Leymann 
>
> During review of the proposal to resolve issue TOSCA-3 a discussion about policy languages came up. See the following meeting notices:
> http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45574 
> Some TC members felt that a strong tie to WS-Policy is not appropriate. There are other approaches to define policies that are relevant for particular domains. Thus, this sub-task should review such other approaches and propose how to define policies in TOSCA.  Alternatives might be (i) to support multiple approaches, or (ii) to invent a new TOSCA policy language that abstracts the policy approaches considered to be relevant for TOSCA.

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