Carry-over Test Cases from Jakarta Release

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 

IN PROGRESS 

Base: R9 E2E Testing

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

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 

IN PROGRESS 

Base: R9 E2E Testing

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

Service deactivation

Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs.

Test case 4 should be completed

@Deepika S 

IN PROGRESS 

Base: R9 E2E Testing

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

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 

IN PROGRESS 

Base: R9 E2E Testing

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

Service Instantiation(new nsi)

OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping in NSMF

OOF

@Malarvizhi Paramasivam 

completed

Prerequisite: CPS needs to be preloaded with coverage Area TA list

Base: R9 Integration Testing

UUI is having discrepancy with TA Mapping as List

Service Instantiation(reuse nsi)

 OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping 

OOF

@Malarvizhi Paramasivam 

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 Slice Termination

RRM Policy update & RRMPolicyMember Removal

SDNC, CPS

@Ahila P 

COMPLETED

CCSDK-3661: RAN Slice Termination - RRMPolicyupdate Closed

Service Activation with CPS (Option1)

Activate a service - this should result in activation of new NSI and associated new NSSIs.

1

@Deepika S 

IN PROGRESS

At least 1 service needs to be instantiated

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

Service deactivation with CPS (Option1)

Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs.

1

@Deepika S 

IN PROGRESS

At least 1 service needs to be instantiated

CN NSSMF - ActivateNSSI WF needs to be fixed.

SO-3838 - Error while executing core NSSMF activate flow OPEN

Service termination with CPS (Option1)

Terminate a service - this should terminate NSI and ALL associated NSSIs.

1

@Deepika S 

At least 1 service needs to be instantiated

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

https://gerrit.onap.org/r/c/integration/+/127465

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

https://gerrit.onap.org/r/c/integration/+/127465

Service/template design (Option2)

Design of CST, and necessary templates: NST, NSST for RAN, Core & TN, Service Profile and Slice Profiles

1

@sravya sherla 

completed

Option2 - NSMF Driven TN Slices in Network Slicing

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

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

 @Abbas Yusuf 

IN PROGRESS

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

@Abbas Yusuf 

IN PROGRESS

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

@Abbas Yusuf  

IN PROGRESS

Service instantiation (Option 2) - Reuse existing  TN BH NSSI

Reuse existing TN BH NSSI

1

@Abbas Yusuf  

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.

Service instantiation (Option 2) - Reuse existing  TN MH NSSI

Reuse existing TN MH NSSI

1

@Abbas Yusuf  

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.

Service instantiation (Option 2) - Reuse existing  TN FH NSSI

Reuse existing TN FH NSSI

1

@Abbas Yusuf  

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.

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

@Abbas Yusuf 

IN PROGRESS

CN Activation not done

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

@Abbas Yusuf  

IN PROGRESS

CN- Deactivation not done

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

@Abbas Yusuf  

completed

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

@Abbas Yusuf  

completed

Service Termination (Option2)

Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI

1

@Abbas Yusuf  

in progress

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.

Service Termination (Option2)

Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN MH NSSI

1

@Abbas Yusuf  

in progress

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.

Service Termination (Option2)

Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN FH NSSI

1

@Abbas Yusuf  

in progress

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.

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 

in progress

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 

completed

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 

COMPLETED