...
| Interface Name | Definition | Capabilities | Version | Status | Payload Model(s) | API Spec (Swagger) |
|---|---|---|---|---|---|---|
| POE-1 | Policy Type Design | Allows applications to create, update, delete, and query PolicyType entities so that they become available for use in ONAP by applications such as CLAMP. | 1.0.0 | production | tosca.policies.root | https://docs.onap.org/projects/onap-policy-parent/en/latest/api/api.html#api-swagger |
| POE-2 | Policy Design | Allows applications (such as CLAMP and Integration) to create, update, delete, and query Policy entities. | 1.0.0 | production | tosca.policies.root | https://docs.onap.org/projects/onap-policy-parent/en/latest/api/api.html#api-swagger |
| POE-3 | Policy Administration | Support CRUD of PDP groups and subgroups and to support the deployment and life cycles of PolicyImpl entities (TOSCA Policy and PolicyTypeImpl entities) on PDP sub groups and PDPs. | 1.0.0 | production | Embedded | https://docs.onap.org/projects/onap-policy-parent/en/latest/pap/pap.html#pap-rest-api-swagger |
| POE-4 | Data Ingress | Listen on a DMaaP topic. | production | Messages of interest are described in the policy logic DMaaP | ||
| POE-5 | Decision Query | 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. | NA | production | Defined by policy | https://docs.onap.org/projects/onap-policy-parent/en/latest/xacml/decision-api.html |
| CLPOE-1 | Control Loop Lifecycle Management and Polciy Lifecycle Management Interface | A user interface (GUI) for:
| NA | Defined by policy | NA (GUI) |
...
| Interface Name | Consumed by | Description | API Spec (Swagger) | ||||||
|---|---|---|---|---|---|---|---|---|---|
| AAF | Policy Framework | Authentication and authorization | |||||||
| DMaaP | Policy Framework Policies | Policy framework uses DMaaP for SDC subscriptions and internal communication. Policies use DMaaP as a transport for contextual information from various sources | |||||||
| SDC | Policy Framework |
| |||||||
| CLDCAE-1 | Policy/CLAMP |
| https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/apis/inventory.html | ||||||
| CLDCAE-2 | Policy/CLAMP | Deploy/remove DCAE µS. | https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/apis/deployment-handler.html | ||||||
| CLCDS-1 | Policy/CLAMP | Get list of operations/actions and corresponding payload for Operational Policy where selected actor is "CDS". |
| ||||||
| AAI | Policies | Enrich ingress data with topology information | |||||||
| SO | Policies | Trigger orchestration actions (policy driven) | |||||||
| Policies | Trigger control actions (policy driven) | ||||||||
| Other | Policies | Trigger any interface defined in a policy, for example, trouble ticketing |
...
- Create control loop from DCAE blueprint, those blueprint are either:
- sent by SDC to DCAE (inventory) via SDC distribution.
- Create configuration policy from the policy-model Tosca, the tosca policy-model are either:
- sent sent by SDC via SDC distribution to everyone; or
- or query by CLAMP to Policy. in this case the policy-model is either pre-provison provisioned in Policy
or separately provision provisioned to Policy via the REST API exposed by Policy.
- Configure Configure DCAE applications of the control loop
- Associate µService configuration policies to the DCAE application
- Configure the operations to be taken by the control loop (by creating/updating/deleting operational policies)
- Deploy/un-deploy control loop flow (blueprints) to DCAE
- Control loop visualization.
...
The main new capability introduced in this release is the integration of the CLAMP component under the policy umbrella (see
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
And additional The PoC experiments with defining Control Loops fully in Tosca will continue, as well. This is covered by
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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 | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Conformance with ONAP-wide requirements (
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...