...
| Pair Wise test | Status | Notes | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Health Check |
| tested on Windriver SDC lab : 10.12.6.10 | ||||||||||||||||
SDC ↔ SO, via DMaaP |
| Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
| ||||||||||||||||
| SDC ↔ AAI, via DMaaP |
| Distributed vFW to AAI through DMaaP see screenshot below
| ||||||||||||||||
SDC ↔ SDNC, via DMaaP |
| distributed vFW to SDNC through DMaaP see screenshot below
| ||||||||||||||||
| 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 |
| Browse distributed service model OK with VID
| ||||||||||||||||
| SDC ↔ UUI, via API |
| Tested by UUI team see pairwise of UUI | ||||||||||||||||
| SDC ↔ Policy, via DMaaP |
| Since HPA pulled their support for their use case, we have nothing configured in order to test that the interface still works. | ||||||||||||||||
| SDC ↔ VNFSDK |
| VNFSDK has swithed switched to HTTPS, SDC needs to be updated to reflect that see
Bug fixed in 1.7.2 Loading test VNF through VNFSDK
Then browsing and retrieving it from SDC
| ||||||||||||||||
| SDC ↔ PORTAL |
| Tested on Windriver CLAMP lab : 10.12.6.10
| ||||||||||||||||
| SDC ↔ CDS |
| Distribution to CDS successful
| ||||||||||||||||
| SDC ↔ VTP |
| Not run as part of this campaign. | ||||||||||||||||
| SDC ↔ MultiCloud |
| Distribution of model successful
| ||||||||||||||||
| SDC ↔ ExternalAPI |
| called extapi for service catalog through extapi successfully
tested using Swagger Firefox plugin
|
...