A method for distributing VPC interconnection configuration in a multi-availability zone environment

Abstract

The present invention provides a method for issuing VPC interconnection configurations in a multi-availability zone environment, including Availability Zone A and Availability Zone B. The traffic between Availability Zone A and Availability Zone B will be forwarded through the DCI border in the DCI interconnection area, so as to achieve interconnection between availability zones. The issuance of interconnection configurations between multiple availability zones is triggered by the online of virtual machines under the VPC. When a virtual machine goes online in a certain subnet under the VPC, the DCI interconnection configuration issuance process is triggered. Advantageous effects of the present invention: A method for issuing VPC interconnection configurations in a multi-availability zone environment realizes VPC network interconnection between different availability zones by introducing a new network device, DCI Border (Data Center Interconnection Border), so as to meet various flexible requirements of users for cross-availability zone networks.

Description

Technical Field

[0001] The present invention belongs to the field of cloud networks, and in particular, relates to a method for issuing VPC interconnection configurations in a multi-availability zone environment. Background Art

[0002] In recent years, the migration of enterprises to the cloud has become a continuous trend. By "migrating to the cloud", not only can enterprises solve their IT usage and operation costs, but also help them solve various management and maintenance problems of traditional computer rooms. For enterprises, the stability and continuity of cloud services are the most important aspects. Strong stability and continuity capabilities can ensure that the services provided by enterprises are always available externally, and the situation of service unavailability caused by the downtime of one or several servers will not occur.

[0003] Therefore, in current public cloud services, public cloud providers use various methods to help users achieve the stability and continuity of cloud services. The specific implementation methods include high-availability servers, off-site disaster recovery and other solutions. Although these solutions have different product forms, ultimately, they all rely on the same technology implementation - multi-availability zone (abbreviated as az) interconnection. When it comes to availability zones, first, we need to understand the concept of regions.

[0004] A region refers to a physical data center. Each region is completely independent, which can achieve the maximum degree of fault tolerance and stability. After a resource is successfully created, the region cannot be changed. An availability zone is a physical area within the same region where power and network are isolated from each other. One availability zone is not affected by the failures of other availability zones. There can be multiple availability zones within a region. Different availability zones are physically isolated but have internal network interconnection, which not only ensures the independence of availability zones but also provides low-cost and low-latency network connections.

[0005] However, the current existing technologies cannot meet the various flexible requirements of users for cross-availability zone networks. Summary of the Invention

[0006] In view of this, the present invention aims to propose a method for issuing VPC interconnection configurations in a multi-availability zone environment. By introducing a new network device DCI Border (Data Center Interconnection Border), the VPC network interconnection between different availability zones is realized, so as to meet the various flexible requirements of users for cross-availability zone networks.

[0007] To achieve the above object, the technical solution of the present invention is realized as follows:

[0008] A method for distributing VPC interconnection configurations in a multi-availability zone environment, including Availability Zone A and Availability Zone B. The service traffic between Availability Zone A and Availability Zone B will be forwarded by the DCI border in the DCI interconnection zone, thereby achieving interconnection between availability zones;

[0009] The distribution of interconnection configurations between multiple availability zones is triggered by the online of virtual machines under the VPC. When a virtual machine is online in a certain subnet under the VPC, the DCI interconnection configuration distribution process is triggered.

[0010] Furthermore, the distribution process includes:

[0011] S1. First, check whether there is a record of this subnet in the status table according to the subnet ID. If it exists, it means that the dci-related configuration has been distributed for this subnet, and the process ends. Otherwise, execute step S2. The status table is the vpc_subnets_dci_status table;

[0012] S2. The non-existence of a record related to this subnet in the status table indicates that the dci interconnection configuration has not been distributed for this subnet. Then continue to query whether there is a record related to the vpc in the status table according to the vpc ID. If there is still no record, it means that this is the first time a virtual machine has been online in this subnet under this vpc in all azs. At this time, only the vpc and subnet information need to be stored in the database, and there is no need to distribute the interconnection configuration;

[0013] S3. In step S2, if a record exists in the status table when querying according to the vpc ID, it is necessary to continue to judge. If all records belong to this az, execute step S4. If all records do not belong to this az, execute step S5. If some records belong to this az, execute step S6;

