Policy Drools PDP Engine
The Drools PDP, aka PDP-D, is the PDP in the Policy Framework that uses the Drools BRMS 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
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.
- PDP-D Engine
- Overview
- Software
- Communication Endpoints
- Controllers
- Tosca Policies
- Software Architecture
- Features
- Data Migration
- Maven Repositories
- AAF
- Policy Tool
- Telemetry Shell
- Other tools
- PDP-D Docker Container Configuration
- Running PDP-D with a single container
- Running PDP-D with nexus and mariadb
- Configuring the PDP-D in an OOM Kubernetes installation
- Additional information
- PDP-D Applications
- Overview
- Software
- Usecases Controller
- Operational Policy Types
- Policy Chaining
- Features
- Offline Mode
- Running the PDP-D Control Loop Application in a single container
- Scale-out use case testing
- vCPE use case testing
- vFirewall use case testing
- Running PDP-D Control Loop Application with other components
- Additional information