Teradata Aster Analytics on Azure Getting Started Guide

Transcription

1 What would you do if you knew? Teradata Aster Analytics on Azure Getting Started Guide Release AD B K May 2017

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Applications-Within, Aster, BYNET, Claraview, DecisionCast, Gridscale, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. Amazon Web Services, AWS, Amazon Elastic Compute Cloud, Amazon EC2, Amazon Simple Storage Service, Amazon S3, AWS CloudFormation, and AWS Marketplace are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. CENTOS is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Cloudera and CDH are trademarks or registered trademarks of Cloudera Inc. in the United States, and in jurisdictions throughout the world. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/os are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. NetVault is a trademark of Quest Software, Inc. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLib are registered trademarks of Simba Technologies Inc. SPARC is a registered trademark of SPARC International, Inc. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Veritas, the Veritas Logo and NetBackup are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or noninfringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright 2017 by Teradata. All Rights Reserved.

3 Table of Contents Preface...5 Purpose... 5 Audience...5 Revision History...5 Supported Releases...5 Additional Information...5 Related Links...5 Related Documents...6 Product Safety Information... 6 Chapter 1: Teradata Aster Analytics on Azure... 7 Aster Analytics on Azure Overview... 7 Aster Analytics on Azure Features... 8 Assumptions... 8 Limitations... 8 Aster Analytics on Azure Software...9 Aster Analytics on Azure Use Cases...9 Chapter 2: Preparing for Aster Analytics on Azure...11 Quick Start Teradata at Your Service Site IDs...12 Enabled Features Resource Groups Network Security Groups and Ports VNets SSH Tunneling Location and Time Zone Considerations...14 Connection Considerations...14 Storage Options...14 Azure Service Limits...15 Chapter 3: Deploying Aster Analytics on Azure Aster Analytics on Azure Deployment Overview Teradata Aster Analytics on Azure, Release AD 3

4 Table of Contents Deploying Aster Analytics on Azure from ARM Template...17 Chapter 4: Deploying Aster AppCenter on Azure...23 Aster AppCenter on Azure Deployment Overview Deploying Aster AppCenter using a Virtual Machine Image Launching Aster AppCenter on Azure Chapter 5: Configuring Aster Analytics Software for Azure...29 The Aster Management Console (AMC) Data Movement...29 Loading Data Using Aster Loader Tool Exporting Data Using the Aster Export Tool...29 Using Teradata Viewpoint...29 Using the Teradata-Aster Database Connector...30 Chapter 6: Administrative Tasks Creating an Azure Active Directory Application and the Service Principal Stop, Deallocate, or Delete a VM in Azure...31 Stopping Aster Analytics on Azure Chapter 7: Troubleshooting Aster Analytics on Azure Customer Support...33 Connection Issues Correcting Connection Issues IP Address Changes Database Issues...33 Logon Problems Viewing Activity Logs Viewing Node Status Chapter 8: Acronyms Acronyms Teradata Aster Analytics on Azure, Release AD

5 Preface Purpose Learn about Teradata Aster software on Azure, including how to deploy and configure Teradata Aster Analytics on Azure to run a self-managed Teradata Aster Analytics multi-node system in the Azure public cloud. Audience This guide is intended for use by System Administrators and others involved in configuring Teradata Aster Analytics and supporting Teradata Aster software in the Azure public cloud. Revision History Date May 2017 Description Initial release Supported Releases The following versions are supported for this release of Teradata Aster Analytics on Azure: Aster Database, version (AD ) Aster Analytics, version 7.00 (AA 7.00) Aster Client, version 6.22 (AC 6.22) Aster AppCenter Additional Information Related Links URL Description Customer documentation for using Teradata and Teradata Aster products Teradata Aster Analytics on Azure, Release AD 5

6 Preface Product Safety Information URL Description Orange Books, technical alerts, knowledge repositories, and access to downloading software packages Teradata Developer Exchange is a collaborative website connecting Teradata employees with customers to share ideas, ask questions, learn, and solve problems related to Teradata products Teradata Community is a collaborative website connecting Teradata employees with customers to share ideas, ask questions, learn, and solve problems related to Teradata products Downloads for the Teradata Aster platform Teradata Aster Community is a collaborative website connecting Teradata Aster employees with customers to learn Aster, discover insights, and share their stories with peers. Azure Marketplace Related Documents To view or download Teradata Aster Analytics on Azure documentation: Access the Teradata Information Products website at: Click on the Teradata Aster Analytics grid. Search and select the desired document. To view or download Microsoft Azure documentation, access the links below. Azure Documentation Center: This is the Microsoft Azure Documentation portal, it contains not only links to how to get started with Azure (including an overview and tutorials), but also links to extensive documentation for everything you need to do in Microsoft Azure. Microsoft Azure Blog: This site provides additional source for up-to-date Azure information. Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. 6 Teradata Aster Analytics on Azure, Release AD

7 CHAPTER 1 Teradata Aster Analytics on Azure Aster Analytics on Azure Overview Microsoft Azure enables you to run a self-managed Aster system directly in the Azure public cloud. As a self-provisioned environment, Teradata Aster Analytics on Azure supports 2 to 32 worker nodes per cluster. Teradata Aster offers the flexibility to choose different disk sizes for the product in the Azure Marketplace. Storage options include 1TB, 4TB, and 8TB per node. Azure Marketplace ( azuremarketplace.microsoft.com) is an online store that helps you find, buy, and immediately start using Teradata Aster software and services. Running Teradata Aster Analytics on Azure is similar to running an Aster cluster in your on-site data center. To a database administrator, there are no differences between the two environments. There are, however, a number of Azure-specific considerations related to configuring software, migrating data, security, data backup, and system management that are explained in this guide. Azure offers a virtual computing environment where you can deploy Aster virtual machine images. A virtual machine image is a template you use to launch a virtual server in the Azure public cloud. Teradata Aster provides pre-configured virtual machine images for Teradata Aster Analytics on Azure in the Azure Marketplace to get you up and running immediately. The architecture of Teradata Aster Analytics on Azure is summarized in this diagram: For a list of acronyms used in this documentation, see Acronyms. Teradata Aster Analytics on Azure, Release AD 7

8 Chapter 1: Teradata Aster Analytics on Azure Aster Analytics on Azure Features Aster Analytics on Azure Features Teradata Aster Analytics on Azure offers the same features that come with an on-premises Teradata Aster system with a couple of exceptions. See Limitations for a list of the exceptions. In addition, there are some features that are enabled by default. See Enabled Features. Aster Analytics on Azure supports these features: Database Feature Massively Parallel Data Storage Distributed Architecture Data Distribution Embedded Analytic Processing Rapid Analytics Development and Model Deployment Description Aster Database is a Massively Parallel Processing (MPP), shared-nothing database designed for general-purpose and analytic data warehousing. Its architecture is comprised of multiple worker servers or nodes which are managed and coordinated by a queen server. Users only interact with the queen node which handles distribution of data and tasks for optimal performance. The data and the workload are distributed among workers to optimize query performance and function execution. This allows each worker node to run in parallel and also allows linear scaling by adding additional worker nodes. Integrated analytic engine with SQL, Teradata Aster SQL-MapReduce framework and Teradata Aster SQL-GR enables analysis of both non-relational and relational data with incremental scalability. Over 150 pre-built analytic functions as well as Visual IDE enables development of apps in hours while supporting many programming languages, such as Java. Refer to the Aster Analytics on Azure documentation set for more information on these features. Assumptions This guide assumes a solid understanding of general cloud computing and the Azure environment, including: Using the Azure Marketplace Managing Azure resources using the ARM (Azure Resource Manager) model Starting, stopping, and terminating an Azure virtual machine, including implications for storage persistence and related costs Limitations Teradata Aster Analytics on Azure does not support the Azure Classic Mode to deploy the solution. Teradata Aster Analytics on Azure does not support: Cluster expansion and node replacement Loader nodes Backup nodes These applications are not supported for use in the Teradata Aster Analytics on Azure environment: 8 Teradata Aster Analytics on Azure, Release AD

9 Aster Backup Chapter 1: Teradata Aster Analytics on Azure Aster Analytics on Azure Software Aster Analytics on Azure Software The following is a list of Teradata Aster Analytics on Azure software that you access from the Azure Marketplace. Software Name Description Software Access Teradata Aster Analytics on Azure Teradata Aster AppCenter This product suite includes: Aster Database Aster Analytics Aster Client The Teradata Aster AppCenter is available on Azure. Resource Manager template and Azure VM image (only accessible via the Resource Manager template) Azure VM image Aster Analytics on Azure Use Cases Analytics Sandbox A short-lived, flexible, and evolving analytic environment that can be easily stood up, evolved, scaled, and shut down based on discovery, development, and testing needs. Migrations Migrate workloads from on-premises to the cloud in total or in part. Migrations include establishing the environment and an initial historical data load/port. Persistent Test and Development Stand up a persistent and scalable environment for developing and testing solutions prior to deploying into production. The test and development environment typically includes the other ecosystem components running in your production environment. For more information, see Teradata Aster Analytics on Azure, Release AD 9

10 Chapter 1: Teradata Aster Analytics on Azure Aster Analytics on Azure Use Cases 10 Teradata Aster Analytics on Azure, Release AD

11 CHAPTER 2 Preparing for Aster Analytics on Azure Quick Start Steps Before deploying Teradata Aster Analytics on Azure VMs, the following information helps you get started. Sign up for an Azure account. Learn about resource groups. Learn about network security groups. Learn about VNets. Learn about Azure service limits and increase them in advance of the time that you need them. Learn about administrative tasks. Learn about available Aster Analytics products. Learn how to deploy Teradata Aster Analytics on Azure Learn how to deploy Teradata Aster AppCenter Register for Teradata Support. Learn about how to use the Teradata Aster Analytics on Azure and the associated software. More Information See and click Start free. See Resource Groups. See Network Security Groups and Ports. See VNets. See Azure Service Limits. Learn about how to avoid incurring charges, including Stop, Deallocate, or Delete a VM in Azure. See Aster Analytics on Azure Software. See Deploying Aster Analytics on Azure. See Deploying Aster AppCenter on Azure. When you subscribe to Teradata Aster Analytics on Azure, you receive a welcome that enables you to register for support. After your support registration is complete, you receive another with your Master Customer Record, Site ID, user ID, and password. See Site IDs. See for Teradata customer documentation. Teradata at Your Service TaYS ( is a secure portal that provides Teradata customers access to Teradata products, services, education, and support and is used to: Request support from Teradata regarding an incident Access educational materials Teradata Aster Analytics on Azure, Release AD 11

12 Chapter 2: Preparing for Aster Analytics on Azure Site IDs Download software releases (existing on-premises Teradata Aster customers only) Customers who already use TaYS for products previously purchased from Teradata cannot use their previous TaYS account for Teradata Aster Analytics on Azure. You must obtain a new TaYS account for Teradata Aster Analytics on Azure. For information on using TaYS, see the TaYS Admin User Manual at the bottom of the TaYS home page. Site IDs A site ID is a unique code to identify your installation of Teradata Aster Analytics on Azure. Although this site ID is not required to use Teradata Aster Analytics on Azure, it is required to receive Teradata support. When you subscribe to Teradata Aster Analytics on Azure, you receive a welcome that enables you to register for support. After your support registration is complete, you receive another with your Master Customer Record, Site ID, user ID, and password. Your Site ID begins with AZRAST, followed by 5 to 9 alphanumeric characters. Existing Teradata customers who have on-premises Teradata systems cannot use their previous site IDs for Teradata Aster Analytics on Azure. You must obtain a new site ID. Enabled Features The following features are enabled by default: Massively Parallel Data Storage Embedded Analytic Processing Rapid Analytics Development and Model Deployment Connectors to external data sources via JDBC and ODBC connectors such as the Aster-to-Teradata Connector to load data to and from Teradata database is supported using the functions load_to_teradata and load_from_teradata. Similarly, the Aster-to-Hadoop Connector to load data to and from Hadoop database is supported using the functions load_to_hcatalog and load_from_hcatalog. Teradata Aster AppCenter, delivered in a separate Azure Virtual Machine image, can be connected to the queen node for app development, sharing, and deployment. Resource Groups The infrastructure of an application is made up of many components, such as a VM, storage account, virtual network, and third-party services. You can deploy, manage, and monitor these resources as a group using the Azure Resource Manager. A resource group is a container that holds these related resources. You can deploy or delete all resources in a single action. Resource Manager provides security, auditing, and tagging for billing purposes to help you manage all resources. Resource Manager also enables you to control who in your organization can perform actions on the resources. You manage permissions by defining roles and adding users or groups to the roles. For critical resources, you can apply an explicit lock that prevents users from deleting or modifying the resource. Azure Resource Manager logs all user actions so your company's cloud administrator can audit those actions. When you deploy Teradata Aster Analytics products in Azure using a solution template, you can either create a new resource group, or deploy it into an existing resource group. The cloud administrator in your 12 Teradata Aster Analytics on Azure, Release AD

13 Chapter 2: Preparing for Aster Analytics on Azure Network Security Groups and Ports company sets the permissions to create a new resource group. When a resource group is deleted, the VM and all associated components are deleted, including the storage. For more information, see the Azure Documentation Center and search for Azure Resource Manager Overview. Network Security Groups and Ports A network security group (NSG) contains a list of Access Control List (ACL) rules that allow or deny network traffic to your VMs in a virtual network. NSGs can be associated with either subnets or individual VMs within that subnet. When an NSG is associated with a subnet, the ACL rules apply to all the VMs in that subnet. In addition, traffic to an individual VM can be restricted further by associating a NSG directly to that VM. You can open a port to a VM by creating a network filter on a subnet or VM network interface. You can then place these filters, which control both inbound and outbound traffic, on an NSG attached to the resource that receives the traffic. Aster deployment in Azure requires creating new security group. You must have the permission to create new security groups. For more information on filtering network traffic with network security groups, access Azure Documentation Center, select Services tab. In the Virtual Network documentation section under Networking menu, search for Network Security Groups under Plan and design. VNets An Azure virtual network (VNet) is a representation of your own network in the cloud. It is a logical isolation of the Azure cloud dedicated to your subscription. You fully control the IP address blocks, DNS settings, security policies, and route tables within this network. You can also further segment your VNet into subnets and deploy VMs. Additionally, you can connect the VNet to your on-premises network. VNets are associated to a resource group which provides network boundaries for resources. A VNet is required when deploying a VM. VNets cannot span over multiple locations. For information, see the Azure Documentation Center and search for Virtual Network Overview. SSH Tunneling You can securely connect to VMs running in a VNet private subnet without exposing them to the Internet. You can set up a public subnet that acts as a proxy/jump box. To securely connect to VMs running in a VNet private subnet, you can use SSH tunneling. Using SSH tunneling improves security by not exposing the management ports of your VM to the Internet or to other subnets in your VNet. For information on how to create an SSH tunnel, see Azure Documentation Center and search for Use SSH Tunneling to access Ambari. Teradata Aster Analytics on Azure, Release AD 13

14 Chapter 2: Preparing for Aster Analytics on Azure Location and Time Zone Considerations Location and Time Zone Considerations Azure allows you to create VMs in defined geographic regions that are closest to your users. For example, West US or East US. Within each region, multiple data centers exist to maximize performance, service availability, and redundancy. Learn about why it is important to choose the right region for legal, compliance, or tax purposes. For more information, access Azure Documentation Center, in the Linux Virtual Machines documentation section under Compute menu, search for Regions and availability for virtual machines in Azure. If you deploy Teradata Aster Analytics on Azure products using a solution template, you select a region (Location) in the template. By default, the time zone for the Teradata Aster Analytics on Azure VM is set to UTC. You have the option to change the operating system time zone in the template. Connection Considerations If you are using VMs within the public cloud, configure these VMs to reside in the same Vnet. When configuring the software, use private IP addresses to connect to these VMs. If you are using VMs to connect from the Azure public cloud to an on-premises Teradata system, use public IP addresses to connect to the on-premises Teradata system when configuring the software. You need to use public IP addresses only if you deploy a VM using a public Azure virtual network. If you deploy a VM using a private Azure virtual network, the VMs have private IPs and a Vnet connection is required for SSH access. Storage Options Teradata Aster Analytics on Azure provisions Azure premium storage for storage purposes. Azure Premium Storage provides the following key implications: Provides the highest reliability among the storage options. Offers data persistence independent of a running VM. Allows shutdown of a VM between sessions to reduce costs. Provides lower performance compared to local storage. Costs less per GB than local storage. Allows for expandable storage through attachment of additional disks. When deploying Teradata Aster Analytics on Azure, for each of the four VM size options (DS12_v2, DS13_v2, DS14_v2, DS15_v2), you have the option to choose 1TB, 4TB, or 8TB as data disk size. For additional information, access Azure Documentation Center, select Services tab, and in the Storage documentation section under Storage menu, search for: Introduction High-performance Premium Storage for VM Disks 14 Teradata Aster Analytics on Azure, Release AD

15 Azure Service Limits When you create your Azure account, Azure sets default service limits on certain resources on a per-region basis. Before deploying VMs, check the limits to determine if any should be increased especially for core, networking, and storage. Plan to request limit increases in advance of the time that you need them. For more information, see Azure Documentation Center and search for Azure Subscription and Service Limits. To request limit increases, create an Azure support request. For more information, see Azure Documentation Center and search for How to Create an Azure Support Request. When you create a support request, select the issue type which is always Quota, your subscription, support plan, severity, deployment model which is Resource Manager, location which is your region, the specify VMs that apply to this request, and complete the following in the table listed below. Request Type Quota Type Details Chapter 2: Preparing for Aster Analytics on Azure Azure Service Limits Cores Cores Request the number of additional cores. Networking Limits Networking: ARM Request the number of additional public IPs and specify the region where they are needed. Storage Storage: ARM Request the number of additional premium storage accounts and specify the region where they are needed. Teradata Aster Analytics on Azure, Release AD 15

16 Chapter 2: Preparing for Aster Analytics on Azure Azure Service Limits 16 Teradata Aster Analytics on Azure, Release AD

17 CHAPTER 3 Deploying Aster Analytics on Azure Aster Analytics on Azure Deployment Overview From the Azure Marketplace, you can deploy Teradata Aster Analytics on Azure from an Azure Resource Manager template offer. After deployment, additional configuration may be required. For more information, see Configuring Aster Analytics Software for Azure. Deploying Aster Analytics on Azure from ARM Template Prerequisite 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. Teradata Aster Analytics on Azure, Release AD 17

18 Chapter 3: Deploying Aster Analytics on Azure Deploying Aster Analytics on Azure from ARM Template 3. Select Teradata Aster Analytics. 4. Click the Basics blade to configure basic settings. Parameter Name User name Authentication type Action Enter a SSH user name. This is the admin username for the virtual machines. 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 Resource group Select a subscription. 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 System Name Prefix Number of Aster worker nodes Action 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. Enter the number of Aster Worker nodes (2 to 32) you want to deploy. 18 Teradata Aster Analytics on Azure, Release AD

19 Chapter 3: Deploying Aster Analytics on Azure Deploying Aster Analytics on Azure from ARM Template Parameter Name Choose VM Size Action This is the VM size selector. To change the size of the VM to provision for each cluster node: a. Click and then View all to display a list of all available VM sizes. b. Click to highlight a desired size based on desired number of cores and memory. c. 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 Data disk size Time zone Enter the password again to confirm. 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. Select a time zone for the cluster. 7. Click OK. 8. Click the Network Settings blade to configure the virtual network. Parameter Name Virtual Network Configuration Action Select an existing virtual network or create a new one to deploy the cluster. Name Address space 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. 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. Teradata Aster Analytics on Azure, Release AD 19

20 Chapter 3: Deploying Aster Analytics on Azure Deploying Aster Analytics on Azure from ARM Template Parameter Name Action 9. Click OK. 10. Click the Summary blade, review the summary, and click OK. 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. 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: a) 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. b) From the left panel, click the to see a list of all resources. c) Under the Name column, select a resource. d) Under Settings, click Deployments. e) 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. f) 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. g) Under Operation details, when the STATUS column displays OK, select the resource. The PROVISIONING STATE displays Succeeded. 20 Teradata Aster Analytics on Azure, Release AD

21 Chapter 3: Deploying Aster Analytics on Azure Deploying Aster Analytics on Azure from ARM Template 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. Teradata Aster Analytics on Azure, Release AD 21

22 Chapter 3: Deploying Aster Analytics on Azure Deploying Aster Analytics on Azure from ARM Template 22 Teradata Aster Analytics on Azure, Release AD

23 CHAPTER 4 Deploying Aster AppCenter on Azure Aster AppCenter on Azure Deployment Overview From the Azure Marketplace, you can deploy an Aster AppCenter via virtual machine image. You can deploy a 1-Node Aster AppCenter on Azure. After deployment, additional steps may be required to configure the Aster AppCenter. Deploying Aster AppCenter using a Virtual Machine Image Prerequisite Before deploying Aster AppCenter 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. 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, refer to the Azure Service Limits. Aster AppCenter uses the ports shown in this table. For more information, refer to the Aster AppCenter User Guide. Port Type Description 443 inbound HTTPS port to access main AppCenter web UI page. This port will be open to public by default. 80 inbound HTTP port to redirect to secure port. This port will be open to public by default. 22 inbound SSH port to log in to the virtual machine. This port will not be open to public by default. User needs to open this port if required outbound Port required to connect to Aster via JDBC. 389 outbound Port required to use LDAP authentication via Active Directory or OpenLDAP. Teradata Aster Analytics on Azure, Release AD 23

24 Chapter 4: Deploying Aster AppCenter on Azure Deploying Aster AppCenter using a Virtual Machine Image AppCenter does not require a separate Resource Group, Virtual Network or Subnet. It can share these resources with an existing Aster installation on Azure. 1. Log in to Azure Marketplace portal using your username and password. 2. Click located in the upper left and search for Teradata Aster. A list of Teradata Aster products appear on the Results pane. 3. Select Teradata Aster AppCenter. 4. Click the Basics blade to configure basic settings. Parameter Name Name VM disk type Action Enter a name for this virtual machine. Select a VM disk type to use for this virtual machine. Teradata recommends using the SSD type. User name Authentication type Enter a user name. Select one of the following: 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. SSH public key Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT. Teradata recommends using the SSH public key type. Subscription Resource group Location Select a subscription. Select Create new and enter a name for the resource group or select Use existing to use an existing resource group, both will work. Select a region where you want to deploy the solution. 24 Teradata Aster Analytics on Azure, Release AD

25 5. Click OK. 6. Click the Size blade to choose a virtual machine size. Chapter 4: Deploying Aster AppCenter on Azure Deploying Aster AppCenter using a Virtual Machine Image Teradata recommends using the default size. 7. Click the Settings blade to configure optional features of the virtual machine. Parameter Name Storage Action Use managed disks Storage account Use the default, No. Aster AppCenter does not use managed disks. Specify the storage account to use for managed disks. Since Aster AppCenter does not use managed disks, leave this field as is with the autofilled content. Network Virtual Network Create a new or select an existing virtual network to deploy the AppCenter. Teradata recommends using an existing Aster deployed virtual network. Subnets Public IP address User the default selected subnets. Enter a name for the public IP address. Teradata recommends using an unique string for the public IP address, to make sure you connect to the desired Aster AppCenter. Network security group (firewall) Select the ports to enable or disable inbound and outbound traffic. Make sure HTTPS and HTTP are open for inbound rules. SSH can be enabled at this step if required. Extensions High availability Monitoring Use the default, No extension. Use the default, None. Use the default monitoring settings. 8. Click the Summary blade, review the summary, and click OK. Teradata recommends writing down the public IP address assigned to this AppCenter virtual machine, so you can access it later. Teradata Aster Analytics on Azure, Release AD 25

26 Chapter 4: Deploying Aster AppCenter on Azure Launching Aster AppCenter on Azure 9. Click the Buy blade, review the terms of use and privacy policy, and click Purchase. Launching Aster AppCenter on Azure After deployment, additional configuration my be required to launch Aster AppCenter on Azure. 1. Confirm that the Aster AppCenter URL is active by accessing the IP address you wrote down when deploying the AppCenter virtual machine, and logging in using the default admin username (admin), and default password (Admin123!). 2. After successfully logging in, click the Settings icon located in the upper right corner. 3. Make sure you change the default Admin Password, and then click Save. 26 Teradata Aster Analytics on Azure, Release AD

27 Chapter 4: Deploying Aster AppCenter on Azure Launching Aster AppCenter on Azure 4. Click the Connections Tab. Complete these fields: Database Connection Name, Aster Database Host (the IP address of the Aster queen), Database Name, Database Username, and Database Password. Make sure that AppCenter is deployed in the same Virtual Network as the Aster Database, and port 2406 is enabled for outbound traffic as AppCenter requires network connectivity to Aster via port Click Test Connection to test the connection. 6. Click Save. Teradata Aster Analytics on Azure, Release AD 27

28 Chapter 4: Deploying Aster AppCenter on Azure Launching Aster AppCenter on Azure Postrequisite Refer to the Aster AppCenter User Guide for information on configuring and using Aster AppCenter. 28 Teradata Aster Analytics on Azure, Release AD

