Program deployment apparatus and method

• US 7,890,613 B2
• Filed: 08/14/2008
• Issued: 02/15/2011
• Est. Priority Date: 05/19/2008
• Status: Expired due to Fees

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Takamoto, Yoshifumi, Tameshige, Takashi
• Primary Examiner(s): Winder; Patrice L
• Assistant Examiner(s): BILGRAMI, ASGHAR H
• Application Number:
  US12/191,767
• Publication Number:
  US 20090287799A1
• Time in Patent Office: 915 Days
• Field of Search: 709/222, 709/220, 709/223
• US Class Current: 709/220
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/64 Retargetable

Abstract

With a management server that is connected via a network to at least one physical server including a physical server with a virtualization facility for providing a virtual server to a client and deploys a program to the at least one physical server as necessary, and by a program deployment method for such a management server for deploying a program to the at least one physical server as necessary, there is provided units for detecting one or more nodes which are any of the physical server, the virtualization facility, and the virtual server and connected via the network, acquiring first configuration information about a virtual layer of each detected node for each detected node, and selectively deploying the program to the relevant node based on the first configuration information for each acquired node.

Claims

1. A management server connected, via a first network, to one or more physical servers that are connected to a storage apparatus via a second network, at least one of the physical servers being a physical server with a virtualization facility for providing a virtual server to a client, the management server comprising:

a detection unit for detecting one or more nodes which are any of the physical servers, the virtualization facility, and the virtual server and connected via the first network;

an acquisition unit for acquiring, for each node detected by the detection unit, first configuration information about a virtual layer of the node; and

a deployment unit for deploying a program to each node based on the first configuration information for each node that is acquired by the acquisition unit,

wherein, the deployment unit;

detects a topology for each node based on the first configuration information corresponding to the node,

does not deploy the program to the physical server on which the virtual server is active or defined, does not deploy the program to the virtualization facility and the physical server which are incompatible with the program, but deploys the program to the physical server on which the virtualization facility is inactive and the virtual server corresponding to the physical server on which the virtualization facility is inactive, and

the management server manages, via the deployed program, the physical server on which the virtualization facility is inactive and the virtual server corresponding to the physical server on which the virtualization facility is inactive.

2. The management server according to claim 1, wherein the acquisition unit acquires second configuration information for each node detected by the detection unit about the type of operation system mounted on the node;

and

the deployment unit decides the type of program to be deployed to the node based on the second configuration information corresponding to the node.

3. The management server according to claim 1, wherein the acquisition unit acquires third configuration information for each node detected by the detection unit about a service for which the node is used;

and

the deployment unit decides the type of the program to be deployed to the node based on the third configuration information corresponding to the node.

4. The management server according to claim 1, wherein the acquisition unit stores a table in which at least one piece of information from among:

an information acquisition source for acquisition of the first configuration information for the virtualization facility, a method for identifying the virtualization facility, and a communication protocol for connection with the information acquisition source is registered for each type of virtualization facility; and

when judging the type of virtualization facility, the acquisition unit attempts, for each type of virtualization facility stored in the table, access to the information acquisition source according to the communication protocol and identification processing by the identification method, and then judges the type of virtualization facility based on the success of the attempt.

5. The management server according to claim 1, wherein the deployment unit judges, based on license information of the program, whether the program can be deployed or not.

6. The management server according to claim 1, wherein the deployment unit deploys the program by establishing connection to the node by a connection method used when the acquisition unit acquires the first configuration information from the node to which the program is to be deployed.

7. A management server method performed by a management server connected, via a first network, to one or more physical servers that are connected to a storage apparatus via a second network, at least one of the physical servers being a physical server with a virtualization facility for providing a virtual server to a client, the management server method comprising:

a first step of detecting one or more nodes which are any of the physical servers, the virtualization facility, and the virtual server and connected via the first network;

a second step of acquiring, for each detected node, first configuration information about a virtual layer of the node; and

a third step of deploying a program to each node based on the first configuration information for each node acquired in the second step,

wherein, the third step includes;

detecting a topology for each node based on the first configuration information corresponding to the node, and

not deploying the program to the physical server on which the virtual server is active or defined, not deploying the program to the virtualization facility and the physical server which are incompatible with the program, but deploying the program to the physical server on which the virtualization facility is inactive, and the virtual server corresponding to the physical server on which the virtualization facility is inactive, and

the management server manages, via the deployed program, the physical server on which the virtualization facility is inactive and the virtual server corresponding to the physical server on which the virtualization facility is inactive.

8. The management server method according to claim 7, wherein in the second step, second configuration information about the type of operation system mounted on the node is acquired for each detected node;

and

in the third step, the type of program to be deployed to the node is decided based on the second configuration information corresponding to the node.

9. The management server method according to claim 7, wherein in the second step, third configuration information about a service for which the node is used is acquired for each detected node;

and

the type of program to be deployed to the node is decided based on the third configuration information corresponding to the node.

10. The management server method according to claim 7, wherein in the second step, when judging the type of virtualization facility based on a table in which at least one piece of information from among:

an information acquisition source for acquisition of the first configuration information for the virtualization facility, a method for identifying the virtualization facility, and a communication protocol for connection with the information acquisition source is registered for each type of virtualization facility, access to the information acquisition source according to the communication protocol and identification processing by the identification method are attempted for each type of virtualization facility stored in the table, and then the type of virtualization facility is judged based on the success of the attempt.

11. The management server method according to claim 7, wherein in the third step, whether the program can be deployed or not is judged based on license information of the program.

12. The management server method according to claim 7, wherein in the third step, the program is deployed to the node by establishing connection to the node by a connection method used when acquiring the first configuration information from the node to which the program is to be deployed.