Carry-over tests from H-release

Owned by Swaminathan Seetharaman
Last updated: Oct 20, 2021 by Ahila P
6 min read

Legend:

NOT STARTED IN PROGRESS DEFERRED COMPLETED

Carry over tests from H-release

Reference: Pl. see the child pages of Integration Test details for Honolulu for tests deferred to each track.

S.No

Topic

Description

Dependency

Tester

Status

Remarks

Test details
NSMF_15Service 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). 

Deepika S


COMPLETED



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.

Deepika S


COMPLETED



NSMF_17Service instantiation (Option 1) - Reuse existing NSI (Regression)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.

Deepika S

COMPLETED

A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT.
NSMF_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.

Deepika S

COMPLETED

A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT.
NSMF_21

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 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.

Deepika S


COMPLETED



NSMF_22

Service instantiation (Option 2) - Reuse existing NSI

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

COMPLETED

External AN NSSMF modify call is handled by NSSMF Adapter.

External CN NSSMF- modify NSSI using NSSI Id


NSMF_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

Deepika S

COMPLETED



NSMF_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.

Deepika S

DEFERRED

Deferred to next release. TN NSSMF doesn't support modify deallocate yet. So this scenario triggers deallocate NSSI API of RAN, CORE and TN NSSMF.
NSMF_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

Deepika S

COMPLETED



NSMF_30Service termination (Option 1)SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF).
Deepika S

DEFERRED



CN NSSMF - deallocateNSSI WF needs to be fixed
RAN_14Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls SO (TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles using modifyNSSI API.

Deepika S

COMPLETED

This test case is only partially completed. So, it is deferred to Istanbul
RAN_15Service instantiation (Option 1) - Reuse existing NSI

When triggered by NSSMF Adaptor with modifyNSSI for reusing an existing NSI, SO (RAN NSSMF) triggers OOF for obtaining the Slice Profiles of RAN NF, TN FH and TN MH subnets for updating the respective NSSIs. Slice Profile details are then updated in AAI.

(Remaining flows are similar to test cases RAN_11 to RAN_14)


Deepika S

COMPLETED

This test case is only partially completed. So, it is deferred to Istanbul
RAN_23Service termination (Option 1)SDN-R makes relevant updates to ConfigDB (removal of S-NSSAI and RAN NF Slice Profile, RRM Policy update)

Hariharan Ramanathan

COMPLETED

This test case is partially completed (Slice Profile removal is not yet checked). So it is deferred to Istanbul.
RAN_24Service termination (Option 1)SDN-R sends relevant (netconf) messages to RAN-NFs (CUs, DUs, Near-RT RICs) of S-NSSAI removal, and update of RRM Policy, etc.

Hariharan Ramanathan

COMPLETED

This test case is partially completed - there are some minor issues in RAN-Sim.
RAN_25Service termination (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) for updating the TN FH and TN MH NSSIs. Slice Profiles of TN FH and MH NSSIs are also removed.TN NSSMF

Deepika S

DEFERRED

Deferred to next release. TN NSSMF doesn't support modify deallocate yet
RAN_26Service termination (Option 1)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases RAN_22 to RAN_25)


Deepika S

COMPLETED



RAN_27Service termination (Option 1)When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should be terminated.

Deepika S

COMPLETED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested


RAN_28Service termination (Option 1)SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should be terminated.

Deepika S

COMPLETED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_29Service termination (Option 1)

SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI and RAN NF NSSI are also removed.

(SDN-R actions are covered in test cases RAN_23 and RAN_24)


Deepika S

