Hybrid cloud capacity expansion method and device, equipment and storage medium

Abstract

The invention provides a hybrid cloud capacity expansion method and device, equipment and a storage medium. The method comprises the following steps: acquiring the current flow of accessing private cloud resources by a user within a preset time period, and acquiring expandable resources of the private cloud when the current flow exceeds a preset flow threshold value; judging whether the private cloud can support the access of target traffic according to the expandable resources, wherein the target traffic is determined according to the current traffic and the preset traffic threshold; when the expandable resources cannot support the access of the target traffic, screening at least one public cloud according to the geographic position of the private cloud to obtain a target public cloud; and creating a service instance on the target public cloud, and registering the service instance in a load balancer, the load balancer being used for distributing the access of the target traffic to the service instance. According to the method provided by the invention, the cloud pool selection method during hybrid cloud capacity expansion is optimized.

Description

Technical Field

[0001] The present application relates to the field of computer cloud computing, and in particular to a hybrid cloud expansion method, apparatus, device, and storage medium. Background Art

[0002] With the continuous development of computer cloud technology, different cloud architecture models play a key role in daily applications. To this end, many enterprises have deployed dedicated private clouds to ensure data security during business deployment. Deploying private clouds can also meet the enterprise's data transmission requirements within provinces or cities. However, in certain scenarios, private clouds may face a surge in terminal access business traffic, resulting in the enterprise's existing deployment being unable to support the current access volume. The existing solution is to lease existing public clouds to expand resources and deploy some resources to the public cloud to ensure normal terminal access despite the surge in business traffic.

[0003] However, existing solutions fail to consider performance when selecting public clouds. Enterprise private cloud services are often regional, with relatively concentrated customer bases and, consequently, traffic sources. Randomly renting a public cloud can create a significant distance between the public cloud and the enterprise's private cloud, leading to poor access performance.

[0004] Therefore, there is an urgent need for a method to optimize the cloud pool selection method when expanding hybrid clouds. Summary of the Invention

[0005] The present application provides a hybrid cloud expansion method, apparatus, device and storage medium to solve the technical problem of an imperfect cloud pool selection method during hybrid cloud expansion.

[0006] In a first aspect, the present application provides a hybrid cloud capacity expansion method, comprising:

[0007] Obtaining current traffic of users accessing private cloud resources within a preset time period, and obtaining scalable resources of the private cloud when the current traffic exceeds a preset traffic threshold;

[0008] Determining, based on the scalable resources, whether the private cloud can support access by target traffic, where the target traffic is determined based on the current traffic and the preset traffic threshold;

[0009] When the scalable resources cannot support access to the target traffic, screening at least one public cloud based on the geographic location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographic area, or the target public cloud includes multiple public clouds, at least some of which belong to the same geographic area as the private cloud;

[0010] A service instance is created on the target public cloud, and the service instance is registered with a load balancer. The load balancer is used to distribute access to the target traffic to the service instance.

[0011] In one possible design, screening at least one public cloud based on the geographical location of the private cloud to obtain a target public cloud includes:

[0012] Obtaining a preset geographical range according to the geographical location of the private cloud;

[0013] Obtaining cloud pool information of public clouds within a preset geographical range, the cloud pool information including available resources and geographical locations corresponding to at least one public cloud;

[0014] At least one public cloud is screened according to the cloud pool information of the public cloud to obtain a target public cloud.

[0015] In one possible design, screening at least one public cloud based on the cloud pool information of the public cloud to obtain a target public cloud includes:

[0016] For each public cloud, obtaining a distance value between the public cloud and the private cloud according to the geographic location of the public cloud and the geographic location of the private cloud;

[0017] Sorting the distance values ​​in ascending order, and associating and storing the distance values ​​with the public clouds corresponding thereto;

[0018] Determine whether the available resources of the first-ranked public cloud can support access to the target traffic;

[0019] If yes, the first ranked public cloud is selected as the target public cloud;

[0020] If not, the target public cloud is determined based on the available resources and ranking order of other public clouds.

[0021] In one possible design, determining the target public cloud based on available resources and the order of arrangement of other public clouds includes:

[0022] Determine whether the available resources of the second-ranked public cloud can support access by the target traffic;

[0023] If yes, the second-ranked public cloud is selected as the target public cloud;

[0024] If not, repeat the process of determining whether the available resources of the public cloud ranked N can support the access of the target traffic;

[0025] If a public cloud that can support access to the target traffic is found before the preset ranking M, then the public cloud is used as the target public cloud;

[0026] If the target public cloud is not obtained after the preset sorting M is judged, multiple public clouds are obtained according to the arrangement order, and the multiple public clouds are used as the target shared cloud.

[0027] In one possible design, obtaining multiple public clouds according to the arrangement order and using the multiple public clouds as the target shared cloud includes:

[0028] According to the arrangement order, when the total available resources of the first N public clouds can support the access of the target traffic, the combination of the first N public clouds is used as the target public cloud, where N is a natural number not less than 1.

[0029] In one possible design, the preset geographical range is a range corresponding to the geographical area where the private cloud is located; if the total available resources of at least one public cloud within the geographical area cannot support access by the target traffic, the method further includes:

[0030] Acquire the missing resources according to the target flow and the sum of the available resources;

[0031] Acquire a target geographical range adjacent to the preset geographical range, and acquire a distance between each public cloud and the private cloud based on the geographical location of at least one public cloud and the geographical location of the private cloud within the target geographical range;

[0032] Obtaining one or more public clouds corresponding to the missing resources from the at least one public cloud in order of distance from nearest to farthest;

[0033] The target public cloud is acquired according to at least one public cloud within the geographical area and one or more public clouds corresponding to the scarce resources.

[0034] In one possible design, after creating the service instance on the target public cloud, the method further includes:

[0035] The preset traffic threshold is updated according to the sum of available resources of the private cloud and the target public cloud.

[0036] In one possible design, when the scalable resource can support access of the target traffic, the method further includes:

[0037] Expanding capacity within the private cloud to obtain expansion resources;

[0038] An expansion instance is created in the expansion resource, the expansion instance is registered with the load balancer, and the target traffic is transferred to the expansion instance.

[0039] In a second aspect, the present application provides a hybrid cloud capacity expansion device, comprising:

[0040] An acquisition module is used to acquire the current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, acquire scalable resources of the private cloud;

[0041] a screening module, configured to determine, based on the scalable resources, whether the private cloud can support access by target traffic, where the target traffic is determined based on the current traffic and the preset traffic threshold;

[0042] When the scalable resources cannot support access to the target traffic, screening at least one public cloud based on the geographic location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographic area, or the target public cloud includes multiple public clouds, at least some of which belong to the same geographic area as the private cloud;

[0043] The execution module is used to create a service instance on the target public cloud and register the service instance with a load balancer, wherein the load balancer is used to distribute the access of the target traffic to the service instance.

[0044] In a third aspect, the present application provides a hybrid cloud capacity expansion device, comprising: a processor, and a memory communicatively connected to the processor;

[0045] The memory stores computer-executable instructions;

[0046] The processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the hybrid cloud capacity expansion method described in the first aspect and various possible designs of the first aspect.

[0047] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, the hybrid cloud expansion method described in the first aspect and various possible designs of the first aspect is implemented.

[0048] The hybrid cloud expansion method, apparatus, device and storage medium provided in the present application obtain the current traffic of users accessing private cloud resources within a preset time period, and in combination with the preset traffic threshold of the private cloud, determine whether the scalable resources of the private cloud can support access with the current traffic. When the scalable resources cannot support access with the current traffic, at least one public cloud belonging to the same geographical area as the private cloud can be screened based on the geographical location of the private cloud, and at least one public cloud can be used as the target public cloud, thereby minimizing the geographical distance between the target public cloud and the private cloud, thereby reducing network latency and increasing data transmission speed, thereby ensuring the performance of the private cloud and the public cloud, optimizing the cloud pool selection method during hybrid cloud expansion, and improving the quality of expansion services. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0050] Figure 1 This is a system architecture diagram of an embodiment of the present application;

[0051] Figure 2 Hybrid cloud expansion method process provided in this application embodiment Figure 1 ;

[0052] Figure 3 Hybrid cloud expansion method process provided in this application embodiment Figure 2 ;

[0053] Figure 4 Hybrid cloud expansion method process provided in this application embodiment Figure 3 ;

[0054] Figure 5 Hybrid cloud expansion method process provided in this application embodiment Figure 4 ;

[0055] Figure 6 Schematic diagram of the structure of the hybrid cloud expansion device provided in the embodiment of the present application Figure 1 ;

[0056] Figure 7 A hardware diagram of the hybrid cloud expansion device provided in an embodiment of the present application.

[0057] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0058] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0059] In the existing technology, when faced with an explosion of terminal access business traffic, enterprises give priority to expanding capacity in their internal private clouds. When the private cloud's scalable resources are insufficient to support the access of business traffic, they will also rent an external public cloud to divert the business traffic to the external public cloud to achieve hybrid cloud expansion. Since the private cloud's scalable resources are limited and enterprises will invest more costs in operation and maintenance deployment, expanding capacity in the public cloud becomes a relatively good solution. However, the current expansion method does not consider performance issues when selecting a public cloud. The business of an enterprise's private cloud is often regional, and the customers are relatively concentrated, so the traffic source is also relatively concentrated. If a public cloud is rented arbitrarily, the distance between the public cloud and the enterprise's private cloud may be too far, which will lead to the problem of reduced access performance.

