| Pair Wise test | Status | Notes |
|---|---|---|
| Health Check | PASS | tested on Windriver SDC lab : 10.12.6.10 |
SDC ↔ SO, via DMaaP | ONGOING | |
| SDC ↔ AAI, via DMaaP | PASS | Distributed vFW to AAI through DMaaP see screenshot below
|
SDC ↔ SDNC, via DMaaP | PASS | distributed vFW to SDNC through DMaaP see screenshot below
|
| SDC ↔ VFC (distribute package), via API | ONGOING | |
| SDC ↔ DCAE (distribute DCAE configuration), via DMaaP | ONGOING | 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) | PASS | 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 | ONGOING | |
| SDC ↔ UUI, via API | ONGOING | |
| SDC ↔ Policy, via DMaaP | ONGOING | |
| SDC ↔ VNFSDK | ONGOING | |
| SDC ↔ PORTAL | PASS | Tested on Windriver CLAMP lab : 10.12.6.10
|
| SDC ↔ CDS | ONGOING | |
| SDC ↔ VTP | ONGOING | |
| SDC ↔ MultiCloud | ONGOING | |
| SDC ↔ ExternalAPI | ONGOING |
General
Content
Integrations