Impact cost calculation device, impact cost calculation method, and program

Abstract

Provided is an impact cost calculation device which calculates the impact cost for a case in which a virtual machine is moved within a site or between sites among a plurality of sites where virtual machines are provided, said device being provided with: a state verification unit which acquires either a login state or process state or both the login state and process state of each virtual machine provided at a site; and an impact degree determination unit which, on the basis of either the login state or process state or both the login state and process state, calculates, for each virtual machine, an impact cost for the user caused by moving the virtual machine.

Description

[Technical Field]

[0001] The present invention relates to a technique for estimating the impact of migrating a virtual machine between bases. [Background technology]

[0002] In recent years, various network services and applications have been provided by virtual machines (hereinafter referred to as VMs) that run on servers (physical machines) at multiple locations (for example, data centers).

[0003] In addition, in order to reduce electricity purchasing costs and achieve decarbonization, each site often receives power from two systems: renewable energy sources such as solar power generation, and commercial electricity supplied by electric power companies.

[0004] With renewable energy power generation, the amount of power supply fluctuates from moment to moment. For example, if the amount of renewable energy supply at site A decreases, the VMs at site A can be moved to site B, which has a surplus of renewable energy supply, making it possible to use the renewable energy at site B without waste and reducing the amount of power purchased at site A from the power company.

[0005] Known methods for migrating VMs include live migration technology (Non-Patent Document 1) and planned failover technology (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] https: / / docs.microsoft.com / en-us / windows-server / virtualization / hyper-v / manage / live-migration-overview [Non-patent document 2] https: / / social.technet.microsoft.com / Forums / windowsserver / ja-JP / e5143d67-41a9-4996-827a-f62cc51e4dfb / hyperv Summary of the Invention [Problem to be solved by the invention]

[0007] As described above, moving VMs can effectively utilize renewable energy, but moving VMs may have an undesirable effect on users who use the VMs.

[0008] Therefore, it is desirable to calculate the degree of impact caused by VM migration in advance and to perform VM migration taking that degree of impact into consideration. However, conventional techniques have not provided a technique for calculating the degree of impact caused by VM migration.

[0009] The present invention has been made in view of the above points, and has an object to provide a technique for calculating the degree of influence that occurs when migrating a VM. [Means for solving the problem]

[0010] According to the disclosed technology, there is provided an impact cost calculation device that calculates an impact cost when a virtual machine is moved within or between multiple bases where virtual machines are installed, the impact cost calculation device comprising: a status confirmation unit that acquires either a login status or a process status, or both the login status and the process status, of each virtual machine provided at the base; an impact determination unit that calculates, for each virtual machine, an impact cost on a user caused by the migration of the virtual machine based on either the login state or the process state, or both the login state and the process state; An impact cost calculation device is provided, comprising: [Effects of the Invention]

[0011] The disclosed technology provides a technology for calculating the degree of impact that occurs when migrating a VM. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an overall configuration of a system according to an embodiment of the present invention. [Figure 2] FIG. 10 illustrates an example of VM migration. [Figure 3] FIG. 1 is a diagram illustrating live migration. [Figure 4] FIG. 1 is a diagram illustrating a planned failover. [Figure 5] FIG. 1 is a diagram for explaining an overview of an embodiment. [Figure 6] FIG. 1 is a configuration diagram of a VM migration influence cost calculation device. [Figure 7] 4 is a flowchart for explaining the operation of the first embodiment. [Figure 8] 10 is a flowchart illustrating the operation of the second embodiment. [Figure 9] 10 is a flowchart illustrating the operation of the third embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of using impact costs. [Figure 11] FIG. 2 illustrates an example of a hardware configuration of the apparatus. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention (the present embodiment) will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0014] (System configuration, operation overview) Fig. 1 shows an example of the overall configuration of a system according to this embodiment. As shown in Fig. 1, a plurality of bases each equipped with a group of servers are connected to a network 300. A VM migration impact cost calculation device 100 and a VM migration destination determination device 200 are also connected to the network 300. One or more users are connected to each VM at each base. Here, the "user" may be a user terminal or a network device that connects the user's network to the VM.

[0015] Each base station is supplied with commercial power from a power company and also with power generated from renewable energy sources. Note that there may be base stations that are supplied with only commercial power from a power company, or base stations that are supplied with only power generated from renewable energy sources.

[0016] Each server at each base is equipped with zero or more virtual machines (VMs). A virtual machine (VM) is a computer that realizes the same functions as a physical computer using software. Each VM can be migrated between bases (or between servers within a base) by a setting command from the VM migration destination determination device 200, for example.

[0017] For example, as shown in Figure 2, if the supply of renewable energy at site A decreases, the VM at site A can be moved to site B, which has an excess supply of renewable energy, thereby making efficient use of the renewable energy at site B and reducing the amount of electricity purchased from the power company at site A.

[0018] However, depending on the usage status of the VM, VM migration may affect services, so it is necessary to move the VM while taking into consideration both the impact on services and the reduction in power purchases.

[0019] Therefore, in this embodiment, the VM movement impact cost calculation device 100 determines the impact of movement for each VM, and the VM movement destination determination device 200 migrates VMs starting with those that are least affected. This makes it possible to reduce the amount of power purchased while minimizing the impact of fluctuations in the supply of renewable energy. Note that the VM movement impact cost calculation device 100 may include the functions of the VM movement destination determination device 200.

[0020] (VM migration methods and issues) Known existing methods for migrating a VM within or between sites include live migration (LM) and planned failover.

[0021] Figure 3 shows an overview of live migration of a VM from a server at base A to a server at base B. With live migration, a VM can be moved without stopping running applications, so there is no interruption to service and no impact on users. However, because the VM, including its memory state, is taken over, if there is a large change in the memory state, it can take a long time to migrate a single VM. This makes it difficult to migrate a large number of VMs in a short period of time.

[0022] In order to make effective use of renewable energy, it is necessary to respond to the demand to move a large number of VMs in a short period of time. However, because it is difficult to move a large number of VMs in a short period of time using live migration, there is a possibility that the necessary amount of power consumption may not be moved at the required time.

[0023] Figure 4 shows an overview of planned failover of a VM from a server at base A to a server at base B. Planned failover is a simple connection change, so it can move a large number of VMs. Although moving a VM does not result in data loss, it does require that terminals connected to the VM be shut down and reconnected after the move, resulting in periods when the VM is unavailable and affecting users.

[0024] As mentioned above, when moving VMs using live migration, the time it takes to move can be long depending on the distance between the locations and the memory access status, making it difficult to move a large number of VMs from one location to another instantly.Planned failover allows you to move a large number of VMs, but it will affect users.

[0025] (Outline of the embodiment) In this embodiment, the VM movement impact cost calculation device 100 calculates the impact of moving a VM from one base to another base for each VM in the form of an impact cost.

[0026] The VM movement impact cost calculation device 100 calculates the impact cost based on, for example, the distance between the source and destination of the movement, the distance to the user, the size of the communication bandwidth, the usage status of each VM, the strength of the connection between VMs, etc.

[0027] The VM movement impact cost calculation device 100 performs an impact evaluation at any time when a VM is moved, and the VM movement destination determination device 200 can determine the VM to be moved, the VM movement method, etc. based on the evaluation result.

[0028] An overview of the processing executed by the VM movement impact cost calculation device 100 will be described with reference to Fig. 5. Fig. 5 shows an example in which the VM movement impact cost calculation device 100 calculates the cost of migrating a VM at base A. The VM movement impact cost calculation device 100 can perform similar processing for each base.

[0029] 5, it is assumed that a process confirmation application that acquires login status, process status, resource status, etc. is running on each VM at base A. The VM movement impact cost calculation device 100 periodically collects information (login status, process status, resource status, distance, bandwidth, etc.) about each VM at base A, and calculates the cost of moving the VM to another server within the base, base B, or base C.

[0030] The VM migration destination determination device 200 determines the migration destination of the VM based on the cost of the impact degree obtained by the VM migration impact cost calculation device 100.

[0031] (Device configuration) Fig. 6 is a diagram showing an example of the configuration of a VM migration impact cost calculation device 100. As shown in Fig. 6, the VM migration impact cost calculation device 100 includes a login status confirmation unit 110, a process status confirmation unit 120, a resource status confirmation unit 130, an impact determination unit 140, and an impact output unit 150. Note that the "login status confirmation unit 110, process status confirmation unit 120, and resource status confirmation unit 130" may be collectively referred to as a "confirmation unit." Furthermore, the VM migration impact cost calculation device 100 may be referred to as an "impact cost calculation device."

[0032] Furthermore, the VM movement impact cost calculation device 100 includes an inter-VM coupling degree DB (database) 161, an initial process state DB 162, a distance / bandwidth to another base DB 163, a risky process DB 164, a distance / bandwidth between a user and a base DB 165, and a resource impact determination definition threshold DB 166. Examples of use of each DB will be explained as appropriate in Examples 1 to 3. The function of each part is outlined below.

[0033] The login status checking unit 110 acquires information on whether or not a user is accessing (logging in to) each VM. The process status checking unit 120 acquires information on processes running in each VM.

[0034] The resource state checking unit 130 acquires resource information such as memory usage rate, memory IO, etc. of each VM. The acquired resources are not limited to memory usage rate, etc., and it is also possible to acquire CPU usage rate, etc.

[0035] The impact determination unit 140 receives data from one, more than one, or all of the login status confirmation unit 110, the process status confirmation unit 120, and the resource status confirmation unit 130, and calculates the impact cost when a VM is migrated. The impact output unit 150 outputs the impact cost for each VM and each migration destination calculated by the impact determination unit 140. The output impact cost may be displayed on a display or input to the VM migration destination determination device 200.

[0036] Below, Examples 1 to 3 will be described as specific examples of calculation of impact costs by the impact degree determination unit 140. In addition, examples of using the calculated impact costs will be described after Examples 1 to 3. In all of Examples 1 to 3 described below, examples of calculation of impact costs will be described assuming that a VM at base A is moved within the base or to another base, as shown in FIG.

[0037] In the following, an example is shown in which the impact cost based on the inter-VM coupling degree of Example 2 is added to the impact cost of Example 1, and further the impact cost related to the operation impact of Example 3 is added, but this is just one example. It is also possible to use the impact costs of Examples 1, 2, and 3 independently. In addition, it is also possible to use the multiple impact costs (additional amounts) explained in Example 1 independently.

[0038] Example 1 In the first embodiment, an example of calculating an impact cost that takes into account the impact on a user based on the login status, process status, and the distance and bandwidth between the user and each location will be described. The explanation will be given along the steps of the flowchart in FIG.

[0039] <S101:ステップ1> The impact degree determining unit 140 starts the impact cost calculation for VM_X.

[0040] <S102、S103> In S102, the influence degree determining unit 140 checks the login state of VM_X acquired by the login state checking unit 110.

[0041] If no user is logged in (No in S103), VM_X is not being used, so it is determined that there is no impact of VM migration, and the impact cost is set to 0.

[0042] If any user is logged in (Yes in S103), the movement of VM_X may have an impact on the users, so 50 is added to the impact cost. Note that if multiple users can log in to VM_X, the impact cost to be added may be increased as the number of logged-in users increases.

[0043] <S104、S105> In S104, the influence degree determining unit 140 checks the processes running in VM_X based on the process state of VM_X acquired by the process state checking unit 120.

[0044] The initial process state DB 162 stores the process state of each VM when it is not being used by a user. By referring to the initial process state DB 162, if the impact determination unit 140 determines that the only process running in VM_X is the initial process (No in S105), it determines that the user has simply logged in, and does not increase the impact cost. Alternatively, it may increase the cost by a small amount (for example, about 5).

[0045] If the operating process includes a process other than the initial process (Yes in S105), the possibility of affecting one of the users increases, so 50 is added to the impact cost. Note that the numerical values ​​of the impact cost explained in each embodiment are just examples.

[0046] <S106、S107> In S106, the impact determination unit 140 refers to the dangerous process information DB 164, which lists processes that would be problematic if their service were to be down, and checks whether any of the processes listed in the dangerous process information DB 164 is running in VM_X. A process that would be problematic if its service were to be down is, for example, a process that would have an undesirable impact on users if its service were to be down.

[0047] If a dangerous process is not running (No in S107), no addition is made to the impact cost. If a dangerous process is running (Yes in S107), it is determined that the impact will be even higher, and 50 is added to the impact cost for VM_X.

[0048] <s108> In S108, the impact determination unit 140 estimates a change in response speed due to movement when a user accesses VM_X from DB 165 that stores the bandwidth and distance between the user and each location. Note that the following description will be given of a case where one user connects to VM_X. When multiple users connect to VM_X, the average value of the multiple users may be used, or the value of the user with the largest change may be used.

[0049] For example, if moving VM_X from location A to location B doubles the response speed of communications for users connected to VM_X, and moving it from location A to location C halves the response speed, then, for example, 10 is added for the move to location B and 10 is subtracted for the move to location C.

[0050] In the above process, S102 to S107 are impact costs that are not related to the migration destination, and S108 is an impact cost that is related to the migration destination. After S108, the impact cost for the next VM is calculated.

[0051] An example of the calculation results of the impact cost for VM(1) is shown in Figure 7. In this example, the impact cost for movement within the site is 50, the impact cost for movement to site B is 60, and the impact cost for movement to site C is 55.

[0052] The above impact cost is passed to the VM migration destination determination device 200, and the VM migration destination determination device 200 can use the impact cost to determine VM migration, for example, by performing a planned failover if the impact cost is 50 or less.

[0053] Example 2 Next, a description will be given of a second embodiment. In the second embodiment, in addition to the impact cost calculation in the first embodiment, an impact cost is calculated taking into consideration the degree of coupling between VMs. An example of processing in the second embodiment will be described along the steps of the flowchart in FIG.

[0054] <s201> The impact degree determining unit 140 starts the impact cost calculation for a certain VM_X.

[0055] <s202> In S202, the influence degree determining unit 140 executes the processes of S102 to S108 in the first embodiment (FIG. 7).

[0056] <s203> In S203, the impact determination unit 140 refers to the inter-VM coupling DB 161 to calculate the impact cost based on the inter-VM coupling.

[0057] When multiple VMs cooperate with each other (for example, when a large amount of communication between VMs is required to provide a service to a user), if these VMs are located at different locations, the communication distance between the VMs becomes long, and the quality of response to the user deteriorates. Thus, the degree of association (degree of cooperation) between VMs is called inter-VM coupling. Note that "inter-VM" may be between two VMs, or between three or more VMs.

[0058] In this embodiment, for example, for each pair of VMs, an administrator stores the inter-VM coupling degree in advance in the inter-VM coupling degree DB 161. Alternatively, the VM movement impact cost calculation device 100 may periodically acquire traffic between each VM, automatically set the inter-VM coupling degree from the traffic volume, and store it in the inter-VM coupling degree DB 161.

[0059] For example, when there is a lot of traffic between VM1 and VM2, the inter-VM coupling degree between these VMs is set higher than when there is little traffic. As a result, the impact determination unit 140 calculates the impact cost of VM migration in which VM1 and VM2 are located at different locations as higher than when there is little traffic.

[0060] For example, the impact determination unit 140 acquires the inter-VM coupling degree for each combination including VM_X from the inter-VM coupling degree DB 161, calculates an additional impact cost for each VM in the combination based on the inter-VM coupling degree, and adds the additional amount to the calculated impact cost of the VM. This additional amount corresponds to the additional impact cost that would be incurred if the two VMs in the combination were not located at the same site.

[0061] Figure 8 shows an example of impact costs that take into account the inter-VM coupling between VM1 and VM2. For example, consider the case where VM1 and VM2 are moved to base B. The impact costs for VM1 and VM2, assuming that they are not located in the same base, are 65 for each VM1 and VM2, and the sum of these is 130.

[0062] On the other hand, when VM1 and VM2 are moved together to base B, the impact cost based on the inter-VM coupling is subtracted, so that the impact cost for the two becomes 124, for example, as shown in FIG.

[0063] As described above, by taking the degree of VM coupling into consideration, it is possible to control VMs with a high degree of coupling so that they are always located at the same base.

[0064] Example 3 Next, a description will be given of Example 3. In Example 3, in addition to the impact cost calculation of Example 1 or Example 2, an impact cost is calculated taking into account the impact on operations. The description will be given along the steps of the flowchart in FIG.

[0065] <s301> The impact degree determining unit 140 starts the impact cost calculation for a certain VM_X.

[0066] <s302> In S302, the influence degree determining unit 140 executes the processes of S102 to S108 in the first embodiment (FIG. 7) or the processes of S202 to S203 in the second embodiment (FIG. 8).

[0067] <s303> In S303, the influence degree determining unit 140 checks the memory usage rate and memory IO of VM_X acquired by the resource state checking unit .

[0068] <s304> In S304, the impact determination unit 140 acquires the distance and bandwidth between base A and the destination base from DB 163, which stores the distance and bandwidth to other bases for each base, calculates the time required for live migration from base A to the destination base based on the distance, bandwidth, and memory usage rate of VM_X, and sets an impact cost to be added based on that time. The longer the distance and memory usage rate, the longer the time required for live migration. Also, the longer the bandwidth, the shorter the time required for live migration.

[0069] The cost value to be added can be changed flexibly, for example, between -10 and +10.

[0070] The impact determination unit 140 also calculates the impact cost based on the time required to move to another server within the same base. This makes it possible to consolidate VMs into one server, free up another server, and turn off the power to that server.

[0071] In any of the first to third embodiments, the impact cost may be added / subtracted based on the resource status of the server at each base acquired by the resource status confirmation unit 130. For example, a resource amount threshold for adding / subtracting the impact cost is stored in the resource impact determination definition threshold DB 166, and the impact cost is added / subtracted using the threshold.

[0072] As an example, if the CPU usage rate of the server at the destination base exceeds threshold X (e.g., 70%), the impact cost for moving to that base is increased by 10, and if it is below threshold Y (e.g., 20%), the impact cost for moving to that base is decreased by 10. Setting costs in this way makes it possible to control resource usage so that it is equalized between bases.

[0073] (Example of impact cost usage) Here, an example will be described in which migration control is performed using the impact cost calculated by the VM migration impact cost calculation device 100. This control is performed by the VM migration destination determination device 200, for example.

[0074] The following description will be given with reference to Fig. 10. As shown in Fig. 10, it is assumed that VMs 1 to 6 exist at base A, and the VM movement impact cost calculation device 100 calculates the impact cost for each VM when it is moved to base B as shown in the figure. It is also assumed that the power consumption of each VM is as shown in the figure, with VM 1 being the smallest and VM 6 being the largest.

[0075] Here, it is assumed that the VM migration destination determination device 200 determines, from the viewpoint of power consumption, to migrate half of the power consumption of VMs at base A to base B. In this case, the power consumption of "VM1 to VM4" and "VM5 to VM6" will be half, respectively. However, since the total impact cost of VM1 to VM4 is 230 and the total impact cost of VM5 to VM6 is 360, the VM migration destination determination device 200 determines to migrate "VM1 to VM4," which will have a smaller impact due to the migration. Furthermore, by individually considering the cost of the operation impact, it is also possible to perform the migration by live migration when the cost of the operation impact is small, and to perform the migration by planned failover when the cost of the operation impact is large.

[0076] This makes it possible, for example, to migrate VMs while balancing "efficient use of renewable energy" and "maintaining service levels."

[0077] (Example of hardware configuration) Both the VM migration impact cost calculation device 100 and the VM migration destination determination device 200 can be realized, for example, by causing a computer to execute a program. This computer may be a physical computer or a virtual machine on the cloud. The VM migration impact cost calculation device 100 and the VM migration destination determination device 200 are collectively referred to as devices.

[0078] That is, the device can be realized by executing a program corresponding to the processing performed by the device using hardware resources such as a CPU and memory built into a computer. The program can be recorded on a computer-readable recording medium (such as a portable memory) and stored or distributed. The program can also be provided via a network such as the Internet or email.

[0079] Fig. 11 is a diagram showing an example of the hardware configuration of the computer. The computer in Fig. 11 includes a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, and the like, all of which are interconnected via a bus B.

[0080] A program for realizing processing on the computer is provided by a recording medium 1001 such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via a network. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.

[0081] The memory device 1003 reads and stores a program from the auxiliary storage device 1002 when an instruction to start the program is received. The CPU 1004 realizes the functions related to the device in accordance with the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network, etc. The display device 1006 displays a GUI (Graphical User Interface) or the like according to the program. The input device 1007 is composed of a keyboard, mouse, buttons, a touch panel, etc., and is used to input various operation instructions. The output device 1008 outputs the results of calculations.

[0082] (Effects of the embodiment) The technology according to the present embodiment makes it possible to grasp the magnitude of the impact when migrating VMs. Therefore, for example, when a large number of VMs must be migrated to a remote site at once, it becomes possible to determine the VMs to be migrated and the migration method (which VMs to migrate and by which method) so as to minimize the impact.

[0083] (Addendum) This specification discloses at least the impact cost calculation device, impact cost calculation method, and program of the following items. (Section 1) 1. An impact cost calculation device that calculates an impact cost when a virtual machine is migrated within or between multiple locations where virtual machines are installed, comprising: a status confirmation unit that acquires either a login status or a process status, or both the login status and the process status, of each virtual machine provided at the base; an impact determination unit that calculates, for each virtual machine, an impact cost on a user caused by the migration of the virtual machine based on either the login state or the process state, or both the login state and the process state; An impact cost calculation device comprising: (Section 2) The impact degree determination unit increases the impact cost when a process other than the initial process exists among the operating processes of the virtual machine, or increases the impact cost when a process that will affect users when the service is down is running. 2. The impact cost calculation device according to claim 1. (Section 3) The impact degree determination unit calculates an impact cost for each virtual machine at each destination base based on the distance and bandwidth between the user and each base. 3. The impact cost calculation device according to claim 1 or 2. (Section 4) The impact degree determination unit calculates an impact cost for a plurality of virtual machines cooperating with each other based on an inter-virtual machine coupling degree for the plurality of virtual machines. 3. An impact cost calculation device according to claim 1. (Section 5) The impact degree determination unit calculates an impact cost for each virtual machine at each base based on the time required to move the virtual machine between servers within the base and the time required to move the virtual machine between the bases. An impact cost calculation device according to any one of paragraphs 1 to 4. (Section 6) 1. An impact cost calculation method executed by an impact cost calculation device that calculates an impact cost when a virtual machine is moved within or between multiple locations where virtual machines are installed, the method comprising: a state confirmation step of acquiring either a login state or a process state, or both the login state and the process state, for each virtual machine provided at the base; an impact determination step of calculating, for each virtual machine, an impact cost on a user caused by the migration of the virtual machine based on either the login state or the process state, or both the login state and the process state; An impact cost calculation method comprising: (Section 7) A program for causing a computer to function as each part of the impact cost calculation device described in any one of paragraphs 1 to 5.

[0084] Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]

[0085] 100 VM migration impact cost calculation device 110 Login status confirmation section 120 Process status confirmation unit 130 Resource Status Checking Unit 140 Impact Judgment Section 150 Impact output section 161 VM coupling degree DB 162 Initial Process State DB 163 Distance and bandwidth database to other locations 164 Dangerous Process DB 165 Distance and bandwidth DB between users and locations 166 Resource Impact Assessment Definition Threshold DB 200 VM migration destination decision device 300 Network 1000 Drive Device 1001 Recording media 1002 Auxiliary storage device 1003 Memory device 1004 CPU 1005 Interface device 1006 Display device 1007 Input Device 1008 Output Device

Claims

1. 1. An impact cost calculation device that calculates an impact cost when a virtual machine is migrated within or between multiple locations where virtual machines are installed, comprising: a status confirmation unit that acquires either a login status or a process status, or both the login status and the process status, of each virtual machine provided at the base; an impact determination unit that calculates, for each virtual machine, an impact cost on a user caused by the migration of the virtual machine based on either the login state or the process state, or both the login state and the process state; An impact cost calculation device comprising:

2. The impact degree determination unit increases the impact cost when a process other than the initial process exists among the operating processes of the virtual machine, or increases the impact cost when a process that will affect users when the service is down is running. The impact cost calculation device according to claim 1 .

3. The impact degree determination unit calculates an impact cost for each virtual machine at each destination base based on the distance and bandwidth between the user and each base. The impact cost calculation device according to claim 1 or 2.

4. The impact degree determination unit calculates an impact cost for a plurality of virtual machines cooperating with each other based on a predetermined inter-virtual machine coupling degree for the plurality of virtual machines. The impact cost calculation device according to any one of claims 1 to 3.

5. The impact degree determination unit calculates an impact cost for each virtual machine at each base based on the time required to move the virtual machine between servers within the base and the time required to move the virtual machine between the bases.

5. The impact cost calculation device according to claim 1, wherein the impact cost calculation device is a computer program.

6. 1. An impact cost calculation method executed by a computer for calculating an impact cost when a virtual machine is moved within or between multiple locations where virtual machines are installed, the method comprising: a state confirmation step of acquiring either a login state or a process state, or both the login state and the process state, for each virtual machine provided at the base; an impact determination step of calculating, for each virtual machine, an impact cost on a user caused by the migration of the virtual machine based on either the login state or the process state, or both the login state and the process state; An impact cost calculation method comprising:

7. A program for causing a computer to function as each unit in the impact cost calculation device according to any one of claims 1 to 5.

Images