[0060] In order to optimize the cloud pool selection method during hybrid cloud expansion so that the distance between the public cloud and the private cloud is maintained within a certain range, thereby ensuring the performance of the public cloud, the present invention designs a hybrid cloud expansion method. When user traffic increases sharply and the scalable resources within the private cloud are insufficient to support user traffic, the method can obtain public clouds within a preset geographical range according to the geographical location of the private cloud, obtain the distance between each public cloud and the private cloud within the preset geographical range respectively, and sort the public clouds in order from small to large. The public cloud or a combination of multiple public clouds that can support user traffic and is closest to the private cloud is used as the target public cloud for expansion, so that the target public cloud and the private cloud are geographically kept at the shortest distance, thereby ensuring the performance of the private cloud and the public cloud and improving the quality of expansion services.

[0061] Figure 1 This is the system architecture diagram of the embodiment of the present application, combined with Figure 1 This paper introduces the system architecture of this application. Figure 1As shown, the system of the present application includes a hybrid cloud expansion system 101 and a terminal 102. The hybrid cloud expansion system 101 of the present application includes a gateway, a monitoring module and an expansion module. When the terminal 102 accesses the service, the monitoring module in the hybrid cloud expansion system 101 can record the traffic situation and resource usage in a unit time, and the monitoring module can feed back the real-time traffic situation and resource usage to the gateway. When the monitoring module detects that the user traffic surges at a certain moment, the monitoring module can control the gateway to execute the flow limiting strategy, and can trigger the expansion capability, so that the expansion module creates a new instance to handle the burst traffic. When expanding, the expansion module first determines whether there are available expansion resources in the private cloud. If the available expansion resources of the private cloud can support the access of user traffic, an expansion instance is created within the private cloud. If the available expansion resources of the private cloud cannot support the access of user traffic, expansion is performed in a public cloud that meets the preset conditions so that the private cloud and the public cloud remain geographically close. And after the expansion module is expanded, the monitoring module can update the traffic threshold of the monitoring module according to the total available resources of the private cloud and the public cloud.

[0062] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0063] Figure 2 Hybrid cloud expansion method process provided in this application embodiment Figure 1 .like Figure 2 As shown, the execution subject of this embodiment can be the above Figure 1 In the hybrid cloud capacity expansion system 101 of the embodiment, the method includes:

[0064] S201. Obtain current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, obtain scalable resources of the private cloud.

[0065] Specifically, private cloud resources can refer to various computing, storage, and network resources deployed within a private cloud, such as virtual machines, databases, applications, and storage systems. These resources can be combined to form a private cloud environment, and user access and usage generate corresponding traffic. Furthermore, current traffic can be the amount of data transmitted by users to various resources within the private cloud environment within a preset time period. Scalable resources in a private cloud can be computing, storage, and network resources whose quantity or capacity can be dynamically expanded based on business needs and load conditions to meet the needs of business growth or traffic surges.

[0066] In one possible design, the preset time period can be one minute. The preset traffic threshold can be a data change threshold or a change rate threshold. Furthermore, in the case where the preset traffic threshold is a data change threshold, the hybrid cloud expansion system can monitor the data traffic within the preset time period, and when it is monitored that the data transmission rate per minute reaches 1Mbps, it can be determined that the current traffic exceeds the preset traffic threshold and obtain the available resources of the private cloud. In the case where the preset traffic threshold is a change rate threshold, the hybrid cloud expansion system can monitor the data traffic changes within the preset time period, and when it is monitored that the data traffic changes from linear growth to exponential growth, it can be determined that the current traffic exceeds the preset traffic threshold and obtain the available resources of the private cloud.

[0067] Alternatively, the preset traffic threshold can also be determined based on system resources. For example, system resources can be key resources such as memory and CPU. Specifically, when current traffic surges, data traffic within a preset time period will also surge, resulting in a significant increase in system resource usage and a decrease in available resources. When system resource usage reaches a preset ratio, it can be determined that the current traffic exceeds the preset traffic threshold. For example, the preset ratio can be 80%. In other words, whether the preset traffic threshold has been reached is determined based on the system resource usage ratio.

[0068] S202: Determine whether the private cloud can support access of target traffic based on scalable resources, where the target traffic is determined based on current traffic and a preset traffic threshold.

[0069] Specifically, the target traffic flow can be the difference between the current traffic flow and a preset traffic flow threshold. If the target traffic flow exceeds the scalable resources, the hybrid cloud expansion system determines that the private cloud cannot support access with the target traffic flow. If the target traffic flow is less than the scalable resources, the hybrid cloud expansion system determines that the private cloud can support access with the target traffic flow.

[0070] S203. When the scalable resources cannot support access to the target traffic, at least one public cloud is screened based on the geographical location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographical area, or the target public cloud includes multiple public clouds, and at least some of the public clouds belong to the same geographical area as the private cloud.

[0071] Specifically, the target public cloud can be a public cloud that meets the private cloud expansion requirements, or a combination of multiple target public clouds. The private cloud expansion requirement can be at least one public cloud in the same geographic region as the private cloud. Furthermore, the target public cloud can be in the same geographic region as the private cloud, or some of the target public clouds can be in the same geographic region as the private cloud.

[0072] In one possible design, when scalable resources cannot support target traffic, the hybrid cloud expansion system can first screen public clouds based on the private cloud's geographic location, and then perform performance screening on public clouds that meet the location criteria. Performance screening can include computing performance screening, storage performance screening, etc. Alternatively, the hybrid cloud expansion system can first perform performance screening on public clouds, and then perform location screening on public clouds that meet the performance criteria.

[0073] S204: Create a service instance on the target public cloud and register the service instance with a load balancer. The load balancer is used to distribute access to the target traffic to the service instance.

[0074] The hybrid cloud expansion method provided in this embodiment obtains the current traffic of users accessing private cloud resources within a preset time period, and combines it with the preset traffic threshold of the private cloud to determine whether the scalable resources of the private cloud can support the access of the current traffic. When the scalable resources cannot support the access of the current traffic, at least one public cloud belonging to the same geographical area as the private cloud can be screened according to the geographical location of the private cloud, and at least one public cloud is used as the target public cloud, thereby ensuring that the target public cloud and the private cloud are geographically spaced at the shortest distance, thereby reducing network latency and increasing data transmission speed, thereby ensuring the performance of the private cloud and the public cloud, optimizing the cloud pool selection method during hybrid cloud expansion, and improving the quality of expansion services.

[0075] Figure 3 Hybrid cloud expansion method process provided in this application embodiment Figure 2 In this embodiment, Figure 2 Based on the embodiment, when the scalable resources of the private cloud cannot support the access of the target traffic, the process of screening the public cloud is described in detail. Figure 3 As shown, the method includes:

[0076] S301: Obtain the current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, obtain scalable resources of the private cloud.

[0077] S302: Determine whether the private cloud can support access to the target traffic based on the scalable resources. The target traffic is determined based on the current traffic and a preset traffic threshold. If the scalable resources can support access to the target traffic, the hybrid cloud expansion system can expand the private cloud to obtain expansion resources, create an expansion instance within the expansion resources, register the expansion instance with the load balancer, and transfer the target traffic to the expansion instance.

[0078] Steps S301-S302 and Figure 2 Steps S201-S202 in the embodiment are similar and are not described in detail in this embodiment.

[0079] S303: When the scalable resources cannot support the access of the target traffic, a preset geographical range is obtained according to the geographical location of the private cloud.

[0080] Specifically, to ensure network latency between the private cloud and the target public cloud and to meet the requirements of private cloud data security management, the preset geographical scope can be a provincial or municipal scope. For example, the preset geographical scope can be the province or city where the private cloud is located.

[0081] S304. Obtain cloud pool information for public clouds within a preset geographic range. The cloud pool information includes available resources and geographic locations corresponding to at least one public cloud. Specifically, the cloud pool information can be obtained through an application programming interface (API) provided by the provider. Available resources of the public cloud include available computing resources, storage resources, network resources, etc.

[0082] S305 . For each public cloud, obtain the distance value between the public cloud and the private cloud according to the geographical location of the public cloud and the geographical location of the private cloud.

[0083] In one possible design, the geographic location of the private cloud and each public cloud is determined by longitude and latitude. The Euclidean distance between the private cloud and each public cloud is calculated using a map and geolocation service. Geolocation services can be implemented through Google Maps, Baidu Maps, and other platforms. For example, based on the geographic location of the private cloud, the hybrid cloud expansion system can obtain four public clouds within a preset geographic range: Public Cloud A, Public Cloud B, Public Cloud C, and Public Cloud D. The distances between these four public clouds and the private cloud are calculated to be 70 kilometers, 50 kilometers, 30 kilometers, and 100 kilometers, respectively.

[0084] S306 , sorting the distance values ​​in ascending order, and associating and storing the distance values ​​and the corresponding public clouds.

[0085] For example, the distance values ​​are sorted in ascending order and the distance values ​​and their corresponding public clouds are associated and stored, resulting in the following arrangement results: public cloud C - 30 kilometers, public cloud B - 50 kilometers, public cloud A - 70 kilometers, public cloud D - 100 kilometers.

[0086] S307: Determine whether the available resources of the first-ranked public cloud can support the access of the target traffic. If so, execute S308; if not, execute S309.

[0087] S308: The public cloud ranked first is selected as the target public cloud.

[0088] S309: Determine whether the available resources of the second-ranked public cloud can support the access of the target traffic. If so, execute S310; if not, execute S311.

[0089] S310: The second-ranked public cloud is selected as the target public cloud.

[0090] S311. Determine the target public cloud based on the available resources and arrangement order of other public clouds.

[0091] In a specific implementation, the hybrid cloud expansion system sorts the distance values ​​in ascending order and associates and stores the distance values ​​with their corresponding public clouds. It then determines whether the available resources of the first-ranked public cloud can support the target traffic. If the available resources of the first-ranked public cloud can support the target traffic, the first-ranked public cloud is selected as the target public cloud. If the available resources of the first-ranked public cloud cannot support the target traffic, the system then determines whether the available resources of the second-ranked public cloud can support the target traffic. If the available resources of the second-ranked public cloud can support the target traffic, the second-ranked public cloud is selected as the target public cloud. If the available resources of the second-ranked public cloud cannot support the target traffic, the system then determines whether the available resources of the third-ranked and subsequent public clouds can support the target traffic. If any public cloud has available resources that can support the target traffic, that public cloud is selected as the target public cloud.

[0092] Furthermore, after determining the target public cloud based on the available resources and arrangement order of other public clouds, it also includes: creating a service instance on the target public cloud and registering the service instance with a load balancer, which is used to distribute access to the target traffic to the service instance.

[0093] Specifically, the required service instance is created on the target public cloud through the corresponding API, and a load balancer is configured on the target public cloud. The service instance is registered with the load balancer through the address or identifier of the service instance, so that the load balancer can distribute the access of the target traffic to the service instance of the target public cloud according to the load balancing strategy, so as to achieve the effect of traffic diversion.

[0094] The hybrid cloud expansion method provided in this embodiment obtains the public clouds within a preset geographical range through the geographical location of the private cloud, and then obtains the distance value between each public cloud and the private cloud, and sorts the distance values ​​in ascending order. It judges in order whether the available resources of the public clouds within the preset geographical range can support the target traffic according to the order of arrangement, which can minimize the distance between the target public cloud and the private cloud, thereby ensuring the performance between the target public cloud and the private cloud.

[0095] Figure 4 Hybrid cloud expansion method process provided in this application embodiment Figure 3 In this embodiment, Figure 3 Based on the embodiment, when the available resources of the second-ranked public cloud cannot support the access of the target traffic, the process of screening the public cloud is described in detail. Figure 4 As shown, the method includes:

[0096] S401: Obtain current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, obtain scalable resources of the private cloud.

[0097] S402: Determine whether the private cloud can support access of target traffic based on scalable resources, where the target traffic is determined based on current traffic and a preset traffic threshold.

[0098] S403: When the scalable resources cannot support the access of the target traffic, a preset geographical range is obtained according to the geographical location of the private cloud.

[0099] S404: Obtain cloud pool information of public clouds within a preset geographical range, where the cloud pool information includes available resources and geographical locations corresponding to at least one public cloud.

[0100] S405 . For each public cloud, obtain the distance value between the public cloud and the private cloud according to the geographical location of the public cloud and the geographical location of the private cloud.

[0101] S406 , sorting the distance values ​​in ascending order, and associating and storing the distance values ​​and the corresponding public clouds.

[0102] Steps S401-S406 and Figure 3 Steps S301 to S306 in the embodiment are similar and are not described in detail in this embodiment.

[0103] S407: When the available resources of the first-ranked and second-ranked public clouds cannot support the access of the target traffic, determine the target public cloud based on the available resources and ranking order of other public clouds.

[0104] S408: Repeat the process of determining whether the available resources of the public cloud ranked N can support the access of the target traffic.

[0105] In one possible design, to ensure latency between private and public clouds, the top N public clouds are selected by distance ranking and a determination is made as to whether any of these clouds has available resources capable of supporting the target traffic, where N can be a natural number greater than 1. For example, N = 3. This prioritized selection of a single public cloud reduces network latency uncertainty, avoids variations in network connection quality and transmission latency between different public clouds, and ensures more consistent and controllable latency. Furthermore, working with a single public cloud provider facilitates service integration and integrated management, avoiding significant disparities in services, APIs, and management tools offered by different public clouds and enabling better integrated management.

[0106] S409: If a public cloud that can support access of the target traffic is obtained before the preset ranking M, the public cloud is used as the target public cloud.

[0107] In one possible design, if the available resources of the top N public clouds cannot support the access of the target traffic, then the available resources of the top M public clouds are determined to be able to support the access of the target traffic, where M can be a natural number greater than 1 and not less than N. For example, M=5.

[0108] S410. If the target public cloud is not found after the preset sorting M is completed, the combination of the first N public clouds in the sorting order is used as the target public cloud when the total available resources of the first N public clouds can support the access of the target traffic, where N is a natural number not less than 1.

[0109] During the specific implementation process, if the hybrid cloud expansion system determines that none of the top M public clouds can support the target traffic, it will perform a combined judgment. The top N public clouds will be combined to determine whether the combined public cloud can support the target traffic.

[0110] For example, if the hybrid cloud expansion system determines that none of the first five public clouds can support the access of the target traffic individually, it will determine in order of arrangement whether the sum of the available resources of the first three public clouds can support the access of the target traffic. When the sum of the available resources of the first three public clouds can support the access of the target traffic, the combination of the first three public clouds will be used as the target public cloud.

[0111] The hybrid cloud expansion method provided in this embodiment can reduce the uncertainty of network latency by giving priority to selecting a single public cloud for expansion, avoiding differences in network connection quality and transmission latency between different public clouds. Selecting a single public cloud can make latency more consistent and controllable. In addition, cooperation with a single public cloud provider can better achieve service integration and integrated management, avoiding the problem of large differences in services, APIs, and management tools provided by different public clouds, and enabling better integrated management. In addition, when a single public cloud cannot support access to the target traffic, the top N public clouds closest to the private cloud can be combined, and the total available resources of the top N public clouds can be used to support access to the target traffic, thereby ensuring the performance between the public cloud and the private cloud during hybrid cloud expansion.

[0112] Figure 5 Hybrid cloud expansion method process provided in this application embodiment Figure 4 In this embodiment, Figure 4 Based on the embodiment, when the scalable resources of the private cloud cannot support the access of the target traffic, and the total available resources of at least one public cloud within the geographical area of ​​the private cloud cannot support the access of the target traffic, the process of obtaining the public cloud is described in detail. Figure 5 As shown, the method includes:

[0113] S501: Obtain the current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, obtain scalable resources of the private cloud.

[0114] S502: Determine whether the private cloud can support access of target traffic based on scalable resources, where the target traffic is determined based on current traffic and a preset traffic threshold.

[0115] S503. When the scalable resources cannot support the access of the target traffic, and the total available resources of at least one public cloud within the private cloud geographical area cannot support the access of the target traffic, obtain the missing resources based on the target traffic and the total available resources.

[0116] Specifically, the resource deficit is the difference between the target traffic and the total available resources. If the public clouds within the preset range determined by the private cloud's geographic location are unable to support the target traffic, the deficit resources need to be diverted to the adjacent public clouds within the preset range to support the sudden surge in user traffic.

[0117] S504: Obtain a target geographical range adjacent to the preset geographical range, and obtain a distance between each public cloud and the private cloud based on the geographical location of at least one public cloud and the geographical location of the private cloud within the target geographical range.

[0118] S505 . Obtain one or more public clouds corresponding to the missing resources from at least one public cloud in order of distance from near to far.

[0119] S506: Acquire a target public cloud based on at least one public cloud within the geographical area and one or more public clouds corresponding to the scarce resources.

[0120] Steps S504-S506 and Figure 4 Steps S403 to S410 in the embodiment are similar and are not described in detail in this embodiment.

[0121] S507: Update the preset traffic threshold according to the total available resources of the private cloud and the target public cloud.

[0122] The hybrid cloud expansion method provided in this embodiment obtains a target geographical range and missing resources adjacent to a preset geographical range. When the scalable resources of the public cloud within the preset geographical range cannot support the access of the target traffic, and when the total available resources of at least one public cloud within the private cloud geographical area cannot support the access of the target traffic, the target public cloud can be obtained through at least one public cloud within the target geographical range and one or more public clouds corresponding to the missing resources, thereby ensuring the stability of the hybrid cloud during expansion.

[0123] Figure 6 Schematic diagram of the structure of the hybrid cloud expansion device provided in the embodiment of the present application Figure 1 .like Figure 6 As shown, the hybrid cloud capacity expansion device 60 includes: an acquisition module 601, a screening module 602, and an execution module 603.

[0124] The acquisition module 601 is used to acquire the current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, acquire the scalable resources of the private cloud.

[0125] A screening module 602 is used to determine whether the private cloud can support access to the target traffic based on scalable resources, where the target traffic is determined based on the current traffic and a preset traffic threshold. When the scalable resources cannot support access to the target traffic, at least one public cloud is screened based on the geographic location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographic area, or the target public cloud includes multiple public clouds, at least some of which belong to the same geographic area as the private cloud.

[0126] The execution module 603 is used to create a service instance on the target public cloud and register the service instance with the load balancer. The load balancer is used to distribute the access of the target traffic to the service instance.

[0127] In one possible design, the acquisition module 601 is further configured to:

[0128] Get the preset geographical range based on the geographical location of the private cloud;

[0129] Obtaining cloud pool information of public clouds within a preset geographical range, the cloud pool information including available resources and geographical locations corresponding to at least one public cloud;

[0130] At least one public cloud is screened according to the cloud pool information of the public cloud to obtain a target public cloud.

[0131] In one possible design, the screening module 602 is further configured to:

[0132] For each public cloud, obtain the distance between the public cloud and the private cloud based on the geographic location of the public cloud and the geographic location of the private cloud;

[0133] Sort the distance values ​​in ascending order, and associate the distance values ​​with their corresponding public clouds for storage;

[0134] Determine whether the available resources of the first-ranked public cloud can support the access of the target traffic;

[0135] If yes, the first ranked public cloud is selected as the target public cloud;

[0136] If not, the target public cloud is determined based on the available resources and ranking order of other public clouds.

[0137] In one possible design, the screening module 602 is further configured to:

[0138] Determine whether the available resources of the second-ranked public cloud can support the access of the target traffic;

[0139] If yes, the second-ranked public cloud is selected as the target public cloud;

[0140] If not, repeat the process to determine whether the available resources of the Nth ranked public cloud can support the access of the target traffic;

[0141] If a public cloud that can support the target traffic is found before the preset ranking M, then the public cloud is used as the target public cloud;

[0142] If the target public cloud is not obtained after the preset sorting M is judged, multiple public clouds are obtained according to the sorting order and are used as the target shared cloud.

[0143] In one possible design, the screening module 602 is further configured to:

[0144] In order of arrangement, when the total available resources of the top N public clouds can support the access of the target traffic, the combination of the top N public clouds is used as the target public cloud, where N is a natural number not less than 1.

[0145] In one possible design, the screening module 602 is further configured to:

[0146] Obtain the missing resources based on the target flow and the sum of available resources;

[0147] Obtain a target geographical range adjacent to the preset geographical range, and obtain the distance between each public cloud and the private cloud based on the geographical location of at least one public cloud and the geographical location of the private cloud within the target geographical range;

[0148] Obtain one or more public clouds corresponding to the missing resources from at least one public cloud in descending order of distance;

[0149] A target public cloud is acquired based on at least one public cloud within a geographical area and one or more public clouds corresponding to the scarce resources.

[0150] In one possible design, the execution module 603 is further configured to:

[0151] Update the preset traffic threshold based on the total available resources of the private cloud and the target public cloud.

[0152] In one possible design, the execution module 603 is further configured to:

[0153] When the scalable resources can support the access of the target traffic, expand the capacity within the private cloud to obtain the scalable resources;

[0154] Create a scaling instance in the scaling resource, register the scaling instance with the load balancer, and transfer the target traffic to the scaling instance.

[0155] Figure 7 This is a hardware diagram of the hybrid cloud expansion device provided in the embodiment of the present application. Figure 7 As shown, the hybrid cloud expansion device 70 provided in this embodiment includes: at least one processor 701 and a memory 702. The device 70 also includes a communication component 703. The processor 701, the memory 702, and the communication component 703 are connected via a bus 704.

[0156] During the specific implementation process, at least one processor 701 executes the computer-executable instructions stored in the memory 702, so that the at least one processor 701 executes the above hybrid cloud expansion method.

[0157] The specific implementation process of the processor 701 can be found in the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here in this embodiment.

[0158] The present application also provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor, the memory storing computer-executable instructions, and the processor executing the computer-executable instructions stored in the memory to implement the above-mentioned hybrid cloud expansion method.

[0159] The present application also provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, the above-mentioned hybrid cloud expansion method is implemented.

[0160] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. The computer-readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0161] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0162] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0163] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0164] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0165] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0166] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0167] In the above embodiments, the description of each embodiment has its own focus. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0168] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0169] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A hybrid cloud expansion method, characterized in that: The method comprises: Obtaining current traffic of users accessing private cloud resources within a preset time period, and obtaining scalable resources of the private cloud when the current traffic exceeds a preset traffic threshold; Determining, based on the scalable resources, whether the private cloud can support access by target traffic, where the target traffic is determined based on the current traffic and the preset traffic threshold; When the scalable resources cannot support access to the target traffic, screening at least one public cloud based on the geographic location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographic area, or the target public cloud includes multiple public clouds, at least some of which belong to the same geographic area as the private cloud; A service instance is created on the target public cloud, and the service instance is registered with a load balancer. The load balancer is used to distribute access to the target traffic to the service instance.

2. The method according to claim 1, characterized in that The step of screening at least one public cloud according to the geographical location of the private cloud to obtain a target public cloud includes: Obtaining a preset geographical range according to the geographical location of the private cloud; Obtaining cloud pool information of public clouds within a preset geographical range, the cloud pool information including available resources and geographical locations corresponding to at least one public cloud; At least one public cloud is screened according to the cloud pool information of the public cloud to obtain a target public cloud.

3. The method according to claim 2, characterized in that The step of screening at least one public cloud according to the cloud pool information of the public cloud to obtain a target public cloud includes: For each public cloud, obtaining a distance value between the public cloud and the private cloud according to the geographic location of the public cloud and the geographic location of the private cloud; Sorting the distance values ​​in ascending order, and associating and storing the distance values ​​and the public clouds corresponding thereto; Determine whether the available resources of the first-ranked public cloud can support access to the target traffic; If yes, the first ranked public cloud is selected as the target public cloud; If not, the target public cloud is determined based on the available resources and ranking order of other public clouds.

4. The method according to claim 3, characterized in that Determining the target public cloud based on the available resources and ranking order of other public clouds includes: Determine whether the available resources of the second-ranked public cloud can support access by the target traffic; If yes, the second-ranked public cloud is selected as the target public cloud; If not, repeat the process of determining whether the available resources of the public cloud ranked N can support the access of the target traffic; If a public cloud that can support access to the target traffic is found before the preset ranking M, then the public cloud is used as the target public cloud; If the target public cloud is not obtained after the preset sorting M is judged, multiple public clouds are obtained according to the arrangement order, and the multiple public clouds are used as the target shared cloud.

5. The method according to claim 4, characterized in that The acquiring of a plurality of public clouds according to the arrangement order and using the plurality of public clouds as the target shared cloud includes: According to the arrangement order, when the total available resources of the first N public clouds can support the access of the target traffic, the combination of the first N public clouds is used as the target public cloud, where N is a natural number not less than 1.

6. The method according to claim 5, characterized in that The preset geographical range is a range corresponding to the geographical area where the private cloud is located; if the total available resources of at least one public cloud within the geographical area cannot support access by the target traffic, the method further includes: Acquire the missing resources according to the target flow and the sum of the available resources; Acquire a target geographical range adjacent to the preset geographical range, and acquire a distance between each public cloud and the private cloud based on the geographical location of at least one public cloud and the geographical location of the private cloud within the target geographical range; Obtaining one or more public clouds corresponding to the missing resources from the at least one public cloud in order of distance from nearest to farthest; The target public cloud is acquired according to at least one public cloud within the geographical area and one or more public clouds corresponding to the scarce resources.

7. The method according to any one of claims 1 to 6, characterized in that After creating the service instance on the target public cloud, the method further includes: The preset traffic threshold is updated according to the sum of available resources of the private cloud and the target public cloud.

8. The method according to claim 1, characterized in that When the scalable resources can support access of the target traffic, the method further includes: Expanding capacity within the private cloud to obtain expansion resources; An expansion instance is created in the expansion resource, the expansion instance is registered with the load balancer, and the target traffic is transferred to the expansion instance.

9. A hybrid cloud expansion device, characterized in that: include: An acquisition module is used to acquire the current traffic of users accessing private cloud resources within a preset time period, and when the current traffic exceeds a preset traffic threshold, acquire scalable resources of the private cloud; a screening module, configured to determine, based on the scalable resources, whether the private cloud can support access by target traffic, where the target traffic is determined based on the current traffic and the preset traffic threshold; When the scalable resources cannot support access to the target traffic, screening at least one public cloud based on the geographic location of the private cloud to obtain a target public cloud, wherein the private cloud and the target public cloud belong to the same geographic area, or the target public cloud includes multiple public clouds, at least some of which belong to the same geographic area as the private cloud; The execution module is used to create a service instance on the target public cloud and register the service instance with a load balancer, wherein the load balancer is used to distribute the access of the target traffic to the service instance.

10. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by a processor.

Images