Deploying a Software Ecosystem from a Solution Template

Teradata® Software for Azure Installation and Administration Guide

prodname
Teradata Software for Azure
vrm_release
6.02
category
Administration
Configuration
Installation
featnum
B035-2810-128K
  • 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.
Azure solution templates allow you to deploy multiple Teradata software products simultaneously. The deployment creates a new resource group containing the VNet, VMs, storage accounts, network security groups, and so on. When deploying, you can create a new resource group or use an existing, empty resource group.

Solution templates create one NSG for all the software launched during the deployment process. Components are defined as the Teradata Database and each software product you deploy. Some ports to these NSGs open automatically after completing this procedure. For more information, see Network Security Groups and Ports.

  1. Log in to the Azure Marketplace and search for Teradata.
  2. Under either Teradata Vantage or Teradata Vantage with IntelliSphere, click Get it now.
  3. From the Software plan menu, select the appropriate Teradata Vantage solution template, then click Continue.
    Solution Template Purchase Option
    Hourly BYOL
    Teradata Vantage  
    Teradata Vantage (BYOL)  
    Teradata Vantage with IntelliSphere  
    Teradata Vantage with IntelliSphere (BYOL)  
    See Teradata Software Purchase Options.
  4. Read through the summary, then click Create.
  5. In the solution template, configure the settings on the Basics blade, then click OK.
    If the interface times out while completing this procedure, return to the previous blade and click OK again so you can continue where you left off.
    Parameter Action
    User name Enter a user name.
    Authentication type Select an authentication method.
    For security reasons, we strongly recommend an SSH public key.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Password
    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.
    Subscription Select a 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.
    See Resource Groups.
    Location Select a region to deploy the solution.

    See Location and Time Zone Considerations.

  6. Configure the settings on the Teradata Database blade, then click OK.
    Parameter Action
    System name prefix Accept the default or enter a prefix for all nodes in the cluster.

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

    DBC password Enter a new default Teradata Database password, using 12 to 15 characters starting with a letter. The following special characters are allowed: ! @ # $ % ^ & * < >.

    For security reasons, you must change the default DBC password to a different password.

    Confirm DBC password Enter the password again to confirm.
    Japanese language support Click Yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is No.
    Entitlement ID

    [BYOL only]

    Enter the entitlement ID (EID) from the email you received after you purchased the license.

    See Bring Your Own License.

    Term of License

    [BYOL only]

    Select a license period that corresponds to the term from the email you received when you purchased the license.
    • 1 Year
    • 3 Years
    • POC: Short-term license (30, 60, or 90 days) used for a proof of concept

    The license period is visible as a suffix to the name in the Product column after you log in to the Teradata EMS server.

    See Bring Your Own License.

    Database Version Select the Teradata Database release version.
    Database Tier Select Enterprise, Advanced, Base, or the free Developer tier.

    See Teradata Database License Tiers.

    VM Size Select a supported VM size.

    See Teradata Database VM Sizes.

    Storage Size Per Node (in TB) Select a supported storage size per node (in TB).
    Scale Out/In

    [B, A, E only1]

    • Select None to disable this feature (default). If you select None, you can still scale out after deployment.
    • Select Scale Out-Ready to set aside 1 to 32 nodes that are available to scale out in the future. Selecting this option automatically allocates 3 extra private IP addresses per subnet, per node.
    • Select Scaled Out-2x to deploy 2 to 32 nodes (in multiples of 2). Selecting this option automatically allocates 1 extra private IP address per subnet, per node.
    • Select Scaled Out-4x to deploy 4 to 64 nodes (in multiples of 4). Selecting this option does not allocate any extra private IP addresses.

    See Scaling Out a System During Deployment.

    Number of nodes Enter the starting number of nodes (x) you want to deploy.

    To determine supported options for scaling out or scaling in, see Supported Node Counts.

    Temporal Select Yes to enable temporal. The default setting is No.

    When enabled, temporal data is displayed in UTC time, so you must set the time zone parameter to UTC. To use a different time zone, contact Teradata Consulting Services to schedule an appointment to enable temporal.

    Teradata Intelligent Memory (TIM)

    [A, E only1]

    Click Yes to enable TIM. The default setting is No.
    TIM Cache Percent If you enabled TIM, type a cache percent from 1 to 80 to specify the size of the hot cylinder cache as a percentage of FSG cache.

    See the ctl utility in Teradata® Database Utilities and the Teradata® Intelligent Memory Orange Book. To find an Orange Book, go to https://access.teradata.com, log in, and search for the book title.

    Row Level Security Click Yes to enable row-level security. The default setting is No.
    Secure Zones Click Yes to enable secure zones. The default setting is No.
    Mainframe Connectivity Enter the number of parsing engines per node (up to 2) you want for mainframe connectivity. Enter 0 if you do not want to connect to a mainframe.
    1 License tiers: D/Developer, B/Base, A/Advanced, E/Enterprise
  7. [Optional] On the Viewpoint blade, click Yes to configure the settings, then click OK. You must configure Viewpoint if you plan to use the following software:
    • Data Mover
    • Data Stream Controller
    • Ecosystem Manager
    • QueryGrid*
    • Server Management
    • Unity
    • Viewpoint
    *For QueryGrid, you must use Viewpoint Multiple Systems or Viewpoint (IntelliSphere). You can use an on-premises installation or follow these steps to deploy on Azure.
    Parameter Action
    Viewpoint system name prefix Accept the default or enter a prefix for all nodes in the cluster.

    The default is viewpoint. The prefix displays in the Azure portal after deploying the VM.

    System nickname Enter a nickname to use to configure Viewpoint.
    Viewpoint portal admin user password Enter the Viewpoint administrator password for the Viewpoint portal, using 12 to 15 characters, starting with a letter. It can contain only letters and numbers.

    Use this password to log in to the Viewpoint portal with the admin user name.

    Confirm portal admin user password Enter the password again to confirm.
    Viewpoint Image version Select a Viewpoint image:
    • Teradata Vantage with IntelliSphere:
      • Teradata Viewpoint (IntelliSphere)
    • Teradata Database:
      • Teradata Viewpoint
      • Teradata Viewpoint with Data Lab
      • Teradata Viewpoint (Multiple Systems)
    See Teradata Software Purchase Options.
    VM size Select a supported VM size (storage size is per node).

    See Supporting Software VM Sizes.

  8. [Optional] On the Server Management blade, click Yes to configure the settings, then click OK.
    Parameter Action
    Site ID

    [B, A, E only1]

    String that identifies this Teradata deployment for Teradata Customer Support (AZRTDB followed by up to 9 numbers). If you do not have the site ID, you can continue without it and add it later. See Site IDs.
    Server Management System name prefix Accept the default or enter a name for all deployed Server Management VMs.
    Server Management admin password Enter the Server Management administrative password, using 12 to 15 characters, starting with a letter. It can consist of only letters and numbers.
    Confirm admin password Enter the password again to confirm.
    Server Management REST password Enter the Server Management REST password, using 12 to 15 characters, starting with a letter. The password can contain only letters and numbers.
    Confirm REST password Enter the password again to confirm.
    Server Management VM Count Number of Server Management VMs (CMICs) to deploy. Minimum for high availability: 2.
    If you deploy one CMIC, you cannot add a second one later. You will have to remove the first one, then redeploy two.
    VM Size Select a supported VM size (storage size is per node).

    See Supporting Software VM Sizes.

    1 License tiers: D/Developer, B/Base, A/Advanced, E/Enterprise
  9. [Optional] On the Teradata Query Service blade, click Yes to configure the settings, then click OK.
    Parameter Action
    Teradata Query Service system name prefix Enter a prefix for all Query Service nodes in the cluster.
    VM size Select a supported VM size (storage size is per node).

    See Supporting Software VM Sizes.

  10. [Optional] On the Data Stream Controller blade, click Yes to configure the settings, then click OK.
    Parameter Action
    DBC password Enter a new default Teradata Database password.

    For security reasons, you must change the default DBC password to a different password.

    Confirm DBC password Enter the password again to confirm.
    DSC admin password Enter the DSC Administrative password, using 12 to 15 characters, starting with a letter. The password can contain only letters and numbers.
    Confirm DSC admin password Enter the password again to confirm.
    DSC system name prefix Enter a prefix for all DSC nodes.

    After the VM is created, a dsc prefix appears in the Azure portal followed by a VM number. For example, dsc-vm0, dsc-vm1, dsc-vm2, and so on.

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

    See Supporting Software VM Sizes.

  11. [Optional] On the Ecosystem Manager blade, click Yes to configure the settings, then click OK.
    Parameter Action
    Ecosystem Manager system name prefix Accept the default or enter a prefix for all nodes in the cluster.

    The default is ecosysmgr. 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.

  12. [Optional] On the Data Mover blade, click Yes to configure the settings, then click OK.
    Parameter Action
    DBC user password Enter a Teradata Database password, using 12 to 15 characters. The password can contain letters and numbers, but numbers are not required. The following special characters are allowed: ! @ # $ % ^ & * < >.

    For security reasons, you must change the default DBC password to a different password.

    Confirm DBC user password Enter the password again to confirm.
    DATAMOVER user password Enter a user password to access the internal DATAMOVER repository, using 12 to 15 characters, starting with a letter. The password can contain only letters and numbers.

    For security reasons, you must change the default datamover password to a different password.

    Confirm DATAMOVER user password Enter the password again to confirm.
    Data Mover system name prefix Enter a prefix for all Data Mover nodes.
    After the VM is created, this prefix appears in the Azure portal followed by the agent name and number. For example, a 4-node Data Mover cluster displays the following:
    • prefix-DM-Master-Agent1
    • prefix-DM-Agent2
    • prefix-DM-Agent3
    • prefix-DM-Agent4
    Additional agents Enter the number of additional agents (nodes) you want to deploy from 0 to 3. One node is already included for the master.
    VM size Select a supported VM size (storage size is per node).

    Although other sizes are available, the recommended size for production workloads is DS5_v2.

    See Supporting Software VM Sizes.

  13. [Optional] On the QueryGrid Manager blade, click Yes to configure the settings, then click OK. Prerequisite: To use QueryGrid Manager, you must use Teradata Viewpoint Multiple Systems or Teradata Viewpoint (IntelliSphere). You can use an on-premises installation or follow these steps to deploy on Azure.
    Parameter Action
    QueryGrid system name prefix Enter a prefix for all QueryGrid nodes.

    After the VM is created, a querygrid prefix appears in the Azure portal followed by a VM number. For example, querygrid_manager1, querygrid_manager2, and so on.

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

    See Supporting Software VM Sizes.

  14. [Optional] On the Unity blade, click Yes to configure the settings, then click OK.
    Parameter 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.

  15. Click the General Settings blade to configure additional settings applicable to all components, then click OK.
    Parameter   Action
    Virtual network Name Accept the default or enter a name for the virtual network.

    The default is (new) vnet-teradata. The name displays in the Azure portal as a resource after the VM deploys.

    Subnets VM subnet name Enter a name for the VM subnet.
    VM subnet address prefix Enter a CIDR block for the private subnet. The template creates a new private subnet in the selected VNet using this CIDR address.

    For Teradata Database MPP VMs, make sure the CIDR range you calculate is 2 IPs per node, plus 5 additional IPs for the subnet. Other Teradata ecosystem products also need IPs in this subnet. For example, you can have up to 9 VMs, you need 9 additional IPs.

    See VNets.

    In the Azure portal, make sure the CIDR address you enter is not being used by existing subnets in the same VNet.

    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.

    The time zone for Teradata Server Management and Teradata Ecosystem Manager is UTC and cannot be changed by this parameter.

    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.

  16. Click the Summary blade, review the information, then click OK.
  17. Click the Buy blade, review the terms of use and privacy policy, then click Create. 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 may cause the creation of the VM to fail. Do not try to SSH into the VM until you get confirmation the VM was created or you receive a failure notification.
  18. To monitor the VM creation progress, do the following from the Azure portal:
    1. Click to see notifications the deployment 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 resources and look at the right pane 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.


  19. If you are using Data Mover, Data Stream Controller, Ecosystem Manager, Query Service, or Viewpoint and want to use public IP addresses, do the following after creating the VMs:
    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.
  20. If you deployed QueryGrid Manager, you must deploy the desired QueryGrid connectors. For instructions, see Teradata® QueryGrid™ Installation and User Guide.
    Teradata Vantage Solution Template Obtaining Connectors
    Teradata Vantage with IntelliSphere QueryGrid connectors are included in the IntelliSphere bundle and deployed with the QueryGrid image.
    Teradata Vantage Contact Teradata Consulting Services to purchase QueryGrid connectors.
  21. If you enabled row-level security, go to the SSH client console and type the following: # dbscontrol -a | grep -i rls

    Sample output:

    RLSPurchased = True See Teradata® Database Security Administration.
  22. If you enabled secure zones, go to the SSH client console and type the following: # dbscontrol -a | grep -i securezones

    Sample output:

    SecureZonesPurchased = True See Teradata® Database Security Administration.
  23. [BYOL only] If you receive licensing errors, see Licensing Issues.
  24. [BYOL only] Monitor the deployment continuously for errors, warnings, or alerts.