SO NFVO NBI API Handler needs to enhance its Delete 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 in NOT_INSTANTIATED state
  • SOL007 NS packages are stored in ETSI Catalog Manager.
  • the Cli-based SO NFVO Client is ready to send the SOL005-compliant Create NS request
  • The SO-NFVO (so-etsi-nfvo) pod is ready
• Test the following scenarios
  • SO NFVO NBI API Handler needs to support the SOL005-compliant Delete NS API - check for 3.3.1 update
    • Supports Delete NS request API: DELETE /api/nslcm/v1/ns_instances/{nsInstanceId}
    • Supports the Sends 204 No Content with an empty payload body
      • Returns a dummy 204 until the business logic is ready
    • Sends NsIdentifierDeletionNotification to the NFVO subscriber(s) (e.g., ONAP SO SOL005 Adapter)

• • • • Note: this will be handled by the separate user story: Sends NsIdentifierCreationNotification to the NFVO subscriber(s) (e.g., ONAP SO SOL005 Adapter)
  • Error handling: if the individual NS instance is not in NOT_INSTANTIATED state, it rejects the deletion request

• Postconditions: the resource representing the NS instance has been removed from the list of NS instance resources

Note: secure communication is handled by a separate user story, SO-3165.