Hybrid Cloud GSLB

A hybrid cloud configuration as a Global Server Load balancer (GSLB) between two regions residing in same or different cloud or on-premise environments. It provides flexibility to implement disaster recovery site.

It requires atleast two Thunder instances in each region or location. One instance serves as the master controller, while the other functions as the site device. It is possible to configure multiple site devices, but it is recommended to have a minimum of three site devices to ensure seamless failover and effective disaster recovery.

Both regions should maintain an equivalent number of resources, whether hosted in the cloud or on-premise.

To create and install three thunder instances in any one region use Thunder-3NIC-3VM template. Same template can be used to install in another region.

Architectural References

Refer to the following for architectural references:

• Azure-to-Azure

Region1 and Region2 both are in Azure cloud.

Figure 194 : Azure-to-Azure Cloud



• Azure-to-On-Premises (any)

Region1 is in Azure cloud and Region2 is on-premise or vice versa.

Figure 195 : Azure-to-On-Premise



• On-Premise-to-On-Premise (any)

Region1 and Region2 are on-premises.

Figure 196 : On-Premise-to-On-Premise

GSLB Deployment Topology

Figure 197 shows the GSLB deployment topology having two regions, Region1 and Region2. Both the regions must have identical number of resources:

• One GSLB controller
  This Thunder instance act as a DNS server that directs client to reach the active load balancer.
  GLSB controller of Region1 is considered as 'Master' and Region2 is considered as 'Member'.
  
• Two site devices
  These Thunder instances act as a load balancer and sends traffic to the server.
  Each site device may have multiple app or web servers configured and route the traffic accordingly.

Figure 197 : Hybrid Cloud GSLB Deployment Topology

Configure Hybrid Cloud GSLB

Hybrid Cloud GSLB configuration requires two regions and each region should host three Thunder instances.

Python3 should be installed on your machine from where the scripts are executed to run the Hybrid Cloud GSLB configuration. For more information, see Install Python3.

To configure hybrid cloud GSLB, perform the following:

1. Run the following command to verify if all the PIP dependencies are installed:

   pip3 install -r REQUIREMENTS.txt

2. Create three vThunder instances if not already created. For more information, see Thunder-3NIC-3VM.

3. Download A10-vThunder_ADC-CONFIGURATION > HYBRID-CLOUD-GSLB folder from GitHub.

4. From Start menu, open PowerShell and navigate to this downloaded folder and open the HYBRID_CLOUD_CONFIG_GSLB_PARAM.json with a text editor.

   NOTE:

   Each parameter has a default value mentioned in the parameter file which can be modified as required.

5. Configure Master Controller for Region1.

   Master Controller is the first vThunder instance in Region1 and it could be any vThunder instance.

   1. Collect Master Controller Parameter Details information.
   2. Update this information under masterConfigDetails section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.

6. Configure Site1 for Region1.

   Site1 is the second vThunder instance in Region1 and it could be any vThunder instance.

   1. Collect Site Details information.
   2. Update this information under siteList1 section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.

7. Configure Site2 for Region1.

   Site2 is the third vThunder instance in Region1 and it could be any vThunder instance.

   1. Collect Site Details information.
   2. Update this information under siteList2 section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.

8. Configure Member Controller for Region2.

   Member Controller is the first vThunder instance in Region2 and it could be any vThunder instance.

   1. Collect Master Controller Parameter Details information.
   2. Update this information under memberConfigDetails section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.

9. Configure Site1 for Region2.

   Site1 is the second vThunder instance in Region2 and it could be any vThunder instance.

   1. Collect Site Details information.
   2. Update this information under siteList3 section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.

10. Configure Site2 for Region2.

    Site2 is the third vThunder instance in Region2 and it could be any vThunder instance.

    1. Collect Site Details information.
    2. Update this information under siteList4 section of the //A10-vThunder_ADC-CONFIGURATION/HYBRID-CLOUD-GSLB/HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file.
11. Verify if all the configurations in the HYBRID_CLOUD_CONFIG_GSLB_PARAM.json file are correct and save the changes.

12. Run the following command to configure GSLB:

    PS C:\Users\TestUser\A10-vThunder_ADC-CONFIGURATION\HYBRID-CLOUD-GSLB> python HYBRID_CLOUD_CONFIG_GSLB.py

13. If the Hybrid cloud is configured successfully, the following message is displayed:

    Gathering public and private ip address for site devices.
    ---------------------------------------------------------
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Configuring slb server for site: site1
    Successfully Configured slb server for site: site1
    Configuring service group for site: site1
    Successfully Configured service group for site:site1
    Successfully Configured virtual server for site: site1
    Successfully Configured gslb site: site1
    Successfully Configured default route:site1
    Configurations are saved on partition: shared
    -----------------------------------------------------------
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Configuring slb server for site: site2
    Successfully Configured slb server for site: site2
    Configuring service group for site: site2
    Successfully Configured service group for site:site2
    Successfully Configured virtual server for site: site2
    Successfully Configured gslb site: site2
    Successfully Configured default route:site2
    Configurations are saved on partition: shared
    -----------------------------------------------------------
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Configuring slb server for site: site3
    Successfully Configured slb server for site: site3
    Configuring service group for site: site3
    Successfully Configured service group for site:site3
    Successfully Configured virtual server for site: site3
    Successfully Configured gslb site: site3
    Successfully Configured default route:site3
    Configurations are saved on partition: shared
    -----------------------------------------------------------
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Configuring slb server for site: site4
    Successfully Configured slb server for site: site4
    Configuring service group for site: site4
    Successfully Configured service group for site:site4
    Successfully Configured virtual server for site: site4
    Successfully Configured gslb site: site4
    Successfully Configured default route:site4
    Configurations are saved on partition: shared
    -----------------------------------------------------------
    Configuring controller devices
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Successfully Configuring gslb server for controller: masterController
    Successfully Configured ServiceIp for site: masterController
    Successfully Configured ServiceIp for site: masterController
    Successfully Configured ServiceIp for site: masterController
    Successfully Configured ServiceIp for site: masterController
    Successfully Configured site information for: masterController
    Successfully Configured site information for: masterController
    Successfully Configured site information for: masterController
    Successfully Configured site information for: masterController
    Successfully Configured gslb policy for: masterController
    Successfully Configured gslb zone for: masterController
    Successfully Configured gslb controller and status interval: masterController
    Successfully Configured gslb controller group: masterController
    Successfully Configured geo location: masterController
    Successfully Configured default route:masterController
    Configurations are saved on partition: shared
    configured ethernet- 1 ip
    configured ethernet- 2 ip
    Successfully Configured gslb server for controller: memberController
    Successfully Configured gslb controller group: memberController
    Successfully Configured default route:memberController
    Configurations are saved on partition: shared