-
Story
-
Resolution: Done
-
Medium
-
None
-
None
SO NFVO NBI API Handler needs to enhance its Terminate NS to ETSI 3.3.1 from ETSI 2.7.1
- Leveraging ETSI 3.3.1 swagger upgrade, upgrade the Terminate NS NBI code to support 3.3.1
- Follow and confirm 3.3.1 changes on the message sequencing, request, response, pre- and post-conditions.
- Precondition:
- NS instance is INSTANTIATED state
- SOL007 NS packages are stored in ETSI Catalog Manager.
- the Cli-based (Postman) SO NFVO Client is ready to send the SOL005-compliant Terminate NS request
- The SO-NFVO (so-etsi-nfvo) pod is ready
- Test the following scenarios
- SO NFVO NBI API Handler needs to supports the SOL005-compliant Terminate NS API - check for 3.3.1 update
- Supports Terminate NS request API: POST /api/nslcm/v1/ns_instances/{nsInstanceId}/terminate (TerminateNsRequest)
- Supports responses 202 Accepted with an empty payload body
- Returns a dummy 202 until the backend business logic is ready
- Use a Location HTTP header that points to the new individual NS Lifecycle Operation Occurrence resource; i.e. the URI of that resource (.../ns_lcm_op_occs/{nsLcmOpOccId}
Supports the Sends nsLcmOperationOccurrenceNotifiation with nsLcmOpOccId, notificationStatus (start, result) until the result status becomes COMPLETED- Optionally, Terminate NS operations uses the GET individual NS LCM operation occurrence request and response
- Error handling: if the operation is failed, error information is provided in the notification message
- SO NFVO NBI API Handler needs to supports the SOL005-compliant Terminate NS API - check for 3.3.1 update
- Post conditions: the NS Instance is set as the TERMINATED state
Note: secure communication is handled by a separate user story, SO-3165.
- mentioned in
-
Page Loading...