JP6037825B2 - Computer management system - Google Patents

Description

  The present invention relates to a management apparatus used for managing the operation of a computer system, and more particularly to a technique for managing resource allocation to virtual machines constructed on a physical computer.

  In the IT market in recent years, the development of virtualization technology is progressing, and services using the virtualization technology are widely provided. By using the virtualization technology, hardware resources such as server CPUs and memories can be logically pooled, and a plurality of virtual machines to which only necessary resources are allocated can be constructed from one physical machine. For example, Patent Document 1 discloses that a plurality of virtual machines are operated on a physical machine, and resources are collected and allocated to the virtual machines according to the resource usage status of each virtual machine.

  Further, when resources are allocated to virtual machines, a technique called overcommitment is generally known in which resources more than physical resources included in a physical machine are allocated to a virtual machine in a pseudo manner.

JP 2005-309644 A

  When resource allocation is performed between virtual machines, the performance of the virtual machine may become unstable if the resource allocated to the virtual machine exceeds the resource of the physical machine. According to Patent Document 1, it is avoided that the resource allocation to the virtual machine running on the physical machine exceeds the resource amount of the physical machine and the performance of the virtual machine becomes unstable. There is no mention of what to do.

  It is an object of the present invention to manage resource allocation so as to avoid such an unstable state when allocating resources to virtual machines.

  In order to solve the above-described problem, the resource management server manages physical machine resource information in which information for specifying a physical machine, the resource capacity of the physical machine, and the unallocated capacity of the resource of the physical machine are stored in association with each other A table, information identifying a virtual machine, a virtual machine resource information management table for storing the capacity of the virtual machine resource and information identifying the physical machine on which the virtual machine is associated, and identifying the virtual machine Information and a policy information management table that associates and stores a policy value that is a threshold value requested by the virtual machine, and the average used resource when the average used resource capacity of the virtual machine exceeds the policy value The allocated resource capacity is calculated so that the capacity is less than the policy value, and the average resource used is calculated. When a resource analysis unit that secures the additional resource capacity is secured from a virtual machine having a sufficient resource capacity to maintain the policy value without lowering the policy value, and when the additional resource capacity is secured, When the reserved additional resource capacity exceeds the unallocated capacity of the physical machine with the virtual machine, the unallocated capacity of each physical machine in the physical machine resource information management table is referred to, and A provisioning instruction unit for issuing a change instruction to move the virtual machine to a physical machine in which the unallocated capacity is larger than a capacity obtained by adding the resource capacity of the virtual machine and the reserved additional resource capacity to allocate resources. And the virtual environment integrated management server receives the change instruction from the resource management server. The resource capacity newly allocated to the virtual machine is subtracted from the unallocated capacity in the physical machine resource information management table, and the resource capacity of the virtual machine in the virtual machine resource information management table is newly A provisioning execution unit that rewrites each value so as to increase the resource capacity allocated to the virtual machine.

  This prevents the resources assigned to the virtual machine from exceeding the resources of the physical machine and the performance of the virtual machine from becoming unstable.

1 is an overall configuration diagram of a computer system. It is a physical machine resource information management table. It is a virtual machine resource information management table. It is a policy information management table. It is an average operation information management table. It is a virtual machine operation information management table. FIG. 10 is a flowchart illustrating a method for automatically optimizing virtual machine resources for each tenant. It is a flowchart figure which shows the flow of the resource average utilization rate update process of a virtual machine. It is a flowchart figure which shows the flow of the additional resource reservation process of a virtual machine. It is a flowchart figure which shows the flow of the resource change process of a virtual machine. It is a flowchart figure which shows the flow of the resource change process of a virtual machine. It is a figure showing the structure of a resource management server.

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

FIG. 1 is a simplified block diagram illustrating the overall configuration of the computer system according to the present embodiment. The computer system is configured by connecting a management terminal 1, a resource management server 2, a virtual environment integrated management server 3, and a virtual machine execution server 4 to a network.
The resource management server 2 determines the resource collection unit 5 that acquires the virtual machine resource operation information from the virtual environment integrated management server 3 and whether or not the resource needs to be added to the virtual machine. The resource analysis unit 6 that calculates the appropriate value of the resource, the policy management unit 7 for setting the policy value in the resource operation information of the virtual machine received from the management terminal 1, and the provisioning instruction to the virtual environment integrated management server 3 And a resource management DB that manages physical machine resource information, virtual machine policy information, resource average operation information, and resource information for each tenant.

  The virtual environment integrated management server 3 receives a provisioning instruction from the resource management server 2, and the provisioning execution unit 8 that instructs the virtual machine execution server to change the resource amount of the CPU and the memory according to the contents, and the resource management server 2 It includes a virtual environment management DB that is referenced to collect virtual machine operation information for each tenant.

  The virtual machine execution server 4 assigns and changes resources to the virtual machine 13, which is a logical computer constructed on the virtual machine execution server 4, in accordance with the instructions received from the virtual environment integrated management server 3, The virtual machine control unit 10 is configured to control the operation of the virtual machine 13 on the machine execution server 4. The virtual machine execution server 4 is a physical computer (physical machine), and is configured by a computer such as a so-called server or personal computer. A plurality of virtual machines 13 can exist on one virtual machine execution server 4.

  In this embodiment, the management terminal 1, the resource management server 2, the virtual environment integrated management server 3, and the virtual machine execution server 4 are connected to the network as described above, but the present invention is not limited to this. It is good also as a server (apparatus) which integrated each server into one, and the place of each function is not specified.

  In this embodiment, the resource management server 2 and the virtual environment integration server 3 have a role as a computer management system. However, the present invention is not limited to this, and a device integrated with the virtual environment integration server 3 as one server. It may be configured as.

