Deployment Templates

This section helps you in provisioning a new Thunder virtual machine on the Azure cloud.

Before proceeding, it is recommended to review the Prerequisites.

 

To provision a new virtual Thunder ADC instance on an Azure cloud, perform the following steps:

1. Create VNet, Subnet, and NSG.
   It is not mandatory to create new resources, the existing resources can be used in deployment and configuration.
2. Create Public IP address.
   It is not mandatory to create new resource, the existing resource can be used in deployment and configuration.

3. Select an appropriate template for deploying vThunder ADC on Azure cloud according to your use case.

   Table 2 provides a list of various use cases along with their respective supported ARM templates.

Table 2 : Supported ARM Templates

Use Case	Template Name	Number of Thunder/s	Number of NICs	Data-in NIC VIP	Description
Standalone Thunder ADC	Thunder-2NIC-1VM	1	2	Private	Creates one vThunder instance with one management and one data NIC (data-in), see Figure 1. Applies additional configuration on vThunder as required: Change Password Basic Server Load Balancer A10 License SSL Certificate
Thunder ADC in High Availability mode with Private VIP.	Thunder-3NIC-2VM-PVTVIP	2	3	Private	Creates two vThunder instances with HA setup and each vThunder has one management and two data NICs (data-in and data-out), see Figure 27. Configures data-in network interface card (NIC) with Private IP on VIP. Applies additional configuration on vThunder as required: Change Password Basic Server Load Balancer A10 License SSL Certificate High Availability When one instance becomes unavailable, another instance seamlessly handles the request without requiring manual intervention. High availability can be configured within the same or different availability zone within a same region.
Thunder ADC in High Availability mode with Public VIP.	Thunder-3NIC-2VM-PUBVIP	2	3	Public	Creates two vThunder instances with HA setup and each vThunder has one management and two data NICs (data-in and data-out), see Figure 54. Configures data-in network interface card (NIC) with Public IP on VIP. Applies additional configuration on vThunder as required: Change Password Basic Server Load Balancer A10 License SSL Certificate High Availability When one instance becomes unavailable, another instance seamlessly handles the request without requiring manual intervention. High availability can be configured within the same or different availability zone within a same region.
Thunder ADC in High Availability mode with Private VIP and Backend Server Autoscale.	Thunder-3NIC-2VM-PVTVIP	2	3	Private	Creates two vThunder instances with HA setup and each vThunder has one management and two data NICs (data-in and data-out), see Figure 28. Configures data-in network interface card (NIC) with Private IP on VIP. Applies additional configuration on vThunder as required: Change Password Server Load Balancer on Backend Autoscale A10 License SSL Certificate High Availability Applies SLB configuration using a webhook URL on vThunder for newly added or deleted web/app servers through backend server VMSS autoscaling. When one instance becomes unavailable, another instance seamlessly handles the request without requiring manual intervention. High availability can be configured within the same or different availability zone within a same region.
Thunder ADC in High Availability mode with Public VIP and Backend Server Autoscale.	Thunder-3NIC-2VM-PUBVIP	2	3	Public	Creates two vThunder instances with HA setup and each vThunder has one management and two data NICs (data-in and data-out), see Figure 55. Configures data-in network interface card (NIC) with Public IP and Private IP on VIP. Applies additional configuration on vThunder as required: Change Password Server Load Balancer on Backend Autoscale A10 License SSL Certificate High Availability Applies SLB configuration using a webhook URL on vThunder for newly added or deleted web/app servers through backend server VMSS autoscaling. When one instance becomes unavailable, another instance seamlessly handles the request without requiring manual intervention. High availability can be configured within the same or different availability zone within a same region.
Thunder ADC with GSLB (Disaster Recovery Site in a cross-region or hybrid cloud environment)	Thunder-3NIC-3VM	3	3	Public	Creates three vThunder instances each vThunder has one management and two data NICs (data-in and data-out) in the same region1 and zone1, see Figure 84. These three vThunder instances are referred as Master Controller (Active), Site1 and Site2. Applies additional configuration on vThunder as required: Change Password Basic Server Load Balancer A10 License SSL Certificate Hybrid Cloud GSLB The identical set of vThunder resources should be deployed in region2 zone1 using the same template. The three vThunder instances in region2 zone1 are referred as the Member Controller (Standby), Site1, and Site2. When region1 experiences an outage, region2 seamlessly handles all requests through DNS switch over.
Thunder ADC in AutoScale Mode.	Thunder-3NIC-VMSS	'N' number of vThunder instances	3	Private	Creates the vThunder instances in a self-autoscaling mode, allowing for automatic scaling based on traffic volume, see Figure 110. The maximum number of Thunder replicas allowed can be defined. Each vThunder instance contains three NICs. Creates Virtual Machine Scale Set (VMSS) and auto scale-in or scale-out based on the performance metric threshold rule. Auto-applies additional configuration on vThunder upon the creation of a webhook URL: SSL Certificate Server Load Balancer A10 License Applies SLB configuration using a webhook URL on vThunder for newly added or deleted web/app servers through backend server VMSS autoscaling. Auto-deploys a Certificate Authority SSL Certificate in Storage account and Server Load Balancer and license in Automation Account Variable. Configures log analysis capabilities using Azure Log Analytics workspace integration. Configures metrics monitoring using Azure Application Insights integration. When one instance becomes unavailable, another instance seamlessly handles the request without requiring manual intervention. Auto configures all vThunder configurations that are pre-defined in the template. NOTE: All the configured vThunder instances do not synchronize their SLB configurations.

After completing the deployment process, proceed to configure your setup. For more information, see ADC Configuration Templates.