Description:

 

Scaling is the process utilized by ONAP to change the amount of resources, including VNF Components (VNFCs), allocated to a VNF. Enhance SDNC scale out functionality to receive scale out request from SO.  When a scale out request is initiated from VID (manual scale out) or as a result of policy, a scale out request for L1-L3 VNFs is sent by SO to SDNC.  SDNC will process this request and perform the appropriate scale out tasks.

Casablanca Scale Out:

• Auto Scale Out - Provide a Closed Loop Response to high demand within a VNF. 

1. Primary impacts will be: Policy, CLAMP, SDC, SO

• Enhancements to Manual Scale Out (from Beijing Release)

1. Healthcheck fix.
2. ConfigScaleOut command LCM API Request - Controller should attain configuration information from SO.
3. SDNC Resource Assignment - IP Address of new instance needs to be added to AAI.
   Note: SDNC should write that IP to AAI, but there's no DG for that task in ONAP right now. This operation will be executed offline. SDNC doesn't have to do that for Casablanca.
4. SDNC needs to import all Beijing capability.

 

Requirements:

1. On receipt of a HealthCheck request from SO, SDNC shall initiate a health check on the VNF specified in the message.  Note that the HealthCheck message will have the same format as the one being sent by SO to APPC.
2. SDNC shall subscribe to the appropriate DMaaP topic to receive Life Cycle Management (LCM) messages – currently SDNC_LCM_READ).
3. SDNC shall receive the scale out request (ConfigScaleOut) from SO on the appropriate DMaaP topic (Currently SDNC_LCM_READ). The request will include the VNF/VNFC that needs to be scaled out.  An example of the scale out message is shown below.  Note that the ConfigScaleOut message will have the same format as the one being sent by SO to APPC.

Note: Current plan includes the following:

• SO retrieves the VNF-level IP address in the Generic VNF object in AAI (ipv4-oam-address) that Robot writes to the inventory via Heatbridge;
• SO builds a payload to SDNC that contains both the VNF-level IP address (in the vDNS VNF that includes vLB VNFC and vDNS VNFC, it would be the vLB OAM IP address) and the config scale out parameters with their values.

 ConfigScaleOut command LCM API Request sent by SO to SDNC via DMaaP: 

{
"common-header" : {
"timestamp" : "2018-05-31T19:59:21.124Z",
"api-ver" : "2.00",
"originator-id" : "SO",
"request-id" : "7936559b-1999-459a-93c9-01f4fcea0ca8",
"sub-request-id" : "7936559b-1999-459a-93c9-01f4fcea0ca8",
"flags" :

{ "mode" : "NORMAL", "force" : "FALSE", "ttl" : 65000 }

},
"action" : "ConfigScaleOut",
"action-identifiers" :

{ "vnf-id" : "3c88f1f1-9711-47b6-b992-5e52115ce3bc" }

,
"payload" : "{\"request-parameters\":

{\"vnf-host-ip-address\":\"10.0.150.1\",\"vf-module-id\":\"e98d4c8c-f3ce-4d0e-9f48-b3547796aa48\"}

,\"configuration-parameters\":{\"ip-addr\":\"192.168.10.215\", \"oam-ip-addr\":\"10.0.150.7\",\"enabled\":\"true\"}}"
}

 

In request example above, vnf-host-ip-address is the IP address for the VNF host, ip-addr in configuration-parameters is the private IP address (used by application) of the VNF Component (VNFC) enabled on the VNF being scaled out, oam-ip-addr in configuration-parameters is the OAM private IP address (used for management) of the VNF Component (VNFC) enabled on the VNF being scaled out.

Upon receipt of that ConfigScaleOut message, SDNC shall use the information in the payload to enable VNFC resource on the VF/VNF. SDNC extracts data from ConfigScaleOut message and sends the data to the VNF using RESTCONF interface.

In the case of vDNS VNF to be used in Casablanca for Scale Out, the VNF has multiple VNF components. It has a vLB VNFC, a traffic generator, and vDNS VNFCs. The VNF-Level IP address for this vDNS VNF is the OAM IP address of the vLB VNFC. RESTCONF commands use that IP Address. In ConfigScaleOut message example above we want to enable an additional vDNS VNFC in the VNF using scale out operation. The RESTCONF message tells the VNF to reconfigure the vLB to open a connection towards the to-be-enabled vDNS VNFC. As such, SDNC interacts with the vLB VNFC of the VNF, not the to-be-enabled vDNS VNFC.

vDNS VNF assumptions:

• All the operations are executed against the vLB VNFC
• 10.0.150.1 is the IP of the vLB (in this example)
• 8183 is the port for RESTCONF interface calls

For the scale out request shown above, assuming that it is for a vDNS VNFC, the RESTCONF call toward the VNF would be as below.

Configuring vLB with information about vDNS instances - Enable single vDNS VNFC instance by telling the VNF to reconfigure the vLB to open a connection toward that vDNS VNFC:
 
PUT http://10.0.150.1:8183/restconf/config/vlb-business-vnf-onap-plugin:vlb-business-vnf-onap-plugin/vdns-instances/vdns-instance/192.168.10.215

 

 {

"vdns-instance": [

      

{            "ip-addr": "192.168.10.215",            "oam-ip-addr": "10.0.150.7",            "enabled": true        }

   ]

}

}

  

Assumptions:

1. SDNC will perform the same actions for Manual and Auto Scale Out cases. For manual scale out, VID will initiate the request to SO.  For auto scale out, Policy will generate the request the request to SO.  SO will then send the same request to SDNC.
2. SDNC will use the LCM related topics on DMaaP to receive the ConfigScaleOut and HealthCheck requests.
3. SDNC will not create any new VMs or VFs. Creation of those will be handled by SO and configuration/resource assignment of the newly created VFs will be performed by SDNC.