...
6. New Release Capabilities
TBD
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 |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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 |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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 |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-429 |
---|
|
). Existing use cases will be supported (no change).Conformance with ONAP wide requirements (
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-441 |
---|
|
, Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-437 |
---|
|
, Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-398 |
---|
|
, Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-396 |
---|
|
, and Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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