Versions Compared

Key

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

...

#

Component(s)

Test Case

Status

Remarks

IT#001DCAE (SON Handler MS)SON Handler Micro-service successfully on-boarded on to DCAE

Status
colourGreen
titleComplete


IT#002DCAE (SON Handler MS)SON Handler Micro-service's DB is up and the Micro-service is able to read/write data.

Status
colourGreen
titleComplete


IT#003DCAE (SON Handler MS)SON Handler Micro-service is able to successfully fetch config policies from Consul.

Status
colourGreen
titleComplete


IT#004OOF and PolicyOOF is able to successfully fetch config policy from Policy

Status
colourBlue
titleNOT APPLICABLE

This test case is no longer applicable, as there is no policy-driven actions in OOF for this use case in Dublin.
IT#005DCAE (SON Handler MS)SON Handler Micro-service is able to successfully receive a message over DMaaP containing PM/FM data (from VES Collector)

Status
colourGreen
titleComplete


IT#006

DCAE (SON Handler MS) and DMaaP

SON Handler Micro-service is able to successfully receive a message over DMaaP containing neighbor list update

Status
colourGreen
titleComplete


IT#007DCAE (SON Handler MS) REST interfaceSON Handler Micro-service is able to successfully fetch neighbor list details using REST interface (Config DB APIs)

Status
colourGreen
titleComplete


IT#008DCAE (SON Handler MS) and OOFSON Handler Micro-service invokes REST API of OOF for PCI optimization

Status
colourGreen
titleCOMPLETE

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

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

IT#009OOF and Config DB (REST API)OOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API)

Status
colourGreen
titleComplete

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

IT#010DCAE (SON Handler MS) and OOFSON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response

Status
colourGreen
titleComplete

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

IT#011DCAE (SON Handler MS) and Config DB (REST API)SON Handler Micro-service is able to successfully fetch PNF details from Config DB (using REST API call)

Status
colourGreen
titleComplete


IT#012DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to send PCI/ANR updates via DMaaP to Policy

Status
colourGreen
titleCOMPLETE

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

IT#013Policy and DMaaPPolicy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates.

Status
colourGreen
titleComplete


IT#014Policy and DMaaPPolicy is able to successfully receive a DMaaP message with PCI/neighbor list update response

Status
colourGreen
titleComplete


IT#015DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to receive PCI/neighbor list update response via DMaaP from Policy, process it and logs the results.

Status
colourGreen
titleComplete


IT#016

DCAE (SON Handler MS)SON Handler Micro-service is able to process PM KPI data, store as needed, and apply rules to recommend removal of a neighbor relationship.

Status
colourGreen
titleCOMPLETE


IT#017SDN-RUpon receiving message from Policy, SDN-R sends netconf message to RAN-Sim.

Status
colourYellowBlue
titlePROGRESSINGNOT APPLICABLE

pending completion of 2 known issues (Medium): CCSDK-1399 and CCSDK-1400

Will be completed when CCSDK-1399 and CCSDK-1400 are delivered (so not part of Dublin).

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

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

The DMaaP listener docker with the code fix is not yet deployed in SB-00 where the testing is done. The code, fix however, is already merged on to Dublin and Master branches. So, once the latest docker is deployed, we will continue and complete the test case at Windriver.

IT#018DCAE (VES Collector)VES Collector receives VES messages from RAN-Simulator

Status
colourGreen
titleComplete

IT#019

SDNC (DMAAP Listener)

SDNC is able to receive DMAAP message from Policy

IT#020

SDNC

SDNC is able to receive a DMAAP message to configure PCI value (Action: ModifyConfig) and invoke RPC: configure-phy-cell-id

Prerequisite: RAN simulator is configured and Netconf mounted onto SDNC

IT#021

SDNC

SDNC is able to receive a DMAAP message to configure PCI value and/or blacklisted flag of neigbor cell/s (Action: ModifyConfigANR) and invoke RPC: generic-neighbor-configuration

Prerequisite: RAN simulator is configured and Netconf mounted onto SDNC

IT#022

SDNC & RAN simulator

RPC execution (configure-phy-cell-id): Verify if Restconf transactions against the Netconf mounted RAN simulator succeed in configuring PCI value of a cell

This can be verified by reviewing either SDNC/DG logs (/opt/opendaylight/current/data/log/configuration-phy-cell-id.log) or executing GET Restconf transaction from the SDNC Restconf API explorer

IT#023

SDNC & RAN simulator

RPC execution (generic-neighbor-configuration): Verify if Restconf transactions against the Netconf mounted RAN simulator succeed in configuring PCI value and/or blacklisted flag of neighbor cell/s

This can be verified by reviewing either SDNC/DG logs (/opt/opendaylight/current/data/log/generic-neighbor-config.log) or executing GET Restconf transaction from the SDNC Restconf API explorer

IT#024

SDNC & RAN simulator

RAN simulator generates Netconf notification to indicate neighbor list change notification

Prerequisite: RAN simulator is configured and Netconf mounted onto SDNC

IT#025

SDNC & RAN simulator

SDNC after receiving Netconf notification invokes RPC handle-nbrlist-change-notif

Prerequisite: RAN simulator is configured and Netconf mounted onto SDNC

IT#026

SDNC & ConfigDB

RPC execution (handle-nbrlist-change-notif): Update configDB by adding new neighbors per NETRCONF notification

Verify ConfigDB is updated by executing GET transaction from Postman

Verify neighbor additions are aligned with neighbor list change Netconf notification

IT#027

SDNC/DMAAP message 

RPC execution (handle-nbrlist-change-notif): DMAAP message ( PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO) is published from SDNR to be consumed by SON MS

Verify DMAAP message is published onto message router

Verify payload of the DMAAP message aligns with the original neighbor list change Netconf notification




Test Case ID

IT#001

Test Case Name

SON Handler Micro-service on-boarding

Description

SON Handler Micro-service is successfully on-boarded on to DCAE

Release

Dublin

Pre-conditions

(a) DCAE up and running

(b) DCAE CLI available

Testing Steps


Steps

Expected Result

  1. SON-Handler component spec validated.
  2. SON-Handler is brought up manually on DCAE.
  3. SON-Handler Blueprint validated successfully.
  4. DCAE is brought online.
  1. SON-Handler comes up online and is stable.


Conclusion (Pass /Fail)


Testing Lab

Windriver lab

...