When a member of a business group requests a vApp, a vCloud reservation is selected from the group's reservations to provision the vApp.
The reservation on which a vApp is provisioned must satisfy the following criteria.
The reservation must be a vCloud reservation.
If the request specifies an allocation model, the virtual datacenter associated with the reservation must have the same allocation model.
The reservation must be enabled.
The vCloud Director or vCloud Air organization must be enabled.
The reservation must have capacity remaining in its machine quota or have an unlimited quota.
The allocated machine quota includes only machines that are powered on. For example, if a reservation has a quota of 50, and 40 machines have been provisioned but only 20 of them are powered on, the reservation’s quota is 40 percent allocated, not 80 percent.
The reservation must have sufficient unallocated memory and storage resources to provision the machine.
In a Pay As You Go reservation, resources can be unlimited.
If the blueprint has specific network settings, the reservation must have the same networks.
If the blueprint or reservation specifies a network profile for static IP address assignment, an IP address must be available to assign to the new machine.
Any blueprint templates must be available on the reservation. If the reservation policy maps to more than one resources, the templates should be public.
If the request specifies an allocation model, the allocation model in the reservation must match the allocation model in the request.
If the blueprint specifies a reservation policy, the reservation must belong to that reservation policy.
Reservation policies are a way to guarantee that the selected reservation satisfies any additional requirements for provisioning machines from a specific blueprint. For example, you can use reservation policies to limit provisioning to compute resources with a specific vApp template.
If no reservation is available that meets all of the selection criteria, provisioning fails.
If multiple reservations meet all of the criteria, the reservation from which to provision a requested machine is determined by the following logic.
Reservations with higher priority are selected over reservations with lower priority.
If multiple reservations have the same priority, the reservation with the lowest percentage of its machine quota allocated is selected.
If multiple reservations have the same priority and quota use, machines are distributed among reservations in round-robin fashion.
If multiple storage paths are available on a reservation with sufficient capacity to provision the machine volumes, storage paths are selected according to the following logic.
If the blueprint or request specifies a storage reservation policy, the storage path must belong to that storage reservation policy.
If the custom property VirtualMachine.DiskN.StorageReservationPolicyMode is set to Not Exact, and no storage path with sufficient capacity is available in the storage reservation policy, then provisioning proceeds with a storage path outside the specified storage reservation policy. The default value of VirtualMachine.DiskN.StorageReservationPolicyMode is Exact.
Storage paths with higher priority are selected over reservations with lower priority.
If multiple storage paths have the same priority, machines are distributed among storage paths by using round-robin scheduling.