Deploying Teradata Database on VMware - Teradata Database on VMware

Teradata Database on VMware Developer Tier Getting Started Guide

Product
Teradata Database on VMware
Release Number
Deployer 3.01.01
Published
December 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
hph1509650909198.ditamap
dita:ditavalPath
TDVMWare_phase4a-4b_DEV.ditaval.ditaval
dita:id
B035-5938
lifecycle
previous
Product Category
Cloud
Before starting this procedure, do the following:
  1. Open a VMware vSphere PowerCLI shell version 5.5 or later.
  2. Type the following command from the PowerCLI prompt to connect to the vCenter that manages the ESXi hosts that will be running the Teradata Database VMs: connect-VIServer -server vCenter.server.name
  3. Navigate to the directory containing the Teradata Database on VMware deployment executable file (C:\mylocation\Teradata_Deployer\).
  4. [Optional] For troubleshooting purposes, make copies of the common.IT.properties.json and node.IT.properties.json properties files, label them according to the system to be deployed, and then save them.
  5. Run tdc.deploy.exe, using the properties files originally used to deploy the VMs.
  6. At the prompt, type deploy, and press Enter.
    1. Select the Common Properties file, and press Enter.
    2. Select the Node Properties file, and press Enter.
    The executable file connects to the vCenter server and validates the information in the properties files. When validation is successful, the executable file deploys the selected templates, and configures the VMs based on the values in the properties files.
  7. If a message warns you that running scripts is disabled, you must set the execution privileges, then proceed to the next step. See Setting PowerCLI Execution Privileges.
  8. Review the information and do one of the following:
    • If it is correct, press y.
    • If the information is incorrect, edit the properties files and re-run the deployment executable file.
If there are no errors, the VM deploys. The deployment executable file is re-entrant, meaning if errors occur, they can be fixed and the executable runs all states again. Action is only taken as needed.
After the VM deploys, complete the applicable procedures under Deployment Verification.