...
Project Name | OOM | Notes |
---|
Health Check | Pass | Both Integration-OOM-Staging-Daily and Integration-OOM-Daily passed HC |
|
|
Data flows for all use case
| VES data reception (VNF to VES simulated)Pass | R3_DCAE_internal_flow.txt |
|
|
VES ↔ TCA , via DMaaP | Pass | See above attachment |
|
|
TCA ↔ Policy, via DMaaP | Pass | See above attachment |
|
|
DCAE (TCA) ↔ AAI, via API Pass | See above attachment |
|
|
DCAE (VES) ↔ Holmes (track metrics data), via DMaaP | Pass | VES-holmes-flow_log.TXT Verified DCAE(VES) events gets posted into DMAAP Fault topic and picked up Holmes container (Additional validation required from Holmes team on internal processing). Jira |
---|
|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | HOLMES-175
| | Control flow for supporting CLAMP | DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler API | Pass | Verified in Heat and OOM; coordinated by Integration team |
|
|
SDC↔ DCAE (blueprint distribution from SDC to DCAE Service Change Handler) | Pass | Verified in Heat and OOM; coordinated by Integration team |
|
|
DCAE (Policy Handler) ↔ Policy, via API and websocketPass | Verified in Heat and OOM; coordinated by Integration team |
|
|
R3 New flow (non-usecase related) |
|
|
|
---|
PNF Reg Flows | VES ↔ PRH, via DMaaP |
Pass | R3__AAI_MR_VES_flow.txtPRH Pass | See above attachment DMaapPass | Test Artifacts: R3_PRH_DMAAP-SO.txt file.
10/26 - PRH event published validated by Krzysztof Kuzmicki; additional SO subscription requires data preload (in SO) and has dependency on SDC/Portal. Recommendation to validate the remaining scope part of ETE testing approved by Helen.
10/24 -https://gerrit.onap.org/r/#/c/71137/ - unfortunate corrections to SO has been merged only to Dublin SO branch. When this merge will be back ported to Casablnca then we can start this test. Without that SO is not able to receive message from (send by PRH)10/22 - Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1102 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
key testing can be started when SO service will successfully instantiatedSO-1099 | HV-VES (5G) | WTP:GPB message ↔ HV-VES (tcp/socket) |
Pass | Windriver SB02 ; log file : hvves_pair_wise_testing_logPass | Windriver SB02 ; log file : hvves_pair_wise_testing_log |
|
|
|
|
|
|
Data-File (5G) | xNF (simulator) ↔ VES (http) |
PassWe use curl command to send fileReady event message to , and get "Accepted" response from VES.fileReady_event.txt
VES Pass | R3_DFC_MR_DR_XNF_flow.txtPassSee above attachment |
|
|
| DataFile Publish (Dmaap DR) |
Pass | See above attachment