CN115174524A - Floating IP distribution method, device, electronic equipment and storage medium - Google Patents

Floating IP distribution method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN115174524A
CN115174524A CN202210546612.5A CN202210546612A CN115174524A CN 115174524 A CN115174524 A CN 115174524A CN 202210546612 A CN202210546612 A CN 202210546612A CN 115174524 A CN115174524 A CN 115174524A
Authority
CN
China
Prior art keywords
floating
target
segment
information
section
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.)
Granted
Application number
CN202210546612.5A
Other languages
Chinese (zh)
Other versions
CN115174524B (en
Inventor
邢召林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tianyi Cloud Technology Co Ltd
Original Assignee
Tianyi Cloud Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tianyi Cloud Technology Co Ltd filed Critical Tianyi Cloud Technology Co Ltd
Priority to CN202210546612.5A priority Critical patent/CN115174524B/en
Publication of CN115174524A publication Critical patent/CN115174524A/en
Priority to PCT/CN2022/141583 priority patent/WO2023221508A1/en
Application granted granted Critical
Publication of CN115174524B publication Critical patent/CN115174524B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/5092—Address allocation by self-assignment, e.g. picking addresses at random and testing if they are already in use

Abstract

The application provides a floating IP allocation method, a floating IP allocation device, electronic equipment and a storage medium, and relates to the technical field of computers. Responding to an acquisition request of a target device, determining a target IP section from each IP section according to floating information corresponding to the acquisition request and section information of each IP section in a mysql database, and determining a corresponding target IP set from a redis database according to the target IP section, wherein the target IP set comprises at least one floating IP which is not distributed in the target IP section, so as to acquire the target floating IP from the target IP set and distribute the target floating IP to the target device. Therefore, after the target IP segment is determined in the mysql database, the target floating IP can be quickly acquired from the corresponding target IP set in the redis database, and the target floating IP is successfully distributed to the target equipment, so that the efficiency and the performance of distributing the floating IP are improved.

Description

Floating IP distribution method, device, electronic equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a floating IP allocation method and device, electronic equipment and a storage medium.
Background
A Floating IP (Floating IP) is generally an IP address that is public and accessible by the internet, and is not automatically assigned to an entity device (host, router, load balancer, etc.), the private cloud uses the private address internally, and the private address inside the private cloud cannot be routed, and only services passing through the Floating IP intranet entity can be identified and accessed by the extranet, and similarly, traffic of the extranet can only pass through the Floating IP to reach the services inside the private cloud.
The traditional floating IP allocation scheme is that when a target device requests to acquire a floating IP, the corresponding floating IP is acquired from a mysql database, and the floating IP is allocated to the target device. However, because the mysql database is multi-threaded, when a plurality of target devices simultaneously request to acquire a floating IP, floating IP allocation may fail, and meanwhile, the speed of acquiring the floating IP from the mysql database is slow, so that the efficiency and performance of allocating the floating IP by using the conventional floating IP allocation scheme are poor.
Disclosure of Invention
In order to solve the existing technical problem, embodiments of the present application provide a method and an apparatus for allocating a floating IP, an electronic device, and a storage medium, which can improve efficiency and performance of allocating a floating IP.
In order to achieve the above purpose, the technical solution of the embodiment of the present application is implemented as follows:
in a first aspect, an embodiment of the present application provides a floating IP allocation method, where the method includes:
responding to a target equipment acquisition request, and determining a target IP subsection from each IP subsection according to floating information corresponding to the acquisition request and the subsection information of each IP subsection in a mysql database;
determining a corresponding target IP set from a redis database according to the target IP segment; wherein the target IP set comprises at least one floating IP in the target IP segment that is unallocated;
and acquiring a target floating IP from the target IP set, and distributing the target floating IP to the target equipment.
In the floating IP allocation method provided in the embodiment of the present application, in response to an acquisition request of a target device, a target IP segment may be determined from the IP segments according to floating information corresponding to the acquisition request and segment information of each IP segment in a mysql database, a corresponding target IP set is determined from a redis database according to the target IP segment, the determined target IP set includes at least one floating IP that is not allocated in the target IP segment, a target floating IP is acquired from the target IP set, and the target floating IP is allocated to the target device. The segmentation information of each IP segment is stored in the mysql database, the IP set containing the floating IP is stored in the redis database, meanwhile, the redis database is operated in a single thread mode, and the floating IP is obtained from the redis database at a high speed, so that when the target device requests to obtain the floating IP and determines the target IP segment from each IP segment of the mysql database, the target floating IP can be quickly obtained from the corresponding target IP set in the redis database and successfully allocated to the target device, and the efficiency and the performance of allocating the floating IP are improved.
In an optional embodiment, the segment information includes the number of unallocated floating IPs in the corresponding IP segment and the starting floating IP and the terminating floating IP in the IP segment; determining a target IP subsection from each IP subsection according to the floating information corresponding to the acquisition request and the subsection information of each IP subsection in the mysql database, wherein the determining comprises the following steps:
if the floating information corresponding to the acquisition request is that the unspecified floating IP is acquired, randomly selecting an IP subsection comprising the unassigned floating IP from the mysql database as a target IP subsection according to the unassigned floating IP number in the subsection information of each IP subsection;
if the floating information corresponding to the acquisition request is to acquire a specified floating IP, determining an IP segment which contains the specified floating IP between an initial floating IP and a final floating IP and is included in the segment information from the mysql database, and taking the determined IP segment as a target IP segment;
and if the floating information corresponding to the acquisition request is to acquire a floating IP in a specified IP section, and the specified IP section in the mysql database comprises the floating IP which is not allocated according to the floating IP number which is not allocated in the section information of the specified IP section, taking the specified IP section as a target IP section.
In this embodiment, when the target device requests to obtain an unspecified floating IP, an IP segment including an unassigned floating IP may be randomly selected from the mysql database as a corresponding target IP segment; when the target equipment requests to acquire the specified floating IP, an IP section containing the specified floating IP between the initial floating IP and the termination floating IP in the mysql database can be used as a corresponding target IP section; when the target device requests to acquire a floating IP in the designated IP section, wherein the floating IP can be an unspecified IP or an appointed IP, whether the designated IP section contains the unallocated floating IP can be determined through a mysql database, and if the designated IP section contains the unallocated floating IP, the designated IP section is the target IP section. Therefore, the corresponding target IP segment can be accurately determined from the mysql database according to different acquisition requests of the target equipment.
In an optional embodiment, the obtaining a target floating IP from the target IP set includes:
if the floating information corresponding to the acquisition request is to acquire an unspecified floating IP, randomly acquiring a floating IP from the target IP set as a target floating IP;
and if the floating information corresponding to the acquisition request is to acquire a specified floating IP and the target IP set comprises the specified floating IP, taking the specified floating IP as a target floating IP.
In this embodiment, when the target device requests to obtain an unspecified floating IP, a floating IP may be randomly obtained from a set of target IPs determined in the redis database as a target floating IP; when the target device requests to acquire the specified floating IP, if the specified floating IP is contained in the target IP set determined in the redis database, the specified floating IP is taken as the target floating IP. Therefore, the corresponding target floating IP can be obtained from the corresponding target IP set of the redis database according to different obtaining requests of the target device, the obtaining efficiency of the floating IP is improved, and the user experience degree is improved.
In an optional embodiment, the method further comprises:
responding to a release request of the target equipment, and determining the target floating IP included in the release request and a target IP section corresponding to the target floating IP;
according to the target IP segmentation, determining a corresponding target IP set from the redis database, and adding the target floating IP to the target IP set;
and updating the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database.
In this embodiment, when the target device no longer uses the target floating IP, and requests to release the target floating IP, the target floating IP may be added to the corresponding target IP set of the redis database, and the number of unallocated floating IPs in the corresponding target IP segment in the mysql database may be updated. So that the floating IP that needs to be released can be quickly and accurately written into the database again.
In an optional embodiment, the method further comprises:
responding to a sealing prohibition request of the operation and maintenance equipment, and determining an object floating IP (Internet protocol) which is contained in the sealing prohibition request and needs to be sealed;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a forbidden state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP fragment of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the fragment information of each IP fragment, and determining the IP set of the object corresponding to the IP fragment of the object from the redis database; and removing the object floating IP from the object IP set, and updating the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database.
In this embodiment, when the operation and maintenance device finds that the target device uses the object floating IP abnormally and requests to block the object floating IP, it may first determine whether the object floating IP is allocated according to allocation information of each floating IP in the mysql database, and if the object floating IP is allocated, modify the state of the object floating IP in the mysql database to a disabled state; if the object floating IP is not allocated, determining an object IP section corresponding to the object floating IP through a mysql database, removing the object floating IP from a corresponding object IP set in a redis database, and updating the number of the unallocated floating IPs in the object IP section in the mysql database. Therefore, when the target equipment improperly uses the floating IP of the object, the floating IP of the object is forbidden to be sealed, so that the target equipment cannot continuously use the floating IP of the object, and the use reasonability of the floating IP is ensured.
In an optional embodiment, the method further comprises:
responding to an unsealing request of the operation and maintenance equipment, and determining an object floating IP needing to be unsealed contained in the unsealing request;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a use state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP fragment of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the fragment information of each IP fragment, and determining the IP set of the object corresponding to the IP fragment of the object from the redis database; and adding the object floating IP to the object IP set, and updating the number of the floating IPs which are not distributed in the segmentation information of the object IP segments in the mysql database.
In this embodiment, when the operation and maintenance device determines that the object floating IP can be decapsulated and requests to decapsulate the object floating IP, it may first determine whether the object floating IP is already allocated according to allocation information of each floating IP in the mysql database, and if the object floating IP is already allocated, modify the state of the object floating IP in the mysql database to a use state; if the object floating IP is not allocated, determining an object IP section corresponding to the object floating IP through a mysql database, adding the object floating IP into a corresponding object IP set in a redis database, and updating the number of the unallocated floating IPs in the object IP section in the mysql database. By unsealing the object floating IP, the target device can continue to use the object floating IP, thereby ensuring the reasonability of the use of the floating IP.
In a second aspect, an embodiment of the present application further provides a floating IP allocation apparatus, where the apparatus includes:
the target segmentation determining unit is used for responding to an acquisition request of target equipment, and determining target IP segments from all IP segments according to floating information corresponding to the acquisition request and segment information of all IP segments in a mysql database;
a target set determining unit, configured to determine, according to the target IP segment, a corresponding target IP set from a redis database; wherein the target IP set comprises at least one floating IP in the target IP segment that is unallocated;
and the target IP allocation unit is used for acquiring a target floating IP from the target IP set and allocating the target floating IP to the target equipment.
In an optional embodiment, the segment information includes the number of unallocated floating IPs in the corresponding IP segment and the starting floating IP and the terminating floating IP in the IP segment; the target segment determining unit is specifically configured to:
if the floating information corresponding to the acquisition request is that the unspecified floating IP is acquired, randomly selecting an IP subsection comprising the unassigned floating IP from the mysql database as a target IP subsection according to the unassigned floating IP number in the subsection information of each IP subsection;
if the floating information corresponding to the acquisition request is to acquire a specified floating IP, determining an IP segment which contains the specified floating IP between an initial floating IP and a final floating IP and is included in the segment information from the mysql database, and taking the determined IP segment as a target IP segment;
and if the floating information corresponding to the acquisition request is to acquire a floating IP in a specified IP section, and the specified IP section in the mysql database comprises the floating IP which is not allocated according to the floating IP number which is not allocated in the section information of the specified IP section, taking the specified IP section as a target IP section.
In an optional embodiment, the target IP allocation unit is specifically configured to:
if the floating information corresponding to the acquisition request is to acquire an unspecified floating IP, randomly acquiring a floating IP from the target IP set as a target floating IP;
and if the floating information corresponding to the acquisition request is to acquire a specified floating IP and the target IP set comprises the specified floating IP, taking the specified floating IP as a target floating IP.
In an optional embodiment, the apparatus further comprises a floating IP releasing unit configured to:
responding to a release request of the target equipment, and determining the target floating IP included in the release request and a target IP section corresponding to the target floating IP;
according to the target IP subsection, determining a corresponding target IP set from the redis database, and adding the target floating IP to the target IP set;
and updating the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database.
In an optional embodiment, the apparatus further comprises a floating IP barring unit for:
responding to a sealing prohibition request of the operation and maintenance equipment, and determining an object floating IP (Internet protocol) which is contained in the sealing prohibition request and needs to be sealed;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a forbidden state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP section of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the section information of each IP section, and determining an IP set of the object corresponding to the IP section of the object from the redis database; and removing the object floating IP from the object IP set, and updating the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database.
In an optional embodiment, the apparatus further includes a floating IP decapsulating unit, configured to:
responding to an unsealing request of operation and maintenance equipment, and determining an object floating IP (Internet protocol) which is contained in the unsealing request and needs to be unsealed;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a use state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP fragment of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the fragment information of each IP fragment, and determining the IP set of the object corresponding to the IP fragment of the object from the redis database; and adding the object floating IP to the object IP set, and updating the number of the floating IPs which are not distributed in the segmentation information of the object IP segments in the mysql database.
In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the floating IP allocation method of the first aspect is implemented.
In a fourth aspect, this application embodiment further provides an electronic device, including a memory and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed by the processor, the processor is enabled to implement the floating IP allocation method of the first aspect.
The technical effect brought by any one implementation manner in the second aspect to the fourth aspect may refer to the technical effect brought by the corresponding implementation manner in the first aspect, and details are not described here again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a flowchart of a floating IP allocation method according to an embodiment of the present application;
fig. 2 is a flowchart of another floating IP allocation method according to an embodiment of the present application;
fig. 3 is a flowchart of a floating IP release process according to an embodiment of the present application;
fig. 4 is a flowchart of a floating IP barring process according to an embodiment of the present application;
fig. 5 is a flowchart of a floating IP decapsulation process according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a floating IP distribution apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another floating IP distribution apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. 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 references in the specification of the present application to the terms "comprises" and "comprising," and variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
A floating IP is generally a public IP address that can be accessed by the internet and is not automatically allocated to a physical device (host, router, load balancer, etc.), the private address is used inside the private cloud, the private address inside the private cloud cannot be routed, the private address can be identified and accessed by the external network only through the services of the floating IP internal network entity, and similarly, the traffic of the external network can reach the services inside the private cloud only through the floating IP.
The floating IP is a public network IP, a public network user enters a Virtual Private Cloud (VPC) through a floating IP applied, the floating IP can be bound on a Virtual Machine (VM), a Bare Machine (BM), an elastic network card, an expansion network card, a HAVIP, a NAT gateway or a Load Balance (LB), only an IPv4 address in a VNet has the floating IP, and the floating IP of IPv6 is not supported.
The main advantage of floating IP is flexibility, free allocation on demand. Floating IP is suitable for both failover and service switchover. The floating IP provides a unified IP to the outside instead of an IP address actually providing a service to the outside.
The traditional floating IP allocation scheme is that when a target device requests to acquire a floating IP, the corresponding floating IP is acquired from a mysql database, and the floating IP is allocated to the target device. However, because the mysql database is multi-threaded, when a plurality of target devices simultaneously request to acquire a floating IP, floating IP allocation may fail, and meanwhile, the speed of acquiring the floating IP from the mysql database is slow, so that the efficiency and performance of allocating the floating IP by using the conventional floating IP allocation scheme are poor.
For example, in response to a request for randomly acquiring a floating IP by a target device a and a target device B at the same time, a conventional floating IP allocation scheme may enable a dual thread to preselect a floating IP1 for both the target device a and the target device B from a mysql database, and modify an allocation state of the floating IP1 in the mysql database, assuming that a thread corresponding to the target device a succeeds in modifying an allocation state of the floating IP1 and allocates the floating IP to the target device a at the same time, a thread corresponding to the target device B fails to modify an allocation state of the floating IP1, and at the same time, the floating IP is allocated to the target device B for identification, that is, the target device B fails to acquire the floating IP at this time.
In order to prevent the floating IP from being allocated unsuccessfully, in response to a request for randomly acquiring the floating IP by the target device a and the target device B at the same time, the conventional floating IP allocation scheme may also lock the IP set 1 when the thread corresponding to the target device a acquires the floating IP in the IP set 1, so that the target device B needs to wait until the target floating IP determined in the IP set 1 is successfully allocated to the target device a, and the IP1 set is unlocked, so that the thread corresponding to the target device B can be started to acquire the floating IP in the IP set 1, but the allocation scheme may cause the acquisition waiting time delay of the floating IP, and increase the allocation duration of the floating IP.
In order to improve the efficiency and performance of allocating floating IPs, an embodiment of the present application provides a floating IP allocation method, where in response to an acquisition request of a target device, a target IP segment is determined from each IP segment according to floating information corresponding to the acquisition request and segment information of each IP segment in a mysql database, and a corresponding target IP set is determined from a redis database according to the target IP segment, where the determined target IP set includes at least one floating IP that is not allocated in the target IP segment, and a target floating IP is acquired from the target IP set and allocated to the target device.
The technical solutions provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The word "exemplary" is used hereinafter to mean "serving as an example, embodiment, or illustration. Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.
The embodiment of the application provides a floating IP allocation method, as shown in fig. 1, including the following steps:
step S101, responding to an acquisition request of a target device, and determining a target IP segment from all IP segments according to floating information corresponding to the acquisition request and segment information of all IP segments in a mysql database.
The fragment information may include the number of unallocated floating IPs in the corresponding IP fragment, and the starting floating IP and the terminating floating IP in the corresponding IP fragment.
Specifically, if the floating information corresponding to the acquisition request is to acquire an unassigned floating IP, one IP segment including the unassigned floating IP is randomly selected from the mysql database as the target IP segment according to the unassigned floating IP number in the segment information of each IP segment. For example, if the target device requests to randomly obtain a floating IP, an IP segment containing an available floating IP may be randomly selected from the IP segments in the mysql database, and if the IP segment is IP segment 1, IP segment 1 may be used as the target IP segment.
And if the floating information corresponding to the acquisition request is the designated floating IP, determining an IP segment which contains the designated floating IP between the initial floating IP and the termination floating IP and is included in the segment information from the mysql database, and taking the determined IP segment as a target IP segment. For example, assuming that the specified floating IP requested to be obtained by the target device is 50, the starting floating IP included in the segment information of the IP segment 1 of the mysql database is 1, and the terminating floating IP is 100, the target IP segment corresponding to the specified floating IP may be determined to be the IP segment 1 according to the starting floating IP and the terminating floating IP included in the segment information of each IP segment of the mysql database.
And if the floating information corresponding to the acquisition request is to acquire the floating IP in the appointed IP section and the appointed IP section in the mysql database comprises the floating IP which is not allocated according to the floating IP number which is not allocated in the section information of the appointed IP section, taking the appointed IP section as the target IP section. Assuming that the specified IP segment requested to be obtained by the target device is IP segment 1, and the number of unallocated floating IPs in the segment information of IP segment 1 of the mysql database is 60, IP segment 1 can be directly used as the target floating IP.
And step S102, determining a corresponding target IP set from a redis database according to the target IP segment.
And after the target IP segments are determined in the mysql database according to the acquisition request of the target equipment, uniquely determining the corresponding target IP sets in the redis database according to the corresponding relation between the IP segments in the mysql database and the IP sets in the redis database.
And step S103, acquiring the target floating IP from the target IP set, and distributing the target floating IP to the target equipment.
And if the floating information corresponding to the acquisition request is to acquire the unspecified floating IP, randomly acquiring a floating IP from the target IP set as a target floating IP. And if the floating information corresponding to the acquisition request is to acquire the appointed floating IP and the target IP set comprises the appointed floating IP, taking the appointed floating IP as the target floating IP.
The floating IP allocation method provided in the embodiment of the present application may be applied to multiple Available Zones (AZ). At least two AZs, and usually three AZs, can be included in a region, and the purpose is to enable customers to run production applications and databases, and build stronger availability, fault tolerance and extensibility. In the region level deployment structure, the floating IP allocation can be deployed in the control node, and the redis database can be deployed in the cache node.
In the floating IP allocation scheme provided in the present application, segment information of an IP segment is stored in a mysql database, an IP set including a floating IP is stored in a redis database, that is, each floating IP is stored in the redis database, and each floating IP is stored in a manner of an IP set corresponding to an IP segment. The floating IP allocation method in the present application is performed as follows:
when a target device requests to acquire a specified floating IP in a specified IP section, whether the specified IP section comprises an available floating IP can be inquired in a mysql database according to the specified IP section, if the specified IP section comprises the available floating IP, an IP set corresponding to the specified IP section is inquired in a redis database, whether the IP set comprises the specified floating IP is determined, if the specified floating IP is contained, the specified floating IP is taken out from the IP set, and the specified floating IP is allocated to the target device;
when the target device requests to acquire an unspecified floating IP in an appointed IP section, whether the appointed IP section comprises an available floating IP can be inquired in the mysql database according to the appointed IP section, if the appointed IP section comprises the available floating IP, an IP set corresponding to the appointed IP section is inquired in the redis database, a floating IP is randomly taken out from the IP set, and the floating IP is distributed to the target device;
when a target device requests to acquire a specified floating IP in an unspecified IP segment, according to the specified floating IP, inquiring an IP segment containing the specified floating IP in a mysql database, determining whether the IP segment contains an available floating IP, if the IP segment contains the available floating IP, inquiring an IP set corresponding to the IP segment in a redis database, determining whether the IP set contains the specified floating IP, and if the IP set contains the specified floating IP, taking out the specified floating IP from the IP set and allocating the specified floating IP to the target device;
when the target device requests to acquire an unspecified floating IP in an unspecified IP segment, the target device may first query the mysql database for an IP segment including an available floating IP, then query the redis database for an IP set corresponding to the IP segment, randomly take out a floating IP from the IP set, and allocate the floating IP to the target device.
Specifically, in an embodiment, the floating IP allocation method provided in this embodiment may also be implemented according to a process shown in fig. 2, and as shown in fig. 2, the method includes the following steps:
step S201, in response to an acquisition request of a target device, determining a request parameter corresponding to the acquisition request.
After receiving an acquisition request of a target device, a request parameter corresponding to the acquisition request can be determined, and the validity of the request parameter is verified at the same time.
Step S202, determining whether the request parameter contains the appointed IP subsection; if yes, go to step S203; if not, step S207 is executed.
Step S203, if the number of the unallocated floating IPs in the segmentation information of the designated IP segment in the mysql database is determined to include the unallocated floating IPs in the designated IP segment, a corresponding target IP set is determined from the redis database according to the designated IP segment.
Step S204, determining whether the appointed IP section in the request parameter contains the appointed floating IP; if yes, go to step S205; if not, step S206 is performed.
Step S205, if the target IP set comprises the specified floating IP, obtaining the specified floating IP from the target IP set, and distributing the specified floating IP to the target device.
Step S206, a floating IP is randomly acquired from the target IP set, and the floating IP is distributed to the target equipment.
Step S207, determining whether the request parameter contains a specified floating IP; if yes, go to step S208; if not, step S210 is executed.
Step S208, a target IP segment containing the appointed floating IP between the initial floating IP and the termination floating IP is determined from the mysql database.
Step S209, according to the target IP segment, determining a corresponding target IP set from the redis database, if the target IP set comprises the specified floating IP, acquiring the specified floating IP from the target IP set, and allocating the specified floating IP to the target device.
Step S210, according to the unallocated floating IP number in the segmentation information of each IP segmentation in the mysql database, randomly selecting a target IP segmentation comprising the unallocated floating IP from each IP segmentation.
And step S211, according to the target IP segment, determining a corresponding target IP set from the redis database, randomly acquiring a floating IP from the target IP set, and allocating the floating IP to the target equipment.
In some embodiments, when the target device decides not to use the allocated floating IP any more, it may request to release the floating IP, and the release procedure of the floating IP may be as shown in fig. 3, including the following steps:
step S301, in response to the release request of the target device, determining a target floating IP included in the release request and a target IP segment corresponding to the target floating IP.
When a release request of a target device is received, the validity of a request parameter corresponding to the release request also needs to be verified.
When the target device requests to release the target floating IP, the release request includes not only the target floating IP but also a target IP segment corresponding to the target floating IP.
Step S302, according to the target IP segment, determining a corresponding target IP set from the redis database, and adding the target floating IP to the target IP set.
According to the target IP segment included in the release request, a corresponding target IP set can be determined in a redis database, and after the target IP set is determined, the target floating IP included in the release request can be added into the target IP set.
Step S303, updating the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database.
After the target floating IP is added into the target IP set in the redis database, the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database is correspondingly updated, that is, the unallocated floating IP number in the segmentation information of the target IP segment is added with 1.
In other embodiments, in the process of using the allocated floating IP by the target device, there may be a case that the floating IP is not reasonably used, and when the operation and maintenance device finds that the target device does not reasonably use the floating IP, the operation and maintenance device may request to block the floating IP so that the target device cannot use the floating IP any more. Specifically, the forbidden process of the floating IP can be as shown in fig. 4, and includes the following steps:
step S401, in response to the sealing prohibition request of the operation and maintenance equipment, determining the floating IP of the object that needs to be sealed and is included in the sealing prohibition request.
When a seal forbidding request of the operation and maintenance equipment is received, the validity of a request parameter corresponding to the seal forbidding request needs to be verified.
Step S402, determining whether the object floating IP is distributed or not according to the distribution information of each floating IP in the mysql database; if yes, go to step S403; if not, step S404 is executed.
After the floating IP is allocated to the target device, the mysql database generates allocation information of the floating IP, which includes the allocated floating IP, IP fragment and status of the floating IP, and so on.
In step S403, the floating IP status of the object in the mysql database is modified to the disabled status.
Step S404, according to the initial floating IP and the termination floating IP included in the segment information of each IP segment, determining the object IP segment corresponding to the object floating IP, and determining the object IP set corresponding to the object IP segment from the redis database.
Step S405, the object floating IP is removed from the object IP set, and the number of the floating IPs which are not distributed in the segmentation information of the object IP segments in the mysql database is updated.
After an object IP set corresponding to the object floating IP is determined in the redis database, the object floating IP can be removed from the object IP set, and the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database is correspondingly updated, that is, the unallocated floating IP number in the segmentation information of the object IP segment is reduced by 1.
In other embodiments, after disabling the floating IP, after a period of time has elapsed, or when the operation and maintenance device decides to remove the disabled state of the floating IP, it may request to unseal the floating IP so that the target device may continue to use the floating IP or allocate the floating IP. Specifically, the floating IP decapsulation process may be as shown in fig. 5, and includes the following steps:
step S501, in response to the decapsulation request of the operation and maintenance device, determining an object floating IP that needs to be decapsulated and is included in the decapsulation request.
When an unsealing request of the operation and maintenance equipment is received, the validity of a request parameter corresponding to the unsealing request needs to be verified.
Step S502, determining whether the floating IP of the object is distributed according to the distribution information of each floating IP in the mysql database; if yes, go to step S503; if not, go to step S504.
In step S503, the floating IP status of the object in the mysql database is modified to the use status.
After the floating IP is allocated to the target device, the mysql database generates allocation information of the floating IP, which includes the allocated floating IP, IP fragment and status of the floating IP, and so on.
Step S504, according to the initial floating IP and the ending floating IP included in the segment information of each IP segment, determining an object IP segment corresponding to the object floating IP, and determining an object IP set corresponding to the object IP segment from the redis database.
And step S505, adding the object floating IP into the object IP set, and updating the number of the floating IPs which are not distributed in the segmentation information of the object IP segments in the mysql database.
After an object IP set corresponding to the object floating IP is determined in the redis database, the object floating IP can be added into the object IP set, and the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database is correspondingly updated, that is, the unallocated floating IP number in the segmentation information of the object IP segment is added with 1.
The application provides a floating IP allocation method which can solve the problems that floating IP allocation fails and floating IP allocation waiting time is too long due to the fact that a mysql database is only adopted for floating IP allocation in the prior art. According to the floating IP allocation method, the segmentation information of the floating IP segments can be stored in the mysql database, the IP set comprising the floating IP is stored in the redis database, and therefore after the corresponding floating IP segments are accurately determined from the mysql database according to the floating IP information included in the acquisition request of the target equipment by means of multi-thread operation of the mysql database and single-thread operation of the redis database, the target floating IP can be quickly and successfully acquired from the redis database and allocated to the target equipment, the efficiency and performance of allocating the floating IP are improved, and meanwhile the success rate of allocating the floating IP can be improved.
The floating IP allocation method shown in fig. 1 is based on the same inventive concept, and a floating IP allocation apparatus is further provided in the embodiment of the present application. Because the device is a device corresponding to the floating IP allocation method of the present application, and the principle of the device for solving the problem is similar to that of the method, the implementation of the device can refer to the implementation of the above method, and repeated details are not repeated.
Fig. 6 shows a schematic structural diagram of a floating IP allocation apparatus provided in an embodiment of the present application, and as shown in fig. 6, the floating IP allocation apparatus includes a target segment determining unit 601, a target set determining unit 602, and a target IP allocation unit 603.
The target segment determining unit 601 is configured to, in response to an acquisition request of a target device, determine a target IP segment from the IP segments according to floating information corresponding to the acquisition request and segment information of each IP segment in the mysql database;
a target set determining unit 602, configured to determine, according to the target IP segment, a corresponding target IP set from a redis database; wherein the target IP set comprises at least one floating IP in the target IP segment that is unassigned;
and a target IP allocating unit 603, configured to acquire the target floating IP from the target IP set, and allocate the target floating IP to the target device.
In an alternative embodiment, the segment information includes the number of unallocated floating IPs in the corresponding IP segment and the starting floating IP and the terminating floating IP in the IP segment; the target segmentation determining unit 601 is specifically configured to:
if the floating information corresponding to the acquisition request is the floating IP which is not appointed, an IP subsection comprising the floating IP which is not distributed is randomly selected from the mysql database as a target IP subsection according to the floating IP number which is not distributed in the subsection information of each IP subsection;
if the floating information corresponding to the acquisition request is the designated floating IP, determining an IP segment which contains the designated floating IP between the initial floating IP and the termination floating IP contained in the segment information from the mysql database, and taking the determined IP segment as a target IP segment;
and if the floating information corresponding to the acquisition request is the floating IP in the designated IP segment, and the designated IP segment in the mysql database comprises the unallocated floating IP according to the unallocated floating IP number in the segment information of the designated IP segment, taking the designated IP segment as the target IP segment.
In an alternative embodiment, the target IP allocating unit 603 is specifically configured to:
if the floating information corresponding to the acquisition request is to acquire an unspecified floating IP, randomly acquiring a floating IP from the target IP set as a target floating IP;
and if the floating information corresponding to the acquisition request is to acquire the specified floating IP and the target IP set comprises the specified floating IP, taking the specified floating IP as the target floating IP.
In an alternative embodiment, as shown in fig. 7, the apparatus may further include a floating IP releasing unit 701, configured to:
responding to a release request of target equipment, and determining a target floating IP included in the release request and a target IP section corresponding to the target floating IP;
according to the target IP segmentation, determining a corresponding target IP set from a redis database, and adding a target floating IP into the target IP set;
and updating the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database.
In an alternative embodiment, as shown in fig. 7, the apparatus may further include a floating IP barring unit 702 for:
responding to a seal forbidding request of the operation and maintenance equipment, and determining an object floating IP needing seal forbidding contained in the seal forbidding request;
if the floating IP of the object is determined to be distributed according to the distribution information of each floating IP in the mysql database, the state of the floating IP of the object in the mysql database is modified into a forbidden state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP section of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the section information of each IP section, and determining the IP set of the object corresponding to the IP section of the object from the redis database; and removing the object floating IP from the object IP set, and updating the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database.
In an alternative embodiment, as shown in fig. 7, the apparatus may further include a floating IP decapsulating unit 703 configured to:
responding to an unsealing request of the operation and maintenance equipment, and determining an object floating IP needing to be unsealed contained in the unsealing request;
if the floating IP of the object is determined to be distributed according to the distribution information of each floating IP in the mysql database, the state of the floating IP of the object in the mysql database is modified into a use state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP section of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the section information of each IP section, and determining the IP set of the object corresponding to the IP section of the object from the redis database; and adding the object floating IP into the object IP set, and updating the number of the unallocated floating IPs in the segmentation information of the object IP segment in the mysql database.
The electronic equipment is based on the same inventive concept as the method embodiment, and the embodiment of the application also provides the electronic equipment. The electronic device may be used for a floating IP assignment process. In this embodiment, the structure of the electronic device may be as shown in fig. 8, including a memory 801 and one or more processors 802.
A memory 801 for storing computer programs executed by the processor 802. The memory 801 may mainly include a program storage area and a data storage area, where the program storage area may store an operating system, programs required for running an instant messaging function, and the like; the storage data area can store various instant messaging information, operation instruction sets and the like.
The memory 801 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 801 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a hard disk (HDD) or a solid-state drive (SSD), or the memory 801 may be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Memory 801 may be a combination of the above.
The processor 802 may include one or more Central Processing Units (CPUs), or be a digital processing unit, etc. A processor 802 for implementing the floating IP allocation method described above when invoking a computer program stored in memory 801.
The specific connection medium between the memory 801 and the processor 802 is not limited in the embodiment of the present application. In fig. 8, the memory 801 and the processor 802 are connected by a bus 803, the bus 803 is represented by a thick line in fig. 8, and the connection manner between other components is merely illustrative and not limited. The bus 803 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to execute the floating IP allocation method in the above-described embodiment.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
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 person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application.

Claims (10)

1. A method of floating IP allocation, comprising:
responding to an acquisition request of target equipment, and determining a target IP subsection from each IP subsection according to floating information corresponding to the acquisition request and the subsection information of each IP subsection in a mysql database;
determining a corresponding target IP set from a redis database according to the target IP segment; wherein the target IP set comprises at least one floating IP in the target IP segment that is unassigned;
and acquiring a target floating IP from the target IP set, and distributing the target floating IP to the target equipment.
2. The method of claim 1, wherein the fragment information includes an unallocated floating IP number in a corresponding IP fragment and a starting floating IP and a terminating floating IP in the IP fragment; determining a target IP subsection from each IP subsection according to the floating information corresponding to the acquisition request and the subsection information of each IP subsection in the mysql database, wherein the determining comprises the following steps:
if the floating information corresponding to the acquisition request is that the unspecified floating IP is acquired, randomly selecting an IP subsection comprising the unassigned floating IP from the mysql database as a target IP subsection according to the unassigned floating IP number in the subsection information of each IP subsection;
if the floating information corresponding to the acquisition request is to acquire a specified floating IP, determining an IP segment which contains the specified floating IP between an initial floating IP and a final floating IP and is included in the segment information from the mysql database, and taking the determined IP segment as a target IP segment;
and if the floating information corresponding to the acquisition request is to acquire a floating IP in a specified IP section and the specified IP section in the mysql database comprises the floating IP which is not distributed according to the floating IP quantity which is not distributed in the section information of the specified IP section, taking the specified IP section as a target IP section.
3. The method of claim 2, wherein the obtaining a target floating IP from the set of target IPs comprises:
if the floating information corresponding to the acquisition request is to acquire an unspecified floating IP, randomly acquiring a floating IP from the target IP set as a target floating IP;
and if the floating information corresponding to the acquisition request is to acquire a specified floating IP and the target IP set comprises the specified floating IP, taking the specified floating IP as a target floating IP.
4. The method of claim 1, wherein the method further comprises:
responding to a release request of the target equipment, and determining the target floating IP included in the release request and a target IP section corresponding to the target floating IP;
according to the target IP segmentation, determining a corresponding target IP set from the redis database, and adding the target floating IP to the target IP set;
and updating the unallocated floating IP number in the segmentation information of the target IP segment in the mysql database.
5. The method of claim 1, wherein the method further comprises:
responding to a seal forbidding request of the operation and maintenance equipment, and determining an object floating IP needing seal forbidding contained in the seal forbidding request;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a forbidden state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP fragment of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the fragment information of each IP fragment, and determining the IP set of the object corresponding to the IP fragment of the object from the redis database; and removing the object floating IP from the object IP set, and updating the unallocated floating IP number in the segmentation information of the object IP segment in the mysql database.
6. The method of claim 1, wherein the method further comprises:
responding to an unsealing request of operation and maintenance equipment, and determining an object floating IP (Internet protocol) which is contained in the unsealing request and needs to be unsealed;
if the floating IP of the object is determined to be distributed according to the distribution information of all the floating IPs in the mysql database, the state of the floating IP of the object in the mysql database is modified into a use state;
if the floating IP of the object is determined to be not distributed according to the distribution information of each floating IP in the mysql database, determining the IP section of the object corresponding to the floating IP of the object according to the initial floating IP and the termination floating IP included in the section information of each IP section, and determining an IP set of the object corresponding to the IP section of the object from the redis database; and adding the object floating IP to the object IP set, and updating the number of the floating IPs which are not distributed in the segmentation information of the object IP segments in the mysql database.
7. A floating IP distribution apparatus, comprising:
the target segmentation determining unit is used for responding to an acquisition request of target equipment, and determining target IP segments from all IP segments according to floating information corresponding to the acquisition request and segment information of all IP segments in a mysql database;
a target set determining unit, configured to determine, according to the target IP segment, a corresponding target IP set from a redis database; wherein the target IP set comprises at least one floating IP in the target IP segment that is unallocated;
and the target IP allocation unit is used for acquiring a target floating IP from the target IP set and allocating the target floating IP to the target equipment.
8. The apparatus of claim 7, wherein the fragmentation information includes a number of floating IPs unallocated in a corresponding IP fragment and a starting floating IP and a terminating floating IP in the IP fragment; the target segmentation determining unit is specifically configured to:
if the floating information corresponding to the acquisition request is that the unspecified floating IP is acquired, randomly selecting an IP subsection comprising the unassigned floating IP from the mysql database as a target IP subsection according to the unassigned floating IP number in the subsection information of each IP subsection;
if the floating information corresponding to the acquisition request is to acquire a specified floating IP, determining an IP segment which contains the specified floating IP between an initial floating IP and a final floating IP and is included in the segment information from the mysql database, and taking the determined IP segment as a target IP segment;
and if the floating information corresponding to the acquisition request is to acquire a floating IP in a specified IP section, and the specified IP section in the mysql database comprises the floating IP which is not allocated according to the floating IP number which is not allocated in the section information of the specified IP section, taking the specified IP section as a target IP section.
9. An electronic device, comprising a processor and a memory, wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 6.
10. A computer-readable storage medium, characterized in that it comprises program code for causing an electronic device to perform the steps of the method of any one of claims 1 to 6, when said program code is run on the electronic device.
CN202210546612.5A 2022-05-18 2022-05-18 Floating IP distribution method and device, electronic equipment and storage medium Active CN115174524B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202210546612.5A CN115174524B (en) 2022-05-18 2022-05-18 Floating IP distribution method and device, electronic equipment and storage medium
PCT/CN2022/141583 WO2023221508A1 (en) 2022-05-18 2022-12-23 Floating ip allocation method and apparatus, and electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210546612.5A CN115174524B (en) 2022-05-18 2022-05-18 Floating IP distribution method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN115174524A true CN115174524A (en) 2022-10-11
CN115174524B CN115174524B (en) 2024-01-02

Family

ID=83483196

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210546612.5A Active CN115174524B (en) 2022-05-18 2022-05-18 Floating IP distribution method and device, electronic equipment and storage medium

Country Status (2)

Country Link
CN (1) CN115174524B (en)
WO (1) WO2023221508A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023221508A1 (en) * 2022-05-18 2023-11-23 天翼云科技有限公司 Floating ip allocation method and apparatus, and electronic device and storage medium

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656763A (en) * 2009-09-11 2010-02-24 华为技术有限公司 IP address automatic distribution method, client and server
US20110252129A1 (en) * 2010-04-12 2011-10-13 Chung-Ang University Industry-Academy Cooperation Apparatus and method for registering node and searching for floating internet protocol address using distributed network
CN104486452A (en) * 2014-09-23 2015-04-01 华为技术有限公司 Address processing method and related equipment and system
CN107241460A (en) * 2017-06-30 2017-10-10 联想(北京)有限公司 The processing method and electronic equipment of a kind of floating address
US9813374B1 (en) * 2015-06-10 2017-11-07 Amazon Technologies, Inc. Automated allocation using spare IP addresses pools
CN111262960A (en) * 2020-01-15 2020-06-09 山东汇贸电子口岸有限公司 Public cloud elastic public network IP cluster implementation method and system
WO2020258814A1 (en) * 2019-06-26 2020-12-30 三维通信股份有限公司 Method and device for ip address allocation and topology management in das system, and storage medium
CN113132503A (en) * 2019-12-31 2021-07-16 华为技术有限公司 Address allocation method and device
CN113176930A (en) * 2021-05-19 2021-07-27 重庆紫光华山智安科技有限公司 Floating address management method and system for virtual machine in container
CN113810513A (en) * 2021-08-16 2021-12-17 新浪网技术(中国)有限公司 Configuration management method and system for elastic public network IP
CN114401251A (en) * 2022-03-25 2022-04-26 中科云策(深圳)科技成果转化信息技术有限公司 Internet-based IP address database processing system and method thereof
CN114500462A (en) * 2020-11-12 2022-05-13 阿里巴巴集团控股有限公司 Virtual private cloud network address allocation method and device, electronic equipment and medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013020267A1 (en) * 2011-08-08 2013-02-14 华为数字技术有限公司 Ip address allocation method, system and device
CN107800814B (en) * 2016-09-05 2021-08-13 国网江苏省电力公司信息通信分公司 Virtual machine deployment method and device
CN111107173B (en) * 2018-10-29 2023-04-07 中国移动通信集团浙江有限公司 IP address planning method and system of IP bearing network
CN112887322A (en) * 2021-02-07 2021-06-01 上海英方软件股份有限公司 Redis-based IP resource management method and device
CN115174524B (en) * 2022-05-18 2024-01-02 天翼云科技有限公司 Floating IP distribution method and device, electronic equipment and storage medium

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656763A (en) * 2009-09-11 2010-02-24 华为技术有限公司 IP address automatic distribution method, client and server
US20110252129A1 (en) * 2010-04-12 2011-10-13 Chung-Ang University Industry-Academy Cooperation Apparatus and method for registering node and searching for floating internet protocol address using distributed network
CN104486452A (en) * 2014-09-23 2015-04-01 华为技术有限公司 Address processing method and related equipment and system
US9813374B1 (en) * 2015-06-10 2017-11-07 Amazon Technologies, Inc. Automated allocation using spare IP addresses pools
CN107241460A (en) * 2017-06-30 2017-10-10 联想(北京)有限公司 The processing method and electronic equipment of a kind of floating address
WO2020258814A1 (en) * 2019-06-26 2020-12-30 三维通信股份有限公司 Method and device for ip address allocation and topology management in das system, and storage medium
CN113132503A (en) * 2019-12-31 2021-07-16 华为技术有限公司 Address allocation method and device
CN111262960A (en) * 2020-01-15 2020-06-09 山东汇贸电子口岸有限公司 Public cloud elastic public network IP cluster implementation method and system
CN114500462A (en) * 2020-11-12 2022-05-13 阿里巴巴集团控股有限公司 Virtual private cloud network address allocation method and device, electronic equipment and medium
CN113176930A (en) * 2021-05-19 2021-07-27 重庆紫光华山智安科技有限公司 Floating address management method and system for virtual machine in container
CN113810513A (en) * 2021-08-16 2021-12-17 新浪网技术(中国)有限公司 Configuration management method and system for elastic public network IP
CN114401251A (en) * 2022-03-25 2022-04-26 中科云策(深圳)科技成果转化信息技术有限公司 Internet-based IP address database processing system and method thereof

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023221508A1 (en) * 2022-05-18 2023-11-23 天翼云科技有限公司 Floating ip allocation method and apparatus, and electronic device and storage medium

Also Published As

Publication number Publication date
CN115174524B (en) 2024-01-02
WO2023221508A1 (en) 2023-11-23

Similar Documents

Publication Publication Date Title
CN108924268B (en) Container cloud service system and pod creation method and device
US10686756B2 (en) Method and apparatus for managing MAC address generation for virtualized environments
US9633040B2 (en) Distributed processing system including a name node and a plurality of data nodes, and method of operating the same
JP2019175415A (en) Method and system for allocating system resources
JP5919609B2 (en) Multi-tenant access to multi-desktops on host machine partitions in a service provider network
US20190392150A1 (en) Network-accessible computing service for micro virtual machines
KR102361929B1 (en) Capacity Management in Provider Networks Using Dynamic Host Device Instance Model Reconfiguration
US9705741B2 (en) Dynamically allocating network addresses
US8695079B1 (en) Allocating shared resources
CN108279979B (en) Method and device for binding CPU for application program container
US20160170855A1 (en) Implementing shared adapter configuration updates concurrent with maintenance actions in a virtualized system
JP2016170669A (en) Load distribution function deployment method, load distribution function deployment device, and load distribution function deployment program
CN111585887A (en) Communication method and device based on multiple networks, electronic equipment and storage medium
CN115174524A (en) Floating IP distribution method, device, electronic equipment and storage medium
CN108667750B (en) Virtual resource management method and device
CN112367256B (en) Creation method, device and storage medium
US11824798B2 (en) Priority based route programming in a network
US9417900B2 (en) Method and system for automatic assignment and preservation of network configuration for a virtual machine
CN114938394A (en) Cross-cluster network control method, device, equipment and storage medium
US20180032250A1 (en) Efficiency in active memory sharing
CN110347473B (en) Method and device for distributing virtual machines of virtualized network elements distributed across data centers
US20210019168A1 (en) Remote memory in hypervisor
KR20150095978A (en) Distributed Storage System using Local Disk of Computing Node on Cloud Computing
JP2017156894A (en) Virtual machine management device, system, and virtual machine management method
TW201518951A (en) Control center deployment method for cloud-based system

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