CN110266833B - IP address management method and edge cluster - Google Patents
IP address management method and edge cluster Download PDFInfo
- Publication number
- CN110266833B CN110266833B CN201910640070.6A CN201910640070A CN110266833B CN 110266833 B CN110266833 B CN 110266833B CN 201910640070 A CN201910640070 A CN 201910640070A CN 110266833 B CN110266833 B CN 110266833B
- Authority
- CN
- China
- Prior art keywords
- virtual
- address
- edge
- edge cluster
- cluster
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 88
- 230000008569 process Effects 0.000 claims abstract description 77
- 230000003068 static effect Effects 0.000 claims description 11
- 238000005315 distribution function Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 3
- 238000005192 partition Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000010355 oscillation Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/58—Association of routers
- H04L45/586—Association of routers of virtual routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Theoretical Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides an IP address management method and an edge cluster, and particularly, a virtual IP address distribution function of a main service process is converted into a distribution function aiming at a virtual IP address field, so that the edge cluster is bound with the distributed virtual IP address field, the edge cluster selects a virtual IP address from the bound virtual IP address field through an agent service process and distributes the virtual IP address to newly-built virtual equipment in the cluster, and the problem that the virtual equipment cannot communicate due to conflict of the virtual IP addresses distributed by the virtual equipment in different edge clusters is solved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to an IP address management method and an edge cluster.
Background
In an Infrastructure as a Service (IaaS) architecture, a user may obtain a corresponding Service from a data center through a network. To avoid the effects of network delays, failures, etc., services are typically deployed at edge nodes that are closer to the user. A plurality of edge nodes may form an edge cluster, and in order to make full use of hardware resources and reduce operation and maintenance costs, the edge cluster typically virtualizes hardware and network resources, for example, abstracts the hardware resources into virtual devices (e.g., containers) for users. The newly-built virtual device is generally configured to uniformly allocate a virtual IP address by a network protocol address management (IPAM) service deployed in the data center, and the virtual device communicates with the data center based on the allocated virtual IP address.
However, when a network failure occurs, the data center cannot allocate a virtual IP address to a virtual device newly built in the edge cluster, and therefore, an agent IPAM service is usually deployed in the edge cluster to allocate a virtual IP address to a virtual device newly built in the edge cluster by itself. By adopting the above manner, the virtual IP addresses allocated to the virtual devices by each edge cluster may conflict, which may result in that the virtual devices cannot communicate.
Disclosure of Invention
The purpose of the present application includes providing an IP address management method and an edge cluster, which can avoid a conflict between virtual IP addresses assigned to virtual devices under the autonomous condition of the edge cluster.
To achieve the above object, embodiments of the present application may be implemented as follows:
in a first aspect, an embodiment of the present application provides an IP address management method, which is applied to an edge cluster, where an agent service process that communicates with a main service process of a data center is deployed in the edge cluster, and the method includes:
determining a target virtual IP address field distributed to the edge cluster by the main service process through the proxy service process;
and when an address allocation request sent by the newly-built virtual equipment in the edge cluster is received, selecting a virtual IP address from the target virtual IP address field to allocate to the newly-built virtual equipment.
In a second aspect, an embodiment of the present application provides an edge cluster, where an agent service process that communicates with a main service process of a data center is deployed;
and the proxy service process is used for determining a target virtual IP address field distributed by the main service process for the edge cluster, and selecting a virtual IP address from the target virtual IP address field to distribute to the newly-built virtual equipment when receiving an address distribution request sent by the newly-built virtual equipment in the edge cluster.
Compared with the prior art, the beneficial effects of the embodiment of the application include, for example: the virtual IP address distribution function of the main service process is converted into the distribution function aiming at the virtual IP address field, the edge cluster is bound with the distributed virtual IP address field, the proxy service process of the edge cluster selects the virtual IP address from the bound virtual IP address field to distribute to the newly-built virtual equipment in the cluster, and therefore the problem that the virtual equipment cannot communicate due to the fact that the virtual IP addresses distributed by the virtual equipment in different edge clusters conflict is solved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram of an architecture of a data center and an edge cluster according to an embodiment of the present application;
fig. 2 is a schematic communication diagram of an edge node and a virtual router in an edge cluster and a data center according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of an IP address management method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of an IP address management method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Furthermore, the appearances of the terms "first," "second," and the like, if any, are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance. It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
Referring to fig. 1, the present embodiment provides a schematic architecture diagram of a data center and an edge cluster. The data center 10 is communicatively coupled to a plurality of edge clusters, such as edge clusters 21, 22, 23, and 24 shown in FIG. 1. The data center 10 is typically deployed on a plurality of servers communicatively connected to each other, and the plurality of servers and their running service processes may communicate with external devices or processes through a gateway 11 of the data center 10.
Each edge cluster includes a virtual router and a plurality of edge nodes that communicate with the data center 10 through the virtual router. For example, fig. 2 shows a schematic diagram of communication between the edge nodes and virtual routers inside the edge cluster 21 and the data center 10. Edge cluster 21 includes four edge nodes 211, 212, 213, and 214, and virtual router 215.
In an implementation manner of this embodiment, an edge cluster may be deployed on a physical machine, in which case each edge node may be a virtual machine deployed on the physical machine, and a virtual switch process is deployed in the virtual machine, so that the virtual machine (edge node) becomes a virtual switch. The virtual machine as the edge node also runs other virtual devices (e.g., containers) which can be regarded as user terminals connected to the virtual switch. For example, in the scenario shown in FIG. 2, the edge node 212 acts as a virtual machine with containers 31 and 32 running therein; the edge node 214 acts as a virtual machine in which the containers 33 and 34 run. Wherein containers 31 and 32 can be considered as subscriber terminals connected to the virtual switch formed by edge node 212 and containers 33 and 34 can be considered as subscriber terminals connected to the virtual switch formed by edge node 214. The containers 31 to 34 may implement data forwarding through the respective connected virtual switches.
Further, the above physical machine is also run with a virtual routing process to form the virtual router, for example, the edge cluster 21 is run with a virtual routing process as one physical machine, thereby forming the virtual router 215. The virtual router 215 may be regarded as a gateway of the edge nodes 211 to 214 within the edge cluster 21, and the edge nodes 211 to 214 may implement data forwarding with the data center 10 through the virtual router 215.
In another implementation manner of this embodiment, an edge cluster may be deployed on multiple physical machines, each edge node in the edge cluster may be a physical machine, the physical machine runs a virtual switching process to form a virtual switch, and a virtual device run by the physical machine may be regarded as a user terminal connected to the virtual switch. For example, in the scenario shown in fig. 2, the edge node 212 runs as one physical machine with the containers 31 and 32, and the edge node 214 runs as one physical machine with the containers 33 and 34, at this time, one of the multiple physical machines for deploying the edge cluster 21 may run with a virtual routing process to form the virtual router 215, and the edge nodes 211 to 214 may implement data forwarding with the data center 10 through the virtual router 215.
In this embodiment, the virtual router of each edge cluster communicates with the gateway 11 of the data center 10 based on a Border Gateway Protocol (BGP), so that route reachability information of different subnets can be provided through BGP route advertisements, and three-layer interworking between the data center 100 and the edge cluster is achieved.
As can be seen from the foregoing description, the virtual switch and the virtual router in the edge cluster are both implemented by a process on a physical machine for deploying the edge cluster, in other words, the forwarding of data by the edge cluster depends on the performance of a Central Processing Unit (CPU) of the physical machine for deploying the edge cluster. Therefore, compared with the mode that the data center communicates with the edge cluster based on the VXLAN (virtual extended local Area Network) protocol in the prior art, the actions of VXLAN header encapsulation and stripping in the forwarding process are reduced, and the loss of the CPU is reduced.
In this embodiment, the data center 10 further includes a main service process 12 deployed on the server, and each edge cluster is further deployed with a proxy service process that communicates with the main service process 12, for example, an edge cluster 21 shown in fig. 2 is deployed with a proxy service process 216. Wherein the proxy service process 216 is located on one physical machine where the edge cluster 21 is located. The host service process may be, for example, an IPAM service process, and the proxy service process may be, for example, a proxy IPAM service process. The main service process 12 and the proxy service process 216 cooperate with each other to allocate a virtual IP address to a virtual device newly built on an edge node in the edge cluster 21, so that the virtual device communicates with the data center 10 or other virtual devices based on the allocated virtual IP address.
Referring to fig. 3, an IP address management method applied to an edge cluster according to the present embodiment is exemplarily shown, and the steps included in the method are described below.
Step S31, determining, by the proxy service process, a target virtual IP address field allocated by the main service process for the edge cluster.
Step S32, when receiving an address assignment request sent by a newly-built virtual device in the edge cluster, selecting a virtual IP address from the target virtual IP address field to assign to the newly-built virtual device.
In this embodiment, a plurality of virtual IP address segments may be directly preset on the main service process 12 of the data center 10, and then an unassigned virtual IP address segment is selected from the plurality of virtual IP address segments and allocated to the edge cluster 21. Wherein, the virtual IP address field allocated to the edge cluster 21 is the target virtual IP address field.
Optionally, the virtual IP address segments may also be obtained by dynamically dividing a preset virtual IP address range by the host service process 12. For example, a user (e.g., an administrator) may configure a virtual IP address range on the main service process 12, where the virtual IP address range is configured to be allocated to a virtual device on an edge node in each edge cluster, and the configured virtual IP address range is the preset virtual IP address range. In addition, the host service process may further be configured with a mask that each virtual IP address segment that the administrator desires to partition has, and the mask may be, for example, a block-size defined in CIDR (class Inter-Domain Routing).
The main service process 12 may obtain the plurality of virtual IP address segments by dividing according to the preset virtual IP address range and the preset mask when starting.
In one example, the range of virtual IP addresses that the administrator configures for assignment by a virtual device is 10.1.0.0/22, where "22" is a mask, indicating the number of bits of the segment number in the range of virtual IP addresses, i.e., the first 22 bits indicate the segment number. Now that the mask of the virtual IP address segment to be obtained by the partition configured by the administrator is 24, that is, the number of bits of the segment number of the virtual IP address segment obtained by the final partition is 24, the host service process 12 may divide the virtual IP address range 10.1.0.0/22 into 255 virtual IP address segments in total, i.e., 10.1.0.1/24-10.1.255.0/24.
The host service process 12 may select one of the 255 virtual IP address segments to assign to the edge cluster 21 and the other edge clusters when it is started. For example, a choice of 10.1.0.0/24 may be assigned to edge cluster 21, a choice of 10.1.1.0/24 may be assigned to edge cluster 22, a choice of 10.1.2.0/24 may be assigned to edge cluster 23, and a choice of 10.1.3.0/24 may be assigned to edge cluster 24. Of course, other virtual IP address segments may be selected to be allocated to the edge clusters 21 to 24, as long as the edge clusters and the virtual IP address segments are ensured to be in one-to-one correspondence.
The proxy service process of each edge cluster may determine the virtual IP address segment that the host service process assigned for its edge cluster, e.g., proxy service process 216 of edge cluster 21 may determine the target virtual IP address segment that the edge cluster assigned to is 10.1.0.0/24.
When a virtual device is newly created on any edge node in the edge cluster 21, for example, when the container 31 is newly created, the newly created container 31 will send an address assignment request to the proxy service process 216, and the proxy service process 216 will select a virtual IP address (e.g., 10.1.0.1) from the determined target virtual IP address field 10.1.0.0/24 to assign to the container 31. Similarly, the proxy service process 216 can select a virtual IP address 10.1.0.2 from the destination virtual IP address field 10.1.0.0/24 to assign to the newly created container 32, select a virtual IP address 10.1.0.3 from the destination virtual IP address field 10.1.0.0/24 to assign to the newly created container 33, and select a virtual IP address 10.1.0.4 from the destination virtual IP address field 10.1.0.0/24 to assign to the newly created container 34.
Compared with the prior art in which virtual IP addresses are uniformly allocated to virtual devices by data center IPAM service processes, and virtual IP addresses are allocated to the virtual devices by proxy IPAM services of the edge nodes respectively when a network fails, through the steps shown in fig. 3, virtual IP address conflicts that may occur in the foregoing manner are avoided, and further, the problem that the virtual devices cannot communicate due to the conflicts is avoided.
In this embodiment, it is specified in the BGP protocol that two nodes connected within one autonomous system are internal (Inner) BGP neighbors to each other, and two connected nodes belonging to different autonomous systems are External (External) BGP neighbors to each other. And, the BGP routes learned by each node will advertise to all EBGP neighbors of that node. Therefore, in this embodiment, in order to make the routes of each edge node through, an Autonomous System (AS) identifier, for example, an AS number, may be allocated to the virtual router in each edge cluster and each edge node, so that the virtual router may respectively establish an external BGP connection with each edge node, and further the virtual router in the edge cluster and each edge node are adjacent to each other AS an EBGP.
For example, in the scenario shown in fig. 2, the virtual router 215 is configured with an AS number 301, the edge node 211 is configured with an AS number 302, the edge node 212 is configured with an AS number 303, the edge node 213 is configured with an AS number 304, and the edge node is configured with an AS number 305.
In this case, the IP address management method provided in this embodiment may further include the steps shown in fig. 4, which are described in detail as follows.
Step S41, after selecting a virtual IP address from the target virtual IP address field through the proxy service process to allocate to the newly-built virtual device, generating a BGP route for the allocated virtual IP address.
Step S42, configuring the generated BGP route to the virtual router, so that the virtual router advertises the generated BGP route to an EBGP neighbor.
The BGP route may include a virtual IP address assigned by the newly-created virtual device and a virtual egress interface corresponding to the virtual IP address, where the virtual egress interface is usually a virtual ethernet port of a virtual switch connected to the newly-created virtual device, and the virtual router records a correspondence relationship between each virtual ethernet port and a physical ethernet port. When the virtual router receives a data packet of a virtual IP address allocated by the destination IP address for the newly-built virtual device, the virtual router can find the corresponding BGP route, and forward the data packet through the physical ethernet port corresponding to the virtual ethernet port indicated by the BGP route.
After the generated BGP routes are configured to the virtual router, the virtual router will carry the BGP routes in a route advertisement message and send the route advertisement message to all EBGP neighbors. In this way, each edge node within the edge cluster can obtain BGP routes for all virtual devices of all edge nodes within the cluster. In this manner, data forwarding between edge nodes within an edge cluster may not necessarily rely on virtual routers, but may be implemented directly by the edge nodes (i.e., virtual switches).
Based on this, the IP address management method provided in this embodiment may further include the following steps:
and storing the received BGP route advertised by the virtual router at each edge node, and forwarding data to other edge nodes in the edge cluster according to the stored BGP route.
For example, in the scenario shown in fig. 2, when the container 31 sends data to the container 34, forwarding may be performed by the edge node 212 itself.
Therefore, forwarding actions executed by the virtual router can be reduced, and the virtual router is prevented from becoming a performance bottleneck of the edge cluster.
Optionally, in this embodiment, the gateway 11 of the data center 10 and the virtual router of each edge cluster may also be adjacent to each other, in which case, the virtual router of each edge cluster notifies the BGP route learned by the virtual router to the gateway 11 of the data center 10.
In practical applications, each BGP route may become reachable or unreachable according to the actual condition of the link, and when the state of one route frequently changes between reachable and unreachable, the route is said to have a route oscillation. In order to avoid this situation, static routes may be configured for the virtual IP address segments corresponding to each edge cluster in the gateway 11 of the data center 10, so that the gateway 11 may not need to learn BGP routes from the virtual routers of each edge cluster, thereby avoiding route oscillation occurring on the gateway 11.
Wherein the static route of each edge cluster includes the target virtual IP address segment allocated by the edge cluster and the outgoing interface of the gateway 11 connected to the edge cluster. Thus, the gateway 11 may determine the forwarding exit of the data packet to be forwarded according to the network segment to which the destination IP of the data to be forwarded belongs.
For example, after assigning the target virtual IP address segment 10.1.0.0/24 to the edge cluster 21, the host service process 12 may create a static route for the edge cluster 21 that includes the target virtual IP address segment 10.1.0.0/24 and an identification of the outgoing interface on the gateway 11 that is connected to the edge cluster 21.
To facilitate those skilled in the art to understand the present solution, a specific example is given below with reference to the scenario shown in fig. 2, and the IP address management method provided in this embodiment is further described.
Firstly, an IPAM service process (main service process 12) of the data center 10 divides a preset virtual address range 10.1.0.0/22 into 255 virtual IP address segments according to a specified mask "24"; selecting a virtual IP address segment 10.1.0.0/24 from the edge cluster 21, and allocating a static route si1 for the edge cluster 21; selecting a virtual IP address field 10.1.0.1/24 from the network address to allocate to the edge cluster 22, and configuring a static route si2 for the edge cluster 22; selecting a virtual IP address segment 10.1.0.2/24 from the edge cluster 23, and allocating a static route si3 for the edge cluster 23; and selecting a virtual IP address segment 10.1.0.3/24 from the network to be distributed to the edge cluster 24, and configuring a static route si4 for the edge cluster 24.
Second, the edge node 212 creates new containers 31 and 32 in response to user actions, and the edge node 214 creates new containers 33 and 34 in response to user actions.
Third, the newly created container 31 sends an address allocation request R1 to the proxy IPAM service process (proxy service process 216) of the edge cluster 21, the newly created container 32 sends an address allocation request R2 to the proxy IPAM service process of the edge cluster 21, the newly created container 33 sends an address allocation request R3 to the proxy IPAM service process of the edge cluster 21, and the newly created container 34 sends an address allocation request R4 to the proxy IPAM service process of the edge cluster 21.
Fourth, the proxy IPAM service process of the edge cluster 21 responds to the address allocation request R1, selects the virtual IP address 10.1.0.1 from the virtual IP address segment 10.1.0.0/24 corresponding to the edge cluster 21 to allocate to the container 31, generates and configures the BGP route di1 of the virtual IP address 10.1.0.1 to the virtual router 215, and the virtual router 215 advertises the BGP route di1 to the edge nodes 211 to 214. The edge nodes 211 to 214 receive and store the BGP routes di1 advertised by the virtual router 215.
Fifth, the proxy IPAM service process of the edge cluster 21 responds to the address allocation request R2, selects a virtual IP address 10.1.0.2 from the virtual IP address segment 10.1.0.0/24 to allocate to the container 32, generates a BGP route di2 for the virtual IP address 10.1.0.2, and advertises the BGP route di2 to the edge nodes 211 to 214. The edge nodes 211 to 214 receive and store the BGP routes di2 advertised by the virtual router 215.
Similarly, the proxy IPAM service process of the edge cluster 21 may respond to the address allocation request R3 of the container 33, allocate a virtual IP address 10.1.0.3 to it, and generate a BGP route di3 advertisement to the edge nodes 211 to 214; and in response to the address allocation request R4 of the container 34, allocates a virtual IP address 10.1.0.4 thereto and generates a BGP route di4 advertisement to the edge nodes 211 to 214.
The edge nodes 211 to 214 receive and store the BGP routes di3 and di4 advertised by the virtual router 215.
Sixthly, the container 31 sends out a data packet data1 with the destination IP being the virtual IP address 10.1.0.4 of the container 34, the data packet data1 first reaches the edge node 212, and the edge node 212 finds the BGP route di4 matching the destination IP from the saved BGP routes.
Seventh, the edge node 212 sends the data packet data1 to the edge node 214 according to the BGP route di4, and the edge node 214 sends the data packet data1 to the container 34.
To sum up, according to the IP address management method and the edge cluster provided in the embodiments of the present application, a virtual IP address assignment function of a main service process is converted into an assignment function for a virtual IP address segment, the edge cluster is bound with the assigned virtual IP address segment, and an agent service process of the edge cluster selects a virtual IP address from the bound virtual IP address segment and assigns the virtual IP address to a newly-built virtual device in the cluster, so that a problem that the virtual devices cannot communicate due to a conflict between virtual IP addresses assigned by virtual devices in different edge clusters is avoided.
In the embodiments provided in the present application, it should be understood that the disclosed clusters and methods may be implemented in other ways. The embodiments described above are merely illustrative, and for example, the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of clusters and methods according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (8)
1. An IP address management method applied to an edge cluster, the edge cluster deploying a proxy service process communicating with a main service process of a data center, the edge cluster including a virtual router and at least two edge nodes communicating with the virtual router, the method comprising:
determining a target virtual IP address field distributed to the edge cluster by the main service process through the proxy service process;
when an address allocation request sent by newly-built virtual equipment in the edge cluster is received, selecting a virtual IP address from the target virtual IP address field to allocate to the newly-built virtual equipment;
configuring different autonomous system identifiers for the virtual router and each edge node respectively;
establishing external BGP connection between the virtual router and each edge node, so that the virtual router and each edge node are external BGP neighbors;
after a virtual IP address is selected from the target virtual IP address field through the proxy service process and is allocated to the newly-built virtual device, a BGP route is generated for the allocated virtual IP address, and the generated BGP route is configured on the virtual router, so that the virtual router advertises the generated BGP route to an EBGP neighbor;
and storing the received BGP route advertised by the virtual router at each edge node, and forwarding data to other edge nodes in the edge cluster according to the stored BGP route.
2. The method according to claim 1, wherein the target virtual IP address segment allocated by the edge cluster is one of at least two virtual IP address segments obtained by dividing a preset virtual address range by the host service process according to a specified mask.
3. The method of claim 1 or 2, wherein the virtual router communicates with a gateway of the data center based on a Border Gateway Protocol (BGP).
4. The method according to claim 3, wherein the virtual router and the gateway of the data center are EBGP neighbors to each other, and a static route corresponding to the edge cluster is configured in the gateway, and the static route includes the target virtual IP address segment and an outgoing interface of the gateway connected to the edge cluster.
5. An edge cluster is characterized in that a proxy service process which is communicated with a main service process of a data center is deployed;
the proxy service process is used for determining a target virtual IP address field distributed by the main service process for the edge cluster, and selecting a virtual IP address from the target virtual IP address field to be distributed to the newly-built virtual equipment when receiving an address distribution request sent by the newly-built virtual equipment in the edge cluster;
the edge cluster comprises a virtual router and at least two edge nodes communicated with the virtual router, wherein the virtual router and each edge node are respectively configured with different autonomous system identifiers; external BGP connection is established between the virtual router and each edge node, so that the virtual router and each edge node are external BGP neighbors;
the proxy service process is further configured to, after a virtual IP address is selected from the target virtual IP address field and allocated to the newly-built virtual device, generate a BGP route for the allocated virtual IP address, and configure the generated BGP route to the virtual router, so that the virtual router advertises the generated BGP route to an EBGP neighbor;
and each edge node stores the received BGP route advertised by the virtual router and forwards data to other edge nodes in the edge cluster according to the stored BGP route.
6. The edge cluster of claim 5, wherein the target virtual IP address segment allocated to the edge cluster is one of at least two virtual IP address segments obtained by dividing a preset virtual address range by the main service process according to a specified mask.
7. The edge cluster of claim 5 or 6, wherein the virtual router communicates with a gateway of the data center based on a Border Gateway Protocol (BGP).
8. The edge cluster according to claim 7, wherein the virtual router and the gateway of the data center are EBGP neighbors to each other, a static route corresponding to the edge cluster is configured in the gateway, and the static route includes the target virtual IP address segment and an outgoing interface of the gateway connected to the edge cluster.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910640070.6A CN110266833B (en) | 2019-07-16 | 2019-07-16 | IP address management method and edge cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910640070.6A CN110266833B (en) | 2019-07-16 | 2019-07-16 | IP address management method and edge cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110266833A CN110266833A (en) | 2019-09-20 |
| CN110266833B true CN110266833B (en) | 2022-03-29 |
Family
ID=67926439
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910640070.6A Active CN110266833B (en) | 2019-07-16 | 2019-07-16 | IP address management method and edge cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110266833B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20210036705A (en) * | 2019-09-26 | 2021-04-05 | 삼성전자주식회사 | Electronic apparatus and method for controlling thereof |
| CN110912827B (en) * | 2019-11-22 | 2021-08-13 | 北京金山云网络技术有限公司 | Route updating method and user cluster |
| CN111131333B (en) * | 2020-02-24 | 2022-10-28 | 广州虎牙科技有限公司 | Business data pushing method and server cluster |
| CN112087336B (en) * | 2020-09-11 | 2022-09-02 | 杭州海康威视系统技术有限公司 | Deployment and management method and device of virtual IP service system and electronic equipment |
| CN112202937B (en) * | 2020-09-30 | 2021-11-30 | 中国核动力研究设计院 | Instrument control simulation system IP allocation method, system, equipment and storage medium |
| CN113766042B (en) * | 2021-01-20 | 2024-09-20 | 北京沃东天骏信息技术有限公司 | Container address configuration method, system, device, equipment and medium |
| CN114866467B (en) * | 2022-05-27 | 2024-07-02 | 济南浪潮数据技术有限公司 | Cluster communication method, device, system, equipment and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103814352A (en) * | 2012-12-31 | 2014-05-21 | 华为技术有限公司 | Virtual equipment reconstruction method and apparatus |
| CN105141512A (en) * | 2015-06-29 | 2015-12-09 | 清华大学 | Unified network configuration and control method supporting packet/circuit mixed exchange network |
| CN106331150A (en) * | 2016-09-18 | 2017-01-11 | 北京百度网讯科技有限公司 | Method and device for scheduling cloud servers |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917436A (en) * | 2005-08-17 | 2007-02-21 | 中国长城计算机深圳股份有限公司 | Method for realizing concentrating type management for network devices based on Web |
| US9813343B2 (en) * | 2013-12-03 | 2017-11-07 | Akamai Technologies, Inc. | Virtual private network (VPN)-as-a-service with load-balanced tunnel endpoints |
| CN103729234B (en) * | 2013-12-20 | 2017-06-27 | 中电长城网际系统应用有限公司 | A kind of cluster virtual machine management method and device |
| CN106559246B (en) * | 2015-09-30 | 2020-01-10 | 新华三技术有限公司 | Cluster implementation method and server |
| CN106331210B (en) * | 2016-08-19 | 2019-08-13 | 中国银联股份有限公司 | IP address distribution method and device in a kind of system for cloud computing |
| US10999100B2 (en) * | 2017-10-02 | 2021-05-04 | Vmware, Inc. | Identifying multiple nodes in a virtual network defined over a set of public clouds to connect to an external SAAS provider |
| CN108494894A (en) * | 2018-03-27 | 2018-09-04 | 快云信息科技有限公司 | A kind of privately owned cloud cluster access system and cut-in method |
-
2019
- 2019-07-16 CN CN201910640070.6A patent/CN110266833B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103814352A (en) * | 2012-12-31 | 2014-05-21 | 华为技术有限公司 | Virtual equipment reconstruction method and apparatus |
| CN105141512A (en) * | 2015-06-29 | 2015-12-09 | 清华大学 | Unified network configuration and control method supporting packet/circuit mixed exchange network |
| CN106331150A (en) * | 2016-09-18 | 2017-01-11 | 北京百度网讯科技有限公司 | Method and device for scheduling cloud servers |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110266833A (en) | 2019-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110266833B (en) | IP address management method and edge cluster | |
| EP3624408B1 (en) | Method for generating forwarding table entry, controller, and network device | |
| US8125891B2 (en) | Method and system for multi-layer network routing | |
| US7889675B2 (en) | Method and system for multi-layer network routing | |
| CN107968752B (en) | SID acquisition method and device | |
| US20210344565A1 (en) | Software defined access fabric without subnet restriction to a virtual network | |
| CN106878480B (en) | DHCP service process sharing method and device | |
| WO2022166465A1 (en) | Message processing method and related apparatus | |
| EP3503484B1 (en) | Message transmission methods and devices | |
| US20230254238A1 (en) | Container routing algorithm using ospf | |
| CN110247778A (en) | Installation method of operating system, device, electronic equipment and storage medium | |
| WO2022142932A1 (en) | Route processing method, and related apparatus and network system | |
| CN114338518B (en) | Route processing method and network equipment | |
| CN113364683B (en) | Route sending method and equipment | |
| CN110601882B (en) | Two-layer private network system and configuration method | |
| CN111630814B (en) | Method for automatically setting up session conforming to dynamic routing protocol by first device and second device | |
| CN115208857A (en) | Address allocation method, device and equipment | |
| CN114125876A (en) | Communication method and related device | |
| CN113328942B (en) | Configuration issuing method and device and computer equipment | |
| US20240146646A1 (en) | Edge platform management device, method for operating edge platform management device, and edge gateway device | |
| CN117501664A (en) | Edge platform management device, operation method of edge platform management device, and edge gateway device | |
| CN116980297A (en) | Message processing method, device and system | |
| CN115941387A (en) | Method and device for receiving and sending border gateway protocol route and storage medium | |
| CN113132221A (en) | Method and device for processing routing information | |
| CN114025025A (en) | SRv6SID issuing method and network equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |