CN108009010B - Management device, system, method, electronic device and storage medium for thin client - Google Patents
Management device, system, method, electronic device and storage medium for thin client Download PDFInfo
- Publication number
- CN108009010B CN108009010B CN201711250166.9A CN201711250166A CN108009010B CN 108009010 B CN108009010 B CN 108009010B CN 201711250166 A CN201711250166 A CN 201711250166A CN 108009010 B CN108009010 B CN 108009010B
- Authority
- CN
- China
- Prior art keywords
- task
- information
- thin client
- client
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a management device, a system, a method, an electronic device and a storage medium of a thin client, the management device of the thin client comprises: a cluster control module for communicating with a plurality of thin clients; a task management module comprising: the information collection module is used for communicating with the cluster control module and collecting client information; the task receiving module is used for receiving a task request; the task definition module is used for defining the execution information of the task according to the task request; the task matching module is used for determining a thin client for executing the task; the timing task scheduling module is used for determining the priority of the tasks; the task issuing module is used for issuing the timing tasks to the plurality of thin clients; and the trigger task scheduling module is used for monitoring the determined real-time state of the thin client, and issuing a trigger task if the thin client triggers the trigger condition. The method and the device provided by the invention effectively realize the management of the timing task and the trigger task of the thin client.
Description
Technical Field
The invention relates to the technical field of computer application, in particular to a management device, a management system, a management method, electronic equipment and a storage medium of a thin client.
Background
With the rapid development of cloud computing, virtual desktops are widely popularized and used in the scenes of business office, education and the like, more and more user groups are provided, one thin client obtains one virtual machine on the 'cloud', and once the scale of each dispersed thin client is enlarged, a unified management control system is needed for carrying out information collection, state log monitoring, software upgrading control, task issuing control and the like on the thin clients by using the virtual desktops for office teaching.
Specifically, the thin client removes most of the extraneous functions of the PC, such as CD-ROM, floppy drive, expansion slot, etc. They use a network connection to communicate with a central server and deliver virtual desktops to users, with much of the traffic processing not being done on local hardware, which helps improve security. Thin clients are easy to deploy and include a centralized management tool that an administrator can apply policies to multiple thin clients simultaneously.
Disclosure of Invention
In order to overcome the defects in the prior art, the invention provides a management device, a management system, a management method, an electronic device and a storage medium of a thin client so as to realize the management of the timing task and the trigger task of the thin client.
According to an aspect of the present invention, there is provided a thin client management apparatus for managing a plurality of thin clients, comprising: a cluster control module for communicating with a plurality of said thin clients; a task management module comprising: the information collection module is used for communicating with the cluster control module and collecting client information of a plurality of thin clients; the task receiving module is used for receiving a plurality of task requests; the task definition module is used for defining execution information of tasks according to the received task requests, wherein the tasks comprise timing tasks and trigger tasks, the execution information of the timing tasks at least comprises information of task belongings, execution starting time, execution time span and execution time interval of the tasks, and the execution information of the trigger tasks at least comprises the information of the task belongings and trigger conditions of the trigger tasks; the task matching module is used for matching the information of the task and the client information to determine a thin client for executing the task; the timing task scheduling module is used for determining the priority of the task according to the execution information and/or the client information of the timing task; the task issuing module is used for issuing a timing task, a thin client executing the timing task and the priority of the timing task to the cluster control module, and issuing the timing task to the thin clients by the cluster control module; and the triggering task scheduling module is used for monitoring the real-time state of the thin client determined by the task matching module through the cluster control module, and directly issuing the triggering task through the task issuing module if the determined thin client triggers the triggering condition.
Optionally, the information to which the task belongs includes one or more of IP addresses, MAC addresses, and version numbers of a plurality of thin clients, the client information includes one or more of IP addresses, MAC addresses, and version numbers of the thin clients, and the task matching module determines the thin client that executes the task by one or more of IP address matching, MAC address matching, and version number matching.
Optionally, the task belonging information includes an identifier of a project to which the task belongs, the client information includes an identifier of a thin client, and the task matching module determines the thin client performing the task by querying the thin client identifier.
Optionally, the client information further includes performance parameters of the thin client and/or performance parameters of a virtual server connected to the thin client, and the task matching module is further configured to: matching the task belonging information of the task with the client information to determine a plurality of thin clients for executing the task; and determining one or more thin clients with the met parameters and/or states from the plurality of determined thin clients according to the client information to execute the task.
Optionally, the timed task scheduling module is further configured to: when the task matching module determines that one thin client performs a plurality of timing tasks, determining priorities of the plurality of timing tasks at any time by: the earlier the execution starting time of the timing task is, the higher the priority of the timing task is; the shorter the execution time span of the timing task is, the higher the priority of the timing task is; the longer the execution time interval of the timing task, the higher the priority of the timing task.
Optionally, when the cluster control module issues a timing task and a trigger task to the same thin client, the thin client preferentially executes the trigger task.
Optionally, the cluster control module issues timing tasks and trigger tasks to the thin clients in a synchronous or asynchronous manner, and collects task execution results from the thin clients in the same manner.
Optionally, when the thin client task fails to be executed, the task is returned to the cluster control module, and the thin client for executing the task is determined again through the task management module.
Optionally, the task management module further includes: and the desktop environment distribution module is used for providing a corresponding desktop template according to the task and generating a desktop environment according to the template, wherein the desktop environment is configured in the thin client when the task is executed.
According to still another aspect of the present invention, there is also provided a management system of a thin client, including: a plurality of thin clients; and a management apparatus of the thin client as described above, for managing the plurality of thin clients.
According to still another aspect of the present invention, there is also provided a management method of a thin client, including: collecting client information of a plurality of thin clients; receiving a plurality of task requests; defining execution information of tasks according to the received multiple task requests, wherein the tasks comprise timing tasks and trigger tasks, the execution information of the timing tasks at least comprises task belonging information, execution starting time, execution time span and execution time interval of the tasks, and the execution information of the trigger tasks at least comprises the task belonging information and trigger conditions of the trigger tasks; matching the task belonging information of the task with the client information to determine a thin client for executing the task; for the timed task: determining the priority of the task according to the execution information and/or the client information of the timing task; issuing a timing task, a thin client executing the timing task and the priority of the timing task to the thin client; for the trigger task: and monitoring the real-time state of the thin client, and if the trigger condition is triggered by the determined thin client, issuing a trigger task to the thin client.
According to still another aspect of the present invention, there is also provided an electronic apparatus, including: a processor; a storage medium having stored thereon a computer program which, when executed by the processor, performs the steps as described above.
According to yet another aspect of the present invention, there is also provided a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps as described above.
Compared with the prior art, the task issuing management method and the task issuing management system of the thin client cluster formed by the thin clients are realized through the management system of the thin clients, different task issuing mechanisms are adopted aiming at the timing task and the trigger task, and the management of the whole thin client cluster and the effective execution of the task are realized.
Drawings
The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.
Fig. 1 shows a schematic diagram of a management system of a thin client according to an embodiment of the present invention.
Fig. 2 illustrates a flowchart of a management method of a thin client according to an embodiment of the present invention.
Fig. 3 schematically illustrates a schematic diagram of a computer-readable storage medium in an exemplary embodiment of the disclosure.
Fig. 4 schematically illustrates an electronic device in an exemplary embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In order to solve the defects of the prior art and realize the management of the timing task and the trigger task of the thin client, the invention provides a management device, a system, a method, an electronic device and a storage medium of the thin client.
Referring first to fig. 1, fig. 1 illustrates a schematic diagram of a management system of a thin client according to an embodiment of the present invention.
As shown in fig. 1, the management system of the thin client comprises a plurality of thin clients 110 and management devices of the thin clients (in some embodiments, the thin clients 110 are located locally, and the management devices of the thin clients are located in the cloud). The multiple thin clients 110 communicate with the cloud server and simulate the same independent working environment through the isolation technology of the cloud server and provide different desktop environments for different thin clients 110.
The management means of the thin client is for managing the plurality of thin clients 110. The management apparatus of the thin client includes a cluster control module 120 and a task management module 130. The cluster control module 120 acts as a task management module 130 and a plurality of thin clients 110 middleware, such that the task management module 130 can obtain client information of the thin clients 110 through the cluster control module 120, and the task management module 130 can issue tasks to the thin clients 110 through the cluster control module 120.
The task management module 130 includes an information collection module 131, a task receiving module 132, a task definition module 133, a task matching module 134, a timed task scheduling module 137, a triggered task scheduling module 135, and a task issuing module 136.
The information collection module 131 is configured to communicate with the cluster control module 120 and collect client information of a plurality of thin clients 110. In some embodiments, the client information may include one or more of an IP address, a MAC address, and a version number of the thin client. In some embodiments, the client information may include an identification of a user logged into the thin client. In some embodiments, the client information may include performance parameters of the thin client and/or performance parameters of a virtual server to which the thin client is connected. Specifically, the client information may include all the above information, or only one or more of them according to actual needs.
The task receiving module 132 is configured to receive a plurality of task requests. The task request may be initiated by any thin client connected virtual server. The task request may also be initiated by other terminals.
The task definition module 133 is configured to define execution information of the task according to the received plurality of task requests. The tasks may include timing tasks and trigger tasks. The execution information of the timing task at least comprises task belonged information, execution starting time, execution time span and execution time interval of the task. The execution information of the trigger task at least comprises the task belonging information and the trigger condition of the trigger task. The task definition module 133 may parse the task request to obtain information to which the task included in the task request belongs, an execution start time, an execution time span, an execution time interval, or a trigger condition of the task. Further, the information to which the task belongs may include one or more of IP addresses, MAC addresses, and version numbers of the plurality of thin clients. In some embodiments, a project may have multiple tasks, and the task belonging information may also include an identification of the project to which the task belongs.
The task matching module 134 is configured to match the information to which the task belongs of the task with the client information to determine a thin client that performs the task. Specifically, in some embodiments, the information to which the task belongs includes one or more of an IP address (or IP address range), a MAC address (or MAC address range), and a version number (or version number range) of the plurality of thin clients. The client information includes one or more of an IP address, a MAC address, and a version number of the thin client. The task matching module 134 may determine one or more thin clients 110 performing the task by one or more of IP address matching, MAC address matching, and version number matching.
In some variations, a project may include one or more tasks. An item may be completed by one or more users. To represent the association of an item with a user, an association of the identity of the user with the identity of the item may be stored. The identification of the user may be an account number of the user logging in the thin client. The identification of the item may be a number of the item or a name of the item. In such a variation, the information to which the task belongs includes an identification of an item to which the task belongs, and the client information includes an identification of a user who logs in the thin client. The task matching module 134 determines one or more thin clients performing the task by querying the identity of the user associated with the identity of the project to which the task belongs.
In yet another variation, the client information further includes performance parameters of the thin client and/or performance parameters of a virtual server to which the thin client is connected. The performance parameter may be the CPU current usage, the current network bandwidth, etc. When a plurality of thin clients are determined by means of IP address matching, MAC address matching, version number matching and/or project matching, the task matching module 134 is further configured to determine, according to the client information, one or more thin clients with met parameters and/or states among the plurality of thin clients that are determined, and execute the task.
The timing task scheduling module 137 determines the priority of the task according to the execution information of the timing task and/or the client information. In one embodiment, when the task matching module 134 determines that one thin client executes a plurality of timed tasks, the earlier the execution start time of the timed task, the higher the priority of the timed task. In yet another embodiment, when the task matching module 134 determines that a thin client performs multiple timed tasks, the shorter the execution time span of the timed tasks, the higher the priority of the timed tasks. In another embodiment, when the task matching module 134 determines that a thin client performs multiple timed tasks, the timed tasks have higher priority with longer time intervals between the timed tasks. Specifically, the priority of the final timing task may be determined by using a combination of the above priority determination methods. For example, the tasks may be sorted from morning to evening by execution start time, with the top N% of the tasks getting a score N corresponding to the execution start time; sorting the tasks from short to fast forward according to the execution time span, wherein the first M% of tasks obtain a score M corresponding to the execution starting time; and sequencing the tasks from long to short according to the execution time interval, wherein the first O% of the tasks obtain a score O corresponding to the execution starting time. The final priority value may be obtained using N, M, O and the corresponding weights. The higher the priority value the more priority is to be performed. In another embodiment of the invention, the priority of each task may be included in the task request.
The trigger task scheduling module 135 is configured to listen to the real-time status of the thin client 110 determined by the task matching module through the cluster control module, and send a trigger task to the task issuing module 136 if the determined thin client triggers the trigger condition (e.g., a power-on event). Specifically, the trigger task scheduling module 135, different from the information collecting module 131, may monitor real-time information of an input device (e.g., a keyboard, a mouse, a touch screen) of the thin client 110, and when the input device of the thin client 110 triggers the trigger condition, the trigger task scheduling module 135 sends the trigger task to the task issuing module 136.
The task issuing module 136 is configured to issue a timing task, a thin client that executes the timing task, and a priority of the timing task to the cluster control module, and the cluster control module issues the timing task to a plurality of thin clients. Alternatively, when receiving the trigger task transmitted by the trigger task scheduling module 135, the cluster control module 120 issues the trigger task to the plurality of thin clients 110.
In some embodiments, when the cluster control module 120 issues a timed task and a triggered task to the same thin client 110, the thin client 110 preferentially performs the triggered task. The cluster control module 120 may issue timing tasks and trigger tasks to a plurality of thin clients in a synchronous or asynchronous manner, and collect task execution results from the thin clients 110 in the same manner. Further, when the thin client 110 fails to perform the task, the task is returned to the cluster control module 120, and the thin client 110 performing the task is determined again through the task management module 130.
In a variation of the present invention, the task management module 130 may also include a desktop environment assignment module. The desktop environment distribution module is used for providing a corresponding desktop template according to the task and generating a desktop environment according to the template, and the desktop environment is configured in the thin client when the task is executed. Further, the desktop template may correspond to an identification of a user logging in to the thin client or to an identification of a project described by the task.
In another variation of the present invention, the thin client management system may further include a monitoring module, wherein the monitoring module is in communication with the cluster control module 120, and is configured to obtain real-time information of the input device (e.g., keyboard, mouse, touch screen) of the thin client 110 and the power on/off of the thin client 110 in real time, store and record the real-time information, and generate an active curve of the thin client 110. The active curve may represent whether the thin client 110 is currently powered on and operated. Further, the monitoring module may communicate with the trigger task scheduling module 135 to provide real-time information of the thin client 110 to the trigger task scheduling module 135. A queue may be disposed between the monitoring module and the trigger task scheduling module 135 to control data flow between the monitoring module and the trigger task scheduling module 135.
Referring next to fig. 2, fig. 2 illustrates a management method of a thin client according to an embodiment of the present invention. Fig. 2 shows a total of 8 steps.
Step S210: client information is collected for a plurality of thin clients.
Step S220: a plurality of task requests are received.
Step S230: defining execution information of tasks according to the received multiple task requests, wherein the tasks comprise timing tasks and trigger tasks, the execution information of the timing tasks at least comprises task belonging information, execution starting time, execution time span and execution time interval of the tasks, and the execution information of the trigger tasks at least comprises the task belonging information and trigger conditions of the trigger tasks.
Step S240: and matching the task belonging information of the task with the client information to determine a thin client for executing the task.
Step S250: and judging whether the task is a timing task.
If the task is determined to be a timed task in step S250, step S260 is executed to determine the priority of the task according to the execution information and/or the client information of the timed task.
If the timing task is not determined (i.e., the trigger task) in step S250, step S270 is executed to listen to the determined real-time status of the thin client.
Step S280: for the timing task in the step S260, issuing the timing task, the thin client for executing the timing task and the priority of the timing task to the thin client; and for the triggering task in the step S270, if the determined thin client triggers the triggering condition, the triggering task is issued to the thin client.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium on which a computer program is stored, which when executed by, for example, a processor, can implement the steps of the electronic prescription flow processing method described in any one of the above embodiments. In some possible embodiments, aspects of the present invention may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of this specification, when the program product is run on the terminal device.
Referring to fig. 3, a program product 300 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the tenant computing device, partly on the tenant device, as a stand-alone software package, partly on the tenant computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing devices may be connected to the tenant computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In an example embodiment of the present disclosure, there is also provided an electronic device that may include a processor, and a memory for storing executable instructions of the processor. Wherein the processor is configured to execute the steps of the electronic prescription flow processing method in any one of the above embodiments via execution of the executable instructions.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 4. The electronic device 600 shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 4, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 that couples various system components including the storage unit 620 and the processing unit 610, a display unit 640, and the like.
Wherein the storage unit stores program code executable by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention described in the electronic prescription flow processing method section described above in this specification. For example, the processing unit 610 may perform the steps as shown in fig. 1.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a tenant to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above-mentioned electronic processing flow processing method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (6)
1. A management apparatus of a thin client for managing a plurality of thin clients, comprising:
the cluster control module is used for communicating with the thin clients, issuing timing tasks and trigger tasks to the thin clients in a synchronous or asynchronous mode, and collecting task execution results from the thin clients in the same mode;
a task management module comprising:
the information collection module is used for communicating with the cluster control module and collecting client information of a plurality of thin clients;
the task receiving module is used for receiving a plurality of task requests;
the task definition module is used for defining execution information of tasks according to the received multiple task requests, wherein the tasks comprise timing tasks and trigger tasks, the execution information of the timing tasks at least comprises task belonging information, execution starting time, execution time span and execution time interval of the tasks, and the execution information of the trigger tasks at least comprises the task belonging information and trigger conditions of the trigger tasks;
a task matching module, configured to match information to which a task belongs with the client information to determine a thin client that executes the task, where the client information further includes performance parameters of the thin client and/or performance parameters of a virtual server connected to the thin client, and the task matching module is further configured to: matching the task belonging information of the task with the client information to determine a plurality of thin clients for executing the task; determining one or more thin clients with the met parameters and/or states from the plurality of determined thin clients for executing the task according to the client information to execute the task;
a timing task scheduling module, configured to determine a priority of a task according to the execution information of the timing task and/or the client information, where the timing task scheduling module is further configured to: when the task matching module determines that one thin client executes a plurality of timing tasks, determining the priority of the plurality of timing tasks by any one of the following items: the earlier the execution starting time of the timing task is, the higher the priority of the timing task is; the shorter the execution time span of the timing task is, the higher the priority of the timing task is; the longer the execution time interval of the timing task is, the higher the priority of the timing task is;
the task issuing module is used for issuing a timing task, a thin client executing the timing task and the priority of the timing task to the cluster control module, and the cluster control module issues the timing task to the thin clients; and
a trigger task scheduling module for monitoring the real-time state of the thin client determined by the task matching module through the cluster control module, and directly issuing the trigger task through the task issuing module if the trigger condition is triggered by the determined thin client;
the desktop environment distribution module is used for providing a corresponding desktop template according to the task and generating a desktop environment according to the desktop template, and the desktop environment is configured in the thin client when the task is executed;
the monitoring module is communicated with the cluster control module, acquires real-time information of an input device of the thin client and the on and off of the thin client in real time, stores and records the acquired real-time information of the input device of the thin client and the on and off of the thin client, and generates an active curve of the thin client; the monitoring module is communicated with the trigger task scheduling module to provide real-time information of the thin client to the trigger task scheduling module; a queue is arranged between the monitoring module and the trigger task scheduling module to control the data flow between the monitoring module and the trigger task scheduling module,
the task matching module determines the thin clients executing the tasks in one or more matching modes of IP address matching, MAC address matching and version number matching; or the information to which the task belongs comprises an identifier of a project to which the task belongs, the client information comprises an identifier of a thin client, and the task matching module determines the thin client executing the task by inquiring the thin client identifier.
2. The thin client management apparatus of claim 1,
and when the thin client task fails to be executed, returning the task to the cluster control module, and re-determining the thin client for executing the task through the task management module.
3. A management system of a thin client, comprising:
a plurality of thin clients; and
the thin client management apparatus of claim 1 or 2, for managing the plurality of thin clients.
4. A management method of a thin client, applied to the management apparatus of a thin client according to claim 1, comprising:
collecting client information of a plurality of thin clients;
receiving a plurality of task requests;
defining execution information of tasks according to the received multiple task requests, wherein the tasks comprise timing tasks and trigger tasks, the execution information of the timing tasks at least comprises task belonging information, execution starting time, execution time span and execution time interval of the tasks, and the execution information of the trigger tasks at least comprises the task belonging information and trigger conditions of the trigger tasks;
matching the information to which the task belongs of the task with the client information to determine a thin client for executing the task, wherein the client information further comprises performance parameters of the thin client and/or performance parameters of a virtual server connected with the thin client, and the step of matching the information to which the task belongs of the task with the client information to determine the thin client for executing the task further comprises: matching the task belonging information of the task with the client information to determine a plurality of thin clients for executing the task; determining one or more thin clients with the met parameters and/or states from the plurality of determined thin clients for executing the task according to the client information to execute the task;
for the timed task:
determining the priority of tasks according to the execution information of the timing tasks and/or the client information, and when the task matching module determines that one thin client executes a plurality of timing tasks, determining the priority of the plurality of timing tasks through any one of the following items: the earlier the execution starting time of the timing task is, the higher the priority of the timing task is; the shorter the execution time span of the timing task is, the higher the priority of the timing task is; the longer the execution time interval of the timing task is, the higher the priority of the timing task is;
issuing a timing task, a thin client executing the timing task and the priority of the timing task to the thin client;
for the trigger task:
monitoring the real-time state of the thin client, and if the trigger condition is triggered by the thin client, issuing a trigger task to the thin client;
the information of the task comprises one or more of IP addresses, MAC addresses and version numbers of a plurality of thin clients, the client information comprises one or more of the IP addresses, the MAC addresses and the version numbers of the thin clients, and the thin clients executing the task are determined in one or more matching modes of IP address matching, MAC address matching and version number matching; or the information to which the task belongs comprises an identification of a project to which the task belongs, the client information comprises an identification of a thin client, and the thin client for executing the task is determined by inquiring the identification of the thin client.
5. An electronic device, characterized in that the electronic device comprises:
a processor;
storage medium having stored thereon a computer program which, when being executed by the processor, carries out the method of claim 4.
6. A storage medium, having stored thereon a computer program which, when executed by a processor, performs the method of claim 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711250166.9A CN108009010B (en) | 2017-12-01 | 2017-12-01 | Management device, system, method, electronic device and storage medium for thin client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711250166.9A CN108009010B (en) | 2017-12-01 | 2017-12-01 | Management device, system, method, electronic device and storage medium for thin client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108009010A CN108009010A (en) | 2018-05-08 |
| CN108009010B true CN108009010B (en) | 2021-03-23 |
Family
ID=62056020
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711250166.9A Active CN108009010B (en) | 2017-12-01 | 2017-12-01 | Management device, system, method, electronic device and storage medium for thin client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108009010B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109101267B (en) * | 2018-07-31 | 2021-11-23 | 上海携程金融信息服务有限公司 | Application release management method and device, electronic equipment and storage medium |
| CN109545292A (en) * | 2018-11-09 | 2019-03-29 | 医渡云（北京）技术有限公司 | A kind of management method, equipment and the medium of medical research follow-up task |
| CN112698927B (en) * | 2019-10-23 | 2024-05-28 | 杭州海康威视数字技术股份有限公司 | Bidirectional communication method, bidirectional communication device, electronic equipment and machine-readable storage medium |
| CN113765958B (en) * | 2020-06-11 | 2024-05-28 | 北京京东振世信息技术有限公司 | Job task processing method and job client |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080148273A1 (en) * | 2006-12-15 | 2008-06-19 | Institute For Information Industry | Dynamic voltage scaling scheduling mechanism for sporadic, hard real-time tasks with resource sharing |
| CN103544064A (en) * | 2013-10-28 | 2014-01-29 | 华为数字技术（苏州）有限公司 | Cloud computing method, cloud management platform and client |
| CN104765639A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Timed task scheduling system and method |
| CN106528297A (en) * | 2016-11-14 | 2017-03-22 | 山东浪潮云服务信息科技有限公司 | System for managing tasks |
-
2017
- 2017-12-01 CN CN201711250166.9A patent/CN108009010B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080148273A1 (en) * | 2006-12-15 | 2008-06-19 | Institute For Information Industry | Dynamic voltage scaling scheduling mechanism for sporadic, hard real-time tasks with resource sharing |
| CN103544064A (en) * | 2013-10-28 | 2014-01-29 | 华为数字技术（苏州）有限公司 | Cloud computing method, cloud management platform and client |
| CN104765639A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Timed task scheduling system and method |
| CN106528297A (en) * | 2016-11-14 | 2017-03-22 | 山东浪潮云服务信息科技有限公司 | System for managing tasks |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108009010A (en) | 2018-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108009010B (en) | Management device, system, method, electronic device and storage medium for thin client | |
| WO2021036936A1 (en) | Method and apparatus for allocating resources and tasks in distributed system, and system | |
| US10977076B2 (en) | Method and apparatus for processing a heterogeneous cluster-oriented task | |
| CN111045911B (en) | Performance test method, performance test device, storage medium and electronic equipment | |
| CN110874272A (en) | Resource allocation method and device, computer readable storage medium and electronic device | |
| US11151505B1 (en) | Automatic analysis of organization process/operations data | |
| CN109672722B (en) | Data deployment method and device, computer storage medium and electronic equipment | |
| CN111679911B (en) | Management method, device, equipment and medium of GPU card in cloud environment | |
| CN109684038B (en) | Docker service container log processing method and device and electronic equipment | |
| US20180288143A1 (en) | Managing idle and active servers in cloud data centers | |
| US10255127B2 (en) | Optimized diagnostic data collection driven by a ticketing system | |
| US10628230B2 (en) | Software based collection of performance metrics for allocation adjustment of virtual resources | |
| US20230222004A1 (en) | Data locality for big data on kubernetes | |
| US10114722B2 (en) | Test of the execution of workloads in a computing system | |
| US20210286647A1 (en) | Embedded persistent queue | |
| CN113760638A (en) | Log service method and device based on kubernets cluster | |
| US20230342369A1 (en) | Data processing method and apparatus, and electronic device and storage medium | |
| TWI760022B (en) | Computer-implemented system and method for diagnosis of live virtual server performance data | |
| US11061743B2 (en) | Event loop optimization through event ordering | |
| US10680912B1 (en) | Infrastructure resource provisioning using trace-based workload temporal analysis for high performance computing | |
| CN113778658A (en) | Task allocation method and device, electronic equipment and storage medium | |
| Brim et al. | Monitoring extreme-scale Lustre toolkit | |
| CN111708677A (en) | Cloud hard disk usage amount acquisition method in cloud computing environment | |
| US20230418598A1 (en) | Modernizing application components to reduce energy consumption | |
| US9436523B1 (en) | Holistic non-invasive evaluation of an asynchronous distributed software process |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |