7.1

Table 4‑13. General Tab Settings (Continued)
Setting Description
Reservation policy Apply a reservation policy to a blueprint to restrict the machines
provisioned from that blueprint to a subset of available reservations.
Fabric administrators create reservation policies to provide an optional
and helpful means of controlling how reservation requests are
processed, for example to collect resources into groups for dierent
service levels, or to make a specic type of resource easily available for
a particular purpose. If your fabric administrator did not congure
reservation policies, you do not see any available options in this drop-
down menu.
Machine  Machine prexes are created by fabric administrators and are used to
create the names of provisioned machines. If you select Use group
default, machines provisioned from your blueprint are named
according to the machine prex congured as the default for the user's
business group. If no machine prex is congured, one is generated
for you based on the name of the business group.
If your fabric administrator congures other machine prexes for you
to select, you can apply one prex to all machines provisioned from
your blueprint, no maer who the requestor is.
Instances: Minimum and Maximum Congure the maximum and minimum number of instances users can
request for a deployment or for a scale in or scale out action. If you do
not want to give users a choice, entering the same value in the
Minimum and Maximum elds congures exactly how many
instances to provision and disables scale actions against this machine
component.
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.
Build Information Tab
Congure build information seings for a vCloud Air machine component.
Table 4‑14. Build Information Tab
Setting Description
Blueprint type For record-keeping and licensing purposes, select whether
machines provisioned from this blueprint are classied as
Desktop or Server.
Action The options you see in the action drop-down menu depend
on the type of machine you select.
The following actions are available:
n
Clone
Make copies of a virtual machine from a template and
customization object.
Configuring vRealize Automation
256 VMware, Inc.