5.1

Table Of Contents
<Link
rel="down"
type="application/vnd.vmware.vcloud.metadata+xml"
href="https://vcloud.example.com/api/admin/vdc/44/metadata" />
<Link
rel="alternate"
type="application/vnd.vmware.vcloud.vdc+xml"
href="https://vcloud.example.com/api/vdc/44" />
<Link
rel="down"
type="application/vnd.vmware.admin.OrganizationVdcResourcePoolSet+xml"
href="https://vcloud.example.com/api/admin/extension/vdc/44/resourcePools" />
<Description>Example vDC</Description>
...
<Tasks>
<Task
name="task"
status="running"
operation="Creating Virtual Datacenter org26vdc1(44)"
...
</Task>
</Tasks>
<AllocationModel>AllocationVApp</AllocationModel>
...
<Capabilities>
<SupportedHardwareVersions>
<SupportedHardwareVersion>vmx-04</SupportedHardwareVersion>
<SupportedHardwareVersion>vmx-08</SupportedHardwareVersion>
</SupportedHardwareVersions>
</Capabilities>
...
</AdminVdc>
When construction is complete, the status changes to 1 and the Task is no longer included in representation.
The following changes in the AdminVdc are also evident:
n
A reference to the vSphere resource pool that supports the vDC appears in a VCloudExtension element.
n
There is an empty ResourceEntities element, because the vDC contains no Media, VAppTemplate, or Disk
entities. For information about adding them, see Chapter 4, “Provisioning an Organization,” on page 55.
n
There is an empty AvailableNetworks element. To add networks to this organization vDC, see “Create an
Organization vDC Network,” on page 166.
n
Additional Link elements are included for operations that are now valid, but that were not valid while the
vDC was under construction.
<AdminVdc
xmlns="http://www.vmware.com/vcloud/v1.5"
xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5"
status="1"
name="org26vdc1"
id="urn:vcloud:vdc:44"
type="application/vnd.vmware.admin.vdc+xml"
href="https://vcloud.example.com/api/admin/vdc/44" ... >
<VCloudExtension
required="false">
<vmext:VimObjectRef>
Chapter 6 Creating and Managing Organizations
VMware, Inc. 143