29 CHAPTER 5 Configuring Aster Analytics Software for Azure The Aster Management Console (AMC) The Aster Database Management Console (AMC) is the main administrative interface to a Teradata Aster Analytics on Azure instance. After launching a Teradata Aster Analytics on Azure instance, use the AMC to manage, configure, and monitor your instance. For information on installing, configuring, and using the AMC, refer to the Aster Database User Guide, which is available from Data Movement To load data into an Aster instance, you can use the Aster Loader Tool, the COPY command, the INSERT command, or a custom-defined SQL-MapReduce data loading function you have written. To export data from an Aster instance, you can use the Aster Export Tool or the COPY TO command. For information on data movement, refer to the Teradata Aster Client Guide on Loading Data Using Aster Loader Tool The Aster Loader Tool, ncluster_loader, is a command-line application for bulk-loading data from files into an Aster instance. It provides an alternative to the SQL COPY statement. Each invocation of the Aster Loader Tool is equivalent to a single invocation of the COPY statement. Each invocation is a single database transaction that loads the contents of the specified data file or files into the specified table or tables. For information on using ncluster_loader, refer to the Teradata Aster Client Guide on Exporting Data Using the Aster Export Tool The Aster Export Tool, ncluster_export, is a command-line application for bulk-exporting data from an Aster instance to a file or to STDOUT. It provides an alternative to the SQL COPY TO statement. Each invocation of the Aster Export Tool is equivalent to a single invocation of the COPY TO statement. Each invocation is a single database transaction that exports the contents of the specified table into the specified file or STDOUT. For information on using ncluster_export, refer to the Teradata Aster Client Guide on Using Teradata Viewpoint Database administrators can manage Teradata Aster Analytics on Azure using Teradata Viewpoint for virtual machines running in the Azure public cloud. This provides one unified platform from which to view Teradata Aster Analytics on Azure, Release AD 29

30 Chapter 5: Configuring Aster Analytics Software for Azure Using the Teradata-Aster Database Connector information about and perform administrative tasks for Teradata Aster Analytics on Azure and Teradata Database on Azure. Viewpoint is analogous to the AMC in its functionality. For information on configuring and using Teradata Viewpoint, refer to the Aster Database User Guide, which is available from Using the Teradata-Aster Database Connector The Teradata-Aster Database Connector is a high-performance, bidirectional connector to copy data between Teradata Aster Analytics on Azure and Teradata Database on Azure. The Connector takes advantage of parallel processing on both databases to enable fast loading of large amounts of data. To do this, Teradata Aster Analytics on Azure creates multiple sessions with Teradata Database on Azure to achieve parallelism during export and load operations. The Connector consists of two Teradata Aster SQL-MapReduce functions called load_from_teradata and load_to_teradata. These two functions use the parallel version of the Teradata Parallel Transport (TPT) API to move data between the two systems. The Connector uses Teradata FastLoad and FastExport to do the loading and exporting of data on the Teradata side. You can use the ncli tdconnector command to check the set up and verification of network connectivity between participating instances, access to required ports, and successful authentication. For more information, refer to the Aster Database User Guide for Commodity Hardware, which is available from 30 Teradata Aster Analytics on Azure, Release AD

31 CHAPTER 6 Administrative Tasks Creating an Azure Active Directory Application and the Service Principal Prerequisite Before starting this procedure, do the following: See the Azure Documentation Center and search Create Service Principal. You will use the Azure documentation to complete the steps in this procedure using the Azure portal, Azure PowerShell, or Azure CLI. Request your Azure subscription administrator to assign the Contributor role. You must create an Azure Active Directory application and the service principal as part of the node failure recovery process. 1. Create the Azure Active Directory application. 2. Create the service principal. 3. Assign the Contributor role to the service principal. Login-AzureRmAccount ## List all the subscriptions Get-AzureRmSubscription Select-AzureRmSubscription -SubscriptionId your_subscription_id $app = New-AzureRmADApplication -DisplayName "{app-name}" -HomePage " -IdentifierUris " {app-name}" -Password "{your-password}" New-AzureRmADServicePrincipal -ApplicationId $app.applicationid New-AzureRmRoleAssignment -RoleDefinitionName Contributor - ServicePrincipalName $app.applicationid.guid $app.applicationid where the ApplicationID is the client ID. The password you choose is the secret key for the service principal. The tenant and subscription IDs appear in the output. Stop, Deallocate, or Delete a VM in Azure You can stop, deallocate or delete a VM in Azure. Before doing any of the following, ensure you have either stopped or terminated the Aster Database. For more information, see Stopping Aster Analytics on Azure. Teradata Aster Analytics on Azure, Release AD 31

32 Chapter 6: Administrative Tasks Stopping Aster Analytics on Azure Stop a VM You can stop a VM from inside of the virtual machine or using an Azure CLI command, such as azure vm stop. This stops the guest operating system, but keeps the compute resources. You will continue to be charged for the VM compute resources by the hour. Deallocate a VM You can deallocate a VM using the Azure portal by clicking Stop which actually stops and deallocates the VM. You can also deallocate a VM using an Azure CLI command, such as azure vm deallocate. Deallocating will stop the VM and release all the compute resources so you are no longer charged for the VM compute resources. However, all persistent disks remain, such as the operating system disk and the attached data disks. The VM can be restarted from the Azure portal. When you deallocate a VM, the data on the temporary/ephemeral local SSD is lost and cannot be recovered. Delete a VM You can delete a VM by either deleting the VM or the resource group in which the VM is contained from using the Azure portal or an Azure CLI command, such as azure vm delete. If the storage account that was used for the operating system and data disks is also deleted, which happens when the whole resource group is deleted, the persistent disks are deleted with it. If you delete only the VM itself, the disks remain in storage and can be attached to another VM that is created in the same region. Stopping Aster Analytics on Azure To stop and later restart a Aster Database VM, you must first stop the database to avoid incurring charges. 1. Stop the database. To shut down Aster Database use the softshutdown command. Execute this command on the queen node as the root user: # ncli system softshutdown Putting the database in this state may take a number of minutes. 2. Wait for the database to shut down. Use the system show and node show commands to check the Aster Database operational state. a) To check the queen s status, execute this command on the queen node as the root user: # ncli system show b) To check the status of all nodes in the cluster, use this command: # ncli node show 3. From the Azure portal, stop the VMs associated with the Teradata Aster Analytics on Azure. 32 Teradata Aster Analytics on Azure, Release AD