Starting with Teradata Fabric version 2.11, support of automated deployment of Teradata Fabric on scalable clusters has been added. With automatic deployment, Teradata Fabric software is installed and new nodes are registered with the Teradata Fabric Manager in the primary cluster automatically. This feature is part of a different package/script named TDQG_DEPLOYMENT, which is part of the node package.
This feature is available for the following clusters:
- Automatically Deploy Teradata Fabric on Hortonworks HDP
- Automatically Deploy Teradata Fabric on Cloudera CDH/CDP
- Automatically Deploy Teradata Fabric on Azure HDInsight
- Automatically Deploy Teradata Fabric on Amazon EMR
- Automatically Deploy Teradata Fabric on Google Cloud Instance Group
- Automatically Deploy Teradata Fabric on Google Cloud Dataproc
- Automatically Deploy Teradata Fabric on Azure Virtual Machine Scale Set
- Automatically Deploy Teradata Fabric on AWS Auto Scaling Group
Review the following automatic deployment considerations and limitations:
- Removing a node from a cluster or removing the Teradata Fabric service from a node does not remove the entry from Viewpoint. You must remove the entry manually, or make use of the automatic node removal feature if enabled.
- Restarting the Teradata Fabric service restarts the node and might impact the active Teradata Fabric queries. This does not apply to HDInsight.
- Automatic deployment is intended for registering a node with Teradata Fabric Manager. It cannot be used to upgrade or downgrade the Teradata Fabric software.
- Automatic deployment does not support adding a single node to multiple Teradata Fabric Managers.