Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-3449

Enhance the Create NS NBI

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None

      SO NFVO NBI API Handler needs to enhance its Create NS to ETSI 3.3.1 from ETSI 2.7.1

      • Leveraging ETSI 3.3.1 swagger upgrade, upgrade the Create 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.
      • Preconditions: 
        • SOL007 NS packages are stored in ETSI Catalog Manager.
        • if SOL 005 Adapter is not ready, 
          • the Cli-based (Postman-based) SO NFVO Client is ready to send the SOL005-compliant Create NS request
        • if the SOL 005 Adapter / Simulator is ready,
          • SOL 005 Adapter / Simulator subscribed to SO NFVO for LCCN notifications
        • The SO-NFVO (so-etsi-nfvo) pod is ready
      • Test the following scenarios: 
        • SO NFVO NBI API Handler needs to support the SOL005-compliant Create NS API 
          • Supports Create NS request API: POST /api/nslcm/v1/ns_instances (CreateNsRequest)
          • Supports Create NS responses with NsInstance with 201 (for success) or an error
            • Returns a dummy 201 until the backend business logic is ready 
            • Only mandatory attributes of NsInstance will be set.
            • Support successful or error conditions
          • Sends NsIdentifierCreationNotification 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)

       

      • Post conditions: the NS Instance is set as NOT_INSTANTIATED state

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

            byungwoojun byungwoojun
            byungwoojun byungwoojun
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: