Key New Feature | SME | Details | Readthedocs/JIRA etc. | Demo |
---|
Re-design of Control Loop Actor/Operation Code | | Control Loop actor code was re-designed and cleaned up enabled faster integration of new actors and operations for control loops. Drools Rules Simplification. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-1930 |
---|
|
|
|
Policy Update notifications | | When versions of policies are deployed/undeployed, an update notification is sent on Dmaap topic so that clients (DCAE in particular) can make Decision API call to get the latest policy that they should be enforcing. | | TOSCA Compliant Policy Types | | In Frankfurt, the policy framework finished its support of TOSCA Compliant Policy Types. New Policy Types were implemented to support these domains: - Control Loop Operations
- Control Loop Guard Queries
- OOF Project Optimization placement
- SDNC Naming Algorithms
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2118 |
---|
|
https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/design/design.html NOTE: documentation is still WIP |
|
Policy Validation, Versioning and Retrieval improvements | | Improvements in validation of Policy Types and PoliciesFixes for Policy VersioningWhen retrieving a Policy Type, inherited policy types are now included in the API call along with referenced Data TypesPAP Component Enhancements | | - Treatment of PASSIVE state for PDPs: If a PDP fails to deploy one or more policies specified in a PDP-UPDATE message, PAP will undeploy those policies that failed to deploy to the PDP. This entails removing the policies from the Pdp Group(s), issuing new PDP-UPDATE requests, and updating the notification tracking data.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2027 |
---|
|
| Native Policy Types | | Native Policy Support for each PDP was implemented. Now users can use the APIs to create policies specific to a PDP such as Drools Rules, XACML XML policies and Apex policies. - Drools Native DRL
- XACML Native XML
- Apex Native Javascript
| |
|
New PAP API for Create and Update PDP Groups | | - A new API is introduced to deploy policies on specific PDPGroups
- Fetch policy deployment status: Clients will be able to poll the PAP API to find out when policies have been successfully or unsuccessfully deployed to the PDP's.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY- |
---|
|
| 1845Documentation is WIP for each PDP to document its native policy type and implementation. |
|
Consolidation of Healthcheck and statistics | | Consolidated the health check of all the components into the PAP. Previously each component had to be queried for health status, now a single call to the PAP can retrieve the health of all the components. NOTE: This does not include legacy components. - Statistics for XACML and Apex PDP components enhanced.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2025 |
---|
|
| Re-design of Control Loop Actor/Operation Code | | Control Loop actor code was re-designed and cleaned up enabled faster integration of new actors and operations for control loops. Drools Rules Simplification. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-1930 |
---|
|
New PAP API for Create and Update PDP Groups | | A new API is introduced to deploy policies on specific PDPGroupsFetch policy deployment status: Clients will be able to poll the PAP API to find out when policies have been successfully or unsuccessfully deployed to the PDP'sYes |
Policy Distribution now uses Lifecycle API and PAP Deployment API | | Policy Distribution now uses the Lifecycle API and PAP deployment API to auto create and deploy policies upon service distribution. The legacy API's support were removed. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-20262067 |
---|
|
|
|
CDS as an Actor in Control Loops | | CDS as an actor in Control Loops is now fully supported. Introduced in Dublin, the new actor is now available to be used in Operational policies. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2087 |
---|
|
| Policy Distribution now uses Lifecycle API and PAP Deployment API | | Policy Distribution now uses the Lifecycle API and PAP deployment API to auto create and deploy policies upon service distribution. The legacy API's support were removed | Yes |
Policy Validation, Versioning and Retrieval improvements | | - Improvements in validation of Policy Types and Policies
- Fixes for Policy Versioning
- When retrieving a Policy Type, inherited policy types are now included in the API call along with referenced Data Types.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2027 |
---|
|
|
|
TOSCA Compliant Policy Types | | In Frankfurt, the policy framework finished its support of TOSCA Compliant Policy Types. New Policy Types were implemented to support these domains: - Control Loop Operations
- Control Loop Guard Queries
- OOF Project Optimization placement
- SDNC Naming Algorithms
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2118 |
---|
|
https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/design/design.html NOTE: documentation is still WIP |
|
Configurable Policy Type and Policy Pre-Loading | | Configurable Pre-loading and pre-deployment of policies. When ONAP is brought up, the user can configure a set of default policies that can be created and deployed. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2028 |
---|
|
|
|
Lifecycle API Enhancements | | - Added a new simplified API to create one or more policies in a single API call.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-20672028 |
---|
|
|
|
XACML PDP Features | | - Decision API for monitoring policies was enhanced to support an abbreviated list of policies.
- Decision API now supports naming policies for CCSDK project.
- Decision API now supports a closest match algorithm for optimization policies and enhancements were made to better support policies with "matchable" properties.
- Support for PASSIVE Mode
- Now returns error when a policy cannot be loaded
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2067 |
---|
|
| Yes |
Native Policy Types | | Introduction to Native Policy Support for each PDP was implemented. Now users can use the APIs to create policies specific to a PDP such as Drools Rules, XACML XML policies and Apex policies. - Drools Native DRL
- XACML Native XML
- Apex Native Javascript
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-1845 |
---|
|
Documentation is WIP for each PDP to document its native policy type and implementation. |
|
Drools PDP Features | | - Support for offline mode which allows users to run drools in a locked environment.
- Parameterize mvn repo urls and proxy settings which allows the users to build the docker images for drools-pdp and drools-application using their own CI pipelines.
- New Controller TOSCA Compliant Operational Policies.
- New Controller TOSCA Compliant Native Controller and Artifact Policies.
- Enhanced Telemetry API to support Native and Controller TOSCA Policy Types.
- Validation of Operational and Native Policies against their policy type.
- Rate limiting of ONSET events to prevent flooding from identical events from DCAE.
- Docker for a generic Drools-PDP standalone that can be used for other applications.
- Native Policies
|
|
|
Apex PDP Features | | Jira Legacy |
---|
|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2026- Multiple Policy Deployment now supported
- Apex now sends the Statistics data in every heartbeat sent to PAP
- Changed JavaScript executor from Nashorn to Rhino as part of Java 11 upgrade.
- Passing parameters from ApexConfig to policy logic.
- Added support for interaction with CDS over gRPC
Configurable Policy Type and Policy Pre-Loading | | Configurable Pre-loading and pre-deployment of policies. When ONAP is brought up, the user can configure a set of default policies that can be created and deployed. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2028 |
---|
|
| Lifecycle API Enhancements | | - Added a new simplified API to create one or more policies in a single API call.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-2028 |
---|
|
| PAP Component Enhancements | | - Treatment of PASSIVE state for PDPs: If a PDP fails to deploy one or more policies specified in a PDP-UPDATE message, PAP will undeploy those policies that failed to deploy to the PDP. This entails removing the policies from the Pdp Group(s), issuing new PDP-UPDATE requests, and updating the notification tracking data.
| |
|
|