JP6668658B2 - Job management method, job management device, and program - Google Patents

Description

  The present invention relates to a job management method, a job management device, and a program. In particular, the present invention relates to a job management method, a job management device, and a program for a job executed in a cloud system.

  2. Description of the Related Art In recent years, operations related to employee work management, sales form management, and the like are often processed by servers on a network. Specifically, the server executes a single or continuous program group included in a job script that describes processing procedures required for performing work such as work management, so that jobs related to work management and the like are processed. Is done. Note that the job script may be referred to as a shell script or a batch script depending on an OS (Operating System) executed on the server.

  Also, one job may be decomposed into a plurality of jobs (processing units), and a context may be set for the plurality of jobs, and a job network in which the context is defined in a flow may be processed by the server. .

  There is a job management device for managing such jobs and job networks. The job management device manages job definition information and performs flow control and the like of a job network. The job management device is often a device specialized for managing jobs and job networks, and necessary information such as a job script is transferred to another device (server, agent) according to the purpose of the job. An actual job is often executed by the other device.

  Work such as work management has been performed on the server for some time, but business processing (job execution) is usually independent of the platform (hardware, OS, etc.) for each system and project. there were. In such a case, it is necessary for the system administrator to manage the application running on the platform, the environment necessary for executing the job, and the like. However, with the development of network technology and information processing technology, system consolidation has progressed, platforms have been virtualized, and middleware required for job execution has often been provided as templates in the form of catalogs. Was.

  In response to such a change in the situation, the person in charge of each system or project does not manage the platform and middleware, but manages the above-mentioned integrated infrastructure (hereinafter simply referred to as infrastructure). A system in which a specific administrator (hereinafter, referred to as an infrastructure administrator) performs overall operation has been increasingly used. In an operation mode in which the infrastructure manager manages the infrastructure in a comprehensive manner, the person in charge of each system executes an arbitrary business process (job) on the infrastructure assigned to the system.

  U.S. Pat. No. 6,086,086 discloses a grid computing system that dynamically builds a software environment in response to specific job resource requirements. Further, Patent Literature 2 predicts the resource usage of a job to be executed using the input data amount of a job to be executed and the relationship between the input data amount of already executed jobs and the resource usage. A job management device is disclosed.

JP 2008-502967 A JP 2014-191360 A

  The disclosures of the above prior art documents are incorporated herein by reference. The following analysis has been made by the present inventors.

  In the above-described system in which the infrastructure manager manages the infrastructure in a comprehensive manner, the infrastructure manager creates many virtual machines (VMs) in response to requests from each user (person in charge of each project). . The user creates an application (parameter sheet) describing the specifications (specifications) of the virtual machine desired to use, and submits the application to the infrastructure administrator.

  The infrastructure administrator creates a virtual machine on a physical machine (PM) according to the application form and pays out the virtual machine to the user. At this time, a technique called IaC (Infrastructure as Code) may be used for the purpose of preventing erroneous input of parameter values by the infrastructure administrator and reducing the burden on the infrastructure administrator. Specifically, by using IaC, the contents of the parameter sheet are coded, and the virtual machine and its environment are automatically set.

  However, business processing (job, job network) cannot be executed on the virtual machine only by giving out the virtual machine to the user (person in charge of the project). That is, a job cannot be executed only by providing a virtual machine having machine specifications (for example, memory capacity, disk capacity, and the like) necessary for executing the job. More specifically, there is an execution requirement in the business process, an appropriate OS, an application, etc. are installed in the virtual machine and an account (execution user) required for executing the application, etc., is not set correctly. Cannot be executed.

  Therefore, in actual system operation, the person in charge of the project notifies the infrastructure administrator of the requirements necessary for business processing and requests the preparation of necessary platforms and applications. After the infrastructure is prepared by the above request, each person in charge designs the business required for job execution, places the batch processing as a program or script on the target server (virtual machine allocated), and schedules the job. Is going.

The summary of the exchange between the infrastructure administrator and each person in charge is as follows.
-The person in charge designs the business process and determines the requirements necessary to execute the business process.
-The person in charge notifies the infrastructure administrator of the business processing requirements.
-The infrastructure administrator builds an infrastructure that meets the business processing requirements that were notified.
-The person in charge arranges the job script on the server and executes the job after the test (test operation).

  In this way, cooperation between the person in charge of infrastructure and the person in charge of each project is necessary for executing the job (the work required for executing the job is shared). However, if there is an inconvenience in the cooperation between the persons in charge, a situation may occur in which the job is not executed normally. In other words, unless the persons in charge in different positions cooperate well with each other, and do not design and build an environment related to business processing in synchronization, the system operation cannot be started smoothly.

  For example, by using the IaC technology, even if the payout of a virtual machine is automatically performed, other operations require cooperation between persons in charge and manual setting of parameters, resulting in a human error. Can occur. For example, a mistake may occur that a user (execution user) required for executing the job is not registered in the virtual machine, or the registered user ID (Identification) is different from the requested user ID. Alternatively, a mistake may occur that the job script is not correctly placed in the virtual machine.

  An object of the present invention is to provide a job management method, a job management device, and a program that contribute to smooth execution of business processing in a cloud system.

According to a first aspect of the present invention, there is provided information related to an instruction defining a process for executing a business, and an execution requirement including a requirement including a guest OS, an application, middleware , and account information for executing the execution process. And, if there is no execution environment that meets the execution requirements in the cloud system, creating an execution environment that meets the execution requirements in the cloud system. Executing in an execution environment conforming to the above.

According to a second aspect of the present invention, information relating to an instruction defining a process for executing a task and an execution requirement including requirements for a guest OS, an application, middleware, and account information for executing the process are input. An input unit for executing, if an execution environment that meets the execution requirements does not exist in the cloud system, an execution environment management unit that creates an execution environment that meets the execution requirements in the cloud system; and An execution unit that executes in an execution environment that meets requirements is provided.

According to a third aspect of the present invention, information on an instruction that defines a process for executing a task and execution requirements including requirements for a guest OS, an application, middleware, and account information for executing the process are input. If there is no execution environment that meets the execution requirement in the cloud system, a process that creates an execution environment that meets the execution requirement in the cloud system, and the execution process conforms to the execution requirement There is provided a program for causing a computer mounted on a job management device to execute a process executed in an execution environment.
This program can be recorded on a computer-readable storage medium. The storage medium can be non-transient, such as a semiconductor memory, hard disk, magnetic recording medium, optical recording medium, and the like. The present invention can be embodied as a computer program product.

  According to each aspect of the present invention, a job management method, a job management device, and a program that contribute to smooth execution of business processing in a cloud system are provided.

It is a figure for explaining an outline of one embodiment. FIG. 1 is a diagram illustrating an example of a configuration of a job execution system according to a first embodiment. FIG. 9 is a diagram illustrating an example of a job requirement. FIG. 2 is a diagram illustrating an example of an internal configuration of the job management device according to the first embodiment. FIG. 6 illustrates an example of physical machine management information. FIG. 6 illustrates an example of virtual machine management information. FIG. 3 is a diagram illustrating an example of an internal configuration of the physical machine according to the first embodiment. 5 is a flowchart illustrating an example of an operation of an execution environment inspection unit according to the first embodiment. FIG. 9 is a diagram illustrating an example of a job requirement. FIG. 9 is a diagram illustrating an example of a job requirement. FIG. 6 is a sequence diagram illustrating an example of an operation of the job execution system according to the first embodiment. FIG. 13 is a diagram illustrating an example of another configuration of the job execution system. FIG. 13 is a diagram illustrating an example of another configuration of the job execution system.

  First, an outline of an embodiment will be described. It should be noted that the reference numerals in the drawings attached to this outline are added for convenience of each element as an example for facilitating understanding, and the description of this outline is not intended to limit the invention in any way.

  As shown in FIG. 1, the job management method according to one embodiment includes first to third steps. The first step is a step of inputting information relating to an instruction defining a process of executing a task and an execution requirement including a requirement for executing the execution process. The second step is a step of creating an execution environment that meets the execution requirements in the cloud system if there is no execution environment that meets the execution requirements in the cloud system. The third step is a step of executing the execution processing in an execution environment that meets the execution requirements. In the present disclosure, an instruction is defined as an instruction to a processor in an execution environment. For example, a script or an executable file corresponds to the instruction.

  In the job management method according to the embodiment, information including information on a job instruction and an execution requirement are input. Further, it is determined whether or not there is an execution environment that satisfies the execution requirement input together with the information on the instruction. If not, an execution environment that meets the execution requirement is created in the cloud system. As a result, there is no need for advance preparation of infrastructure or cooperation between persons in charge, and necessary jobs are executed. That is, smooth execution of business processing in the cloud system is realized.

  Hereinafter, specific embodiments will be described in more detail with reference to the drawings. In each embodiment, the same components are denoted by the same reference numerals, and description thereof will be omitted.

[First Embodiment]
The first embodiment will be described in more detail with reference to the drawings.

  FIG. 2 is a diagram illustrating an example of a configuration of the job execution system according to the first embodiment. Referring to FIG. 2, the job execution system includes a terminal 10 and a data center 20. The terminal 10 and the data center 20 are mutually connected via a network.

  The data center 20 includes a job management device 21 and a plurality of physical machines 22-1 to 22-n (n is a positive integer, the same applies hereinafter). If there is no particular reason to distinguish the physical machines 22-1 to 22-n, the physical machines are simply referred to as “physical machines 22”.

  The plurality of physical machines 22 installed in the data center 20 are information processing devices (computers) that constitute a service providing infrastructure in a cloud system. In the cloud system, virtual machines are created for each user (tenant) of the data center 20.

  The job management device 21 is a device that controls and manages the physical machine 22. Specifically, the job management device 21 manages the specifications (for example, hardware specifications, usable software, and the like) and the operation state of the physical machine 22. The job management device 21 creates a virtual machine in the physical machine 22 forming the cloud system, and provides a user of the data center 20 with a job execution environment (virtual machine).

  The terminal 10 is a terminal used by a user of the data center 20. For example, the user of the data center 20 operates the terminal 10 to specify a requirement (hereinafter, referred to as a job requirement) for causing a virtual machine created on the physical machine 22 to execute business processing such as work management. Input to the management device 21.

  FIG. 3 is a diagram illustrating an example of the job requirement. For example, the job requirements include job definition information and job execution requirements.

  The job definition information includes information defining an outline of a job to be executed by a virtual machine provided to each tenant. For example, the job definition information includes a tenant ID (Identification) assigned by the operator of the data center 20 and an instruction (an entity of a job for realizing the business process; for example, a script file or an execution file) ) And schedule information related to job execution. In the example illustrated in FIG. 3, in the virtual machine assigned to “Tenant A”, the processing (programs and their execution order) described in the script file with the file name “JOB_A.sh” is “every Tuesday morning. 8:00 ".

  The job execution requirement includes information on a requirement for executing a job specified by the job definition information. For example, the job execution requirements include specifications (memory capacity, disk capacity, and the like) required for a virtual machine that executes the job, software (OS, application, middleware, and the like) required when executing the job, and an account ( Execution account). In the example illustrated in FIG. 3, “OS_A” is installed as an OS and “AP_A” is installed as an application (AP) in a virtual machine having a memory capacity of 2 Gbytes and a disk capacity of 10 Gbytes, and “USER_A” is executed. It is understood that registration as an account is necessary for execution of a job.

  When a job requirement is input from the terminal 10, the job management device 21 illustrated in FIG. 2 prepares an execution environment (virtual machine) that meets the job execution requirement included in the job requirement. More specifically, the job management device 21 prepares a virtual machine that meets the job execution requirements, and uses the virtual machine as a job execution environment. Further, the job management device 21 controls the execution of the job according to the schedule information included in the job definition information.

  The user (tenant) of the data center 20 operates the terminal 10 to refer to (or acquire) the execution result of the job executed by the virtual machine.

  FIG. 4 is a diagram illustrating an example of the internal configuration of the job management device 21. Referring to FIG. 4, the job management device 21 includes a communication control unit 201, a job requirement processing unit 202, an execution environment inspection unit 203, a physical machine management unit 204, a job execution control unit 205, a job requirement storage unit 211, a physical machine management information storage unit 212, and a virtual machine management information storage unit 213. The components constituting the job management device 21 are interconnected via an internal bus, and the control modules including the job requirement processing unit 202 are configured to be able to access a storage unit such as the job requirement storage unit 211.

  The communication control unit 201 is a unit that controls communication with another device (the terminal 10, the physical machine 22, or the like). When receiving a message from another device, the communication control unit 201 distributes the message to each unit in the job management device 21. Alternatively, when a message transmission instruction is received from each unit in the job management apparatus 21, the message is transferred to another apparatus. When a job requirement is input from the terminal 10, the communication control unit 201 stores the input job requirement in the job requirement storage unit 211 and notifies the job requirement processing unit 202 that the job requirement has been acquired.

  The job requirement processing unit 202 is a unit that processes job requirements acquired from the terminal 10. Specifically, upon acquiring the job requirement, the job requirement processing unit 202 requests the execution environment inspection unit 203 to perform an inspection on the job execution requirement and the execution environment (virtual machine) described in the job requirement. When the execution environment inspection unit 203 completes the inspection, the job requirement processing unit 202 performs processing according to the inspection result notified from the execution environment inspection unit 203.

  More specifically, if the job requirement processing unit 202 obtains the first inspection result “the job can be executed on an existing virtual machine” from the execution environment inspection unit 203, the job requirement processing unit 202 , And information specifying a virtual machine that executes a job corresponding to the job requirement.

  Further, when the job requirement processing unit 202 acquires the second inspection result that “the job can be executed by changing the specifications of the existing virtual machine” from the execution environment inspection unit 203, the job requirement processing unit 202 Request the specification change (configuration change, reconfiguration) of the virtual machine. At this time, the job requirement processing unit 202 provides information on the change in the specification of the virtual machine to the physical machine management unit 204.

  Further, when the job requirement processing unit 202 acquires the third inspection result that “new execution of a virtual machine is required to execute a job” from the execution environment inspection unit 203, the job requirement processing unit 202 Request creation of a new virtual machine. At this time, the job requirement processing unit 202 provides information on the newly created virtual machine to the physical machine management unit 204.

  When the change of the virtual machine or the creation of the new virtual machine by the physical machine management unit 204 is completed, the job requirement processing unit 202 provides the job execution control unit 205 with the information specifying the job requirement and the job requirement corresponding to the job requirement. And information identifying the virtual machine that executes the job.

  In addition, when the job requirement processing unit 202 acquires the first to third inspection results from the execution environment inspection unit 203, the job requirement processing unit 202 informs that the job execution environment can be provided via the communication control unit 201. Notify the terminal 10.

  Further, when the job requirement processing unit 202 acquires the fourth inspection result “job execution is impossible” from the execution environment inspection unit 203, the job requirement processing unit 202 notifies the terminal 10 via the communication control unit 201 of the fact. Notify.

  As described above, based on the request (instruction) from the job requirement processing unit 202, the execution environment inspection unit 203 performs an inspection on the job execution requirements included in the job requirements and the execution environment (virtual machine). More specifically, based on the job requirements, the physical machine management information stored in the physical machine management information storage unit 212, and the virtual machine management information stored in the virtual machine management information storage unit 213, the first The inspection corresponding to the fourth to fourth inspection results is performed, and the result is notified to the job requirement processing unit 202. A more detailed description of the operation of the execution environment inspection unit 203 will be described later.

  The physical machine management unit 204 is a unit that controls and manages the physical machine 22 in the data center 20 (a unit that manages a virtual machine that is a job execution environment). Specifically, if there is no virtual machine that meets the job execution requirement in the cloud system, the physical machine management unit 204 assigns a virtual machine that meets the job execution requirement to the physical machine 22 for each tenant of the cloud system. Create separately. More specifically, based on a request from the job requirement processing unit 202, the physical machine management unit 204 changes the specifications of an existing virtual machine or creates a new virtual machine in the physical machine 22. The change or new creation of a virtual machine by the physical machine management unit 204 is performed after the inspection by the execution environment inspection unit 203 (the inspection on the execution requirements and the execution environment is performed first). Further, when a change occurs in the physical machine management information or the virtual machine management information, the physical machine management unit 204 stores the information (the physical machine management information storage unit 212 and the virtual machine management information storage unit). 213) is updated.

  The job execution control unit 205 is a unit that executes a job included in the job requirement in an execution environment (virtual machine) that meets the job execution requirement included in the job requirement. Specifically, the job execution control unit 205 performs control (job execution control) related to starting and stopping of a job (job process) described in the job requirement. Further, the job execution control unit 205 sets the instructions included in the job definition information in the virtual machine that executes the job of the job requirement. For example, the job execution control unit 205 distributes a script file necessary for executing the job to the virtual machine and sets the job executable state. When the setting of the instruction to the virtual machine is completed, the job execution control unit 205 instructs the virtual machine to which the instruction has been set to execute the job according to the schedule information described in the job definition information.

  Each storage unit of the job requirement storage unit 211, the physical machine management information storage unit 212, and the virtual machine management information storage unit 213 includes a storage medium such as an HDD (Hard Disk Drive).

  The job requirement storage unit 211 stores the job requirements acquired from the terminal 10.

  The physical machine management information storage unit 212 centrally manages the physical machine management information and stores the information. FIG. 5 is a diagram illustrating an example of the physical machine management information. Referring to FIG. 5, as physical machine management information, hardware specifications (for example, available memory capacity, disk capacity) and software (available OS, available applications, available middleware) of each physical machine 22 are provided. (MW; MiddleWare)) is registered.

  The virtual machine management information storage unit 213 centrally manages the virtual machine management information and stores the information. FIG. 6 is a diagram illustrating an example of the virtual machine management information. Referring to FIG. 6, as the virtual machine management information, for each tenant, the virtual machine assigned to each tenant, the physical machine in which the virtual machine is created, the specifications of the virtual machine, and the virtual machine installed in the virtual machine. Software (for example, a guest OS and an executable application) and information on an execution account of the software are registered. That is, the virtual machine management information manages the specifications (specifications regarding hardware and specifications regarding software) of the virtual machine created in the physical machine 22. Note that, in the present disclosure, an execution account for executing software is included in the specifications regarding software.

  FIG. 7 is a diagram illustrating an example of the internal configuration of the physical machine 22. Referring to FIG. 7, the physical machine 22 includes a hardware resource 301 and a hypervisor 302.

  The hardware resources 301 of the physical machine 22 include a central processing unit (CPU), a memory such as a dynamic random access memory (DRAM), a storage medium such as a hard disk drive (HDD), and a communication medium such as a network interface card (NIC). Interface etc. are included.

  The hypervisor 302 is a means for constructing and managing a virtual environment in the physical machine 22. That is, creation and change of a virtual machine are controlled by the hypervisor 302. The virtual hardware created by virtualizing the hardware resource 301 is allocated to the virtual machine created by the hypervisor 302. The virtual hardware 311 includes a virtual NIC, and communication between the virtual machine and another device is performed via the virtual NIC. On the virtual machine, a guest OS 312 operates, and on the guest OS 312, an application 313 and middleware 314 operate.

  Next, an operation of the job management apparatus 21 according to the first embodiment will be described focusing on the execution environment inspection unit 203.

  FIG. 8 is a flowchart illustrating an example of the operation of the execution environment inspection unit 203 according to the first embodiment.

  In step S101, the execution environment inspection unit 203 determines whether a virtual machine that meets the job execution requirements acquired from the terminal 10 already exists. Specifically, the execution environment inspection unit 203 makes the determination based on whether or not the specifications (hardware specifications and software specifications) of the existing virtual machine already constructed on the physical machine 22 include the job execution requirements. I do. If a virtual machine that meets the job execution requirement already exists (step S101, Yes branch), the execution environment inspection unit 203 executes the processing from step S102. If there is at least one difference between the element of the job execution requirement and the corresponding element of the virtual machine management information (when the specification of the existing virtual machine does not include the job execution requirement included in the job requirement), the execution is performed. The environment inspection unit 203 determines that there is no virtual machine that satisfies the job execution requirement (step S101, No branch), and executes the processing after step S104.

  For example, it is assumed that the execution environment inspection unit 203 has acquired the job requirements as shown in FIG. In this case, the execution environment inspection unit 203 refers to the virtual machine management information storage unit 213 to determine whether there is a virtual machine assigned to the tenant A and meeting the job execution requirements shown in FIG. Is determined.

  Referring to FIG. 6, since the specifications of the virtual machine VM1-1 created in the physical machine 22-1 include the job execution requirements, the execution environment inspection unit 203 transitions to step S102 and continues the processing.

  On the other hand, when the execution environment inspection unit 203 acquires the job requirements as shown in FIGS. 10A and 10B, it is the virtual machine assigned to the tenant A, and the specification is Since there is no virtual machine that satisfies the requirement, the process proceeds to step S104 to continue the process. The job execution requirement illustrated in FIG. 10A is because the execution accounts do not match as compared with the virtual machine VM1-1 described in the first line of FIG. The job execution requirement illustrated in FIG. 10B is because the OS (guest OS) does not match the virtual machine VM1-1 described in the first line of FIG.

  In step S102, the execution environment inspection unit 203 determines whether the job (script file) described in the job requirement can be executed in the virtual machine (existing virtual machine) selected in step S101. Specifically, the execution environment inspection unit 203 makes the determination based on whether or not the job (execution process defined by the script file) can coexist with other processes executed on the existing virtual machine.

  Note that various techniques can be used for the determination in step S102 executed by the execution environment inspection unit 203. For example, the execution environment inspection unit 203 may compare the schedule information described in the job requirement with the schedule information of the job executed in the existing virtual machine, and determine whether the job can be executed. If the execution timing of the job described in the job requirements is different from the execution timing of the job executed in the existing virtual machine (for example, when each job is executed on a different day of the week), the execution environment inspection unit 203 determines that the two jobs can be executed on the same virtual machine.

  Alternatively, as disclosed in Patent Literature 2, the input data amount of a job to be executed (a job described in the job requirements; a job to be executed) and the already executed job (selected in step S101) It may be determined whether or not the job to be executed can be executed on an existing virtual machine by using the relationship between the input data amount of the executed virtual machine and the resource usage.

  If the job can be executed in the existing virtual machine (step S102, Yes branch), the execution environment inspection unit 203 determines that the execution of the requested job can be performed by the existing virtual machine (step S102). S103). That is, the existing virtual machine is determined to be an execution environment that meets the job execution requirements. In this case, the execution environment inspection unit 203 sets the first inspection result as the inspection result regarding the job execution requirement.

  In step S104, the execution environment inspection unit 203 determines whether the requested job execution requirement can be satisfied by changing the specification of the existing virtual machine. Specifically, the execution environment inspection unit 203 makes the above determination based on whether or not the difference between the specifications of the existing virtual machine and the job execution requirements is a predetermined difference.

  For example, as shown in FIG. 10A, when only the execution account is different between the job execution requirement and the existing virtual machine VM1-1, the requested job execution requirement is changed to the existing virtual machine. It is determined that addition is possible. In this case, it is easy to add an execution account to an existing virtual machine. Or, if the difference between the requested job execution requirement and the existing virtual machine is such that the memory capacity of the already created virtual machine is smaller than the memory capacity of the job execution requirement, change the specifications of the existing virtual machine. By doing so, it is determined that it is possible to provide an execution environment (virtual machine) that meets the job execution requirements. This is because it is easy to add a memory capacity to an existing virtual machine.

  On the other hand, as shown in FIG. 10B, when the OS of the job execution requirement is different from the OS (guest OS) installed in the existing virtual machine VM1-1, the execution environment inspection unit 203 It is determined that the change to the existing virtual machine cannot meet the requested job execution requirement. This is because it is difficult to cope with different OSs.

  The criterion for determining whether or not the requested job execution requirement can be met by changing the existing virtual machine when any of the elements match shall be determined in advance according to the characteristics and characteristics of each element. I do.

  If it is determined that the job execution requirement can be met by changing the existing virtual machine (step S104, Yes branch), the execution environment inspection unit 203 determines that the specification change of the existing virtual machine is necessary (step S104). S105). In this case, the execution environment inspection unit 203 sets the second inspection result as a result of the inspection regarding the job execution requirement.

  When the requested job execution requirement cannot be satisfied by the existing virtual machine (step S102, No branch), or when the requested job execution requirement cannot be satisfied by changing the existing virtual machine (step S104). (No branch), the execution environment inspection unit 203 determines whether it is possible to create a virtual machine that meets the requested job execution requirements (step S106). In other words, the execution environment checking unit 203 determines that there is no virtual machine that satisfies the job execution requirement, and that it is not possible to provide an execution requirement that satisfies the job execution requirement even by changing an existing virtual machine. Next, it is determined whether or not it is necessary to newly create a virtual machine. Specifically, the execution environment inspection unit 203 refers to the physical machine management information storage unit 212 and determines whether there is a physical machine 22 capable of creating a virtual machine that meets the requested job execution requirement. I do.

  For example, the job requirement illustrated in FIG. 10B determines that it is necessary to newly create a virtual machine because “OS_C” is not installed in the virtual machine assigned to tenant A. You. In this case, referring to the physical machine management information shown in FIG. 5 and the job requirements shown in FIG. 10B, “OS_C” can be installed in the physical machine 22-2. It is determined that a suitable execution environment (virtual machine) can be created in the physical machine 22-2.

  If there is a physical machine 22 that can create a virtual machine that satisfies the job execution requirement (step S106, Yes branch), the execution environment inspection unit 203 creates a virtual machine that satisfies the requested job execution requirement. It is determined that it is possible (step S107). In this case, the execution environment inspection unit 203 sets the third inspection result as a result of the inspection regarding the job execution requirement.

  If there is no physical machine 22 capable of creating a virtual machine that meets the job execution requirement (step S106, No branch), the execution environment inspection unit 203 creates a virtual machine that meets the requested job execution requirement. Is determined to be impossible (step S108). In this case, the execution environment inspection unit 203 sets the fourth inspection result as a result of the inspection regarding the job execution requirement.

  In step S109, the execution environment inspection unit 203 notifies the job requirement processing unit 202 of any of the first to fourth inspection results and details thereof.

  Specifically, when the execution environment inspection unit 203 obtains the first inspection result, the execution environment inspection unit 203 attaches identification information (a virtual machine ID) for identifying a virtual machine that executes the job to the inspection result, and The processing unit 202 is notified.

  When the second inspection result is obtained, the execution environment inspection unit 203, together with the inspection result, identification information for identifying the virtual machine that needs to be changed, and the content of the change (for example, the name of the execution account to be added or the need for addition) To the job requirement processing unit 202).

  When the third inspection result is obtained, the execution environment inspection unit 203 sends, along with the inspection result, identification information that specifies the physical machine 22 capable of creating a virtual machine that meets the job execution requirement to the job requirement processing unit 202. Notify.

  When the fourth inspection result is obtained, the execution environment inspection unit 203 notifies the job requirement processing unit 202 that a virtual machine that meets the requested job execution requirement cannot be prepared.

  Next, the operation of the job execution system according to the first embodiment will be described with reference to FIG.

  In step S01, the terminal 10 inputs a job requirement by a user of the data center 20, and outputs the acquired job requirement to the job management device 21. The job requirement processing unit 202 of the job management apparatus 21 stores the acquired job requirements in the job requirement storage unit 211, and requests the execution environment inspection unit 203 to check the job execution requirements and the execution environment included in the job requirements. .

  In step S02, the execution environment inspection unit 203 refers to the job requirements, the physical machine management information, and the virtual machine management information, and performs an inspection on the job execution requirements and the execution environment. After that, the execution environment inspection unit 203 notifies the job requirement processing unit 202 of the inspection result (one of the above-described first to fourth inspection results).

  The job requirement processing unit 202 that has acquired the inspection result by the execution environment inspection unit 203 performs a process according to each inspection result.

  Specifically, when the first inspection result (which can be handled by the existing virtual machine) is obtained, the job requirement processing unit 202 executes the virtual job that executes the job included in the job requirement input from the terminal 10. The identification information specifying the machine is notified to the job execution control unit 205 (step S03).

  When the second inspection result (which can be dealt with by changing an existing virtual machine) is obtained, the job requirement processing unit 202 notifies the physical machine management unit 204 of the change content of the virtual machine, and Request a change. In this case, the physical machine management unit 204 instructs the physical machine 22 (more precisely, the hypervisor 302) to change the specification of the existing virtual machine based on the notified change content of the virtual machine (step S10). S04). When the specification change of the virtual machine is completed, the physical machine management unit 204 notifies the job requirement processing unit 202 of the change. Thereafter, the job requirement processing unit 202 notifies the job execution control unit 205 of identification information for specifying the virtual machine that executes the job.

  If the third inspection result (a new virtual machine needs to be created) is obtained, the job requirement processing unit 202 notifies the physical machine management unit 204 of the specifications of the newly created virtual machine, and Request creation. In this case, the physical machine management unit 204 instructs the physical machine 22 to create a new virtual machine based on the notified virtual machine specifications (Step S05). That is, the physical machine management unit 204 acquires a job execution requirement included in the job requirement as a specification of a newly created virtual machine, and creates an infrastructure that satisfies the job execution requirement. Specifically, the physical machine management unit 204 creates a virtual machine, installs an OS, an application, and middleware in the created virtual machine, and sets an execution account.

  When the creation of the virtual machine is completed, the physical machine management unit 204 notifies the job requirement processing unit 202 of the completion. Thereafter, the job requirement processing unit 202 notifies the job execution control unit 205 of identification information for specifying the virtual machine that executes the job.

  In step S06, the job requirement processing unit 202 responds to the job requirement input from the terminal 10. Specifically, if the first to third inspection results are obtained, the job requirement processing unit 202 can provide an environment that satisfies the job execution requirements included in the job requirements (the job execution Is notified to the terminal 10.

  On the other hand, when the fourth inspection result (a virtual machine satisfying the job execution requirement cannot be created) is acquired, the job requirement processing unit 202 provides an environment that satisfies the job execution requirement included in the job requirement. The terminal 10 is notified of the impossibility (error). At this time, the job requirement processing unit 202 may notify the terminal 10 of the information about the insufficient resources (memory capacity, disk capacity, etc.) and software, along with the error.

  Upon receiving the notification of the virtual machine that executes the job, the job execution control unit 205 refers to the job requirement storage unit 211 and sets the instructions included in the job definition information in the notified virtual machine (step S11). For example, the job execution control unit 205 instructs the virtual machine to set a script file at a predetermined position (a predetermined folder) of the virtual machine. More specifically, the job execution control unit 205 transmits the script file entity described in the job definition information to the virtual machine, and instructs the virtual machine to store the script file in a predetermined location.

  Alternatively, when the information related to the instructions described in the job definition information is, for example, path information indicating a storage location of the script file, the job execution control unit 205 transmits the path information to the virtual machine, and transmits the path information to the virtual machine. Of the script file from the location described in (1), and instruct to store it in a predetermined location.

  Thereafter, the job execution control unit 205 refers to the job requirement storage unit 211 at a predetermined timing or a predetermined time, and checks the schedule information (step S12).

  As a result of the confirmation, if it is determined that the job needs to be executed, the job execution control unit 205 instructs the virtual machine to execute the job (Step S13).

  The virtual machine that has received the instruction for executing the job executes the job (step S14).

  Thereafter, the user of the data center 20 operates the terminal 10 to refer to and obtain the job execution result (step S15).

  The processes related to steps S01 to S06 shown in FIG. 11 correspond to a phase for designing a job to be executed by the cloud system and a construction phase for creating an infrastructure. Further, the processing according to steps S11 to S15 corresponds to a job execution phase.

  As described above, the job execution system according to the first embodiment inputs the job (business process) execution requirements to the job management apparatus 21, and the job management apparatus 21 automatically constructs the job execution environment. It has a configuration (mechanism) to be performed. That is, when inputting the job requirements from the terminal 10 (when defining a job), the job management apparatus 21 has means for describing not only the information on the instructions but also the execution requirements. And save it. The job management device 21 determines whether an environment (virtual machine) that satisfies the execution requirement input together with the information on the instruction exists, and if not, determines whether an infrastructure that meets the execution requirement can be created. It has means for confirmation and determination. That is, the determination as to whether the defined job is executable is performed in advance. Further, the job management apparatus 21 has means for creating an environment (virtual machine, infrastructure) in which a job can be executed, and can create the environment before executing the job.

  By the functions of the above-described units included in the job management apparatus 21, there is no need for advance preparation of infrastructure or cooperation between persons in charge, and the person in charge of the project (operation person; the user of the terminal 10) designs and builds a job. By doing so, the necessary job is executed. In other words, one administrator can build the necessary infrastructure (execution environment) at any time without having to share the roles like the person in charge of the infrastructure and the person in charge of the business. Mistakes are reduced. In addition, since information including infrastructure information and definition information necessary for job management is coded, copying (migration) can be easily performed. It can be operated as a real environment.

  Note that the configuration (FIG. 2) of the job execution system described in the first embodiment is an example, and does not limit the configuration of the system. For example, each function of the job management device 21 may be realized by a plurality of devices. For example, as shown in FIG. 12, a device that processes a job requirement input from the terminal 10 (job management device 21a) and a device that manages the physical machines 22 in the data center 20 (cloud management device 31) are provided. It may be a system configuration. In this case, when the job management device 21a inputs the job requirement from the terminal 10, the job management device 21a requests the cloud management device 31 to provide an execution environment that meets the job execution requirement included in the job requirement. Upon receiving the request, the cloud management device 31 checks the job execution requirements and the virtual machines created on the physical machines 22 in the data center 20. The cloud management apparatus 31 prepares a job execution environment (virtual machine) in accordance with an inspection result such that an existing virtual machine can conform to job execution requirements, or that a new virtual machine needs to be created. Responds to a request from the device 21a. When it is possible to receive the provision of the job execution environment from the data center 20, the job management device 21a executes the job on the execution environment. As described above, the job management device 21a includes the functions of the job requirement processing unit 202 and the job execution control unit 205 described in the first embodiment, and the cloud management device 31 includes the execution environment inspection unit 203 The function of the physical machine management unit 204 can be included.

  Alternatively, as shown in FIG. 13, even if one job management device 21b and a plurality of data centers 20-1 to 20-m (m is a positive integer, the same applies hereinafter) are included in the job execution system. Good. That is, the job execution system may have a configuration in which the job execution environment is made redundant by the plurality of data centers 20-1 to 20-m. In this case, the job management device 21b can select the cloud management device 31 that requests the provision of the job execution environment in consideration of the operation status of each data center.

  In the first embodiment, the job execution control unit 205 starts the job according to the schedule information. However, the job execution environment (virtual machine) may be deleted after the job execution is completed. Specifically, after the execution of the job in the virtual machine is completed, the job execution control unit 205 may request the physical machine management unit 204 to delete the execution environment (virtual machine) of the job. That is, auto scaling in a cloud environment can be realized. Jobs are often executed at intervals of periods such as weekends and month ends, and at these timings, the load on the physical machine increases. Therefore, an instance (job execution requirement) for performing the target business process (job) is defined in advance, and a new virtual machine is created and started at the timing when the job needs to be executed ( Delete the virtual machine after the job execution is completed.) As a result, the resources of the physical machine that provides the job execution environment can be used efficiently. In the case of the normal auto-scaling, necessary instances can be created, but they are not linked to job management, and it is not possible to define a dependency between an instance and a job (application).

  In the first embodiment, a case has been described in which the job execution requirements include an application and middleware. However, there are jobs that do not require such software. In the first embodiment, the case where the type (name) of the software is included in the job execution requirement has been described. However, information on the software version and the license is included in the job execution requirement, and the physical machine management information and the virtual machine These pieces of information (information such as version and license) may be managed by the machine management information. That is, whether or not the execution environment can be provided may be determined in consideration of the version required for the execution environment and the version that can be provided by the execution environment. Alternatively, if there are not enough licenses that can be allocated to the virtual machine, it may be determined that the virtual machine cannot execute the job.

  Each unit such as a job requirement processing unit 202, an execution environment inspection unit 203, a physical machine management unit 204, and a job execution control unit 205 included in the job management device 21 according to the first embodiment is mounted on the job management device 21. The present invention can also be realized by a computer program that causes a computer to execute each process using the hardware. In other words, any means may be used for executing the function performed by the execution environment inspection unit 203 or the like with some kind of hardware and / or software.

  In the first embodiment, the case where one job is defined by the job requirement has been described, but details regarding the job network may be defined by the job requirement. In this case, one job requirement includes job execution requirements corresponding to a plurality of jobs and information on the execution order of the plurality of jobs. In such a case, the job management device 21 may perform the inspection and the construction of the environment described in the first embodiment for the individual job execution requirements included in the job requirements. Further, after the execution environment (virtual machine) corresponding to each job is prepared, the job management apparatus 21 executes each job (executes the execution control of the job network according to the information on the execution order of the jobs included in the job requirements). Do).

  Further, by installing the above-described computer program in the storage unit of the computer, the computer can function as a job management device. Furthermore, by causing the computer to execute the above-described computer program, the job management method can be executed by the computer. Also, the program can be downloaded via a network or updated using a storage medium storing the program.

  Further, in the plurality of flowcharts used in the above description, a plurality of steps (processes) are described in order, but the execution order of the steps executed in the embodiment is not limited to the described order. In the embodiment, the order of the illustrated steps can be changed within a range that does not hinder the contents, such as executing each processing in parallel.

