JP2011175391A - Management computer and deployment method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a management computer that efficiently deploys a disk image in a server whose application environment is different, in introducing a server. <P>SOLUTION: A management server 102 is provided with: a storage device for storing a master image of a disk image in deploying it; an image acquisition part 202 for acquiring the disk image of a deployment source computer for creating the master image; an image distribution part 204 for deploying the master image to the deployment destination computer; and an image difference distribution part 205 for, when there is a difference between a designated application and an application included in the master image in deploying the master image to the deployment destination computer, deploying the image of the different application as an additional application after deploying the master image. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a management computer and a deployment method that can be efficiently deployed when a disk image is deployed to a different server such as an application environment when the server is introduced.

  Generally, when a server is introduced, it is necessary to install an operating system (OS), an application, and the like. At this time, deployment software is often used when a large number of servers are introduced. The deployment software has a function of operating on a management server different from the server on which the OS and applications are installed, and distributing (deploying) to the server on which the OS and applications are installed.

  Here, distribution (deployment) indicates copying image data in which an OS and applications created and stored in advance are installed to the disk of the target server. Patent Document 1 describes a method for generalizing deployment.

JP 2009-122963 A

  In the prior art of Patent Document 1, for example, if the software configuration (application environment) required for the deployment destination server (target server) is different, a disk image that depends on the software configuration is required. It was difficult to create a disk image. In addition, having a large number of disk images was difficult from the viewpoint of management.

  The present invention is an invention for solving the above-described problems, and provides a management computer and a deployment method that can be efficiently deployed when a disk image is deployed to a different server such as an application environment when the server is introduced. For the purpose.

  In order to achieve the above object, the management computer (for example, the management server 102) of the present invention is a management computer that deploys a disk image to the computer, and acquires the disk image of the deployment source computer (for example, the server device 104). An image acquisition unit that stores the acquired disk image as a master image in a storage device, an image distribution unit that deploys the master image to a deployment destination computer (for example, the server device 105), and a master image that is deployed to the deployment destination computer When the specified application is different from the application included in the master image, the image difference that deploys the image of the different application as an additional application after deploying the master image And having a distribution unit.

  According to the present invention, when a disk image is deployed to a different server such as an application environment when the server is introduced, it can be efficiently deployed.

