Device and method for balancing active load of Docker container

Abstract

The invention discloses a device and a method for balancing an active load of a Docker container. The method comprises the following steps: receiving a to-be-executed application file and presetting to-be-executed application details; converting the to-be-executed application file into a Docker mirror image; executing an application starting command in the Docker mirror image; transmitting a registration request and registering an application to a distributed coordination server; acquiring registering information from the distributed coordination server, acquiring change data, corresponding to the container, of an application example, and analyzing the data; updating a configuration file to a general load balancer by configuring a template. According to the device and the method disclosed by the invention, a real-time active discovering and registering mechanism is realized; the general load balancer is adopted for providing services for a Docker container cluster.

Description

technical field [0001] The present invention relates to the technical field of the Internet, in particular to a Docker container active load balancing device and method. Background technique [0002] Docker is an open source application container engine. A single instance running a Docker container cannot meet the production needs. The industry generally adopts the Docker cluster mode to provide external services. At present, many open source container cluster management systems such as kubernetes, mesos, swarm, etc. Combining basic network solutions such as flannel, weave, pipework, etc., solves the problems faced by Docker clusters, but the load balancing of Docker container clusters has not yet had a perfect solution. [0003] The goal of Docker container discovery is to expose services hidden inside Docker containers, reducing or eliminating communication barriers between Docker containers. [0004] The purpose of Docker container cluster load balancing is to uniformly ...

AI Technical Summary

Problems solved by technology

[0005] At present, a common load balancing solution for Docker clusters, such as kubernetes, provides three modes of load balancing: 1. Use the host IP+PORT method, which needs to expose the host IP to the caller, especially when After the host machine goes down, the caller needs to switch to other host machines; 2. Use the native Service method and provide external services with private IP. This method requires that the caller must also be inside the kubernetes cluster, otherwise privateIP cannot Access; 3. Use dedicated load balancing in IaaS environments such as GCE and AWS. This method is not available to most enterprises, and all of these cannot meet the needs of production for high availability.

[0006] Obviously, based on the common Docker cluster load balancing solution, it often depends on the cluster management system. Changes or upgrades of the cluster management system will lead to the failure of the original method; Stop changing information, but also refresh the load balancer synchronously; or due to the use of a dedicated load balancer, the requirements for learning and maintenance costs are high, which is not suitable for technology precipitation and increases enterprise costs; or when the service runs in multiple environments such as Docker environment, vmware, kvm or running independently in the host environment cannot meet the needs of heterogeneous environments

Images