Cloud computing technology-based elastic public IP configuration method and cloud management platform

Abstract

Embodiments of the present application relate to the technical field of cloud computing, and in particular to a cloud computing technology-based elastic public IP configuration method and a cloud management platform. The method is applied to the cloud management platform, and an infrastructure managed by the cloud management platform comprises a first access point, a second access point, a cloud resource and a monitoring node. The cloud management platform can bind a first elastic public IP of the first access point to the cloud resource, so that the first access point uses the first elastic public IP for public network access. The monitoring node can monitor the working state of the first access point, and when the monitoring node monitors that the first access point is in an abnormal working state, the cloud management platform can switch to bind a second elastic public IP of the second access point to the cloud resource, so that the first access point uses the second elastic public IP for public network access. The present application can improve the stability of cloud resources for public network access.

Description

Elastic public network IP configuration method and cloud management platform based on cloud computing technology

[0001] This application claims priority to Chinese patent application No. 202311865864.5 filed on December 29, 2023, with invention name “Cloud platform system and method for selecting a public IP address”, and No. 202410386798.1 filed on March 29, 2024, with invention name “Elastic public IP configuration method and cloud management platform based on cloud computing technology”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of cloud computing technology, and in particular to a method for configuring an elastic public network IP based on cloud computing technology and a cloud management platform. Background Art

[0003] With the development of cloud computing technology, the application of cloud resources is becoming more and more widespread. Cloud resources can include virtual machines, containers, bare metal servers, dedicated hosts, or any combination thereof. Currently, cloud resources can not only provide external services but also enable access to the public network.

[0004] Before a cloud resource is accessed over the public network, a public Internet Protocol (IP) address may be bound to the cloud resource, and the cloud resource may be accessed over the public network based on the bound public IP address.

[0005] However, when cloud resources are currently accessed through the public network based on public IP addresses, the public IP addresses may become unavailable. For example, if the access point providing the public IP address experiences a power outage or network disconnection, the cloud resources will become inaccessible through the public network. Summary of the Invention

[0006] The present application provides a method for configuring an elastic public IP address based on cloud computing technology and a cloud management platform. This method can avoid network interruptions when cloud resources are accessed over the public network and improve the stability of public network access. The corresponding technical solutions are as follows:

[0007] In a first aspect, a method for configuring an elastic public IP address based on cloud computing technology is provided. The method is used in a cloud management platform, and the cloud management platform is used to manage infrastructure. The infrastructure includes a first data center located in a first availability zone, a second data center located in a second availability zone, and a third data center located in a third availability zone. The method includes:

[0008] The cloud management platform receives first access point information input by the tenant, where the first access point information indicates the first access point of the first elastic public IP purchased by the tenant, and the first access point is located in the first data center of the first availability zone. The cloud management platform also receives first cloud resource information input by the tenant, where the first cloud resource information indicates the first cloud resource bound to the first elastic public IP and the second availability zone where the first cloud resource is located, and the first cloud resource is located in the second data center of the second availability zone. The cloud management platform establishes a first communication channel between the first data center and the second data center, where the first communication channel is used to transmit packets sent from the infrastructure's external network to the first access point with a destination address of the first elastic public IP from the first data center to the first cloud resource in the second data center, and / or to transmit packets generated by the first cloud resource with a destination address belonging to the external network from the second data center to the first access point of the first data center and then to the external network via the first access point.

[0009] The cloud management platform receives monitoring information input by the tenant regarding the first access point, wherein the monitoring information carries the first elastic public IP address. The cloud management platform deploys a monitoring node in the first availability zone or in an adjacent availability zone of the first availability zone, the monitoring node being configured to regularly monitor the operating status of the first access point and provide feedback to the cloud management platform regarding the operating status. The cloud management platform notifies the tenant of the operating status; and / or, if the operating status is abnormal, the cloud management platform establishes a second communication channel between a third data center and a second data center, wherein the third data center includes a second access point with a second elastic public IP address purchased by the tenant, the second communication channel being configured to transmit packets sent via an external network to the second access point in the third data center with a destination address of the second elastic public IP address from the third data center to the first cloud resource in the second data center, and / or transmit packets generated by the first cloud resource with a destination address of the external network from the second data center to the second access point in the third data center and then transmit them to the external network via the second access point.

[0010] In the solution described in this application, the cloud management platform binds a first elastic public IP to a first cloud resource according to the user's instructions, so that the first cloud resource can use the first elastic public IP for public network access. When the first cloud resource uses the first elastic public IP for public network access, the cloud management platform can also set a monitoring node for the first access point corresponding to the first elastic public IP to regularly detect the working status of the first access point. When the cloud management platform determines that the first access point is in an abnormal working state, it can switch the first cloud resource bound to the first elastic public IP to a second elastic public IP corresponding to a second access point in normal working state. In this way, when the first cloud resource uses the first elastic public IP for public network access, if the first access point goes from a normal working state to an abnormal working state, the cloud management platform can switch the binding of the first cloud resource to the second elastic public IP corresponding to the second access point in normal working state. This allows the first cloud resource to always be bound to a connected and available elastic public IP without network interruption, thereby improving the stability of the first cloud resource's public network access.

[0011] In one practicable manner, the monitoring node is further configured to periodically monitor the working status of the second access point. The cloud management platform establishes a second communication channel between the third data center and the second data center when the working status is an abnormal working state, including: when the working status of the first access point is an abnormal working state and the working status of the second access point is a normal working state, the cloud management platform unbinds the first elastic public IP address from the first cloud resource, binds the second elastic public IP address to the first cloud resource, and establishes the second communication channel between the third data center and the second data center.

[0012] In the solution described in this application, in addition to monitoring the operating status of the first access point bound to the first cloud resource, the monitoring node can also monitor the operating status of a second access point allocated to the first cloud resource but not bound to the first cloud resource. This allows the cloud management platform to quickly identify the second access point in working order after determining that the first access point is in an abnormal operating state, and to bind a second elastic public IP address to the first cloud resource. This avoids rebinding an access point in an abnormal operating state to the first cloud resource, thereby improving the stability of public network access for the first cloud resource.

[0013] In one feasible manner, there are multiple monitoring nodes, and the cloud management platform establishes a second communication channel between the third data center and the second data center when the working state is an abnormal working state, including: when the cloud management platform determines that the number of monitoring nodes that monitor the first access point as being in an abnormal working state accounts for more than a proportion threshold in the total number of monitoring nodes, establishing the second communication channel between the third data center and the second data center.

[0014] In the solution described in this application, the cloud management platform can set up multiple monitoring nodes to monitor the working status of the access points allocated for cloud resources. The multiple monitoring nodes can be located in areas that are not connected to the access points, thereby improving the accuracy of detecting the working status of the access points.

[0015] In one possible implementation, the monitoring information also includes a percentage threshold and the availability zone where each monitoring node is located. This allows tenants to configure their own monitoring strategies for access points, increasing flexibility in detecting access point operating status.

[0016] In one practicable embodiment, the method further includes: the cloud management platform receiving monitoring data from a monitoring node regarding the operating status of the first access point, the monitoring data including a packet loss rate and a latency. If the packet loss rate corresponding to the first access point is greater than a packet loss rate threshold or the latency corresponding to the first access point is less than a latency threshold, determining that the operating status of the first access point is an abnormal operating state.

[0017] In one practicable embodiment, the method further includes: when the operating status of the first access point is abnormal, the cloud management platform sends an alarm message to a cloud management terminal corresponding to the cloud management platform, wherein the alarm message carries an access point identifier corresponding to the first access point. In this way, a technician can quickly identify the abnormal operating status of the first access point, thereby improving the efficiency of fault analysis and troubleshooting of the first access point.

[0018] In one practicable embodiment, the method further includes: when the operating status of the first access point is abnormal, the cloud management platform sending a stop monitoring notification corresponding to the first access point to the monitoring node, wherein the stop monitoring notification instructs the monitoring node to stop periodically monitoring the operating status of the first access point. Thus, when the first access point is in an abnormal operating state, stopping monitoring of the operating status of the first access point can avoid ineffective monitoring of the first access point.

[0019] In a second aspect, a cloud management platform is provided. The cloud management platform is used to manage infrastructure, where the infrastructure includes a first data center located in a first availability zone, a second data center located in a second availability zone, and a third data center located in a third availability zone. The cloud management platform includes:

[0020] A receiving module is configured to receive first access point information input by a tenant, wherein the first access point information is used to indicate a first access point of a first elastic public IP purchased by the tenant, and the first access point is located in a first data center in a first availability zone; and receive first cloud resource information input by the tenant, wherein the first cloud resource information is used to indicate a first cloud resource bound to the first elastic public IP and a second availability zone where the first cloud resource is located, wherein the first cloud resource is located in a second data center in the second availability zone.

[0021] a channel establishment module, configured to establish a first communication channel between the first data center and the second data center, wherein the first communication channel is configured to transmit a message with a destination address of a first elastic public IP address sent to the first access point through the external network of the infrastructure from the first data center to the first cloud resource in the second data center, and / or to transmit a message with a destination address belonging to the external network generated by the first cloud resource from the second data center to the first access point of the first data center and to send it to the external network via the first access point;

[0022] The receiving module is further configured to receive monitoring information input by the tenant for the first access point, wherein the monitoring information carries the first elastic public network IP;

[0023] A setting module is used to set a monitoring node in the first availability zone or an availability zone adjacent to the first availability zone, the monitoring node is used to regularly monitor the working status of the first access point and feed the working status back to the cloud management platform;

[0024] A processing module is used for the cloud management platform to notify tenants of the working status; and / or to establish a second communication channel between the third data center and the second data center when the working status is an abnormal working state, wherein the third data center includes a second access point with a second elastic public network IP purchased by the tenant, and the second communication channel is used to transmit a message with a destination address of the second elastic public network IP sent to the second access point in the third data center through an external network from the third data center to the first cloud resource in the second data center, and / or to transmit a message with a destination address of the external network generated by the first cloud resource from the second data center to the second access point in the third data center and send it to the external network via the second access point.

[0025] In one feasible manner, the monitoring node is further used to periodically monitor the working status of the second access point; the channel establishment module is used to: when the working status of the first access point is an abnormal working state and the working status of the second access point is a normal working state, unbind the first elastic public network IP from the first cloud resource, bind the second elastic public network IP to the first cloud resource, and establish a second communication channel between the third data center and the second data center.

[0026] In one practicable manner, there are multiple monitoring nodes, and the channel establishing module is configured to establish a second communication channel between the third data center and the second data center when it is determined that the proportion of the number of monitoring nodes that have monitored the first access point as being in an abnormal working state in the total number of monitoring nodes is greater than a proportion threshold.

[0027] In one achievable manner, the monitoring information also includes a percentage threshold and the availability zone where each monitoring node is located.

[0028] In one practicable manner, the cloud management platform further includes a determination module configured to: receive monitoring data from a monitoring node on the operating status of the first access point, the monitoring data including a packet loss rate and a delay; and determine that the operating status of the first access point is an abnormal operating status when the packet loss rate corresponding to the first access point is greater than a packet loss rate threshold or the delay corresponding to the first access point is less than a delay threshold.

[0029] In one feasible manner, the cloud management platform further includes an alarm module, which is used to: when the working status of the first access point is an abnormal working status, the cloud management platform sends an alarm message to the cloud management terminal corresponding to the cloud management platform, and the alarm message carries an access point identifier corresponding to the first access point.

[0030] A third aspect provides a public cloud system, including:

[0031] The first access point is located in the first data center of the first availability zone and is configured with a first elastic public IP address.

[0032] The first cloud resource is located in the second data center in the second availability zone.

[0033] The second access point is located in a third data center in a third availability zone and is configured with a second elastic public IP address. The first availability zone, the second availability zone, and the third availability zone are located in different regions.

[0034] The monitoring node is configured to monitor the working status of the first access point.

[0035] The backbone network is used to connect the first data center in the first availability zone with the second data center in the second availability zone, and after the monitoring node detects that the working status of the first access point is an abnormal working state, connect the first data center in the first availability zone with the third data center in the third availability zone.

[0036] The first access point is also used to receive a message with a destination address of the first elastic public IP sent through the external network of the infrastructure, and send the message to the first cloud resource of the second data center via the backbone network, and / or receive a message generated by the first cloud resource with a destination address belonging to the external network, and send it to the external network.

[0037] The second access point is further used to, after the monitoring node detects that the working status of the first access point is an abnormal working status, receive a message with a destination address of the first elastic public IP sent through the external network of the infrastructure, and send the message to the first cloud resource of the second data center via the backbone network, and / or receive a message generated by the first cloud resource with a destination address belonging to the external network and send it to the external network.

[0038] In a fourth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory;

[0039] The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method described in the first aspect and any implementable manner of the first aspect.

[0040] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed by a computing device, causes the computing device to execute the method described in the first aspect and any achievable manner of the first aspect.

[0041] In a sixth aspect, a computer-readable storage medium is provided, comprising computer program instructions. When the computer program instructions are executed by a computing device, the computing device executes the method described in the first aspect and any achievable method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] FIG1 is a schematic diagram of a data center distribution provided in an embodiment of the present application;

[0043] FIG2 is a schematic diagram of the structure of an elastic public IP configuration system provided in an embodiment of the present application;

[0044] FIG3 is a flow chart of a method for configuring an elastic public IP address provided in an embodiment of the present application;

[0045] FIG4 is a schematic diagram of an elastic public IP configuration interface provided in an embodiment of the present application;

[0046] FIG5 is a schematic diagram of an elastic public network access structure provided in an embodiment of the present application;

[0047] FIG6 is a schematic diagram of another elastic public network access structure provided in an embodiment of the present application;

[0048] FIG7 is a schematic diagram of another elastic public network access structure provided in an embodiment of the present application;

[0049] FIG8 is a schematic diagram of another elastic public network access structure provided in an embodiment of the present application;

[0050] FIG9 is a flow chart of a method for configuring an elastic public IP address provided in an embodiment of the present application;

[0051] FIG10 is a schematic diagram of an elastic public IP configuration interface provided in an embodiment of the present application;

[0052] 11 is a schematic diagram of a primary and backup IP solution for a GEIP binding virtual machine according to an embodiment of the present application;

[0053] 12 is a schematic diagram of a master-master IP solution for a GEIP binding gateway according to an embodiment of the present application;

[0054] FIG13 is a schematic diagram of a method for accessing a public network provided in an embodiment of the present application;

[0055] FIG14 is a schematic diagram of the structure of a cloud management platform device provided in an embodiment of the present application;

[0056] FIG15 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0057] FIG16 is a schematic diagram of a computing device cluster structure provided in an embodiment of the present application;

[0058] FIG17 is a schematic diagram of another computing device cluster structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0060] Elastic IP (EIP): Provides independent public IP resources, including public IP addresses and public network bandwidth. It can be bound to and unbound from cloud resources such as virtual machines, bare metal servers, virtual IP addresses, elastic load balancers, NAT gateways, containers, and dedicated hosts.

[0061] A Global Elastic IP (GEIP) is a global elastic public IP product. Compared to EIP, GEIP can be bound and unbound across regions to resources such as Elastic Cloud Servers, Bare Metal Servers, virtual IPs, Elastic Load Balancers, and NAT Gateways.

[0062] Access point: The location of the elastic public IP resource, corresponding to the cloud provider's point of presence (POP) or region. The access point is located in the cloud provider's data center.

[0063] Point of Presence (POP): In the field of cloud computing, a POP is located at the edge of the cloud network provided by the cloud vendor, allowing external access to the cloud network through the POP.

[0064] Cloud resources: Cloud resources include virtual machines, containers, bare metal servers, dedicated hosts, or any combination thereof.

[0065] [Corrected 21.01.2025 according to Rule 26] Region: The location of a data center. A region includes multiple regions. In one embodiment provided in this application, the regions include, for example, China and Asia Pacific.

[0066] Region: The location of a data center. Regions are typically divided based on geographic location and network latency, also known as regions. Public services such as elastic computing are shared within the same region. In one embodiment provided in this application, regions include, for example, North China, East China, North China-Beijing-1, and East China-Shanghai-1.

[0067] Availability Zone (AZ): The location of a data center. An AZ is a collection of one or more independent physical data centers within a region with sufficient power and network resources. Multiple AZs within a region are connected by high-speed fiber. In one embodiment provided herein, the AZs include, for example, AZ A in Beijing and AZ B in Beijing.

[0068] Backbone Network: A large-scale high-speed network used to connect multiple areas.

[0069] Cross-AZ network: A high-speed network used to connect multiple availability zones within the same region.

[0070] Cloud management platform and infrastructure: The cloud management platform is used to manage the cloud vendor's infrastructure. The infrastructure consists of multiple data centers located in different regions, where each region has at least one data center. The cloud management platform can provide interfaces related to cloud computing services, such as configuration pages or application program interfaces (APIs) for tenants to access cloud services. Tenants can log in to the cloud management platform using a pre-registered account and password, and after successful login, they can select and purchase cloud services provided by the data center in the predetermined region, such as object storage services, virtual machine services, container services, or other known cloud services.

[0071] Tenant: A top-level object used to manage cloud services and / or cloud resources. A tenant registers a tenant account and sets a tenant password on a cloud management platform through a local client (e.g., a browser). The local client remotely logs in to the cloud management platform using the tenant account and password. The cloud management platform provides a configuration interface or API for tenants to configure and use cloud services. As mentioned above, cloud services are specifically provided by the infrastructure managed by the cloud management platform.

[0072] Domain Name System (DNS): A service that converts domain names into IP addresses for computer connections, enabling end users to be routed to the appropriate resources. It is typically a database that maps domain names to IP addresses.

[0073] In existing elastic public network services, elastic public network resources are strongly correlated with regions. Most regions are located in first-tier cities, and elastic public network IP and bandwidth resources are relatively expensive. Relatively cheap resources in surrounding provincial capitals and second-tier cities cannot be connected to the region. The cost of purchasing public network resources is high, and tenant cloud resources cannot be flexibly deployed. Related technologies provide edge services for the above situations. Edge sites are built in non-first-tier cities to sink computing, storage, and network resources to the corresponding cities. However, this solution has high construction costs, long construction cycles, and poor cloud-edge intercommunication experience. It cannot meet the needs of some customers who do not need to sink computing and network resources, but only need low-cost bandwidth access at the edge.

[0074] The present application provides a method, device, and system for configuring elastic public IP addresses based on cloud computing technology. This method eliminates the need to restrict cloud resources and public network resources to the same region, enabling tenants to interconnect cloud resources with public network resources in any region of the cloud. This allows tenants to flexibly deploy their cloud resources based on their business needs, reducing the cost of using public network resources and enabling refined bandwidth operations, thus facilitating cost control for both tenants and cloud vendors.

[0075] To illustrate the distribution of data centers in an embodiment of the present application, please refer to Figure 1 below. Figure 1 is a data center distribution diagram provided in an embodiment of the present application. As shown in Figure 1, the diagram shows the geographical and regional distribution of data centers. The diagram includes region 11 and region 12, wherein region 11 includes area 111 and area 112, and region 12 includes area 121 and area 122, wherein area 111 includes data center 1110, data center 1111, data center 1112, and data center 1113, and the same applies to other regions. Among them, data center 1110 and data center 1210 are interconnected through a cross-regional communication channel 131, and the communication channel 131 is established via a cross-regional backbone network provided by the cloud vendor; data center 1110 and data center 1120 are interconnected through a communication channel 132 in the same region and across regions, and the communication channel 132 is established via a cross-regional backbone network provided by the cloud vendor; data center 1110 and data center 1111 are interconnected through a communication channel 133 in the same region, and the communication channel 133 is established via a cross-availability zone network provided by the cloud vendor, wherein data center 1111 and data center 1110 may be located in different availability zones in the same city, or in different availability zones in different cities, and this application does not limit this. It is worth noting that in other embodiments provided in this application, the number of regions, the number of regions in each region, and the number of data centers in each region are not limited to the numbers shown in the figure. For example, each region may include one or more regions, and this application does not limit this.

[0076] In the scenario where tenants use cloud resources provided by cloud vendors and bind elastic public network resources to cloud resources, relevant technologies require that the tenant's elastic public network resources and cloud resources must be located in the same region, and do not support the use of elastic public network IPs across regions for tenant cloud resources. In order to solve the above problems, the embodiments of the present application provide an elastic public network IP configuration method, device and system based on cloud computing technology. The method is applied to a cloud management platform, which is used to manage infrastructure. The cloud management platform establishes a communication channel for the data center where the tenant's cloud resources are located and the data center where the elastic public network resources are located via the backbone network through the cloud management platform, so that tenants can deploy cloud resources based on their business needs and deploy elastic public network resources provided by cloud vendors in any region for their cloud resources.

[0077] In order to illustrate the structure of the elastic public IP configuration system provided in the embodiment of the present application, please refer to Figure 2 below. Figure 2 shows a schematic diagram of the structure of an elastic public IP configuration system provided in the present application. Specifically, the figure is a refinement of the infrastructure including data center 1110, data center 1120, and data center 1210 in Figure 1. The elastic public IP configuration system structure is introduced below based on the schematic diagram of the elastic public IP configuration system structure in Figure 2 in combination with the data center distribution diagram in Figure 1. As shown in Figure 2, the infrastructure 1 includes a cloud management platform 10, and also includes a data center 1110 set in area 111...data center k, a data center 1210 set in area 121...data center m, and a data center 1120 set in area 112...data center n. Among them, data center 1110 is the elastic public network access point of the tenant, and public network resources provided by the cloud vendor are deployed on the server 11101 of data center 1110. The public network resources include elastic public IP and public network bandwidth. Data center 1210 located in area 121 has server 12101, on which virtual machine 12101 of tenant 40 is configured. Data center 1120 located in area 112 has server 11201, on which virtual machine 11201 of tenant 40 is configured. With reference to FIG1 , areas 111 and 112 are located in region 11, and area 121 is located in region 12. That is, in one solution shown in an embodiment of the present application, areas 111 and 121 are located in different regions, while areas 111 and 112 are located in the same region. That is, data center 1110 and data center 1210 are located in different regions, while data center 1110 and data center 1120 are located in different areas of the same region. Infrastructure 1 is provided with a cross-regional backbone network 13, which is used to connect cross-regional data centers in infrastructure 1. Exemplarily, cloud management platform 10 establishes a communication channel 131 between data center 1110 and data center 1210 for tenant 40 via cross-regional backbone network 13, and also establishes a communication channel 132 between data center 1110 and data center 1120 for tenant 40 via cross-regional backbone network 13. Tenant 40 can log in to cloud management platform 10 using tenant client 30 via the internet 20 using a tenant account and password, configure cloud resources including virtual machine 121011 and virtual machine 112011 on cloud management platform 10, set up elastic public network access points for cloud resources, and configure elastic public network IP addresses and public network bandwidth. It is worth noting that, for ease of explanation, the embodiment of the present application shows three areas and two communication channels in the infrastructure 1, but the embodiment of the present application is not limited to the solution including only three areas and two communication channels. For example, no communication channel may be established according to the needs of the tenant, or one or two or more communication channels may be established according to the needs of the tenant. The embodiment of the present application is not limited to this.

[0078] Based on the elastic public IP configuration scenarios described in Figures 1 and 2, the elastic public IP configuration method based on cloud computing technology provided in an embodiment of the present application is described in detail below in combination with Figure 3.

[0079] Please refer to FIG3 below, which is a flow chart of a method for configuring an elastic public network IP based on cloud computing technology provided by an embodiment of the present application. As shown in FIG3 , the method includes but is not limited to the following steps:

[0080] S101. Tenant 40 inputs access point information, cloud resource information, and bandwidth information.

[0081] For example, tenant 40 configures access point information, cloud resource information, and bandwidth information on an interface provided by cloud management platform 10 via tenant client 30 and Internet 20. An embodiment of how a tenant configures access point information, cloud resource information, and bandwidth information can be seen in Figure 4 , which is a schematic diagram of an elastic public IP configuration interface provided in an embodiment of the present application. As shown in FIG4 , the items available for tenant configuration on the elastic public network IP configuration interface include the access region, the region where the instance is located, the bound instance, the bandwidth type, the bandwidth name, the bandwidth size, and the elastic public network name. For example, the access region is North China-Beijing, and the instance region is East China-Shanghai. The bound instance, specifically, in this embodiment, is a virtual machine or an elastic cloud server. In other embodiments provided in this application, the bound instance includes, for example, a container, a bare metal server, a dedicated host, an elastic network card, or a load balancing device. The bandwidth type, specifically, in this embodiment, the data center 1210 where the tenant virtual machine 121011 is located and the data center 1110 where the access point is located are located in different regions of different regions. The bandwidth type is, for example, cross-region bandwidth. In other embodiments provided in this application, the bandwidth type may include cross-region bandwidth, regional bandwidth, regional bandwidth, and metropolitan bandwidth, which will be expanded in the following embodiments. The bandwidth size is, for example, 100 Mbit / s. The bandwidth name and elastic public network name are, for example, the names set by the tenant. It is worth noting that FIG4 is only one configuration interface provided in an embodiment of this application. In other embodiments provided in this application, the configurable items may include one or more of the above configuration items, and this application does not limit this.

[0082] [Corrected on 21.01.2025 according to Rule 26] Optionally, in one embodiment provided in the present application, the bandwidth type may include cross-region bandwidth, regional bandwidth, regional bandwidth, and metropolitan area bandwidth. Among them, cross-region bandwidth is the bandwidth type when the data center where the elastic public network resource and the tenant cloud resource are located is across regions. For example, the data center where the elastic public network resource is located is located in the China region, and the data center where the tenant cloud resource is located is located in the Asia-Pacific region. Regional bandwidth is the bandwidth type when the data center where the elastic public network resource and the tenant cloud resource are located is located in different regions of the same region. For example, the data center where the elastic public network resource is located is located in the East China region of the China region, and the data center where the tenant cloud resource is located is located in the North China region of the China region. Regional bandwidth is the bandwidth type when the data center where the elastic public network resource and the tenant cloud resource are located is located in different cities in the same region. For example, the data center where the elastic public network resource is located is located in Shanghai in the East China region, and the data center where the tenant cloud resource is located is located in Hangzhou in the East China region. Metropolitan bandwidth is the bandwidth type when the data center where the elastic public network resource and the tenant cloud resource are located is in the same region and the same city. For example, the data center where the elastic public network resource is located is located in Shanghai Availability Zone A in the East China region, and the data center where the tenant cloud resource is located is located in Shanghai Availability Zone B in the East China region. Optionally, in one embodiment provided in the present application, the cloud management platform 10 reminds the tenant 40 of the bandwidth type used when the tenant 40 configures elastic public network resources for its cloud resources.

[0083] By classifying bandwidth into different types, tenants can choose the bandwidth type based on their business needs when configuring bandwidth using elastic public network services, making the backbone network and cross-availability zone network bandwidth operations between tenants and cloud vendors more refined and facilitating cost control.

[0084] S102. Tenant 40 sends access point information, cloud resource information, and bandwidth information.

[0085] For example, the tenant 40 logs into the cloud management platform 10 via the Internet 20 through the tenant client 30 and inputs access point information, cloud resource information, and bandwidth information, which are sent to the cloud management platform 10 via the Internet 20 .

[0086] S103. The cloud management platform 10 receives access point information, cloud resource information, and bandwidth information.

[0087] For example, the cloud management platform 10 receives the access point information, cloud resource information, and bandwidth information input by the tenant 40 in the tenant client 30 in steps S101 and S102 via the Internet 20. In one embodiment provided in the present application, in conjunction with FIG4 , the above-mentioned content that can be set by the tenant 40 is obtained by an interface in the cloud management platform 10, for example, by the elastic public network information configuration interface of the cloud management platform 10, and the interface is, for example, an application programming interface (API) or an API-based configuration interface, or other interactive interface that can interact with the tenant, which is not limited in the present embodiment.

[0088] S104. The cloud management platform 10 establishes a communication channel 131 between the data center 1110 and the data center 1210, allocates elastic public IP addresses for cloud resources, and sets bandwidth.

[0089] For example, the cloud management platform 10 determines the data center 1110 where the access point is located and the data center 1210 where the cloud resources are located based on the access point information and cloud resource information input by the tenant 40 in step S101, establishes a communication channel 13 between the data center 1110 and the data center 1210 via the backbone network 13, allocates the elastic public IP resource in the data center 1110 to the virtual machine 121011 in the data center 1210 based on the access point information and cloud resource information input by the tenant 40 in step S101, and sets the bandwidth for the communication channel 13 based on the bandwidth information input by the tenant 40 in step S101.

[0090] S105. The user client 50 sends a message.

[0091] For example, user 60 sends a message through user client 50, and the destination address of the message is the elastic public IP address of tenant 40 virtual machine 121011.

[0092] S106 . The data center 1110 receives the message and sends the message to the data center 1210 through the communication channel 131 .

[0093] For example, the message from user 60 is sent to data center 1110 located in area 111 via Internet 20. Data center 1110 receives the message and resolves the correspondence between the elastic public IP and virtual machine 121011 located in data center 1210, and sends the message to data center 1210 via communication channel 131.

[0094] S107. Virtual machine 121011 in data center 1210 receives the message.

[0095] For example, the message is transmitted from the data center 1110 to the data center 1210 via the communication channel 131, and is transmitted to the virtual machine 121011 of the tenant 40 via the gateway, and the virtual machine 121011 receives the message.

[0096] S108. Tenant 40 inputs the unbinding information.

[0097] For example, the tenant 40 inputs the unbinding information on the interface provided by the cloud management platform 10 via the Internet 20 through the tenant client 30. In an embodiment provided in the present application, the unbinding information input by the tenant includes cloud resource information.

[0098] S109. Tenant 40 sends an unbinding message.

[0099] For example, the tenant 40 logs in to the cloud management platform 10 via the Internet 20 through the tenant client 30 and inputs the unbinding information which is sent to the cloud management platform 10 via the Internet 20 .

[0100] S110. The cloud management platform 10 receives the unbinding information.

[0101] For example, the cloud management platform 10 receives the unbinding information input by the tenant 40 in the tenant client 30 in steps S108 and S109 via the Internet 20. In one embodiment provided in the present application, the unbinding information content that can be set by the tenant 40 is obtained by an interface in the cloud management platform 10, for example, by an unbinding information configuration interface of the cloud management platform 10, and the interface is, for example, an application programming interface (API) or an API-based configuration interface, or other interactive interface that can interact with the tenant, which is not limited in the present embodiment.

[0102] S111. The cloud management platform 10 deletes the communication channel 131 and unbinds the elastic public IP, bandwidth, and virtual machine 121011.

[0103] For example, the cloud management platform 10 deletes the communication channel 13 between the data center 1110 and the data center 1210 established via the backbone network 13. The cloud management platform 10 notifies the corresponding gateway to delete the correspondence between the elastic public IP and the virtual machine 121011. The cloud management platform 10 deletes the correspondence between the elastic public IP and the virtual machine 121011 recorded by itself, and the cloud management platform 10 reclaims the bandwidth resources allocated to the virtual machine 121011.

[0104] Optionally, for steps S108 to S111, in another embodiment provided in the present application, the tenant 40 inputs the binding information of the virtual machine 112011 in the data center 1120 and the cloud resources located in the data center 1110. After receiving the binding information, the cloud management platform 10 automatically unbinds the virtual machine 121011 in the data center 1210 that has been bound to the elastic public IP of the data center 1110, and binds the cloud resource information newly input by the tenant 40, i.e., the virtual machine 112011 in the data center 1120, to the elastic public IP in the data center 1110.

[0105] In the above-mentioned elastic public IP configuration method embodiment, the data center 1110 where the elastic public network resources are located is located in area 111 of region 11, and the data center 1210 where the tenant 40 cloud resources, namely the virtual machine 121011, are located is located in area 121 of region 12. The two data centers are located in different areas of different regions, and the bandwidth set by the cloud management platform 10 for the communication channel established for the two data centers is, for example, a cross-region bandwidth.

[0106] Optionally, in another embodiment provided by the present application, the data center 1110 where the elastic public network resource is located is located in area 111 of the region 11, and the data center 1120 where another cloud resource of the tenant 40, namely the virtual machine 112011, is located is located in area 112 of the region 11, that is, the two data centers are located in different areas of the same region. For example, in this embodiment, in combination with the elastic public network IP configuration method of Figure 3, in step S101, the bandwidth type in the bandwidth information input by the tenant 40 can be the regional bandwidth, and in step S104, the cloud management platform 10 establishes a communication channel 132 between the data center 1110 and the data center 1120 via the cross-regional backbone network 13. The other steps in this embodiment can be obtained by analogy with the above embodiment and will not be repeated here.

[0107] Optionally, in another embodiment provided by the present application, the data center 1110 where the elastic public network resource is located is located in area 111 of region 11, and the tenant's other cloud resource is located in data center 1111, which is located in area 111 of region 11, that is, the two data centers are located in the same area of ​​the same region, and the two data centers are located in different cities. For example, in this embodiment, in combination with the elastic public network IP configuration method of Figure 3, in step S101, the bandwidth type in the bandwidth information input by the tenant 40 can be regional bandwidth, and in step S104, the cloud management platform 10 establishes a communication channel between data center 1110 and data center 1111 via a cross-availability zone network. The other steps in this embodiment can be obtained by analogy with the above embodiment and will not be repeated here.

[0108] Optionally, in another embodiment provided by the present application, the data center 1110 where the elastic public network resource is located is located in area 111 of region 11, and the tenant's other cloud resource is located in data center 1112, which is located in area 111 of region 11, that is, the two data centers are located in the same area of ​​the same region, and the two data centers are located in the same city. For example, in this embodiment, in combination with the elastic public network IP configuration method of Figure 3, in step S101, the bandwidth type in the bandwidth information input by the tenant 40 can be a metropolitan area bandwidth, and in step S104, the cloud management platform 10 establishes a communication channel between the data center 1110 and the data center 1112 via a cross-availability zone network. The other steps in this embodiment can be obtained by analogy with the above embodiment and will not be repeated here.

[0109] It is worth noting that cross-region bandwidth, regional bandwidth, regional bandwidth, and metropolitan area bandwidth are only names provided in the embodiments of this application, used to refer to various distribution situations of data centers where tenant cloud resources are located and data centers where elastic public network resources are located. In other embodiments provided in this application, other descriptions can be used as names of various distribution situations including these distribution situations, and the embodiments of this application do not limit this expression.

[0110] It is worth noting that in the relevant technologies, the expression "backbone network" is also used in a small number of cases to cover the two scenarios of "cross-regional backbone network" and "cross-availability zone network" in the embodiments of this application. Those skilled in the art should know that the difference in such expressions does not affect the various data center distribution scenarios involved in the above embodiments, and the embodiments of this application do not limit this expression.

[0111] Figure 5 shows a schematic diagram of an elastic public network access structure provided by an embodiment of the present application. As shown in Figure 5, in an embodiment provided by the present application, the tenant deploys its cloud resources in a data center in a domestic area, and sets a public network access point for its cloud resources in an overseas area. Thus, overseas terminal users served by the tenant can access the elastic public network nearby overseas, and use the cloud vendor's cross-border backbone network to access domestic cloud resources, thereby realizing low-latency access of the tenant's overseas terminal users to the tenant's cloud resources. For example, tenant 40 deploys its cloud resources 52011 in the data center 5201 in the domestic area 520. Tenant 40 binds its cloud resources to the elastic public IP resources in the data center 5101 located in the overseas area 510. The cloud management platform 10 establishes a communication channel between the data center 5101 and the data center 5201 via the backbone network 13. The overseas user 501 is the user of the cloud resources 52011 of tenant 40. The overseas user 501 uses the overseas user client 501 to send a message to access the cloud resources 52011 via the Internet. The destination address of the message is the elastic public IP in the data center 5101. The message is first sent to the data center 5101. The communication channel between the data center 5101 and the data center 5201 transmits the message from the data center 5101 to the cloud resources in the data center 5201.

[0112] Please refer to Figure 6 below, which shows a schematic diagram of a DNS system provided in an embodiment of the present application in conjunction with an elastic public IP configuration. As shown in Figure 6, in an embodiment provided in the present application, the tenant deploys its cloud resources in the infrastructure and, based on business needs, deploys elastic public network access points for the cloud resources in multiple areas where cloud resource users are relatively concentrated, and configures an intelligent domain name resolution service (Domain Name System, DNS). When the end user wants to access the tenant's cloud resources, the DNS service returns the corresponding elastic public IP to the end user based on information such as the end user's region, thereby facilitating the end user's low-latency access to resources and providing the tenant with a highly reliable and low-cost public network access solution. For example, tenant 40 deploys cloud resource 60011 in data center 6001 in region 600. Tenant 40 sets an elastic public IP 61111 for its cloud resource 60011 at access point 611 in region 621, sets an elastic public IP 61211 for its cloud resource 60011 at access point 612 in region 622, and sets an elastic public IP 61311 for its cloud resource 60011 at access point 613 in region 623. The cloud management platform 10 establishes communication channels between data center 6111 and data center 6001, between data center 6121 and data center 6001, and between data center 6131 and data center 6001 via backbone network 13. When a user near region 621 wants to access cloud resource 60011, the user client 601 sends a message carrying the domain name of cloud resource 60011 via the Internet. The DNS system returns the elastic public IP address in region 621 to the user based on the region 621 of the user. 61111, and so on, the DNS system returns elastic public IP 61211 to users near area 622, and returns elastic public IP 61311 to users near area 623. In other embodiments provided in this application, the communication channels between data center 6111 and data center 6001, between data center 6121 and data center 6001, and between data center 6131 and data center 6001 can be established via a cross-region backbone network or via a cross-availability zone network, respectively. This embodiment does not limit this. In other embodiments provided in this application, the factors affecting the DNS service's return of elastic public IP policies to users include the end user region, and may also include other factors, such as the end user's operator, which is not limited in this embodiment. Optionally, the business instances or cloud resources referred to in the embodiments of this application include one or any combination of virtual machines, containers, bare metal servers, and dedicated hosts.

[0113] Please refer to Figure 7 below, which shows a schematic diagram of a public network access based on elastic public IP provided in an embodiment of the present application. In the embodiment of the present application, the public network can refer to an external network of the infrastructure, such as the Internet. As shown in Figure 7, in an embodiment provided by the present application, the tenant deploys its cloud resources in the infrastructure and, based on business needs, deploys elastic public network access points in multiple regions for cloud resources. In addition to enabling terminal users to access tenant cloud resources, elastic public IP can also enable access to the public network. For example, tenant 40 deploys cloud resource 60011 in data center 6001 in region 600. Tenant 40 sets elastic public IP 61111 for cloud resource 60011 at access point 611 in region 621, elastic public IP 61211 for cloud resource 60011 at access point 612 in region 622, and elastic public IP 61311 for cloud resource 60011 at access point 613 in region 623. Cloud management platform 10 establishes communication channels via backbone network 13 between data center 6111 and data center 6001, between data center 6121 and data center 6001, and between data center 6131 and data center 6001. Cloud management platform 10 can first select an elastic public IP from elastic public IP 61111, elastic public IP 61211, and elastic public IP 61311 to bind to cloud resource 60011. For example, elastic public IP 61111 can be bound to cloud resource 60011. When cloud resource 60011 needs to access the external network of the infrastructure, that is, needs to access the public network, cloud resource 60011 can send a message carrying the public domain name to data center 6111 through the communication channel between data center 6111 and data center 6001. Data center 6111 can then send the message to the public IP address corresponding to the public domain name, thereby enabling cloud resource 60011 to access the public network.

[0114] Continuing with Figure 7 , if data center 6111 experiences an abnormality while cloud resource 60011 is accessing the public network, cloud resource 60011 will be unable to access the public network. However, cloud resource 60011 is unaware of the operating status of data center 6111. Therefore, after cloud resource 60011 is unable to access the public network, the cause of the inability to access the public network cannot be determined in a timely manner. The user must wait for technical personnel to perform troubleshooting, which in turn affects the stability and efficiency of cloud resource 60011's access to the public network.

[0115] Therefore, the embodiment of the present application further provides an elastic public IP configuration method, which can monitor the working status of the access point and automatically bind the elastic public IP provided by the access point with normal working status to the cloud resource based on the monitoring results, thereby improving the stability and efficiency of cloud resource access to the public network.

[0116] Figure 8 shows a schematic diagram of a public network access based on elastic public network IP provided by an embodiment of the present application. The cloud management platform 10 can set a monitoring node 70 for multiple access points corresponding to cloud resources. As shown in Figure 8, the cloud management platform can set a monitoring node 70 for access point 611, access point 612 and access point 613. The monitoring node 70 can regularly detect the connectivity of the elastic public network IP 61111 provided by access point 611, the elastic public network IP 61211 provided by access point 612 and the elastic public network IP 61311 provided by access point 613, and then determine the working status of access point 611, access point 612 and access point 613. For example, when it is determined that the elastic public network IP 61111 is not connected, it can be determined that the working status corresponding to access point 611 is an abnormal working status. When it is determined that the elastic public network IP 61211 is connected, it can be determined that the working status corresponding to access point 612 is normal. The monitoring node 70 can send the monitoring results to the cloud management platform 10. After receiving the monitoring results, the cloud management platform 10 can unbind the cloud resource 60011 from the elastic public IP, and then bind the elastic public IP 61211 to the cloud resource 60011. After that, the cloud resource 60011 can access the public network through the elastic public IP 61211. This can prevent the cloud resource 60011 from using the elastic public IP 61111 to access the public network when the access point 611 is in an abnormal working state, thereby improving the stability and efficiency of the cloud resource 60011 accessing the public network. Among them, the monitoring node 70 can be located in the same availability zone as the access point, or the monitoring node 70 can be located in a different availability zone in the same region as the access point, or the monitoring node 70 can be in a different region than the access point.

[0117] Please refer to Figure 9 below, which is a flow chart of a method for configuring an elastic public network IP based on cloud computing technology provided by an embodiment of the present application. As shown in Figure 9, the method includes but is not limited to the following steps:

[0118] S201. Tenant 40 inputs access point information, first cloud resource information, and bandwidth information.

[0119] S202. Tenant 40 sends access point information, first cloud resource information, and bandwidth information.

[0120] S203. The cloud management platform 10 receives access point information, first cloud resource information, and bandwidth information.

[0121] The processing of the above steps S201-S203 is similar to the processing of the above steps S101-S103, and will not be repeated here.

[0122] S204. The cloud management platform 10 establishes a first communication channel between the data center 1110 and the data center 1210, allocates a first elastic public IP address to the first cloud resource, and sets bandwidth.

[0123] For example, tenant 40 may set multiple access points for virtual machine 121011 in data center 1210, including, for example, access points located in data center 1110, data center 1130, and data center 1140 (data center 1110, data center 1130, and data center 1140 are not shown in FIG9 ). Data center 1110 is a first data center, and the access point located in data center 1110 may be the first access point set by tenant 40 for virtual machine 121011, also known as a default access point. Data center 1210 is a second data center, and virtual machine 121011 is a first cloud resource included in the second data center. Data center 1130 or data center 1140 may be a third data center, and the access point in data center 1130 or data center 1140 is a second access point, also known as a backup access point.

[0124] Based on the access point information and first cloud resource information entered by tenant 40 in step S201, cloud management platform 10 can determine data center 1110 where the first access point is located and data center 1210 where the first cloud resource is located. Cloud management platform 10 can establish a first communication channel, i.e., communication channel 131, between data centers 1110 and 1210 via backbone network 13. Based on the access point information and first cloud resource information entered by tenant 40 in step S101, cloud management platform 10 can bind the first elastic public IP resource in data center 1110 to virtual machine 121011. Furthermore, cloud management platform 10 can set the bandwidth for communication channel 131 based on the bandwidth information entered by tenant 40 in step S101. After completing the above settings, virtual machine 121011 can access the public network using the bound first elastic public IP address.

[0125] S205. Tenant 40 inputs monitoring information.

[0126] For example, tenant 40 configures monitoring information on an interface provided by cloud management platform 10 via tenant client 30 and Internet 20. As shown in FIG10 , tenant 40 can configure the detection type for monitoring nodes to monitor the elastic public IP address provided by access points, the address of the access points, the monitoring frequency, and the region where the access points are located.

[0127] S206. Tenant 40 sends monitoring information.

[0128] For example, the tenant 40 logs in to the cloud management platform 10 via the Internet 20 through the tenant client 30 to input monitoring information, and sends the monitoring information to the cloud management platform 10 via the Internet 20 .

[0129] S207. The cloud management platform 10 receives monitoring information.

[0130] For example, the cloud management platform 10 receives the monitoring information input by the tenant 40 in the tenant client 30 in steps S201 and S202 via the Internet 20 .

[0131] S208. The cloud management platform 10 sets the monitoring node 70 according to the received monitoring information.

[0132] For example, based on the detection information, the cloud management platform 10 can set up monitoring nodes in data center 1110, data center 1110, data center 1210, and / or data center 1120. For example, the cloud management platform 10 can send a monitoring task notification to monitoring node 70 based on the IP address of monitoring node 70 included in the monitoring information. The monitoring task notification can include the monitoring frequency, monitoring method, and the elastic public IP address corresponding to the detected access point. The detected access point can include a default access point or a backup access point.

[0133] S209 . The monitoring node 70 regularly monitors the working status of the access point.

[0134] After receiving the monitoring task notification, the monitoring node 70 may detect the connectivity of the elastic public IP corresponding to the detected access point according to the set monitoring frequency and detection method.

[0135] In one example, the monitoring node 70 may send a ping packet to the monitored first elastic public IP address at a monitoring frequency to obtain network connectivity parameters corresponding to the first elastic public IP address. The network connectivity parameters may include packet loss rate and / or latency. After obtaining the network connectivity parameters corresponding to the first elastic public IP address during each monitoring period, the monitoring node 70 may determine whether the network connectivity parameters of the first elastic public IP address meet the network connectivity conditions.

[0136] The network connectivity condition can be that the packet loss rate of the elastic public IP is less than the corresponding packet loss rate threshold, or the latency of the elastic public IP is less than the corresponding latency threshold, or the packet loss rate of the elastic public IP is less than the corresponding packet loss rate threshold and the latency is less than the corresponding latency threshold. The packet loss rate threshold, latency threshold, and ratio threshold can all be pre-set by technical personnel. Alternatively, the network connectivity condition can also be that the IP health of the elastic public IP is greater than the corresponding health threshold. The IP address health can be calculated by weighted calculation of the packet loss rate and latency of the elastic public IP. The weights required for the weighted calculation and the health threshold can both be pre-set by technical personnel.

[0137] S210 . The monitoring node 70 sends the working status of the first access point to the cloud management platform 10 .

[0138] After determining the working status of the first access point, the monitoring node 70 may send the working status of the first access point to the cloud management platform.

[0139] S211. The cloud management platform 10 notifies the tenant 40 of the working status of the first access point.

[0140] Optionally, after receiving the working status corresponding to the first access point, the cloud management platform 10 may send the working status to the tenant client corresponding to the tenant 40 .

[0141] S212. When the working status of the first access point is an abnormal working status, the cloud management platform 10 establishes a second communication channel between the data center 1110 and the data center 1130, allocates a second elastic public IP for the cloud resources and sets the bandwidth.

[0142] The data center 1130 includes a backup access point for cloud resources. The working state corresponding to the backup access point is a normal working state.

[0143] For example, if the cloud management platform 10 receives a notification that the first access point currently used by virtual machine 121011 is in an abnormal working state, it means that virtual machine 121011 cannot normally access the public network through the currently bound first elastic public IP. Therefore, the cloud management platform 10 can switch the access point for virtual machine 121011 and rebind the elastic public IP.

[0144] The cloud management platform 10 can first unbind the binding relationship between the first cloud resource and the first elastic public IP address. Then, based on the access point information and the first cloud resource information input by tenant 40 in step S201, it can determine the data center 1130 where the backup access point is located and the data center 1210 where the first cloud resource is located. A second communication channel, namely, communication channel 133, is established between data centers 1130 and 1210 via backbone network 13. The second elastic public IP address in data center 1130 is bound to virtual machine 121011, and the bandwidth is set for communication channel 133 based on the bandwidth information input by tenant 40 in step S101. After completing the above settings, the switching of the elastic public IP address bound to virtual machine 121011 is completed, and virtual machine 121011 can access the public network based on the newly bound second elastic public IP address.

[0145] In one achievable manner, the monitoring information sent in the above step S206 includes information on multiple monitoring nodes. The multiple monitoring nodes include monitoring nodes located in the same availability zone as the data center 1110, monitoring nodes located in different availability zones, and monitoring nodes located in different large regions. In step S210, the cloud management platform 10 can receive monitoring results sent by multiple monitoring nodes. If the cloud management platform 10 determines that the number of monitoring nodes that monitor the first access point as being in an abnormal working state accounts for a greater than a percentage threshold in the total number of monitoring nodes, it can determine that the working state of the first access point is an abnormal working state, and then step S212 can be executed. In this way, by monitoring the working state of the access point through monitoring nodes in different availability zones and different large regions, the accuracy of monitoring the working state of the access point can be improved.

[0146] For example, the tenant 40 can configure the percentage threshold and the availability zone of each monitoring node through the tenant client 30 on the interface provided by the cloud management platform 10. That is, the percentage threshold and the availability zone of each monitoring node can be set in the monitoring information and sent to the cloud management platform 10 via the Internet. This allows for customized monitoring of the access point operating status and improves the flexibility of access point operating status monitoring.

[0147] Optionally, in another embodiment provided herein, upon determining that the operating status of a first access point in data center 1110 is abnormal, cloud management platform 10 may send an alarm message to a cloud management terminal corresponding to the cloud management platform. The alarm message carries an access point identifier corresponding to the first access point, such as the first elastic public IP address corresponding to the access point. This allows technicians at the cloud management terminal to immediately obtain information that the access point is in an abnormal operating state and then investigate the cause of the abnormal operating state, thereby improving troubleshooting efficiency.

[0148] Optionally, in another embodiment provided in the present application, when the working status of the first access point in the data center 1110 of the cloud management platform 10 is an abnormal working status, a notification to stop monitoring the access point in the corresponding data center 1110 can be sent to the monitoring node 70 to instruct the monitoring node 70 to stop monitoring the working status of the first access point, thereby reducing useless monitoring and reducing the occupation of network resources.

[0149] Optionally, in another embodiment provided by the present application, the present application embodiment provides two solutions for binding elastic public IP. Taking the elastic public IP as a GEIP address as an example, the two solutions are introduced:

[0150] Solution 1: When the cloud resource is a virtual machine, the address management service in the cloud management platform binds a second elastic public IP address to the virtual machine running the public network access service.

[0151] Figure 11 is a primary and backup IP solution for a GEIP-bound virtual machine provided in an embodiment of the present application. As shown in Figure 11, the virtual machine is assigned GEIP1 and GEIP2. Among them, GEIP1 can be the primary IP address bound to the virtual machine, and GEIP1 can be the backup IP address bound to the virtual machine. The technician can configure the monitoring information corresponding to the access point in the configuration interface, that is, configure the monitoring node that needs to monitor GEIP1 and GEIP2. Continuing to refer to Figure 11, the address management service can control whether to switch the bound primary IP address to the backup IP address based on the monitoring results output by the address monitoring service according to the configured monitoring policy. For example, after the address management service determines that GEIP1 is unavailable, the GEIP1 bound to the virtual machine can be switched to GEIP2.

[0152] Solution 2: The address management service in the cloud management platform binds a second elastic public IP address to the gateway connected to the cloud resources.

[0153] Figure 12 is a master-master IP solution for a GEIP-bound gateway provided in an embodiment of the present application. As shown in Figure 12, the virtual machine is assigned GEIP1 and GEIP2. Among them, GEIP1 and GEIP2 can both be the primary IP addresses bound to the virtual machine, but GEIP1 or GEIP2 is bound to the gateway of the virtual machine. The technician can configure the monitoring information in the configuration interface of the terminal, that is, configure the monitoring nodes that need to monitor GEIP1 and GEIP2, and can configure the site monitoring strategy in the configuration interface. Continuing to refer to Figure 12, the address management service can control whether to switch the bound primary IP address to other primary IP addresses based on the monitoring results output by the address monitoring service according to the configured monitoring strategy. For example, after the address management service determines that GEIP1 is unavailable, the GEIP1 bound to the gateway can be switched to GEIP2.

[0154] Figure 13 is a schematic diagram of a method for public network access provided by an embodiment of the present application. As shown in Figure 3, multiple monitoring nodes located in different regions can monitor the availability of multiple elastic public IPs allocated by the public network access service according to the monitoring period, and then send the obtained network connectivity parameters to the cloud network scheduling service. The cloud network scheduling service can determine the available and unavailable elastic public IPs among the multiple elastic public IPs according to the pre-configured strategy and the received network connectivity parameters, and then obtain the scheduling result and send it to the address management service. After receiving the scheduling result, if the scheduling result indicates that the elastic public IP bound to the current public network access service is unavailable, the address management service can switch the available elastic public IP for the cloud resources, thereby realizing normal public network access for the cloud resources.

[0155] It can be seen that in the embodiment of the present application, the address management service can automatically switch the available elastic public IP for the public access service based on the availability of each elastic public IP monitored by the address monitoring service. This can avoid network interruption caused by the unavailability of the elastic public IP for the public access service, thereby improving the stability of public access to cloud resources.

[0156] Please refer to Figure 14 below, which is a schematic diagram of the structure of a cloud management platform device provided in an embodiment of the present application. As shown in Figure 7, the cloud management platform 10 includes a receiving module 1401, a channel establishment module 1402, a setting module 1403, and a processing module 1404. Among them:

[0157] The receiving module 1401 is used to perform the actions of receiving the access point information, cloud resource information, and bandwidth information input by the tenant in step S103 in the embodiment of FIG. 3 and step S203 in the embodiment of FIG. 9 , and the action of receiving the unbinding information input by the tenant in step S110 .

[0158] The channel establishing module 1402 is used to execute the action of establishing the communication channel between data centers in step S104 in the embodiment of FIG. 3 and step S204 in the embodiment of FIG. 9 .

[0159] The setting module 1403 is used to execute the action of setting a monitoring node for the access point in step S209 in the embodiment of FIG. 9 .

[0160] The processing module 1404 is used to execute the action of notifying the tenant of the working status in step S211 in the embodiment of FIG. 9 , or the action of establishing a communication channel between data centers in step S212 .

[0161] The receiving module 1401, channel establishment module 1402, setting module 1403, and processing module 1404 can all be implemented via software or hardware. For example, the following describes the implementation of the receiving module 1401, taking the receiving module 1401 as an example. Similarly, the implementation of the channel establishment module 1402, setting module 1403, and processing module 1404 can refer to the implementation of the detection module.

[0162] As an example of a software functional unit, the receiving module 1401 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the receiving module 1401 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple geographically close data centers. Typically, a region may include multiple AZs.

[0163] Similarly, multiple hosts / virtual machines / containers running the code can be distributed within the same virtual private cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

[0164] As an example of a hardware functional unit, the detection module may include at least one computing device, such as a server. Alternatively, the detection module may be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0165] The multiple computing devices included in the detection module can be distributed in the same region or in different regions. The multiple computing devices included in the detection module can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the detection module can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0166] It should be noted that, in other embodiments, the receiving module 1401, the channel establishment module 1402, the setting module 1403, and the processing module 1404 can be used to execute any step in the elastic public IP configuration method. The steps that the receiving module 1401, the channel establishment module 1402, the setting module 1403, and the processing module 1404 are responsible for implementing can be specified as needed. The receiving module 1401, the channel establishment module 1402, the setting module 1403, and the processing module 1404 respectively implement different steps in any one of the elastic public IP configuration methods to realize all the functions of the cloud management platform.

[0167] This application also provides a public cloud system, including a first access point, a second access point, cloud resources, monitoring nodes, and a backbone network. The first access point, the second access point, the cloud resources, the monitoring nodes, and the backbone network can all be implemented via software or hardware. For example, the implementation of the first access point is described below. Similarly, the implementation of the second access point, the cloud resources, the monitoring nodes, and the backbone network can refer to the implementation of the access point.

[0168] As an example of a software functional unit, a module may include a code running on a computing instance. The computing instance may be at least one of a physical host (computing device), a virtual machine, a container, and other computing devices. Furthermore, the computing device may be one or more. For example, the first access point may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the application may be distributed in the same region or in different regions. The multiple hosts / virtual machines / containers used to run the code may be distributed in the same AZ or in different AZs, and each AZ includes one data center or multiple geographically close data centers. Generally, a region may include multiple AZs.

[0169] Similarly, the multiple hosts / virtual machines / containers running the code can be distributed within the same VPC or across multiple VPCs. Typically, a VPC is located within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

[0170] As an example of a hardware functional unit, a cloud management platform may include at least one computing device, such as a server. Alternatively, the cloud management platform may be implemented using an ASIC or a PLD. The PLD may be implemented using a CPLD, FPGA, GAL, or any combination thereof.

[0171] The multiple computing devices included in the first access point can be distributed in the same region or in different regions. The multiple computing devices included in the access point can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the first access point can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0172] This application also provides a computing device 1500. As shown in Figure 15, computing device 1500 includes a bus 1502, a processor 1504, a memory 1506, and a communication interface 1508. Processor 1504, memory 1506, and communication interface 1508 communicate with each other via bus 1502. Computing device 1500 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 1500.

[0173] Bus 1502 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG15 shows a single bus line, but this does not imply a single bus or type of bus. Bus 1502 may include a path for transmitting information between various components of computing device 1500 (e.g., memory 1506, processor 1504, and communication interface 1508).

[0174] The processor 1504 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0175] The memory 1506 may include volatile memory, such as random access memory (RAM). The memory 1506 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0176] Memory 1506 stores executable program code, which processor 1504 executes to implement the functions of the aforementioned receiving module 1401, channel establishment module 1402, configuration module 1403, and processing module 1404, thereby implementing the method for accessing the public network. Specifically, memory 1506 stores instructions for executing the method for configuring an elastic public IP address.

[0177] The communication interface 1508 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 1500 and other devices or a communication network.

[0178] Embodiments of the present application also provide a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0179] As shown in Figure 16, the computing device cluster includes at least one computing device 1500. The memory 1506 in one or more computing devices 1500 in the computing device cluster may store the same instructions for executing the elastic public network IP configuration method.

[0180] In some possible implementations, the memory 1506 of one or more computing devices 1500 in the computing device cluster may also store partial instructions for executing the elastic public IP configuration method. In other words, the combination of one or more computing devices 1500 can jointly execute the instructions for executing the elastic public IP configuration method.

[0181] It should be noted that the memory 1506 in different computing devices 1500 in the computing device cluster can store different instructions, which are used to execute part of the functions of the receiving module 1401, the channel establishment module 1402, the setting module 1403, and the processing module 1404 respectively.

[0182] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN) or a local area network (LAN), etc. FIG17 illustrates a possible implementation. As shown in FIG16 , two computing devices 1500A and 1500B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 1506 in the computing device 1500A stores instructions for executing the functions of the receiving module 1401 and the channel establishment module 1402. Simultaneously, the memory 1506 in the computing device 1500B stores instructions for executing the functions of the setting module 1403 and the processing module 1404. It should be understood that the functions of the computing device 1500A shown in FIG17 may also be performed by multiple computing devices 1500. Similarly, the functions of the computing device 1500B may also be performed by multiple computing devices 1500.

[0183] The present application also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection method of the computing device cluster described in Figures 16 and 17. The difference is that the memory 1506 of one or more computing devices 1500 in the computing device cluster can store the same instructions for configuring an elastic public network IP.

[0184] In some possible implementations, the memory 1506 of one or more computing devices 1500 in the computing device cluster may also store some instructions for the elastic public IP configuration method. In other words, the combination of one or more computing devices 1500 can jointly execute the instructions for the elastic public IP configuration method.

[0185] It should be noted that the memory 1506 in different computing devices 1500 in the computing device cluster can store different instructions for executing certain functions of the cloud desktop system. In other words, the instructions stored in the memory 1506 in different computing devices 1500 can implement the functions of the receiving module 1401, the channel establishment module 1402, the setting module 1403, and the processing module 1404.

[0186] Embodiments of the present application also provide a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored on any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to execute a method for configuring an elastic public IP address.

[0187] Embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device, or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the elastic public network IP configuration method.

[0188] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for configuring an elastic public network IP based on cloud computing technology, characterized in that The method is used for a cloud management platform which is used to manage infrastructure. The infrastructure includes a first data center located in a first availability zone, a second data center located in a second availability zone, and a third data center located in a third availability zone. The method includes: The cloud management platform receives first access point information input by a tenant, where the first access point information is used to indicate a first access point of a first elastic public network IP purchased by the tenant, and the first access point is located in the first data center of the first availability zone; The cloud management platform receives first cloud resource information input by the tenant, where the first cloud resource information is used to indicate a first cloud resource bound to the first elastic public network IP and the second availability zone where the first cloud resource is located, and the first cloud resource is set in the second data center of the second availability zone; The cloud management platform establishes a first communication channel between the first data center and the second data center, where the first communication channel is used to transmit a packet whose destination address is the first elastic public network IP and is sent to the first access point through the external network of the infrastructure from the first data center to the first cloud resource in the second data center, and / or transmit a packet whose destination address belongs to the external network and is generated by the first cloud resource from the second data center to the first access point in the first data center and send it to the external network through the first access point; The cloud management platform receives monitoring information input by the tenant for the first access point, where the monitoring information carries the first elastic public network IP; The cloud management platform sets a monitoring node in the first availability zone or an adjacent availability zone of the first availability zone. The monitoring node is used to periodically monitor the working state of the first access point and feedback the working state to the cloud management platform; The cloud management platform notifies the tenant of the working state; and / or, when the working state is an abnormal working state, the cloud management platform establishes a second communication channel between the third data center and the second data center. The third data center includes a second access point of a second elastic public network IP purchased by the tenant. The second communication channel is used to transmit a packet whose destination address is the second elastic public network IP and is sent to the second access point in the third data center through the external network from the third data center to the first cloud resource in the second data center, and / or transmit a packet whose destination address is the external network and is generated by the first cloud resource from the second data center to the second access point in the third data center and send it to the external network through the second access point.

2. The method according to claim 1, characterized in that, The monitoring node is further used to periodically monitor the working state of the second access point; When the working state is an abnormal working state, the cloud management platform establishes a second communication channel between the third data center and the second data center, including: When the working state of the first access point is an abnormal working state and the working state of the second access point is a normal working state, the cloud management platform unbinds the first elastic public network IP from the first cloud resource, binds the second elastic public network IP to the first cloud resource, and establishes a second communication channel between the third data center and the second data center.

3. The method according to claim 1 or 2, characterized in that, The number of the monitoring nodes is multiple. When the working state is an abnormal working state, the cloud management platform establishes the second communication channel between the third data center and the second data center, including: When the cloud management platform determines that the proportion of the monitoring nodes that monitor the first access point as being in an abnormal working state in the total number of the monitoring nodes is greater than a proportion threshold, the cloud management platform establishes the second communication channel between the third data center and the second data center.

4. The method according to claim 3, wherein The monitoring information further includes the proportion threshold and the availability zone where each monitoring node is located.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The cloud management platform receives monitoring data for monitoring the working state of the first access point by the monitoring nodes, where the monitoring data includes a packet loss rate and a latency. When the packet loss rate corresponding to the first access point is greater than a packet loss rate threshold or the latency corresponding to the first access point is less than a latency threshold, the cloud management platform determines that the working state of the first access point is an abnormal working state.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: When the working state of the first access point is an abnormal working state, the cloud management platform sends an alarm message to the cloud management terminal corresponding to the cloud management platform, where the access point identifier corresponding to the first access point is carried in the alarm message.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: When the working state of the first access point is an abnormal working state, the cloud management platform sends a stop monitoring notice corresponding to the first access point to the monitoring nodes, where the stop monitoring notice is used to instruct the monitoring nodes to stop regularly monitoring the working state of the first access point.

8. A cloud management platform, characterized in that, The cloud management platform is used to manage infrastructure, where the infrastructure includes a first data center set in a first availability zone, a second data center set in a second availability zone, and a third data center set in a third availability zone. The cloud management platform includes: A receiving module, configured to receive first access point information input by a tenant, where the first access point information is used to indicate a first access point of a first elastic public network IP purchased by the tenant, and the first access point is located in the first data center of the first availability zone; receive first cloud resource information input by the tenant, where the first cloud resource information is used to indicate a first cloud resource bound to the first elastic public network IP and the second availability zone where the first cloud resource is located, where the first cloud resource is set in the second data center of the second availability zone. A channel establishment module, configured to establish a first communication channel between the first data center and the second data center, where the first communication channel is used to transmit a packet with a destination address of the first elastic public network IP sent to the first access point through the external network of the infrastructure from the first data center to the first cloud resource in the second data center, and / or transmit a packet generated by the first cloud resource with a destination address belonging to the external network from the second data center to the first access point in the first data center and send it to the external network via the first access point; The receiving module is further configured to receive monitoring information input by the tenant for the first access point, where the monitoring information carries the first elastic public network IP; A setting module, configured to set a monitoring node in the first available zone or an available zone adjacent to the first available zone, where the monitoring node is used to periodically monitor the working state of the first access point and feedback the working state to the cloud management platform; A processing module, configured to notify the tenant of the working state by the cloud management platform; and / or, configured to establish a second communication channel between the third data center and the second data center when the working state is an abnormal working state, where the third data center includes a second access point of the second elastic public network IP purchased by the tenant, and the second communication channel is used to transmit a packet with a destination address of the second elastic public network IP sent to the second access point in the third data center through the external network from the third data center to the first cloud resource in the second data center, and / or transmit a packet generated by the first cloud resource with a destination address of the external network from the second data center to the second access point in the third data center and send it to the external network via the second access point.

9. The cloud management platform according to claim 8, wherein The monitoring node is further configured to periodically monitor the working state of the second access point; the channel establishment module is configured to: When the working state of the first access point is an abnormal working state and the working state of the second access point is a normal working state, unbind the first elastic public network IP from the first cloud resource, bind the second elastic public network IP to the first cloud resource, and establish a second communication channel between the third data center and the second data center.

10. The cloud management platform according to claim 8 or 9, characterized in that, The number of the monitoring nodes is multiple, and the channel establishment module is configured to: Establish a second communication channel between the third data center and the second data center when it is determined that the proportion of the number of monitoring nodes that monitor the first access point as being in an abnormal working state in the total number of monitoring nodes is greater than a proportion threshold.

11. The cloud management platform according to claim 10, characterized in that, The monitoring information further includes the proportion threshold and the available zone where each monitoring node is located.

12. The cloud management platform according to any one of claims 8 to 11, characterized in that, The cloud management platform further includes a determination module, configured to: Receive monitoring data obtained by the monitoring node for monitoring the working state of the first access point, where the monitoring data includes a packet loss rate and a latency; When the packet loss rate corresponding to the first access point is greater than the packet loss rate threshold or the latency corresponding to the first access point is less than the latency threshold, determine that the operating state of the first access point is an abnormal operating state.

13. The cloud management platform according to any one of claims 8 to 12, characterized in that, The cloud management platform further includes an alarm module for: When the operating state of the first access point is an abnormal operating state, the cloud management platform sends an alarm message to the cloud management terminal corresponding to the cloud management platform, and the access point identifier corresponding to the first access point is carried in the alarm message.

14. The cloud management platform according to any one of claims 8 to 13, characterized in that The cloud management platform further includes a sending module for: When the operating state of the first access point is an abnormal operating state, the cloud management platform sends a stop monitoring notice corresponding to the first access point to the monitoring node, and the stop monitoring notice is used to instruct the monitoring node to stop regularly monitoring the operating state of the first access point.

15. A cluster of computing devices, characterized in that, Comprising at least one computing device, each computing device includes a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 7.

16. A computer program product comprising instructions, characterized in that, When the instructions are run by the computing device, the computing device executes the method according to any one of claims 1 to 7.

17. A computer-readable storage medium, characterized in that, Comprising computer program instructions, when the computer program instructions are executed by the computing device, the computing device executes the method according to any one of claims 1 to 7.

Images