Page History

...

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

• • • Grant VNF Request

• • • • HTTP Method Type: POST

      • VNFM Endpoint: /grants

      • Request Payload: GrantRequest

      • Response Header: 201 success

      • Response Body: not applicable

• • • VNF Life-cycle Granting

• • • • The purpose of the grant request is to have the VNFM’s resource request authorized by VNFM Adapter/SO and to get advice on where to allocate resources such as virtual machines based upon capacity.

        Grant requests are also useful to ensure that all resources (capacity, quota, flavors, SRTs, etc.) required for successful VNF deployment are available.

      • There are two Grant Response modes, synchronous and asynchronous. Synchronous response mode will be supported for Dublin.

        • Synchronous Mode

          1. VNFM sends a POST request to the Grant resource with a “GrantRequest” in the body

          2. VNFM Adapter with SO makes the granting decision

          3. VNFM Adapter with SO returns to VNFM a “201 Created” response with a “Grant” data structure in the body

• • • • • Asynchronous Mode

1. 1. 1. 1. 1. VNFM sends a POST request to the Grant resource with a “GrantRequest” in the body
            2. VNFM Adapter with SO returns to VNFM a “202 Accepted” response with an empty body, and a “Location” header indicates a callback URL
            3. VNFM Adapter with SO makes the granting decision
            4. VNFM keeps trying to obtain the grant by sending a GET request to VNFM Adapter until a “200 OK” response with a “grant” data in the body
            5. VNFM Adapter finishes the granting process and returns a “200 OK” response with a “Grant” data in the body

Image Added

• • VNFM Adapter Homing Decision for VNF Granting

• • • Note: the following logic concept is inspired by the VFC Homing decision mechanism.
    • Use of OOF is optional. For those models without using HPA, VNFM Adapter will make a grant decision based on VIM registration information. 

Image Added

• • 1. VNFM Adapter sends out homing requests to OOF (OSDF) containing resource info
    2. OOF (OSDF) pulls all the related homing constraints from Policy
    3. OOF (HAS) checks AAI database to pull region (flavor) information
    4. OOF (HAS) communicates with Multi-Cloud to check cloud capacity (vims which fulfill the requirements)
    5. OOF (OSDF) returns homing allocation solution to VNFM Adapter

• • • OOF collects information as following:
      • Service and Resource Info, from: AAI
      • HPA Flavors/Capabilities/Capacity Info, from: AAI
      • Policy Models (Homing, PCI) from: Policy
      • Infrastructure Metrics Info (capacity), from: MultiCloud
      • Cloud Agnostic Intent Info, from: MultiCloud
      • PCI configuration data (not yet a part of SDC model)

• • More SVFM SOL003 Interfaces for Future Release

...