Page Comparison

...

Frankfurt release targets the completion of the work started in Dublin to re-build the Policy Framework infrastructure. Work was done 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:

• Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-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.

• Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-9

   - Enhances the validation of TOSCA Policy Types and provides tools to Policy Designers.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-2028-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.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-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.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-21POLICY-2026

   - Finishing the work to fully move ALL the Control Loop Policy Types into TOSCA compliance with CLAMP team.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-18452087

   - Started in Dublin as dark code, finishing the support for this new actor to be fully available for Control Loop Operational Policies.

New or modified interfaces

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-2025REQ-162

   - 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.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQPOLICY-21

...

• 2028

   - Finished work such as added "application/yaml" as Content-Type.

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-20252026

   - Clarified PAP ↔ communication of Policy Types, Health Status, PDP Group Details, Passive vs Active modes.

If they are modified, are the backwards compatible?

Yes - all API's are backwards compatible. No real changes, only enhancements (eg adding new Content-Type) and added some convenience API's.

Interface naming (point to an example)

The Policy R4 Dublin R6 Frankfurt Independent Versioning And Release Process Plan - has a list of our incoming and outgoing dependencies.

Consumed API from other projects

Published API - These projects use the policy libraries to build their code

Reference to the interfaces.

All API's are Documented: https://docs.onap.readthedocs.ioorg/en/elaltolatest/submodules/policy/parent.git/docs/api/offeredapisapi.html

Legacy API: Policy API

What are the system limits?

...

• Will be deprecating the legacy Control Loop Operational and Guard policies after this release.