Before successfully completing the configuration of blueprints, create a template in the endpoint in which resources will be provisioned. One key goal when creating this template is to make the VM template as reusable as possible. This allows the one template to be used by many blueprints in vRealize Automation. This helps ease the management overhead of blueprints, since there are fewer templates to manage. Reducing the amount of software installed on the template also reduces the number of updates that need to be made to the template.

For implementations in which vRealize Automation is deployed in vCloud Director, and for managing the OrgVDC in which it is contained, cloud service provider administrators create the vApp templates and publish them in the public catalog for consumption.

In fully managed offerings in which vSphere is used as the compute resource, the required VM templates have to be created by the cloud service provider administrators in each respective hosted vSphere instance. For dedicated private cloud offerings, the customer’s internal administrators are responsible for creating the necessary VM templates for use with vRealize Automation blueprints.