Brief Project Overview (brief as it should be known)
The ONAP Policy Framework is a comprehensive policy design, deployment, and execution environment. The Policy Framework is the decision making component in an ONAP system. It allows you to specify, deploy, and execute the governance of the features and functions in your ONAP system, be they closed loop, orchestration, or more traditional open loop use case implementations. The Policy Framework is the component that is the source of truth for all policy decisions.
New component capabilities for Frankfurt, i.e. the functional enhancements.
Frankfurt release targets the completion of the work started in Dublin to re-build the infrastructure. Work was done to complete missing functionality that was previously in the legacy components, or was targeted to be part of the platform and was not finished in Dublin:
- REQ-25 - Getting issue details... STATUS - When policies are deployed/undeployed (eg new version or removal), then some ONAP components need more immediate notification. Eg. DCAE microservices.
- REQ-9 - Getting issue details... STATUS - Enhances the validation of TOSCA Policy Types and provides tools to Policy Designers.
- POLICY-1845 - Getting issue details... STATUS - 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.
- REQ-162 - Getting issue details... STATUS - Finishing the work with the OOF team that started in Dublin, and working with the SDNC team to complete their work in Frankfurt.
- REQ-21 - Getting issue details... STATUS - Finishing the work to fully move the Control Loop Policy Types into TOSCA with CLAMP team.
- POLICY-2087 - Getting issue details... STATUS - Started in Dublin as dark code, finishing the support for this new actor to be available for Control Loop Operational Policies.
New or modified interfaces
- POLICY-2025 - Getting issue details... STATUS - 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-2028 - Getting issue details... STATUS - Finished work such as added "application/yaml" as Content-Type.
- POLICY-2026 - Getting issue details... STATUS - 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 R6 Frankfurt Independent Versioning And Release Process Plan - has a list of our incoming and outgoing dependencies.
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
| Portal | 2.6.0 | No upgrades targeted for this release. |
| AAF | v2.1.2 | |
| Dmaap | v1.1.8 | |
| SDC | 1.6.0 | |
| AAI | 1.0.1 | v16 schema |
| APP-C | Dmaap LCM API | No direct link to any libraries |
| SO | REST - No direct link to any libraries | |
| VFC | REST - No direct link to any libraries | |
| SDNR | Dmaap - No direct link to any libraries | |
| SDNC | REST - No direct link to any libraries |
Published API - These projects use the policy libraries to build their code
Project | API | Notes |
|---|---|---|
| CLAMP | Policy Lifecycle API Policy Administration API | implemented in own java code |
| OOF | Policy Decision API | implemented in own python code |
| SDNC | Policy Decision API | implemented in own code |
| DCAE | Policy Lifecycle API Policy Decision API Policy Update Notifications (via Dmaap) | Implemented own python code or performed manually. |
Reference to the interfaces.
All API's are Documented: https://onap.readthedocs.io/en/elalto/submodules/policy/parent.git/docs/offeredapis.html
Legacy API: Policy API
What are the system limits?
4Gb Memory - for most of the components.
Involved use cases, architectural capabilities or functional requirements.
vFW, Scale Out, vCPE, 5G OOF
Listing of new or impacted models used by the project (for information only).
POLICY-2118 - Getting issue details... STATUS - continuation of work started in Dublin
- Will be deprecating the legacy Control Loop Operational and Guard policies after this release.
POLICY-1930 - Getting issue details... STATUS - to further support better performance during runtime of Control Loops and ability for ONAP Policy Developers to easily create and integrate their own actors into runtime Control Loops.