2. Auto-Scaling and Cloud Bursting : 2.4 The Upscaling and Bursting Process : 2.4.6 Instantiate a New vApp Yellow Section
2.4.6 Instantiate a New vApp Yellow Section
The Instantiate a New vApp section of the workflow tries, for a given virtual datacenter, to instantiate a new vApp from the vApp template that matches the vApp template name and identifier defined in the auto-scale and burst settings. If, for any reason, the instantiation fails, the workflow tries to instantiate it in the next virtual datacenter, in the burst order. The vApp name is generated automatically, based on the name of the existing vApp.
Figure 5. Workflow Schema: Instantiate a New vApp Workflow Steps
For each bursting virtual datacenter:
1. Instantiate another vApp:
a. Generate a new vApp name.
b. Instantiate the vApp.
c. Deploy the vApp.
d. Add as many virtual machines as are set in the minimum number of instances.
2. If the Instantiate another vApp action succeeds, exit the loop to the Get vApp Tier 1 VM IPs section.
3. If not, try from another virtual datacenter.
If the instantiation could not be done in any of the virtual datacenters, fail. In the case where the virtual datacenter was the one provided as input parameter, go back to the start of the workflow to attempt the different operations with the burst virtual datacenters. Error Handling
If a vApp instantiation fails, instantiate from the next available virtual datacenter. Logs
*Information : "Attempting to burst to VDC [virtual datacenter name]";
*Warning: "Failed to instantiate vApp Template in VDC [virtual datacenter name]";
*If the vApp cannot be instantiated in any virtual datacenter: "Found no VDC to burst to !"