...
The TOSCA Policy artifact is used internally by the Policy Framework, or is input by CLAMP or other systems. This artifact specifies the values of the properties for the policy and specifies the specific entities the policy acts on. Policy Design uses the TOSC Policy artifact and the PolicyTypeImpl artifact to create an executable PolicyImpl artifact.
1 Policy
...
Types
Policy Type Design manages TOSCA PolicyType artifacts and their PolicyTypeImpl implementations.
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 TOSCA PolicyType may ultimately be defined by the modeling team but for now are defined by the Policy Framework project.
In order to define a policy, Policy Parameters must be passed to Policy Design as a Yaml document. The structure of the Policy Parameters Yaml document must comply with the structure defined in the Policy Model Parameter Schema for the Policy model being used for policy design.
Various editors and GUIs are available for creating PolicyTypeImpl implementations. However, systematic integration of PolicyTypeImpl implementation is outside the scope of the ONAP Dublin release.
The PolicyType definitions and implementations listed below Certain Policy Models are preloaded and are always available for use in the Policy Framework.
| Policy ModelType | Description |
|---|---|
| onap.policies.Monitoring | Overarching model that supports Policy driven DCAE microservice components used in a Control Loops |
| onap.policies.controlloop.Operational | Used to support actor/action operational policies for control loops |
| onap.policies.controlloop.Guard | Control Loop guard policies for policing control loops |
| onap.policies.controlloop.Coordination | Control Loop Coordination policies to assist in coordinating multiple control loops at runtime |
onap.policies.Monitoring model
Overarching model policy type that supports Policy driven DCAE microservice components used in a Control Loops. The implementation that supports this model will be developed using XACML PDP to support question/answer Policy Decisions during runtime for the DCAE Policy Handler. The implementation of this Model will be used to support dynamically generated DCAE microservice component Policy Models Types created during Design Time using TOSCA-Lab within SDC.
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
tosca_definitions_version: tosca_simple_yaml_1_0_0
policy_types:
onap.policies.controlloop.Guard:
derived_from: tosca.policies.Root
description: Guard Policies for Control Loop Operational Policies
onap.policy.controlloop.guard.blacklist:
derived_from: onap.policies.controlloop.Guard
description: Supports blacklist of VNF's from performing control loop actions on.
properties:
blacklist_policy:
type: map
description:
entry_schema:
type: onap.datatypes.guard.blacklist
data_types:
onap.datatypes.guard.blacklist:
derived_from: tosca.datatypes.Root
properties:https://wiki.onap.org/display/DW/Policy+Types
actor:
type: string
description: Specifies the Actor
required: true
recipe:
type: string
description: Specified the Recipe
required: true
time_range:
type: tosca.datatypes.TimeInterval
description: An optional range of time during the day the blacklist is valid for.
required: false
controlLoopName:
type: string
description: An optional specific control loop to apply this guard to.
required: false
blacklist:
type: list
description: List of VNF's
required: true
|
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
policy_types:
onap.policies.controlloop.Guard:
derived_from: tosca.policies.Root
description: Guard Policies for Control Loop Operational Policies
onap.policy.controlloop.guard.minmax:
derived_from: onap.policies.controlloop.Guard
description: Supports Min/Max number of VF Modules
properties:
minmax_policy:
type: map
description:
entry_schema:
type: onap.datatypes.guard.minmax
data_types:
onap.datatypes.guard.minmax:
derived_from: tosca.datatypes.Root
properties:
actor:
type: stringstringhttps://wiki.onap.org/display/DW/Policy+Types
description: Specifies the Actor
required: true
recipe:
type: string
description: Specified the Recipe
required: true
time_range:
type: tosca.datatypes.TimeInterval
description: An optional range of time during the day the Min/Max limit is valid for.
required: false
controlLoopName:
type: string
description: An optional specific control loop to apply this guard to.
required: false
min_vf_module_instances:
type: integer
required: true
description: The minimum instances of this VF-Module
max_vf_module_instances:
type: integer
required: false
description: The maximum instances of this VF-Module
|
...