Some or all of the above embodiments may be described as in the following supplementary notes, but are not limited thereto.
[Appendix 1]
This is the same as the job management method according to the first aspect described above.
[Appendix 2]
The job management method according to claim 1, wherein the step of creating the execution environment creates a virtual machine as the execution environment in the cloud system.
[Appendix 3]
The job management method according to claim 2, further comprising a checking step of performing the check on the execution requirement and the execution environment prior to the creation of the execution environment.
[Appendix 4]
The inspection step includes:
If the specifications of the existing virtual machine already created in the cloud system include the execution requirements and the execution process can coexist with other processes executed in the existing virtual machine, The job management method according to claim 3, wherein the existing virtual machine is determined to have an execution environment that meets the execution requirements.
[Appendix 5]
The inspection step includes:
When the difference between the specification of the existing virtual machine and the execution requirement is a predetermined difference, providing an execution environment that meets the execution requirement by changing the specification of the existing virtual machine. Is determined to be possible,
The job management method according to attachment 3 or 4, further comprising a step of changing a specification of the existing virtual machine so as to conform to the execution requirement.
[Appendix 6]
The inspection step includes:
If there is no virtual machine that satisfies the execution requirement, and it is not possible to provide an execution requirement that satisfies the execution requirement even by changing the existing virtual machine, a new virtual machine needs to be created. Is determined,
The step of creating the execution environment includes:
The job management method according to Appendix 5, wherein a new virtual machine that meets the execution requirement is created in the cloud system.
[Appendix 7]
7. The job management method according to claim 2, further comprising, before executing the execution process, setting the instruction in a virtual machine serving as the execution environment.
[Appendix 8]
8. The job management method according to claim 1, further comprising, after the execution of the execution process is completed, deleting the execution environment in which the execution process is executed.
[Appendix 9]
This is the same as the job management device according to the second aspect described above.
[Appendix 10]
This is as in the program according to the third aspect described above.
In addition, the form of Supplementary Note 9 and the form of Supplementary Note 10 can be expanded to the form of Supplementary Note 2 to the form of Supplementary Note 8 similarly to the form of Supplementary Note 1.

  The disclosures of the above cited patent documents and the like are incorporated herein by reference. Modifications and adjustments of the embodiments or examples are possible within the framework of the entire disclosure (including the claims) of the present invention and based on the basic technical concept thereof. In addition, various combinations or selections of various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) within the frame of the entire disclosure of the present invention. Is possible. That is, the present invention naturally includes various variations and modifications that can be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with respect to the numerical ranges described herein, any numerical values or small ranges included in the ranges should be construed as being specifically described even if not otherwise specified.

10 Terminal 20, 20-1 to 20-m Data Center 21, 21a, 21b Job Management Device 22, 22-1 to 22-n Physical Machine 31 Cloud Management Device 201 Communication Control Unit 202 Job Requirement Processing Unit 203 Execution Environment Inspection Unit 204 Physical machine management unit 205 Job execution control unit 211 Job requirement storage unit 212 Physical machine management information storage unit 213 Virtual machine management information storage unit 301 Hardware resource 302 Hypervisor 311 Virtual hardware 312 Guest OS
313 Application 314 Middleware

Claims (10)

Inputting information related to an instruction that defines the execution process of the business, and execution requirements including requirements for a guest OS, an application, middleware, and account information for executing the execution process;
If an execution environment that meets the execution requirements does not exist in the cloud system, creating an execution environment that meets the execution requirements in the cloud system;
Executing the execution process in an execution environment that meets the execution requirements;
Job management methods including:   The job management method according to claim 1, wherein the step of creating the execution environment creates a virtual machine as the execution environment in the cloud system.   3. The job management method according to claim 2, further comprising a checking step of checking the execution requirements and the execution environment prior to creating the execution environment. The inspection step includes:
If the specifications of the existing virtual machine already created in the cloud system include the execution requirements and the execution process can coexist with other processes executed in the existing virtual machine, 4. The job management method according to claim 3, wherein it is determined that the existing virtual machine has an execution environment that meets the execution requirements. The inspection step includes:
When the difference between the specification of the existing virtual machine and the execution requirement is a predetermined difference, providing an execution environment that meets the execution requirement by changing the specification of the existing virtual machine. Is determined to be possible,
5. The job management method according to claim 4, further comprising: changing a specification of the existing virtual machine so as to conform to the execution requirement. The inspection step includes:
If there is no virtual machine that satisfies the execution requirement, and it is not possible to provide an execution requirement that satisfies the execution requirement even by changing the existing virtual machine, a new virtual machine needs to be created. Is determined,
The step of creating the execution environment includes:
The job management method according to claim 5, wherein a new virtual machine that meets the execution requirement is created in the cloud system.   7. The job management method according to claim 2, further comprising, before executing the execution processing, setting the instruction in a virtual machine serving as the execution environment. 8. The job management method according to any one of claims 1 to 7, further comprising, after the execution of the execution process is completed, deleting an execution environment in which the execution process is executed. An input unit for inputting information related to an instruction that defines an execution process of a business, and an execution requirement including requirements of a guest OS, an application, middleware, and account information for executing the execution process;
If there is no execution environment that meets the execution requirements in the cloud system, an execution environment management unit that creates an execution environment that meets the execution requirements in the cloud system ,
An execution unit that executes the execution process in an execution environment that meets the execution requirements;
A job management device comprising: A process of inputting information related to an instruction that defines a process of executing a business, and an execution requirement including a requirement of a guest OS, an application, middleware, and account information for executing the execution process;
If there is no execution environment that meets the execution requirements in the cloud system, a process of creating an execution environment that meets the execution requirements in the cloud system;
A process of executing the execution process in an execution environment that meets the execution requirement;
That causes a computer mounted on a job management device to execute the program.

Images