Currently the policy checks for dummy vf module - i.e. one with is-base-module field to be false and uses the name to determine new vf module name.

This logic should be replaced with finding the vf module with is-base-module as "false" and orchestration-status as "inactive". It is presumed that SO shall populate this in AAI during the previous scale-out. The additional advantage with this approach is that we shall be able to use the naming policy to determine the VF module name of the scaled-out version.

If such entry in AAI is not found, policy should return an error.