Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Frankfurt release targets the completion of the work started in Dublin to re-build the Policy Framework infrastructure. The new capabilities were to complete missing functionality that was previously in the legacy components, or was targeted to be part of the platform and was not able to be finished in Dublin:


Policy Update Notifications James Hahn

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-25
 - When policies are deployed/undeployed (eg new version or removal), then some ONAP components need more immediate notification. Notably, DCAE microservices need to respond quickly to policy changes. James Hahn


Policy Validation Liam Fallon

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-9
 - Enhances the validation of TOSCA Policy Types and provides tools to Policy Designers. Liam Fallon


Support for Native Policies  Chenfei Gao Jorge Hernandez

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1845
 - Some support for this in the legacy components, this work greatly enhances the ability to load PDP native policies that either execute alone or in conjunction with TOSCA Policy Types. Adds in Apex Native Policy Types in addition to XACML, Drools.


Optimization Policies Pamela Dragosh

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-162
 - Finishing the transition to new Policy Types with the OOF team that began in Dublin. This release we are working with the SDNC team to complete their transition in Frankfurt.


TOSCA Compliant Operational and Guard Policies

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-21
 - Finishing the work to fully move ALL the Control Loop Policy Types into TOSCA compliance with CLAMP team


Integration of CDS As an Actor Former user (Deleted) Rashmi Pujar

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2087
 - Started in Dublin as dark code, finishing the support for this new actor to be fully available for Control Loop Operational Policies


PDP Statistics - China Ericsson Team


PDP Monitoring GUI - China Ericsson Team


Consolidation of Policy Health Check Ram Krishna Verma

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2025
 - Per Integration team, one single health check requested that gives status for the whole of Policy Framework components. Added some enhancement for collection of statistics on how well the Policy components are executing.


Policy API Enhancements Chenfei Gao

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2028
 - Finished work such as added "application/yaml" as Content-Type.


PAP ↔ PDP Communication Ram Krishna Verma James Hahn

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2026
 - Clarified PAP ↔ communication of Policy Types, Health Status, PDP Group Details, Passive vs Active modes. Ram Krishna Verma