CN105610946B - A kind of cloud springboard machine system based on docker technologies - Google Patents
A kind of cloud springboard machine system based on docker technologies Download PDFInfo
- Publication number
- CN105610946B CN105610946B CN201511021768.8A CN201511021768A CN105610946B CN 105610946 B CN105610946 B CN 105610946B CN 201511021768 A CN201511021768 A CN 201511021768A CN 105610946 B CN105610946 B CN 105610946B
- Authority
- CN
- China
- Prior art keywords
- docker
- machine
- springboards
- springboard
- main
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The cloud springboard machine system based on docker technologies that an embodiment of the present invention provides a kind of, including：Central management module, it disposes the running environment of docker container servers to build docker container servers, and build docker Container Management modules, when meeting predetermined conditions, the instruction for creating main docker springboards machine is sent to docker Container Management modules, disposes the running environment of the main docker springboards machine；Docker Container Management modules create when receiving the instruction for creating main docker springboards machine and start corresponding main docker springboards machine, by the port mapping of docker container servers to the interactive service port of main docker springboards machine；Main docker springboards machine, addition need the server managed, monitor and record the access behavior for the server that user manages needs.This programme can reduce the cost for disposing virtual springboard machine.
Description
Technical field
The present invention relates to software technology fields, more particularly to a kind of cloud springboard machine system based on docker technologies.
Background technology
The security audit of server is mainly used for monitoring the various operation behaviors of user, and then the safety of audit server.
The audit hardware for having many springboard machines (fort machine) etc on current market contributes to the access rights of control user, audit
The operation behavior of user, to achieve the purpose that the operation that notes abnormalities in time, to ensure the safety of server.An and springboard machine
Price it is more expensive, it is typically all to buy one or two springboard machine to remove all server of management enterprises to lead to enterprise.
With the fast development of cloud computing and the maturation of virtualization technology, enterprise also begins to dispose the private clound of oneself to drop
Low infrastructure cost.The deployment of private clound causes enterprise servers quantity to explode, then, how to go effectively to manage a large amount of
Server, including user right access control, user behavior audit etc., is exactly a comparison distinct issues.If having
Thousands of employees, up to ten thousand servers still go to manage with one or two springboard machine, then the workload of safe operation maintenance personnel can be big
Big to increase, the stability and reliability of work quality are just difficult to be guaranteed, and cloud springboard machine then can preferably solve this
A little problems.
Currently, the deployment of the virtual springboard machine in cloud springboard machine system is all based on system-level virtualization technology, such as
The virtualization technologies such as xen, vmware, i.e., rerun a client operating system on host system.And client operating system
Configuration is that fixed allocation is good, that is to say, that these virtualization technologies are can be independent and fixed to the distribution of virtual springboard machine
The hardware resources such as CPU, memory, hard disk.By the number of servers that springboard machine is managed each virtually in practical application and divide
Cloth position is different, and therefore, there are dramatic differences for the hardware resource needed for each virtual springboard machine, are not identical, it is seen then that existing
The problem of some cloud springboard machine systems can cause low hardware resource utilization and the wasting of resources, disposes the cost of virtual springboard machine very
It is high.
Invention content
The cloud springboard machine system based on docker technologies that the embodiment of the invention discloses a kind of, to improve the profit of hardware resource
With rate, the wasting of resources is solved the problems, such as, reduce the cost for disposing virtual springboard machine.Specific technical solution is as follows：
The cloud springboard machine system based on docker technologies that the embodiment of the invention discloses a kind of, the system comprises：
Central management module, for disposing the running environment of docker container servers to build docker container services
Device, and docker Container Management modules are built in the docker container servers, which is arranged
For available mode, also, when meeting predetermined conditions, the docker into the docker container servers for belonging to available mode holds
Device management module sends the instruction for creating main docker springboards machine, and in the docker Container Managements module creation and starts phase
The running environment for the main docker springboards machine deployment main docker springboards machine answered；
Docker Container Management modules, in the main docker springboards machine of establishment for receiving central management module transmission
When instruction, corresponding main docker springboards machine is created and started, and by the port mapping of the docker container servers to institute
The interactive service port of main docker springboards machine is stated, so that user accesses the master by the port of docker container servers
Docker springboard machines；
The main docker springboards machine monitors for adding the server for needing to manage and records user to the needs
The access behavior of the server of management, wherein every server is under the jurisdiction of unique main docker springboards machine.
In a specific embodiment of the present invention, the docker Container Managements module is additionally operable to：
Receive central management module transmission establishment from the instruction of docker springboard machines when, create and start with it is described
Main docker springboards machine is associated at least one from docker springboard machines, and the port of the docker container servers is reflected
From the interactive service port of docker springboard machines described in being mapped to, so that the port that user passes through docker container servers accesses institute
It states from docker springboard machines；
The central management module, is additionally operable to：The docker Container Managements module creation and start accordingly from
Docker springboard machine deployments should be from the running environment of docker springboard machines；
It is described to be used for from docker springboard machines：Meet the requirements for access of the different user in geographic location, so that handy
Family accesses the server that its associated main docker springboards machine is added by described from docker springboard machines.
In a specific embodiment of the present invention, the central management module is additionally operable to：
Key information in the main docker springboards machine is synchronized to associated all described from docker springboard machines
In.
In a specific embodiment of the present invention, the central management module is additionally operable to：
The task message of springboard machine is generated, and is sent out the task message by the port of the docker container servers
It is sent to the corresponding main docker springboards machine or from docker springboard machines；
Correspondingly, the main docker springboards machine or from docker springboard machines, is additionally operable to：
It receives and executes the task message.
In a specific embodiment of the present invention, the central management module is additionally operable to：
Send the instruction deleted main docker springboards machine or deleted from docker springboard machines；
Correspondingly, the docker Container Managements module, is additionally operable to：
It receives the main docker springboards machine of the deletion or deletes the instruction from docker springboard machines, and delete corresponding main
Docker springboards machine or from docker springboard machines.
In a specific embodiment of the present invention, the central management module is additionally operable to：
Monitor whether all main docker springboards machines work normally in preset time range；
When being judged as NO, by the main docker springboards machine not worked normally in preset time range labeled as failure shape
State, and check that this is marked as the main docker springboards machine of failure state and whether has associated normally to move from docker springboards machine
Make, if so,
The slave docker springboards machine of the normal work is arranged as main docker springboards machine, and to the docker container tubes
It manages module and sends the instruction created from docker springboard machines, otherwise,
The instruction for creating main docker springboards machine is sent to the docker Container Managements module；
Correspondingly, the docker Container Managements module, is additionally operable to：
The instruction created from docker springboard machines is received, creates and starts accordingly from docker springboard machines, by institute
The user information stated in the main docker springboards machine labeled as failure state is synchronized in the slave docker springboards machine newly created；
The instruction for creating main docker springboards machine is received, create and starts corresponding main docker springboards machine, by institute
The user information stated in the main docker springboards machine labeled as failure state is synchronized in the main docker springboards machine newly created.
In a specific embodiment of the present invention, the central management module is additionally operable to：
It monitors and all whether is worked normally in preset time range from docker springboards machine；
When being judged as NO, by the slave docker springboards machine not worked normally in preset time range labeled as failure shape
State, and the instruction created from docker springboard machines is sent to the docker Container Managements module；
Correspondingly, the docker Container Managements module, is additionally operable to：
The instruction created from docker springboard machines is received, creates and starts accordingly from docker springboard machines, by institute
The user information stated in the main docker springboards machine associated by the slave docker springboards machine labeled as failure state is synchronized to new wound
In the slave docker springboards machine built.
In a specific embodiment of the present invention, the central management module is specifically used for：
In the docker Container Managements module creation and start the main docker springboards machine or from docker springboard machines
Afterwards, using the main docker springboards machine created described in fabric remote deployments or from the running environment of docker springboard machines.
In a specific embodiment of the present invention, the central management module is additionally operable to：
Acquisition upgrading specifies main docker springboards machine or after the instruction of docker springboard machines, using fabric remote deployments
It is described to specify main docker springboards machine or the running environment from docker springboard machines.
In a specific embodiment of the present invention, the central management module is additionally operable to：
All main docker springboards machines and key information and database information from docker springboard machines are periodically carried out standby
Part, and will be in the storage to corresponding cloud disk of backup file.
In a specific embodiment of the present invention, the main docker springboards machine and from docker springboard machines is also used
In：
Local daily record is synchronized to central database, wherein the local daily record is to log in daily record and User operation log,
The central database is central database corresponding with the system.
In a specific embodiment of the present invention, the main docker springboards machine is additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the main docker springboards machine；
If it does,
The version updating packet is downloaded, and the main docker springboards machine is updated in predetermined point of time；
It is described from docker springboard machines, be additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the docker springboard machines；
If it does,
The version updating packet is downloaded, and described from docker springboard machines in predetermined point of time update.
In a specific embodiment of the present invention, the system also includes：
Interactive module refers to for receiving administrative staff to the main docker springboards machine or from the management of docker springboard machines
It enables, and executes the management corresponding with instruction is managed to corresponding main docker springboards machine or from docker springboard machines and operate, and/
Or, for receiving user to the main docker springboards machine or from the inquiry instruction of docker springboard machines, and to leading accordingly
Docker springboards machine executes and the inquiry operation corresponding to inquiry instruction from docker springboard machines.
A kind of cloud springboard machine system based on docker technologies provided in an embodiment of the present invention, including docker containers structure
Module, central management module, docker Container Managements module and docker springboard machines virtualize skill using the docker of lightweight
Art, after docker Container Management modules receive the instruction for the establishment docker springboard machines that central management module is sent out, Ke Yixiang
The multiple docker springboards machines of establishment answered, all docker springboard machines share the resources such as calculating, storage of host hardware, can be with
It realizes the shared of hardware resource, greatly improves resource utilization, avoid the wasting of resources, reduce the cost for disposing virtual springboard machine.
Description of the drawings
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with
Obtain other attached drawings according to these attached drawings.
Fig. 1 is a kind of structural schematic diagram of the cloud springboard machine system based on docker technologies provided in an embodiment of the present invention；
Fig. 2 is a kind of another structural representation of the cloud springboard machine system based on docker technologies provided in an embodiment of the present invention
Figure；
Fig. 3 is a kind of work of the cloud springboard machine systematic difference example based on docker technologies provided in an embodiment of the present invention
Make principle schematic.
Specific implementation mode
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation describes, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall within the protection scope of the present invention.
As shown in Figure 1, an embodiment of the present invention provides a kind of cloud springboard machine system based on docker technologies, the system packet
It includes：Central management module 101, docker Container Managements module 102, main docker springboards machine 103.
Wherein, central management module 101, for disposing the running environment of docker container servers to build docker appearances
Device server, and docker Container Management modules are built in the docker container servers, by the docker container services
Device is set as available mode, also, when meeting predetermined conditions, into the docker container servers for belonging to available mode
Docker Container Management modules send the instruction for creating main docker springboards machine, and in the docker Container Managements module creation
And start the running environment of the corresponding main docker springboards machine deployment main docker springboards machine.
It should be noted that according to the actual application, one or more docker container servers can be built, and
Corresponding docker Container Managements module is built in each docker container servers, this is all reasonable.
Wherein, docker Container Managements module 102, in the main docker of establishment for receiving central management module transmission
When the instruction of springboard machine, corresponding main docker springboards machine is created and started, and by the port of the docker container servers
It is mapped to the interactive service port of the main docker springboards machine, so that user is visited by the port of docker container servers
Ask the main docker springboards machine.
It should be noted that according to the actual application, it can be according to the establishment master for receiving central management module transmission
The instruction of docker springboard machines creates in a docker container server and starts one or more main docker springboards
Machine can also create in different docker container servers and start one or more main docker springboards machines, this is all
Reasonably.
Wherein, the main docker springboards machine 103 monitors for adding the server for needing to manage and records user couple
The access behavior of the server for needing to manage, wherein every server is under the jurisdiction of unique main docker springboards machine.
It should be noted that a main docker springboards machine, which can add more, needs the server managed, still, to keep away
Exempt from managerial confusion, every server can only be under the jurisdiction of unique main docker springboards machine, cannot be added to more masters simultaneously
Docker springboard machines.
It is emphasized that the main springboard machine 103 monitors and records visit of the user to the server for needing to manage
Ask that the specific implementation of behavior may be used springboard machine monitoring in the prior art and record the service that user manages needs
The specific implementation of the access behavior of device.
A kind of cloud springboard machine system based on docker technologies provided in an embodiment of the present invention, including docker containers structure
Module, central management module, docker Container Managements module and docker springboard machines virtualize skill using the docker of lightweight
Art, after docker Container Management modules receive the instruction for the establishment docker springboard machines that central management module is sent out, Ke Yixiang
The multiple docker springboards machines of establishment answered, all docker springboard machines share the resources such as calculating, storage of host hardware, can be with
It realizes the shared of hardware resource, greatly improves resource utilization, avoid the wasting of resources, reduce the cost for disposing virtual springboard machine.
Further, in a kind of relatively good implementation of the present invention, which may be used also
For：
Receive central management module 101 transmission establishment from the instruction of docker springboard machines when, create and start with
The main docker springboards machine is associated at least one from docker springboard machines, and by the end of the docker container servers
Mouth be mapped to it is described from the interactive service port of docker springboard machines so that the port that user passes through docker container servers is visited
It asks described from docker springboard machines；
Correspondingly, the central management module 101, can be also used for：In the docker Container Managements module creation and start
It accordingly should be from the running environment of docker springboard machines from docker springboard machine deployments；
Wherein, described to be used for from docker springboard machines：Meet the requirements for access of the different user in geographic location, so that
It obtains user and accesses the server that its associated main docker springboards machine is added from docker springboard machines by described.
Demand is, it is emphasized that described can monitor from springboard machine and record what user added associated main springboard machine
The access behavior of server, also, existing skill may be used from the specific implementation of springboard machine monitoring and record access behavior
Springboard machine monitoring in art and record the server that user manages needs access behavior specific implementation.
For example, user is respectively in Beijing and the Shanghai cities Liang Ge, can be in Beijing and the Shanghai cities Liang Ge
It is respectively created and starts associated with the main docker springboards machine from docker springboard machines, Beijing in docker container servers
User can access the main docker by the slave docker springboards machine that Pekinese's docker container servers create and start
The server that springboard machine is added, the user in Shanghai can create and start by the docker container servers in Shanghai from
Docker springboard machines access the server that the main docker springboards machine is added, and can improve access speed in this way, reduce master
The processing pressure of docker springboard machines.
Further, described from docker springboards creating and starting in a kind of relatively good implementation of the present invention
After machine, central management module 101 can be also used for：Key information in the main docker springboards machine is synchronized to associated institute
Have from docker springboard machines, so that all key informations from docker springboard machines and the key in the main docker springboards machine
Information is consistent, and is achieved the purpose that highly reliable.
Further, in a kind of relatively good implementation of the present invention, above-mentioned central management module 101 can also be used
In：
The task message of springboard machine is generated, and is sent the task message by the port of the docker container servers
To corresponding main docker springboards machine or from docker springboard machines.For example, which can be：Add or delete takes
Business device message, add or delete user right message, cipher key distribution message, are not limited thereto certainly.
Corresponding main docker springboards machine or from docker springboard machines, is additionally operable to：It receives and executes the task message.
Further, the central management module 101 can be also used in a kind of relatively good implementation of the present invention：
When not needing a certain main docker springboards machine or a certain springboard machine from docker, to docker Container Management moulds
Block 102 sends the instruction deleted main docker springboards machine or deleted from docker springboard machines；
Correspondingly, docker Container Managements module 102, can be also used for：
It receives the main docker springboards machine of the deletion or deletes the instruction from docker springboard machines, and delete corresponding main
Docker springboards machine or from docker springboard machines.
Further, in a kind of relatively good implementation of the present invention, above-mentioned central management module 101 can also be used
In：
Monitor whether all main docker springboards machines work normally in preset time range；
When being judged as NO, by the main docker springboards machine not worked normally in preset time range labeled as failure shape
State, and check that this is marked as the main docker springboards machine of failure state and whether has associated normally to move from docker springboards machine
Make, if so,
The slave docker springboards machine of the normal work is arranged as main docker springboards machine, and to the docker container tubes
It manages module and sends the instruction created from docker springboard machines, otherwise,
The instruction for creating main docker springboards machine is sent to above-mentioned docker Container Managements module 102；
Correspondingly, the docker Container Managements module 102, is additionally operable to：
Instruction of the above-mentioned establishment from docker springboard machines is received, create and is started accordingly from docker springboard machines, it will be upper
The user information stated in the main docker springboards machine labeled as failure state is synchronized in the slave docker springboards machine newly created；
The instruction for receiving the main docker springboards machine of above-mentioned establishment creates and starts corresponding main docker springboards machine, will be upper
The user information stated in the main docker springboards machine labeled as failure state is synchronized in the main docker springboards machine newly created.
Wherein, above-mentioned preset time range can according to actual needs be defined by user, for example, 1 hour, 2 hours, it is 5 small
When etc.；It determines whether the main docker springboards machine works normally, whether can keep heartbeat by checking it, whether can be just
Often the existing ways such as connection determine, are herein not specifically limited.
It should be noted that check this be marked as the main docker springboards machine of failure state whether have it is associated from
When docker springboard machines are operating normally, the main docker springboards machine place that priority check is marked as failure state with this is same
Associated from docker springboard machines, the more conducively quick solution of failure in this way of docker container management service devices.
Further, in a kind of relatively good implementation of the present invention, above-mentioned central management module 101 can also be used
In：
It monitors and all whether is worked normally in preset time range from docker springboards machine；
When being judged as NO, by the slave docker springboards machine not worked normally in preset time range labeled as failure shape
State, and the instruction created from docker springboard machines is sent to above-mentioned docker Container Managements module 102；
Correspondingly, the docker Container Managements module 102, can be also used for：
Instruction of the above-mentioned establishment from docker springboard machines is received, create and is started accordingly from docker springboard machines, it will be upper
The user information stated in the main docker springboards machine associated by the slave docker springboards machine labeled as failure state is synchronized to new wound
In the slave docker springboards machine built.
Wherein, above-mentioned preset time range can according to actual needs be defined by user, for example, 1 hour, 2 hours, it is 5 small
When etc.；It determines whether the main docker springboards machine works normally, whether can keep heartbeat by checking it, whether can be just
Often the existing ways such as connection determine, are herein not specifically limited.
Further, it in a kind of relatively good implementation of the present invention, is created in above-mentioned docker Container Managements module 102
It builds and starts the main docker springboards machine or after docker springboard machines, central management module 101 is using the long-range portions fabric
Affix one's name to the main docker springboards machine created or the running environment from docker springboard machines.
Further, in a kind of relatively good implementation of the present invention, central management module 101 can be also used for：It obtains
Specified main docker springboards machine must be upgraded or after the instruction of docker springboard machines, this specifies master using fabric remote deployments
Docker springboards machine or running environment from docker springboard machines, are upgraded.
Further, in a kind of relatively good implementation of the present invention, central management module 101 can also be to all masters
Docker springboards machine and key information and database information from docker springboard machines are periodically backed up, and backup file is deposited
It stores up in corresponding cloud disk, prevents loss of data.
In addition, above-mentioned main docker springboards machine and can be also used for from docker springboard machines：
Local daily record is synchronized to central database, to store and manage local daily record.Wherein, the local daily record is to step on
Lu Zhi and User operation log, the central database are central database corresponding with the system.
Further, the main docker springboards machine, is additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the main docker springboards machine；
If it does,
The version updating packet is downloaded, and the main docker springboards machine is updated in predetermined point of time；
It is described from docker springboard machines, be additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the docker springboard machines；
If it does,
The version updating packet is downloaded, and is somebody's turn to do from docker springboard machines in predetermined point of time update.
Wherein, the predetermined point of time can be preset random time point, such as each noon on Wednesday 12:00
Deng.It may be implemented periodically actively to upgrade in this way.
It should be noted that a kind of cloud springboard machine system based on docker technologies provided in an embodiment of the present invention, such as Fig. 2
It is shown, can also include：Interactive module 104.
The interactive module 104 can be used for：Administrative staff are received to above-mentioned main docker springboards machine or from docker springboards
The management of machine instructs, and the pipe corresponding with instruction is managed is executed to corresponding main docker springboards machine or from docker springboard machines
Reason operation, and/or, for receiving user to above-mentioned main docker springboards machine or from the inquiry instruction of docker springboard machines, and it is right
Corresponding main docker springboards machine executes and the inquiry operation corresponding to inquiry instruction from docker springboard machines.
Specifically, administrative staff can be jumped by the interactive module 104 to above-mentioned main docker springboards machine or from docker
Trigger is managed operation, for example, user right operation, cipher key operation, system maintenance etc.；User can pass through interactive module
104 inquire the information such as the login daily record of oneself, operation log.
Further, which can be also used for：Receive the IP letters that docker Container Managements module 102 is sent
The information such as breath, port mapping, and these information are stored in central database, to prevent loss of data, ensure data information peace
Entirely.It can be also used for：Application programming interfaces are provided, so as to above-mentioned main docker springboards machine and can pass through from docker springboards machine
Local daily record is synchronized to central database by the application programming interfaces.
Further, which can be also used for storing above-mentioned version updating packet, above-mentioned main docker springboards
Machine or from docker springboard machines, can in the periodic detection interactive module 104 with the presence or absence of described right from docker springboards machine institute
The version updating packet answered, and execute corresponding update operation.
With reference to specific application example, it is provided for the embodiments of the invention a kind of cloud jump based on docker technologies
Trigger system is introduced.
As shown in figure 3, a kind of cloud springboard machine system based on docker technologies, may include：
Central management module belongs to the docker Container Managements module 1 of docker container servers 1 and belongs to docker appearances
The docker Container Managements module 1 of device server 2, the main docker springboards machine 01 created by docker Container Managements module 1
And from docker springboard machine 01-1, the main docker springboards machine 02 created by docker Container Managements module 2, from docker
Springboard machine 02-1 and associated with main docker springboards machine 01 from docker springboard machines 01-2, main docker springboards machine 01 is responsible for
Server 01, server 02 and server 03, the responsible server 04 of main docker springboards machine 02 and server 05, Yi Jijiao
Mutual module.
The operation principle of the cloud springboard machine system is：
The running environment of central management module deployment docker container servers 1 and docker container servers 2, and
Docker Container Managements module 1 is built in docker container servers 1, and docker is built in docker container servers 2 and is held
Device management module 2 sets docker container servers 1 and 2 to available mode, also, according to actual needs, to
Docker Container Managements module 1, which is sent, creates main docker springboards machine 01 and the instruction from docker springboard machines 01-1, to
Docker Container Managements module 2 sends and creates main docker springboards machine 02, from docker springboard machine 02-1 and with main docker
The associated instruction from docker springboard machines 01-2 of springboard machine 01.
Docker Container Managements module 1 is created and is opened in the above-mentioned establishment instruction for receiving central management module transmission
It moves main docker springboards machine 01 and is receiving central management from docker springboard machine 01-1, docker Container Managements module 2
Module send above-mentioned establishment instruction when, create and start main docker springboards machine 02, from docker springboard machine 02-1 and with
Main docker springboards machine 01 is associated from docker springboard machine 01-2, and by the port mapping of docker container servers 1 to leading
Docker springboards machine 01 and from the interactive service port of docker springboard machines 01-1, by the port of docker container servers 2
It is mapped to main docker springboards machine 02, from docker springboard machine 02-1 and associated with main docker springboards machine 01 from docker
The interactive service port of springboard machine 01-2.Central management module disposes above-mentioned all main docker springboards machines and all from docker
The running environment of springboard machine.
The main addition of docker springboards machine 01 needs the server 01, server 02 and the server 03 that manage, monitors and records
Access behavior of the user to server 01, server 02 and server 03, the main addition of docker springboards machine 02 need the clothes managed
Business device 04 and server 05, monitor and record access behavior of the user to server 04 and server 05.
It is creating and is starting from docker springboard machines 01-1, from docker springboard machine 02-1 and from docker springboard machines 01-2
Afterwards, central management module by the key information in main docker springboards machine 01 be synchronized to from docker springboard machine 01-1 and from
In docker springboard machines 01-2, the key information in main docker springboards machine 02 is synchronized to from docker springboard machines 02-1,
So that all key informations from docker springboard machines are consistent with the key information in corresponding main docker springboards machine, reach
To highly reliable purpose.
Central management module can also generate the task message of springboard machine, for example, central management module is held by docker
The port of device server 1 sends the task message for deleting server 01 to main docker springboards machine 01, correspondingly, main docker is jumped
After trigger 01 receives the task message, server 01 is deleted.
When not needing a certain main docker springboards machine or a certain springboard machine from docker, central management module can be to
Docker Container Management modules send the instruction deleted main docker springboards machine or deleted from docker springboard machines.For example, it is desired to
Delete from docker springboard machine 01-2 when, central management module to docker Container Managements module 2 send delete from docker jump
The instruction of trigger 01-2 correspondingly, docker Container Managements module 2 receives the instruction, and is deleted from docker springboard machines 01-2.
In a kind of optional realization method of the present invention, central management module can be also used for：
Monitor whether all main docker springboards machines work normally in preset time range；
It is assumed that judging that main docker springboards machine 01 does not work normally, by main docker springboards in preset time range
Whether machine 01 is labeled as failure state, and check that main docker springboards machine 01 is associated and normally moved from docker springboard machines 01-1
Make, if so,
The slave docker springboards machine 01-1 of the normal work is arranged as main docker springboards machine 01, and to docker containers
Management module 1 sends the instruction created from docker springboard machines 01-1, otherwise,
The instruction for creating main docker springboards machine 01 is sent to above-mentioned docker Container Managements module 1；
Wherein, above-mentioned preset time range can according to actual needs be defined by user, for example, 1 hour, 2 hours, it is 5 small
When etc.；It determines whether main docker springboards machine 01 works normally, whether can keep heartbeat by checking it, whether can be normal
The existing ways such as connection determine, are herein not specifically limited.
It should be noted that check this be marked as the main docker springboards machine 01 of failure state whether have it is associated from
When docker springboard machines are operating normally, priority check and same docker container management services device where main docker springboards machine 01
1 slave docker springboards machine 01-1 is more conducive to the quick solution of failure in this way.
Correspondingly, docker Container Managements module 1, is additionally operable to：
Instruction of the above-mentioned establishment from docker springboard machines 01-1 is received, create and is started from docker springboard machine 01-1, it will
The slave docker springboards machine 01-1 newly created is synchronized to labeled as the user information in the main docker springboards machine 01 of failure state
In；
The instruction for receiving the main docker springboards machine of above-mentioned establishment 01, creates and starts main docker springboards machine 01, will mark
It is synchronized in the main docker springboards machine 01 newly created for the user information in the main docker springboards machine 01 of failure state.
In a kind of relatively good implementation of the present invention, above-mentioned central management module can be also used for：
It monitors and all whether is worked normally in preset time range from docker springboards machine；
It is assumed that judging in preset time range, not work normally, will be jumped from docker from docker springboard machines 02-1
Trigger 02-1 is labeled as failure state, and the finger created from docker springboard machines 02-1 is sent to docker Container Managements module 2
It enables；
Wherein, above-mentioned preset time range can according to actual needs be defined by user, for example, 1 hour, 2 hours, it is 5 small
When etc.；It determines whether the main docker springboards machine works normally, whether can keep heartbeat by checking it, whether can be just
Often the existing ways such as connection determine, are herein not specifically limited.
Correspondingly, docker Container Managements module 2, can be also used for：
Instruction of the above-mentioned establishment from docker springboard machines 02-1 is received, create and is started from docker springboard machine 02-1, it will
The user information in main docker springboards machine 02 associated by slave docker springboards machine 02-1 labeled as failure state is synchronized to
In the slave docker springboards machine 02-1 newly created.
Specifically, creating and starting corresponding in above-mentioned docker Container Managements module 1 or docker Container Managements module 2
Main docker springboards machine or after docker springboard machines, central management module use the main docker that fabric remote deployments create
Springboard machine or running environment from docker springboard machines.
Further, central management module can be also used for：It obtains upgrading and specifies main docker springboards machine or from docker
After the instruction of springboard machine, using fabric remote deployments, this is specified main docker springboards machine or from the operation ring of docker springboard machines
Border is upgraded.For example, after obtaining the instruction for upgrading main docker springboards machine 02 that administrative staff are sent by interactive module,
Using the movement environment of the main docker springboards machine of fabric remote deployments 02, it is upgraded.
Further, central management module can also be to main docker springboards machine 01 and from docker springboard machines 01-
1, main docker springboards machine 02, key information and database from docker springboard machine 02-1 and from docker springboard machines 01-2
Information is periodically backed up, and by the storage to corresponding cloud disk of backup file, prevents loss of data.
In addition, main docker springboards machine 01 and from docker springboard machines 01-1, main docker springboards machine 02, from docker
Springboard machine 02-1 and it can be used for from docker springboard machines 01-2：
The application programming interfaces provided by interactive module, are synchronized to central database, to store and manage by local daily record
The local daily record of reason.Wherein, the local daily record is to log in daily record and User operation log, and the central database is and the system
It unites corresponding central database.
Further, above-mentioned main docker springboards machine 01 and from docker springboard machines 01-1, main docker springboards machine 02,
And it can be with from docker springboard machines 01-2 from docker springboard machine 02-1：With the presence or absence of respective in periodic detection interactive module
Corresponding version updating packet；If it does, downloading the version updating packet, and it is updated in predetermined point of time, wherein described
Predetermined point of time can be preset random time point, such as each noon on Wednesday 12:00 etc..It is fixed to may be implemented in this way
Phase actively upgrades.
Above-mentioned interactive module, specifically can be used for：Receive administrative staff to above-mentioned main docker springboards machine 01 and from
Docker springboard machines 01-1, main docker springboards machine 02, from docker springboard machine 02-1 and from docker springboard machines 01-2's
Management instruction, and execute the management corresponding with instruction is managed to corresponding main docker springboards machine or from docker springboard machines and grasp
Make, and/or, for receiving user to above-mentioned main docker springboards machine 01 and from docker springboard machines 01-1, main docker is jumped
Trigger 02, the inquiry instruction from docker springboard machine 02-1 and from docker springboard machines 01-2, and to corresponding main docker
Springboard machine executes and the inquiry operation corresponding to inquiry instruction from docker springboard machines.
Specifically, administrative staff can be jumped by the interactive module to above-mentioned main docker springboards machine 01 and from docker
Trigger 01-1, main docker springboards machine 02 are managed behaviour from docker springboard machine 02-1 and from docker springboard machines 01-2
Make, for example, user right operation, cipher key operation, system maintenance etc.；User can inquire the login day of oneself by interactive module
The information such as will, operation log.
Further, which can be also used for：Receive docker Container Managements module 1 and docker Container Managements
The information such as IP information, port mapping that module 2 is sent, and these information are stored in central database, to prevent loss of data,
Ensure data information security.
A kind of cloud springboard machine system based on docker technologies provided in an embodiment of the present invention, including docker containers structure
Module, central management module, docker Container Managements module and docker springboard machines virtualize skill using the docker of lightweight
Art, after docker Container Management modules receive the instruction for the establishment docker springboard machines that central management module is sent out, Ke Yixiang
The multiple docker springboards machines of establishment answered, all docker springboard machines share the resources such as calculating, storage of host hardware, can be with
It realizes the shared of hardware resource, greatly improves resource utilization, avoid the wasting of resources, reduce the cost for disposing virtual springboard machine.
It should be noted that herein, relational terms such as first and second and the like are used merely to a reality
Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation
In any actual relationship or order or sequence.Moreover, the terms "include", "comprise" or its any other variant are intended to
Non-exclusive inclusion, so that the process, method, article or equipment including a series of elements is not only wanted including those
Element, but also include other elements that are not explicitly listed, or further include for this process, method, article or equipment
Intrinsic element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that
There is also other identical elements in process, method, article or equipment including the element.
One of ordinary skill in the art will appreciate that realizing that all or part of step in the above embodiment is can to lead to
It crosses program and is completed to instruct relevant hardware, the program can be stored in computer read/write memory medium, here
The alleged storage medium obtained, such as：ROM/RAM, magnetic disc, CD etc..
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the scope of the present invention.It is all
Any modification, equivalent replacement, improvement and so within the spirit and principles in the present invention, are all contained in protection scope of the present invention
It is interior.
Claims (13)
1. a kind of cloud springboard machine system based on docker technologies, which is characterized in that the system comprises：
Central management module, for disposing the running environment of docker container servers to build docker container servers, and
Docker Container Management modules are built in the docker container servers, which is set as available
State, also, when meeting predetermined conditions, the docker Container Managements into the docker container servers for belonging to available mode
Module sends the instruction for creating main docker springboards machine, and in the docker Container Managements module creation and starts corresponding main
The running environment of the docker springboard machines deployment main docker springboards machine；
Docker Container Management modules, for the instruction in the main docker springboards machine of establishment for receiving central management module transmission
When, create and start corresponding main docker springboards machine, and by the port mapping of the docker container servers to the master
The interactive service port of docker springboard machines, so that user accesses the master by the port of docker container servers
Docker springboard machines；
The main docker springboards machine needs the server that manages for adding, and monitors and records user and needs to manage to described
Server access behavior, wherein every server is under the jurisdiction of unique main docker springboards machine.
2. the system as claimed in claim 1, which is characterized in that the docker Container Managements module is additionally operable to：
When receiving the establishment of central management module transmission from the instruction of docker springboard machines, creates and start and the master
Docker springboard machines are associated at least one from docker springboard machines, and by the port mapping of the docker container servers
To described from the interactive service port of docker springboard machines, so that described in port access of the user by docker container servers
From docker springboard machines；
The central management module, is additionally operable to：In the docker Container Managements module creation and start accordingly from docker
Springboard machine deployment should be from the running environment of docker springboard machines；
It is described to be used for from docker springboard machines：Meet the requirements for access of the different user in geographic location, so that user is logical
Described in crossing the server that its associated main docker springboards machine is added is accessed from docker springboard machines.
3. system as claimed in claim 2, which is characterized in that the central management module is additionally operable to：
Key information in the main docker springboards machine is synchronized to associated all described from docker springboard machines.
4. system as claimed in claim 2, which is characterized in that the central management module is additionally operable to：
The task message of springboard machine is generated, and is sent to the task message by the port of the docker container servers
The corresponding main docker springboards machine or from docker springboard machines；
Correspondingly, the main docker springboards machine or from docker springboard machines, is additionally operable to：
It receives and executes the task message.
5. system as claimed in claim 2, which is characterized in that the central management module is additionally operable to：
Send the instruction deleted main docker springboards machine or deleted from docker springboard machines；
Correspondingly, the docker Container Managements module, is additionally operable to：
It receives the main docker springboards machine of the deletion or deletes the instruction from docker springboard machines, and delete corresponding main docker
Springboard machine or from docker springboard machines.
6. system as claimed in claim 2, which is characterized in that the central management module is additionally operable to：
Monitor whether all main docker springboards machines work normally in preset time range；
When being judged as NO, the main docker springboards machine not worked normally in preset time range is labeled as failure state,
And check this be marked as the main docker springboards machine of failure state whether have it is associated from docker springboard machines be operating normally,
If so,
The slave docker springboards machine of the normal work is arranged as main docker springboards machine, and to the docker Container Managements mould
Block sends the instruction created from docker springboard machines, otherwise,
The instruction for creating main docker springboards machine is sent to the docker Container Managements module；
Correspondingly, the docker Container Managements module, is additionally operable to：
The instruction created from docker springboard machines is received, creates and starts accordingly from docker springboard machines, by the mark
The user information being denoted as in the main docker springboards machine of failure state is synchronized in the slave docker springboards machine newly created；
The instruction for creating main docker springboards machine is received, create and starts corresponding main docker springboards machine, by the mark
The user information being denoted as in the main docker springboards machine of failure state is synchronized in the main docker springboards machine newly created.
7. system as claimed in claim 6, which is characterized in that the central management module is additionally operable to：
It monitors and all whether is worked normally in preset time range from docker springboards machine；
When being judged as NO, the slave docker springboards machine not worked normally in preset time range is labeled as failure state,
And the instruction created from docker springboard machines is sent to the docker Container Managements module；
Correspondingly, the docker Container Managements module, is additionally operable to：
The instruction created from docker springboard machines is received, creates and starts accordingly from docker springboard machines, by the mark
The user information that is denoted as in the main docker springboards machine associated by the slave docker springboards machine of failure state, which is synchronized to, newly to be created
From docker springboard machines.
8. the system as described in claim 2-7 any one, which is characterized in that the central management module is specifically used for：
In the docker Container Managements module creation and starts the main docker springboards machine or after docker springboard machines, adopt
The main docker springboards machine created described in fabric remote deployments or the running environment from docker springboard machines.
9. system as claimed in claim 8, which is characterized in that the central management module is additionally operable to：
Acquisition upgrading specifies main docker springboards machine or after the instruction of docker springboard machines, described in fabric remote deployments
Specify main docker springboards machine or the running environment from docker springboard machines.
10. system as claimed in claim 8, which is characterized in that the central management module is additionally operable to：
All main docker springboards machines and key information and database information from docker springboard machines are periodically backed up, and
It will be in the storage to corresponding cloud disk of backup file.
11. system as claimed in claim 8, which is characterized in that the main docker springboards machine and from docker springboard machines, also
For：
Local daily record is synchronized to central database, wherein the local daily record is to log in daily record and User operation log, described
Central database is central database corresponding with the system.
12. system as claimed in claim 8, which is characterized in that the main docker springboards machine is additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the main docker springboards machine；
If it does,
The version updating packet is downloaded, and the main docker springboards machine is updated in predetermined point of time；
It is described from docker springboard machines, be additionally operable to：
Periodic detection is with the presence or absence of the version updating packet corresponding to the docker springboard machines；
If it does,
The version updating packet is downloaded, and described from docker springboard machines in predetermined point of time update.
13. system as claimed in claim 8, which is characterized in that the system also includes：
Interactive module, for receive administrative staff to the main docker springboards machine or from the management of docker springboard machines instruct,
And execute the management corresponding with instruction is managed to corresponding main docker springboards machine or from docker springboard machines and operate, and/or,
For receiving user to the main docker springboards machine or from the inquiry instruction of docker springboard machines, and to corresponding main docker
Springboard machine executes and the inquiry operation corresponding to inquiry instruction from docker springboard machines.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511021768.8A CN105610946B (en) | 2015-12-30 | 2015-12-30 | A kind of cloud springboard machine system based on docker technologies |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511021768.8A CN105610946B (en) | 2015-12-30 | 2015-12-30 | A kind of cloud springboard machine system based on docker technologies |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105610946A CN105610946A (en) | 2016-05-25 |
| CN105610946B true CN105610946B (en) | 2018-08-03 |
Family
ID=55990480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511021768.8A Active CN105610946B (en) | 2015-12-30 | 2015-12-30 | A kind of cloud springboard machine system based on docker technologies |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105610946B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106911816A (en) * | 2017-02-22 | 2017-06-30 | 郑州云海信息技术有限公司 | The setting system and springboard machine of a kind of port forwarding |
| CN107608763A (en) * | 2017-09-26 | 2018-01-19 | 中国科学院声学研究所 | A kind of method for entering Docker container operations by Web browser |
| CN109819053B (en) * | 2019-03-11 | 2021-07-30 | 携程旅游信息技术（上海）有限公司 | Springboard machine system applied to mixed cloud environment and control method thereof |
| CN111343004B (en) * | 2020-02-11 | 2023-05-26 | 苏宁金融科技(南京)有限公司 | Fabric network remote deployment method, device and system based on Docker |
| CN111639314B (en) * | 2020-05-15 | 2024-01-12 | 京东科技控股股份有限公司 | Container login system, method, server and storage medium |
| CN113765963A (en) * | 2020-07-24 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Data processing method, device, equipment and computer readable storage medium |
| CN113765871B (en) * | 2020-09-09 | 2023-08-04 | 北京沃东天骏信息技术有限公司 | Method and device for managing fort machine |
| CN114979108A (en) * | 2022-05-05 | 2022-08-30 | 北京精一强远科技有限公司 | System, method, equipment and medium for remote assistance and safety audit |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101471926A (en) * | 2007-12-24 | 2009-07-01 | 北京启明星辰信息技术股份有限公司 | Method and system for defining network behavior auditing access rule |
| CN104486346A (en) * | 2014-12-19 | 2015-04-01 | 北京奇艺世纪科技有限公司 | Stepping stone system |
| CN105119913A (en) * | 2015-08-13 | 2015-12-02 | 东南大学 | Web server architecture based on Docker and interactive method between modules |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7885934B2 (en) * | 2004-08-17 | 2011-02-08 | Teleran Technologies, Inc. | Monitoring and auditing system |
-
2015
- 2015-12-30 CN CN201511021768.8A patent/CN105610946B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101471926A (en) * | 2007-12-24 | 2009-07-01 | 北京启明星辰信息技术股份有限公司 | Method and system for defining network behavior auditing access rule |
| CN104486346A (en) * | 2014-12-19 | 2015-04-01 | 北京奇艺世纪科技有限公司 | Stepping stone system |
| CN105119913A (en) * | 2015-08-13 | 2015-12-02 | 东南大学 | Web server architecture based on Docker and interactive method between modules |
Non-Patent Citations (1)
| Title |
|---|
| 基于GateOne软件的堡垒机应用研究;刘瑞成;《金融科技时代》;20141031;正文全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105610946A (en) | 2016-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105610946B (en) | A kind of cloud springboard machine system based on docker technologies | |
| CN111027921B (en) | Service processing method and device, electronic equipment and storage medium | |
| CN102571906B (en) | High availability of machines during patching | |
| CN111274001B (en) | Micro-service management platform | |
| CN102103518B (en) | System for managing resources in virtual environment and implementation method thereof | |
| US8321549B2 (en) | Action execution management for service configuration items | |
| CN102779185B (en) | High-availability distribution type full-text index method | |
| CN102438041B (en) | Upgrade of highly available farm server groups | |
| US8015343B2 (en) | Providing executing programs with reliable access to non-local block data storage | |
| CN102571905B (en) | A kind of method and system for online service supervising the network and machine | |
| CN102523101B (en) | Machine manager service fabric | |
| EP2324429B1 (en) | Providing executing programs with reliable access to non-local block data storage | |
| US20120311377A1 (en) | Replaying jobs at a secondary location of a service | |
| KR20170051471A (en) | Methods and systems for portably deploying applications on one or more cloud systems | |
| CN105706086A (en) | Managed service for acquisition, storage and consumption of large-scale data streams | |
| CN103036986A (en) | Update notification provided on distributed application object | |
| JP2012099048A (en) | Monitoring system and monitoring method for computer | |
| CN102681899A (en) | Virtual computing resource dynamic management system of cloud computing service platform | |
| CN102426543A (en) | Placing objects on hosts using hard and soft constraints | |
| CN114666333A (en) | Control method for cloud computing resource scheduling problem based on multi-tenant theory | |
| EP1522015A1 (en) | Method and system for managing a computer system | |
| CN112925555A (en) | Model management method, device, equipment and storage medium | |
| Tang et al. | Application centric lifecycle framework in cloud | |
| Adeel-Ur-Rehman et al. | System administration of ATLAS TDAQ computing environment | |
| WO2020256797A1 (en) | Object storage system with meta object replication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |