ONAP Casablanca Release delivers platform capabilities that support scaling up resources. The use case has been designed and implemented to fully take advantage of existing functionalities, using newer APIs and technologies whenever possible. Compared to the previous version delivered for Beijing, which supported only manual trigger and one VNF type, the new use case adds:
...
1) When running closed loop-enabled scale out, the closed loop designed in CLAMP conflicts with the default closed loop defined for the old vLB/vDNS use case
Resolution: Change TCA configuration for the old vLB/vDNS use case
- Connect to Consul: http://<Cluster IP><ANY K8S VM IP ADDRESS>:30270 and click on "Key/Value" → "dcae-tca-analytics"
- Change "eventName" in the vLB default policy to something different, for example "vLB" instead of the default value "vLoadBalancer"
- Change "subscriberConsumerGroup" in the TCA configuration to something different, for example "OpenDCAE-c13" instead of the default value "OpenDCAE-c12"
- Click "UPDATE" to upload the new TCA configuration
2) When running closed loop-enabled scale out, the permitAll guard policy conflicts with the scale out guard policy
...
Example of SDNC VF module topology to define a JSON path to configuration parameters for scale out: sdnc_resource_example.txt
VID API to enable scale out for a given VNF.
- UUID is the VNF model version ID in the CSAR file
- invariantUUID is the VNF model invariant ID in the CSAR file
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
curl -X POST \
https://<ANY K8S VM IP ADDRESS>:30200/vid/change-management/vnf_workflow_relation \
-H 'Accept-Encoding: gzip, deflate' \
-H 'Content-Type: application/json' \
-H 'Postman-Token: 7086e3eb-f6a9-416c-85f9-6c99ae7c2c02' \
-H 'cache-control: no-cache' \
-d '{
"workflowsDetails":[
{
"workflowName":"VNF Scale Out",
"vnfDetails":{
"UUID":"d5c2aff0-d2bc-401e-8277-fd90c1351b0e",
"invariantUUID":"cdc1ac36-a3c9-41e8-872b-10d02a6eded1"
}
}
]
}' |
Configuration parameters:
...