Preparing the ova Templates

Teradata® Database on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

brand
Cloud
prodname
Teradata Database on VMware
vrm_release
Deployer 3.02
category
Configuration
Installation
featnum
B035-5958-018K
Check that you have installed the VMware Client Integration Plug-in on your workstation. Access the VMware Knowledge Base and search for Installing VMware Client Integration Plug-in. If you have the plug-in installed, ensure it has been upgraded to the latest version.
Before initially deploying the VM, this procedure describes how to upload the .ova file to the vCenter and convert it to a template. Having the template reside on vCenter enables the VM to quickly deploy. Having the template reside on your local system takes the VM longer to deploy.

For best results, use either Internet Explorer 11 or Google Chrome as your browser.

  1. Log in to the vSphere Client using your login credentials.
  2. Under Inventories, select Hosts and Clusters to see all the ESXi hosts managed by the vCenter server.
  3. Right-click the ESXi host name on which you want to clone the VM, and select All vCenter Actions > Deploy OVF Template. If menus differ, look under All vCenter Actions.
  4. From the Deploy OVF Template dialog box, do the following to begin the cloning process:
    1. Under Select source, select Local file, then click Browse and go to the directory containing the .ova file that you want to clone. For example, C:\powercli6\templates\SP3\Teradata_Database_16.20.xx.xx_SLES11_SP3_on_VMware_20170707125811.ova
    2. Click Next.
    3. Under Review details, verify the .ova file, and click Next.
    4. Under Select name and folder, select a folder or datacenter in your vCenter server in which to clone your VM, modify the name of the VM to make it unique (for example, Teradata_Database_16.20.xx.xx_SLES11_SP3_on_VMware_20170707125811, where 16.20.xx.xx represents the template version you are using), and click Next.
    5. Under Select storage, select the datastore on which you want to clone the VM, then select Thin Provision from the Select virtual disk format menu if you want to speed up the clone time and save space in the datastore, and click Next. Leave the VM Storage Policy as is.
    6. Verify all information, and click Finish to clone the template.
  5. From the vSphere Client, do the following to verify the VM was cloned:
    1. Click the ESXi host name on which you cloned the VM.
    2. Click the Related Objects tab.
    3. Click Virtual Machines.
    4. Under the Name column, verify the VM is in a powered off state and the status is normal.
  6. Under the Name column, right-click the VM you cloned, and select All vCenter Actions > Convert to Template. The VM is converted to a template.
  7. From the vSphere Client, do the following to verify the VM was converted to a template:
    1. Click the ESXi host name on which you cloned the VM.
    2. Click the Related Objects tab.
    3. Click VM Templates.
    4. Under the Name column, verify the template appears.
  8. If you have a physical server with 2 to 7 pNodes, you must clone the template to another ESXi host.
    1. From the Related Objects, click VM Templates.
    2. Right-click the template name, and select All vCenter Actions > Clone to Template.
    3. Under Select a name and folder, enter a name of the new template, then select a folder or datacenter in your vCenter server to put the new template, and click Next.
    4. Under Select a compute resource, select the ESXi host and its datastore to host the template, and click Next.
    5. Under Select storage, select the virtual disk format.
    6. If you want to speed up the clone time and save space in the datastore, select Thin Provision from the Select virtual disk format menu, and click Next.
    7. Under Ready to complete, verify all information, and click Finish to clone the template.
Following are examples of deploying VMs from vCenter for either of the latest Teradata Database versions and associated products. For the latest template version numbers, see Templates.

The template name in the examples below is the VM name you modified in step 4d.

{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "tpa",
   "Template":  "Teradata_Database_16.20.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "tpa",
   "Template":  "Teradata_Database_15.10.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "vp",
   "Template":  "Teradata_Viewpoint_16.20.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "cmic",
   "Template":  "Teradata_CMIC_12.07.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "dsu",
   "Template":  "Teradata_DSC_16.20.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "em",
   "Template":  "Teradata_EM_16.20.xx.xx_SLES11_SP3_on_VMware_20170707235215"
}