1 is an overall configuration diagram showing a computer system of the present invention. It is a block diagram which shows the example of a management server. It is a block diagram which shows the example of a server apparatus. It is explanatory drawing in the case of deploying with respect to a server apparatus. It is explanatory drawing which shows the example of a server management table. It is explanatory drawing which shows the example of a driver application expansion management table. It is explanatory drawing which shows the example of a deployment management table. It is explanatory drawing which shows the example of an image management table. It is explanatory drawing which shows the example of a delivery management table. It is a flowchart which shows the process of an image acquisition part. It is a flowchart which shows the process of a structure information acquisition part. It is a flowchart which shows the process of a hardware configuration information acquisition agent. It is a flowchart which shows the process of OS * application information acquisition agent. It is a flowchart which shows the process of an image acquisition / image delivery agent. It is a flowchart which shows the process of an image delivery part. It is a flowchart which shows the process of an image difference delivery part.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is an overall configuration diagram showing a computer system of the present invention. The computer system includes a management server 102 (management computer), a storage device 101 (storage device), a server device 104 (for example, a deployment source computer), a server device 105 (for example, a deployment destination computer), an SVP (Service Processor) 117, a network A switch 103 is included. The management server 102 is a central device for controlling the computer system in this embodiment. The management server 102 includes a deployment management unit 108 and various tables (109 to 113) on the memory 201 (see FIG. 2). The management server 102 is connected to the storage apparatus 101 and is connected to the server apparatuses 104 and 105 and the SVP 117 via the network switch 103. The management server 102 communicates with the OS / application information acquisition agent 114 when the OS on the server devices 104 and 105 is operating. Servers such as the management server 102 and the server devices 104 and 105 are sometimes called computers.

  The various tables include a server management table 109 (see FIG. 5) that stores information on the server devices 104 and 105 connected to the network switch 103, and a driver that stores information on various drivers stored in the driver storage disk 107. Application development management table 110 (see FIG. 6), deployment management table 111 (see FIG. 7) that stores identification information such as the OS type of the server device to be deployed and the deployment target after deployment, the type of the created disk image, etc. There is an image management table 112 (see FIG. 8) for storing the above information as a master image, a distribution management table 113 (see FIG. 9) for storing identification information such as whether application image development is possible, and application size. The management server 102 has a function of acquiring images from the server devices 104 and 105 and deploying images to the server devices 104 and 105.

  The deployment of the present embodiment is an OS equivalent to the OS running on the image acquisition source server device (for example, the server device 104) by expanding the disk image 106 on the deployment destination server device (for example, the server device 105). And business programs are distributed to the deployment destination server device. The management server 102 has a function of creating a disk image obtained by imaging data from the server device 104 when acquiring a deployment image, and a function of deploying to the server device when deploying.

  A distribution destination server device that distributes a disk image is called an image distribution destination server device or a deployment destination computer, and the server device from which the distributed disk image is acquired is referred to as an image acquisition source server device or a deployment source computer. Call. Each server device may be an image acquisition source server device or an image distribution destination server device. The hardware configuration of each server device may be the same or different.

  As described above, the deployment of the present embodiment has a function of creating an image of the image acquisition source server device from the contents of the disk device in which the operating system (OS) running on the image acquisition source server device 104 is recorded. A function to save this in another disk device and copy it to the disk device of the image distribution destination server device when there is a deployment instruction from the user, and a function to set the unique information of the image distribution destination server device after copying Have.

  The unique information of the server device includes, for example, a computer name and an IP (Internet Protocol) address assigned to a NIC (Network Interface Card).

  The storage apparatus 101 has a disk image 106 for each image acquisition source server apparatus and a driver storage disk 107 for storing various device drivers. The driver storage disk 107 is a disk that stores drivers necessary for the operation of the OS. This is used for installing a driver lacking in the operation of the OS when the management server 102 deploys an image to the server device 105. The driver information file in the driver storage disk 107 contains information on the type of device supported by the driver, information on the device supported by the driver, the name of the device, and the like. By referring to the driver information file, the identifier of the device corresponding to each driver and information on the type of the device are acquired. The device type information here is, for example, “NIC” or “HBA” (Host Bus Adapter).

  The server apparatuses 104 and 105 have an operating environment such as a memory and a processor. The configuration of the server devices 104 and 105 will be described later with reference to FIG.

  The SVP 117 is connected to the management server 102 via the network switch 103, and has a function of notifying the management server 102 when the server devices 104 and 105 are turned ON / OFF or when a failure occurs in the server devices 104 and 105. . The SVP 117 can also manage the hardware configuration such as the memory capacity of the server devices 104 and 105, the UUID (Universally Unique IDentifier), the connected input / output interface, and the type of the processor. Information can also be transferred in response to a configuration information acquisition request.

  In this embodiment, an example is shown in which the management server 102 creates a disk image of the server device 104 and deploys the created image to another server device 105.

  FIG. 2 is a configuration diagram illustrating an example of the management server 102. Reference is made to FIG. 1 as appropriate. The management server 102 includes a memory 201, a processor 208, a network interface 209, and a disk interface 210. These network interface 209 and disk interface 210 are collectively referred to as devices, and may also be referred to as input / output devices and input / output interfaces.

  As described above, the memory 201 stores the server management table 109, the driver / application development management table 110, the deployment management table 111, the image management table 112, and the distribution management table 113. The deployment management unit 108 on the memory 201 includes an image acquisition unit 202, a configuration information acquisition unit 203, an image distribution unit 204, an image difference distribution unit 205, a hardware configuration information acquisition agent 206, and an image acquisition / image distribution agent 207. Composed.

  The processor stores various programs such as the image acquisition unit 202, the configuration information acquisition unit 203, the image distribution unit 204, the image difference distribution unit 205, the hardware configuration information acquisition agent 206, and the image acquisition / image distribution agent 207 stored in the memory 201. By executing this, image acquisition, configuration information acquisition, image distribution, hardware configuration information acquisition agent processing, and image acquisition / image distribution agent processing are performed.

  Each program such as the image acquisition unit 202, configuration information acquisition unit 203, image distribution unit 204, image difference distribution unit 205, hardware configuration information acquisition agent 206, image acquisition / image distribution agent 207, etc. It can also be replaced by hardware, for example, as an integrated circuit.

  The image acquisition unit 202 creates the disk image 106 of the server device 104. The disk image 106 is data in which the complete contents and structure of the file system are stored in one file. In normal image acquisition, boot information and partial / physical information locked by the OS 115 cannot be acquired. However, when a disk image is acquired, an image including all of them can be created.

  The configuration information acquisition unit 203 acquires hardware configuration information of the server devices 104 and 105 connected to the network switch 103.

  The image distribution unit 204 distributes the disk image 106 to various server devices. The image acquisition / image distribution agent 207 executes image acquisition / image distribution on a server device that is a target of image acquisition or image distribution. The image distribution unit 204 distributes the target information of the driver when the disk image 106 is different in the image distribution destination server device 105. The hardware configuration information acquisition agent 206 acquires information on the server device from which configuration information is acquired and transmits the information to the configuration information acquisition unit 203.

  The image difference distribution unit 205 performs image distribution on the server device that is the target of image distribution when there is a difference between the application installed in the server device 105 that is the image distribution destination and the application registered in the master image. Execute. Specifically, the image difference distribution unit 205 has a function of executing distribution of an application required after distribution for a master image to be described later, and executes the application when there is software not developed in the master image. Distribute (software).

  The server management table 109, the driver / application development management table 110, the deployment management table 111, the image management table 112, and the distribution management table 113 are held in the storage device 101 and stored in the memory 201 as necessary. May be.

  FIG. 3 is a configuration diagram illustrating an example of the server device 104. The server device 104 includes a memory 301, a processor 302, a network interface 303, a disk interface 304, and a BMC (Base board Management Controller) 116. The memory 301 stores an OS 115, an OS / application information acquisition agent 114, a business application 306, and the like, and is executed by the processor 302. A plurality of network interfaces 303 and disk interfaces 304 can be provided.

  The BMC 116 is connected to the SVP 117 (see FIG. 1) via a LAN (Local Area Network), and transfers configuration information and notifies a failure. Note that the BMC 116 can operate independently of the processor 302, and can notify the SVP 117 of a failure even when the processor 302 fails and becomes inoperable.

  The BMC 116 can perform power management in accordance with an external request. The BMC 116 monitors the abnormality by monitoring the signals of the temperature sensor and the voltage sensor installed in the server device 104, and has a function of returning the presence or absence of abnormality in response to an inquiry from the outside. Note that the BMC 116 is supplied with power from an auxiliary power source (not shown), which is different from the server device 104, so that it always functions even when the server device 104 is turned off.

  Devices connected to the disk interface 304 are connected to a built-in HDD (Hard Disk Drive), a storage device, or the like. The connected device is connected to the processor 302 via the disk interface 304, and stores the OS 115, the business application 306, and the like in a built-in HDD or storage device. When the server device 104 is activated, a necessary program is transferred to the memory. In the deployment in this embodiment, the OS 115 and the business application 306 are copied from the management server 102 to the internal disk 401 (see FIG. 4), and control is performed so that the OS 115 and the business application 306 operate normally.

  FIG. 4 is an explanatory diagram when deploying to the server apparatus 105. When the hardware configuration of the server device 104 that is the disk image acquisition source and the hardware configuration of the deployment destination server device 105 are the same, the management server 102 uses the disk image in the storage device 101 as the image distribution destination server device 105. Deploy to the internal disk 401 via the network switch 103.

  When there is a difference between the hardware configuration of the image acquisition source server device 104 and the hardware configuration of the image distribution destination server device 105, the management server 102 uses the disk image in the storage device 101 as the image distribution destination server device. After deploying to the internal disk 401 of 105 via the network switch 103, deployment is performed individually for different objects. The difference in hardware configuration refers to, for example, the types of the network interface 303 and the disk interface 304.

  In this embodiment, the disk image 106 of a certain server device 104 is stored in the storage device 101 and deployed to a plurality of deployment destination computers all at once, such as for a large scale out in a data center. Applicable. By comparing the hardware configuration with the hardware configuration of a plurality of deployment destination computers, it can be determined whether or not deployment is possible.

  FIG. 5 is an explanatory diagram showing an example of the server management table 109. A column 501 stores server identifiers. Here, an identifier is assigned to each server device. A column 502 stores a unique ID assigned to each server device. The column 503 stores the hardware type indicating the form of the server device such as a blade server or a tower server. The column 504 stores information on the CPU mounted on the server device, and the column 505 stores information on the memory capacity.

  The column 506 stores information on devices and connection methods, and stores the names of devices mounted on the server apparatus and the identifiers of devices having unique identifiers. Examples of identifiers unique to the device include a NIC MAC (Media Access Control address) address, an HBA WWN (World Wide Name), and the like. In the example shown in FIG. 5, the device includes “SAS (Serial Attached SCSI)”, “built-in HDD”, “FC ((Fibre Channel)”, etc., and “LAN1” and “LAN2” are stored as connection methods. ing.

  The column 507 stores OS information. Note that when new server information is added to the server management table 109, OS information is not recorded as information in the column 507.

  In FIG. 5, master servers (for example, master server 1 and master server 2) are also registered as hardware configuration information of the master image managed by the image management table 112 (see FIG. 8). That is, the master server can be said to be a virtual server stored as a master image.

  By having the server management table 109, the hardware configuration of the image distribution destination server device 105 when comparing the hardware configuration information of the master server and the hardware configuration information of the server device 105 of the image distribution destination at the time of deployment. Information can be acquired from the server management table 109. In addition, the management server 102 acquires the hardware configuration information of the server devices 104 and 105 connected via the network switch 103 by the configuration information acquisition unit 203 (see FIG. 2), and correctly holds it while updating it as needed. Can be managed.

  FIG. 6 is an explanatory diagram showing an example of the driver / application development management table 110. The driver / application development management table 110 is stored in the driver storage disk 107 and manages drivers and applications. A column 601 stores driver identifiers. A column 602 stores the type of OS corresponding to the driver. A column 603 stores device identifiers. For example, information such as NIC1 and NIC2 is stored. A column 604 stores a file storage position which is position information where the driver or application is stored. A column 605 stores development file information that is position information for developing the driver. A column 606 stores image information of the driver.

  The management server 102 acquires information from the driver information corresponding to the driver stored in the driver storage disk 107 and stores the information in the column. In addition, the management server 102 can acquire information related to the driver specified by the driver identifier via the Internet and store it in the column. The user can also register manually. By having the driver / application development management table 110, it is possible to manage device drivers stored in the driver storage disk 107.

  FIG. 7 is an explanatory diagram illustrating an example of the deployment management table 111. The deployment management table 111 stores information (columns 702 to 706) relating to the image distribution destination disk image identified by the deployment management identifier 701. A column 702 stores server identifiers. A column 703 stores an identifier of a master image that is master information. A column 704 stores device information that is driver information and its update presence / absence information (update flag). A column 705 stores a name that is application information to be used and distribution presence / absence information (distribution flag). Column 706 stores distribution destination designation presence / absence information (distribution destination flag). Unnecessary updates to the server management table 109 during image distribution can be suppressed based on distribution destination designation presence / absence information.

  Note that whether or not the column 704 is updated is set in S1510 of FIG. In addition, the setting of presence / absence of distribution in the column 705 is set in S1521 of FIG.

  The image distribution unit 204 and the image acquisition / image distribution agent 207 can uniquely specify the disk image 106 by the management server 102 referring to the deployment management table 111.

  FIG. 8 is an explanatory diagram showing an example of the image management table 112. The image management table 112 stores information regarding the environment of the image master acquired by the image acquisition unit 202. A column 801 stores a master image identifier. A column 802 stores the OS type information of the image. A column 803 stores driver information obtained for an image. A column 804 stores imaged application information (used application information). The storage location of each disk image 106 stored in the storage apparatus 101 is stored in association with each image identifier (master image identifier (see column 801)) in the image management table 112. Since the management server 102 has the image management table 112, not only the user (administrator) who instructs deployment but also the image distribution unit 204 and the image acquisition / image distribution agent 207 can uniquely specify the disk image 106. .

  FIG. 9 is an explanatory diagram showing an example of the distribution management table 113. The distribution management table 113 stores information regarding management of applications to be distributed. A column 901 stores application identifiers. A column 902 stores information such as whether image development is possible. Specifically, when “1”, the image is developed, when “2”, the image is not developed, and when “3”, the deployment management unit 108 automatically determines. Such a setting can suppress the capacity of the disk image by not forming an image when the capacity of the application is large and a plurality of disk images are covered. A column 903 stores whether or not silent installation is possible. Silent installation refers to no notification of a message or the like when software is installed on a server device. A column 904 stores information on whether individual settings are necessary for executing the software. A column 905 stores information indicating whether individual setting is necessary. The case where the individual setting is “Yes” corresponds to, for example, a case where hardware information setting necessary for operating the application is required.

  A column 906 stores application sizes. Although details will be described later (see FIG. 16), the application size is used when the image difference distribution unit 205 determines whether or not the master image includes an application that is highly likely to be used in common in the master image. Is done.

  FIG. 10 is a flowchart showing the processing of the image acquisition unit 202. The image acquisition unit 202 receives selection of the server device 104 that is an image acquisition target from the user (S1001). It communicates with an OS / application information acquisition agent on the OS of the server apparatus 104 that is an image acquisition target, and acquires and stores OS and application information (software configuration information) (S1002).

  The configuration information acquisition unit 203 acquires hardware configuration information from the server device 104 that is an image acquisition target (image acquisition source). The acquired configuration information is stored in the image acquisition source hardware configuration information (S1003). Details will be described with reference to FIG.

  The image acquisition unit 202 transfers the image acquisition / image distribution agent 207 to the server device 104 that is the image acquisition source, and the image acquisition / image distribution agent 207 operates on the server device 104 that is the image acquisition source, The created image transfer operation to the image acquisition unit 202 is executed (step 1004), and the process is terminated.

  The image acquisition / image delivery agent 207 acquires device driver information of the image acquisition source server device 104 and transfers it to the image acquisition unit 202 together with the disk image to be created. Alternatively, the image acquisition / image distribution agent 207 includes the disk image to be created and transfers it to the image acquisition unit 202.

  FIG. 11 is a flowchart showing the processing of the configuration information acquisition unit 203. The configuration information acquisition unit 203 powers on and starts the server device 104 from which configuration information is acquired (S1101), and responds to a network boot request from the server device 104 to target the hardware configuration information acquisition agent 206. Is transferred to the server device 104 (S1102). The configuration information acquisition unit 203 acquires the hardware configuration information of the target server device 104 from the hardware configuration information acquisition agent 206, stores it in the server management table 109 (S1103), and stores the hardware stored in the server management table 109. The configuration information (acquired information) is copied to the server management table 109 as master server information (S1104), and the process ends.

  By executing this flow, the hardware configuration information of the server device 104 and the function information of the mounted device can be stored in the server management table 109.

  Further, when the configuration information acquisition unit 203 is called by the image acquisition unit 202, the hardware configuration information of the server device 104 that is the image acquisition source, acquired by the same processing, is stored in the image acquisition source hardware configuration information. can do. As a result, the management server 102 can manage the hardware configuration information of all the server devices 104 and 105 connected via the network switch 103.

  FIG. 12 is a flowchart showing the processing of the hardware configuration information acquisition agent 206. The hardware configuration information acquisition agent 206 acquires the detailed information of the processors and memories of the server apparatuses 104 and 105 from which the hardware configuration information is acquired (S1201). Detailed information includes name, version, and the like.

  The hardware configuration information acquisition agent 206 determines whether all the information about the device has been acquired (S1202). If not acquired (S1202, No), the process returns to S1201. If it has been acquired (S1202, Yes), the hardware configuration information acquisition agent 206 transmits the acquired content of the device information mounted on the target server apparatuses 104 and 105 to the configuration information acquisition unit 203 of the management server 102. Transmit (S1203), and the process ends.

  By executing this flow, an operation of actually acquiring information is performed on the server apparatuses 104 and 105 that acquire hardware configuration information.

  FIG. 13 is a flowchart showing the processing of the OS / application information acquisition agent 114. The OS / application information acquisition agent 114 acquires the device setting information together with the OS information of the server device from which the software configuration information is acquired (S1301). The OS / application information acquisition agent 114 acquires information on the application installed in the target server device (S1302). The OS / application information acquisition agent 114 transmits the acquired information to the image acquisition unit 202 of the management server 102 (S1303).

  By executing this flow, an operation of actually acquiring information is performed on the server device 104 that acquires the software configuration information.

  FIG. 14 is a flowchart showing the processing of the image acquisition / image distribution agent 207. The image acquisition / image distribution agent 207 determines whether the processing request is an image acquisition request or an image distribution request (S1401). When the request is an image acquisition request (S1401, Yes), that is, when the image acquisition / image distribution agent 207 is called from the image acquisition unit 202, the process proceeds to S1402. The image acquisition / image distribution agent 207 acquires the image data of the disk that the image acquisition / image distribution agent 207 serves as the target server device in accordance with an instruction from the management server 102 (S1402), and the acquired image data is stored in the management server. The image is transferred to the image acquisition unit 202 (S1403), and the process ends.

  On the other hand, if the request is not image acquisition in step 1401 (S1401, No), that is, if the image acquisition / image distribution agent 207 is called from the image distribution unit 204, the process proceeds to step 1404. The image acquisition / image distribution agent 207 selects the disk image 106 in the storage apparatus 101 in accordance with the instruction from the deployment management unit 108, acquires the disk image included therein (S1404), and the image acquisition / image distribution agent 207 performs step. The disk image acquired in 1404 is copied to the disk (S1405), and the process ends.

  By executing this flow, the actual image acquisition and image distribution operations on the server devices 104 and 105 that are the targets of image acquisition and image distribution are executed.

  FIG. 15 is a flowchart showing the processing of the image distribution unit 204. When the image distribution unit 204 receives an image distribution request indicating which disk image 106 is deployed on which server device 105 (S1501), the image distribution unit 204 acquires configuration information of the image distribution destination (S1503). Specifically, in S1501, when the image distribution request for DP1, which is the management identifier shown in FIG. 7, is received, that is, when the deployment management table 111 is referenced using DP1 as a key, the server apparatus 105 that is the master information distribution destination is the server 1 It can be seen that the master image is the master image 1. In S1503, if the server 1 is registered in the server management table 109 of FIG. 5, the registered configuration information (for example, physical information such as CPU, memory, and device) is acquired. If it is not registered, it is acquired via the configuration information acquisition unit 203. As the configuration information of the master image 1, the configuration information of the master server 1 corresponding to the master image 1 is acquired with reference to FIG.

  The image distribution unit 204 refers to the column 706 of the deployment management table 111 in FIG. 7 to determine whether there is a distribution destination designation of the distribution destination server device 105 (S1513), and if there is (S1513, Yes), When the physical information such as CPU and memory is changed, the information is updated in the registered server management table 109 via the configuration information acquisition unit 203 (S1514), and the process proceeds to S1504. On the other hand, when the delivery destination is not designated (S1513, No), the process proceeds to S1504.

  In step S <b> 1504, the image distribution unit 204 refers to the server management table 109 and compares the hardware configuration information of the master server with the hardware configuration information of the image distribution destination server device 105. Are determined to be the same (S1505). If the comparison results are the same (S1505, Yes), the process proceeds to S1517. If they are not identical (S1505, No), the process proceeds to S1508.

  Specifically, in S1504, the hardware configuration information of the server 1 and the master server 1 in the server management table 109 is compared. If it is determined in S1505 that the CPU, memory, and device are not the same, step S1508 is executed. Migrate to

  In step S <b> 1508, the image distribution unit 204 confirms whether or not the contents of the devices being used match. If a difference is found in the contents of the device (S1508, No), the image distribution unit 204 sets whether or not to update the device (1510), and proceeds to S1509. Specifically, if there is a difference in the comparison result, the driver update presence / absence information in the deployment management table 111 is automatically set (for example, the update flag is set from 0 to 1). As a result, the image difference distribution unit 205 deploys the device whose update flag is 1. Note that the update presence / absence information can be changed by setting in advance by the user when it is desired to fix the version in a specific server device.

  In step S1509, the image distribution unit 204 determines whether all devices have been checked (S1509). If all checks have been completed (step S1509, Yes), the process proceeds to step S1517, and all checks have not been completed. In the case (No at Step S1509), the process returns to S1508.

  In step S1517, the image distribution unit 204 refers to the used application information (see the column 804 in the image management table 112 in FIG. 8) and the application information (see the column 705 in the deployment management table 111 in FIG. 7) to obtain the master image. And the software configuration of the distribution destination server device 105 are compared to determine whether the software configuration is the same (S1518). If the comparison results are the same (S1518, Yes), the process proceeds to S1506. When they are not the same (S1518, No), the process proceeds to S1519.

  In step S <b> 1519, the image distribution unit 204 determines whether the application information (see the column 705 in FIG. 7) of the distribution destination server device 105 is application information that exists only in the deployment management table 111. If the application information exists only in the deployment management table 111 (S1519, Yes), the image distribution unit 204 sets whether to distribute the application information (1521), and proceeds to S1520. If the application information does not exist only in the deployment management table 111 (S1519, No), the process proceeds to S1520.

  In S1520, the image distribution unit 204 determines whether all the application information in the deployment management table 111 has been checked (S1520). If all are checked (Yes in Step S1520), the process proceeds to S1506, and all are not checked. (Step S1520, No), it returns to S1519.

  Specifically, in S1517, the use application information of the master image 1 (see column 804 in FIG. 8) is “none”, and the application information of the server 1 (see column 705 in FIG. 7) is “A software”. is there. In S1518, it is determined that the software configuration is not the same. In S1519, it is determined that “A software” exists only in the deployment management table 111. In S1521, the distribution flag of “A software” is set from 0 to 1. .

  In step S1506, the image distribution unit 204 distributes the designated master image to the hard disk, and determines whether there is image difference distribution (S1507). At the time of determination, whether or not the driver information (see the column 704 in the deployment management table 111 in FIG. 7) is updated or not, and whether or not the application information (see the column 705 in FIG. 7) is distributed or not. Based on the determination. As a result of the determination, if it is determined that there is an image difference (S1507, Yes), the image difference distribution unit 205 is executed, and if it is determined that there is no image difference (S1507, No), the process ends.

  Specifically, in the case of distribution to the server 1 shown in FIG. 7, since the distribution flag of “A software” and the like is 1, the image distribution of “A software” is performed by the image difference distribution unit 205.

  FIG. 16 is a flowchart showing the processing of the image difference distribution unit 205. The image difference distribution unit 205 acquires information on which driver / application information is to be deployed from the image distribution unit 204 to the server device 105, deletes the driver with the update flag for initialization, and updates the update driver and application. The deployment is executed (S1601), and all the drivers / applications targeted for image difference distribution are checked (S1602). If all are checked (S1602, Yes), the process proceeds to S1603. If all are not checked (S1602, No), the process returns to S1601.

  In step S1603, the image difference distribution unit 205 refers to the column 902 of the distribution management table 113 in FIG. 9 and determines whether image development of the application distributed in step S1601 is possible. If image development is possible or automatic determination is possible (S1603, Yes), the process proceeds to S1604. If not (S1603, No), the process ends.

  In step S <b> 1604, the image difference distribution unit 205 refers to the column 705 shown in the deployment management table 111, and compares the total number of management identifiers registered in the deployment management table 111 with the application distributed in step S <b> 1601. It is determined whether the usage rate is 75% or more. The application usage rate is also the application rate of the application to the deployment destination computer managed by the management server 102, and delivery is specified for the total number of deployment destination computers registered in the deployment management table 111. It means the ratio of the number of computers where the target application is registered. When the usage rate is 75% or more (S1604, Yes), the process proceeds to S1605, and when the usage rate is less than 75% (S1604, No), the process ends.

  In step S1605, the image difference distribution unit 205 determines whether the application size of the application distributed in step S1601 is 500 MB (megabytes) or less. If it is 500 MB or less (S1605, Yes), the process proceeds to S1606. If it is larger than 500 MB (S1605, No), the process is terminated.

  In step S <b> 1606, image acquisition processing is executed via the image acquisition unit 202, the application image distributed to the disk image of the master image 1 is added, and the application application information in the column 804 of the image management table 112 is added to the application application information. Add a name.

  According to the present embodiment, the image difference distribution unit 205 has a relatively high application usage frequency and a relatively small application size (when deploying) in the master image of the image management table 112 (see FIG. 8). To ensure that the disk image capacity does not increase.

  The storage device (for example, the memory 201) of the present embodiment stores application information for each deployment destination computer as the deployment management table 111 (deployment management information), and the image difference distribution unit 205 adds an application (addition) Application) is required at a ratio of a predetermined value (for example, 75%) or more with respect to the total number of deployment destination computers registered in the deployment management information (step S1604), and the determination result is a predetermined value In the case of the above ratio, the image acquisition unit 202 can be instructed to include the image of the additional application in the master image (step S1606).

  In the storage device (for example, the memory 201) of the present embodiment, the application size for each application is stored as the distribution management table 113 (distribution management information), and the image difference distribution unit 205 is a target to be added to the master image. With reference to the distribution management information, if the additional application is a predetermined application size (for example, 500 MB) or more (step S1605), it can be determined not to be the additional application.

  The deployment method of the present embodiment is performed by a management computer (for example, the management server 102) having an image acquisition unit 202 that acquires a disk image from a deployment source computer and an image distribution unit 204 that deploys a disk image to a deployment destination computer. This is a deployment method that deploys the application required on the deployment destination computer.

  The image acquisition unit 202 acquires a disk image of the deployment source computer, holds the acquired disk image as a master image in a storage device (for example, the storage device 101), and the image distribution unit 204 stores the master image in the deployment destination computer. When an application required for deployment and a deployment destination computer is different from an application included in a master image, an image of a different application can be deployed as an additional application.

  In addition, the storage device stores application information for each deployment destination computer as deployment management information, and the image distribution unit 204 stores the additional application for the total number of deployment destination computers registered in the deployment management information. It is determined whether the image is required at a rate equal to or greater than a predetermined value, and if the determination result is a rate equal to or greater than the predetermined value, the image acquisition unit 202 can be instructed to include the image of the additional application in the master image.

  According to this embodiment, when deploying a disk image to a different server such as an application environment when the server is introduced, it can be efficiently deployed. Further, since the master image is used, there is an effect that a disk image for each hardware / software (application) configuration is not necessary. Further, since there is no deployment image for each hardware / software configuration, there is an effect that the data stored in the management server does not compress the disk capacity.

101 Storage device (storage device)
102 Management server (management computer)
103 Network switch 104 Server device (deployment source computer)
105 Server device (deployment destination computer)
106 Disk image 107 Driver storage disk 108 Deployment management unit 109 Server management table 110 Driver / application development management table 111 Deployment management table (deployment management information)
112 Image management table 113 Distribution management table (distribution management information)
114 OS / application information acquisition agent 115 OS
116 BMC
117 SVP
201, 301 Memory 202 Image acquisition unit 203 Configuration information acquisition unit 204 Image distribution unit 205 Image difference distribution unit 206 Hardware configuration information acquisition agent 207 Image acquisition / image distribution agent 208, 302 Processor 209, 303 Network interface 210, 304 Disk interface 306 Business application 401 Internal disk

Claims (5)

A management computer that deploys a disk image to a computer,
An image acquisition unit that acquires the disk image of a deployment source computer and stores the acquired disk image as a master image in a storage device;
An image distribution unit that deploys the master image to a deployment destination computer;
When deploying the master image to the deployment destination computer, if the specified application is different from the application included in the master image, the image of the different application is deployed as an additional application after the master image is deployed. A management computer. In the storage device, application information for each deployment destination computer is stored as deployment management information,
The image difference delivery unit
When it is determined whether the additional application is required at a ratio of a predetermined value or more with respect to the total number of deployment destination computers registered in the deployment management information, and the determination result is a ratio of a predetermined value or more The management computer according to claim 1, wherein the image acquisition unit is instructed to include the image of the additional application in the master image. The storage device stores an application size for each application as distribution management information, and the image difference distribution unit includes:
The application as a target to be added to the master image is referred to the distribution management information, and if the additional application is larger than a predetermined application size, the application is not set as the additional application. Management computer. In a management computer having an image acquisition unit for acquiring a disk image from a deployment source computer and an image distribution unit for deploying the disk image on a deployment destination computer, the deployment method deploys an application required on the deployment destination computer. And
The image acquisition unit
Obtaining the disk image of the deployment source computer, holding the obtained disk image as a master image in a storage device;
The image distribution unit
Deploying the master image to the deployment destination computer, and deploying the image of the different application as an additional application when the application required for the deployment destination computer is different from the application included in the master image. A deployment method characterized by In the storage device, application information for each deployment destination computer is stored as deployment management information,
The image distribution unit
When it is determined whether the additional application is required at a ratio of a predetermined value or more with respect to the total number of deployment destination computers registered in the deployment management information, and the determination result is a ratio of a predetermined value or more The deployment method according to claim 4, wherein the image acquisition unit is instructed to include the image of the additional application in the master image.

Images