CN107133072B - Operation execution method and device - Google Patents

Operation execution method and device Download PDF

Info

Publication number
CN107133072B
CN107133072B CN201710289687.9A CN201710289687A CN107133072B CN 107133072 B CN107133072 B CN 107133072B CN 201710289687 A CN201710289687 A CN 201710289687A CN 107133072 B CN107133072 B CN 107133072B
Authority
CN
China
Prior art keywords
event
type
configuration file
server
command
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710289687.9A
Other languages
Chinese (zh)
Other versions
CN107133072A (en
Inventor
张�杰
袁朋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Information Technologies Co Ltd
Original Assignee
New H3C Information Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Information Technologies Co Ltd filed Critical New H3C Information Technologies Co Ltd
Priority to CN201710289687.9A priority Critical patent/CN107133072B/en
Publication of CN107133072A publication Critical patent/CN107133072A/en
Application granted granted Critical
Publication of CN107133072B publication Critical patent/CN107133072B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3041Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is an input/output interface
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files

Abstract

The application provides an operation execution method and device, and the method comprises the following steps: monitoring a specified type event generated when a first type server executes a specific operation, obtaining event data corresponding to the specified type event, and writing the event data into a configuration file; when a second-class server needs to execute the specific operation, a command to be executed is generated according to the event data in the configuration file, and the command to be executed is sent to the second-class server, so that the second-class server executes the specific operation according to the command to be executed. Through the technical scheme of this application, do not need the managers to manage alone every server, can realize to repeated operation by a key, the management of every server can be accomplished to the host computer promptly to reduce managers's repeated operation, reduce managers's work load, improve work efficiency.

Description

Operation execution method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to an operation execution method and apparatus.
Background
The effective management of the server is an inevitable problem for managers, and the current implementation method is as follows: the manager realizes individual management of each server through a KVM (Keyboard Video Mouse, display terminal, and Mouse). However, with the rapid development of internet big data, the number of servers in a data center is greatly increased, and when a manager manages the servers individually through a KVM, some repetitive operations are involved, which greatly increase the workload of the manager and reduce the work efficiency of the manager.
Disclosure of Invention
The application provides an operation execution method, which is applied to a host computer and comprises the following steps:
monitoring a specified type event generated when a first type server executes a specific operation, obtaining event data corresponding to the specified type event, and writing the event data into a configuration file;
when a second-class server needs to execute the specific operation, a command to be executed is generated according to the event data in the configuration file, and the command to be executed is sent to the second-class server, so that the second-class server executes the specific operation according to the command to be executed.
The application provides an operation execution device, is applied to the host computer, the device includes:
the acquisition module is used for monitoring an appointed type event generated when a first type server executes a specific operation and acquiring event data corresponding to the appointed type event;
the storage module is used for writing the event data into a configuration file;
the generating module is used for generating a command to be executed according to the event data in the configuration file when the second type server needs to execute the specific operation;
and the sending module is used for sending the command to be executed to the second type server so as to enable the second type server to execute the specific operation according to the command to be executed.
Based on the technical scheme, in the embodiment of the application, a manager only needs to manage a first type of server (such as a server) through a host, and when the first type of server executes a specific operation, the host can monitor an event of a specified type and write event data corresponding to the event of the specified type into a configuration file; therefore, when specific operations need to be executed on the second type of server (such as a plurality of servers), the command to be executed can be generated according to the event data in the configuration file, and the command to be executed is sent to the second type of server, so that the second type of server executes the specific operations. Based on the mode, the management personnel do not need to manage each server independently, the repeated operation can be realized by one key, namely, the host can complete the management of each server, the repeated operation of the management personnel is reduced, the workload of the management personnel is reduced, and the working efficiency is improved. And the operating systems of different second type servers may be the same or different, i.e., no matter what the operating system of the second type server is, the second type server can be caused to perform specific operations.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart of a method of operation execution in one embodiment of the present application;
FIGS. 3A and 3B are examples of configuration files in one embodiment of the present application;
FIG. 4 is a block diagram of an operation execution device according to an embodiment of the present application;
fig. 5 is a hardware configuration diagram of a host according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
The present application proposes an operation execution method that can be applied to a system including a host for managing a server and a server, and the host may be a PC (Personal Computer). The server is a device for providing services deployed in a data center, and the number of the servers may be plural. As shown in fig. 1, for an application scenario diagram of the operation execution method, 3 servers are taken as an example for explanation, and the number may be more in practice. Furthermore, a KVM client may be configured for each server within the host, with different KVM clients being used to manage different servers.
Wherein the servers may perform the same specific operations, which may include but are not limited to: installing an operating system, system configuration, installing software, etc., without limitation as to the type of specific operation.
In the course of performing certain operations by these servers, these servers may be distinguished as a first type of server and a second type of server. The first type server refers to a server managed by a manager through a KVM, and the number of the first type servers may be one. The second type of server refers to a server that does not need to be managed by a manager through a KVM, and the number of the second type of servers may be one or more than one.
In an example, the second type of server may be different from the first type of server, for example, if the server 1 is the first type of server, and the servers 2 and 3 are the second type of server, the administrator may manage the server 1 through the KVM client 1, and during this management process, the host may monitor the event of the specified type and write the event data corresponding to the event of the specified type into the configuration file. Based on this, the host can manage the servers 2 and 3 according to the configuration file, and the manager does not need to manage the servers 2 and 3 through the KVM client.
In another example, the second type of server and the first type of server may also be the same, for example, if the server 1 is the first type of server and the server 1 is the second type of server, the administrator may manage the server 1 through the KVM client 1, and during this management process, the host may monitor the event of the specified type and write the event data corresponding to the event of the specified type into the configuration file. Further, on the basis of the existing configuration file, the host can manage the server 1 according to the configuration file, and a manager does not need to manage the server 1 through the KVM client.
In the application scenario, referring to fig. 2, a flowchart of the operation execution method is shown.
In step 201, a host monitors an event of a specified type generated when a first type server executes a specific operation, obtains event data corresponding to the event of the specified type, and writes the event data into a configuration file.
In one example, the specified type of event may include, but is not limited to: a mouse event and/or a keyboard event; the event data corresponding to the mouse event may include, but is not limited to: event type and/or event occurrence location; the event data corresponding to the keyboard event may include, but is not limited to: event type and keypad code.
Further, the event type corresponding to the mouse event may include, but is not limited to, one or any combination of the following: left click, right click, double click, move, scroll, drag, delay, and the delay is the time difference between two consecutive mouse events; the event occurrence position corresponding to the mouse event may include, but is not limited to: current coordinate information of the mouse; the event type corresponding to the keyboard event may include, but is not limited to, one or any combination of the following: keyboard press, keyboard pop-up, time difference between keyboard press and keyboard pop-up.
For example, during the process of executing a specific operation on the server 1 by the KVM client 1, the administrator may input operation information to the KVM client 1 through a keyboard (a keyboard event may be generated at this time), or may input operation information to the KVM client 1 through a mouse (a mouse event may be generated at this time), and after obtaining the operation information, the KVM client 1 may execute the specific operation on the server 1 by using the operation information, and the process of the specific operation is not limited, as long as the server 1 finally completes the specific operation.
When the manager inputs the operation information to the KVM client 1 through the mouse, the KVM client 1 may monitor the event, that is, a mouse event (a specific type event generated when the server 1 performs a specific operation), and may obtain an event type and an event occurrence position corresponding to the mouse event.
The event type may be left click, right click, double click, move, scroll, drag, delay (e.g., a time difference between two consecutive mouse events, i.e., a difference between an end time of a last mouse event and a start time of a next mouse event, which is a delayed value), and the like. In addition, the event occurrence position may be current coordinate information of the mouse (e.g., horizontal and vertical coordinates, the coordinate information is based on a position of the interface as a reference point, e.g., the reference point may be an upper left corner of the interface, a lower right corner of the interface, a lower left corner of the interface, an upper right corner of the interface, etc.).
Then, in the process of executing the mouse event by the KVM client 1, thereby performing a specific operation on the server 1, the KVM client 1 may obtain event data corresponding to the mouse event and write the event data into the configuration file. As shown in FIG. 3A, for an example of event data written to a configuration file, MoveTo indicates that the event type is move; 1279364 indicates that the event occurrence location is 1279 on the abscissa and 364 on the ordinate; delay indicates that the event type is Delay, 12621 indicates that the value of Delay is 12621 milliseconds; the LeftClick represents that the event type is left click; for other parameters in the event data, the meanings are similar, and are not described in detail.
When the manager inputs the operation information to the KVM client 1 through the keyboard, the KVM client 1 may monitor this event, i.e., a keyboard event (a specified type of event generated when the server 1 performs a specific operation), and may obtain an event type and a keyboard code corresponding to the keyboard event. The event type may be a keyboard press (KeyDown), a keyboard pop (KeyUp), and a time difference between the keyboard press and the keyboard pop. In addition, the keyboard code can be 16, 83 and other numerical values, for example, 16 represents the shift key.
Then, in the process of executing the keyboard event by the KVM client 1, thereby performing a specific operation on the server 1, the KVM client 1 may obtain the event data corresponding to the keyboard event and write the event data into the configuration file. As shown in fig. 3B, in the example of event data written to the configuration file, KeyDown indicates that the event type is a keyboard press, and 83 indicates that the keyboard code pressed is 83; delay represents the time difference between the keyboard press and the keyboard bounce, 218 represents that the time when the keyboard is pressed is 218 milliseconds; KeyUp indicates that the event type is keyboard bounce; for other parameters in the event data, the meanings are similar, and are not described in detail.
In one example, as shown in fig. 3A, when event data corresponding to a mouse event is written into a configuration file, the event data may be written into the configuration file in rows, and each piece of information is separated by a space. Furthermore, as shown in fig. 3B, when writing the event data corresponding to the keyboard event into the configuration file, the event data may be written into the configuration file in rows, and each piece of information may be separated by a space. In addition, the event data corresponding to the mouse event and the event data corresponding to the keyboard event can be written into the same configuration file or different configuration files.
Step 202, when the second type server needs to execute a specific operation (the same as the specific operation in step 201), the host generates a command to be executed according to the event data in the configuration file, and sends the command to be executed to the second type server, so that the second type server executes the specific operation according to the command to be executed.
In one example, the process for "generating a command to be executed according to event data in a configuration file" may include, but is not limited to: the host simulates an event corresponding to the event data according to the event data to obtain a parameter corresponding to the simulated event, wherein the parameter is used for enabling the second type server to execute specific operation according to the parameter; the host then generates a command to be executed that includes the parameter. Of course, the embodiment is not limited to the manner of generating the command to be executed, for example, the command to be executed carrying the event data may also be directly generated, and the manner of generating the command to be executed is not limited.
Further, the process for "the host simulates an event corresponding to the event data according to the event data" may include, but is not limited to: the host reads the event data through a Robot object (the Robot object may be used to simulate a mouse event, a keyboard event, etc.), and simulates an event corresponding to the event data. When it is hot, the present embodiment is not limited to the way of simulating events through the Robot object, and is not limited to this.
For example, when a specific operation needs to be performed on the server 2/server 3, the KVM client 2/KVM client 3 may read event data from the configuration file, simulate an event corresponding to the event data according to the event data, obtain a parameter corresponding to the simulated event, generate a command to be executed including the parameter, and send the command to be executed to the server 2/server 3, so that the server 2/server 3 performs the specific operation according to the command to be executed. In the above process, no manager performs a specific operation on the server 2/server 3 through the KVM client 2/KVM client 3.
For the process of "the KVM client 2 simulates an event corresponding to the event data according to the event data and obtains a parameter corresponding to the simulated event", the KVM client 2 may simulate the event corresponding to the event data after reading the event data. For example, for the event data "MoveTo 1279364", "Delay 12621" and "LeftClick 1279364", the event corresponding to the event data simulated by the KVM client 2 may be: the mouse is moved to position (1279, 364), then delayed 12621 milliseconds, and then the left mouse button is clicked at position (1279, 364). For another example, for the event data "KeyDown 83", "Delay 218", and "KeyUp 83", the event corresponding to the event data simulated by the KVM client 2 may be: the keypad code 83 is pressed, the time for which the keypad code 83 is pressed is 218 msec, and then the keypad code 83 is popped up. In addition, for other event data, the manner of simulating the event is similar to that described above, and is not described herein again.
In one example, the KVM client 2 may read the event data through the Robot object and simulate an event corresponding to the event data. Specifically, a Robot object (may also be referred to as a Robot class) may be configured for the KVM client 2, and the Robot object may be used to simulate a mouse event, a keyboard event, and the like, and an implementation manner of the Robot object is not limited as long as the mouse event and the keyboard event can be simulated. Based on this, the KVM client 2 may read the event data in the configuration file by row through the Robot object, and simulate an event corresponding to the event data, and the specific simulation process is not described in detail herein.
In one example, the KVM client 2 may simulate an event (e.g., a simulated mouse event, a simulated keyboard event, etc.) corresponding to the event data, and then obtain parameters corresponding to the event during the execution of the event, wherein the parameters are used for the server 2 to perform a specific operation according to the parameters. The KVM client 2 may then generate a command to be executed including these parameters and send the command to be executed to the server 2. And after receiving the command to be executed, the server 2 may parse the parameters from the command to be executed and execute a specific operation according to the parameters.
In the execution process of each event, a parameter corresponding to the event may be obtained, and the parameter is not limited as long as the server 2 can execute a specific operation according to the parameter.
In one example, for a process in which the host generates a command to be executed according to event data in the configuration file, based on the difference of the storage locations of the configuration file, the following ways may be included, but are not limited to:
firstly, after the event data is written into the configuration file, the configuration file can be stored in a local storage medium of the host; based on this, for the process of generating the command to be executed by the host according to the event data in the configuration file, the configuration file may be acquired from the local storage medium of the host, and the command to be executed may be generated according to the event data in the configuration file. Based on the implementation mode, the specific operation executed on the plurality of servers can be realized through one host. For example, after the host 1 stores the configuration file in the local storage medium of the host 1, the configuration file may be read from the local storage medium and used to perform a specific operation on a plurality of servers, such as performing a specific operation on the server 1, the server 2, the server 3, and the like.
Secondly, after the event data is written into the configuration file, the configuration file can be stored in a storage medium of a second type server; based on this, for the process of generating the command to be executed by the host according to the event data in the configuration file, the configuration file may be acquired from the storage medium of the second type server, and the command to be executed may be generated according to the event data in the configuration file. Based on the implementation, the specific operation performed on one or more servers can be realized through different hosts. For example, after the host 1 generates a configuration file for the server 1, the configuration file may be stored in a storage medium of the server 1 and/or the server 2. Then, the host 1/the host 2 may read the configuration file from the storage medium of the server 1 and/or the server 2 and perform a specific operation on the server 1 and/or the server 2 using the configuration file.
In one example, a record button for recording the profile, a save button for saving the profile, and a play button for performing a specific operation according to the profile may also be created. The use of the record, save and play buttons is described below:
after receiving the click command of the recording button, the host may perform a process of "monitoring a specified type event generated when the first type server performs a specific operation, obtaining event data corresponding to the specified type event, and writing the event data into a configuration file", that is, completing recording of the event data. Then, in the event data recording process, if a command to stop recording is received, the recording process may be stopped.
After receiving a click command of the save button, the host may acquire a storage path selected by the user and store a configuration file (a configuration file obtained in the recording process) to a storage medium matching the storage path. For example, if the storage path selected by the user is a local storage medium of the host, the configuration file is stored to the local storage medium of the host; if the storage path selected by the user is the storage medium of the server, storing the configuration file into the storage medium of the server; of course, the storage path may also be other storage media, and is not limited.
After receiving the click command of the play button, the host may acquire the configuration file from the storage medium matching the storage path, and execute a process of "generating a command to be executed according to event data in the configuration file".
Based on the technical scheme, in the embodiment of the application, a manager only needs to manage a first type of server (such as a server) through a host, and when the first type of server executes a specific operation, the host can monitor an event of a specified type and write event data corresponding to the event of the specified type into a configuration file; therefore, when specific operations need to be executed on the second type of server (such as a plurality of servers), the command to be executed can be generated according to the event data in the configuration file, and the command to be executed is sent to the second type of server, so that the second type of server executes the specific operations. Based on the mode, the management personnel do not need to manage each server independently, the repeated operation can be realized by one key, namely, the host can complete the management of each server, so that the repeated operation of the management personnel is reduced, the workload of the management personnel is reduced, and the working efficiency is improved. Moreover, the operating systems of different servers of the second type may be the same or different, i.e., no matter what the operating system of the server of the second type, the server of the second type may be caused to perform certain operations.
Based on the same application concept as the method, the embodiment of the present application further provides an operation execution device, which can be applied to a host, and is a structural diagram of the operation execution device, as shown in fig. 4.
An obtaining module 11, configured to monitor a specified type event generated when a first type server executes a specific operation, and obtain event data corresponding to the specified type event;
the storage module 12 is used for writing the event data into a configuration file;
a generating module 13, configured to generate a command to be executed according to the event data in the configuration file when the second type server needs to execute the specific operation;
a sending module 14, configured to send the command to be executed to the second class server, so that the second class server executes the specific operation according to the command to be executed.
The storage module 12 is further configured to store the configuration file to a local storage medium of the host; and/or storing the configuration file to a storage medium of a second type server;
the generating module 13 is specifically configured to, in a process of generating a command to be executed according to the event data in the configuration file, acquire the configuration file from a local storage medium of the host, and generate the command to be executed according to the event data in the configuration file; alternatively, the first and second electrodes may be,
and acquiring the configuration file from a storage medium of the second type server, and generating a command to be executed according to the event data in the configuration file.
The obtaining module 11 is specifically configured to monitor a specified type event generated when a first type server executes a specific operation after receiving a click command of a recording button, and obtain event data corresponding to the specified type event;
the storage module 12 is further configured to, after receiving a click command of a save button, acquire a storage path selected by a user, and store the configuration file to a storage medium matched with the storage path;
the generating module 13 is specifically configured to, after receiving a click command of a play button, acquire a configuration file from a storage medium matched with the storage path, and generate a command to be executed according to the event data in the configuration file.
The specific type of event monitored by the obtaining module 11 includes: a mouse event and/or a keyboard event; the event data corresponding to the mouse event obtained by the obtaining module 11 includes: the event type and/or the event occurrence position and the event data corresponding to the keyboard event comprise: event type and keyboard code;
the event type corresponding to the mouse event obtained by the obtaining module 11 includes one or any combination of the following: left click, right click, double click, move, scroll, drag, delay, the delay being the time difference between two consecutive mouse events; the event occurrence position corresponding to the mouse event obtained by the obtaining module comprises: current coordinate information of the mouse;
the event type corresponding to the keyboard event obtained by the obtaining module 11 includes one or any combination of the following: keyboard press, keyboard pop-up, time difference between keyboard press and keyboard pop-up.
The generating module 13 is specifically configured to, in a process of generating a command to be executed according to the event data in the configuration file, simulate an event corresponding to the event data according to the event data, and obtain a parameter corresponding to the simulated event, where the parameter is used to enable the second server to execute the specific operation according to the parameter; and generating a command to be executed comprising the parameters.
In terms of hardware, the hardware architecture diagram of the host provided in the embodiment of the present application may specifically refer to fig. 5. The method comprises the following steps: a machine-readable storage medium and a processor, wherein:
a machine-readable storage medium: the instruction code is stored.
A processor: the machine-readable storage medium is used for communicating with a machine-readable storage medium, reading and executing the instruction codes stored in the machine-readable storage medium, and the operation execution operations disclosed by the above examples of the application are realized.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (10)

1. An operation execution method applied to a host, the host comprising a first KVM client configured for a first type of server and a second KVM client configured for a second type of server, the first KVM client being configured to manage the first type of server, the second KVM client being configured to manage the second type of server, the method comprising:
monitoring a specified type event generated when a first type server executes specific operation through the first KVM client, obtaining event data corresponding to the specified type event, and writing the event data into a configuration file; wherein the specific operation comprises installing an operating system;
when a second-class server needs to execute the specific operation, a command to be executed is generated by the second KVM client according to the event data in the configuration file, and the command to be executed is sent to the second-class server, so that the second-class server executes the specific operation according to the command to be executed.
2. The method of claim 1,
after the writing the event data to a configuration file, the method further comprises:
storing, by the first KVM client, the configuration file to a local storage medium of the host; and/or the presence of a gas in the gas,
storing the configuration file to a storage medium of a second type server;
the process of generating a command to be executed by the second KVM client according to the event data in the configuration file includes:
acquiring the configuration file from a local storage medium of the host through the second KVM client, and generating a command to be executed according to the event data in the configuration file; alternatively, the first and second electrodes may be,
and acquiring the configuration file from a storage medium of the second type server through the second KVM client, and generating a command to be executed according to the event data in the configuration file.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
after receiving a click command of a recording button through the first KVM client, executing a process of monitoring a specified type event generated when a first type server executes a specific operation and obtaining event data corresponding to the specified type event;
after receiving a click command of a save button through the first KVM client, acquiring a storage path selected by a user, and storing the configuration file to a storage medium matched with the storage path;
and after receiving a click command of a play button through the second KVM client, acquiring a configuration file from a storage medium matched with the storage path, and executing a process of generating a command to be executed according to the event data in the configuration file.
4. The method of claim 1, wherein the specified type of event comprises: a mouse event and/or a keyboard event; the event data corresponding to the mouse event comprises: event type and/or event occurrence location; the event data corresponding to the keyboard event comprises: event type and keyboard code;
the event type corresponding to the mouse event comprises one or any combination of the following types: left click, right click, double click, move, scroll, drag, delay; the delay is the time difference between two consecutive mouse events; the event occurrence position corresponding to the mouse event comprises: current coordinate information of the mouse;
the event type corresponding to the keyboard event comprises one or any combination of the following: keyboard press, keyboard pop-up, time difference between keyboard press and keyboard pop-up.
5. The method according to claim 1 or 2, wherein the process of generating a command to be executed by the second KVM client according to the event data in the configuration file specifically includes:
simulating an event corresponding to the event data by the second KVM client according to the event data to obtain a parameter corresponding to the simulated event, wherein the parameter is used for enabling the second type server to execute the specific operation according to the parameter;
generating, by the second KVM client, a command to be executed including the parameter.
6. An operation execution device applied to a host, the host comprising a first KVM client configured for a first type of server and a second KVM client configured for a second type of server, the first KVM client being configured to manage the first type of server, the second KVM client being configured to manage the second type of server, the device comprising:
an obtaining module, configured to monitor, by the first KVM client, a specified type event generated when the first type server executes a specific operation, and obtain event data corresponding to the specified type event; wherein the specific operation comprises installing an operating system;
a storage module for writing the event data to a configuration file through the first KVM client;
a generation module, configured to generate, by the second KVM client, a command to be executed according to the event data in the configuration file when the second type server needs to execute the specific operation;
a sending module, configured to send the command to be executed to the second class server through the second KVM client, so that the second class server executes the specific operation according to the command to be executed.
7. The apparatus of claim 6,
the storage module is further configured to store the configuration file to a local storage medium of the host through the first KVM client; and/or storing the configuration file to a storage medium of a second type server;
the generating module is specifically configured to, during a process of generating a command to be executed according to the event data in the configuration file by the second KVM client, acquire the configuration file from a local storage medium of the host by the second KVM client, and generate the command to be executed according to the event data in the configuration file; alternatively, the first and second electrodes may be,
and acquiring the configuration file from a storage medium of the second type server through the second KVM client, and generating a command to be executed according to the event data in the configuration file.
8. The apparatus according to claim 6 or 7,
the obtaining module is specifically configured to monitor a specified type event generated when a first type server executes a specific operation after receiving a click command of a recording button through the first KVM client, and obtain event data corresponding to the specified type event;
the storage module is further configured to obtain a storage path selected by a user after receiving a click command of a save button through the first KVM client, and store the configuration file to a storage medium matched with the storage path;
the generating module is specifically configured to, after receiving a click command of a play button through the second KVM client, obtain a configuration file from a storage medium matched with the storage path, and generate a command to be executed according to the event data in the configuration file.
9. The apparatus of claim 6,
the specific type of event monitored by the obtaining module comprises: a mouse event and/or a keyboard event; the event data corresponding to the mouse event obtained by the obtaining module includes: the event type and/or the event occurrence position, and the obtained event data corresponding to the keyboard event comprise: event type and keyboard code;
the event type corresponding to the mouse event obtained by the obtaining module includes one or any combination of the following: left click, right click, double click, move, scroll, drag, delay, the delay being the time difference between two consecutive mouse events; the event occurrence position corresponding to the mouse event obtained by the obtaining module comprises: current coordinate information of the mouse;
the event type corresponding to the keyboard event obtained by the obtaining module comprises one or any combination of the following: keyboard press, keyboard pop-up, time difference between keyboard press and keyboard pop-up.
10. The apparatus according to claim 6 or 7,
the generation module is specifically configured to, in a process of generating a command to be executed according to the event data in the configuration file by the second KVM client, simulate, by the second KVM client, an event corresponding to the event data according to the event data, and obtain a parameter corresponding to the simulated event, where the parameter is used to enable the second server to execute the specific operation according to the parameter; generating, by the second KVM client, a command to be executed including the parameter.
CN201710289687.9A 2017-04-27 2017-04-27 Operation execution method and device Active CN107133072B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710289687.9A CN107133072B (en) 2017-04-27 2017-04-27 Operation execution method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710289687.9A CN107133072B (en) 2017-04-27 2017-04-27 Operation execution method and device

Publications (2)

Publication Number Publication Date
CN107133072A CN107133072A (en) 2017-09-05
CN107133072B true CN107133072B (en) 2021-02-26

Family

ID=59716361

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710289687.9A Active CN107133072B (en) 2017-04-27 2017-04-27 Operation execution method and device

Country Status (1)

Country Link
CN (1) CN107133072B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109189575A (en) * 2018-08-20 2019-01-11 北京奇虎科技有限公司 A kind of Explore of Unified Management Ideas and device of more OpenStack clusters
CN109976798A (en) * 2019-02-02 2019-07-05 杭州迪普科技股份有限公司 A kind of reminding method and device
CN110083342B (en) * 2019-04-26 2023-04-18 重庆紫光华山智安科技有限公司 Program generation method and device and computer readable storage medium

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5055901B2 (en) * 2005-10-26 2012-10-24 ソニー株式会社 Portable playback device, related information notification method, and related information notification program
CN100568808C (en) * 2006-10-12 2009-12-09 国际商业机器公司 Method and apparatus to a plurality of webserver parallel work-flows
CN101175284B (en) * 2006-11-01 2010-12-22 联想移动通信科技有限公司 Function testing method of portable electronic apparatus
US20090150532A1 (en) * 2007-12-06 2009-06-11 Aten International Co., Ltd. Methods and systems for client computer managing multiple servers
CN102023915A (en) * 2010-11-22 2011-04-20 任蓓瑜 Device and method for monitoring and managing keyboard, video and mouse
CN102841789B (en) * 2012-06-29 2016-05-25 北京奇虎科技有限公司 A kind of method and apparatus of recording with playback that user in browser is operated
CN104717337B (en) * 2015-04-03 2018-03-02 杭州昕云信息科技有限公司 A kind of method of batch testing mobile phone application and its equipment used
CN105446650A (en) * 2015-12-07 2016-03-30 北京奇虎科技有限公司 Keyboard input information recording method, apparatus and system

Also Published As

Publication number Publication date
CN107133072A (en) 2017-09-05

Similar Documents

Publication Publication Date Title
US9122341B2 (en) Resolving merged touch contacts
CN104268055B (en) The monitoring method and device of a kind of program exception
CN107133072B (en) Operation execution method and device
CN111064712B (en) Game resource packaging method and system
CN107423404B (en) Flow instance data synchronous processing method and device
US10706087B1 (en) Delegated decision tree evaluation
US10193989B2 (en) Visualization of user behavior
US20220066846A1 (en) Method for aggregating notification messages, and electronic device
CN110908880B (en) Buried point code injection method, event reporting method and related equipment thereof
US9553761B2 (en) Dynamic server to server configuration and initialization
US11813538B2 (en) Videogame telemetry data and game asset tracker for session recordings
US20160132399A1 (en) Implementing change data capture by interpreting published events as a database recovery log
WO2017097047A1 (en) Method for using mobile terminal without traces, and mobile terminal
CN114153732A (en) Fault scene testing method and device, electronic equipment and storage medium
JP2023553220A (en) Process mining for multi-instance processes
CN109376085B (en) Test case generation method and device and computer readable storage medium
CN113453048A (en) Audio and video tactile feedback setting method, audio and video playing method and computer equipment
CN105988917A (en) Method and device for obtaining abnormal information
CN110716699A (en) Method and apparatus for writing data
CN111414162B (en) Data processing method, device and equipment thereof
US11921608B2 (en) Identifying a process and generating a process diagram
CN106372846A (en) Method and device for determining state of course
CN107545198A (en) A kind of button management method and device
CN106484507B (en) A kind of processing method and processing device using thread
JP2022113227A (en) Common infrastructure system for dx implementation

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province

Applicant after: Xinhua Sanxin Information Technology Co., Ltd.

Address before: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province

Applicant before: Huashan Information Technology Co., Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant