Page History

...

• • Leverage ETSI standards for VNF LCM in SO

  • Build SO VNFM Adapter

    • Use SOL003 APIs (2.5.1) for VNF LCM

    • Support operations such as create, instantiate, grant, query, terminate, LCN subscription and LCN

    • Support terminate is a stretch goal

  • Enhance SO BPMN workflows & recipes

    • VNF-level and VF-Module workflows, leveraging VNFM Adapter 

    • Passing VNF LCM requests to VNFM using VNFM Adapter

  • Policy based VNF scale out thru VNFM Adapter (Stretch Goal)

    • VNFM Adapter interfaces for VES event

    • Policy Framework for scaling decisions

    • SO workflows for VNF Scale out

  • Provide VNF package management for VNFM (Stretch Goal; under investigation)

  • VNF-level and VF Module-level Assignment modeling in SDNC and A&AI (open issue)

  • VNF Application Configuration thru VNFM Adapter and VNFM (open issue & not for Dublin)

...

• • 
    

    • Terminate VNF

      • HTTP Method Type: POST

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

      • Request Payload: TerminateVnfRequest

      • Response Header: 202 success

      • Response Body: not applicable

      • Design
        • VNF precondition = INSTANTIATED state
        • After the operation, VNF state = NOT_INSTANTIATED 
        • VNFM Adapter sends a POST request to the Task resource that represents the lifecycle operation to be executed on the VNF instance, and includes in the payload body a data structure of type TerminateVNFRequest (VNFM Adapter → VNFM); POST ../vnf_instances/{vnfInstanceId}/terminate
        • VNFM Creates a "VNF LCM operation occurrence" resource for the request (VNFM → VNFM Adapter)
        • VNFM returns a "202 Accepted" response with an empty payload body and a "Location" HTTP header that points to the new "VNF LCM operation occurrence" resource (VNFM → VNFM Adapter); .../vnf_lcm_op_occs/{vnfLcmOpOccId}
        • VNFM sends to the VNFM Adapter a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state
        • VNFM and VNFM Adapter exchange granting information (see Granting section)
        • VNFM sends to the VNFM Adapter a VNF lifecycle management operation occurrence notification to indicate that the VNF LCM operation occurrence enters the "PROCESSING" state
        • VNFM Adapter polls the "VNF LCM operation occurrence" resource to obtain information about the ongoing operation by sending a GET request to the resource that represents the VNF LCM operation occurrence.
        • VNFM returns to the VNFM Adapter information of the operation, such as the operation status, by providing in the payload body a data structure of type "VnfLcmOpOcc"
        • VNFM has finished the operation <<Operation>>
        • VNFM sends a VNF lifecycle management operation occurrence notification to VNFM Adapter to indicate the completion of the lifecycle management operation occurrence with the success state "COMPLETED"
        • Note: its communication exchange pattern is the same as the Instantiate VNF.

        • Parameters and Data source

          Parameter	Required?	Data Source	Note
          terminationType	Yes	from user input
          gracefulTerminationTimeout	Optional	from VNFD	This attribute is only applicable in case of graceful termination. The unit is seconds
          additionalParams	Option	from VNFD

          
          

• • • More SVFM SOL003 Interfaces for Future Release

...