...
The other ONAP projects CLAMP depends on are:
- SDC/DCAE-D : Rest based interface exposed by the SDC, Distribution of service to DCAE + SDC UX UI SDKDistribution of Templates to CLAMP via SDC distribution client jar
- DCAE: Rest based interface exposed by DCAE, Common Controller Framework, DCAE microservices onboarded (TCA, Stringmatch, Holmes (optional))
- Policy: Rest based interface (the Policy team provide a "jar" to handle the communication), both XACML and Drools PDP, APIs to App-C/VF-C/SDN-C
- DMaaP: Message bus within DCAE and cross-ONAP
- VNF use cases : defines what type(s) of control loop(s) can be implemented and configured by CLAMP
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Same as Beijing | API exposed by SDC to get list of Alarms and service information's | Date for which the API is reviewed and agreed | Already available | Link toward the detailed API description |
| Same as Beijing | SDC Client(jar library provided by SDC team) used to get service template (describing control loop flow) and blueprint id( to know which blueprint has been distributed to DCAE for this Control Loop template) | Already available | ||
| Same as Beijing | API exposed by Policy to create/update policies | Already available | ||
| Same as Beijing | API exposed by DCAE to start/stop a Closed Loop | Already available | ||
| Same as Beijing | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | ||
| Same as Beijing | API exposed by DCAE to get status of a Closed Loop | Already available |
...