JP2016009341A - Virtual machine arrangement system and arrangement method, and computer program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an arrangement device with which it is possible to suppress the congestion of a network when arranging a large-scale system configured by a large number of virtual machines across the network.SOLUTION: An arrangement device according to the present invention has: configuration determination means for deriving, on the basis of physical server configuration information indicting the configuration of each virtual machine arranged in the same server device and the configuration of modules that each virtual machine includes, a common configuration including at least modules common to each virtual machine, and outputting common configuration information indicating the common configuration; VM image generation means for generating, on the basis of the common configuration information, a VM image that includes at least the common modules without including any duplicate thereof; arrangement information generation means for generating, on the basis of the common configuration information and the physical server configuration information, arrangement information including the information that is needed when arranging the VM image; and a delivery control unit for transmitting the VM image, the physical server configuration information, and the arrangement information to the server device.

Description

  The present invention relates to a technology for improving the efficiency of virtual machine deployment.

  There is known a method of deploying a large-scale system constituted by a plurality of virtual machines (Virtual Machines, VMs) over a network. In such a method, when there are a large number of virtual machines to be deployed, VM images related to the respective virtual machines, installation images of software components to be deployed, and the like flow through a network in large quantities. As a result, network congestion is likely to occur, and there is a problem that it takes time to complete the deployment of all VMs.

  For such a problem, Patent Document 1 discloses a method for managing remote deployment of virtual machines in a network environment. In the method described in Patent Document 1, distribution segments are limited by holding VM images hierarchically as in an existing content delivery network (CDN). That is, this method can reduce a network load by not flowing a VM image to an unnecessary segment.

  Patent Document 2 discloses a virtual computer providing system that provides a new virtual computer according to a user's request based on an existing virtual computer. In the system described in Patent Literature 2, a virtual machine provision service management server device creates a new virtual machine by duplicating an existing virtual machine. Then, the virtual machine provision service management server device initializes the environment of the replicated virtual machine based on various management information, and then provides the environment to the user, thereby saving the user's setup effort. Can do.

  Patent Document 3 discloses a method for deploying (deploying) OSs of a plurality of virtual machines. In the method described in Patent Document 3, the management server or the virtual machine performs a duplication process of transferring a duplication of the image file of the virtual machine to another virtual machine in order in a plurality of virtual machines. That is, in this method, a plurality of duplication processes are sequentially executed one by one so as not to be performed simultaneously in parallel, thereby preventing the duplication process from causing network congestion.

JP 2011-123891 A WO2013 / 035134 JP 2011-238132 A

  However, when deploying and constructing a large-scale system including a large number of virtual machines, the method disclosed in Patent Document 1 cannot prevent network congestion due to transfer of VM images within the same segment. That is, in order to obtain the effect of reducing the total amount of VM images flowing through the network by this method, there is a problem that it is necessary to construct a network having a complex isolated segment.

  Also in the system disclosed in Patent Document 2, when a large-scale system including a plurality of virtual machines is a deployment target, a large amount of VM images cannot be avoided flowing through the network. This is because the system disclosed in Patent Document 2 is intended to provide a single VM environment, and thus is not sufficiently effective in reducing the transfer amount when providing a plurality of VM environments.

  Further, the method disclosed in Patent Document 3 has a problem that it takes time to complete deployment of a large number of virtual machines. The reason is that the duplication processing is simply executed one by one without reducing the total amount of data flowing through the network in duplication of the VM image.

  One object of the present invention is to provide a deployment device that can suppress the occurrence of network congestion when a large-scale system composed of a large number of virtual machines is deployed over a network.

  In order to achieve the above object, a deployment device according to an aspect of the present invention is characterized by including the following configuration.

That is, the deployment device according to one aspect of the present invention is
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Configuration determining means for deriving a configuration and outputting common configuration information representing the common configuration;
VM image generation means for generating a VM image including at least the common software module without duplication based on the common configuration information;
Deployment information generating means for generating deployment information including information necessary for deploying the VM image based on the common configuration information and the physical server configuration information;
A distribution control unit that transmits the VM image, the physical server configuration information, and the deployment information to the server device.

In order to achieve the above object, a deployment method according to one aspect of the present invention is performed by an information processing apparatus.
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Deriving the configuration
Generating common configuration information representing the common configuration;
Generating a VM image including at least the common software module without duplication based on the common configuration information;
Based on the common configuration information and the physical server configuration information, generate deployment information including information necessary for deploying the VM image,
Transmitting the VM image, the physical server configuration information, and the deployment information to the server device;
In the server device,
Receiving the VM image, the physical server configuration information, and the deployment information;
Duplicating the VM image according to the number of virtual machines deployed on the server device, obtained based on the physical server configuration information,
A software module is deployed to each replicated VM image using the deployment information so that the configuration of the virtual machine described in the physical server configuration information is obtained.

  The object can also be achieved by a deployment apparatus having the above-described configurations and a corresponding method by a computer program for realizing the method by a computer, and a computer-readable storage medium storing the computer program. Is done.

  The present invention has an effect that it is possible to suppress network congestion associated with a large amount of VM image transfer in the deployment of a large-scale system composed of a large number of virtual machines.

It is a block diagram which shows the structure of the deployment system which concerns on the 1st Embodiment of this invention. It is a block diagram which shows the structure of the deployment system which concerns on the 2nd Embodiment of this invention. It is a figure which shows the system configuration information 300 which is an example of the system configuration information 111 in 2nd Embodiment. It is a flowchart which shows the outline of the operation | movement which the deployment apparatus 100 and the server apparatus 200 perform in 2nd Embodiment. It is a figure which shows the concept of the physical server structure information in 2nd Embodiment, the minimum coverage structure, and the maximum common structure. It is a conceptual diagram which shows the structure procedure of the virtual machine using the minimum coverage structure in the server apparatus 200 which concerns on 2nd Embodiment. It is a conceptual diagram which shows the structure procedure of the virtual machine using the largest common structure in the server apparatus 200 which concerns on 2nd Embodiment. It is a flowchart which shows the operation | movement at the time of the structure determination part 102 which concerns on 2nd Embodiment determines a delivery structure. It is a figure which shows an example of the deployment script component 500 in 2nd Embodiment. It is a flowchart which shows the operation | movement at the time of producing | generating the minimum coverage structure information which the structure determination part 102 in 2nd Embodiment performs. It is a flowchart which shows the operation | movement at the time of producing | generating the largest common structure information which the structure determination part 102 in 2nd Embodiment performs. It is a flowchart which shows the operation | movement at the time of producing | generating the VM image which the VM image production | generation part 103 in 2nd Embodiment performs. It is a flowchart which shows the operation | movement at the time of deploying the virtual machine which the agent 210 in 2nd Embodiment performs. It is a figure which shows an example of the system configuration information 350 in 3rd Embodiment. It is a flowchart which shows the operation | movement at the time of deploying the virtual machine which the agent 210 in 3rd Embodiment performs. It is a figure which illustrates the structure of the computer (information processing apparatus) applicable to each embodiment of this invention and the deployment system which concerns on the modification.

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

<First Embodiment>
FIG. 1 is a block diagram showing a configuration of a deployment system according to the first embodiment of the present invention. Referring to FIG. 1, the deployment system according to the present embodiment includes a deployment device 1 and a server device 10. The server device 10 is a physical server (host) that is a deployment destination of a plurality of virtual machines.

  The deployment apparatus 1 and the server apparatus 10 can communicate via a communication network (hereinafter simply referred to as a network) such as the Internet or a local area network (LAN).

  The deployment device 1 and the server device 10 are configured by a general information processing device (computer) that operates under control of a computer program (software program) that is executed using a CPU (Central Processing Unit: not shown). May be. Or each part of the deployment apparatus 1 and the server apparatus 10 may be comprised by a dedicated hardware device or a logic circuit. A hardware configuration example in which the deployment device 1 and the server device 10 are realized by a computer will be described later with reference to FIG.

  The deployment device 1 includes a configuration determination unit 2, a virtual machine (VM) image generation unit 3, a deployment information generation unit 4, and a distribution control unit 5.

  The configuration determination unit 2 can derive a common configuration including at least a software module (hereinafter also simply referred to as “module”) common to each virtual machine based on the physical server configuration information 20 for the server device 10. The physical server configuration information 20 is information representing the configuration of each virtual machine deployed on the same server device 10 and the configuration of software modules included in each virtual machine. The common configuration is a configuration of a VM image distributed to the server device 10. Note that the common configuration may include modules that are not common to all virtual machines but are deployed to some virtual machines. The configuration determination unit 2 outputs common configuration information representing the derived common configuration to the VM image generation unit 3 and the deployment information generation unit 4.

  Based on the common configuration information received from the configuration determination unit 2, the VM image generation unit 3 can generate a VM image including at least common modules without duplication. For example, the VM image generation unit 3 generates a VM image that includes modules included in the common configuration information one by one.

  The deployment information generation unit 4 includes information necessary for deploying the VM image generated by the VM image generation unit 3 based on the common configuration information received from the configuration determination unit 2 and the physical server configuration information 20. Information can be generated. In other words, the deployment information includes information necessary when the module deployment unit 12 described later sets a VM image so that the final virtual machine configuration described in the physical server configuration information 20 is obtained. Details of the deployment information will be described later in the description of the module deployment unit 12.

  The distribution control unit 5 sends the VM image generated by the VM image generation unit 3, the physical server configuration information 20 given to the configuration determination unit 2, and the deployment information generated by the deployment information generation unit 4 to the server device 10. Can be sent.

  The server device 10 includes a virtual machine (VM) image copying unit 11 and a module deployment unit 12.

  The VM image duplicating unit 11 receives the VM image, the physical server configuration information 20 and the deployment information transmitted from the distribution control unit 5, and sends the received VM image to the server device 10 based on the physical server configuration information 20. It can be replicated according to the number of virtual machines deployed. That is, the VM image duplicating unit 11 obtains the number of necessary virtual machines based on the received physical server configuration information 20, and duplicates the VM image according to the number.

  The module deployment unit 12 can deploy a module using the deployment information so that each VM image replicated by the VM image replication unit 11 has a configuration described in the physical server configuration information 20. In other words, the module deployment unit 12 performs deletion (exclusion / deinstallation) of an extra module, additional deployment (installation) of a missing module, or module setting on a VM image as necessary. Also good. In addition, the deployment information can include, for example, various information such as a method for canceling module deployment, additional deployment, and setting, the location of information, and parameters.

  Note that the module deployment unit 12 may acquire software components (installation files and the like) necessary for deploying the missing modules from an external device such as a repository (not shown) or a storage device (not shown). Alternatively, the deployment information generation unit 4 may generate deployment information including the above software components. In this case, the module deployment unit 12 can add an insufficient module using the software component included in the received deployment information.

  As described above, according to the present embodiment, the deployment device 1 can transmit, to the server device 10 that deploys a plurality of virtual machines, a VM image from which duplication of modules included in those virtual machines is eliminated. it can. Then, the server device 10 can deploy a plurality of virtual machines having different module configurations based on one received VM image.

  As described above, the deployment device 1 according to the present embodiment has an effect that the total amount of data flowing through the network can be reduced when the virtual machine is deployed to the server device 10. Therefore, the deployment apparatus 1 has an effect of suppressing the occurrence of network congestion when a large-scale system configured by a large number of virtual machines is deployed over the network.

  The reason is that in the deployment device 1, the configuration determination unit 2 derives a common configuration including modules common to the virtual machines deployed in the server device 10. This is because the VM image generation unit 3 generates a VM image including modules without duplication according to the common configuration. That is, the VM image generation unit 3 can reduce the transfer amount of the VM image based on the common configuration. Furthermore, in the server apparatus 10, the VM image duplicating unit 11 configures a plurality of virtual machines by duplicating the received one VM image according to the final number of virtual machines.

<Second Embodiment>
Next, a second embodiment based on the above-described first embodiment will be described. The following description will focus on the characteristic parts according to the second embodiment, and a detailed description overlapping with the components of the second embodiment having the same configuration as that of the first embodiment will be omitted.

  The present embodiment is an example in which the present invention is applied in the construction of a large-scale system including a large number of server devices and various types of virtual machines.

  First, the configuration of this embodiment will be described below with reference to FIG. FIG. 2 is a block diagram showing the configuration of the deployment system according to the second embodiment of the present invention.

  Referring to FIG. 2, the deployment system according to the present embodiment includes a deployment device 100, a component repository 120, and a plurality of server devices 200.

  The deployment device 100, the component repository 120, and each server device 200 can communicate with each other via a communication network (hereinafter simply referred to as a network) 1000 such as the Internet or a local area network (LAN).

  The deployment device 100, the component repository 120, and the server device 200 are operated by a general information processing device (computer) that operates under the control of a computer program (software program) that is executed using a CPU (not shown). It may be configured. Alternatively, each unit of the deployment device 100, the component repository 120, and the server device 200 may be configured by a dedicated hardware device or a logic circuit. A hardware configuration example in which the deployment device 100, the component repository 120, and the server device 200 are realized by a computer will be described later with reference to FIG.

  First, the configuration of the deployment device 100 will be described below.

  The deployment device 100 includes a configuration determination unit 102, a virtual machine (VM) image generation unit 103, a deployment script generation unit 104, a distribution control unit 105, and a storage device 110. The storage device 110 can store system configuration information 111, a virtual machine (VM) image template repository 112, and a script repository 113.

  The system configuration information 111 includes information representing the configuration of the virtual machine deployed on each server device 200. The system configuration information 111 includes information corresponding to the physical server configuration information 20 in the first embodiment regarding each server device 200. In the present embodiment, it is assumed that the system configuration information 111 is stored in advance in the storage device 110 as input information to the configuration determination unit 102. The system configuration information 111 may be input by another method, for example, transmitted from an external device (not shown) to the deployment device 100 via the network 1000. Details of the system configuration information 111 will be described later at the end of the description of the configuration.

  The VM image template repository 112 can store a VM image template serving as a material when the VM image generation unit 103 described later generates a VM image. It is assumed that the VM image template repository 112 is stored in the storage device 110 in advance.

  The script repository 113 can store a deployment script component 500 that is a material used when the deployment script generation unit 104 described later generates a deployment script. The deployment script corresponds to the deployment information in the first embodiment. It is assumed that the script repository 113 is stored in the storage device 110 in advance. Details of the deployment script component 500 will be described later at the end of the description of the configuration.

  The configuration determining unit 102 is based on the configuration determining unit 2 in the first embodiment. The configuration determination unit 102 in the present embodiment acquires physical server configuration information 20 for each server device 200 from the system configuration information 111. The configuration determination unit 102 determines the configuration (distribution configuration) of the VM image to be distributed to each server device 200 based on the acquired physical server configuration information 20.

  In addition, when determining the distribution configuration, the configuration determination unit 102 according to the present embodiment, based on the physical server configuration information 20, determines the “maximum common configuration” or “minimum configuration” in the module deployed in the virtual machine. One of the “coverage configurations” is derived. “Maximum common configuration (GCC configuration)” is a configuration that includes modules that are commonly included in each virtual machine without overlapping each other (one module at a time). In addition, the “minimum comprehensive configuration (LCC configuration)” is a configuration that includes all modules included in each virtual machine without duplication. The “maximum common configuration” and “minimum coverage configuration” correspond to the “common configuration” in the first embodiment.

  The configuration determination unit 102 outputs the GCC configuration derived for each server device 200 or common configuration information representing the LCC configuration to the VM image generation unit 103 and the deployment script generation unit 104. That is, the configuration determination unit 102 selects a VM image based on either one of the GCC configuration or the LCC configuration as a VM image to be distributed to each server device 200.

  The VM image generation unit 103 is based on the VM image generation unit 3 in the first embodiment. The VM image generation unit 103 generates a VM image for each server device 200 based on the common configuration information for each server device 200 received from the configuration determination unit 102. The VM image generation unit 103 can acquire necessary materials and the like when generating a VM image from the VM image template repository 112, a component repository 120 described later, and a script repository 113 as necessary.

  The deployment script generation unit 104 is based on the deployment information generation unit 4 in the first embodiment. The deployment script generation unit 104 generates a deployment script for each server device 200 based on the common configuration information for each server device 200 received from the configuration determination unit 102 and the physical server configuration information 20. The deployment script includes information necessary for deploying the VM image for each server device 200 generated by the VM image generation unit 103 so as to have a final virtual machine configuration. The deployment script generation unit 104 generates a deployment script by using the system configuration information 111 (physical server configuration information 20 for each server device 200) and the deployment script component 500 acquired from the common configuration information script repository 113.

  The distribution control unit 105 is based on the distribution control unit 5 in the first embodiment. The distribution control unit 105 can transmit the VM image generated by the VM image generation unit 103, the deployment script generated by the deployment script generation unit 104, and the system configuration information 111 for each server device 200.

  The storage device 110 is realized by, for example, a semiconductor memory device or a disk device.

  The above is the description of the configuration of the deployment device 100. Next, the configuration of the component repository 120 will be described below.

  The component repository 120 can return the software component 121 necessary for module deployment to the request source in response to a request issued by executing the deployment script or the deployment script component 500. The software component 121 is an installation file required when a module is additionally deployed to a VM image.

  Below, the structure of the server apparatus 200 is demonstrated.

  The server device 200 includes a virtual machine monitor (VM Monitor, VMM) 201 and an agent 210.

  The VMM 201 can operate the VM image deployed by the agent 210 as a virtual machine.

  The agent 210 includes a virtual machine (VM) image copying unit 211 and a module deployment unit 212.

  The VM image duplication unit 211 is based on the VM image duplication unit 11 in the first embodiment. The VM image copying unit 211 receives the VM image, the system configuration information 111, and the deployment script transmitted from the distribution control unit 105. Then, the VM image duplication unit 211 obtains the number of necessary virtual machines based on the physical server configuration information 20 for the own machine included in the system configuration information 111, and duplicates the VM image according to the number.

