Deploying Aster Analytics on Azure from ARM Template - Aster Analytics on Azure

Teradata Aster® Analytics on Azure Getting Started Guide
Product
Aster Analytics on Azure
Published
May 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
bvi1488473168476.ditamap
dita:ditavalPath
Azure.ditaval
dita:id
bvi1488473168476
lifecycle
previous
Product Category
Cloud

Before deploying Teradata Aster Analytics on Azure, 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.

Your assigned permission should allow you to:
  • Create resource groups
  • Create new network security groups

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, make sure your current subscription has enough spare quota and resource limits. And check if Azure service limits need to be increased.

For more information, see Azure Service Limits.

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

  1. Log in to Azure Marketplace portal using your username and password.
  2. Click the located in the upper left and search for Teradata Aster. A list of Teradata Aster products appears on the Results pane.


  3. Select Teradata Aster Analytics.
  4. Click the Basics blade to configure basic settings.
    Parameter Name Action
    User name Enter a SSH user name. This is the admin username for the virtual machines.
    Authentication type Select one of the following:
    Password
    Enter a password between 12 and 72 characters long, with at least 3 of the following: 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 RSA public key which can be generated with tools such as ssh-keygen.
    Subscription Select a subscription.
    Resource group Select Create new and enter a name to create a new resource group for the deployment.
    If you want to choose an existing resource group by selecting Use existing, make sure it is an empty resource group that does not contain existing resources.
    Location Select a region where you want to deploy the solution.
  5. Click OK.
  6. Click the Aster Settings blade to configure the Aster Cluster settings.
    Parameter Name Action
    System Name Prefix

    This is the prefix for resource name. It displays in the Azure portal after the VM deploys.

    The default is aster.

    Accept the default or enter a prefix to be used for all nodes in the cluster.
    Number of Aster worker nodes Enter the number of Aster Worker nodes (2 to 32) you want to deploy.
    Choose VM Size This is the VM size selector. To change the size of the VM to provision for each cluster node:
    1. Click and then View all to display a list of all available VM sizes.
    2. Click to highlight a desired size based on desired number of cores and memory.
    3. Click Select.

    For each available size, Azure displays its default features, including number of Data disks.

    Aster Analytics on Azure uses customized storage layout which is different from the Azure default settings.

    Ignore the Azure default values, and refer to the Data disk size parameter on this page for actual disk space selection for the deployment.
    Aster database password Enter a new default Aster 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.
    Confirm password Enter the password again to confirm.
    Data disk size This is the data disk size for each node in the deployment. Aster offers options of 1TB, 4TB, and 8TB.

    For more information, see Storage Options.
    Time zone Select a time zone for the cluster.
  7. Click OK.
  8. Click the Network Settings blade to configure the virtual network.
    Parameter Name   Action
    Virtual Network Configuration   Select an existing virtual network or create a new one to deploy the cluster.
    Name Accept the default or enter a name for the virtual network.

    The name displays in the Azure portal as a resource after the VM deploys.
    Address space Enter a CIDR (Classless Inter-Domain Routing) IP address block for the virtual network.
    Subnet Subnet name Select the default or enter a name for the VM subnet.
    Subnet address prefix Enter a CIDR IP address block for the subnet. The template creates a new subnet in the selected VNet using this CIDR address.

    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.
    Make sure the subnet is contained within the Address space for the virtual network used.
  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 about 30 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 either you get confirmation the VM has been created or you receive 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 only send alerts if you have set them prior to starting the deployment.
    2. From the left panel, click the to see a list of all resources.
    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.


    You can also check the status of the deployment from the Azure Dashboard.
    Please be aware that occasionally the alerts shown on the Azure Dashboard are inconsistent with the actual deployment status. It is recommended that you always check the actual status of the deployment object and the activity logs to get updates on the deployment status.