Deploying a Teradata Ecosystem from a Solution Template

Prerequisite

Before deploying a Teradata ecosystem, you must be logged into the Azure portal using an account with a sufficient level of permissions in the Azure subscription and be assigned the Contributor role at the subscription level.For more information, see the Azure Documentation Center and search for Get started with access management in the Azure portal and Use role assignments to manage access to your Azure subscription resources. In addition, check if Azure service limits need to be increased. For more information, see Azure Service Limits.

Azure solution templates allow you to deploy multiple Teradata software products simultaneously. The deployment creates a new resource group containing all the resources you need, such as the VNet, network security groups, VMs, storage accounts, and so on. When deploying, you can choose to create a new resource group or use an empty existing resource group.

This template creates one NSG for all the software launched during the solution template deployment process. Components are defined as the Teradata Database and each software product you are deploying. Some ports to these NSGs are opened automatically after completing this procedure. For information about which ports are opened, see Network Security Groups and Ports.

If you plan to use Data Mover, Data Stream Controller, Ecosystem Manager, Server Management, or Viewpoint, you must configure Viewpoint as described in this procedure. You can select from one of three Viewpoint options to deploy as part of the Teradata ecosystem. Teradata Viewpoint (Single Teradata System) is included for free with your purchase of Teradata Database. You can select Teradata Viewpoint (Single Teradata System) with Data Lab or Teradata Viewpoint (Multiple Teradata Systems) at an additional cost.

For more information, see Deploying a Single Viewpoint VM from an Image.

If you are using Data Mover, Data Stream Controller, Ecosystem Manager, Server Management, or Viewpoint and want to use public IP addresses, you must create the public IP addresses after the VMs are created and adjust the NSG rules to accept connections using public IP addresses.

If the interface times out while performing the steps in this procedure, return to the previous blade and click OK again so you can continue where you left off.

