7.2

Table Of Contents
Table 9. Support for Scalable Components (Continued)
Component Type
Suppor
ted Notes
XaaS components No XaaS components are not scalable and are not updated during a scale
operation. If you are using XaaS components in your blueprint, you could
create a resource action for users to run after a scale operation, which could
either scale or update your XaaS components as required. Alternatively, you
could disable scale by conguring exactly the number of instances you want
to allow for each machine component.
Nested blueprints Yes Supported components in nested blueprints might only update if you create
explicit dependencies to scaled machine components. You create explicit
dependencies by drawing dependency lines on the design canvas.
When you scale out a deployment, vRealize Automation allocates the requested resources on the current
reservation before proceeding. If the scale is partially successful, and fails to provision one or more items
against those allocated resources, the resources are not deallocated and do not become available for new
requests. Resources that are allocated but unused because of a scale failure are known as dangling resources.
You can try to repair partially successful scale operations by aempting to scale the deployment again.
However, you cannot scale a deployment to its current size, and xing a partially successful scale this way
does not deallocate the dangling resources. You can view the request execution details screen and nd out
which tasks failed on which nodes to help you decide whether to x the partially successful scale with
another scale operation. Failed and partially successful scale operations do not impact the functionality of
your original deployment, and you can continue to use your catalog items while you troubleshoot any
failures.
For a clustered deployment, in which the deployment created from a blueprint contains more than one VM,
scaling fails if the blueprint uses a hostname custom property but does not contain a machine prex value.
To avoid this issue, you can use the machine prex option in the blueprint denition. Otherwise, the scaling
function aempts to use the same hostname seing for each VM in the cluster.
Scale Up or Scale Down By Using Reconfigure
After you provision a vSphere, vCloud Air, or vCloud Director virtual or cloud machine you can adjust to
changing workload demands by requesting a machine recongure to increase (scale up) or decrease (scale
down) machine resource specications for CPU, memory, storage, or networks. You can also add, edit, or
remove custom properties and change descriptions. You can request to recongure machines for scale up or
scale down that are in the On or O state.
When you recongure a virtual or cloud machine for scale up, vRealize Automation allocates the requested
resources on the current reservation before proceeding. If the resources are not available, the machine
recongure fails. If a machine recongure request fails, any resources allocated for scale up are deallocated
and available for new requests. When you recongure a virtual or cloud machine for scale down, resources
are not made available to new requests unless the recongure nishes successfully.
Table 10. Required Entitlements for Machine Reconfigure for Scaling Scenarios ( vSphere , vCloud Air ,
and vCloud Director only
Virtual or Cloud Machine Owner wants to... Required Entitlements
Run the recongure for scaling immediately after any
required approvals are given.
Recongure
Specify a date and time to run the reconguration for
scaling.
Recongure
Reschedule a recongure for scaling because the request
was not approved until after the scheduled time.
Recongure
Retry a failed recongure request. Execute recongure
Foundations and Concepts
VMware, Inc. 33