15 Terminating a VNF

This procedure represents the Terminate VNF operation. The client can use this procedure to terminate a VNF instance. The POST method terminates a VNF instance.

Following are the two types of request parameters for the Terminate VNF operation:

• FORCEFUL : The VNFM deletes the VNF and releases the resources immediately after accepting the request.
• GRACEFUL : After accepting the request, the VNFM first validates if the VNF configuration is cleaned up. Once the validation is successful, VNFM deletes the VNF and releases the resources.

  Note:

  VNFM does not support clean-up or reverse cloud-init. The user must manually clean the configuration before Graceful Termination.

Below table describes the parameters used for sending request to VNFM.

Table 15-1 Parameters and Definitions for Terminating VNF

Parameters	Definitions
terminationType	Indicates whether forceful or graceful termination is requested.

15.1 Forceful Termination

The VNFM will delete the VNF immediately after accepting the request. The instance file is updated with VNF Operational State set to STOPPED.

Note:

If the VNF is still in service, requesting forceful termination can adversely impact the network service.

Figure 15-1 Forceful termination

Terminating DSR and SDS VNF Instance Forcefully

Sample Request:

Request URL: POST: https://<<VNFM HOST IP>>:8443/vnflcm/<<vnfm_version>>/vnf_instances/< VNF ID received from create request>/terminate

Accept: application/json

Content-Type: application/json

Authorization: Token generated after login

{
   "terminationType": "FORCEFUL"
}

Sample Response

Response Code: 202
{
     location: https://localhost:8443/vnflcm/<<vnfm_version>>/vnf_lcm_op_occs/lcmOp-fb21f9d3-43ad-46cd-a03f-7220bb36a5c6  
     date: Tue, 29 Jan 2019 10:39:24 GMT  
     content-length: 0  content-type:
     application/xml 
}

15.2 Graceful Termination

The VNFM first validates if the VNF configuration is cleaned up after accepting the request. Once that configuration is cleaned, the VNFM deletes the VNF. Then the instance file is updated with VNF Operational State set to STOPPED.

If AppWorks configurations are not cleaned manually and the orchestrator tries to do graceful termination for that VNF, then the termination of VNF fails.

Note:

• User must manually cleanup the AppWorks configurations before doing Graceful Termination.
• gracefulTerminationTimeout is the sleep time given before Graceful stack termination.

Steps for cleaning up the AppWorks Configuration for Signaling Stack of DSR and SDS:

1. Open corresponding Active NOAM GUI of the Signaling instance.
2. In Status & Manage Tab, under HA, edit the Max Allowed HA Role of instances of the Signaling stack as OOS.
3. In Configuration Tab, under Server Groups, edit the corresponding server groups of the instances and uncheck SG Inclusion for the Server, and press OK. After this step, the excluded Servers must disappear in Status & Manage -> Server section.
4. Finally, go to Configuration -> Servers section, select the servers that needs to be deleted and click Delete.

   Note:

   • For DSR / SDS Signaling VNF clean up, the user must perform the above steps twice, first for C-level servers and then repeat the steps for B-level servers.
   • In case of re-deployment Places present at Configuartion → Places of the existing signaling setup need to be deleted manually from DSR GUI of Active NOAM.

Figure 15-2 Graceful termination

Terminating DSR and SDS VNF Instance Gracefully

Sample Request:

Request URL: POST: https://<<VNFM HOST IP>>:8443/vnflcm/<<vnfm_version>>/vnf_instances/< VNF ID received from create request>/terminate

Accept: application/json

Content-Type: application/json

Authorization : <Token generated after login>

{
  "terminationType": "GRACEFUL",
  "gracefulTerminationTimeout": 0
}

Sample Response

RResponse Code : 202

{

     location: https://localhost:8443/vnflcm/<<vnfm_version>>/vnf_lcm_op_occs/lcmOp-fb21f9d3-43ad-46cd-a03f-7220bb36a5c6  

     date: Tue, 29 Jan 2019 10:39:24 GMT  

     content-length: 0  content-type:

     application/xml 

}