...
| Drawio |
|---|
| border | true |
|---|
| |
|---|
| diagramName | policy_r7 |
|---|
| simpleViewer | false |
|---|
| width | |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 1007 |
|---|
| revision | 2 |
|---|
|
In the Honolulu release the CLAMP component is being integrated into the Policy component as a PoC (see
| 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-473 |
|---|
|
) . CLAMP's functional role to provision Policy stays the same, as the project and associated resources are simply moved under the policy umbrella.2. API Definitions
2a. Exposed APIs
...
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
Please see the TOSCA Policy Primer page for an introduction to TOSCA policy concepts. See the Policy Design and API flow page for a description of the component interactions.
...
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
...
The main new capability introduced in this release as a PoC is the integration of the CLAMP component under the policy umbrella (see
| 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-473 |
|---|
|
). The software is being moved under the policy/clamp repository (https://git.onap.org/policy/clamp). The OOM helm charts are also moving as a subcomponent of policy (https://git.onap.org/oom/tree/kubernetes/policy/components).And additional PoC experiments with defining Control Loops fully in Tosca. This is covered by
| 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-478 |
|---|
|
.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 (
| 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-429 |
|---|
|
). Existing use cases will be supported (no change).Conformance with ONAP wide requirements (
| 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-441 |
|---|
|
,| 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-437 |
|---|
|
, | 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-398 |
|---|
|
, | 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-396 |
|---|
|
, and | 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-439 |
|---|
|
(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.
7. References
- Honolulu architecture description https://docs.onap.org/projects/onap-policy-parent/en/latest/architecture/architecture.html
Policy Framework API's - https://docs.onap.org/projects/onap-policy-parent/en/latest/offeredapis.html