This page is intended to establish shows how the Policy Design and API Flow to/from the PAP and PDP's will work to support Model Driven Control Loops in Dublin.

...

1 Policy Type Design

TOSCA defines a PolicyType as an artifact that "defines a type of requirement that affects or governs an application or service’s topology at  some stage of its lifecycle, but is not explicitly part of the topology itself". In the definition of a PolicyType in TOSCA, one specifies:

• its properties, which define the configuration parameters that the policy takes
• its targets, which define the node types and/or groups to which the policy type applies
• its triggers, which specify the conditions in which policies of this type are fired

During Model Design, a Policy Model and a Policy Model Parameter Schema is created. The Policy Model contains the definition of the policy together with its inputs and outputs, rules and logic. This model may be expressed in XACML, as Drools rules, or as an APEX model definition. The Policy Model Parameter Schema is a TOSCA definition of the parameters that a Policy Model must receive in order for it to be transformed into a policy. The schemas will ultimately be defined by the modeling team but for now are defined by the Policy Framework project.

...