Page History

...

• • Even though SO Building Blocks are used for the SO VNFM Adapter, assignment data will be pre-loaded into SDNC for the Dublin release.
  • In El Alto release, preload data could be replaced with SO request data (TBD)
  • Possible preload data structure. The additionalParams and extVirtualLinks data will be preloaded to SDNC, and the SO VNFM Adapter will retrieve the data from SDNC.

    • {  
         "additionalParams ":"{\"param_1\": \"value_1\",\"param_2\": \"value_2\",\"param_3\": \"value_3\"}",
         "extVirtualLinks":"[{\"id\": \"vlaue\",\"resourceId\": \"value\",\"extCps\": [{\"cpdId\": \"cpdId_value\",\"fixedAddresses\": [{\"fixedAddresses\": {\"macAddress\": [\"macAddress_1\", \"macAddress_2\"]}}]}]}]"
      }

• VNFM Simulator

SVNFM is provided by its vendor, which is vendor-specific by nature. For ONAP integration testing for SO VNFM Adapter, a generic VNFM Simulator is needed. This generic VNFM Simulator will support SOL003-compliant interfaces. 

In Dublin, the Simulator will support Crate, Instantiate, Terminate and Delete VNF operations and Grant request/response handling. Simulated mock-up request and response data will be exchanged.

• VNFM Adapter Locating SVNFM

• • VNFM Adapter locates a proper SVNFM based on VNF NF Type/VNFD  and VNFM registration
  • Two methods are suggested as follows, and one of them will be chosen.

...

• • SOL003 Interfaces between VNFM Adapter (Client) and SVNFM (Provider)

           Note: for the interface details, see the VNFM Adapter APIs, 

SO VNFM Adapter APIs

.

• • • Create VNF

      • HTTP Method Type: POST

      • VNFM Endpoint: /vnf_instances/

      • Request Payload: CreateVnfRequest

      • Response Header: 201 success

      • Response Body: VnfInstance

...