Allows applications to create, update, delete, and queryPolicyTypeentities so that they become available for use in ONAP by applications such as CLAMP.
Support CRUD of PDP groups and subgroups and to support the deployment and life cycles ofPolicyImplentities (TOSCAPolicyandPolicyTypeImplentities) on PDP sub groups and PDPs.
Policy decisions are required by ONAP components to support the policy-driven ONAP architecture. Policy Decisions are implemented using the XACML and Apex PDPs. The calling application (which may be another policy – e.g. invocation of a guard policy from PDP-D) must provide attributes in order for the PDP to return a correct decision.
Trigger any interface defined in a policy, for example, trouble ticketing
...
6. New Release Capabilities
Support for Control Loop CCVPN support 5G OOF PCI support E2E Network Slicing support Scale out support Security hardening ONAP maturity Performance (S3P) ONAP maturity Securtiy (S3P) CLC Coordination directives Code refactoring
Policy-CLAMP merger (POC) Stateless PAP
7. References
The main new capability introduced in this release as a PoC is the integration of the CLAMP component under the policy umbrella (see
As outlined in the architecture review page (Policy Honolulu-R8 Architecture Review) the only new use case that may be supported as a stretch goal is the 5G one (
(there are some risks, see Honolulu Risks page)) are already or will be supported.
Additional enhancements to the Policy components will be introduced in this release that have no external impact. These include but are not limited to:
Stateless PAP (Keep no state in PAP runtime container, so state retrieval would be from database).
Interoperability of Native and non-native policies in the Drools PDP.
Healthcheck status improvements as well as statistics reporting.