COMPLETED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_30Service termination (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs

Deepika S

COMPLETED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_31Service termination (Option 1)

When OOF returns that RAN NSSI should be terminated, SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should not be terminated.

(RAN NF NSSI update actions are covered by RAN_22 to RAN_24, and TN FH and MH NSSI actions are covered by RAN_30)


Deepika S

COMPLETED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
CORE_06Service Deallocate (with no NSSI termination)When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI
Alex Borovitzky

COMPLETED

Deferred to Istanbul release

Used request: 

DELETE http://{{so}}:30277/onap/so/infra/3gppservices/v1/deAllocate

{
  "name": "nssi_CN_NSST",
  "serviceInstanceID": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
  "networkType": "cn",
  "globalSubscriberId": "5GCustomer",
  "subscriptionServiceType": "5G",
  "additionalProperties": {
    "sliceProfileId": "705998ac-f513-11eb-9a03-0242ac130003",
    "nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628"
  }
}


Gerrit change: https://gerrit.onap.org/r/c/so/+/122554

CORE_07Service Deallocate (Terminate NSSI)When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI
Alex Borovitzky

DEFERRED

Deferred to Istanbul release

When I execute Modify with creation of SliceProfile flow, and then execute Deallocate without termination, then OOF returns "Associated to more than one" reason and terminationResponse is false. That's correct behavior.

During Deallocate without termination flow I remove association with Slice Profile and the Slice Profile itself.

Then when I execute the Deallocate with termination flow I get also terminationResponse is false with a reason "not available in AAI" response.

However, NSSI can be queried in AAI without any issue. Waiting for OOF fix.

Used request: 

DELETE http://{{so}}:30277/onap/so/infra/3gppservices/v1/deAllocate

{
  "name": "nssi_CN_NSST",
  "serviceInstanceID": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
  "networkType": "cn",
  "globalSubscriberId": "5GCustomer",
  "subscriptionServiceType": "5G",
  "additionalProperties": {
    "sliceProfileId": "705998ac-f513-11eb-9a03-0242ac130003",
    "nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628"
  }
}

CORE_04Service instantiation (Existing NSSI)When triggered by NSSMF Adaptor with allocateNSSI for allocating a new Core NSSI, Core NSSMF (SO) triggers OOF for Core NSSI selection, OOF provides returns existing Core NSSI.
Aleem Raja

COMPLETED

For shared-NSSI, updates to be done in SO. The code updates is expected to be part of Honululu_MNT (SO-3605). A note will be added to Honolulu release documentation.


Used request for allocate flow 
{
	"name": "CN_NSST",
	"modelInvariantUuid": "8ebba719-f815-47e3-8473-c5f0db801356",
	"modelUuid": "70e2b55b-8dca-4ff3-8f47-374c2965b731",
	"globalSubscriberId": "5GCustomer",
	"subscriptionServiceType": "5G",
	"networkType": "cn",
	"sst": null,
	"additionalProperties": {
		"sliceProfile": {
			"snssaiList": ["01-5B179BD4"],
			"sliceProfileId": "1c7046f2-a5a3-4d7f-9da8-388ee641a795",
			"plmnIdList": ["39-00"],
			"maxNumberOfUEs": 1000,
			"coverageAreaTAList": ["1", "2", "3", "4"],
			"latency": 2,
			"resourceSharingLevel": "non-shared"
		},
		"endPoint": {
			"ipAddress": "10.120.1.34",
			"logicInterfaceId": "123456",
			"nextHopInfo": "123456"
		},
		"nsiInfo": {
			"nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628",
			"nsiName": "nsi_NSTO1"
		},
		"scriptName": "AN1"
	}
}


request sent to oof: 
{
	"apiPath": "/api/oof/selection/nssi/v1",
	"requestDetails": "{\"requestInfo\":{\"transactionId\":\"2d50bc2b-8de7-4f39-9967-50883df10d8c\",\"requestId\":\"2d50bc2b-8de7-4f39-9967-50883df10d8c\",\"callbackUrl\":\"http://so-oof-adapter.onap:8090/so/adapters/oof/callback/v1/cn/2d50bc2b-8de7-4f39-9967-50883df10d8c\",\"sourceId\":\"SO\",\"timeout\":600,\"numSolutions\":1},\"NSSTInfo\":{\"UUID\":\"70e2b55b-8dca-4ff3-8f47-374c2965b731\",\"invariantUUID\":\"8ebba719-f815-47e3-8473-c5f0db801356\",\"name\":\"CN_NSST\"},\"sliceProfile\":{\"plmnIdList\":[\"39-00\"],\"sliceProfileId\":\"1c7046f2-a5a3-4d7f-9da8-388ee641a795\",\"latency\":2,\"maxNumberOfUEs\":1000,\"snssaiList\":[\"01-5X179YZ4\"],\"coverageAreaTAList\":[\"1\",\"2\",\"3\",\"4\"],\"resourceSharingLevel\":\"shared\"}}"
}
oof response 
{
	"requestId": "2d50bc2b-8de7-4f39-9967-50883df10d8c",
	"transactionId": "2d50bc2b-8de7-4f39-9967-50883df10d8c",
	"requestStatus": "completed",
	"statusMessage": "",
	"solutions": [{
		"UUID": "70e2b55b-8dca-4ff3-8f47-374c2965b731",
		"invariantUUID": "8ebba719-f815-47e3-8473-c5f0db801356",
		"NSSIName": "nssi_CN_NSST",
		"NSSIId": "11c0c52a-d748-48aa-86e3-c783cbf5026f"
	}]
}




OOF returns existing NSSI. Find the associated network service with NSSI
Aleem Raja

COMPLETED

For shared-NSSI, updates to be done in SO. The code updates is expected to be part of Honululu_MNT (SO-3605). A note will be added to Honolulu release documentation.
  • Used same Request for shared flow as above.
  • From OOF we get NSSI and from NSSI Id we fetch associated network service form AAI which has ComposedOf relationship with NSSI
  • Note: For now, for network service, there is no service-role.
AAI Response for NSSI 
{
	"service-instance-id": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
	"service-instance-name": "nssi_CN_NSST",
	"service-type": "5G",
	"service-role": "nssi",
	"environment-context": "General_Revenue-Bearing",
	"workload-context": "Production",
	"model-invariant-id": "8ebba719-f815-47e3-8473-c5f0db801356",
	"model-version-id": "70e2b55b-8dca-4ff3-8f47-374c2965b731",
	"resource-version": "1626325035666",
	"orchestration-status": "activated",
	"service-function": "shared",
	"relationship-list": {
		"relationship": [{
			"related-to": "service-instance",
			"relationship-label": "org.onap.relationships.inventory.ComposedOf",
			"related-link": "/aai/v23/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G/service-instances/service-instance/1c7046f2-a5a3-4d7f-9da8-388ee641a795",
			"relationship-data": [{
				"relationship-key": "customer.global-customer-id",
				"relationship-value": "5GCustomer"
			}, {
				"relationship-key": "service-subscription.service-type",
				"relationship-value": "5G"
			}, {
				"relationship-key": "service-instance.service-instance-id",
				"relationship-value": "1c7046f2-a5a3-4d7f-9da8-388ee641a795"
			}],
			"related-to-property": [{
				"property-key": "service-instance.service-instance-name",
				"property-value": "CN_SliceProfile_1c7046f2"
			}]
		}, {
			"related-to": "service-instance",
			"relationship-label": "org.onap.relationships.inventory.ComposedOf",
			"related-link": "/aai/v23/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G/service-instances/service-instance/de6a0aa2-19f2-41fe-b313-a5a9f159acd7",
			"relationship-data": [{
				"relationship-key": "customer.global-customer-id",
				"relationship-value": "5GCustomer"
			}, {
				"relationship-key": "service-subscription.service-type",
				"relationship-value": "5G"
			}, {
				"relationship-key": "service-instance.service-instance-id",
				"relationship-value": "de6a0aa2-19f2-41fe-b313-a5a9f159acd7"
			}],
			"related-to-property": [{
				"property-key": "service-instance.service-instance-name",
				"property-value": "ns_fiveg_11c0c52a-d748-48aa-86e3-c783cbf5026f"
			}]
		}, {
			"related-to": "allotted-resource",
			"relationship-label": "org.onap.relationships.inventory.Uses",
			"related-link": "/aai/v23/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G/service-instances/service-instance/e7ace67c-6cce-4b65-84ae-eb594858aa87/allotted-resources/allotted-resource/293d348d-7b5e-4fce-adb8-732b5de45eab",
			"relationship-data": [{
				"relationship-key": "customer.global-customer-id",
				"relationship-value": "5GCustomer"
			}, {
				"relationship-key": "service-subscription.service-type",
				"relationship-value": "5G"
			}, {
				"relationship-key": "service-instance.service-instance-id",
				"relationship-value": "e7ace67c-6cce-4b65-84ae-eb594858aa87"
			}, {
				"relationship-key": "allotted-resource.id",
				"relationship-value": "293d348d-7b5e-4fce-adb8-732b5de45eab"
			}],
			"related-to-property": [{
				"property-key": "allotted-resource.description"
			}, {
				"property-key": "allotted-resource.allotted-resource-name"
			}]
		}]
	}
}
CORE_08Service Modify (create Slice Profile Instance)When triggered by NSSMF Adaptor with modify for modifying Core NSSI
Alex Borovitzky

COMPLETED

Deferred to Istanbul release

Used request:

PUT http://{{so}}:30277/onap/so/infra/3gppservices/v1/modify

{
  "name": "nssi_CN_NSST",
  "globalSubscriberId": "5GCustomer",
  "subscriptionServiceType": "5G",
  "networkType": "cn",
  "serviceInstanceID": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
  "additionalProperties": {
    "sliceProfile": {
        "snssaiList": ["01-5B179BD4"],
        "sliceProfileId": "12d23796-e273-11eb-ba80-0242ac130004",
        "plmnIdList": ["39-00"],
        "maxNumberOfUEs": 1000,
        "coverageAreaTAList": ["1", "2", "3", "4"],
        "latency": 2,
        "sST": "eMBB"
    },
    "nsiInfo": {
      "nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628",
      "nsiName": "nsi_NSTO1"
    },
    "isCreateSliceProfileInstance": "true"
  }
}


Gerrit change: https://gerrit.onap.org/r/c/so/+/122554

CORE_09Service Modify (delete Slice Profile Instance)When triggered by NSSMF Adaptor with modify for modifying Core NSSI
Alex Borovitzky

COMPLETED

Deferred to Istanbul release

Used request:

PUT http://{{so}}:30277/onap/so/infra/3gppservices/v1/modify

{
  "name": "nssi_CN_NSST",
  "globalSubscriberId": "5GCustomer",
  "subscriptionServiceType": "5G",
  "networkType": "cn",
  "serviceInstanceID": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
  "additionalProperties": {
    "sliceProfileId": "705998ac-f513-11eb-9a03-0242ac130003",
    "nsiInfo": {
      "nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628",
      "nsiName": "nsi_NSTO1"
    },
    "isCreateSliceProfileInstance": "false"
  }
}

Gerrit change: https://gerrit.onap.org/r/c/so/+/122554

CORE_05Service Activation and Service DeactivateWhen triggered by NSSMF Adaptor with activateNSSI or deactivateNSSI for activating/deactivating Core NSSI
Aleem Raja

COMPLETED

Impact due to code change. SO-3605

Two APIs
-activate : http://{{k8s}}:30277/onap/so/infra/3gppservices/v1/activate
-deactivate : http://{{k8s}}:30277/onap/so/infra/3gppservices/v1/deActivate

- Request Payload
{
"serviceInstanceID": "11c0c52a-d748-48aa-86e3-c783cbf5026f",
"globalSubscriberId": "5GCustomer",
"subscriptionServiceType": "5G",
"networkType": "cn",
"additionalProperties": {
"nsiId": "NSId5a44-3109-48bd-9cd5-bfb2a4d52628",
"snssaiList": ["01-5B179BD4"],
"sliceProfileId": "1c7046f2-a5a3-4d7f-9da8-388ee641a795"
}
}

Note: - To check configuration updated for activate/deactivate flow, CBA package needs to be updated after Guilin rel