...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Legend:
Legend
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA:
...
https://jira.onap.org/browse/REQ-1149
| S.No | Topic | Description | Dependency | Tester | Status | Remarks | Test Details | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Service termination (Option 1) | SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF). | COMPLETED | CN NSSMF - deallocateNSSI WF has been fixed , not yet and merged (https://gerrit.onap.org/r/c/so/+/127018) | |||||||||||
| 2 | Service Deallocate (Terminate NSSI) | When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI | COMPLETED | When I execute Modify with creation of SliceProfile flow, and then execute Deallocate without termination, then OOF returns "Associated to more than one" reason and terminationResponse is false. That's correct behavior. During Deallocate without termination flow I remove association with Slice Profile and the Slice Profile itself. Then when I execute the Deallocate with termination flow I get also terminationResponse is false with a reason "not available in AAI" response. However, NSSI can be queried in AAI without any issue. Waiting for OOF fix. | Used request: DELETE http://{{so}}:30277/onap/so/infra/3gppservices/v1/deAllocate { | ||||||||||
| 3 | Service instantiation with manual intervention | For scenario (c) in below table, operator shall override via NSMF portal in UUI the selection of reusable NSI and indicate creation of new NSI. | (c) for service instantiation should work first | Deepika S | COMPLETED | Base: R9 E2E Testing | |||||||||
| 4 | Service activation | Activate a service - this should result in activation of new NSI and associated new NSSIs. | (a) or (b) for service instantiation should work first. | Deepika S | COMPLETEDDEFERRED | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| ||||||||
| 5 | Activate a service - this should result in activation of S-NSSAI, and the activate command should pass to all the NSSMFs | (c) for service instantiation should work first | Deepika S | COMPLETEDDEFERRED | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| |||||||||
| 6 | Service deactivation | Dectivate Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs. | Test case 4 should be completed | Deepika S | COMPLETEDDEFERRED | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| ||||||||
| 7 | Dectivate Deactivate a service - this should result in deactivation of S-NSSAI, and the deactivate command should pass to all the NSSMFs | Test case 5 should be completed | Deepika S | COMPLETEDDEFERRED | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| |||||||||
| 8 | Service termination | Terminate a service - this should terminate NSI and ALL associated NSSIs. Note: The proper configuration updates should be sent to the RAN NFs. | At least 1 service instantiation test case should be completed | Deepika S | COMPLETED | CN NSSMF - deallocateNSSI WF has been fixed , not yet and merged (https://gerrit.onap.org/r/c/so/+/127018) Base: R9 E2E Testing | |||||||||
| 9 | Service termination | Terminate a service - this should terminate NSI but terminate only Core NSSI and TN BH NSSI, and not RAN NSSI (Assumption: RAN NSSI not terminated => RAN NF NSSI not terminated, TN FH and MH NSSIs not terminated) Note: The proper configuration updates should be sent to the RAN NFs and TN NSSMF (for FH and MH NSSIs, using modifyNSSI API). | At least 1 service instantiation test case involving reuse should be completed | Deepika S | COMPLETED | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to Core & TN BH NSSIs, but > 1 Slice Profile is linked to RAN NSSI. CN NSSMF - deallocateNSSI WF has been fixed not yet and merged (https://gerrit.onap.org/r/c/so/+/127018) Base: R9 E2E Testing | |||||||||
| 10 | Service termination | Terminate a service - this should terminate NSI but not terminate only Core NSSI and , TN BH NSSI , and not RAN NSSI (Assumption: RAN NSSI not terminated => RAN NF NSSI not terminated, TN FH and MH NSSIs not terminated) Note: The proper configuration updates should be sent to the RAN NFs, Core NFs and TN NSSMF (for FH and MH NSSIs, using modifyNSSI API). | At least 1 service instantiation test case involving reuse should be completed | Deepika S | COMPLETED | This can happen when only 1 Service Profile is linked to NSI and > 1 Slice Profile each is linked to RAN, Core & TN BH NSSIs. CN NSSMF - deallocateNSSI WF has been fixed , not yet and merged (https://gerrit.onap.org/r/c/so/+/127018) Base: R9 E2E Testing | |||||||||
| 11 | Service Instantiation(new nsi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping in NSMF | OOF | Malarvizhi Paramasivam | DEFERRED | Prerequisite: CPS needs to be preloaded with coverage Area TA list Base: R9 Integration Testing | UUI is having discrepancy with TA Mapping as List | ||||||||
| 12 | Service Instantiation(new ran nssi) | SDNR integration with CPS - allocate flow: CPS should be updated with the RAN configurations | SDN-R, CPS | COMPLETED | TBDMT templates should be preloaded Base: R9 Integration Testing | This will be tracked under J-release test cases as the relevant implementation is targeted for J-release | |||||||||
| 13 | Service Instantiation (new RAN NSSI) | SDN-R configures RAN NFs via O1. All NFs and the cells should be updated with the proper configuration | SDN-R, CPS, RANSimulator | COMPLETED | Base: R9 Integration Testing | This will be tracked under J-release test cases as the relevant implementation is targeted for J-release | |||||||||
| 14 | Service Instantiation(reuse nsi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping | OOF | Malarvizhi Paramasivam | DEFERRED | Prerequisite: CPS needs to be preloaded with coverage Area TA list Base: R9 Integration Testing | UUI is having discrepancy with TA Mapping as List | ||||||||
| 15 | Service Activation | Required details should be properly queried from CPS | SDN-R, CPS | YASHWANTH GANDHAPU | COMPLETED | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS Base: R9 Integration Testing | |||||||||
| 16 | Service Activation | RAN Slice should be activated: status should be set to ACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | YASHWANTH GANDHAPU | COMPLETED | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator Base: R9 Integration Testing | |||||||||
| 17 | Service Deactivation | Required details should be properly queried from CPS | SDN-R, CPS | YASHWANTH GANDHAPU | COMPLETED | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS Base: R9 Integration Testing | |||||||||
| 18 | Service Deactivation | RAN Slice should be deactivated: status should be set to INACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | YASHWANTH GANDHAPU | COMPLETED | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator Base: R9 Integration Testing | |||||||||
| 19 | Closed Loop | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim. | Niranjana Y | COMPLETED | Base: R9 Integration Testing | This will be tracked under J-release test cases as the relevant implementation is targeted for J-release | |||||||||
| 20 | Reconfigure | RAN-Sim updates DB and netconf servers. | Niranjana Y | COMPLETED | Base: R9 Integration Testing | This will be tracked under J-release test cases as the relevant implementation is targeted for J-release | |||||||||
...