Virtual Systems and Media Images in a vCloud
Virtual systems and media images are stored in a vDC and can be included in a catalog. Media images are
stored in their native representation (ISO or floppy). Virtual systems are stored as templates, using an open
standard format (OVF 1.0). These templates can be retrieved from catalogs and transformed into virtual
systems, called vApps, through a process called instantiation, which binds a template's abstract resource
requirements to resources available in a vDC. A vApp contains one or more individual virtual machines (Vm
elements), along with parameters that define operational details such as:
How the contained virtual machines are connected to each other and to external networks.
The order in which individual virtual machines are powered on or off.
End‐user license agreement terms for each virtual machine.
Deployment lease terms (typically inherited from the containing organization) that constrain the vApp's
consumption of vDC resources
Access control information specifying which users and groups can perform operations such as deploy,
power on, modify, and suspend on the vApp and the virtual machines it contains.
vCloud SDK for .NET Design
The vCloud SDK for .NET provides object‐specific methods for creating, updating, retrieving, and deleting
objects defined by the vCloud API. It also provides methods for operating virtual systems. The SDK includes
the following class libraries
com.vmware.vcloud.api.rest.schema provides constructor, getter, and setter methods for all objects
defined by the vCloud API.
com.vmware.vcloud.sdk provides methods that create, update, retrieve, and delete vCloud API objects.
com.vmware.vcloud.sdk.admin provides methods that create, update, retrieve, and delete vCloud
administrative API objects.
com.vmware.vcloud.sdk.admin.extensions provides methods that create, update, retrieve, and
delete vCloud API vSphere extension objects.
com.vmware.vcloud.sdk.utility provides utility methods that simplify the implementation of clients.
Many of the classes implemented in these libraries are wrapper classes whose methods access vCloud API
resources using an object reference. Each vCloud API object reference includes the URL (href attribute value),
resource type, and name properties that define the object. Static methods get resources by passing object
references, and act as constructors for SDK wrapper objects.
N
The vCloud SDK for .NET does not provide object lifecycle management. Every wrapper object
OTE
represents the resource at the time of the GET operation. If a client makes multiple GET requests for the same
resource, the client receives multiple representations of the resource wrapped in the helper object. There is no
automatic refresh of the client‐side representation. It is the client's responsibility to make new requests to get
the latest values. To avoid memory leaks, the client must dispose of objects that are not in use.
VMware, Inc.
Chapter 1 About the vCloud SDK for .NET
9