KR102188987B1 - Operation method of cloud computing system for zero client device using cloud server having device for managing server and local server - Google Patents

Abstract

The present invention relates to a method of operating a cloud computing system for a zero-client terminal by using a cloud server having a server management device and a local server, capable of stably performing maintenance. According to the present invention, the method of operating the cloud computing system for the zero-client terminal by using the cloud server having the server management device and the local server includes: a failure symptom information extraction step; a failure pattern information generation step; a failure treatment information generation step; a failure grading assignment step; a failure information terminal transmission step; a selection information reception determination step; determining whether failure information of a management target server meets a preset condition when selection information is not received; and a failure repair or prevention treatment performance step.

Description

[Operation method of cloud computing system for zero client device using cloud server having device for managing server and local server}

The present invention relates to a cloud computing system for a zero client terminal using a cloud server equipped with a server management device and a local server. More specifically, as a system that can simultaneously use a cloud server and a local server by using a terminal for zero clients in a cloud computing system environment, data from a local server can be used with multiple terminals for zero clients (multiple monitors, keyboards, Mouse), and the local server is connected to the cloud server so that the local server can be used in real time like a personal computer in a number of other spaces for use with the cloud, and the cloud server is equipped with a server management device to provide a cloud server or a server of a local server. It relates to a cloud computing system for a zero client terminal that can effectively perform management.

In general, cloud computing is a type of Internet-based computing, and provides shared computer processing resources and data when requested by computers and other devices.

Cloud service refers to a service that stores data on the Internet and allows users to use it anytime, anywhere through the Internet connection without installing necessary data or programs on their computer. Data stored on the Internet through cloud services can be easily shared and delivered with simple operations and clicks. In addition to simply storing data on a server on the Internet, you can perform a desired task using the functions of an application provided on the web without installing a separate program, and multiple people can work while sharing documents at the same time. have.

However, these tasks cause a decrease in speed and load when performing tasks with excessive resource consumption or when more than a certain number of users simultaneously access the cloud server, and in order to fundamentally solve this, the capacity of the cloud server must be increased. There is a problem that causes more consumption.

On the other hand, server management requires specialized skills, and a considerable cost is required to hire such specialized personnel. Therefore, in particular, small companies, etc., do not hire a professional technician as the server manager, but rather select an appropriate person from the existing manpower in the company and have it as the server manager. In that case, it is difficult to manage the server smoothly, and it is almost impossible to smoothly cope with the occurrence of a server failure.

In addition, even when a server manager with specialized skills is employed for server management, if the server manager is located in a remote location from the server due to business trips, etc., it is difficult to promptly notify the manager of the server situation when a server failure occurs. It was difficult to smoothly cope with the occurrence. Moreover, even when the server administrator is notified of the occurrence of a failure of the server, it is difficult to immediately respond to it because it is located in a remote location, resulting in a huge loss such as the server going down.

In the related art, in a server integrated management system that integrates and manages a plurality of servers, when a failure occurs in a server, it detects the failure and recovers the failure afterwards. However, such a conventional post-failure recovery method has a problem that the operation of the server is stopped during the period of restoring a server in which a failure occurs, a loss occurs due to the interruption of use of the server, and the damage due to manpower and cost for the recovery is large. have.

KR 10-1263706 B1 KR 10-2015-0124642 A

Therefore, the problem to be solved by the present invention is that in order to solve the problems of the prior art as described above, a number of users selectively receive software shared resources from a cloud server or a local server as a terminal for a zero client. The purpose of this is to provide a cloud computing system for a zero client terminal that can prevent wasted budget by securing a certain speed by sharing the load of and building unnecessary cloud servers.

Another object to be solved by the present invention is to provide a cloud computing system for a zero client terminal using a cloud server and a local server capable of stable maintenance.

A method of operating a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to the present invention for solving the above problem is a cloud service server providing software shared resources to a user, the cloud service server At least one in which various data is output by receiving an image signal from at least one of a plurality of local servers connected to and providing a software shared resource and a hardware shared resource to a user, the cloud service server, and the plurality of local servers. A zero-client terminal including an output device or an input device, and a server management device for managing the cloud service server and the plurality of local servers as management target servers, wherein the server management device includes the management target servers A server management information collection unit that collects server management information from the server, and a failure pattern information generation unit that generates failure pattern information of a monitoring server that is a monitoring target among the management target servers based on the server management information and past failure case information stored in the database. , A failure action information generation unit that generates failure action information of the monitoring server using the failure pattern information and the past failure case information, and failure level information of the monitoring server based on the failure pattern information and the failure action information Server management comprising a failure information generation unit having a failure level information generation unit that generates, and a failure action performing unit that performs a failure repair or preventive action on the monitoring server based on the failure action information and the failure level information A method of operating a computing system for a zero client terminal using a cloud server equipped with a device and a local server, wherein the failure pattern information generation unit classifies the servers to be compared and managed with the same or similar configuration as the currently monitored server from the management target servers And the failure cases occurring in the comparative management target servers and corresponding past server management information in time series. Failure indication information extraction step of extracting failure indication information related to the occurrence of failure by matching, and the failure pattern information generation unit compares the extracted failure indication information with server management information collected from the monitoring server to match failure type, failure probability, and failure. A failure pattern information generation step of generating failure pattern information including at least one of the information on the expected time of occurrence, the failure action information generation unit to the failure type, probability of failure, and failure prediction time obtained by the failure pattern information generation unit. A failure action information generation step of generating failure action information regarding a failure repair or preventive action of a monitoring server by using at least one of the information and past failure case information, the failure level information generation unit, the failure pattern information and the failure action information A failure rating that gives a rating of the current or expected failure in the monitoring server by quantifying the impact of the current or expected failure on the use of the managed server and the difficulty, duration and cost of repairing the failure based on Assignment step, a failure information terminal transmission step in which the failure action execution unit periodically transmits failure information generated by the failure information generation unit to a user terminal or an administrator terminal, and the failure action execution unit repairs a failure from the user terminal or the manager terminal Or a step of determining whether to receive selection information to determine whether to receive selection information on whether to execute a preventive action, and if the selection information is not received, the failure action execution unit checks whether the failure information of the management target server meets a preset condition. Determining, and, when the selection information is received or the failure information satisfies a preset condition, the failure action execution unit performs a failure repair or preventive action on the managed server. Includes.

After the step of performing the action, the fault measure monitoring unit may further include a monitoring and feedback step of monitoring the result of the fault repair or preventive measure of the fault measure performing unit and feedback the fault repair or preventive measure result to the user terminal or the administrator terminal. have.

After the monitoring and feedback step, the failure action monitoring unit converts server management information, failure pattern information, failure class information, and failure action information of the managed server related to the failure repair or preventive action performed by the failure action execution unit into a database. It may further include a step.

As described above, according to the cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to the present invention, a plurality of users can use a cloud server or a software shared resource of a local server as a terminal for a zero client. By selectively receiving it, it is effective in securing a certain speed by sharing the load of the cloud server and preventing wasted budget by building unnecessary cloud servers.

In addition, by comparing and analyzing server management information collected from a cloud server or local server with past failure case information, failure pattern information, failure grade information, and failure action information are generated, and based on this, failure repair or failure of the cloud server or local server By periodically performing preventive measures, stable maintenance of a computing system for a zero client terminal using a cloud server and a local server may be possible.

1 is a configuration diagram showing a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to embodiments of the present invention;
2 is a block diagram showing an embodiment of a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to embodiments of the present invention;
3 is a schematic block diagram for explaining a cloud server having a server management device of FIG. 1;
4 is a block diagram for explaining a server management apparatus according to embodiments of the present invention;
FIG. 5 is a block diagram specifying the failure information generation unit of FIG. 4;
6 is a flow chart sequentially showing a method of operating a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to an embodiment of the present invention.

Specific details of the embodiment are included in the detailed description and drawings.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various forms different from each other, only this embodiment makes the disclosure of the present invention complete, and those skilled in the art to which the present invention pertains. It is provided to fully inform the person of the scope of the invention, and the invention is only defined by the scope of the claims.

The same reference numerals refer to the same components throughout the specification. Embodiments described herein will be described with reference to an ideal configuration diagram, a block diagram, and a flow chart of the present invention.

Hereinafter, with reference to the accompanying drawings, a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to an embodiment of the present invention and a method of operating the same will be described.

First, a cloud server having a server management device according to an embodiment of the present invention and a cloud computing system for a zero client terminal using a local server will be described in detail with reference to FIGS. 1 to 5.

1 is a configuration diagram showing a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to embodiments of the present invention, and FIG. 2 is a server management according to embodiments of the present invention. A configuration diagram showing an embodiment of a cloud computing system for a zero-client terminal using a cloud server with a device and a local server, and FIG. 3 is a schematic block diagram for explaining a cloud server with the server management device of FIG. 1; 4 is a block diagram illustrating a server management apparatus according to embodiments of the present invention, and FIG. 5 is a block diagram illustrating a failure information generation unit of FIG. 4.

1 to 2, a cloud computing system 100 for a zero client terminal using a cloud server and a local server having a server management device according to embodiments of the present invention includes a cloud server 10 and a local server. (20), a USB hub 30, a first communication unit 40, a second communication unit 50, including a terminal 70 for a zero client. According to embodiments of the present invention, a plurality of users can use a cloud server and a local server as a combination by using a terminal for zero clients without a main memory device including their respective central processing units or storage.

The cloud server 10 provides software shared resources to users. As an example, the cloud server 10 provides a software shared resource, that is, a program specific to the user's task, so that the user can access the cloud server 10 and execute the program with a terminal for zero clients. According to the concept of the present invention, the cloud server 10 may include a server management device 400 for managing the cloud server 10 or the local server 20. The server management device 400 will be described in detail with reference to FIGS. 3 to 5.

The local server 20 is connected to the cloud server 10 and provides a software shared resource and a hardware shared resource to a user.

In addition, the local server 20 is connected to a number of zero-client terminals (corresponding to input/output devices including monitors, keyboards, and mice) in a certain space, so that a number of users can output and output through the zero-client terminal without a computer body. To use the input function, software shared resources and hardware shared resources are provided.

The USB hub 30 is connected between the local server 20 and the first communication unit 40 and is configured to communicate with a peripheral device supporting USB. More specifically, the local server 20 is connected to the cloud server 10, and the USB hub 30 for transmitting the USB signal from the local server 20 to the first communication unit 40 is the local server 20 It is interconnected with a USB hub connection cable 31, and a plurality of first communication units 40 are connected to the USB hub 30.

The USB hub 30 transmits/receives various document data, voice data, etc. from the local server 20 to the first communication unit 40 from the local server 20 through a USB connection cable 32 inserted into the USB port 47. .

The first communication unit 40 includes a LAN connection port 41, a graphic card connection port 43, and a first USB port 47, and the first communication unit 40 includes a local server 20 and a graphic card. It is connected with a cable 45 to receive a signal from the local server 20.

In particular, it includes a graphic card connection port 43, a first USB port 47, and a LAN connection port 41 for transmitting video signals from the cloud server 10 and the local server 20 to the terminal for zero clients. It is equipped with a port for connecting hardware.

In addition, the first communication unit 40 may be viewed as a transmission device that transmits a signal to the second communication unit 50, and the second communication unit 50 may be viewed as a reception device that receives a signal from the first communication unit.

In addition, the first communication unit 40 is provided with two or more graphic card connection ports 43 for transmitting the video signal of the local server 20 or the cloud server 10 to a terminal for a zero client, one of the local server 20 ) To receive the video signal, the other side to receive the video signal from the cloud server (10).

In addition, the first communication unit 40 is provided with two or more first LAN connection ports 41 for transmitting a signal of the cloud server 10 or a signal of the local server 20 to the second communication unit 50 When one side receives the signal from the local server 20, the other side receives the signal from the cloud server 10.

More specifically, referring to FIGS. 1 to 2, a plurality of local servers 20 are connected to the cloud server 10, and the local server 20 transmits USB signals to the plurality of first communication units 40. The USB hub 30 is connected, and the graphic card cable 45 is connected to the graphic card port 43 of the first communication unit 40, respectively, so that the zero client terminal has one part of the cloud server 10 The signal is output and the other part is characterized by outputting the signal of the local server 20.

The second communication unit 50 receives a signal from the first communication unit 40, and a second LAN connection port 51, a speaker port 57, a keyboard port 55, a mouse port 56, a terminal for zero clients. A port capable of connecting hardware including a connection port 53, a second USB port 59, and a microphone port 58 is provided.

The second communication unit 50 includes one or more second LAN connection ports 51 for receiving signals from the cloud server 10 and the local server 20 from the first communication unit 40, and a video signal At least one terminal connection port 53 for a zero client is configured to transmit a message to the terminal 70 for a zero client, a keyboard 90 is connected to the keyboard port 55 of the second communication unit 50, and a mouse A mouse 91 is connected to the port 56, a speaker may be connected to the speaker port 57, and various USBs may be connected to the USB port 59.

The zero client terminal 70 is connected to one or more second communication units 50 and transmits video signals from the cloud server 10 or the local server 20 through the first communication unit 40 and the second communication unit 50. It includes one or more output devices and input devices for receiving transmission and outputting various data. Here, as an output device, a monitor may be used as a representative, and a keyboard 90, a mouse 91, and the like are used as an input device.

In addition, the zero client terminal 70 is a terminal that performs communication through the cloud server 10, the local server 20, and the first and second communication units 40 and 50, and includes a CPU and a memory device in the terminal. Since there is no central processing unit, it is a terminal that performs only simple communication with the first and second communication units 40 and 50.

In addition, in the terminal 70 for the zero client (corresponding to the input/output device including the monitor, keyboard 90, and mouse 91), the user selects either the cloud server 10 or the local server 20 You can connect, and you can perform tasks using shared software resources installed on the selected server.

More specifically, the output device of the zero client terminal 70 outputs a signal from the cloud server 10 to one screen or a part of a split screen, and the signal from the local server 20 is another screen or It is characterized in that it outputs to another part of the split screen or a screen of another connected output device.

For example, the zero client terminal 70 may output a signal from the cloud server 10 from one monitor and the signal from the local server 20 from another monitor, and in some cases, one monitor The data of the cloud server 10 and the data of the local server 20 may be output respectively so that the user can change the screen on one monitor and check the output screen respectively.

Therefore, the user may receive software resources from the cloud server 10 when processing usual general tasks, and there may be inconveniences such as slowdown when using heavy software such as HD full video and CAD programs. At this time, the local server 20 may receive and use software resources.

In addition, when a plurality of users each work with data using the cloud server 10 through the zero client terminal 70 and select the local server 20 when necessary, the local server 20 from the zero client terminal 70 You can work with the data of ).

3 is a schematic block diagram illustrating a cloud server including the server management apparatus of FIG. 1.

3, the cloud server 10 according to embodiments of the present invention is connected to a plurality of local servers 20 and manages the cloud server 10 and/or a plurality of local servers 20 The server management device 400 may be included as a means for doing so. For example, the server management device 400 may correspond to a management server provided in the cloud server 10 as a part of the cloud server 10. That is, the cloud server 10 includes a cloud service server 10A provided for use of the zero client terminal 70 as described with reference to FIGS. 1 and 2, a cloud service server 10A, and a plurality of local It may include a management server 400 provided for management of the servers 20. As another example, the server management device 400 may be provided in the form of a separate management server independent from the cloud server 10.

The server management device 400 receives server management information from each of the cloud service server 10A and/or a plurality of local servers 20, and generates corresponding failure pattern information, failure action information, and failure level information. It is possible to perform a measure for repairing or preventing a failure of the cloud service server 10A or the local server 20. Hereinafter, the cloud service server 10A and/or the plurality of local servers 20 are referred to as a management target server.

Further, the server management device 400 may transmit failure pattern information, failure action information, and failure level information to the user terminal 200 or the manager terminal 300, and measures for repair or prevention of failure of the managed server A selection request signal for whether to perform may be transmitted to the user terminal 200 or the manager terminal 300, and selection information for this may be received from the user terminal 200 or the manager terminal 300. Here, the user terminal 200 may be a user terminal that receives the cloud computing system 100 of the present invention from a supplier and provides it to the user of the zero client terminal 70, and the manager terminal 300 is It may be a terminal of a provider or server management company that supplies the cloud computing system 100 to a user.

The user terminal 200 and the manager terminal 300 may transmit and receive information from the server management device 400. The user terminal 200 and the manager terminal 300 are not only general desktop computers, but also smart phones, mobile phones, navigation systems, notebook computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), and tablets. It may include an electronic device such as a PC. An electronic device may have one or more general or special purpose processors, memory, storage, and/or networking components (wired or wireless).

4 is a block diagram illustrating a server management apparatus according to embodiments of the present invention. 5 is a block diagram illustrating a failure information generation unit of FIG. 4.

4 and 5, the server management apparatus 400 according to embodiments of the present invention includes a control unit 410, a database 420, a server management information collection unit 430, and a failure information generation unit 440. , A failure action execution unit 450 and a failure action monitoring unit 460 may be included. In addition, the failure information generation unit 440 may include a failure pattern information generation unit 442, a failure action information generation unit 444, and a failure level information generation unit 446.

The controller 410 may control the overall operation of the server management device 400. For example, the control unit 410 may control the operations of the database 420, the server management information collection unit 430, the failure information generation unit 440, the failure action execution unit 450, and the failure action monitoring unit 460. have. The control unit 410 may include a processor and a memory. The processor may be a data processing device embedded in hardware having a circuit physically structured to perform a function represented by a code or instruction included in a program. The processor is, for example, a microprocessor, a central processing unit (CPU), a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA). ) Can be included. The memory may perform a function of temporarily or permanently storing data processed by the processor. The memory may include magnetic storage media or flash storage media.

The database 420 may include a big data storage unit 422, a failure information storage unit 424 and a backup data storage unit 426.

The big data storage unit 422 may store server management information of a management target server and past failure case information of the management target server.

The failure information storage unit 424 may store failure pattern information, failure action information, and failure class information generated by the failure information generation unit.

The backup data storage unit 426 may backup and store data of a management target server as a result of a failure repair or preventive action performed by the failure action execution unit 450.

The server management information collection unit 430 may collect server management information from the management target server(s) (ie, the cloud service server 10A and/or a plurality of local servers 20). Server management information is basic information for determining whether a failure of the managed server has occurred, among the identification information of the managed server, storage medium information, CPU performance information, memory usage information, process status information, configuration file information, and login information. It may include at least one.

Specifically, the identification information may include information on a product model, a manufacturing date, a use start date, and a server installation location of the managed server.

The storage medium information may include information on the type, total capacity, used capacity, and remaining capacity of a storage medium of a management target server such as a hard disk drive (HDD) or a solid star drive (SSD).

The CPU performance information is information related to a state of a CPU process, and may include information on a CPU type and CPU usage of a managed server. For example, the CPU performance information may include information on the number of clocks of the CPU, the usage of the CPU user, the usage of the CPU system, the standby usage for CPU input/output, and the CPU idle period.

The memory usage information may include information on the total memory size of the managed server and information on the memory usage currently being used.

The process status information may include information on the currently running process name and process ID, user ID, CPU occupancy rate, total memory size, memory used, current state of the process, and CPU usage period of the managed server.

The environment configuration file information may include information on major configuration file information of the management target server and information on changing the environment configuration file.

The login information may include information about a user ID, a password, a login time, a login IP address, and a terminal node device type who accessed the management target server using the zero client terminal 70.

The server management information collection unit 430 may collect the above-described server management information at regular intervals, and the collected server management information may be transmitted to and stored in the database 420.

The failure pattern information generation unit 442 may generate failure pattern information of a management target server based on server management information and past failure case information. The past failure case information is a failure case that occurred in the past in the managed server (ie, the cloud service server 10A and/or a plurality of local servers 20) and the past server management information corresponding to the failure case. It may include. The failure pattern information may include at least one of information on a failure type, a probability of failure, and an expected time point of failure.

Specifically, the failure pattern information generation unit 442 has the same configuration as a management target server currently monitored from a plurality of management target servers (hereinafter, may be referred to as a monitoring server for convenience of description), and a similar comparison management target server Classify (s), and extract failure symptom information related to the occurrence of failure by matching the failure cases occurring in the comparison management target server(s) and the corresponding past server management information in time series, and extracting the extracted failure symptom information. Identification information collected from the monitoring server, storage medium information, CPU performance information, memory usage information, process status information, configuration file information, and information on the failure type, probability of failure, and expected time of failure by contrasting with at least one of log-in information Failure pattern information including at least one of may be generated.

As an example, the failure pattern information generation unit 442 time-series a failure case in which a failure occurred in the storage media of the server(s) subject to comparison management and storage medium information (e.g., usage versus usage period) at the time of the failure. At least among the information on the type of failure, possibility of failure, and expected time of failure in comparison with the extracted failure indication information and the storage media information of the monitoring server by matching with to extract the failure symptom information related to the wear rate and replacement time of the storage medium. It is possible to generate failure pattern information including one.

As another example, the failure pattern information generation unit 442 may include a failure case in which a system speed decrease has occurred due to excessive use of a CPU processor of the server(s) to be compared and managed, and CPU performance information (e.g., user, system, CPU process usage information according to each I/O standby) is matched in time series to extract information on failure symptoms related to system speed slowdown, and the extracted failure indication information is compared with the CPU performance information of the monitoring server, such as failure type, failure probability, and failure. It is possible to generate failure pattern information including at least one of information on the expected time of occurrence.

As another example, the failure pattern information generation unit 442 extracts failure symptom information from the failure case, such as a system down, in relation to a change in the past configuration file in the comparison management target server(s), and In comparison with the symptom information and the configuration file information of the monitoring server, failure pattern information including at least one of information on a failure type, a failure possibility, and an expected time point of occurrence of a failure may be generated.

According to an embodiment, the failure pattern information generation unit 442 may generate failure pattern information by using a model learned using a big data-based deep learning technique. For example, the failure pattern information generation unit 442 applies server management information and past failure case information to a previously learned failure pattern information generation model, extracts failure indication information related to failure, and manages the extracted failure indication information. Includes at least one of failure type, probability of failure, and expected time of failure by contrasting with at least one of identification information, storage media information, CPU performance information, memory usage information, process status information, configuration file information, and login information of the target server. It is possible to generate failure pattern information.

The failure pattern information generation model is a model learned by a deep learning technique, and may be an information processing algorithm for extracting and generating failure pattern information of a management target server using server management information and past failure case information. For example, the deep learning technique may include Deep Neural Networks (DNN), Convolutional Deep Neural Networks (CNN), or Reccurent Neural Network (RNN). Deep learning is higher than existing classification models such as SVM (Support vector machine), BN (Bayesian network), DT (Decision tree), kNN (k-th nearest neighbor) in various classification problems such as image, speech recognition, and pattern recognition. Accuracy is shown, and especially in the problem of classifying data expressed in the form of text sequences, CNN and RNN show superior performance compared to existing TF/IDF based'Bag of words' or'n-gram' based models. have.

The failure action information generation unit 444 uses at least one of information on a failure type, a possibility of a failure, and an expected failure time and past failure case information obtained by the failure pattern information generation unit 442 to repair the failure of the monitoring server. Alternatively, failure action information can be generated for preventive actions.

Specifically, the failure action information generation unit 444 is the same as the failure pattern information (for example, at least one of information on the failure type, failure probability, and failure prediction time), information on failure repair or preventive measures related to a similar failure pattern It is possible to generate failure action information by extracting from information on past failure cases of the server(s) to be compared and managed, and selecting an optimal failure repair or preventive action from the extracted failure repair or preventive action information. For example, failure action information is an optimal failure repair or preventive action method according to failure pattern information, and failure action information regarding storage medium replacement, memory expansion, environment file setting restoration, CPU process reset, unnecessary software execution suspension, temporary file deletion, etc. It may include.

The failure level information generation unit 446 is based on the failure pattern information and failure action information, and the effect of the current or expected failure (hereinafter referred to as the expected failure) on the use of the managed server and the failure repair. By quantifying the difficulty, duration, and cost, the monitoring server can assign a failure rating of a failure that is currently occurring or expected to occur in the future.

For example, the failure level information generation unit 446 is rated 4 when the status of the currently monitored management target server (i.e., monitoring server) is normal, 3 when a minor failure such as a system speed decrease occurs or is expected, and If a failure such as exceeding capacity, critical wear rate, or exceeding the critical replacement period is expected and urgent action is required, a failure grade is assigned as grade 2, and if a serious failure such as system down or data loss is expected in the near future, a failure grade is assigned. can do.

The failure action execution unit 450 may be set in advance according to the failure level or may perform a failure repair or preventive action according to a user or administrator's selection, based on the failure action information and the failure level information.

