Dynamic Load Balancer Configuration in Virtualized Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed load balancer configurations in software-defined datacenters are static and manual, making them difficult to maintain and inefficient, as they require administrators to know all potential clients and their locations for proper configuration, leading to increased configuration data size and scalability issues.
Innovation Solution
A method involving a logical load balancer with a traffic detector that sends load balancer configurations to local load balancers via a configuration distributor, allowing dynamic configuration and load balancing within the hypervisor, reducing the need for manual administration and scaling efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If administrators manually configure distributed load balancer components on each host, then load balancing can be properly configured for known clients, but the system becomes difficult to maintain and does not scale well
Solution Approach 1:
The load balancer component on each host automatically detects VIP traffic and requests configuration from the logical load balancer without manual administrator intervention. The system self-configures by detecting traffic patterns and obtaining necessary configuration data dynamically, eliminating the need for manual configuration maintenance while ensuring accurate load balancing setup.
Solution Approach 2:
The load balancer component provides feedback to the logical load balancer by reporting detected VIP traffic and client information. The logical load balancer uses this feedback to dynamically update configuration data and push it to appropriate hosts, creating a closed-loop system that automatically adapts to changing traffic patterns without manual intervention.
2Ease of operation
If administrators assume all hosts require distributed load balancer components, then configuration is simplified, but configuration data size increases significantly
Solution Approach 1:
Instead of uniformly configuring all hosts with load balancer components, the system enables the component only on hosts where VIP traffic is actually detected. Each host's configuration is tailored to its actual traffic needs, avoiding unnecessary configuration data on hosts that don't require load balancing functionality.
Solution Approach 2:
The system takes a partial approach by deploying load balancer components only where needed rather than on all hosts. Configuration data is pushed selectively to hosts that have detected VIP traffic, providing exactly the right amount of configuration without excessive data distribution.
3Ease of manufacture
If manual configuration methods are used for distributed load balancer, then initial setup is possible, but scalability is limited and administrative burden increases
Solution Approach 1:
The system transitions from static manual configuration to dynamic automatic configuration. The load balancer component continuously monitors for VIP traffic and automatically requests configuration updates from the logical load balancer, allowing the system to scale dynamically as new clients and traffic patterns emerge without administrative intervention.
Solution Approach 2:
The logical load balancer pre-configures template configuration data that can be rapidly pushed to multiple hosts. When VIP traffic is detected, the configuration is already prepared and can be automatically distributed, enabling rapid scaling without requiring administrators to perform preliminary manual configuration for each new host.
Data Source
AI summary
An example method of distributed load balancing in a virtualized computing system includes: configuring, at a logical load balancer, a traffic detector to detect traffic to a virtual internet protocol address (VIP) of an application having a plurality of instances; detecting, at the traffic detector, a first request to the VIP from a client executing in a virtual machine (VM) supported by a hypervisor executing on a first host; sending, by a configuration distributor of the logical load balancer in response to the detecting, a load balancer configuration to a configuration receiver of a local load balancer executing in the hypervisor for configuring the local load balancer to perform load balancing for the VIP at the hypervisor using the load balancer configuration.