Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note: SO future release could consider SOL001/SOL004 internal representation in its Catalog DB, or using the Run-time Catalog DB

  • Design

    • xTBD


  • VNFM Adapter VNF Package Management

...

  • SOL003 Support and Design


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


      • Create VNF

        • HTTP Method Type: POST

        • VNFM Endpoint: /vnf_instances/

        • Request Payload: CreateVnfRequest

        • Response Header: 201 success

        • Response Body: VnfInstance

      • Instantiate VNF

        • HTTP Method Type: POST

        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}/instantiate

        • Request Payload: InstantiateVNFRequest

        • Response Header: 202 success

        • Response Body: not applicable

      • Query VNF Instances

        • HTTP Method Type: GET

        • VNFM Endpoint: /vnf_instances  (for multiple VNFs), /vnf_instances/{vnfInstanceId}  (for single VNF)

        • Request Payload: not applicable

        • Response Header: 200 success

        • Response Body: VnfInstance[] (for multiple VNFs), VnfInstance (for single VNF)


    • 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


    • More SVFM SOL003 Interfaces for Future Release


      • Scale VNF

        • HTTP Method Type: POST

        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}/scale
        • Request Payload: ScaleVnfRequest
        • Response Header: 202 accepted
        • Response Body: not applicable
      • Scale to Level Vnf
        • HTTP Method Type: POST
        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}/scale_to_level
        • Request Payload: ScaleVnfToLevelRequest
        • Response Header: 202 accepted
        • Response Body: not applicable
      • Terminate VNF

        • HTTP Method Type: POST

        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}/terminate

        • Request Payload: TerminateVnfRequest

        • Response Header: 202 success

        • Response Body: not applicable

      • Delete VNF
        • HTTP Method Type: DELETE

        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}

        • Request Payload: not applicable

        • Response Header: 204 success

        • Response Body: not applicable

      • Operate VNF
        • HTTP Method Type: POST

        • VNFM Endpoint: /vnf_instances/{vnfInstanceId}/operate

        • Request Payload: OperateVnfRequest

        • Response Header: 202 success

        • Response Body: not applicable


  • Impacted ONAP components


    • SO 
      • SO Catalog DB for SOL001/SOL004 support
      • BPMN Workflows and Recipes
      • VNFM Adapter
    • SDC 
      • Support SOL001/SOL004
    • SDNC
      • VNF-level Network Assignment, instead of VF-Module
    • A&AI
      • VNF-level Inventory Update
      • VNFM location
    • Policy
      • Scale-Out support for ETSI-based scaling
    • Modeling
      • Support SOL001/SOL004

...