The policy based generic VNF scale out scenario is planned for Casablanca release. Till then for Beijing release, it is desired that vDNS / load balancer use case should support scale out for multiple times.

We need to generate unique value for attribute "vf-module-name" for every scale out operation. This is planned to be achieved with below modifications in processing of policy invocation -

1. Determine if the scale out operation is being done for the first time. This could be derived from count of VF modules with attribute "is-base-vf-module" attribute being "false" as only one. 
2. In this case, replace the string "Vfmodule" of the "vf-module-name" attribute with string "vDNS" (Existing logic) and additionally append the string "-1". For every scale out operation, we shall increment the suffix to generate distinct "vf-module-name" values.
3. If there are multiple instances of "vf-module-name" with "is-base-vf-module" attribute being "false", select the value with the maximum suffix, increment this by one and use the new formed name as value of attribute "vf-module-name"
4. The vDNS HEAT template needs to be modified such that the instance name is not hardcoded and that a unique instance name is generated every time when the HEAT template is processed.

NOTE: The manual SDNC preload would have to be performed for "to be" scaled out instance. Thus after every successful scale out operation, perform manual SDNC preload with the VF module name having the incremented suffix.