[0014] S4. All records belonging to this az indicate that this operation is for the online of a virtual machine under a newly added subnet under the vpc in this az. In this case, only the subnet information needs to be stored in the database, and there is no need to distribute the dci interconnection configuration;

[0015] S5. All records not belonging to this az indicate that this is for the online of a virtual machine under a subnet in the vpc under a new az. It is necessary to distribute the dci interconnection configuration and query how many availability zones are included in the records in the table;

[0016] S6. Some records belong to this az and some records belong to non-this az, indicating that the vpc has already distributed the interconnection configuration between availability zones. This virtual machine is for the online of a virtual machine under a newly added subnet in the vpc. Therefore, it is necessary to store the subnet information in the database and call the interface to distribute the network segment information related to the subnet to the dci borders in each availability zone to achieve network segment interconnection.

[0017] Further, in step S5, the specific method is as follows:

[0018] Group the vpc-related data in the table. Using the availability zone as the grouping condition, find the number of groups. Assume that in the current vpc in the database table, there are records in availability zones B, C, and D. Then, set it as availability zone A. When a virtual machine goes online within the vpc in availability zone A this time, first, it is necessary to issue the configuration for intercommunication with availability zones B, C, and D at the dci border in availability zone A; at the same time, it is necessary to issue the intercommunication configuration with availability zone A on the dci borders of availability zones B, C, and D respectively. At the same time, since availability zones B / C / D already exist in the database, it indicates that the intercommunication configuration between availability zones B / C / D has been issued before, and there is no need to issue it repeatedly this time.

[0019] Further, in step S6, the specific method is as follows:

[0020] Group the vpc-related data in the table. Using the availability zone as the grouping condition, find the number of groups. Assume that in the current vpc in the database table, there are records in availability zones A, B, C, and D. Then, it is necessary to call the interfaces of these 4 availability zones respectively, and issue the network segment information related to the subnet through the dci border, so as to implement the routing information for configuring the subnet network segment granularity.

[0021] In a second aspect, the present solution discloses an electronic device, including a processor and a memory communicatively connected to the processor and used for storing instructions executable by the processor. The processor is used to execute the method for issuing VPC intercommunication configuration in a multi-availability zone environment described in the first aspect above.

[0022] In a third aspect, the present solution discloses a server, including at least one processor and a memory communicatively connected to the processor. The memory stores instructions executable by the at least one processor. When the instructions are executed by the processor, the at least one processor is caused to execute the method for issuing VPC intercommunication configuration in a multi-availability zone environment described in the first aspect.

[0023] In a fourth aspect, the present solution discloses a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the method for issuing VPC intercommunication configuration in a multi-availability zone environment described in the first aspect.

[0024] Compared with the prior art, the method for issuing VPC intercommunication configuration in a multi-availability zone environment described in the present invention has the following beneficial effects:

[0025] (1) A method for distributing VPC interconnection configurations in a multi-availability zone environment realizes VPC network interconnection between different availability zones by introducing a new network device DCI Border (Data Center Interconnection Border), thereby meeting various flexible requirements of users for cross-availability zone networks.

[0026] (2) The purpose of a method for distributing VPC interconnection configurations in a multi-availability zone environment is to accurately and efficiently distribute configurations with low latency and high accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings, which form a part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments and descriptions thereof are used to explain the invention and do not constitute an improper limitation of the invention. In the drawings:

[0028] Figure 1 is a schematic diagram of a simplified network architecture between multiple availability zones described in an embodiment of the present invention;

[0029] Figure 2 is a schematic diagram of the core processing logic flow chart for distributing multi-availability zone configurations after a virtual machine is launched, described in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0030] It should be noted that, without conflict, the embodiments in the present invention and the features in the embodiments can be combined with each other.

[0031] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments.

[0032] As Figure 1 shown, between Availability Zone A and Availability Zone B, specific service traffic is forwarded through the DCIborder in the DCI interconnection area, thereby realizing interconnection between availability zones.

[0033] The present invention will illustrate the core content such as the timing and specific details of distributing the configurations of VPCs and subnets in the tenant network when realizing specific interconnection between DCIs.

[0034] The core database tables are as follows (cross-availability zone vpc and subnet status information table):

[0035]

[0036] The above table records whether the subnets under the current vpc have had interconnection configurations distributed in the current availability zone, as well as the status information of instance records, etc.

[0037] Figure 2 The timing and details of distributing VPC interconnection configurations between multiple availability zones will be described in detail

[0038] Through Figure 2 It can be seen that the distribution of the interconnection configuration between multiple available zones is triggered by the online of virtual machines under the VPC. When a virtual machine goes online in a certain subnet under the VPC, the DCI interconnection configuration distribution process is triggered.

[0039] 1. First, check whether there is a record of this subnet in the vpc_subnets_dci_status table (hereinafter referred to as the status table) according to the subnet ID. If it exists, it means that the DCI-related configuration has been distributed for this subnet, and the process ends.

[0040] 2. If there is no record of this subnet in the status table, it means that the DCI interconnection configuration has not been distributed for this subnet. Then continue to query the status table according to the VPC ID to see if there is a record related to the VPC. If there is still no record, it means that this is the first time a virtual machine in this subnet under this VPC has gone online in all AZs. At this time, only the VPC and subnet information needs to be stored in the database, and there is no need to distribute the interconnection configuration. (See the position of Note 1)

[0041] 3. If a record exists in the status table when querying according to the VPC ID, it is necessary to continue to judge:

[0042] 1) If all records belong to this AZ: It means that this operation is for the online of virtual machines under a newly added subnet under the VPC within this AZ. In this case, only the subnet information needs to be stored in the database, and there is no need to distribute the DCI interconnection configuration. (See the position of Note 2)

[0043] 2) All records do not belong to this AZ: It means that this is for the online of virtual machines under a subnet within the VPC in a new AZ. It is necessary to distribute the DCI interconnection configuration, and at the same time, it is necessary to query how many available zones are included in the records in the table.

[0044] The specific operation is to group the data related to the VPC in the table, with the available zone as the grouping condition, and find the number of groups (assuming that currently under the VPC in the database, there are records in Availability Zone B, Availability Zone C, and Availability Zone D). Then, when a virtual machine goes online within the VPC in the current available zone (assuming it is Availability Zone A), first, it is necessary to distribute the configuration for interconnection with Availability Zones B, C, and D at the DCI border in Availability Zone A; at the same time, it is necessary to distribute the configuration for interconnection with Availability Zone A at the DCI borders in Availability Zones B, C, and D respectively. At the same time, since Availability Zones B / C / D already exist in the database, it means that the interconnection configuration between Availability Zones B / C / D has been distributed before, and there is no need to distribute it repeatedly this time. (See the position of Note 3)

[0045] 3) Some records belong to this AZ, and some records belong to non-this AZ: In this case, it indicates that the VPC has already issued an interconnection configuration between availability zones. This time, the virtual machine is going online in a newly added subnet within the VPC. Therefore, it is necessary to store the subnet information in the repository and at the same time call the interface to send the network segment information related to the subnet to the DCI border in each availability zone to achieve network segment interconnection. (See the position of Note 4)

[0046] The specific operation is to group the VPC-related data in the table, with the availability zone as the grouping condition, and find the number of groups (assuming that there are records under availability zone A, availability zone B, availability zone C, and availability zone D in the current VPC in the database table). Then, it is necessary to call the interfaces of these 4 availability zones respectively, and through the DCI border, send the network segment information related to the subnet, so as to implement the routing information at the subnet network segment granularity.

[0047] The specific implementation method is as follows: First, the user needs to select a cross-availability zone product (taking the virtual machine as an example) on the page. Then, the user needs to select VPC1 in availability zone one and create a virtual machine. After that, in availability zone two, the user also needs to select VPC1 and create another virtual machine. At this time, when the second virtual machine goes online, through the method introduced in the present invention, the background program will automatically issue the interconnection configuration between availability zone one and availability zone two of the VPC. The user can log in to any one of the just-created virtual machines at will and use ping or other methods to verify whether the traffic between cross-availability zones is interconnected.

[0048] Those of ordinary skill in the art can realize that the units and method steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but this implementation should not be considered to exceed the scope of the present invention.

[0049] In several embodiments provided by the present application, it should be understood that the disclosed methods and systems can be implemented in other ways. For example, the division of the above-mentioned units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. The above-mentioned units may or may not be physically separated. The components shown as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

[0050] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be covered by the scope of the claims and the description of the present invention.

[0051] The above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for distributing VPC interconnection configurations in a multi-availability zone environment, characterized in that: It includes Availability Zone A and Availability Zone B. The service traffic between Availability Zone A and Availability Zone B will be forwarded by the DCI border in the DCI interconnection zone, so as to achieve interconnection between availability zones; The distribution of interconnection configurations between multiple availability zones is triggered by the online of virtual machines under the VPC. When a virtual machine goes online in a certain subnet under the VPC, the DCI interconnection configuration distribution process is triggered; The distribution process includes: S1. First, check whether there is a record of this subnet in the status table according to the subnet ID. If it exists, it means that the DCI-related configuration has been distributed to this subnet, and the process ends. Otherwise, execute step S2. The status table is the vpc_subnets_dci_status table; S2. The non-existence of a record related to this subnet in the status table indicates that the DCI interconnection configuration has not been distributed to this subnet. Then continue to query the status table according to the VPC ID to see if there is a record related to the VPC. If there is still no record, it means that this is the first time a virtual machine in this subnet under this VPC has gone online in all AZs. At this time, only the VPC and subnet information need to be stored in the database, and there is no need to distribute the interconnection configuration; S3. In step S2, if a record exists in the status table queried according to the VPC ID, further judgment is required. If all records belong to this AZ, execute step S4. If all records do not belong to this AZ, execute step S5. If some records belong to this AZ, execute step S6; S4. All records belonging to this AZ indicate that this operation is for the online of a virtual machine under a newly added subnet under the VPC in this AZ. In this case, only the subnet information needs to be stored in the database, and there is no need to distribute the DCI interconnection configuration; S5. All records not belonging to this AZ indicate that this is for the online of a virtual machine under a subnet in the VPC in a new AZ. It is necessary to distribute the DCI interconnection configuration and also query how many availability zones are included in the records in the table; S6. Some records belong to this AZ and some records belong to non-this AZ, indicating that the VPC has already distributed the interconnection configuration between availability zones. This virtual machine is for the online of a virtual machine under a newly added subnet in the VPC. Therefore, it is necessary to store the subnet information in the database and at the same time call the interface to distribute the network segment information related to the subnet to the DCI borders in each availability zone to achieve network segment interconnection; In step S5, the specific method is as follows: Group the data related to VPC in the table, with the availability zone as the grouping condition, and find the number of groups. Assume that in the current VPC in the database table, there are records in Availability Zone B, Availability Zone C, and Availability Zone D. Then, set it as Availability Zone A. When a virtual machine goes online within the VPC in Availability Zone A this time, first, it is necessary to issue the configuration for interconnection with Availability Zones B, C, and D at the DCI border in Availability Zone A; at the same time, it is necessary to issue the interconnection configuration with Availability Zone A at the DCI borders in Availability Zones B, C, and D respectively. At the same time, since Availability Zones B / C / D already exist in the database, it means that the interconnection configuration between Availability Zones B / C / D has been issued before, and there is no need to issue it repeatedly this time.

2. A method for issuing VPC interconnection configuration in a multi-availability zone environment according to claim 1, characterized in that, in step S6, the specific method is as follows: Group the data related to VPC in the table, with the availability zone as the grouping condition, and find the number of groups. Assume that in the current VPC in the database table, there are records in Availability Zone A, Availability Zone B, Availability Zone C, and Availability Zone D. Then, it is necessary to call the interfaces of these 4 availability zones respectively, and issue the network segment information related to the subnet through the DCI border, so as to implement the routing information at the subnet network segment granularity.

3. An electronic device, including a processor and a memory communicatively connected to the processor and used to store instructions executable by the processor, characterized in that: the processor is used to execute the method for issuing VPC interconnection configuration in a multi-availability zone environment according to any one of claims 1-2 above.

4. A server, characterized in that: including at least one processor and a memory communicatively connected to the processor, the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor so that the at least one processor executes the method for issuing VPC interconnection configuration in a multi-availability zone environment according to any one of claims 1-2 above.

5. A computer-readable storage medium storing a computer program, characterized in that: when the computer program is executed by a processor, it implements the method for issuing VPC interconnection configuration in a multi-availability zone environment according to any one of claims 1-2.

Images