...
2. API Definitions
2a. Exposed APIs
| Interface Name | Definition | Capabilities | Version | Status |
|---|
| Payload Model(s) |
|---|
| 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. |
| production | tosca.policies.root | |
| POE-2 | Policy Design | Allows applications (such as CLAMP and Integration) to create, update, delete, and query Policy entities. |
| production | tosca.policies.root | |
| 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. |
| production |
| Embedded | |
| 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 PDP. The calling application must provide attributes in order for the XACML PDP to return a correct decision. |
| NA | production | Defined by policy |
2b. Consumed APIs
| API Key | API Name | Description |
|---|---|---|
| AAI-X | Topology | Enrich ingress data with topology information |
| SO-X | Service Orchestrator | Trigger orchestration actions (policy driven) |
| Controller-X | Controller API | trigger control actions (policy driven) |
| TT-X | Trouble Ticketing | trigger open loop ticketing system |
| Other | Other Actions | Trigger any interface defined in a policy |
...