FIG. 12 is a block diagram showing the configuration of the resource management server 2. The resource management server 2 includes a CPU 0201, a memory 0202, a hard disk 0203, a communication control device 0205, and an I / O interface 0208. Through the communication control device 0205, the virtual environment integrated management server 3, the virtual machine execution server 4, Connected to the management terminal 1. Further, it is connected to the input device 0206 and the output device 0207 through the I / O interface. The resource management DB is stored in a storage device such as a hard disk. The resource collection unit, lease analysis unit, policy management unit, and provisioning instruction unit are each realized as a program, and the functions are realized by the CPU executing these programs.
<Table>
The determination of the state in which the virtual machine resource has sufficient capacity will be described in detail later. For example, if the virtual machine 13 is allocated with the physical 2 GB memory of the virtual machine execution server 4, the virtual machine 13 is not necessarily The entire 2 GB memory is not used, and the physical memory area used varies depending on the load of the virtual machine 13. A case where a surplus portion that is not used in the physical memory area is large is a case where there is a margin in the resources of the virtual machine 13.

  FIG. 2 is a diagram illustrating a data structure and a data configuration example of the physical machine resource information management table 112 provided in the resource management server 2. The physical machine resource information management table 112 is a table for storing resource information for each virtual machine execution server 4.

  The physical machine resource information management table 112 includes a physical machine ID 1121, a CPU resource 1122, an allocated CPU resource 1123, an unallocated CPU resource 1124, a memory resource 1125, an allocated memory resource 1126, and an unallocated memory resource 1127.

  The physical machine ID 1121 stores a value (physical machine ID) for identifying the virtual machine execution server 4 executing the virtual machine 13, and an arbitrary physical machine ID is uniquely assigned to each virtual machine execution server 4. It is done. The CPU resource 1122 includes the CPU resource amount held by the virtual machine execution server 4 identified by the physical machine ID stored in the physical machine ID 1121, and the allocated CPU resource 1123 includes the CPU resource amount on the virtual machine execution server 4. The total CPU resource amount allocated to one or a plurality of virtual machines operating in the CPU free resource 1124 is the unused CPU resource amount among the CPU resources held by the virtual machine execution server 4. However, the memory resource 1125 includes the memory resource amount held by the virtual machine execution server 4, and the allocated memory resource 1126 includes one or more virtual machines 13 operating on the virtual machine execution server 4. The total amount of memory resources allocated to The 1127, among the memory resources that the virtual machine execution server 4 holds, the memory resource amount of unused, are respectively stored.

  In this embodiment, only the CPU and the memory are considered as resources, but other resources such as a storage device and a communication device may be included.

  FIG. 3 is a diagram illustrating a data structure and a data configuration example of the virtual machine resource information management table 113 provided in the resource management server 2. The virtual machine resource information management table 113 is a table for managing the CPU resource amount and the memory resource amount allocated to the virtual machine.

  The virtual machine resource information management table 113 includes a virtual machine ID 1131, a CPU resource 1132, a memory resource 1133, a physical machine ID 1134, and a tenant ID 1135. A value identifying the virtual machine 13 is assigned to the virtual machine ID 1131, a current CPU resource amount assigned to the virtual machine 13 is assigned to the CPU resource 1132, and a virtual machine 13 is assigned to the memory resource 1133. The current memory resource amount is the physical machine ID 1134, the physical machine ID that identifies the virtual machine execution server 4 on which the virtual machine 13 is placed, and the tenant ID is the tenant to which each virtual machine 13 is assigned. Each tenant ID for identifying whether the user belongs is stored.

  Here, a tenant refers to a unit for grouping single or multiple virtual machines. In the present embodiment, resources are distributed among virtual machines within the same tenant (within a group), and control is performed so that the sum of the resources of the virtual machines within the same tenant is constant. For example, in a data center or the like, a customer purchases a plurality of virtual machines from a person who manages virtual machines in units of tenants. If any of the virtual machines in the same tenant runs out of resources by controlling the resource allocation as described above, the other resources within the total of the resources of the purchased virtual machines in the same tenant By allocating resources from a virtual machine with sufficient capacity to a virtual machine with insufficient resources, resources can be accommodated reasonably without purchasing additional virtual machines or resources.

  In this embodiment, the virtual machine resource information management table associates each virtual machine with a tenant. However, the present invention is not limited to this, and a tenant DB that associates only the virtual machine with the tenant may be provided.

  Further, resources such as CPU resources and memory resources allocated to the virtual machine 13 refer to capacities that are physically allocated from the physical machine to the virtual machine.

  FIG. 4 is a diagram illustrating a data structure and a data configuration example of the policy information management table 114 included in the resource management server 2. The policy information management table 114 is a table for storing policy information received from the management terminal 1 by the policy management unit 7.

  The policy information management table 114 has a virtual machine ID 1141, a CPU policy value 1142, a memory policy value 1143, a start time 1144, an end time 1145, and a priority 1146. The virtual machine ID 1141 has a value for identifying the virtual machine 13 owned by the tenant, and the CPU policy value 1142 has a threshold value for determining whether or not to allocate CPU resources to the virtual machine 13 as a memory policy value 1143. The threshold value for determining whether or not to allocate memory resources to the virtual machine is the start time 1144, the time at which the collection of the virtual machine resource operation information is started, and the end time 1145 is the start time. The time at which the collection of the virtual machine resource operation information is completed, and the priority 1146 stores a value representing the priority of the virtual machine 13 that performs automatic resource allocation. In this embodiment, it is assumed that priority 1 is the highest priority value, and VM01 is given the highest priority in the policy information management table 114.

  In the present embodiment, a usage rate that is a ratio of a resource amount actually used by the virtual machine 13 to a resource amount allocated to the virtual machine 13 is used as a policy value in a predetermined period by the virtual machine 13. When the average value (average usage rate) of the resource usage rate exceeds a certain usage rate (policy value) arbitrarily determined by the user, resource allocation is performed.

  Specifically, when the virtual machine ID is VM01, the physical resource allocated to this virtual machine is 6 GHz, the memory resource is 8 GB, and the CPU policy value is from the virtual machine resource information management table of FIG. When 60% is used, 3.6 GHz out of 6 GHz, and when the memory policy value is 70%, when 5.6 GB or more out of 8 GB is used, resource allocation processing is performed.

  In other words, in the case of VM01, if the CPU resource is used at 3.6 GHz or more, the CPU resource allocation processing from the virtual machine having the remaining resources to VM01 is performed, and if the memory resource is used at 5.6 GB or more, The memory resource allocation process is started from the virtual machine having sufficient resources to VM01. Details of the resource allocation processing will be described later.

  In this embodiment, resource allocation processing is performed when the average resource usage rate exceeds the policy value, but resource allocation processing is performed when the usage rate instantaneously exceeds the policy value set as the threshold value. You may do it.

  FIG. 5 is a diagram illustrating a data structure and a data configuration example of the average operation information management table 115 included in the resource management server 2. The average operation information management table 115 is a table for storing an average resource usage rate as the operation information of the virtual machine 13. The operation information management table 115 includes a virtual machine ID 1151, a CPU average usage rate 1152, and a memory average usage rate 1153. The virtual machine ID 1151 contains a value for identifying a virtual machine owned by the tenant, and the CPU average usage rate 1152 contains the average value of the CPU usage rate of the virtual machine at the resource collection time specified in the policy management table 114. In the average usage rate 1153, the average value of the memory usage rate of the virtual machine in the resource collection time specified in the policy management table 114 is stored.

  Here, for example, when attention is paid to the virtual machine whose virtual machine ID is VM01, the allocated CPU resource is 6 GHz from the virtual machine resource information management table 113 of FIG. Further, from the average operation information management table 115 in FIG. 5, the CPU average usage rate of the VM01 is 80%, and the CPU resource of the virtual machine VM01 is used on an average of 4.8 GHz per unit time. I understand.

  FIG. 6 is a diagram illustrating a data structure and a data configuration example of the virtual machine operation information management table 121 included in the virtual environment integrated management server 3. The virtual environment integrated management server 3 manages the resource usage status of each virtual machine based on this table. The operation information management table 121 is managed for each virtual machine. The operation information management table 121 stores time 1211, CPU usage rate 1212, and memory usage rate 1213. At a time 1211, information in a certain range of time such as 00:00:00 to 00:30 is stored in order (in this case, divided every 30 minutes and stored in order). The CPU usage rate 1212 stores a value indicating the average usage rate of the CPU resource of the virtual machine in the time range indicated by the time 1211. The memory usage rate 1213 stores the memory resource used by the virtual machine in the same time range. Stores a value that represents the percentage of the quantity.

