Cloud-based load balancing method and device, equipment and medium

Abstract

The invention provides a cloud-based load balancing method and device, equipment and a medium, and effectively solves the problem that a cloud load balancing product has relatively large defects when carrying out load balancing and flow control on a credential cloud platform. The method comprises the steps of determining a target deployment mode based on a connection type of the cloud platform; the hardware load balancing equipment receives an external network request sent by an external network through the target deployment mode to obtain a balancing result; the hardware load balancing device sends the balancing result to an intra-cloud core switch based on a routing mode corresponding to the target deployment mode, so that the intra-cloud core switch forwards the balancing result to the service access switch based on the intra-cloud IP; and the service access switch calls a plurality of computing nodes based on the equalization result, so that the plurality of computing nodes respectively provide corresponding network services for an external network based on the equalization result.

Description

Technical Field

[0001] The present application relates to the technical field of information technology application innovation cloud platform, and specifically, to a cloud-based load balancing method, device, equipment and medium. Background Art

[0002] With the rapid development of information technology, load balancing technology in application delivery has been widely used in data centers and cloud computing as a key means to improve system service capabilities and availability. Traditional hardware load balancing products are usually implemented through dedicated hardware devices (such as load balancers). These devices are directly deployed between the server and the external network and run independently of the operating system. They use built-in traffic scheduling algorithms to distribute user access traffic to multiple servers on demand to achieve load balancing. Hardware load balancing devices usually have powerful processing capabilities and rich load balancing strategies, such as F5, Deepin, and Sangfor. Cloud load balancing products are based on virtualization technology and provide load balancing services on cloud platforms. They are implemented through software, such as Figure 1 As shown in the figure, it is integrated into the cloud management platform and supports dynamic expansion and flexible configuration. Cloud load balancing products can adjust resource allocation in real time according to business load to achieve effective resource utilization. At the same time, they also have high availability and automatic failover capabilities to ensure business continuity.

[0003] In recent years, with the large-scale deployment of the Xinchuang (i.e., information technology application innovation) cloud platform in data centers, cloud load balancing products are being widely used due to their natural advantages of being highly integrated with cloud platforms. Although cloud service technology is constantly improving and the functions of cloud load balancing products are constantly being enhanced and expanded, compared with the specific hardware acceleration functions and customization capabilities of traditional hardware load balancing, cloud load balancing products are still subject to certain restrictions in terms of usage scenarios. With the distributed deployment of technology products, a large number of application systems that were originally deployed in traditional network areas and used hardware load balancing have begun to use the cloud load balancing products of the Xinchuang cloud platform. Due to their functional characteristics, they cannot meet specific requirements such as the primary and standby loads of traditional hardware load balancing, http 1.1 health checks, and reverse access of back-end nodes to front-end load IPs. This greatly limits the application delivery capabilities of technology products during distributed deployment. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a cloud-based load balancing method, device, equipment and medium, which effectively solves the major defects of cloud load balancing products when performing load balancing and traffic control on the trusted cloud platform.

[0005] In a first aspect, an embodiment of the present application provides a cloud-based load balancing method, which is applicable to a cloud platform, wherein the cloud platform includes a cloud edge switch, a cloud core switch, a service access switch, a computing node, a layer 2 bridge switch, an off-cloud aggregation switch, and a hardware load balancing device, and the method includes:

[0006] Determine and adopt the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information;

[0007] The hardware load balancing device receives an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud;

[0008] The hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP;

[0009] The service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes respectively provide corresponding network services to the external network based on the balancing result.

[0010] In combination with the first aspect, an embodiment of the present application provides a first possible implementation of the first aspect, wherein the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device is determined and adopted based on the connection type of the cloud platform, including:

[0011] Determining whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform;

[0012] If so, the cloud platform is deployed according to the deployment mode corresponding to the connection type.

[0013] In combination with the first aspect, an embodiment of the present application provides a second possible implementation of the first aspect, wherein, if so, deploying the cloud platform according to the deployment mode corresponding to the connection type includes:

