JP2012221019A - Command schedule correspondence type cloud unifying operation system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To minimize an operational influence on a physical server by controlling a command input to the physical server so as to be efficient even when a large amount of commands are simultaneously inputted from a user not by a simple command queuing in a cloud system comprising a multiplatform.SOLUTION: A command of a common format is received from a host terminal, a platform is obtained from a virtual server name included in the command, the command is converted into a real command of a format of the platform, and a job including the real command is stored in a command queue. The job is extracted from the command queue, and the real command of the job is inputted to a command processing part of a corresponding platform. A command result executed by the command processing part of the platform is stored in a result queue processing part.

Description

  The present invention relates to a virtual environment control technology for autonomously scheduling input commands in a cloud system composed of multiple platforms.

  With the development of information systems, the number of cases where multiple platforms coexist in one cloud system is increasing. These information systems have a problem that, when performing the same type of operation, it is necessary to input a different command for each platform, and the burden on management is larger than when all the systems are configured with the same type of system. In a cloud system that allows an end user to operate a virtual server, commands for operating a large number of virtual servers may be simultaneously input to a command processing unit that operates the virtual server. In order to solve such problems, there is a need for a mechanism for centrally managing a plurality of platforms on an information system to absorb differences between platforms and to schedule operation commands for simultaneously input virtual servers. Yes.

  There is the following Patent Document 1 as a known technical document related to the present invention. In this document, for each device constituting a predetermined system, the operation manager can set each device with a common command format, and after converting the common format into a command for each device, each device And a technique for setting each device.

  FIG. 8 shows an example of a system that performs such centralized management. This system is a virtual node 818 connected to a network 810, and the virtual node 818 includes a router 811, a switch 812, a firewall 813, a switch 814, a load balancer 815, a switch 816, and a server farm 817. . In addition, an operation management integration node 819 is provided, and each device that is a component of the virtual node 818 is managed by the operation management integration node 819. The operation management integration node 819 enables the operation manager to set each device with a common command format, converts the common format into a command for each device, and inputs the device to each device to set each device. be able to. Also check the consistency of the setting definition of the common format. For example, even if the switches 812, 814, and 816 are devices that accept commands of different command formats, the operation manager sets the settings of the switches 812, 814, and 816 from the operation management integration node 819 with a common command format. It can be carried out.

JP 2005-197826 A

  As described above, in the case where multiple platforms are mixed in one cloud system, the operation commands to be input to the virtual servers of different platforms can all be operated in a common format, and the virtual in the platforms mixed in the cloud system can be operated. There is a need to centrally manage server operation commands.

  Also, in a cloud system where multiple virtual server platforms are mixed, it is not uncommon for the total number of virtual servers to range from thousands to tens of thousands. However, the command processing unit that controls the virtual server may not be able to process the input command and may hang up or delay abnormally. When the command processing unit enters such a state, the virtual server managed by the corresponding command processing unit cannot be operated, and customer satisfaction may be reduced.

  In order to solve such a problem when a large number of commands are simultaneously input, it is conceivable to store the input commands in a queue and execute the commands one by one.

  However, if you simply store commands in the queue and execute the commands in sequence, even if a large number of commands are stored in the queue, even if a new command is input, the command is actually executed. It may take time. In cloud systems, operations such as scaling out freely according to the system load at a certain point in time are common, but there is a problem that if the commands cannot be executed at the intended timing, operations that take advantage of the cloud system will not be possible . For this reason, there is a need for a mechanism that enables scheduling so that commands can be executed efficiently and allows an administrator to execute commands with the highest priority in an emergency.

  The object of the present invention is not to simply queue commands in a multi-platform cloud system, but to efficiently input commands to a physical server even when a large number of commands are simultaneously input from a user. It is an object to provide a command schedule-compatible cloud operation system and method that can be controlled to minimize the influence of operations on physical servers.

  To achieve the above object, the invention according to claim 1 is a command schedule-compatible cloud unified operation system comprising a host terminal and a control server that receives a command from the host terminal, wherein the host terminal Means for transmitting a command in a common format to a server, wherein the control server stores virtual server information storage means for storing a correspondence relationship between the virtual server and the platform, and an actual command for each platform corresponding to the command in the common format Command conversion information storage means storing the format of the command, means for receiving a command of the common format from the host terminal, and the virtual server name included in the received command of the common format as a key from the virtual server information storage means to the platform Hand to search And using the retrieved platform name as a key, the command conversion information storage means acquires the format of the actual command to be input to the command processing unit of the platform, and the received common format is based on the acquired format of the actual command. A means for converting the command into an actual command, a means for storing a job including the obtained actual command in the command queue, a job is extracted from the command queue, and the actual command of the job is processed by the command processing of the corresponding platform. And a means for receiving a command result executed by a command processing unit of the platform, and a unit for storing the received command result in a result queue processing unit.

  According to a second aspect of the present invention, in the command schedule compatible cloud unified operation system according to the first aspect, when a job is taken out from the command queue and an actual command of the job is transmitted to the command processing unit, the job The transmission is performed after confirming that the physical server that is the transmission destination of the job is not executing the job.

  According to a third aspect of the present invention, in the command schedule compatible cloud unified operation system according to the first or second aspect, when the job is stored in the command queue, the job is input under the administrator authority. If it is a job of the above, it is stored at the head of the command queue, otherwise it is stored at the end of the command queue.

  The invention according to claim 4 is a command schedule compatible cloud unified operation method using a host terminal and a control server that receives a command from the host terminal, wherein the control server has a correspondence relationship between a virtual server and a platform. Virtual server information storage means for storing the command and command conversion information storage means for storing the format of the actual command for each platform corresponding to the command of the common format, and the host terminal A command transmission step, the control server receiving a common format command from the host terminal, and the control server using the virtual server name included in the received common format command as a key. From information storage means And the control server obtains the format of the actual command to be input to the command processing unit of the platform from the command conversion information storage means using the searched platform name as a key, and Converting the received command in the common format into an actual command based on the format; storing the job including the actual command obtained in the control server in a command queue; Taking out a job from the queue and inputting the actual command of the job to the command processing unit of the corresponding platform; receiving the result of the command executed by the command processing unit of the platform; Server Characterized in that it comprises a step of storing the received command Results Results queue processing unit.

  The invention according to claim 5 is the command schedule compatible cloud unified operation method according to claim 4, wherein when the job is extracted from the command queue and the actual command of the job is transmitted to the command processing unit, the job The transmission is performed after confirming that the physical server that is the transmission destination of the job is not executing the job.

  The invention according to claim 6 is the command schedule compatible cloud unified operation method according to claim 4 or 5, wherein when the job is stored in the command queue, the job is input under the administrator authority. If it is a job of the above, it is stored at the head of the command queue, otherwise it is stored at the end of the command queue.

  The present invention provides an interface capable of automatically scheduling a command processing order so that a command can be executed efficiently even when a large number of commands are input in a cloud system composed of multiple platforms. be able to.

