Test Lab: Win Lab, Rutgers University
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA:
...
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Carry over test cases from Istanbul Release
...
S. No | Test Case | Description |
|---|
Dependency |
|---|
Tester | Status | Remarks | Test Details |
|---|
| 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. | IN PROGRESS | 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 | IN PROGRESS | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| |||
| 6 | Service deactivation | Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs. |
| Test case 4 should be completed | IN PROGRESS |
| Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
| ||||||
| 7 | 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 | IN PROGRESS | Base: R9 E2E Testing | CN NSSMF - ActivateNSSI WF needs to be fixed.
|
| 11 | Service Instantiation(new nsi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping in NSMF | OOF |
| Prerequisite: CPS needs to be preloaded with coverage Area TA list Base: R9 Integration Testing | UUI is having discrepancy with TA Mapping as List | |||||||||
| 14 | Service Instantiation(reuse nsi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping | OOF | COMPLETED | Prerequisite: CPS needs to be preloaded with coverage Area TA list Base: R9 Integration Testing | Below OOF Fix needs to be merged https://gerrit.onap.org/r/c/optf/has/+/131914 | |||||||||
RAN NSSMF integration test cases from Jakarta release
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 14 | RAN Slice Termination | RRM Policy update & RRMPolicyMember Removal | SDNC, CPS | COMPLETED |
|
E2E network slicing test cases from Jakarta release
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details |
|---|---|---|---|---|---|---|---|---|
| 6 | Service Activation |
with CPS (Option1) |
Activate a service - this should result in |
activation of new NSI and associated new NSSIs. | 1 | IN PROGRESS | At least 1 service needs to be instantiated | CN NSSMF - ActivateNSSI WF needs to be fixed.
|
| 7 | Service |
| deactivation with CPS (Option1) |
| Deactivate a service - this should |
| result in deactivation of new NSI and associated new NSSIs. | 1 |
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.
IN PROGRESS | At least 1 service needs to be instantiated | CN NSSMF - ActivateNSSI WF needs to be fixed.
| ||||||
| 9 | Service termination with CPS (Option1) | Terminate a service - this should terminate NSI and ALL associated NSSIs. | 1 | At least 1 service needs to be instantiated | ||||
| 10 | Service activation (Option 2) | Service activation from CSMF portal (UUI) resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 | Deepika S | IN PROGRESS | At least 1 service needs to be instantiated | External RAN NSSMF code for activate/deactivate NSSI implementation is not merged yet | |
| 11 | Service deactivation (Option 2) | Service deactivation from CSMF portal (UUI) resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 | Deepika S | IN PROGRESS | At least 1 service needs to be instantiated | External RAN NSSMF code for activate/deactivate NSSI implementation is not merged yet | |
| 12 | Service/template design (Option2) | Design of CST, and necessary templates: NST, NSST for RAN, Core & TN, Service Profile and Slice Profiles | 1 |
| Option2 - NSMF Driven TN Slices in Network Slicing | ||||||||||
| 13 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused in the response. | 1 | At least 1 service needs to be instantiated |
| Abbas Yusuf | IN PROGRESS | |||
| 14 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. | 1 | At least 1 service needs to be instantiated |
IN PROGRESS | ||||
| 15 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression) | 1 | At least 1 service needs to be instantiated |
IN PROGRESS | ||||
| 16 | Service instantiation (Option 2) - Reuse existing NSI | NSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile NOTE: This involves reuse of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated |
IN PROGRESS | |||
| 17 | Service instantiation (Option 2) - Reuse existing TN BH NSSI | Reuse existing TN BH NSSI | 1 |
IN PROGRESS | Pre-requisite: There is an existing TN BH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN BH NSSI is reused, or creating a suitable and shareable TN BH NSSI upfront. | |||
| 18 | Service instantiation (Option 2) - Reuse existing TN MH NSSI | Reuse existing TN MH NSSI | 1 |
IN PROGRESS |
| Pre-requisite: There is an existing TN MH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN MH NSSI is reused, or creating a suitable and shareable TN MH NSSI upfront. | |||
| 19 | Service instantiation (Option 2) - Reuse existing TN FH NSSI | Reuse existing TN FH NSSI | 1 |
IN PROGRESS | Pre-requisite: There is an existing TN FH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN FH NSSI is reused, or creating a suitable and shareable TN FH NSSI upfront. | |||
| 20 | Service activation (Option 2) | Service activation from CSMF portal (UUI) for Option 2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and internal RAN NSSMF NOTE: This involves activation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated |
IN PROGRESS | CN Activation not done | |||
| 21 | Service deactivation (Option 2) | Service deactivation from CSMF portal (UUI) for Option 1/2 resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards RAN, Core and Transport NSSMFs NOTE: This involves deactivation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be activated |
IN PROGRESS | CN- Deactivation not done | |||
| 22 | Service Termination (Option2) | Service termination from CSMF portal (UUI) for Option 2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated | 1 | At least 1 service needs to be instantiated |
|
| 23 | Service Termination (Option2) | SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF). NOTE: This involves termination of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated |
|
| 24 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI | 1 |
|
| This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN BH NSSI. | ||||
| 25 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN MH NSSI | 1 |
Status |
|
| This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN MH NSSI. | ||||
| 26 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN FH NSSI | 1 |
|
| This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN FH NSSI. |
E2E network slicing
...
test cases from Jakarta release (using resource occupancy details)
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 4 | Service instantiation - Reuse existing NSI (nsmf based tn slices) | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused based on the resource occupancy data received from DCAE(slice-analysis-ms). | 1 | At least 1 service needs to be instantiated | Niranjana Y |
| ||||||||||||||
| 5 | Service instantiation - Reuse existing NSI (Option1) | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused based on the resource occupancy data received from DCAE(slice-analysis-ms). | 1 | At least 1 service needs to be instantiated | Niranjana Y |
| 6 | OOF requests for resource occupancy data | OOF (HAS) should fetch the resource occupancy details from DCAE (slice-analysis-ms). | 1 | Malarvizhi Paramasivam | |||||||||
| Status | ||||||||||||||||||||
| colour | Yellow | |||||||||||||||||||
| title | inprogress | 7 | Get resource occupancy data | Slice analysis MS receives request from OOF for resource occupancy details. Slice-analysis requests DES (Data Exposure Service) for the PM data for a specific time interval, converts it into configuration data, aggregates and calculates the available resources for the requested slices and returns it back to OOF. | 1 | Niranjana Y |
| |||||||||||||
| Status | ||||||||||||||||||||
| colour | Yellow | |||||||||||||||||||
| title | inprogress | 8 | Update candidate list in HAS | HAS finds the difference between the response from DCAE and the requested config in service/slice profile and adds the difference attributes to the candidate list for the optimization based on the found difference value. | 1 | Malarvizhi Paramasivam | ||||||||||||||
| Status | ||||||||||||||||||||
| colour | Yellow | |||||||||||||||||||
| title | inprogress | 9 | Return solution to SO | HAS runs the optimization to choose the suitable NSI/NSSI. The selected NSI/NSSI is returned to OSDF, which forwards it to SO. | 1 | Malarvizhi Paramasivam |
|