Versions Compared

Old Version 1

changes.mady.by.user cl664y@att.com

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
Both

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

-Daily and Integration

-Daily

DCAE-Healthcheck-OOM-

Daily passed HC

Staging.txt

Data flows for all use case


VES data reception (VNF to VES simulated)Pass
R3_
DCAE-VNF_
internal
VES_
flow
TCA.txt

VES ↔ TCA , via DMaaP

PassSee above attachment
TCA ↔ Policy, via DMaaPPassSee above
attachment
attachement

DCAE (TCA) ↔  AAI, via API

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

DCAE-

holmes

VESCollector-

flow_log

Holmes.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).

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
key

HOLMES-175

Control flow for supporting CLAMP

DCAE↔ CLAMP (CLAMP trigger blueprint deployment) , via DCAE Deployment Handler APIPassVerified in Heat and OOM; coordinated by Integration team

POLICY-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
Verified in Heat and OOM; coordinated by Integration team

SDC-DCAE_ServiceChangeHandler.txt

DCAE-InventoryUpdate_FromSCH.txt

DCAE (Policy Handler) ↔ Policy, via API and websocketPass

05/07 - Verified

in Heat and OOM; coordinated by Integration teamR3 New flow (non-usecase related

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 specific)


PNF Reg FlowsVES ↔ PRH, via DMaaP
PassR3_PRH_AAI_MR_VES_flow.txt
Passed

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 API
Pass10/22 -
Passed

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

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 DMaap(send by PRH)

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).


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
key

SO

DCAEGEN2-

1102

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

SO

INT-

1099

1056

testing can be started when SO service will successfully instantiated

to be closed




HV-VES 
(5G)Windriver SB02 ; log file : hvves_pair_wise_testing_log
WTP:GPB message ↔ HV-VES (tcp/socket)
PassVES ↔ DataFile via DMaaPPassR3_DFC_MR_DR_XNF_flow.txtDataFile ↔ xNF (ftpes)PassSee above attachmentDataFile Publish (Dmaap DR) PassSee above attachment
Passed



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

Passed