Prepare Virtual Machines from .ova Files | Teradata Vantage on VMware - Preparing Virtual Machines from .ova Files - Teradata Vantage on VMware

Teradata Vantage™ on VMware Base, Advanced, Enterprise Tiers Getting Started Guide
Product
Teradata Vantage on VMware
Release Number
Deployer 3.04
Published
October 2021
Language
English (United States)
Last Update
2021-10-29
dita:mapPath
qbi1545241606156.ditamap
dita:ditavalPath
lyx1526581533412.ditaval
dita:id
B035-5958
Product Category
Cloud
PrerequisiteCheck 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, make sure it has been upgraded to the latest version.
Before initially deploying the VM, use this procedure to upload the .ova file to the vCenter and then convert it to a template.

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 select Browse and go to the directory containing the .ova file that you want to clone.
      For example, C:\powercli6\templates\SP3\Vantage_Advanced_SQL_XX.XX.xx.xx_SLES12_SP3_on_VMware_20170707125811.ova
    2. Select Next.
    3. Under Review details, verify the .ova file, and select Next.
    4. Under Select name and folder, select a folder or data center in your vCenter server in which to clone your VM, modify the name of the VM to make it unique, and select Next.
      For example, Vantage_Advanced_SQL_XX.XX.xx.xx_SLES12_SP3_on_VMware_20170707125811, where XX.XX.xx.xx represents the template version you are using.
    5. Under Select storage, select the datastore on which you want to clone the VM, select Thin Provision from the Select virtual disk format menu, and select Next.
      Leave the VM Storage Policy as is.
    6. Verify all information, and select Finish to clone the template.
  5. From the vSphere Client, do the following to verify the VM was cloned:
    1. Select the ESXi host name on which you cloned the VM.
    2. Select the VMs tab.
    3. Select 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. Select the ESXi host name on which you cloned the VM.
    2. Select the VMs tab.
    3. Select VM Templates in Folders.
    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 VMs tab, select VM Templates in Folders.
    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 data center in your vCenter server to put the new template, and select Next.
    4. Under Select a compute resource, select the ESXi host and its datastore to host the template, and select Next.
    5. Under Select storage, select the virtual disk format.
    6. Select Thin Provision from the Select virtual disk format menu, and select Next.
    7. Under Ready to complete, verify all information, and select Finish to clone the template.

Examples of deploying VMs from vCenter

Following are examples of deploying VMs from vCenter for the latest Vantage versions and associated products.

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

{
   "ESXiHost":  "esxi-05.company-domain.com",
   "Datastore":  "esxi-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "xx.xx.xx.xx",
   "vmType":  "tpa",
   "Template":  "Vantage_Advanced_SQL_XX.XX.xx.xx_SLES12_SP3_on_VMware_20170707235215"
}

{
   "ESXiHost":  "esxi-05.company-domain.com",
   "Datastore":  "esxi-05.datastore",
   "vmName":  "cobra27",
   "eth0":  "xx.xx.xx.xx",
   "vmType":  "tpa",
   "Template":  "Vantage_Advanced_SQL_XX.XX.xx.xx_SLES12_SP3_on_VMware_20170707235215"
}

{
   "ESXiHost":  "esxi-05.company-domain.com",
   "Datastore":  "esxi-05.datastore",
   "vmName":  "cobra28",
   "eth0":  "xx.xx.xx.xx",
   "vmType":  "cmic",
   "Template":  "Vantage_CMIC_XX.xx.xx.xx_SLES12_SP3_on_VMware_20170707235215"
}

{
   "ESXiHost":  "esxi-05.company-domain.com",
   "Datastore":  "esxi-05.datastore",
   "vmName":  "cobra30",
   "eth0":  "xx.xx.xx.xx",
   "vmType":  "dsu",
   "Template":  "Vantage_DSC_XX.XX.xx.xx_SLES12_SP3_on_VMware_20170707235215"
}

{
   "ESXiHost":  "esxi-05.company-domain.com",
   "Datastore":  "esxi-05.datastore",
   "vmName":  "cobra35",
   "eth0":  "xx.xx.xx.xx",
   "vmType":  "vp",
   "Template":  "Vantage_Viewpoint_TDRest_XX.XX.xx.xx.xx_SLES12_SP3_on_VMware_20170707235215"
}