The module deployment unit 212 is based on the module deployment unit 12 in the first embodiment. The module deployment unit 212 deploys a module to each replicated VM image by using a deployment script so that the configuration of the virtual machine described in the physical server configuration information 20 for the own machine in the system configuration information 111 is obtained. (Dedeployment or additional deployment). That is, the module deployment unit 212 can undeploy (delete) unnecessary (excess) modules for each copied VM image. Alternatively, the module deployment unit 212 can additionally deploy a necessary (deficient) module for each replicated VM image.
In this embodiment, the module deployment unit 212 can acquire the software component 121 necessary for additional deployment of the module from the component repository 120 by executing the deployment script.

  The above is the description of the configuration of the server device 200.

  As the last description of the configuration, details of the system configuration information 300 and the deployment script component 500 will be described. First, details of the system configuration information 300 will be described. FIG. 3 is a diagram illustrating system configuration information 300 that is an example of the system configuration information 111 according to the second embodiment.

  Referring to FIG. 3, the system configuration information 300 includes one repository specifying unit 301 and one or more physical server configuration information 302 and 306.

  The repository designation unit 301 includes information that designates the location of each repository such as the component repository 120, the VM image template repository 112, and the script repository 113.

  Each of the physical server configuration information 302 and 306 corresponds to the physical server configuration information 20 in the first embodiment. That is, the system configuration information 300 includes physical server configuration information 20 for at least two server devices 200. Hereinafter, the configuration of the physical server configuration information will be described in detail using the physical server configuration information 302 as an example.

  The physical server configuration information 302 includes one physical server name information 303 and one or more virtual machine configuration information 304 and 305.

  The physical server name information 303 includes host name information for specifying the deployment destination server apparatus 200. In FIG. 3, the physical server name 303 includes host name information “hs132.example.com”.

  The virtual machine configuration information 304 includes configuration information of a virtual machine deployed in the server device 200 specified by the physical server name information 303. The virtual machine configuration information 304 includes a virtual machine identifier “h132-1”, a name “temp-1032” representing a VM image template to be used, and component names of at least “mod_A” and “mod_B” as modules to be deployed. Is included.

  Similarly, the virtual machine configuration information 305 defines virtual machine configuration information with an identifier of “h132-2”. That is, the same VM image template “temp-1032” as “h132-1” is used for the virtual machine “h132-2”. Further, at least a module having a component name of “mod_A” is arranged in this virtual machine.

  The configuration of the physical server configuration information 306 is basically the same as the configuration of the physical server configuration information 302 described above. The above is the description of the configuration of the system configuration information 300.

  Next, details of the deployment script component 500 stored in the script repository 113 will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of the deployment script component 500 according to the second embodiment.

  For example, the deployment script component 500 may be prepared for each module deployed in the virtual machine. The target module in the deployment script component 500 illustrated in FIG. 9 is a module having a component name “mod_A”. The deployment script component 500 includes an installation unit 501, an uninstallation unit 502, and a setting unit 503.

  The installation unit 501 includes information on a script that can install the target module in the virtual machine. Further, the installation unit 501 may include conflict information indicating modules that cannot be installed on the same machine.

  The uninstall unit 502 includes information on a script that can uninstall the target module installed in the virtual machine from the virtual machine. Note that in the case of a module that is difficult to cleanly uninstall, the deployment script component 500 may not include the uninstall unit 502.

  The setting unit 503 includes information on a script that can set the target module in accordance with the execution environment. For example, the setting unit 503 may be a script that allows the coping module to set parameters in accordance with each server device 200 that is the distribution destination of the VM image. If there is no need to make settings, the deployment script component 500 may not include the setting unit 503.

  As an example of a script included in each part of the deployment script component 500, Puppet (Introduction to Puppet, [online], Puppet Labs, [Search June 6, 2014], Internet <URL: http://docs.puppetlabs.com /guides/introduction.html>). In addition, as an example of the above script, in addition to Chef (An Overview of Chef, [online], Chef Software, Inc, [June 6, 2014 search], Internet <URL: http: //docs.opscode .com / chef_overview.html>).

  The script included in the installation unit 501 and the uninstallation unit 502 may use a mechanism that can perform installation and uninstallation processing of the target module.

  As an example of the above mechanism, in the case of a Linux (registered trademark) OS, apt (Gustavo Noronha Silva, APT HOWTO (Obsolete Documentation), [online], Debian Project, [Search June 6, 2014], Internet <URL: http: //www.debian.org/doc/manuals/apt-howto/index.en.html>) is available. In addition, as an example of the above mechanism, in the case of Linux OS, in addition to yum (Hradilek Jaromir, 14 others, Red Hat Enterprise Linux 6 Installation Guide Red Hat Enterprise Linux 6 Installation, Configuration, Management Edition 4, No. 4 Chapter 6 Yum, [online], October 31, 2013, Red Hat, Inc., [Search June 6, 2014], Internet <URL: https://access.redhat.com/site/documentation /ja-JP/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-yum.html>). In addition, as an example of the above-described mechanism, in the case of a Linux OS, the RPM Package Manager (RPM 4.11.2 Release Notes, [online], Open Source Lab, [June 6, 2014 search], Internet <URL: http://www.rpm.org/wiki/Releases/4.11.2>).

  As an example of the above mechanism, in the case of a Windows (registered trademark) OS, InstallShield (InstallShield, Overview, [online], 2014, Flexera Software LLC., [Search June 6, 2014], Internet <URL: http://www.flexerasoftware.com/products/software-installation/installshield-software-installer/).

  The above is the description of the deployment script component 500. The above is the description of the configuration of the present embodiment.

  Next, the operation of the present embodiment having the above-described configuration will be described using a specific example. First, with reference to FIG. 4 to FIG. 7, an operation outline from the determination of the distribution configuration in the deployment device 100 to the final deployment of the virtual machine in the server device 200 will be described. FIG. 4 is a flowchart illustrating an outline of operations performed by the deployment device 100 and the server device 200 in the second embodiment.

  Referring to FIG. 4, first, the configuration determining unit 102 in the deployment device 100 acquires virtual machine configuration information for each server device 200 from the system configuration information 111 (step S10). Specifically, the configuration determining unit 102 first acquires system configuration information 111 including configuration information for a plurality of server devices 200 from the storage device 110. Then, the configuration determination unit 102 extracts the physical server configuration information 20 (information corresponding to the physical server configuration information 302 and 306 in FIG. 3) separately from the system configuration information 111 for each server device 200.

  Here, as a specific example, it is assumed that the configuration determining unit 102 has acquired the physical server configuration information 400 of the server device 200 illustrated in FIG. FIG. 5 is a diagram illustrating the concept of physical server configuration information, minimum coverage configuration, and maximum common configuration in the second embodiment. The physical server configuration information 400 illustrated in FIG. 5 is a schematic diagram of one of the physical server configuration information 302 and 306 included in the system configuration information 111 (300) illustrated in FIG. The physical server configuration information 400 in this specific example includes three virtual machine configuration information 401 to 403 for constructing virtual machines VM_A, VM_B, and VM_C for a certain server device 200.

  The virtual machine configuration information 401 to 403 is premised on the same VM image template being specified. The VM_A virtual machine configuration information 401 includes information that three software modules, modules A, B, and C, are deployed in the VM_A. Similarly, the virtual machine configuration information 402 of VM_B includes information that three software modules of modules A, B, and D are deployed in VM_B. Further, the VM_C virtual machine configuration information 403 includes information indicating that two software modules, modules A and B, are deployed in the VM_C.

  The following description of the outline is a description of a procedure (operation) in the case of deploying a virtual machine to the server apparatus 200 that is a deployment target based on one piece of physical server configuration information 400 (FIG. 5). That is, the operation described below is executed for each physical server configuration information 400 included in the system configuration information 111.

  Next, the configuration determining unit 102 determines the distribution configuration (step S11). Specifically, the configuration determination unit 102 has a distribution configuration that includes all the modules A, B, C, and D included in each of the virtual machine configuration information 401 to 403 as the minimum coverage configuration (LCC) 404. decide. That is, the LCC 404 is the minimum configuration that covers all modules deployed in the virtual machine of the server apparatus 200 that is the deployment target.

  Alternatively, the configuration determination unit 102 may determine the maximum common configuration (GCC) 405 instead of the LCC when it is determined that the virtual machine cannot be deployed based on the VM image corresponding to the LCC. The GCC 405 includes one module A and one B that are commonly included in all the virtual machine configuration information 401 to 403. In other words, the GCC 405 has a configuration in which as many modules as possible are incorporated (maximum) in common with all the virtual machines of the server apparatus 200 that is the deployment target. Details of the procedure in which the configuration determining unit 102 determines the LCC 404 and the GCC 405 as distribution configurations will be described after the outline of the operation.

  The configuration determining unit 102 outputs common configuration information representing the distribution configuration determined to either the LCC 404 or the GCC 405 to the VM image generating unit 103 and the deployment script generating unit 104.

  An outline of operations after step S12 will be described for each distribution configuration.

  First, an outline of operations after step S12 when the LCC 404 is determined as a distribution configuration will be described with reference to FIGS. FIG. 6 is a conceptual diagram illustrating a configuration procedure of a virtual machine using the minimum coverage configuration in the server apparatus 200 according to the second embodiment.

  In step S12, the VM image generation unit 103 generates a VM image (VM_LCC 414 in FIG. 6) corresponding to the LCC 404 based on the common configuration information received from the configuration determination unit 102, and the distribution control unit 105 generates the generated VM image. (Step S12).

  On the other hand, the deployment script generation unit 104 generates a deployment script corresponding to the LCC 404, and outputs the generated deployment script to the distribution control unit 105 (step S13). That is, the deployment script generation unit 104 generates a deployment script including at least a deployment script component 500 corresponding to a module that needs to be undeployed from the VM_LCC 414. In this specific example, the deployment script generation unit 104 generates deployment scripts for all modules A to D included in the LCC 404.

  The distribution control unit 105 transmits the VM image (VM_LCC 414), the deployment script corresponding to the LCC 404, and the system configuration information 111 to the target server device 200 (step S14). This is the end of the operation of the deployment device 100.

  In the server device 200, the VM image copying unit 211 of the agent 210 receives the VM_LCC 414, the deployment script, and the system configuration information 111 (step S20). The agent 210 reads the physical server configuration information 400 for the own machine included in the system configuration information 111, and performs the following processing based on the physical server configuration information 400.

  Next, the agent 210 deploys a virtual machine in the server device 200 so as to have a virtual machine configuration indicated by the physical server configuration information 400 for the own device (step S21).

  Specifically, first, the VM image replication unit 211 replicates the VM_LCC 414 according to the number of virtual machines included in the physical server configuration information 400. In this specific example, as illustrated in FIG. 6, the VM image copying unit 211 copies as three VM images of VM_A 411, VM_B 412, and VM_C 413. Next, the module deployment unit 212 of the agent 210 cancels the deployment of unnecessary modules from each copied VM image so as to match the physical server configuration information 400. In this specific example, the module deployment unit 212 cancels the deployment of the module D from the VM_A 411. Further, the module deployment unit 212 cancels the deployment of the module C from the VM_B 412. Further, the module deployment unit 212 cancels the deployment of the modules C and D from the VM_C 413. The method for canceling the deployment is premised on being described in the received deployment script.

  As a result of such a procedure, a desired virtual machine configuration is constructed in the server device 200.

  Next, an outline of operations after step S12 when the GCC 405 is determined as the distribution configuration will be described with reference to FIGS. FIG. 7 is a conceptual diagram illustrating a configuration procedure of a virtual machine using the maximum common configuration in the server apparatus 200 according to the second embodiment.

  In step S12, the VM image generation unit 103 generates a VM image (VM_GCC 425 in FIG. 7) corresponding to the GCC 405 based on the common configuration information received from the configuration determination unit 102, and the distribution control unit 105 generates the generated VM image. (Step S12).

  On the other hand, the deployment script generation unit 104 generates a deployment script corresponding to the GCC 405, and outputs the generated deployment script to the distribution control unit 105 (step S13). That is, the deployment script generation unit 104 generates a deployment script corresponding to at least a module that needs to be additionally deployed in the VM_GCC 425. In this specific example, the deployment script generation unit 104 generates deployment scripts for all modules A to D included in the physical server configuration information 400.

  The distribution control unit 105 transmits the VM image (VM_GCC 425), the deployment script corresponding to the GCC 405, and the system configuration information 111 to the target server device 200 (step S14). This is the end of the operation of the deployment device 100.

  In the server device 200, the VM image copying unit 211 of the agent 210 receives the VM_GCC 425, the deployment script, and the system configuration information 111 (step S20). The agent 210 reads the physical server configuration information 400 for the own machine included in the system configuration information 111, and performs the following processing based on the physical server configuration information 400.

  Next, the agent 210 deploys a virtual machine in the server device 200 so as to have a virtual machine configuration indicated by the physical server configuration information 400 for the own device (step S21).

  Specifically, first, the VM image replication unit 211 replicates the VM_GCC 425 according to the number of virtual machines included in the physical server configuration information 400. In this specific example, the VM image duplicating unit 211 duplicates as three VM images of VM_A 421, VM_B 422, and VM_C 423 as shown in FIG. Next, the module deployment unit 212 of the agent 210 additionally deploys the missing module to each copied VM image so as to match the physical server configuration information 400. In this specific example, the module deployment unit 212 adds the module C to the VM_A 421. Further, the module deployment unit 212 adds the module D to the VM_B 422. The module deployment unit 212 does not add any module to the VM_C 413. It is assumed that the method of adding is described in the received deployment script. Further, in the present embodiment, the module deployment unit 212 can acquire the software component 121 (install file or the like) of the module to be added from the component repository 120.

  As a result of such a procedure, a desired virtual machine configuration is constructed in the server device 200.

  The above is the outline of the operations performed by the deployment device 100 and the server device 200. The execution order of step S12 and step S13 is not limited to the above. That is, step S13 may be executed prior to step S12 or concurrently.

  Next, with reference to FIGS. 8 and 10 to 13, detailed operations of the respective units in the above-described outline description will be described. In the following, description will be made using a specific example similar to the description of the operation outline.

  First, the operation P1000 of the configuration determining unit 102 in steps S10 and S11 of FIG. 4 will be described in detail with reference to FIG. FIG. 8 is a flowchart illustrating an operation when the configuration determining unit 102 according to the second embodiment determines a distribution configuration.

  The configuration determination unit 102 first reads the configuration information of all virtual machines to be deployed from the system configuration information 111 of the server device 200 that is the deployment destination, and the configuration information of the read virtual server is the physical server that is the deployment destination. Grouping is performed for each (server apparatus 200) (step S1001). Next, the configuration determining unit 102 groups the configuration information of the virtual machine group deployed on one server device 200 for each virtual machine for which the same VM image template is designated (step S1002).

  In this specific example, one group (a group of virtual machines that are the same server device 200 and the same VM image template) as a result of grouping in steps S1001 and S1002 is included in the physical server configuration information 400 (FIG. 5). It corresponds to a virtual machine group.

  The operation of the configuration determining unit 102 from step S1003 to step S1008 is the operation of the configuration determining unit 102 for the physical server configuration information 400 (FIG. 5) of one server apparatus 200.

  Next, the configuration determining unit 102 generates a minimum coverage configuration (LCC) 404 (FIG. 5) for the group of virtual machines that are the same server device 200 and the same VM image template (step S1003). The LCC 404 can include information representing a VM image template of a virtual machine group to be processed in addition to a list of modules representing a distribution configuration. Details of the operation P1100 when generating the LCC 404 will be described later.

  Next, the configuration determining unit 102 acquires the deployment script component 500 for all the software modules included in the LCC 404 (step S1004). In the present embodiment, the configuration determining unit 102 can acquire the deployment script component 500 for all the software modules included in the LCC 404 from the script repository 113.

  Next, the configuration determining unit 102 checks whether there is a configuration conflict such as that the module included in the LCC 404 cannot be installed on the same machine based on each acquired deployment script component 500 (step S1005). When there is a configuration conflict (Y in step S1005), the configuration determination unit 102 executes an operation in step S1007 described later.

  If there is no configuration conflict (N in step S1005), the configuration determination unit 102 checks whether or not a deployment cancellation procedure (uninstallation unit) exists in all the acquired deployment script components 500 (step S1006).

  When there is an uninstall unit in all the deployment script components 500 (Y in step S1006), the configuration determination unit 102 determines to adopt the LCC 404 as the distribution configuration.

  On the other hand, if there is a configuration conflict (Y in step S1005), and if there is even one deployment script component 500 without an uninstall unit (N in step S1006), the configuration determination unit 102 creates a VM image corresponding to the LCC 404. It is determined that it is impossible to deploy a virtual machine based on it. Then, the configuration determining unit 102 generates the maximum common configuration (GCC) 405 (FIG. 5) for the virtual machine group that is the same server device 200 and the same VM image template, grouped in step S1002 (step S1007). ). Details of the operation P1200 when generating the GCC 405 will be described later. The GCC 405 can include information representing a VM image template of a target virtual machine group in addition to a list of modules representing a distribution configuration. The configuration determining unit 102 determines the adoption of the GCC 405 as the distribution configuration.

  Next, the configuration determination unit 102 outputs common configuration information representing the determined distribution configuration (LCC 404 or GCC 405) to the VM image generation unit 103 and the deployment script generation unit 104, so that the VM image and the deployment script are output. Generation is instructed (step S1008).

  The configuration determining unit 102 repeats the processing from step S1003 to S1008 for the virtual machine group to which the other VM image template is specified that is deployed in the target server apparatus 200 in step S1003 (step S1009). .

  After the processing from step S1003 to step S1009 is completed, the configuration determination unit 102 further repeats the processing from step S1002 to step S1009 for the remaining server devices 200 included in the system configuration information 111 (step S1010).

  In step S1004, the configuration determining unit 102 may not be able to acquire the deployment script component 500 for all software modules. That is, the configuration determination unit 102 only needs to acquire the deployment script component 500 for at least a module that needs to be undeployed from the VM_LCC 414 or a module that has a configuration conflict.

  Similarly, in step S <b> 1006, the configuration determining unit 102 may target at least the deployment script component 500 for the module that needs to be undeployed from the VM_LCC 414 when checking the presence of the uninstall unit. That is, in the case of a specific example, regarding the modules A and B, the configuration determination unit 102 may determine the LCC 404 as the distribution configuration without the deployment script component 500 in which the uninstall unit exists.

  In step S1008, the configuration determination unit 102 may output the acquired deployment script component 500 to the deployment script generation unit 104 instead of the common configuration information. In that case, the deployment script generation unit 104 can generate a deployment script from the deployment script component 500 received from the configuration determination unit 102.

  The above is the details of the operation P1000 of the configuration determination unit 102 in steps S10 and S11 of FIG.

  Next, the operation P1100 of the configuration determining unit 102 when generating the LCC 404 (step S1003 in FIG. 8) will be described in detail with reference to FIG. FIG. 10 is a flowchart illustrating an operation when generating the minimum coverage configuration information performed by the configuration determination unit 102 according to the second embodiment. The virtual machine configuration information 401 to 403 (FIG. 5) targeted for the following operation is virtual machine configuration information included in the physical server configuration information 400 targeted in step S1003.

  First, the configuration determining unit 102 initializes, as an empty list, a storage area (not shown) that stores the LCC 404 as a return value for storing the result of the operation P1100 (step S1101).

  Next, the configuration determining unit 102 performs the following operation on each of the virtual machine configuration information 401 to 403 (FIG. 5).

  First, the configuration determining unit 102 enumerates modules deployed in the virtual machine for one selected from the virtual machine configuration information 401 to 403 (step S1102).

  Next, the configuration determining unit 102 adds modules that are not included in the LCC 404 among the listed modules to the LCC 404 (step S1103).

  The configuration determining unit 102 repeats the processes of steps S1102 and S1103 for the remaining virtual machine configuration information (step S1104). The configuration determining unit 102 can generate the LCC 404 in this way.

  Next, with reference to FIG. 11, the operation P1200 of the configuration determining unit 102 when generating the GCC 405 (step S1007 in FIG. 8) will be described in detail. FIG. 11 is a flowchart illustrating an operation when generating the maximum common configuration information performed by the configuration determination unit 102 according to the second embodiment. The virtual machine configuration information 401 to 403 (FIG. 5) targeted for the following operations is virtual machine configuration information included in the physical server configuration information 400 targeted in step S1007.

  First, the configuration determination unit 102 stores a storage area (not shown) for storing the GCC 405 as a return value for storing the result of the operation P1200, as a list of modules included in any one of the virtual machine configuration information 401 to 403. (Step S1201).

  Next, the configuration determining unit 102 performs the following operation on each of the virtual machine configuration information 401 to 403.

  First, the configuration determining unit 102 enumerates modules deployed in the virtual machine for one selected from the virtual machine configuration information 401 to 403 (step S1202).

  Next, the configuration determining unit 102 deletes, from the GCC 405, modules that are not included in the modules listed in step S1202 from the GCC 405 (step S1203).

  The configuration determining unit 102 repeats the processes of steps S1202 and S1203 for the remaining virtual machine configuration information (step S1204). The configuration determining unit 102 can generate the GCC 405 in this way.

  Next, the operation P1300 of the VM image generation unit 103 when generating a VM image (step S12 of FIG. 4) will be described in detail with reference to FIG. FIG. 12 is a flowchart illustrating an operation when the VM image generation unit 103 according to the second embodiment generates a VM image. The VM image generation unit 103 generates the following VM image in response to a VM image generation instruction (step S1008 in FIG. 8) from the configuration determination unit 102.

  First, the VM image generation unit 103 receives common configuration information representing the distribution configuration of the LCC 404 or GCC 405 from the configuration determination unit 102. Next, the VM image generation unit 103 acquires a VM image template used for the generated VM image from the VM image template repository 112 based on the common configuration information. Then, the VM image generation unit 103 activates the acquired VM image template as a VM (step S1301).

  Next, the VM image generation unit 103 acquires the deployment script component 500 corresponding to the modules listed in the common configuration information from the script repository 113. Also, the VM image generation unit 103 acquires the software component 121 corresponding to each module listed in the common configuration information from the component repository 120. Then, the VM image generation unit 103 deploys each module (software component 121) to the VM activated in step S1301, based on the installation unit 501 of the deployment script component 500 (step S1302). Note that if the VM image template already contains a module, the VM image generation unit 103 does not need to deploy the module to the VM. Further, the VM image generation unit 103 uninstalls the extra module from the VM based on the deployment script component 500 of the extra module not included in the common configuration information among the modules already included in the VM image template ( (Undeployment) may be performed.

  Finally, the VM image generation unit 103 stops the VM in which the above-described module is deployed, and generates a VM image file that can be distributed from the stopped VM (step S1303). In this way, the VM image generation unit 103 can generate a VM image corresponding to the LCC 404 or GCC 405. The VM image generated here is transmitted to the server device 200 by the distribution control unit 105 in step S14 of FIG.

  The above is the details of the operation P1300 of the VM image generation unit 103 in step S12 of FIG.

  Next, with reference to FIG. 13, the operation P2000 of the agent 210 when deploying a virtual machine to the server apparatus 200 (step S21 in FIG. 4) will be described in detail. FIG. 13 is a flowchart illustrating an operation when deploying a virtual machine performed by the agent 210 according to the second embodiment. After receiving the VM image (VM_LCC 414 in FIG. 6 or VM_GCC 425 in FIG. 7), the deployment script, and the system configuration information 111, the agent 210 deploys the virtual machine as follows.

  First, the VM image duplicating unit 211 reads the received system configuration information 111 and duplicates the received VM image according to the number of virtual machines specified in the physical server configuration information 400 for the own device (step S2001).

  Next, the module deployment unit 212 selects the virtual machine configuration information 401 to 403 (FIG. 5) included in the physical server configuration information 400 one by one, and performs the following operation on each selected virtual machine configuration information. Do.

  First, when the received VM image has an LCC configuration (VM_LCC 414) (Y in step S2002), the module deployment unit 212 lists modules to be deleted from the VM image (step S2003). Specifically, the module deployment unit 212 obtains a difference between the selected virtual machine configuration information and the module configuration of the VM_LCC 414 (that is, the LCC 404).

  Next, the module deployment unit 212 cancels the deployment of all the modules based on the uninstall unit 502 (FIG. 9) of the deployment script component 500 corresponding to each listed module (step S2004). This completes the process for one piece of virtual machine configuration information when the received VM image is based on the LCC configuration.

  On the other hand, when the received VM image has a GCC configuration (VM_GCC 425) (N in step S2002), the module deployment unit 212 lists modules to be added to the VM image (step S2005). Specifically, the module deployment unit 212 obtains a difference between the virtual machine configuration information selected after step S2001 and the module configuration of the VM_GCC 425 (ie, GCC 405).

  Next, the module deployment unit 212 acquires the software components 121 of those modules from the component repository 120 based on the installation unit 501 (FIG. 9) of the deployment script component 500 corresponding to each listed module. The module deployment unit 212 can acquire the location of the component repository 120 from the repository designation unit 301 (FIG. 3) of the system configuration information 111. Then, the module deployment unit 212 deploys each module using the acquired software component 121 based on the installation unit 501 (step S2006). This completes the process for one piece of virtual machine configuration information when the received VM image is based on the GCC configuration. Thereafter, the VMM 201 can operate the VM image deployed by the agent 210 as a virtual machine.

  The module deployment unit 212 repeats the processing from step S2002 to step S2006 for all virtual machines deployed based on the same VM image (step S2007).

  As described above, the agent 210 can deploy all the virtual machines in the server device 200 based on one VM image by executing the above-described processing on all the virtual machine groups to be deployed. it can.

  The above is the details of the operation P2000 of the agent 210 in step S21 of FIG.

  As described above, the present embodiment has an effect that the total amount of data flowing through the network can be reduced when the virtual machine is deployed on the server apparatus 200. In other words, the deployment apparatus 200 according to the present embodiment does not distribute a large amount of virtual machine images at the time of initial construction of a large-scale system composed of a large number of virtual machines, thereby suppressing the occurrence of network congestion. There is an effect that can be done.

  This is because, in the deployment device 100, the configuration determining unit 102 derives a common configuration of virtual machine modules configured based on the same VM image template for each server device 200. Then, the VM image generation unit 3 generates one VM image including modules without duplication based on the common configuration. This is because the distribution control unit 105 finally transmits the one VM image to the server device 200 once to complete the transmission of the VM images related to a plurality of virtual machines.

  In this embodiment, the distribution control unit 105 transmits the system configuration information 111 to the server device 200. If the information required by the agent 210 of the server device 200 that is the transmission destination is included, the distribution control unit 105 Not limited to. For example, instead of the system configuration information 111, the distribution control unit 105 may transmit physical server configuration information 400 (FIG. 5) for the destination server device 200 and information indicating the location of the component repository 120.

<Third Embodiment>
Next, a third embodiment based on the above-described second embodiment will be described. In the following description, the characteristic parts according to the third embodiment will be mainly described, and the detailed description of the components of the third embodiment having the same configuration as that of the second embodiment will be omitted.

  The configuration of this embodiment is as shown in FIG. 2 as in the second embodiment. This embodiment is different from the second embodiment in that the server apparatus 200, which is the deployment destination of the virtual machine, can set the software module included in each virtual machine. In other words, in the present embodiment, setting for modules deployed in each virtual machine becomes possible, so that different settings can be handled for each virtual machine.

  With reference to FIG. 14, the configuration of the system configuration information 350 in the present embodiment will be described. FIG. 14 is a diagram illustrating an example of the system configuration information 350 according to the third embodiment.

  As shown in FIG. 14, the components 301 to 306 of the system configuration information 350 include the module information 351 in which parameter settings are specified in the virtual machine configuration information 304, except for the system configuration information 300 ( This is the same as FIG. In the specific example illustrated in FIG. 14, the module information 351 includes information specifying that a value “zzzzz” is set for a parameter with an ID “params.param1” in the module “mod_A”.

  Note that the module information 351 in which parameter settings are specified may be included in other virtual machine configuration information such as the virtual machine configuration information 306, for example.

  Next, the operation of the deployment system according to this embodiment will be described. The operations up to distribution of the VM image to the server device 200 in the present embodiment are the same as those in the second embodiment. That is, the operation of each unit in the agent 210 of the server device 200 according to the present embodiment is the same as in the second embodiment.

  The operation of this embodiment is different from that of the second embodiment in the virtual machine deployment processing in the server apparatus 200. With reference to FIG. 15, the operation P2100 of the agent 210 in the present embodiment will be described in detail. FIG. 15 is a flowchart illustrating an operation when deploying a virtual machine performed by the agent 210 according to the third embodiment.

  The operation of the agent 210 according to the present embodiment is that a module setting operation (step S2101) is added between step S2006 (FIG. 13) and step S2007 performed by the module deployment unit 212 in the second embodiment. It is different. That is, in FIG. 15, each operation shown as steps S2001 to S2007 is the same as that in the second embodiment, and thus a duplicate description is omitted.

  Referring to FIG. 15, when the VM image received from the deployment apparatus 100 has a GCC configuration (VM_GCC 425) (N in Step S2002), the module deployment unit 212 lists modules to be added to the VM image (Step S2005). ). Next, the module deployment unit 212 acquires the software component 121 of each listed module from the component repository 120, and deploys each module using the acquired software component 121 (step S2006).

  In the present embodiment, the module deployment unit 212 sets the settings for each module specified in the module information 351 (FIG. 14) of the system configuration information 350 based on the setting unit 503 of the deployment script component 500 (FIG. 9). Is performed (step S2101). Specifically, the module deployment unit 212 uses the setting method described in the setting unit 503 of the deployment script component 500 for the module “mod_A”, and sets “zzzzz” for the ID parameter “params.param1”. Set the value.

  In the present embodiment, this completes the processing for one piece of virtual machine configuration information when the received VM image is based on the GCC configuration.

  Similar to the second embodiment, the module deployment unit 212 repeats the processing from step S2002 to step S2006 and step S2101 for all virtual machines deployed based on the same VM image (step S2007).

  As described above, the agent 210 according to the present embodiment executes the above-described processing on all virtual machine groups to be deployed, so that all virtual machines in the server apparatus 200 are based on one VM image. Can be deployed.

  As described above, in addition to the same effects as those of the second embodiment described above, this embodiment also has an effect that it is possible to cope with different settings for each virtual machine.

  This is because the module deployment unit 212 can set parameters and the like for the software modules included in each virtual machine according to the module information 351 included in the system configuration information 350.

  Note that the module deployment unit 212 may perform settings for a module that is included in the received VM image and that does not cancel (delete) the deployment at the time of deployment. In this case, the module deployment unit 212 performs setting for each module (step S2101) either during or before or after the operation performed when the received VM image is an LCC (steps S2003 to S2004).

  1 and 2 in each embodiment described above may be configured by independent hardware circuits, or may be regarded as a function (processing) unit (software module) of a software program. it can. However, the division of each part shown in these drawings is a configuration for convenience of explanation, and various configurations can be assumed for mounting. An example of the hardware environment in such a case will be described with reference to FIG.

  FIG. 16 is a diagram illustrating the configuration of a computer (information processing apparatus) applicable to each of the embodiments of the present invention and a deployment system according to a modification example thereof. That is, FIG. 16 shows a computer configuration capable of realizing at least one of the deployment devices 1 and 100, the server devices 10 and 200, and the component repository 120 in each of the above-described embodiments. The hardware environment that can realize each function is shown.

  The computer 900 shown in FIG. 16 includes a CPU (Central Processing Unit) 901, a ROM (Read Only Memory) 902, a RAM (Random Access Memory) 903, a communication interface (I / F) 904, a display 905, and a hard disk device (HDD). ) 906, and these are connected via a bus 907. When the computer shown in FIG. 16 functions as the deployment devices 1 and 100, the server devices 10 and 200, and the component repository 120, the display 905 need not always be provided.

  The communication interface 904 is a general communication unit that realizes communication between the computers in each of the above-described embodiments. The hard disk device 906 stores a program group 906A and various storage information 906B. The program group 906A is, for example, a computer program for realizing a function corresponding to each block (each unit) shown in FIGS. 1 and 2 described above. The various storage information 906B is, for example, the system configuration information 111, the VM image template repository 112, the script repository 113, and the software component 121 illustrated in FIG. In such a hardware configuration, the CPU 901 governs the overall operation of the computer 900.

  The present invention described with reference to each of the above embodiments is a block diagram (FIGS. 1 and 2) or a flowchart (FIGS. 4, 8, 10 to 13) referred to in the description of each embodiment, and After the computer program capable of realizing the function of FIG. 15) is supplied, the computer program is read out and executed by the CPU 901 of the hardware. The computer program supplied to the computer may be stored in a non-volatile storage device (storage medium) such as a readable / writable temporary storage memory 903 or a hard disk device 906.

  In the above-described case, the computer program can be supplied to each device by a method of installing in the device via various recording media such as a floppy disk (registered trademark) and CD-ROM, the Internet, etc. Currently, a general procedure can be employed, such as a method of downloading from the outside via the communication network 1000. In such a case, the present invention can be understood to be configured by a computer-readable storage medium in which the code constituting the computer program or the code is recorded.

  Note that a part or all of the above-described embodiment can be described as the following supplementary notes, but is not limited to the following supplementary notes.

(Appendix 1)
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Configuration determining means for deriving a configuration and outputting common configuration information representing the common configuration;
VM image generation means for generating a VM image including at least the common software module without duplication based on the common configuration information;
Deployment information generating means for generating deployment information including information necessary for deploying the VM image based on the common configuration information and the physical server configuration information;
A deployment device comprising: a distribution control unit that transmits the VM image, the physical server configuration information, and the deployment information to the server device.

(Appendix 2)
The deployment apparatus according to claim 1, wherein the configuration determination unit derives, as the common configuration, a minimum coverage configuration that includes all software modules included in the virtual machines without duplication when the common configuration is derived. .

(Appendix 3)
The deployment apparatus according to claim 1, wherein the configuration determining unit derives, as the common configuration, a maximum common configuration that is a configuration that includes modules that are commonly included in the virtual machines when the common configuration is derived. .

(Appendix 4)
When the configuration determining unit determines that the virtual machine cannot be deployed based on a VM image corresponding to the minimum coverage configuration when the minimum coverage configuration is derived as the common configuration, the minimum coverage configuration is determined. The deployment device according to appendix 2, wherein instead of a configuration, a maximum common configuration, which is a configuration that includes modules that are commonly included in the respective virtual machines without duplication, is derived as the common configuration.

(Appendix 5)
The VM image, the physical server configuration information, and the deployment information transmitted from the deployment device according to any one of appendices 1 to 4 are received, and the VM image is obtained based on the physical server configuration information VM image duplicating means for duplicating according to the number of virtual machines deployed in the server device;
A server device comprising: module deployment means for deploying a software module to each of the replicated VM images using the deployment information so as to have a virtual machine configuration described in the physical server configuration information.

(Appendix 6)
The server device according to claim 5, wherein the module deploying unit deploys the software module by deleting an unnecessary module for each duplicated VM image when deploying the software module.

(Appendix 7)
The server device according to claim 5, wherein when deploying the software module, the module deploying unit deploys the software module by additionally deploying a missing module for each replicated VM image.

(Appendix 8)
Using an information processing device
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Deriving the configuration
Generating common configuration information representing the common configuration;
Generating a VM image including at least the common software module without duplication based on the common configuration information;
Based on the common configuration information and the physical server configuration information, generate deployment information including information necessary for deploying the VM image,
Transmitting the VM image, the physical server configuration information, and the deployment information to the server device;
In the server device,
Receiving the VM image, the physical server configuration information, and the deployment information;
Duplicating the VM image according to the number of virtual machines deployed on the server device, obtained based on the physical server configuration information,
A deployment method that deploys a software module to each replicated VM image using the deployment information so that the configuration of the virtual machine is described in the physical server configuration information.

(Appendix 9)
9. The deployment method according to claim 8, wherein, when deriving the common configuration, a minimum covering configuration that includes all software modules included in each virtual machine without duplication is derived as the common configuration.

(Appendix 10)
9. The deployment method according to claim 8, wherein, when deriving the common configuration, a maximum common configuration, which is a configuration including modules that are commonly included in the virtual machines, is derived as the common configuration.

(Appendix 11)
When it is determined that it is impossible to deploy the virtual machine based on the VM image corresponding to the minimum coverage configuration when the minimum coverage configuration is derived as the common configuration, instead of the minimum coverage configuration, The deployment method according to appendix 9, wherein a maximum common configuration, which is a configuration including modules that are commonly included in each virtual machine, is derived as the common configuration.

(Appendix 12)
The deployment method according to appendix 8 or 9, wherein in the server device, when deploying the software module, the software module is deployed by deleting unnecessary modules for each of the duplicated VM images.

(Appendix 13)
In the server device, when the software module is deployed, the software module is deployed by additionally deploying the missing module for each replicated VM image. The deployment method according to any one of the above.

(Appendix 14)
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine A configuration determination process for deriving a configuration and outputting common configuration information representing the common configuration;
A VM image generation process for generating a VM image including at least the common software module without duplication based on the common configuration information;
A deployment information generation process for generating deployment information including information necessary for deploying the VM image based on the common configuration information and the physical server configuration information;
A computer program that causes a first computer to execute distribution control processing for transmitting the VM image, the physical server configuration information, and the deployment information to the server device.

(Appendix 15)
The computer according to claim 14, wherein, in the configuration determination process, when the common configuration is derived, a minimum coverage configuration that includes all software modules included in the virtual machines without duplication is derived as the common configuration. program.

(Appendix 16)
The computer according to claim 14, wherein, in the configuration determination process, when the common configuration is derived, a maximum common configuration that includes a module that is included in each virtual machine without duplication is derived as the common configuration. program.

(Appendix 17)
In the configuration determination process, when the minimum coverage configuration is derived as the common configuration, when it is determined that the virtual machine cannot be deployed based on the VM image corresponding to the minimum coverage configuration, the minimum coverage configuration The computer program according to claim 15, wherein, instead of a configuration, a maximum common configuration that includes a module that is included in each virtual machine in common is derived as the common configuration.

(Appendix 18)
The VM image, the physical server configuration information, and the deployment information transmitted from the first computer according to any one of appendices 14 to 17 are received, and the VM image is based on the physical server configuration information VM image duplication processing to be duplicated according to the number of virtual machines deployed on the server device,
Module deployment processing for deploying a software module to each of the replicated VM images using the deployment information so that the configuration of the virtual machine described in the physical server configuration information is achieved in the second computer A computer program to be executed.

(Appendix 19)
The computer program according to appendix 18, wherein, in the module deployment process, when the software module is deployed, the software module is deployed by deleting an unnecessary module for each copied VM image.

(Appendix 20)
The computer program according to claim 18, wherein, in the module deployment process, when the software module is deployed, the software module is deployed by additionally deploying a missing module for each replicated VM image. .

DESCRIPTION OF SYMBOLS 1,100 Deployment apparatus 2,102 Configuration determination part 3,103 Virtual machine (VM) image generation part 4 Deployment information generation part 5,105 Distribution control part 10,200 Server apparatus 11, 211 VM image duplication part 12,212 Module deployment Unit 20, 302, 306, 400 Physical server configuration information 104 Deployment script generation unit 110 Storage device 111, 300, 350 System configuration information 112 Virtual machine (VM) image template repository 113 Script repository 120 Component component repository 121 Software component 201 Virtual machine Monitor (VMM)
210 Agent 301 Repository designation unit 303 Physical server name information 304, 305 Virtual machine configuration information 351 Module information 401 VM_A virtual machine configuration information 402 VM_B virtual machine configuration information 403 VM_C virtual machine configuration information 404 Minimum coverage configuration (LCC)
405 Maximum common configuration (GCC)
411, 421 VM_A
412, 422 VM_B
413, 423 VM_C
414 VM image corresponding to LCC404 (VM_LCC)
425 VM image corresponding to GCC405 (VM_GCC)
500 Deployment Script Parts 501 Installation Unit 502 Uninstallation Unit 503 Setting Unit 900 Information Processing Device (Computer)
901 CPU
902 ROM
903 RAM
904 Communication interface (I / F)
905 Display 906 Hard disk device (HDD)
906A Program group 906B Various stored information 907 Bus 1000 Network (communication network)

Claims (10)

Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Configuration determining means for deriving a configuration and outputting common configuration information representing the common configuration;
VM image generation means for generating a VM image including at least the common software module without duplication based on the common configuration information;
Deployment information generating means for generating deployment information including information necessary for deploying the VM image based on the common configuration information and the physical server configuration information;
A deployment device comprising: a distribution control unit that transmits the VM image, the physical server configuration information, and the deployment information to the server device. The deployment according to claim 1, wherein the configuration determination unit derives, as the common configuration, a minimum coverage configuration that includes all software modules included in each virtual machine without duplication when the common configuration is derived. apparatus. The deployment according to claim 1, wherein when the configuration determination unit derives the common configuration, the configuration determination unit derives, as the common configuration, a maximum common configuration that includes a module that is included in each virtual machine without overlap. apparatus. When the configuration determining unit determines that the virtual machine cannot be deployed based on a VM image corresponding to the minimum coverage configuration when the minimum coverage configuration is derived as the common configuration, the minimum coverage configuration is determined. The deployment device according to claim 2, wherein instead of a configuration, a maximum common configuration that is a configuration that includes modules that are included in each virtual machine in common is derived as the common configuration. The VM image, the physical server configuration information, and the deployment information transmitted from the deployment device according to claim 1 are received, and the VM image is used as the physical server configuration information. VM image duplicating means for duplicating according to the number of virtual machines deployed on the server device obtained based on
A server device comprising: module deployment means for deploying a software module to each of the replicated VM images using the deployment information so as to have a virtual machine configuration described in the physical server configuration information. The server device according to claim 5, wherein when deploying the software module, the module deploying unit deploys the software module by deleting an unnecessary module for each copied VM image. The server device according to claim 5, wherein when deploying the software module, the module deploying unit deploys the software module by additionally deploying a missing module for each replicated VM image. . Using an information processing device
Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine Deriving the configuration
Generating common configuration information representing the common configuration;
Generating a VM image including at least the common software module without duplication based on the common configuration information;
Based on the common configuration information and the physical server configuration information, generate deployment information including information necessary for deploying the VM image,
Transmitting the VM image, the physical server configuration information, and the deployment information to the server device;
In the server device,
Receiving the VM image, the physical server configuration information, and the deployment information;
Duplicating the VM image according to the number of virtual machines deployed on the server device, obtained based on the physical server configuration information,
A deployment method that deploys a software module to each replicated VM image using the deployment information so that the configuration of the virtual machine is described in the physical server configuration information. Based on physical server configuration information, which is information representing the configuration of each virtual machine deployed on the same server device and the configuration of software modules included in each virtual machine, at least a common software module common to each virtual machine A configuration determination process for deriving a configuration and outputting common configuration information representing the common configuration;
A VM image generation process for generating a VM image including at least the common software module without duplication based on the common configuration information;
A deployment information generation process for generating deployment information including information necessary for deploying the VM image based on the common configuration information and the physical server configuration information;
A computer program that causes a first computer to execute distribution control processing for transmitting the VM image, the physical server configuration information, and the deployment information to the server device. The server that has received the VM image, the physical server configuration information, and the deployment information transmitted from the first computer according to claim 9, and obtained the VM image based on the physical server configuration information VM image duplication processing for duplicating according to the number of virtual machines deployed in the device;
Module deployment processing for deploying a software module to each of the replicated VM images using the deployment information so that the configuration of the virtual machine described in the physical server configuration information is achieved in the second computer A computer program to be executed.

Images