6.02 - Deploying Unity from a Solution Template - Teradata Software for Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Teradata Vantage on Azure
Release Number
Release Date
January 2019
Content Type
Publication ID
English (United States)
  • You must log into the Azure portal using an account with sufficient permissions in the Azure subscription and be assigned the Contributor role at the subscription level. See Azure Documentation Center.
  • You might need to increase Azure service limits. See Azure Service Limits.
Deploying Unity from a solution template creates a new Azure resource group and connects the Unity VMs to an existing subnet in the same VNet as the Teradata Database VM and the software application VMs.

During the deployment process, this template creates one NSG for Teradata Unity. All ports to the NSG automatically open after completing this procedure.

  1. Log in to the Azure Marketplace and search for Teradata Unity.
  2. Select Teradata Unity, then click Get it now > Continue.
  3. In the listing, click Create.
  4. Click the Basics blade to configure basic settings.
    Parameter Name Action
    User name Enter the operating system admin name used to log in.
    Authentication type Select an authentication method.
    For security reasons, Teradata strongly recommends an SSH public key.
    Enter a password of at least 12 characters, using at least 1 lower case character, 1 upper case character, 1 number, and 1 special character. Enter the password again to confirm.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Subscription Select an Azure subscription.
    Resource group Select one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    Location Select a region where you want to deploy the solution and where all resources will be created.
  5. Click OK.
  6. Click the Unity blade to configure the settings.
    Parameter Name Action
    Unity system name prefix Accept the default or enter a prefix for all nodes in the cluster.

    The default is unity. The prefix displays in the Azure portal after the VM deploys.

    VM size Select a supported VM size (storage size is per node).

    See Supporting Software VM Sizes.

  7. Click OK.
  8. Click the Network Settings blade to configure the virtual network.
    Parameter Name Action
    Existing Virtual Network Accept the default or enter a prefix for all nodes in the cluster.

    The default is unity. The prefix displays in the Azure portal after the VM deploys.

    Subnet Review your subnet configuration.
    NTP server list Use the default or enter one or more network time protocol servers, separated by commas.
    Time zone Enter the operating system time zone. The default time zone is UTC.

    If you enable temporal, you must set the time zone parameter to UTC. If you want to use a different time zone, contact Teradata Consulting Services to enable temporal.

  9. Click OK.
  10. Click the Summary blade, review the summary, and click OK.
  11. Click the Buy blade, review the terms of use and privacy policy, and click Purchase. This process can take 20 to 60 minutes depending on your configuration and the availability of resources in your region.
    Trying to SSH into the VM might cause the creation of the VM to fail. Do not try to SSH into the VM until you receive either a confirmation the VM was created or a failure notification.
  12. To monitor the VM creation progress, do the following from the Azure portal:
    1. Click to see notifications to determine if the deployment has started. Notifications send alerts only if you have set them prior to starting the deployment.
    2. From the left panel, click the Resource groups blade.
    3. Under the Name column, select a resource.
    4. Under Settings, click Deployments.
    5. Select any of the resources and look at the pane to the right to see if they are being deployed. The deployment is not complete until all VMs in the cluster are provisioned and the automatic process of configuring the database has finished. Under Operation details, a blue status symbol appears in the first column next to each resource to indicate the deployment process is continuing.
    6. Click located at the top of the right pane to refresh the pane. Under Operation details, the blue status symbol changes to a green check mark in the first column next to each resource to indicate the deployment process has finished.
    7. Under Operation details, when the STATUS column displays OK, select the resource. The PROVISIONING STATE displays Succeeded.
  13. If you want to use public IP addresses, do the following after the VMs are created.
    1. Create the public IP addresses and assign these addresses to a VM. See https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address.
    2. Adjust the NSG rules to accept connections using public IP addresses to allow access. The solution template defines an NSG for each software product VM.