Cloud desktop platform management system and fault processing method of cloud desktop platform
Through the cooperation of the monitoring and management of the cloud desktop platform management system, the problem of low operation and maintenance efficiency of the cloud desktop platform is solved, and the rapid repair and management of faults is achieved, and the stability and operation and maintenance efficiency of the platform are improved. .
Patent Information
- Application Number
- CN202410962306.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2024-11-15
AI Technical Summary
The operation and maintenance efficiency of the cloud desktop platform is low, resulting in increased management complexity and inefficient fault handling.
It provides a cloud desktop platform management system, including monitoring management module, fault processing module and work order management module. By monitoring the operating status of the platform, it obtains alarm information, generates work orders and performs fault repairs, and realizes multi-module collaborative management.
It improves the operation and maintenance efficiency of the cloud desktop platform, and achieves rapid repair and management of faults through multi-module collaboration, improving the stability and reliability of the platform.
Smart Images

Figure CN118972384A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of cloud service technology, and in particular to a cloud desktop platform management system and a cloud desktop platform fault handling method. Background Art
[0002] With the booming development of cloud desktops, cloud desktops are increasingly favored by various enterprises. Due to its complex technology, cloud desktops have greatly increased the complexity of operation and maintenance management. Traditional cloud desktop operation and maintenance are mostly based on self-application and management concepts. The current scale of cloud desktop platforms and the large number of enterprise departments involved have led to confusion in the operation and maintenance mechanism of cloud desktops, resulting in low operation and maintenance efficiency. Summary of the invention
[0003] The embodiments of the present application provide a cloud desktop platform management system and a cloud desktop platform fault handling method to at least solve the technical problem of low cloud desktop operation and maintenance efficiency in related technologies.
[0004] According to one aspect of an embodiment of the present application, a cloud desktop platform management system is provided, including: a monitoring management module, a fault handling module and a work order management module; the monitoring management module is used to monitor the operating status of the cloud desktop platform and obtain alarm information of the cloud desktop platform; the fault handling module is used to receive fault information and complete the repair of the fault corresponding to the fault information according to the fault information, and the fault information is generated according to the alarm information; the work order management module is used to create a work order based on the alarm information, and send the work order to the fault handling module, and the fault handling module generates the fault information according to the work order.
[0005] Optionally, the fault handling module includes: a first receiving unit and a processing unit; the first receiving unit is used to receive the fault information, and the fault information includes: a fault level and a corresponding repair plan; the processing unit is used to complete the repair of the fault according to the repair plan.
[0006] Optionally, the processing unit is also used to determine that the fault is repaired according to the repair plan when the fault level is a first level fault; when the fault level is a second level fault, obtain a predetermined emergency plan and handle the fault according to the emergency plan; receive a fault handling result, and the fault handling result is used to indicate whether the fault is repaired, wherein the fault severity corresponding to the first level fault and the second level fault increases in sequence.
[0007] Optionally, the work order management module includes: a creation unit, a first sending unit and a second receiving unit; the creation unit is used to create the work order based on the alarm information; the first sending unit is used to send the work order to a first terminal corresponding to the secondary operation and maintenance account to obtain the fault information, and when the fault information indicates that the fault level is a second-level fault, send the work order to a second terminal corresponding to the third-level operation and maintenance account; the second receiving unit is used to receive a fault handling result, and the fault handling result is used to indicate whether the fault is repaired, wherein the authority of the third-level operation and maintenance account is greater than the authority of the second-level operation and maintenance account.
[0008] Optionally, the system also includes: a change management module, the change management module includes: a third receiving unit, a second sending unit and a change unit; the third receiving unit is used to receive a change request, the change request is sent through a third terminal corresponding to the first-level account; the second sending unit is used to send the change request to a fourth terminal corresponding to the second-level account for verification, and after the change request is verified, send the change request to a fifth terminal corresponding to the third-level account for secondary verification, and if the change request passes the secondary verification, send a change instruction to the third terminal, the change instruction is used to indicate that the change request has passed the verification; the third receiving unit is also used to receive the verification result sent by the fourth terminal and the secondary verification result sent by the fifth terminal, and receive the change result corresponding to the change request, wherein the authority of the first-level account is lower than that of the second-level account.
[0009] Optionally, the system also includes: a capacity management module, which is used to collect historical resource usage data of the server corresponding to the cloud desktop platform, and build a capacity analysis model based on the historical data; use the capacity analysis model to analyze the resource usage data of the server at the current moment to obtain target resource usage data of the server within a preset time period; and adjust the resources of the server according to the target resource usage data.
[0010] Optionally, the system further includes: a business continuity management module, configured to generate an emergency plan for repairing the second level failure.
[0011] Optionally, the system also includes: a problem management module; the problem management module is used to receive feedback information reported by multiple user terminals, the feedback information is used to indicate problems generated during the operation of the cloud desktop platform, and to send the feedback information to corresponding processing accounts respectively, and receive processing results fed back by the processing accounts.
[0012] According to another aspect of an embodiment of the present application, a fault handling method for a cloud desktop platform is also provided, including: monitoring the operating status of the cloud desktop platform through a monitoring management module to obtain alarm information; generating a work order based on the alarm information through a work order management module, and sending the work order to a first terminal corresponding to a second-level operation and maintenance account to obtain the fault information, and when the fault information indicates that the fault level is a second-level fault, sending the work order to a second terminal corresponding to a third-level operation and maintenance account to obtain an emergency plan, wherein the authority of the third-level operation and maintenance account is greater than the authority of the second-level operation and maintenance account; when the fault level is a first-level fault, determining through the fault management module to complete the repair of the fault according to the repair plan in the fault information, and when the fault level is a second-level fault, obtaining a predetermined emergency plan and handling the fault according to the emergency plan.
[0013] According to another aspect of the embodiments of the present application, a computer program product is also provided, including computer instructions, which, when executed by a processor, implement the fault handling method of the above-mentioned cloud desktop platform.
[0014] In an embodiment of the present application, a cloud desktop platform management system is provided, including: a monitoring management module, a fault handling module and a work order management module; the monitoring management module is used to monitor the operating status of the cloud desktop platform and obtain the alarm information of the cloud desktop platform; the fault handling module is used to receive fault information and complete the repair of the fault corresponding to the fault information according to the fault information, and the fault information is generated according to the alarm information; the work order management module is used to create a work order based on the alarm information, and send the work order to the fault handling module, and the fault handling module generates the fault information according to the work order, thereby achieving the purpose of managing the cloud desktop platform through the cooperation of multiple functional modules, thereby realizing the technical effect of improving the operation and maintenance efficiency of the cloud desktop platform, and then solving the technical problem of low operation and maintenance efficiency of the cloud desktop in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0016] Figure 1 It is a structural block diagram of a cloud desktop platform management system according to an embodiment of the present application;
[0017] Figure 2 is a structural diagram of a fault processing module according to an embodiment of the present application;
[0018] Figure 3is a structural diagram of a work order management module according to an embodiment of the present application;
[0019] Figure 4 This is a schematic diagram of an alarm event processing flow according to an embodiment of the present application;
[0020] Figure 5 This is a flow chart of an alarm work order according to an embodiment of the present application;
[0021] Figure 6 is a structural diagram of a change management module according to an embodiment of the present application;
[0022] Figure 7 is a schematic diagram of a change process according to an embodiment of the present application;
[0023] Figure 8 is a schematic diagram of the structure of another cloud desktop platform management system according to an embodiment of the present application;
[0024] Fig. 9 is a schematic diagram of a capacity management process according to an embodiment of the present application;
[0025] Fig.10 It is a flowchart of a fault handling method for a cloud desktop platform according to an embodiment of the present application. DETAILED DESCRIPTION
[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.
[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0028] In order to solve the problems existing in the related art, the present application embodiment provides a cloud desktop platform management system, such as Figure 1 As shown, including:
[0029] A monitoring management module 10, a fault handling module 20 and a work order management module 30; the monitoring management module 10 is used to monitor the operating status of the cloud desktop platform and obtain the alarm information of the cloud desktop platform; the fault handling module 20 is used to receive fault information and complete the repair of the fault corresponding to the fault information according to the fault information, and the fault information is generated according to the alarm information; the work order management module 30 is used to create a work order based on the alarm information and send the work order to the fault handling module 20, and the fault handling module 20 generates the fault information according to the work order.
[0030] It should be noted that the monitoring management module 10 can use pre-set monitoring components to automatically monitor the cloud desktop platform, including scheduled inspections, automatic alarms, etc. The monitoring covers different levels and dimensions from switches, load balancing, firewalls, servers and other hardware equipment, desktop virtualization, lines, and services. All monitoring items that affect the stability of the platform are fully set, including CPU utilization, memory usage, network traffic, number of user connections, and system response time, etc., so that the hidden dangers of the entire platform can be known at the first time to avoid the problem from further expansion.
[0031] The work order management module 30 is used to create and dispatch work orders. An optional work order is an alarm work order, which is created when an alarm message is received.
[0032] like Figure 2 As shown, the fault processing module 20 includes: a first receiving unit 201 and a processing unit 202; the first receiving unit 201 is used to receive the fault information, and the fault information includes: a fault level and a corresponding repair plan; the processing unit 202 is used to complete the repair of the fault according to the repair plan.
[0033] Among them, the processing unit 202 is also used to determine that the fault is repaired according to the repair plan when the fault level is a first-level fault; when the fault level is a second-level fault, obtain a predetermined emergency plan and handle the fault according to the emergency plan; receive a fault handling result, and the fault handling result is used to indicate whether the fault is repaired, wherein the fault severity corresponding to the first-level fault and the second-level fault increases in sequence.
[0034] like Figure 3 As shown, the work order management module 30 includes:
[0035] A creation unit 301, a first sending unit 302 and a second receiving unit 303; the creation unit 301 is used to create the work order based on the alarm information; the first sending unit 302 is used to send the work order to a first terminal corresponding to a second-level operation and maintenance account to obtain the fault information, and when the fault information indicates that the fault level is a second-level fault, send the work order to a second terminal corresponding to a third-level operation and maintenance account; the second receiving unit 303 is used to receive a fault handling result, and the fault handling result is used to indicate whether the fault is repaired, wherein the authority of the third-level operation and maintenance account is greater than that of the second-level operation and maintenance account.
[0036] It should be noted that the work orders created by the work order management module 30 also include: declaration work orders, and the declaration work order types can be divided into the following categories: access application, port opening, security vulnerability scanning, data backup, resource opening, resource adjustment, VPN service and others.
[0037] It is understandable that the fault handling module 20 is used to restore services as quickly as possible and reduce its adverse impact on the business when a cloud desktop platform fails, so as to ensure service quality and availability level. The process of executing tasks by the fault management module involves event detection and recording, event classification and support, event investigation and diagnosis, event resolution and recovery, and event closure. Taking the event as an alarm as an example, Figure 4 A schematic diagram of an alarm event processing flow is shown, such as Figure 4 As shown:
[0038] In the first step, the monitoring management module 10 detects alarm information and sends the alarm information to the work order management module 30. The work order management module 30 creates an alarm work order based on the alarm information and sends the alarm work order to the first terminal corresponding to the secondary operation and maintenance account;
[0039] In the second step, the first terminal receives the order and immediately determines the impact scope of the fault level assessment. The first terminal generates a fault repair plan for the first-level fault. In an optional manner, the fault repair plan received by the first terminal is pre-deposited by the second-line operation and maintenance personnel through the second-level operation and maintenance account; if the first terminal determines that the fault level is a second-level fault, the work order management module 30 sends the alarm information to the second terminal corresponding to the third-level operation and maintenance account;
[0040] In the third step, the second terminal corresponding to the third-level operation and maintenance account starts the emergency plan and repairs the fault according to the emergency plan. If the fault is not repaired within the preset time, an alarm message will be sent to the operation and maintenance expert, who will repair the fault.
[0041] Step 4: After troubleshooting, the operation and maintenance team will summarize the troubleshooting results and compile them into a fault replay report, which will be emailed back within 24 hours.
[0042] Figure 5 A flow chart of alarm work order flow is shown, such as Figure 5 As shown, when the work order management module 30 receives the alarm information, the alarm is aggregated and a dispatch work order is created. The operation and maintenance personnel process the work order after receiving it. If it cannot be processed, the work order will be upgraded and dispatched to an expert for processing. After the work order processing is completed and the alarm is confirmed to be restored, the corresponding work order will be entered into the knowledge base for subsequent query and browsing.
[0043] In some embodiments of the present application, the system further includes: a change management module, such as Figure 6 As shown, the change management module 40 includes: a third receiving unit 401, a second sending unit 402 and a change unit 403; the third receiving unit 401 is used to receive a change request, and the change request is sent through a third terminal corresponding to the first-level account; the second sending unit 402 is used to send the change request to a fourth terminal corresponding to the second-level account for verification, and after the change request is verified, send the change request to a fifth terminal corresponding to the third-level account for secondary verification, and if the change request passes the secondary verification, send a change instruction to the third terminal, and the change instruction is used to indicate that the change request has passed the verification; the third receiving unit 401 is also used to receive the verification result sent by the fourth terminal and the secondary verification result sent by the fifth terminal, and receive the change result corresponding to the change request, wherein the authority of the first-level account is lower than that of the second-level account.
[0044] Figure 7 A schematic diagram of a change process is shown, such as Figure 7 As shown in the figure, before the cloud desktop platform is changed, the first-level account sends a change request, which includes: the reason for the change, the content of the operation, the change risk assessment, and the emergency plan when the change is abnormal. If necessary, a pre-change test is required, and the specific test time and test plan are proposed together. After receiving the change request, the second-level account reviews and verifies the change request within the specified time. After the verification is passed, the platform performs the relevant change operations and confirms the results after the change is completed.
[0045] like Figure 8 As shown, the system also includes: a resource management module and a capacity management module, wherein the capacity management module is used to collect the resource usage history data of the server corresponding to the cloud desktop platform, and build a capacity analysis model based on the historical data; use the capacity analysis model to analyze the resource usage data of the server at the current moment to obtain the target resource usage data of the server within a preset time period; and adjust the resources of the server according to the target resource usage data.
[0046] The resource management module is used to manage, maintain and update the platform resources throughout their life cycle. After the capacity management evaluates and plans the resources, the resources are applied for. After the resource application is completed, the resources are continuously operated and maintained and their status is monitored during the use period. When the resources expire or the service is offline, the resources are recycled. Finally, the resources are configured, the capacity is updated and managed.
[0047] Among them, resource management refers to the management, maintenance and update of cloud desktop terminal resources throughout their life cycle. The resource life cycle management process includes: 1. Resource application process: application, review and confirmation, approval, resource delivery; 2. Resource operation and maintenance, status monitoring; 3. Resource recycling (expiration, business offline): offline notification, review and confirmation, backup and archiving, resource release; 4. Resource configuration, capacity change, management update.
[0048] The capacity management module builds a capacity model based on the server and container list to manage the capacity in the cloud platform environment and better support system operation and maintenance. The model determines the appropriate resource configuration by monitoring and analyzing the indicator data of servers and containers, evaluating the support capacity of cloud desktop basic resources, and predicting workload requirements, so that the system construction plan can be allocated on demand.
[0049] Furthermore, a capacity model is deployed in the capacity management module to plan the capacity occupied by the cloud desktop platform. The general steps and processes of the construction are as follows. Fig. 9 As shown:
[0050] The first step is data collection: First, you need to collect the metrics data of the server and container. These metrics can include CPU usage, memory utilization, disk space, and network bandwidth. Data collection can be achieved through monitoring tools or metric collection systems.
[0051] The second step is data storage and processing: The collected indicator data can be stored in a database or data warehouse for subsequent processing and analysis. This step requires cleaning, aggregation and transformation of the data in preparation for capacity analysis.
[0052] The third step is capacity analysis: Using the stored and processed data, capacity analysis is performed to understand the current resource usage and trends. This includes statistics and analysis of resource utilization of servers and containers, for example, viewing average, peak and valley data, as well as time patterns and periodicity of resource usage.
[0053] Step 4: Workload Forecasting: Based on historical data and trend analysis, workload demand forecasting can be performed using forecasting algorithms. This is done based on previous workload patterns and business needs in order to identify future resource requirements and peak loads.
[0054] Step 5: Capacity planning: Based on the results of capacity analysis and workload forecasting, capacity planning is performed. This includes determining the resource configuration of servers and containers, such as the number of servers, container size, and resource allocation ratio. The goal is to ensure that resources are sufficient and used efficiently according to demand.
[0055] Step 6: Capacity management and optimization: Once capacity planning is done, capacity management and optimization are required. This includes monitoring the indicator data of servers and containers, tracking resource usage in real time, promptly discovering and solving resource bottlenecks and efficiency issues, and adjusting capacity planning based on actual conditions.
[0056] In some embodiments of the present application, the system further includes: a business continuity management module, configured to generate an emergency plan for repairing the second level failure.
[0057] It is understandable that business continuity management is to develop emergency recovery plans for network and infrastructure failures, conduct recovery drills, and ensure that when equipment fails, the normal operation of the system can be restored as soon as possible by executing the emergency plan. Among them, emergency plan drills are generally triggered by agreement, crisis or hidden dangers. According to the lessons learned from the drill work, a drill report is issued to explain the causes of the problems that occurred, formulate rectification plans, and then confirm the new emergency plan. Successful emergency plans should be solidified in a timely manner to provide reference and guidance for the handling of subsequent related issues, so as to minimize the impact of failures on customer business.
[0058] In some embodiments of the present application, the system also includes: a problem management module; a problem management module, used to receive feedback information reported by multiple user terminals, the feedback information is used to indicate problems generated during the operation of the cloud desktop platform, and to send the feedback information to corresponding processing accounts respectively, and receive processing results fed back by the processing accounts.
[0059] Specifically, the steps of executing tasks in the problem management module are divided into: problem collection, classification and assignment. Collect problems reported by users, sort them according to their priority and assign them to corresponding team members, diagnose the root cause of the problem and determine the activities required for problem solutions. Problems are tracked and recorded until they are resolved to ensure timely response and resolution of problems.
[0060] Based on the cloud desktop management system provided in the embodiment of the present application, the embodiment of the present application also provides a method for troubleshooting a cloud desktop platform, such as Fig.10 As shown, including:
[0061] Step S901, monitoring the operation status of the cloud desktop platform through the monitoring management module to obtain alarm information;
[0062] Step S902: Generate a work order based on the alarm information through a work order management module, and send the work order to a first terminal corresponding to the second-level operation and maintenance account to obtain the fault information, and send the work order to a second terminal corresponding to the third-level operation and maintenance account to obtain an emergency plan when the fault information indicates that the fault level is a second-level fault, wherein the authority of the third-level operation and maintenance account is greater than that of the second-level operation and maintenance account;
[0063] Step S903, when the fault level is a first level fault, the fault management module determines to complete the fault repair according to the repair plan in the fault information; when the fault level is a second level fault, obtains a predetermined emergency plan and handles the fault according to the emergency plan.
[0064] It should be noted that the cloud desktop platform management system provided in the embodiment of the present application is constructed based on ITIL (Information Technology Infrastructure Library), which highlights the standardized operation and maintenance process of the cloud desktop platform, and constructs the above-mentioned cloud desktop platform management system by combining the various modules in ITIL with the characteristics of the cloud desktop platform. The cloud desktop management system provided in the embodiment of the present application attaches importance to the importance of event / fault management, change management, capacity management, business continuity management, etc., especially for the capacity management part, by building a capacity model to predict workload requirements, so that the system construction plan can be allocated on demand. The beneficial effects of this method include providing high-quality management services, improving operation and maintenance efficiency, and enhancing platform stability.
[0065] It is understandable that the cloud desktop management system provided in the embodiment of the present application comprehensively applies the key concepts and best practices in the ITIL framework, and is combined with cloud desktop operation and maintenance management, such as monitoring management, event / fault management, change management, resource management, problem management, work order management, capacity management, business continuity management, etc. By effectively combining these concepts, the value proposition and long-term planning of cloud desktop services can be clarified, and a set of comprehensive methods suitable for cloud desktop platform management and operation can be formed to ensure standardized processes and effective management in each link, thereby improving the quality and efficiency of after-sales operation and maintenance of cloud desktop projects. It covers key links such as monitoring management, event / fault management, change management, resource management, problem management, work order management, capacity management, and business continuity management, and realizes effective control and coordination of the entire process of cloud desktop platform operation and maintenance. This enables the operation and maintenance team to manage the platform comprehensively and effectively, ensuring the stability and reliability of the cloud desktop platform. Using a pre-built capacity model, by monitoring and analyzing the indicator data of servers and containers, and evaluating the support capabilities of cloud desktop basic resources, predicting workload requirements, to determine appropriate resource configuration, so that system construction planning can be allocated on demand. Business continuity management is incorporated into the ITIL system to minimize the impact of failures on customer business. Fault management and IT monitoring systems are connected, and events are identified and classified to complete the recording, processing, query, review, and distribution of events, so as to repair the business as soon as possible when an event occurs. Event management ensures the continuous and stable operation of the project by responding to and resolving events in a timely manner.
[0066] An embodiment of the present application also provides a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the fault handling method of the cloud desktop platform in the present application are implemented.
[0067] An embodiment of the present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the fault handling method of the cloud desktop platform in the present application.
[0068] An embodiment of the present application also provides a computer program, which, when executed by a processor, implements the steps of the fault handling method of the cloud desktop platform in the present application.
[0069] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0070] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.
[0071] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
[0072] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0073] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0074] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a communication device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.
[0075] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A cloud desktop platform management system, characterized in that: include: Monitoring management module, fault handling module and work order management module; The monitoring management module is used to monitor the operating status of the cloud desktop platform and obtain alarm information of the cloud desktop platform; The fault processing module is used to receive fault information and complete the repair of the fault corresponding to the fault information according to the fault information, wherein the fault information is generated according to the alarm information; The work order management module is used to create a work order based on the alarm information and send the work order to the fault processing module, and the fault processing module generates the fault information according to the work order.
2. The system according to claim 1, characterized in that The fault processing module comprises: a first receiving unit and a processing unit; The first receiving unit is used to receive the fault information, wherein the fault information includes: a fault level and a corresponding repair solution; The processing unit is used to complete the repair of the fault according to the repair plan.
3. The system according to claim 2, characterized in that The processing unit is also used to When the fault level is a first level fault, determining to complete the repair of the fault according to the repair plan; When the fault level is a second-level fault, obtaining a predetermined emergency plan and handling the fault according to the emergency plan; A fault handling result is received, where the fault handling result is used to indicate whether the fault is repaired, wherein the fault severities corresponding to the first-level fault and the second-level fault are in ascending order.
4. The system according to claim 1, characterized in that The work order management module includes: A creating unit, a first sending unit and a second receiving unit; The creation unit is used to create the work order based on the alarm information; The first sending unit is used to send the work order to a first terminal corresponding to the second-level operation and maintenance account to obtain the fault information, and send the work order to a second terminal corresponding to the third-level operation and maintenance account when the fault information indicates that the fault level is a second-level fault; The second receiving unit is used to receive a fault handling result, where the fault handling result is used to indicate whether the fault is repaired, wherein the authority of the third-level operation and maintenance account is greater than the authority of the second-level operation and maintenance account.
5. The system according to claim 1, characterized in that The system further includes: a change management module, the change management module including: a third receiving unit, a second sending unit and a changing unit; The third receiving unit is used to receive a change request, where the change request is sent via a third terminal corresponding to the first-level account; The second sending unit is used to send the change request to a fourth terminal corresponding to the second-level account for verification, and after the change request passes the verification, send the change request to a fifth terminal corresponding to the third-level account for secondary verification, and if the change request passes the secondary verification, send a change instruction to the third terminal, wherein the change instruction is used to indicate that the change request passes the verification; The third receiving unit is further used to receive the verification result sent by the fourth terminal and the secondary verification result sent by the fifth terminal, and receive the change result corresponding to the change request, wherein the authority of the first-level account is lower than that of the second-level account.
6. The system according to claim 1, characterized in that The system further comprises: a capacity management module, The capacity management module is used to collect the resource usage history data of the server corresponding to the cloud desktop platform, and build a capacity analysis model based on the historical data; use the capacity analysis model to analyze the resource usage data of the server at the current moment to obtain the target resource usage data of the server within a preset time period; and adjust the resources of the server according to the target resource usage data.
7. The system according to claim 1, characterized in that The system further comprises: The business continuity management module is used to generate emergency plans for repairing second-level failures.
8. The system according to claim 1, characterized in that The system further comprises: Problem management module; The problem management module is used to receive feedback information reported by multiple user terminals, where the feedback information is used to indicate problems generated during the operation of the cloud desktop platform, and to send the feedback information to corresponding processing accounts respectively, and receive processing results fed back by the processing accounts.
9. A method for troubleshooting a cloud desktop platform, characterized in that: include: Monitor the operation status of the cloud desktop platform through the monitoring management module and obtain alarm information; Generate a work order based on the alarm information through a work order management module, and send the work order to a first terminal corresponding to the second-level operation and maintenance account to obtain fault information, and send the work order to a second terminal corresponding to the third-level operation and maintenance account to obtain an emergency plan when the fault information indicates that the fault level is a second-level fault, wherein the authority of the third-level operation and maintenance account is greater than that of the second-level operation and maintenance account; Through the fault management module, when the fault level is a first-level fault, it is determined to complete the fault repair according to the repair plan in the fault information; when the fault level is a second-level fault, a predetermined emergency plan is obtained and the fault is handled according to the emergency plan.
10. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by the processor, the fault handling method of the cloud desktop platform described in claim 9 is implemented.
Citation Information
Patent Citations
Cloud desktop device monitoring method and device
CN113138895A
Cloud desktop fault detection method and device, server and cloud desktop system
CN116743546A
Virtual cloud desktop fault detection method, apparatus and device, and readable storage medium
CN116974834A
