JP6928237B2 - Control program, control device and control method - Google Patents

Description

The present invention relates to control programs, control devices and control methods.

For example, a business operator that provides a service to a user (hereinafter, also simply referred to as a business operator) constructs and operates a business system (hereinafter, also referred to as an information processing system) for providing the service.

Specifically, the business operator, for example, has a plurality of virtual machines (hereinafter, also referred to as VM: Virtual Machine) that perform processing for processing requests from users, and processing requests from users for a plurality of virtual machines. A business system having a virtual machine for distribution (hereinafter, also referred to as a load balancer) is constructed. Then, the load balancer refers to, for example, the current load of each virtual machine, and causes the virtual machine having a relatively low load to process the processing request from the user. As a result, the business operator can provide services to users while leveling the load of each virtual machine constituting the business system (see, for example, Patent Documents 1 to 4).

International Publication No. 2011/114623 Japanese Unexamined Patent Publication No. 2015-022501 Special Table 2013-506908 Japanese Unexamined Patent Publication No. 2006-048680

In the above-mentioned business system, when the processing requests from users increase, it may not be possible for one load balancer to distribute the processing requests to each virtual machine.

Therefore, the business operator prepares, for example, a plurality of load balancers as needed. Then, the business operator causes one of the plurality of load balancers to function as a load balancer (hereinafter, also simply referred to as a management device) that distributes processing requests from users to other load balancers. In addition, the business operator causes each of the load balancers other than the management device to function as a load balancer that distributes the processing requests distributed from the management device to each virtual machine. As a result, the business operator can provide services to users while leveling the load of each virtual machine constituting the business system even when a plurality of load balancers operate. ..

Here, the management device may add or delete a load balancer, for example, in addition to distributing processing requests from users. Specifically, the management device acquires information indicating the current load (hereinafter, also referred to as load information) from each of the physical machines on which each virtual machine operates. Then, for example, when there is a physical machine whose current load is higher than a predetermined threshold value, the management device determines that the load of the load balancer operating on the physical machine is high, and operates on the physical machine. Add a load balancer. This enables the management device to determine whether or not to add a load balancer to each physical machine without acquiring load information for each virtual machine, and each load balancer makes a processing request. It is possible to adjust the number of virtual machines to be distributed.

However, in the physical machine on which each virtual machine operates, a virtual machine (hereinafter, also referred to as another virtual machine) in which the load balancer does not distribute processing requests may operate. Therefore, when the management device adds the load balancer based on the load information for each physical machine, the load balancer may be added more than necessary, and the processing load of the heavy physical machine is further increased. In some cases.

Therefore, in one aspect, it is an object of the present invention to provide a control program, a control device, and a control method capable of leveling the load of each physical machine.

In one aspect of the embodiment, a specific virtual machine that distributes the received request to any of the plurality of virtual machines, each of which is built on one of the plurality of physical machines, is placed on one of the plurality of physical machines. In the control program to be executed, the physical machine to which the specific virtual machine is to be placed is specified based on the load information of the plurality of physical machines, and the plurality of virtual machines of the plurality of virtual machines are specified based on the load information of the specified physical machine. Among them, the number of virtual machines capable of distributing the requests received by the specific virtual machine is calculated, and the number of the plurality of virtual machines is calculated according to the arrangement of the specific virtual machine in the specified physical machine. A computer is made to execute a process in which the number of virtual machines corresponding to the above-mentioned number is set as the distribution destination virtual machine for which the request received by the specific virtual machine is distributed.

According to one aspect, it is possible to level the load of each physical machine.

FIG. 1 is a diagram showing an overall configuration of the information processing system 10. FIG. 2 describes a specific example of the processing in the management device 1. FIG. 3 describes a specific example of the processing in the management device 1. FIG. 4 describes a specific example of the processing in the management device 1. FIG. 5 is a diagram showing a hardware configuration of the management device 1. FIG. 6 is a diagram showing a hardware configuration of the physical machine 2. FIG. 7 is a block diagram of the function of the management device 1. FIG. 8 is a block diagram of the functions of the physical machine 2 that are realized by the load balancer 3a. FIG. 9 is a flowchart illustrating an outline of the control process according to the first embodiment. FIG. 10 is a diagram illustrating an outline of a control process according to the first embodiment. FIG. 11 is a diagram illustrating an outline of the control process according to the first embodiment. FIG. 12 is a diagram illustrating an outline of the control process according to the first embodiment. FIG. 13 is a diagram illustrating an outline of the control process according to the first embodiment. FIG. 14 is a diagram illustrating an outline of the control process according to the first embodiment. FIG. 15 is a diagram illustrating an outline of a control process according to the first embodiment. FIG. 16 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 17 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 18 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 19 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 20 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 21 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 22 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 23 is a flowchart illustrating the details of the control process according to the first embodiment. FIG. 24 is a diagram illustrating specific examples of the distribution management information 131 and the host management information 132. FIG. 25 is a diagram illustrating a specific example of VM management information 133. FIG. 26 is a diagram illustrating specific examples of distribution management information 131 and host management information 132. FIG. 27 is a diagram illustrating a specific example of VM management information 133. FIG. 28 is a diagram illustrating specific examples of distribution management information 131 and host management information 132. FIG. 29 is a diagram illustrating specific examples of distribution management information 131 and host management information 132.

[Information processing system configuration]
FIG. 1 is a diagram showing an overall configuration of the information processing system 10. The information processing system 10 shown in FIG. 1 is, for example, a business system for providing a service to a user. In the information processing system 10 shown in FIG. 1, a management device 1 and a physical machine 2 are provided in a data center (not shown). The business terminal 5 can access the data center via a network such as the Internet or an intranet.

The physical machine 2 is composed of, for example, a plurality of physical machines. Each physical machine has a CPU (Central Computing Unit), a memory (DRAM: Dynamic Random Access Memory), and a large-capacity memory such as a hard disk (HDD: Hard Disk Drive). Then, the physical resources of the physical machine 2 are allocated to a plurality of virtual machines 3 that execute each process for providing a service to the user.

The virtualization software 4 is basic software that operates the virtual machine 3 by allocating the CPU, memory, and hard disk of the physical machine 2. The virtualization software 4 operates on, for example, the physical machine 2.

For example, when the user receives a processing request transmitted via a user terminal (not shown), the management device 1 distributes the received processing request to one of the virtual machines 3. The management device 1 may be composed of, for example, a virtual machine 3. Hereinafter, a specific example of the processing of the management device 1 will be described.

[Specific examples of processing in the management device]
2 to 4 show a specific example of the processing in the management device 1. Hereinafter, the description will be made assuming that the physical machine 2 is composed of physical machines 21, 22 and 23. Further, a part of the virtual machines 3 operating in the physical machines 21, 22 and 23 distributes processing requests to the other virtual machines 3 by load balancing devices 31a, 32a and 33a (hereinafter, these are collectively referred to as load balancing). It will be described as assuming that each of them operates as a device (also referred to as a device 3a). Further, the load balancer 31a distributes the processing request to the VMs 31b, 31c and 31d, the load balancer 32a distributes the processing request to the VMs 32b, 32c and 32d, and the load balancer 33a distributes the processing request to the VMs 33b and 33c. The description will be made assuming that the processing request is distributed to the user.

When the management device 1 receives a processing request from a user terminal (not shown) or the like, the management device 1 distributes the received processing request to any of the load balancing devices 31a, 32a, and 33a.

Specifically, as shown in FIG. 2, the management device 1 acquires, for example, information indicating the load of each physical machine as a whole (hereinafter, also simply referred to as load information) from the physical machines 21, 22 and 23. Then, the management device 1 identifies, for example, the physical machine 2 having the smallest current load based on the acquired load information. After that, as shown in FIG. 3, the management device 1 distributes processing requests to, for example, the load balancer 3a operating in the specified physical machine 2. As a result, the management device 1 can level the load on each physical machine 2.

Further, the management device 1 determines, for example, whether or not it is necessary to add or delete the load balancer in each physical machine 2 at a periodic timing.

Specifically, as shown in FIG. 3, the management device 1 determines whether or not there is a physical machine 2 whose current load exceeds a predetermined threshold value, for example, based on the acquired load information. judge. Then, when there is a physical machine 2 that exceeds a predetermined threshold value, the management device 1 determines that the load of the load balancer 3a operating in the physical machine 2 is high, and determines that the load of the new load balancer 3a is high. Is added. As a result, the management device 1 can prevent the response to the processing request from being delayed due to the high load of the load balancer 3a, for example. Further, in this case, the management device 1 may determine whether or not to add a new load balancer 3a without acquiring the load information of each of the virtual machines 3 generated in each physical machine 2. It will be possible.

Here, the physical machine 2 may generate a virtual machine 3 (another virtual machine 3) in which the load balancer 3a does not distribute processing requests. Specifically, in the example shown in FIG. 4, the other virtual machines 3 VM31e, 31f and 31g are generated in the physical machine 21, and the other virtual machine 3 VM32e is generated in the physical machine 22. ing. Therefore, when the management device 1 adds the load balancer 3a based on the load information of 2 for each physical machine, the load balancer 3a may be added more than necessary, and the processing load of each physical machine 2 is increased. May increase more.

Therefore, the management device 1 in the present embodiment distributes the processing request received to any of the plurality of virtual machines 3 constructed in any of the plurality of physical machines 2 based on the load information of the plurality of physical machines 2. The physical machine 2 to which the specific load balancer 3a (hereinafter, also referred to as the specific virtual machine 3) is arranged is specified. Then, the management device 1 calculates the number of virtual machines 3 that can distribute the processing requests received by the specific load balancer 3 among the plurality of virtual machines 3 based on the load information of the specified physical machine 2.

Further, the management device 1 sets a specific load on the number of virtual machines 3 according to the calculated number among the plurality of virtual machines 3 according to the arrangement of the specific load balancer 3a on the specified physical machine 2. Let the virtual machine 3 be the distribution destination for distributing the processing requests received by the distribution device 3a.

That is, when the management device 1 adds a new load balancer 3a, the management device 1 adds a new load balancer 3a to the physical machine 2 having a relatively small load. Then, the management device 1 is a new load balancer that distributes the processing requests to the virtual machine 3 (a part of the virtual machine 3) generated by the load balancer 3a generated on the physical machine 2 having a large load. Let 3a do it.

As a result, the management device 1 can prevent the new load balancer 3a from being added to the physical machine 2 having a large load. Further, the management device 1 can suppress the load of the physical machine 2 having a large load by reducing the number of virtual machines 3 to be distributed by the load balancer 3a generated in the physical machine 2 having a large load. Become. Therefore, the management device 1 can level the load of each physical machine 2.

[Hardware configuration of information processing system]
Next, the hardware configuration of the information processing system 10 will be described. FIG. 5 is a diagram showing a hardware configuration of the management device 1. Further, FIG. 6 is a diagram showing a hardware configuration of the physical machine 2.

As shown in FIG. 5, the management device 1 includes a CPU 101 which is a processor, a memory 102, an external interface (hereinafter, also referred to as an I / O unit) 103, and a storage medium 104. The parts are connected to each other via the bus 105.

The storage medium 104 stores, for example, a program 110 for performing a process for managing the load balancer 3a (hereinafter, also referred to as a control process) in a program storage area (not shown) in the storage medium 104. Further, the storage medium 104 has, for example, an information storage area 130 (hereinafter, also referred to as a storage unit 130) for storing information used when performing control processing.

When the program 110 is executed, the CPU 101 loads the program 110 from the storage medium 104 into the memory 102, and performs control processing in cooperation with the program 110. Further, the external interface 103 communicates with, for example, the physical machine 2.

Further, as shown in FIG. 6, the physical machine 2 has a CPU 201 which is a processor, a memory 202, an external interface (hereinafter, also referred to as an I / O unit) 203, and a storage medium 204. The parts are connected to each other via the bus 205.

The storage medium 204 stores, for example, a program 210 for performing a control device in a program storage area (not shown) in the storage medium 204. Further, the storage medium 204 has, for example, an information storage area 230 (hereinafter, also referred to as a storage unit 230) for storing information used when performing control processing.

When the program 210 is executed, the CPU 201 loads the program 210 from the storage medium 204 into the memory 202, and performs control processing in cooperation with the program 210. Further, the external interface 203 communicates with, for example, the management device 1 and the business operator terminal 5.

[Information processing system functions]
Next, the function of the information processing system 10 will be described. FIG. 7 is a block diagram of the function of the management device 1. Further, FIG. 8 is a block diagram of the functions of the physical machine 2 that are realized by the load balancer 3a.

[Management device function]
First, the function of the management device 1 will be described. By cooperating with the program 110, the CPU 101 of the management device 1 includes a processing request receiving unit 111, a processing request distribution unit 112, an information acquisition unit 113, an information management unit 114, and the information management unit 114, as shown in FIG. It operates as an arrangement destination specifying unit 115, a machine number calculation unit 116, and a distribution destination determination unit 117. Further, in the information storage area 130, for example, distribution management information 131, host management information 132, VM management information 133, and threshold value information 134 are stored.

The processing request receiving unit 111 receives, for example, a processing request transmitted from a user terminal (not shown). Then, the processing request distribution unit 112 distributes the processing request received by the processing request receiving unit 111 to any of the load balancers 3a, for example.

The information acquisition unit 113 acquires load information from each physical machine 2 at a periodic timing, for example. Then, the information management unit 114 updates the distribution management information 131, the host management information 132, and the VM management information 133 stored in the information storage area 130 based on the load information acquired by the information acquisition unit 113. The distribution management information 131 is information about the management device 1 and each load balancing device 3a, and the host management information 132 is information about each physical machine 2. Further, the VM management information 133 is information about each virtual machine 3 to which the load balancer 3a distributes processing requests.

The placement destination specifying unit 115 specifies the physical machine 2 to be placed where the new load balancer 3a is to be placed, based on the load information of each physical machine 2. Specifically, for example, when there is a physical machine 2 whose current load exceeds the threshold information 134, the placement destination specifying unit 115 specifies the physical machine 2 to be placed where the new load balancer 3a is placed. ..

The machine number calculation unit 116 calculates the number of virtual machines 3 among the virtual machines 3 to which the new load balancer 3a can distribute processing requests, based on the load information of the physical machines 2 specified by the placement destination identification unit 115. calculate.

The distribution destination determination unit 117 is set to the number calculated by the machine number calculation unit 116 of each virtual machine 3 according to the arrangement of the new load balancer 3a on the physical machine 2 specified by the arrangement destination identification unit 115. The corresponding number of virtual machines 3 is determined as the virtual machines 3 to which the new load balancer 3a distributes the processing requests.

[Functions of physical machine (load balancer)]
Next, among the functions of the physical machine 2, the functions realized by the load balancer 3a will be described. The CPU 201 of the physical machine 2 functions as a processing request receiving unit 311 and a processing request distribution unit 312 as shown in FIG. 8 by cooperating with the program 210. Further, in the information storage area 230, for example, the distribution management information 131, the host management information 132, and the VM management information 133 are stored, as in the information storage area 130 in the management device 1.

The processing request receiving unit 311 receives, for example, the processing request transmitted from the management device 1. Then, the processing request distribution unit 312 distributes the processing request received by the processing request receiving unit 311 to any of the virtual machines 3, for example.

[Outline of the first embodiment]
Next, the outline of the first embodiment will be described. FIG. 9 is a flowchart illustrating an outline of the control process according to the first embodiment. 10 to 15 are diagrams for explaining the outline of the control process according to the first embodiment. The outline of the control process in the first embodiment shown in FIG. 9 will be described with reference to FIGS. 10 to 15.

[Load Balancing Device in the First Embodiment]
First, the load balancer 3a according to the first embodiment will be described.

As shown in FIG. 10, the load balancer 3a according to the first embodiment requests processing requests distributed by the management device 1 to each of the plurality of virtual machines 3 generated in one or more physical machines 2. Sort out.

That is, the load balancer 3a in the first embodiment refers not only to the virtual machine 3 generated in the same physical machine 2 as the own device but also to the virtual machine 3 generated in another physical machine 2. Also distributes processing requests.

Specifically, in the example shown in FIG. 10, the load balancer 3a generated in the physical machine 21 is generated in the virtual machines 3 generated in the physical machine 21, VM31b, 31c and 31d, and in the physical machine 22. The processing requests distributed by the management device 1 are distributed to the virtual machines 3 VMs 32b, 32c, and 32d. Further, in the example shown in FIG. 10, the load balancer 3c generated by the physical machine 21 requests the processing requests distributed by the management device 1 to the VMs 33b and 31c, which are the virtual machines 3 generated by the physical machine 23. Is sorted.

As a result, for example, when the load of the load balancer 3a generated by each physical machine 2 is small, the management device 1 distributes processing requests to the virtual machines 3 generated by the plurality of physical machines 2 by one unit. It becomes possible to let the load balancer 3a perform the operation. Therefore, the management device 1 can reduce the processing load of each physical machine 2. Hereinafter, one or more physical machines 2 in which one or more virtual machines 3 to which one load balancer 3a distributes processing requests operates are also referred to as a group.

[Flowchart diagram for outline of the first embodiment]
Next, a flowchart of an outline of the first embodiment will be described.

As shown in FIG. 9, the management device 1 waits until the virtual machine addition determination timing (NO in S1). The virtual machine addition determination timing may be, for example, the timing at which the existence of the physical machine 2 whose current load exceeds the threshold value information 134 stored in advance in the information storage area 130 is detected. Specifically, for example, as shown in FIG. 11, the management device 1 detects that the load of the physical machine 21 exceeds the threshold information 134 due to the generation of the VM31e, which is another virtual machine 3. If this is the case, it may be determined that it is time to add the virtual machine.

Then, when the virtual machine addition timing is reached (YES in S1), as shown in FIG. 12, the management device 1 is a new load balancer from the plurality of physical machines 2 based on the load information of the plurality of physical machines 2. The physical machine 2 to which the 3a is arranged is specified (S2). Further, as shown in FIG. 12, the management device 1 is a load balancer 3a among a plurality of virtual machines 3 constructed in the plurality of physical machines 2 based on the load information of the physical machines 2 specified in the process of S2. Calculates the number of virtual machines 3 that can distribute the processing requests received by (S3).

After that, the management device 1 increases the number of virtual machines according to the number calculated in the process of S3 among the plurality of virtual machines 3 according to the arrangement of the load balancer 3a on the physical machine 2 specified in the process of S2. Let 3 be a virtual machine 3 to which the load balancer 3a distributes processing requests (S4).

Specifically, for example, when the physical machine 22 is specified in the process of S2, the management device 1 generates a new load balancer 3a, the load balancer 32a, in the physical machine 22, as shown in FIG. .. Then, the management device 1 causes, for example, the load balancer 32a, which is a new load balancer 3a, to distribute the processing requests to the VMs 32b, 32c, and 32d operating in the physical machine 22.

Further, for example, when the number of virtual machines 3 calculated in the process of S3 is 6 or more, the management device 1 is added to the VMs 32b, 32c, and 32d generated in the physical machine 22 as shown in FIG. , The physical machine 21 causes the load balancer 32a, which is a new load balancer 3a, to distribute the processing requests to the VMs 31b, 31c, and 31d generated. Then, in this case, for example, as shown in FIG. 14, the management device 1 deletes the load balancer 31a from which the virtual machine 3 to which the processing request is distributed has disappeared.

On the other hand, for example, when the physical machine 23 is specified in the process of S2 and the number of virtual machines 3 calculated in the process of S3 is 5 or more, the management device 1 uses the physical machine 23 as shown in FIG. In addition to the VMs 33b and 33c generated in the above, the load balancer 33a, which is an existing load balancer 3a, is made to distribute the processing requests for the VMs 32b, 32c and 32d generated in the physical machine 22.

That is, when the management device 1 adds a new load balancer 3a, the management device 1 adds a new load balancer 3a to the physical machine 2 having a relatively small load. Then, the management device 1 is a new load balancer that distributes the processing requests to the virtual machine 3 (a part of the virtual machine 3) generated by the load balancer 3a generated on the physical machine 2 having a large load. Let 3a do it.

As a result, the management device 1 can prevent the new load balancer 3a from being added to the physical machine 2 having a large load. Further, the management device 1 can suppress the load of the physical machine 2 having a large load by reducing the number of virtual machines 3 to be distributed by the load balancer 3a generated in the physical machine 2 having a large load. Become. Therefore, the management device 1 can level the load of each physical machine 2.

[Details of the first embodiment]
Next, the details of the first embodiment will be described. 16 to 23 are flowcharts illustrating the details of the control process according to the first embodiment. Further, FIGS. 24 to 29 are diagrams for explaining the details of the control process according to the first embodiment. The details of the control processing shown in FIGS. 16 to 23 will be described with reference to FIGS. 24 to 29.

[Distribution processing]
First, a process (hereinafter, also referred to as a distribution process) performed when a process request is transmitted from a user terminal (not shown) or the like will be described. 16 and 17 are diagrams for explaining the sorting process.

As shown in FIG. 16, the processing request receiving unit 111 of the management device 1 waits until, for example, receives the processing request transmitted by the user via the user terminal (not shown) (NO in S11).

Then, when the processing request is received (YES in S11), the processing request distribution unit 112 of the management device 1 refers to the host management information 132 and calculates the sum of the loads of the physical machines 2 of each group (S12). .. After that, the processing request distribution unit 112 refers to the distribution management information 131, and identifies the load balancer corresponding to the group having the smallest sum calculated in the processing of S12 (S13). Hereinafter, specific examples of the distribution management information 131 and the host management information 132 will be described.

[Specific examples of distribution management information and host management information]
24, 26, 28, and 29 are diagrams for explaining specific examples of the distribution management information 131 and the host management information 132. Specifically, FIGS. 24 (A), 26 (A), 28 (A), and 29 (A) are diagrams for explaining specific examples of the distribution management information 131. 24 (B), 26 (B), 28 (B), and 29 (B) are diagrams for explaining a specific example of the host management information 132. The contents of the distribution management information 131 and the host management information 132 shown in FIG. 24 correspond to the states of the respective devices described in FIG.

The distribution management information 131 shown in FIG. 24A and the like includes a "group ID" that identifies each group, a "flag" that indicates whether each device is the management device 1 or the load balancer 3a, and the like. It has an "device ID" that identifies each device and an "IP address" in which the IP address of each device is set as items. In the "flag", either "true" indicating that each device is the management device 1 or "false" indicating that each device is the load balancing device 3a is set. Further, the distribution management information 131 shown in FIG. 24A or the like is the number of load balancers 3a in which the management device 1 distributes processing requests, or the virtual machine 3 in which the load balancer 3 distributes processing requests. The "distribution number" in which the number of processing requests is set and the upper limit of the number of load balancing devices 3a in which the management device 1 distributes processing requests, or the number of virtual machines 3 in which the load balancing device 3 distributes processing requests. The "upper limit" is set. Further, the distribution management information 131 shown in FIG. 24A or the like is the “load information” in which the current load information of each device is set and the “host ID” that identifies the physical machine 2 in which each device is generated. "Is set. In the "load information", for example, the current average usage rate of the CPU assigned to each device is set.

Specifically, in the distribution management device 1 shown in FIG. 24 (A), "true" is set as the "flag" for the information whose "group ID" is "0000", and "1000" is set as the "device ID". Is set, and "100.100.100.50" is set as the "IP address". Then, in the distribution management device 1 shown in FIG. 24 (A), "2 (units)" is set as the "distribution number" for the information whose "group ID" is "0000", and is set as the "upper limit value". "4 (units)" is set, "10% / sec" is set as "load information", and "2000" is set as "host ID". Further, in the distribution management device 1 shown in FIG. 24 (A), "false" is set as the "flag" for the information in which the "group ID" is "0001", and "1001" is set as the "device ID". It is set, and "100.100.100.51" is set as the "IP address". Then, in the distribution management device 1 shown in FIG. 24 (A), "6 (units)" is set as the "distribution number" for the information whose "group ID" is "0001", and is set as the "upper limit value". "6 (units)" is set, "10% / sec" is set as "load information", and "2001" is set as "host ID". Description of the other information contained in FIG. 24 (A) will be omitted.

Further, in the host management information 132 shown in FIG. 24B or the like, a "group ID" for identifying each group, a "host ID" for identifying each physical machine 2, and an IP address of each physical machine 2 are set. It has an "IP address" to be used as an item. Then, in the host management information 132 shown in FIG. 24B and the like, the "VM number" in which the number of virtual machines 3 generated in each physical machine 2 is set, and the load distribution device 3a and the load distribution device 3a are used. The items include a "number of own service VMs" in which the total number of virtual machines 3 to which processing requests are distributed is set, and a "load information" in which the current load information of each physical machine 2 is set.

Specifically, in the host management information 132 shown in FIG. 24 (B), the information in which the "group ID" is "00001" and the "host ID" is "20001" is referred to as "100. "100.100.1" is set, "4 (units)" is set as "VM number", "4 (units)" is set as "own service VM number", and "30%" is set as "load information". / Second "is set. Further, in the host management information 132 shown in FIG. 24 (B), the information in which the "group ID" is "00001" and the "host ID" is "20002" is referred to as "100.100. "100.2" is set, "3 (units)" is set as the "VM number", "3 (units)" is set as the "own service VM number", and "20% / sec" is set as the "load information". "Is set. The description of other information included in FIG. 24 (B) will be omitted.

Then, in the processing of S12, the processing request distribution unit 112 refers to, for example, the host management information 132 described with reference to FIG. The sum of the set information "30% / sec" and "20% / sec" is calculated as "50% / sec". Further, the processing request distribution unit 112 refers to, for example, the host management information 132 described with reference to FIG. 24 (B), and uses the information set in the "load information" of the information in which the "group ID" is "0002". Identify a certain "30% / sec". That is, the processing request distribution unit 112 calculates "50% / sec" as the sum of the loads of each physical machine 2 included in the group whose "group ID" is "0001", and the "group ID" is "0002". "30% / sec" is calculated as the sum of the loads of each physical machine 2 included in the group.

After that, the processing request distribution unit 112 refers to the distribution management information 131 described with reference to FIG. 24A in the processing of S13, and “30% / sec” calculated in the processing of S12 (calculated in the processing of S12). "0001" corresponding to "50% / sec" and "30% / sec") is the information set in the "device ID" of the information set in the "group ID". Specify "10001".

Returning to FIG. 16, the processing request distribution unit 112 transmits the processing request received in the processing of S11 to the load balancer 3a specified in the processing of S13 (S14). Specifically, when the "group ID" of the load balancer 3a specified in the process of S13 is "10001", the load balancer 3a whose "group ID" is "10001" is accepted in the process of S11. Send a processing request.

As a result, the management device 1 can level the processing load in each load balancer 3a.

On the other hand, as shown in FIG. 17, the processing request receiving unit 311 of the load balancing device 3a waits until the processing request transmitted from the management device 1 is received (NO in S21).

Then, when the processing request is received (YES in S21), the processing request distribution unit 312 refers to the VM management information 133, and the virtual machine 3 having the smallest load information from the virtual machine 3 to which the own device distributes the processing request. (S22). Hereinafter, specific examples of VM management information will be described.

[Specific example of VM management information]
25 and 27 are diagrams for explaining a specific example of the VM management information 133. The content of the VM management information 133 shown in FIG. 25 corresponds to the state of each device described in FIG.

The VM management information 133 shown in FIG. 25 and the like includes a "host ID" that identifies the physical machine 2 in which each virtual machine 3 is generated, a "VMID" that identifies each virtual machine 3, and an IP of each virtual machine 3. It has an "IP address" in which an address is set as an item. Further, in the VM management information 133 shown in FIG. 25 or the like, a "processing type" that identifies a service provided to a user by operating each virtual machine 3 and current load information of each virtual machine 3 are set. It has "load information" as an item.

Specifically, in the VM management information 133 shown in FIG. 25, the information in which the "host ID" is "20001" and the "VMID" is "30001" has "100.100.100." As the "IP address". "101" is set, "A" is set as the "processing type", and "10% / sec" is set as the "load information". Further, in the VM management information 133 shown in FIG. 25, the information in which the "host ID" is "20001" and the "VMID" is "30002" is "100.100.100.102" as the "IP address". Is set, "A" is set as the "processing type", and "5% / sec" is set as the "load information". Description of the other information contained in FIG. 25 will be omitted.

Then, in the processing of S22, when the load balancing device 31a receives the processing request from the management device 1, the processing request distribution unit 312 refers to, for example, the VM management information 133 shown in FIG. "20001" corresponding to the operating physical machine 2 identifies "30001", "30002" and "30003" which are the information set in the "VMID" of the information set in the "host ID". Here, in the VM management information 133 shown in FIG. 25, the "load information" of the information in which "30001", "30002", and "30003" are set in the "VMID" includes "10% / sec" and "5". "% / Second" and "10% / second" are set respectively. Therefore, in the processing request distribution unit 312, "5% / sec" (the smallest value among "10% / sec", "5% / sec", and "10% / sec") becomes "load information". The information "30002" which is the information set in the "VMID" of the set information is specified (S22).

Returning to FIG. 16, the processing request distribution unit 312 transmits the processing request received in the processing of S21 to the virtual machine 3 specified in the processing of S22 (S23). Specifically, when the virtual machine 3 whose "VMID" is "30002" is specified in the processing of S22, the processing request distribution unit 312 requests the virtual machine 3 whose "VMID" is "30002" to process. To send.

As a result, the load balancer 3a can equalize the processing load in each virtual machine 3 that distributes the processing requests.

[Information update processing]
Next, a process for updating the distribution management information 131, the host management information 132, and the VM management information 133 stored in the information storage area 130 (hereinafter, also referred to as an information update process) will be described. FIG. 18 is a diagram illustrating an information update process.

As shown in FIG. 18, the information acquisition unit 113 of the management device 1 waits until the information acquisition timing (NO in S31). The information acquisition timing is a timing for acquiring information necessary for updating the distribution management information 131, the host management information 132, and the VM management information 133, and may be, for example, a periodic timing.

Then, when the information acquisition timing comes (YES in S31), the information acquisition unit 113 accesses each physical machine 2, and the information necessary for updating the distribution management information 131, the host management information 132, and the VM management information 133. (S32).

Specifically, the information acquisition unit 113 acquires, for example, the information set in the “number of VMs” and the “number of own service VMs” in the host management information 132. Further, the information acquisition unit 113 acquires information set in, for example, the "VMID", "IP address", "processing type", and "load information" in the VM management information 133.

After that, the information management unit 114 of the management device 1 updates the distribution management information 131, the host management information 132, and the VM management information 133 stored in the information storage area 130 based on the information acquired in the process of S32 (S33). ).

Specifically, the information management unit 114 updates the host management information 132 and the VM management information 133 with the information acquired in the process of S32, for example. Further, the information management unit 114 sets the information set in the "distribution number" and the "upper limit value" in the distribution management information 131 and the "load information" in the host management information 132 from the information acquired in the process of S32. The information to be obtained is calculated, and the distribution management information 131 and the host management information 132 are updated according to the calculated information.

As a result, the management device 1 can perform control processing based on the information updated at any time according to the change in the state of the virtual machine 3.

[Details of control processing]
Next, the details of the control process will be described. 19 to 23 are diagrams for explaining the details of the control process.

As shown in FIG. 19, the arrangement destination specifying unit 115 of the management device 1 waits until the control timing (NO in S41). The control timing may be, for example, a periodic timing.

Then, when the control timing is reached (YES in S41), the placement destination specifying unit 115 acquires the load information included in the host management information 132 stored in the information storage area 130 (S42). Specifically, the placement destination specifying unit 115 acquires the load information for each physical machine 2 among the information included in the host management information 132. Further, in this case, the arrangement destination specifying unit 115 acquires the threshold information 134 stored in the information storage area 130 (S43).

After that, the placement destination specifying unit 115 identifies the physical machine 2 from the plurality of physical machines 2 in which the load information acquired in the process of S42 exceeds the threshold information 134 acquired in the process of S43 (S44).

As a result, when there is no physical machine 2 whose load information exceeds the threshold information 134 (NO in S45), the placement destination specifying unit 115 ends the control process. That is, in this case, the placement destination specifying unit 115 determines that it is not necessary to place the new load balancer 3a in any of the physical machines 2.

On the other hand, when there is a physical machine 2 whose load information exceeds the threshold information 134 (YES in S45), the placement destination specifying unit 115 sets the new load balancer 3a to any of the physical machines 2 as shown in FIGS. 20 and 20 and later. Performs the process for arranging the crab. Hereinafter, a specific example will be described when there is a physical machine 2 whose load information exceeds the threshold information 134.

[Specific example when there is a physical machine whose load information exceeds the threshold information]
26 and 27 are diagrams illustrating specific examples of distribution management information 131, host management information 132, and VM management information 133 when there is a physical machine 2 whose load information exceeds the threshold information 134. Specifically, as described with reference to FIG. 11, a specific example of each information when the load information of the physical machine 21 exceeds the threshold information 134 as a result of generating another virtual machine 3 VM31e in the physical machine 21. Will be explained.

In this case, as shown in the underlined portion of FIG. 26B, the information management unit 114 sets the "VM number" of the information in which the "group ID" is "0001" and the "host ID" is "20001". Add 1 to the set value. On the other hand, the information management unit 114 does not update the value set in the "own service VM number" because the VM 31e generated in the physical machine 21 is another virtual machine 3.

Further, in this case, the information management unit 114 updates the "load information" of the information in which the "group ID" is "0001" and the "host ID" is "20001". Specifically, as shown in the underlined portion of FIG. 26B, the information management unit 114 has, for example, a "load" of information in which the "group ID" is "0001" and the "host ID" is "20001". Update "Information" to "45% seconds".

Further, in the information management unit 114, as the information corresponding to the VM31e generated in the physical machine 21, for example, as shown in the underlined portion of FIG. 27, the "host ID" is "20001" and the "VMID" is "VMID". Add information that is "30009", "IP address" is "100.100.100.109", "processing type" is "B", and "load information" is "15% / sec". ..

Then, for example, when the value indicated by the threshold value information 134 stored in the information storage area 130 is "40% / sec", the load information of the physical machine 21 exceeds the threshold value information 134 in the arrangement destination specifying unit 115. It is determined that the load balancer 3a is present, and the process for arranging the new load balancer 3a in any of the physical machines 2 is started (YES in S44 and S45).

Returning to FIG. 19, when there is a physical machine 2 whose load information exceeds the threshold information 134 (YES in S45), the placement destination specifying unit 115 refers to the host management information 132 and a plurality of physical machines 2 as shown in FIG. Among the physical machines 2, one or more physical machines 2 on which one or more virtual machines 3 whose processing requests are distributed by the load balancer 3a operating on the existing physical machines 2 operate are specified (S51).

Specifically, when the load information of the physical machine 21 exceeds the threshold information 134, the placement destination specifying unit 115 refers to, for example, the host management information 132 described with reference to FIG. 26B, and the physical machine 21 and the physical machine 21 It identifies the physical machine 22 whose information set in the "group ID" is the same as that of the physical machine 21.

Then, the placement destination specifying unit 115 refers to the host management information 132, and identifies the physical machine 2 whose load information is less than a predetermined threshold value from the one or more physical machines specified in the process of S51 (S52). The predetermined threshold value is, for example, a value obtained by subtracting the value indicated by the load information of the load balancer 3a operating in the physical machine 2 existing in the process of S45 from the value indicated by the load information of each physical machine 2. good.

Specifically, when the load information of the physical machine 21 exceeds the threshold information 134, the placement destination specifying unit 115 refers to, for example, the distribution management information 131 described with reference to FIG. 26 (A), and refers to the physical machine 21. "10001" corresponding to the load balancer 3a specifies "10% / sec" which is the information set in the "load information" of the information set in the "device ID". Further, the placement destination specifying unit 115 refers to, for example, the host management information 132 described with reference to FIG. 26B, and “20002” corresponding to the physical machine 22 included in the same group as the physical machine 21 is the “host ID”. Specify "20% / sec" which is the information set in the "load information" of the information set in.

When the threshold information 134 stored in the information storage area 130 is "40% / sec", the predetermined threshold value is "10% / sec", which is the specified value, and the threshold information 134 is "40% / sec". It is "30% / sec" subtracted from "second", which is larger than the specified value "20% / sec". Therefore, in this case, the placement destination specifying unit 115 specifies the physical machine 22 as the physical machine 2 whose load information is less than a predetermined threshold value.

