Deployer 3.01 - Deploying Teradata Database on VMware for Sites with Internet Access - Teradata Database on VMware

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

Teradata Database on VMware
Deployer 3.01
January 2018
Before starting this procedure, do the following:
Your deployment site must have access to the web-based Teradata EMS server for this procedure. If your site cannot access the Internet, see Deploying Teradata Database on VMware for Sites without Internet Access.
  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
  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 and 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. From the PowerCLI terminal, type deploy. For a description of the actions this state (command) performs, PowerCLI Commands for Teradata Database on VMware.
  9. 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.