Jump to: navigation, search

Difference between revisions of "Policy Framework in STP"

Line 17: Line 17:
  
 
=== Policy Dependency ===
 
=== Policy Dependency ===
Define dependencies between policies.  
+
Define dependencies relationship between policies.  
 +
Example:
 +
<validation>
 +
  <rule>
 +
    <dependency policy_id = "policy A">
 +
      <on policy_id="policy B", version="2.0"/>
 +
      <on policy_id="policy C"/>
 +
    </dependency>
 +
  </rule>
 +
</validation>
 
=== Policy Conflict ===
 
=== Policy Conflict ===
 +
Define conflict relationship between policies
 +
Example:
 +
<validation>
 +
  <rule>
 +
    <conflict policy_id = "policy A">
 +
            <with policy_id="policy D", version="2.0" />
 +
            <with policy_id="policy E" />
 +
    </conflict>
 +
  </rule>
 +
</validation>
 +
 +
 
=== Policy Subject Constraints ===
 
=== Policy Subject Constraints ===
=== eclipse.emf.validation ===
+
Define the subject set with the policy may apply
=== rule based xml validator in stp ===
+
Example:"
 +
<validation>
 +
  <rule>
 +
    <!-- policy A can apply to both endpoint and message -->
 +
    <subjects policy_id = "policy A">
 +
            <subject>endpoint</subject>
 +
            <subject>message</subject>
 +
    </subjects>
 +
  </rule>
 +
  <rule>
 +
    <!-- policy B can only apply to message -->
 +
    <subjects policy_id = "policy B">
 +
            <subject>message</subject>
 +
    </subjects>
 +
  </rule>
 +
</validation>
 +
 
 +
 
 +
=== Policy Validation Engine Implementation ===
 +
Need to write a engine to support the about validation rules. When user add a policy, we will call the engine
 +
to do the validating, the give meaningful error message if any.
 +
 
 +
==== eclipse.emf.validation ====
 +
Need to looking into the emf.validation to see if we can use use it here.
 +
User defines the validation rules from GUI. How to translate those rules to emf validator class
 +
on the fly is a problem in that case.
 +
 
 +
==== rule based xml validator in stp ====
 +
Alternative, we may think about extend the current rule based xml validator for policy validation engine here.
 +
?
  
 
== Policy Association ==
 
== Policy Association ==

Revision as of 01:53, 26 September 2007

This wiki is used as a starting point to kick off the discuss of Policy support in STP. Johnson Ma

Introduction

Use Cases

Design Map =

Policy Registry

Policy Creation

Policy Editor

Policy Validation

The policy validation framework is used to define a validation mechanism when applying ws-policy. Policy is created by policy editor. We will write provide a policy validation rule editor for user to dynamic add/remove validation rules as well.

The validation rules will cover following category:

Policy Dependency

Define dependencies relationship between policies. Example:

<validation>
  <rule>
    <dependency policy_id = "policy A">
      <on policy_id="policy B", version="2.0"/>
      <on policy_id="policy C"/>
    </dependency>
  </rule>
</validation>

Policy Conflict

Define conflict relationship between policies Example:

<validation>
  <rule>
    <conflict policy_id = "policy A">
           <with policy_id="policy D", version="2.0" />
           <with policy_id="policy E" />
    </conflict>
  </rule>
</validation>


Policy Subject Constraints

Define the subject set with the policy may apply Example:"

<validation>
  <rule>
    <subjects policy_id = "policy A">
           <subject>endpoint</subject>
           <subject>message</subject>
    </subjects>
  </rule>
  <rule>
    <subjects policy_id = "policy B">
           <subject>message</subject>
    </subjects>
  </rule>
</validation>


Policy Validation Engine Implementation

Need to write a engine to support the about validation rules. When user add a policy, we will call the engine to do the validating, the give meaningful error message if any.

eclipse.emf.validation

Need to looking into the emf.validation to see if we can use use it here. User defines the validation rules from GUI. How to translate those rules to emf validator class on the fly is a problem in that case.

rule based xml validator in stp

Alternative, we may think about extend the current rule based xml validator for policy validation engine here. ?

Policy Association

Screenshots

User Roles

 *Policy Developer -- write policies for projects, company or domain
 *Service Developer -- write policy, config and apply existing policy to service component.
 *Deployment Assembler -- apply policies to services during deployment
 *Operator -- dynamic config/modify policy at runtime. 

Runtime support

Example