Changes and Additions - Teradata Software for AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
upc1519757374969.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud
Date Release Description
November 2018 5.08 Implemented the following changes:
  • Added new topics:
  • Updated the supported releases
  • Updated references to product offering names on the AWS Marketplace from Teradata Database to Teradata Vantage
  • Added instructions for BYOL users scaling a system up or down
  • Replaced Teradata REST Services with Teradata Query Service
  • Added Custom Tags option to the Planning Worksheet
  • Added ability to connect to a mainframe when deploying a Teradata ecosystem, deploying Teradata Database separately, or after deploying an instance to allow data transfer between your mainframe and the Teradata Database in the public cloud.
  • Added ability to add hot standby nodes when deploying a Teradata ecosystem, deploying Teradata Database separately, or deploying an instance.
  • When a new system image is created, Teradata Database reprovisions hot standby nodes based on the new system image.
  • If you provisioned HSNs and scaled an instance up, you must run tdc-hot-standby --update-hsns to refresh the HSN nodes.
  • Added a notice not to manually attach EBS volumes to your instance as they are automatically attached at the time the instance is deployed.
  • Prior to scaling a system in or out, you must stop Teradata Database.
  • For all supported m4 instance types, increased the AMP count to 24 and storage configuration to 24 x (209 GB to 3 TB).
  • Changed the total node storage to a maximum of 72 TB per node for EBS instance types when deploying a Teradata ecosystem or deploying Teradata Database separately.
  • For scaling out and in, increased the maximum volume count per node, maximum scale out, and minimum scale in limits.
  • Changed the tdc-nodestart-post-swupgrade command to tdc-image.
  • Added information for clarity:
    • Added log on and switching to root user to Configuring and Initializing ClientHandler on Teradata Database Nodes.
    • Added the tdinfo command and a new step if you are using Teradata DSC for Scaling Out a System and Scaling In a System.
  • Removed the following topics:
    • Configuring a Teradata Viewpoint Instance for DSC
  • Changed feature names to conform to industry standards:
    • Fold to scale in
    • Unfold to scale out
    • Resizing to scaling up or scaling down