JP5396339B2 - Resource control method and resource control system - Google Patents

Description

  The present invention relates to a technique of a method for assigning resources to virtual machines in a virtual system environment.

  Active efforts are being made to reduce IT costs by virtualizing multiple machines running business applications and consolidating them into a single physical machine. For example, if a certain business runs on a system that is physically composed of three machines, it costs IT costs by constructing and operating three virtual machines on one physical machine. Can be reduced to one-third of the conventional value.

  Here, the number of virtual machines (aggregation level) per physical machine is directly linked to the cost that can be reduced, so in order to further increase the degree of aggregation, the “average” resource required by each virtual machine In many cases, a virtual machine is arranged on a physical machine so that the total amount is equal to the resource amount of the physical machine. This makes it possible to place more virtual machines on a physical machine with limited resources. Therefore, on the contrary, the sum of the “maximum” resource amount required by each virtual machine that operates a business application is generally larger than the resource amount that a physical machine has.

  When the sum of the maximum resource amounts required by the virtual machine exceeds the resource amount of the physical machine, it is necessary to appropriately and appropriately determine the amount of resources allocated to each virtual machine.

  In the conventional technique, as shown in Patent Document 1, the amount of resources allocated to each virtual machine is determined according to a predetermined ratio or a fixed value for each virtual machine. Furthermore, when there is a surplus resource in a certain virtual machine, the surplus resource is collected, and then the surplus resource is reassigned to the lacking virtual machine.

Patent application title: Resource control method and system

  When a business system that is already in operation is virtualized and consolidated, a plurality of business applications may operate on a single virtual machine, or a single business may be executed across a plurality of virtual machines. In such a case, a resource that can be used in a certain job may be affected by another job executed on the same virtual machine. However, in the prior art, since resource allocation is performed in units of virtual machines, consideration is not given to cases where they are affected by other business operations. With resource allocation in units of virtual machines in the prior art, it is not possible to allocate resources from a business viewpoint that takes into account the impact of business operations executed on the same virtual machine.

  In the present invention, when a plurality of tasks are executed on one machine or when one task is executed across a plurality of machines, resources can be allocated from a task viewpoint. With the goal.

In the present invention, a “business space” is defined as a space for executing a business in a virtual space in a physical machine, and resources are allocated to the business space.
A copy of a virtual machine necessary for execution of the business is placed in the business space described above, and these virtual machines are operated using resources allocated to the business space. By causing only virtual machines arranged in the business space to execute the business, the machines that execute the business can be aggregated in the business space, and a certain resource can be allocated to each business.

  At this time, the resource allocation to the business space and the virtual machine arranged in the business space is controlled from the execution status of the job constituting the business allocated to each business space. By using the job execution status instead of the actual resource usage status, it is possible to correctly grasp the amount of resources required for the business and perform appropriate resource allocation.

  According to the present invention, in a virtualization system, when a plurality of tasks are executed on one virtual machine, or when one task is executed across a plurality of virtual machines, resource allocation is performed from a task viewpoint. Can be done.

Explanatory drawing which showed the whole structure in Example 1. Explanatory drawing which showed the detail of the work space of Example 1. Explanatory drawing which showed the detail of the memory | storage part of Example 1. FIG. Conceptual diagram of jobs in the first embodiment Job management table in the first embodiment Resource allocation management table by business in Example 1 Business space management table in the first embodiment Business space resource allocation management table in the first embodiment Job execution status management table in the first embodiment Flow chart showing the flow of business space allocation in the first embodiment Flowchart showing the flow of job execution in the first embodiment Flowchart showing the flow of resource allocation in the first embodiment Conceptual diagram showing assignment to business space in Example 1 Resource allocation management table in Embodiment 1 Screen that displays the job execution status and resource allocation status in Example 1 Explanatory drawing which showed the whole structure in Example 2. Explanatory drawing which showed the detail of the management manager in Example 2. Explanatory drawing which showed the detail of the memory | storage part of the management manager in Example 2. FIG. Job management table for management manager in embodiment 2 Resource allocation management table for business managers according to the second embodiment Business manager management space management table in the second embodiment Business manager resource allocation management table for management manager in embodiment 2 Management manager job execution status management table in the second embodiment Machine resource management table for management manager in embodiment 2 The flowchart which showed the outline | summary of the flow which allocates a business space to each operation | work in Example 2, and allocates a business space to each execution machine. The flowchart which showed the flow which allocates work space to each work in Example 2. The flowchart which showed the flow which allocates business space to each execution machine in Example 2. The flowchart which showed the flow which allocates (updates) business space with respect to each execution machine in Example 2. The flowchart which showed the flow at the time of performing a job in Example 2. The flowchart which showed the flow at the time of submitting a job to work space in Example 2. The flowchart which showed the flow which moves work space in Example 2. The flowchart which showed the flow which deletes work space in Example 2.

  Embodiments of the system according to the present invention will be described below with reference to the drawings.

First, terms used below will be described.
A job is one of procedures for configuring a business or service, and includes business application, command, script execution, and the like. A job definition that defines job execution content is called a job definition, and an identifier for identifying the job definition is called a job ID.

  A business is a set of a plurality of jobs, and a series of procedures can be executed by defining a trigger for executing a job or a job that is continuously executed after execution of a certain job. The definition of this series of procedures is called a business definition, and an identifier for identifying the business definition is called a business ID.

  A virtual machine is a logical machine that operates in a physical machine by virtualization technology, has an independent OS, and operates in the same way as a physical machine. The resources required for virtual machine operation are shared by multiple virtual machines operating in the physical machine, and each virtual machine is allocated and used as a virtual resource. The At this time, it is possible to decide how many physical machine resources are allocated to which virtual machine. A resource shared by a plurality of virtual machines includes a CPU and a memory.

  In addition, a virtual machine copy can be easily created by copying a logical volume constituting the virtual machine.

  In the present embodiment, a case will be described in which resources for adjusting the allocation amount for each business are a CPU and a memory, and the allocation ratio is the same. It is also possible in the concept of the present invention to reduce the resources to be managed, add other resources as management targets, and determine the allocation ratio to work for each resource.

  Also, in this embodiment, when the present invention is applied to a plurality of physical machines, a business space corresponding to the execution status of a job on each execution machine and a virtual machine executed on the business space A method of controlling the resource allocation in each execution machine will be described. It is also possible in the concept of the present invention to collectively perform these controls in the management manager.

