WO2014087545A1 - Procédé de déploiement de machine virtuelle, et système de calculateur - Google Patents

Procédé de déploiement de machine virtuelle, et système de calculateur Download PDF

Info

Publication number
WO2014087545A1
WO2014087545A1 PCT/JP2012/081846 JP2012081846W WO2014087545A1 WO 2014087545 A1 WO2014087545 A1 WO 2014087545A1 JP 2012081846 W JP2012081846 W JP 2012081846W WO 2014087545 A1 WO2014087545 A1 WO 2014087545A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
virtual machine
value
deployment
virtual
Prior art date
Application number
PCT/JP2012/081846
Other languages
English (en)
Japanese (ja)
Inventor
成昊 金
崇博 大平
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2012/081846 priority Critical patent/WO2014087545A1/fr
Publication of WO2014087545A1 publication Critical patent/WO2014087545A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances

Definitions

  • the present invention relates to a computer system and an information processing method, and more particularly to deployment of a virtual machine.
  • 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.
  • a virtualized environment will be constructed and operated in stages.
  • a virtualized system when a virtualized system is operating, it is necessary to newly virtualize another system and deploy it to the same physical machine.
  • 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.
  • 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 deployment daemon
  • 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.
  • the deployment process when deploying a new virtual machine or updating a virtual machine, uses a part of the bandwidth of the existing virtual machine as in the past, thereby improving the performance of the existing virtual machine.
  • 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.
  • FIG. 1 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.
  • This example describes the initialization process and the virtual machine deployment process.
  • 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.
  • 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 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.
  • FIG. 2 Initialization processing (FIG. 2): Virtual machine bandwidth allocation processing (FIG. 3) is performed.
  • 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.
  • FIG. 6 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.
  • 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.
  • 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.
  • the numbers of the process flow diagrams described later are shown.
  • 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.
  • the bandwidth management mechanism 150 allocates a network bandwidth to be used for each virtual machine.
  • the bandwidth management mechanism 150 initializes the network bandwidth used by the deployment daemon 130 on the physical machine 100.
  • 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).
  • “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.
  • 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.
  • 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).
  • “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.
  • step S301 of the initialization processing sequence in the physical machine 100 of the computer system 10 will be described.
  • 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).
  • 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.
  • 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).
  • 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.
  • the threshold value which is the bandwidth value required for the basic operation of the virtual machine
  • 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.
  • 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.
  • 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.
  • the bandwidth history table 152 described in FIG. 1 is not necessary.
  • 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.
  • the bandwidth is mutually interchanged between virtual machines or between a virtual machine and a deployment daemon.
  • 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.
  • 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.
  • the bandwidth interchange processing is performed by other virtual machines. Perform processing to accommodate the bandwidth.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • the bandwidth used by the deployment daemon that transfers virtual machine images can also be used effectively between virtual machines.
  • 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).
  • the bandwidth interchange processing during non-transfer of the virtual machine image is terminated.
  • 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).
  • the virtual machine bandwidth securing process (S403-4) in FIG. 8 is performed, and the process is terminated.
  • the virtual machine bandwidth return processing (S403-3) in FIG. 7 is performed, and the processing is terminated.
  • 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.
  • 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).
  • 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).
  • 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.
  • 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).
  • the virtual machine bandwidth securing process is terminated.
  • the bandwidth management mechanism 150 uses a virtual machine that uses less bandwidth than the threshold 151b and does not accommodate bandwidth.
  • 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).
  • 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).
  • 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.
  • 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).
  • the bandwidth mutual accommodation processing during the virtual machine image transfer ends.
  • the virtual machine bandwidth return processing (S403-3) in FIG. 7 is performed, and the processing is terminated.
  • 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).
  • 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.
  • 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).
  • 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.
  • the deployment application 250 starts transferring the virtual machine image file 210 to the deployment daemon 130 of the physical machine 100 (S902).
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'objet de l'invention possède : un mécanisme de gestion de bande qui commande une bande de réseau dans une machine physique possédant un hyperviseur faisant fonctionner une machine virtuelle, et envoie un état d'utilisation de bande à un serveur de gestion de déploiement ; un logiciel démon de déploiement qui reçoit un fichier image de la machine virtuelle lors du déploiement de cette dernière, et qui l'exporte sur un disque ; et un mécanisme de planification qui planifie la machine virtuelle et un démon de déploiement. Un mécanisme de commande de bande de déploiement qui commande une bande d'envoi de réseau du fichier image, est présent dans le serveur de gestion de déploiement gérant le fichier image de la machine virtuelle. Ce mécanisme de commande de bande de déploiement du serveur de gestion de déploiement, commande la bande de réseau.
PCT/JP2012/081846 2012-12-07 2012-12-07 Procédé de déploiement de machine virtuelle, et système de calculateur WO2014087545A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/081846 WO2014087545A1 (fr) 2012-12-07 2012-12-07 Procédé de déploiement de machine virtuelle, et système de calculateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/081846 WO2014087545A1 (fr) 2012-12-07 2012-12-07 Procédé de déploiement de machine virtuelle, et système de calculateur

Publications (1)

Publication Number Publication Date
WO2014087545A1 true WO2014087545A1 (fr) 2014-06-12

Family

ID=50882989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/081846 WO2014087545A1 (fr) 2012-12-07 2012-12-07 Procédé de déploiement de machine virtuelle, et système de calculateur

Country Status (1)

Country Link
WO (1) WO2014087545A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003157177A (ja) * 2001-11-22 2003-05-30 Hitachi Ltd 仮想計算機システム及びプログラム
JP2005115653A (ja) * 2003-10-08 2005-04-28 Ntt Data Corp 仮想マシン管理装置及びプログラム
JP2005191688A (ja) * 2003-12-24 2005-07-14 Hitachi Software Eng Co Ltd 通信帯域貸借システム
JP2006166297A (ja) * 2004-12-10 2006-06-22 Fumio Kobayashi 通信帯域制御装置、通信帯域制御方法及びプログラム
JP2007316724A (ja) * 2006-05-23 2007-12-06 Hitachi Ltd 計算機システム、管理計算機及びプログラム配布方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003157177A (ja) * 2001-11-22 2003-05-30 Hitachi Ltd 仮想計算機システム及びプログラム
JP2005115653A (ja) * 2003-10-08 2005-04-28 Ntt Data Corp 仮想マシン管理装置及びプログラム
JP2005191688A (ja) * 2003-12-24 2005-07-14 Hitachi Software Eng Co Ltd 通信帯域貸借システム
JP2006166297A (ja) * 2004-12-10 2006-06-22 Fumio Kobayashi 通信帯域制御装置、通信帯域制御方法及びプログラム
JP2007316724A (ja) * 2006-05-23 2007-12-06 Hitachi Ltd 計算機システム、管理計算機及びプログラム配布方法

Similar Documents

Publication Publication Date Title
US10572290B2 (en) Method and apparatus for allocating a physical resource to a virtual machine
EP3270289B1 (fr) Infrastructure de calcul à plusieurs détenteurs basée sur des conteneurs
KR102281739B1 (ko) 리소스 스케줄링 방법, 스케줄링 서버, 클라우드 컴퓨팅 시스템, 및 저장 매체
JP6190969B2 (ja) マルチテナントリソース調停方法
EP3553657A1 (fr) Procédé et dispositif permettant d'attribuer une tâche de système distribué
US9069465B2 (en) Computer system, management method of computer resource and program
US20130339956A1 (en) Computer system and optimal arrangement method of virtual machine in computer system
US11755369B2 (en) Techniques for container scheduling in a virtual environment
WO2017179537A1 (fr) Dispositif de commande de mise à jour de logiciel, système de commande de mise à jour de logiciel, procédé de commande de mise à jour de logiciel et support d'enregistrement sur lequel est stocké un programme de commande de mise à jour de logiciel
WO2019056771A1 (fr) Procédé et dispositif de gestion de mise à niveau de système de mémoire partagée, et système de mémoire partagée
JPWO2015087442A1 (ja) ストレージシステムの移行方式および移行方法
CN113382077B (zh) 微服务调度方法、装置、计算机设备和存储介质
CN109992373B (zh) 资源调度方法、信息管理方法和装置及任务部署系统
JP6010975B2 (ja) ジョブ管理装置、ジョブ管理方法、及びプログラム
JP2012181578A (ja) 更新制御装置及びプログラム
CN114489517B (zh) 一种离线加速迁移方法、系统、设备及存储介质
CN116881012A (zh) 一种容器应用垂直扩容方法、装置、设备及可读存储介质
WO2014087545A1 (fr) Procédé de déploiement de machine virtuelle, et système de calculateur
JP6191361B2 (ja) 情報処理システム、情報処理システムの制御方法及び制御プログラム
WO2020022018A1 (fr) Dispositif d'attribution de ressources, système d'attribution de ressources et programme d'attribution de ressources
JP6836536B2 (ja) ストレージシステム及びｉｏ処理の制御方法
WO2018173300A1 (fr) Procédé de commande d'e/s et système de commande d'e/s
JP2016062535A (ja) 情報処理システム、情報処理システムの制御方法及び制御プログラム
US20240061698A1 (en) Managing the assignment of virtual machines to non-uniform memory access nodes
JP6235973B2 (ja) サーバ

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12889684

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12889684

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP