CN104991815A - Docker container management method and system - Google Patents
Docker container management method and system Download PDFInfo
- Publication number
- CN104991815A CN104991815A CN201510347731.8A CN201510347731A CN104991815A CN 104991815 A CN104991815 A CN 104991815A CN 201510347731 A CN201510347731 A CN 201510347731A CN 104991815 A CN104991815 A CN 104991815A
- Authority
- CN
- China
- Prior art keywords
- docker container
- physical machine
- create
- order
- establishment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present invention provides a Docker container management method and system. The method comprises: receiving a trigger instruction of a create button for creating at least one Docker container on a visual interface; according to a preset scheduling policy, assigning a physical machine capable of creating the Docker container and an IP address of the Docker container from physical machines and IP addresses to be scheduled; according a preconfigured script parameter rule on execution of Docker container creation, and the assigned physical machine and IP address, generating a command of executing the creation of the Docker container; and executing the command to create the Docker container on the physical machine. According to the present invention, the utilization of a visual interface to create a Docker container is more intuitive, simpler, and higher in operability, and also can provide an automated creation process with no need of manual involvement and with high efficiency.
Description
Technical field
The present invention relates to field of computer technology, particularly a kind of management method of Docker container and system.
Background technology
Docker is an application container engine of increasing income, and developer can be packed and applies and rely on bag in a transplantable container, be then published on any popular Linux machine, also can realize virtual.Container uses sandbox mechanism completely, do not have any interface each other, almost do not have performance cost, can run in machine and data center easily.
At present, when physical machine creates Docker container, need the configuration information of the multiple physical machine to be scheduled of developer's manual queries, as CPU (the Central Processing Unit of physical machine, central processing unit), internal memory, hard disk and the quantity having created Docker container in this physical machine etc., and then whether this physical machine of artificial judgment can create new Docker container, and then progressively manually set up.For the Docker container created, still need manually to go to check and manage.Visible, the way to manage of current Docker container is dumb, and not intelligent, efficiency is lower.
Summary of the invention
In view of the above problems, the present invention is proposed to provide a kind of overcoming the problems referred to above or the management method of Docker container solved the problem at least in part and system.
According to an aspect of of the present present invention, provide a kind of management method of Docker container, comprising:
Receive the triggering command for establishment button visualization interface creating at least one Docker container;
According to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container;
The script argument rule created according to pre-configured execution Docker container and the described physical machine of distributing and described IP address, generate the order performing and create Docker container; And
Perform described order, to create Docker container in described physical machine.
Alternatively, when receiving for when visualization interface creating the triggering command of establishment button of at least one Docker container, described method also comprises: at least one calling Docker container creates parameter and select for user; Obtain one or more establishment parameters that user chooses from least one establishment parameter described;
The scheduling strategy that described basis is preset, from physical machine to be scheduled and IP address, the step that distribution can create the physical machine of Docker container and the IP address of this Docker container comprises further: according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.
Alternatively, described at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
Alternatively, according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled, distribute the step that can create the physical machine of Docker container and comprise further:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of described one or more establishment parameter and described physical machine to be scheduled, from described physical machine to be scheduled, distribute the physical machine that can create Docker container.
Alternatively, described Docker container comprises multiple, generates the step performing the order creating Docker container and comprises further:
For each Docker container, generate the order performing and create this Docker container respectively.
Alternatively, the step performing described order comprises further:
Utility command executing means SaltStack performs multiple described order.
Alternatively, the step of the multiple described order of utility command executing means SaltStack execution comprises further:
Multiple described order is added the queue of SaltStack tasks carrying;
According to the order executing rule of specifying, the multiple described order of SaltStack concurrence performance or order is used to perform multiple described order.
Alternatively, described method also comprises:
Described visualization interface presents the Docker container of establishment; And
To the Docker container executivecontrol function that described visualization interface presents.
Alternatively, the step described visualization interface presenting the Docker container of establishment comprises further:
Obtain the command execution results creating Docker container in described physical machine, and be presented on described visualization interface.
Alternatively, described control operation comprise following one of at least:
Start, restart, close, delete, suspend.
According to another aspect of the present invention, additionally provide a kind of management system of Docker container, comprising:
Command reception assembly, is suitable for receiving the triggering command for establishment button visualization interface creating at least one Docker container;
Allocation component, is suitable for the scheduling strategy according to presetting, and from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container;
Formation component, is suitable for the described physical machine of script argument rule and the distribution created according to pre-configured execution Docker container and described IP address, generates the order performing and create Docker container; And
Executive module, is suitable for performing described order, to create Docker container in described physical machine.
Alternatively, described system also comprises:
Invocation component, is suitable for when receiving for when visualization interface creating the triggering command of establishment button of at least one Docker container, and at least one calling Docker container creates parameter and select for user;
Securing component, is suitable for one or more establishment parameters that acquisition user chooses from least one establishment parameter described;
Described allocation component, is also suitable for according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container.
Alternatively, described at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
Alternatively, described allocation component is also suitable for:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of described one or more establishment parameter and described physical machine to be scheduled, from described physical machine to be scheduled, distribute the physical machine that can create Docker container.
Alternatively, described formation component is also suitable for:
When described Docker container comprises multiple, for each Docker container, generate the order performing and create this Docker container respectively.
Alternatively, described executive module is also suitable for:
Utility command executing means SaltStack performs multiple described order.
Alternatively, described executive module is also suitable for:
Multiple described order is added the queue of SaltStack tasks carrying;
According to the order executing rule of specifying, the multiple described order of SaltStack concurrence performance or order is used to perform multiple described order.
Alternatively, described system also comprises:
Present assembly, be suitable for the Docker container presenting establishment on described visualization interface; And
Control Component, is suitable for the Docker container executivecontrol function to described visualization interface presents.
Alternatively, present assembly described in be also suitable for:
Obtain the command execution results creating Docker container in described physical machine, and be presented on described visualization interface.
Alternatively, described control operation comprise following one of at least:
Start, restart, close, delete, suspend.
In embodiments of the present invention, receive the triggering command for establishment button visualization interface creating at least one Docker container, according to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.And then the script argument rule created according to pre-configured execution Docker container and the physical machine of distributing and IP address, generate the order performing and create Docker container.Finally, perform this order, to create Docker container in the physical machine of distributing.As can be seen here, the present invention utilizes visualization interface to create Docker container, and more intuitively, easy, operability is high.In the process creating Docker container, according to the scheduling strategy preset, robotization distributes the physical machine and the IP address of this Docker container that create Docker container, and generate the order performing and create Docker container, without the need to inquiring about the configuration information of multiple physical machine to be scheduled manually, also without the need to artificial judgment condition, more progressively manual creation, improve the efficiency of establishment.
Above-mentioned explanation is only the general introduction of technical solution of the present invention, in order to technological means of the present invention can be better understood, and can be implemented according to the content of instructions, and can become apparent, below especially exemplified by the specific embodiment of the present invention to allow above and other objects of the present invention, feature and advantage.
According to hereafter by reference to the accompanying drawings to the detailed description of the specific embodiment of the invention, those skilled in the art will understand above-mentioned and other objects, advantage and feature of the present invention more.
Accompanying drawing explanation
By reading hereafter detailed description of the preferred embodiment, various other advantage and benefit will become cheer and bright for those of ordinary skill in the art.Accompanying drawing only for illustrating the object of preferred implementation, and does not think limitation of the present invention.And in whole accompanying drawing, represent identical parts by identical reference symbol.In the accompanying drawings:
Fig. 1 shows the schematic flow sheet of the management method of Docker container according to an embodiment of the invention;
Fig. 2 shows the schematic flow sheet of the management method of Docker container according to another embodiment of the present invention;
Fig. 3 shows the schematic flow sheet of the management method of the Docker container according to further embodiment of this invention;
Fig. 4 shows the structural representation of the management system of Docker container according to an embodiment of the invention; And
Fig. 5 shows the structural representation of the management system of Docker container according to another embodiment of the present invention.
Embodiment
Below with reference to accompanying drawings exemplary embodiment of the present disclosure is described in more detail.Although show exemplary embodiment of the present disclosure in accompanying drawing, however should be appreciated that can realize the disclosure in a variety of manners and not should limit by the embodiment set forth here.On the contrary, provide these embodiments to be in order to more thoroughly the disclosure can be understood, and complete for the scope of the present disclosure can be conveyed to those skilled in the art.
For solving the problems of the technologies described above, embodiments provide a kind of management method of Docker container.Fig. 1 shows the schematic flow sheet of the management method of Docker container according to an embodiment of the invention.As shown in Figure 1, the method can comprise the following steps S102, step S104, step S106 and step S108.
Step S102, receives the triggering command for establishment button visualization interface creating at least one Docker container.
Step S104, according to the scheduling strategy preset, from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container.
Step S106, the script argument rule created according to pre-configured execution Docker container and the physical machine of distributing and IP address, generate the order performing and create Docker container.
Step S108, performs this order, to create Docker container in the physical machine of distributing.
In embodiments of the present invention, receive the triggering command for establishment button visualization interface creating at least one Docker container, according to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.And then the script argument rule created according to pre-configured execution Docker container and the physical machine of distributing and IP address, generate the order performing and create Docker container.Finally, perform this order, to create Docker container in the physical machine of distributing.As can be seen here, the present invention utilizes visualization interface to create Docker container, and more intuitively, easy, operability is high.In the process creating Docker container, according to the scheduling strategy preset, robotization distributes the physical machine and the IP address of this Docker container that create Docker container, and generate the order performing and create Docker container, without the need to inquiring about the configuration information of multiple physical machine to be scheduled manually, also without the need to artificial judgment condition, more progressively manual creation, improve the efficiency of establishment.
In step s 102, creating button can be the button creating single Docker container, also can be the button creating multiple Docker container.If creating button is the button creating multiple Docker container, then can realizes a key batch and create, thus when supvr or developer need to create multiple Docker container, the time of establishment can be saved, improve the efficiency created.
In an embodiment of the present invention, when creating Docker container, the current configuration information of automatic acquisition physical machine to be scheduled can be realized, as the CPU of physical machine, internal memory, hard disk and the quantity having created Docker container in this physical machine etc., manually check the configuration information of multiple physical machine to be scheduled without the need to developer.After the current configuration information getting physical machine to be scheduled, can analyze the current configuration information of physical machine to be scheduled, and then distribute the physical machine that can create Docker container.
The scheduling strategy mentioned in step S104, can formulate according to the actual demand of supvr or developer, the physical machine that such as priority allocation CPU is higher, or the physical machine that priority allocation internal memory is larger, or priority allocation load capacity preferably physical machine, etc.For example, physical machine to be scheduled has 3, is respectively physical machine A, B and C, suppose that the software and hardware configuration parameter of these 3 physical machine is all identical, physical machine A creates 30 Docker containers, physical machine B has created 20 Docker containers, physical machine C has created 10 Docker containers.When needs establishment 5 Docker containers, so can newly create this 5 Docker containers on physical machine C.It should be noted that, it is only schematic for enumerating herein, can not limit the present invention.
In an alternative embodiment of the invention, can also establishment parameter be set neatly, creates Docker container in conjunction with the establishment parameter arranged, thus meet different establishment demands.Namely, when receiving the triggering command for the establishment button of Docker container on visualization interface, at least one the establishment parameter calling Docker container is selected for user, obtain user and create from least one the one or more establishment parameters chosen parameter, and then step S104 may be embodied as according to one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.Here the establishment parameter mentioned can comprise the number etc. of operating system, CPU, internal memory, hard disk, different machine room establishment Docker container.
Further, embodiments provide a kind of according to one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled, distribution can create the possibility of the physical machine of Docker container, in this scenario, the software and hardware configuration parameter of physical machine to be scheduled can be obtained, and then according to the software and hardware configuration parameter of one or more establishment parameter and physical machine to be scheduled, from physical machine to be scheduled, distribute the physical machine that can create Docker container.For example, physical machine to be scheduled has 2, is respectively physical machine 1 and 2, the operating system of physical machine 1 is Windows, the operating system of physical machine 2 is Linux, if it is Linux that one or more establishment parameter comprises operating system, is then distributed in physical machine 2 and creates this Docker container.Certainly, it is only schematic for enumerating herein, does not limit the present invention.
When needing the Docker container created to comprise multiple, generating the order performing establishment Docker container in step S106 may be embodied as each Docker container, generate the order performing and create this Docker container respectively, that is, the order of corresponding this Docker container of execution of each Docker container.
Further, above in step S108, perform this order and may be embodied as utility command executing means SaltStack and perform multiple order.Here SaltStack is a very powerful order executing means, and it is one and is very easy to run, and distributed command can be supported to perform and complicated configuration file management, has enhanced scalability, can support that thousands of station server runs simultaneously.
In another embodiment of the present invention, when utility command executing means SaltStack performs multiple order, multiple order can be added the queue of SaltStack tasks carrying, and then according to the order executing rule of specifying, use the multiple order of SaltStack concurrence performance or order to perform multiple order, thus improve the speed created.
After establishment Docker container, the embodiment of the present invention can also carry out the bookkeepings such as control to the Docker container created.Fig. 2 shows the schematic flow sheet of the management method of Docker container according to another embodiment of the present invention.As shown in Figure 2, the method can comprise the following steps S202 and step S204.
Step S202, visualization interface presents the Docker container of establishment.
Step S204, to the Docker container executivecontrol function that visualization interface presents.
If the Docker container created is multiple, then can present the Docker container of multiple establishment on visualization interface, and then to multiple Docker containers executivecontrol function respectively that visualization interface presents.
The present invention is the pre-configured program code controlled Docker container on backstage, and be integrated on visualization interface, when receiving the triggering command to control knob on visualization interface, corresponding control operation can be realized by calling program, coding code is removed by developer during without the need to creating Docker container at every turn, thus save programming time, improve control efficiency.Further, visualization interface can be web (network) page, or other pages, the present invention is not limited thereto.
Further, on visualization interface, the Docker container of establishment is presented in step S202, embodiments provide a kind of optional scheme, in this scenario, obtain the command execution results creating Docker container in physical machine, as created successfully, create unsuccessfully, the position of the physical machine created, the configuration information of the physical machine created, state of the Docker container created etc., and be presented on this visualization interface, so that supvr or developer can obtain the relevant information creating Docker container in time, and then to the executivecontrol function of Docker container, as started, restart, close, delete, the control operations such as time-out.
The implementation procedure of the management method of Docker container of the present invention is introduced in detail below by a specific embodiment.In this embodiment, bulk management operation is carried out to Docker container, mainly comprise initial preliminary work and execution work.
In initial preliminary work, mainly need to carry out following three steps:
1, configure physical machine pond, multiple physical machine pond can be divided into according to machine room, obtained the configuration information of physical machine by order executive system salt, and timing upgrades.
2, for each physical machine pond configured prepares IP resource, and carry out hostname resolution, host name is distributed automatically according to certain rule.
3, in physical machine, be equipped with the script performing the functions such as container creates, restarts, deletes, start and stop.
In execution work, Fig. 3 shows the schematic flow sheet of the management method of the Docker container according to further embodiment of this invention.As shown in Figure 3, the method can comprise the following steps S302, step S304, step S306, step S308, step S310, step S312, step S314 and step S316.
Step S302, receives the triggering command of the establishment button for Docker container on visualization interface, and at least one the establishment parameter calling Docker container is selected for user.
Step S304, obtains user and creates from least one the one or more establishment parameters chosen parameter.
In this step, create the number etc. that parameter can comprise operating system, CPU, internal memory, hard disk, different machine room establishment Docker container.
Step S306, according to one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container.
In this step, the software and hardware configuration parameter of physical machine to be scheduled can be obtained, and then according to the software and hardware configuration parameter of one or more establishment parameter and physical machine to be scheduled, from physical machine to be scheduled, distribute the physical machine that can create Docker container.
Step S308, for each Docker container, the script argument rule created according to pre-configured execution Docker container and the physical machine of distributing and IP address, generate to perform and create the order of this Docker container.
Step S310, adds the queue of SaltStack tasks carrying by multiple order.
Step S312, according to the order executing rule of specifying, uses the multiple order of SaltStack concurrence performance, to realize creating Docker container in corresponding physical machine.
Step S314, obtains the command execution results creating Docker container in physical machine, and is presented on visualization interface.
In this step, command execution results as created successfully, creating unsuccessfully, the position of physical machine that creates, the configuration information of the physical machine of establishment, the Docker container of establishment state etc.
Step S316, to the Docker container executivecontrol function that visualization interface presents.
In this step, control operation as started, restarting, close, delete, time-out etc.
In the present embodiment, utilize visualization interface realize more directly perceived, easy to the management of Docker container, operability is high, can avoid situation about may make mistakes when supvr or developer's input command.Further, the present invention is the pre-configured program code controlled Docker container on backstage, and be integrated on visualization interface, when receiving the triggering command to control knob on visualization interface, corresponding control operation can be realized by calling program, remove coding code by developer during without the need to creating Docker container at every turn, thus save programming time, improve control efficiency.
Based on same inventive concept, the embodiment of the present invention additionally provides a kind of management system of Docker container.Fig. 4 shows the structural representation of the management system of Docker container according to an embodiment of the invention.See Fig. 4, this system at least comprises: command reception assembly 410, allocation component 420, formation component 430 and executive module 440.
Now introduce the annexation between each composition of the management system of the Docker container of the embodiment of the present invention or the function of device and each several part:
Command reception assembly 410, is suitable for receiving the triggering command for establishment button visualization interface creating at least one Docker container;
Allocation component 420, and instruction receiving unit 410 couples mutually, is suitable for the scheduling strategy according to presetting, and from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container;
Formation component 430, couples mutually with allocation component 420, is suitable for physical machine and the IP address of script argument rule and the distribution created according to pre-configured execution Docker container, generates the order performing and create Docker container; And
Executive module 440, couples mutually with formation component 430, is suitable for performing described order, to create Docker container in described physical machine.
In an embodiment of the present invention, as shown in Figure 5, the system that Fig. 4 shows above can also comprise:
Invocation component 450, is suitable for when receiving the triggering command for the establishment button of Docker container on visualization interface, and at least one the establishment parameter calling Docker container is selected for user;
Securing component 460, couples mutually with invocation component 450 and allocation component 420, is suitable for obtaining user and creates from least one the one or more establishment parameters chosen parameter;
Above-mentioned allocation component 420, is also suitable for according to one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container.
In an embodiment of the present invention, at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
In an embodiment of the present invention, above-mentioned allocation component 420 is also suitable for:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of one or more establishment parameter and physical machine to be scheduled, from physical machine to be scheduled, distribute the physical machine that can create Docker container.
In an embodiment of the present invention, above-mentioned formation component 430 is also suitable for:
When Docker container comprises multiple, for each Docker container, generate the order performing and create this Docker container respectively.
In an embodiment of the present invention, above-mentioned executive module 440 is also suitable for:
Utility command executive system salt instrument performs multiple order.
In an embodiment of the present invention, above-mentioned executive module 440 is also suitable for:
Multiple order is added the queue of salt tasks carrying;
According to the order executing rule of specifying, the salt multiple order of instrument concurrence performance or order is used to perform multiple order.
In an embodiment of the present invention, as shown in Figure 5, this system can also comprise:
Present assembly 470, couple mutually with executive module 440, be suitable for the Docker container presenting establishment on described visualization interface; And
Control Component 480, and presents assembly 470 and couples mutually, is suitable for the Docker container executivecontrol function to described visualization interface presents.
In an embodiment of the present invention, the above-mentioned assembly 470 that presents also is suitable for:
Obtain the command execution results creating Docker container in physical machine, and be presented on visualization interface.
In an embodiment of the present invention, control operation comprise following one of at least:
Start, restart, close, delete, suspend.
According to the combination of any one preferred embodiment above-mentioned or multiple preferred embodiment, the embodiment of the present invention can reach following beneficial effect:
In embodiments of the present invention, receive the triggering command for establishment button visualization interface creating at least one Docker container, according to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.And then the script argument rule created according to pre-configured execution Docker container and the physical machine of distributing and IP address, generate the order performing and create Docker container.Finally, perform this order, to create Docker container in the physical machine of distributing.As can be seen here, the present invention utilizes visualization interface to create Docker container, and more intuitively, easy, operability is high.In the process creating Docker container, according to the scheduling strategy preset, robotization distributes the physical machine and the IP address of this Docker container that create Docker container, and generate the order performing and create Docker container, without the need to inquiring about the configuration information of multiple physical machine to be scheduled manually, also without the need to artificial judgment condition, more progressively manual creation, improve the efficiency of establishment.
Further, the present invention is the pre-configured program code controlled Docker container on backstage, and be integrated on visualization interface, when receiving the triggering command to control knob on visualization interface, corresponding control operation can be realized by calling program, remove coding code by developer during without the need to creating Docker container at every turn, thus save programming time, improve control efficiency.
In instructions provided herein, describe a large amount of detail.But can understand, embodiments of the invention can be put into practice when not having these details.In some instances, be not shown specifically known method, structure and technology, so that not fuzzy understanding of this description.
Similarly, be to be understood that, in order to simplify the disclosure and to help to understand in each inventive aspect one or more, in the description above to exemplary embodiment of the present invention, each feature of the present invention is grouped together in single embodiment, figure or the description to it sometimes.But, the method for the disclosure should be construed to the following intention of reflection: namely the present invention for required protection requires feature more more than the feature clearly recorded in each claim.Or rather, as claims below reflect, all features of disclosed single embodiment before inventive aspect is to be less than.Therefore, the claims following embodiment are incorporated to this embodiment thus clearly, and wherein each claim itself is as independent embodiment of the present invention.
Those skilled in the art are appreciated that and adaptively can change the module in the equipment in embodiment and they are arranged in one or more equipment different from this embodiment.Module in embodiment or unit or assembly can be combined into a module or unit or assembly, and multiple submodule or subelement or sub-component can be put them in addition.Except at least some in such feature and/or process or unit be mutually repel except, any combination can be adopted to combine all processes of all features disclosed in this instructions (comprising adjoint claim, summary and accompanying drawing) and so disclosed any method or equipment or unit.Unless expressly stated otherwise, each feature disclosed in this instructions (comprising adjoint claim, summary and accompanying drawing) can by providing identical, alternative features that is equivalent or similar object replaces.
In addition, those skilled in the art can understand, although embodiments more described herein to comprise in other embodiment some included feature instead of further feature, the combination of the feature of different embodiment means and to be within scope of the present invention and to form different embodiments.Such as, in detail in the claims, the one of any of embodiment required for protection can use with arbitrary array mode.
All parts embodiment of the present invention with hardware implementing, or can realize with the software module run on one or more processor, or realizes with their combination.It will be understood by those of skill in the art that the some or all functions that microprocessor or digital signal processor (DSP) can be used in practice to realize according to the some or all parts in the management system of the Docker container of the embodiment of the present invention.The present invention can also be embodied as part or all equipment for performing method as described herein or device program (such as, computer program and computer program).Realizing program of the present invention and can store on a computer-readable medium like this, or the form of one or more signal can be had.Such signal can be downloaded from internet website and obtain, or provides on carrier signal, or provides with any other form.
The present invention will be described instead of limit the invention to it should be noted above-described embodiment, and those skilled in the art can design alternative embodiment when not departing from the scope of claims.In the claims, any reference symbol between bracket should be configured to limitations on claims.Word " comprises " not to be got rid of existence and does not arrange element in the claims or step.Word "a" or "an" before being positioned at element is not got rid of and be there is multiple such element.The present invention can by means of including the hardware of some different elements and realizing by means of the computing machine of suitably programming.In the unit claim listing some devices, several in these devices can be carry out imbody by same hardware branch.Word first, second and third-class use do not represent any order.Can be title by these word explanations.
So far, those skilled in the art will recognize that, although multiple exemplary embodiment of the present invention is illustrate and described herein detailed, but, without departing from the spirit and scope of the present invention, still can directly determine or derive other modification many or amendment of meeting the principle of the invention according to content disclosed by the invention.Therefore, scope of the present invention should be understood and regard as and cover all these other modification or amendments.
The embodiment of the invention also discloses:
The management method of A1, a kind of Docker container, comprising:
Receive the triggering command for establishment button visualization interface creating at least one Docker container;
According to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container;
The script argument rule created according to pre-configured execution Docker container and the described physical machine of distributing and described IP address, generate the order performing and create Docker container; And
Perform described order, to create Docker container in described physical machine.
A2, method according to A1, wherein,
When receiving for when visualization interface creating the triggering command of establishment button of at least one Docker container, described method also comprises: at least one calling Docker container creates parameter and select for user; Obtain one or more establishment parameters that user chooses from least one establishment parameter described;
The scheduling strategy that described basis is preset, from physical machine to be scheduled and IP address, the step that distribution can create the physical machine of Docker container and the IP address of this Docker container comprises further: according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.
A3, method according to A2, wherein, described at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
A4, method according to A3, wherein, according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled, distribute the step that can create the physical machine of Docker container and comprise further:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of described one or more establishment parameter and described physical machine to be scheduled, from described physical machine to be scheduled, distribute the physical machine that can create Docker container.
A5, method according to any one of A1-A4, wherein, described Docker container comprises multiple, generates the step performing the order creating Docker container and comprises further:
For each Docker container, generate the order performing and create this Docker container respectively.
A6, method according to A5, wherein, the step performing described order comprises further:
Utility command executing means SaltStack performs multiple described order.
A7, method according to A6, wherein, the step that utility command executing means SaltStack performs multiple described order comprises further:
Multiple described order is added the queue of SaltStack tasks carrying;
According to the order executing rule of specifying, the multiple described order of SaltStack concurrence performance or order is used to perform multiple described order.
A8, method according to any one of A1-A7, wherein, also comprise:
Described visualization interface presents the Docker container of establishment; And
To the Docker container executivecontrol function that described visualization interface presents.
A9, method according to A8, wherein, the step that described visualization interface presents the Docker container of establishment comprises further:
Obtain the command execution results creating Docker container in described physical machine, and be presented on described visualization interface.
A10, method according to A8 or A9, wherein, described control operation comprise following one of at least:
Start, restart, close, delete, suspend.
The management system of B11, a kind of Docker container, comprising:
Command reception assembly, is suitable for receiving the triggering command for establishment button visualization interface creating at least one Docker container;
Allocation component, is suitable for the scheduling strategy according to presetting, and from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container;
Formation component, is suitable for the described physical machine of script argument rule and the distribution created according to pre-configured execution Docker container and described IP address, generates the order performing and create Docker container; And
Executive module, is suitable for performing described order, to create Docker container in described physical machine.
B12, system according to B11, wherein, also comprise:
Invocation component, is suitable for when receiving for when visualization interface creating the triggering command of establishment button of at least one Docker container, and at least one calling Docker container creates parameter and select for user;
Securing component, is suitable for one or more establishment parameters that acquisition user chooses from least one establishment parameter described;
Described allocation component, is also suitable for according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container.
B13, system according to B12, wherein, described at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
B14, system according to B13, wherein, described allocation component is also suitable for:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of described one or more establishment parameter and described physical machine to be scheduled, from described physical machine to be scheduled, distribute the physical machine that can create Docker container.
B15, system according to any one of B11-B14, wherein, described formation component is also suitable for:
When described Docker container comprises multiple, for each Docker container, generate the order performing and create this Docker container respectively.
B16, system according to B15, wherein, described executive module is also suitable for:
Utility command executing means SaltStack performs multiple described order.
B17, system according to B16, wherein, described executive module is also suitable for:
Multiple described order is added the queue of SaltStack tasks carrying;
According to the order executing rule of specifying, the multiple described order of SaltStack concurrence performance or order is used to perform multiple described order.
B18, system according to any one of B11-B17, wherein, also comprise:
Present assembly, be suitable for the Docker container presenting establishment on described visualization interface; And
Control Component, is suitable for the Docker container executivecontrol function to described visualization interface presents.
B19, system according to B18, wherein, described in present assembly and be also suitable for:
Obtain the command execution results creating Docker container in described physical machine, and be presented on described visualization interface.
B20, system according to B18 or B19, wherein, described control operation comprise following one of at least:
Start, restart, close, delete, suspend.
Claims (10)
1. a management method for Docker container, comprising:
Receive the triggering command for establishment button visualization interface creating at least one Docker container;
According to the scheduling strategy preset, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container;
The script argument rule created according to pre-configured execution Docker container and the described physical machine of distributing and described IP address, generate the order performing and create Docker container; And
Perform described order, to create Docker container in described physical machine.
2. method according to claim 1, wherein,
When receiving for when visualization interface creating the triggering command of establishment button of at least one Docker container, described method also comprises: at least one calling Docker container creates parameter and select for user; Obtain one or more establishment parameters that user chooses from least one establishment parameter described;
The scheduling strategy that described basis is preset, from physical machine to be scheduled and IP address, the step that distribution can create the physical machine of Docker container and the IP address of this Docker container comprises further: according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled and IP address, distribute and can create the physical machine of Docker container and the IP address of this Docker container.
3. method according to claim 2, wherein, described at least one create parameter comprise following one of at least:
Operating system, CPU, internal memory, hard disk, different machine room create the number of Docker container.
4. method according to claim 3, wherein, according to described one or more establishment parameter and default scheduling strategy, from physical machine to be scheduled, distribute the step that can create the physical machine of Docker container and comprise further:
Obtain the software and hardware configuration parameter of physical machine to be scheduled;
According to the software and hardware configuration parameter of described one or more establishment parameter and described physical machine to be scheduled, from described physical machine to be scheduled, distribute the physical machine that can create Docker container.
5. the method according to any one of claim 1-4, wherein, described Docker container comprises multiple, generates the step performing the order creating Docker container and comprises further:
For each Docker container, generate the order performing and create this Docker container respectively.
6. method according to claim 5, wherein, the step performing described order comprises further:
Utility command executing means SaltStack performs multiple described order.
7. method according to claim 6, wherein, the step that utility command executing means SaltStack performs multiple described order comprises further:
Multiple described order is added the queue of SaltStack tasks carrying;
According to the order executing rule of specifying, the multiple described order of SaltStack concurrence performance or order is used to perform multiple described order.
8. the method according to any one of claim 1-7, wherein, also comprises:
Described visualization interface presents the Docker container of establishment; And
To the Docker container executivecontrol function that described visualization interface presents.
9. method according to claim 8, wherein, the step that described visualization interface presents the Docker container of establishment comprises further:
Obtain the command execution results creating Docker container in described physical machine, and be presented on described visualization interface.
10. a management system for Docker container, comprising:
Command reception assembly, is suitable for receiving the triggering command for establishment button visualization interface creating at least one Docker container;
Allocation component, is suitable for the scheduling strategy according to presetting, and from physical machine to be scheduled and IP address, distributes and can create the physical machine of Docker container and the IP address of this Docker container;
Formation component, is suitable for the described physical machine of script argument rule and the distribution created according to pre-configured execution Docker container and described IP address, generates the order performing and create Docker container; And
Executive module, is suitable for performing described order, to create Docker container in described physical machine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510347731.8A CN104991815B (en) | 2015-06-19 | 2015-06-19 | The management method and system of Docker container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510347731.8A CN104991815B (en) | 2015-06-19 | 2015-06-19 | The management method and system of Docker container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104991815A true CN104991815A (en) | 2015-10-21 |
| CN104991815B CN104991815B (en) | 2019-01-18 |
Family
ID=54303631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510347731.8A Active CN104991815B (en) | 2015-06-19 | 2015-06-19 | The management method and system of Docker container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104991815B (en) |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105763670A (en) * | 2016-04-08 | 2016-07-13 | 北京搜狐新媒体信息技术有限公司 | Method and device for allocating IP address to container |
| CN105824688A (en) * | 2016-03-16 | 2016-08-03 | 合网络技术（北京）有限公司 | Method for solving start concurrence bottleneck of docker container |
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN106067858A (en) * | 2016-05-24 | 2016-11-02 | 中国联合网络通信集团有限公司 | Communication means between container, Apparatus and system |
| CN106095533A (en) * | 2016-06-14 | 2016-11-09 | 中国联合网络通信集团有限公司 | Method of server expansion and device |
| CN106161104A (en) * | 2016-08-22 | 2016-11-23 | 浪潮电子信息产业股份有限公司 | A kind of based on Docker event automatic configuration Docker container with the method for mainframe network IP |
| CN106210162A (en) * | 2016-06-29 | 2016-12-07 | 中国联合网络通信集团有限公司 | Communication control method and device |
| CN106302448A (en) * | 2016-08-15 | 2017-01-04 | 中国联合网络通信集团有限公司 | remote access control method and device |
| CN106302771A (en) * | 2016-08-23 | 2017-01-04 | 浪潮电子信息产业股份有限公司 | A kind of method for configuring domain name of the application created based on Docker container |
| CN106445585A (en) * | 2016-08-30 | 2017-02-22 | 中国民生银行股份有限公司 | Application deployment method and system based on container technology |
| CN106656980A (en) * | 2016-10-21 | 2017-05-10 | 郑州云海信息技术有限公司 | Method for automatically configuring accessing control of Docker container |
| CN106970822A (en) * | 2017-02-20 | 2017-07-21 | 阿里巴巴集团控股有限公司 | A kind of container creation method and device |
| CN107196982A (en) * | 2016-03-14 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind for the treatment of method and apparatus of user's request |
| CN107203394A (en) * | 2017-04-18 | 2017-09-26 | 中国科学院计算技术研究所 | A kind of high safety docker container batch dispositions methods and device |
| CN107229507A (en) * | 2017-05-31 | 2017-10-03 | 郑州云海信息技术有限公司 | A kind of container mirror image construction method and device |
| CN107515783A (en) * | 2016-06-16 | 2017-12-26 | 阿里巴巴集团控股有限公司 | Application container management-control method and device based on application container cluster tool |
| CN107885461A (en) * | 2017-10-19 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Method and apparatus are locally stored in a kind of data |
| CN107896230A (en) * | 2017-12-26 | 2018-04-10 | 车智互联（北京）科技有限公司 | A kind of system for supporting high concurrent order to perform passage |
| CN108874505A (en) * | 2018-06-07 | 2018-11-23 | 上海熙菱信息技术有限公司 | A kind of Docker container technique packaging method |
| WO2019153829A1 (en) * | 2018-02-12 | 2019-08-15 | 人和未来生物科技（长沙）有限公司 | Method and system for rapid generation of container dockerfile and container mirror image |
| CN110134494A (en) * | 2019-05-17 | 2019-08-16 | 四川长虹电器股份有限公司 | A kind of container automatic management method based on Docker container |
| CN111026499A (en) * | 2019-11-13 | 2020-04-17 | 广州文远知行科技有限公司 | Container processing method, device, computer equipment and storage medium |
| CN111399974A (en) * | 2019-03-26 | 2020-07-10 | 深圳市鸿合创新信息技术有限责任公司 | Resource management method and device and electronic equipment |
| WO2020181598A1 (en) * | 2019-03-08 | 2020-09-17 | 厦门网宿有限公司 | Method for processing nginx network isolation spaces in batches and nginx server |
| US11023266B2 (en) | 2017-05-16 | 2021-06-01 | International Business Machines Corporation | Detecting and counteracting a multiprocessor effect in a virtual computing environment |
| US11126457B2 (en) | 2019-03-08 | 2021-09-21 | Xiamen Wangsu Co., Ltd. | Method for batch processing nginx network isolation spaces and nginx server |
| US11269596B2 (en) | 2019-06-20 | 2022-03-08 | International Business Machines Corporation | Automated microservice creation based on user interaction |
| CN111399974B (en) * | 2019-03-26 | 2024-05-28 | 深圳市鸿合创新信息技术有限责任公司 | Resource management method and device and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103281306A (en) * | 2013-05-03 | 2013-09-04 | 四川省电力公司信息通信公司 | Virtualized infrastructure platform for cloud data centers |
| US20140282539A1 (en) * | 2013-03-15 | 2014-09-18 | Adventium Enterprises, Llc | Wrapped nested virtualization |
| CN104657215A (en) * | 2013-11-19 | 2015-05-27 | 南京鼎盟科技有限公司 | Virtualization energy-saving system in Cloud computing |
| CN104683388A (en) * | 2013-11-27 | 2015-06-03 | 宁波复博信息技术有限公司 | Cloud resource management system and management method thereof |
-
2015
- 2015-06-19 CN CN201510347731.8A patent/CN104991815B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140282539A1 (en) * | 2013-03-15 | 2014-09-18 | Adventium Enterprises, Llc | Wrapped nested virtualization |
| CN103281306A (en) * | 2013-05-03 | 2013-09-04 | 四川省电力公司信息通信公司 | Virtualized infrastructure platform for cloud data centers |
| CN104657215A (en) * | 2013-11-19 | 2015-05-27 | 南京鼎盟科技有限公司 | Virtualization energy-saving system in Cloud computing |
| CN104683388A (en) * | 2013-11-27 | 2015-06-03 | 宁波复博信息技术有限公司 | Cloud resource management system and management method thereof |
Cited By (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107196982A (en) * | 2016-03-14 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind for the treatment of method and apparatus of user's request |
| CN107196982B (en) * | 2016-03-14 | 2021-01-22 | 阿里巴巴集团控股有限公司 | User request processing method and device |
| US10902030B2 (en) | 2016-03-14 | 2021-01-26 | Alibaba Group Holding Limited | User request processing method and device |
| TWI752939B (en) * | 2016-03-14 | 2022-01-21 | 香港商阿里巴巴集團服務有限公司 | Method and device for processing user request |
| CN105824688A (en) * | 2016-03-16 | 2016-08-03 | 合网络技术（北京）有限公司 | Method for solving start concurrence bottleneck of docker container |
| CN105824688B (en) * | 2016-03-16 | 2019-05-28 | 合一网络技术(北京)有限公司 | A method of it solving docker container and starts concurrent bottleneck |
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN105897946B (en) * | 2016-04-08 | 2019-04-26 | 北京搜狐新媒体信息技术有限公司 | A kind of acquisition methods and system of access address |
| CN105763670B (en) * | 2016-04-08 | 2019-01-29 | 北京搜狐新媒体信息技术有限公司 | A kind of method and device for container allocation IP address |
| CN105763670A (en) * | 2016-04-08 | 2016-07-13 | 北京搜狐新媒体信息技术有限公司 | Method and device for allocating IP address to container |
| CN106067858A (en) * | 2016-05-24 | 2016-11-02 | 中国联合网络通信集团有限公司 | Communication means between container, Apparatus and system |
| CN106067858B (en) * | 2016-05-24 | 2019-02-15 | 中国联合网络通信集团有限公司 | Communication means, apparatus and system between container |
| CN106095533B (en) * | 2016-06-14 | 2019-06-18 | 中国联合网络通信集团有限公司 | Method of server expansion and device |
| CN106095533A (en) * | 2016-06-14 | 2016-11-09 | 中国联合网络通信集团有限公司 | Method of server expansion and device |
| CN107515783A (en) * | 2016-06-16 | 2017-12-26 | 阿里巴巴集团控股有限公司 | Application container management-control method and device based on application container cluster tool |
| CN107515783B (en) * | 2016-06-16 | 2021-01-22 | 阿里巴巴集团控股有限公司 | Application container cluster tool-based application container management and control method and device |
| CN106210162A (en) * | 2016-06-29 | 2016-12-07 | 中国联合网络通信集团有限公司 | Communication control method and device |
| CN106210162B (en) * | 2016-06-29 | 2019-03-19 | 中国联合网络通信集团有限公司 | Communication control method and device |
| CN106302448B (en) * | 2016-08-15 | 2020-03-13 | 中国联合网络通信集团有限公司 | Remote access control method and device |
| CN106302448A (en) * | 2016-08-15 | 2017-01-04 | 中国联合网络通信集团有限公司 | remote access control method and device |
| CN106161104B (en) * | 2016-08-22 | 2019-06-04 | 浪潮电子信息产业股份有限公司 | A method of based on Docker event automatic configuration Docker container with mainframe network IP |
| CN106161104A (en) * | 2016-08-22 | 2016-11-23 | 浪潮电子信息产业股份有限公司 | A kind of based on Docker event automatic configuration Docker container with the method for mainframe network IP |
| CN106302771A (en) * | 2016-08-23 | 2017-01-04 | 浪潮电子信息产业股份有限公司 | A kind of method for configuring domain name of the application created based on Docker container |
| CN106445585A (en) * | 2016-08-30 | 2017-02-22 | 中国民生银行股份有限公司 | Application deployment method and system based on container technology |
| CN106656980A (en) * | 2016-10-21 | 2017-05-10 | 郑州云海信息技术有限公司 | Method for automatically configuring accessing control of Docker container |
| CN106970822A (en) * | 2017-02-20 | 2017-07-21 | 阿里巴巴集团控股有限公司 | A kind of container creation method and device |
| CN107203394A (en) * | 2017-04-18 | 2017-09-26 | 中国科学院计算技术研究所 | A kind of high safety docker container batch dispositions methods and device |
| US11023266B2 (en) | 2017-05-16 | 2021-06-01 | International Business Machines Corporation | Detecting and counteracting a multiprocessor effect in a virtual computing environment |
| CN107229507A (en) * | 2017-05-31 | 2017-10-03 | 郑州云海信息技术有限公司 | A kind of container mirror image construction method and device |
| CN107885461B (en) * | 2017-10-19 | 2022-02-01 | 北京京东尚科信息技术有限公司 | Data local storage method and device |
| CN107885461A (en) * | 2017-10-19 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Method and apparatus are locally stored in a kind of data |
| CN107896230A (en) * | 2017-12-26 | 2018-04-10 | 车智互联（北京）科技有限公司 | A kind of system for supporting high concurrent order to perform passage |
| WO2019153829A1 (en) * | 2018-02-12 | 2019-08-15 | 人和未来生物科技（长沙）有限公司 | Method and system for rapid generation of container dockerfile and container mirror image |
| US11656893B2 (en) | 2018-02-12 | 2023-05-23 | Genetalks Bio-Tech (Changsha) Co., Ltd. | Container dockerfile and container mirror image quick generation methods and systems |
| CN108874505A (en) * | 2018-06-07 | 2018-11-23 | 上海熙菱信息技术有限公司 | A kind of Docker container technique packaging method |
| US11126457B2 (en) | 2019-03-08 | 2021-09-21 | Xiamen Wangsu Co., Ltd. | Method for batch processing nginx network isolation spaces and nginx server |
| WO2020181598A1 (en) * | 2019-03-08 | 2020-09-17 | 厦门网宿有限公司 | Method for processing nginx network isolation spaces in batches and nginx server |
| CN111399974A (en) * | 2019-03-26 | 2020-07-10 | 深圳市鸿合创新信息技术有限责任公司 | Resource management method and device and electronic equipment |
| CN111399974B (en) * | 2019-03-26 | 2024-05-28 | 深圳市鸿合创新信息技术有限责任公司 | Resource management method and device and electronic equipment |
| CN110134494A (en) * | 2019-05-17 | 2019-08-16 | 四川长虹电器股份有限公司 | A kind of container automatic management method based on Docker container |
| US11269596B2 (en) | 2019-06-20 | 2022-03-08 | International Business Machines Corporation | Automated microservice creation based on user interaction |
| CN111026499B (en) * | 2019-11-13 | 2021-09-17 | 广州文远知行科技有限公司 | Container processing method, device, computer equipment and storage medium |
| CN111026499A (en) * | 2019-11-13 | 2020-04-17 | 广州文远知行科技有限公司 | Container processing method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104991815B (en) | 2019-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104991815A (en) | Docker container management method and system | |
| US10949237B2 (en) | Operating system customization in an on-demand network code execution system | |
| US11416307B2 (en) | System and method for processing task resources | |
| US20210081233A1 (en) | Execution of auxiliary functions in an on-demand network code execution system | |
| EP3073374B1 (en) | Thread creation method, service request processing method and related device | |
| US10552133B2 (en) | Image deployment method and apparatus | |
| US8838669B2 (en) | System and method for layered application server processing | |
| CN103064742A (en) | Automatic deployment system and method of hadoop cluster | |
| CN106331135B (en) | A kind of part interface update method, system, client and server-side | |
| CN110489126B (en) | Compiling task execution method and device, storage medium and electronic device | |
| CN104750528A (en) | Management method and device for components in Android program | |
| WO2004012080A2 (en) | Method for dynamically allocating and managing resources in a computerized system having multiple consumers | |
| CN104750555A (en) | Management method and device for progresses in Android program | |
| CN109471896A (en) | Data source information dynamic altering method and device | |
| CN105204927A (en) | Application arrangement device and method for terminal equipment | |
| CN105808323A (en) | Virtual machine creation method and system | |
| CN106230977B (en) | A kind of client functionality loading method, system, client and server-side | |
| CN109960517A (en) | Production method, device, system and the storage medium of image file | |
| US11144359B1 (en) | Managing sandbox reuse in an on-demand code execution system | |
| CN111953503B (en) | NFV resource deployment arrangement method and network function virtualization orchestrator | |
| US20120174094A1 (en) | Virtual appliance deployment | |
| CN107797845B (en) | Method and apparatus for accessing containers | |
| CN109144526B (en) | Rapid deployment system and method for substation automation software | |
| US20140130045A1 (en) | Instantiating virtual appliances | |
| CN116578353A (en) | Application starting method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220729 Address after: 300450 No. 9-3-401, No. 39, Gaoxin 6th Road, Binhai Science Park, Binhai New Area, Tianjin Patentee after: 3600 Technology Group Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230713 Address after: 1765, floor 17, floor 15, building 3, No. 10 Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: Beijing Hongxiang Technical Service Co.,Ltd. Address before: 300450 No. 9-3-401, No. 39, Gaoxin 6th Road, Binhai Science Park, Binhai New Area, Tianjin Patentee before: 3600 Technology Group Co.,Ltd. |