VMware VirtualCenter 1.1 Support Documentation

 Prev   Contents   Last   Next 

A template is a golden image created from a virtual machine. The template, as did the source virtual machine, typically includes a specified operating system and a configuration which provides virtual counterparts to hardware components. A template can also include an installed guest operating system and a set of applications.

The figure below illustrates creating a template from a managed virtual machine on an ESX Server and a GSX Server. Refer to Abbreviations for a description of abbreviations.

Creating a Template Process

VirtualCenter uses virtual machine templates as a quick and consistent method for adding new virtual machines to the VirtualCenter environment. This process of deploying a template includes selecting the appropriate template and designating a VirtualCenter target host to receive the new virtual machine. The deployed virtual machine is added to the farm where the host resides. Refer to Creating Virtual Machines from a Template for additional information on deploying templates.

The figure below illustrates creating a new virtual machine from a template (deploying a template) using the optional virtual machine customization feature. Refer to Abbreviations for a description o abbreviations.

Deploying a Template

Templates are created from:

• Existing virtual machines. These virtual machines can be either:
  • GSX Server and ESX Server virtual machines located on any VirtualCenter managed host.

    To templatize a virtual machine on an ESX Server or GSX Server host, the host must be registered with VirtualCenter.

  • Workstation virtual machines stored on a disk local to the VirtualCenter server.
• Existing templates, by making a copy (cloning) of the template.

Templates are stored at the following locations:

• Template upload directory — On the VirtualCenter server machine. A copy of the original virtual machine virtual disks are placed in the directory you specify as the template upload directory.

  This method is useful when your source virtual machine is not located on a SAN-based storage device.

  Templates in the template repository can be deployed to any host managed by VirtualCenter.

• Datastore — On the managed host with the source virtual machine. Select a datastore, if there are several available. The datastore does not need to be the same datastore as the original virtual machine.

  This method is useful for rapidly deploying templates.

  After a template is created, if it is residing on a VMFS volume or a datastore other than the VirtualCenter template repository, it can be deployed to only hosts that have direct access to that datastore.

  On ESX Server hosts: the datastores are the VMFS volumes you configured for your ESX Server. You can configure any number of VMFS volumes per ESX Server host.

  On GSX Server hosts: the datastore is a designated directory. Each GSX Server host is allowed only one datastore at a time. You can change the designated datastore and rename it, but only one at a time is allowed. Refer to Configuring Datastores on GSX Server Hosts for information on designating a GSX Server datastore.

  Note: If a host that has a templates stored locally (not in the template repository) is removed from VirtualCenter, all the templates are also removed. Returning the host to VirtualCenter does not re-register the templates.

• Local to the source virtual machine — This option is available for, but not limited to, importing Workstation formatted virtual machines and is not recommended.

  This method is useful when your source virtual machine is located on a SAN-based storage device.

The figure below illustrates the options for creating a template from various virtual machine sources. This includes, ESX Server golden images, as well as managed and unmanaged virtual machines. Refer to Abbreviations for a description of abbreviations.

Creating a Template Options