Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira reference: 
Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-631

Test lab: CMCC Lab

Summary: Option 2 test cases, and many of the regression test cases are deferred to Istanbul. The functionality as working in Guilin can be expected to work for these scenarios. Service termination testing is also deferred to Istanbul.

Legend:

NOT STARTED IN PROGRESS DEFERRED COMPLETED

Italics - Regression test cases

S. No.TopicTest Case DescriptionPriorityDependency/IssueTesterStatusRemarks
NSMF_01Service/template designSuccessful design of CST and Service Profile Templates1
StatuscolourGreytitleNOT STARTED

COMPLETED


NSMF_02Service/template designSuccessful design of NST (option
1 and option
2)1
StatuscolourGreytitleNOT STARTED

COMPLETED


NSMF_03Service instantiationService instantiation via CSMF Portal (UUI) for Option 1/2 resulting in NST Selection request from SO towards OOF, and receiving the NST details in the callback from OOF. Note:
 
Since OOF fetches NST details from SDC, there is no need for any manual configuration to onboard templates in a flat file.1

COMPLETED


NSMF_10
1NSMF_04Service instantiation (Option 1)After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 1.2NSMF_01
Service instantiation (Option
1
2) - New NSINSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option
1
2). Note: In the RAN Slice Profile, coverageAreaTAList shall contain a valid list of TAs corresponding to the coverageArea provided by the user (and passed in the Service Profile by SO (NSMF) to OOF
).1NSMF_02Service instantiation (Option 1) - New NSISO (NSMF) presents the NSI solution to NSMF Portal (UUI) for manual intervention. NSMF Portal (UUI) provides endpoints for RAN and Core sub-nets while allowing creation of new NSI
) - see Remarks.1
NSMF_03Service instantiation (Option 1) - New NSINSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSI is allocated successfully.1NSMF_04Service instantiation (Option 1) - New NSINSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully.1NSMF_01Service instantiation (Option 1) - New NSINSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully.1NSMF_02

COMPLETED


NSMF_11Service instantiation (Option 2) - New NSI
After NST selection,
NSMF (SO)
fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 2.4NSMF_03Service instantiation (Option 2) - New NSINSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 2).4NSMF_04Service instantiation (Option 2) - New NSINSMF (SO)
calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides (empty) response that no RAN NSSI exists (that can be reused).
4
1

DEFERRED

Option 2 regression testing is deferred to Istanbul
NSMF_
01
12Service instantiation (Option 2) - New NSINSMF (SO) triggers External RAN NSSMF with allocateNSSI operation via the NSSMF adaptor (it also sends Slice Profile info), and new RAN NSSI is created successfully. RAN EP info is updated in AAI by NSMF Adaptor.
1

DEFERRED

Option 2 regression testing is deferred to Istanbul
4
NSMF_
02
13Service instantiation (Option 2) - New NSINSMF (SO) triggers (external) Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully.
(This is more of a regression test case as new Core NSSI is already covered in COM_08)
1

DEFERRED

Option 2 regression testing is deferred to Istanbul
NSMF_14
41NSMF_03
Service instantiation (Option 2) - New NSINSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully.
 (This is more of a regression test case as new TN NSSI is already covered in COM_09)4
1
NSMF_04Service instantiation (Option 1) - New NSINSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSMF responds that an existing RAN NSSI can be reused.52NSMF_01Service instantiation (Option 1) - New NSINSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSMF responds that an existing Core NSSI can be reused.52

DEFERRED

Option 2 regression testing is deferred to Istanbul
NSMF_15
NSMF_02
Service instantiation (Option 2) - New NSINSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides response with a suitable RAN NSSI exists (that can be reused).
 1

DEFERRED

Option 2 testing is deferred to Istanbul
NSMF_16Service instantiation (Option 2) - New NSINSMF (SO) triggers External RAN NSSMF with modifyNSSI operation via the NSSMF adaptor (it also sends info of NSSI to be reused), and RAN NSSI is updated successfully. RAN EP info is updated in AAI by NSMF Adaptor.1

DEFERRED

Option 2 testing is deferred to Istanbul
NSMF_17
62NSMF_03
Service instantiation (Option 1) - Reuse existing NSINSMF (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

Status
colourGreen
titleCOMPLETED

72


NSMF_
04
18Service instantiation (Option 1) - Reuse existing NSINSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles
7
.1

Status
colourGreen
titleCOMPLETED

A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT.
2
NSMF_
01
19Service instantiation (Option 1) - Reuse existing NSINSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression)
7
1

Status
colourGreen
titleCOMPLETED

2


NSMF_
02
20Service instantiation (Option 1) - Reuse existing NSINSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile
1

Status
colourGreen
titleCOMPLETED

72


NSMF_
03
21

Service instantiation (Option 2) - Reuse existing NSI

(similar to testcases COM_17 and 18)

NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing existing NSI to be reused in the response. 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.
8
1
2

DEFERRED

Option 2 testing is deferred to Istanbul
NSMF_22
NSMF_04Service instantiation (Option 1) - Reuse existing NSINSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression)82NSMF_01

Service instantiation (Option 2) - Reuse existing NSI

(similar to testcase COM_20)

NSMF then calls modifyNSSI API towards
internal
Core and Transport NSSMFs, and external RAN NSSMF with details of NSI to be reused and the respective Slice Profile
1

DEFERRED

Option 2 testing is deferred to Istanbul
82
NSMF_
02
23Service activation (Option 1)

Service activation from CSMF portal (UUI) for Option 1/2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards RAN, Core and Transport NSSMFs

1
9

DEFERRED

This regression testing is deferred to Istanbul
2
NSMF_
03
24Service activation (Option 2)Service activation from CSMF portal (UUI) for Option 1/2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF1
9

DEFERRED

Option 2 testing is deferred to Istanbul
NSMF_
04
25Service deactivation (Option 1)

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

1
10

DEFERRED

This regression testing is deferred to Istanbul
2
NSMF_
01
26Service deactivation (Option 2)Service deactivation from CSMF portal (UUI) for Option 1/2 resulting in NSI Dectivation API called towards SO (NSMF). SO (NSMF) calls deactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF1
10

DEFERRED

Option 2 testing is deferred to Istanbul
NSMF_
02
27Service termination (Option 1/2)Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should not be terminated
11
1

DEFERRED

Service termination testing is deferred to Istanbul as this also requires e2e testing
2
NSMF_
03
28Service termination (Option 1/2)SO (NSMF) triggers RAN, Core and TN NSSMF with modifyNSSI API to remove S-NSSAI from the respective NSSIs. Service and Slice profiles and their links are also removed.
1

DEFERRED

Service termination testing is deferred to Istanbul as this also requires e2e testing
112
NSMF_
04
29Service termination (Option 1)Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated
122
2

DEFERRED

Service termination testing is deferred to Istanbul as this also requires e2e testing
NSMF_30
COM_31
Service termination (Option 1)SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF).2
12

DEFERRED

Service termination testing is deferred to Istanbul as this also requires e2e testing
2