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

Instantiate NS Backend Service

XMLWordPrintable

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

      Supports the Instantiate NS backend operations and workflows which do the following sequence:

      <Instantiate NS: note: the following workflow is a template, and it can be enhanced as needed.>

      • Supports SOL005-compliant InstantiateNSRequest request and parameters
        • Creates BPMN workflows and business logic for the following Instantiate NS operations
          • Create a Job Id
            • Updates NS_Instance Status to INSTANTIATING to the NFVO NS Instance database table
            • Handles input parameters from the InstantiateNsRequest
              • additionalParamsForNs
                • the VnfProfileId is the vnf descriptor id from the tosca.nodes.nfv.VNF vnf_profile (tosca.datatypes.nfv.VnfProifle) properties in NSD
                  • note: the VnfProfile data type properties are: instantiation_Level, min_number_of_instances, max_number_of_instances
                  • note: this property is only used in an NSD service template when describing a VNF node template with the corresponding VnfProfile information.
                • pass vim_id with tenant id
              • additionalParamsForVnf
                • If it is provided in the request, use use additionalParamsForVnf attributes
                • Otherwise, formulate additionalParams for SOL003 Adapter invocation, from the NSD
                • pass vim_id tenent id
                • use of VNF input for additionalParamsForVnf is under investigation
              • pseudo logic:
                • plan_input = job_id, ns_inst_id, dst_plan, additionalParamsForNs, additionalParamsForVnf, additionalParamsForPnf
                • dst_plan = get nsd with the given nspackage_id, input parameters
                • Gets an ns instance id from the parameter
                • Gets job id and occ id from the NS LCM Mgr
              • Gets VNF VIM from the location_constraints
                • Gets NSD from ETSI Catalog Manager and parses NSD (by using either SDC parser or ETSI Catalog Manager parser)
                  • Note: until either SDC parser or ETSI Catalog Manager parser is ready, use the current SO NFVO internal TOSCA parser
                • If ETSI Catalog Manage parser is used, use the following ETSI Catalog Manager API:
                  curl -X POST /api/parser/v1/parsernsd' \

                                                                     -H 'Content-Type: application/json' \

                                                                     --data-raw '

                                                                     {     "csarId": "csarid",     "packageType": "ns",     "inputs": "[]" }

                                                                     '

      • Updates NFVO_INST db to modify nsd model
      • Gets VNFs from the NSD
      • For each VNF, invokes the SOL003 Adapter with SOL003-compliant requests
        • To call the SOL003 Adapter, use the current SOL003 Adapter Rest API (which is internal to SO)
          • Note: exposing ETSI SOL003-compliant SOL003 Adapter REST API will be handled by the separate user story (most likely in the Honolulu release). 
          • The SOL003 Adapter internal REST API will be enhanced to carry additional attribute(s), such as tenant id, VNF package id
          • The Create VNF internal API in SOL003 Adapter will invoke both Create and Instantiate VNFs
          • Send parameters such as vnfd_id, vnfm_type, vimId, s_vimId (with "cloud_owner"_"cloud_regionid") and tenant id to the SOL003 Adapter
          • For Granting VNF, support VNF granting based on the existing SOL003 Adapter.
        • Note: Currently SOL003 adapter uses “ModelVersionId" from generic-vnf to retrieve the VNFD from SDC/etsi catalog. In order to create generic-vnf it also need model invariant id because of the relationship defined between generic-vnf and service-design-and-creation/models.
      • Supports VirtualLink connections between VNFs
        • Supports createVLs (call MultiCloud through MultiCloud Adapter)
          • Follow the Create VLs user story
      • Updates NFVO_NSINST db table: update NFVO_NSINST with the nsd model
      • Sets job status = NS Instantiate ends
      • Updates NsLcmOpOCC to COMPLETED
      • Note: Sends nsLcmOperationOccurrenceNotification
        • Note: this notification will be handled by a separate notification and subscription user story.

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

              Created:
              Updated:
              Resolved: