Creating and Editing Templates

Document created by esther.yoon on Jul 21, 2015Last modified by fran.schwarzmann on Aug 15, 2016
Version 3Show Document
  • View in full screen mode

This information can also be found in the user manual in your VMTurbo Operations Manager.

 

Creating and Editing Templates

 

To define a reservation, you specify the workload by choosing:

     • A VM template

       The VM template specifies the resources required for each VM you will deploy.

     • A Deployment Profile

       The Deployment Profile specifies deployment details such as the source VM package (the OVF or VHD files) and optional placement constraints.

 

Operations Manager creates a number of VM Templates automatically as it discovers source VM data on the target hypervisors. These templates are read‐only — you cannot edit them because they reflect data that is specified in your environment. Operations Manager also discovers associated Deployment Profiles that correspond with the discovered templates (also read‐only).

 

You can create your own VM Templates and Deployment Profiles, and use them to deploy VMs. In this way, you can plan for and deploy VMs with different configurations than any VMs currently defined in your environment.

 

 

Creating VM Templates

 

VM Templates describe the resource allocation that you want to provide for a class of VMs. When deploying VMs, Operations Manager uses the values that are specified in a chosen VM template. VM templates specify:

     • VCPUs

       The virtual CPUs assigned to the VM.

     • Virtual Memory

       The memory allocation for the VM, in MB. Note that you should never allocate less than is required for the guest OS.

     • Storage

       The amount of disk storage assigned to the VM, in GB.

     • Network Throughput Used

       The amount of the host’s network throughput to assign to the VM, in MB/s.

     • IOPS

       The IO operations per second allocated to the VM.

     • IO Throughput Used

       The amount of throughput on the host’s IO bus to assign to the VM, in MB/s.

 

The values you set for these resources determine the configuration of any VMs you deploy using this template.

 

To create a VM Template:

     1. Click the Create/Edit icon to open the dialog box.

    2. In the dialog box, click the Add icon for the VM Templates list.

         To edit an existing template, select the template and click the Edit icon. Note that you can only edit user‐created templates.

    3. In the fields that appear, enter settings for the VM Template.

         The Template Name and Vendor fields help identify the template for future use.

     4. Click Apply when you’re done.

 

 

Creating Deployment Profiles

 

A Deployment Profile specifies the physical files that will be copied to deploy the VM, as well as optional placement limitations.

 


NOTE: In many cases it’s best to let Operations Manager choose where to place the VMs you deploy. However, if you want to limit deployment to a specific datacenter or cluster, you can use a Deployment Profile to specify these constraints. If you are creating a profile for VMs in a Hyper‐V environment, you should always select a Hyper‐V datacenter or cluster for the profile.


 

Before creating the profile, you should know:

     • The path to the VM package files (OVF or VHD) that will be copied to create the VM

     • Optionally, the name of the datacenter or cluster that you want to deploy the VMs to

 

To create a Deployment Profile:

     1. Click the Create/Edit icon to open the dialog box.

     2. In the dialog box, click the Add icon for the Deployment Profiles list.

     3. In the fields that appear, provide the settings for the Deployment Profile.

     4. Click Apply when you’re done.

 

 

Discovered Deployment Data

 

Many hypervisor technologies support the use of source VMs as files that can be cloned, and the clones can be deployed as running VMs. For example, XenServer and CloudStack require the use of such source VMs to deploy new running VMs in their environments. When it performs discovery, Operations Manager identifies the source VM data on each hypervisor, and builds a corresponding set of VM Templates and Deployment Profiles.

 


NOTE: Hyper‐V targets do not include discovered VM Templates and Deployment Profiles. You must create these files

to deploy VMs in a Hyper‐V environment. In the Deployment Profile, you must specify a Hyper‐V datacenter, or a

cluster that is a member of a Hyper‐V datacenter.


 

For discovered VM Templates and Deployment Profiles, Operations Manager uses the following naming conventions:

     • VM Template — These names begin with the IP address of the hypervisor that stores them

     • Deployment Profile — These names begin with the characters DEP- for “Deployment”, and if they match a discovered template, the profile name mirrors the template’s name

 

To view the settings for a discovered template or profile, open the template editor and select the item you want to inspect. The editor shows the template or profile in a dimmed view.

 

You cannot edit a discovered VM Template or Deployment Profile. This is to preserve the integrity of the template and profile in relation to the source VM data.

Attachments

    Outcomes