blob: ccbad75afc2885a2a4bd581c8cf573afb750a53a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. _drools-label:
Policy Drools PDP Engine
########################
.. contents::
:depth: 1
The Drools PDP, aka PDP-D, is the PDP in the Policy Framework that uses the
`Drools BRMS <https://www.drools.org/>`__ to enforce policies.
The PDP-D functionality has been partitioned into two functional areas:
- PDP-D Engine.
- PDP-D Applications.
**PDP-D Engine**
The PDP-D Engine is the infrastructure that *policy applications* use.
It provides networking services, resource grouping, and diagnostics.
The PDP-D Engine supports the following Tosca Native Policy Types:
- onap.policies.native.Drools
- onap.policies.native.drools.Controller
These types are used to dynamically add and configure new application controllers.
The PDP-D Engine hosts applications by means of *controllers*.
*Controllers* may support other Tosca Policy Types. The
types supported by the *Control Loop* applications are:
- onap.policies.controlloop.operational.common.Drools
- onap.policies.controlloop.Operational
**PDP-D Applications**
A PDP-D application, ie. a *controller*, contains references to the
resources that the application needs. These include networked endpoint references,
and maven coordinates.
*Control Loop* applications are used in ONAP to enforce operational policies.
The following guides offer more information in these two functional areas.
.. toctree::
:maxdepth: 2
pdpdEngine.rst
pdpdApps.rst
|
