CN110289982B - Container application capacity expansion method and device, computer equipment and storage medium - Google Patents
Container application capacity expansion method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110289982B CN110289982B CN201910410683.0A CN201910410683A CN110289982B CN 110289982 B CN110289982 B CN 110289982B CN 201910410683 A CN201910410683 A CN 201910410683A CN 110289982 B CN110289982 B CN 110289982B
- Authority
- CN
- China
- Prior art keywords
- container
- application
- expanded
- instance
- instances
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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/0876—Aspects of the degree of configuration automation
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The embodiment of the application provides a container application capacity expansion method and device, 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: acquiring the application environment and the area of the container application according to the set number of the container instances of the container application to be expanded and the acquired identification information of the container application, determining a host and an IP of the container instances to be expanded according to the application environment and the area of the container application and the number of the container instances to be expanded, inheriting the information of the container instances created by the container application, creating the container instances to be expanded on the determined host according to the inherited information of the container instances, and setting the determined IP as the IP of the container instances to be expanded. The embodiment of the application can realize capacity expansion of the container instance of the container application, improve the speed and efficiency of the capacity expansion of the container application, and improve the user experience while ensuring the service when the user request is increased.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for extending a container application, a computer device, and a storage medium.
Background
In a cloud Platform, such as a Platform as a Service (PaaS) Platform, when a container application is created, a general container application is put into use. However, in the process of providing services by the container application, if the user traffic is increased and the container instances of the container application are not changed, more and more users are required to respond to each container instance. Due to the limited resources of each container instance of the container application, more and more users may cause the container application not to well meet the user's requirements, such as the response becomes slow, which inevitably reduces the user's experience. The conventional capacity expansion of container application requires a user to manually expand the capacity by using a plurality of professional command sentences one by one, so the capacity expansion efficiency is low, mistakes are easily made, and the specific and high professional knowledge of the user is required.
Disclosure of Invention
Embodiments of the present application provide a method and an apparatus for capacity expansion of a container application, a computer device, and a storage medium, which can improve user experience while ensuring a service when a user requests an increase in capacity, and improve capacity expansion efficiency of the container application.
In a first aspect, an embodiment of the present application provides a capacity expansion method for a container application, including:
if a capacity expansion setting instruction is received, acquiring a container application identifier in the capacity expansion setting instruction, and calling a preset setting interface according to the capacity expansion setting instruction so as to set the number of container instances to be expanded of the container application through the preset setting interface; if a capacity expansion instruction is received, acquiring an application environment corresponding to the container application, an area of the container application and resource information required by a container instance to be expanded from a database according to the container application identifier; determining a host of the container instance to be expanded according to the application environment of the container application, the area of the container application, the number of the container instances to be expanded and resource information required by the container instances to be expanded; determining the IP of the container instance to be expanded according to the application environment of the container application, the area of the container application and the number of the container instances to be expanded; inheriting the information of the created container instance of the container application, creating a container instance to be expanded on the determined host according to the inherited information of the container instance, and setting the determined IP as the IP of the expanded container instance; and updating the information of the created container instance to a database.
In a second aspect, an embodiment of the present invention provides a capacity expansion device for a container application, where the capacity expansion device for the container application includes a unit configured to execute the method according to 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, an embodiment of 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 described in the first aspect.
The embodiment of the application can realize the capacity expansion of the container instance of the container application, the user experience is improved while the service is ensured when the user request is increased, the specific capacity expansion process of the container instance of the container application is automatically carried out, the capacity expansion efficiency of the container application is improved, the capacity expansion can be carried out without specific and higher professional knowledge of the user, and the time cost and the labor cost are saved.
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 schematic flowchart of a capacity expansion method for a container application according to an embodiment of the present application;
fig. 2 is a schematic sub-flow diagram of a capacity expansion method for a container application according to an embodiment of the present application;
fig. 3 is a schematic sub-flow diagram of a capacity expansion method for a container application according to an embodiment of the present application;
fig. 4 is a schematic sub-flow chart of a capacity expansion method for a container application according to an embodiment of the present application;
FIG. 5 is a schematic block diagram of a capacity expansion device for a container application provided by an embodiment of the present application;
fig. 6 is a schematic block diagram of an IP determination unit provided in an embodiment of the present application;
FIG. 7 is a schematic block diagram of an inheritance unit provided by an embodiment of the present application;
FIG. 8 is a schematic block diagram of a load update unit provided in 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, of the 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 flowchart of a capacity expansion method for a container application according to an embodiment of the present application. As shown in fig. 1, the method includes S101-S106.
S101, if a capacity expansion setting instruction is received, acquiring a container application identifier in the capacity expansion setting instruction, and calling a preset setting interface according to the capacity expansion setting instruction so as to set the number of container instances to be subjected to capacity expansion of the container application through the preset setting interface.
The capacity expansion setting instruction of the container application can be triggered in various ways, such as being triggered by a user touching or clicking a related button or an image, and such as clicking a capacity expansion button corresponding to a certain container application in a list of the container application to trigger the capacity expansion setting instruction of the container application; and voice capacity expansion information of the user can be received to trigger and the like. In this embodiment, the manner of triggering the capacity expansion setting instruction of the container application is not limited. The capacity expansion setting instruction includes information of the container application, such as identification information of the container application. The identification information of the container application may be a name of the container application or a number of the container application, and the like, which may determine which container application is specific. And calling a preset setting interface according to the capacity expansion setting instruction, wherein the preset setting interface is developed by a developer and can exist in the form of one setting interface. The number of the container instances to be expanded of the container application can be set through a preset setting interface. For example, in an embodiment, the preset setting interface may further set the use time of the container instance to be expanded and the resource group of the container instance to be expanded. The service time of the container example to be expanded can be in a month unit, and other time can be in other units. It can be understood that the container instance to be expanded is charged after successful expansion, and the resource group of the container application includes a resource account for the charge required for expansion.
In one embodiment, a preset setting interface is called according to a capacity expansion setting instruction, and data such as the number of container instances to be expanded, the service time of the container instances to be expanded, and resource groups of the container instances to be expanded in the preset setting interface all have default values; detecting whether the modification of the default value by the user is received; if the modification of the default value by the user is received, taking the modified value as a final value; and if the modification of the user is not received, taking the default value as a final value. The number of the container instances to be expanded may be determined according to the increased number of the current user access amount and the preset user access amount that each container instance may normally access. The service time of the container instance to be expanded is defaulted to 1 month, and the resource group of the container instance to be expanded is defaulted to the resource group used when the container application is created.
And S102, if a capacity expansion instruction is received, acquiring the application environment corresponding to the container application, the area of the container application and the resource information required by the container instance to be expanded from a database according to the identifier of the container application.
The capacity expansion instruction may be triggered in various ways, such as by a user touching or clicking a relevant button (e.g., a confirm button, a submit button, etc.) or an image; and voice capacity expansion information of the user can be received to trigger and the like. In this embodiment, the manner of triggering the capacity expansion instruction of the container application is not limited.
And determining which container application can be determined according to the identification information of the container application, so as to further search the application environment of the container application, the area of the container application and the resource information required by the container instance to be expanded in the database.
The application environment of the container application includes a production environment, a test environment, a development environment, and the like. Wherein, the production environment means that the container application is successfully created and then is connected to the external environment or is accessed by an external user; the test environment means that the container application is used for testing after being successfully created; the development environment means that the container application is successfully created and then used for development. And determining the position of the container application creation according to the application environment of the container application and the area of the container application. Wherein, the area of container application is composed of two parts: "area" + "safe area". Wherein a "safe area" is a sub-area under the "area". Determining the specific position of the container application, and determining according to the application environment of the container application and the area of the container application, which can be understood as creating the container application in a machine room corresponding to a certain area under a certain application environment. Such as creating the container application in a computer room where an SF (a smaller area identification under the letter) sub-area under the letter (place name) area under the test environment is located. It can be understood that one application environment and one area determine one machine room position, and different application environments in the same area correspond to different machine rooms. The resource information required by the container instance to be expanded may be determined according to the resource information required to be used for creating the container instance and stored in the container instance that has been created successfully, and specifically, the resource information required by the container application that has been created successfully may be obtained from the database.
S103, determining a host of the container instance to be expanded according to the application environment of the container application, the area of the container application, the number of the container instances to be expanded and resource information required by the container instances to be expanded.
Specifically, the position of container application creation is determined according to the application environment of the container application and the area of the container application; determining a host machine cluster according to the determined position created by the container application; and determining a specific host of the container instances to be expanded from the determined host cluster according to the number of the container instances to be expanded and the resource information required by the container instances to be expanded. Specifically, the specific host cluster is determined automatically by a container arrangement tool, the host cluster where the container application is located is identified by the container arrangement tool according to the application environment of the container application and the area of the container application, and the container arrangement tool determines the host of the container instance to be expanded from the host cluster according to the number of the container instances to be expanded, the resource information required by the container instances to be expanded, and the resource condition of the host cluster. The container arrangement tool may be a Marathon arrangement tool, or may be another container arrangement tool. One container instance is created on one host, and understandably, one container instance corresponds to one host. And if the number of the container instances to be expanded is multiple, correspondingly determining multiple host machines.
And S104, determining the IP of the container instance to be expanded according to the application environment of the container application, the area of the container application and the number of the container instances to be expanded.
In an embodiment, determining an IP of a container instance to be expanded according to an application environment of the container application, an area of the container application, and a set number of container instances of the container application to be expanded includes: determining the position of container application creation according to the application environment of the container application and the area of the container application; determining a pre-allocated IP address pool for creating the container instance according to the determined position of the container application creation; and acquiring the IP addresses with the same number as the container instances of the container application to be expanded from the IP address pool, and determining the acquired IP addresses as the IP of the container instances to be expanded. And if the number of the container instances to be expanded is multiple, correspondingly determining multiple IPs.
In one embodiment, as shown in FIG. 2, step S104 includes the following steps S1041-S1048.
S1041, judging whether the container application has a pre-allocation IP, wherein the pre-allocation IP is an IP allocated to a container instance which needs to be newly added to the container application in advance, and the pre-allocation IP is only used by the container application.
Some container applications pre-allocate some IPs at or after creation for the container application, and these IPs are used to directly allocate to the newly added container instance when the container application adds the container instance, and these IPs are called pre-allocation IPs. The pre-allocated IP is pre-allocated to the container application and is only used by the container application and not used by any other container application. The container instance IP allocation speed can be improved by directly allocating the pre-allocation IP to the container instance of the container application.
Wherein, the pre-allocated IP has corresponding identification information. If the container application has pre-allocated IPs, the number of pre-allocated IPs, the IP states in the pre-allocated IPs, and the corresponding IP addresses of the container application are stored in the database. The IP state in the pre-allocated IP includes an idle state, an allocated state, and the like. And acquiring the idle IP number of the IP state in the pre-allocated IP which is in the idle state.
If the container application has a pre-allocated IP, execute step S1042; if the container application does not have the pre-allocated IP, step S1047 is executed.
S1042, judging whether the number of idle IPs in the pre-allocation IPs of the container application is larger than or equal to the number of container instances to be expanded.
If the container application has the pre-allocation IP, acquiring the number of idle IPs in the pre-allocation IP of the container application, and judging whether the number of the idle IPs in the pre-allocation IP of the container application is greater than or equal to the number of container instances to be expanded.
If the number of idle IPs in the container application pre-allocation IPs is greater than or equal to the number of container instances to be expanded, executing step S1043; otherwise, step S1044 is executed.
S1043, obtaining the idle IPs with the same number as the container instances to be expanded from the idle IPs in the pre-allocation IPs, and using the obtained idle IPs as the IPs of the container instances to be expanded.
S1044, determining the number of the residual IP to be allocated according to the number of the idle IP in the pre-allocated IP and the number of the container instances to be expanded.
Specifically, the difference between the number of container instances to be expanded and the number of idle IPs in the pre-allocated IPs is calculated, and the difference is used as the number of remaining IPs to be allocated.
S1045, determining the position of the container application creation according to the application environment of the container application and the area of the container application, and acquiring an IP address pool which is pre-allocated to the corresponding position in the database and is used for creating a container instance.
S1046, obtaining the idle IPs with the same number as the residual IPs to be distributed from the IP address pool, and taking all the idle IPs in the pre-distributed IPs and the idle IPs obtained from the IP address pool as the IPs of the container instances to be expanded of the container application.
In the above steps S1042 to S1046, the IP of the container instance to be expanded is determined according to the number of idle IPs in the pre-allocated IP, the number of container instances to be expanded, the application environment of the container application, and the area of the container application.
S1047, determining the position of the container application creation according to the application environment of the container application and the area of the container application, and acquiring an IP address pool which is pre-allocated to the corresponding position in the database and is used for creating a container instance.
And S1048, determining the idle IPs with the same number as the container instances to be expanded from the IP address pool, and taking the obtained idle IPs as the IPs of the container instances to be expanded.
When allocating the IP to the container instance to be expanded in steps S1041 to S1048, considering whether there is a pre-allocated IP in the container application, the IP is preferentially allocated to the container instance to be expanded from the pre-allocated IP.
It should be noted that the execution sequence of the step of determining the host of the container instance to be expanded and the step of determining the IP of the container instance to be expanded is not specifically limited, that is, the execution sequence of step S103 and step S104 is not limited, and in other embodiments, step S104 may be executed first, and then step S103 may be executed. In other embodiments, step S103 and step S103 may be performed simultaneously or separately.
S105, inheriting the information of the container instance created by the container application, creating the container instance to be expanded on the determined host according to the inherited information of the container instance, and setting the determined IP as the IP of the expanded container instance.
In one embodiment, as shown in FIG. 3, the step S105 includes the following steps S1051-S1053.
S1051, inheriting the information of the container instance created by the container application.
Inheriting information of the container instance created by the container application, which can be simply understood as copying information of the container instance created by the container application.
S1052, the inherited container instance information is sent to the determined host machine through the container arrangement tool, and a capacity-expanded container instance is created.
And creating a container instance to be expanded on the determined host according to the inherited information of the container instance created by the container application. Thus, the created expanded container instance inherits the application package, configuration, and the like of the existing created container instance, and is not created again according to the application image and configuration of the container application, that is, the application package, configuration, and the like do not need to be uploaded again. Therefore, the speed of the container instance applied by the expansion container is greatly increased, and the second-level expansion can be achieved.
Meanwhile, it should be noted that if there are a plurality of container instances to be expanded, the container instances to be expanded may be created in parallel on the determined hosts. Each container example to be expanded corresponds to one host, and a plurality of container examples to be expanded are established in parallel, so that the expansion speed is further increased.
When the container instance to be expanded is created on the determined host machine, the inherited information of the container instance can be sent to the determined host machine through the container arranging tool, and the container instance to be expanded is created on the determined host machine. The container arrangement tool may be a Marathon tool or another tool. It should be noted that, since the container arrangement tool may be connected to the host, when expanding the volume of the container application, the volume expansion may be performed on the host without logging on a specific host (the current method of expanding the volume needs to log on the specific host first and then expand the volume), so that the efficiency of expanding the container application is improved by expanding the volume through the container arrangement tool; in addition, when the capacity is expanded for the container application, the capacity expansion can be performed without the need of higher professional knowledge of a user, and the labor cost is reduced.
S1053, connecting the created container instance, binding the created container instance with the determined IP, and setting the determined container IP as the IP of the created container instance.
When the creation of the container instance to be expanded is completed, the IP of the container instance needs to be set for the created container instance. The IP may be set by the automation operation and maintenance tool, and specifically, the created container instance is connected by the automation operation and maintenance tool, and the created container instance is bound to the determined IP of the container instance to be expanded. Wherein, the automatic operation and maintenance tools are the ansable tools and the like.
And S106, updating the information of the created container instance to a database.
The information of the created container instance is information of the expanded container instance, and includes information such as an IP of the expanded container instance, a host where the expanded container instance is located, and the number of the expanded container instances. The database is updated to remain consistent with the data in the database.
In an embodiment, when the set information further includes the usage time of the container instance to be expanded and the resource group of the container instance to be expanded, before step S102, the method further includes the following step S102 a.
S102a, determining whether there is enough money in the resource group to expand the corresponding container instance according to the number of container instances to be expanded by the container application, the using time of the container instances to be expanded, and the resource group of the container instances to be expanded.
The cost required by the container instances of the container expansion application is determined according to the number of the container instances to be expanded, the using time of the container instances to be expanded and the unit price of each container instance to be expanded in each month. The cost of the container instances to be expanded is the number of container instances to be expanded, the usage time of the container instances to be expanded, and the unit price per month of each container instance to be expanded. Calculating the difference value between the residual amount in the resource group and the cost needed by the container example to be expanded; if the difference is greater than or equal to zero, determining that sufficient money exists in the resource group to expand the container instance; if the difference is less than zero, it is determined that there is not sufficient money in the resource group to expand the container instance.
If it is determined that there is a sufficient amount to expand the container instance in the resource group, go to step S102; if it is determined that there is not a sufficient amount to expand a container instance in the resource group, step S102b is performed.
And S102b, prompting.
The embodiment further determines whether there is a sufficient amount of money in the resource group of the container instance to be expanded to create the container instance to be expanded.
In an embodiment, as shown in fig. 1, the capacity expansion method for a container application further includes the following steps S107 to S108.
S107, detecting whether the container application creates a load balancing application.
Wherein, understandably, the load balancing application provides load for the container application, and thus, the container application can be understood as a backend application of the load balancing application, and the backend application is an application which really provides service. And acquiring the information of the container application according to the identification information of the container application, wherein the information of the container application comprises whether the container application creates the load balancing application. And if the container application does not create the load balancing application, ending.
And S108, if the container application creates the load balancing application, modifying the configuration file of the load balancing application according to the type of the load balancing application so as to add the information of the created container instance in the configuration file.
Information of a container instance of the container application is recorded in a configuration file of a load balancing application of the container application. After the container application is expanded, if the container instance of the expanded container application is desired to start to provide the service, the expanded container instance needs to be added into a configuration file of the load balancing application of the container application, so that the load balancing application can distribute the user request to the container instance of the expanded container application according to a load balancing algorithm when distributing the user request, and the container instance of the container application can really provide the service.
The load balancing application comprises F5, LVS (linux Virtual Server) load balancing application, Haproxy load balancing application, Nginx load balancing application and the like. Among them, because the F5 load balancing application is a hard load balancing application, created on a specific F5 device, and the LVS load balancing application, the Haproxy load balancing application, the Nginx load balancing application, etc. are soft load balancing applications, the types of load balancing applications include F5 and non-F5, where the non-F5 includes the LVS load balancing application, the Haproxy load balancing application, the Nginx load balancing application, etc. The information of the container instance added in the configuration file at least comprises the IP of the container instance and the port corresponding to the container instance for providing the service.
In one embodiment, as shown in FIG. 4, step S108 includes the following steps S1081-S1086.
S1081, judging whether the type of the load balancing application of the container application is F5.
S1082, if the type of the load balancing application of the container application is F5, determining F5 equipment where the F5 load balancing application is located according to the container application.
S1083, obtaining a configuration file of the F5 load balancing application on the F5 device, and adding information of the created container instance in the configuration file.
Specifically, the information of each created container instance is used as the information of each pool member, wherein the information of each created container instance comprises the information of the IP of the container instance, the port of the container instance for providing service, the running state of the container instance and the like; and modifying the number of pool members in the pool information, wherein the number of the modified pool members is equal to the number of the pool members before modification plus the number of the created container instances.
S1084, if the type of the load balancing application is not F5, determining a corresponding container of the load balancing application according to the container application, acquiring a configuration file from the corresponding container of the load balancing application, and downloading the acquired configuration file to the local.
If the type of the load balancing application is not F5, determining a corresponding container of the load balancing application according to the container application, and acquiring a configuration file of the load balancing application from the container of the load balancing application; and downloading the acquired configuration file to a local preset directory. It should be noted that, downloading the acquired configuration file to the local for modifying the configuration file, rather than directly and remotely modifying the configuration file on the container of the load balancing application, takes into account that if the network is interrupted during the process of modifying the configuration file, the rewriting process is also interrupted, i.e. the influence of an unexpected situation occurring during the process of remotely rewriting the configuration file is eliminated, and on the other hand, the speed of rewriting the configuration file in the local is faster than that in the remote.
S1085, adding information of the created container instance in the configuration file.
If the load balancing application is the LVS load balancing application, adding the created container instance information to a configuration file (the configuration file indicated here includes keepalive. conf) of the LVS load balancing application, including: acquiring a preset container instance template; for each port of the container application, copying the container instance template by the same number of copies according to the expanded container instance number; replacing the IP parameters of the container instance in the container instance template with the IP of the expanded container instance, and replacing the port of the container application with the port parameters in the container instance template, so as to finish the replacement of all container instance templates under the port of the container application; and inserting the replaced container instance template into a corresponding position in the configuration file of the LVS load balancing application so as to add the information of the expanded container instance in the configuration file of the LVS load balancing application.
The container instance template comprises an IP parameter of a container instance, a port parameter of a container instance providing service, a health check parameter of the container instance and the like, wherein the port parameter of the container instance providing service is determined according to a port of a container application, and the parameter values in the health check parameter of the container instance, the weight parameter of the container instance and the like have corresponding default values. In the replacement, for each port of the container application, the IP of one container instance is expanded to replace the IP in one container instance template. It can be understood that if there are 2 service-providing ports of the container application and the number of the container instances to be expanded is 1, then 2 container instance templates need to be copied; if the container application has 2 ports to service and the number of container instances to be expanded is 2, then 4 container instance templates need to be copied. Each container instance template corresponds to a port of the container application and an IP of the container instance being expanded. In a configuration file of the LVS load balancing application, in a section of configuration (code segment) determined by the virtual IP and each LVS port, after the configuration corresponding to the last real server, that is, after the configuration corresponding to the container instance of the last container application, the replaced container instance template content is added. Wherein, each real server corresponds to the content of the container instance of one container application.
In an embodiment, if there is no pre-stored container instance template, the configuration content of a real server part in the LVS load balancing application may also be directly obtained as the container instance template.
If the load balancing application is a Haproxy load balancing application, adding the created container instance information to a configuration file of the Haproxy load balancing application (where the configuration file includes Haproxy. conf), including: positioning an option forward node in a listen node in a configuration file; and adding information of the created container instance in a server node under the option forward node, wherein the information of the added container instance comprises the IP of the container instance, the port of the container instance (namely the port of the container application), health check parameters and the like. The information of one container instance corresponds to one server node segment, and the information of a plurality of container instances corresponds to a plurality of server node segments.
If the load balancing application is a Nginx load balancing application, then the created container instance information is added to a configuration file for the Nginx load balancing application (the configuration file referred to herein includes Nginx. conf), including: and positioning an upstream node in the configuration file, and adding information of the created container instance in a server node below the upstream node, wherein the information of the added container instance comprises the IP of the container instance, the port of the container instance (namely the port of the container application), health check parameters and the like. The information of one container instance corresponds to one server node segment, and the information of a plurality of container instances corresponds to a plurality of server node segments.
S1086, pushing the configuration file added with the information of the created container instance to the corresponding container of the load balancing application, and restarting the load balancing service of the corresponding container of the load balancing application, so that the modification of the configuration file is effective.
Fig. 5 is a schematic block diagram of a capacity expansion device for a container application according to an embodiment of the present application. The device comprises a unit corresponding to the capacity expansion method for executing the container application. As shown in fig. 5, the capacity expansion apparatus 100 for container application includes a setting unit 101, an obtaining unit 102, a host determining unit 103, an IP determining unit 104, a capacity expansion unit 105, and an information updating unit 106.
The setting unit 101 is configured to, if a capacity expansion setting instruction is received, obtain a container application identifier in the capacity expansion setting instruction, and call a preset setting interface according to the capacity expansion setting instruction, so as to set, through the preset setting interface, a number of container instances to be subjected to capacity expansion in the container application.
The obtaining unit 102 is configured to, if a capacity expansion instruction is received, obtain, from a database, an application environment corresponding to the container application, an area of the container application, and resource information required by a container instance to be expanded, according to the container application identifier.
A host determining unit 103, configured to determine a host of the container instance to be expanded according to the application environment of the container application, the area of the container application, the number of container instances to be expanded, and resource information required by the container instance to be expanded;
an IP determining unit 104, configured to determine an IP of the container instance to be expanded according to the application environment of the container application, the area of the container application, and the number of the container instances to be expanded.
A capacity expansion unit 105, configured to inherit the information of the container instance created by the container application, create, according to the inherited information of the container instance, a container instance to be expanded on the determined host, and set the determined IP as an IP of the expanded container instance.
And an information updating unit 106, configured to update the information of the created container instance to the database.
In an embodiment, as shown in fig. 5, the capacity expansion device 100 for a container application further includes a determining unit 102a and a prompting unit 102 b. The determining unit 102a is configured to determine whether there is enough money in the resource group to expand the corresponding container instance according to the number of container instances to be expanded in the container application, the use time of the container instances to be expanded, and the resource group of the container instances to be expanded. If it is determined that there is not a sufficient amount in the resource group to accommodate the container instance, the prompting unit 102b is triggered for prompting. If it is determined that there is a sufficient amount of money in the resource group to accommodate the container instance, acquisition unit 102 is triggered.
In an embodiment, as shown in fig. 6, the IP determining unit 104 includes a pre-allocation determining unit 1041, an address pool determining unit 1042, a container IP determining unit 1043, a number determining unit 1044, and a remaining number determining unit 1045. The pre-allocation determining unit 1041 is configured to determine whether a pre-allocation IP exists in the container application, where the pre-allocation IP is an IP that is allocated to a container instance that needs to be newly added to the container application in advance, and the pre-allocation IP is only used by the container application. The address pool determining unit 1042 is configured to determine, if the container application does not have a pre-allocated IP, a location where the container application is created according to an application environment of the container application and an area of the container application, and obtain an IP address pool, which is pre-allocated to a corresponding location in a database and used for creating a container instance. A container IP determining unit 1043, configured to determine, from the IP address pool, idle IPs whose number is the same as that of the container instances to be expanded, and use the obtained idle IPs as the IPs of the container instances to be expanded. A quantity determining unit 1044, configured to determine whether the quantity of idle IPs in the container application pre-allocation IP is greater than or equal to the quantity of container instances to be expanded if the container application has a pre-allocation IP. The container IP determining unit 1043 is further configured to, if the number of idle IPs in the container application pre-allocation IP is greater than or equal to the number of container instances to be expanded, obtain, from the idle IPs in the pre-allocation IP, idle IPs whose number is the same as the number of container instances to be expanded, and use the obtained idle IPs as the IPs of the container instances to be expanded. A remaining number determining unit 1045, configured to determine, if the number of idle IPs in the container application pre-allocation IP is smaller than the number of container instances to be expanded, the number of remaining IPs to be allocated according to the number of idle IPs in the pre-allocation IP and the number of container instances to be expanded. The address pool determining unit 1042 is further configured to determine, according to the application environment of the container application and the area of the container application, a location where the container application is created, and obtain an IP address pool, which is pre-allocated to a corresponding location in the database and used for creating a container instance. The container IP determining unit 1043 is further configured to obtain, from the IP address pool, the number of idle IPs that is the same as the number of remaining IPs that need to be allocated, and use all idle IPs in the pre-allocated IPs and the idle IPs obtained from the IP address pool as the IP of the container instance to be expanded for the container application.
In one embodiment, as shown in fig. 7, the capacity expansion unit 105 includes an inheritance unit 1051, a container creation unit 1052, and an IP setting unit 1053. Wherein, the inheriting unit 1051 is configured to inherit information of the container instance created by the container application. A container creating unit 1052, configured to send the inherited information of the container instance to the determined host through a container orchestration tool, and create a volume-expanded container instance. And the IP setting unit is used for connecting the created container instance, binding the created container instance with the determined IP and setting the determined IP as the IP of the created container instance.
In an embodiment, as shown in fig. 5, the capacity expansion apparatus 100 of the container application further includes a detection unit 107 and a configuration update unit 108. Wherein the content of the first and second substances,
a detecting unit 107, configured to detect whether the container application creates a load balancing application.
And a load updating unit 108, configured to, if the container application creates a load balancing application, modify a configuration file of the load balancing application according to a type of the load balancing application, so as to add information of the created container instance to the configuration file.
In one embodiment, as shown in fig. 8, the load update unit 108 includes a type determination unit 1081, an F5 device determination unit 1082, a load configuration update unit 1083, a configuration download unit 1084, and a restart unit 1085. The type determination unit 1081 is configured to determine whether a type of a load balancing application of the container application is F5. An F5 device determining unit 1082, configured to determine, according to the container application, an F5 device where the F5 load balancing application is located, if the type of the load balancing application of the container application is F5. A load configuration updating unit 1083, configured to obtain, on the F5 device, a configuration file of the F5 load balancing application, and add information of the created container instance in the configuration file. A configuration downloading unit 1084, configured to, if the type of the load balancing application is not F5, determine, according to the container application, a container of the corresponding load balancing application, acquire a configuration file from the container of the corresponding load balancing application, and download the acquired configuration file to the local. A load configuration updating unit 1083, further configured to add information of the created container instance in the configuration file. A restarting unit 1085, configured to push the configuration file to which the information of the created container instance is added into the container of the corresponding load balancing application, and restart the load balancing service of the container of the corresponding load balancing application, so that the modification of the configuration file is effective.
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 terminal or other device, such as a server in a PaaS platform. The device 100 includes a processor 102, memory, and a network interface 103 connected by a system bus 101, where the memory may include a non-volatile storage medium 104 and an internal memory 105.
The non-volatile storage medium 104 may store an operating system 1041 and computer programs 1042. The computer program 1042 stored in the nonvolatile storage medium can implement the capacity expansion method of the container application described in the server when executed by the processor 102. The processor 102 is used to provide computing and control capabilities that support the operation of the overall device 100. The internal memory 105 provides an environment for running a computer program in the non-volatile storage medium, and when the computer program is executed by the processor 102, the processor 102 may be caused to execute the capacity expansion method of the container application described in the server. The network interface 103 is used for network communication. It will be appreciated by those skilled in the art that the configurations shown in the figures are block diagrams of only some of the configurations relevant to the present application, and do not constitute a limitation on the devices to which the present application may be applied, and that a particular device may include more or less components than those shown in the figures, or may combine certain components, or have a different arrangement of components.
The processor 102 is configured to run a computer program stored in a memory to implement any embodiment of the capacity expansion method for the container application.
It should be understood that, in the embodiment of the present application, the Processor 102 may be a Central Processing Unit (CPU), and the Processor may also 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, which is a non-volatile computer-readable storage medium. The storage medium stores a computer program which, when executed by a processor, implements any of the embodiments of the capacity expansion method for a container application described above.
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. The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (9)
1. A capacity expansion method for a container application, the method comprising:
if a capacity expansion setting instruction is received, acquiring a container application identifier in the capacity expansion setting instruction, and calling a preset setting interface according to the capacity expansion setting instruction so as to set the number of container instances to be expanded of the container application through the preset setting interface;
if a capacity expansion instruction is received, acquiring an application environment corresponding to the container application, an area of the container application and resource information required by a container example to be expanded from a database according to the container application identifier;
determining a host of the container instance to be expanded according to the application environment of the container application, the area of the container application, the number of the container instances to be expanded and resource information required by the container instances to be expanded;
judging whether the container application has a pre-allocation IP (Internet protocol), wherein the pre-allocation IP is an IP allocated to a container instance needing to be newly added to the container application in advance, and the pre-allocation IP is only used by the container application;
if the container application has the pre-allocated IP, determining the position of the container application according to the application environment of the container application and the area of the container application, and acquiring an IP address pool which is pre-allocated to the corresponding position in the database and is used for creating a container instance;
determining the number of idle IPs which is the same as the number of the container instances to be expanded from the IP address pool, and taking the obtained idle IPs as the IPs of the container instances to be expanded;
inheriting the information of the created container instance of the container application, creating a container instance to be expanded on the determined host according to the inherited information of the container instance, and setting the determined IP as the IP of the expanded container instance;
and updating the information of the created container instance to a database.
2. The method according to claim 1, wherein the preset setting interface is further configured to set a usage time of the container instance to be expanded and a resource group of the container instance to be expanded;
after receiving the capacity expansion instruction, the method further comprises:
determining whether sufficient money exists in the resource group to expand the container instances to be expanded according to the number of the container instances to be expanded in the container application, the service time of the container instances to be expanded and the resource group of the container instances to be expanded;
and if the resource group has enough money to expand the container example to be expanded, executing the step of acquiring the application environment corresponding to the container application, the area of the container application and the resource information required by the container example to be expanded from a database according to the identifier of the container application.
3. The method of claim 1, further comprising:
if the container application has the pre-allocation IP, judging whether the number of idle IPs in the pre-allocation IP of the container application is larger than or equal to the number of container instances to be expanded;
if the number of the idle IPs in the container application pre-allocation IP is larger than or equal to the number of the container instances to be expanded, acquiring the idle IPs with the number equal to the number of the container instances to be expanded from the idle IPs in the pre-allocation IP, and taking the acquired idle IPs as the IPs of the container instances to be expanded;
if the number of idle IPs in the pre-allocation IP of the container application is smaller than the number of container instances to be expanded, determining the number of residual IPs to be allocated according to the number of idle IPs in the pre-allocation IP and the number of container instances to be expanded;
determining the position of container application creation according to the application environment of the container application and the area of the container application, and acquiring an IP address pool which is pre-allocated to the corresponding position in a database and is used for creating a container instance;
and acquiring the idle IPs with the same number as the residual number of the IPs to be allocated from the IP address pool, and taking all the idle IPs in the pre-allocated IPs and the idle IPs acquired from the IP address pool as the IPs of the container instances to be expanded of the container application.
4. The method according to claim 1, wherein inheriting information of the container instance created by the container application, creating a container instance to be expanded on the determined host according to the inherited information of the container instance, and setting the determined IP as an IP of the expanded container instance, includes:
inheriting information of container instances that have been created by the container application;
sending the inherited information of the container instance to the determined host machine through a container arrangement tool, and creating a capacity-expanded container instance;
and connecting the created container instance, and binding the created container instance with the determined IP so as to set the determined IP as the IP of the created container instance.
5. The method of claim 1, further comprising:
detecting whether the container application creates a load balancing application;
and if the container application creates the load balancing application, modifying the configuration file of the load balancing application according to the type of the load balancing application so as to add the information of the created container instance in the configuration file.
6. The method of claim 5, wherein modifying the configuration file of the load balancing application according to the type of the load balancing application to add the information of the created container instance in the configuration file comprises:
judging whether the type of the load balancing application of the container application is F5;
if the type of the load balancing application of the container application is F5, determining F5 equipment where the F5 load balancing application is located according to the container application;
obtaining a configuration file of the F5 load balancing application on the F5 device, and adding information of the created container instance in the configuration file;
if the type of the load balancing application is not F5, determining a corresponding container of the load balancing application according to the container application, acquiring a configuration file from the corresponding container of the load balancing application, and downloading the acquired configuration file to the local;
adding information of the created container instance in the configuration file;
pushing the configuration file added with the information of the created container instance to the container of the corresponding load balancing application, and restarting the load balancing service of the container of the corresponding load balancing application so as to enable modification of the configuration file to be effective.
7. A flash chamber for a container application, the flash chamber comprising:
the device comprises a setting unit, a capacity expansion setting unit and a control unit, wherein the setting unit is used for acquiring a container application identifier in a capacity expansion setting instruction if the capacity expansion setting instruction is received, and calling a preset setting interface according to the capacity expansion setting instruction so as to set the number of container instances to be expanded of the container application through the preset setting interface;
the acquisition unit is used for acquiring an application environment corresponding to the container application, an area of the container application and resource information required by a container instance to be expanded from a database according to the container application identifier if an expansion instruction is received;
the host determining unit is used for determining a host of the container example to be expanded according to the application environment of the container application, the area of the container application, the number of the container examples to be expanded and the resource information required by the container example to be expanded;
the pre-allocation judging unit is used for judging whether the container application has a pre-allocation IP (Internet protocol), wherein the pre-allocation IP is an IP allocated to a container instance which needs to be newly added to the container application in advance, and the pre-allocation IP is only used by the container application;
the address pool determining unit is used for determining the position of the container application creation according to the application environment of the container application and the area of the container application if the container application has the pre-allocated IP, and acquiring an IP address pool which is pre-allocated to the corresponding position in the database and is used for creating a container instance;
a container IP determining unit, configured to determine, from the IP address pool, idle IPs that are the same in number as the number of container instances to be expanded, and use the obtained idle IPs as IPs of the container instances to be expanded;
the capacity expansion unit is used for inheriting the information of the created container instance of the container application, creating a container instance to be subjected to capacity expansion on the determined host according to the inherited information of the container instance, and setting the determined IP as the IP of the capacity expansion container instance;
and the information updating unit is used for updating the information of the created container instance to the database.
8. 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-6.
9. 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-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910410683.0A CN110289982B (en) | 2019-05-17 | 2019-05-17 | Container application capacity expansion method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910410683.0A CN110289982B (en) | 2019-05-17 | 2019-05-17 | Container application capacity expansion method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110289982A CN110289982A (en) | 2019-09-27 |
| CN110289982B true CN110289982B (en) | 2022-08-23 |
Family
ID=68002070
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910410683.0A Active CN110289982B (en) | 2019-05-17 | 2019-05-17 | Container application capacity expansion method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110289982B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111262727B (en) * | 2020-01-08 | 2023-04-07 | 广州虎牙科技有限公司 | Service capacity expansion method, device, equipment and storage medium |
| CN111314457B (en) * | 2020-02-13 | 2022-04-29 | 北京百度网讯科技有限公司 | Method and device for setting virtual private cloud |
| CN111491040B (en) * | 2020-04-09 | 2023-03-24 | 北京城市网邻信息技术有限公司 | IP distribution method and IP distribution device |
| CN111522624B (en) * | 2020-04-17 | 2023-10-20 | 成都安恒信息技术有限公司 | Message forwarding performance elastic expansion system and expansion method based on virtualization technology |
| CN111290838B (en) * | 2020-05-09 | 2020-08-18 | 支付宝(杭州)信息技术有限公司 | Application access request processing method and device based on container cluster |
| CN112822071B (en) * | 2020-12-31 | 2022-03-25 | 中国工商银行股份有限公司 | Network fault diagnosis method and device based on double-layer soft load architecture |
| CN114615340B (en) * | 2022-03-08 | 2023-10-20 | 抖音视界有限公司 | Request processing method and device, computer equipment and storage device |
| CN114726734A (en) * | 2022-03-21 | 2022-07-08 | 平安壹账通云科技(深圳)有限公司 | Cloud service resource capacity expansion method and device, electronic equipment and storage medium |
| CN115361359A (en) * | 2022-08-18 | 2022-11-18 | 中电云数智科技有限公司 | IP address management device and method based on kubernets |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102821000A (en) * | 2012-09-14 | 2012-12-12 | 乐视网信息技术（北京）股份有限公司 | Method for improving usability of PaaS platform |
| CN105159759A (en) * | 2015-08-31 | 2015-12-16 | 华为软件技术有限公司 | Application example deployment method and device |
| WO2015197564A1 (en) * | 2014-06-23 | 2015-12-30 | Getclouder Ltd. | Cloud hosting systems featuring scaling and load balancing with containers |
| CN105515864A (en) * | 2015-12-11 | 2016-04-20 | 深圳市中润四方信息技术有限公司 | Container resource adaptive adjustment method and container resource adaptive adjustment system |
| CN105979009A (en) * | 2016-07-06 | 2016-09-28 | 乾云众创（北京）信息科技研究院有限公司 | Method for automatically balancing increased load of cloud application container |
| CN106301829A (en) * | 2015-05-21 | 2017-01-04 | 华为技术有限公司 | A kind of method and apparatus of Network dilatation |
| CN107229520A (en) * | 2017-04-27 | 2017-10-03 | 北京数人科技有限公司 | Data center operating system |
| CN107766050A (en) * | 2017-10-31 | 2018-03-06 | 新华三云计算技术有限公司 | The dispositions method and device of a kind of heterogeneous applications |
| CN108023742A (en) * | 2016-10-31 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of expansion method of application, device and system |
| CN109343963A (en) * | 2018-10-30 | 2019-02-15 | 杭州数梦工场科技有限公司 | A kind of the application access method, apparatus and relevant device of container cluster |
| CN109495398A (en) * | 2017-09-11 | 2019-03-19 | 中国移动通信集团浙江有限公司 | A kind of resource regulating method and equipment of container cloud |
-
2019
- 2019-05-17 CN CN201910410683.0A patent/CN110289982B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102821000A (en) * | 2012-09-14 | 2012-12-12 | 乐视网信息技术（北京）股份有限公司 | Method for improving usability of PaaS platform |
| WO2015197564A1 (en) * | 2014-06-23 | 2015-12-30 | Getclouder Ltd. | Cloud hosting systems featuring scaling and load balancing with containers |
| CN106301829A (en) * | 2015-05-21 | 2017-01-04 | 华为技术有限公司 | A kind of method and apparatus of Network dilatation |
| CN105159759A (en) * | 2015-08-31 | 2015-12-16 | 华为软件技术有限公司 | Application example deployment method and device |
| CN105515864A (en) * | 2015-12-11 | 2016-04-20 | 深圳市中润四方信息技术有限公司 | Container resource adaptive adjustment method and container resource adaptive adjustment system |
| CN105979009A (en) * | 2016-07-06 | 2016-09-28 | 乾云众创（北京）信息科技研究院有限公司 | Method for automatically balancing increased load of cloud application container |
| CN108023742A (en) * | 2016-10-31 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of expansion method of application, device and system |
| CN107229520A (en) * | 2017-04-27 | 2017-10-03 | 北京数人科技有限公司 | Data center operating system |
| CN109495398A (en) * | 2017-09-11 | 2019-03-19 | 中国移动通信集团浙江有限公司 | A kind of resource regulating method and equipment of container cloud |
| CN107766050A (en) * | 2017-10-31 | 2018-03-06 | 新华三云计算技术有限公司 | The dispositions method and device of a kind of heterogeneous applications |
| CN109343963A (en) * | 2018-10-30 | 2019-02-15 | 杭州数梦工场科技有限公司 | A kind of the application access method, apparatus and relevant device of container cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110289982A (en) | 2019-09-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110289982B (en) | Container application capacity expansion method and device, computer equipment and storage medium | |
| US10592269B2 (en) | Dynamic code deployment and versioning | |
| CN110278288B (en) | Method and device for pre-allocating container IP, computer equipment and storage medium | |
| CN108572795B (en) | Capacity expansion method, device, equipment and storage medium based on built storage virtualization | |
| CN110225094B (en) | Load balancing application virtual IP switching method and device, computer equipment and storage medium | |
| EP3668009A1 (en) | Life cycle management method and device for network service | |
| CN109995814B (en) | Cloud host resource migration method and device, communication equipment and storage medium | |
| CN110289983B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| US11924117B2 (en) | Automated local scaling of compute instances | |
| CN110266761B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| WO2022213850A1 (en) | Method and apparatus for constructing android running environment | |
| CN110224860A (en) | Load balancing application creation method, device, computer equipment and storage medium | |
| CN110262872B (en) | Load balancing application management method and device, computer equipment and storage medium | |
| US11556369B2 (en) | Virtual machine deployment method and OMM virtual machine | |
| CN110138577B (en) | Cluster creation method, first server and readable storage medium | |
| CN111897558A (en) | Kubernets upgrading method and device for container cluster management system | |
| WO2020232887A1 (en) | Configuration modification method and apparatus for container application, and computer device and storage medium | |
| KR20130061734A (en) | Cloud-shared resource providing system | |
| CN110286997B (en) | Multi-container application creation method, device, computer equipment and storage medium | |
| CN108121543A (en) | A kind of software code process of compilation method and device | |
| EP3879875A1 (en) | Resource change method and device, apparatus, and storage medium | |
| CN110275776A (en) | Capacity reduction method, device, computer equipment and the storage medium of container application | |
| WO2020233002A1 (en) | Container instance ip switching method and apparatus, computer device, and storage medium | |
| KR102519721B1 (en) | Apparatus and method for managing computing resource | |
| CN111399860A (en) | Light application deployment method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |