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
- REQ-9 - Getting issue details... STATUS
- POLICY-2028 - Getting issue details... STATUS
- POLICY-2026 - Getting issue details... STATUS
- POLICY-1845 - Getting issue details... STATUS
- REQ-162 - Getting issue details... STATUS
- REQ-21 - Getting issue details... STATUS
- POLICY-2087 - Getting issue details... STATUS
New or modified interfaces
- POLICY-2025 - Getting issue details... STATUS
If they are modified, are the backwards compatible?
Yes - all API's are backwards compatible.
Interface naming (point to an example)
The Policy R4 Dublin 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 | |
| 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 | Implemented own python code |
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.