Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyHOLMES-175

Project NameOOMNotes
Health CheckPassOn Integration-OOM-Stating tenant

Data flows for all use case


VES data reception (VNF to VES simulated)PassR3_DCAE_internal_flow.txt

VES ↔ TCA , via DMaaP

PassSee above attachment
TCA ↔ Policy, via DMaaPPassSee above attachment

DCAE (TCA) ↔  AAI, via API

PassSee above attachment
DCAE (VES) ↔ Holmes (track metrics data), via DMaaPWIP
Pending Holmes team validation

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyHOLMES-175

Control flow for supporting CLAMP

DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler APIBlockedPassVerified in Heat ; pending OOM test with CLAMP/Policy having AAF dependencyand OOM
SDC↔ DCAE (blueprint distribution from SDC to DCAE Service Change Handler)BlockedPassVerified in Heat ; pending OOM test with CLAMP/Policy having AAF dependencyand OOM
DCAE (Policy Handler) ↔ Policy, via API and websocketBlockedPassVerified in Heat ; pending OOM test with CLAMP/Policy having AAF dependencyand OOM
R3 New flow (non-usecase related)


PNF Reg FlowsVES ↔ PRH, via DMaaPPassR3_PRH_AAI_MR_VES_flow.txt

PRH ↔ AAI, via APIPassSee above attachment

PRH ↔ SO, via DMaapBlocked

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1102
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1099
testing can be started when SO service will successfully instantiated





HV-VES  (5G)WTP:GPB message ↔ HV-VES (tcp/socket)Pass

Windriver SB02 ; log file : hvves_pair_wise_testing_log


HV-VES ↔ DMAAP/kafka Pass

Windriver SB02 ; log file : hvves_pair_wise_testing_log





Data-File  (5G)xNF (simulator) ↔ VES (http)Pass

We use curl command to send fileReady event message to VES, and get "Accepted" response from VES.

fileReady_event.txt


VES ↔ DataFile via DMaaPPassR3_DFC_MR_DR_XNF_flow.txt

DataFile ↔ xNF (ftpes)PassSee above attachment

DataFile Publish (Dmaap DR) PassSee above attachment

...