In this embodiment, the average resource usage rate is stored every 30 minutes from 00:00, but is not limited to this, and it may be every hour or every 10 minutes. Also good.
<Flowchart>
Next, the processing flow of the present embodiment will be described.

  FIG. 7 is a flowchart illustrating a method for automatically optimizing virtual machine resources for each tenant in the present embodiment. First, in step S1, the resource management server 2 performs resource average usage rate update processing (FIG. 8) described later on the virtual machine. Next, in step S2, the average resource usage rate of the virtual machine updated in step S1 is compared with the policy value of the resource to determine whether additional resource allocation is necessary. If additional resource allocation is necessary, step S3 is performed. Proceed to If additional resource assignment is unnecessary, the process proceeds to step S10.

  For example, the average usage rate from the start time to the end time of the resource collection time in the policy information management table 114 is obtained from the CPU and memory usage rates of each virtual machine in the operation information management table 121, and the average operation information management table 115 Update the data. Then, the updated CPU and memory average usage rate is compared with the CPU policy value and the memory policy value for each virtual machine in the policy information management table 114, and each average usage rate value exceeds the policy value. In this case, it is determined that additional resource allocation is necessary, and the process proceeds to resource addition processing. In the present embodiment, the CPU policy value of the virtual machine ID VM01 is 60%, the memory policy value is 70%, and the CPU usage rate exceeds the CPU policy value. judge. On the other hand, since the average usage rate of the memory is lower than the memory policy value, it is determined that the resource addition allocation is not allowed.

In step S3, a process for securing additional resources to the virtual machine (FIG. 9) is performed. The additional resource securing process will be described later in detail. In step S4, the result of whether or not the resource can be secured is determined. If the resource can be secured, the process proceeds to step S5. If resources cannot be secured, the process proceeds to step S10.
In step S5, when the resources secured in S3 are added to the virtual machine, the total value of the resource amounts of the virtual machines operating on the virtual machine execution server 4 on which the virtual machine operates is the virtual machine execution server. It is determined whether the resource amount of 4 is exceeded (overcommit determination). In step S5, if overcommit is determined in the overcommit determination, the process proceeds to step S6. If it is not overcommit, the process proceeds to step S9.
Here, the overcommitment means that, for example, the resource (5) and the resource (6) are placed where the resource (10) exists on the physical machine. In this case, since the resource (10) is handled as the resource (11) in a pseudo manner, there is a problem that the processing becomes heavy.
Specifically, the physical machine ID corresponding to the virtual machine ID to which resources are additionally allocated is identified from the virtual machine resource information management table 113, and the identified physical machine ID is collated with the physical machine resource information management table 112. The amount of unallocated resources of the virtual machine execution server 4 specified by the physical machine ID is specified. When the amount of resources to be additionally allocated exceeds the specified amount of unallocated resources, it is determined as overcommit. For example, when the virtual machine ID of the virtual machine to which resources are additionally allocated is VM01, the virtual machine execution server with the physical machine ID PM01 is identified with reference to the virtual machine resource information management table 113. The identified physical machine IDPM01 is collated with the physical machine resource information management table 112, the unallocated CPU resource of this virtual machine execution server is identified as 1 GHz, and compared with the amount of resources to be additionally allocated, 1 GHz When the number is larger, it is determined as overcommit.

  In step S6, when a resource is additionally allocated to the virtual machine, a physical machine having an allowable amount that does not exceed the physical machine resource is searched from the physical machine resource management table 112 in the order of the physical machine ID. Specifically, the additional resource secured in step S3, the sum of the resource amount of the virtual machine, the unallocated resource in the physical machine resource management table 112 (unallocated CPU resource 1124 when adding a CPU, When adding a memory, refer to the unallocated memory resource 1127), and select a resource that increases the amount of unallocated resources.

  In step S7, if the corresponding virtual machine execution server exists as a result of the search in step S6, the process proceeds to step S8. If the corresponding virtual machine does not exist, the process proceeds to step S10.

