Integration Test of RAN NSSMF
Test Lab: Win Lab, Rutgers University
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA: https://jira.onap.org/browse/REQ-1151
RAN NSSMF integration test
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details | |
---|---|---|---|---|---|---|---|---|---|
1 | Service/template design | Successful design of RAN NSST, RAN NF NSST, TN MH NSST, TN FH NSST, RAN Slice Profile, RAN NF Slice Profile, TN MH Slice Profile, TN FH Slice Profile Templates | 1 | @Deepika S | COMPLETED | ||||
2 | Service instantiation (Option 1) - New NSI, new TN FH NSSI | When triggered by RAN NSSMF with allocateNSSI for allocating a TN FH NSSI, SO (TN NSSMF) triggers OOF for TN NSSI selection, OOF provides null solutions(i.e., suitable and shareable TN FH NSSI not available) and the allocate WF should process with creation of new TN FH NSSI. | 1 | @Deepika S | COMPLETED | ||||
3 | Service instantiation (Option 1) - New NSI, new TN MH NSSI | When triggered by RAN NSSMF with allocateNSSI for allocating a TN MH NSSI, SO (TN NSSMF) triggers OOF for TN NSSI selection, OOF provides null solutions(i.e., suitable and shareable TN MH NSSI not available) and the allocate WF should process with creation of new TN MH NSSI. | 1 | @Deepika S | COMPLETED | ||||
4 | Service instantiation (Option 1) - New NSI, reuse TN MH NSSI | Reuse existing TN MH NSSI | 1 | @Deepika S | COMPLETED | 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. | |||
5 | Service instantiation (Option 1) - New NSI, reuse TN FH NSSI | Reuse existing TN FH NSSI | 1 | @Deepika S | COMPLETED | 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. | |||
6 | Service Termination (Option1) | When triggered by RAN NSSMF with DeallocateNSSI for deallocating existing TN FH NSSI, SO (TN NSSMF) triggers OOF for terminate call, OOF returns whether the NSSI should be terminated or not. If it returns TN FH NSSI can be terminated and the WF should process with deallocation of existing TN FH NSSI. | 1 | @Deepika S | COMPLETED | ||||
7 | Service Termination (Option1) | When triggered by RAN NSSMF with DeallocateNSSI for deallocating existing TN MH NSSI, SO (TN NSSMF) triggers OOF for terminate call, OOF returns whether the NSSI should be terminated or not. If it returns TN MH NSSI can be terminated and the WF should process with deallocation of existing TN MH NSSI. | 1 | @Deepika S | COMPLETED | ||||
8 | Service Termination (Option1) | This should terminate TOP RAN NSSI but terminate only RAN NF NSSI and TN FH NSSI, and not TN MH NSSI | 1 | @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 NSSIs, but > 1 Slice Profile is linked to TN MH NSSI. | Modify deallocate operation is not supported yet, TN NSSMF will update the status as completed without modifying/deallocating the NSSI | ||
9 | Service Termination (Option1) | This should terminate TOP RAN NSSI but terminate only RAN NF NSSI and TN MH NSSI, and not TN FH NSSI | 1 | @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 NSSIs, but > 1 Slice Profile is linked to TN FH NSSI. | Modify deallocate operation is not supported yet, TN NSSMF will update the status as completed without modifying/deallocating the NSSI | ||
10 | RAN Slice allocation with CPS (Option1) | Request trigger from RAN NSSMF should create a RAN Slice in ran-network | 1 | SO (RAN NSSMF), SDNC, RAN Simulator, CPS | @Ahila P | COMPLETED | |||
11 | RAN Slice allocation with CPS (Option1) | Verify the RAN Slice allocation in RAN Simulator | 1 | SO (RAN NSSMF), SDNC, RAN Simulator, CPS | @Ahila P | COMPLETED | |||
12 | RAN Slice allocation with CPS (Option1) | Verify the RAN slice Configuration update in CPS | 1 | SO (RAN NSSMF), SDNC, RAN Simulator, CPS | @Ahila P | COMPLETED | |||
13 | RAN slicing with CPS | Yang model upload to CPS using DML Plugin | 1 | SDNC, CPS | @Niranjana Y | COMPLETED | This test case work with the CPS component installed in K8 cluster using helm chart. | ||
14 | RAN Slice Termination | RRM Policy update & RRMPolicyMember Removal | SDNC, CPS | @Ahila P | DEFERRED |