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-36) Policies should be toplevel entities


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

Paul Lipton  commented on TOSCA-36:
-----------------------------------

A question: could simple conditions (expressions that trigger actions) also be expressed as requirements that trigger capabilities? For example, NodeType X has a condition like minimum transaction rate that triggers actions (plans)? Also, could the condition (expression) be evaluated by a process/function provided in a deploymentArtifact? Just speculating. <co-chair hat off>

> Policies should be toplevel entities
> ------------------------------------
>
>                 Key: TOSCA-36
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-36
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Derek Palma
>
> Policies are currently associated with nodes. Policies should be top level entities so they can be referenced and reused from multiple contexts.

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