VMware

VMware VirtualCenter 1.4.x Support Documentation


Documentation | Knowledge Base | Discussion Forums

previous Prev   Contents   Last   Next next

Understanding Templates

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, a set of applications, and a configuration which provides virtual counterparts to hardware components.

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

Link to templatecreate.png

Creating a Template Overview

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 managed 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 of abbreviations.

Link to templatedeploy.png

Deploying a Template

Templates are created from:

  • Existing virtual machines. These virtual machines can be either:
  • GSX Server, VMware Server, or ESX Server - virtual machines located on any VirtualCenter managed host.

    • To create a template from a virtual machine on an ESX Server, GSX Server, or VMware Server host, VirtualCenter must manage the host.

  • GSX Server or Workstation - virtual machines stored on a disk local to the VirtualCenter server.
  • Existing templates by making a copy of (cloning) 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 is 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 one from the available datastores. The datastore does not need to be the same datastore as the one on 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 managed 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 or VMware Server hosts: The datastore is a designated directory. Each GSX Server or VMware Server host is allowed only one datastore at a time. You can change the designated datastore and rename it, but only one datastore at a time is allowed. Refer to Configuring Datastores on GSX Server or VMware Server Hosts for information on designating a GSX Server or VMware Server datastore.

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

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

    Link to processtemplates.png

    Creating a Template Options

    previous Prev   Contents   Last   Next next