In step S8, the virtual machine is moved to the virtual machine execution server found in S6 by using a function of moving the virtual machine included in the virtual environment integrated management server 3 to another virtual machine execution server.
In step S9, resource allocation processing (FIG. 10) for the virtual machine is performed. In step S10, when steps S1 to S9 are completed for all virtual machines of the tenant, the process proceeds to step S11. If there is a virtual machine that has not been completed, the process returns to step S1, and the same processing is performed on the virtual machine with the next highest priority.

  In step S11, when steps S1 to S10 are completed for all tenants, a series of processing ends. If there is a tenant that has not been completed, the process returns to step S1 and the same processing is performed for the next tenant.

  FIG. 8 is a flowchart showing the flow of the resource average usage rate update process of the virtual machine, which is executed in the resource collection unit 5 included in the resource management server 2. In this processing, the resource collection unit 5 performs update processing on each of the CPU average usage rate and the memory average usage rate. First, processing is performed from the CPU average usage rate.

  In step S12, the resource collection unit 5 determines the CPU of the virtual machine from the time indicated by the start time 1144 to the time indicated by the end time 1145 of the policy management table 114 from the operation information management table 121 of the virtual environment integrated management server 3. Get usage rate. In this embodiment, for the virtual machine whose virtual machine ID is VM01 defined in the policy management table 114, the start time of the resource collection time is 09:00 and the end time is 17:00, so 09:00 to 09 in the operation information management table. : 30, 09:30 to 10:00 ... 16:30 to 17:00, respectively. Here, as the resource usage rate, the usage rate information sequentially sent from the virtual machine may be used as it is, or when the sent information is not the usage rate but the usage resource amount, The usage rate may be calculated by referring to the machine resource information management table and viewing the received resource amount with respect to the resource amount allocated to the virtual machine.

  For example, if the CPU usage used by the virtual machine with the virtual machine ID VM01 is 3 GHz, the CPU resource amount 6 GHz allocated to the virtual machine with the virtual machine ID VM01 from the virtual machine resource information management table 113 The usage rate can be calculated from 3/6 × 100 to 50%.

  In step S13, a new CPU average usage rate is recalculated from the CPU usage rate acquired in step S12 and the CPU average usage rate 1152, and the calculated value is rewritten and updated to the CPU average usage rate 1152. Since the latest value of the resource usage is stored in the average operation information management table 115, it is updated when a new usage rate is calculated.

  Here, the start time and end time of the resource collection time in the policy information management table 114 are the start time and end time for which an average usage rate that can be arbitrarily set by the user is calculated, and the virtual machine operation information management table Is to check the usage rate of operating machines that are updated sequentially.

  Further, in the present embodiment, it is expressed as a percentage of the usage rate, but it is not limited to this, and the resource amount may be expressed as it is.

  Specifically, the average usage rate of 09: 0 to 17:00 is calculated from the value read in step S12, and the policy values in the policy management table 114 are updated. For example, when the CPU usage rate of 00:00:00 to 00:30 in the operation information management table is 15% and the CPU usage rate of 00:30 to 01:00 is 10%, the usage rate of 00:00:00 to 10:00. Is 12.5% at (10 + 15) / 2.

  In step S <b> 14, the resource collection unit 5 acquires the memory usage rate of the virtual machine from the time indicated by the start time 1144 to the time indicated by the end time 1145 of the policy management table 114 from the operation information management table 121. In step S15, a new memory average usage rate is recalculated from the acquired memory usage rate and memory average usage rate 1153, and the calculated value is rewritten and updated to the memory average usage rate 1153.

  FIG. 9 is a flowchart showing the flow of the virtual machine additional resource securing process performed in the resource analysis unit 6 included in the resource management server 2. This process is performed for each of the CPU resource and the memory resource. First, processing is performed from CPU resources.

  In step S16, if the CPU resource needs to be added to the virtual machine in the determination in step S2, the process proceeds to step S17. If it is not necessary to add a CPU resource, the process proceeds to step S20.

  In step S17, an additional CPU resource amount to be allocated to the virtual machine is calculated. The value of the additional CPU resource amount is obtained so that the CPU average usage rate 1152 is lower than the CPU policy value 1142.

  The CPU resource amount is calculated from the CPU resource 1132, the CPU policy value 1142, and the CPU average usage rate 1152. Assuming that the physical CPU resource amount allocated to the virtual machine is “V”, the CPU policy value is “W”, the CPU average usage rate is “X”, and the additional CPU resource amount is “A”, (V + A) × W / 100 = V × X / 100. When this is obtained for A, the additional CPU resource amount can be obtained by A = V × (X−W) / W.

  Specifically, for example, the virtual machine VM01 of this embodiment requires an additional allocation of CPU resources because the CPU average usage rate exceeds the CPU policy value, and the additional CPU resource amount is set to “A”. When calculated, it becomes (6 + A) × 60/100 = 6 × 80/100. When this is obtained for A, A = 2 (GHz), and in order to maintain the CPU policy value, the CPU resource of 2 GHz is changed to other Need to be recovered from the virtual machine.

In step S18, the CPU resource amount that can be recovered is calculated from the virtual machine with low priority. The CPU resource amount that can be recovered is a value that can maintain the CPU policy without the CPU average usage rate 1152 exceeding the CPU policy value 1142.

  Also, a tenant ID corresponding to the virtual machine ID of the virtual machine to be allocated in the virtual machine resource information management table is specified, and resources are allocated from virtual machines having the same tenant ID. Here, the resource allocation is performed only in the tenant used by the user, thereby preventing the influence on other tenants. In this embodiment, it is expressed as a tenant. However, the present invention is not limited to this, and any grouping of a plurality of virtual machines may be used, and a group ID may be used. When the relationship between the virtual machine and the tenant is defined by the tenant DB described above, the virtual machine ID to be allocated is checked against the tenant DB, the tenant ID is identified, and the virtual machine having the identified tenant ID What is necessary is just to identify ID and collect | recover resources from the virtual machine of specified virtual machine ID.

  The CPU resource amount that can be collected from the virtual machine is calculated from the CPU resource 1132 of the virtual machine resource information management table 113, the CPU policy value 1142 of the policy information management table 114, and the CPU average usage rate 1152 of the average operation information management table 115. Assuming that the CPU resource is “V”, the CPU policy value is “W”, the CPU average usage rate is “X”, and the recoverable CPU resource amount is “B”, (V−B) × W / 100 = V × X When this is obtained for B, the amount of CPU resources that can be recovered by B = V × (W−X) / W can be obtained. Here, if the value of B is negative, the CPU average usage rate exceeds the policy value, and resources cannot be collected.

  Specifically, for example, an amount of resources that can be collected for the virtual machine VM02 of the present embodiment is obtained. When the amount of CPU resources that can be collected is calculated as “B”, it becomes (4-B) × 80/100 = 4 × 20/100, and when this is obtained for B, B = 3 (GHz) and 3 GHz CPU resources are obtained. It can be recovered from VM02.

  It should be noted that resources are not collected from a virtual machine having a higher priority than itself, and calculation of collection of CPU resource amount is not performed. If there is no resource that can be collected, the resource cannot be secured.

  In step S19, it is determined whether or not the additional CPU resource amount can be secured in step S18. If the additional CPU resource amount is secured, the process proceeds to step S20. If not secured, the process is terminated.

  Steps S20 to S23 are processes for calculating the additional memory resource amount, and the concept is the same as the method for calculating the additional CPU resource amount.

  FIG. 10 is a flowchart showing a flow of virtual machine resource change processing (determination of whether or not to overcommit) executed by the resource management server 2.

  In step S24, in the additional resource securing process in step S3, it is determined whether the resource recovery target virtual machine and the resource receiving virtual machine are located on the same virtual machine execution server, and the same virtual machine execution server If not, the process proceeds to step S25. If it is, the process ends.

In step S25, in the additional resource securing process in step S3, it is determined whether or not the amount of resources collected from other virtual machine execution servers exceeds the free resources of the virtual machine execution server on which the virtual machine is placed. If so, the process proceeds to step S26. When it does not exceed, this process is terminated.
In step S26, if the resource amount secured in S3 is allocated to the virtual machine on the virtual machine execution server on which the virtual machine is arranged, it is determined that overcommitment occurs. In other words, it is determined that the virtual machine is in a state where resources higher than the physical machine are allocated.

  FIG. 11 is a flowchart showing the flow of the virtual machine resource changing process executed in the provisioning instruction unit 8 included in the resource management server 2. This process is performed for each of the CPU resource and the memory resource. First, processing is performed from CPU resources.

  In step S27, in the additional CPU resource securing process of FIG. 9, the provisioning instruction unit 8 issues a resource change instruction for the virtual machine that is the target of CPU resource collection, and the provisioning execution unit 9 that receives the instruction performs the resource change process. Do. If there are multiple virtual machines to be collected, resource change processing is performed for all virtual machines.

  In step S28, the provisioning instruction unit 8 issues a change instruction to additionally allocate the CPU resource collected in step S27 for the virtual machine to which additional resource allocation is performed, and the provisioning execution unit 9 that has received the change instruction performs additional resource allocation. Do. The resource management server 2 assigns the allocated CPU resources 1123, unallocated CPU resources 1124, and virtual machine resource information of the physical machines in the physical machine resource information management table 112 in which the virtual machines changed in S27 and S28 are arranged. The value of the CPU resource 1132 of the virtual machine in the management table 113 is rewritten and updated.

  In step S29, in the additional memory resource securing process of FIG. 9, the provisioning instruction unit 8 issues a resource change instruction for the virtual machine from which memory resources are to be collected, and the provisioning execution unit 9 that receives the instruction performs the resource change process. Do. If there are multiple virtual machines to be collected, resource change processing is performed for all virtual machines.

  In step S30, the provisioning instruction unit 10 issues an instruction to change the additional allocation for the virtual machine that performs the resource additional allocation for the memory resource collected in step S29, and the provisioning execution unit 9 that receives the change instruction performs the additional allocation of the resource. . The resource management server 2 assigns the allocated memory resource 1126, the unallocated memory resource 1127, and the virtual machine resource information of the physical machine in the physical machine resource information management table 112 in which the virtual machines changed in S29 and S30 are arranged. The value of the memory resource 1133 of the virtual machine in the management table 113 is rewritten and updated.

  As a result, when resources are allocated among virtual machines, control can be performed so that overcommitment does not occur.

1: management terminal, 2: resource management server, 3: virtual environment integrated management server, 4: virtual machine execution server, 5: resource collection unit, 6: resource analysis unit, 7: policy management unit, 8: provisioning instruction unit, 9: Provisioning execution unit, 10: Virtual machine control unit, 11: Resource management DB, 12: Virtual environment management DB, 13: Virtual machine

Claims (4)

A physical machine resource information management table that stores information for identifying a physical machine, the physical capacity of the physical machine and the unallocated capacity of the physical machine resource in association with each other;
A virtual machine resource information management table that stores information that identifies a virtual machine, a resource capacity of the virtual machine, and information that identifies the physical machine where the virtual machine is associated;
A policy information management table for storing information specifying the virtual machine and a policy value that is a threshold value requested by the virtual machine in association with each other;
When the average used resource capacity of the virtual machine exceeds the policy value, an allocated resource capacity is calculated such that the average used resource capacity is lower than the policy value, and the average used resource capacity is higher than the policy value. A resource analysis unit that reserves additional resource capacity from another virtual machine having a sufficient resource capacity to maintain the policy value without any change,
When the additional resource capacity is reserved, when the reserved additional resource capacity exceeds the unallocated capacity of the physical machine with the virtual machine, each physical machine in the physical machine resource information management table Refer to the unallocated capacity, and move the virtual machine onto a physical machine in which the unallocated capacity is larger than the capacity obtained by adding the resource capacity of the virtual machine and the reserved additional resource capacity. A resource management server having a provisioning instruction unit for issuing a change instruction for allocating resources;
When the change instruction from the resource management server is received, the resource capacity newly allocated to the virtual machine is subtracted from the unallocated capacity of the physical machine resource information management table, and the virtual machine resource information management table A virtual environment integrated management server having a provisioning execution unit for rewriting values so that the resource capacity of the virtual machine is increased by the resource capacity newly allocated to the virtual machine. . The computer management system according to claim 1,
The virtual machine resource information management table further includes:
A tenant ID that identifies a group to which a virtual machine belongs is stored in association with information that identifies the virtual machine, a capacity of the virtual machine resource, and information that identifies the physical machine where the virtual machine is located,
The resource analysis unit
The additional resource capacity is secured from virtual machines having the same tenant ID. A computer management system according to any one of claims 1 to 2,
The policy information management table further includes
Storing priority information for each virtual machine in association with information identifying the virtual machine and the policy value;
The resource analysis unit
A computer management system that preferentially selects virtual machines that secure the additional resource capacity in the order of priority. Storing in the physical machine resource information management table the information identifying the physical machine, the resource capacity of the physical machine and the unallocated capacity of the resource of the physical machine in association with each other;
Storing in the virtual machine resource information management table the information identifying the virtual machine, the resource capacity of the virtual machine and the information identifying the physical machine with the virtual machine in association with each other;
Associating information for identifying the virtual machine with a policy value that is a threshold value requested by the virtual machine in a policy information management table;
When the average used resource capacity of the virtual machine exceeds the policy value, an allocated resource capacity is calculated such that the average used resource capacity is lower than the policy value, and the average used resource capacity is higher than the policy value. Securing additional resource capacity from other virtual machines having sufficient resource capacity to maintain the policy value without
When the additional resource capacity is reserved, when the reserved additional resource capacity exceeds the unallocated capacity of the physical machine with the virtual machine, each physical machine in the physical machine resource information management table Refer to the unallocated capacity, and move the virtual machine onto a physical machine in which the unallocated capacity is larger than the capacity obtained by adding the resource capacity of the virtual machine and the reserved additional resource capacity. Issuing change instructions to allocate resources;
The resource capacity newly allocated to the virtual machine is subtracted from the unallocated capacity in the physical machine resource information management table, and the resource capacity of the virtual machine in the virtual machine resource information management table is newly allocated to the virtual machine. And a step of rewriting each value so as to increase by the amount of the resource capacity.

Images