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. See Azure Documentation Center. In addition, check if Azure service limits need to be increased. See Azure Service Limits.

Before unfolding a system, ensure you have enough IP addresses. Each new VM requires 1 IP address from each subnet. A total of 3 IP addresses per VM are required. The available IP addresses per subnet in a VNet are in Virtual network > Subnets.

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.

These templates create 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 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 you plan to use Data Mover, Data Stream Controller, Ecosystem Manager, QueryGrid, Server Management, or Viewpoint, you must configure Viewpoint.

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.

  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 Teradata Database solution template you want to deploy.
    Your choice of solution template determines whether you are purchasing the Teradata IntelliSphere bundle, or purchasing software products separately.
    • Teradata Database with IntelliSphere [Enterprise, Advanced, and Base tiers only]
    • Teradata Database
  4. Click the Basics blade to configure basic settings.
    Parameter NameAction
    User nameEnter a user name.
    Authentication typeSelect 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.
    SubscriptionSelect a subscription.
    Resource groupSelect one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    LocationSelect a region where you want to deploy the solution.
  5. Click OK.
  6. Click the Teradata Database blade to configure the Teradata Database.
    Parameter NameAction
    System name prefixAccept 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 passwordEnter a new default Teradata Database password of 12 to 15 characters long, consisting of letters and numbers, but it does not have to contain numbers. It must start 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 passwordEnter the password again to confirm.
    Japanese language supportClick Yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is No.
    Purchase Method Select one of the following purchase methods:
    • Hourly
    • BYOL
    Entitlement ID

    (BYOL only)

    Enter the entitlement ID which is a unique string of characters that enable you to use the licensed software.

    Obtain the EID from the email you received when you purchased the license.

    Term of License

    (BYOL only)

    Select one of the following for the license period:
    • 1 Year
    • 3 Years
    • POC: Short-term license (30, 60 or 90 days) used for a proof-of-concept

    Obtain the term from the email you received when you purchased the license.

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

    Database Version Select the Teradata Database release version.
    Database Tier Select one of the following database license tiers:
    • Enterprise
    • Advanced
    • Base (not available for Fold/Unfold)
    • Developer (available for Hourly, but not available for BYOL, Fold/Unfold, or with Teradata IntelliSphere)
    See Teradata Database License Tiers.
    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.
    Storage Size Per Node Select the storage size per node if applicable for the VM size you chose.

    See Supported VM Sizes.

    Fold / Unfold (Advanced and Enterprise tiers only) Do one of the following:
    Note
    If you choose to not unfold during launch, you can do so after launching. See Unfolding a System.
    • Select None to disable this feature (default).
    • Select Unfold-Ready to automatically allocate extra private IP addresses from the subnet.

      The initial state for a system has 3 extra private IP addresses reserved per subnet per node.

      The following examples are for launching a 4 node system:
      • When the system unfolds to 2x, then 8 nodes are launched and 1 private IP address per subnet per node is reserved.
      • When the system unfolds to 4x, then 16 nodes are launched. No extra private IP addresses are reserved.
    • Select Unfolded-2x to launch half of the premium storage, enabling you to later fold the system after launching. See Folding a System.

      The initial state for a system has 1 extra IP address per subnet per node.

    • Select Unfolded-4x to launch a quarter of the premium storage, enabling you to later fold the system after launching. See Folding a System. No extra private IP addresses are reserved.
    Number of nodes Enter the number of nodes you want to deploy.
    Teradata Intelligent Memory (TIM)

    [Enterprise, Advanced tiers only]

    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 Utilities and the Teradata Intelligent Memory Orange Book.

    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 Data Mover, Data Stream Controller, Ecosystem Manager, Server Management, or Viewpoint, complete the following steps.
    For Teradata QueryGrid, you must use Teradata Viewpoint (Multiple Teradata Systems). You can use an on-premises installation or follow these steps to deploy on Azure.
    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 in to the Viewpoint portal with the user name of admin.

    Confirm portal admin user password Enter the password again to confirm.
    Viewpoint Image version Select a Viewpoint image:
    • Teradata Database with IntelliSphere:
      • Teradata Viewpoint - IntelliSphere
    • Teradata Database:
      • Teradata Viewpoint Multiple Systems
      • Teradata Viewpoint Single System Data Lab
      • Teradata Viewpoint Single System
    See Software Purchase Options.
    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. 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 NameAction
    Server Management Click Yes to deploy Server Management. No is the default value.
    Site ID

    [Enterprise, Advanced, Base tiers only]

    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 passwordType the Server Management Administrative password, using 6 to 32 alphanumeric characters.
    Confirm admin passwordEnter the password again to confirm.
    Server Management REST passwordType the Server Management REST password, using 6 to 32 alphanumeric characters.
    Confirm REST passwordEnter the password again to confirm.
    Server Management VM Count Select the number of CMICs to deploy. Minimum number for high availability: 2
    Note
    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 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. 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. 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 NameAction
    Data Stream ControllerClick 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 password Enter the password again to confirm.
    DSC admin password Type the DSC Administrative password, using 6-32 alphanumeric characters.
    Confirm DSC admin password Enter the password again to confirm.
    DSC system name prefixEnter 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. 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
    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. 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 NameAction
    Data Mover Click Yes to deploy Data Mover.
    DBC user passwordEnter 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 passwordEnter 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. See Supporting Software VM Sizes.

  19. Click OK.
  20. [Optional] Click the QueryGrid Manager blade.
    Prerequisite: To use QueryGrid Manager, use Teradata Viewpoint Multiple Systems or Teradata Viewpoint - IntelliSphere installed on-premises, or deploy it on Azure as described in step 8.
    Parameter Name Action
    QueryGrid Manager Click Yes to deploy QueryGrid Manager.

    No is the default value.

    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 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. See Supporting Software VM Sizes.

  21. Click OK.
  22. 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.

    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.

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

  23. Click OK.
  24. Click the Summary blade, review the summary, and click OK.
  25. 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.
  26. 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.
  27. 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.
  28. If you deployed Teradata QueryGrid, you must deploy the desired QueryGrid connectors.
    For instructions, see Teradata QueryGrid Installation and User Guide.
    Teradata Database Solution Template Obtaining Connectors
    Teradata Database with IntelliSphere QueryGrid connectors are included in the IntelliSphere bundle and deployed with the QueryGrid image.
    Teradata Database Contact your Teradata Account Team to purchase QueryGrid connectors.
  29. 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
    See Security Administration.
  30. 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
    See Security Administration.
  31. [BYOL only] If you receive licensing errors, see Licensing Issues.
  32. [BYOL only] Monitor the deployment continuously for errors, warnings, and alerts.

results matching ""

    No results matching ""