If the system includes more than one Provider VDC, and at least two of those Provider VDCs use a common set of storage profiles, a VMWVdcTemplate in that system can include multiple ProviderVdcReference elements. Each time this sort of template is instantiated, the system evaluates the current resource commitments of each of the referenced Provider VDCs and chooses the one best able to support a new organization VDC.

A VDC template that includes routed networking and specifies multiple Provider VDCs must include references to the following objects:
  • Two or more candidate Provider VDCs that share at least one storage profile. Each of the Provider VDCs must have at least one available external network.
  • A reference to a Provider VDC storage profile defined in all candidate Provider VDCs
  • A network pool specification.
When this form of VDC template is instantiated, it creates an organization VDC that is backed by one of the candidate Provider VDCs.

When you specify multiple Provider VDCs in a template that includes networking, you must also add a Binding element to each ProviderVdcReference. A Binding associates a symbolic name with an external network in the Provider VDC. You use this symbolic name as the value of the href attribute of the Network configured in the template. When the template is instantiated, the system replaces the symbolic name with a reference to the network specified in the Value element of the Binding.


This operation is restricted to system administrators.

Use a procedure like the one shown in Create a VDC Template or Create a VDC Template That Includes Routed Networking to create a VMWVdcTemplate request body. You can specify multiple Provider VDCs in a VDC template whether or not the template includes routed networking. The procedure shown here adds another Provider VDC to the template shown in Create a VDC Template That Includes Routed Networking.


  1. List the Provider VDCs that exist in the system.
    You can use a query like this one to list all the Provider VDCs in the system.
    GET https://vcloud.example.com/api/query?type=providerVdc&format=references
  2. List the external networks and network pools available in each Provider VDCto specify in this VDC template.
    Use a request like this one to retrieve the XML representation of the Provider VDC:
    GET https://vcloud.example.com/api/admin/extension/providervdc/35
    The AvailableNetworks element in the response lists the external networks created in that Provider VDC. The NetworkPoolReferences element in the response lists references to all network pools created in that Provider VDC.
    <vmext:VMWProviderVdc ... >
             href="https://vcloud.example.com/api/admin/network/297" />
          <vcloud:Network ... />
          <vcloud:Network ... />
             href="https://vcloud.example.com/api/admin/extension/networkPool/313" />
  3. For each Provider VDC that you include in this template, create a ProviderVdcReference that references the Provider VDC and includes a Binding element that references an external network available in that Provider VDC.
  4. POST the VMWVdcTemplate request body to the system's add link for vdcTemplates.


The system creates the new VDC template and returns a VMWVdcTemplate element that includes a set of Link elements that you can use to access, remove, or modify the new template.

Example: Create a VDC Template With Routed Networking and Multiple Provider VDCs

This request creates a VDC template that is identical to the one shown in Create a VDC Template That Includes Routed Networking, but adds a second ProviderVdcReference and includes Binding elements that provide symbolic references to external networks.

The Binding element in each ProviderVdcReference pairs a Name element that contains a user-specified identifier in URN format with a Value element that specifies the href of an external network in the candidate Provider VDC. The GatewayConfiguration of the template uses that URN instead of a URL for the href attribute of its Network element.
<Network href="urn:vcloud:binding:35c80ae2-36ef-4e2f-a430-ca704db9709f"/>
When the template is instantiated, this URN is replaced by the network URL in the Value part of the Binding associated with the ProviderVdcReference that the system selects during instantiation.

This example also uses the AutomaticNetworkPoolReference flag to specify that organization VDCs created by instantiating this template use the VXLAN network pool that was created automatically when the Provider VDC was created. If you decide not to use AutomaticNetworkPoolReference in a VDC template that specifies multiple Provider VDCs, you must specify a network pool that exists in one of the candidate Provider VDCs. All organization VDCs that are created from this template use that pool, regardless of the Provider VDC that is chosen during instantiation.

POST https://vcloud.example.com/api/admin/extension/vdcTemplates
Content-Type: application/vnd.vmware.admin.vmwVdcTemplate+xml
<?xml version="1.0" encoding="UTF-8"?>
   <Description>Example AllocationVapp VDC Template with Gateway</Description>
         <vmext:Value href="https://vcloud.example.com/api/admin/network/297"></vmext:Value>
         <vmext:Value href="https://vcloud.example.com/api/admin/network/99"></vmext:Value>
         <Gateway name="theEdge">
            <Description>Edge Gateway defined by VDC template</Description>
                     <DisplayName>Uplink interface defined by VDC template</DisplayName>
         <Network name="RoutedOVDCNet">
            <Description>Routed through an Edge Gateway</Description>
      <StorageProfile name="Bronze">