CN112256425A

CN112256425A - Load balancing method and system, computer cluster, information editing method and terminal

Info

Publication number: CN112256425A
Application number: CN202011116697.0A
Authority: CN
Inventors: 赵贝; 刘云冲; 矫恒浩
Original assignee: Qingdao Hisense Media Network Technology Co Ltd
Current assignee: Qingdao Hisense Media Network Technology Co Ltd
Priority date: 2020-10-19
Filing date: 2020-10-19
Publication date: 2021-01-22
Anticipated expiration: 2040-10-19
Also published as: CN112256425B; WO2021120976A3; WO2021120976A2

Abstract

The application discloses a load balancing method and system, a computer cluster, an information editing method and a terminal, and belongs to the technical field of networks. The method comprises the following steps: receiving a service setting request sent by a terminal, wherein the service setting request is used for requesting to operate a target service of a computer cluster; updating a load balancing rule according to the service setting request and a target load balancing algorithm corresponding to the target service carried in the service setting request; and carrying out load balancing according to the load balancing rule. The method and the device solve the problem that the flexibility of load balancing of the computer cluster is low. The method and the device are used for load balancing.

Description

Load balancing method and system, computer cluster, information editing method and terminal

Technical Field

The present application relates to the field of network technologies, and in particular, to a load balancing method and system, a computer cluster, an information editing method, and a terminal.

Background

With the development of network technology, cloud services implemented by computer clusters are favored.

The computer cluster can provide multiple services (English), the computer cluster comprises a management node and a plurality of computing nodes (such as servers), the computer cluster shares the received service request through the plurality of computing nodes, and the management node needs to perform load balancing of the plurality of computing nodes aiming at different services so as to ensure that the plurality of computing nodes can efficiently provide different services. In the related art, for different services, the management node performs load balancing by using the default load balancing algorithm.

Thus, there is less flexibility in load balancing among clusters of computers.

Disclosure of Invention

The application provides a load balancing method and system, a computer cluster, an information editing method and a terminal, which can solve the problem of poor flexibility of load balancing in the computer cluster. The technical scheme is as follows:

in one aspect, a load balancing method is provided, where the method includes:

receiving a service setting request sent by a terminal, wherein the service setting request is used for requesting to operate a target service of the computer cluster;

updating a load balancing rule according to the service setting request and a target load balancing algorithm corresponding to the target service carried in the service setting request;

and carrying out load balancing according to the load balancing rule.

In another aspect, an information editing method is provided, and the method includes:

when an information editing instruction is received, displaying an information editing page;

receiving a target load balancing algorithm corresponding to a target service input in the information editing page;

sending a service setting request to a computer cluster, wherein the service setting request is used for requesting to operate a target service of the computer cluster, and the service setting request carries a target load balancing algorithm corresponding to the target service.

In yet another aspect, a computer cluster is provided, the computer cluster comprising:

the interface node is used for receiving a service setting request sent by a terminal, wherein the service setting request is used for requesting to operate a target service of the computer cluster;

the load balancing node is used for updating a load balancing rule according to the service setting request and a target load balancing algorithm corresponding to the target service carried in the service setting request; and carrying out load balancing according to the load balancing rule.

In another aspect, a terminal is provided, where the terminal includes:

a communication interface for communicating with a computer cluster;

the display screen is used for displaying an information editing page when receiving an information editing instruction;

the processor is used for receiving a target load balancing algorithm corresponding to the target service input in the information editing page; and sending a service setting request to the computer cluster through the communication interface, wherein the service setting request carries a target load balancing algorithm corresponding to the target service.

The beneficial effect that technical scheme that this application provided brought includes at least:

in the load balancing method provided by the application, the computer cluster can update the load balancing rule according to the target load balancing algorithm corresponding to the target service carried by the service setting request, so that when load balancing is performed based on the load balancing rule, corresponding load balancing algorithms can be adopted for different services, and if the target load balancing algorithm is adopted for the target service for load balancing, the flexibility of the computer cluster for load balancing is improved.

And moreover, a target load balancing algorithm is carried in the service setting request, and the computer cluster can update the load balancing rule directly according to the service setting request, so that the request quantity is saved, and the network overhead is reduced.

Drawings

Fig. 1 is a schematic diagram of a load balancing system according to an embodiment of the present application;

FIG. 2 is a diagram of the relationship of a service, container node, and endpoint object;

fig. 3 is a schematic structural diagram of a server provided in an embodiment of the present application;

fig. 4 is a block diagram of a terminal according to an embodiment of the present disclosure;

fig. 5 is a flowchart of a load balancing method according to an embodiment of the present application;

fig. 6 is a flowchart of an information editing method provided in an embodiment of the present application;

fig. 7 is a flowchart of another load balancing method provided in an embodiment of the present application;

fig. 8 is a schematic diagram of a message flow when load balancing is performed in a computer cluster according to an embodiment of the present application;

fig. 9 is a flowchart of another load balancing method according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

With the development of network technologies, the demand for network services is increasing, and the requirement for efficient provision of services is also increasing, and then a cloud platform for implementing cloud services based on a computer cluster is gradually and widely applied. As shown in FIG. 1, a computer cluster 10 may include a management node 101 and a plurality of compute nodes 102, each management node 101 or compute node 102 may be a separate server; or the management node and the computing node may also be deployed in multiple servers and composed of different modules in the multiple servers, which is not limited in the embodiment of the present application. Containerized deployment may be performed in a computer cluster, which may include multiple containers, a container being a standardized software unit. The container may contain information needed when the program is running, such as code, runtime, system tools, system libraries and settings, etc. Alternatively, the computer cluster may be a kubernets (K8 s for short) based cluster, which may be referred to as a kubernets cluster. Kubernets is an open-source application for managing containerization on multiple hosts (such as servers) in a cloud platform, and provides a mechanism for application deployment, planning, updating and maintenance, so that containerization deployment of applications in a cluster can be simpler and more efficient.

The management node in the Kubernetes cluster can be called Master or cluster control node; each compute Node may be referred to as a Node or a load work Node. Each Node is assigned some workload (e.g. container) by the Master, and each Node may be deployed with multiple container nodes (Pod). The Pod is the smallest unit capable of being created and deployed in the kubernets cluster, is an application instance in the kubernets cluster, and contains one or more containers and resources shared by the containers. It should be noted that each Pod has a corresponding label (english: label) for indicating the application corresponding to the Pod. A group of Pod with the same tag can be abstracted into a Service, i.e. a Service, which can provide a uniform entry for the group of Pod, and processes related to the application inside and outside the cluster can communicate through the Service. The management node may manage individual services in a kubernets cluster. After a Service including label is created in the kubernets cluster, an end point (english: Endpoints) object with the same name is created in the cluster at the same time, and the end point object is used for storing an Internet Protocol (IP) address of the Pod under the Service. FIG. 2 is a diagram of the relationship of a service, container node, and endpoint object. As shown in fig. 2, the service named "my-service" has a corresponding selector (in english: selector), where the selector is equivalent to parameter information of the service and is used to indicate a tag of the service, and the tag of the service "my-service" in fig. 2 is "app ═ MyApp"; the port (port) corresponding to the service is identified as "9376- > 80". The service is an abstraction of three pod names "my-pod-1", "my-pod-2", and "my-pod-3", respectively, all labeled identically, all "app ═ MyApp", and the IP addresses of the three pods are "10.1.2.3", "10.1.4.5", and "10.1.3.8", respectively. The name of the endpoint object corresponding to the service is also "my-service", the endpoint object shown in fig. 2 may create the endpoint object corresponding to the service before the third pod, the IP address of the pod under the service is recorded in the endpoint object, that is, "10.1.2.3" and "10.1.4.5", and the identifier of the port of the service is also recorded in the endpoint object.

Service implements its communication and load balancing mechanisms through proxy (proxy) components, which include proxy processes running on each node in the cluster. And the proxy process is responsible for monitoring the change of the service and the endpoint in the cluster and maintaining the forwarding rule on each Node, and the proxy process is a specific implementation carrier of the service and can implement a network agent of the Pod on the Node. The Proxy component is a component for setting a load balancing rule in the kubernets cluster, the load balancing rule may include a load balancing algorithm required for load balancing, and based on the load balancing algorithm, a routing and forwarding rule between processes may be determined. When the Kubernetes cluster performs load balancing, for example, the management node needs to determine a specific load balancing mode based on the load balancing algorithm. The load balancing rules may include iptables rules or IP Virtual Server (IPVS) rules. The kubernets cluster may support a variety of load balancing algorithms, wherein a static load balancing algorithm may include: a Round Robin (RR) method, a Weighted Round Robin (WRR) method, a source address Hash (SH) method, a Destination Hash (DH) method, and the like. The dynamic load balancing algorithm comprises: a Least Connection (LC) method, a Weighted Least Connection (WLC) method, and the like.

The following embodiments of the present application provide a load balancing method and system, which can improve the flexibility of load balancing of a computer cluster. With continued reference to fig. 1, the load balancing system may include: a computer cluster 10, and a terminal 20 connected to the computer cluster 10. The terminal 20 may be used to manage a computer cluster 10. For example, a client for managing the computer cluster 10 may run in the terminal 20, and the terminal 20 may send a management request to the computer cluster 10, so that the computer cluster 10 performs corresponding operations based on the management request, thereby implementing management of the computer cluster 10 by the terminal 20. The terminal 20 may also request the computer cluster to provide services for it. For example, the terminal 20 may communicate with the management node 101 in the computer cluster, such as sending a service request to the management node 101, and then the management node 101 allocates a corresponding pod to process the request based on the service request, during which the computer cluster needs to perform load balancing. The terminal 20 may be a computer, or may also be a smart phone, a tablet computer, a notebook computer, or other electronic devices that can perform load balancing with the computing node, which is not limited in this embodiment of the application. Fig. 1 shows only one terminal 20 in the load balancing system 10, and optionally, the load balancing system 10 may include a plurality of terminals, such as 3, 5 or more. Alternatively, the computer cluster 10 and the terminal 20 may be connected through a wired network or a wireless network, wherein the wired network may include, but is not limited to: universal Serial Bus (USB), wireless networks may include, but are not limited to: wireless Fidelity (WIFI for short), bluetooth, infrared, Zigbee (Zigbee), data network, and the like.

Fig. 3 is a schematic structural diagram of a server according to an embodiment of the present application. The server may be the computer cluster 10 described above, or may also be a computing node or a management node in the computer cluster. The server includes a Central Processing Unit (CPU)301, a system memory 304 including a Random Access Memory (RAM)302 and a Read Only Memory (ROM)303, and a system bus 305 connecting the system memory 304 and the central processing unit 301. The server also includes a basic input/output system (I/O system) 306, which facilitates the transfer of information between devices within the computer, and a mass storage device 307, which stores an operating system 313, application programs 314, and other program modules 315.

The basic input/output system 306 comprises a display 308 for displaying information and an input device 309, such as a mouse, keyboard, etc., for a user to input information. Wherein the display 308 and input device 309 are connected to the central processing unit 301 through an input output controller 310 connected to the system bus 305. The basic input/output system 306 may also include an input/output controller 310 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, an input-output controller 310 may also provide output to a display screen, a printer, or other type of output device.

The mass storage device 307 is connected to the central processing unit 301 through a mass storage controller (not shown) connected to the system bus 305. The mass storage device 307 and its associated computer-readable media provide non-volatile storage for the server. That is, the mass storage device 307 may include a computer-readable medium (not shown) such as a hard disk or CD-ROM drive.

Without loss of generality, the computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 304 and mass storage device 307 described above may be collectively referred to as memory.

According to various embodiments of the present application, the server may also operate with remote computers connected to a network through a network, such as the Internet. That is, the servers may be coupled to the network 312 via the network interface unit 311, which is coupled to the system bus 305, or the network interface unit 311 may be used to couple to other types of networks or remote computer systems (not shown).

The memory also includes one or more programs, which are stored in the memory and executed by the central processor 501.

Fig. 4 is a block diagram of a terminal according to an embodiment of the present disclosure. The terminal 20 includes: a processor 1301 and a memory 1302.

Processor 1301 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 1301 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1301 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1301 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, processor 1301 may further include an AI (Artificial Intelligence) processor for processing computational operations related to machine learning.

Memory 1302 may include one or more computer-readable storage media, which may be non-transitory. The memory 1302 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1302 is used to store at least one instruction for execution by processor 1301 to implement the information editing methods provided by method embodiments herein.

In some embodiments, the terminal 20 may further optionally include: a peripheral interface 1303 and at least one peripheral. Processor 1301, memory 1302, and peripheral interface 1303 may be connected by a bus or signal line. Each peripheral device may be connected to the peripheral device interface 1303 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1304, display screen 1305, camera assembly 1306, audio circuitry 1307, positioning assembly 1308, and power supply 1309.

Peripheral interface 1303 may be used to connect at least one peripheral associated with I/O (Input/Output) to processor 1301 and memory 1302. In some embodiments, processor 1301, memory 1302, and peripheral interface 1303 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1301, the memory 1302, and the peripheral device interface 1303 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 1304 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1304 may serve as a communication interface for the terminal to ensure that the terminal communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 1304 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1304 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 1304 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 1304 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 1305 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1305 is a touch display screen, the display screen 1305 also has the ability to capture touch signals on or over the surface of the display screen 1305. The touch signal may be input to the processor 1301 as a control signal for processing. At this point, the display 1305 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 1305 may be one, disposed on the front panel of the terminal 20; in other embodiments, the display 1305 may be at least two, respectively disposed on different surfaces of the terminal 20 or in a folded design; in other embodiments, the display 1305 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 20. Even further, the display 1305 may be arranged in a non-rectangular irregular figure, i.e., a shaped screen. The Display 1305 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 1306 is used to capture images or video. Optionally, camera assembly 1306 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 1306 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuit 1307 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1301 for processing, or inputting the electric signals to the radio frequency circuit 1304 for realizing voice communication. The microphones may be provided in plural numbers, respectively, at different portions of the terminal 20 for the purpose of stereo sound collection or noise reduction. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1301 or the radio frequency circuitry 1304 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, audio circuitry 1307 may also include a headphone jack.

The positioning component 1308 is used for positioning the current geographic Location of the terminal 20 to implement navigation or LBS (Location Based Service). The Positioning component 1308 can be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.

The power supply 1309 is used to power the various components in the terminal 20. The power source 1309 may be alternating current, direct current, disposable or rechargeable. When the power source 1309 comprises a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, the terminal 20 also includes one or more sensors 1310. The one or more sensors 1310 include, but are not limited to: acceleration sensor 1311, gyro sensor 1312, pressure sensor 1313, fingerprint sensor 1314, optical sensor 1315, and proximity sensor 1316.

The acceleration sensor 1311 can detect the magnitude of acceleration on three coordinate axes of the coordinate system established with the terminal 20. For example, the acceleration sensor 1311 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 1301 may control the display screen 1305 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 1311. The acceleration sensor 1311 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 1312 may detect a body direction and a rotation angle of the terminal 20, and the gyro sensor 1312 may cooperate with the acceleration sensor 1311 to collect a 3D motion of the user with respect to the terminal 20. Processor 1301, based on the data collected by gyroscope sensor 1312, may perform the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

The pressure sensor 1313 may be disposed on a side bezel of the terminal 20 and/or underlying the display 1305. When the pressure sensor 1313 is disposed on the side frame of the terminal 20, a user's holding signal to the terminal 20 may be detected, and the processor 1301 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 1313. When the pressure sensor 1313 is disposed at a lower layer of the display screen 1305, the processor 1301 controls an operability control on the UI interface according to a pressure operation of the user on the display screen 1305. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 1314 is used for collecting the fingerprint of the user, and the processor 1301 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 1314, or the fingerprint sensor 1314 identifies the identity of the user according to the collected fingerprint. When the identity of the user is identified as a trusted identity, the processor 1301 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 1314 may be disposed on the front, back, or side of the terminal 20. When a physical key or vendor Logo is provided on the terminal 20, the fingerprint sensor 1314 may be integrated with the physical key or vendor Logo.

The optical sensor 1315 is used to collect the ambient light intensity. In one embodiment, the processor 1301 may control the display brightness of the display screen 1305 according to the ambient light intensity collected by the optical sensor 1315. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1305 is increased; when the ambient light intensity is low, the display brightness of the display screen 1305 is reduced. In another embodiment, the processor 1301 can also dynamically adjust the shooting parameters of the camera assembly 1306 according to the ambient light intensity collected by the optical sensor 1315.

A proximity sensor 1316, also known as a distance sensor, is typically disposed on a front panel of the terminal 20. The proximity sensor 1316 is used to gather the distance between the user and the front face of the terminal 20. In one embodiment, the processor 1301 controls the display 1305 to switch from the bright screen state to the dark screen state when the proximity sensor 1316 detects that the distance between the user and the front surface of the terminal 20 gradually decreases; the display 1305 is controlled by the processor 1301 to switch from the breath-screen state to the bright-screen state when the proximity sensor 1316 detects that the distance between the user and the front surface of the terminal 20 is gradually increasing.

Those skilled in the art will appreciate that the configuration shown in fig. 4 is not intended to be limiting of terminal 20 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

Fig. 5 is a flowchart of a load balancing method provided in an embodiment of the present application, where the load balancing method may be used for the computer cluster 10 in fig. 1. As shown in fig. 5, the method may include:

step 501, receiving a service setting request sent by a terminal, where the service setting request is used to request to operate a target service of a computer cluster.

Step 502, updating the load balancing rule according to the service setting request and a target load balancing algorithm corresponding to the target service carried in the service setting request.

And 503, carrying out load balancing according to the load balancing rule.

In summary, in the load balancing method provided in the embodiment of the present application, the computer cluster may update the load balancing rule according to the target load balancing algorithm corresponding to the target service carried in the service setting request, so that when load balancing is performed based on the load balancing rule, corresponding load balancing algorithms may be adopted for different services, and if load balancing is performed for the target service by adopting the target load balancing algorithm, flexibility of load balancing performed by the computer cluster is improved.

Fig. 6 is a flowchart of an information editing method provided in an embodiment of the present application, which may be used in the terminal 20 shown in fig. 1 or fig. 4. As shown in fig. 6, the method may include:

step 601, when receiving an information editing instruction, displaying an information editing page.

Step 602, receiving a target load balancing algorithm corresponding to the target micro service input in the information editing page.

Step 603, sending a service setting request to the computer cluster, where the service setting request is used to request to operate a target service of the computer cluster, and an indication of the service setting request carries a target load balancing algorithm corresponding to the target service.

To sum up, in the information editing method provided in this embodiment of the present application, the service setting request sent by the terminal to the computer cluster may carry a target load balancing algorithm corresponding to the target service. Therefore, the computer cluster can update the load balancing rule according to the target load balancing algorithm, and further can adopt the corresponding load balancing algorithm for different services when carrying out load balancing based on the load balancing rule, for example, the target load balancing algorithm is adopted for target services to carry out load balancing, so that the flexibility of carrying out load balancing by the computer cluster can be improved.

Fig. 7 is a flowchart of another load balancing method provided in an embodiment of the present application, which may be used in the load balancing system shown in fig. 1. As shown in fig. 7, the method may include:

and step 701, when the terminal receives an information editing instruction, displaying an information editing page. Step 702 is performed.

The computer cluster can support the use of a plurality of applications, and each application can correspond to one service in the computer cluster to realize various running requirements of the application program. A developer may operate each service in the computer cluster through a terminal (e.g., a computer), for example, may perform a deployment operation or an update operation on the service in the computer cluster. For example, when a certain application supported by the computer cluster needs to be updated, the developer may send a code required for updating the application to the computer cluster through a computer connected to the computer cluster, and update a service corresponding to the application in the computer cluster accordingly. Alternatively, the developer may write the code directly on the computer, or the code written on other devices may be sent to the computer cluster through the computer.

When a developer needs to operate services in a computer cluster, the developer can operate on a terminal to trigger the terminal to receive an information editing instruction, and then a display screen of the terminal can display an information editing page according to the information editing instruction. For example, the information editing page may be a code input page, and a developer may input information required by the computer cluster to operate the service, such as a code of the service or a parameter of the service, in the information editing page.

Step 702, the terminal receives a target load balancing algorithm corresponding to the target service input in the information editing page. Step 703 is performed.

In an alternative example, a developer may write the content of the load balancing algorithm corresponding to the target service in an information editing page displayed on a display screen of the terminal, and accordingly the terminal may receive the target load balancing algorithm input in the information editing page.

In another optional example, the target load balancing algorithm is any one of multiple load balancing algorithms supported by the computer cluster, corresponding identifiers are preset for the multiple load balancing algorithms, and a developer may also directly input the identifier of the target load balancing algorithm in the information editing page. For example, the identifier of the load balancing algorithm may be a name set for the load balancing algorithm, and the name may indicate a load balancing manner of the load balancing algorithm, for example, the name of the polling method may be RR, and a worker may directly know an implementation manner of the load balancing algorithm according to the name. Alternatively, the identifier of the load balancing algorithm may be represented by an arbitrarily set value, for example, "1" may be used to represent the polling method, and "2" may be used to represent the minimum connection method. Optionally, a load balancing algorithm option may be displayed in the information editing page, and the developer may trigger (e.g., click) the load balancing option to select a target load balancing algorithm corresponding to the target service. For example, after the load balancing algorithm option is triggered, identifiers of multiple load balancing algorithms supported by the computer cluster may be displayed on a display screen of the terminal, and a worker may click the displayed identifiers to select a corresponding load balancing algorithm as a target load balancing algorithm.

Optionally, a target load balancing algorithm corresponding to the target service may be recorded in operation setting content of the target service, where the operation setting content may also be referred to as service details, for example, the operation setting content may include service codes and comments (english: annotations), and the target load balancing algorithm is recorded in the comments in the operation setting content of the target service. For example, the developer may input the operation setting content of the target service in the information editing page, and trigger the load balancing option when writing the comment in the operation setting content, select the target load balancing algorithm, and record the identifier of the target load balancing algorithm in the comment.

Step 703, the terminal sends a service setting request to the computer cluster, where the service setting request is used to request to operate a target service of the computer cluster, and the service setting request carries a target load balancing algorithm corresponding to the target service. Step 704 is performed.

After the developer finishes editing the operation setting content of the target service, the developer can trigger the terminal to generate a service setting request according to the operation setting content, and send the service setting request to the computer cluster. Accordingly, the computer cluster may receive the service setting request sent by the terminal. The service setting request carries a target load balancing algorithm corresponding to a target service; if the service setting request carries the operation setting content of the target service, the target load balancing algorithm is recorded in the annotation in the operation setting content. The service setup request is for requesting an operation on a target service of the computer cluster. Optionally, the operation performed on the target service requested by the service setting request may include an update operation of the service or a deployment operation of the service, where the update operation of the service is to update a service originally existing in the computer cluster, and the deployment operation of the service is to add an originally non-existing service to the computer cluster.

Optionally, the computer cluster includes an Application Programming Interface Server (API Server) component and a storage component. The storage component may be an Etcd component, which discovers a storage repository for a highly available, strongly consistent service. Optionally, the API Server component and the storage component may be deployed in multiple nodes of a computer cluster. The API server component serves as a unified inlet of the computer cluster and a coordinator of each component in the computer cluster, and provides interface service by using a Hypertext transfer protocol (HTTP) API. The adding, modifying, deleting, checking and monitoring operations of the resources of the service in the computer cluster can be processed by the API Server component and then submitted to the Etcd component for storage. The increase of the resources of the service is also deployment operation performed on the service, and the modification of the resources of the service is also update operation performed on the service. In the embodiment of the application, the terminal can send the service setting request to the API Server component of the computer cluster so as to request to operate the target service. The API Server can write the operation setting content of the target service carried by the service setting request into the Etcd component so as to realize the operation on the target service. When the target service is operated, the endpoint object corresponding to the target service is also changed correspondingly. The following embodiments of the present application explain an operation of a target service as an example of an update operation.

Step 704, the computer cluster judges whether the service setting request carries a target load balancing algorithm corresponding to the target service. If the service setting request carries a target load balancing algorithm corresponding to the target service, executing step 705; if the service request does not carry the target load balancing algorithm corresponding to the target service, step 706 is executed.

After receiving the service setting request, the computer cluster can acquire information carried by the service setting request and analyze the information to judge whether the service setting request carries a target load balancing algorithm corresponding to a target service. For example, the computer cluster may directly obtain the comment in the operation setting content carried by the service setting request, and determine whether the comment includes the target load balancing algorithm or the identifier thereof.

For example, a proxy component running in each Node in the computer cluster may monitor each service and a corresponding endpoint object in the computer cluster, for example, list monitoring (english: list-watch) is performed on services and endpoints stored in the Etcd component. When the service and the corresponding endpoint object are determined to be changed, for example, when the service is updated, a comment in operation setting content of a target service carried by a service setting request can be obtained, and whether an identifier of a target load balancing algorithm corresponding to the target service is recorded in the comment is further judged. Optionally, the identifier of the target load balancing algorithm may be recorded in a preset position in the annotation, and the proxy component may directly obtain information of the preset position to determine whether the information is the identifier of the target load balancing algorithm. For example, the proxy component may compare the information of the preset location with identifiers of a plurality of load balancing algorithms supported by the computer cluster, and determine whether an identifier identical to the information exists in the identifiers of the plurality of load balancing algorithms. And when the identifiers of the multiple load balancing algorithms have the identifiers same as the information, determining that the service setting request carries a target load balancing algorithm corresponding to the target service, and determining that the load balancing algorithm indicated by the identifiers is the target load balancing algorithm. And when the identifiers of the load balancing algorithms are different from the information, determining that the service setting request does not carry the target load balancing algorithm corresponding to the target service.

Step 705, the computer cluster updates the load balancing rule according to the target load balancing algorithm. Step 707 is performed.

In the embodiment of the application, a load balancing algorithm required to be adopted for load balancing and state information of each pod in a computer cluster are recorded in the load balancing rule. When it is determined that the service setting request carries the target load balancing algorithm corresponding to the target service, the computer cluster may update the load balancing algorithm in the load balancing rule, and set the load balancing algorithm corresponding to the target service in the service setting request as the target load balancing algorithm. Such as updates to the load balancing rules, may be performed by proxy components in the computer cluster. Optionally, the proxy component in the computer cluster may also update other contents in the load balancing rule according to the operation of the API Server component on the service. For example, when monitoring the adding or deleting operation of a pod in a service, the proxy component updates the state information of each pod in the service in the load balancing rule; or, when the source address, the destination address or the port corresponding to the pod in service changes, the relevant information of the pod in the load balancing rule may be updated accordingly.

Optionally, the load balancing rule in the computer cluster may include a rule corresponding to each pod in the cluster, and each pod may correspond to a rule, and the load balancing rule may indicate a status of the pod, such as whether the pod can be normally used, and a source address, a destination address, a port, and the like corresponding to a request that can be processed by the pod. The load balancing algorithm for the target service in the load balancing rule may be recorded in a position other than the rule corresponding to the pod.

Step 706, the computer cluster updates the load balancing rule according to a default load balancing algorithm. Step 707 is performed.

The computer cluster may correspond to a default load balancing algorithm, for example, the default load balancing algorithm is a round robin method. When the computer cluster determines that the service setting request does not carry the target load balancing algorithm corresponding to the target service, the load balancing rule can be updated according to the default load balancing algorithm. Optionally, the proxy component in the computer cluster may update other contents in the load balancing rule than the load balancing algorithm only according to the operation of the API Server component on the service. For example, when monitoring an addition or deletion operation of a pod in a certain service, the proxy component updates the state information of each pod in the service in the load balancing rule; or, when a source address, a destination address, or a port corresponding to a pod in a service changes, the relevant information of the pod in the load balancing rule may be updated accordingly. For other descriptions of the load balancing rule, reference may be made to the related description of step 705, and further description of the embodiments of the present application is omitted.

Step 707, the terminal sends a service request for the target service to the computer cluster. Step 708 is performed.

For example, an application supported by the target service may be run on the terminal, and when the user uses the application through the terminal, the terminal may be triggered to send a service request for the target service to the computer cluster to request the computer cluster to provide the corresponding service for the user.

Step 708, when the computer cluster receives the service request, load balancing is performed according to the load balancing rule.

When receiving a service request sent by a terminal, a computer cluster may determine, according to a load balancing algorithm, a route required to process the service request, and further determine a device or a computing resource in the device that actually processes the service request, so as to instruct the device to actually process the service request. For example, the service request sent by the terminal may carry a Cluster IP (english: Cluster IP) of the target service, so as to indicate that the service targeted by the service request is the target service, where the Cluster IP is a unique IP address of the service in the computer Cluster. The terminal may send the service request to a load balancer (DS) in the computer cluster. The Director Server may perform routing and forwarding according to the Cluster IP of the target service through a load balancing rule, and finally send the service request sent by the terminal to a Real Server (RS) that actually processes the request, for example, to a real backend Pod in the real Server.

Fig. 8 is a schematic diagram of a message flow when performing load balancing in a computer cluster according to an embodiment of the present application, and fig. 8 illustrates an example in which a load balancing rule based on load balancing performed by the computer cluster is an IPVS rule. As shown in fig. 8, the terminal 20 may send the generated service request to the load balancer, and an operating system of the load balancer may include a kernel space and a user space, where the kernel space includes five links, namely, a pre-routing (forwarding) link, a packet Ingress (INPUT) link, a packet egress (OUTPUT) link, a FORWARD (FORWARD) link, and a post-routing (post) link. The service request sent by the terminal will first reach the PREROUTING chain in the kernel space of the load balancer. At this time, the source address of the message is Client IP (CIP), that is, the IP address of the terminal, and the destination address is Virtual IP (VIP), which is a cluster IP. The kernel of the load balancer may determine whether a destination address carried in a packet of the service request is a local address, and when determining that the destination address is the local address, may send the packet to the INPUT chain. When the data packet reaches the INPUT chain, the IPVS will check whether the destination address and the port identifier carried in the data packet are in the IPVS rule, so as to determine whether the service requested by the data packet is a cluster service. If the destination address and port carried in the data packet do not exist in the IPVS rule, the INPUT chain sends the data packet to the user space. If the Destination Address and the port identifier carried in the packet exist in the IPVS rule, the IPVS may determine a backend server that processes the packet by using a load balancing algorithm specified by the IPVS rule, and then the INPUT chain changes the Destination Address carried in the packet into an Address of the backend server, that is, the packet is subjected to Destination Address Translation (DNAT). At this time, the source address of the data packet is CIP, and the destination address is the Real Server IP (RIP) of the back end. The INPUT chain may then send the packet after the destination address is changed to the posing chain, determine a routing path by the posing chain, and send the packet to a Real Server (Real Server) at the back end, so that the Real Server processes the packet. After receiving the data packet, the Real Server can detect whether the destination address of the data packet is the address of the local machine, and when determining that the destination address of the data packet is the address of the local machine, the Real Server processes the data packet and starts to construct a response message and sends the response message back to the Director Server. At this time, the source address of the data message is RIP and the destination address is CIP. Before responding to the terminal, the Director Server modifies the source address of the data packet into the VIP address of the Director Server, and then responds to the terminal, wherein the source address of the data packet is VIP and the destination address is CIP.

In the embodiments of the present application, the foregoing embodiments only take the case that the service setting request is only a request for operating one target service, and optionally, the service setting request may be a request for operating a plurality of target services. For each target service in the multiple target services, the load balancing system may perform steps 701 to 708, which is not described in detail in this embodiment.

It should be noted that, in the related art, a load balancing algorithm may be set only at a cluster level, and the same load balancing algorithm is used for load balancing for all services in a computer cluster, that is, when requests for different services are received, the default load balancing algorithm is used for determining computing resources for processing the requests. In the embodiment of the application, the corresponding load balancing algorithm can be set for each service in the computer cluster, so that after the computer cluster receives the service request of the terminal, the computer cluster can adopt the appropriate load balancing algorithm for different services to perform load balancing, the characteristic that the computer cluster supports various load balancing algorithms can be fully utilized, and the flexibility of the computer cluster for performing load balancing is improved.

The load balancing method in the embodiment of the present application may be implemented by different nodes in a computer cluster in a coordinated manner, and the load balancing method in the embodiment of the present application is described below by taking the computer cluster including three nodes, i.e., an interface node, a storage node, and a load balancing node as an example. For example, fig. 9 is a flowchart of a further load balancing method provided in an embodiment of the present application, and as shown in fig. 9, the method may include:

step 901, when the terminal receives an information editing instruction, displaying an information editing page. Step 902 is performed.

It should be noted that, in the step 901, reference may be made to the step 701, and details of the embodiment of the present application are not described herein again.

Step 902, the terminal receives a target load balancing algorithm corresponding to the target service input in the information editing page. Step 903 is performed.

It should be noted that step 702 may be referred to as step 902, and details of the embodiment of the present application are not described herein again.

Step 903, the terminal sends a service setting request to the interface node, where the service setting request is used to request to operate a target service of the computer cluster, the service setting request carries an operation setting content of the target service, and a target load balancing algorithm is recorded in a comment in the operation setting content. Step 904 is performed.

It should be noted that, in step 903, reference may be made to step 703, and details of the embodiment of the present application are not described herein again.

Step 904, the interface node stores the operation setting content of the target service in the storage node, so as to operate the target service according to the service setting request. Step 905 is performed.

For example, the service setting request may be used to request to update or deploy a target service, and the interface node may add, modify, or delete information related to the target service stored in the storage node according to the request, so as to implement an operation on the target service. It should be noted that, in step 903, reference may be made to the related description of the operation setting content stored in step 703, which is not described in detail in this embodiment of the application.

Step 905, the load balancing node monitors the target service in the storage node. Step 906 is performed.

It should be noted that, in step 905, reference may be made to related descriptions of monitoring services and endpoints by the proxy component in step 704, which is not described in detail in this embodiment of the present application.

Step 906, when monitoring that the target service in the storage node changes, the load balancing node determines whether a target load balancing algorithm corresponding to the target service is recorded in a comment in the operation setting content of the target service. If a target load balancing algorithm corresponding to the target service is recorded in the comment in the operation setting content, executing step 907; if the comment in the operation setting content does not record the target load balancing algorithm corresponding to the target service, step 908 is executed.

It should be noted that step 906 may refer to step 704, and details of the embodiment of the present application are not described herein.

Step 907, the load balancing node updates the load balancing rule according to the target load balancing algorithm. Step 709 is performed.

It should be noted that step 907 refers to step 705, and details are not described in this embodiment of the application.

And 908, updating the load balancing rule by the load balancing node according to a default load balancing algorithm. Step 709 is performed.

It should be noted that step 908 may refer to step 706, and details of this embodiment are not described herein.

Step 909, the terminal sends a service request for the target service to the interface node. Step 910 is performed.

It should be noted that step 707 may be referred to in step 909, and details of the embodiment of the present application are not described herein.

Step 910, when the interface node receives the service request, the load balancing node performs load balancing according to the load balancing rule.

It should be noted that step 910 may refer to step 708, and details of the embodiment of the present application are not described herein.

To sum up, in the load balancing method provided in the embodiment of the present application, the load balancing node in the computer cluster may update the load balancing rule according to the target load balancing algorithm corresponding to the target service carried in the service setting request, so that when load balancing is performed based on the load balancing rule, corresponding load balancing algorithms may be used for different services, and if load balancing is performed using the target load balancing algorithm for the target service, flexibility of load balancing performed by the computer cluster is improved.

It will be understood that the terms "comprises" and "comprising," and any variations thereof, in this application are intended to cover a non-exclusive inclusion, such that a product or apparatus that comprises a list of elements is not necessarily limited to those elements explicitly listed, but may include other elements not expressly listed or inherent to such product or apparatus. The term "module," as used herein, refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and/or software code that is capable of performing the functionality associated with that element.

It should be noted that, the method embodiments provided in the embodiments of the present application can be mutually referred to corresponding apparatus embodiments, and the embodiments of the present application do not limit this. The sequence of the steps of the method embodiments provided in the embodiments of the present application can be appropriately adjusted, and the steps can be correspondingly increased or decreased according to the situation, and any method that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall be covered by the protection scope of the present application, and therefore, the details are not repeated.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by a program to instruct relevant hardware, where the program may be stored in a computer-readable storage medium, and when the program in the computer-readable storage medium is run on a computer, the computer is caused to execute the load balancing method provided by the embodiments of the present application. The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.

Embodiments of the present application further provide a computer program product including instructions, which, when running on a computer, causes the computer to execute the load balancing method provided in the embodiments of the present application.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of load balancing, for a cluster of computers, the method comprising:

and carrying out load balancing according to the load balancing rule.

2. The method according to claim 1, wherein the operation comprises an update operation of a service or a deployment operation of a service, the service setting request carries operation setting content of the target service, and the target load balancing algorithm is recorded in a comment in the operation setting content.

3. The method according to claim 2, wherein the updating the load balancing rule according to the service setting request and a target load balancing algorithm corresponding to the target service carried in the service setting request includes:

and updating the load balancing rule according to the target load balancing algorithm when the target load balancing algorithm is determined to be recorded in the annotation in the operation setting content.

4. The method of claim 3, further comprising:

and updating the load balancing rule according to a default load balancing algorithm when the target load balancing algorithm is determined not to be recorded in the annotation in the operation setting content.

5. The method according to any one of claims 1 to 4, wherein the target load balancing algorithm is any one of a plurality of load balancing algorithms supported by the computer cluster, each of the plurality of load balancing algorithms has a corresponding identifier, and the service setting request carries the identifier of the target load balancing algorithm.

6. An information editing method, applied to a terminal, the method comprising:

7. The information editing method according to claim 6, wherein the receiving of the target load balancing algorithm corresponding to the target service input in the information editing page includes:

receiving operation setting content of the target service input in the information editing page, wherein a target load balancing algorithm corresponding to the target service is recorded in a note in the operation setting content.

8. A computer cluster, the computer cluster comprising:

9. A terminal, characterized in that the terminal comprises:

a communication interface for communicating with a computer cluster;

10. A load balancing system, the load balancing system comprising: the computer cluster of claim 8 and the terminal of claim 9; and the terminal is connected with the computer cluster.