For information on taking down an Azure VM, Stop, Deallocate, or Delete a VM in Azure.

  1. Log in to Azure Marketplace portal using your user name and password.
  2. Click located in the upper left and search for Teradata.
    A list of Teradata products appears under the Results pane.
  3. Select the product you want to deploy.
    For a list of products in each Teradata ecosystem (referred to as tiers), see Teradata Database License Tiers.
  4. Click the Basics blade to configure basic settings.
    Parameter Name Action
    User name Enter a user name.
    Authentication type Select an authentication method.
    Note:
    For security reasons, an SSH public key is strongly recommended.
    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.
    Location Select a region where you want to deploy the solution.
  5. Click OK.
  6. Click the Teradata Database blade to configure the Teradata Database.
    Parameter Name Action
    System name prefix Accept the default or enter a prefix to be used 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 between 8 and 15 characters long, consisting of letters and numbers, but it does not have to contain numbers. It must start with a letter.

    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.
    Database Tier Select one of the following database license tiers:
    • Developer
    • Base
    • Advanced
    • Enterprise
    VM Size To change the size of the VM to provision for each cluster node, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.
    Number of nodes Enter the number of nodes you want to deploy.
    Storage Size Per Node Select the storage size per node if applicable for the VM size you chose.

    For more information, see Supported VM Sizes.

    Row Level Security Click Yes to enable the Teradata Row-Level Security feature. The default setting is No.
    Secure Zones Click Yes to enable the Teradata Secure Zones feature. The default setting is No.
  7. Click OK.
  8. If you plan to use Viewpoint, Server Management, Data Stream Controller, Ecosystem Manager, or Data Mover, complete the following steps.
    1. Click the Viewpoint blade to configure Viewpoint.
    2. Complete the following actions.
    Parameter Name Action
    Viewpoint Click Yes to deploy Viewpoint.
    Viewpoint system name prefix Accept the default or enter a prefix to be used for all nodes in the cluster.

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

    System nickname Enter a nickname to be used to configure Viewpoint.
    Viewpoint portal admin user password Enter the Viewpoint administrator password for the Viewpoint portal, using between 8 and 15 characters. It must start with an alpha character and can contain numbers.

    This password is used to log on to the Viewport portal with the user name of admin.

    Confirm portal admin user password Enter the password again to confirm.
    Viewpoint Image version Select from one of three Viewpoint images:
    • Teradata Viewpoint Single System
    • Teradata Viewpoint Multiple Systems
    • Teradata Viewpoint Single System Data Lab
    VM size To change the size of the VM to provision for each cluster node, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  9. Click OK.
  10. [Optional] Click the Server Management blade.
    Prerequisite: You must complete step 8 before completing the following actions.
    Parameter Name Action
    Server Management Click Yes to deploy Server Management. No is the default value.
    Site ID Type the Site ID to be used when connecting to the Teradata Database, using 0 to 15 alphanumeric characters in all capitals. 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 Server Management VMs deployed.
    Server Management admin password Type the Server Management Administrative password, using 6 to 32 alphanumeric characters.
    Confirm admin password Enter the password again to confirm.
    Server Management REST password Type the Server Management REST password, using 6 to 32 alphanumeric characters.
    Confirm REST password Enter the password again to confirm.
    Server Management VM Count Select the number of CMICs to deploy. Two is the minimum number of CMICs for high availability.
    VM Size To change the size, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  11. Click OK.
  12. [Optional] Click the Teradata REST Services blade.
    Prerequisite: You must complete step 8 before completing the following actions.
    Parameter Name Action
    Teradata REST Services Click Yes to deploy Teradata REST Services.
    Teradata REST Services system name prefix Enter a prefix to be used for all Teradata REST Services nodes in the cluster.
    VM size To change the size, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  13. Click OK.
  14. [Optional] Click the Data Stream Controller blade.
    Prerequisite: You must complete step 8 before completing the following actions.
    Parameter Name Action
    Data Stream Controller Click Yes to deploy Data Stream Controller.
    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 passwordEnter the password again to confirm.
    DSC admin passwordType the DSC Administrative password, using 6-32 alphanumeric characters.
    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 sizeTo change the size, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  15. Click OK.
  16. [Optional] Click the Ecosystem Manager blade.
    Prerequisite: You must complete step 8 before completing the following actions.
    Parameter Name Action
    Ecosystem Manager Click Yes to deploy Ecosystem Manager.
    Ecosystem Manager system name prefix Accept the default or enter a prefix to be used for all nodes in the cluster.

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

    VM size To change the size of the VM to provision for each cluster node, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  17. Click OK.
  18. [Optional] Click the Data Mover blade.
    Prerequisite: You must complete step 8 before completing the following actions.
    Parameter Name Action
    Data Mover Click Yes to deploy Data Mover.
    DBC user password Enter a new default Teradata Database user password.

    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 the user password to be used to access the internal DATAMOVER repository.

    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 To change the size, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.

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

    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  19. Click OK.
  20. Click the General Settings blade to configure additional settings applicable to all components.
    Parameter Name Action
    Virtual network Create a new or select an existing virtual network to deploy cluster servers.
    Name Accept the default or enter a name to be used 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.

    Three public subnets will be created that attach three network cards to each server, one per subnet.

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

    For Teradata Database MPP VMs, ensure the CIDR range you calculate is two 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.

    For more information, see VNets.

    Check to ensure the CIDR address you enter is not being used by existing subnets in the same VNet by going to the Azure portal.

    BYNET0 name Enter a name for Bynet0.
    BYNET0 address prefix

    [Teradata Database MPP Only]

    For Teradata Database MPP VMs, enter a subnet CIDR.

    For Teradata Database single-node VMs, type the same CIDR block as the public subnet.

    BYNET1 name Enter a name for Bynet1.
    BYNET1 address prefix

    [Teradata Database MPP Only]

    For Teradata Database MPP VMs, enter a subnet CIDR.

    For Teradata Database single-node VMs, type the same CIDR block as the public subnet.

    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.

  21. Click OK.
  22. Click the Summary blade, review the summary, and click OK.
  23. Click the Buy blade, review the terms of use and privacy policy, and click Purchase.
    This process can take anywhere between 20 to 60 minutes depending on your configuration and the availability of resources in your region.
    Note:
    Trying to SSH into the VM may cause the creation of the VM to fail. Do not try to SSH into the VM until either you get confirmation the VM has been created or you receive a failure notification.
  24. 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 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.


  25. If you are using Data Mover, Data Stream Controller, Ecosystem Manager, Server Management, Teradata REST Services, or Viewpoint and want to use public IP addresses, do the following after the VMs are created:
    1. Create the public IP addresses.
    2. Adjust the NSG rules to accept connections using public IP addresses.
      The solution template defines an NSG for each software product VM.
  26. If you enabled Teradata Row-Level Security, go to the SSH client console and type the following:
    # dbscontrol -a | grep -i rls

    Sample output:

    RLSPurchased = True
    For more information about Teradata Row-Level Security, see Security Administration.
  27. If you enabled Teradata Secure Zones, go to the SSH client console and type the following:
    # dbscontrol -a | grep -i securezones

    Sample output:

    SecureZonesPurchased = True
    For more information about Teradata Secure Zones, see Security Administration.

results matching ""

    No results matching ""