FIG. 1 is an explanatory diagram showing the overall configuration of the first embodiment of the present invention. An example in which a virtual system is configured in the physical computer 100 is shown.
The physical computer 100 includes a disk interface 110, a communication interface 111, a CPU 112, a memory 113, and a display interface 114. The storage unit 101 is connected through the disk interface 110, the network 102 is connected through the communication interface 111, and the display device 103 is connected through the display interface 114. The memory 113 is loaded with the OS 120, job management unit 121, business space management unit 122, and virtualization unit 123, and business spaces 124 and 125 described later are secured. One or more virtual machines are assigned to the business space. Details of the business space will be described with reference to FIG. 2, and details of the storage unit will be described with reference to FIG.

  Based on the information in the job management table 300 and the business-specific resource allocation management table 301 shown in FIG. 3, the job management unit 121 allocates a business space for each business, operates a virtual machine in the allocated business space, It is a processing unit that executes jobs in a virtual machine and manages the execution status thereof. Details of these processes are shown in FIGS.

  The business space management unit 122 manages resource allocation for each business space and virtual machine based on the information in the business space management table 302, the business space resource allocation management table 303, and the job execution status management table 304 shown in FIG. It is a processing part to perform. Details of this processing are shown in FIG.

FIG. 2 is an explanatory diagram showing a detailed configuration of the business space. In order to simplify the explanation, a single virtual machine is assumed.
The business space 124 includes a logical CPU 200 and a logical memory 201 which are resources used in the business space, and one or a plurality of virtual machines 130 and one or a plurality of virtual disks 131 are allocated thereto.

  The virtual machine 130 is recorded as a logical volume in the storage unit 101, and operates as a virtual machine by loading it into memory as necessary. The virtual machine 130 includes a logical disk interface 210, a logical communication interface 211, a logical CPU 212, a logical memory 213, and a logical display interface 214. Further, it is connected to the virtual disk 131 through the logical disk interface 210. The logical memory 213 is loaded with the OS 220, the job execution unit 221, and one or more business applications 222.

  The virtual disk 131 is recorded as a logical volume in the storage unit 101, and contents read and written through the logical disk interface of the virtual machine 130 are reflected in the logical volume in the storage unit 101.

FIG. 3 is an explanatory diagram showing a detailed configuration of the storage unit 101.
The storage unit 101 stores a job management table 300, a business-specific resource allocation management table 301, a business space management table 302, a business space resource allocation management table 303, a job execution status management table 304, and a resource allocation management table 305. In addition, virtual machine logical volumes 310 and 312 and virtual disk logical volumes 311 and 313 are stored as logical volumes of virtual machines and virtual disks.

  FIG. 4 is a conceptual diagram showing the business executed in the present embodiment, the job constituting the business, its execution host, and the execution order. Circles in the figure represent jobs, and arrows represent job execution order. This information is managed in the form of a job management table 300 shown in FIG.

In this embodiment, business 1 (410) to business 4 (440) are executed on three hosts, host A, host B, and host C.
The business 1 (410) includes a job 1A (411), a job 1B (412), and a job 1C (413), which are executed in this order. Similarly, job 2 (420) is job 2A1 (421), job 2A2 (422), job 2C (423), and job 3 is job 3A1 (431), job 3A2 (432), job 3C (433). The business 4 (440) is composed of a job 4C (441). Job 1A (411), job 2A1 (421), and job 2A2 (422) are executed on host A. Similarly, job 1B (412), job 3B1 (431), and job 3B2 (432) are job 1C (413), job 2C (423), job 3C (433), and job 4C (441) on host B. Is executed on the host C.

FIG. 5 shows details of the job management table 300.
A table for managing jobs and job execution contents. A job ID 500, a job ID 501, command contents 502 executed by each job, a host 503 for executing the job, and a job executed after the job is executed. It has job ID 504 and information of job ID 505 of the job to be executed before executing the job. FIG. 5 shows an example in which the business definition shown in FIG. 4 is stored.

  FIG. 6 shows details of the business-specific resource allocation management table 301. This table manages the resource allocation amount for each business ID, and has information on the business ID 600 and the resource allocation ratio 601. The resource allocation ratio 601 corresponds to a numerical value of the business priority. The resource allocation ratio 601 is a resource allocation amount when the entire computer resource is 100%, and therefore determines the resource amount to be allocated for each business. In this embodiment, the resource allocation ratio 601 or a specific resource amount calculated from the allocation ratio is referred to as a business resource amount. The business resource amount can be changed in advance through a user setting screen.

  FIG. 7 shows details of the business space management table 302. A table for managing a business belonging to a business space and a host constituting the business space, and has information of a business ID 700, a business space ID 701, and a configuration host 702. The business space management table 302 is created by the procedure shown in FIG.

  FIG. 8 shows details of the business space resource allocation management table 303. This table manages the allocation ratio of computer resources allocated to each business space, and has information on business space ID 800 and resource allocation ratio 801. The business space resource allocation management table 303 is created by the procedure shown in FIG. The resource allocation ratio is a resource amount to be allocated for each business space when the entire computer resource is 100%. Thereby, resources are allocated to the business space according to the business priority. In this embodiment, the resource allocation ratio 801 or a specific resource amount calculated from the allocation ratio is referred to as a spatial resource amount.

FIG. 9 shows details of the job execution status management table 304.
This table manages jobs being executed for each business space, and has information on business space ID 900, job execution ID 901, job ID 902, and execution host 903.
The job execution status management table 304 is created by the procedure shown in FIG.

  FIG. 10 is a flowchart illustrating a flow in which the job management unit 121 assigns a business space to each business. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The job management unit 121 refers to the job management table 300 and the task-specific resource allocation management table 301 and performs allocation processing to the task space in order from the task with the highest priority (1000). First, a new work space for assigning work is defined (1001). A business space ID is allocated to the defined business space for management. Among the tasks that have not been assigned a business space, the business with the highest priority is assigned to the business space defined in 1001, and the business space management table 302 is updated (1002). The business space management table 302 is referred to, and a machine necessary for configuring the business space is calculated (1003). Referring to the business space management table 302 and the business resource allocation management table 301, the priority for the business space is calculated, and the business space resource allocation management table 303 is updated (1004). It is checked whether the defined business space satisfies the following formula 1 (1005). By checking whether the resources necessary for the operation of the virtual machine required for the configuration of the business space are sufficiently small with respect to the resources allocated to the business space, the business space can be allocated efficiently. The “coefficient” in the equation is determined in advance according to resources and physical machine characteristics.

数１を満たす場合、業務空間への業務の割り当てを確定とし、次の業務空間の定義と業務の割り当てのため、１０００に戻る（１００７）。この場合、１００２で割り当てられた業務が、１００１で定義した業務空間を占有する。数１を満たさない場合、業務空間の割り当てがおこなわれていない業務のうち次に優先度の高い業務を、１００１で定義した業務空間に追加で割り当て、業務空間管理テーブル３０２を更新した後、１００３の手順から繰り返す（１００６）。この場合、１００１で定義した業務空間は、数１を満たすように複数の業務で共有される。以上の処理を、すべての業務について業務空間が割り当てられるまで繰り返す（１００８）。

If Equation 1 is satisfied, the assignment of the work to the work space is confirmed, and the process returns to 1000 for the definition of the next work space and the assignment of the work (1007). In this case, the business assigned in 1002 occupies the business space defined in 1001. If the number 1 is not satisfied, a task having the next highest priority among tasks that have not been assigned a task space is additionally allocated to the task space defined in 1001, and the task space management table 302 is updated, and then 1003 The above procedure is repeated (1006). In this case, the business space defined in 1001 is shared by a plurality of businesses so as to satisfy Equation 1. The above processing is repeated until a business space is assigned for all business operations (1008).

  After the completion of the assignment process, the job management unit 121 notifies the virtualization unit 123 to create a business space and a necessary virtual machine copy (1009). The virtualization unit 123 refers to the business space management table, creates a copy of the virtual machine logical volume and virtual disk logical volume recorded in the storage unit 101, and stores the business space and the required virtual machine in the memory. expand.

  FIG. 13 shows an example in which the work shown in FIG. 4 is assigned to the work space according to the above flow.

  FIG. 11 is a flowchart illustrating a flow in which the job management unit 121 executes a job. First, the job management unit 121 acquires a job ID and a job execution host from the job management table 300 (1100). With reference to the business space management table 302, the business space for executing the job is acquired from the business ID (1101). The job management unit 121 notifies the job execution unit 221 on the execution host in the business space acquired in 1101 of the information of the job to be executed, and causes the job to be executed on the virtual machine in the business space (1102). .

  The job management unit 121 adds an execution job entry to the job execution status management table 304 (1103). The job management unit 121 periodically checks the job execution status with the job execution unit 221 (1104). When the job execution has been completed, the job management unit 121 deletes the entry of the execution job from the job execution status management table 304 (1105, 1107). If the job execution has not ended, the information in the job execution status management table 304 is updated, and the process returns to 1004 (1106). As a result, only the entry of the job being executed is always recorded in the job execution status management table.

  With reference to the job management table 300, it is confirmed whether the next job is defined (1108). If the next job is defined, the job specified by the next job ID is executed, and the execution of the job is terminated (1109). If the next job is not defined, the execution of the job is terminated as it is.

  FIG. 12 is a flowchart showing a flow in which the business space management unit 122 allocates resources to each business space and each virtual machine. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The business space management unit 122 performs resource allocation processing in order for all business spaces (1200). First, the business space management unit 122 obtains resources allocated to the business space from the business space resource allocation management table 303, and determines the allocation amounts to the logical CPU 200 and the logical memory 201 in the business space (1201). The business space management unit 122 acquires the number of jobs being executed in the business space from the job execution status management table 304 (1202). The business space management unit 122 acquires a host in the business space from the business space management table 302, and sequentially performs resource allocation processing for all the hosts in the business space (1203). The business space management unit 122 acquires job execution information from the job execution status management table 304. For example, the number of jobs being executed on the host is acquired (1204). The amount of resources allocated to the host is determined by the following formula 2 (1205). Resources allocated to the business space are allocated to the hosts according to the number of jobs being executed.

以上の手順で決定したホストごとのリソース割り当て量で、リソース割り当て管理テーブル３０５を更新する（１２０６）。これを、業務空間と、各業務空間を構成するホストの数だけ繰り返す（１２０７、１２０８）。

The resource allocation management table 305 is updated with the resource allocation amount for each host determined by the above procedure (1206). This is repeated by the number of business spaces and the number of hosts constituting each business space (1207, 1208).

  The business space management unit 122 requests the virtualization unit 123 to allocate resources (1209). The virtualization unit 123 allocates resources to the virtual host according to the information in the resource allocation management table 305. In the example shown in FIGS. 8 and 9, three jobs having job execution IDs 003, 006, and 007 are being executed in the business space 3, and the resource 20 assigned to the business space 3 for each job. % Is evenly allocated by 6.66%. Since the job with the job execution ID 003 is being executed by the host B and the jobs with the job execution IDs 006 and 007 are being executed by the host C, the resources allocated to each host are 6.67% for the host B and 13 for the host C. .33%.

  For example, when all jobs executed in the business space 3 are completed, the amount of space resources allocated to the business space 3 can be redistributed to other business spaces having jobs currently being executed. It is.

業務空間３で実行していた全てのジョブが終了した場合、現在実行中のジョブを有する業務空間は、業務空間１と業務空間２となる。図８の業務空間リソース割当管理テーブル３０３に定義する業務空間１の５０％と業務空間２の３０％との割合を維持しながら、再配分すればよい。上述数３に基づいて再配分すると、業務空間１に対して６２．５％、業務空間２に対して３７．５％を配分する。この再配分された空間リソース量に基づいて、各業務空間で実行中のジョブを稼働するホストに対するリソース量を再計算すればよい。また新たに業務空間３の業務３を稼働させたい場合は、上述のように実行中のジョブの状況を再確認し、業務空間に割当てるべき空間リソース量を上述数３に基づいて再調整することで、実現できる。このように、業務空間に対して割当てるべき空間リソース量を、業務の優先度に応じて適宜調整することで、業務を遂行する仮想マシンに対するリソース量を、他の優先度の高い業務への空間リソース量を配慮し、維持しながら適宜自由に設定することができる。

When all the jobs that have been executed in the business space 3 are completed, the business spaces having the job that is currently being executed are the business space 1 and the business space 2. Redistribution may be performed while maintaining the ratio of 50% of the business space 1 and 30% of the business space 2 defined in the business space resource allocation management table 303 of FIG. When reallocation is performed based on the above equation 3, 62.5% is allocated to the business space 1 and 37.5% is allocated to the business space 2. Based on the redistributed space resource amount, the resource amount for the host operating the job being executed in each business space may be recalculated. In addition, when the business 3 in the business space 3 is newly operated, the status of the job being executed is reconfirmed as described above, and the amount of space resources to be allocated to the business space is readjusted based on the above formula 3. It can be realized. In this way, by appropriately adjusting the amount of space resources that should be allocated to the work space according to the priority of the work, the amount of resources for the virtual machine that performs the work is reduced to the space for other high-priority work. It can be set freely as needed while considering and maintaining the amount of resources.

  As described above, the business-specific resource allocation management table 301 can be changed on the setting screen from the user. Therefore, when the business resource amount is changed while the system is operating, the spatial resource amount is determined according to the above procedure. It is possible to reconfigure and change the amount of resources for a running virtual machine. Thus, the amount of space resources that can be allocated to the business space can be changed as appropriate according to the status of the job being executed.

  FIG. 13 is a conceptual diagram showing an example in which the work shown in FIG. 4 is assigned to the work space according to the flow shown in FIG. Business 1 is executed in business space 1 (1300), business 2 is executed in business space 2 (1310), and business 3 and business 4 are executed in business space 3 (1320). In the business space 1 (1300), virtual machine replicas necessary for execution of the business 1 are arranged. In each virtual machine, a job 1A (411), a job 1B (412), a job 1C (related to the business 1) are stored. Only 413) is executed. In the business space 2 (1310), a replica of the virtual machine of the host B that is unnecessary for the execution of the business 2 is not arranged. In the host C arranged in the business space 3 (1320), both the job 3C (433) constituting the business 3 and the job 4C (441) constituting the business 4 are executed.

FIG. 14 shows details of the resource allocation management table 305.
It is a table for managing the hosts arranged in the business space and the resource allocation status to each host, and has information on business space ID 1400, host name 1401, and resource allocation amount 1402. The resource allocation management table 305 is created by the procedure shown in FIG.

  FIG. 15 is a diagram showing a screen for displaying the business space allocation status, job execution status, and resource allocation status to the administrator. It is displayed on the display device 103.

  The generated business space and the status of the host replicated in each business space are indicated by 1500 to 1502 and 1510 to 1516, respectively. The status of the business being executed is indicated by 1520 to 1535. Reference numerals 1520 to 1535 represent jobs, and a job being executed is displayed so that it can be identified by a color or the like, such as 1520. As a result, it is possible to visually confirm how many jobs of which business are being executed on which host. The job execution status is also shown in tables 1540 to 1542 and can be confirmed in a list format.

  The resource allocation status to each virtual host is shown in 1510 to 1516 and can be visually confirmed together with the job execution status.

  FIG. 16 is an explanatory diagram showing the overall configuration of the second embodiment when the present invention is applied to a plurality of physical machines. Physical computers 100 and 1610 capable of executing business are secured as computer resources 1600. In order to simplify the explanation, two physical computers are secured as computer resources. The detailed configuration of the physical computers 100 and 1610 is as described with reference to FIG. A physical computer secured as a computer resource is connected to the management manager through the network 102. Details of the management manager will be described with reference to FIG.

  FIG. 17 is an explanatory diagram showing details of a management manager that controls the assignment of the entire business space, jobs, and resources when the present invention is applied to a plurality of physical machines. An example in which the management manager is configured in a physical computer 1700 is shown.

  The physical computer 1700 includes a disk interface 1710, a communication interface 1711, a CPU 1712, a memory 1713, and a display interface 1714. Further, the storage unit 1701 is connected through the disk interface 1710, the network 102 is connected through the communication interface 1711, and the display device 1703 is connected through the display interface 1714. The memory 1713 is loaded with an OS 1720, a management manager job management unit 1721, and a management manager execution machine management unit 1722, and jobs of a physical computer (hereinafter referred to as an execution machine) that executes a task secured as a computer resource. And control resource allocation. The management manager controls the allocation of the business space to the execution machine, the allocation of resources to the business space, and the submission of jobs to the business space, but the business space according to the job execution status on the execution machine In addition, the allocation of resources to virtual machines executed on the business space is performed on each execution machine according to the procedure described above.

  FIG. 18 is an explanatory diagram showing details of the storage unit 1701. The storage unit 1701 includes a management manager job management table 1800, a management manager business resource allocation management table 1801, a management manager business space management table 1802, a management manager business space resource allocation management table 1803, and a management manager job execution. A status management table 1804 and a management manager machine resource management table 1805 are stored. Further, virtual machine logical volumes 1810 and 1812 and virtual disk logical volumes 1811 and 1813 are stored as logical volumes of virtual machines and virtual disks.

  When a plurality of execution machines are controlled using the management manager, the job management table 300 and the job-specific resource allocation management table 301 defined on the execution machine are the management manager job management table 1800 and the management manager respectively. This is defined in the business-specific resource allocation management table 1801. The job management table 300, the business space management table 302, and the business space resource allocation management table 303 of the execution machine are updated from the management manager. In addition, the logical volume of the virtual machine or virtual disk is transferred to the execution machine by the management manager as necessary. Therefore, all definitions necessary for operation are performed by the management manager.

  FIG. 19 shows details of the management manager job management table 1800. The job management table and the job execution contents are the same as those in the job management table 300 shown in FIG. 5. The job ID 1900, the job ID 1901, and the contents of the command executed by each job. 1902, the host 1903 that executes the job, the job ID 1904 of the job that is executed after the job is executed, and the job ID 1905 of the job that is executed before the job is executed. The job management table 300 manages only information on jobs executed on the physical computer, whereas the management manager job management table 1800 manages information on jobs executed on the entire computer resource. This information can be defined in advance through the user setting screen, and can be changed through the user setting screen. In order to simplify the explanation, an example in which business 1 to business 6 are defined is shown.

  FIG. 20 shows details of the business manager resource allocation management table 1801 for management manager. It is a table for managing the resource allocation amount for each business, and has information of business ID 2000, resource allocation amount 2001, minimum multiplicity 2002, and maximum multiplicity 2003. The resource allocation amount 2001 represents the resource allocation ratio 601 in the business-specific resource allocation management table 301 shown in FIG. 6 as a relative ratio to the resources of the execution machine, whereas the resources of a plurality of execution machines In order to cope with the difference, it is expressed by an absolute resource amount. The minimum multiplicity 2002 defines the minimum number of business spaces to be created when executing the business. The maximum multiplicity 2003 defines how many business spaces are created when executing the business. This information can be defined in advance through the user setting screen, and can be changed through the user setting screen.

  FIG. 21 shows the details of the management manager business space management table 1802. A table for managing a business to be executed in the business space, a host constituting the business space, an execution machine of the business space, and a resource allocation amount necessary for executing the business space, and a business space ID 2100, a business ID 2101, and a configuration. It has information on the host 2102, the execution machine 2103, and the resource allocation amount 2104. The management manager business space management table 1802 is created according to the procedure shown in FIGS. In addition, addition, change, and deletion are performed in the procedures shown in FIGS. 29, 31, and 32, respectively.

  FIG. 22 shows the details of the management manager business space resource allocation management table 1803. A table for managing the resource allocation amount for each execution space and the currently required resource amount determined from the execution status of the operation in the operation space for each execution machine. The execution machine 2200, the operation space ID 2201, the resource allocation amount 2202, and the required resources It has information of amount 2203. The required resource amount 2203 represents the resource amount that actually needs to be allocated, determined from the job execution status in the business space. In other words, even if resources are allocated to the business space, if a job is not executed in the business space, it is not necessary to allocate resources to the business space, and it can be obtained by considering the job execution status. Represents the amount of resources actually required at that time. The management manager business space resource allocation management table 1803 is created according to the procedure shown in FIG. Moreover, it is changed by the procedure shown in FIGS. 30 and 31, and is deleted by the procedure shown in FIG.

  FIG. 23 shows the details of the management manager job execution status management table 1804. It is a table for managing whether or not a job being executed and a new job can be submitted for each business space, and includes information on a business ID 2300, a business space ID 2301, a job execution ID 2302, and a job submission availability 2303. The job submission availability 2303 indicates whether a new job can be submitted to the business space. When deleting the business space, the job submission permission / prohibition 2303 is used to prevent the new job from being submitted and free up the business space. The management manager job execution status management table 1804 is created according to the procedure shown in FIG. In addition, they are added, changed, and deleted by the procedures shown in FIGS. 29, 30, and 32, respectively.

  FIG. 24 shows details of the management manager machine resource management table 1805. A table that manages the amount of resources held for each execution machine, the amount of unallocated resources, and the amount of resources that are currently surplus determined from the execution status of tasks in the business space. It has information on the allocated resource amount 2402 and the surplus resource amount 2403. The possessed resource amount 2401 represents the resource amount of the machine as an absolute value. The unallocated resource amount 2402 is a resource amount that is not explicitly allocated to the business space, and represents a resource amount that can be allocated when the business space is added to the machine. It is used to determine whether to add a business space when executing a business or to determine the destination when a user moves the business space. The surplus resource amount 2403 is obtained by subtracting the total amount for the execution machine of the required resource amount 2203 shown in the management manager business space resource allocation management table 1803 in FIG. 22 from the resource amount 2401 of the execution machine. Represents the surplus resource amount after allocating the necessary resources for each job currently being executed on the machine. In practice, the surplus resources are allocated to the business space where the business is being executed and are used by the job being executed according to the procedure shown in FIG.

  Of the information in the management manager machine resource management table 1805, the execution machine 2400 and the owned resource amount 2401 are defined in advance by the user based on the information of the execution machine secured as computer resources. The unallocated resource amount 2402 and the surplus resource amount 2403 are set according to the procedure shown in FIG. Moreover, it changes in the procedure shown in FIG.30, FIG.31, FIG.32.

  FIG. 25 is a flowchart showing a flow in which the management manager allocates a business space to each business and allocates a business space to each execution machine. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The management manager job management unit 1721 assigns a business space to each business (2500). This process will be described in detail with reference to FIG. Next, the execution machine management unit 1722 for management manager assigns execution machines to each business space (2501). This process will be described in detail with reference to FIG. After assignment of the business space to the execution machine is completed, the business space is updated for all execution machines (2502). A necessary management table or logical volume is transferred to each execution machine, and the virtualization unit 123 of each execution machine is instructed to add or delete a business space (2503). This process will be described in detail with reference to FIG. The processing of 2503 is repeated until the update of the business space is completed for all execution machines (2504).

  FIG. 26 is a flowchart illustrating a flow in which the management manager job management unit 1721 allocates a business space to each business. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The management manager job management unit 1721 refers to the management manager job management table 1800 and the management manager task-specific resource allocation management table 1801 and performs allocation processing to a task space.

  First, for all tasks having a maximum multiplicity of 2 or more, allocation processing to the task space is performed (2600). For a task having a maximum multiplicity of 2 or more, a task space is added or deleted, and therefore the task space is allocated by the task alone. First, a new work space for assigning work is defined, and work for which work space is not assigned is assigned to the defined work space (2601). At this time, a business space ID is assigned to the defined business space so as to be unique for management. In accordance with the assignment result in 2601, the management manager business space management table 1802 is updated for the business space ID and the business ID (2602). In accordance with the definition and assignment result in 2601, the assignment result is added to the management manager job execution status management table 1804 (2603). At this time, there is no job execution ID, and whether or not a job can be submitted is “enabled”.

  Next, a machine necessary for configuring the business space is calculated (2604). With reference to the business manager resource allocation management table 1801 for the manager, the resource allocation amount for the business space is acquired (2605). The business space management table for business space management manager 1802 is updated for the configuration host and resource allocation (2606). The business space management table 1802 for the business space management manager is duplicated so that the number of minimum multiplicity is reached (2607). At this time, only the business space ID is updated to be unique. The above processing is repeated until a business space is allocated for all business operations having a maximum multiplicity of 2 or more (2608).

  Next, for all the tasks that have not been assigned a business space, assignment processing to the business space is performed in order from the business with the highest priority (2609). This allocation process is almost the same as that shown in FIG. First, a business space for assigning a business is newly defined, and a business with the highest priority is assigned to the defined business space among business for which business space is not assigned (2610). A business space ID is assigned to the defined business space so as to be unique for management. The management manager business space management table 1802 is updated for the configuration host and resource allocation amount (2611). In accordance with the assignment result in 2610 or 2616 described later, the assignment result is added to the job execution status management table for management manager 1804 (2612). The management manager business space management table 1802 is referred to, and a machine required to configure the business space is calculated from the business executed in the business space (2613). With reference to the management manager business space management table 1802 and the management manager business resource allocation management table 1801, the resource allocation amount for the business space is calculated (2614). It is checked whether the defined business space satisfies Equation 1 (2615). Equation 1 uses the same formula as in the first embodiment. As in the case of FIG. 10, the allocation of the business space is performed by checking whether the resources necessary for the operation of the virtual machine required for the configuration of the business space are sufficiently small with respect to the resources allocated to the business space. Can be done efficiently. The “coefficient” in the formula is determined in advance according to the resource and the characteristics of the execution machine secured in the computer resource 1600.

  When Equation 1 is satisfied, the assignment of the work to the work space is confirmed, and the work space management table for management manager 1802 is updated for the configuration host and the resource allocation amount (2616). After that, the process returns to 2609 to define the next business space and assign the business (2617). In this case, the assignment result in 2610 is confirmed, and one business occupies the business space defined in 2610.

  If the number 1 is not satisfied, a task having the next highest priority among tasks that have not been assigned a task space is additionally allocated to the task space defined in 2610, and then the procedure of 2611 is repeated (2616). In this case, the business space defined in 2610 is shared by a plurality of businesses so as to satisfy Equation 1. The above processing is repeated until a business space is assigned for all business operations (2618).

  FIG. 27 is a flowchart illustrating a flow in which the management manager execution machine management unit 1722 allocates a business space to each execution machine. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The management manager execution machine management unit 1722 refers to the management manager business space management table 1802 and the management manager business space resource allocation management table 1803 and performs business space allocation processing. For all business spaces to which no execution machine is allocated, allocation processing to the execution machines is performed in descending order of resource allocation (2700). First, in order to determine the execution machine to which the business space is allocated, the execution machine having the largest number of unallocated resources is searched (2701). On the retrieved execution machine, it is confirmed that no other business space for executing the same business is assigned (2702). If another business space that executes the same business has already been allocated on the searched execution machine, a search is made for the next largest unallocated resource among the execution machines, and the evaluation is returned to 2702 and evaluated again. (2703). If it is confirmed in the evaluation of 2702 that no other business space for executing the same business is allocated on the searched execution machine, the business space is allocated to the execution machine (2704).

According to the determined allocation, the management manager business space management table 1802 is updated for the execution machine (2705). The management manager business space resource allocation management table 1803 is updated for the execution machine, business space ID, resource allocation amount, and required resource amount. Here, for the business space to be newly added, the required resource amount is set to 0 (2706). The management manager machine resource management table 1805 is updated for the unallocated resource amount and the surplus resource amount. The surplus resource amount is obtained by subtracting the necessary resource amount of the execution machine from the retained resource amount, and is assumed to be the same as the surplus resource amount (2707).
The above processing is repeated until execution machines are assigned to all the business spaces (2708).

  FIG. 28 is a flowchart showing a flow in which the management manager execution machine management unit 1722 assigns (updates) a business space to each execution machine. Although an example of the allocation method is shown, the allocation method is not limited to this.

  The management machine execution machine management unit 1722 updates the contents of the job management table 300 of the execution machine (2800). The job definition of the job executed on the execution machine is transferred from the management manager to the execution machine, and the update is reflected. If the job management table 300 has a job definition for a job that is not executed on the execution machine, the job definition is deleted.

  The management machine execution machine management unit 1722 updates the contents of the business space management table 302 of the execution machine (2801). For the business space executed on the machine, the business space ID, the business ID, and the configuration host information are transferred from the management manager business space management table 1802 to the business space management table 302 of the execution machine, and the update is reflected. If the business space management table 302 has a business space definition that is not executed on the execution machine, the definition is deleted.

  The execution machine management unit 1722 for management manager updates the contents of the business space resource allocation management table 303 of the execution machine (2802). For the business space executed on the machine, the priority on the execution machine is calculated from the management manager resource allocation management table 1801 and the management manager machine resource management table 1805, and the resource allocation ratio in the business space resource allocation management table 303 is calculated. To do. If the business space definition that is not executed on the execution machine is in the business space resource allocation management table 303, the definition is deleted.

  Next, it is evaluated whether there is a business space to be deleted on the execution machine (2803). If there is no business space to be deleted, the process proceeds to the next process 2805. If there is a business space to be deleted, the virtual machine 123 of the execution machine is instructed to delete the business space, and the process proceeds to the next process 2805 (2804).

  Transfer the missing virtual machine logical volumes used on the execution machine from the management manager to the execution machine. If there is a logical volume of a virtual machine that is not executed by the execution machine, the virtual machine logical volume is deleted (2805).

  Transfer the missing virtual disk logical volumes used on the execution machine from the management manager to the execution machine. If there is a virtual disk logical volume of a virtual machine that is not executed by the execution machine, the virtual disk logical volume is deleted (2806).

  Next, it is evaluated whether there is a business space to be added on the execution machine (2807). If there is no business space to be added, the business space update processing is completed. If there is a business space to be added, the virtual machine 123 of the execution machine is instructed to add the business space, and the business space update processing is completed (2808).

  FIG. 29 is a flowchart showing a flow when the management manager job management unit 1721 executes a job. Although an example of a job execution method is shown, the execution method is not limited to this.

  The management manager job management unit 1721 refers to the management manager resource allocation management table 1801 and the management manager job execution status management table 1804, and evaluates whether the business space of the maximum multiplicity has already been allocated for the business (2900). ).

  If the business space with the maximum multiplicity has already been assigned for the business, refer to the job execution status management table for management manager 1804, and execute the job in the business space for which the job submission is possible. The business space with the smallest number of jobs is searched (2901). The business space searched in 2901 is determined as the business space to be submitted (2902).

When the business space of the maximum multiplicity has not been allocated for the business, the management manager machine resource management table 1805 is referred to and the execution machine having the largest amount of unallocated resources is searched (2903). It is checked whether a new business space can be allocated to the execution machine searched in 2903 (2904). When assignment is impossible, the processing from 2901 is executed. If allocation is possible, it is confirmed that no other business space for executing the same business is allocated on the execution machine searched in 2903 (2905). If another business space that executes the same business has already been allocated on the execution machine that has been searched, the next execution machine that has the next highest number of unallocated resources is searched, and the evaluation returns to 2904 for evaluation again. (2906). If it is confirmed in the evaluation of 2905 that no other business space for executing the same business is assigned on the searched execution machine, the business space is assigned to the execution machine (2907).
In accordance with the allocation, the management manager business space management table 1802 is updated for the business space ID, business ID, configuration host, and resource allocation amount (2908).

The management manager job execution status management table 1804 is updated so as to add a business space for the business (2909).
In accordance with the added definition, necessary management tables and logical volumes are transferred to the execution machine, and the virtualization unit 123 of the execution machine is instructed to add a business space (2910). This process has been described in detail with reference to FIG. When the creation of the business space is completed, the created business space is determined as the job submission target business space (2911). A job is submitted to an existing business space determined in 2902 as a job input target or a newly created business space determined in 2911 (2912). This process will be described in detail with reference to FIG.

FIG. 30 is a flowchart showing a flow when the management manager job management unit 1721 submits a job to the business space.
The management manager job management unit 1721 assigns a unique job execution ID for identifying a job to be submitted, and updates the management manager job execution status management table 1804 for the job execution ID (3000).
From the job execution status, the management manager business space resource allocation management table 1803 is updated for the required resource amount (3001). The required resource amount after the update is the sum of the resource allocation amounts for each business being executed in the business space.
The surplus resource amount in the management manager machine resource management table 1805 is updated from the required resource amount calculated in 3001 (3002). The job management unit of the execution machine is instructed to execute the job (3003). At this time, the job execution ID is also notified, and the management manager and the execution machine manage with the same job execution ID. Thereafter, the execution status of the job on the execution machine is monitored (3004). Monitoring is continued until a series of jobs are completed (3005). When the series of jobs is completed, the job execution ID is deleted from the management manager job execution status management table 1804 (3006). From the job execution status, the management manager business space resource allocation management table 1803 is updated for the required resource amount (3007). The required resource amount after the update is the sum of the resource allocation amounts for each business being executed in the business space. The surplus resource amount in the management manager machine resource management table 1805 is updated from the required resource amount calculated in 3007 (3008).

  FIG. 31 is a flowchart illustrating a flow in which the management manager execution machine management unit 1722 moves a machine that executes a business space. Although an example of the moving method is shown, the moving method is not limited to this.

  First, the management manager execution machine management unit 1722 refers to the management manager work space management table 1802 and the management manager machine resource management table 1805 to check whether the unallocated resource amount of the migration destination machine is sufficient (3100). . If there are not enough unallocated resources, the migration process is not performed. If there are enough unallocated resources, the migration source machine is instructed to stop the business space to the virtualization unit 123 of the migration source machine in order to stop the migration target business space (3101). The contents of the job management table 300 used in the migration target business space are transferred from the migration source machine to the migration destination machine (3102). The contents of the work space management table 302 used in the move target work space are transferred from the move source machine to the move destination machine (3103). The information on the migration target business space is deleted from the business space resource allocation management table 303 of the migration source machine (3104). Information of the migration target business space is added to the business space resource allocation management table 303 of the migration destination machine (3105). At this time, the priority at the migration destination machine is calculated from the management manager resource allocation management table 1801 and the management manager machine resource management table 1805, and is set as the resource allocation ratio of the business space resource allocation management table 303. The contents of the job execution status management table 304 used in the migration target business space are transferred from the migration source machine to the migration destination machine (3106). The virtual machine logical volume used in the migration target business space is transferred from the migration source machine to the migration destination machine (3107). The virtual disk logical volume used in the migration target business space is transferred from the migration source machine to the migration destination machine (3108). In accordance with the result of the business space movement, the management manager business space management table 1802 is updated for the execution machine (3109).

  In accordance with the result of the business space movement, the management manager business space resource allocation management table 1803 is updated for the business space ID, resource allocation amount, and required resource amount (3110). Delete the business space information from the source machine and add the business space information to the destination machine. The resource allocation amount and required resource amount do not change before and after movement. The surplus resource amount in the management manager machine resource management table 1805 is updated for each of the migration source machine and the migration destination machine from the assignment of the business space changed in 3110 (3111). Resume the work space to be moved on the destination machine. The virtual machine 123 of the destination machine is instructed to resume the business space (3112).

  FIG. 32 is a flowchart showing a flow in which the management manager job management unit 1721 deletes a business space. An example of a method of deleting a business space is shown, but the method of deleting is not limited to this.

  First, the management manager job management unit 1721 updates the job submission availability in the management manager job execution status management table 1804 to “impossible” for the business space (3200). Check the usage status of the business space. The management manager job execution status management table 1804 is checked, and the job execution ID being executed in the business space is monitored (3201). If there is a job execution ID, since the job is being executed in the business space, the process returns to 3201 and waits for completion of the job (3202). If there is no job execution ID, the business space is deleted. First, information on the business space is deleted from the business space management table for management manager 1802 (3203). The business space information is deleted from the management manager business space resource allocation management table 1803 (3204). For the execution host that was executing the business space, the unallocated resource amount and the surplus resource amount in the management manager machine resource management table 1805 are updated (2305). The surplus resource amount is obtained by subtracting the necessary resource amount of the execution machine from the retained resource amount. The business space information is deleted from the management manager job execution status management table 1804 (3206). In accordance with the updated definition, the virtual machine 123 of the execution machine is instructed to delete the business space (3207). This process has been described in detail with reference to FIG.

  From the above, once a resource is allocated to each business space, a virtual machine is operated within the allocated resource range and the job is executed. Therefore, even when a resource is allocated to perform another job, it is executed. There is no direct impact on the jobs inside. In addition, resources are allocated to the business space of another business according to the priority of the business. For example, even when an important job is being executed, the execution of another business must be started. Does not affect important jobs.

  Also, by defining a business space for executing business, resources can be allocated for each business as shown in FIG. This is effective in that it is not necessary to consider the execution state in advance in a business system that performs a plurality of complicated tasks. For example, in a working business system, even when a new business is to be added, the resource allocation ratio shown in FIG. 6 can be set according to the priority of the business and the resource ratio for other business can be changed. It becomes possible.

  In the previous embodiment, the points defined in advance before starting the execution of the business have been described. However, it is also possible to change the amount of business resources when starting the execution of the business. Since the amount of resource allocation for business (business resource amount) is once converted into the resource allocation amount (spatial resource amount) to the business space, the resource allocated to the running virtual machine can be changed using the result . Thereby, it is possible to adjust the resource allocation of the entire computer in accordance with the execution state of the business.

  As described above, in a business system that performs a task that constitutes a complex job, it is necessary to perform appropriate resource allocation according to the priority of the task while simultaneously performing a plurality of tasks. As in the present invention, by defining a “business space” between a business and a virtual machine, it is possible to assign an appropriate resource to the business, and based on the resource appropriately allocated at the time of business execution You will be able to run virtual machines.

  Even when multiple execution machines are used, by defining the business space, the business space is secured on the appropriate execution machine based on the resources allocated to the business, and based on the resources allocated to the business space. The virtual machine is executed. The unallocated resource amount is calculated from the assignment status of the business space to each execution machine, and the surplus resource amount is calculated from the job execution status in each business space. Using the business execution plan and the information, the user can move a business space for executing a specific business to an execution machine with a large amount of unallocated resources and surplus resources.

  In the previous embodiment, the business space has been described as a logical space having resources. However, it may be considered as a logical unit for simply calculating a resource allocation amount by grouping a plurality of virtual machines. Is possible. In this case as well, after calculating the resource allocation amount for the business space based on the business space and the job execution status of each virtual machine in the business space, the resource allocation to each virtual machine in the business space The point to perform is the same.

100, 1610 Physical computer 101, 1611 Storage unit 102 Network 103 Display device 110 Disk interface 111 of physical computer 111 Communication interface 112 of physical computer CPU of physical computer
113 Physical Computer Memory 114 Physical Computer Display Interface 120 Host OS
121 Job management unit 122 Business space management unit 123 Virtualization units 124 and 125 Business space 130 and 132 managed by the virtualization unit 123 Virtual machines 131 and 133 managed by the virtualization unit 123 Managed by the virtualization unit 123 Virtual disk 200 Logical CPU assigned to the business space
201 Logical memory allocated to business space 210 Logical disk interface 211 of virtual machine Logical communication interface 212 of virtual machine Logical CPU of virtual machine
213 Virtual machine logical memory 214 Virtual machine logical display interface 220 Guest OS on the virtual machine
221 Job execution unit on virtual machine 222 Business application 300 on virtual machine Job management table 301 Business resource allocation management table 302 Business space management table 303 Business space resource allocation management table 304 Job execution status management table 305 Resource allocation management table 310 , 312 Virtual machine logical volume 311, 313 Virtual disk logical volume 1600 Computer resource 1700 Physical computer 1701 Storage unit 1703 Display device 1710 Physical computer disk interface 1711 Physical computer communication interface 1712 Physical computer CPU
1713 Physical Computer Memory 1714 Physical Computer Display Interface 1720 OS
1721 Management manager job management unit 1722 Management manager execution machine management unit 1800 Management manager job management table 1801 Management manager task-specific resource allocation management table 1802 Management manager task space management table 1803 Management manager task space resource allocation management table 1804 Management manager job execution status management table 1805 Management manager machine resource management tables 1810 and 1812 Virtual machine logical volumes 1811 and 1813 Virtual disk logical volumes

Claims (12)

A resource control method for allocating resources necessary to run a virtual machine on a computer and execute business,
The calculator is
Storing a correspondence relationship between a job, a priority of the job, and at least one job constituting the job;
Storing the correspondence between the business and the business space for executing the business;
Obtain job execution information indicating the status of the job being executed on the computer,
Based on the correspondence relationship between the acquired job execution information, the business space to which the job being executed belongs, and the priority of the job to which the job being executed belongs, the job to which the job being executed belongs Calculate the amount of resources allocated to the space,
A resource control method, comprising: calculating a resource amount to be allocated to a virtual machine on which the job being executed in the business space is operating from the calculated resource amount. The priority of the business is represented by the resource allocation amount of the computer,
The resource control method according to claim 1. The calculator further includes:
A virtual machine for operating a job to be executed is generated by duplication, and a resource amount for the virtual machine is calculated and executed.
The resource control method according to claim 2. A resource control system for allocating resources necessary to run a virtual machine on a computer and execute business,
The calculator is
A business management storage unit that stores a correspondence relationship between a business, the priority of the business, and at least one job constituting the business;
A business space storage unit for storing a correspondence relationship between the business and the business space executed by the business;
A job execution information acquisition unit for acquiring job execution information indicating a status of a job being executed on the computer;
The job execution information acquired by the job execution information acquisition unit, the job space to which the job being executed belongs, and the priority of the job to which the job being executed belongs, and the job management storage unit, A business space resource allocation unit that calculates a resource amount to be allocated to the business space to which the job being executed belongs by referring to the correspondence relationship stored in the business space storage unit;
A virtual machine resource allocation unit for calculating a resource amount to be allocated to a virtual machine on which the job being executed in the business space operates, from the resource amount calculated by the business space resource allocation unit;
A resource control system comprising: The priority of the business stored in the business management storage unit is represented by a resource allocation amount of the computer,
The resource control system according to claim 4. The virtual machine resource allocation unit
Further, the virtual machine necessary for operating the job is generated by duplication, and further includes calculating and executing the calculated resource amount for the virtual machine,
The resource control system according to claim 5. A resource control method in a control device for allocating resources necessary to run a virtual machine on a plurality of computers and execute a job,
The control device includes:
Stores the amount of resources held by computers that execute business,
Storing the correspondence relationship between the business and the amount of resources allocated to the business, the minimum multiplicity, the maximum multiplicity, and at least one job constituting the business;
Storing a correspondence relationship between the business and at least one business space for executing the business;
Storing a correspondence relationship between the business space and the computer executing the business space;
From the correspondence between the business and the business space for executing the business, and the correspondence between the business and the resource amount allocated to the business, the resource amount allocated to the business space is calculated,
From the calculated resource amount to be allocated to the business space and the correspondence between the business space and the computer that executes the business space, calculate the resource amount necessary for the computer,
From the correspondence between the calculated resource amount necessary for the computer and the resource amount possessed by the computer, the resource amount that can be allocated by the computer is calculated,
A resource control method characterized in that a computer to which a business space for executing the business is to be added is calculated from the calculated resource amount that can be allocated by the computer. The assignment of the business space to the computer further includes:
From the correspondence between the amount of resources held by the computer and the amount of resources allocated to the business space, the priority in the computer is calculated,
Resource control is performed by the computer.
The resource control method according to claim 7. The control device further includes:
Obtain job execution information indicating the status of the job being executed on the computer,
Based on the correspondence between the acquired job execution information and the business space to which the job being executed belongs, a business space in which the job for the business is newly executed is calculated,
Calculating a computer to execute the job of the business from the calculated business space,
The resource control method according to claim 7. A resource control system in a control device that allocates resources necessary to run a virtual machine on a plurality of computers and execute a business,
The control device includes:
A computer resource management storage unit for storing the amount of resources held by each of the plurality of computers;
A business management storage unit for storing a correspondence relationship between a business, a required resource amount allocated to the business, a multiplicity of the business, and at least one job constituting the business;
A business space storage unit that stores a correspondence relationship between the business and at least one business space that executes the business;
An execution computer storage unit that stores a correspondence relationship between the business space and the computer that executes the business space;
Referencing the correspondence between the business and the business space for executing the business from the business space storage unit, referring to the correspondence between the business and the resource requirement allocated to the business from the business management storage unit,
A business space resource allocation unit for calculating a resource allocation amount to be allocated to the business space;
Referencing the resource allocation amount and the correspondence between the business space and the computer executing the business space from the execution computer storage unit, and calculating the required resource amount necessary for the computer,
A computer resource management unit that references a correspondence relationship between the required resource amount and the retained resource amount held by the computer from a computer resource management storage unit, and calculates an allocatable resource amount that can be allocated by the computer;
A resource control system, comprising: an execution computer allocation unit that identifies, from the plurality of computers, a computer to which a business space for executing the business is to be added based on the allocatable resource amount. The execution computer allocation unit further includes:
The retained resource amount held by the computer is acquired from the computer resource management storage unit, and the priority for each of the plurality of computers is calculated from the correspondence with the resource allocation amount calculated by the business space resource allocation unit. It is characterized by
The resource control system according to claim 10. The control system further comprises:
A job execution information acquisition unit for acquiring job execution information indicating a status of a job being executed on the computer;
A job execution status management storage unit for storing a correspondence relationship between the job execution information acquired by the job execution information acquisition unit and the business space to which the job being executed belongs;
An execution business space search unit that calculates a business space in which the job of the job is to be newly executed from the execution status of the job referenced from the job execution status management storage unit;
An execution computer search unit that specifies, from the plurality of computers, a computer that should execute the job of the business from the calculated business space,
The resource control system according to claim 10.

Images