WO2020233020A1 - 预分配容器ip的方法、装置、计算机设备及存储介质 - Google Patents

预分配容器ip的方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2020233020A1
WO2020233020A1 PCT/CN2019/118241 CN2019118241W WO2020233020A1 WO 2020233020 A1 WO2020233020 A1 WO 2020233020A1 CN 2019118241 W CN2019118241 W CN 2019118241W WO 2020233020 A1 WO2020233020 A1 WO 2020233020A1
Authority
WO
WIPO (PCT)
Prior art keywords
container
allocated
ips
idle
preset
Prior art date
Application number
PCT/CN2019/118241
Other languages
English (en)
French (fr)
Inventor
黄桂钦
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020233020A1 publication Critical patent/WO2020233020A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0826—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • 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/5061—Pools of addresses

Definitions

  • This application relates to the field of cloud computing technology, and in particular to a method, device, computer equipment, and storage medium for pre-allocating container IP.
  • the container application needs to be expanded, which involves assigning IP to the newly added container.
  • the existing method of allocating container IP needs to apply for the allocation of IP resources in advance, and the application process is complicated (for example, it needs to apply first, and then go through level-by-level review, etc.), which is very time-consuming.
  • the container IP after application needs to be paid for, so once the application is successful, you need to pay. Since IP resources will be applied for and allocated in advance, this may increase costs.
  • the embodiments of the present application provide a method, device, computer device, and storage medium for pre-allocating container IP, which can reduce the time for applying for IP allocation when adding a new container to the container application, and at the same time can avoid cost waste caused by IP allocation in advance.
  • an embodiment of the present application provides a method for pre-allocating container IP, the method including:
  • the allocation request is used to pre-allocate an IP for a container that the container application needs to add; obtain the area where the container application is created; obtain an idle IP in the preset IP address pool in the area ; Determine the IP number of the pre-allocated container IP; determine the same number of IPs from the idle IP according to preset rules, and set the determined IP status to the pre-allocated state; assign the determined IP in the pre-allocated state to The container application allows the container application to take out the corresponding IP from the IP in the pre-allocated state when adding a new container and allocate it to the newly added container.
  • an embodiment of the present application provides a device for pre-allocating a container IP.
  • the device for pre-allocating a container IP includes a unit for executing the method described in the first aspect.
  • an embodiment of the present application provides a computer device, the computer device includes a memory, and a processor connected to the memory;
  • the memory is used to store a computer program
  • the processor is used to run the computer program stored in the memory to execute the method described in the first aspect above.
  • an embodiment of the present application provides a computer-readable storage medium that stores a computer program that, when executed by a processor, implements the method described in the first aspect.
  • the embodiment of this application pre-allocates the IP of the container for the container application, and can pre-allocate the IP for the container that the container application needs to add.
  • the time required to apply for IP allocation is reduced , And reduce the cost waste caused by IP allocation in advance.
  • FIG. 1 is a schematic flowchart of a method for pre-allocating container IP according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for pre-allocating container IP according to another embodiment of the present application.
  • FIG. 3 is a schematic diagram of a sub-flow of a method for pre-allocating container IP according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a sub-flow of a method for pre-allocating container IP according to an embodiment of the present application
  • FIG. 5 is a schematic block diagram of a device for pre-allocating container IP according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of an apparatus for pre-allocating container IP according to another embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a quantity determining unit provided by an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a pre-allocation unit provided by an embodiment of the present application.
  • Fig. 9 is a schematic block diagram of a computer device provided by an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a method for pre-allocating container IP provided by an embodiment of the present application. As shown in Figure 1, the method includes S101-S106.
  • S101 Receive an allocation request for pre-allocated container IP, where the allocation request is used to pre-allocate an IP for a container that needs to be added to the container application.
  • the container in the pre-allocated container IP refers to a container that is predicted to increase in business demand and needs to be added, and the container IP is the IP corresponding to the container that needs to be added. It should be noted that in this application, the container to be added is not actually added, because once the container is added and the IP is assigned, then the container needs to be paid. In this application, if there is no new container, the IP address resource is allocated to the container that needs to be added in advance, so that after the container is added, the IP address of the newly-added container can be quickly assigned from the pre-allocated IP address. The new container is quickly put into use.
  • the allocation request for pre-allocating the container IP may be triggered by a request to create a container application.
  • receiving a pre-allocated container IP allocation request includes: if a request to create a container application is received, obtaining identification information carried in the request to create a container application, and determining whether the identification information includes the identification of the pre-allocated container IP; if The identification information includes the identification of the pre-allocated container IP, and it is determined that the allocation request of the pre-allocated container IP is received.
  • the container IP is pre-allocated for the container application when the container application is created.
  • one of the application scenarios involved is that a data item (including options) whether to pre-allocate the container IP is set in the interface of creating the container application, and the option of whether to pre-allocate the container IP is received or selected by the user; If a request to create a container application is received (which can be triggered by the user clicking a button related to creating the container application), the identification information carried in the request to create the container application is obtained, and it is determined whether the identification information includes the identification of the pre-allocated container IP.
  • the options of pre-allocated container IP include: “Yes” and “No”, if the corresponding flags of "Yes” and “No” are “1” and “0” respectively. If the corresponding identification information in the request to create the container application is "1”, then it is determined that the identification information includes the identification of the pre-allocated container IP, then it is determined that the allocation request for the pre-allocated container IP is received; If the corresponding identification information is "0", it is determined that the identification information does not include the identification of the pre-allocated container IP, and it is determined that the allocation request of the pre-allocated container IP is not received.
  • the allocation request for the pre-allocated container IP may be triggered by the user clicking the relevant button of the pre-allocated container IP after the container application is created. Understandably, after the container application is created, the container IP is pre-allocated for the container application.
  • the container IP when a container application is created, a certain number of containers will be created first and the IP will be allocated to the created certain number of containers at the same time.
  • the container created for the container application When creating a container application, the container created for the container application will be charged and can be used immediately. The pre-allocated container IP will not be charged, and the pre-allocated IP must be allocated to the newly added container before charging.
  • the container application area refers to the location of the computer room where the container application is created. It consists of two parts: the "application environment” for creating the container application and the "area” + “security area” for the container application. Among them, “safe area” is understood as a sub-area under "area”.
  • the "application environment” of a container application includes a production environment, a test environment, and a development environment. Among them, the production environment can be understood as an environment that can provide services for Internet users, a test environment is an environment that is used for internal testing, and a development environment is an environment that is used for internal development. For each environment, there is a corresponding organic room.
  • the "area” + "safe area” of the container application can be understood as creating the container application in the sub-area corresponding to the "xxx safe area” under the "xx area” computer room. Understandably, the machines in the computer room are also divided into sub-areas. Finally, the area where the container application is created can be understood as a sub-area corresponding to a certain safe area under a certain area of the computer room in a certain environment. For example, the area where the container application is created is: in the sub-area A under the computer room of the Baosight area in the test environment. It should be noted that the above division of the container application area is only an example, and in this application, the division of the container application area is not limited.
  • the area where the container application is created can be obtained. If the container IP is pre-allocated for the container application when the container application is created, the data items corresponding to the area where the container application is created are set in the container application creation interface, such as the "application environment" of the container application and the "container application” Area” + “Security Area”, get the content of the corresponding data item, you can get the area where the container application is created. If the container IP is pre-allocated for the container application after the container application is created, the area where the container application is created can be directly obtained according to the information of the container application.
  • the IPs in the IP address pool are all LAN IPs. Understandably, an IP address pool is pre-allocated in the area where the container application is created.
  • the IP address pool is the preset IP address pool.
  • the IP address pool includes idle IP. The status of idle can be obtained according to the status of the IP.
  • Idle IP Idle IP is not allocated and can be allocated to container applications in this area at any time. In general, the number of free IPs in the IP address pool is sufficient for container applications in the area.
  • FIG. 2 is a schematic flowchart of a method for distributing container IP provided by another embodiment of the present application. Before step S103, the method further includes:
  • S103a Detect whether the ratio of the number of idle IPs in the preset IP address pool of the area to the preset number of idle IPs in the area is lower than a preset ratio.
  • the preset ratio is 10%. That is, if the ratio of idle IP data in the area IP address pool to the preset number of idle IPs in the area is lower than the preset ratio.
  • step S103b is executed; if it is not lower than the preset ratio, step S103 is executed, which is to execute acquiring preset IPs in the area Steps for free IP in the address pool.
  • S103b Send a request for applying for a new IP address segment.
  • S103c Receive a new IP address segment allocated by the user according to the request, fill the IP in the new IP address segment into an IP address pool, and set the status of the newly filled IP to an idle state.
  • This embodiment can actively request to apply for a new IP address segment when the ratio of the number of idle IPs in the area to the preset number of idle IPs is lower than the preset ratio, and after the new IP address segment is allocated, the new Fill the IP in the IP address segment of the IP address pool into the IP address pool, and set the status of the newly filled IP to be idle. In this way, you can obtain idle IPs according to the IP status to avoid insufficient idle IP addresses in the area to affect the cloud Use of the platform.
  • the time when the new IP address segment is filled is recorded. In this way, on the one hand, relevant information can be consulted later, and on the other hand, it is convenient for the subsequent allocation of container IP.
  • the method further includes:
  • enabling the firewall function includes setting the accessible ports such as 80, 8080, 7001, etc., and setting the accessible IP. After the firewall function is set, the IP can be put into use. Specifically, the firewall function of all IPs in the IP network segment can be set at one time. Understandably, the services provided by the IP corresponding to an IP network segment may be similar or identical.
  • the existing method of allocating container IP needs to apply for the allocation of IP resources in advance. After applying for IP resources, it is also necessary to enable the firewall function for each applied IP separately. Turning on one by one is very time-consuming and easy to make mistakes.
  • the solution in this application will enable the firewall function for the IP in the IP network segment, and enable the entire IP network segment at once. The firewall function in this saves time and reduces the error rate.
  • the firewall function is enabled for the IP in advance, if a container is created and the pre-allocated IP is assigned to the created container, the container can be put into use immediately. When a new container needs to be added and put into use immediately due to business needs, the time required to apply for an IP allocation and enable the firewall function for the IP is reduced, and the new container can be put into use immediately.
  • S104 Determine the IP quantity of the pre-allocated container IP.
  • the IP number of the pre-allocated container IP can be determined based on historical data, or directly based on the number set by the user, or the default number can be used directly.
  • step S104 includes the following steps S301-S306.
  • S301 Detect whether a request for setting the IP quantity of the pre-allocated container IP by the user is received.
  • step S302 If a request for setting the IP number of the pre-allocated container IP by the user is received, step S302 is performed; if a setting request for the user to set the IP number of the pre-allocated container IP is not received, step S303 is performed.
  • S302 Set the IP quantity of the pre-allocated container IP according to the setting request, and use the IP quantity of the pre-allocated container IP set by the user as the determined IP quantity of the pre-allocated container IP.
  • the preset traffic information of the container application similar to the container application and the corresponding container number information are obtained. Assuming that the container application corresponds to a certain social software A, then obtain the preset traffic information of the container application B similar to the container application and the corresponding container number information, using the traffic information of the container application B and the corresponding container number The number information is used as a reference basis. If the container application has existed before and there is related historical data information at the same time, then the traffic information corresponding to the container application and the corresponding container number information are obtained.
  • the historical data information may be one-time data information, or may be related multiple times information.
  • step S304 is executed; if no historical data information is obtained, step S306 is executed.
  • the historical data information of the container application includes: the container application has relevant historical data information, so that the historical data information of the container application can be directly obtained; the container application has no relevant historical data information, but preset The container application similar to the container application has related historical data information, and thus the historical data information of the container application similar to the container application is obtained. If no historical data information is obtained, including: the container application has no relevant historical data information, and a preset container application similar to the container application also has no relevant historical data information.
  • S304 Determine the total number of containers that the container application needs to create according to the traffic information and the corresponding container number information.
  • the acquired historical data information is the traffic information corresponding to the container application and the number of corresponding containers, according to the current traffic information of the container application and the acquired historical data information before the current time, determine what the container application needs The total number of containers created. For example, the user traffic information of a social software on the day of the Spring Festival last year is A1, and the number of corresponding containers is B1.
  • the preset traffic information corresponding to the container application similar to the container application and the corresponding container number information according to the current traffic information of the container application, and the acquired preset similar to the container application
  • the historical data information of the container application determines the total number of containers that the container application needs to create.
  • S305 Determine the number of IPs of pre-allocated container IPs according to the total number of containers that the container application needs to create and the number of containers that the container application has created.
  • the number of IPs of the pre-allocated container IP the total number of containers that the container application needs to create-the number of containers that the container application has created.
  • the container IP is pre-allocated for the container application when the container application is created (pre-allocated container IP is understood to be the IP allocated for future expansion of the container application)
  • the number of containers that have been created is the container application creation The number of containers corresponding to completion.
  • S306 Acquire a preset IP quantity as the determined IP quantity of the pre-allocated container IP.
  • the preset number of IPs can also be understood as the default number of IPs.
  • This embodiment further defines how to determine the IP number of the pre-allocated container IP.
  • S105 Determine the same number of IPs from the idle IPs according to a preset rule, and set the status of the determined IPs to a pre-allocated state.
  • the preset rule is to first allocate an IP from the IP address segment of the container IP that has been allocated by the container application, and if the IP is not enough, allocate an IP from the next IP address segment that has a free IP.
  • it can be randomly assigned, or it can be assigned in ascending or descending order of IP addresses.
  • step S105 includes the following steps S401-S406.
  • S401 Acquire an IP address segment of the container IP that has been allocated by the container application.
  • S402 Detect whether there are a corresponding number of idle IPs in the IP address segment.
  • the corresponding number refers to the determined IP number of the pre-allocated container IP.
  • the number of idle IPs in the IP address segment is less than the number of IPs of the pre-allocated container IP, then the corresponding number of IPs is obtained from multiple IP address pools.
  • S405 If there are no idle IPs in the IP address segment, determine the same number of idle IPs as the determined IP from the next IP address segment with idle IPs.
  • S406 Set the state of the determined IP to a pre-allocated state.
  • the IP address segments with idle IPs are obtained according to the sequence of the filling time of the IP address segments, which facilitates IP management.
  • IP status is pre-allocated, the IP will not be charged, and the IP can no longer be used by other container applications.
  • S106 Allocate the determined IP in the pre-allocated state to the container application, so that the container application takes out the corresponding IP from the IP in the pre-allocated state when adding a new container and allocates it to the newly added container.
  • Allocate the determined IP in the pre-allocated state to the container application specifically, bind the determined IP in the pre-allocated state to the container application and record it in a configuration file corresponding to the container application.
  • the above method embodiments pre-allocate the container IP for the container application.
  • the IP can be assigned to the container of the container application in advance.
  • the time required to apply for an IP allocation is reduced.
  • the container is put into use immediately, and the cost waste caused by IP allocation in advance is reduced.
  • the method further includes:
  • S106a If the expansion request of the container application is received, create a container of the container application, where the number of created containers is the same as the number of containers to be added in the expansion request.
  • S106b Take out IPs in the pre-allocated state related to the container application and allocate the same number of IPs as the number of newly added containers to the created container.
  • the number of newly added containers is one, one IP is taken from the pre-allocated IP and assigned to the newly added container; if there are multiple newly added containers, then one is taken from the pre-allocated IP Multiple IPs, and assigned to multiple new containers. In this way, the speed of putting the container into use is accelerated.
  • the method further includes:
  • the IP status of the pre-allocated IP corresponding to the container application is set to the idle state; or a release request to release the pre-allocated IP is received, and the pre-allocated IP corresponding to the release request is The IP state is set to idle state. In this way, it is avoided that the pre-allocated IP is pre-allocated, and the pre-allocated IP is not used for a long time to waste the morning resources.
  • Fig. 5 is a schematic block diagram of a device for pre-allocating container IP provided by an embodiment of the present application.
  • the device includes a unit corresponding to the above method for pre-allocating container IP.
  • the device 100 includes a request receiving unit 101, an area acquiring unit 102, an idle IP acquiring unit 103, a quantity determining unit 104, a pre-allocation unit 105, and an application binding unit 106.
  • the request receiving unit 101 is configured to receive a pre-allocated container IP allocation request, where the allocation request is used to pre-allocate an IP for a container that needs to be added to the container application.
  • the area acquiring unit 102 is configured to acquire the area where the container application is created.
  • the idle IP obtaining unit 103 is configured to obtain idle IPs in the preset IP address pool in the area.
  • the quantity determining unit 104 is configured to determine the IP quantity of the pre-allocated container IP.
  • the pre-allocation unit 105 is configured to determine the same number of IPs from the idle IPs according to a preset rule, and set the status of the determined IP to a pre-allocation state.
  • the application binding unit 106 is configured to allocate the determined IP in the pre-allocated state to the container application, so that the container application takes out the corresponding IP from the IP in the pre-allocated state when adding a new container and allocates it to the new IP. Increased container.
  • FIG. 6 it is a schematic block diagram of a device for pre-allocating container IP according to another embodiment of the present application.
  • the device 200 includes a request receiving unit 101, an area acquiring unit 102, and a ratio detecting unit 103a.
  • the request sending unit 103b, the address filling unit 103c, the idle IP obtaining unit 103, the quantity determining unit 104, the pre-allocation unit 105, and the application binding unit 106 correspond to those in the embodiment of FIG. 5 respectively.
  • the request receiving unit 101, the area acquiring unit 102, the idle IP acquiring unit 103, the quantity determining unit 104, the pre-allocation unit 105, and the application binding unit 106 correspond to those in the embodiment of FIG. 5 respectively.
  • FIG. 5 In the description.
  • the ratio detecting unit 103a is configured to detect whether the ratio of the number of idle IPs in the preset IP address pool of the area to the preset number of idle IPs in the area is lower than the preset ratio.
  • the request sending unit 103b is configured to send a request for applying for a new IP address segment if the ratio of the number of idle IPs to the preset number of idle IPs in the area is lower than the preset ratio.
  • the address filling unit 103c is configured to receive a new IP address segment allocated by the user according to the request, fill the IP in the new IP address segment into the IP address pool, and set the status of the newly filled IP to an idle state.
  • the address filling unit 103c is configured to receive a new IP address segment allocated by the user according to the request, fill the IP in the new IP address segment into the IP address pool, and set the newly filled IP address The state is idle, and the time when the new IP address segment is filled is also recorded.
  • the device 200 further includes a firewall opening unit 103d.
  • the firewall enabling unit 103d is used to enable the firewall function of the IP in the newly filled IP address segment.
  • the device 200 further includes a creation unit 106a and an IP allocation unit 106b.
  • the creating unit 106a is configured to create container instances of the container application if the expansion request of the container application is received, wherein the number of container instances created is the same as the number of container instances to be added in the expansion request .
  • the IP allocation unit 106b is configured to extract a corresponding number of IPs from the IPs in the pre-allocated state related to the container application and allocate them to the created container instance.
  • the device 200 further includes a setting unit.
  • the setting unit is configured to set the IP status of the pre-allocated IP corresponding to the container application to an idle state if it is detected that the container application is offline; or if a release request to release the pre-allocated IP is received, the release request The IP state of the corresponding pre-allocated IP is set to the idle state.
  • the request receiving unit 101 includes an identification acquiring unit and a request receiving determining unit.
  • the identification acquiring unit is configured to, if a request to create a container application is received, acquire identification information carried in the request to create a container application, and determine whether the identification information includes an identification of the pre-allocated container IP.
  • the request reception determining unit is configured to determine that the allocation request of the pre-allocated container IP is received if the identification information includes the identifier of the pre-allocated container IP.
  • the quantity determining unit 104 includes a request detecting unit 1041, a historical data determining unit 1042, a total number determining unit 1043, and an IP quantity determining unit 1044.
  • the request detection unit 1041 is configured to detect whether a user setting request for setting the IP quantity of the pre-allocated container IP is received.
  • the IP quantity determining unit 1044 if receiving a request for setting the IP quantity of the pre-allocated container IP from the user, set the IP quantity of the pre-allocated container IP according to the setting request, and use the IP quantity of the pre-allocated container IP set by the user as the determined The IP number of the pre-allocated container IP.
  • the historical data determining unit 1042 is configured to determine whether the historical data information of the container application has been obtained if the user's request for setting the IP number of the pre-allocated container IP is not received, wherein the historical data information includes the information before the current time.
  • the flow information of the container application or the preset container application similar to the container application and the corresponding number of containers.
  • the total number determining unit 1043 is configured to determine the total number of containers that the container application needs to create according to the traffic information and corresponding container number information if the historical data information of the container application is acquired.
  • the IP quantity determining unit 1044 is further configured to determine the IP quantity of the pre-allocated container IP according to the total number of containers that the container application needs to create and the number of containers that the container application has created.
  • the IP quantity determining unit 1044 is further configured to, if no historical data information is obtained, obtain the preset IP quantity as the determined IP quantity of the pre-allocated container IP.
  • the pre-allocation unit 105 includes an address segment acquisition unit 1051, an idle IP detection unit 1052, a pre-allocation determination unit 1053, and a state setting unit 1054.
  • the address segment obtaining unit 1051 is configured to obtain the IP address segment of the container IP allocated by the container application.
  • the idle IP detecting unit 1052 is used to detect whether there are corresponding numbers of idle IPs in the IP address segment.
  • the pre-allocation determining unit 1053 is configured to determine a corresponding number of idle IPs from the IP address segment as the determined IP if there are a corresponding number of idle IPs in the IP address segment.
  • the pre-allocation determining unit 1053 is further configured to, if the number of free IPs in the IP address segment is less than the number of IPs of the pre-allocated container IP, obtain the remaining free IPs in the IP address segment, and from the next IP with free IP Determine the remaining number of free IPs in the address segment, and use the acquired remaining free IP and the determined free IP as the determined IP, where the remaining number is the difference between the number of IPs and the number of remaining free IPs.
  • the pre-allocation determining unit 1053 is further configured to determine the same number of idle IPs as the determined IP from the next IP address segment with idle IP if there is no idle IP in the IP address segment.
  • the status setting unit 1054 is configured to set the status of the determined IP to the pre-allocated status.
  • the pre-allocation determining unit 1053 acquires the next IP address segment with free IP in the order of filling time of the IP address segment.
  • the above-mentioned apparatus may be implemented in the form of a computer program, and the computer program may run on the computer device as shown in FIG. 9.
  • FIG. 9 is a schematic block diagram of a computer device provided by an embodiment of the application.
  • the equipment is a server and other equipment in the cloud platform.
  • the device 300 includes a processor 302, a memory, and a network interface 303 connected through a system bus 301, where the memory may include a non-volatile storage medium 304 and an internal memory 305.
  • the non-volatile storage medium 304 can store an operating system 3041 and a computer program 3042.
  • the computer program 3042 stored in the non-volatile storage medium is executed by the processor 302, the aforementioned method of pre-allocating the container IP can be implemented.
  • the processor 302 is used to provide computing and control capabilities and support the operation of the entire device.
  • the internal memory 305 provides an environment for the operation of the computer program in the non-volatile storage medium.
  • the processor 302 can make the processor 302 execute the aforementioned method of pre-allocating the container IP.
  • the network interface 303 is used for network communication. Those skilled in the art can understand that the structure shown in FIG.
  • the processor 302 is configured to run a computer program stored in a memory to implement any embodiment of the method for pre-allocating container IP in this application.
  • the computer program may be stored in a storage medium, and the storage medium may be a computer-readable storage medium.
  • the computer program is executed by at least one processor in the computer system to implement the process steps of the foregoing method embodiment.
  • the storage medium may be a computer-readable storage medium.
  • the storage medium stores a computer program, which, when executed by a processor, implements any embodiment of the method for pre-allocating container IP in the present application.
  • the storage medium is a physical, non-transitory storage medium, such as a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk or an optical disk, and other physical storage that can store computer programs. medium.
  • ROM Read-Only Memory
  • the storage medium is a physical, non-transitory storage medium, such as a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk or an optical disk, and other physical storage that can store computer programs. medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请实施例提供一种预分配容器IP的方法、装置、计算机设备及存储介质，其涉及云计算技术领域，可应用于PaaS平台中。所述方法包括：接收为容器应用的需新增的容器预分配的分配请求；获取创建容器应用的区域；获取该区域中预设IP地址池中的空闲IP；确定预分配容器IP的IP数量；根据预设规则从空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；将所确定的预分配状态的IP分配给容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。

Description

预分配容器IP的方法、装置、计算机设备及存储介质
本申请要求于2019年05月17日提交中国专利局、申请号为201910411988.3、申请名称为“预分配容器IP的方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算技术领域，尤其涉及一种预分配容器IP的方法、装置、计算机设备及存储介质。
背景技术
当检测到业务需求量增加，需要对容器应用进行扩容，涉及到对新增的容器分配IP。现有的分配容器IP的方式需要提前申请分配IP资源，申请过程复杂(如需要先进行申请，然后再经过一级一级的审核等)，非常耗时。申请后的容器IP需要付费使用，因此一旦申请成功，即需要进行付费。由于会提前申请和分配IP资源，如此可能会导致费用增加。
发明内容
本申请实施例提供一种预分配容器IP的方法、装置、计算机设备及存储介质，可减少容器应用新增容器时申请分配IP的时间，同时可避免提前分配IP而造成的成本浪费。
第一方面，本申请实施例提供了一种预分配容器IP的方法，该方法包括：
接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP；获取创建所述容器应用的区域；获取所述区域中预设IP地址池中的空闲IP；确定预分配容器IP的IP数量；根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
第二方面，本申请实施例提供了一种预分配容器IP的装置，该预分配容器IP的装置包括用于执行上述第一方面所述的方法对应的单元。
第三方面，本申请实施例提供了一种计算机设备，所述计算机设备包括存储器，以及与所述存储器相连的处理器；
所述存储器用于存储计算机程序，所述处理器用于运行所述存储器中存储的计算机程序，以执行上述第一方面所述的方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，实现上述第一方面所述的方法。
本申请实施例通过为容器应用预分配容器的IP，可预先为容器应用需新增的容器分配IP，当由于业务需求，需立即新增容器并投入使用时，减少了需要申请分配IP的时间，并且减少提前分配IP而造成的成本浪费。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的预分配容器IP的方法的流程示意图；
图2是本申请另一实施例提供的预分配容器IP的方法的流程示意图；
图3是本申请实施例提供的预分配容器IP的方法的子流程示意图；
图4是本申请实施例提供的预分配容器IP的方法的子流程示意图；
图5是本申请实施例提供的预分配容器IP的装置的示意性框图；
图6是本申请另一实施例提供的预分配容器IP的装置的示意性框图；
图7是本申请实施例提供的数量确定单元的示意性框图；
图8是本申请实施例提供的预分配单元的示意性框图；
图9是本申请实施例提供的计算机设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是本申请实施例提供的预分配容器IP的方法的流程示意图。如图1所示，该方法包括S101-S106。
S101，接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP。
可以理解地，预分配容器IP中的容器指的是预测业务需求量会增加而需新增的容器，那么容器IP即为该需新增的容器所对应的IP。需要注意的是，在本申请中，需新增的容器实际上并没有新增，因为一旦新增容器并分配IP，那么就需要为该容器付费。在本申请中，在没有新增容器的情况下，预先为需要新增的容器分配IP地址资源，以在新增容器后可以快速地从预分配的IP地址中为新增容器分配IP并将新增容器快速的投入使用。
其中，在一实施例中，预分配容器IP的分配请求可以由创建容器应用的请求触发。具体地，接收预分配容器IP的分配请求，包括：若接收到创建容器应用的请求，获取创建容器应用的请求中携带的标识信息，判断所述标识信息是否包括预分配容器IP的标识；若所述标识信息包括预分配容器IP的标识，确定接收到预分配容器IP的分配请求。
可以理解地，在创建容器应用时就为该容器应用预分配容器IP。在该种情况下，所涉及的一个应用场景是，在创建容器应用的界面中设置有是否预分配容器IP的数据项(包括选项)，接收用户输入或者选择的是否预分配容器IP的选项；若接收到创建容器应用的请求(可以由用户点击创建容器应用的相关按钮触发)，获取创建容器应用的请求中携带的标识信息，判断所述标识信息是否包括预分配容器IP的标识。如预分配容器IP的选项中包括：“是”和“否”，若“是”和“否”对应的标识分别为“1”和“0”。若创建容器应用的请求中的对应标识信息为“1”，那么确定所述标识信息包括预分配容器IP的标识，则确定接收到预分配容器IP的分配请求；若创建容器应用的请求中的对应标识信息为“0”，那么确定所述标识信息不包括预分配容器IP的标识，则确定未接收到预分配容 器IP的分配请求。
在一实施例中，预分配容器IP的分配请求可以在容器应用创建完成后，由用户点击预分配容器IP的相关按钮触发。可以理解地，在容器应用创建完成后，再为该容器应用预分配容器IP。
需要注意的是，不管是否需要预分配容器IP，容器应用在创建时，都会先创建一定数量的容器并同时为创建的一定数量的容器分配IP。在创建容器应用时为该容器应用创建的容器会收费，并可以立即投入使用。而预分配的容器IP是不会收费的，并且需要将该预分配的IP分配给新增的容器后，才进行收费。
S102，获取创建所述容器应用的区域。
容器应用的区域指的是创建容器应用的机房位置，由两部分组成：创建容器应用的“应用环境”和容器应用的“区域”+“安全区域”。其中，“安全区域”理解为“区域”下的子区域。容器应用的“应用环境”包括生产环境、测试环境、开发环境。其中，生产环境可理解为可为互联网用户提供服务的环境，测试环境是内部用于测试所需要使用的环境，开发环境是内部用于开发所需要使用的环境。对于每一种环境都对应设置有机房。容器应用的“区域”+“安全区域”，可以理解为，将容器应用创建在“xx区域”机房下的“xxx安全区域”所对应的子区域中。可以理解地，机房中的机器也会划分了子区域的。最终，创建容器应用的区域可理解为，在某个环境中某个区域机房下的某个安全区域所对应的子区域中。如创建容器应用的区域为：测试环境中的宝信区域机房下的A子区域中。需要注意的是，以上容器应用的区域的划分只是一种实施例，在本申请中，并不限定容器应用的区域的划分。即无论容器应用的区域如何划分，都可以获取创建容器应用的区域。如若是在创建容器应用时为该容器应用预分配容器IP，那么在创建容器应用的界面中设置有创建容器应用的区域所对应的数据项，如容器应用的“应用环境”和容器应用的“区域”+“安全区域”，获取所对应的数据项的内容，即可获取创建容器应用的区域。如若是在容器应用创建完成后，再为该容器应用预分配容器IP，那么可根据容器应用的信息直接获取创建该容器应用的区域。
S103，获取所述区域中预设IP地址池中的空闲IP。
一般情况下，该IP地址池中的IP都是局域网IP。可以理解地，在创建容 器应用的区域中预先分配有IP地址池，该IP地址池即为预设IP地址池，该IP地址池中包括空闲IP，可以根据IP的状态来获取状态为空闲的空闲IP。空闲IP是没有被分配的，可以随时分配给该该区域下的容器应用。在一般情况下，IP地址池中的空闲IP数量足够该区域下的容器应用使用。
但是在一些情况下，也会存在IP地址池中的空闲IP数量不是很充足的情况。如此，在其他一些实施例中，如图2所示，图2是本申请另一实施例提供的与分布容器IP的方法流程示意图，在步骤S103之前，所述方法还包括：
S103a，检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例。
如预设比例为10％。即若所述区域IP地址池中的空闲IP数据与所述区域中的预设空闲IP数量的占比是否低于预设比例。
若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，执行步骤S103b；若不低于预设比例，执行步骤S103，即执行获取所述区域中预设IP地址池中的空闲IP的步骤。
S103b，发送申请新IP地址段的请求。
即若检测到空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，主动发送申请新IP地址段的请求。
S103c，接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
该实施例可在所述区域中的空闲IP数量与预设空闲IP数量的占比低于预设比例时，主动请求申请新的IP地址段，并在分配新的IP地址段后，将新的IP地址段中的IP填充到IP地址池，设置新填充的IP的状态为空闲状态，如此，就可以根据IP的状态来获取空闲IP，以避免所述区域中的空闲IP地址不足影响云平台的使用。
在一实施例中，在设置新填充的IP的状态为空闲状态的同时，记录该新的IP地址段填充的时间。如此，一方面可供后续查阅相关信息，另一方面，为后续分配容器IP提供方便。
在一实施例中，分配了新的IP地址段，设置新填充的IP的状态为空闲状态后，所述方法还包括：
S103d，开启新填充的IP网段的防火墙功能。
其中，开启防火墙功能，包括设置可以访问的端口如80、8080、7001等端口，以及设置可以访问的IP等。设置了防火墙功能后，该IP才可以真正投入使用。具体地，可一次性设置该IP网段的所有IP的防火墙功能。可以理解地，一个IP网段所对应的IP提供的服务可能是类似的或者相同的。
需要注意的是，现有的分配容器IP的方式需要提前申请分配IP资源，申请了IP资源后，还需要为每个申请的IP单独开启防火墙功能。一个一个的开启，非常耗时，也很容易出现纰漏，本申请中的方案在分配了新的IP网段后，即为IP网段中的IP开启防火墙功能，一次性全部开启整个IP网段中的防火墙功能，节省了时间，也降低了错误率。另一方面，由于提前为IP开启了防火墙功能，若创建容器，将预分配的IP分配给创建的容器后，该容器就可以立即投入使用。当由于业务需求，需立即新增容器并投入使用时，减少了需要申请分配IP以及为该IP开启防火墙功能的时间，可立即将新增容器投入使用。
S104，确定预分配容器IP的IP数量。
预分配容器IP的IP数量，可以根据历史数据来进行确定，也可以直接根据用户设置的数量进行确定，还可以直接使用默认的数量。
在一实施例中，如图3所示，步骤S104包括以下步骤S301-S306。
S301，检测是否接收到用户设置预分配容器IP的IP数量的设置请求。
若接收到用户设置预分配容器IP的IP数量的设置请求，执行步骤S302；若未接收到用户设置预分配容器IP的IP数量的设置请求，执行步骤S303。
S302，根据所述设置请求设置预分配容器IP的IP数量，将用户设置的预分配容器IP的IP数量作为所确定的预分配容器IP的IP数量。
S303，判断是否获取到所述容器应用的历史数据信息，其中，所述历史数据信息包括当前时间之前该容器应用或者预设的与所述容器应用类似的容器应用的流量信息以及所对应的容器个数信息。
如若该容器应用以前并不存在，或者该容器应用已经已经存在，但是没有相关的历史数据信息，那么获取预设的与该容器应用类似的容器应用的流量信息以及所对应的容器个数信息。假设该容器应用对应为某社交软件A，那么获取预设的与该容器应用类似的容器应用B的流量信息以及所对应的容器个数信 息，以容器应用B的流量信息以及所对应的容器个数信息作为参考依据。若该容器应用以前已经存在，同时也有相关的历史数据信息，那么获取该容器应用所对应的流量信息以及所对应的容器个数信息。其中，历史数据信息可以是一次的数据信息，也可以是相关联的多次的信息。如预测春节当天，某社交软件需要新增的容器数量(假设春节当天该社交软件会新增大量的用户访问量)，那么可以获取该社交软件去年春节当天以及春节前后的用户流量信息和所对应的容器个数信息，也可以获取该社交软件近预设年数(如近三年)或者以往每年的春节当天以及春节前后的用户流量信息和所对应的容器个数信息。
若获取到该容器应用的历史数据信息，执行步骤S304；若未获取到任何历史数据信息，执行步骤S306。
其中，若获取到该容器应用的历史数据信息，包括：该容器应用有相关的历史数据信息，如此可以直接获取该容器应用的历史数据信息；该容器应用没有相关的历史数据信息，但是预设的与该容器应用类似的容器应用有相关的历史数据信息，如此获取与该容器应用类似的容器应用的历史数据信息等。若未获取到任何历史数据信息，包括：该容器应用没有相关的历史数据信息，预设的与该容器应用类似的容器应用也没有相关的历史数据信息。
S304，根据所述流量信息以及所对应的容器个数信息，确定所述容器应用所需创建的容器总数。
若获取的历史数据信息是该容器应用所对应的流量信息以及所对应的容器个数信息，根据该容器应用当前的流量信息，和获取的当前时间之前的历史数据信息，确定该容器应用所需创建的容器总数。如某社交软件去年春节当天的用户流量信息为A1，所对应的容器个数为B1，假设当前时间为今年春节前一天，根据历史数据信息可知，去年春节前一天与今年春节前一天(当前时间)的用户流量相当，那么可直接按照去年的容器个数确定该容器应用所需创建的容器总数；若根据历史数据信息可知，去年春节前一天与今年春节前一天(当前时间)相比，今年春节前一天的用户数据流量增加了10％，那么确定该容器应用所需创建的容器总数为B1*(1+10％)。需要注意的是，该举例只是为了理解技术方案，实际执行时并不限定如此。如若获取的是预设的与该容器应用类似的容器应用所对应的流量信息以及所对应的容器个数信息，根据该容器应用当 前的流量信息，和获取的预设的与该容器应用类似的容器应用的历史数据信息，确定该容器应用所需创建的容器总数。
S305，根据所述容器应用所需创建的容器总数、所述容器应用已创建的容器数量，确定预分配容器IP的IP数量。
其中，预分配容器IP的IP数量＝该容器应用所需创建的容器总数-该容器应用已创建的容器数量。其中，若在容器应用创建的同时为该容器应用预分配容器IP(预分配容器IP理解为为以后该容器应用的扩容而分配的IP)，那么已创建的容器数量，即为该容器应用创建完成时所对应的容器数量。
S306，获取预设的IP数量作为所确定的预分配容器IP的IP数量。预设的IP数量也可以理解为默认的IP数量。
该实施例进一步限定了如何确定预分配容器IP的IP数量。
S105，根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态。
其中，预设规则为先从该容器应用已分配的容器IP的IP地址段中分配IP，若IP不够，从下一个存在有空闲IP的IP地址段中分配IP。同时，需要注意的是，从每个IP地址段中分配IP时，可以是随机分配，也可以是按照IP地址的递增顺序或者递减顺序进行分配。
在一实施例中，如图4所示，步骤S105包括以下步骤S401-S406。
S401，获取所述容器应用已分配的容器IP的IP地址段。
S402，检测该IP地址段是否存在对应数量的空闲IP。其中，对应数量指的是所确定的预分配容器IP的IP数量。
S403，若该IP地址段存在对应数量的空闲IP，从该IP地址段中确定对应数量的空闲IP作为所确定的IP。
S404，若该IP地址段中的空闲IP的数量少于预分配容器IP的IP数量，获取该IP地址段中的剩余空闲IP，从下一个存在有空闲IP的IP地址段中确定剩余数量的空闲IP，将所获取的剩余空闲IP和所确定的空闲IP作为所确定的IP，其中，剩余数量为IP数量与剩余空闲IP数量之差。
可以理解地，若该IP地址段中的空闲IP的数量小于预分配容器IP的IP数量，那么从多个IP地址池中获取对应数量的IP。
S405，若该IP地址段中已不存在空闲IP，从下一个存在有空闲IP的IP地址段中确定相同数量的空闲IP作为所确定的IP。
S406，设置所确定的IP的状态为预分配状态。
在一实施例中，获取下一个存在有空闲IP的IP地址段时，是按照IP地址段填充时间的先后顺序来获取的。如此，按照IP地址段填充时间的先后顺序来获取存在有空闲IP的IP地址段，方便IP的管理。
需要注意的是，若IP的状态为预分配状态，该IP不会收取费用，同时该IP已经不能被其他的容器应用所使用。
S106，将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
将所确定的预分配状态的IP分配给该容器应用，具体地，将该确定的预分配状态的IP与该容器应用绑定，并记录在该容器应用所对应的配置文件中。
以上方法实施例为容器应用预分配容器IP，可预先为容器应用的容器分配IP，当由于业务需求，需立即新增容器并投入使用时，减少了需要申请分配IP的时间，可将新增容器立即投入使用，并且减少提前分配IP而造成的成本浪费。
在一实施例中，如图2所示，所述方法还包括：
S106a，若接收到所述容器应用的扩容请求，创建所述容器应用的容器，其中创建的容器数量与所述扩容请求中的需新增的容器数量相同。
S106b，从所述容器应用相关的预分配状态的IP中取出与新增的容器数量相同数量的IP分配给所创建的容器。
其中，若新增的容器数量为1个，从预分配状态的IP中取出一个IP，并分配给新增的容器；若新增的容器数量有多个，那么从预分配状态的IP中取出多个IP，并分配给新增的多个容器。如此，加快了容器投入使用的速度。
预分配IP后，预分配状态的IP相当于已经被占用，其他容器应用不能再使用该预分配状态的IP。在一实施例中，所述方法还包括：
若检测到容器应用下线，将所述容器应用所对应的预分配IP的IP状态设置为空闲状态；或者接收到释放预分配IP的释放请求，将所述释放请求所对应的预分配IP的IP状态设置为空闲状态。如此，以避免预分配了IP，而该预分配的IP长久不使用所早晨的资源浪费。
图5是本申请实施例提供的预分配容器IP的装置的示意性框图。如图5所示，该装置包括用于执行上述预分配容器IP的方法所对应的单元。具体地，如图5所示，该装置100包括请求接收单元101、区域获取单元102、空闲IP获取单元103、数量确定单元104、预分配单元105以及应用绑定单元106。
请求接收单元101，用于接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP。区域获取单元102，用于获取创建所述容器应用的区域。空闲IP获取单元103，用于获取所述区域中预设IP地址池中的空闲IP。数量确定单元104，用于确定预分配容器IP的IP数量。预分配单元105，用于根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态。应用绑定单元106，用于将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
在一实施例中，如图6所示，是本申请另一实施例提供的预分配容器IP的装置的示意性框图，该装置200包括请求接收单元101、区域获取单元102、比例检测单元103a、请求发送单元103b、地址填充单元103c、空闲IP获取单元103、数量确定单元104、预分配单元105、应用绑定单元106。其中，请求接收单元101、区域获取单元102、空闲IP获取单元103、数量确定单元104、预分配单元105以及应用绑定单元106与图5实施例中的分别对应，具体请参看图5实施例中的描述。
其中，比例检测单元103a，用于检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例。请求发送单元103b，用于若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，发送申请新IP地址段的请求。地址填充单元103c，用于接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
在一实施例中，地址填充单元103c，用于接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态，同时记录该新的IP地址段填充的时间。
在一实施例中，如图6所述，该装置200还包括防火墙开启单元103d。所 述防火墙开启单元103d，用于开启新填充的IP地址段中的IP的防火墙功能。
在一实施例中，如图6所示，该装置200还包括创建单元106a、IP分配单元106b。其中，创建单元106a，用于若接收到所述容器应用的扩容请求，创建所述容器应用的容器实例，其中创建的容器实例的数量与所述扩容请求中的需新增的容器实例数量相同。IP分配单元106b，用于从所述容器应用相关的预分配状态的IP中取出对应数量的IP分配给所创建的容器实例。
在一实施例中，所述装置200还包括设置单元。所述设置单元，用于若检测到容器应用下线，将所述容器应用所对应的预分配IP的IP状态设置为空闲状态；或者接收到释放预分配IP的释放请求，将所述释放请求所对应的预分配IP的IP状态设置为空闲状态。
在一实施例中，请求接收单元101，包括标识获取单元、请求接收确定单元。其中，标识获取单元，用于若接收到创建容器应用的请求，获取创建容器应用的请求中携带的标识信息，判断所述标识信息是否包括预分配容器IP的标识。请求接收确定单元，用于若所述标识信息包括预分配容器IP的标识，确定接收到预分配容器IP的分配请求。
在一实施例中，如图7所示，数量确定单元104包括请求检测单元1041、历史数据判断单元1042、总数确定单元1043以及IP数量确定单元1044。其中，请求检测单元1041，用于检测是否接收到用户设置预分配容器IP的IP数量的设置请求。IP数量确定单元1044，若接收到用户设置预分配容器IP的IP数量的设置请求，根据所述设置请求设置预分配容器IP的IP数量，将用户设置的预分配容器IP的IP数量作为所确定的预分配容器IP的IP数量。历史数据判断单元1042，用于若未接收到用户设置预分配容器IP的IP数量的设置请求，判断是否获取到所述容器应用的历史数据信息，其中，所述历史数据信息包括当前时间之前该容器应用或者预设的与所述容器应用类似的容器应用的流量信息以及所对应的容器个数信息。总数确定单元1043，用于若获取到所述容器应用的历史数据信息，根据所述流量信息以及所对应的容器个数信息，确定所述容器应用所需创建的容器总数。IP数量确定单元1044，还用于根据所述容器应用所需创建的容器总数、所述容器应用已创建的容器数量，确定预分配容器IP的IP数量。IP数量确定单元1044，还用于若未获取到任何历史数据信息，获取预 设的IP数量作为所确定的预分配容器IP的IP数量。
在一实施例中，如图8所述，预分配单元105包括地址段获取单元1051、空闲IP检测单元1052、预分配确定单元1053、状态设置单元1054。其中，地址段获取单元1051，用于获取所述容器应用已分配的容器IP的IP地址段。空闲IP检测单元1052，用于检测该IP地址段是否存在对应数量的空闲IP。预分配确定单元1053，用于若该IP地址段存在对应数量的空闲IP，从该IP地址段中确定对应数量的空闲IP作为所确定的IP。预分配确定单元1053，还用于若该IP地址段中的空闲IP的数量少于预分配容器IP的IP数量，获取该IP地址段中的剩余空闲IP，从下一个存在有空闲IP的IP地址段中确定剩余数量的空闲IP，将所获取的剩余空闲IP和所确定的空闲IP作为所确定的IP，其中，剩余数量为IP数量与剩余空闲IP数量之差。预分配确定单元1053，还用于若该IP地址段中已不存在空闲IP，从下一个存在有空闲IP的IP地址段中确定相同数量的空闲IP作为所确定的IP。状态设置单元1054，用于设置所确定的IP的状态为预分配状态。
在一实施例中，预分配确定单元1053，在获取下一个存在有空闲IP的IP地址段时是按照IP地址段填充时间的先后顺序来获取的。
需要说明的是，所属领域的技术人员可以清楚地了解到，上述装置和各单元的具体实现过程，可以参考前述方法实施例中的相应描述，为了描述的方便和简洁，在此不再赘述。
上述装置可以实现为一种计算机程序的形式，计算机程序可以在如图9所示的计算机设备上运行。
图9为本申请实施例提供的一种计算机设备的示意性框图。该设备为云平台中的服务器等设备。该设备300包括通过系统总线301连接的处理器302、存储器和网络接口303，其中，存储器可以包括非易失性存储介质304和内存储器305。
该非易失性存储介质304可存储操作系统3041和计算机程序3042。该非易失性存储介质中所存储的计算机程序3042被处理器302执行时，可实现上述所述的预分配容器IP的方法。该处理器302用于提供计算和控制能力，支撑整个设备的运行。该内存储器305为非易失性存储介质中的计算机程序的运行提 供环境，该计算机程序被处理器302执行时，可使得处理器302执行上述所述的预分配容器IP的方法。该网络接口303用于进行网络通信。本领域技术人员可以理解，图9中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的设备的限定，具体的设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器302用于运行存储在存储器中的计算机程序，以实现本申请预分配容器IP的方法的任意实施例。
本领域普通技术人员可以理解的是实现上述实施例的方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成。该计算机程序可存储于一存储介质中，该存储介质可以为计算机可读存储介质。该计算机程序被该计算机系统中的至少一个处理器执行，以实现上述方法的实施例的流程步骤。
因此，本申请还提供了一种存储介质。该存储介质可以为计算机可读存储介质。该存储介质存储有计算机程序，该计算机程序当被处理器执行时实现本申请预分配容器IP的方法的任意实施例。
所述存储介质为实体的、非瞬时性的存储介质，例如可以是U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、磁碟或者光盘等各种可以存储计算机程序的实体存储介质。在本申请所提供的几个实施例中，应该理解到，所揭露的装置、设备和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的装置、设备和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种预分配容器IP的方法，包括：
    接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP；
    获取创建所述容器应用的区域；
    获取所述区域中预设IP地址池中的空闲IP；
    确定预分配容器IP的IP数量；
    根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；
    将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
  2. 根据权利要求1所述的方法，其中，在所述获取所述区域中预设IP地址池中的空闲IP之前，所述方法还包括：
    检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例；
    若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，发送申请新IP地址段的请求；
    接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    开启新填充的IP地址段中的IP的防火墙功能。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    记录新填充的IP地址段填充的时间。
  5. 根据权利要求1所述的方法，其中，所述根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态，包括：
    获取所述容器应用已分配的容器IP的IP地址段；
    检测该IP地址段是否存在对应数量的空闲IP；
    若该IP地址段存在对应数量的空闲IP，从该IP地址段中确定对应数量的空闲IP作为所确定的IP；
    若该IP地址段中的空闲IP的数量少于预分配容器IP的IP数量，获取该IP地址段中的剩余空闲IP，从下一个存在有空闲IP的IP地址段中确定剩余数量的空闲IP，将所获取的剩余空闲IP和所确定的空闲IP作为所确定的IP，其中，剩余数量为IP数量与剩余空闲IP数量之差；
    若该IP地址段中已不存在空闲IP，从下一个存在有空闲IP的IP地址段中确定相同数量的空闲IP作为所确定的IP；
    设置所确定的IP的状态为预分配状态。
  6. 根据权利要求1所述的方法，其中，所述确定预分配容器IP的IP数量，包括：
    检测是否接收到用户设置预分配容器IP的IP数量的设置请求；
    若接收到用户设置预分配容器IP的IP数量的设置请求，根据所述设置请求设置预分配容器IP的IP数量，将用户设置的预分配容器IP的IP数量作为所确定的预分配容器IP的IP数量；
    若未接收到用户设置预分配容器IP的IP数量的设置请求，判断是否获取到所述容器应用的历史数据信息，其中，所述历史数据信息包括当前时间之前该容器应用或者预设的与所述容器应用类似的容器应用的流量信息以及所对应的容器个数信息；
    若获取到所述容器应用的历史数据信息，根据所述流量信息以及所对应的容器个数信息，确定所述容器应用所需创建的容器总数；
    根据所述容器应用所需创建的容器总数、所述容器应用已创建的容器数量，确定预分配容器IP的IP数量；
    若未获取到任何历史数据信息，获取预设的IP数量作为预分配容器IP的IP数量。
  7. 根据权利要求1所述的方法，其中，所述接收预分配容器IP的分配请求，包括：
    若接收到创建容器应用的请求，获取创建容器应用的请求中携带的标识信息，判断所述标识信息是否包括预分配容器IP的标识；
    若所述标识信息包括预分配容器IP的标识，确定接收到预分配容器IP的分配请求。
  8. 根据权利要求1所述的方法，其中，所述方法还包括：
    若接收到所述容器应用的扩容请求，创建所述容器应用的容器，其中创建的容器数量与所述扩容请求中的需新增的容器数量相同；
    从所述容器应用相关的预分配状态的IP中取出与新增的容器数量相同数量的IP分配给所创建的容器。
  9. 一种预分配容器IP的装置，所述预分配容器IP的装置包括：
    请求接收单元，用于接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP；
    区域获取单元，用于获取创建所述容器应用的区域；
    空闲IP获取单元，用于获取所述区域中预设IP地址池中的空闲IP；
    数量确定单元，用于确定预分配容器IP的IP数量；
    预分配单元，用于根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；
    应用绑定单元，用于将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    比例检测单元，用于检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例；
    请求发送单元，用于若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，发送申请新IP地址段的请求；
    地址填充单元，用于接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
  11. 一种计算机设备，包括存储器，以及与所述存储器相连的处理器；其中，所述存储器用于存储计算机程序；所述处理器用于运行所述存储器中存储的计算机程序，以执行如下步骤：
    接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP；
    获取创建所述容器应用的区域；
    获取所述区域中预设IP地址池中的空闲IP；
    确定预分配容器IP的IP数量；
    根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；
    将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
  12. 根据权利要求11所述的计算机设备，其中，在所述获取所述区域中预设IP地址池中的空闲IP之前，所述处理器还执行以下步骤：
    检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例；
    若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，发送申请新IP地址段的请求；
    接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
  13. 根据权利要求12所述的计算机设备，其中，所述处理器还执行以下步骤：
    开启新填充的IP地址段中的IP的防火墙功能。
  14. 根据权利要求11所述的计算机设备，其中，所述处理器还执行以下步骤：记录新填充的IP地址段填充的时间。
  15. 根据权利要求11所述的计算机设备，其中，所述根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态，包括：
    获取所述容器应用已分配的容器IP的IP地址段；
    检测该IP地址段是否存在对应数量的空闲IP；
    若该IP地址段存在对应数量的空闲IP，从该IP地址段中确定对应数量的空闲IP作为所确定的IP；
    若该IP地址段中的空闲IP的数量少于预分配容器IP的IP数量，获取该IP地址段中的剩余空闲IP，从下一个存在有空闲IP的IP地址段中确定剩余数量的空闲IP，将所获取的剩余空闲IP和所确定的空闲IP作为所确定的IP，其中，剩余数量为IP数量与剩余空闲IP数量之差；
    若该IP地址段中已不存在空闲IP，从下一个存在有空闲IP的IP地址段中确定相同数量的空闲IP作为所确定的IP；
    设置所确定的IP的状态为预分配状态。
  16. 根据权利要求11所述的计算机设备，其中，所述确定预分配容器IP的IP数量，包括：
    检测是否接收到用户设置预分配容器IP的IP数量的设置请求；
    若接收到用户设置预分配容器IP的IP数量的设置请求，根据所述设置请求设置预分配容器IP的IP数量，将用户设置的预分配容器IP的IP数量作为所确定的预分配容器IP的IP数量；
    若未接收到用户设置预分配容器IP的IP数量的设置请求，判断是否获取到所述容器应用的历史数据信息，其中，所述历史数据信息包括当前时间之前该容器应用或者预设的与所述容器应用类似的容器应用的流量信息以及所对应的容器个数信息；
    若获取到所述容器应用的历史数据信息，根据所述流量信息以及所对应的容器个数信息，确定所述容器应用所需创建的容器总数；
    根据所述容器应用所需创建的容器总数、所述容器应用已创建的容器数量，确定预分配容器IP的IP数量；
    若未获取到任何历史数据信息，获取预设的IP数量作为预分配容器IP的IP数量。
  17. 根据权利要求11所述的计算机设备，其中，所述接收预分配容器IP的分配请求，包括：
    若接收到创建容器应用的请求，获取创建容器应用的请求中携带的标识信息，判断所述标识信息是否包括预分配容器IP的标识；
    若所述标识信息包括预分配容器IP的标识，确定接收到预分配容器IP的分配请求。
  18. 根据权利要求11所述的计算机设备，其中，所述处理器还执行以下步骤：
    若接收到所述容器应用的扩容请求，创建所述容器应用的容器，其中创建的容器数量与所述扩容请求中的需新增的容器数量相同；
    从所述容器应用相关的预分配状态的IP中取出与新增的容器数量相同数量的IP分配给所创建的容器。
  19. 一种计算机可读存储介质，其中，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，实现如下步骤：
    接收预分配容器IP的分配请求，所述分配请求用于预先为容器应用需新增的容器分配IP；
    获取创建所述容器应用的区域；
    获取所述区域中预设IP地址池中的空闲IP；
    确定预分配容器IP的IP数量；
    根据预设规则从所述空闲IP中确定相同数量的IP，并设置所确定的IP的状态为预分配状态；
    将所确定的预分配状态的IP分配给所述容器应用，以使所述容器应用在新增容器时从所述预分配状态的IP中取出对应IP分配给新增的容器。
  20. 根据权利要求19所述的计算机可读存储介质，其中，在所述获取所述区域中预设IP地址池中的空闲IP之前，所述处理器还执行以下步骤：
    检测所述区域预设IP地址池中的空闲IP数量与所述区域中的预设空闲IP数量的占比是否低于预设比例；
    若空闲IP数量与所述区域中的预设空闲IP数量的占比低于预设比例，发送申请新IP地址段的请求；
    接收用户根据该请求而分配的新的IP地址段，将该新的IP地址段中的IP填充到IP地址池，并设置新填充的IP的状态为空闲状态。
PCT/CN2019/118241 2019-05-17 2019-11-14 预分配容器ip的方法、装置、计算机设备及存储介质 WO2020233020A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910411988.3 2019-05-17
CN201910411988.3A CN110278288B (zh) 2019-05-17 2019-05-17 预分配容器ip的方法、装置、计算机设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020233020A1 true WO2020233020A1 (zh) 2020-11-26

Family

ID=67959929

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118241 WO2020233020A1 (zh) 2019-05-17 2019-11-14 预分配容器ip的方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN110278288B (zh)
WO (1) WO2020233020A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766043A (zh) * 2021-05-11 2021-12-07 腾讯科技（深圳）有限公司 配置目标容器的方法、装置、计算机设备及存储介质
CN113992525A (zh) * 2021-10-12 2022-01-28 支付宝(杭州)信息技术有限公司 一种应用的容器数量调节方法及装置
CN114500464A (zh) * 2021-12-13 2022-05-13 天翼物联科技有限公司 一种容器静态ip分配方法、系统、装置及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278288B (zh) * 2019-05-17 2021-10-26 平安科技（深圳）有限公司 预分配容器ip的方法、装置、计算机设备及存储介质
CN113645319A (zh) * 2020-04-27 2021-11-12 中兴通讯股份有限公司 地址分配方法和系统、电子设备、计算机可读存储介质
CN113760441A (zh) * 2020-08-31 2021-12-07 北京京东尚科信息技术有限公司 容器创建方法、装置、电子设备及存储介质
CN113111034B (zh) * 2021-04-07 2023-08-04 山东英信计算机技术有限公司 一种索引预分配的方法及装置
CN114710443B (zh) * 2022-03-17 2024-03-19 杭州华橙软件技术有限公司 一种针对转发服务器的流量调度方法及装置
CN115550315B (zh) * 2022-08-10 2023-08-29 北京中关村软件园发展有限责任公司 一种基于下一代互联网的数字化云服务管理方法和系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1391173A (zh) * 2001-06-08 2003-01-15 提阿克股份有限公司 网络装置、伺服装置、客户装置、网络ip地址赋予方法与程序
JP2003069604A (ja) * 2001-08-23 2003-03-07 Nifty Corp 動的アドレス割当方法，動的アドレス割当装置及び動的アドレス割当プログラム
CN102413205A (zh) * 2011-12-23 2012-04-11 华为技术有限公司 一种ip地址分配方法及相关中继设备、服务器和系统
US9369428B2 (en) * 2012-09-27 2016-06-14 Verzion Patent And Licensing Inc. Systems and methods for assigning Internet Protocol addresses
CN108848037A (zh) * 2018-05-31 2018-11-20 平安医疗科技有限公司 业务请求处理方法、装置、计算机设备和存储介质
CN110278288A (zh) * 2019-05-17 2019-09-24 平安科技（深圳）有限公司 预分配容器ip的方法、装置、计算机设备及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8938554B2 (en) * 2006-03-02 2015-01-20 Oracle America, Inc. Mechanism for enabling a network address to be shared by multiple labeled containers
CN105763670B (zh) * 2016-04-08 2019-01-29 北京搜狐新媒体信息技术有限公司 一种为容器分配ip地址的方法及装置
US10469629B2 (en) * 2017-06-23 2019-11-05 Cisco Technology, Inc. Container networking for connecting network controller applications to a switch fabric
CN107566541B (zh) * 2017-08-03 2021-03-23 携程旅游信息技术（上海）有限公司 容器网络资源分配方法、系统、存储介质和电子设备
CN107666525B (zh) * 2017-09-08 2020-11-24 北京京东尚科信息技术有限公司 集群容器ip分配的方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1391173A (zh) * 2001-06-08 2003-01-15 提阿克股份有限公司 网络装置、伺服装置、客户装置、网络ip地址赋予方法与程序
JP2003069604A (ja) * 2001-08-23 2003-03-07 Nifty Corp 動的アドレス割当方法，動的アドレス割当装置及び動的アドレス割当プログラム
CN102413205A (zh) * 2011-12-23 2012-04-11 华为技术有限公司 一种ip地址分配方法及相关中继设备、服务器和系统
US9369428B2 (en) * 2012-09-27 2016-06-14 Verzion Patent And Licensing Inc. Systems and methods for assigning Internet Protocol addresses
CN108848037A (zh) * 2018-05-31 2018-11-20 平安医疗科技有限公司 业务请求处理方法、装置、计算机设备和存储介质
CN110278288A (zh) * 2019-05-17 2019-09-24 平安科技（深圳）有限公司 预分配容器ip的方法、装置、计算机设备及存储介质

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766043A (zh) * 2021-05-11 2021-12-07 腾讯科技（深圳）有限公司 配置目标容器的方法、装置、计算机设备及存储介质
CN113766043B (zh) * 2021-05-11 2024-02-23 腾讯科技（深圳）有限公司 配置目标容器的方法、装置、计算机设备及存储介质
CN113992525A (zh) * 2021-10-12 2022-01-28 支付宝(杭州)信息技术有限公司 一种应用的容器数量调节方法及装置
CN114500464A (zh) * 2021-12-13 2022-05-13 天翼物联科技有限公司 一种容器静态ip分配方法、系统、装置及存储介质
CN114500464B (zh) * 2021-12-13 2023-12-12 天翼物联科技有限公司 一种容器静态ip分配方法、系统、装置及存储介质

Also Published As

Publication number Publication date
CN110278288A (zh) 2019-09-24
CN110278288B (zh) 2021-10-26

Similar Documents

Publication Publication Date Title
WO2020233020A1 (zh) 预分配容器ip的方法、装置、计算机设备及存储介质
CN107580083B (zh) 一种容器ip地址分配的方法和系统
JP6670025B2 (ja) クラウド・ネットワーキングのためのマルチテナント認識型動的ホスト構成プロトコル（ｄｈｃｐ）機構
US10701139B2 (en) Life cycle management method and apparatus
US10313428B2 (en) Multi-subnet participation for network gateway in a cloud environment
CN111460460B (zh) 任务访问方法、装置、代理服务器及机器可读存储介质
WO2017147800A1 (zh) 资源配置方法、虚拟网络功能管理器和网元管理系统
US9998531B2 (en) Computer-based, balanced provisioning and optimization of data transfer resources for products and services
US10042676B1 (en) Capacity pool health index
EP3618352B1 (en) Virtual machine management
WO2017084453A1 (zh) 云平台资源管理方法、装置及系统
US11710206B2 (en) Session coordination for auto-scaled virtualized graphics processing
WO2023160033A1 (zh) 虚拟网卡资源的配置方法、装置、计算机设备及介质
WO2017054533A1 (zh) 云互通的外部资源管理方法、装置及系统
US20220382590A1 (en) Cloud provider account mappings
CN112860421B (zh) 用于作业处理的方法、设备和计算机程序产品
WO2020135517A1 (zh) 部署虚拟化网络功能的方法和装置
WO2020252921A1 (zh) 多活负载均衡应用的扩容方法、装置、设备及存储介质
CN107295112B (zh) 受限网络环境下分配域名的方法和系统
CN115883283A (zh) 一种容器化vnf的部署方法及装置
CN109542622A (zh) 一种数据处理方法及装置
WO2019072171A1 (zh) 环形组网下的网络功能虚拟化业务链映射的方法及装置
CN110262894B (zh) 负载均衡应用管理方法、装置、计算机设备及存储介质
CN110045930B (zh) 虚拟平台管理存储设备卷的方法、装置、设备及介质
CN111277634B (zh) 一种数据id分配方法、装置、系统以及服务器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19929651

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19929651

Country of ref document: EP

Kind code of ref document: A1