WO2014087545A1

WO2014087545A1 - Virtual machine deployment method and computer system

Info

Publication number: WO2014087545A1
Application number: PCT/JP2012/081846
Authority: WO
Inventors: 成昊金; 崇博大平
Original assignee: 株式会社日立製作所
Priority date: 2012-12-07
Filing date: 2012-12-07
Publication date: 2014-06-12

Abstract

A physical machine that has a hypervisor for running a virtual machine, the physical machine further having: a bandwidth management mechanism for controlling a network bandwidth and transmitting bandwidth usage to a deployment management server; deployment daemon software for receiving an image file for a virtual machine when the virtual machine is deployed, and writing the image file to a disk; and a scheduling mechanism for performing scheduling for the virtual machine and the deployment daemon. A deployment management server for managing the virtual machine image file has a deployment bandwidth control mechanism for controlling the network transmission bandwidth of the image file. The deployment bandwidth control mechanism in the deployment management server controls the network bandwidth.

Description

Virtual machine deployment method and computer system

The present invention relates to a computer system and an information processing method, and more particularly to deployment of a virtual machine.

When virtualizing a mission-critical computer system that requires highly reliable processing and advanced real-time performance (response performance), it is necessary to guarantee the performance of the virtual machine. Usually, performance is secured by allocating sufficient computer resources to a virtual machine. Therefore, deployment for ensuring the performance of the virtual machine is performed. “Deploy” refers to making a component such as software used via a network available. For example, the memory capacity, the disk capacity, and the CPU usage time necessary for the virtual machine are calculated and allocated in advance to guarantee the performance. Patent Document 1 discloses an example of a method of selecting and deploying from a plurality of physical machines a physical machine that can secure the resource amount of the virtual machine 1 when newly deploying the virtual machine to the physical machine. Patent Document 2 discloses an example of a method for predicting a load change of a virtual machine and allocating appropriate computer resources.

JP 2011-198332 A JP 2011-170787 A

For long-term system operation and maintenance, a virtualized environment will be constructed and operated in stages. In other words, when a virtualized system is operating, it is necessary to newly virtualize another system and deploy it to the same physical machine. In such a case, in order to realize another virtual machine on the same physical machine, it is necessary to arrange a large-capacity virtual machine image file on the physical machine. However, when transferring this computer image file using a network, the network bandwidth of the physical machine and virtual machine is temporarily used in large quantities, and the network bandwidth of the physical machine and the virtual machine already running Since a part is used for transferring the image file, there is a problem that the performance is deteriorated.

An object of the present invention is to guarantee the performance of an existing virtual machine when a new virtual machine is deployed.

The computer system according to the present invention is a computer system that includes a physical machine having a hypervisor that operates a virtual machine and a deployment management server that is responsible for deploying the virtual machine that manages the disk image file of the virtual machine.

For physical machines, the bandwidth management mechanism that controls the network bandwidth and sends the bandwidth usage status to the deployment management server, and receives virtual machine image files and writes them to disk when deploying virtual machines A deployment daemon (deploy daemon), a virtual machine, and a schedule mechanism for scheduling the deployment daemon are included. A daemon is a program that operates as a background process. The deployment management server has a deployment bandwidth control mechanism that controls the network transmission bandwidth of the image file.

The bandwidth management mechanism of the physical machine controls the network bandwidth of the virtual machine of the physical machine in consideration of the bandwidth usage status of the virtual machine, and the deployment bandwidth control mechanism of the deployment management server controls the network bandwidth of transferring the virtual machine image file. It is characterized by that.

The present invention is also configured as a deployment method executed by the computer system.

According to the present invention, when deploying a new virtual machine or updating a virtual machine, the deployment process uses a part of the bandwidth of the existing virtual machine as in the past, thereby improving the performance of the existing virtual machine. By preventing the deterioration and controlling the network bandwidth used for deployment and the network bandwidth of the existing virtual machine, it is possible to secure the necessary network bandwidth and guarantee the real-time property of the virtual machine.

It is a figure which shows the structural example of a computer system. It is a flowchart explaining an initialization process. It is a flowchart explaining the bandwidth allocation process for virtual machines. It is a flowchart explaining a band mutual accommodation process. 10 is a flowchart for explaining mutual bandwidth interchange processing during virtual machine image non-transfer. It is a flowchart explaining the band mutual accommodation process during virtual machine image transfer. It is a figure which shows the structural example of a virtual machine zone | band return process. It is a figure which shows the structural example of a virtual machine bandwidth ensuring process. It is a figure which shows the structural example of the band accommodation process to a deployment daemon. It is a figure which shows the structural example of a deployment bandwidth control mechanism process. It is a figure which shows the structural example of a deployment application process. It is a figure which shows the structural example of a deployment daemon process. It is a figure which shows a bandwidth management table. It is a figure which shows a band history table. It is a figure which shows a band accommodation destination table. It is a figure which shows a virtual machine image transfer flag table. It is a figure which shows a deployment bandwidth table. It is a figure which shows a process outline. It is a figure which shows the relationship between the magnitude relationship of a parameter, and each process.

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

This example describes the initialization process and the virtual machine deployment process.

<System configuration>
FIG. 1 shows a configuration of a computer system 10 according to an embodiment.

The computer system 10 includes a physical machine 100 that operates the virtual machine 120 and a deployment management server 200 that performs control for realizing the virtual machine on the physical machine 100. Both the physical machine 100 and the deployment management server 200 are realized by a processing device having a CPU, a memory, an input / output terminal, and a storage device.

The physical machine 100 includes a hypervisor 110, a disk 170 for recording information, and a communication IF 160, and is connected to the deployment management server 200 via a network 260. The hypervisor 110 includes a deployment daemon 130 that receives virtual machine image files from the virtual machines 120 and 121 and the deployment management server 200 and writes them to the disk 170. The hypervisor 110 also schedules the virtual machines 120 and 121, and each virtual machine. A bandwidth management mechanism 150 that manages bandwidth used by the machine and the deployment daemon 130 is provided. The bandwidth management mechanism 150 performs bandwidth status monitoring and exchange of bandwidth (values) between virtual machines, records bandwidth management information used by each virtual machine and the deployment daemon 130 in the bandwidth management table 151, and The bandwidth used by the virtual machine and the deployment daemon 130 is recorded in the bandwidth history table 152. The bandwidth management mechanism 150 controls the bandwidth used by each virtual machine based on the bandwidth management table 151.

The deployment management server 200 stores the virtual machine image file 210 for realizing the virtual machine on the physical machine, the communication IF 240, the deployment bandwidth control mechanism 230 for controlling the network bandwidth, and the disk image file 210 of the virtual machine 120 in the physical machine 100. A deployment application 250 to be transferred and a display 220 for displaying the transfer status of the image file are provided. The deployment bandwidth control mechanism 230 controls the transfer bandwidth of the virtual machine image file 210.

Each of the hypervisor 110 of the physical machine 100 and the deployment bandwidth control mechanism 230 and the deployment application 250 of the deployment management server 200 is realized by software (program), stored in each memory, and executed by the CPU. It is also possible to store these software in a computer-readable storage medium, read the software stored in the storage medium into a memory, and execute it on the CPU.

<Description of each table>
The bandwidth management table 151 shown in FIG. 13 is a table for managing information related to the bandwidth of each virtual machine and deployment daemon. The management target 151a, the bandwidth threshold 151b, the margin value 151c, the accommodation value 151d, and these values Is composed of a band value 151e. The definitions of the threshold value 151b, the margin value 151c, and the accommodation value 151d will be described later.

The bandwidth history table 152 shown in FIG. 14 is a table for managing how much bandwidth each virtual machine or deployment daemon is currently using, and includes a management target 152a and a used bandwidth 152b.

The bandwidth accommodation destination table 153 illustrated in FIG. 15 is a table for managing the correspondence between the virtual machine and the deployment daemon and other virtual machines and deployment daemons that allow bandwidth, the bandwidth accommodation source 153a and the bandwidth accommodation destination. 153b.

The virtual machine image transfer table 154 shown in FIG. 16 is a table for managing the presence / absence of transfer of virtual machine images for each virtual machine. The transfer destination virtual machine 154a and the flag 154b indicating the presence / absence of transfer (if there is transfer) “1”).

The deployment bandwidth table 231 shown in FIG. 17 is a table for managing a bandwidth value to be secured at the time of deployment for each virtual machine, and includes a virtual machine 231a and a deployment bandwidth value 231b.

<Process overview>
Based on FIG. 18, an outline of processing in the physical machine 100 and the deployment management server 200 will be described. Figures in parentheses are related figures.

Physical machine:
(1) Initialization processing (FIG. 2): Virtual machine bandwidth allocation processing (FIG. 3) is performed.

(2) When the bandwidth is a fixed bandwidth, the following processing is not performed and the operation is performed in the fixed bandwidth.

(3) If the bandwidth is a movable bandwidth, the following mutual bandwidth interchange processing (FIG. 4) is repeatedly executed at regular time intervals during operation, and the virtual machine and the deployment are performed based on the magnitude relationship between the bandwidth to be used and the threshold. Flex bandwidth between daemons.

(3-1) When the virtual machine image file is not being transferred (FIG. 5):
The following processing is performed according to whether the bandwidth interchange value of the virtual machine is 0 or more.

(0 or less) Virtual machine bandwidth return processing to return the bandwidth that was otherwise accommodated to itself (FIG. 7)
(0 or more) Virtual machine bandwidth reservation processing to allow extra bandwidth (Figure 8)
(3-2) When a virtual machine image file is being transferred (FIG. 6):
The following processing is performed depending on whether the use bandwidth of the virtual machine is larger than the threshold.

(> Threshold) Virtual machine bandwidth return processing to return the bandwidth that was otherwise accommodated to itself (FIG. 7)
(<Threshold) Bandwidth interchange processing for accommodating the bandwidth required for image file transfer to the deployment daemon (FIG. 9)
Deployment management server:
(1) Control the bandwidth of the deployment daemon (Figure 10)
(2) Transfer virtual machine image file to physical machine based on deployment start command (FIG. 11) → physical machine deployment daemon stores file on disk (FIG. 12)
FIG. 19 is a diagram showing the relationship between the magnitude relationship of the parameters related to the band and each of the above processes.

As will be described later, the processing executed during non-transfer or transfer of a virtual machine image file differs depending on the magnitude relationship between the use bandwidth of the virtual machine and the threshold and the interchange value of the virtual machine is 0 / less. In () of FIG. 19, the numbers of the process flow diagrams described later are shown.

<Initialization processing sequence>
An initialization process sequence in the physical machine 100 of the computer system 10 will be described with reference to FIG.

The initialization processing sequence is configured by each virtual machine bandwidth allocation processing (S301), deployment daemon bandwidth allocation processing (S302 to S305), priority setting processing (S306), and bandwidth value initial setting processing (S307, S308). Is done.

In each virtual machine bandwidth allocation process (S301, which will be described in detail in FIG. 3), on the physical machine 100 in accordance with the requirements of each virtual machine (required processing performance, importance of processing, urgency, etc.) The bandwidth management mechanism 150 allocates a network bandwidth to be used for each virtual machine.

In the deployment daemon bandwidth allocation process (S302), the bandwidth management mechanism 150 initializes the network bandwidth used by the deployment daemon 130 on the physical machine 100. First, a predetermined value is set in the threshold 151b of the deployment daemon 130, and “0” is set in the margin value 151c. The accommodation value 151d of the deployment daemon 130 is set to a value obtained by adding the margin value 151c of each virtual machine in the bandwidth management table 151 to the accommodation value 151d (S302). The margin value 151c of each virtual machine in the bandwidth management table 151 is subtracted from the accommodation value 151d of each virtual machine in the bandwidth management table 151, and the subtraction result is set to the accommodation value 151d of each virtual machine (S303). Further, “deploy daemon” is set in the bandwidth accommodation source of the bandwidth accommodation destination table 153 (S304). The bandwidth management mechanism 150 recalculates the bandwidth value 151e (threshold 151b + margin value 151c + accommodation value 151d) of each virtual machine and deployment daemon, and sets the bandwidth value in the bandwidth management table 151 (S305). The threshold 151b and the margin value 151c are values of the bandwidth possessed by the virtual machine itself, and the accommodation value 151d is a bandwidth value accommodated from another virtual machine.

The priority setting process (S306) for the virtual machine and the deployment daemon will be described. The schedule mechanism 140 that executes the priority setting process controls the execution priority of each virtual machine. This corresponds to a scheduler of a conventional OS, and is a part of the function executed by the hypervisor 110 in this embodiment. In accordance with the requirements of each virtual machine, the scheduling mechanism 140 on the physical machine 100 sets the scheduling priority of each virtual machine. The schedule mechanism 140 sets the priority of the deployment daemon 130 to the lowest level. This is to minimize the influence of the operation of the deployment daemon 130 on each virtual machine and to guarantee the real-time property of the virtual machine 120. Also, regarding the priority of the network packet, the priority of the packet addressed to the deployment daemon 130 is set to the lowest level, and the setting is made so that the packet addressed to each virtual machine is processed with priority.

The bandwidth management mechanism 150 controls the bandwidth of each virtual machine and the deployment daemon according to the bandwidth value 151e of the bandwidth management table 151 (S307). The bandwidth management mechanism 150 transmits the bandwidth value of the deployment daemon to the bandwidth control mechanism of the deployment management server (S308). Steps S307 and S308 are processes for applying each value set in steps S301 to S306 first (before actual operation). Here, “controlling the bandwidth” means setting a bandwidth value in the hypervisor 110 that monitors bandwidth usage or restricts usage. Steps S307 and S308 correspond to the processing of FIG. 9 included in FIG. 4 to be described later.

<Virtual machine bandwidth initialization processing>
With reference to FIG. 3, the details of step S301 of the initialization processing sequence in the physical machine 100 of the computer system 10 will be described.

In the virtual machine bandwidth allocation process (S301), first, before the actual operation, the bandwidth management mechanism 150 on the physical machine 100 allocates a network bandwidth to be used for each virtual machine according to the requirements of the virtual machine. ,initialize.

The bandwidth management mechanism 150 records the threshold value and the margin value of the network bandwidth allocated to each virtual machine in the bandwidth management table 151 (S301-1). When setting the network bandwidth, consider the load caused by interrupts to each virtual machine, and design it to ensure real-time performance. Here, the threshold 151b is a basic value of a virtual machine that is an index for performing processing for obtaining bandwidth from other virtual machines when there is a virtual machine that uses the bandwidth with a value larger than that. This is the value of the bandwidth required for proper operation. Further, the margin value 151c is a margin with respect to a threshold when designing a bandwidth used by the virtual machine, and is also a value at which the virtual machines can accommodate the bandwidth.

The virtual machine accommodation value 151d in the bandwidth management table 151 is initialized with "0" (S301-2). Here, the accommodation value 151 d is a numerical value indicating “a value of a bandwidth accommodated from another virtual machine”. It is set to “0” at the initialization stage. If the value of the accommodation value 151d is negative, it indicates that the bandwidth has been accommodated by another virtual machine.

The bandwidth value 151e of each virtual machine in the bandwidth management table 151 is calculated and recorded as the sum of the threshold value 151b, the margin value 151c, and the accommodation value 151d (S301-3). The bandwidth management mechanism 150 controls the network bandwidth of each virtual machine with the bandwidth value 151e calculated here.

By the above initialization process, not only the threshold value, which is the bandwidth value required for the basic operation of the virtual machine, but also the margin value and the accommodation value that can cope with the fluctuation of the bandwidth during operation are assigned to each virtual machine. The bandwidth to be managed by each virtual machine is determined.

<Operation example with fixed bandwidth>
As an example of the embodiment, an operation example in a fixed band is shown. In operation with a fixed bandwidth, bandwidth is not interchanged between a plurality of virtual machines and between a virtual machine and a deployment daemon. The bandwidth of each virtual machine 120 is controlled by the threshold value 151 b recorded in the bandwidth management table 151. Further, the deployment daemon 130 controls the bandwidth by the sum of the margin values 151c of the virtual machines recorded in the bandwidth management table 151. At this time, the bandwidth history table 152 described in FIG. 1 is not necessary. In addition, the inter-band interchange processing described below is not performed. Therefore, the bandwidth once allocated by other virtual machines during operation does not fluctuate.

<Operation example in movable band>
As an example of the embodiment, an operation example in the movable band is shown. In operation in the movable band, the bandwidth is mutually interchanged between virtual machines or between a virtual machine and a deployment daemon. When each virtual machine and the deployment daemon use a large amount of bandwidth, the virtual machine that does not use the bandwidth very much has the bandwidth interchanged. Thereby, the virtual machine and the deployment daemon can effectively use the bandwidth of the entire system.

For the operation in the movable band, the following mutual bandwidth processing is performed.

<Bandwidth interchange processing>
With reference to FIG. 4, a mutual bandwidth interchange process executed during actual operation in the physical machine 100 of the computer system 10 will be described.

Band mutual interchange processing is performed periodically with a period of, for example, about 1 second while the physical machine 100 is in operation. By repeatedly executing this bandwidth interchange processing during operation, the bandwidth demand of each virtual machine that changes during operation and the appropriate bandwidth allocation according to the temporary transfer of virtual machine image files (between virtual machines) (Band interchange) at any time.

When the bandwidth usage of the virtual machine is small between the virtual machines 120 and 121, or between the deployment daemon 130 and the virtual machines 120 and 121 and there is a margin, the bandwidth interchange processing is performed by other virtual machines. Perform processing to accommodate the bandwidth. As a result, a bandwidth whose total amount is limited can be effectively utilized among a plurality of virtual machines, and a necessary bandwidth can be temporarily allocated from the virtual machine to the deployment daemon 130 when transferring the virtual machine image file.

The bandwidth management mechanism 150 on the physical machine 100 refers to the virtual machine image transfer flag table 154 in FIG. 16 and determines whether the virtual machine image file is being transferred in the virtual machine (S401).

When the virtual machine image is being transferred, the mutual bandwidth interchange process (S402) during the virtual machine image transfer shown in FIG. 6 is performed for each virtual machine. Thereafter, a bandwidth history recording process (S404) is performed.

In the bandwidth history recording process, the bandwidth management mechanism 150 of the physical machine 100 records the bandwidth used by each virtual machine and the deployment daemon in the bandwidth history table 152 of FIG.

If the virtual machine image is not being transferred, the bandwidth mutual interchange processing (S403) during non-transfer of the virtual machine image of FIG. 5 is performed for each virtual machine. Thereafter, a bandwidth history recording process (S404) is performed.

<Band interchange processing during non-transfer of virtual machine images>
With reference to FIG. 5, the mutual bandwidth interchange processing (S403) during the virtual machine image non-transfer in the physical machine 100 of the computer system 10 will be described.

The mutual bandwidth interchange processing during non-transfer of the virtual machine image is processing that is performed when the virtual machine image is not transferred, and the bandwidth is interchanged between the virtual machines. As a result, the bandwidth used by the deployment daemon that transfers virtual machine images can also be used effectively between virtual machines.

帯域 Mutual bandwidth interchange processing during non-transfer of virtual machine images is performed for each virtual machine.

The bandwidth management mechanism 150 of the physical machine 100 determines whether or not the bandwidth used by the virtual machine is less than the threshold 151b with reference to the bandwidth history table 152 (S403-1).

If the bandwidth used by the virtual machine is less than the threshold value 151b, the bandwidth interchange processing during non-transfer of the virtual machine image is terminated.

When the bandwidth used by the virtual machine is equal to or greater than the threshold 151b, the bandwidth management mechanism 150 determines whether or not the accommodation value 151d of the virtual machine is 0 or more with reference to the bandwidth management table 151 (S403). -2).

When the virtual machine accommodation value 151d is 0 or more, the virtual machine bandwidth securing process (S403-4) in FIG. 8 is performed, and the process is terminated.

If the virtual machine accommodation value 151d is not 0 or more, the virtual machine bandwidth return processing (S403-3) in FIG. 7 is performed, and the processing is terminated.

<Virtual machine bandwidth return processing>
With reference to FIG. 7, the virtual machine bandwidth return process (S403-3) in the physical machine 100 of the computer system 10 will be described.

The virtual machine bandwidth return process is a process in which the virtual machine returns itself the bandwidth that has been accommodated by other virtual machines or deployment daemons. As a result, it is possible to cope with a sudden increase in the bandwidth required for processing by returning the bandwidth that has been accommodated elsewhere.

In the virtual machine bandwidth return process, the bandwidth return destination virtual machine is referred to as an interchange source virtual machine.
The bandwidth management mechanism 150 adds and sets its own margin value 151c to the virtual machine accommodation value 151d (S501).

The bandwidth management mechanism 150 refers to the bandwidth accommodation destination table 153 of FIG. 15 to select a virtual machine of the accommodation source 153a, and from the accommodation value 151d of the virtual machine of the accommodation source 153b, the margin value 151c of the accommodation source virtual machine Is subtracted and set again (S502).

The bandwidth management mechanism 150 recalculates and sets the bandwidth value 151e of each virtual machine (S503). Here, the bandwidth value 151e is calculated in the bandwidth management table 151 as the threshold value 151b + the margin value 151c + the accommodation value 151d. The calculated bandwidth value is set in the bandwidth value 151e of the bandwidth management table 151.

The bandwidth management mechanism 150 resets the accommodation destination 153b of the virtual machine of the accommodation source 153a of the bandwidth accommodation destination table 153 (S504).

The bandwidth management mechanism 150 controls the bandwidth of each virtual machine according to the bandwidth value 151e of the bandwidth management table 151 (S505).

The bandwidth management mechanism 150 transmits the bandwidth value 151e of the deployment daemon to the deployment bandwidth control mechanism 230 of the deployment management server 200 (S506).

<Virtual machine bandwidth reservation processing>
With reference to FIG. 8, the virtual machine bandwidth securing process (S403-4) in the physical machine 100 of the computer system 10 will be described.

The virtual machine bandwidth securing process is a process for securing the bandwidth by having the bandwidth required by the virtual machine interchanged from other virtual machines whose used bandwidth is less than the threshold 151b. As a result, it is guaranteed to cope with a sudden increase in bandwidth required for processing.

In the virtual machine bandwidth securing process, a virtual machine that performs the virtual machine bandwidth securing process is referred to as a bandwidth accommodation destination virtual machine.

The bandwidth management mechanism 150 refers to the bandwidth history table 151 and the bandwidth accommodation destination table 153. The bandwidth management mechanism 150 uses less bandwidth than the threshold 151b and does not allow bandwidth to other virtual machines 120 and 121 or the deployment daemon 130. It is determined whether there is a virtual machine (S601).

If the used bandwidth is less than the threshold 151b and there is no virtual machine that does not accommodate the bandwidth, the virtual machine bandwidth securing process is terminated.

When there is a virtual machine that uses less bandwidth than the threshold 151b and does not accommodate the bandwidth, the bandwidth management mechanism 150 uses a virtual machine that uses less bandwidth than the threshold 151b and does not accommodate bandwidth. Among them, the bandwidth history table 152 in FIG. 14 is referred to, and the one having the smallest bandwidth is selected (S602). The virtual machine selected here is referred to as an accommodation source virtual machine.

The bandwidth management mechanism 150 subtracts the accommodation value 151d of the selected accommodation source virtual machine from the accommodation value 151d of the accommodation source virtual machine selected in step S602, and sets it in the bandwidth management table 151 (S603).

The bandwidth management mechanism 150 adds and sets the margin value 151c of the accommodation source virtual machine selected in step S602 to the accommodation value 151d of the bandwidth accommodation destination virtual machine (S604).

The bandwidth management mechanism 150 sets the accommodation destination virtual machine in the item 153a of the accommodation source virtual machine selected in the process of step S602 in the bandwidth accommodation destination table 153 (S605).

<Band interchange processing during virtual machine image transfer>
With reference to FIG. 6, the mutual bandwidth interchange process (S402) during virtual machine image transfer in the physical machine 100 of the computer system 10 will be described. This process is a process for accommodating the bandwidth to the deployment daemon 130 if the virtual machine has a sufficient bandwidth. As a result, the deployment daemon 130 can transfer the virtual machine image file without affecting the operation of the virtual machine having a sufficient bandwidth.

The bandwidth management mechanism 150 of the physical machine 100 determines whether or not the bandwidth used by the virtual machine is less than the threshold 151b with reference to the bandwidth history table 152 (S402-1).

If the bandwidth used by the virtual machine is less than the threshold 151b, the bandwidth interchange processing (S402-4) to the deployment daemon 130 of FIG. 9 is performed, and the bandwidth mutual interchange processing during the virtual machine image transfer is terminated.

If the bandwidth used by the virtual machine is equal to or greater than the threshold 151b, the bandwidth management mechanism 150 determines whether or not the accommodation value 151d of the virtual machine is 0 or more with reference to the bandwidth management table 151 (S402-). 2).

When the virtual machine accommodation value 151d is 0 or more, the bandwidth mutual accommodation processing during the virtual machine image transfer ends.

<Band interchange processing to deployment daemon>
With reference to FIG. 9, the bandwidth accommodation processing (S402-4) to the deployment daemon during the virtual machine image transfer in the physical machine 100 of the computer system 10 will be described.

The bandwidth accommodation processing to the deployment daemon 130 is processing for accommodating bandwidth to the deployment daemon 130 when the bandwidth usage of the virtual machine is small and there is room. As a result, since the bandwidth is accommodated from the spare virtual machine to the deployment daemon 130, it is not necessary to increase the bandwidth of the entire system for transferring the virtual machine image file.

The bandwidth management mechanism 150 refers to the bandwidth management table 151, and subtracts its own margin value 151c from the virtual machine accommodation value 151d (S701).

The bandwidth management mechanism 150 adds the margin value 151c of the virtual machine to the accommodation value 151d of the deployment daemon 130 and resets the setting (S702).

The bandwidth management mechanism 150 sets a deployment daemon in the virtual machine accommodation destination 153b of the bandwidth accommodation destination table 153 (S703).

The bandwidth management mechanism 150 controls the bandwidth of each of the virtual machines 120 and 121 and the deployment daemon 130 according to the bandwidth value 151e of the bandwidth management table (S704).

The bandwidth management mechanism 150 transmits the bandwidth value 151e of the deployment daemon to the deployment bandwidth control mechanism 230 of the deployment management server 200 (S705).
The deployment bandwidth control mechanism 230 of the deployment management server 200 controls the transfer bandwidth of the virtual machine image file with the bandwidth value 151e of the deployment daemon received from the bandwidth management mechanism 150 (S706).

<Deployment bandwidth control mechanism processing>
The deployment bandwidth control mechanism process 230 in the deployment management server 200 of the computer system 10 will be described with reference to FIG.

The deployment bandwidth control mechanism process is a process performed by the deployment bandwidth control mechanism 230 of the deployment management server 200 to control the bandwidth of the deployment daemon 130. Since the bandwidth of the deployment daemon 130 is controlled by the bandwidth obtained as a result of the bandwidth interchange between the virtual machines in the physical machine 100, the operation of the virtual machine is not affected.

It is determined whether a packet for setting a bandwidth value has arrived from the bandwidth management mechanism 150 of the physical machine (S801).

If the packet has not arrived, return to the start of processing.

When the packet has arrived, the deployment bandwidth control mechanism 230 records the bandwidth value 151e of the deployment daemon 130 received from the bandwidth management mechanism 150 of the physical machine 100 in the deployment bandwidth table 231 of FIG. 17 (S802).

The deployment bandwidth control mechanism 230 controls the bandwidth of the deployment application 250 with the deployment bandwidth value 231b of the deployment bandwidth table 231 (S803).

<Deploy application processing>
With reference to FIG. 11, the deployment application processing 250 in the deployment management server 200 of the computer system 10 will be described.

The deploy application process is a process for the deploy application 250 of the deployment management server 200 to transfer the virtual machine file image 210 to the physical server 100. The deployment management server 200 collectively manages various virtual machine file images 210 and provides them to each of the virtual machines, thereby eliminating the need for the physical machine 100 to prepare various virtual machine file images 210.

Judge whether a deployment start command has been issued by the user. (S901).

If the deployment start command has not been issued, return to the start of processing.

When the deployment start command is issued, the deployment application 250 starts transferring the virtual machine image file 210 to the deployment daemon 130 of the physical machine 100 (S902).

It is determined whether the transfer of the virtual machine image file 210 is completed (S903).

If the transfer ends, the process ends.

If the transfer has not been completed, the deployment application 250 calculates the transfer completion time by dividing the remaining transfer amount of the virtual machine image file 210 by the current use bandwidth, and displays it on the display 220 (S904). Return to the virtual machine image file transfer determination process.

<Deploy daemon processing>
The deployment daemon process in the physical machine 100 of the computer system 10 will be described with reference to FIG.

The deployment daemon process is a process in which the physical machine deployment daemon 130 receives a virtual machine image file from the deployment application 250 of the deployment management server 200 and writes it to the disk 170. By writing the virtual machine image file transmitted from the deployment management server 200 to the disk 170, the virtual machine image file can be shared between the virtual machines, and the virtual machine image used by one virtual machine can be re-used by another virtual machine. It can be used, and the transfer of the virtual machine image file between the deployment management server 200 and the physical machine 100 and the bandwidth interchange processing associated with the transfer can be omitted.

It is determined whether the virtual machine image file 210 is sent from the deployment application 250 of the deployment management server 200 (S1001).

If no file has been sent, “0” is recorded in the flag 154b of the transfer flag table 154 in FIG. 16 (S1002).

If the file has been sent, the deployment daemon 130 writes the received virtual machine image file 210 to the disk 170 (S1003).

The deploy daemon 130 records “1” in the flag 154b of the transfer flag table 154 (S1004).

<Extensibility of computer system>
The example in the case where there is one physical machine 100 in the computer system 10 has been described above, but the number of physical machines is not limited to one. In addition, although an example in which there are two virtual machines 120 and 121 operating on the physical machine 100 has been described, the number of virtual machines is not limited to two. By appropriately configuring the network 260 that connects the physical machine 100 and the deployment management server 200 as in the case of a single machine, the network system can be expanded to a computer system including two or more physical machines 100.

In this embodiment, the virtual machine image file is transferred from the deployment management server 200, but the virtual machine image file can also be transferred from an external medium such as a DVD to the deployment daemon 130.

In this example, the method for preventing interference with physical machines and existing virtual machines has been described with special reference to virtual machine deployment. However, not only for deployment, but also for migration and backup of virtual machines. Example forms can be applied.

As mentioned above, although one embodiment has been described, the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the invention.

10: computer system, 100: physical machine, 110: hypervisor, 120: virtual machine 1, 121: virtual machine 2, 130: deployment daemon, 140: schedule mechanism, 150: bandwidth management mechanism, 151: bandwidth management table, 152 : Bandwidth history table, 153: bandwidth accommodation table, 160, 240: communication IF, 170: disk, 200: deployment management server, 210: virtual machine image file, 220: display, 230: deployment bandwidth control mechanism, 260: network

Claims

A virtual machine deployment method in a computer system in which a physical machine that operates a plurality of virtual machines and a deployment management server that controls the physical machine to realize the virtual machine are connected via a network. Machine
For each of the plurality of virtual machines, an initial value of a band-related value including a threshold value that is a band value required for basic operation of the virtual machine is set.
Based on the magnitude relationship between the bandwidth used by the virtual machine and the threshold at regular time intervals, the virtual machine and a virtual machine image file for realizing the virtual machine on the physical machine are obtained from the deployment management server. Perform mutual bandwidth interchange processing to allow bandwidth interchange with the receiving deployment daemon.
A virtual machine deployment method characterized by that.
The band mutual accommodation processing is:
When the virtual machine image file is not being transferred, a first bandwidth mutual interchange process is performed in which bandwidths are mutually interchanged between the virtual machines,
If the virtual machine image file is being transferred, if there is a margin in the virtual machine bandwidth, perform a second bandwidth mutual accommodation process to accommodate the bandwidth to the deployment daemon,
Record the bandwidth used by each of the plurality of virtual machines and the deployment daemon after the first or second bandwidth interchange processing.
The virtual machine deployment method according to claim 1.
The first inter-band interchange process is:
When the virtual machine image file is not being transferred, an accommodation value included in the value related to the bandwidth, which is a bandwidth value accommodated from another virtual machine, is not 0 or more,
Perform the virtual machine bandwidth return processing to return the bandwidth that has been accommodated to other virtual machines to your virtual machine,
If the accommodation value is 0 or more,
Based on a margin value that is a margin with respect to the threshold value, a virtual machine bandwidth securing process is performed in which the bandwidth is accommodated from another virtual machine having a margin,
The virtual machine deployment method according to claim 2.
The bandwidth securing process is characterized in that the margin value received from a virtual machine that uses less bandwidth than the threshold and does not accommodate any other bandwidth is added to the accommodation value of the virtual machine. Item 4. The virtual machine deployment method according to Item 3.
The second interband interchange process is:
If the bandwidth used by the virtual machine is greater than the threshold,
Perform the virtual machine bandwidth return processing to return the bandwidth that has been accommodated to other virtual machines to your virtual machine,
If the bandwidth used by the virtual machine is not greater than the threshold,
Performing bandwidth accommodation processing for accommodating the bandwidth necessary for transferring the virtual image file to the deployment daemon;
The virtual machine deployment method according to claim 2.
In the bandwidth accommodation process, the margin value subtracted from the accommodation value of the virtual machine is added to the accommodation value of the deployment daemon and reset,
Sending the bandwidth value that is the sum of the threshold value, the margin value, and the accommodation value to the deployment management server,
Setting the bandwidth value in a bandwidth management table of the virtual machine and the deployment daemon;
The virtual machine deployment method according to claim 5.
The virtual machine bandwidth return process adds the margin value to the accommodation value of the virtual machine,
6. The virtual machine deployment method according to claim 3, wherein the margin value of the virtual machine is subtracted from the flexibility value of the selected virtual machine or the deployment daemon.
A physical machine that runs multiple virtual machines;
A deployment management server that performs control for realizing the virtual machine on the physical machine;
A network connecting the physical machine and the deployment management server;
The physical machine is
An initialization processing means for setting an initial value of a bandwidth-related value, including a threshold value that is a bandwidth value necessary for basic operation of the virtual machine, for each of the plurality of virtual machines; A deployment daemon that receives, from the deployment management server, a virtual machine image file for realizing the virtual machine on the physical machine based on a magnitude relationship between a bandwidth used by the virtual machine and the threshold value. Having bandwidth mutual accommodation means for accommodating bandwidth between
A computer system characterized by that.
The band mutual interchange means is:
When the virtual machine image file is not being transferred, a first bandwidth mutual interchange process is performed in which bandwidths are mutually interchanged between the virtual machines,
If the virtual machine image file is being transferred, if there is a margin in the virtual machine bandwidth, perform a second bandwidth mutual accommodation process to accommodate the bandwidth to the deployment daemon,
Record the bandwidth used by each of the plurality of virtual machines and the deployment daemon after the first or second bandwidth interchange processing.
The computer system according to claim 8.
The first inter-band interchange process is:
When the virtual machine image file is not being transferred, an accommodation value included in the value related to the bandwidth, which is a bandwidth value accommodated from another virtual machine, is not 0 or more,
Perform the virtual machine bandwidth return processing to return the bandwidth that has been accommodated to other virtual machines to your virtual machine,
If the accommodation value is 0 or more,
Based on a margin value that is a margin with respect to the threshold value, a virtual machine bandwidth securing process is performed in which the bandwidth is accommodated from another virtual machine having a margin,
The computer system according to claim 9.
The second interband interchange process is:
If the bandwidth used by the virtual machine is greater than the threshold,
Perform the virtual machine bandwidth return processing to return the bandwidth that has been accommodated to other virtual machines to your virtual machine,
If the bandwidth used by the virtual machine is not greater than the threshold,
Performing bandwidth accommodation processing for accommodating the bandwidth necessary for transferring the virtual image file to the deployment daemon;
The computer system according to claim 9.
In the bandwidth accommodation process, the margin value subtracted from the accommodation value of the virtual machine is added to the accommodation value of the deployment daemon and reset,
Sending the bandwidth value that is the sum of the threshold value, the margin value, and the accommodation value to the deployment management server,
Setting the bandwidth value in a bandwidth management table of the virtual machine and the deployment daemon;
The computer system according to claim 11, wherein:
A virtual machine deployment method in a computer system in which a physical machine that operates a plurality of virtual machines and a deployment management server that performs control for realizing the virtual machine by the physical machine are connected via a network, The physical machine
For each of the plurality of virtual machines, an initial value of a band-related value including a threshold value that is a band value required for basic operation of the virtual machine is set.
A virtual machine deployment characterized by controlling a bandwidth of each of the plurality of virtual machines and a bandwidth of a deployment daemon that receives a virtual machine image file from the deployment management server based on an initial value of the set bandwidth value. Method.
When setting the initial value,
A bandwidth is allocated to each of the plurality of virtual machines;
Allocate bandwidth to the deployment daemon,
Set priorities according to the requirements of the plurality of virtual machines, set the lowest priority to the deployment daemon,
Set the allocated bandwidth for each of the plurality of virtual machines,
Sending the bandwidth value assigned to the deployment daemon to the deployment management server;
The virtual machine deployment method according to claim 13.
When allocating bandwidth to each of the plurality of physical machines,
A bandwidth value that is a sum of a threshold value that is a bandwidth value necessary for basic operation of the virtual machine, a margin value that is a margin for the threshold value, and an accommodation value that is a bandwidth value accommodated from other virtual machines. The virtual machine deployment method according to claim 14, wherein the virtual machine deployment method is set for each of the plurality of virtual machines.