[0014] Based on the deployment mode, the layer 2 bridge switch and the cloud edge switch connected to the cloud platform are configured respectively to obtain configuration results;

[0015] Based on the configuration result, the operation and maintenance interface of the cloud platform is configured to complete the configuration of the cloud platform.

[0016] In combination with the first aspect, an embodiment of the present application provides a third possible implementation of the first aspect, wherein the determining whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform further includes:

[0017] If not, controlling the off-cloud aggregation switch to connect to the hardware load balancing device;

[0018] Configure a cloud border switch connected to the hardware load balancing device, and interconnect the configured cloud border switch with the cloud-outside aggregation switch.

[0019] In combination with the first aspect, the embodiment of the present application provides a fourth possible implementation of the first aspect, wherein the configuring a cloud edge switch connected to the hardware load balancing device, and interconnecting the configured cloud edge switch with the cloud outside aggregation switch, includes:

[0020] Creating a plurality of corresponding sub-interfaces on the cloud edge switch based on the intra-cloud IP in the cloud platform;

[0021] A VRF corresponding to the sub-interface is configured on the off-cloud aggregation switch to complete the interconnection between the cloud edge switch and the off-cloud aggregation switch.

[0022] In combination with the first aspect, an embodiment of the present application provides a fifth possible implementation of the first aspect, wherein the hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP, including:

[0023] The hardware load balancing device determines a routing mode between the hardware load balancing device and the core switch in the cloud based on the target deployment mode;

[0024] The hardware load balancing device sends the balancing result to the core switch in the cloud based on the routing mode.

[0025] In combination with the first aspect, an embodiment of the present application provides a sixth possible implementation of the first aspect, wherein the service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes provide corresponding network services for the external network based on the balancing result, including:

[0026] The multiple computing nodes execute corresponding network services based on the balancing results and generate network service results, and send the network service results to the service access switch;

[0027] The service access switch sends the network service result to the external network through a preset communication method.

[0028] In a second aspect, an embodiment of the present application provides a cloud-based traffic control and load balancing device, the device comprising:

[0029] An adoption module is used to determine and adopt a target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information;

[0030] A sending module, used for the hardware load balancing device to receive an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud;

[0031] A forwarding module, configured for the hardware load balancing device to send the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP;

[0032] The calling module is used for the service access switch to call multiple computing nodes based on the balancing result, so that the multiple computing nodes provide corresponding network services for the external network based on the balancing result.

[0033] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, any step of a cloud-based load balancing method is performed.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the computer program executes any one of the steps of a cloud-based load balancing method.

[0035] A cloud-based load balancing method provided in an embodiment of the present application is applicable to a cloud platform, wherein the cloud platform includes a cloud edge switch, a core switch within the cloud, a service access switch, a computing node, a layer 2 bridge switch, an off-cloud aggregation switch, and a hardware load balancing device. The method first determines and adopts a target deployment mode between the cloud edge switch, the core switch within the cloud, the layer 2 bridge switch, the off-cloud aggregation switch, and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information; secondly, the hardware load balancing device receives an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP within the cloud; then the hardware load balancing device uses the routing mode corresponding to the target deployment mode to balance the external network request. The balancing result is sent to the core switch in the cloud, so that the core switch in the cloud forwards the balancing result to the service access switch based on the IP in the cloud; finally, the service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes provide corresponding network services to the external network based on the balancing result, and receives external network requests and performs balancing processing through the target deployment mode between the hardware load balancing device and the cloud boundary switch, the core switch in the cloud, the Layer 2 bridge switch, the aggregation switch outside the cloud and the hardware load balancing device, and realizes flow control in the process of balancing processing, and realizes forwarding external network requests outside the cloud to the real server in the cloud for balancing, thereby solving the major defects of cloud load balancing products when performing load balancing and flow control on the trusted cloud platform, thereby improving the effectiveness of load balancing and flow control of the trusted cloud platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0037] Figure 1 A connection diagram of an existing cloud load balancing product is shown;

[0038] Figure 2 A schematic diagram of a process of a first cloud-based load balancing method provided in an embodiment of the present application is shown;

[0039] Figure 3 A schematic diagram of a deployment mode in which a cloud platform provided by an embodiment of the present application supports access to a layer 2 bridge switch is shown;

[0040] Figure 4 A schematic diagram showing a deployment mode in which the cloud platform provided in an embodiment of the present application does not support access to a Layer 2 bridge switch;

[0041] Figure 5 A schematic diagram of the structure of a first cloud-based traffic control and load balancing device provided in an embodiment of the present application is shown;

[0042] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0043] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0044] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0045] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0046] Compared with traditional hardware, current cloud load balancing products are relatively weak in terms of specific hardware acceleration functions and customization capabilities of load balancing, and are still subject to certain restrictions in usage scenarios. With the distributed deployment of technology products, a large number of application systems that were originally deployed in traditional network areas and used hardware load balancing have begun to use the cloud load balancing products of the Xinchuang Cloud Platform. Due to their functional characteristics, they cannot meet specific requirements such as the primary and standby loads of traditional hardware load balancing, http1.1 health checks, and reverse access of back-end nodes to front-end load IPs. This greatly limits the application delivery capabilities of technology products during the distributed deployment process.

[0047] Based on this, the embodiments of the present application provide a cloud-based load balancing method, apparatus, device and medium, which are described below through embodiments.

[0048] Example 1

[0049] To facilitate understanding of this embodiment, a cloud-based load balancing method disclosed in the embodiment of this application is first introduced in detail. Figure 2 A flow chart of a cloud-based load balancing method is shown. The present application provides a cloud-based load balancing method, which is applicable to a cloud platform. The cloud platform includes a cloud edge switch, a cloud core switch, a service access switch, a computing node, a layer 2 bridge switch, an off-cloud aggregation switch, and a hardware load balancing device. The method includes:

[0050] S101, determining and adopting a target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information;

[0051] S102, the hardware load balancing device receives an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud;

[0052] S103, the hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP;

[0053] S104: The service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes respectively provide corresponding network services for the external network based on the balancing result.

[0054] In step S101, the cloud platform described in the present application is the Xinchuang cloud platform. Due to the variety of application scenarios, in order to make the cloud platform more adaptable to application scenarios, the actual hardware facility structure and connection type of the cloud platform are not exactly the same. For example, facilities and equipment that can be installed and used in some cloud platforms cannot be installed and used in other cloud platforms. Whether the cloud platform can install some facilities or equipment is determined according to the connection type between the facilities and equipment inside the cloud platform. Therefore, the deployment mode is determined based on the connection type of the cloud platform, that is, different connection types correspond to different deployment modes between facilities and equipment. Therefore, the deployment mode required in the cloud platform is the target deployment mode, and the cloud boundary switch, the core switch in the cloud, the Layer 2 bridge switch, the aggregation switch outside the cloud and the hardware load balancing device are deployed according to the target deployment mode; and correspondingly, different deployment modes have different configuration information, so as to better ensure the deployment effect of the cloud platform.

[0055] In the specific implementation process of step S101, there is an embodiment in which: the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device is determined and adopted based on the connection type of the cloud platform, including:

[0056] S1011, judging whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform;

[0057] S1012: If yes, deploy the cloud platform according to the deployment mode corresponding to the connection type.

[0058] In steps S1011-S1012, the cloud platform usually has multiple connection types, including but not limited to direct connection, indirect connection (such as through a gateway), dedicated line connection, VPN connection, etc. The multiple connection types are intended to meet the access requirements of different devices and different scenarios. Therefore, the connection type of the cloud platform can be used to determine whether the layer 2 bridge switch can access the cloud platform. The layer 2 bridge switch provides high-speed and secure layer 2 interconnection between the VPC (virtual private cloud) and the cloud external network segment. It can realize the layer 2 interconnection between the cloud external network segment and the same network segment subnet of the cloud VPC, as well as the layer 3 interconnection between subnets of different network segments. In addition, the layer 2 Bridging also supports 4-7 layer network capabilities, allowing devices outside the cloud to access resources such as elastic load balancing, peer connections, and VPC terminal nodes in the cloud; and if the connection type of the cloud platform allows the Layer 2 bridge switch to be connected to the cloud platform, the cloud platform is deployed according to the deployment mode corresponding to the connection type. Then the deployment mode corresponding to this connection type is that one end of the cloud edge switch is connected to the external network, the other end of the cloud edge switch is connected to one end of the core switch in the cloud, and the other end of the core switch in the cloud is respectively connected to the Layer 2 bridge switch and the service access switch, and the Layer 2 bridge switch is also connected to a hardware load balancing device, such as Figure 3 As shown, in order to ensure that the deployment mode enables the cloud platform to operate normally, the cloud platform is configured accordingly.

[0059] In the specific implementation process of step S1012, there is an embodiment: if so, deploying the cloud platform according to the deployment mode corresponding to the connection type, including:

[0060] S10121. Based on the deployment mode, configure the layer 2 bridge switch and the cloud edge switch connected to the cloud platform respectively to obtain configuration results;

[0061] S10122. Perform interface configuration on the operation and maintenance interface of the cloud platform based on the configuration result to complete the configuration of the cloud platform.

[0062] In steps S10121-S10122, the cloud platform is configured for the corresponding deployment mode based on the connection type of the layer 2 bridge switch that the cloud platform can connect to, such as configuring the basic network of the layer 2 bridge switch, including remote management, M-LAG deployment, and docking with the core switch / load balancing device in the cloud, and configuring EVPN neighbors on the cloud boundary switch and the layer 2 bridge switch to achieve intercommunication with the external network outside the cloud, the external network is a network that needs to communicate data with the cloud platform, and after the configuration is completed, the configuration result of the configuration is output or generated, and based on the configuration result of the configuration, the interface configuration is performed on the operation and maintenance interface of the cloud platform, the interface configuration includes adding a layer 2 bridge switch device, configuring a BGP peer, creating a device group, a layer 2 bridge access point, a layer 2 bridge instance, etc., thereby completing the hardware and software configuration of the cloud platform.

[0063] In the specific implementation process of step S1011, there is an embodiment in which: judging whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform further includes:

[0064] S10111. If not, control the off-cloud aggregation switch to connect to the hardware load balancing device;

[0065] S10112. Configure a cloud border switch connected to the hardware load balancing device, and interconnect the configured cloud border switch with the cloud external aggregation switch.

[0066] In steps S10111-S10112, if the connection type of the cloud platform cannot enable the Layer 2 bridge switch to be connected to the cloud platform, that is, the cloud platform does not support the connection of the Layer 2 bridge switch, the deployment mode corresponding to this connection type is that the external network is connected to one end of the cloud-outside aggregation switch, and the other end of the cloud-outside aggregation switch is respectively connected to the edge switch and the hardware load balancing device, and the cloud edge switch is also connected to the cloud-inside core switch, then the cloud-outside aggregation switch, the cloud edge switch, and the cloud-inside core switch in the cloud platform are controlled to be connected to the hardware load balancing device according to the above deployment mode, such as Figure 4 As shown, the cloud edge switch connected to the hardware load balancing device is configured, including configuration operations such as remote management, M-LAG deployment, and interconnection with the core switch in the cloud, and the cloud-outside aggregation switch is controlled to be interconnected with the configured cloud edge switch that meets the requirements of the cloud platform, thereby realizing the deployment of the cloud platform.

[0067] In the specific implementation process of step S10112, there is an embodiment in which: configuring the cloud edge switch connected to the hardware load balancing device, and interconnecting the configured cloud edge switch with the cloud external aggregation switch, includes:

[0068] S101121. Create a plurality of corresponding sub-interfaces on the cloud edge switch based on the intra-cloud IP in the cloud platform;

[0069] S101122. Configure a VRF corresponding to the sub-interface on the off-cloud aggregation switch to interconnect the cloud edge switch with the off-cloud aggregation switch.

[0070] In steps S101121-S101122, multiple facilities and equipment in the cloud platform all have cloud IPs, and cloud IP refers to the IP address of a virtual machine (VM) or a container instance in the internal network of a cloud service provider. Then, a sub-interface corresponding to the cloud IP is set in the cloud edge switch according to the number and type of cloud IPs. For example, one or a class of cloud IPs has a sub-interface, and other situations may also be included. Then, a VRF corresponding to the sub-interface is configured on the cloud-outside aggregation switch, that is, one sub-interface corresponds to one VRF. Then, the cloud edge switch and the cloud-outside aggregation switch are interconnected through the VRF and the sub-interface. In this deployment mode, the cloud edge switch and the cloud are configured with routing forwarding and isolation, so as to forward external network requests from the external network to the cloud, configure outbound routing on the cloud edge switch, forward external network requests from hardware load balancing to the cloud-outside aggregation switch, and forward them to load balancing processing by the cloud-outside aggregation switch.

[0071] In step S102, when the external network sends an external network request to the platform, the hardware load balancing device receives the external network request sent by the external network through the target deployment mode. If the cloud platform supports access to a Layer 2 bridge switch, the external network request sent by the external network is sent to the hardware load balancing device via the cloud boundary switch, the core switch within the cloud, and the Layer 2 bridge switch. If the cloud platform does not support access to a Layer 2 bridge switch, the external network request sent by the external network is sent to the hardware load balancing device via the cloud external aggregation switch, wherein the external network request includes a cloud IP, which is used for the cloud platform to identify and balance the external network request based on the cloud IP, so that the hardware load balancing device balances the external network request to obtain a balanced result; the balanced result includes decision information on how to allocate the external network request to different computing nodes, and while the hardware load balancing device balances the external network request to obtain a balanced result, it also controls the traffic generated during the sending of the external network request to ensure the smooth operation of the cloud platform.

[0072] In step S103, the hardware load balancing device obtains a balancing result after balancing the external network request, and sends the balancing result to the core switch in the cloud according to the routing mode corresponding to the target deployment mode. Different deployment modes correspond to different routing modes. The balancing result still includes the IP in the cloud. The hardware load balancing device sends the balancing result based on the target deployment mode so that the core switch in the cloud forwards the balancing result to the service access switch based on the IP in the cloud. That is, when the cloud platform performs load balancing and traffic control on the external network request, it is based on the IP in the cloud in the external network request, and the service access switch also receives the balancing result based on the IP in the cloud.

[0073] In the specific implementation process of step S103, there is an embodiment in which the hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP, including:

[0074] S1031, the hardware load balancing device determines the routing mode between the hardware load balancing device and the core switch in the cloud based on the target deployment mode;

[0075] S1032. The hardware load balancing device sends the balancing result to the core switch in the cloud based on the routing mode.

[0076] In steps S1031-S1032, in the cloud platform, different deployment modes correspond to different routing modes. When the target deployment mode includes a Layer 2 bridge switch, the routing mode corresponding to the target deployment mode is: the hardware load balancing device sends the balancing result to the core switch in the cloud via the Layer 2 bridge switch; when the target deployment mode does not include a Layer 2 bridge switch, the routing mode corresponding to the target deployment mode is that the hardware load balancing device sends the balancing result to the core switch in the cloud via the cloud external aggregation switch and the cloud boundary switch. Therefore, after confirming that the deployment mode in the cloud platform is determined, the routing mode is also determined immediately. Therefore, the balancing result is sent to the core switch in the cloud according to the determined routing mode.

[0077] In step S104, after receiving the balancing result, the service access switch calls multiple computing nodes based on the decision information in the balancing result, so that the multiple computing nodes provide corresponding network services to the external network based on the balancing result. In the process of the entire computing node providing network services, the hardware load balancing device continuously monitors the status of external network requests and the load of the computing nodes. If it is detected that some computing nodes are overloaded or the demand for some network services has changed, the load balancing device will recalculate the balancing result and notify the service access switch to make corresponding adjustments. The cloud platform also has a fault recovery and fault tolerance mechanism. If a computing node fails or cannot provide network services, the hardware load balancing device can detect this situation and automatically redirect the request to other available computing nodes, which ensures the continuity and availability of network services.