1 is an overall configuration diagram of a cloud unified operation system according to an embodiment of the present invention. It is a figure which shows the structure of virtual server information DB. It is a figure which shows the structure of command conversion DB. It is a figure which shows the structure of physical server status DB. It is a flowchart which shows the whole flow in this system. It is a flowchart which shows the flow of a scheduling process. It is a flowchart which shows the flow of a command transmission determination process. It is a schematic block diagram of the conventional cloud operation system

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a system configuration diagram showing an embodiment of the present invention. The cloud unified operation system of this embodiment includes a host terminal 101 including a command transmission unit 102, and a control server 103 that inputs commands to command processing units of various platforms in accordance with commands received from the host terminal 101. Prepare.

  The control server 103 executes a command receiving unit 104 that receives a command transmitted from the command transmitting unit 102 of the host terminal 101, a platform searching unit 105 that searches for a platform of a virtual server that is passed as an argument of the command, and is executed for each platform. A command conversion unit 106 that converts commands, a scheduling processing unit 107 that gives priority to commands, a command queue processing unit 108 that stores commands in a command queue, and an actual command transmission unit 109 that inputs commands to a command processing unit of a predetermined platform A command execution result receiving unit 110 for receiving the result of the executed command, a result queue processing unit 111 for storing the result of the executed command, a virtual server information DB 112 for storing platform information of the virtual server, Command conversion DB113 containing all commands that operate on virtual servers per-platform, and includes a physical server status DB114 which physical server stores the status of whether the job is running.

  In addition, it includes command processing units 115a and 115b for each platform that actually operate commands input from the control server 103, and physical servers 116a, 116b, and 116c of each platform that hold virtual images of virtual servers. The host terminal 101 and the control server 103, the control server 103 and the command processing units 115a and 115b of each platform, the command processing units 115a and 115b of each platform, and the physical servers 116a, 116b, and 116c of the platform are connected to the network. .

  FIG. 2 is a diagram illustrating an example of virtual server related information stored in the virtual server information DB 112. As shown in the figure, the virtual server information DB 112 stores a virtual server name 201, a platform name 202 indicating a platform to which the virtual server belongs, and a physical server name 203 indicating a physical server in which the virtual server image is stored. Has been. The virtual server name 201 is a unique server name in the entire cloud system. In the command transmitted by the command transmission unit 102 of the host terminal 101, this virtual server name is designated as an argument. Thus, the intended virtual server can be operated without depending on which physical server stores the virtual server image file in the transmitted command.

  FIG. 3 is a diagram illustrating an example of command conversion related information stored in the command conversion DB 113. As shown in the figure, in the command conversion DB 113, a platform name 301, a command name 302 indicating a command itself which is a command before conversion and input from the control server 103, and a command input to the command processing unit 115 of the platform are shown. A command 303 for storing a format is stored. The command name 302 is a common command name that can be used in common for different platforms. The platform name 301 corresponds to the platform name 202 and can be combined with the virtual server information DB 112 to constitute an actual command to be input to the command processing unit of the platform.

  Here, for example, it is assumed that a command poweron vm_pA1 is input from the host terminal 101. Since vm_pA1 is specified as the virtual server name of the argument, a record in which the virtual server name 201 of the virtual server information DB 112 is vm_pA1 is referenced, the platform name 202 of vm_pA1 is platformA, and the physical server name 203 is PhysicsServerA Can be searched. Further, by searching the command conversion DB 113 for the platform name platformA and the command name poweron, it can be seen that the command format of the corresponding platformA is vmpoweron -p <physical server name> -v <virtual server name>. Based on this information, the actual command to be input to the physical server of platformA can be input as vmpoweron -p PhysicsServerA -v vm_pA1.

  FIG. 4 is a diagram illustrating an example of status information stored in the physical server status DB 114. As shown in the figure, the physical server status DB 114 stores a physical server name 401 and a status 402. In the initial state, the status 402 of all physical servers is set to NotRunning. When a command is input to a physical server, the status 402 for the corresponding physical server name 401 is updated to Running, and when the job is completed, it is returned to NotRunning.

  FIG. 5 is a flowchart showing an outline of processing in the unified cloud operation system of this embodiment. First, the host terminal 101 passes a command input from the user to the command transmission unit 102. The command transmission unit 102 transmits the command to the control server 103 via the network (step 501). The command can be used in common regardless of the platform, and the virtual server name is specified as an argument.

  Next, the command receiving unit 104 of the control server 103 receives the command (step 502). The platform search unit 105 searches the virtual server information DB 112 for the platform name 202 and the physical server name 203 of the virtual server using the virtual server name received by the command receiving unit 104 as a key (step 503). The command conversion unit 106 refers to the command 303 in the command conversion DB 113 based on the command received in step 502 and the information of the platform name 202, and converts it into an actual command to be input to the command processing unit (step 504). Furthermore, a job ID that is unique for the entire command to be executed is assigned to the actual command (step 505). The scheduling processing unit 107 stores the job in the corresponding part of the command queue by the scheduling process (step 506). This scheduling process will be described in detail with reference to FIG.

  Next, the command queue processing unit 108 performs command transmission determination processing (step 507). The command transmission determination process will be described in detail with reference to FIG. 7, but in short, a process of setting a job that can be transmitted to each command processing unit among the jobs stored in the command queue to a “command transmission waiting state”. is there. A job in the command queue (including job ID, actual command, and physical server name of the transmission destination of the actual command) that has been set to “command transmission waiting state” by the command transmission determination process is passed to the actual command transmission unit 109. (Step 508). The actual command transmission unit 109 updates the physical server status DB so as to change the status 402 of the physical server that is the input destination of the passed command to Running (step 509). Further, the actual command transmission unit 109 transmits the actual command of the job passed in step 508 to the command processing unit of the platform of the corresponding physical server (step 510).

  Next, the command execution result receiving unit 110 receives the result of the command transmitted from the command processing units 115a and 115b of each platform (step 511), and stores the result of the command in the result queue (step 512). The result queue processing unit 111 outputs the command queue and the result queue having the same job ID to a file and deletes them from both queues (step 513). The command queue and the result queue having the same job ID are jobs that have been processed by the server. Next, the result queue processing unit 111 updates the physical server status DB so as to change the status of the physical server that executed the command to NotRunning (step 514).

  FIG. 6 is a flowchart showing details of the scheduling process in step 506 of FIG. First, it is confirmed whether or not administrator authority is given to the received command (step 601). If not given, the job is queued at the end of the command queue (step 602). If it has been assigned, the job is queued at the head of the job waiting in the command queue (step 603).

  Note that all jobs queued in the command queue in the process of FIG. 6 are all in the “waiting state” in the initial state immediately after queueing. The “waiting state” job in the command queue is changed from “waiting state” to “command transmission waiting state” in the process of FIG. 7 (step 507 in FIG. 5) described later. The job in “command transmission waiting state” in the command queue is transferred to the actual command transmission unit in step 508 of FIG.

  FIG. 7 is a flowchart showing details of the command transmission determination process in step 507 of FIG. First, the status of all physical servers is acquired from the physical server status DB 114 (FIG. 4) (step 701). Next, it is determined whether or not a command for a physical server whose status is NotRunning exists in the command queue (step 702). If it exists, the status of the job in the command queue is changed to “command transmission waiting status” (step 703). If not, the process returns to step 701 and waits until the next job is submitted to the command queue (step 702).

  In FIG. 5, the entire processing flow is shown for convenience of explanation, but in practice, the processing in steps 502 to 506, the processing in step 507, the processing in steps 508 to 510, and the steps 511 to 510 are performed. The processing of 514 is executed as a separate task. That is, in the processes of steps 502 to 506, the process of queuing the job into the command queue is repeated according to the command input from the user. In the process of step 507, the process of changing the job in which the physical server that is the transmission destination of the job is NotRunning to “command transmission waiting state” is repeated for the job stored in the command queue. In the processing of steps 508 to 510, the processing of taking out the “command transmission waiting state” job in the command queue and transmitting it to the command processing unit of the relevant physical server is repeated. In the processing of steps 511 to 514, the processing after the command processing result is obtained is repeated.

  According to the system of the above embodiment, even when different platforms are mixed, a command can be input to each platform using a common command format. Also, even when commands that operate a large number of virtual servers are entered at the same time, the entered commands are temporarily stored in the command queue and processed while taking out commands for physical servers in the NotRunning state from the command queue. As a result, the command cannot be processed and it will not hang up or be delayed abnormally. Furthermore, even if a command is input after a command for operating a large number of virtual servers is input at the same time, it is scheduled and input to the physical server as in steps 506 to 510, so that efficient processing as a whole is possible. .

  DESCRIPTION OF SYMBOLS 101 ... Host terminal, 102 ... Command transmission part, 103 ... Control server, 104 ... Command reception part, 105 ... Platform search part, 106 ... Command conversion part, 107 ... Scheduling processing part, 108 ... Command queue processing part, 109 ... Real Command transmission unit, 110 ... Command execution result reception unit, 111 ... Result queue processing unit, 112 ... Virtual server information DB, 113 ... Command conversion DB, 114 ... Physical server status DB, 115 ... Command processing unit for each platform, 116 ... Physical server for each platform.

Claims (6)

A command schedule compatible cloud unified operation system comprising a host terminal and a control server for receiving a command from the host terminal,
The host terminal comprises means for transmitting a command in a common format to the control server;
The control server
Virtual server information storage means for storing the correspondence between the virtual server and the platform;
Command conversion information storage means for storing a format of an actual command for each platform corresponding to the command of the common format;
Means for receiving a command in a common format from the host terminal;
Means for retrieving a platform from the virtual server information storage means using the virtual server name included in the received command in the common format as a key;
Using the retrieved platform name as a key, the command conversion information storage means acquires the format of the actual command to be input to the command processing unit of the platform, and the received common format command based on the acquired format of the actual command Means to convert to a real command,
Means for storing a job including the obtained actual command in a command queue;
Means for taking out the job from the command queue and inputting the actual command of the job to the command processing unit of the corresponding platform;
Means for receiving a command result executed by the command processing unit of the platform;
A command schedule-compatible cloud unified operation system comprising: means for storing a received command result in a result queue processing unit. In the command schedule compatible cloud unified operation system according to claim 1,
When retrieving a job from the command queue and transmitting the actual command of the job to the command processing unit, the job is transmitted after confirming that the physical server that is the transmission destination of the job is not executing the job. Command schedule compatible cloud unified operation system. In the command schedule compatible cloud unified operation system according to claim 1 or 2,
When storing the job in the command queue, if the job is a job of a command input under the authority of an administrator, the job is stored at the head of the command queue; otherwise, the command queue Command schedule compatible cloud unified operation system characterized by being stored at the end of. A command schedule compatible cloud unified operation method using a host terminal and a control server for receiving a command from the host terminal,
The control server is provided with virtual server information storage means for storing the correspondence relationship between the virtual server and the platform, and command conversion information storage means for storing the format of the actual command for each platform corresponding to the common format command. ,
The host terminal sending a common format command to the control server;
The control server receiving a command in a common format from the host terminal;
The control server searching for a platform from the virtual server information storage means using the virtual server name included in the received common format command as a key;
The control server obtains a format of an actual command to be input to the command processing unit of the platform from the command conversion information storage unit using the searched platform name as a key, and receives the reception based on the obtained format of the actual command. Converting a common format command into an actual command,
The control server storing a job including the obtained actual command in a command queue;
The control server retrieves a job from the command queue and inputs the actual command of the job to the command processing unit of the corresponding platform;
The control server receiving a command result executed by the command processing unit of the platform;
The control server includes a step of storing a received command result in a result queue processing unit. A command schedule-compatible cloud unified operation method, comprising: In the command schedule corresponding | compatible cloud unified operation method of Claim 4,
When retrieving a job from the command queue and transmitting the actual command of the job to the command processing unit, the job is transmitted after confirming that the physical server that is the transmission destination of the job is not executing the job. Command schedule compatible cloud unified operation method. In the command schedule-compatible cloud unified operation method according to claim 4 or 5,
When storing the job in the command queue, if the job is a job of a command input under the authority of an administrator, the job is stored at the head of the command queue; otherwise, the command queue Command-scheduled cloud unified operation method characterized by storing at the end of.

Images