Use case: Deployment of domain name based autoscale™ service group
Deployment scenario
-
Create datacenters (represented by GSLB sites).
add gslb site aws-sydney 192.0.2.2add gslb site aws-nvirginia 198.51.100.111add gslb site alb-southindia 203.0.113.6 -
Add a name server with the DNS gateway IP address where the GSLB node is added. This must be done in all datacenters.
add dns nameServer 8.8.8.8 -
Add servers for ELB and ALB.
add server aws-sydney_server lb-sydney-1052691850.ap-southeast-2.elb.amazonaws.comadd server aws-nvirginia_server LB-nvirginia-860559595.us-east-1.elb.amazonaws.comadd server alb-southindia_server alb.southindia.cloudapp.azure.com -
Add GSLB autoscale service groups for each ELB and ALB and bind each server to the respective service group.
add gslb serviceGroup aws-nvirginia_sg HTTP -autoScale DNS -siteName aws-nvirginiaadd gslb serviceGroup aws-sydney_sg HTTP -autoScale DNS -siteName aws-sydneyadd gslb serviceGroup alb-southindia_sg HTTP -autoScale DNS -siteName alb-southindiabind gslb serviceGroup aws-nvirginia_sg aws-nvirginia_server 80bind gslb serviceGroup aws-sydney_sg aws-sydney_server 80bind gslb serviceGroup alb-southindia_sg alb-southindia_server 80 -
Add a GSLB virtual server and bind the application domain and the service groups to this virtual server.
add gslb vserver gv1 HTTPbind gslb vserver gv1 -serviceGroupName aws-nvirginia_sgbind gslb vserver gv1 -serviceGroupName aws-sydney_sgbind gslb vserver gv1 -serviceGroupName alb-southindia_sg