A network construction method, device, electronic device and storage medium

Abstract

The present application provides a network construction method, apparatus, electronic device, and storage medium. The method includes: obtaining a plurality of data centers and determining the network address segments of each data center; generating an inter-data-center network according to the data centers and the network address segments of each data center; the address pool of the inter-data-center network is the sum of the network address segments of the plurality of data centers; constructing a node network based on the inter-data-center network; wherein, the address pool of the node network is reused with the address pool of the inter-data-center network. By constructing a node network on the network architecture across data centers and reusing the address pool of the node network with the address pool of the inter-data-center network, problems such as insufficient resources of the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments of each data center are improved, and the system stability is enhanced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly, to a network construction method, apparatus, electronic device, and storage medium. Background Art

[0002] With the continuous development of cloud technology, various cloud computing models such as public cloud and private cloud have emerged. Some complex services usually require the construction of a hybrid cloud architecture of multiple models. In the traditional hybrid cloud model, the clouds of multiple data centers are interconnected to achieve the goal of the hybrid cloud. This model will cause problems such as insufficient address pools or address pool conflicts, and the system risk is relatively high. Summary of the Invention

[0003] The purpose of the embodiments of the present invention is to provide a network construction method, apparatus, electronic device, and storage medium, which can effectively solve the problems of insufficient address pool resources or address pool conflicts by constructing a multi-layer network architecture across data centers, and improve system stability.

[0004] In a first aspect, an embodiment of the present application provides a network construction method, including: obtaining a plurality of data centers, and determining the network address segment of each data center; generating a cross-data center network according to the data centers and the network address segment of each data center; the address pool of the cross-data center network is the sum of the network address segments of the plurality of data centers; constructing a node network based on the cross-data center network; wherein, the address pool of the node network is multiplexed with the address pool of the cross-data center network.

[0005] In the above implementation process, by constructing a node network on the network architecture across data centers, the address pool of the node network is multiplexed with the address pool of the cross-data center network, improving problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments of each data center, and improving system stability.

[0006] Optionally, in an embodiment of the present application, the method further includes: receiving the address information of the node network through a forwarding database configuration center; generating a node network address forwarding table according to the address information of the node network; forwarding the first data according to the node network address forwarding table.

[0007] In the above implementation process, the forwarding database configuration center dynamically senses network changes, generates a node network address forwarding table, and forwards the first data according to the node network address forwarding table, without broadcasting to each port to find the destination address, reducing the impact of broadcast storms on services.

[0008] Optionally, in the embodiments of the present application, generating an inter-data center network according to the data centers and the network address segments of each data center includes: obtaining the dedicated network corresponding to each data center; accessing the data center to a unified routing center through the dedicated network corresponding to the data center to generate an inter-data center network; the inter-data center network is used for data exchange between data centers.

[0009] In the above implementation process, the data center accesses the data center to a unified routing center through the dedicated network corresponding to the data center to generate an inter-data center network, constructs the data centers of heterogeneous networks into an inter-data center network, and realizes data exchange between data centers.

[0010] Optionally, in the embodiments of the present application, after constructing a node network based on the inter-data center network, the method further includes: constructing a container network based on the node network; the container network is used for communication inside and between containers; the address pool of the container network is reused with the address pool of the node network.

[0011] In the above implementation process, the data centers of heterogeneous networks are constructed into an inter-data center network. By constructing a node network on the network architecture of the inter-data center, the address pool of the node network is reused with the address pool of the inter-data center network, and by constructing a container network on the node network, a homogeneous network with the same attributes is generated through the data centers of heterogeneous networks, improving problems such as insufficient resources of the data center network address pool, network address conflicts, and difficulty in separating and managing the network address segments of each data center, and improving system stability.

[0012] Optionally, in the embodiments of the present application, the method further includes: receiving the address information of the container network through a forwarding database configuration center; generating a container network address forwarding table according to the address information of the container network; forwarding the second data according to the container network address forwarding table.

[0013] In the above implementation process, the forwarding database configuration center dynamically senses network changes to generate a container network address forwarding table, and forwards the second data according to the container network address forwarding table, without broadcasting to each port to find the destination address, reducing the impact of broadcast storms on services.

[0014] Optionally, in the embodiments of the present application, the method further includes: generating a centralized switching network based on the inter-data center network, the node network, and the container network.

[0015] In the above implementation process, based on a three-layer network including a cross-data center network, a two-layer node network, and a one-layer container network, a centralized switching network is generated to implement generating a homogeneous network with the same attributes through a data center with heterogeneous networks, improving problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments in each data center network, and enhancing system stability.

[0016] Optionally, in the embodiments of the present application, the network address segments of multiple data centers do not contain each other.

[0017] In the above implementation process, the network address segments of multiple data centers do not contain each other. The address pool of the node network is reused with the address pool of the cross-data center network, and the address pool of the container network is reused with the address pool of the node network, improving problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments in each data center network.

[0018] In a second aspect, an embodiment of the present application further provides a network construction device, including: an acquisition module for acquiring multiple data centers and determining the network address segment of each data center; a cross-data network module for generating a cross-data center network according to the data centers and the network address segment of each data center; the address pool of the cross-data center network is the sum of the network address segments of multiple data centers; a node network construction module for constructing a node network based on the cross-data center network; wherein, the address pool of the node network is reused with the address pool of the cross-data center network.

[0019] In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor and a memory, the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method described above is executed.

[0020] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, the method described above is executed.

[0021] By using the network construction method, device, electronic device, and storage medium provided by the present application, by constructing a node network on the network architecture across data centers, the address pool of the node network is reused with the address pool of the cross-data center network, and by generating a homogeneous network with the same attributes through a data center with heterogeneous networks, problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments in each data center network are improved, and system stability is enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] To more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings required for the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application, and thus should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other related drawings can also be obtained based on these drawings.

[0023] Figure 1 A schematic flowchart of a network construction method provided by an embodiment of the present application;

[0024] Figure 2 A schematic diagram of a method for implementing a two-layer network multi-data center hybrid cloud provided by an embodiment of the present application;

[0025] Figure 3 A schematic structural diagram of a network construction device provided by an embodiment of the present application;

[0026] Figure 4 A schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0027] The following will describe in detail the embodiments of the technical solutions of the present application with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solutions of the present application, and thus are only examples and cannot be used to limit the protection scope of the present application.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the present application.

[0029] In the description of the embodiments of the present application, technical terms such as "first" and "second" are only used to distinguish different objects and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity, specific order or primary-secondary relationship of the indicated technical features. In the description of the embodiments of the present application, "a plurality" means two or more, unless otherwise specifically defined.

[0030] Please refer to Figure 1 The schematic flowchart of a network construction method provided by an embodiment of the present application shown. The network construction method provided by an embodiment of the present application can be applied to an electronic device, and the electronic device can include a terminal and a server; where the terminal can specifically be a smart phone, a tablet computer, a computer, a personal digital assistant (Personal Digital Assistant, PDA), etc.; the server can specifically be an application server or a Web server. The network construction method can include the following steps:

[0031] Step S110: Obtain multiple data centers and determine the network address segments of each data center.

[0032] Obtain multiple data centers for building a network. Here, a data center is a physical facility that supports enterprise computing activities and realizes centralized processing, storage, transmission, exchange, and management of information. A data center architecture is an architectural design that establishes connections between switches and servers. A data center can be a cloud data center, and data centers include private clouds, public clouds, industry clouds, and self-built data centers, etc.

[0033] Determine the network address segments of each data center. For example, if it is necessary to build an inter-data-center network on four data center architectures of private cloud, public cloud, industry cloud, and self-built data center, then respectively plan the network address segments of the private cloud data center, the public cloud data center, the self-built data center, and the industry cloud data center.

[0034] It should be noted that there should be no inclusion relationship or conflict among the planned network address segments of the four data centers. The network address segment is the network address range, and the network address segment of the data center can be determined according to actual needs. As an optional implementation manner, the network address segment of the private cloud data center can be 10.168.2.0 / 24, the network address segment of the public cloud data center can be 192.168.3.0 / 24, the network address segment of the self-built data center can be 172.16.2.0 / 24, the network address segment of the industry cloud data center can be 172.16.3.0 / 24, and the network address segment of the data center can also be other data, which is not limited in the embodiments of the present application.

[0035] Step S120: Generate an inter-data-center network according to the data centers and the network address segments of each data center; the address pool of the inter-data-center network is the sum of the network address segments of multiple data centers.

[0036] Each data center accesses the unified routing center through a dedicated network, for example, accesses the unified routing center through a VPN (Virtual Private Network) or a network dedicated line. The unified routing center provides scalable enterprise-level routing and distribution functions. Multiple data centers achieve centralized data exchange in the unified routing center, and generate an inter-data-center network with the unified routing center according to the accessed data centers. The address pool of the inter-data-center network is the sum of the network address segments of the data centers that build the inter-data-center network.

[0037] Step S130: Build a node network based on the inter-data-center network; where the address pool of the node network is reused with the address pool of the inter-data-center network.

[0038] Building a node network based on a cross-data center network can be called an overlay network. An overlay network is a network that runs on top of one or more existing networks, providing specific additional functionality. An overlay network alters the performance, functionality, or characteristics of the underlying network in one or more ways. Overlay networks and underlay networks are relative terms. An overlay network uses network virtualization technology to build one or more virtual logical networks on the same underlay network.

[0039] Because the overlay network layer is an independent network layer, the address pool of the underlay network can be reused without conflict. In the embodiment of the present application, the cross-data center network is an underlay network, and a node network is constructed on the cross-data center network. The address pool of the node network is reused with the address pool of the cross-data center network.

[0040] Based on the cross-data center network, the node network can be built in a cloud-native environment. Cloud-native is a method of building and running applications. Cloud-native emphasizes that the initial development is for ultimate deployment in a cloud environment. In dynamic environments such as public clouds, private clouds, and hybrid clouds, organizations or enterprises can build and deploy elastically scalable applications.

[0041] In the above implementation process, by building a node network on the cross-data center network architecture, the address pool of the node network is reused with the address pool of the cross-data center network, thereby improving problems such as insufficient data center network address pool resources, network address conflicts, and difficult management of separate address segments of each data center network, thereby improving system stability.

[0042] Optionally, in an embodiment of the present application, the method further includes: receiving address information of the node network through a forwarding database configuration center; generating a node network address forwarding table based on the address information of the node network; and forwarding the first data based on the node network address forwarding table.

[0043] In specific implementations, if port forwarding data within a node network uses broadcasting, it can waste resources and even cause broadcast storms. A broadcast storm occurs when broadcast data overwhelms the network, consuming significant bandwidth and disrupting normal business operations. A broadcast occurs when a data frame or packet is transmitted to every node on a node network segment. Due to network topology design, connectivity issues, or other reasons, broadcasts can replicate and propagate data frames across the segment, degrading network performance.

[0044] To avoid broadcast storms, the data forwarding is made more targeted through the forwarding database configuration center. Specifically, for example, the FDB (Forwarding DataBase) configuration center can dynamically sense network changes, generate a node network address forwarding table based on the address information received from the node network, and forward the first data according to the node network address forwarding table.

[0045] The node network address forwarding table may include information such as the source address, vlan (Virtual Local Area Network), and port of the first data. By querying the destination address of the first data through the node network address forwarding table, it can be directly forwarded through the port corresponding to the destination address, without the need to broadcast to each port to find the destination address. If the forwarding database configuration center receives network changes, it will update the node network address forwarding table, and by refreshing the node network address forwarding table in real time, the impact of broadcast storms on services can be reduced.

[0046] In the above implementation process, the forwarding database configuration center dynamically senses network changes, generates a node network address forwarding table, and forwards the first data according to the node network address forwarding table, without the need to broadcast to each port to find the destination address, reducing the impact of broadcast storms on services.

[0047] Optionally, in the embodiments of the present application, a cross-data center network is generated according to the data center and the network address segment of each data center, including: obtaining the dedicated network corresponding to each data center; connecting the data center to a unified routing center through the dedicated network corresponding to the data center to generate a cross-data center network; the cross-data center network is used for data exchange between data centers.

[0048] In the specific implementation process: obtain the dedicated network corresponding to each data center, and the dedicated network can be a VPN (Virtual Private Network) or a network dedicated line. Connect the data center to a unified routing center through the dedicated network corresponding to the data center, and multiple data centers achieve centralized data exchange in the unified routing center, and a cross-data center network is generated according to the connected data centers by the unified routing center.

[0049] The cross-data center network refers to integrating the computing environments of various platforms and data centers. Specifically, for example, the cross-data center network is a combination of cloud platforms and cloud service resources provided by cloud service providers.

[0050] In an optional embodiment, the cross-data center network can be a three-layer network, and the node network constructed based on the cross-data center network is a two-layer network.

[0051] In the above implementation process, the data center accesses the unified routing center through the dedicated network corresponding to the data center, generates a cross-data center network, constructs the data centers with heterogeneous networks into a cross-data center network, and realizes the data exchange of the data center.

[0052] Optionally, in the embodiment of the present application, after constructing the node network based on the cross-data center network, the method further includes: constructing a container network based on the node network; the container network is used for communication inside and between containers; the address pool of the container network and the address pool of the node network are multiplexed.

[0053] In the specific implementation process: constructing a container network on top of the node network, the specific implementation methods include SDN (Software Defined Network), such as vxlan (Network Virtualization Technology). The container network is used for communication inside and between containers.

[0054] The container network also belongs to the overlay network, so it can continue to reuse the same IP segment with the underlying overlay and underlay networks, and there will be no communication anomalies caused by network address segment conflicts. The underlying overlay is the node network, and the underlay network is the cross-data center network.

[0055] Although different Overlay networks share the devices and lines in the Underlay network, the services in the Overlay network are decoupled from the physical networking and interconnection technologies in the Underlay network. The multi-instantiation of the Overlay network can serve different services of the same tenant, such as multiple departments, or different tenants.

[0056] A container is a more lightweight isolation method than a virtual machine, mainly through namespace (namespace) and cgroup (control group) technologies for resource isolation. Namespace is used for isolation in naming, and cgroup is responsible for isolation in terms of applications. The way the container network connects to the physical network is very similar to that of a virtual machine, and containers on a physical machine can access each other through bridging, and the way to access the external network is, for example, NAT.

[0057] Continuing with the above embodiment, the cross-data center network is a three-layer network, the node network constructed based on the cross-data center network is a two-layer network, and the container network constructed on top of the node network can be a one-layer container network.

[0058] In the above implementation process, the data centers of heterogeneous networks are constructed into a cross-data center network. By constructing a node network on the cross-data center network architecture, the address pool of the node network is multiplexed with the address pool of the cross-data center network, and a container network is constructed on the node network, so as to generate a homogeneous network with the same attributes from the data centers of heterogeneous networks, improve problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments in each data center network, and improve the system stability.

[0059] Optionally, in the embodiment of the present application, the method further includes: receiving the address information of the container network through the forwarding database configuration center; generating a container network address forwarding table according to the address information of the container network; and forwarding the second data according to the container network address forwarding table.

[0060] In the specific implementation process: when forwarding data on the container network, if the destination address is searched through broadcast, it will cause the entire network traffic to be occupied by broadcast packets, and other service traffic cannot be normally forwarded.

[0061] The forwarding database configuration center makes data forwarding more targeted. Specifically, for example, the FDB (Forwarding DataBase) configuration center can dynamically sense network changes, receive the address information of the container network, generate a container network address forwarding table according to the address information of the container network, and forward the second data according to the container network address forwarding table.

[0062] The container network address forwarding table can include information such as the source address, vlan, and port of the second data. By querying the destination address of the second data through the container network address forwarding table, it can be directly forwarded through the port corresponding to the destination address, without broadcasting to each port to find the destination address. If the forwarding database configuration center receives a change in the container network, it will update the container network address forwarding table, and by refreshing the container network address forwarding table in real time, the impact of the broadcast storm on the service can be reduced.

[0063] In the above implementation process, the forwarding database configuration center dynamically senses network changes, generates a container network address forwarding table, and forwards the second data according to the container network address forwarding table, without broadcasting to each port to find the destination address, reducing the impact of the broadcast storm on the service.

[0064] Optionally, in the embodiment of the present application, the method further includes: generating a centralized switching network based on the cross-data center network, the node network, and the container network.

[0065] In the specific implementation process: there are four data centers, namely private cloud, public cloud, industry cloud, and self-built data center. The four data centers are connected to a unified routing center in the form of a private network, and centralized data exchange is realized in the unified routing center to build a three-layer network across data centers. A two-layer network architecture, that is, a node network, is built in the cloud-native environment. A container network is built on top of the node network.

[0066] The unified routing center generates a centralized exchange network based on the three-layer network across data center networks, two-layer node networks, and one-layer container networks.

[0067] In the above implementation process, a centralized exchange network is generated based on the three-layer network across data center networks, two-layer node networks, and one-layer container networks, so as to generate a homogeneous network with the same attributes from data centers through heterogeneous networks, and improve problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments of each data center, and improve system stability.

[0068] Optionally, in the embodiments of the present application, the network address segments of multiple data centers do not contain each other.

[0069] In the specific implementation process: the network address segments of multiple data centers are planned respectively. For example, the network address segments of the private cloud, public cloud, industry cloud, and self-built data center, then the network address segments of the private cloud, public cloud, industry cloud, and self-built data center do not contain each other or the network address segments do not conflict.

[0070] In the above implementation process, the network address segments of multiple data centers do not contain each other, the address pool of the node network is reused with the address pool of the network across data centers, and the address pool of the container network is reused with the address pool of the node network, improving problems such as insufficient resources in the data center network address pool, network address conflicts, and difficulty in managing the separation of network address segments of each data center.

[0071] Please refer to Figure 2 the schematic diagram of the implementation method of the two-layer network multi-data center hybrid cloud provided by the embodiments of the present application shown.

[0072] In an optional embodiment, there are four data center architectures: private cloud, public cloud, self-built data center, and industry cloud. The network address segment of each data center is determined. The network address segment of the private cloud data center is 10.168.2.0 / 24, the network address segment of the public cloud data center is 192.168.3.0 / 24, the network address segment of the self-built data center is 172.16.2.0 / 24, and the network address segment of the industry cloud data center is 172.16.3.0 / 24. There cannot be network address segment inclusion or conflict among the four data centers.

[0073] Four data centers are connected to the unified routing center in the manner of a private network, and centralized data exchange is realized in the unified routing center. A three-layer network across data centers is constructed. Among them, the network address pool of the three-layer network across data centers is the sum of the address segments of the four planned data centers, and the network address pool of the three-layer network across data centers can be 172.16.0.0 / 24.

[0074] In the cloud-native environment, a two-layer node network architecture based on the three-layer network is constructed, which is called the overlay network. The overlay network layer is an independent network layer, which can reuse the address pool of the underlay network without conflict. The underlay network is the three-layer network across data centers. As Figure 2 shown, the address pool of the node network can be 172.16.0.0 / 24, and the node network can include n nodes.

[0075] In the layer of the node network, due to cross-data center interactions, problems such as ARP broadcast storms will occur, resulting in a decline in network performance. The FDB configuration center dynamically senses network changes and refreshes the address forwarding table in real time, making data forwarding more targeted, avoiding packets from looking for the destination address in the form of broadcast, and reducing the impact of broadcast storms on services.

[0076] A container network is constructed on top of the node network for communication within and between containers. The container network also belongs to the overlay network, so it can continue to reuse the same IP segment as the underlying overlay and underlay networks without communication anomalies due to network conflicts. The IP segment of the container network can be 172.16.0.0 / 24, and the container network can include n containers.

[0077] The container network is also connected to the FDB configuration center to sense changes in the two-layer network and refresh the address forwarding table in real time, avoiding packets from looking for the destination address in the form of broadcast, and reducing the impact of broadcast storms on services.

[0078] The unified routing center constructs a centralized switching network across regions and data centers based on the cross-data center network, the node network, and the container network.

[0079] Please refer to Figure 3 the structural schematic diagram of the network construction device provided by the embodiment of the present application shown; The embodiment of the present application provides a network construction device 200, including:

[0080] An obtaining module 210, configured to obtain a plurality of data centers and determine the network address segment of each data center;

[0081] The cross-data network module 220 is used to generate a cross-data center network based on the data centers and the network address segments of each data center; the address pool of the cross-data center network is the sum of the network address segments of multiple data centers;

[0082] The node network construction module 230 is used to construct a node network based on the cross-data center network; wherein the address pool of the node network is multiplexed with the address pool of the cross-data center network.

[0083] Optionally, in an embodiment of the present application, the network construction device also includes: a first forwarding database module, used to receive address information of the node network through a forwarding database configuration center; generate a node network address forwarding table based on the address information of the node network; and forward the first data based on the node network address forwarding table.

[0084] Optionally, in an embodiment of the present application, the network construction device, the cross-data network module 220, is specifically used to obtain the proprietary network corresponding to each data center; through the proprietary network corresponding to the data center, the data center is connected to the unified routing center to generate a cross-data center network; the cross-data center network is used for data exchange between data centers.

[0085] Optionally, in an embodiment of the present application, the network construction device, the container network construction module, is used to build a container network based on the node network; the container network is used for communication within the container and between containers; the address pool of the container network is reused with the address pool of the node network.

[0086] Optionally, in an embodiment of the present application, the network construction device, the second forwarding database module, is used to receive the address information of the container network through the forwarding database configuration center; generate a container network address forwarding table based on the address information of the container network; and forward the second data according to the container network address forwarding table.

[0087] Optionally, in an embodiment of the present application, the network construction device, the switching network module, is used to generate a centralized switching network based on a cross-data center network, a node network, and a container network.

[0088] Optionally, in an embodiment of the present application, a network construction device, wherein the network address segments of multiple data centers do not contain each other.

[0089] It should be understood that the device corresponds to the above-mentioned network construction method embodiment and can perform each step involved in the above-mentioned method embodiment. The specific functions of the device can be found in the description above. To avoid repetition, a detailed description is appropriately omitted here. The device includes at least one software function module that can be stored in a memory in the form of software or firmware or fixed in the operating system (OS) of the device.

[0090] Please refer to Figure 4 the schematic structural diagram of the electronic device provided by the embodiment of the present application shown. An electronic device 300 provided by an embodiment of the present application includes: a processor 310 and a memory 320. The memory 320 stores machine-readable instructions executable by the processor 310. When the machine-readable instructions are executed by the processor 310, the above method is executed.

[0091] An embodiment of the present application also provides a storage medium. A computer program is stored on the storage medium. When the computer program is run by a processor, the above method is executed.

[0092] Among them, the storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (abbreviated as SRAM), electrically erasable programmable read-only memory (abbreviated as EEPROM), erasable programmable read-only memory (abbreviated as EPROM), programmable read-only memory (abbreviated as PROM), read-only memory (abbreviated as ROM), magnetic memory, flash memory, magnetic disk or optical disc.

[0093] In several embodiments provided by the embodiments of the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the drawings show the possible architectures, functions, and operations of devices, methods, and computer program products according to multiple embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code. The module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0094] In addition, in each embodiment of the present application, each functional module may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.

[0095] The above description is only an optional implementation manner of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the embodiments of the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the embodiments of the present application.

Claims

1. A network construction method, characterized in that, including: Obtain multiple data centers and determine the network address segments of each of the data centers; Generate an inter-data center network according to the data centers and the network address segments of each data center; the address pool of the inter-data center network is the sum of the network address segments of the multiple data centers; Construct a node network based on the inter-data center network; wherein, the address pool of the node network is multiplexed with the address pool of the inter-data center network.

2. The method according to claim 1, wherein The method further includes: Receive the address information of the node network through a forwarding database configuration center; generate a node network address forwarding table according to the address information of the node network; Forward the first data according to the node network address forwarding table.

3. The method according to claim 1, wherein Generating an inter-data center network according to the data centers and the network address segments of each data center includes: Obtain the dedicated network corresponding to each of the data centers; Connect the data center to a unified routing center through the dedicated network corresponding to the data center to generate an inter-data center network; the inter-data center network is used for data exchange between the data centers.

4. The method according to claim 1, wherein After constructing a node network based on the inter-data center network, the method further includes: Construct a container network based on the node network; the container network is used for communication inside and between containers; the address pool of the container network is multiplexed with the address pool of the node network.

5. The method according to claim 4, characterized in that The method further includes: Receive the address information of the container network through a forwarding database configuration center; generate a container network address forwarding table according to the address information of the container network; Forward the second data according to the container network address forwarding table.

6. The method according to claim 4, wherein The method further includes: Generate a centralized switching network based on the inter-data center network, the node network, and the container network.

7. The method according to any one of claims 1-6, characterized in that, Wherein, The network address segments of the multiple data centers do not contain each other.

8. A network construction device, characterized in that, including: An obtaining module, configured to obtain multiple data centers and determine the network address segments of each of the data centers; An inter-data network module, configured to generate an inter-data center network according to the data centers and the network address segments of each data center; the address pool of the inter-data center network is the sum of the network address segments of the multiple data centers; A node network construction module, configured to construct a node network based on the inter-data center network; wherein, the address pool of the node network is multiplexed with the address pool of the inter-data center network.

9. An electronic device, characterized in that, including: A processor and a memory, the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is executed.

10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is run by a processor, the method according to any one of claims 1 to 7 is executed.

Images