DCAE R9 Istanbul Pairwise Test
Note: These test cases will be moved tointegration board (towards M3/RC0, similar to Guilin - DCAE Pair Wise Testing for Guilin Release)
Project Name | Status | Notes | |
---|---|---|---|
Health Check | |||
Data flows for all use case | VES data reception (VNF to VES simulated) | ||
VES ↔ TCAgen2 , via DMaaP | |||
TCAgen2 ↔ Policy, via DMaaP | |||
DCAE (TCAgen2) ↔ AAI, via API | NA | Note: To be validated part of integration test | |
DCAE (VES) ↔ Holmes (track metrics data), via DMaaP | NA | Note: To be validated part of integration test | |
Control flow for supporting CLAMP | DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler API | ||
SDC↔ DCAE (blueprint distribution from SDC to DCAE Service Change Handler) | |||
DCAE (Policy Handler) ↔ Policy, via API Retrieval | |||
Policy → DCAE (Policy Handler), update notification via DMaaP |
ONAP Bootstrapped services (non-usecase specific) | Status | ||
---|---|---|---|
PNF Reg Flows | VES ↔ PRH, via DMaaP | ||
PRH ↔ AAI, via API | |||
PRH ↔ SO, via DMaaP Note: Scope of this test is to validate DMaap notification/structure (E2E PNF registration flow to be verified during integration phase) | |||
HV-VES | WTP:GPB message ↔ HV-VES (tcp/socket) | ||
HV-VES ↔ DMAAP/kafka | |||
Bulk PM usecase | VES ↔ DFC, via DMaaP | ||
DFC datacollection | |||
DFC↔ PM-Mapper, via DMaaP/DR | |||
PM-Mapper ↔ Dmaap | |||