This dual-region design supports provisioning workloads across regions from the same portal using the same single-machine blueprints. A synchronization mechanism is required to have consistent templates across regions. There are multiple ways to achieve synchronization, for example, vSphere Content Library or external services like vCloud Connector or vSphere Replication.

Table 1. Template Synchronization Design Decision

Decision ID

Design Decision

Design Justification

Design Implication


This design uses vSphere Content Library to synchronize templates across regions.

The vSphere Content Library is built into the version of vSphere being used and meets all the requirements to synchronize templates.

Storage space must be provisioned in each region.

vRealize Automation can not directly consume templates from vSphere Content Library.

When users select this blueprint, vRealize Automation clones a vSphere virtual machine template with preconfigured vCenter customizations.

Figure 1. Template Synchronization

In this VMware Validated Design, when the user selects a blueprint, vRealize Automation clones a virtual machine template from a local vSphere content library