2. Auto-Scaling and Cloud Bursting : 2.3 Configuration : 2.3.4 Auto-Scaling and Bursting Configuration Process
2.3.4 Auto-Scaling and Bursting Configuration Process
The Set vApp Autoscaling and bursting settings workflow checks to determine whether this vApp already has a scale and burst configuration. If not, the workflow generates a random identifier for the vApp and records it in the vApp metadata. Storing the vApp Template Name and a configuration ID in the vApp metadata allows all the vApps issued from the same template to be found and their scaling configuration to be retrieved.
Using the vApp metadata insures that all the parameters are copied when you:
*Add the vApp as a vApp Template to a catalog.
*Download the vApp Template as an OVF.
*Upload the OVF as a vApp template.
*Instantiate the vApp template as a vApp.
*Copy or Clone the vApp.
If the vApp is being configured for the first time, the workflow replicates the vApp Template across the different virtual datacenters in the same organization as the vApp, and instantiates a single undeployed (not started) vApp. This vApp adds as many virtual machines for each tier as defined by the minimum VM number setting in the configuration.
The vApp Template is used to add the virtual machines of a given tier to a vApp or to instantiate a new vApp when necessary.
If the vApp already has a configuration, the workflow updates its configuration elements attribute properties.
Storing the scaling configuration in vCenter Orchestrator configuration elements lets you get or modify a single configuration for all the deployed vApps and vApp templates issued from the same base vApp.