Specifically, the failure action execution unit 450 periodically transmits failure information generated by the failure information generation unit 440, that is, failure pattern information, failure action information, and failure level information to the user terminal 200 or the manager terminal 300. ). In addition, the failure action execution unit 450 transmits a selection request signal for failure repair or preventive action execution to the user terminal 200 or the administrator terminal 300 along with an alarm message regarding the failure information, and repairs or prevents the failure. By receiving selection information on whether to execute or not, it can perform troubleshooting or preventive measures. In contrast, the failure action execution unit 450 may automatically perform a failure repair or preventive action when failure information of a management target server satisfies a preset condition.

For example, when the failure level is 2 or 3, the failure action execution unit 450 stops the use of unnecessary memory or software, cleans up disks, and restores configuration files according to preset conditions or user (or administrator) selection. , Blacklisted users can be forced to log out. As another example, the failure action execution unit 450 may backup and store data of a management target server according to a preset condition or a selection of a user (or an administrator) when a serious server failure is expected, such as in the case of the first grade.

The failure action monitoring unit 460 may monitor a result of a failure repair or preventive action of the failure action execution unit 450 and feed back a result of the failure repair or preventive action to the user terminal 200 or the manager terminal 300. . In addition, the failure action monitoring unit 460 converts the server management information, failure pattern information, failure level information, and failure action information of the managed server related to the failure repair or preventive action performed by the failure action unit 450 into a database. It can be used as information on past failure cases for management of the server to be managed in the future.

Hereinafter, a cloud server having a server management device according to an embodiment of the present invention and a method of operating a cloud computing system for a zero client terminal using a local server will be described in detail with reference to FIG. 6, but one embodiment of the present invention. In the description of the configuration of a cloud server having a server management device according to the example and a cloud computing system for a zero client terminal using a local server, a description of a description regarding a time series operation method will be omitted.

6 is a flow chart sequentially showing a method of operating a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to an embodiment of the present invention.

As shown in FIG. 6, the method of operating a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to an embodiment of the present invention is first, the failure pattern information generation unit 442 (A) Classifies the comparison management target servers having the same or similar configuration as the monitoring server currently being monitored from the management target servers (1, 20), and analyzes failure cases occurring in the comparison management target servers and corresponding past server management information. A failure symptom information extraction step (S10) of extracting failure symptom information related to the occurrence of a failure by matching in time series is performed.

Thereafter, the failure pattern information generation unit 442 compares the extracted failure symptom information with server management information collected from the monitoring server to include at least one of information on a failure type, a failure possibility, and an expected time point of failure. A failure pattern information generation step (S20) of generating failure pattern information to be performed is performed.

Then, the failure action information generation unit 444 uses at least one of information on a failure type, a possibility of a failure, and an expected time of failure obtained by the failure pattern information generation unit 442 and past failure case information. A failure action information generation step (S30) of generating failure action information regarding a failure repair or preventive action of the monitoring server is performed.

After that, the failure level information generation unit 446 affects the current or expected failures occurring in the future based on the failure pattern information and the failure action information on the use of the managed server, the difficulty of repairing the failure, the duration, and A failure grade assignment step (S40) of assigning a grade of a failure currently occurring or expected to occur in the future in the monitoring server by quantifying the cost is performed.

Then, the failure information terminal transmission step (S50) of periodically transmitting the failure information generated by the failure information generation unit 440 to the user terminal 200 or the manager terminal 300 by the failure action execution unit 450 (S50). ).

Thereafter, a step of determining whether to receive selection information for determining whether to receive selection information on whether to perform a troubleshooting or preventive action from the user terminal 200 or the manager terminal 300 by the failure action execution unit 450 (S60 ).

In this case, when the selection information is not received, the failure action execution unit 450 further performs a step (S65) of determining whether failure information of the management target server satisfies a preset condition.

Thereafter, when the selection information is received or the failure information meets a preset condition, the failure action execution unit 450 performs a failure repair or preventive action step of performing a failure repair or preventive action on the management target server ( S70) is performed.

after that. The failure action monitoring unit 460 monitors the result of the failure repair or preventive action of the failure action execution unit 450 and feeds back the failure repair or preventive action result to the user terminal 200 or the manager terminal 300 The monitoring and feedback step (S80) is performed.

Finally, after the monitoring and feedback step (S80), the failure action monitoring unit 460 includes server management information and failure pattern information of the managed server related to the failure repair or preventive action performed by the failure action execution unit 450 , To perform the step (S90) of converting the failure level information and the failure action information into a database.

As described above, according to the method of operating a cloud computing system for a zero client terminal using a cloud server and a local server having a server management device according to an embodiment of the present invention according to the present invention, server management information collected from a management target server is By comparing and analyzing past failure case information, failure pattern information, failure class information, and failure action information are generated, and based on this, the cloud server and local server are periodically repaired or prevented. Stable maintenance of a computing system for a zero client terminal may be possible.

Although the preferred embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements by those skilled in the art using the basic concept of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

10: cloud server 20: local server
70: terminal for zero client
100: cloud computing system for zero client terminals
200: user terminal 300: administrator terminal
400: server management device
410: control unit 420: database
430: server management information collection unit 440: failure information generation unit
450: failure action execution unit 460: failure action monitoring unit

Claims (3)

Cloud service server that provides software shared resources to users,
A plurality of local servers connected to the cloud service server and providing software shared resources and hardware shared resources to users,
A terminal for zero clients including one or more output devices or input devices for receiving video signals from at least one of the cloud service server and the plurality of local servers and outputting various data, and
It includes a server management device for managing the cloud service server and the plurality of local servers as management target servers,
The server management device
Server management information collection unit for collecting server management information from the management target servers,
Based on the server management information and past failure case information stored in the database, a failure pattern information generation unit that generates failure pattern information of a monitoring server to be monitored among the management target servers, using the failure pattern information and the past failure case information A failure information generation unit having a failure management information generation unit that generates failure management information of the monitoring server, and a failure level information generation unit that generates failure level information of the monitoring server based on the failure pattern information and the failure management information. , And,
Computing for a zero client terminal using a cloud server and a local server with a server management device including a failure action execution unit that performs a failure repair or preventive action on the monitoring server based on the failure action information and the failure level information As a method of operating the system,
The failure pattern information generation unit classifies the servers to be compared and managed in the same or similar configuration as the currently monitored server from the management target servers, and watches the failure cases occurring in the comparison management target servers and corresponding past server management information Fault symptom information extraction step of extracting fault symptom information related to fault occurrence by thermal matching,
The failure pattern information generation unit compares the extracted failure symptom information with server management information collected from the monitoring server to generate failure pattern information including at least one of information on a failure type, a failure possibility, and an expected time point of failure. The step of generating failure pattern information,
The failure action information generation unit uses at least one of information on the type of failure, the possibility of failure, and the expected time of failure, and the information on the past failure case obtained by the failure pattern information generation unit Failure action information generation step of generating action information,
Based on the failure pattern information and the failure action information, the failure level information generation unit quantifies the effect of the currently occurring or expected failure on the use of the managed server, and the difficulty, duration, and cost of repairing the failure. A failure rating step that assigns a rating of a failure occurring now or expected to occur in the future,
A failure information terminal transmission step in which the failure action execution unit periodically transmits failure information generated by the failure information generation unit to a user terminal or an administrator terminal,
Determining whether or not the failure action execution unit receives selection information on whether to perform a failure repair or preventive action from the user terminal or an administrator terminal; determining whether to receive selection information;
When the selection information is not received, the failure action execution unit determines whether failure information of the management target server satisfies a preset condition, and
When the selection information is received or the failure information satisfies a preset condition, the failure action execution unit performs a failure repair or preventive action on the managed server.
Including
A method of operating a computing system for a zero client terminal using a cloud server having a server management device and a local server. In claim 1,
After the step of repairing or performing preventive measures,
A monitoring and feedback step in which the failure action monitoring unit monitors the result of the failure repair or preventive action of the failure action execution unit and feeds back the failure repair or preventive action result to the user terminal or the administrator terminal
Further comprising
A method of operating a computing system for a zero client terminal using a cloud server having a server management device and a local server. In paragraph 2,
After the monitoring and feedback step,
The failure action monitoring unit converts server management information, failure pattern information, failure level information, and failure action information into a database of the management target server related to failure repair or preventive measures performed by the failure action execution unit.
Further comprising
A method of operating a computing system for a zero client terminal using a cloud server having a server management device and a local server.

Images