Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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 in the legacy components:


New or modified interfaces

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


AAFv2.1.2
Dmaapv1.1.8


SDC1.6.0
AAI1.0.1

v16 schema

APP-CDmaap LCM APINo 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


OOFPolicy Lifecycle APIimplemented in own python code
SDNCPolicy Lifecycle APIimplemented in own code
DCAEPolicy Lifecycle APIImplemented 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.



  • No labels