...
| Drawio | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
In the Honolulu release the CLAMP component was successfully integrated into the Policy component as a PoC (see
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Interface Name | Definition | Capabilities | Version | Status | Payload Model(s) | API Spec (Swagger) |
|---|---|---|---|---|---|---|
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 | |
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 | |
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 | ||
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 |
|
|
|
|
|
2b. Consumed APIs
Interface Name | Consumed by | Description | API Spec (Swagger) | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||
|
| ||||||||
CLSDC-1 | Policy/CLAMP |
| https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html | ||||||
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". |
| ||||||
Policies | Enrich ingress data with topology information | ||||||||
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 |
3. Component Description
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
...