CN105245373A - Construction and operation method of container cloud platform system - Google Patents
Construction and operation method of container cloud platform system Download PDFInfo
- Publication number
- CN105245373A CN105245373A CN201510656868.1A CN201510656868A CN105245373A CN 105245373 A CN105245373 A CN 105245373A CN 201510656868 A CN201510656868 A CN 201510656868A CN 105245373 A CN105245373 A CN 105245373A
- Authority
- CN
- China
- Prior art keywords
- application
- container
- mirror image
- running
- running example
- 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
- 238000000034 method Methods 0.000 title claims abstract description 81
- 238000010276 construction Methods 0.000 title abstract 4
- 230000008569 process Effects 0.000 claims abstract description 43
- 230000036541 health Effects 0.000 claims abstract description 20
- 238000012545 processing Methods 0.000 claims abstract description 13
- 238000004891 communication Methods 0.000 claims abstract description 4
- 230000003466 anti-cipated effect Effects 0.000 claims description 12
- 238000012423 maintenance Methods 0.000 claims description 11
- 230000009471 action Effects 0.000 claims description 9
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000012217 deletion Methods 0.000 claims description 7
- 230000037430 deletion Effects 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 7
- 230000008676 import Effects 0.000 claims description 6
- 238000004364 calculation method Methods 0.000 claims description 4
- 238000004458 analytical method Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000008859 change Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 claims description 3
- 238000011017 operating method Methods 0.000 claims description 3
- 238000012546 transfer Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 230000001419 dependent effect Effects 0.000 abstract description 2
- 238000004806 packaging method and process Methods 0.000 abstract 1
- 238000005516 engineering process Methods 0.000 description 5
- 238000002955 isolation Methods 0.000 description 3
- 238000013508 migration Methods 0.000 description 3
- 230000005012 migration Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
Abstract
The invention relates to a construction and operation method of a container cloud platform system. The construction and operation method comprises the following steps: (1) the system is constructed; (2) access shunting is carried out on a control instruction and a service instruction; (3) a container cluster scheduling module forwards an access request to a specific container, and the specific container carries out service processing on the access request, returns the access request to the container cluster scheduling module, and then returns a processing result to a caller; (4) a host containerization engine module containerizes a host, records and maintains an application operated in the current platform and an application operation example list, supports and processes the control instruction, forwards instruction information, and monitors and feeds back the state of an application operation example; (5) a general controller module processes the control instruction of a container cloud platform; (6) an application health management module monitors the application condition; and (7) a message bus carries out message communication of a cloud platform device. The construction and operation method provided by the invention is used for packaging and operating dependent terms of third party applications with a container as a unit for achieving isolated operation and avoiding mutual interference, and the system resources of the host are used more fully.
Description
Technical field
The invention belongs to cloud platform technology field, building and operation method of especially a kind of container cloud plateform system.
Background technology
Cloud Pass platform is an IT resource pool based on cloud computing technology foundation and publicly-owned cloud service operation supporting platform.Third party software developer can on cloud Pass platform fast Development application deployment product provide service to end user, the application service of that End-Customer can obtain as required enriching on this platform, safety, high reliability.
Traditional cloud Pass platform adopts virtual machine to realize the isolation of different software developer application usually, and using the minimum unit of virtual machine as scheduling.Adopt virtual machine to there is a lot of problem as the minimum unit of scheduling, comprise that start-up time is long, occupying system resources is many, mirrored storage file is large, the migration adjustment of running example is consuming time.
Container technique comes management code and application program by the mode of virtualizing operating systems, it is a kind of Intel Virtualization Technology just starting in 2013 to occur and rise rapidly, container technique is is mainly designed and developed by some poly-talented innovative enterprises, such as: BlueData, CoreOS, Docker, Kismatic, PortWorx etc., wherein, Docker is one of main representative of container technique.Container technique makes it possible to more evaluation work load to be tucked on a station server, and can be that new calculation task improves increase capacity in a flash.In theory, this means to buy less hardware, self-built or lease less data center place, and employ less staff to manage these equipment.Comprise a whole user environment space exclusively enjoyed in each container, and the variation in a container can not affect the running environment of other containers.In order to this effect can be reached, container technique employs a series of system level mechanism, such as utilize Linuxnamespaces to carry out space isolation, decide container by the mount point of file system and can access which file, determine each container can utilize how many resources by cgroups.Share same system kernel between this outer container, like this when same storehouse is used by multiple container, the service efficiency of internal memory can get a promotion.
The pain spot solving traditional cloud Pass platform that develops into of linux container technology provides possibility.Present patent application is exactly a kind of container cloud stage apparatus and method that utilize container technique to realize, and this device and method is to solve the pain spot of conventional cloud Pass platform.
Summary of the invention
The object of the invention is to overcome the deficiencies in the prior art, building and operation method of a kind of container cloud plateform system is provided.
The present invention solves its technical problem and takes following technical scheme to realize:
Building and an operation method of container cloud plateform system, comprises step as follows:
(1) the building of system, this system comprises load equalizer, load equalizer and container cluster scheduler module and master controller model calling, load equalizer is the Outside Access entrance of container cloud platform, be responsible for control command and the access shunting of service order and the Authority Verification of access request, container cluster scheduler module is connected with host container engine modules, and master controller module is connected with messaging bus, messaging bus and application health control model calling;
Wherein, master controller module comprises control of authority module and management control module further;
Wherein host container engine modules comprises server end, agent side and mirror image warehouse further;
(2) the access shunting of control command and service order, concrete steps are as follows:
1. access URL is resolved, get the signing messages of access;
2. signing messages is passed to master controller module, carried out the checking of signing messages by the control of authority module of master controller module, the result returns to load equalizer;
If 3. the result is failure, then load equalizer returns failure information to caller, calls end; If the result is successfully, then load equalizer analyzes the type of access instruction, analyzes control command or service order;
4. if URL request is then transmitted to master controller by control command, the process of control command is carried out by master controller;
5. if URL request is then transmitted to container cluster scheduler module by service order, the process of service order is carried out by container cluster scheduler module;
(3) container cluster scheduler module is responsible for the reverse proxy of access, access request is forwarded to concrete container, return to container cluster scheduler module after carrying out Business Processing by concrete container, return result to caller by container cluster scheduler module;
Concrete steps are as follows:
1. set up the Dynamic Maintenance routing table of container cluster scheduler module in internal memory, structure is as follows:
Treatment step is:
A, container cluster scheduler module starts successfully, issues container cluster scheduler module start success message to messaging bus;
B, agent side subscription container colony dispatching module in host container engine modules starts success message, after receiving message, the agent side timed sending heartbeat message in host container engine modules is to messaging bus, and messaging bus comprises the specifying information of the application example that the machine is run;
C, container cluster scheduler module service end subscribes to this heartbeat message, after receiving the heartbeat message of agent side in host container engine modules, parses Apply Names, application example IP address, application example port;
D, if existed in the routing table safeguarded in container cluster scheduler module internal memory of this application example IP address, application example port, then upgrades the nearest heart time of application example;
If do not existed in the routing table that this application example IP address, application example port are safeguarded in container cluster scheduler module in internal memory, then at the newly-increased route record of routing table that container colony dispatching is safeguarded in internal memory;
2. according to URL request, container cluster scheduler module parses the Apply Names of access;
3. according to the Apply Names of access, the scheduling strategy of setting, selects suitable application example and processes from container colony dispatching module;
4. access request is given to the application example of selection;
5. application example process URL request, completes concrete calling, and will call result and return to container cluster scheduler module;
6. will call result by container cluster scheduler module and return to front end caller;
(4) host container engine modules is responsible for main frame to carry out containerization, and pool layout utilization is carried out to all containers, be responsible for record and safeguard the application and application running example inventory that run in current platform, support management control module processing controls instruction in master controller module, be responsible for receiving the command information of master controller module forwards and the state of maintenance application and application running example inventory, monitoring and feedback application running example;
Wherein, server end in host container engine modules is responsible for receiving command information that master controller forwards and the agent side being transmitted to response processes, and the control command that service end accepts comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing;
Wherein, storage and the download service of mirror image are responsible in the mirror image warehouse in host container engine modules, for server-side processes structure application mirror image, deletion application mirror image, acquisition are applied image listing instruction and provided support;
Wherein, agent side in host container engine modules runs and is deployed in various cloud main frame, VMWare virtual machine, or on the main frame of other form, utilize container technique, run at it message content that main frame forwards according to service end and create running example, delete running example, the running status of monitoring running example, simultaneously, agent side is responsible for the heartbeat of back-to-back running example, the resource status of main frame is run at feedback place, when agent side creates running example, need to obtain image file from mirror image warehouse to create mirror image, agent side is that server-side processes obtains application inventory, create application, delete application, the more example quantity of new opplication,
(5) process of the control command of master controller module load container cloud platform, comprise control of authority and management control, the signing messages checking of access control URL is responsible in control of authority, management controls the API being responsible for outwards providing REST style, the API provided comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image and obtain application image listing, and concrete steps content is as follows:
1. set up master controller module maintenance application signing messages table, structure is as follows:
| Apply Names | Signing messages |
2. control of authority is carried out:
A, receives signing messages; Signing messages comprises following features: 128 bit lengths, possess uniqueness, corresponds to unique application, possesses time response, can lose efficacy, possess verifying function to signing messages;
B, finds and whether has corresponding application signature information in application signature information table;
C, if the signing messages finding application, returns successfully; If do not find the signing messages of application, return failure;
3. carry out management to control:
A, resolves URL request parameter, the interface of analysis operation;
B, if action type obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing, is then forwarded to host container engine by URL request;
C, host container engine carries out concrete operation, and result is fed back to the management control module of master controller;
D, will call result by master controller and return to caller.
(6) apply Health management service to monitor applicable cases, if running status and the expecting state of discovery application are inconsistent, then notify that containerization engine modules processes by application health control, thus complete the adjustment of application running status, step content is as follows:
1. after applying the startup of health control module, start two threads, the heartbeat message theme that in thread 1 subscription container engine, agent side is issued, and be responsible for heartbeat message to be stored in key-value pair system, thread 2 is responsible for the expecting state of application and running status to compare, and informs containerization engine treatment state difference;
2. apply health control thread 1 monitoring information bus all the time, after receiving heartbeat message, analyze the state of Apply Names, application running example reference address, application running example, leave in key-value pair system with the form of key-value pair;
3. apply the timing of health control thread 2 and obtain the expecting state of current application and the running example of expection from containerization engine, and the actual motion state obtaining current application from key-value pair system is compared simultaneously, judge the difference with expecting state, and inform that containerization engine processes;
(7) messaging bus is responsible for the message communicating of cloud stage apparatus, each cloud platform interior module carries out connection communication by messaging bus, messaging bus provides registration and the subscription of message subject, the message subject that the producer can issue is registered on messaging bus, if consumer will use certain class message, messaging bus is subscribed to this message subject.
And the content 1. walking Dynamic Maintenance routing table in described step (3) is described as:
Apply Names is the title of the application disposed in a reservoir, a corresponding one or more application example of application, and provides concrete process by application example; Scheduling strategy is the processing policy of load dispatch, and the load strategy of this scheduling strategy support comprises poll, weighting, Hash and acquiescence, is polling schemas; The IP address that application example IP address uses when being access container application; The port that uses when application example port is access container application; Heart time nearest when application example heart time is container application.
And the concrete steps obtaining application inventory in described step (4) are as follows:
1. host container engine modules accessing database table obtains title, application state, the corresponding running example of application;
2. host container engine modules organising data returns to caller.
And the concrete steps creating application in described step (4) are as follows:
1. the server module in host container engine modules sends the message of establishment application resource request to messaging bus;
2. the agent side in host container engine modules subscribes to this message, after each agent side receives message, by calculating, obtaining the running example quantity that this main frame can create, and feeding back to server end module;
3. server module arranges time-out time, obtain the agent side inventory responded within the scope of certain hour, the running example number created of comprehensive these agent sides feedback, proportionally distribute each agent side by the instance number that request creates, the computing formula that each agent side intends creating running example number is as follows:
(the running example sum that the running example number that agent side can create/all agent sides can create) × application needs to create running example number,
Result of calculation carry rounds;
Wherein, distribute the concrete steps of the running example number that can create to agent side as follows for service end:
I, service end record is at every turn to the establishment instance number that agent side distributes;
Ii, the instance number default value at every turn created to agent side distribution is the running example number by formulae discovery agent side plan establishment out above;
Iii, if the instance number sum created adds the running example number being less than or equal to the establishment of application needs to agent side for distribution running example number summation, is then dispensing by formulae discovery agent side out above to this agent side and intends the running example number of establishment;
Iv, if the instance number sum created adds the running example number being greater than the establishment of application needs to agent side for distributing running example number summation, then the instance number created to agent side distribution equals to apply needs the application example number of establishment to deduct the instance number of distributing establishment;
4. server module sends the application running example number needing to create to the agent side of specifying;
5. agent side obtains image file and creates running example from mirror image warehouse, by messaging bus notification server end after having created, and in container colony dispatching the access path of registered application running example;
6. server end is according to information in the establishment situation amendment record tables of data of feedback, and after the running example number required for application has all created, the state of amendment application is in starting.
And the concrete steps of deleting application in described step (4) are as follows:
1. containerization engine service end analyzes the Apply Names that will delete;
2. containerization engine service end sends the message of deletion application to messaging bus;
3. containerization Enabler Proxy end subscribes to the message of deleting application, judges whether the main frame at self place has the running example of this application, if the running example of not this application, do not carry out any operation after receiving message; If there is the running example of this application, delete the running example of this application.
And the concrete steps upgrading application example quantity in described step (4) are as follows:
1. running example quantity, the alter operation type of containerization engine service end analytical applications title, change;
If 2. action type increases running example, operating procedure is consistent with the concrete steps creating application in described step (4);
If 3. action type reduces running example, concrete operations are as follows:
I, containerization engine service end obtain current running example inventory from record sheet;
Ii, containerization engine service end Stochastic choice go out the running example that will delete;
The transmission of iii, containerization engine service end will delete the message of application running example to messaging bus;
Iv, containerization Enabler Proxy end subscribe to this message, judge whether the main frame at self place has this running example after receiving message, if not this running example, do not carry out any operation; If there is this running example, delete this running example.
And the concrete steps building application mirror image in described step (4) are as follows:
1. containerization engine service termination receives the application component bag that caller imports into;
2. containerization engine downloads foundation image from mirror image warehouse, the foundation image that is added to by application component bag is built into a new application mirror image, and arranges title and the label of application mirror image;
3. application mirror image is submitted to mirror image warehouse;
4. containerization engine service end will the structure information of application mirror image, comprises the application title of mirror image and tag feedback to caller.
And, delete application mirror image in described step (4) and obtain the concrete steps applying mirror image as follows:
Delete application mirror image
1. containerization engine service termination receives title and the label of the mirror image that will delete that caller imports into;
2. the API calling mirror image warehouse completes image file and deletes;
Obtain application mirror image
1. containerization engine service end calls the API in mirror image warehouse, obtains image listing inventory;
2. containerization engine service end organizes return data, and feedback result is to caller.
And step concrete steps are 3. as follows in described step (6):
The timing of A, thread 2 obtains application actual motion state from key-value pair system, and each the running status moment got is as a snapshot;
Nearest three snapshots of B, thread 2 record application actual motion state, and three snapshots are compared, if three snapshot states are inconsistent, are judged as that current network is unstable or carrying out Failure Transfer and cause, in this case do not process; If three snapshot states are consistent, start to judge that whether application example actual motion state is consistent with expecting state, after having judged, judge that whether the example quantity applied is consistent with anticipated number.
And described step B starts to judge that the concrete steps whether actual motion state is consistent with expecting state are as follows:
1. according to the application example inventory that containerization engine provides, record and compare one by one with in key-value pair system, if both running example states of record are inconsistent, the RESTAPI completion status calling containerization engine changes;
2. only compare the application example being in operation and halted state, the application of the state of mediating do not processed,
Situation 1: the example of the record in containerization engine does not have in key-value pair system, thread 2 notifies that containerization engine newly creates an example;
Situation 2: the example recorded in containerization engine state in key-value pair system is inconsistent, thread 2 notifies containerization engine adapts example state;
Situation 3: do not have record in containerization engine, but have heartbeat in key-value pair system, thread 2 notifies that containerization engine removes this example;
And the concrete steps carrying out processing when judging in described step B that whether the example quantity of application is consistent with anticipated number are as follows:
1. obtain the desired value that the application of recording in containerization engine modules runs quantity, and the example heartbeat quantity of key-value pair system log (SYSLOG) compares;
2. only compare the application being in operation and halted state, other states do not process;
The possible situation that both compare existence comprises:
Situation 1: if the example anticipated number of containerization engine record is more than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine reduces running example;
Situation 2: if the example anticipated number of containerization engine record is less than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine increases running example.
Advantage of the present invention and good effect are:
1, the present invention utilizes container technique, and the underlying host environment of cloud Platform Dependent is carried out containerization, and the container on different main frame is carried out pool layout utilization, can utilize the system resource of main frame more fully.
2, the present invention utilizes container technique, take container as the minimum scheduling unit of application, solves conventional cloud Pass and utilizes virtual machine technique as the pain spot that brings of minimum scheduling unit of application, comprises migration adjustment that is long, running example start-up time consuming time etc.
3, the present invention utilizes container technique, provides a kind of third-party application isolation operation method on the same host.Each third-party application take container as the packing operation that unit carries out relying on item, isolates operation each other, does not interfere with each other.
4, the present invention utilizes container technique, provides the apparatus and method that a kind of third-party application trustship runs.These apparatus and method can monitor the health condition of hosts applications, and carry out fault migration and state adjustment timely, response speed is better than conventional cloud Pass platform.
Accompanying drawing explanation
Fig. 1 is first stage apparatus connection diagram of the present invention;
Fig. 2 is host container engine structure schematic diagram in the present invention.
Embodiment
Below in conjunction with accompanying drawing, the embodiment of the present invention is further described, it is emphasized that embodiment of the present invention is illustrative, instead of determinate, can not in this, as the restriction to the scope of protection of the invention.
Building and an operation method of container cloud plateform system, comprises step as follows:
(1) the building of system, as shown in Figure 1, this system comprises load equalizer, load equalizer and container cluster scheduler module and master controller model calling, load equalizer is the Outside Access entrance of container cloud platform, and be responsible for control command and the access shunting of service order and the Authority Verification of access request, container cluster scheduler module is connected with host container engine modules, master controller module is connected with messaging bus, messaging bus and application health control model calling;
Wherein, master controller module comprises control of authority module and management control module further;
Wherein, as shown in Figure 2, host container engine modules comprises server end, agent side and mirror image warehouse further.
(2) the access shunting of control command and service order, concrete steps are as follows:
1. access URL is resolved, get the signing messages of access;
2. signing messages is passed to master controller module, carried out the checking of signing messages by the control of authority module of master controller module, the result returns to load equalizer.
If 3. the result is failure, then load equalizer returns failure information to caller, calls end; If the result is successfully, then load equalizer analyzes the type of access instruction, analyzes control command or service order;
4. if URL request is then transmitted to master controller by control command, the process of control command is carried out by master controller;
5. if URL request is then transmitted to container cluster scheduler module by service order, the process of service order is carried out by container cluster scheduler module;
(3) container cluster scheduler module is responsible for the reverse proxy of access, access request is forwarded to concrete container, return to container cluster scheduler module after carrying out Business Processing by concrete container, return result to caller by container cluster scheduler module;
Wherein, the step of described step (3) is as follows:
1. the Dynamic Maintenance router-table structure of container cluster scheduler module in internal memory is as follows:
Wherein, Apply Names is the title of the application disposed in a reservoir, a corresponding one or more application example of application, and provides concrete process by application example; Scheduling strategy is the processing policy of load dispatch, and the load strategy of this scheduling strategy support comprises poll, weighting, Hash and acquiescence, is polling schemas; The IP address that application example IP address uses when being access container application; The port that uses when application example port is access container application; Heart time nearest when application example heart time is container application;
The concrete steps of process are as follows:
A, container cluster scheduler module starts successfully, issues container cluster scheduler module start success message to messaging bus;
B, agent side subscription container colony dispatching module in host container engine modules starts success message, after receiving message, the agent side timed sending heartbeat message in host container engine modules is to messaging bus, and messaging bus comprises the specifying information of the application example that the machine is run;
C, container cluster scheduler module service end subscribes to this heartbeat message, after receiving the heartbeat message of agent side in host container engine modules, parses Apply Names, application example IP address, application example port;
D, if existed in the routing table safeguarded in container cluster scheduler module internal memory of this application example IP address, application example port, then upgrades the nearest heart time of application example.
If do not existed in the routing table that this application example IP address, application example port are safeguarded in container cluster scheduler module in internal memory, then at the newly-increased route record of routing table that container colony dispatching is safeguarded in internal memory;
2. according to URL request, container cluster scheduler module parses the Apply Names of access;
3. according to the Apply Names of access, the scheduling strategy of setting, selects suitable application example and processes from container colony dispatching module;
4. access request is given to the application example of selection;
5. application example process URL request, completes concrete calling, and will call result and return to container cluster scheduler module;
6. will call result by container cluster scheduler module and return to front end caller;
(4) host container engine modules is responsible for main frame to carry out containerization, and pool layout utilization is carried out to all containers, be responsible for record and safeguard the application and application running example inventory that run in current platform, an application corresponds to one or more application running example, application is logical concept, application running example is the processing unit of application reality, the corresponding container of each application running example, support management control module processing controls instruction in master controller module, be responsible for receiving the command information of master controller module forwards and maintenance application and application running example inventory, the state of monitoring and feedback application running example,
Wherein, server end in host container engine modules is responsible for receiving command information that master controller forwards and the agent side being transmitted to response processes, and the control command that service end accepts comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing;
Wherein, storage and the download service of mirror image are responsible in the mirror image warehouse in host container engine modules, for server-side processes structure application mirror image, deletion application mirror image, acquisition are applied image listing instruction and provided support;
Wherein, agent side in host container engine modules runs and is deployed in various cloud main frame, VMWare virtual machine, or on the main frame of other form, utilize container technique, run at it message content that main frame forwards according to service end and create running example, delete running example, the running status of monitoring running example, simultaneously, agent side is responsible for the heartbeat of back-to-back running example, the resource status of main frame is run at feedback place, when agent side creates running example, need to obtain image file from mirror image warehouse to create mirror image, agent side is that server-side processes obtains application inventory, create application, delete application, more these instructions of example quantity of new opplication provide support,
Concrete, the concrete steps obtaining application inventory in described step (4) are as follows:
1. host container engine modules accessing database table obtains title, application state, the corresponding running example of application;
2. host container engine modules organising data returns to caller;
Concrete, the concrete steps creating application in described step (4) are as follows:
1. the server module in host container engine modules sends the message of establishment application resource request to messaging bus;
2. the agent side in host container engine modules subscribes to this message, after each agent side receives message, by calculating, obtaining the running example quantity that this main frame can create, and feeding back to server end module;
3. server module arranges time-out time, obtain the agent side inventory responded within the scope of certain hour, the running example number created of comprehensive these agent sides feedback, proportionally distribute each agent side by the instance number that request creates, the computing formula that each agent side intends creating running example number is as follows:
(the running example sum that the running example number that agent side can create/all agent sides can create) × application needs to create running example number, and result of calculation carry rounds;
Wherein, distribute the concrete steps of the running example number that can create to agent side as follows for service end:
I, service end record is at every turn to the establishment instance number that agent side distributes;
Ii, the instance number default value at every turn created to agent side distribution is the running example number by formulae discovery agent side plan establishment out above;
Iii, if the instance number sum created adds the running example number being less than or equal to the establishment of application needs to agent side for distribution running example number summation, is then dispensing by formulae discovery agent side out above to this agent side and intends the running example number of establishment;
Iv, if the instance number sum created adds the running example number being greater than the establishment of application needs to agent side for distributing running example number summation, then the instance number created to agent side distribution equals to apply needs the application example number of establishment to deduct the instance number of distributing establishment.
4. server module sends the application running example number needing to create to the agent side of specifying;
5. agent side obtains image file and creates running example from mirror image warehouse, by messaging bus notification server end after having created, and in container colony dispatching the access path of registered application running example;
6. server end is according to information in the establishment situation amendment record tables of data of feedback, and after the running example number required for application has all created, the state of amendment application is in starting.
Wherein, the concrete steps of deleting application in described step (4) are as follows:
1. containerization engine service end analyzes the Apply Names that will delete;
2. containerization engine service end sends the message of deletion application to messaging bus;
3. containerization Enabler Proxy end subscribes to the message of deleting application, judges whether the main frame at self place has the running example of this application, if the running example of not this application, do not carry out any operation after receiving message; If there is the running example of this application, delete the running example of this application.
Wherein, the concrete steps upgrading application example quantity in described step (4) are as follows:
1. running example quantity, the alter operation type (increase running example or reduce running example) of containerization engine service end analytical applications title, change;
If 2. action type increases running example, operating procedure is consistent with the concrete steps creating application in described step (4);
If 3. action type reduces running example, concrete operations are as follows:
I, containerization engine service end obtain current running example inventory from record sheet;
Ii, containerization engine service end Stochastic choice go out the running example that will delete;
The transmission of iii, containerization engine service end will delete the message of application running example to messaging bus;
Iv, containerization Enabler Proxy end subscribe to this message, judge whether the main frame at self place has this running example after receiving message, if not this running example, do not carry out any operation; If there is this running example, delete this running example.
Wherein, the concrete steps building application mirror image in described step (4) are as follows:
1. containerization engine service termination receives the application component bag that caller imports into;
2. containerization engine downloads foundation image from mirror image warehouse, the foundation image that is added to by application component bag is built into a new application mirror image, and arranges title and the label of application mirror image;
3. application mirror image is submitted to mirror image warehouse;
4. containerization engine service end will the structure information of application mirror image, comprises the application title of mirror image and tag feedback to caller.
Wherein, the deletion mirror image concrete steps of described step (4) are as follows:
1. containerization engine service termination receives title and the label of the mirror image that will delete that caller imports into;
2. the API calling mirror image warehouse completes image file and deletes.
Wherein, the concrete steps obtaining application mirror image in described step (4) are as follows:
1. containerization engine service end calls the API in mirror image warehouse, obtains image listing inventory;
2. containerization engine service end organizes return data, and feedback result is to caller.
(5) process of the control command of master controller module load container cloud platform, comprise control of authority and management control, the signing messages checking of access control URL is responsible in control of authority, management controls the API being responsible for outwards providing REST style, the API provided comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image and obtain application image listing, and concrete steps are as follows:
1. master controller module maintenance application signing messages table, structure is as follows:
| Apply Names | Signing messages |
2. control of authority is carried out:
A, receives signing messages; Signing messages comprises following features: 128 bit lengths, possess uniqueness, corresponds to unique application, possesses time response, can lose efficacy, possess verifying function to signing messages;
B, finds and whether has corresponding application signature information in application signature information table;
C, if the signing messages finding application, returns successfully; If do not find the signing messages of application, return failure;
3. carry out management to control:
A, resolves URL request parameter, the interface of analysis operation;
B, if action type obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing, is then forwarded to host container engine by URL request;
C, host container engine carries out concrete operation, and result is fed back to the management control module of master controller;
D, will call result by master controller and return to caller.
(6) apply Health management service to monitor applicable cases, if running status and the expecting state of discovery application are inconsistent, then notify that containerization engine modules processes by application health control, thus complete the adjustment of application running status, step is as follows:
1. after applying the startup of health control module, start two threads, the heartbeat message theme that in thread 1 subscription container engine, agent side is issued, and be responsible for heartbeat message to be stored in key-value pair system, thread 2 is responsible for the expecting state of application and running status to compare, and informs containerization engine treatment state difference;
2. apply health control thread 1 monitoring information bus all the time, after receiving heartbeat message, analyze the state of Apply Names, application running example reference address, application running example, leave in key-value pair system with the form of key-value pair;
3. apply the timing of health control thread 2 and obtain the expecting state of current application and the running example of expection from containerization engine, and the actual motion state obtaining current application from key-value pair system is compared simultaneously, judge the difference with expecting state, and inform that containerization engine processes;
Wherein, described step concrete steps are 3. as follows:
The timing of A, thread 2 obtains application actual motion state from key-value pair system, and each the running status moment got is as a snapshot;
Nearest three snapshots of B, thread 2 record application actual motion state, and three snapshots are compared, if three snapshot states are inconsistent, are judged as that current network is unstable or carrying out Failure Transfer and cause, in this case do not process; If three snapshot states are consistent, start to judge that whether application example actual motion state is consistent with expecting state, after having judged, judge that whether the example quantity applied is consistent with anticipated number.
Wherein, check in described step B that the concrete steps whether running example actual motion state is consistent with expecting state are as follows:
The application example inventory that i provides according to containerization engine, records and compares one by one with in key-value pair system, if both running example states of record are inconsistent, the RESTAPI completion status calling containerization engine changes
Ii only compares the application example being in operation and halted state, does not process the application of the state of mediating
Situation 1: the example of the record in containerization engine does not have in key-value pair system, thread 2 notifies that containerization engine newly creates an example
Situation 2: the example recorded in containerization engine state in key-value pair system is inconsistent, thread 2 notifies containerization engine adapts example state
Situation 3: do not have record in containerization engine, but have heartbeat in key-value pair system, thread 2 notifies that containerization engine removes this example
And, judge in described step B that the concrete steps whether the example quantity of application is consistent with anticipated number are as follows:
I obtains the desired value that the application of recording in containerization engine modules runs quantity, and the example heartbeat quantity of key-value pair system log (SYSLOG) compares;
Ii only compares the application being in operation and halted state, and other states do not process.
The possible situation that both compare existence comprises:
Situation 1: if the example anticipated number of containerization engine record is more than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine reduces running example;
Situation 2: if the example anticipated number of containerization engine record is less than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine increases running example;
(7) messaging bus is responsible for the message communicating of cloud stage apparatus, each cloud platform interior module carries out connection communication by messaging bus, messaging bus provides registration and the subscription of message subject, the message subject that the producer can issue is registered on messaging bus, if consumer will use certain class message, messaging bus is subscribed to this message subject.
Claims (10)
1. the building and an operation method of container cloud plateform system, is characterized in that: comprise step as follows:
(1) the building of system, this system comprises load equalizer, load equalizer and container cluster scheduler module and master controller model calling, load equalizer is the Outside Access entrance of container cloud platform, be responsible for control command and the access shunting of service order and the Authority Verification of access request, container cluster scheduler module is connected with host container engine modules, and master controller module is connected with messaging bus, messaging bus and application health control model calling;
Wherein, master controller module comprises control of authority module and management control module further;
Wherein host container engine modules comprises server end, agent side and mirror image warehouse further;
(2) the access shunting of control command and service order, concrete steps are as follows:
1. access URL is resolved, get the signing messages of access;
2. signing messages is passed to master controller module, carried out the checking of signing messages by the control of authority module of master controller module, the result returns to load equalizer;
If 3. the result is failure, then load equalizer returns failure information to caller, calls end; If the result is successfully, then load equalizer analyzes the type of access instruction, analyzes control command or service order;
4. if URL request is then transmitted to master controller by control command, the process of control command is carried out by master controller;
5. if URL request is then transmitted to container cluster scheduler module by service order, the process of service order is carried out by container cluster scheduler module;
(3) container cluster scheduler module is responsible for the reverse proxy of access, access request is forwarded to concrete container, return to container cluster scheduler module after carrying out Business Processing by concrete container, return result to caller by container cluster scheduler module;
Concrete steps are as follows:
1. set up the Dynamic Maintenance routing table of container cluster scheduler module in internal memory, structure is as follows:
Treatment step is:
A, container cluster scheduler module starts successfully, issues container cluster scheduler module start success message to messaging bus;
B, agent side subscription container colony dispatching module in host container engine modules starts success message, after receiving message, the agent side timed sending heartbeat message in host container engine modules is to messaging bus, and messaging bus comprises the specifying information of the application example that the machine is run;
C, container cluster scheduler module service end subscribes to this heartbeat message, after receiving the heartbeat message of agent side in host container engine modules, parses Apply Names, application example IP address, application example port;
D, if existed in the routing table safeguarded in container cluster scheduler module internal memory of this application example IP address, application example port, then upgrades the nearest heart time of application example;
If do not existed in the routing table that this application example IP address, application example port are safeguarded in container cluster scheduler module in internal memory, then at the newly-increased route record of routing table that container colony dispatching is safeguarded in internal memory;
2. according to URL request, container cluster scheduler module parses the Apply Names of access;
3. according to the Apply Names of access, the scheduling strategy of setting, selects suitable application example and processes from container colony dispatching module;
4. access request is given to the application example of selection;
5. application example process URL request, completes concrete calling, and will call result and return to container cluster scheduler module;
6. will call result by container cluster scheduler module and return to front end caller;
(4) host container engine modules is responsible for main frame to carry out containerization, and pool layout utilization is carried out to all containers, be responsible for record and safeguard the application and application running example inventory that run in current platform, support management control module processing controls instruction in master controller module, be responsible for receiving the command information of master controller module forwards and the state of maintenance application and application running example inventory, monitoring and feedback application running example;
Wherein, server end in host container engine modules is responsible for receiving command information that master controller forwards and the agent side being transmitted to response processes, and the control command that service end accepts comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing;
Wherein, storage and the download service of mirror image are responsible in the mirror image warehouse in host container engine modules, for server-side processes structure application mirror image, deletion application mirror image, acquisition are applied image listing instruction and provided support;
Wherein, agent side in host container engine modules runs and is deployed in various cloud main frame, VMWare virtual machine, or on the main frame of other form, utilize container technique, run at it message content that main frame forwards according to service end and create running example, delete running example, the running status of monitoring running example, simultaneously, agent side is responsible for the heartbeat of back-to-back running example, the resource status of main frame is run at feedback place, when agent side creates running example, need to obtain image file from mirror image warehouse to create mirror image, agent side is that server-side processes obtains application inventory, create application, delete application, the more example quantity of new opplication,
(5) process of the control command of master controller module load container cloud platform, comprise control of authority and management control, the signing messages checking of access control URL is responsible in control of authority, management controls the API being responsible for outwards providing REST style, the API provided comprises and obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image and obtain application image listing, and concrete steps content is as follows:
1. set up master controller module maintenance application signing messages table, structure is as follows:
2. control of authority is carried out:
A, receives signing messages; Signing messages comprises following features: 128 bit lengths, possess uniqueness, corresponds to unique application, possesses time response, can lose efficacy, possess verifying function to signing messages;
B, finds and whether has corresponding application signature information in application signature information table;
C, if the signing messages finding application, returns successfully; If do not find the signing messages of application, return failure;
3. carry out management to control:
A, resolves URL request parameter, the interface of analysis operation;
B, if action type obtains application inventory, creates application, deletes application, upgrades application example quantity, builds application mirror image, deletes application mirror image, obtains application image listing, is then forwarded to host container engine by URL request;
C, host container engine carries out concrete operation, and result is fed back to the management control module of master controller;
D, will call result by master controller and return to caller.
(6) apply Health management service to monitor applicable cases, if find the running status of application and expecting state inconsistent, then notify that containerization engine modules processes by application health control, thus complete the adjustment of application running status,
Step content is as follows:
1. after applying the startup of health control module, start two threads, the heartbeat message theme that in thread 1 subscription container engine, agent side is issued, and be responsible for heartbeat message to be stored in key-value pair system, thread 2 is responsible for the expecting state of application and running status to compare, and informs containerization engine treatment state difference;
2. apply health control thread 1 monitoring information bus all the time, after receiving heartbeat message, analyze the state of Apply Names, application running example reference address, application running example, leave in key-value pair system with the form of key-value pair;
3. apply the timing of health control thread 2 and obtain the expecting state of current application and the running example of expection from containerization engine, and the actual motion state obtaining current application from key-value pair system is compared simultaneously, judge the difference with expecting state, and inform that containerization engine processes;
(7) messaging bus is responsible for the message communicating of cloud stage apparatus, each cloud platform interior module carries out connection communication by messaging bus, messaging bus provides registration and the subscription of message subject, the message subject that the producer can issue is registered on messaging bus, if consumer will use certain class message, messaging bus is subscribed to this message subject.
2. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: the content 1. walking Dynamic Maintenance routing table in described step (3) is described as:
Apply Names is the title of the application disposed in a reservoir, a corresponding one or more application example of application, and provides concrete process by application example; Scheduling strategy is the processing policy of load dispatch, and the load strategy of this scheduling strategy support comprises poll, weighting, Hash and acquiescence, is polling schemas; The IP address that application example IP address uses when being access container application; The port that uses when application example port is access container application; Heart time nearest when application example heart time is container application.
3. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: the concrete steps obtaining application inventory in described step (4) are as follows:
1. host container engine modules accessing database table obtains title, application state, the corresponding running example of application;
2. host container engine modules organising data returns to caller.
4. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: the concrete steps creating application in described step (4) are as follows:
1. the server module in host container engine modules sends the message of establishment application resource request to messaging bus;
2. the agent side in host container engine modules subscribes to this message, after each agent side receives message, by calculating, obtaining the running example quantity that this main frame can create, and feeding back to server end module;
3. server module arranges time-out time, obtain the agent side inventory responded within the scope of certain hour, the running example number created of comprehensive these agent sides feedback, proportionally distribute each agent side by the instance number that request creates, the computing formula that each agent side intends creating running example number is as follows:
(the running example sum that the running example number that agent side can create/all agent sides can create) × application needs to create running example number,
Result of calculation carry rounds;
Wherein, distribute the concrete steps of the running example number that can create to agent side as follows for service end:
I, service end record is at every turn to the establishment instance number that agent side distributes;
Ii, the instance number default value at every turn created to agent side distribution is the running example number by formulae discovery agent side plan establishment out above;
Iii, if the instance number sum created adds the running example number being less than or equal to the establishment of application needs to agent side for distribution running example number summation, is then dispensing by formulae discovery agent side out above to this agent side and intends the running example number of establishment;
Iv, if the instance number sum created adds the running example number being greater than the establishment of application needs to agent side for distributing running example number summation, then the instance number created to agent side distribution equals to apply needs the application example number of establishment to deduct the instance number of distributing establishment;
4. server module sends the application running example number needing to create to the agent side of specifying;
5. agent side obtains image file and creates running example from mirror image warehouse, by messaging bus notification server end after having created, and in container colony dispatching the access path of registered application running example;
6. server end is according to information in the establishment situation amendment record tables of data of feedback, and after the running example number required for application has all created, the state of amendment application is in starting.
5. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: the concrete steps of deleting application in described step (4) are as follows:
1. containerization engine service end analyzes the Apply Names that will delete;
2. containerization engine service end sends the message of deletion application to messaging bus;
3. containerization Enabler Proxy end subscribes to the message of deleting application, judges whether the main frame at self place has the running example of this application, if the running example of not this application, do not carry out any operation after receiving message; If there is the running example of this application, delete the running example of this application;
And the concrete steps upgrading application example quantity in described step (4) are as follows:
1. running example quantity, the alter operation type of containerization engine service end analytical applications title, change;
If 2. action type increases running example, operating procedure is consistent with the concrete steps creating application in described step (4);
If 3. action type reduces running example, concrete operations are as follows:
I, containerization engine service end obtain current running example inventory from record sheet;
Ii, containerization engine service end Stochastic choice go out the running example that will delete;
The transmission of iii, containerization engine service end will delete the message of application running example to messaging bus;
Iv, containerization Enabler Proxy end subscribe to this message, judge whether the main frame at self place has this running example after receiving message, if not this running example, do not carry out any operation; If there is this running example, delete this running example.
6. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: the concrete steps building application mirror image in described step (4) are as follows:
1. containerization engine service termination receives the application component bag that caller imports into;
2. containerization engine downloads foundation image from mirror image warehouse, the foundation image that is added to by application component bag is built into a new application mirror image, and arranges title and the label of application mirror image;
3. application mirror image is submitted to mirror image warehouse;
4. containerization engine service end will the structure information of application mirror image, comprises the application title of mirror image and tag feedback to caller.
7. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: delete application mirror image in described step (4) and obtain the concrete steps of application mirror image as follows:
Delete application mirror image
1. containerization engine service termination receives title and the label of the mirror image that will delete that caller imports into;
2. the API calling mirror image warehouse completes image file and deletes;
Obtain application mirror image
1. containerization engine service end calls the API in mirror image warehouse, obtains image listing inventory;
2. containerization engine service end organizes return data, and feedback result is to caller.
8. the building and operation method of container cloud plateform system according to claim 1, is characterized in that: in described step (6), step concrete steps are 3. as follows:
The timing of A, thread 2 obtains application actual motion state from key-value pair system, and each the running status moment got is as a snapshot;
Nearest three snapshots of B, thread 2 record application actual motion state, and three snapshots are compared, if three snapshot states are inconsistent, are judged as that current network is unstable or carrying out Failure Transfer and cause, in this case do not process; If three snapshot states are consistent, start to judge that whether application example actual motion state is consistent with expecting state, after having judged, judge that whether the example quantity applied is consistent with anticipated number.
9. the building and operation method of container cloud plateform system according to claim 8, is characterized in that: described step B starts to judge that the concrete steps whether actual motion state is consistent with expecting state are as follows:
1. according to the application example inventory that containerization engine provides, record and compare one by one with in key-value pair system, if both running example states of record are inconsistent, the RESTAPI completion status calling containerization engine changes;
2. only compare the application example being in operation and halted state, the application of the state of mediating do not processed,
Situation 1: the example of the record in containerization engine does not have in key-value pair system, thread 2 notifies that containerization engine newly creates an example;
Situation 2: the example recorded in containerization engine state in key-value pair system is inconsistent, thread 2 notifies containerization engine adapts example state;
Situation 3: do not have record in containerization engine, but have heartbeat in key-value pair system, thread 2 notifies that containerization engine removes this example.
10. the building and operation method of container cloud plateform system according to claim 8, is characterized in that: judge in described step B that whether consistent with anticipated number the example quantity concrete steps processed applied are as follows:
1. obtain the desired value that the application of recording in containerization engine modules runs quantity, and the example heartbeat quantity of key-value pair system log (SYSLOG) compares;
2. only compare the application being in operation and halted state, other states do not process;
The possible situation that both compare existence comprises:
Situation 1: if the example anticipated number of containerization engine record is more than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine reduces running example;
Situation 2: if the example anticipated number of containerization engine record is less than the example quantity of key-value pair system log (SYSLOG), informs that containerization engine increases running example.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510656868.1A CN105245373B (en) | 2015-10-12 | 2015-10-12 | A kind of container cloud platform system is built and operation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510656868.1A CN105245373B (en) | 2015-10-12 | 2015-10-12 | A kind of container cloud platform system is built and operation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105245373A true CN105245373A (en) | 2016-01-13 |
| CN105245373B CN105245373B (en) | 2017-08-04 |
Family
ID=55042884
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510656868.1A Active CN105245373B (en) | 2015-10-12 | 2015-10-12 | A kind of container cloud platform system is built and operation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105245373B (en) |
Cited By (65)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105743995A (en) * | 2016-04-05 | 2016-07-06 | 北京轻元科技有限公司 | Transplantable high-available container cluster deploying and managing system and method |
| CN105893133A (en) * | 2016-03-31 | 2016-08-24 | 乐视控股（北京）有限公司 | Application service seamless migration method and system based on container technology |
| CN105912596A (en) * | 2016-04-05 | 2016-08-31 | 中国银联股份有限公司 | Method and device for operation of databases |
| CN106020930A (en) * | 2016-05-13 | 2016-10-12 | 深圳市中润四方信息技术有限公司 | Application container based application management method and system |
| CN106101176A (en) * | 2016-05-27 | 2016-11-09 | 成都索贝数码科技股份有限公司 | The media cloud that melts of a kind of integration produces delivery system and method |
| CN106209827A (en) * | 2016-07-08 | 2016-12-07 | 安徽四创电子股份有限公司 | Virtual card port system based on container cloud and service creating method thereof |
| CN106412126A (en) * | 2016-12-05 | 2017-02-15 | 深圳中兴网信科技有限公司 | Docker image description information display method and display device |
| CN106445515A (en) * | 2016-09-18 | 2017-02-22 | 深圳市华云中盛科技有限公司 | PaaS cloud implementation method based on containers |
| CN106506655A (en) * | 2016-11-18 | 2017-03-15 | 国云科技股份有限公司 | A kind of container group scheduling method suitable for cloud platform |
| CN106708598A (en) * | 2016-07-29 | 2017-05-24 | 腾讯科技（深圳）有限公司 | Setup method and device for virus analysis environment |
| CN106776029A (en) * | 2016-12-21 | 2017-05-31 | 上海爱数信息技术股份有限公司 | A kind of method and system for optimizing server memory resource utilization |
| CN106844489A (en) * | 2016-12-24 | 2017-06-13 | 上海七牛信息技术有限公司 | A kind of file operation method, device and system |
| CN106878385A (en) * | 2016-12-30 | 2017-06-20 | 新华三技术有限公司 | Private clound dispositions method and device |
| WO2017129106A1 (en) * | 2016-01-29 | 2017-08-03 | 腾讯科技（深圳）有限公司 | Data request processing method, server and system |
| CN107105009A (en) * | 2017-03-22 | 2017-08-29 | 北京荣之联科技股份有限公司 | Job scheduling method and device based on Kubernetes system docking workflow engines |
| WO2017157156A1 (en) * | 2016-03-14 | 2017-09-21 | 阿里巴巴集团控股有限公司 | Method and apparatus for processing user requests |
| CN107220101A (en) * | 2017-04-19 | 2017-09-29 | 阿里巴巴集团控股有限公司 | A kind of container creation method and device |
| CN107329819A (en) * | 2017-07-11 | 2017-11-07 | 杭州时趣信息技术有限公司 | A kind of job management method and device |
| CN107341073A (en) * | 2017-06-08 | 2017-11-10 | 北京优帆科技有限公司 | A kind of method and device for realizing container compatible mainframe fictitious host computer image file |
| CN107423112A (en) * | 2017-06-28 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of Docker container states real-time synchronization method |
| WO2017219676A1 (en) * | 2016-06-23 | 2017-12-28 | 华为技术有限公司 | A cloud application detection method and apparatus |
| CN107547250A (en) * | 2017-06-26 | 2018-01-05 | 新华三云计算技术有限公司 | The method and apparatus that database is disposed in cloud computing management platform |
| CN107678756A (en) * | 2017-09-29 | 2018-02-09 | 千寻位置网络有限公司 | A kind of Web based on Docker applies a key dissemination method |
| CN107704310A (en) * | 2017-09-27 | 2018-02-16 | 郑州云海信息技术有限公司 | A kind of method, apparatus and equipment for realizing container cluster management |
| CN107911463A (en) * | 2017-11-27 | 2018-04-13 | 深信服科技股份有限公司 | A kind of business is across cloud framework and its creation method, management method |
| CN108108230A (en) * | 2018-01-26 | 2018-06-01 | 成都精灵云科技有限公司 | Cloud platform delivery system based on docker |
| CN108205481A (en) * | 2016-12-19 | 2018-06-26 | 华为技术有限公司 | The container instance creation method and device of application |
| CN108259418A (en) * | 2016-12-28 | 2018-07-06 | 中移(苏州)软件技术有限公司 | A kind of system and method for function trusteeship service |
| CN108363802A (en) * | 2018-02-28 | 2018-08-03 | 深圳市华云中盛科技有限公司 | Text collection method based on container and its system |
| CN108363610A (en) * | 2018-02-09 | 2018-08-03 | 华为技术有限公司 | A kind of control method and equipment of virtual machine monitoring plug-in unit |
| CN108512940A (en) * | 2018-04-20 | 2018-09-07 | 济南浪潮高新科技投资发展有限公司 | A kind of Internet of Things cloud platform terminal notification method for pushing |
| CN108628613A (en) * | 2018-05-02 | 2018-10-09 | 山东汇贸电子口岸有限公司 | The implementation method of the stateful service of container cluster based on domestic CPU and OS |
| CN108964968A (en) * | 2018-03-27 | 2018-12-07 | 深圳市康拓普信息技术有限公司 | Service access management method and system under a kind of container cloud environment |
| CN109005433A (en) * | 2018-09-04 | 2018-12-14 | 北京邮电大学 | A kind of video cloud service platform architecture and implementation method |
| CN109104467A (en) * | 2018-07-25 | 2018-12-28 | 北京京东尚科信息技术有限公司 | Develop environment construction method, apparatus and plateform system and storage medium |
| CN109313577A (en) * | 2016-06-30 | 2019-02-05 | 微软技术许可有限责任公司 | Data plane API in distributed computing network |
| CN109417561A (en) * | 2016-04-11 | 2019-03-01 | 华为技术有限公司 | Distributive resource managing method and system |
| CN109672633A (en) * | 2018-12-27 | 2019-04-23 | 南京极域信息科技有限公司 | A kind of virtual switch method |
| CN109710433A (en) * | 2018-12-30 | 2019-05-03 | 浙江蓝卓工业互联网信息技术有限公司 | Data processing method, apparatus and system based on metadata driven |
| CN109857577A (en) * | 2019-01-28 | 2019-06-07 | 北京三快在线科技有限公司 | Access control method, device, medium and electronic equipment |
| CN109936571A (en) * | 2019-02-22 | 2019-06-25 | 全球能源互联网研究院有限公司 | A kind of mass data sharing method, opening and shares platform and electronic equipment |
| CN110109686A (en) * | 2019-04-25 | 2019-08-09 | 中电科嘉兴新型智慧城市科技发展有限公司 | It is a kind of that O&M method and system is applied based on Container Management engine |
| CN110162381A (en) * | 2019-04-04 | 2019-08-23 | 北京升鑫网络科技有限公司 | Proxy executing method in a kind of container |
| CN110288993A (en) * | 2019-06-26 | 2019-09-27 | 广州探迹科技有限公司 | A kind of individualized intelligent voice interactive method and device based on container technique |
| CN110389811A (en) * | 2018-04-18 | 2019-10-29 | 杭州海康威视系统技术有限公司 | A kind of test method based on distributed system, device |
| CN110603522A (en) * | 2017-05-02 | 2019-12-20 | 纳木技术株式会社 | Method for containerizing application program on cloud platform |
| CN110753120A (en) * | 2019-10-25 | 2020-02-04 | 北京浪潮数据技术有限公司 | Stateful load creating method, device, equipment and medium |
| CN110825499A (en) * | 2020-01-13 | 2020-02-21 | 中软信息系统工程有限公司 | Method and device for realizing security isolation based on unified container cloud platform |
| US10615998B2 (en) | 2016-08-17 | 2020-04-07 | Red Hat, Inc. | State analysis of remote computing images |
| CN111240806A (en) * | 2020-01-14 | 2020-06-05 | 南京邮电大学 | Distributed container mirror image construction scheduling system and method |
| CN111527474A (en) * | 2018-01-03 | 2020-08-11 | 国际商业机器公司 | Dynamic delivery of software functionality |
| CN111552543A (en) * | 2020-05-22 | 2020-08-18 | 北京联想软件有限公司 | Container management and control method and processing node |
| CN111654553A (en) * | 2020-06-30 | 2020-09-11 | 平安银行股份有限公司 | Management and control operation method and device based on middleware, computer equipment and medium |
| CN111786904A (en) * | 2020-07-07 | 2020-10-16 | 上海道客网络科技有限公司 | System and method for realizing container dormancy and awakening |
| CN111857953A (en) * | 2020-07-17 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Container cluster management method, device, equipment and readable storage medium |
| CN111858098A (en) * | 2020-07-24 | 2020-10-30 | 成都成信高科信息技术有限公司 | Data exchange method based on mass data |
| CN111949366A (en) * | 2020-07-07 | 2020-11-17 | 北京思特奇信息技术股份有限公司 | System and method for reverse proxy of out-of-container service to inside of container |
| CN112131023A (en) * | 2020-09-23 | 2020-12-25 | 平安科技（深圳）有限公司 | Message processing system, method, device and storage medium for application container engine |
| CN112153036A (en) * | 2020-09-18 | 2020-12-29 | 湖南联盛网络科技股份有限公司 | Security defense method and system based on proxy server |
| CN112491984A (en) * | 2020-11-13 | 2021-03-12 | 上海连尚网络科技有限公司 | Container editing engine cluster management system based on virtual network bridge |
| CN112671820A (en) * | 2020-08-17 | 2021-04-16 | 紫光云技术有限公司 | Method for realizing public cloud load balancing service based on container |
| CN112968897A (en) * | 2021-02-25 | 2021-06-15 | 浙江清华长三角研究院 | Container calculation method operating in decentralized system |
| CN113497830A (en) * | 2021-06-25 | 2021-10-12 | 浙江大华技术股份有限公司 | Cloud network communication method, platform, equipment and storage medium |
| CN114338133A (en) * | 2021-12-24 | 2022-04-12 | 中国联合网络通信集团有限公司 | Application access system, method, communication device and storage medium |
| WO2022237447A1 (en) * | 2021-05-10 | 2022-11-17 | 中兴通讯股份有限公司 | Operation and maintenance method, apparatus, and system, server, electronic device, and medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202495970U (en) * | 2012-02-14 | 2012-10-17 | 广州亦云信息技术有限公司 | Distributed PAAS cloud computing platform |
| CN103024060B (en) * | 2012-12-20 | 2015-05-13 | 中国科学院深圳先进技术研究院 | Open type cloud computing monitoring system for large scale cluster and method thereof |
| CN104702663B (en) * | 2014-12-12 | 2018-08-28 | 用友网络科技股份有限公司 | Cloud processing unit and method |
-
2015
- 2015-10-12 CN CN201510656868.1A patent/CN105245373B/en active Active
Cited By (104)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017129106A1 (en) * | 2016-01-29 | 2017-08-03 | 腾讯科技（深圳）有限公司 | Data request processing method, server and system |
| US10902030B2 (en) | 2016-03-14 | 2021-01-26 | Alibaba Group Holding Limited | User request processing method and device |
| CN107196982B (en) * | 2016-03-14 | 2021-01-22 | 阿里巴巴集团控股有限公司 | User request processing method and device |
| CN107196982A (en) * | 2016-03-14 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind for the treatment of method and apparatus of user's request |
| WO2017157156A1 (en) * | 2016-03-14 | 2017-09-21 | 阿里巴巴集团控股有限公司 | Method and apparatus for processing user requests |
| CN105893133A (en) * | 2016-03-31 | 2016-08-24 | 乐视控股（北京）有限公司 | Application service seamless migration method and system based on container technology |
| CN105743995B (en) * | 2016-04-05 | 2019-10-18 | 北京轻元科技有限公司 | A kind of system and method for the deployment of portable High Availabitity and management container cluster |
| CN105912596A (en) * | 2016-04-05 | 2016-08-31 | 中国银联股份有限公司 | Method and device for operation of databases |
| CN105743995A (en) * | 2016-04-05 | 2016-07-06 | 北京轻元科技有限公司 | Transplantable high-available container cluster deploying and managing system and method |
| CN109417561A (en) * | 2016-04-11 | 2019-03-01 | 华为技术有限公司 | Distributive resource managing method and system |
| CN106020930A (en) * | 2016-05-13 | 2016-10-12 | 深圳市中润四方信息技术有限公司 | Application container based application management method and system |
| CN106020930B (en) * | 2016-05-13 | 2019-07-23 | 深圳市中润四方信息技术有限公司 | A kind of application management method and system based on application container |
| CN106101176A (en) * | 2016-05-27 | 2016-11-09 | 成都索贝数码科技股份有限公司 | The media cloud that melts of a kind of integration produces delivery system and method |
| US11176244B2 (en) | 2016-06-23 | 2021-11-16 | Huawei Technologies Co., Ltd. | Cloud application detection method and cloud application detection apparatus |
| CN107545178B (en) * | 2016-06-23 | 2021-01-15 | 华为技术有限公司 | Cloud application detection method and cloud application detection device |
| WO2017219676A1 (en) * | 2016-06-23 | 2017-12-28 | 华为技术有限公司 | A cloud application detection method and apparatus |
| CN107545178A (en) * | 2016-06-23 | 2018-01-05 | 华为技术有限公司 | The detection method and cloud application detection means of a kind of cloud application |
| US11121906B2 (en) | 2016-06-30 | 2021-09-14 | Microsoft Technology Licensing, Llc | Data plane API in a distributed computing network |
| CN109313577A (en) * | 2016-06-30 | 2019-02-05 | 微软技术许可有限责任公司 | Data plane API in distributed computing network |
| CN106209827A (en) * | 2016-07-08 | 2016-12-07 | 安徽四创电子股份有限公司 | Virtual card port system based on container cloud and service creating method thereof |
| CN106708598B (en) * | 2016-07-29 | 2021-03-19 | 腾讯科技（深圳）有限公司 | Virus analysis environment building method and device |
| CN106708598A (en) * | 2016-07-29 | 2017-05-24 | 腾讯科技（深圳）有限公司 | Setup method and device for virus analysis environment |
| US11025454B2 (en) | 2016-08-17 | 2021-06-01 | Red Hat, Inc. | State analysis of remote computing images |
| US10615998B2 (en) | 2016-08-17 | 2020-04-07 | Red Hat, Inc. | State analysis of remote computing images |
| CN106445515A (en) * | 2016-09-18 | 2017-02-22 | 深圳市华云中盛科技有限公司 | PaaS cloud implementation method based on containers |
| CN106506655B (en) * | 2016-11-18 | 2019-04-26 | 国云科技股份有限公司 | A kind of container group scheduling method suitable for cloud platform |
| CN106506655A (en) * | 2016-11-18 | 2017-03-15 | 国云科技股份有限公司 | A kind of container group scheduling method suitable for cloud platform |
| CN106412126A (en) * | 2016-12-05 | 2017-02-15 | 深圳中兴网信科技有限公司 | Docker image description information display method and display device |
| CN108205481A (en) * | 2016-12-19 | 2018-06-26 | 华为技术有限公司 | The container instance creation method and device of application |
| CN108205481B (en) * | 2016-12-19 | 2022-03-08 | 华为技术有限公司 | Application container instance creation method and device |
| CN106776029A (en) * | 2016-12-21 | 2017-05-31 | 上海爱数信息技术股份有限公司 | A kind of method and system for optimizing server memory resource utilization |
| CN106776029B (en) * | 2016-12-21 | 2020-06-09 | 上海爱数信息技术股份有限公司 | Method and system for optimizing utilization rate of server memory resources |
| CN106844489A (en) * | 2016-12-24 | 2017-06-13 | 上海七牛信息技术有限公司 | A kind of file operation method, device and system |
| CN108259418A (en) * | 2016-12-28 | 2018-07-06 | 中移(苏州)软件技术有限公司 | A kind of system and method for function trusteeship service |
| CN108259418B (en) * | 2016-12-28 | 2021-08-24 | 中移(苏州)软件技术有限公司 | System and method for function hosting service |
| CN106878385A (en) * | 2016-12-30 | 2017-06-20 | 新华三技术有限公司 | Private clound dispositions method and device |
| CN107105009B (en) * | 2017-03-22 | 2020-03-10 | 北京荣之联科技股份有限公司 | Job scheduling method and device for butting workflow engine based on Kubernetes system |
| CN107105009A (en) * | 2017-03-22 | 2017-08-29 | 北京荣之联科技股份有限公司 | Job scheduling method and device based on Kubernetes system docking workflow engines |
| CN107220101A (en) * | 2017-04-19 | 2017-09-29 | 阿里巴巴集团控股有限公司 | A kind of container creation method and device |
| CN107220101B (en) * | 2017-04-19 | 2020-06-23 | 阿里巴巴集团控股有限公司 | Container creation method and device |
| CN110603522B (en) * | 2017-05-02 | 2023-04-18 | 纳木技术株式会社 | Method for containerizing application program on cloud platform |
| CN110603522A (en) * | 2017-05-02 | 2019-12-20 | 纳木技术株式会社 | Method for containerizing application program on cloud platform |
| CN107341073A (en) * | 2017-06-08 | 2017-11-10 | 北京优帆科技有限公司 | A kind of method and device for realizing container compatible mainframe fictitious host computer image file |
| CN107341073B (en) * | 2017-06-08 | 2020-07-03 | 北京青云科技股份有限公司 | Method and device for realizing compatibility of container host and virtual host image file |
| CN107547250A (en) * | 2017-06-26 | 2018-01-05 | 新华三云计算技术有限公司 | The method and apparatus that database is disposed in cloud computing management platform |
| CN107423112B (en) * | 2017-06-28 | 2020-06-26 | 浪潮云信息技术有限公司 | Docker container state real-time synchronization method |
| CN107423112A (en) * | 2017-06-28 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of Docker container states real-time synchronization method |
| CN107329819A (en) * | 2017-07-11 | 2017-11-07 | 杭州时趣信息技术有限公司 | A kind of job management method and device |
| CN107704310A (en) * | 2017-09-27 | 2018-02-16 | 郑州云海信息技术有限公司 | A kind of method, apparatus and equipment for realizing container cluster management |
| CN107704310B (en) * | 2017-09-27 | 2021-06-29 | 郑州云海信息技术有限公司 | Method, device and equipment for realizing container cluster management |
| CN107678756A (en) * | 2017-09-29 | 2018-02-09 | 千寻位置网络有限公司 | A kind of Web based on Docker applies a key dissemination method |
| CN107911463A (en) * | 2017-11-27 | 2018-04-13 | 深信服科技股份有限公司 | A kind of business is across cloud framework and its creation method, management method |
| CN111527474B (en) * | 2018-01-03 | 2023-12-26 | 国际商业机器公司 | Dynamic delivery of software functions |
| CN111527474A (en) * | 2018-01-03 | 2020-08-11 | 国际商业机器公司 | Dynamic delivery of software functionality |
| CN108108230A (en) * | 2018-01-26 | 2018-06-01 | 成都精灵云科技有限公司 | Cloud platform delivery system based on docker |
| CN108363610A (en) * | 2018-02-09 | 2018-08-03 | 华为技术有限公司 | A kind of control method and equipment of virtual machine monitoring plug-in unit |
| CN108363802A (en) * | 2018-02-28 | 2018-08-03 | 深圳市华云中盛科技有限公司 | Text collection method based on container and its system |
| CN108363802B (en) * | 2018-02-28 | 2021-10-29 | 深圳市华云中盛科技股份有限公司 | Container-based text collection method and system |
| CN108964968A (en) * | 2018-03-27 | 2018-12-07 | 深圳市康拓普信息技术有限公司 | Service access management method and system under a kind of container cloud environment |
| CN108964968B (en) * | 2018-03-27 | 2022-01-11 | 南方电网深圳数字电网研究院有限公司 | Service access management method and system in container cloud environment |
| CN110389811A (en) * | 2018-04-18 | 2019-10-29 | 杭州海康威视系统技术有限公司 | A kind of test method based on distributed system, device |
| CN110389811B (en) * | 2018-04-18 | 2022-04-05 | 杭州海康威视系统技术有限公司 | Testing method and device based on distributed system |
| CN108512940A (en) * | 2018-04-20 | 2018-09-07 | 济南浪潮高新科技投资发展有限公司 | A kind of Internet of Things cloud platform terminal notification method for pushing |
| CN108628613A (en) * | 2018-05-02 | 2018-10-09 | 山东汇贸电子口岸有限公司 | The implementation method of the stateful service of container cluster based on domestic CPU and OS |
| CN109104467B (en) * | 2018-07-25 | 2021-07-30 | 北京京东尚科信息技术有限公司 | Development environment construction method and device, platform system and storage medium |
| CN109104467A (en) * | 2018-07-25 | 2018-12-28 | 北京京东尚科信息技术有限公司 | Develop environment construction method, apparatus and plateform system and storage medium |
| CN109005433A (en) * | 2018-09-04 | 2018-12-14 | 北京邮电大学 | A kind of video cloud service platform architecture and implementation method |
| CN109005433B (en) * | 2018-09-04 | 2019-05-21 | 北京邮电大学 | A kind of video cloud service platform architecture and implementation method |
| CN109672633A (en) * | 2018-12-27 | 2019-04-23 | 南京极域信息科技有限公司 | A kind of virtual switch method |
| CN109710433A (en) * | 2018-12-30 | 2019-05-03 | 浙江蓝卓工业互联网信息技术有限公司 | Data processing method, apparatus and system based on metadata driven |
| CN109857577A (en) * | 2019-01-28 | 2019-06-07 | 北京三快在线科技有限公司 | Access control method, device, medium and electronic equipment |
| CN109936571A (en) * | 2019-02-22 | 2019-06-25 | 全球能源互联网研究院有限公司 | A kind of mass data sharing method, opening and shares platform and electronic equipment |
| CN110162381A (en) * | 2019-04-04 | 2019-08-23 | 北京升鑫网络科技有限公司 | Proxy executing method in a kind of container |
| CN110109686A (en) * | 2019-04-25 | 2019-08-09 | 中电科嘉兴新型智慧城市科技发展有限公司 | It is a kind of that O&M method and system is applied based on Container Management engine |
| CN110109686B (en) * | 2019-04-25 | 2023-03-24 | 中电科嘉兴新型智慧城市科技发展有限公司 | Application operation and maintenance method and system based on container management engine |
| CN110288993A (en) * | 2019-06-26 | 2019-09-27 | 广州探迹科技有限公司 | A kind of individualized intelligent voice interactive method and device based on container technique |
| CN110753120B (en) * | 2019-10-25 | 2022-06-10 | 北京浪潮数据技术有限公司 | Stateful load creating method, device, equipment and medium |
| CN110753120A (en) * | 2019-10-25 | 2020-02-04 | 北京浪潮数据技术有限公司 | Stateful load creating method, device, equipment and medium |
| CN110825499A (en) * | 2020-01-13 | 2020-02-21 | 中软信息系统工程有限公司 | Method and device for realizing security isolation based on unified container cloud platform |
| CN110825499B (en) * | 2020-01-13 | 2020-06-19 | 中软信息系统工程有限公司 | Method and device for realizing security isolation based on unified container cloud platform |
| CN111240806B (en) * | 2020-01-14 | 2022-04-01 | 南京邮电大学 | Distributed container mirror image construction scheduling method |
| CN111240806A (en) * | 2020-01-14 | 2020-06-05 | 南京邮电大学 | Distributed container mirror image construction scheduling system and method |
| CN111552543A (en) * | 2020-05-22 | 2020-08-18 | 北京联想软件有限公司 | Container management and control method and processing node |
| CN111654553B (en) * | 2020-06-30 | 2023-07-25 | 平安银行股份有限公司 | Middleware-based management and control operation method and device, computer equipment and medium |
| CN111654553A (en) * | 2020-06-30 | 2020-09-11 | 平安银行股份有限公司 | Management and control operation method and device based on middleware, computer equipment and medium |
| CN111949366B (en) * | 2020-07-07 | 2024-04-05 | 北京思特奇信息技术股份有限公司 | System and method for reversely proxy out-of-container service to inside of container |
| CN111949366A (en) * | 2020-07-07 | 2020-11-17 | 北京思特奇信息技术股份有限公司 | System and method for reverse proxy of out-of-container service to inside of container |
| CN111786904B (en) * | 2020-07-07 | 2021-07-06 | 上海道客网络科技有限公司 | System and method for realizing container dormancy and awakening |
| CN111786904A (en) * | 2020-07-07 | 2020-10-16 | 上海道客网络科技有限公司 | System and method for realizing container dormancy and awakening |
| CN111857953A (en) * | 2020-07-17 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Container cluster management method, device, equipment and readable storage medium |
| CN111857953B (en) * | 2020-07-17 | 2023-06-16 | 苏州浪潮智能科技有限公司 | Container cluster management method, device, equipment and readable storage medium |
| CN111858098B (en) * | 2020-07-24 | 2023-11-17 | 成都成信高科信息技术有限公司 | Data exchange method based on mass data |
| CN111858098A (en) * | 2020-07-24 | 2020-10-30 | 成都成信高科信息技术有限公司 | Data exchange method based on mass data |
| CN112671820A (en) * | 2020-08-17 | 2021-04-16 | 紫光云技术有限公司 | Method for realizing public cloud load balancing service based on container |
| CN112153036A (en) * | 2020-09-18 | 2020-12-29 | 湖南联盛网络科技股份有限公司 | Security defense method and system based on proxy server |
| CN112131023A (en) * | 2020-09-23 | 2020-12-25 | 平安科技（深圳）有限公司 | Message processing system, method, device and storage medium for application container engine |
| CN112131023B (en) * | 2020-09-23 | 2023-08-11 | 平安科技（深圳）有限公司 | Message processing system, method, equipment and storage medium for application container engine |
| CN112491984B (en) * | 2020-11-13 | 2022-08-12 | 上海连尚网络科技有限公司 | Container editing engine cluster management system based on virtual network bridge |
| CN112491984A (en) * | 2020-11-13 | 2021-03-12 | 上海连尚网络科技有限公司 | Container editing engine cluster management system based on virtual network bridge |
| CN112968897A (en) * | 2021-02-25 | 2021-06-15 | 浙江清华长三角研究院 | Container calculation method operating in decentralized system |
| WO2022237447A1 (en) * | 2021-05-10 | 2022-11-17 | 中兴通讯股份有限公司 | Operation and maintenance method, apparatus, and system, server, electronic device, and medium |
| CN113497830A (en) * | 2021-06-25 | 2021-10-12 | 浙江大华技术股份有限公司 | Cloud network communication method, platform, equipment and storage medium |
| CN114338133B (en) * | 2021-12-24 | 2023-07-07 | 中国联合网络通信集团有限公司 | Application access system, method, communication device and storage medium |
| CN114338133A (en) * | 2021-12-24 | 2022-04-12 | 中国联合网络通信集团有限公司 | Application access system, method, communication device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105245373B (en) | 2017-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105245373A (en) | Construction and operation method of container cloud platform system | |
| US10292044B2 (en) | Apparatus for end-user transparent utilization of computational, storage, and network capacity of mobile devices, and associated methods | |
| CN107707622B (en) | Method and device for accessing desktop cloud virtual machine and desktop cloud controller | |
| CN108270818B (en) | Micro-service architecture system and access method thereof | |
| US8447757B1 (en) | Latency reduction techniques for partitioned processing | |
| CN105025053A (en) | Distributed file upload method based on cloud storage technology and system | |
| CN102594861A (en) | Cloud storage system with balanced multi-server load | |
| CN104408071A (en) | Distributive database high-availability method and system based on cluster manager | |
| US20240095082A1 (en) | Method and system for multiple services to share same gpu, and device and medium | |
| CN106354559A (en) | Method and device for processing cloud desktop resources | |
| WO2018121334A1 (en) | Web application service providing method, apparatus, electronic device and system | |
| CN113965560A (en) | Data transmission method, proxy server, storage medium, and electronic device | |
| CN110297867B (en) | Database cluster operation method and system based on domestic CPU and distributed container cluster | |
| CN111935238A (en) | Cloud platform load balancing management system, method, equipment and medium | |
| CN103067486B (en) | Based on the large data processing method of PaaS platform | |
| US20130054735A1 (en) | Wake-up server | |
| CN113014608B (en) | Flow distribution control method and device, electronic equipment and storage medium | |
| CN103677983A (en) | Scheduling method and device of application | |
| CN112468589A (en) | Data distribution method and device, computer equipment and storage medium | |
| US20120198482A1 (en) | Distributed Multi-System Management | |
| US9106676B1 (en) | Grid-based server messaging infrastructure | |
| CN113900774A (en) | Virtual machine control method and device of cloud operating system and storage medium | |
| CN112073499A (en) | Dynamic service method of multi-machine type cloud physical server | |
| CN103514044B (en) | Resource optimization method, device and system of dynamic behavior analysis system | |
| CN115643271A (en) | Method, device, server and medium for synchronizing multi-application data on cloud |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information |
Inventor after: Chen Wenkang Inventor after: Zhao Guangjun Inventor after: Wang Ruying Inventor after: Li Xinrong Inventor after: Li Zhibin Inventor after: Lu Xiandong Inventor after: Zhang Haitao Inventor before: Gao Yong Inventor before: Zhang Haitao Inventor before: Hu Xiaonan Inventor before: Ji Panpan |
|
| COR | Change of bibliographic data | ||
| CB03 | Change of inventor or designer information |
Inventor after: Chen Wenkang Inventor after: Zhao Guangjun Inventor after: Wang Ruying Inventor after: Li Xinrong Inventor after: Gao Yong Inventor after: Zhang Haitao Inventor after: Hu Xiaonan Inventor after: Ji Panpan Inventor before: Chen Wenkang Inventor before: Zhao Guangjun Inventor before: Wang Ruying Inventor before: Li Xinrong Inventor before: Li Zhibin Inventor before: Lu Xiandong Inventor before: Zhang Haitao |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231101 Address after: Room 608, Building J, Haitai Green Industry Base, No. 6 Haitai Development Sixth Road, Huayuan Industrial Zone, Xiqing District, Tianjin, 300384 Patentee after: TIANJIN RICHSOFT ELECTRIC POWER INFORMATION TECHNOLOGY Co.,Ltd. Patentee after: State Grid Siji Location Service Co.,Ltd. Address before: 6th floor, Building J, Software Park, Haitai Green Industry Base, Xiqing District, Tianjin, 300384 Patentee before: TIANJIN RICHSOFT ELECTRIC POWER INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |