[OASIS Issue Tracker] Issue Comment Edited: (TOSCA-36) Policies should be toplevel entities

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

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

Efraim Moscovich  edited comment on TOSCA-36 at 7/19/12 9:56 PM:
-----------------------------------------------------------------

I agree. 
In addition, a policy should define conditions (expressions that trigger actions) and actions (that could invoke plans).


      was (Author: efraim):
    Per latest doc (TOSCA-v1.0-wd09), plans are defined at the ServiceTemplate level:
<ServiceTemplate id="ID"
                  name="string"?
                  targetNamespace="anyURI"> 
	
   <Extensions>?
	 <Extension namespace="anyURI" 
	            mustUnderstand="yes|no"?/>+   
	 </Extensions>
...	

   <NodeTypes>?
	         ...
	 </NodeTypes>
	
	 <RelationshipTypes>?
	         ...
	 </RelationshipTypes>
	
	 <Plans>?
	         ...
	 </Plans>
	
</ServiceTemplate>
-----
They are discussed in the context of nodes, but they could be referenced from other entities as well if there are good use cases.

  
> 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