A cloud data center-oriented network virtualization implementation method, device, equipment and storage medium

Abstract

The application discloses a cloud data center-oriented network virtualization implementation method and device, equipment and a storage medium, relates to the field of cloud computing, and is applied to a cloud computing management platform and comprises the following steps: allocating corresponding target addresses to target devices based on the device types of the target devices of a cloud data center; announcing the target addresses of first network devices to all network devices based on a preset routing switching mechanism to determine full-network topology information of the cloud data center; the network devices comprise the first network devices and second network devices; the first network devices are leaf switches, and the second network devices are spine switches; determining the topology relationship between a source server and a destination server based on a target message by using the full-network topology information and an identifier mapping table, so that the target message is forwarded to the destination server by the first network devices and the second network devices based on the topology relationship. The application improves the overall transmission efficiency of the virtualization technology in a large-scale cloud data center environment.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of cloud computing, and particularly relates to a cloud data center-oriented network virtualization implementation method and device, equipment and a storage medium. BACKGROUND

[0002] Traditional cloud data centers usually rely on network virtualization schemes based on tunnel encapsulation (such as VXLAN (Virtual Extensible Local Area Network), NVGRE (Network Virtualization using Generic Routing Encapsulation), etc.). These methods, although to some extent, realize network isolation and multi-tenant support, but due to the need for packet encapsulation and forwarding at a higher protocol layer (network layer or transport layer), significant CPU processing overhead, encapsulation header overhead, and increased network delay are brought.

[0003] In summary, how to improve the overall transmission efficiency of virtualization technology in a large-scale cloud data center environment is a problem to be solved at present. SUMMARY

[0004] Therefore, the purpose of the present application is to provide a cloud data center-oriented network virtualization implementation method, device, equipment and storage medium, which can improve the overall transmission efficiency of virtualization technology in a large-scale cloud data center environment. The specific scheme is as follows:

[0005] In a first aspect, the present application discloses a cloud data center-oriented network virtualization implementation method, applied to a cloud computing management platform, comprising:

[0006] Based on the device type of each target device of the cloud data center, a corresponding target address is allocated to each target device; the device type includes a network device and an edge virtual network; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device;

[0007] Based on a preset routing exchange mechanism, the target address of each first network device is announced to all network devices to determine the full network topology information of the cloud data center; the network device includes the first network device and a second network device; the first network device is a leaf switch, and the second network device is a spine switch;

[0008] The full-network topology information and the pre-acquired identity mapping table are used to determine the topology relationship between the corresponding source server and the destination server based on the target message, so that the target message is forwarded to the destination server by the first network device and the second network device based on the topology relationship.

[0009] Optionally, the full-network topology information of the cloud data center is determined by announcing the target address of each first network device to all the network devices based on the preset routing exchange mechanism, comprising:

[0010] All target second network devices corresponding to each first network device are determined; the target second network device is a second network device connected to the first network device;

[0011] A neighbor relationship is established between each first network device and the corresponding target second network device;

[0012] The first address of the first network device is announced to the corresponding target second network device, so that the routing information of the first network device is recorded to the local routing table of the target second network device by using the target second network device, and the routing information is forwarded to other first network devices having a neighbor relationship with the target second network device, and the routing information is recorded in the local routing table of the other first network devices;

[0013] The full-network topology information of the cloud data center is determined based on all the routing information.

[0014] Optionally, the identity mapping table is used to record the mapping relationship between the MAC address of the cloud server in the virtual network inside the current cloud data center and the first address of the first network device corresponding to the cloud server.

[0015] Optionally, the network virtualization method for cloud data center also includes:

[0016] If a cloud server startup request is acquired, a target edge server is determined based on the cloud server startup request by using a preset server scheduling strategy;

[0017] A target cloud server corresponding to the cloud server startup request is created and started on the target edge server, and the target cloud server is mounted to the corresponding target edge virtual network;

[0018] The virtual network information and the MAC address information corresponding to the target cloud server are announced to a first edge network device, so that the first edge network device sends the triple information corresponding to the target cloud server to a second edge network device;

[0019] sending, by the second edge network device, the triple information to other first network devices having a neighbor relationship with the second edge network device and storing the triple information into the identifier mapping table local to the other first network devices having a neighbor relationship with the second edge network device;

[0020] The first edge network device is the first network device corresponding to the target edge server, the second edge network device is the second network device having a neighbor relationship with the first edge network device, and the triple information includes virtual network information corresponding to the target cloud server, MAC address information corresponding to the target cloud server, and the first address of the first edge network device.

[0021] Optionally, the determining, based on the target message, a topology relationship between the source server and the destination server by using the whole-network topology information and the pre-acquired identifier mapping table comprises:

[0022] sending, by the source server, a target message to the first network device corresponding to the source server; the target message is a message encapsulated in a VLAN format;

[0023] processing, by the first network device corresponding to the source server, the target message to extract a second address in the target message from an outer Ethernet header of the target message;

[0024] determining, based on the whole-network topology information and the pre-acquired identifier mapping table, the first network device corresponding to the destination server of the target message to determine the topology relationship between the source server and the destination server;

[0025] The topology relationship includes a first topology relationship, a second topology relationship, and a third topology relationship; the first topology relationship is that the source server and the destination server are located in the same edge server, the second topology relationship is that the source server and the destination server are located in different edge servers of the same first network device, and the third topology relationship is that the source server and the destination server are located in different edge servers of different first network devices.

[0026] Optionally, the forwarding, by the first network device and the second network device, the target message to the destination server based on the topology relationship comprises:

[0027] If the topology relationship between the source server and the destination server is the first topology relationship, the target message is directly forwarded in the edge servers corresponding to the source server and the destination server;

[0028] if the topological relationship between the source server and the destination server is a second topological relationship, the target message is forwarded to the edge server corresponding to the destination server by the first network device corresponding to the source server, so that the outer encapsulation of the target message is removed by the edge server corresponding to the destination server, and the obtained inner target message is forwarded to the destination server;

[0029] if the topological relationship between the source server and the destination server is a third topological relationship, the inner message of the target message is taken out by the first network device corresponding to the source server, and the inner message is encapsulated based on a first preset message encapsulation format to obtain a new target message; the new target message is forwarded hop by hop to the first network device corresponding to the destination server, so that the target message is re-encapsulated based on a second preset message encapsulation format by the first network device corresponding to the destination server, and the re-encapsulated target message is sent to the edge server corresponding to the destination server, so that the re-encapsulated target message is sent to the destination server by the edge server corresponding to the destination server.

[0030] Optionally, the forwarding of the target message to the destination server by the first network device and the second network device based on the topological relationship comprises:

[0031] the forwarding of the target message to the destination server by the first network device and the second network device based on the topological relationship and a preset load balancing strategy.

[0032] In a second aspect, the application discloses a network virtualization implementation device for a cloud data center, applied to a cloud computing management platform, comprising:

[0033] an address allocation module configured to allocate a corresponding target address to each target device based on the device type of each target device in the cloud data center; the device type comprises a network device and an edge virtual network; the target address comprises a first address used to identify the location information of the target device and a second address used to identify the edge virtual network information of the target device;

[0034] a topological information determination module configured to determine the full-network topological information of the cloud data center by declaring the target address of each first network device to all network devices based on a preset routing switching mechanism; the network devices comprise the first network devices and second network devices; the first network devices are leaf switches, and the second network devices are spine switches;

[0035] The packet forwarding module is configured to determine a topological relationship between a corresponding source server and a destination server based on a target packet by using the whole network topological information and a pre-acquired identifier mapping table, and to forward the target packet to the destination server by using the first network device and the second network device based on the topological relationship.

[0036] In a third aspect, the present application discloses an electronic device, comprising:

[0037] A memory for saving a computer program;

[0038] A processor for executing the computer program to implement the aforementioned network virtualization implementation method for a cloud data center.

[0039] In a fourth aspect, the present application discloses a computer readable storage medium for saving a computer program, wherein the computer program is executed by a processor to implement the aforementioned network virtualization implementation method for a cloud data center.

[0040] In the present application, when implementing network virtualization for a cloud data center, the cloud computing management platform assigns a corresponding target address to each target device based on the device type of each target device in the cloud data center; the device type includes network devices and edge virtual networks; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device; the target address of each first network device is announced to all network devices based on a preset routing exchange mechanism to determine the full network topology information of the cloud data center; the network devices include the first network devices and second network devices; the first network devices are leaf switches, and the second network devices are spine switches; the topology relationship between the source server and the destination server is determined based on the target message using the full network topology information and a pre-acquired identification mapping table, so that the target message is forwarded to the destination server using the first network devices and the second network devices based on the topology relationship. It can be seen that in the present application, the cloud computing management platform redefines the network address structure inside the cloud data center by assigning a corresponding target address to each target device based on the device type of each target device in the cloud data center, and the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device, thereby supporting fine management and efficient addressing of large-scale virtual networks. In addition, the cloud computing management platform announces the target address of each first network device to all network devices based on a preset routing exchange mechanism to determine the full network topology information of the cloud data center, which realizes fast synchronization and automatic routing generation of the full network topology, and avoids the problems of uncertainty and slow convergence caused by MAC learning in traditional Ethernet. Then the cloud computing management platform can determine the topology relationship between the source server and the destination server based on the target message using the full network topology information and the identification mapping table, so as to forward the target message to the destination server based on the topology relationship. Through the above process, the network virtualization function is originally integrated into the network protocol design, the construction and operation process of the virtual network is comprehensively optimized, and the overall transmission efficiency and resource utilization rate of the cloud data center network are improved. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor based on the provided drawings.

[0042] Figure 1 A flow chart of a network virtualization implementation method for a cloud data center is disclosed in the present application.

[0043] Figure 2 A specific network virtualization internal implementation architecture diagram disclosed by the application;

[0044] Figure 3 A specific target address structure diagram disclosed by the application;

[0045] Figure 4 A typical cloud data center network topology diagram disclosed by the application;

[0046] Figure 5 A specific packet header format diagram disclosed by the application;

[0047] Figure 6 A specific message format diagram issued by an edge server disclosed by the application;

[0048] Figure 7 A specific encapsulated frame structure diagram disclosed by the application;

[0049] Figure 8 A network protocol stack change diagram disclosed by the application; wherein, Figure 8 a is a network protocol stack diagram of a traditional network virtualization implementation method based on a transport layer tunnel mechanism, Figure 8 b is a network protocol stack diagram of a network virtualization implementation method provided by the embodiment;

[0050] Figure 9 A cloud data center-oriented network virtualization implementation device structure diagram disclosed by the application;

[0051] Figure 10 An electronic device structure diagram disclosed by the application. DETAILED DESCRIPTION

[0052] The technical solutions in the embodiments of the application will be clearly and completely described below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are only part of the embodiments of the application, rather than all the embodiments of the application. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor fall within the protection scope of the application.

[0053] Traditional cloud data center usually relies on network virtualization scheme based on tunnel encapsulation (such as VXLAN, NVGRE, etc.). These methods, although to some extent, realize network isolation and multi-tenant support, but due to the need for packet encapsulation and forwarding at a higher protocol layer (network layer or transport layer), significant CPU processing overhead, encapsulation header overhead, and increased network delay are brought. In order to solve the above technical problems, the application discloses a network virtualization implementation method for cloud data center, which can improve the overall transmission efficiency of virtualization technology in large-scale cloud data center environment.

[0054] Referring to Figure 1 As shown in the figure, the embodiment of the application discloses a network virtualization implementation method for cloud data center, applied to a cloud computing management platform, comprising:

[0055] Step S11, based on the device type of each target device of the cloud data center, the corresponding target address is allocated to each target device; the device type includes network device and edge virtual network; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device.

[0056] In this embodiment, as Figure 2 As shown in the figure, in order to simplify the architecture of the internal virtual network of the edge server, only one virtual network, virtual switch virtual switch, is reserved, and the cloud server of the tenant will be directly mounted on the virtual switch, and different local VLAN (Virtual Local Area Network, Virtual Local Area Network) is used to distinguish different virtual networks. This embodiment avoids the problems of configuration complexity, loop occurrence and the like caused by multiple virtual bridge connections by reserving only a single virtual switch in the edge server and distinguishing different virtual networks through VLAN tags, and significantly improves the deployment efficiency and network security.

[0057] In this embodiment, the cloud computing management platform allocates corresponding target addresses to each target device based on the device type of each target device of the cloud data center, wherein the device type includes network device and edge virtual network; the target address (i.e. target device address) includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device. As Figure 3The structure of a target address is shown, which includes three parts. The first part is a reserved field (Reserved) with 4 bits, which is all 0 by default. The second part is a Locator ID, also called the first address, with 48 bits, which is used for routing and forwarding in the cloud data center. The third part is an Edge ID, also called the second address, with 12 bits. The 48-bit Locator ID follows the semantics of the Ethernet MAC address, including unicast, multicast and broadcast semantics. The 12-bit Edge ID has two cases. One is the network device itself, such as a spine switch and a leaf switch, whose Edge ID is all 0, i.e. 0x000H. The other is an edge virtual network, whose Edge ID is allocated by the leaf switch connected to the device, which is used to identify the identity of the virtual network and needs to be mapped to a globally unique virtual network ID. The Edge ID is only valid in the management domain of the current switch and does not have global semantics. In addition, there is a special case, which is a traditional server that does not support access to the cloud data center network. The format of its network address is similar to that of the switch. The high 48 bits are the MAC address of the device itself, and the low 12 bits are all 0, i.e. 0x000H.

[0058] In this embodiment, the virtual network has three different representations in the protocol architecture of this embodiment. In the edge server, the virtual network is marked by the VLAN on the virtual switch. When the cloud servers in different virtual networks are mounted to the virtual switch, they will be labeled with the VLAN tag corresponding to the virtual network. On the uplink leaf switch of the edge cloud server, the virtual network can be identified by the Edge ID. After leaving the leaf switch, the virtual network is identified by a 32-bit global Network ID, which is uniformly allocated by the cloud computing management platform and transmitted with the packet during packet forwarding. The virtual network has three different representations in the protocol architecture of this embodiment. In the edge server, the virtual network is marked by the VLAN on the virtual switch. When the cloud servers in different virtual networks are mounted to the virtual switch, they will be labeled with the VLAN tag corresponding to the virtual network. On the uplink leaf switch of the edge cloud server, the virtual network can be identified by the Edge ID. After leaving the leaf switch, the virtual network is identified by a 32-bit global Network ID, which is uniformly allocated by the cloud computing management platform and transmitted with the packet during packet forwarding. By integrating the virtual network identification information in the protocol design stage, only a lightweight encapsulation is required, which significantly reduces the encapsulation header redundancy brought by traditional tunneling protocols (such as VXLAN, NVGRE), thereby improving the effective load ratio and improving the overall network transmission efficiency.

[0059] Step S12: Based on a preset routing and switching mechanism, the target address of each first network device is advertised to all network devices to determine the overall network topology information of the cloud data center; the network devices include the first network device and the second network device; the first network device is a leaf switch and the second network device is a spine switch.

[0060] In this embodiment, as Figure 4 The diagram illustrates a typical cloud data center topology. Unlike complex scenarios such as the Internet and enterprise networks, the routing and switching mechanism in a cloud data center can be greatly simplified due to the deterministic and stable nature of its network topology, resulting in a pre-defined routing and switching mechanism. Network devices in a cloud data center have only two roles: first-level network devices (leaf switches) and second-level network devices (spine switches). The ultimate goal of route generation is to announce the location information of each leaf switch to all network devices in the network. Under this premise, based on the pre-defined routing and switching mechanism, the target addresses of each first-level network device are announced to all network devices to determine the overall network topology information of the cloud data center. Specifically, this may include: determining all target second-level network devices corresponding to each first-level network device; identifying the target second-level network devices as those connected to the first-level network devices; establishing neighbor relationships between each first-level network device and its corresponding target second-level network device; announcing the first address of each first-level network device to the corresponding target second-level network device, allowing the target second-level network device to record the routing information of the first-level network device in its local routing table and forward the routing information to other first-level network devices that have a neighbor relationship with the target second-level network device, recording the routing information in the local routing tables of these other first-level network devices; and determining the overall network topology information of the cloud data center based on all routing information.

[0061] In other words, in this embodiment, each leaf switch establishes a neighbor relationship with all the spine switches connected to it. The leaf switch then announces its Locator ID to all its neighbors, i.e., the spine switches. After receiving the address announcement from the leaf switch, the spine switch records it in its local routing table and continues to announce this address information to all other leaf switches with which it has established a neighbor relationship. After receiving address announcements from other leaf switches of the spine switch, the leaf switch records them in its local routing table. The routing table format is shown in Table 1 below. This embodiment, by adopting a simplified neighbor relationship establishment and Locator ID announcement mechanism, combined with static topology characteristics, quickly synchronizes routing information across the entire network, avoiding the uncertainty and slow convergence problems of MAC table-based learning, and improving the stability and reliability of the cloud data center network.

[0062] Table 1 Routing Table Format

[0063]

[0064] It's important to note that leaf switches do not forward address advertisements from spine switches to avoid routing loops. Additionally, in certain special cases where spine switches are interconnected, neighbor relationships need to be established between them; this is generally considered a non-standard network topology. Furthermore, when a leaf switch is connected to a traditional device, such as a traditional physical server (which does not support newer cloud data center network protocols), the leaf switch will act as a proxy, advertising the device's 48-bit MAC address as the Locator ID to the spine, thus generating routing information to that traditional device across the entire network. When all leaf and spine switches advertise routing information according to the aforementioned preset routing exchange mechanism, a complete network topology can be generated on every switch (including all leaf and spine switches). Each switch can then select routes based on the 48-bit Locator ID, significantly improving routing scalability and meeting the routing requirements of cloud data centers. By introducing a novel addressing structure of 48-bit Locator ID and 12-bit Edge ID, this application achieves efficient identification and isolation of large-scale nodes and virtual networks within cloud data centers, breaking through the traditional VLAN quantity limit and meeting the needs of large-scale cloud environments for multi-tenant isolation and resource management.

[0065] Understandably, in this embodiment, if the cloud computing management platform receives a cloud server startup request, it determines the target edge server based on the cloud server startup request using a preset server scheduling strategy; it creates and starts the target cloud server corresponding to the cloud server startup request on the target edge server, and mounts the target cloud server to the corresponding target edge virtual network; it notifies the first edge network device of the virtual network information and MAC address information corresponding to the target cloud server, so that the first edge network device can send the triple information corresponding to the target cloud server to the second edge network device; it uses the second edge network device to send the triple information to other first network devices that have a neighbor relationship with the second edge network device, and saves the triple information to the local identifier mapping table of the other first network devices that have a neighbor relationship with the second edge network device; wherein, the first edge network device is the first network device corresponding to the target edge server, the second edge network device is the second network device that has a neighbor relationship with the first edge device, and the triple information includes the virtual network information corresponding to the target cloud server, the MAC address information corresponding to the target cloud server, and the first address of the first edge network device.

[0066] In other words, when a user purchases a cloud server within a virtual network through the cloud computing console, the cloud computing platform will create and start a cloud server on a specific edge server according to the corresponding scheduling policy, and connect it to the corresponding virtual network. After creation, the virtual network information (Network ID) and MAC address information of the cloud server need to be announced to the edge leaf switches. The edge leaf switches record this information and announce the Network ID, MAC address, and their own Locator ID as a triple to all neighboring spine switches. Upon receiving this triple, the neighboring spine switches record it in their local mapping table and then announce it to other neighboring leaf switches. Other neighboring leaf switches, upon receiving the triple, first determine if a cloud server with the same Network ID exists among the edge servers under their own leaf switch. If it exists, they record the triple in their local virtual network identifier mapping table; otherwise, they ignore the announcement. The identifier mapping table records the mapping relationship between the MAC address of the cloud server within the virtual network of the current cloud data center and the first address of the first network device corresponding to the cloud server. By generating full network topology information and complete routing tables in advance, the latency of session establishment is effectively reduced.

[0067] Step S13: Using the network topology information and the pre-acquired identifier mapping table, determine the topology relationship between the corresponding source server and destination server based on the target packet, and forward the target packet to the destination server using the first network device and the second network device based on the topology relationship.

[0068] In this embodiment, the topological relationship between the source server and the destination server is determined based on the target packet using the network-wide topology information and a pre-acquired identifier mapping table. This includes: sending the target packet from the source server to the first network device corresponding to the source server; the target packet being a packet encapsulated in VLAN format; processing the target packet using the first network device corresponding to the source server to extract the second address from the outer Ethernet header of the target packet; and determining the first network device corresponding to the destination server of the target packet based on the network-wide topology information and the pre-acquired identifier mapping table, thereby determining the topological relationship between the source server and the destination server. The topological relationship includes a first topological relationship, a second topological relationship, and a third topological relationship. The first topological relationship indicates that the source server and the destination server are within the same edge server; the second topological relationship indicates that the source server and the destination server are within different edge servers of the same first network device; and the third topological relationship indicates that the source server and the destination server are within different edge servers of different first network devices. The header format of the target packet is as follows: Figure 5 As shown, the message header consists of three parts: Destination, Source, and Network ID. The Destination address identifies the destination information that the target message needs to transmit, the Source address identifies the source of the message, and the Network ID identifies the virtual network information carried by the message.

[0069] In other words, in this embodiment, when two cloud servers in a virtual network communicate, there are three scenarios: the source server and the destination server are both located inside the same edge server; the source server and the destination server are inside different edge servers under the same leaf switch; and the source server and the destination server are inside different edge servers under different leaf switches. These three scenarios correspond to the first topology relationship, the second topology relationship, and the third topology relationship, respectively.

[0070] In one specific implementation, if the topology between the source server and the destination server is a first topology, the target packet is forwarded directly within the edge servers corresponding to the source and destination servers. If the topology between the source and destination servers is a second topology, the target packet is forwarded to the edge server corresponding to the destination server using the first network device corresponding to the source server. The edge server then removes the outer encapsulation of the target packet and forwards the resulting inner target packet to the destination server. If the topology between the source and destination servers is a third topology, the first network device corresponding to the source server extracts the inner packet of the target packet and encapsulates it based on a first preset packet encapsulation format to obtain a new target packet. This new target packet is forwarded hop-by-hop to the first network device corresponding to the destination server. The first network device then re-encapsulates the target packet based on a second preset packet encapsulation format and sends the re-encapsulated target packet to the edge server corresponding to the destination server. The edge server then sends the re-encapsulated target packet to the destination server.

[0071] In other words, if the source server and destination server are both located within the same edge server, communication between them can be achieved directly within the edge server. If the source server and destination server are located within different edge servers of the same leaf switch, the packets sent by the source server will have an outer header added by the virtual switch within the edge server before being sent to the leaf switch. The leaf switch determines that the destination is located on another local edge server, and then directly forwards the packet to the edge server corresponding to that destination server. The edge server corresponding to the destination server receives the packet, removes the outer header encapsulation, and delivers the inner packet to the destination server, thus completing the transmission and reception process. In one specific implementation, to maximize compatibility, packets sent from the edge server to the leaf switch are encapsulated using the traditional VLAN format. That is, before the packets from the virtual network are sent to the leaf switch, the virtual switch on the physical edge server adds an IEEE 802.1q outer header to the Ethernet packet header, such as... Figure 6 As shown, the VLAN ID in the VLAN Header is the Edge ID assigned by the Leaf switch, i.e., the virtual network ID, while the outer Destination MAC and Source MAC are directly copied from the inner MAC address. After the packet arrives at the Leaf switch, the Leaf switch extracts the VLAN ID information from the outer Ethernet header, interprets this VLAN ID as the Edge ID, and queries the global Network ID corresponding to this Edge ID for the virtual network.

[0072] In this embodiment, if the topology between the source server and the destination server is a third topology, that is, the source server and the destination server are located inside different edge servers under different leaf switches, the packets sent by the source server will be added by the virtual switch within the edge server, such as... Figure 6 The outer header shown is sent to the Leaf switch. After the packet arrives at the Leaf switch, the virtual network identifier mapping table is queried (as shown in Table 2 below). If it is found that the destination of the packet is under a different Leaf switch, the inner packet content is extracted, and a new packet is re-encapsulated in the outer layer based on the first preset packet encapsulation format. Figure 7 The packet header shown is the inner Ethernet frame structure extracted from the original packet from the edge server and encapsulated within the frame structure of the new cloud network data center. The Network ID is a globally recognized virtual network identifier, Destination is the first address of the first network device corresponding to the destination server, and Source is the first address of the first network device corresponding to the source server. Through hop-by-hop forwarding, the target packet is finally delivered to the leaf switch corresponding to the destination server. Upon receiving the packet, the leaf switch corresponding to the destination server removes the outer encapsulation header and re-attaches a new header based on the second preset packet encapsulation format, such as... Figure 6 The outer header, as shown, contains the VLAN field, which is the Edge ID of the virtual network under this leaf switch. The MAC addresses of the source and destination servers are directly copied from the inner header. After encapsulation, the target packet is sent to the edge server corresponding to the destination server. The virtual switch in the edge server then delivers the target packet to the final destination cloud server, thus completing the packet transmission and reception process.

[0073] Table 2. Virtual Network Identifier Mapping Table Format

[0074]

[0075] It should be pointed out that, Figure 7 In the outer header of the message, the high 48 bits of the Destination field represent the Locator ID of the leaf switch corresponding to the destination server, and the low 12 bits are all 0s. The high 48 bits of the Source field represent the Locator ID of the leaf switch corresponding to the source server, and the low 12 bits are all 0s. For future protocol extensions, the low 12 bits could be considered for reuse.

[0076] It should be noted that this embodiment, by employing a direct encapsulation and forwarding mechanism based on the data link layer, avoids the complex process of frequent uploading to the network and transport layers required by traditional tunnel virtualization technologies. This significantly reduces the CPU processing overhead of edge servers and intermediate network devices, reduces forwarding latency, and improves communication performance. Figure 8 As shown, Figure 8 'a' is a schematic diagram of the network protocol stack for a traditional network virtualization implementation method based on transport layer tunneling mechanism. Figure 8 b is a schematic diagram of the network protocol stack of the network virtualization implementation method provided in this embodiment. By comparison, it can be seen that compared with the traditional network virtualization implementation method based on the transport layer tunnel mechanism, the network virtualization implementation method disclosed in this embodiment has great optimization at the protocol stack processing level of edge servers and intermediate network devices.

[0077] It is understandable that forwarding target packets to the destination server using the first and second network devices based on the topology includes: forwarding the target packets to the destination server using the first and second network devices based on the topology and a preset load balancing strategy. Specifically, to simplify network traffic scheduling strategies and reduce the probability of network congestion, a full-traffic load balancing strategy is adopted for packet forwarding on equal-cost routes. That is, if there are N equal-cost routes to a certain destination, the traffic is evenly distributed to the next hop corresponding to these N equal-cost routes. When all nodes adopt this balanced forwarding strategy, the traffic of the entire network will tend to be even, and the probability of congestion will be greatly reduced.

[0078] As can be seen, in this application, the cloud computing management platform assigns corresponding target addresses to each target device based on the device type of each target device in the cloud data center. The target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device, thereby redefining the network address structure within the cloud data center and supporting fine-grained management and efficient addressing of large-scale virtual networks. Furthermore, the cloud computing management platform, based on a preset routing switching mechanism, announces the target addresses of each first network device to all network devices to determine the overall network topology information of the cloud data center, achieving rapid synchronization of the overall network topology and automatic route generation, avoiding the uncertainty and slow convergence problems caused by MAC learning in traditional Ethernet. The cloud computing management platform can then use the overall network topology information and the identifier mapping table to determine the topological relationship between the source server and the destination server based on the target packet, and forward the target packet to the destination server based on the topology relationship. Through the above process, this application natively integrates network virtualization functionality into the network protocol design, comprehensively optimizing the construction and operation and maintenance process of virtual networks, and improving the overall transmission efficiency and resource utilization of the cloud data center network.

[0079] See Figure 9 As shown, this application discloses a network virtualization implementation device for cloud data centers, applied to a cloud computing management platform, comprising:

[0080] Address allocation module 11 is used to allocate corresponding target addresses to each target device based on the device type of each target device in the cloud data center; the device type includes network devices and edge virtual networks; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device;

[0081] The topology information determination module 12 is used to announce the target address of each first network device to all network devices based on a preset routing switching mechanism to determine the overall network topology information of the cloud data center; the network devices include the first network device and the second network device; the first network device is a leaf switch and the second network device is a spine switch;

[0082] The message forwarding module 13 is used to determine the topological relationship between the corresponding source server and destination server based on the target message using the network topology information and the pre-acquired identifier mapping table, so as to forward the target message to the destination server using the first network device and the second network device based on the topology relationship.

[0083] In one specific embodiment, the topology information determination module 12 may specifically include:

[0084] A device determination unit is used to determine all target second network devices corresponding to each first network device; the target second network device is the second network device connected to the first network device.

[0085] The neighbor relationship establishment unit is used to establish neighbor relationships between each of the first network devices and the corresponding target second network devices;

[0086] The routing information recording unit is used to announce the first address of the first network device to the corresponding target second network device, so as to use the target second network device to record the routing information of the first network device in the local routing table of the target second network device, and forward the routing information to other first network devices that have a neighbor relationship with the target second network device, and record the routing information in the local routing table of the other first network devices;

[0087] The network topology information determination unit is used to determine the network topology information of the cloud data center based on all the routing information.

[0088] In one specific embodiment, the device may further include:

[0089] The edge server determination module is used to determine the target edge server based on the cloud server startup request and a preset server scheduling strategy if a cloud server startup request is obtained.

[0090] The cloud server mounting module is used to create and start the target cloud server corresponding to the cloud server startup request on the target edge server, and mount the target cloud server to the corresponding target edge virtual network;

[0091] The triplet information sending module is used to notify the first edge network device of the virtual network information and MAC address information corresponding to the target cloud server, so as to use the first edge network device to send the triplet information corresponding to the target cloud server to the second edge network device.

[0092] The triplet information storage module is used to send the triplet information to other first network devices that have a neighbor relationship with the second edge network device using the second edge network device, and to save the triplet information to the local identifier mapping table of the other first network devices that have a neighbor relationship with the second edge network device.

[0093] Wherein, the first edge network device is the first network device corresponding to the target edge server, the second edge network device is the second network device that has a neighbor relationship with the first edge network device, and the triplet information includes the virtual network information corresponding to the target cloud server, the MAC address information corresponding to the target cloud server, and the first address of the first edge network device.

[0094] In one specific embodiment, the message forwarding module 13 may include:

[0095] The first message sending unit is used to send a target message to the first network device corresponding to the source server using the source server; the target message is a message encapsulated in VLAN format.

[0096] The address extraction unit is used to process the target packet using the first network device corresponding to the source server, so as to extract the second address in the target packet from the outer Ethernet header of the target packet;

[0097] The topology relationship determination unit is used to determine the first network device corresponding to the destination server of the target packet based on the network-wide topology information and a pre-acquired identifier mapping table, so as to determine the topology relationship between the source server and the destination server;

[0098] The topology relationship includes a first topology relationship, a second topology relationship, and a third topology relationship; the first topology relationship is that the source server and the destination server are located within the same edge server; the second topology relationship is that the source server and the destination server are located within different edge servers of the same first network device; and the third topology relationship is that the source server and the destination server are located within different edge servers of different first network devices.

[0099] In one specific embodiment, the message forwarding module 13 may include:

[0100] The first message forwarding unit is configured to forward the target message directly within the edge server corresponding to the source server and the destination server if the topological relationship between the source server and the destination server is a first topological relationship.

[0101] The second message forwarding unit is configured to, if the topology between the source server and the destination server is a second topology, use the first network device corresponding to the source server to forward the target message to the edge server corresponding to the destination server, so as to use the edge server corresponding to the destination server to remove the outer encapsulation of the target message and forward the resulting inner target message to the destination server.

[0102] The third message forwarding unit is configured to, if the topology between the source server and the destination server is a third topology, extract the inner message of the target message using the first network device corresponding to the source server, encapsulate the inner message based on a first preset message encapsulation format to obtain a new target message, forward the new target message hop-by-hop to the first network device corresponding to the destination server, re-encapsulate the target message using the first network device corresponding to the destination server based on a second preset message encapsulation format, and send the re-encapsulated target message to the edge server corresponding to the destination server, so that the edge server corresponding to the destination server can send the re-encapsulated target message to the destination server.

[0103] In one specific embodiment, the message forwarding module 13 may include:

[0104] The fourth message forwarding unit is used to forward the target message to the destination server using the first network device and the second network device based on the topology and a preset load balancing strategy.

[0105] Furthermore, embodiments of this application also disclose an electronic device,Figure 10 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0106] Figure 10 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the network virtualization implementation method for cloud data centers disclosed in any of the foregoing embodiments. Alternatively, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0107] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0108] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored thereon can include an operating system 221, computer programs 222, etc., and the storage method can be temporary storage or permanent storage.

[0109] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the network virtualization implementation method for cloud data centers executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0110] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned network virtualization implementation method for cloud data centers. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0111] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0112] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0113] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0114] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0115] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for implementing network virtualization for cloud data centers, characterized in that, Applications in cloud computing management platforms, including: Based on the device type of each target device in the cloud data center, a corresponding target address is assigned to each target device; the device type includes network devices and edge virtual networks; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device; Based on a preset routing and switching mechanism, the target address of each first network device is advertised to all network devices to determine the overall network topology information of the cloud data center; the network devices include the first network device and the second network device; the first network device is a leaf switch and the second network device is a spine switch; Using the network topology information and a pre-acquired identifier mapping table, the topology relationship between the corresponding source server and destination server is determined based on the target packet, and the target packet is forwarded to the destination server using the first network device and the second network device based on the topology relationship; The step of announcing the target address of each first network device to all network devices based on a preset routing and switching mechanism to determine the overall network topology information of the cloud data center includes: Identify all target second network devices corresponding to each first network device; the target second network device is the second network device connected to the first network device. Establish neighbor relationships between each of the first network devices and the corresponding target second network devices; The first address of the first network device is advertised to the corresponding target second network device, so that the target second network device records the routing information of the first network device in the local routing table of the target second network device, and forwards the routing information to other first network devices that have a neighbor relationship with the target second network device, and records the routing information in the local routing table of the other first network devices; The network topology of the cloud data center is determined based on all the routing information. The step of determining the topological relationship between the corresponding source server and destination server based on the target packet using the network-wide topology information and a pre-acquired identifier mapping table includes: The target packet is sent from the source server to the first network device corresponding to the source server; the target packet is a packet encapsulated in VLAN format. The target packet is processed using the first network device corresponding to the source server to extract the second address from the outer Ethernet header of the target packet; Based on the network topology information and the pre-acquired identifier mapping table, the first network device corresponding to the destination server of the target packet is determined, so as to determine the topological relationship between the source server and the destination server; The topology relationship includes a first topology relationship, a second topology relationship, and a third topology relationship; the first topology relationship is that the source server and the destination server are located within the same edge server; the second topology relationship is that the source server and the destination server are located within different edge servers of the same first network device; the third topology relationship is that the source server and the destination server are located within different edge servers of different first network devices. The identifier mapping table is used to record the mapping relationship between the MAC address of the cloud server in the virtual network inside the current cloud data center and the first address of the first network device corresponding to the cloud server.

2. The network virtualization implementation method for cloud data centers according to claim 1, characterized in that, Also includes: If a cloud server startup request is received, the target edge server is determined based on the cloud server startup request using a preset server scheduling strategy. Create and start the target cloud server corresponding to the cloud server startup request on the target edge server, and attach the target cloud server to the corresponding target edge virtual network; The virtual network information and MAC address information corresponding to the target cloud server are announced to the first edge network device, so that the first edge network device can send the triplet information corresponding to the target cloud server to the second edge network device. The second edge network device sends the triplet information to other first network devices that are neighbors of the second edge network device, and saves the triplet information to the local identifier mapping table of the other first network devices that are neighbors of the second edge network device. Wherein, the first edge network device is the first network device corresponding to the target edge server, the second edge network device is the second network device that has a neighbor relationship with the first edge network device, and the triplet information includes the virtual network information corresponding to the target cloud server, the MAC address information corresponding to the target cloud server, and the first address of the first edge network device.

3. The network virtualization implementation method for cloud data centers according to claim 1, characterized in that, The step of forwarding the target packet to the destination server using the first network device and the second network device based on the topology includes: If the topology between the source server and the destination server is the first topology, then the target packet is forwarded directly within the edge server corresponding to the source server and the destination server. If the topology between the source server and the destination server is a second topology, then the first network device corresponding to the source server is used to forward the target packet to the edge server corresponding to the destination server, so that the edge server corresponding to the destination server can remove the outer encapsulation of the target packet and forward the resulting inner target packet to the destination server. If the topology between the source server and the destination server is a third topology, then the first network device corresponding to the source server extracts the inner packet of the target packet, and encapsulates the inner packet based on a first preset packet encapsulation format to obtain a new target packet. The new target packet is then forwarded hop-by-hop to the first network device corresponding to the destination server, so that the first network device corresponding to the destination server can re-encapsulate the target packet based on a second preset packet encapsulation format. The re-encapsulated target packet is then sent to the edge server corresponding to the destination server, so that the edge server corresponding to the destination server can send the re-encapsulated target packet to the destination server.

4. The network virtualization implementation method for cloud data centers according to any one of claims 1 to 3, characterized in that, The step of forwarding the target packet to the destination server using the first network device and the second network device based on the topology includes: Based on the topology and preset load balancing strategy, the first network device and the second network device are used to forward the target packet to the destination server.

5. A network virtualization implementation device for cloud data centers, characterized in that, Applications in cloud computing management platforms, including: The address allocation module is used to allocate corresponding target addresses to each target device based on the device type of each target device in the cloud data center; the device type includes network devices and edge virtual networks; the target address includes a first address for identifying the location information of the target device and a second address for identifying the edge virtual network information of the target device; The topology information determination module is used to announce the target address of each first network device to all network devices based on a preset routing switching mechanism to determine the overall network topology information of the cloud data center; the network devices include the first network device and the second network device; the first network device is a leaf switch and the second network device is a spine switch; The message forwarding module is used to determine the topological relationship between the corresponding source server and destination server based on the target message using the network topology information and the pre-acquired identifier mapping table, so as to forward the target message to the destination server using the first network device and the second network device based on the topology relationship; The topology information determination module specifically includes: A device determination unit is used to determine all target second network devices corresponding to each first network device; the target second network device is the second network device connected to the first network device. The neighbor relationship establishment unit is used to establish neighbor relationships between each of the first network devices and the corresponding target second network devices; The routing information recording unit is used to announce the first address of the first network device to the corresponding target second network device, so as to use the target second network device to record the routing information of the first network device in the local routing table of the target second network device, and forward the routing information to other first network devices that have a neighbor relationship with the target second network device, and record the routing information in the local routing table of the other first network devices; The network topology information determination unit is used to determine the network topology information of the cloud data center based on all the routing information. The message forwarding module specifically includes: The first message sending unit is used to send a target message to the first network device corresponding to the source server using the source server; the target message is a message encapsulated in VLAN format. The address extraction unit is used to process the target packet using the first network device corresponding to the source server, so as to extract the second address in the target packet from the outer Ethernet header of the target packet; The topology relationship determination unit is used to determine the first network device corresponding to the destination server of the target packet based on the network-wide topology information and a pre-acquired identifier mapping table, so as to determine the topology relationship between the source server and the destination server; The topology relationship includes a first topology relationship, a second topology relationship, and a third topology relationship; the first topology relationship is that the source server and the destination server are located within the same edge server; the second topology relationship is that the source server and the destination server are located within different edge servers of the same first network device; the third topology relationship is that the source server and the destination server are located within different edge servers of different first network devices. The identifier mapping table is used to record the mapping relationship between the MAC address of the cloud server in the virtual network inside the current cloud data center and the first address of the first network device corresponding to the cloud server.

6. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the network virtualization implementation method for cloud data centers as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, Used to store computer programs, wherein the computer programs, when executed by a processor, implement the network virtualization implementation method for cloud data centers as described in any one of claims 1 to 4.

Images