Method and system for realizing cross-VPC communication based on cloud scene

Abstract

The invention particularly relates to a method and a system for realizing cross-VPC communication based on a cloud scene. According to the method for realizing cross-VPC communication based on the cloud scene, a collaborative private network is created, and cloud servers needing mutual communication are added into the same private network for communication; an eth1 network card is added to the cloud server added to the private network, a private network IP is allocated, and the cloud servers of different VPCs realize cross-VPC communication by means of the eth1 network card; different private networks are isolated from one another, so that the safety and isolation are ensured; when the cloud server exits from the private network, deleting the corresponding cloud server from the private network, and deleting the eth1 network card of the corresponding server at the same time; and when no any added cloud server exists in the private network, deleting the private network. According to the method and the system for realizing cross-VPC communication based on the cloud scene, the private network is dedicated, the operation is flexible and convenient, the communication barriers of cloud servers in different VPCs can be broken through, and the high efficiency, the safety and the flexibility are ensured.

Description

Technical Field

[0001] The present invention relates to the field of computer network communication technology, and in particular to a method and system for realizing cross-VPC connectivity based on a cloud scenario. Background Art

[0002] In recent years, with the advancement of digital transformation, enterprises' demand for cloud computing and network interconnection has continued to increase. Correspondingly, promoting the deep integration of cloud computing and big data technologies and improving cloud computing infrastructure and service capabilities have received increasing attention from all parties.

[0003] Network interconnection refers to connecting two or more communication networks through certain methods and one or more network communication devices to form a larger network system. The purpose of network interconnection is to enable users in different networks to communicate with each other, share software and data, etc.

[0004] Software Defined Network (SDN) is a new type of network innovation architecture and a way to implement network virtualization. Its core technology OpenFlow separates the control plane and data plane of network devices, thereby achieving flexible control of network traffic, making the network more intelligent and providing a good platform for innovation of core networks and applications.

[0005] With the development of the digital economy, all industries around the world are accelerating their digital transformation. Enterprises and organizations are seeking more flexible, efficient, and secure network solutions to cope with ever-changing business needs and rapidly growing data volumes. Therefore, the present invention proposes a method and system for realizing cross-VPC connectivity based on cloud scenarios. Summary of the invention

[0006] In order to overcome the deficiencies of the prior art, the present invention provides a simple and efficient method and system for realizing cross-VPC connectivity based on cloud scenarios.

[0007] The present invention is achieved through the following technical solutions:

[0008] A method and system for realizing cross-VPC connectivity based on a cloud scenario, comprising the following steps:

[0009] Step S1: Create a collaborative private network

[0010] Create a virtual private network in a special network segment, with the network type of Vxlan, defined as a collaborative private network; add cloud servers that need to communicate with each other to the same private network for communication, so as to achieve communication between cloud servers in different VPCs;

[0011] In step S1, the private network creation process is as follows:

[0012] Step S1.1, create a collaborative private network form, fill in the name, IPv4 network segment and description in the private network form;

[0013] The IPv4 network segment cannot overlap with the VPC network segment that needs to be connected, the external access network segment, or the network segment that is interconnected through peer connections or VPNs.

[0014] Step S1.2: Create a collaborative private network creation request according to the private network form information, and send the request to the server;

[0015] Step S1.3: After receiving the private network creation request sent by the Web page, the server verifies the request parameters;

[0016] Step S1.4, create a Vxlan type network with a custom specified name according to the request parameters of the private network creation request;

[0017] Step S1.5, create a subnet with a custom specified IPv4 network segment under the created Vxlan network;

[0018] Step S1.6, storing the private network information in the database and responding to the Web page;

[0019] Step S1.7: After receiving the response from the server, the web page is refreshed to display the private network information, including ID, name, status, IPv4 network segment, and number of available IPs / total number of IPs.

[0020] Step S2: Cloud server joins the private network

[0021] After the cloud server joins the private network, add an eth1 network card to the cloud server and assign a private network IP;

[0022] The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation.

[0023] In step S2, the process of the cloud server joining the private network is as follows:

[0024] Step S2.1, select a private network and add a cloud server;

[0025] Step S2.2: In the form for adding a cloud server, select the VPC, the subnet under the VPC, and the cloud server under the subnet, create a join request based on the form information, and send the request to the server;

[0026] Step S2.3: After receiving the request sent by the Web page, the server verifies the request parameters;

[0027] Step S2.4, create a port using the private network subnet, and attach the port to the cloud server in the join request as the eth1 network card of the cloud server;

[0028] Step S2.5: store the information of the added cloud server into the database and respond to the web page;

[0029] Step S2.1.3: After receiving the response from the server, the web page is refreshed to display the cloud server information, including the cloud server ID and private network IP address.

[0030] Step S3: The cloud server exits the private network

[0031] When a cloud server exits the private network, the corresponding cloud server is deleted from the private network, and the eth1 network card of the corresponding server is deleted, so that the cloud server loses the ability to communicate with other cloud servers in the private network;

[0032] In step S3, the cloud server exits the private network process as follows:

[0033] Step S3.1, select the cloud server to be exited on the web page, initiate a logout request, and send it to the server;

[0034] Step S3.2: After receiving the exit request, the server deletes the eth1 network card and database record of the corresponding cloud server and responds to the web page;

[0035] Step S3.3: After receiving the response, the web page refreshes the list of cloud servers added to the private network.

[0036] Step S4: Delete the private network

[0037] When there are no cloud servers added to the private network, delete the private network, including cleaning up the underlying OpenStack resources and database resources.

[0038] In step S4, the process of deleting the private network is as follows:

[0039] Step S4.1, select the private network to be deleted on the web page, initiate a deletion request, and send it to the server;

[0040] Step S4.2: After receiving the deletion request, the server deletes the network, subnet and database records of the corresponding private network and responds to the web page;

[0041] Step S4.3: After receiving the response, the web page refreshes the private network list.

[0042] A NAT gateway system based on cloud computing, comprising:

[0043] The private network creation module is responsible for creating a virtual private network in a special network segment. The network type is Vxlan and is defined as a collaborative private network. Cloud servers that need to communicate with each other are added to the same private network for communication to achieve communication between cloud servers in different VPCs. This function provides a network foundation for cross-VPC cloud server network interconnection.

[0044] The cloud server joining module is responsible for adding an eth1 network card to the cloud server after it joins the private network, and assigning a private network IP, such as 12.12.200.34;

[0045] The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation.

[0046] The cloud server exit module is responsible for deleting the corresponding cloud server from the private network when the cloud server exits the private network, and at the same time deleting the eth1 network card of the corresponding server, so that the cloud server loses the ability to communicate with other cloud servers in the private network;

[0047] The private network deletion module is responsible for deleting the private network when there are no cloud servers added to the private network, including cleaning up the underlying OpenStack resources and database resources.

[0048] A device for realizing cross-VPC connectivity based on a cloud scenario, characterized in that it includes a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above-mentioned method steps when executing the computer program.

[0049] A readable storage medium, characterized in that: a computer program is stored on the readable storage medium, and the computer program implements the above method steps when executed by a processor.

[0050] The beneficial effects of the present invention are as follows: the method and system for realizing cross-VPC connectivity based on cloud scenarios have dedicated networks and are flexible and convenient to operate, and can break through the communication barriers of cloud servers in different VPCs, thereby ensuring high efficiency, security and flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0052] Attached Figure 1 This is a schematic diagram of a method for realizing cross-VPC connectivity based on a cloud scenario in the present invention.

[0053] Attached Figure 2 Schematic diagram of the method for adding different private networks to the cloud server of the present invention.

[0054] Attached Figure 3 This is a schematic diagram of the method for the cloud server to exit a private network according to the present invention.

[0055] Attached Figure 4 Schematic diagram of a method for adding different cloud servers to the same private network according to the present invention. DETAILED DESCRIPTION

[0056] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0057] The method for realizing cross-VPC connectivity based on a cloud scenario includes the following steps:

[0058] Step S1: Create a collaborative private network

[0059] Create a virtual private network in a special network segment, with the network type of Vxlan, defined as a collaborative private network; add cloud servers that need to communicate with each other to the same private network for communication, so as to achieve communication between cloud servers in different VPCs;

[0060] In step S1, the private network creation process is as follows:

[0061] Step S1.1, create a collaborative private network form, fill in the name, IPv4 network segment and description in the private network form;

[0062] The IPv4 network segment cannot overlap with the VPC network segment that needs to be connected, the external access network segment, and the network segment that is interconnected through peer connections or VPNs. The recommended network segment is 12.12.200.0 / 24.

[0063] Step S1.2: Create a collaborative private network creation request according to the private network form information, and send the request to the server;

[0064] Step S1.3: After receiving the private network creation request sent by the Web page, the server verifies the request parameters;

[0065] Step S1.4, create a Vxlan type network with a custom specified name according to the request parameters of the private network creation request;

[0066] Step S1.5, create a subnet with a custom specified IPv4 network segment under the created Vxlan network;

[0067] Step S1.6, storing the private network information in the database and responding to the Web page;

[0068] Step S1.7: After receiving the response from the server, the web page is refreshed to display the private network information, including ID, name, status, IPv4 network segment, and number of available IPs / total number of IPs.

[0069] Step S2: Cloud server joins the private network

[0070] After the cloud server joins the private network, add an eth1 network card to the cloud server and assign a private network IP, such as 12.12.200.34;

[0071] The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation.

[0072] In step S2, the process of the cloud server joining the private network is as follows:

[0073] Step S2.1, select a private network, such as private network 1, and add a cloud server;

[0074] Step S2.2: In the form for adding a cloud server, select the VPC, the subnet under the VPC, and the cloud server under the subnet, create a join request based on the form information, and send the request to the server;

[0075] Step S2.3: After receiving the request sent by the Web page, the server verifies the request parameters;

[0076] Step S2.4, create a port using the private network subnet, and attach the port to the cloud server in the join request as the eth1 network card of the cloud server;

[0077] Step S2.5: store the information of the added cloud server into the database and respond to the web page;

[0078] Step S2.1.3: After receiving the response from the server, the web page is refreshed to display the cloud server information, including the cloud server ID and private network IP address.

[0079] Step S3: The cloud server exits the private network

[0080] When a cloud server exits the private network, the corresponding cloud server is deleted from the private network, and the eth1 network card of the corresponding server is deleted, so that the cloud server loses the ability to communicate with other cloud servers in the private network;

[0081] The cloud server exit private network function combined with the cloud server join private network function can easily realize communication and disconnection between cloud servers in multiple VPCs.

[0082] In step S3, the cloud server exits the private network process as follows:

[0083] Step S3.1: Customize and select the cloud server to be exited on the web page, initiate an exit request, and send it to the server;

[0084] Step S3.2: After receiving the exit request, the server deletes the eth1 network card and database record of the corresponding cloud server and responds to the web page;

[0085] Step S3.3: After receiving the response, the web page refreshes the list of cloud servers added to the private network.

[0086] Step S4: Delete the private network

[0087] When there are no cloud servers added to the private network, delete the private network, including cleaning up the underlying OpenStack resources and database resources.

[0088] In step S4, the process of deleting the private network is as follows:

[0089] Step S4.1, select the private network to be deleted on the web page, initiate a deletion request, and send it to the server;

[0090] Step S4.2: After receiving the deletion request, the server deletes the network, subnet and database records of the corresponding private network and responds to the web page;

[0091] Step S4.3: After receiving the response, the web page refreshes the private network list.

[0092] The cloud computing-based NAT gateway system includes:

[0093] The private network creation module is responsible for creating a virtual private network in a special network segment. The network type is Vxlan and is defined as a collaborative private network. Cloud servers that need to communicate with each other are added to the same private network for communication to achieve communication between cloud servers in different VPCs. This function provides a network foundation for cross-VPC cloud server network interconnection.

[0094] The cloud server joining module is responsible for adding an eth1 network card to the cloud server after it joins the private network, and assigning a private network IP, such as 12.12.200.34;

[0095] The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation.

[0096] The cloud server exit module is responsible for deleting the corresponding cloud server from the private network when the cloud server exits the private network, and at the same time deleting the eth1 network card of the corresponding server, so that the cloud server loses the ability to communicate with other cloud servers in the private network;

[0097] The private network deletion module is responsible for deleting the private network when there are no cloud servers added to the private network, including cleaning up the underlying OpenStack resources and database resources.

[0098] The device for implementing cross-VPC connectivity based on a cloud scenario includes a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above method steps when executing the computer program.

[0099] The readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method steps are implemented.

[0100] Compared with the prior art, the method and system for realizing cross-VPC connectivity based on cloud scenarios have the following characteristics:

[0101] 1) A virtual private network with a special network segment is provided as a private network, which is dedicated to the private network.

[0102] 2) It provides a flexible and fast way to join and leave a private network.

[0103] 3) Supports intercommunication between cloud servers in multiple VPCs, breaking down the communication barriers between cloud servers in different VPCs.

[0104] 4) Realizes the functions of dynamic network topology and traffic scheduling.

[0105] 5) It provides the function of flexible configuration and management of the network, ensuring efficiency, security and flexibility.

[0106] The embodiment described above is only one specific implementation of the present invention. Common changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for realizing cross-VPC connectivity based on a cloud scenario, characterized in that: The following steps are involved: Step S1: Create a collaborative private network Create a virtual private network in a special network segment, with the network type of Vxlan, defined as a collaborative private network; add cloud servers that need to communicate with each other to the same private network for communication, so as to achieve communication between cloud servers in different VPCs; Step S2: Cloud server joins the private network After the cloud server joins the private network, add an eth1 network card to the cloud server and assign a private network IP; The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation. Step S3: The cloud server exits the private network When a cloud server exits the private network, the corresponding cloud server is deleted from the private network, and the eth1 network card of the corresponding server is deleted, so that the cloud server loses the ability to communicate with other cloud servers in the private network; Step S4: Delete the private network When there are no cloud servers added to the private network, delete the private network, including cleaning up the underlying OpenStack resources and database resources.

2. The NAT gateway method based on cloud computing according to claim 1, characterized in that: In the step S1, The process of creating a private network is as follows: Step S1.1, create a collaborative private network form, fill in the name, IPv4 network segment and description in the private network form; The IPv4 network segment cannot overlap with the VPC network segment that needs to be connected, the external access network segment, or the network segment that is interconnected through peer connections or VPNs. Step S1.2: Create a collaborative private network creation request according to the private network form information, and send the request to the server; Step S1.3: After receiving the private network creation request sent by the Web page, the server verifies the request parameters; Step S1.4, create a Vxlan type network with a custom specified name according to the request parameters of the private network creation request; Step S1.5, create a subnet with a custom specified IPv4 network segment under the created Vxlan network; Step S1.6, storing the private network information in the database and responding to the Web page; Step S1.7: After receiving the response from the server, the web page is refreshed to display the private network information, including ID, name, status, IPv4 network segment, and number of available IPs / total number of IPs.

3. The NAT gateway method based on cloud computing according to claim 1, characterized in that: In the step S2, The process of cloud server joining the private network is as follows: Step S2.1, select a private network and add a cloud server; Step S2.2: In the form for adding a cloud server, select the VPC, the subnet under the VPC, and the cloud server under the subnet, create a join request based on the form information, and send the request to the server; Step S2.3: After receiving the request sent by the Web page, the server verifies the request parameters; Step S2.4, create a port using the private network subnet, and attach the port to the cloud server in the join request as the eth1 network card of the cloud server; Step S2.5: store the information of the added cloud server into the database and respond to the web page; Step S2.1.3: After receiving the response from the server, the web page is refreshed to display the cloud server information, including the cloud server ID and private network IP address.

4. The NAT gateway method based on cloud computing according to claim 1, characterized in that: In the step S3, The process of the cloud server exiting the private network is as follows: Step S3.1: Customize and select the cloud server to be exited on the web page, initiate an exit request, and send it to the server; Step S3.2: After receiving the exit request, the server deletes the eth1 network card and database record of the corresponding cloud server and responds to the web page; Step S3.3: After receiving the response, the web page refreshes the list of cloud servers added to the private network.

5. The NAT gateway method based on cloud computing according to claim 1, characterized in that: In the step S4, The process of deleting a private network is as follows: Step S4.1, select the private network to be deleted on the web page, initiate a deletion request, and send it to the server; Step S4.2: After receiving the deletion request, the server deletes the network, subnet and database records of the corresponding private network and responds to the web page; Step S4.3: After receiving the response, the web page refreshes the private network list.

6. A NAT gateway system based on cloud computing, characterized in that: include: The private network creation module is responsible for creating a virtual private network in a special network segment. The network type is Vxlan and is defined as a collaborative private network. Add cloud servers that need to communicate with each other to the same private network to achieve communication between cloud servers in different VPCs; The cloud server joining module is responsible for adding an eth1 network card to the cloud server and allocating a private network IP after the cloud server joins the private network. The eth1 network cards of cloud servers in different VPCs of the same private network belong to the same virtual private network. Cloud servers in different VPCs use eth1 network cards to achieve cross-VPC connectivity. Different private networks are isolated from each other to ensure security and isolation. The cloud server exit module is responsible for deleting the corresponding cloud server from the private network when the cloud server exits the private network, and at the same time deleting the eth1 network card of the corresponding server, so that the cloud server loses the ability to communicate with other cloud servers in the private network; The private network deletion module is responsible for deleting the private network when there are no cloud servers added to the private network, including cleaning up the underlying OpenStack resources and database resources.

7. A device for realizing cross-VPC connectivity based on a cloud scenario, characterized in that: The method comprises a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the method according to any one of claims 1 to 5 when executing the computer program.

8. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images