Versions Compared

Old Version 2

changes.mady.by.user Christopher McCray

Saved on

compared with

New Version Current

changes.mady.by.user Vijay Kumar

Saved on

Key

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


Project NameOOMNotes
Health CheckPass

As of status on 04/30 on Integration-OOM-Staging-Daily

DCAE-Healthcheck-OOM-Staging.txt

Data flows for all use case


VES data reception (VNF to VES simulated)PassDCAE-VNF_VES_TCA.txt

VES ↔ TCA , via DMaaP

PassSee above attachment
TCA ↔ Policy, via DMaaPPassSee above attachement

DCAE (TCA) ↔  AAI, via API

PassSee above attachement
DCAE (VES) ↔ Holmes (track metrics data), via DMaaPPass

DCAE-VESCollector-Holmes.TXT

See results on Holmes Pair Wise Testing for Dublin Release

Control flow for supporting CLAMP

DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler APIPass

05/09 - Testing was completed this afternoon. Results below

DCAE-CLAMP-deploymentlogs_TEST2.txt

DCAE-CLAMP-deploymentlogs.TXT

05/06  - Identified issues on Policy with recent test (

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1735
 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1736
); pending retest after fix from Policy.

SDC distribution issue to CLAMP/Policy  

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2257

SDC↔ DCAE (blueprint distribution from SDC to DCAE Service Change Handler)Pass

SDC-DCAE_ServiceChangeHandler.txt

DCAE-InventoryUpdate_FromSCH.txt

DCAE (Policy Handler) ↔ Policy, via API and websocket
R3 New flow
Pass

05/07 - Verified after Policy patch applied in SB00; Policy-PolicyHandler-Consul-TCA.txt

05/06  - Connection validated; identified issues on Policy in recent test (

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1735
 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1736
); pending retest after fix by Policy team.

SDC distribution issue to CLAMP/Policy  

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2257


ONAP Bootstrapped services (non-usecase
related
specific)


PNF Reg FlowsVES ↔ PRH, via DMaaPPassed

05/09 - Input event in DMaaP (from VES) whish red by PRH: VES-REG-OUTPUT-as-pnf-notification.json

05/06 - logs_robot_windriver_pnf_registrate.zip 

Dependent on

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1831
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1465
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1056


PRH ↔ AAI, via APIPassed

05/06  - See above attachment

Dependent on

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1831
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1465
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1056


PRH ↔ SO, via DMaapPass

5/9 - The message from PRH to DMAAP was verified. PRH DMaap o/p : PNF-READY.json.

Nokia Team attempted E2E validation which has more external dependencies (SO, SDNC, AAI, PORTAL etc) was blocked by  

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-757
.  As this falls outside pair-wise realm; this issue should be tracked  under Integration test. From DCAE-PRH standpoint - message payload/structure being published into DMaap was validated (same as R3).

HV-VES  (5G)


05/06  - Requires Portal being up - Wind river Portal page not accessible; also at Nokia's lab Portal page not working. Internal 500 server error. Dependent on

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1831
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1465
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1056
to be closed




HV-VES WTP:GPB message ↔ HV-VES (tcp/socket)Passed



HV-VES ↔ DMAAP/kafka 
Data-File  (5G)xNF (simulator) ↔ VES (http)VES ↔ DataFile via DMaaPDataFile ↔ xNF (ftpes)DataFile Publish (Dmaap DR) 
Passed