• SO NFVO NBI API Handler needs to enhance its Get NS operation 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: 
    • the Cli-based (Postman) 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
    • Supports the SOL005-compliant GET NS LCM operation occurrences API 
      • Supports multiple NS LCM operation occurrences request API: GET / api/nslcm/v1/ns_lcm_op_occs
      • Supports responses for multiple NS LCM operation occurrences with 200 OK (NsLcmOpOcc[])
      • Supports individual NS LCM operation occurrence request API: GET /api/nslcm/v1/ns_lcm_op_occs/{nsLcmOpOccId}
        • nsLcmOpOccId is an attribute in the NsLcmOperationOccurrenceNotification
      • Supports responses for the individual NS LCM operation occurrence with 200 OK (NsLcmOpOcc), where its opeationStatus=PROCESSING, COMPLETED)
        Note: Instantiate NS and Terminate NS use the GET individual NS LCM operation occurrence

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