...
| 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 | ||
| API exposed by Policy to create/update guard policies (used for scale out use case operational policies) | ongoing | TBD | ||
| 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 |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| new policy api(and contents) for guard policies creation not defined yet | ||
| "vf_module_id" usage for scale out use case not yet completely confirmed |
Resources
Link toward the Resources Committed to the Release centralized page.
...