CN107517232A - The scheduling system of cloud desktop - Google Patents
The scheduling system of cloud desktop Download PDFInfo
- Publication number
- CN107517232A CN107517232A CN201610428714.1A CN201610428714A CN107517232A CN 107517232 A CN107517232 A CN 107517232A CN 201610428714 A CN201610428714 A CN 201610428714A CN 107517232 A CN107517232 A CN 107517232A
- Authority
- CN
- China
- Prior art keywords
- cloud desktop
- cloud
- user
- engine
- desktop
- 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.)
- Withdrawn
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/14—Session management
-
- 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/50—Network services
- H04L67/535—Tracking the activity of the user
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The present invention relates to the scheduling system of cloud desktop, the system are built-up by cloud desktop and cloud platform：Cloud platform includes deployment engine, user authentication, Resource Scheduler, session management and Event receiver；Cloud desktop includes Agent action listeners engine and task manager.Cloud desktop dispatching method of the present invention is：True operation of the user in operating system and the influence to operating system are obtained by the action listener engine (agent) affixed one's name in cloud desktop sidepiece, while user really operated and influence sends cloud platform to；Cloud platform is when dispatching cloud desktop, by analyzing the event in cloud desktop, to determine whether user is also using the cloud desktop, and user's application is when being again coupled to cloud desktop, the session connection of previous user and cloud desktop can be again supplied to user, with meet user be continuing with before cloud desktop needs.The present invention can help keeper to be confirmed whether really reclaim cloud desktop, while monitor the internal operation state of cloud desktop, make rational security audit.
Description
Technical field
The present invention relates to cloud computing technology, specifically a kind of scheduling system of cloud desktop.
Background technology
Cloud desktop is a kind of remote virtual desktop, is the desktop in network internal storage storage, i.e. no matter user is at any one
On computer, as long as accessing storage address with regard to the desktop of oneself can be opened.
At present, the scheduling of cloud desktop is mainly based upon running status of the cloud desktop on host.The dispatching method can not
The correct real conditions for perceiving the operation of cloud desktop internal operating system, such as：Although cloud desktop is in running status, user is
Through not using, keeper can not be confirmed whether that cloud desktop can be reclaimed, so cause the waste of resource.Simultaneously administrative staff without
Method monitors the internal operation state of cloud desktop, understands the true operation conditions of cloud desktop, can not carry out rational security audit
Most users are intended to after disconnecting cloud desktop, when using cloud desktop next time, all data and internal memory shape
State is still the state at that time before disconnecting.But because cloud platform can not know that user is to disconnect cloud main frame or stop using cloud
Main frame, so one free time of user or new cloud desktop can only be distributed to for users to use, this undoubtedly causes time and money
The waste in source.
The content of the invention
It is an object of the invention to：A kind of dispatching method of cloud desktop is provided, the session of previous user and cloud desktop is connected
Connect and be again supplied to user, to provide the user conveniently, and save time and resource.
What the present invention was realized in：
The dispatching method of the cloud desktop of the present invention, by cloud desktop side (or its " cloud desktop ") and cloud platform side (or it "
Cloud platform ") it is built-up：That is, user is obtained in operating system by the action listener engine agent affixed one's name in cloud desktop sidepiece
Interior true operation and the influence to operating system, while user is really operated and influence sends cloud platform side to.Yun Ping
Platform side is when dispatching cloud desktop, by analyzing the event in cloud desktop side, to determine whether user is also using the cloud desktop, with
And the session connection of previous user and cloud desktop side can be again supplied to user when being again coupled to cloud desktop side by user's application,
With meet user be continuing with before cloud desktop side needs.
First, the cloud platform side, including program software have：Deployment engine 1-1, user authentication 1-7, Resource Scheduler 1-
2nd, session management 1-3 and Event receiver 1-6.The respective function of these programs is：
Deployment engine 1-1：It is responsible for the deployment of cloud desktop and agent action listener engines 1-4 injection；
Event receiver 1-6：It is responsible for the event collection of all action listener engines (Agent), according to Agent action listeners
Engine source 1-4 is classified and and preserved；
Resource Scheduler 1-2：It is responsible for the scheduling of cloud desktop and the life cycle of cloud desktop, and access control；
Session management 1-3：It is responsible for the session relationship of user and cloud desktop side；
User authentication 1-7：It is responsible for cloud platform side, cloud desktop side, user's system certification of client, safeguards the user of three
Unified and identification.
2nd, the cloud desktop side：Including Agent action listener engine 1-4 and task manager 1.5.
Task manager 1-5：Preserve system, application, all events of three ranks of safety of operating system.
Cloud platform side is when disposing cloud desktop side, meeting automatic deployment Agent action listener engines 1- inside cloud desktop side
4, while unique expression of cloud platform side distribution is recorded, Agent action listener engines 1-4 is responsible for analyzing the system thing of cloud desktop side
Part, and give satisfactory reporting events to cloud platform side, while record the user profile of cloud desktop side, need day to be processed
Will is classified.Because a cloud desktop side can be accessed simultaneously by multiple users, therefore can have the daily record of multiple users in system
Information.Because Agent action listener engines 1-4 have recorded the hosted information of cloud desktop side during deployment, (host is
Agent action listener engines 1-4 host) and the daily record rank analyzed is needed, Agent action listener engines 1-4 only needs
Give satisfactory information reporting to cloud platform side.
The analysis frequency that Agent action listener engine 1-4 are set according to cloud platform, daily record letter of the analysis in real time without analysis
Breath, information format are as follows：
EventID=" event id "
CategoryString=" login/cancellation/disconnection "；
ComputerName=" cloud table title "；
EventType=event types；
Logfile=security logs；
Message=" is logined successfully "
Username=" login username "
Domain=" computer AD domain names "
LoginID=" session id "
LoginType=" Telnet "
LoginProID=" session process ID "
AudType=" is audited successfully "；
TIME_CREATED=" event occurs for event "；
The dispatching method (analysis process) of the cloud desktop of the present invention is as follows：
1) Agent action listeners engine 1-4 obtains log analysis list 2-1, and daily record is believed by system event interface
" event id " -- Event ID are stored in 2-2 in a queue to breath.The analysis interface provided by cloud platform obtains log analysis
Project 2-2.Analysis EventID is completed by comparing last time, the whether analyzed 2-3 of the daily record is judged according to EventID, that is, needs
The EventID of analysis needs to be more than the EventID analyzed；
2) Agent action listeners engine 1-4 according to EventID inverted order by start one by one analyze, until analysis
Untill a suitable daily record；
3) suitable daily record needs the requirement by following condition：Whether CategoryString2-4 meets the requirements, it is necessary to
For one kind in " Loginoff/Break ".Whether Username2-5 is correct, it is necessary to is Agent1-4 host.Audtype2-
Whether 6 is correct, it is necessary to for " examination ＆ verification passes through ".
4) once Agent action listeners engine 1-4 finds first suitable daily record, it will the daily record
Specifying information notice reporting cloud platform 2-7, while stop all analyses, will own in this analysis queue
EventID is labeled as having analyzed, while records EventID2-8, waits the processing of cloud platform.
This method is correctly perceived by the Agent action listener engine analysis event management programs being deployed in cloud desktop
The real conditions of cloud desktop internal operating system operation, help keeper to be confirmed whether really reclaim cloud desktop, save resource；
Facilitate administrative staff to monitor the internal operation state of cloud desktop simultaneously, understand the true operation conditions of cloud desktop, make rational
Security audit.
With reference to the accompanying drawings and examples, the present invention will be further described.
Brief description of the drawings
The principle schematic of the cloud desktop dispatching method of Fig. 1 the present embodiment
Fig. 2 is the analysis procedural block diagram to the present embodiment cloud desktop scheduling system
Fig. 3 implementation processes
Embodiment
A kind of dispatching method of cloud desktop of embodiment
Fig. 1, Fig. 2 are two kinds of form of presentations to the technology of the present invention feature.
Fig. 1 shows the principle of the cloud desktop dispatching method of the present embodiment
It is built-up by cloud desktop side and cloud platform side：
Its cloud platform side, mainly including following programs --- deployment engine 1-1, user authentication 1-7, Resource Scheduler 1-2,
Session management 1-3 and Event receiver 1-6.
Deployment engine 1-1：It is responsible for the deployment of cloud desktop and the injection of action listener engine (agent)；
Event receiver 1-6：It is responsible for the event collection of all action listener engines (Agent), according to action listener engine
(Agent) 1-4 sources are classified and and preserved；
Resource Scheduler 1-2：It is responsible for the scheduling of cloud desktop and the life cycle of cloud desktop, and access control；
Session management 1-3：It is responsible for the session relationship of user and cloud desktop side；
User authentication 1-7：It is responsible for cloud platform side, cloud desktop side, user's system certification of client, safeguards the user of three
Unified and identification.
Its cloud desktop side：Including Agent action listener engine 1-4 and task manager 1.5.
Task manager 1-5：Preserve system, application, all events of three ranks of safety of operating system.
Agent action listener engines 1-4 is responsible for analyzing the system event of cloud desktop side, and by satisfactory reporting events
Cloud platform side is given, while records the user profile of cloud desktop side, need daily record classification to be processed.Due to Agent action listeners
Engine 1-4 have recorded the hosted information of cloud desktop side during deployment, and (host is Agent1-4 action listener engines
Host) and need the daily record rank analyzed, agent only needs that the information reporting of filtering requirement will be met to cloud platform side i.e.
Can.
Fig. 2 is the analysis process to the present embodiment cloud desktop scheduling system
Analysis process is as follows：
1) Agent1-4 action listeners engine is by system event interface, obtains log analysis list 2-1, and by Event
ID is stored in 2-2 in a queue.The analysis interface provided by cloud platform obtains log analysis project 2-2.By in comparison
It is secondary to complete analysis EventID, the whether analyzed 2-3 of the daily record is judged according to EventID, if the daily record has been analyzed so
Cloud platform side will 2-9 stopping analyses
2) Agent1-4 action listeners engine according to EventID inverted order by start one by one analyze, until analysis
Untill a suitable daily record；
3) suitable daily record needs the requirement by following condition：Whether CategoryString meets the requirements 2-4, it is necessary to
For one kind in " Loginoff/Break ".The whether correct 2-5 of Username, it is necessary to be Agent1-4 host.Audtype is
No correct 2-6, it is necessary to for " examination ＆ verification passes through ".
4) once Agent1-4 action listeners engine finds first suitable daily record, it will the specifying information of daily record leads to
Know and report cloud platform 2-7, while 2-9 stops analysis, and the maximum EventID in this analysis queue is labeled as having analyzed,
Mark daily record has been analyzed, and records EventID2-8.The processing of cloud platform is waited simultaneously.
Fig. 3 shows the implementation process of the present embodiment cloud desktop scheduling
Implementation process is as follows：
1. disposing cloud platform first, and dispose multiple cloud desktops and corresponding Agent1-4 action listeners engine
2. user applies for cloud desktop 3-1.One cloud desktop of application program that user passes through client.Client application
Program submits user's application information to cloud platform；
3. carry out user authentication 3-2.After cloud platform receives the application cloud desktop request of user, the certification letter of user is judged
Whether breath is legal；
4. judge to whether there is cloud desktop under the account simultaneously.If it does not exist, then cloud desktop 3- is created in cloud platform
3.After the completion for the treatment of that cloud desktop creates, in cloud desktop On-premise Agent1-4 action listener engines, while recorded in cloud platform
Agent action listeners engine, cloud desktop and the triadic relation of user.Can only possess in each cloud desktop unique agent and
Its agent ID.Simultaneously Agent to cloud platform register 3-5 and record analysis daily record content (including CategoryString and
username)；
5. treat that the Agent1-4 action listener engines in cloud desktop complete registration in cloud platform.Cloud platform is sent out to client
Send the access mode of cloud desktop.User is allowed to use cloud desktop；
6. the Agent1-4 action listeners engine of cloud desktop is due to the managing process being registered as in desktop system, therefore not
Any domestic consumer is allowed to close.Whether it will be by the daily record of real-time analyzer, to judge user also in operation cloud table
Face；
7. when user log off cloud desktop 3-6 operating systems, agent can be obtained by analysis system daily record
CategoryString=" Logoff " and the information of " user of Username=cloud platforms ", determine that use has been logged out in user
Cloud desktop；
Cloud desktop Logout Events 3-7 is obtained, the cloud DESKTOP INFORMATION of user log off is sent to cloud platform.At this moment cloud platform may be used
To choose whether to delete or close main frame 3-8, then user again next time again apply cloud desktop when, cloud platform can create
New cloud desktop is to user
8. when with indoor disconnection cloud desktop operating system 3-9, agent can be obtained by analysis system daily record
CategoryString=" Break " and the information of " user of Username=cloud platforms ", determine the already off use of user
Cloud desktop.The information that Agent disconnects user cloud desktop is sent to cloud platform, and cloud platform obtains cloud desktop disconnected event 3-10,
And remind administrative staff that the desktop is off, while the session information of cloud desktop is stored in session list, record
User and the session information 3-11 of virtual machine.3-12 when application uses cloud desktop again after user disconnects cloud desktop, cloud platform
It will determine that whether the 3-13 cloud desktops session information is also present, the cloud desktop that will can be used if there is cloud platform before user
Login method is sent to user, and assignment record session information 3-14.
Claims (1)
1. the scheduling system of cloud desktop, it is characterised in that：It is built-up by cloud desktop and cloud platform；
The cloud platform, including program software have：Deployment engine (1-1), user authentication (1-7), Resource Scheduler (1-2),
Session management (1-3) and Event receiver (1-6)；These programs perform respective function：
Deployment engine (1-1)：It is responsible for the deployment of cloud desktop and action listener engine agent injection；
Event receiver (1-6)：It is responsible for all action listener engine Agent event collection, according to action listener engine Agent
Classified and and preserved in source；
Resource Scheduler (1-2)：It is responsible for the scheduling of cloud desktop and the life cycle of cloud desktop, and access control；
Session management (1-3)：It is responsible for the session relationship of user and cloud desktop side；
User authentication (1-7：) be responsible for cloud platform, cloud desktop, user's system certification of client, safeguard three user it is unified and
Identification；
The cloud desktop：Including Agent action listeners engine (1-4) and task manager (1.5)；
Task manager (1-5)：Preserve system, application, all events of three ranks of safety of operating system；
Cloud platform when disposing cloud desktop, by cloud platform into each cloud desktop installation and deployment Agent action listener engines (1-
4) and task manager (1-5), while in the unique mark of each Agent action listeners engine (1-4) of cloud platform internal record,
Agent action listeners engine (1-4) is responsible for the system event of analysis cloud desktop, and satisfactory reporting events are put down to cloud
Platform, while record the user profile of cloud desktop, need daily record classification to be processed；
Analysis frequency analysis all system days without analysis that Agent action listeners engine (1-4) configures according to cloud platform
Will；
The dispatching method of cloud desktop is as follows：
1) Agent action listeners engine (1-4) obtains log analysis list (2-1), and daily record is believed by system event interface
Breath " event id "-Event ID are stored in a queue；The analysis interface provided by cloud platform obtains log analysis project
(2-2)；Analysis EventID is completed by comparing last time, judges whether the daily record is analyzed (2-3), that is, needs according to EventID
The EventID of analysis needs to be more than the EventID analyzed；
2) Agent action listeners engine 1-4 being analyzed one by one according to EventID, it is until obtaining a suitable daily record
Only；
3) the suitable daily records of need to meet following condition：Whether CategoryString (2-4) meets the requirements, it is necessary to for "
One kind in Loginoff/Break "；Whether Username (2-5) is correct, it is necessary to for Agent action listeners engine (1-4)
Host；Whether Audtype (2-6) is correct, it is necessary to for " examination ＆ verification passes through "；
4) once Agent action listeners engine (1-4) finds first suitable daily record, the specifying information of daily record can be led to
Know and report cloud platform (2-7), while stop all analyses, all EventID in this analysis queue are labeled as having divided
Analysis, while EventID (2-8) is recorded, wait the processing of cloud platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610428714.1A CN107517232A (en) | 2016-06-16 | 2016-06-16 | The scheduling system of cloud desktop |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610428714.1A CN107517232A (en) | 2016-06-16 | 2016-06-16 | The scheduling system of cloud desktop |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107517232A true CN107517232A (en) | 2017-12-26 |
Family
ID=60720112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610428714.1A Withdrawn CN107517232A (en) | 2016-06-16 | 2016-06-16 | The scheduling system of cloud desktop |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107517232A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112272219A (en) * | 2020-10-16 | 2021-01-26 | 成都华栖云科技有限公司 | Multi-platform automatic cloud desktop publishing method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651743A (en) * | 2009-09-10 | 2010-02-17 | 华耀环宇科技（北京）有限公司 | Remote desktop access system facing to mobilephone terminal user |
| US8046468B2 (en) * | 2009-01-26 | 2011-10-25 | Vmware, Inc. | Process demand prediction for distributed power and resource management |
| CN102469131A (en) * | 2010-11-15 | 2012-05-23 | 中兴通讯股份有限公司 | Terminal based on virtualization technology, system and service providing method |
| CN102566910A (en) * | 2011-12-14 | 2012-07-11 | 广州杰赛科技股份有限公司 | Virtual desktop system and method for refreshing on-screen display of virtual desktop client |
| CN104144172A (en) * | 2013-05-06 | 2014-11-12 | 上海宏第网络科技有限公司 | Cloud platform system and method based on desktop virtualization technology |
-
2016
- 2016-06-16 CN CN201610428714.1A patent/CN107517232A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8046468B2 (en) * | 2009-01-26 | 2011-10-25 | Vmware, Inc. | Process demand prediction for distributed power and resource management |
| CN101651743A (en) * | 2009-09-10 | 2010-02-17 | 华耀环宇科技（北京）有限公司 | Remote desktop access system facing to mobilephone terminal user |
| CN102469131A (en) * | 2010-11-15 | 2012-05-23 | 中兴通讯股份有限公司 | Terminal based on virtualization technology, system and service providing method |
| CN102566910A (en) * | 2011-12-14 | 2012-07-11 | 广州杰赛科技股份有限公司 | Virtual desktop system and method for refreshing on-screen display of virtual desktop client |
| CN104144172A (en) * | 2013-05-06 | 2014-11-12 | 上海宏第网络科技有限公司 | Cloud platform system and method based on desktop virtualization technology |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112272219A (en) * | 2020-10-16 | 2021-01-26 | 成都华栖云科技有限公司 | Multi-platform automatic cloud desktop publishing method |
| CN112272219B (en) * | 2020-10-16 | 2022-11-04 | 成都华栖云科技有限公司 | Multi-platform automatic cloud desktop publishing method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10140453B1 (en) | Vulnerability management using taxonomy-based normalization | |
| US20160294666A1 (en) | Method and system for monitoring server cluster | |
| US9720999B2 (en) | Meta-directory control and evaluation of events | |
| CN104700024B (en) | A kind of method and system of Unix classes host subscriber operational order audit | |
| CN104038466B (en) | Intruding detection system, method and apparatus for cloud computing environment | |
| CN105119757A (en) | Method and system for operation and maintenance automation of enterprise servers | |
| CN105072118A (en) | Login management system and method for call center seat | |
| CN113424157A (en) | Multi-dimensional periodic detection of IoT device behavior | |
| WO2014067428A1 (en) | Full life-cycle management method for sensitive data file based on fingerprint information implantation | |
| US7779113B1 (en) | Audit management system for networks | |
| CN110661811A (en) | Firewall policy management method and device | |
| CN107463839A (en) | A kind of system and method for managing application program | |
| CN103326883A (en) | Uniform safety management and comprehensive audit system | |
| CN106276457A (en) | The method of elevator data management | |
| CN107463490B (en) | Cluster log centralized collection method applied to platform development | |
| CN106557370A (en) | Computing resource dynamic dispatching platform based on Realtime Statistics | |
| WO2015139565A1 (en) | Heterogeneous logging system management configuration | |
| CN105808441B (en) | A kind of various dimensions performance diagnogtics analysis method | |
| CN114780214A (en) | Task processing method, device, system and equipment | |
| CN106649028A (en) | Automated Linux system maintenance task method | |
| CN110633191B (en) | Method and system for monitoring service health of software system in real time | |
| CN107517232A (en) | The scheduling system of cloud desktop | |
| WO2021073415A1 (en) | User management method and device for server out-of-band management system | |
| US20100111094A1 (en) | Relay device, access analysis device, method of controlling relay device, and storage medium for the same | |
| CN113778709B (en) | Interface calling method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20171226 |