Test Lab:
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA: https://jira.onap.org/browse/REQ-1154
E2E network slicing test
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details |
|---|---|---|---|---|---|---|---|---|
| 1. | Service/template design (Option1) | Design of CST, and necessary templates: NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | 1 | Deepika S | ||||
| 2 | Service Instantiation (Option1) | Reuse existing TN BH NSSI | 1 | At least 1 service needs to be instantiated | 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. | |||
| 3 | Service Termination (Option1) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI | 1 | Service instantiation test case involving reuse should be completed | Deepika S | 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. | ||
| 4 | Service/template design (Option2) | Design of CST, and necessary templates: NST, NSST for RAN, Core & TN, Service Profile and Slice Profiles | 1 | Option2 - TN based slices | ||||
| 5 | 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 | ||||
| 6 | 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 | ||||
| 7 | 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 | ||||
| 8 | 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 | ||||
| 9 | Service instantiation (Option 2) - Reuse existing TN BH NSSI | Reuse existing TN BH NSSI | 1 | 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. | ||||
| 10 | Service instantiation (Option 2) - Reuse existing TN MH NSSI | Reuse existing TN MH NSSI | 1 | 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. | ||||
| 11 | Service instantiation (Option 2) - Reuse existing TN FH NSSI | Reuse existing TN FH NSSI | 1 | 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. | ||||
| 12 | 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 | Malarvizhi Paramasivam | |||
| 13 | 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 | Malarvizhi Paramasivam | |||
| 14 | 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 | ||||
| 15 | 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 | ||||
| 16 | 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. | ||||
| 17 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN MH 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 MH NSSI. | ||||
| 18 | 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. |