Machine blueprints determine a machine's attributes, the manner in which it is provisioned, and its policy and management settings. You can use the vApp (vCloud) blueprint to associate a vApp Component (vCloud) blueprint with each virtual machine in the vApp template. A vApp blueprint contains references to vApp component blueprints.
Before you can create a vApp blueprint, vApp component blueprints must exist for the component machines that are to be included in the vApp.
A member of the business group associated with a vApp blueprint can use the blueprint to provision a vApp and its virtual machines in a vCloud Air or vCloud Director organization. The provisioning process also produces a vApp machine and its component machines in vRealize Automation.
The vApp component blueprints must be available to the same business group as the vApp blueprint.
The vApp blueprint can specify a vApp template to be used to create the vApp and provision its component machines.
The vApp and its component machines use a machine prefix and the next available sequence of numbers, for example CA04, CA05, and CA06.
Administrators can specify a vApp lease duration. The lease specified in vRealize Automation overrides the lease specified in vCloud Director. Every 45 minutes, by default, a workflow checks if it needs to synchronize your vCloud Director or vCloud Air lease length.
If no lease length is specified in vRealize Automation, the lease length is interpreted as having been set to never expire. This lease length value is also evaluated by the synchronization workflow checker.
If a lease length conflict is found, the lease value is synchronized to match the lease length defined invRealize Automation. This prevents provisioned machines from expiring before the lease period that is defined in vRealize Automation is reached. The scheduled workflow checks the lease length values for provisioned machines every 45 minutes. To overwrite the 45 minute setting, reinstall the schedule by using repoutil.
You can also use the VCloud.Lease.Sync.TimeBufferMins custom property to specify a threshold integer for a compute resource such that lease synchronization only occurs for machines that are set to expire in that time period. The default value is 720 minutes, which is 12 hours. If VCloud.Lease.Sync.TimeBufferMins is not present, the default value is used. For example, if the default values are used, vRealize Automation runs the lease synchronization checker workflow every 45 minutes, and only the leases of machines that are set to expire in vCloud Director or vCloud Air within 12 hours are changed to match the lease length defined in vRealize Automation.
When a vApp expires, its component machines also expire. The vApp and its component machines are destroyed immediately when their lease expires.
As you create a vApp blueprint, you specify the vApp component blueprints to include in that vApp blueprint. While you must specify a vApp template to clone from when you create a vApp blueprint, template specification is optional when you create a vApp component blueprint. You might choose to specify a template when you create a vApp component blueprint if there are one or more settings in the template that you want to use in your component blueprint, for example a specific endpoint, compute resource, and storage setting combination. You can either use the settings from the template or change those settings for your blueprint. Blueprint settings are used during provisioning. If you have more than one component in a vApp template, you can use one vApp component blueprint for all the components.