...
# | Component(s) | Test Case | Status | Remarks | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IT#001 | DCAE (SON Handler MS) | SON Handler Micro-service successfully on-boarded on to DCAE |
| |||||||||||||||||||||||||||||
IT#002 | DCAE (SON Handler MS) | SON Handler Micro-service's DB is up and the Micro-service is able to read/write data. |
| |||||||||||||||||||||||||||||
IT#003 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully fetch config policies from Consul. |
| |||||||||||||||||||||||||||||
IT#004 | OOF and Policy | OOF is able to successfully fetch config policy from Policy |
| This test case is no longer applicable, as there is no policy-driven actions in OOF for this use case in Dublin. | ||||||||||||||||||||||||||||
IT#005 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully receive a message over DMaaP containing PM/FM data (from VES Collector) |
| |||||||||||||||||||||||||||||
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 |
| |||||||||||||||||||||||||||||
IT#007 | DCAE (SON Handler MS) REST interface | SON Handler Micro-service is able to successfully fetch neighbor list details using REST interface (Config DB APIs) |
| |||||||||||||||||||||||||||||
IT#008 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service invokes REST API of OOF for PCI optimization |
|
| ||||||||||||||||||||||||||||
IT#009 | OOF and Config DB (REST API) | OOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API) |
|
| ||||||||||||||||||||||||||||
IT#010 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response |
|
| ||||||||||||||||||||||||||||
IT#011 | DCAE (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) |
| |||||||||||||||||||||||||||||
IT#012 | DCAE (SON Handler MS) and Policy | SON Handler Micro-service is able to send PCI/ANR updates via DMaaP to Policy |
|
| ||||||||||||||||||||||||||||
IT#013 | Policy and DMaaP | Policy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates. |
| |||||||||||||||||||||||||||||
IT#014 | Policy and DMaaP | Policy is able to successfully receive a DMaaP message with PCI/neighbor list update response |
| |||||||||||||||||||||||||||||
IT#015 | DCAE (SON Handler MS) and Policy | SON Handler Micro-service is able to receive PCI/neighbor list update response via DMaaP from Policy, process it and logs the results. |
| |||||||||||||||||||||||||||||
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. |
| |||||||||||||||||||||||||||||
IT#017 | SDN-R | Upon receiving message from Policy, SDN-R sends netconf message to RAN-Sim. |
pending completion of 2 known issues (Medium): CCSDK-1399 and CCSDK-1400 | Will be completed when CCSDK-1399 and CCSDK-1400 are delivered.
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#018 | DCAE (VES Collector) | VES Collector receives VES messages from RAN-Simulator |
| |||||||||||||||||||||||||||||
IT#019 | SDNC SDNR (DMAAP Listener) | SDNC SDNR is able to receive DMAAP message from Policy | ||||||||||||||||||||||||||||||
IT#020 | SDNCSDNR | SDNC SDNR 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 SDNCSDNR | |||||||||||||||||||||||||||||
IT#021 | SDNCSDNR | SDNC SDNR 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 SDNCSDNR | |||||||||||||||||||||||||||||
IT#022 | SDNC SDNR & 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 SDNCSDNR/DG logs (/opt/opendaylight/current/data/log/configuration-phy-cell-id.log) or executing GET Restconf transaction from the SDNC SDNR Restconf API explorer | |||||||||||||||||||||||||||||
IT#023 | SDNC SDNR & 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 SDNCSDNR/DG logs (/opt/opendaylight/current/data/log/generic-neighbor-config.log) or executing GET Restconf transaction from the SDNC SDNR Restconf API explorer | |||||||||||||||||||||||||||||
IT#024 | SDNC SDNR & RAN simulator | RAN simulator generates Netconf notification to indicate neighbor list change notification | Prerequisite: RAN simulator is configured and Netconf mounted onto SDNCSDNR | |||||||||||||||||||||||||||||
IT#025 | SDNC SDNR & RAN simulator | SDNC SDNR after receiving Netconf notification invokes RPC handle-nbrlist-change-notif | Prerequisite: RAN simulator is configured and Netconf mounted onto SDNCSDNR | |||||||||||||||||||||||||||||
IT#026 | SDNC SDNR & 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 | SDNCSDNR/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 | |||||||||||||||||||||||||||||
...