[0078] In the specific implementation process of step S104, there is an embodiment in which the service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes provide corresponding network services to the external network based on the balancing result, including:

[0079] S1041. The multiple computing nodes execute corresponding network services based on the balancing result and generate network service results, and send the network service results to the service access switch;

[0080] S1042: The service access switch sends the network service result to an external network through a preset communication method.

[0081] In steps S1041-S1042, the multiple computing nodes execute corresponding network services based on the decision information in the balancing result and generate network service results. The network service results include processed data, query results, generated documents, or responses to specific operations, etc. The network service results are sent to the external network via a predetermined communication method. The predetermined communication method can be that the business access switch directly sends the network service results to the external network through wireless communication or other methods, or it can be that the network service results are sent to the external network in the reverse order of the target deployment mode and the routing mode. There is no specific limitation, thereby ensuring that users or devices in the external network can receive the network service results they request, thereby completing the entire network service process.

[0082] This application uses the existing cloud load balancing product and the hardware load balancing device of this application in different scenarios at the same time. The resulting support balancing and traffic control effects are shown in Table 1. It can be seen that the hardware load balancing device of this application is better than the cloud load balancing product.

[0083] Table 1 shows the support balancing and traffic control effects produced by cloud load balancing products and hardware load balancing devices.

[0084]

[0085] Example 2

[0086] The present application also provides a cloud-based load balancing device, such as Figure 5 The block diagram of a cloud-based load balancing device is shown. The functions implemented by the cloud-based load balancing device correspond to the steps of performing a cloud-based load balancing method on a terminal device. The device can be understood as a component of a server including a processor, and the device includes:

[0087] Adopting module 501, for determining and adopting the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information;

[0088] A sending module 502 is used for the hardware load balancing device to receive an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud;

[0089] Forwarding module 503, used for the hardware load balancing device to send the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP;

[0090] The calling module 504 is used for the service access switch to call multiple computing nodes based on the balancing result, so that the multiple computing nodes respectively provide corresponding network services for the external network based on the balancing result.

[0091] In a feasible implementation, the conversion module includes:

[0092] A judgment module, used to judge whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform;

[0093] A deployment module is used to deploy the cloud platform according to the deployment mode corresponding to the connection type.

[0094] In a feasible implementation manner, the conversion module further includes:

[0095] An access module, configured to configure the layer 2 bridge switch and the cloud edge switch connected to the cloud platform based on the deployment mode, and obtain configuration results;

[0096] The first configuration module is used to configure the operation and maintenance interface of the cloud platform based on the configuration result to complete the configuration of the cloud platform.

[0097] In a feasible implementation manner, the conversion module further includes:

[0098] A connection module, used for controlling the off-cloud aggregation switch to connect with the hardware load balancing device if no;

[0099] The interconnection module is used to configure the cloud edge switch connected to the hardware load balancing device, and interconnect the configured cloud edge switch with the cloud external aggregation switch.

[0100] In a feasible implementation manner, the conversion module further includes:

[0101] A creation module, used to create a plurality of corresponding sub-interfaces on the cloud edge switch based on the intra-cloud IP in the cloud platform;

[0102] The second configuration module is used to configure the VRF corresponding to the sub-interface on the cloud-outside aggregation switch to complete the interconnection between the cloud edge switch and the cloud-outside aggregation switch.

[0103] In a feasible implementation manner, the forwarding module includes:

[0104] A determination module, used for the hardware load balancing device to determine a routing mode between the hardware load balancing device and the core switch in the cloud based on the target deployment mode;

[0105] The first sending module is used for the hardware load balancing device to send the balancing result to the core switch in the cloud based on the routing mode.

[0106] In a feasible implementation, the calling module includes:

[0107] A generating module, configured for the plurality of computing nodes to execute corresponding network services based on the balancing result and generate network service results, and to send the network service results to the service access switch;

[0108] The communication module is used for the service access switch to send the network service result to the external network through a preset communication method.

[0109] Example 3

[0110] The present application also provides an electronic device, such as Figure 6As shown, it includes: a processor 601, a memory 602 and a bus 603, the memory 602 stores machine-readable instructions executable by the processor 601, when the electronic device is running, the processor 601 communicates with the memory 602 through the bus 603, and when the machine-readable instructions are executed by the processor 601, any step of the cloud-based load balancing method is performed.

[0111] Example 4

[0112] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program executes any one of the steps of the cloud-based load balancing method.

[0113] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0114] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0115] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0116] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a platform server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0117] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A cloud-based load balancing method, characterized in that: Applicable to a cloud platform, the cloud platform includes a cloud edge switch, a cloud core switch, a service access switch, a computing node, a layer 2 bridge switch, an off-cloud aggregation switch, and a hardware load balancing device, the method includes: Determine and adopt the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information; The hardware load balancing device receives an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud; The hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP; The service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes respectively provide corresponding network services to the external network based on the balancing result.

2. The method according to claim 1, characterized in that: The determining and adopting of the target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform includes: Determining whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform; If so, the cloud platform is deployed according to the deployment mode corresponding to the connection type.

3. The method according to claim 2, characterized in that If so, deploying the cloud platform according to the deployment mode corresponding to the connection type includes: Based on the deployment mode, the layer 2 bridge switch and the cloud edge switch connected to the cloud platform are configured respectively to obtain configuration results; Based on the configuration result, the operation and maintenance interface of the cloud platform is configured to complete the configuration of the cloud platform.

4. The method according to claim 2, characterized in that: The determining whether the layer 2 bridge switch supports access to the cloud platform based on the connection type of the cloud platform further includes: If not, controlling the off-cloud aggregation switch to connect to the hardware load balancing device; Configure a cloud border switch connected to the hardware load balancing device, and interconnect the configured cloud border switch with the cloud-outside aggregation switch.

5. The method according to claim 4, characterized in that The configuring a cloud border switch connected to the hardware load balancing device, and interconnecting the configured cloud border switch with the cloud external aggregation switch, includes: Creating a plurality of corresponding sub-interfaces on the cloud edge switch based on the intra-cloud IP in the cloud platform; A VRF corresponding to the sub-interface is configured on the off-cloud aggregation switch to complete the interconnection between the cloud edge switch and the off-cloud aggregation switch.

6. The method according to claim 1, characterized in that The hardware load balancing device sends the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP, including: The hardware load balancing device determines a routing mode between the hardware load balancing device and the core switch in the cloud based on the target deployment mode; The hardware load balancing device sends the balancing result to the core switch in the cloud based on the routing mode.

7. The method according to claim 1, characterized in that The service access switch calls multiple computing nodes based on the balancing result, so that the multiple computing nodes respectively provide corresponding network services to the external network based on the balancing result, including: The multiple computing nodes execute corresponding network services based on the balancing results and generate network service results, and send the network service results to the service access switch; The service access switch sends the network service result to the external network through a preset communication method.

8. A cloud-based traffic control and load balancing device, characterized in that: The device comprises: An adoption module is used to determine and adopt a target deployment mode between the cloud edge switch, the cloud core switch, the layer 2 bridge switch, the cloud aggregation switch and the hardware load balancing device based on the connection type of the cloud platform; different connection types correspond to different deployment modes; different deployment modes have different configuration information; A sending module, used for the hardware load balancing device to receive an external network request sent by an external network through the target deployment mode, so that the hardware load balancing device balances the external network request to obtain a balanced result; the external network request includes an IP in the cloud; A forwarding module, configured for the hardware load balancing device to send the balancing result to the cloud core switch based on the routing mode corresponding to the target deployment mode, so that the cloud core switch forwards the balancing result to the service access switch based on the cloud IP; The calling module is used for the service access switch to call multiple computing nodes based on the balancing result, so that the multiple computing nodes provide corresponding network services for the external network based on the balancing result.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of a cloud-based load balancing method as described in any one of claims 1 to 7 are performed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the cloud-based load balancing method as described in any one of claims 1 to 7 are executed.

Images