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
...
Resolution: Delete the extra newline with VIM
- Connect to the SDNC container from the Rancher VM in the Kubernetes cluster, for example kubectl exec -it -n onap dev-sdnc-sdnc-0 bash
- Install your favorite text editor, for example apt-get update; apt-get install vim -y
Open /opt/onap/sdnc/restapi/templates/lcm-dmaap-publish-template.json and execute the following operations:
:set binary
- :set noeol
- :wq
- If SDNC is deployed in cluster mode (3 SDNC replicas, dev-sdnc-sdnc-0, dev-sdnc-sdnc-1, dev-sdnc-sdnc-2), apply the same change to all the replicas in the cluster
...