Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

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 DMaaPWIPPending Holmes team validation

Control flow for supporting CLAMP

DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler APINoVerified in Heat; pending OOM test with CLAMP/Policy having AAF dependency
SDC↔ DCAE (blueprint distribution from SDC to DCAE Service Change Handler)NoVerified in Heat; pending OOM test with CLAMP/Policy having AAF dependency
DCAE (Policy Handler) ↔ Policy, via API and websocketNoVerified in Heat; pending OOM test with CLAMP/Policy having AAF dependency
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

SO-1102 - Getting issue details... STATUS SO-1099 - Getting issue details... STATUS 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 PassWindriver SB02




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




  • No labels