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://<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
...
- Connect to the Policy GUI, either through the ONAP Portal (https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm) or directly (https://policy.api.simpledemo.onap.org:30219/onap/login.htm)
- If using the ONAP Portal, use demo/demo123456! as credentials, otherwise, if accessing Policy GUI directly, use demo/demo
- Click "Policy" → "Push" on the left panel
- Click the pencil symbol next to "default" in the PDP Groups table
- Select "Decision_AllPermitGuard"
- Click "Remove"
3) When
...
distributing the closed loop from CLAMP to policy if we get error as - policy send failed PE300: Invalid template, the
...
Resolution: Replace the "input" field in the JSON template with "output"
...
Open /opt/onap/sdnc/restapi/templates/lcm-dmaap-publish-template.json and replace "input" with "output" in the JSON object body
...
Save the changes
...
template name closedLoopControlName was not found in the dictionary.
For proper operation via CLAMP, the rules template need to be uploaded to Policy. This can be achieved by executing the push-policies.sh script before creating the Control Loop via CLAMP:
kubectl get pods -n onap -o wide | grep policy | grep pap # identify the PAP pop
kubectl exec -it <pap-pod> -c pap -n onap -- bash -c "/tmp/policy-install/config/push-policies.sh"
Videos:
These videos provide a detailed documentation of how to run scale out use case using manual or automated (i.e. closed loop-enabled) trigger:
...
Example of SDNC VF module topology to define a JSON path to configuration parameters for scale out: sdnc_resource_example.txt
Configuration parameters for CDT: parameters_vLB.yaml
VNF interface for CDT: Vloadbalancerms..dnsscaling..module-1.xml
AAI API to set Availability Zone:
CloudOwner is the cloud-owner object in AAI
- RegionOne is the cloud-region-id in AAI
- AZ1 is the name of the Availability Zone
| Code Block | ||||
|---|---|---|---|---|
| ||||
curl -X PUT \
https://10.12.7.29:30233/aai/v14/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/availability-zones/availability-zone/AZ1 \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-H 'Postman-Token: 4fe938e9-28d7-4956-8822-e01b6f27a894' \
-H 'X-FromAppId: AAI' \
-H 'X-TransactionId: get_aai_subscr' \
-H 'cache-control: no-cache' \
-d '{
"availability-zone-name": "AZ1",
"hypervisor-type": "hypervisor"
}' |
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
...