After that, when there is a physical machine 2 whose load information is less than a predetermined threshold value (YES in S53), the placement destination specifying unit 115 places one of the existing physical machines 2 as the placement destination of the new load balancer 3a. A new load balancer 3a is arranged in the determined physical machine 2 as the physical machine 2 (S54).

Further, in this case, the distribution destination determination unit 117 of the management device 1 transfers all of the virtual machines 3 to which the processing requests are distributed among the virtual machines 3 operating in the physical machines 2 existing in the processing of S53 in S54. The load balancer 3a arranged in the process determines as the virtual machine 3 that distributes the process request (S55).

Specifically, in the physical machine 22, when the VMs 32b, 32c and 32d are operating as the virtual machines 3 to which the load balancer 31a distributes the processing requests, the distribution destination determination unit 117 newly adds the VMs 32b, 32c and 32d. The load balancer 32a, which is a load balancer 3a, determines the virtual machine 3 to distribute processing requests.

That is, when the load information of the physical machine 21 exceeds the threshold information 134, the placement destination specifying unit 115 suppresses the number of virtual machines 3 to which the load balancer 31a operating in the physical machine 21 distributes processing requests.

As a result, the management device 1 can reduce the load of the physical machine 21 whose load information exceeds the threshold information 134.

Subsequently, as shown in FIG. 21, the machine number calculation unit 116 of the management device 1 indicates that the load distribution device 3a arranged in the process of S54 refers to the virtual machines 3 other than the virtual machine 3 determined in the process of S55. A virtual machine generated in a physical machine 2 other than the physical machine 2 determined in the processing of S54 among one or more physical machines 2 specified in the processing of S51 whether or not it is possible to distribute the processing request. Judgment is made every 3 (S61).

Then, when it is determined that the processing request can be distributed to the virtual machines 3 other than the virtual machine 3 determined in the processing of S55 (YES in S62), the distribution destination determination unit 117 processes the processing of S62. The virtual machine 3 determined to be able to be distributed in S54 is determined as the virtual machine 3 to which the new load balancer 3a arranged in the process of S54 distributes the processing request (S63).

That is, the physical machine 2 that generated the new load distribution device 3a processes not only the virtual machine 3 that operates in the physical machine 2 but also the virtual machines 3 other than the virtual machine 3 that operates in the physical machine 2. It may be possible to sort out requests. Therefore, in the process of S61, the machine number calculation unit 116 determines whether or not the load balancer 3a arranged in the process of S54 can distribute the process request to more virtual machines 3. I do.

Specifically, the machine number calculation unit 116 determines, for example, in the process of S54 within the range in which the value set in the "distribution number" in the distribution management information 131 does not exceed the value set in the "upper limit value". The number of virtual machines 3 to which processing requests to be distributed that operate in the physical machines 2 other than the physical machines 2 are assigned to the load distribution device 3a arranged in the processing of S54 for each virtual machine 3 generated in each physical machine 2. Add to the value set in the corresponding "Distribution number". Then, the machine number calculation unit 116 determines the virtual machine 3 in which the number of virtual machines 3 is added to the value set in the “distribution number” as the virtual machine 3 to be distributed by the new load balancer 3a.

After that, the information management unit 114 determines whether or not the load balancer 3a operating on the physical machine 2 that existed in the process of S45 can be deleted (S64). Specifically, the information management unit 114 determines whether or not there is a virtual machine 3 to which the load balancer 3a operating on the physical machine 2 that existed in the process of S45 distributes the processing request. Similarly, when the information management unit 114 determines in the processing of S62 that it is not possible to distribute the processing request to the virtual machine 3 other than the virtual machine 3 determined in the processing of S55 (NO in S62). , S64 is processed.

Then, when it is determined that the load balancer 3a operating in the physical machine 2 existing in the processing of S45 can be deleted (YES in S64), the information management unit 114 determines that the physical machine 2 existing in the processing of S45. The load balancer 3a that was operating in is deleted (S65). On the other hand, when it is determined that the load balancer 3a operating on the physical machine 2 existing in the process of S45 cannot be deleted (NO in S64), the information management unit 114 does not perform the process of S65.

This makes it possible to further reduce the load on the physical machine 21 whose load information exceeds the threshold information 134.

[Specific examples of distribution management information and host management information (1)]
Next, specific examples of the distribution management information 131 and the host management information 132 when the processes of S63 and S65 are performed will be described. Specifically, when each device is in the state described with reference to FIG. 14, specific examples of the distribution management information 131 and the host management information 132 updated in the information update process will be described.

In this case, as shown in FIG. 28 (A), the information management unit 114 is set to "00001" in the "group ID" of the distribution management information 131 shown in FIG. 26 (A), and the "device ID". Delete the information for which "10001" is set. Then, as shown in the underlined portion of FIG. 28, the information management unit 114 has "00001" set in the "group ID", "false" set in the "flag", and "1003000" in the "device ID". It is set, "100.100.100.53" is set in "IP address", "6" is set in "Distribution number", "6" is set in "Upper limit value", and "Load information" is set. The information in which "10% / sec" is set and "20002" is set in the "host ID" is added.

That is, the information management unit 114 reflects the information indicating that the load balancer 31a operating in the physical machine 21 has been deleted and the load balancer 32a has been generated in the physical machine 22 in the distribution management information 131. Further, the information management unit 114 distributes processing requests not only to the three virtual machines 3 generated in the physical machine 22 but also to the three virtual machines 3 generated in the physical machine 21 to the load balancer 31a. Instead, the distribution management information 131 reflects the information indicating that the load balancer 32a has started.

Further, in this case, the information management unit 114 has the "VM number" and "VM number" of the information in which the "group ID" is "00001" and the "host ID" is "20001", as shown in FIG. 28 (B). Subtract 1 from the value set in "Number of VMs of own service". Then, as shown in FIG. 28B, the information management unit 114 sets the "VM number" of the information in which the "group ID" is "00001" and the "host ID" is "20002" and the "own service". 1 is added to the value set in "VM number".

That is, the information management unit 114 reflects the information indicating that the load balancer 31a operating in the physical machine 21 has been deleted and the load balancer 32a has been generated in the physical machine 22 in the host management information 132.

Returning to FIG. 20, when there is no physical machine 2 whose load information is less than a predetermined threshold value in the processing of S53 (NO in S53), the placement destination specifying unit 115 manages the host as shown in FIG. With reference to the information 132, the load balancer 3a operating on the physical machines 2 other than the one or more physical machines 2 specified in the process of S51 is specified from the physical machines 2 of the other group (S71).

That is, in this case, the arrangement destination specifying unit 115 is processed by the load balancer 3a among the load balancers 3a operating in the physical machines 2 in a group different from the physical machines 2 whose load information exceeds the threshold information 134. The load balancer 3a that can distribute the processing request to the virtual machine 3 that distributes the request is specified.

Specifically, when the load information of the physical machine 21 exceeds the threshold information 134, the placement destination specifying unit 115 refers to, for example, the host management information 132 described with reference to FIG. 26 (B), and the physical machine 21 and the physical machine 21 and the physical machine 21. The load distribution device 33a that operates in the physical machine 23, which is the physical machine 2 other than the machine 22, is specified.

Then, the machine number calculation unit 116 also processes each of the load distribution devices 3a specified in the processing of S71 for the virtual machine 3 to which the load distribution device 3a operating in the physical machine 2 existing in S45 distributes the processing request. Whether or not the request can be distributed is determined for each virtual machine 3 generated in one or more physical machines 2 specified in the process of S51 among the plurality of physical machines 2 (S72).

Then, when it is determined that the load balancer 3a capable of distributing the processing request does not exist (NO in S73), the placement destination specifying unit 115 arranges the new physical machine 2 and the new load balancer 3a. It is determined as the previous physical machine 2 (S74).

That is, in this case, the placement destination specifying unit 115 determines that the new load balancer 3a cannot be generated in any of the currently operating physical machines 2. Therefore, the placement destination specifying unit 115 determines that it is necessary to prepare a new physical machine 2 and generate a new load balancer 3a in the physical machine 2. Then, the placement destination specifying unit 115 outputs the above contents to, for example, the business operator terminal 5.

On the other hand, in the processing of S73, when it is determined that the physical machine 2 capable of distributing the processing request exists (YES in S73), the arrangement destination specifying unit 115 is the distribution destination determining unit 115 as shown in FIG. 117 determines the virtual machine 3 determined to be capable of being distributed by the process of S73 as the virtual machine 3 to which the load balancer 3a specified in the process of S71 distributes the processing request (S81).

Specifically, in the machine number calculation unit 116, for example, the load is the threshold information 134 within the range in which the value set in the "distribution number" in the distribution management information 131 does not exceed the value set in the "upper limit value". " Add to the value set in "Number of distributions". Then, the machine number calculation unit 116 loads the virtual machine 3 in which the number of the virtual machines 3 is added to the value set in the “distribution number” on the physical machine 2 specified in the process of S71. It is determined as the virtual machine 3 to be distributed by the distribution device 3a.

After that, the information management unit 114 determines whether or not the load balancer 3a operating on the physical machine 2 that existed in the process of S45 can be deleted (S82). Specifically, the information management unit 114 determines whether or not there is a virtual machine 3 to which the load balancer 3a operating on the physical machine 2 that existed in the process of S45 distributes the processing request.

Then, when it is determined that the load balancer 3a operating on the physical machine 2 existing in the processing of S45 can be deleted (YES in S82), the information management unit 114 determines that the physical machine 2 existing in the processing of S45. The load balancer 3a that was operating in is deleted (S83). On the other hand, when it is determined that the load balancer 3a operating on the physical machine 2 existing in the process of S45 cannot be deleted (NO in S82), the information management unit 114 does not perform the process of S83.

This makes it possible to further reduce the load on the physical machine 21 whose load information exceeds the threshold information 134.

[Specific example of distribution management information and host management information (2)]
Next, a specific example of the distribution management information 131 and the host management information 132 when the processing of S81 is performed and the processing of S83 is performed will be described. Specifically, when each device is in the state described with reference to FIG. 15, specific examples of the distribution management information 131 and the host management information 132 updated in the information update process will be described.

In this case, the information management unit 114 has information in which "00001" is set in the "group ID" of the distribution management information 131 shown in FIG. 26 (A), as shown in the underlined portion of FIG. 29 (A). The value set in "Distribution number" is updated to the value obtained by subtracting "3 (units)" which is the number of virtual machines 3 operating in the physical machine 22. Further, as shown in the underlined portion of FIG. 29 (A), the information management unit 114 is the information in which "00002" is set in the "group ID" of the distribution management information 131 shown in FIG. 26 (A). The value set in the "number of distributions" is updated to a value obtained by adding "3 (units)", which is the number of virtual machines 3 operating on the physical machine 22.

That is, the information management unit 114 reflects in the distribution management information 131 information indicating that the load balancer 33a has started distribution to a part of the virtual machines 3 to which the load balancer 31a has distributed the processing requests. Let me.

As described above, the management device 1 in the present embodiment receives the processing request received by any of the plurality of virtual machines 3 constructed in any of the plurality of physical machines 2 based on the load information of the plurality of physical machines 2. The physical machine 2 to which the specific load balancer 3a is to be arranged is specified. Then, the management device 1 calculates the number of virtual machines 3 that can distribute the processing requests received by the specific load balancer 3 among the plurality of virtual machines 3 based on the load information of the specified physical machine 2.

Further, the management device 1 sets a specific load on the number of virtual machines 3 according to the calculated number among the plurality of virtual machines 3 according to the arrangement of the specific load balancer 3a on the specified physical machine 2. Let the virtual machine 3 be the distribution destination for distributing the processing requests received by the distribution device 3a.

That is, when the management device 1 adds a new load balancer 3a, the management device 1 adds a new load balancer 3a to the physical machine 2 having a relatively small load. Then, the management device 1 is a new load balancer that distributes the processing requests to the virtual machine 3 (a part of the virtual machine 3) generated by the load balancer 3a generated on the physical machine 2 having a large load. Let 3a do it.

As a result, the management device 1 can prevent the new load balancer 3a from being added to the physical machine 2 having a large load. Further, the management device 1 can suppress the load of the physical machine 2 having a large load by reducing the number of virtual machines 3 to be distributed by the load balancer 3a generated in the physical machine 2 having a large load. Become. Therefore, the management device 1 can level the load of each physical machine 2.

The above embodiments can be summarized as follows.

(Appendix 1)
In a control program in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines built on one of the plurality of physical machines is placed on one of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the physical machine to which the specific virtual machine is to be placed is specified, and the physical machine to be placed is specified.
Based on the load information of the specified physical machine, the number of virtual machines that can distribute the request received by the specific virtual machine among the plurality of virtual machines is calculated.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. Set as the distribution destination virtual machine,
A control program characterized by having a computer execute processing.

(Appendix 2)
In Appendix 1,
The load information of the plurality of physical machines is information indicating the current load of each of the plurality of physical machines.
In the specific process, the load information of the plurality of physical machines is referred to, and when the plurality of physical machines have a physical machine whose current load is equal to or higher than a predetermined threshold value, the physical machine to be placed is determined. conduct,
A control program characterized by that.

(Appendix 3)
In Appendix 2,
In the specific process,
Among the plurality of physical machines, one or more physical machines in which one or more virtual machines whose requests are distributed by virtual machines operating in the physical machines whose current load is equal to or higher than the first threshold value are specified.
The physical machine to be placed is determined from the physical machines whose current load is less than the second threshold value among the one or more physical machines.
A control program characterized by that.

(Appendix 4)
In Appendix 3,
In the specific process,
When there is no physical machine whose current load is less than the second threshold value in the one or more physical machines, the physical machine of the placement destination is selected from the physical machines other than the one or more physical machines among the plurality of physical machines. Make machine decisions,
A control program characterized by that.

(Appendix 5)
In Appendix 3,
In the process of setting the number of virtual machines corresponding to the number as the distribution destination virtual machine, the distribution destination virtual machine is determined from the one or more virtual machines.
A control program characterized by that.

(Appendix 6)
In Appendix 5,
In the process of using the number of virtual machines corresponding to the number as the distribution destination virtual machine, each virtual machine operating in each physical machine is determined as the distribution destination virtual machine.
A control program characterized by that.

(Appendix 7)
In Appendix 6,
In the process of using the number of virtual machines according to the number as the distribution destination virtual machine, the virtual machine operating on a physical machine different from the virtual machine that distributes the request to the one or more virtual machines among the one or more virtual machines. Is prioritized and determined as the virtual machine to be distributed.
A control program characterized by that.

(Appendix 8)
In Appendix 5, further
When all of the one or more virtual machines are determined as the distribution destination virtual machines, the virtual machines that distribute the requests to the one or more virtual machines are deleted.
A control program characterized by having a computer execute processing.

(Appendix 9)
In Appendix 1,
In the calculation process
With reference to the load information of the specified physical machine, the difference between the current load of the specified physical machine and the third threshold value is calculated.
The number of additional virtual machines whose load increase of the specified physical machine is equal to or less than the difference is calculated as the number of virtual machines to which the request received by the specific virtual machine can be distributed.
A control program characterized by that.

(Appendix 10)
In Appendix 9,
In the calculation process, the virtual machine capable of distributing the request received by the specific virtual machine to the maximum number of the distribution destination virtual machines in which the increase in the load of the specified physical machine is equal to or less than the difference. Calculated as the number of
A control program characterized by that.

(Appendix 11)
In a control device in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines built in each of the plurality of physical machines is arranged in any of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the placement destination specifying unit that specifies the physical machine to be placed where the specific virtual machine is placed, and the placement destination specifying unit.
A machine number calculation unit that calculates the number of virtual machines that can distribute requests received by the specific virtual machine among the plurality of virtual machines based on the load information of the specified physical machine.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. It has a distribution destination determination unit that serves as a distribution destination virtual machine.
A control device characterized by that.

(Appendix 12)
In Appendix 11,
The load information of the plurality of physical machines is information indicating the current load of each of the plurality of physical machines.
The placement destination specifying unit refers to the load information of the plurality of physical machines, and determines the physical machine of the placement destination when the plurality of physical machines have a physical machine whose current load is equal to or higher than a predetermined threshold value. I do,
A control device characterized by that.

(Appendix 13)
In Appendix 12,
The placement destination identification part is
Among the plurality of physical machines, one or more physical machines in which one or more virtual machines whose requests are distributed by virtual machines operating in the physical machines whose current load is equal to or higher than the first threshold value are specified.
The physical machine to be placed is determined from the physical machines whose current load is less than the second threshold value among the one or more physical machines.
A control device characterized by that.

(Appendix 14)
In Appendix 13,
The placement destination identification part is
When there is no physical machine whose current load is less than the second threshold value in the one or more physical machines, the physical machine of the placement destination is selected from the physical machines other than the one or more physical machines among the plurality of physical machines. Make machine decisions,
A control device characterized by that.

(Appendix 15)
In a control method in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines, each of which is built on one of a plurality of physical machines, is arranged on one of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the physical machine to which the specific virtual machine is to be placed is specified, and the physical machine to be placed is specified.
Based on the load information of the specified physical machine, the number of virtual machines that can distribute the request received by the specific virtual machine among the plurality of virtual machines is calculated.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. Set as the distribution destination virtual machine,
A control method characterized by that.

(Appendix 16)
In Appendix 15,
The load information of the plurality of physical machines is information indicating the current load of each of the plurality of physical machines.
In the specifying step, the load information of the plurality of physical machines is referred to, and when the plurality of physical machines have a physical machine whose current load is equal to or higher than a predetermined threshold value, the physical machine to be placed is determined. conduct,
A control method characterized by that.

(Appendix 17)
In Appendix 16,
In the specific step,
Among the plurality of physical machines, one or more physical machines in which one or more virtual machines whose requests are distributed by virtual machines operating in the physical machines whose current load is equal to or higher than the first threshold value are specified.
The physical machine to be placed is determined from the physical machines whose current load is less than the second threshold value among the one or more physical machines.
A control method characterized by that.

(Appendix 18)
In Appendix 17,
In the specific step,
When there is no physical machine whose current load is less than the second threshold value in the one or more physical machines, the physical machine of the placement destination is selected from the physical machines other than the one or more physical machines among the plurality of physical machines. Make machine decisions,
A control method characterized by that.

1: Management device 2: Physical machine 3: Virtual machine 4: Virtualization software 5: Business terminal

Claims (11)

In a control program in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines built on one of the plurality of physical machines is placed on one of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the physical machine to which the specific virtual machine is to be placed is specified, and the physical machine to be placed is specified.
Based on the load information of the specified physical machine, the number of virtual machines that can distribute the request received by the specific virtual machine among the plurality of virtual machines is calculated.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. Set as the distribution destination virtual machine,
A control program characterized by having a computer execute processing. In claim 1,
The load information of the plurality of physical machines is information indicating the current load of each of the plurality of physical machines.
In the specific process, the load information of the plurality of physical machines is referred to, and when the plurality of physical machines have physical machines whose current load is equal to or higher than a predetermined threshold value, the physical machine to be placed is determined. conduct,
A control program characterized by that. In claim 2,
In the specific process,
Among the plurality of physical machines, one or more physical machines in which one or more virtual machines whose requests are distributed by virtual machines operating in the physical machines whose current load is equal to or higher than the first threshold value are specified.
The physical machine to be placed is determined from the physical machines whose current load is less than the second threshold value among the one or more physical machines.
A control program characterized by that. In claim 3,
In the specific process,
When there is no physical machine whose current load is less than the second threshold value in the one or more physical machines, the physical machine of the placement destination is selected from the physical machines other than the one or more physical machines among the plurality of physical machines. Make machine decisions,
A control program characterized by that. In claim 3,
In the process of setting the number of virtual machines corresponding to the number as the distribution destination virtual machine, the distribution destination virtual machine is determined from the one or more virtual machines.
A control program characterized by that. In claim 5,
In the process of using the number of virtual machines corresponding to the number as the distribution destination virtual machine, each virtual machine operating in each physical machine is determined as the distribution destination virtual machine.
A control program characterized by that. In claim 6,
In the process of using the number of virtual machines according to the number as the distribution destination virtual machine, the virtual machine operating on a physical machine different from the virtual machine that distributes the request to the one or more virtual machines among the one or more virtual machines. Is prioritized and determined as the virtual machine to be distributed.
A control program characterized by that. In claim 5, further
When all of the one or more virtual machines are determined as the distribution destination virtual machines, the virtual machines that distribute the requests to the one or more virtual machines are deleted.
A control program characterized by having a computer execute processing. In claim 1,
The specified load information of the physical machine includes the number of virtual machines generated in the specified physical machine and the load information of each virtual machine generated in the specified physical machine.
In the calculation process, the specific number of virtual machines generated in the specified physical machine and the load information of each of the virtual machines generated in the specified physical machine are used . Calculate the number of virtual machines that can distribute the requests received by the virtual machines,
A control program characterized by that. In a control device in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines built in each of the plurality of physical machines is arranged in any of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the placement destination specifying unit that specifies the physical machine to be placed where the specific virtual machine is placed, and the placement destination specifying unit.
A machine number calculation unit that calculates the number of virtual machines that can distribute requests received by the specific virtual machine among the plurality of virtual machines based on the load information of the specified physical machine.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. It has a distribution destination determination unit that serves as a distribution destination virtual machine.
A control device characterized by that. In a control method in which a specific virtual machine that distributes a request received to any of a plurality of virtual machines, each of which is built on one of a plurality of physical machines, is arranged on one of the plurality of physical machines.
Based on the load information of the plurality of physical machines, the physical machine to which the specific virtual machine is to be placed is specified, and the physical machine to be placed is specified.
Based on the load information of the specified physical machine, the number of virtual machines that can distribute the request received by the specific virtual machine among the plurality of virtual machines is calculated.
According to the arrangement of the specific virtual machine on the specified physical machine, among the plurality of virtual machines, the number of virtual machines corresponding to the calculated number is distributed to the request received by the specific virtual machine. Set as the distribution destination virtual machine,
A control method characterized by that.

Images