You must perform some configuration outside of vRealize Automation to prepare for machine provisioning. To provision and manage machines in vCloud Director by using vRealize Automation, you prepare the organization virtual data center with templates and customization objects.

To provision vCloud Director vApps using vRealize Automation cloning, the organization requires a vApp template consisting of one or more virtual machine resources. vRealize Automation vApp blueprints and vApp component blueprints reference these resources. They also provide the ability to further configure machines during the provisioning and management process.

Templates that are to be shared across organizations must be public.

Note:

When you create a vApp blueprint by cloning from a vCloud Director template, that template's unique identifier (UID) becomes associated with the blueprint. When the blueprint is published to the vRealize Automation catalog and used in the provisioning and data collection processes, the associated vCloud Director template is recognized. If you delete the vApp template in vCloud Director, subsequent vRealize Automation provisioning and data collection fails because the associated template no longer exists. Instead of deleting and recreating a template, for example to upload an updated version, you can replace the template using the vCloud Director template replacement process. Using vCloud Director to replace the template, rather than deleting and recreating the template, keeps the template's unique ID intact and allows provisioning and data collection to continue functioning.

The following high-level overview is of the preparation required to provision vCloud Director vApps using vRealize Automation. For more information about vCloud Director administrator tasks, see vCloud Director product documentation.

  1. In vCloud Director, create a vApp template for cloning and add it to the organization catalog.

    Depending on access, the template can be added to the global catalog.

  2. In vCloud Director, use the vApp template to specify custom settings such as passwords, domain, and scripts for the guest operating system on each machine.

    You can use vRealize Automation to override some of these settings.

    Customization can vary depending on the guest operating system of the resource.

  3. In vCloud Director, configure the catalog to be shared with everyone in the organization.

    The vCloud Director organization administrator allows all users and groups in the organization to have access to the catalog. Without this sharing designation, the catalog templates are not be visible to tenant administrators or business group managers in vRealize Automation.

  4. Run endpoint data collection in vRealize Automation to collect your templates.

  5. Gather the following information so that tenant administrators and business group managers can include it in their blueprints:

    • Name of the vApp template.

    • Amount of total storage specified for the template.

      Note:

      Only reserved templates are available as a cloning source.