Pair Wise test | Status |
---|
Notes | ||||||||
---|---|---|---|---|---|---|---|---|
Health Check |
| tested on Windriver SDC lab : 10.12.6.10 | ||||||
SDC ↔ SO, via DMaaP |
| ||||||||
SDC ↔ AAI, via DMaaP |
| ||||||||
SDC ↔ SDNC, via DMaaP |
| |||||||
SDC ↔ VFC (distribute package), via API |
| ||||||||
SDC ↔ DCAE (distribute DCAE configuration), via DMaaP |
| Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
Tca.yaml has been deployed properly to DCAE as CLAMP was able to deploy the Loop template (CLAMP does a query to DCAE to get the ID of that artifact when it deploys the SDC notification) | |||||||
SDC ↔ CLAMP (distribute Control Loop blueprint) |
| Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
In CLAMP we see well the 3 different versions of the service deployed from SDC | ||||||
SDC ↔ VID, via API |
| ||||||||
SDC ↔ UUI, via API |
| ||||||||
SDC ↔ Policy, via DMaaP |
| ||||||||
SDC ↔ VNFSDK |
| ||||||||
SDC ↔ PORTAL |
| Tested on Windriver CLAMP lab : 10.12.6.10
| ||||||
SDC ↔ CDS |
| |||||||
SDC ↔ VTP |
| ||||||||
SDC ↔ MultiCloud |
| |||||||
SDC ↔ ExternalAPI |
|