Showcase VNF | Test Environment | Integration Team Liaison |
|---|---|---|
| Rutgers Winlab ONAP Wireless Lab |
| Component/Activity | Responsible(s) |
|---|---|
Overall Point of Contact, Use case scope and content | N.K. Shankaranarayanan (AT&T), Swaminathan Seetharaman (Wipro) |
| ConfigDB | |
| DCAE | |
| OOF | |
| Policy | mehreen kaleem |
| SDN-R | Sandeep Shah |
| RAN-Simulator | Saravanan Ayyadurai |
| Winlab Setup | George Clapp |
| E2E Use case setup/config | |
| Integration Testing |
Development Status & High-Level Requirements
| Project | PTL | JIRA Epic / User Story* | Requirements |
|---|---|---|---|
| AAI |
| ||
| DCAE |
|
| |
| OOF |
|
| |
| Policy | EPIC POLICY-1438 US POLICY-1463: US POLICY-1464: | EPIC POLICY-1438
| |
| SDC |
| ||
| SDNC | (Carryover items from Dublin) -SDNC-430: Modify RAN informational model and yang model for RAN |
| |
| (RANSim) |
|
*Each Requirement should be tracked by its own User Story in JIRA
APIs
There are two inter-module API specifications in this use case. Both were defined for Casablanca and there will be enhancements done for Dublin release.
(Note: The API from the SON Handler MS to the FM/PM Database is internal to DCAE and the API is not exposed.)
(a) OOF API for PCI:
Link to API spec on OOF page: PCI Optimization API
Link to OOF Impacts page for Dublin enhancments: OOF Impacts
(b) Config DB API:
Link to Config DB spec: https://wiki.onap.org/download/attachments/28382769/SDNC_ConfigDB_API_Ver2.json?api=v2 (Nov 2018)
Link to Config DB page for Dublin enhancements: Config DB Impacts
Integration Testing
Note: The OOF-PCI use case implementation and testing will be done at the Rutgers University Winlab ONAP Wireless Lab. Access is available to interested ONAP members.
Please see this page for details: Open Wireless Laboratory (OWL) at Wireless Information Network Laboratory (WINLAB)
Note: DMaaP should be setup for most of the test cases below.
| # | Component(s) | Test Case | Status | Remarks |
|---|---|---|---|---|
| 1 | DCAE (SON Handler MS) | SON Handler Micro-service successfully on-boarded on to DCAE | NOT YET TESTED | |
| 2 | DCAE (SON Handler MS) | SON Handler Micro-service's DB is up and the Micro-service is able to read/write data. | NOT YET TESTED | |
| 3 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully fetch config policies from Consul. | ||
| 4 | OOF and Policy | OOF is able to successfully fetch config policy from Policy | NOT YET TESTED | |
| 5 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully receive a message over DMaaP containing PM/FM data (from VES Collector) | NOT YET TESTED | |
| 6 | DCAE (SON Handler MS) and SDN-R | SON Handler Micro-service is able to successfully receive a message over DMaaP containing neighbor list update (from SDN-R) | NOT YET TESTED | |
| 7 | DCAE (SON Handler MS) and Config DB | SON Handler Micro-service is able to successfully fetch neighbor list details from Config DB. | NOT YET TESTED | |
| 8 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service invokes REST API of OOF for PCI optimization and receives response from OOF | NOT YET TESTED | |
| 9 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service invokes REST API of OOF for PCI optimization and receives response from OOF | NOT YET TESTED | |
| 10 | OOF and Config DB | OOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API) | NOT YET TESTED | |
| 11 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response | NOT YET TESTED | |
| 12 | DCAE (SON Handler MS) and Config DB | SON Handler Micro-service is able to successfully fetch PNF details from Config DB | NOT YET TESTED | |
| 13 | DCAE (SON Handler MS) and Policy | SON Handler Micro-service is able to send PCI/neighbor list updates via DMaaP to Policy | NOT YET TESTED | |
| 14 | Policy and SDN-R | Policy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates. | NOT YET TESTED | |
| 15 | Policy and SDN-R | Policy is able to successfully receive a DMaaP message (fromSDN-R) with PCI/neighbor list update response | NOT YET TESTED | |
| 16 | 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 trigger necessary actions | NOT YET TESTED | |
17 | DCAE (SON Handler MS) | SON Handler Micro-service is able to process FM KPI data, store as needed, and apply rules to recommend removal of a neighbor relationship. | NOT YET TESTED | |
| 18 | ConfigDB | ConfigDB established with Dublin enhancements | NOT YET TESTED | |
| 19 | SDN-R | SDN-R receives netconf notification, updates ConfigDB for neighbor list change | NOT YET TESTED | |
| 20 | SDN-R | Upon receiving message from Policy, SDN-R sends netconf message to RAN-Sim. | NOT YET TESTED | |
| 21 | DCAE (Collector) | VES Collector receives VES message from RAN-Simulator | NOT YET TESTED | |
| 22 | DCAE (SON-Handler MS), Config DB | (Stretch goal) ConfigDB has new cells marked as "Pending-activation". SON Handler MS receives and responds to query to find PCI allocation for new cells. | NOT YET TESTED | |
Use Case Testing - End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
| # | Test Case | Status |
|---|---|---|
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |