CN110278288B

CN110278288B - Method and device for pre-allocating container IP, computer equipment and storage medium

Info

Publication number: CN110278288B
Application number: CN201910411988.3A
Authority: CN
Inventors: 黄桂钦
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2019-05-17
Filing date: 2019-05-17
Publication date: 2021-10-26
Anticipated expiration: 2039-05-17
Also published as: CN110278288A; WO2020233020A1

Abstract

The embodiment of the application provides a method and a device for pre-allocating a container IP, computer equipment and a storage medium, relates to the technical field of cloud computing, and can be applied to a PaaS platform. The method comprises the following steps: receiving an allocation request for pre-allocation of a container to be newly added for a container application; acquiring an area for creating a container application; acquiring idle IP in a preset IP address pool in the area; determining the IP number of the pre-allocation container IP; determining the same number of IPs from the idle IPs according to a preset rule, and setting the determined state of the IPs as a pre-allocation state; and allocating the determined IP in the pre-allocation state to a container application, so that when the container application adds a new container, the corresponding IP is taken out from the IP in the pre-allocation state and allocated to the new container. The embodiment of the application can allocate the IP to the container which needs to be newly added in the container application in advance, and when the container needs to be newly added and put into use, the time for allocating the IP is shortened, and the cost waste caused by allocating the IP in advance is reduced.

Description

Method and device for pre-allocating container IP, computer equipment and storage medium

Technical Field

The application relates to the technical field of cloud computing, in particular to a method and a device for pre-allocating container IP, computer equipment and a storage medium.

Background

When detecting that the service demand increases, the capacity of the container application needs to be expanded, which relates to allocating IP to the newly added container. The existing method for allocating the container IP needs to apply for allocating IP resources in advance, the application process is complex (if the application needs to be carried out first, then the first-level auditing is carried out, and the like), and the time is very long. The applied container IP needs to be used for a fee, and therefore, once the application is successful, the fee needs to be paid. This may result in increased costs due to the application and allocation of IP resources in advance.

Disclosure of Invention

The embodiment of the application provides a method, a device, a computer device and a storage medium for pre-allocating an IP (Internet protocol) of a container, which can reduce the time for applying for allocating the IP when the newly added container is applied to the container and can avoid the cost waste caused by allocating the IP in advance.

In a first aspect, an embodiment of the present application provides a method for pre-allocating an IP of a container, where the method includes:

receiving an allocation request of a pre-allocated container IP, wherein the allocation request is used for allocating the IP to a container which needs to be newly added in container application in advance; acquiring an area for creating the container application; acquiring idle IP in a preset IP address pool in the area; determining the IP number of the pre-allocation container IP; determining the same number of IPs from the idle IPs according to a preset rule, and setting the determined state of the IPs as a pre-allocation state; and allocating the determined IP in the pre-allocation state to the container application, so that when the container application adds a new container, the corresponding IP is taken out from the IP in the pre-allocation state and allocated to the new container.

In a second aspect, an embodiment of the present invention provides an apparatus for pre-allocating a container IP, where the apparatus for pre-allocating a container IP includes corresponding units for executing the method described in the first aspect.

In a third aspect, an embodiment of the present invention provides a computer device, where the computer device includes a memory and a processor connected to the memory;

the memory is adapted to store a computer program and the processor is adapted to execute the computer program stored in the memory to perform the method of the first aspect.

In a fourth aspect, the present invention provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method according to the first aspect.

According to the embodiment of the application, the IP of the container is pre-allocated to the container application, the IP can be allocated to the container which needs to be newly added in the container application in advance, and when the container needs to be immediately newly added and put into use due to service requirements, the time for applying for allocating the IP is reduced, and cost waste caused by allocating the IP in advance is reduced.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a flow chart of a method for pre-allocating container IPs provided by an embodiment of the present application;

FIG. 2 is a flow chart illustrating a method for pre-allocating container IPs according to another embodiment of the present application;

FIG. 3 is a sub-flow diagram of a method for pre-allocating container IPs provided by an embodiment of the present application;

FIG. 4 is a sub-flow diagram of a method for pre-allocating container IPs provided by an embodiment of the present application;

FIG. 5 is a schematic block diagram of an apparatus for pre-allocating container IPs provided by an embodiment of the present application;

FIG. 6 is a schematic block diagram of an apparatus for pre-allocating container IPs provided by another embodiment of the present application;

FIG. 7 is a schematic block diagram of a quantity determination 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.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic flow chart of a method for pre-allocating container IPs according to an embodiment of the present disclosure. As shown in fig. 1, the method includes S101-S106.

S101, receiving an allocation request of a pre-allocated container IP, wherein the allocation request is used for allocating the IP to a container needing to be newly added in container application in advance.

It can be understood that the container in the pre-allocated container IP refers to a container that is predicted to be newly added when the traffic demand will increase, and the container IP is the IP corresponding to the container that is newly added. It should be noted that in the present application, the container to be added is not actually added because once the container is added and the IP is assigned, a fee is paid for the container. In the application, under the condition that no new container is added, IP address resources are allocated to the container needing to be added in advance, so that after the container is added, IP can be allocated to the new container from the pre-allocated IP address quickly, and the new container can be put into use quickly.

Wherein, in an embodiment, the allocation request of the pre-allocation container IP may be triggered by a request to create a container application. Specifically, receiving an allocation request of a pre-allocation container IP includes: if a request for creating the container application is received, acquiring identification information carried in the request for creating the container application, and judging whether the identification information comprises an identification of a pre-allocated container IP (Internet protocol); and if the identification information comprises the identification of the pre-allocation container IP, determining that the allocation request of the pre-allocation container IP is received.

It will be appreciated that the container application is pre-allocated a container IP upon creation of the container application. In this case, one application scenario involved is that a data item (including an option) whether to pre-allocate the container IP is set in the interface for creating the container application, and the option whether to pre-allocate the container IP is received or selected by the user; if a request for creating the container application is received (which can be triggered by a user clicking a relevant button for creating the container application), identification information carried in the request for creating the container application is obtained, and whether the identification information comprises an identification of a pre-allocated container IP is judged. Options such as pre-allocating container IP include: "yes" and "no", if "yes" and "no" correspond to the label "1" and "0", respectively. If the corresponding identification information in the request for creating the container application is '1', determining that the identification information comprises an identification of a pre-allocation container IP, and determining that an allocation request of the pre-allocation container IP is received; and if the corresponding identification information in the request for creating the container application is '0', determining that the identification information does not comprise the identification of the pre-allocation container IP, and determining that the allocation request of the pre-allocation container IP is not received.

In one embodiment, the allocation request for the pre-allocated container IP may be triggered by the user clicking on the relevant button of the pre-allocated container IP after the container application creation is complete. It will be appreciated that after the container application creation is complete, the container application is pre-assigned the container IP.

It should be noted that, regardless of whether pre-allocation of container IPs is required, the container application creates a certain number of containers and allocates IPs to the created certain number of containers at the same time. The container created for the container application is charged when the container application is created and can be immediately taken into use. The pre-allocated container IP is not charged and the charge is only made after the pre-allocated IP is allocated to the newly added container.

S102, acquiring an area for creating the container application.

The area of the container application refers to a machine room location where the container application is created, and consists of two parts: an "application environment" of the container application and a "zone" + "secure zone" of the container application are created. Wherein a "safe area" is understood as a sub-area under the "area". The "application environment" of the container application includes a production environment, a test environment, and a development environment. The production environment is an environment that can provide services for internet users, the test environment is an environment used for testing internally, and the development environment is an environment used for developing internally. And a machine room is correspondingly arranged for each environment. The "zone" + "safe zone" of the container application may be understood as creating the container application in a sub-zone corresponding to the "xxx safe zone" under the "xx zone" machine room. It will be appreciated that the machines in the machine room will also be divided into sub-areas. Finally, the area where the container application is created may be understood as a sub-area corresponding to a certain security area under a certain area room in a certain environment. If the area for creating the container application is: in the A subregion under the treasure letter region computer lab in the test environment. It should be noted that the above division of the area of the container application is only an example, and in the present application, the division of the area of the container application is not limited. That is, regardless of how the area of the container application is divided, the area where the container application is created can be acquired. If the container IP is pre-allocated to the container application when the container application is created, a data item corresponding to the area where the container application is created, such as an "application environment" of the container application and an "area" + "secure area" of the container application, is set in the interface where the container application is created, and the content of the corresponding data item is acquired, that is, the area where the container application is created can be acquired. If the container IP is pre-allocated to the container application after the container application is created, the area for creating the container application can be directly acquired according to the information of the container application.

S103, acquiring the idle IP in the preset IP address pool in the area.

Typically, the IPs in the IP address pool are local area network IPs. It can be understood that an IP address pool, that is, a preset IP address pool, is pre-allocated in the area where the container application is created, the IP address pool includes a free IP, and the free IP in a free state can be obtained according to the state of the IP. The free IP is not allocated and can be allocated to the container application under the area at any time. In general, the number of free IPs in the pool of IP addresses is sufficient for the container application under that area to use.

In some cases, however, there may be situations where the number of free IPs in the IP address pool is not sufficient. Thus, in some other embodiments, as shown in fig. 2, fig. 2 is a schematic flowchart of a method for distributing container IPs according to another embodiment of the present application, before step S103, the method further includes:

s103a, detecting whether the ratio of the idle IP number in the area preset IP address pool to the preset idle IP number in the area is lower than a preset ratio.

Such as a predetermined ratio of 10%. Namely, if the ratio of the idle IP data in the regional IP address pool to the preset idle IP number in the region is lower than the preset ratio.

If the ratio of the idle IP number to the preset idle IP number in the area is lower than the preset ratio, executing step S103 b; if not, executing step S103, namely executing the step of acquiring the idle IP in the preset IP address pool in the area.

S103b, sending a request for a new IP address field.

If the ratio of the idle IP number to the preset idle IP number in the area is lower than the preset ratio, actively sending a request for applying for a new IP address field.

S103c, receiving a new IP address field allocated by the user according to the request, filling the IP in the new IP address field into an IP address pool, and setting the state of the newly filled IP as an idle state.

According to the embodiment, when the ratio of the number of idle IP in the area to the preset number of idle IP is lower than the preset ratio, the method actively requests to apply for a new IP address field, fills the IP in the new IP address field into the IP address pool after the new IP address field is allocated, and sets the state of the newly filled IP as the idle state, so that the idle IP can be obtained according to the state of the IP, and the condition that the use of the cloud platform is influenced by insufficient idle IP addresses in the area is avoided.

In one embodiment, the state of the newly populated IP is set to an idle state while the time of the new IP address field population is recorded. Therefore, on one hand, the method can be used for consulting the relevant information subsequently, and on the other hand, convenience is provided for the IP of the subsequent distribution container.

In an embodiment, a new IP address segment is allocated, and after the state of the newly populated IP is set to the idle state, the method further includes:

s103d, starting the firewall function of the newly filled IP network segment.

The firewall function is started, and the firewall function comprises setting accessible ports such as 80, 8080, 7001 and the like, and setting accessible IP and the like. After the firewall function is set, the IP can be really put into use. Specifically, the firewall functions of all the IPs of the IP network segment may be set at once. It is understood that the services provided by the IPs corresponding to an IP network segment may be similar or identical.

It should be noted that, in the existing manner of allocating container IP, an application for allocating IP resources is required in advance, and after the application for IP resources, a firewall function needs to be separately opened for each IP that applies. One starting is very time-consuming and easy to careless and neglect, and the scheme in the application starts the firewall function for the IP in the IP network segment after the new IP network segment is allocated, and completely starts the firewall function in the whole IP network segment at one time, so that the time is saved, and the error rate is also reduced. On the other hand, since the firewall function is opened for the IP in advance, if a container is created, the container can be immediately put into use after the pre-allocated IP is allocated to the created container. When a new container is required to be added and put into use immediately due to service requirements, the time for applying for IP allocation and opening the firewall function for the IP is reduced, and the new container can be put into use immediately.

S104, determining the IP number of the pre-allocation container IP.

The number of the IP of the pre-allocation container IP may be determined according to historical data, may be determined directly according to the number set by the user, or may be determined directly using a default number.

In one embodiment, as shown in FIG. 3, step S104 includes the following steps S301-S306.

S301, whether a setting request for setting the IP number of the pre-allocation container IP by a user is received or not is detected.

If a setting request for setting the IP number of the pre-allocation container IP by a user is received, executing step S302; if a setting request for setting the IP number of the pre-allocation container IP by the user is not received, step S303 is executed.

S302, the IP number of the pre-allocation container IP is set according to the setting request, and the IP number of the pre-allocation container IP set by the user is used as the determined IP number of the pre-allocation container IP.

And S303, judging whether historical data information of the container application is acquired, wherein the historical data information comprises flow information of the container application before the current time or a preset container application similar to the container application and corresponding container number information.

If the container application does not exist before, or the container application already exists but does not have relevant historical data information, acquiring preset flow information of container applications similar to the container application and corresponding container number information. Assuming that the container application corresponds to a certain social software a, the preset traffic information of the container application B similar to the container application and the corresponding container number information are obtained, and the traffic information of the container application B and the corresponding container number information are used as reference bases. If the container application already exists before and has related historical data information, acquiring the flow information corresponding to the container application and the number information of the corresponding containers. The historical data information may be data information of one time or information of multiple times in a related manner. If the number of newly added containers is needed by certain social software in the spring festival day (assuming that a large amount of user access is newly added to the social software in the spring festival day), the user traffic information and the corresponding container number information of the social software in the spring festival day of the last year and before and after the spring festival can be obtained, or the user traffic information and the corresponding container number information of the social software in the spring festival day of the last year (for example, three years) or the previous year and before and after the spring festival can be obtained.

If the historical data information of the container application is acquired, executing step S304; if no history data information is acquired, step S306 is executed.

Wherein, if the historical data information of the container application is acquired, the method includes: the container application has related 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 a preset container application similar to the container application has relevant historical data information, so that the historical data information and the like of the container application similar to the container application are acquired. If no historical data information is acquired, the method comprises the following steps: the container application has no related historical data information, and the preset container application similar to the container application also has no related historical data information.

S304, determining the total number of the containers required to be created by the container application according to the flow information and the corresponding container number information.

If the acquired historical data information is the flow information corresponding to the container application and the number information of the corresponding containers, determining the total number of the containers required to be created by the container application according to the current flow information of the container application and the acquired historical data information before the current time. If the user traffic information of a certain social software in the spring festival of the last year is A1, the number of corresponding containers is B1, and if the current time is the day before the spring festival of the present year, the historical data information shows that the user traffic of the day before the spring festival of the last year is equivalent to the user traffic of the day before the spring festival of the present year (the current time), the total number of the containers required to be created by the container application can be directly determined according to the number of the containers in the last year; if the user data traffic of the previous day of the spring festival of the last year is increased by 10% compared with the previous day of the spring festival of the present year (the current time) according to the historical data information, the total number of containers required to be created by the container application is determined to be B1 (1+ 10%). It should be noted that this example is only for understanding the technical solution, and the actual implementation is not limited to this. If the traffic information corresponding to the preset container application similar to the container application and the corresponding container number information are acquired, determining the total number of containers required to be created by the container application according to the current traffic information of the container application and the acquired historical data information of the preset container application similar to the container application.

S305, determining the IP number of the pre-allocated container IP according to the total number of the containers required to be created by the container application and the number of the containers already created by the container application.

The number of IP of the pre-allocated container IP is equal to the total number of containers that the container application needs to create — the number of containers that the container application has created. If a container IP is pre-allocated for the container application while the container application is created (the pre-allocated container IP is understood as an IP allocated for subsequent capacity expansion of the container application), the created number of containers is the number of containers corresponding to the container application when the container application is created.

S306, acquiring the preset IP number as the determined IP number of the pre-allocation container IP. The preset number of IPs may also be understood as a default number of IPs.

This embodiment further defines how the number of IPs for the pre-allocated container IP is determined.

And S105, determining the same number of IPs from the idle IPs according to a preset rule, and setting the determined states of the IPs as pre-allocation states.

The preset rule is that an IP is allocated from an IP address field of the container IP allocated by the container application, and if the IP is not enough, the IP is allocated from the next IP address field with a free IP. Meanwhile, it should be noted that when allocating the IP from each IP address segment, the allocation may be random, or may be performed according to the ascending order or the descending order of the IP addresses.

In one embodiment, as shown in FIG. 4, step S105 includes the following steps S401-S406.

S401, the IP address field of the container IP allocated by the container application is obtained.

S402, whether the IP address field has a corresponding number of idle IPs is detected. Wherein the corresponding number refers to the determined IP number of the pre-allocated container IP.

S403, if the IP address field has a corresponding number of idle IPs, determining the corresponding number of idle IPs from the IP address field as the determined IP.

S404, if the number of the idle IP in the IP address field is less than the number of the IP of the pre-allocated container IP, acquiring the residual idle IP in the IP address field, determining the residual idle IP in the next IP address field with the idle IP, and taking the acquired residual idle IP and the determined idle IP as the determined IP, wherein the residual number is the difference between the number of the IP and the number of the residual idle IP.

It is to be understood that if the number of free IPs in the IP address field is less than the number of IPs of the pre-allocated container IP, then a corresponding number of IPs are obtained from the multiple IP address pools.

S405, if no idle IP exists in the IP address field, determining the same number of idle IPs as the determined IP from the next IP address field with the idle IP.

S406, setting the determined IP state as a pre-allocation state.

In an embodiment, when acquiring the next IP address field with an idle IP, the next IP address field is acquired according to the sequence of the filling time of the IP address field. Therefore, the IP address field with the idle IP is obtained according to the sequence of the filling time of the IP address field, and the management of the IP is convenient.

It should be noted that if the status of an IP is pre-allocated, the IP will not be charged and the IP will not be available for other container applications.

S106, allocating the determined IP in the pre-allocation state to the container application, so that when the container application adds a new container, the corresponding IP is taken out from the IP in the pre-allocation state and allocated to the new container.

And allocating the determined IP in the pre-allocation state to the container application, specifically, binding the determined IP in the pre-allocation state with the container application, and recording the bound IP in a configuration file corresponding to the container application.

The method embodiment pre-allocates the IP for the container application, can pre-allocate the IP for the container application container, reduces the time required for applying for allocating the IP when the container needs to be immediately added and put into use due to the service requirement, can immediately put the added container into use, and reduces the cost waste caused by allocating the IP in advance.

In an embodiment, as shown in fig. 2, the method further comprises:

s106a, if a capacity expansion request of the container application is received, creating containers of the container application, where the created containers are the same as the containers that need to be newly added in the capacity expansion request.

S106b, the IP with the same number as the newly added containers is taken out from the IP in the pre-allocation state related to the container application and allocated to the created containers.

If the number of the newly added containers is 1, taking out an IP from the IPs in the pre-distribution state, and distributing the IP to the newly added containers; if the number of the newly added containers is multiple, taking out multiple IPs from the IPs in the pre-allocation state, and allocating the multiple IPs to the newly added containers. Thus, the speed of putting the container into use is accelerated.

After pre-allocating the IP, the IP in the pre-allocated state is equivalent to being occupied, and other container applications can not use the IP in the pre-allocated state any more. In an embodiment, the method further comprises:

if the container application is detected to be offline, setting the IP state of the pre-allocated IP corresponding to the container application to be an idle state; or receiving a release request for releasing the pre-allocated IP, and setting the IP state of the pre-allocated IP corresponding to the release request as an idle state. Thus, the pre-allocated IP is avoided, and the pre-allocated IP does not use the resource waste in the morning for a long time.

Fig. 5 is a schematic block diagram of an apparatus for pre-allocating a container IP provided in an embodiment of the present application. As shown in fig. 5, the apparatus includes corresponding units for performing the method for pre-allocating container IP. Specifically, as shown in fig. 5, the apparatus 100 includes a request receiving unit 101, an area acquiring unit 102, an idle IP acquiring unit 103, a number determining unit 104, a pre-allocating unit 105, and an application binding unit 106.

A request receiving unit 101, configured to receive an allocation request for pre-allocating a container IP, where the allocation request is used to allocate an IP to a container that needs to be newly added to a container application in advance.

An area obtaining unit 102, configured to obtain an area for creating the container application.

And an idle IP obtaining unit 103, configured to obtain an idle IP in a preset IP address pool in the area.

A number determination unit 104 for determining the IP number of the pre-allocation container IP.

And the pre-allocation unit 105 is used for determining the same number of IPs from the idle IPs according to a preset rule and setting the determined states of the IPs as pre-allocation states.

An application binding unit 106, configured to allocate the determined IP in the pre-allocation state to the container application, so that when a container application adds a new container, the container application takes out the IP in the pre-allocation state and allocates the corresponding IP to the new container.

In an embodiment, as shown in fig. 6, which is a schematic block diagram of an apparatus for pre-allocating a container IP provided in another embodiment of the present application, the apparatus 200 includes a request receiving unit 101, an area obtaining unit 102, a proportion detecting unit 103a, a request sending unit 103b, an address filling unit 103c, a free IP obtaining unit 103, a quantity determining unit 104, a pre-allocating unit 105, and an application binding unit 106. The request receiving unit 101, the area obtaining unit 102, the idle IP obtaining unit 103, the quantity determining unit 104, the pre-allocating unit 105, and the application binding unit 106 correspond to those in the embodiment of fig. 5, and refer to the description in the embodiment of fig. 5 specifically.

The ratio detecting unit 103a is configured to detect whether a ratio of the number of idle IPs in the area preset IP address pool to the preset number of idle IPs in the area is lower than a preset ratio.

A request sending unit 103b, configured to send a request for applying for a new IP address field if a ratio of the idle IP number to a preset idle IP number in the area is lower than a preset ratio.

An address padding unit 103c, configured to receive a new IP address field allocated by the user according to the request, pad an IP in the new IP address field into an IP address pool, and set a state of the newly-padded IP to an idle state.

In an embodiment, the address padding unit 103c is configured to receive a new IP address field allocated by the user according to the request, pad an IP in the new IP address field into an IP address pool, set a state of the newly-padded IP to an idle state, and record a time for padding the new IP address field.

In one embodiment, as shown in fig. 6, the apparatus 200 further includes a firewall opening unit 103 d. The firewall opening unit 103d is configured to open the firewall function of the IP in the newly populated IP address segment.

In an embodiment, as shown in fig. 6, the apparatus 200 further includes a creating unit 106a and an IP allocating unit 106 b. The creating unit 106a is configured to create container instances of the container application if a capacity expansion request of the container application is received, where the number of created container instances is the same as the number of container instances that need to be newly added in the capacity expansion request. An IP allocation unit 106b, configured to fetch a corresponding number of IPs from the IPs in the pre-allocation state associated with the container application and allocate the IPs to the created container instance.

In an embodiment, the apparatus 200 further comprises a setting unit. The setting unit is used for setting the IP state of the pre-allocated IP corresponding to the container application to be an idle state if the container application is detected to be offline; or receiving a release request for releasing the pre-allocated IP, and setting the IP state of the pre-allocated IP corresponding to the release request as an idle state.

In an embodiment, the request receiving unit 101 includes an identifier obtaining unit and a request receiving determining unit. The identifier obtaining unit is configured to, if a request for creating a container application is received, obtain identifier information carried in the request for creating the container application, and determine whether the identifier information includes an identifier of a pre-allocated container IP. And the request receiving and determining unit is used for determining that the allocation request of the pre-allocation container IP is received if the identification information comprises the identification of the pre-allocation container IP.

In an embodiment, as shown in fig. 7, the number determining unit 104 includes a request detecting unit 1041, a history data judging unit 1042, a total number determining unit 1043, and an IP number determining unit 1044. The request detecting unit 1041 is configured to detect whether a setting request for setting the IP number of the pre-allocated container IP is received. If a setting request for setting the IP number of the pre-allocation container IP is received from the user, the IP number determination unit 1044 sets the IP number of the pre-allocation container IP according to the setting request, and uses the IP number of the pre-allocation container IP set by the user as the determined IP number of the pre-allocation container IP. The historical data determining unit 1042 is configured to determine, if a setting request for setting the number of IPs for pre-allocating a container IP by a user is not received, whether historical data information of the container application is obtained, where the historical data information includes traffic information of the container application before a current time or a preset container application similar to the container application, and corresponding container number information. A total number determining unit 1043, configured to determine, if the historical data information of the container application is obtained, a total number of containers that the container application needs to create according to the traffic information and the corresponding container number information. The IP number determining unit 1044 is further configured to determine the IP number of the pre-allocated container IP according to the total number of containers required to be created by the container application and the number of containers already created by the container application. The IP number determining unit 1044 is further configured to, if no history data information is obtained, obtain a preset IP number as the determined IP number of the pre-allocated container IP.

In one embodiment, as depicted in FIG. 8, pre-allocation unit 105 includes an address fragment acquisition unit 1051, an idle IP detection unit 1052, a pre-allocation determination unit 1053, and a state setting unit 1054. The address field obtaining unit 1051 is configured to obtain an IP address field of the container IP allocated by the container application. An idle IP detection unit 1052, configured to detect whether there are a corresponding number of idle IPs in the IP address field. A pre-allocation determining unit 1053, configured to determine, if there are a corresponding number of idle IPs in the IP address field, a corresponding number of idle IPs from the IP address field as the determined IPs. The pre-allocation determining unit 1053 is further configured to, if the number of idle IPs in the IP address field is less than the number of IPs in the pre-allocation container IP, obtain the remaining idle IPs in the IP address field, determine the remaining number of idle IPs from the next IP address field in which an idle IP exists, and take the obtained remaining idle IPs and the determined idle IPs as the determined IPs, where the remaining number is the difference between the number of IPs and the number of remaining idle IPs. The pre-allocation determining unit 1053 is further configured to determine, if there is no idle IP in the IP address field, the same number of idle IPs as the determined IP from the next IP address field in which there is an idle IP. A state setting unit 1054 for setting the determined state of the IP to a pre-allocation state.

In an embodiment, the pre-allocation determining unit 1053 obtains the next IP address field with idle IP according to the sequence of the filling time of the IP address field.

It should be noted that, as will be clear to those skilled in the art, specific implementation processes of the above apparatus and each unit may refer to corresponding descriptions in the foregoing method embodiments, and for convenience and brevity of description, no further description is provided herein.

The above-described apparatus may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 9.

Fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present application. The device is a server and other devices in the cloud platform. The device 300 includes a processor 302, memory, and network interface 303 connected by a system bus 301, where the memory may include a non-volatile storage medium 304 and internal memory 305.

The non-volatile storage medium 304 may store an operating system 3041 and computer programs 3042. The computer program 3042 stored in the non-volatile storage medium may implement the method of pre-allocating a container IP described above when executed by the processor 302. The processor 302 is used to provide computing and control capabilities to support the operation of the overall device. The internal memory 305 provides an environment for running a computer program in a non-volatile storage medium, which when executed by the processor 302, causes the processor 302 to perform the method for pre-allocating a container IP as described above. The network interface 303 is used for network communication. Those skilled in the art will appreciate that the configuration shown in fig. 9 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation on the devices to which the present application applies, and that a particular device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

Wherein the processor 302 is configured to run a computer program stored in the memory to implement the steps of:

In an embodiment, before the step of obtaining the free IP in the preset IP address pool in the area, the processor 302 further implements the following steps:

detecting whether the ratio of the idle IP number in the area preset IP address pool to the preset idle IP number in the area is lower than a preset ratio or not; if the ratio of the idle IP number to the preset idle IP number in the area is lower than the preset ratio, sending a request for applying for a new IP address field; and receiving a new IP address field allocated by the user according to the request, filling the IP in the new IP address field into an IP address pool, and setting the state of the newly filled IP as an idle state.

In an embodiment, after the processor 302 performs the steps of receiving a new IP address field allocated by the user according to the request, populating an IP address pool with the IP in the new IP address field, and setting the state of the newly populated IP to be an idle state, the following steps are further implemented:

and opening the firewall function of the newly filled IP address field.

In an embodiment, when the processor 302 executes the steps of determining the same number of IPs from the idle IPs according to the preset rule, and setting the determined IP state as the pre-allocation state, the following steps are specifically implemented:

acquiring an IP address field of the container IP allocated by the container application; detecting whether the IP address field has a corresponding number of idle IPs; if the IP address field has a corresponding number of idle IPs, determining the corresponding number of idle IPs from the IP address field as the determined IPs; if the number of idle IPs in the IP address field is less than the number of IPs of the pre-allocated container IPs, acquiring the remaining idle IPs in the IP address field, determining the remaining idle IPs from the next IP address field with the idle IPs, and taking the acquired remaining idle IPs and the determined idle IPs as the determined IPs, wherein the remaining number is the difference between the number of IPs and the number of the remaining idle IPs; if the idle IP does not exist in the IP address field, determining the same number of idle IPs from the next IP address field with the idle IP as the determined IP; setting the determined state of the IP to a pre-allocation state.

In an embodiment, when the processor 302 performs the step of determining the IP number of the pre-allocation container IP, the following steps are specifically implemented:

detecting whether a setting request for setting the IP number of the pre-allocation container IP is received by a user; if a setting request for setting the IP number of the pre-allocation container IP by a user is received, setting the IP number of the pre-allocation container IP according to the setting request, and taking the IP number of the pre-allocation container IP set by the user as the determined IP number of the pre-allocation container IP; if a setting request for setting the IP number of the pre-allocated container IP by a user is not received, judging whether historical data information of the container application is acquired, wherein the historical data information comprises flow information of the container application before the current time or a preset container application similar to the container application and corresponding container number information; if the historical data information of the container application is acquired, determining the total number of containers required to be created by the container application according to the flow information and the corresponding container number information; determining the IP number of the pre-allocated container IP according to the total number of the containers required to be created by the container application and the number of the containers already created by the container application; and if no historical data information is acquired, acquiring a preset IP number as the determined IP number of the pre-allocated container IP.

In an embodiment, when the processor 302 executes the step of receiving the allocation request of the pre-allocation container IP, the following steps are specifically implemented:

if a request for creating the container application is received, acquiring identification information carried in the request for creating the container application, and judging whether the identification information comprises an identification of a pre-allocated container IP (Internet protocol); and if the identification information comprises the identification of the pre-allocation container IP, determining that the allocation request of the pre-allocation container IP is received.

In one embodiment, the processor 302 further implements the following steps:

if a capacity expansion request of the container application is received, creating containers of the container application, wherein the number of the created containers is the same as the number of the containers needing to be newly added in the capacity expansion request; and taking the IP with the same number as the newly added containers from the IP in the pre-allocation state related to the container application to allocate to the created containers.

It should be understood that in the embodiments of the present application, the Processor 302 may be a Central Processing Unit (CPU), and the Processor may be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program may be stored in a storage medium, which may be a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present application also provides a storage medium. The storage medium may be a computer-readable storage medium including a non-volatile computer-readable storage medium. The storage medium stores a computer program which, when executed by a processor, implements the steps of:

In an embodiment, before the step of obtaining a free IP in a preset IP address pool in the area, the processor further implements the following steps:

In an embodiment, after performing the steps of receiving a new IP address field allocated by the user according to the request, populating an IP address pool with the IP in the new IP address field, and setting the state of the newly populated IP to be an idle state, the processor further implements the following steps:

and opening the firewall function of the newly filled IP address field.

In an embodiment, when the processor executes the steps of determining the same number of IPs from the idle IPs according to a preset rule and setting the determined IP state as a pre-allocation state, the following steps are specifically implemented:

In an embodiment, when the processor executes the step of determining the number of IPs of the pre-allocation container IP, the following steps are specifically implemented:

In an embodiment, when the processor executes the step of receiving the allocation request of the pre-allocation container IP, the following steps are specifically implemented:

In one embodiment, the processor further implements the steps of:

The storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, which can store various computer readable storage media.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and the division of the unit is only one logical function division, and other division manners may be available in actual implementation. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of pre-allocating container IPs, the method comprising:

receiving an allocation request of a pre-allocated container IP, wherein the allocation request is used for allocating the IP to a container which needs to be newly added in container application in advance;

acquiring an area for creating the container application;

acquiring idle IP in a preset IP address pool in the area;

determining the IP number of the pre-allocation container IP;

determining the same number of IPs from the idle IPs according to a preset rule, and setting the determined state of the IPs as a pre-allocation state;

and allocating the determined IP in the pre-allocation state to the container application, so that when the container application adds a new container, the corresponding IP is taken out from the IP in the pre-allocation state and allocated to the new container.

2. The method of claim 1, wherein before the obtaining of the free IP in the preset IP address pool in the area, the method further comprises:

detecting whether the ratio of the idle IP number in the area preset IP address pool to the preset idle IP number in the area is lower than a preset ratio or not;

if the ratio of the idle IP number to the preset idle IP number in the area is lower than the preset ratio, sending a request for applying for a new IP address field;

and receiving a new IP address field allocated by the user according to the request, filling the IP in the new IP address field into an IP address pool, and setting the state of the newly filled IP as an idle state.

3. The method of claim 2, further comprising:

and opening the firewall function of the IP in the newly filled IP address field.

4. The method according to claim 1, wherein the determining the same number of IPs from the idle IPs according to a preset rule and setting the states of the determined IPs to be pre-allocation states comprises:

acquiring an IP address field of the container IP allocated by the container application;

detecting whether the IP address field has a corresponding number of idle IPs;

if the IP address field has a corresponding number of idle IPs, determining the corresponding number of idle IPs from the IP address field as the determined IPs;

if the number of idle IPs in the IP address field is less than the number of IPs of the pre-allocated container IPs, acquiring the remaining idle IPs in the IP address field, determining the remaining idle IPs from the next IP address field with the idle IPs, and taking the acquired remaining idle IPs and the determined idle IPs as the determined IPs, wherein the remaining number is the difference between the number of IPs and the number of the remaining idle IPs;

if the idle IP does not exist in the IP address field, determining the same number of idle IPs from the next IP address field with the idle IP as the determined IP;

setting the determined state of the IP to a pre-allocation state.

5. The method of claim 1, wherein the determining the number of IPs for the pre-allocated container IP comprises:

detecting whether a setting request for setting the IP number of the pre-allocation container IP is received by a user;

if a setting request for setting the IP number of the pre-allocation container IP by a user is received, setting the IP number of the pre-allocation container IP according to the setting request, and taking the IP number of the pre-allocation container IP set by the user as the determined IP number of the pre-allocation container IP;

if a setting request for setting the IP number of the pre-allocated container IP by a user is not received, judging whether historical data information of the container application is acquired, wherein the historical data information comprises flow information of the container application before the current time or a preset container application similar to the container application and corresponding container number information;

if the historical data information of the container application is acquired, determining the total number of containers required to be created by the container application according to the flow information and the corresponding container number information;

determining the IP number of the pre-allocated container IP according to the total number of the containers required to be created by the container application and the number of the containers already created by the container application;

and if no historical data information is acquired, acquiring a preset IP number as the IP number of the pre-allocated container IP.

6. The method of claim 1, wherein receiving an allocation request for a pre-allocated container IP comprises:

if a request for creating the container application is received, acquiring identification information carried in the request for creating the container application, and judging whether the identification information comprises an identification of a pre-allocated container IP (Internet protocol);

and if the identification information comprises the identification of the pre-allocation container IP, determining that the allocation request of the pre-allocation container IP is received.

7. The method of claim 1, further comprising:

if a capacity expansion request of the container application is received, creating containers of the container application, wherein the number of the created containers is the same as the number of the containers needing to be newly added in the capacity expansion request;

and taking the IP with the same number as the newly added containers from the IP in the pre-allocation state related to the container application to allocate to the created containers.

8. An apparatus for pre-allocating container IPs, said apparatus for pre-allocating container IPs comprising:

the device comprises a request receiving unit, a processing unit and a processing unit, wherein the request receiving unit is used for receiving an allocation request of a pre-allocated container IP, and the allocation request is used for allocating the IP to a container which needs to be newly added for container application in advance;

an area acquisition unit configured to acquire an area in which the container application is created;

an idle IP obtaining unit, configured to obtain an idle IP in a preset IP address pool in the area;

a quantity determination unit for determining the IP quantity of the pre-allocation container IP;

the pre-allocation unit is used for determining the same number of IPs from the idle IPs according to a preset rule and setting the determined state of the IPs as a pre-allocation state;

and the application binding unit is used for allocating the determined IP in the pre-allocation state to the container application so as to take out the corresponding IP from the IP in the pre-allocation state to be allocated to the newly added container when the container application adds the newly added container.

9. A computer device, comprising a memory, and a processor coupled to the memory;

the memory is used for storing a computer program; the processor is configured to execute a computer program stored in the memory to perform the method of any of claims 1-7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.