Background -

For scale up scenarios, the closed control loop policy component invokes "VF Module Create" API on SO. The related workflow checks existence of VF module name as part of it's validation. However, for scale-up scenario the VF module is already created in AAI as part of prerequisites - and only instantiation in cloud remains pending. Hence for the scale up scenario, below functionality is desired in the new SO workflow -

PART-A
1. Extract the "relatedInstance.instanceId" for the "modelType" as "service" from the payload. This is the "service-instance-id". Payload remains the same as that for "VF Module Create" API
2. Query AAI to get all the related nodes for the "service-instance-id" value extracted above
3. Refer the node with property "is-base-vf-module" having value as "false" AND  "orchestration-status" having value as "inactive". Get the "vf-module-name" from this node
4. Query SDNC with "vf-module-name" as retrieved from step 3 above
5. Initiate the stack creation in cloud environment
6. Do not create a new VF Module, but update the orchestration status of the VF module referred in step 3 above - Set  "orchestration-status" as "active"

For the next scale up operation to succeed there are two more configuration steps that needs to be done now.

PART-B
1. Create a new VF module in AAI with similar parameters from the node selected in step 3 of PART-A. Only difference is "vf-module-name" should be a new name, "is-base-vf-module" should be set as "false" and "orchestration-status" value should be set as "inactive"
2. Update SDNC configuration for the new VF module created. "vf-module-name" should be from step 1 of PART-B above. All other parameters should be as retrieved from step 4 of PART-A above.

NOTE: It is assumed that the HEAT template shall have the script to determine unique instance name for every instantiation.