METHOD, APPARATUS, AND COMPUTER PRODUCT FOR MANAGING OPERATION

- FUJITSU LIMITED

A system resource manager of a site management server registers a server domain as a group of servers having a uniform physical wire connection, registers a server group as a group of servers that use uniform software in a registered server domain, and changes an application of a server by controlling a switch of software that is stored in a RAID device connected to a server belonging to a registered server group via a SAN for each application and that is used by the server.

Skip to: Description  ·  Claims  · Patent History  ·  Patent History
Description

This is a divisional of application Ser. No. 11/787,759, filed Apr. 17, 2007, which is a continuation filed under 35 U.S.C. §111(a), of International Application No. PCT/JP2004/015384, filed Oct. 18, 2004.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a technology for managing an operation of resources constituting an information processing system, with a capability of enabling an administrator to perform a change of resource application with ease and efficiency in a large-scale information processing system including a large number of resources such as servers.

2. Description of the Related Art

Conventionally, in an information processing system formed by connecting resources such as servers via a network, there has been developed a technique for changing an application of a server by switching software to be transferred to the server when the server is booted.

For example, Japanese Patent Laid-open Publication No. 2003-22190 discloses a multi-booting method of a system for changing a content of a boot program transferred from a boot disk, every time each server is booted, to operate the server in various environments.

However, in the conventional technology, when there is a plurality of servers to be used by changing the application, there has been difficulty in managing switching of these applications.

That is, the software needs to be switched individually relative to each server, thereby causing a problem in that it is burdensome to an administrator of the information processing system. Particularly, when a size of the information processing system increases and the number of servers increases, execution of the switching of the software becomes even more difficult.

Accordingly, in a large-scale information processing system including a large number of servers, it is an important issue as to how easily and efficiently an administrator can change the application of the server.

SUMMARY OF THE INVENTION

It is an object of the present invention to at least partially solve the problems in the conventional technology.

A computer-readable recording medium according to one aspect of the present invention stores therein a computer program for managing an operation of resources constituting an information processing system, the computer program causing a computer to execute group registering including registering a resource group as a group of resources that use uniform software; and changing a usage of a resource by controlling switching of a software used by a resource that belongs to the resource group registered at the group registering.

A method of managing an operation of resources constituting an information processing system, according to another aspect of the present invention, includes group registering including registering a resource group as a group of resources that use uniform software; and changing a usage of a resource by controlling switching of a software used by a resource that belongs to the resource group registered at the group registering.

An apparatus for managing an operation of resources constituting an information processing system, according to still another aspect of the present invention, includes a group registering unit that registers a resource group as a group of resources that use uniform software; and an application changing unit that changes an application of a resource by controlling switching of a software used by a resource that belongs to the resource group registered by the group registering unit.

The above and other objects, features, advantages and technical and industrial significance of this invention will be better understood by reading the following detailed description of presently preferred embodiments of the invention, when considered in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram of resource operation management;

FIG. 2 is an explanatory diagram of a concept of a repurposing process according to an embodiment;

FIG. 3 depicts a functional configuration of a resource operation management system according to the embodiment;

FIG. 4 is a flowchart of an allocation process procedure of a server to a task;

FIG. 5 is an example of site data in which information of an operation management server is registered;

FIG. 6 is an example of domain management server data in which information of a domain management server is registered;

FIG. 7 is an example of management subnet data in which information of a subnet to be managed is registered;

FIG. 8 is an example of middleware-cooperation IF data that stores a command for executing various processes in cooperation with middleware;

FIG. 9 is an example of server domain data that stores information of a server domain, which is a domain to which the server belongs;

FIG. 10 is an example of pool group data in which information of a pool group is stored;

FIG. 11 is an example of storage domain data in which information of a storage domain is stored;

FIG. 12 is an explanatory diagram for explaining a network domain and a network sub-domain;

FIG. 13 is an example of network sub-domain data in which information of a network sub-domain is stored;

FIG. 14 is an example of network domain data in which information of a network domain is stored;

FIG. 15 is an example of load-distributing apparatus data in which information of a load distributing apparatus is stored;

FIG. 16 is an explanatory diagram for explaining a configuration example of a network sub-group;

FIG. 17 is an example of network sub-group data in which information of a network sub-group is stored;

FIG. 18 is an example of inter-server-domain link data, in which information of correspondence between the server domains is stored;

FIG. 19 is an example of inter-server/storage domain link data, in which information of correspondence between the server domain and the storage domain is stored;

FIG. 20 is an example of network boot-server data in which information of the server that performs network boot is stored;

FIG. 21 is an example of management-target server data in which data of the server to be managed is stored;

FIG. 22 is an example of provisioning configuration data in which information of a group to which the server belongs is stored;

FIG. 23 is an example of connections of servers and a storage device having a uniform connection state;

FIG. 24 is an explanatory diagram of a uniformity checking process of the connection based on WWPN;

FIG. 25 is an example of storage template data in which data of a storage template is stored;

FIG. 26 is an example of server group data in which information of a server group is stored;

FIG. 27 is an example of server/storage group link data in which information of a storage group corresponding to a server group is stored;

FIG. 28 is an example of inter-server-group link data in which information of correspondence between the server groups is stored;

FIG. 29 is an example of load distribution group data in which group information of the load distributing apparatus is stored;

FIG. 30 is an example of network group data in which information of a network group is stored;

FIG. 31 is a flowchart of a setting process procedure for setting a logical volume to a RAID device;

FIG. 32 is an example of a setting screen of the logical volume;

FIG. 33 is an example of RAID-level setting data in which setting information of a RAID level is stored;

FIG. 34 is an example of RAID device data in which information of the RAID device is stored;

FIG. 35 is an example of provisioning configuration data in which storage sub groups are set;

FIG. 36 is a flowchart of a setting process procedure of the logical volume, for the server to recognize the logical volume;

FIG. 37 is an explanatory diagram for explaining a setting process of the logical volume constructed by the RAID device;

FIG. 38 is an example of affinity group data in which information of an affinity group is stored;

FIG. 39 is an example of multipath configuration data in which information of a multipath configuration is stored;

FIG. 40 is an example of mirror volume configuration data in which information of a mirror volume configuration is stored;

FIG. 41 is an example of IP address management data in which information of an IP address allocated to the server is stored;

FIG. 42 is an example of software image management data in which information of software images is stored;

FIG. 43 is an example of software-distribution image management data in which information of software distribution images is stored;

FIG. 44 is an example of snapshot management data in which information of snapshots is stored;

FIG. 45 is a flowchart of a process procedure for adding a server to the server group;

FIG. 46 is an example of distribution management data in which information of a distribution status of software distribution images is stored;

FIG. 47 is a flowchart for explaining a presetting process procedure according to the repurposing process;

FIG. 48 is a flowchart of a repurposing process procedure;

FIG. 49 is an example of repurposing setting data in which information of repurposing setting is stored;

FIG. 50 is an example of repurposing operation data in which information of server status is stored;

FIG. 51 is an example of schedule setting data in which schedule information for executing the repurposing process is stored;

FIG. 52 is an example of repurposing setting data in which at least one server group is set to each state;

FIG. 53 is a hardware configuration of a computer, which is a site management server shown in FIG. 3;

FIG. 54 is a hardware configuration of a computer, which is a domain management server shown in FIG. 3; and

FIG. 55 is a hardware configuration of a computer, which is a server shown in FIG. 3.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention are explained in detail below with reference to the accompanying drawings. The present invention is not limited to the embodiments.

A concept of server operation management according to an embodiment is explained first. FIG. 1 is a conceptual diagram of operation management of resources such as servers and storages, and FIG. 2 is an explanatory diagram of a concept of a repurposing process according to present the embodiment. The repurposing process is for automatically switching an application of the server.

In FIG. 1, a case is depicted in which information processing apparatuses such as web servers 41 to 49, AP (application) servers 51 to 56, DB (database) servers 61 to 63, and storages 71 to 79 are used for each of tasks 1 and 2.

The web servers 41 to 49 are servers that provide contents to be browsed by web browsers to client terminals via the Internet. The AP servers 51 to 56 are servers that take over execution of information processes requested by the web servers 41 to 49 that have received an information processing request from a user.

DB servers 61 to 63 are server devices that manage an access to a database, when an access request to the database is received from the AP servers 51 to 56. Storages 71 to 79 are storage units connected to the Web servers 41 to 49, the AP servers 51 to 56, and the DB servers 61 to 63 via a network, which constitutes a SAN (storage area network).

In a resource operation management process according to the present invention, in a LAN (local area network) or the SAN, resource groups of the server and the storage, in which a physical connection state between other devices is uniform with each other, are managed as domains.

For example, in the case shown in FIG. 1, server groups used for the tasks 1 and 2 are managed as a web domain 4, an AP domain 5, and a DB domain 6, while a storage group used for the tasks 1 and 2 is managed as a storage domain 7.

In this case, the web servers 41 to 49 that belong to the web domain 4 have uniform connections to other devices, the AP servers 51 to 56 that belong to the AP domain 5 have uniform connections to other devices, the DB servers 61 to 63 that belong to the DB domain 6 have uniform connections to other devices, and the storages 71 to 79 that belong to the storage domain 7 have uniform connections to other devices.

With the operation management, unused ones of the web servers 41 to 49, the AP servers 51 to 56, the DB servers 61 to 63, and the storages 71 to 79 are registered to a pool 3 for each domain. The web servers 41 to 49, the AP servers 51 to 56, the DB servers 61 to 63, and the storages 71 to 79 are assigned to each of the tasks 1 and 2 as appropriate.

For example, in the example of FIG. 1, the web servers 42 and 43, the AP server 51, the DB server 61, and the storage 77 are assigned to the task 1, while the web server 49, the AP servers 52 and 53, the DB server 62, and the storages 78 and 79 are assigned to the task 2.

If load on the web servers 42, 43, 49, the AP servers 51, 52, 53, and the DB servers 61, 62 assigned to the tasks 1 and 2 increases, or if storage capacity of the storages 77 to 79 is not enough, the web servers 41, 44 to 48, the AP servers 54 to 56, the DB server 63, and the storages 71 to 76 registered to the pool 3 are added as servers available for the task.

Specifically, by introducing a software required for the web servers 41, 44 to 48, the AP servers 54 to 56, and the DB server 63 registered to the pool 3 and automatically executing setting of the network and the like, the web servers 41, 44 to 48, the AP servers 54 to 56, and the DB server 63 are added as the servers available for the task.

When adding the storages 71 to 76, the storages 71 to 76 are added as the storages 71 to 76 available for the task by automatically executing setting of logical volumes and setting of the network for the storages 71 to 76.

For example, in FIG. 1, the web server 44 that was registered to the pool 3 is added to the web domain 4 of the task 2.

Moreover, according to the resource allocation management method, if the web servers 42, 43, 49, the AP servers 51 to 53, the DB servers 61, 62, or the storages 77 to 79 used for the tasks 1 and 2 are not used for a long time, the web servers 42, 43, 49, the AP servers 51 to 53, the DB servers 61, 62, and the storages 77 to 79 are excluded from the servers available for the task and registered to the pool 3.

The web servers 42, 43, 49, the AP servers 51 to 53, the DB servers 61, 62, and the storages 77 to 79 registered to the pool 3 are to be used if the load on the web servers 42, 43, 49, the AP servers 51 to 53, and the DB servers 61, 62, used for other tasks 1 and 2 increases or if the storage capacity of the storages 77 to 79 is not enough.

Specifically, by deleting the software introduced to the web servers 42, 43, 49, the AP servers 51 to 53, and the DB servers 61, 62 and automatically changing setting of the network and the like, the web servers 42, 43, 49, the AP servers 51 to 53, and the DB servers 61, 62 are excluded from the servers available for the tasks 1 and 2 and registered to the pool 3.

Moreover, to exclude the storages 77 to 79 from the storages available for the tasks 1 and 2 and to register them to the pool 3, by automatically executing setting of the network to the storages 77 to 79, the storages 77 to 79 can be excluded from the storages available for the tasks 1 and 2 and registered to the pool 3.

For example, in FIG. 1, the AP server 52 that was registered to the pool 3 is excluded from the servers available for the task in the AP domain 5 of the task 2, and it is registered to the pool 3. The server 54 registered to the pool 3 is reused in such a case that the load on the server 51 used for the task 1 increases, and it is added to the task 1.

As shown in FIG. 2, in the repurposing process, the application of the server is automatically switched according to a time zone. In FIG. 2, servers 8c1 and 8c2 belonging to a pool group 8c are added to a DB server group 8a belonging to a DB domain during daytime of weekday. The DB server group 8a is a group of servers that store data in the database in the DB domain.

The servers 8a1 and 8a2 added to the DB server group 8a are booted by network boot from DB server boot disks 9a1 and 9a2, in which DB server software is stored, and provided to a task.

The servers 8a1 and 8a2 added to the DB server group 8a are returned to the pool group 8c during nighttime and holidays and added to a batch server group 8b. The batch server group 8b is a group of servers that perform a batch process in the DB domain.

Servers 8b1 and 8b2 added to the batch server group 8b are booted by network boot from batch server disks 9b1 and 9b2, in which batch server software is stored, and provided to the task.

Thus, in the repurposing process, the server group is registered as a group of servers using uniform software, and the switching of the software used by the servers belonging to the registered server group is controlled. Accordingly, even in the large-scale information processing system including a large number of servers, a change of server application can be performed by the administrator with ease and efficiency by managing the servers in a unit of server group.

A functional configuration of the resource operation management system according to the present embodiment is explained. FIG. 3 depicts a functional configuration of the resource operation management system according to the embodiment.

As shown in FIG. 3, in the operation management system, an operation management client 10 is connected to a site management server 20 via an FW (firewall) 30 over a network. The site management server 20 is connected over the network to domain management servers 50 and 60 via an FW 40.

Furthermore, the site management server 20 is connected over the network to a router 80 that belongs to an edge domain 180 via the FW 40. The site management server 20 is also connected over the network to storages 160a to 160c that belong to a storage domain 220, and to a storage 160d that is pooled via the FW 40.

The domain management server 50 is connected over the network to an SLB (server load balancer) 100 and to servers 110a to 110c that belong to a web domain 190.

Furthermore, the domain management server 60 is connected over the network to an FW 120, an SLB 130, servers 140a to 140c that belong to an AP domain 200, servers 150a to 150c that belong to a DB domain 210.

The storages 160a to 160c that belong to the storage domain 220, and the storage 160d that is pooled are also connected via a SAN 170 to the servers 110a to 110c that belong to the web domain 190, the servers 140a to 140c that belong to the AP domain 200, and the servers 150a to 150c that belong to the DB domain 210.

In this case, the operation management client 10 is a client terminal that receives various requests related to resource management from an administrator and transmits information to the site management server 20, and that receives various output results from the site management server 20 and displays the output results on a monitor or the like.

The site management server 20 executes the resource operation management process and the repurposing process explained in FIGS. 1 and 2 in cooperation with domain management servers 50 and 60. The site management server 20 has respective function units of a system resource manager 21, a server RM (resource manager) 22, a software RM (resource manager) 23, a network RM (network) 24, a storage RM (resource manager) 25, a system resource DB (database) 26, and an AP (application)-management control unit 27.

The system resource manager 21 receives various pieces of setting information related to the resource operation management process from the operation management client 10 and executes the resource setting process and the repurposing process in cooperation with the server RM 22, the software RM 23, the network RM 24, and the storage RM 25. The system resource manager 21 controls transfer of data between the domain management servers 50 and 60.

The server RM 22 is a managing unit that performs a boot and a shutdown of each of the servers 110a to 110c, 140a to 140c, and 150a to 150c, a collection of information about hardware, a setting, and the like. The server RM 22 performs the above processes in cooperation with a server sub RM (resource manager) 52 of the domain management server 50, and a server RM agent 112a of the server 110a.

The software RM 23 is a managing unit that performs software installation, setting, collection of information about the software, and the like for each of the servers 110a to 110c, 140a to 140c, and 150a to 150c. The software RM 23 performs the above processes in cooperation with a software sub RM (resources manager) 53 of the domain management server 50, and a software RM agent 113a of the server 110a.

The network RM 24 is a managing unit that performs information collection, setting, and the like related to the network. The network RM 24 performs the above processes in cooperation with a network sub RM (resource manager) 54 of the domain management server 50, and a network RM agent 114a of the server 110a.

The storage RM 25 is a managing unit that performs information collection, setting, and the like related to the storages 160a to 160c that belong to the storage domain 220, and relate to the storage 160d that is pooled. The storage RM 25 manages the storages 160a to 160c and the storage 160d pooled without involving the domain management servers 50 and 60.

The system resource DB 26 is a database that contains various resource information managed by the system resource manager 21, the server RM 22, the software RM 23, the network RM 24, and the storage RM 25. Details of stored data are explained later.

The AP-management control unit 27 is a processing unit that controls and manages an AP (application) managing unit 116a. More specifically, the AP-management control unit 27 sends a request for executing process related to an application such as installation and setting to the AP managing unit 116a. Functions of the AP-management control unit 27 are realized by executing middleware installed on the site management server 20.

The domain management servers 50 and 60 are servers that manage resources in a domain or a plurality of domains. The domain management server 50 includes a system resource domain manager 51, the server sub RM 52, the software sub RM 53, the network sub RM 54, and a domain resource DB (database) 55.

The domain management server 60 includes the same function units as the function units of the domain management server 50, and therefore, the function units of the domain management server 60 are not shown in FIG. 3 and explanations thereof are omitted.

The system resource domain manager 51 is a managing unit that performs information collection, setting process, and the like related to resources that belong to each of the domains in cooperation with the server sub RM 52, the software sub RM 53, and the network sub RM 54.

Furthermore, the system resource domain manager 51 performs data reception and data transmission to and from networking equipment such as the site management server 20, an FW 90, and the SLB 100, as well as to and from the servers 110a to 110c to be managed.

The server sub RM 52 is a managing unit that performs boot, shutdown, collection of information about hardware, setting, and the like in cooperation with the server RM 22 and the server RM agent 112a.

The software sub RM 53 is a managing unit that performs software installation, setting, collection of information about software, and the like for each of the servers 110a to 110c in cooperation with the software RM 23 and the software RM agent 113a.

The network sub RM 54 is a managing unit that performs information collection, setting, and the like related to a network in cooperation with the network RM 24 and the network RM agent 114a.

The domain resource DB 55 is a database that stores therein information acquired from the servers 110a to 110c and the system resource DB 26, when the server sub RM 52, the software sub RM 53, or the network sub RM 54 collects various information or specifies settings related to the servers 110a to 110c to be managed. In addition, the domain resource DB 55 stores therein a virtual OS (operating system) used for network boot of the servers 110a to 110c.

The router 80 is networking equipment that performs routing of data packets in data communication via the Internet 70. The FWs 30, 40, 90, and 120 are networking equipments that prevent unauthorized access to each of the servers 110a to 110c, 140a to 140c, and 150a to 150c.

The SLBs 100 and 130 are load balancers that distribute and transfer information-processing requests for the servers 110a to 110c or 140a to 140c to a plurality of the servers 110a to 110c or 140a to 140c. Although switches are also connected in upstream sides and downstream sides of the SLBs 100 and 130, the switches are not shown in FIG. 3.

The servers 110a to 110c, 140a to 140c, and 150a to 150c are servers that perform various information processes. The server 110a includes a resource manager agent 111a, the server RM agent 112a, the software RM agent 113a, the network RM agent 114a, a storage RM agent 115a, and the AP managing unit 116a.

The servers 110b, 140a, 140b, 150a, and 150b include the same function units as those of the server 110a. Therefore, the function units of the servers 110b, 140a, 140b, 150a, and 150b are not shown in FIG. 3, and explanations thereof are omitted.

The servers 110c, 140c, and 150c are servers that are pooled, and do not include each of the resource manager agent 111a, the server RM agent 112a, the software RM agent 113a, the network RM agent 114a, the storage RM agent 115a, and the AP managing unit 116a.

When the server 110c, 140c, or 150c is set as a server available for tasks, a computer program that realizes each of the function units is installed on the server 110c, 140c, or 150c and is executed to realize each of the function units.

The resource manager agent 111a is an agent that receives a request for executing process such as setting and information collection from the domain management server 50 of the system resource domain manager 51 for the server 110a, and performs processes in cooperation with the server RM agent 112a, the software RM agent 113a, the network RM agent 114a, and the storage RM agent 115a.

The server RM agent 112a is an agent that performs a boot and a shutdown of the server 110a, a collection of information about hardware, a setting, and the like. The software RM agent 113a is an agent that performs software installation, setting, and collection of information about software for the server 110a.

The network RM agent 114a is an agent that performs information collection, setting, and the like related to a network connected to the server 110a. The storage RM agent 115a is an agent that performs information collection, setting, and the like related to a storage connected to the server 110a.

The storages 160a to 160c are storages used by the servers 110a to 110c that belong to the web domain 190, the servers 140a to 140c that belong to the AP domain 200, and the servers 150a to 150c that belong to the DB domain 210. The storage 160d is a storage that is pooled. The storages 160a to 160d are constituted of RAID devices.

A VLAN (virtual local area network) is set as a network that connects between the servers 110a to 110c that belong to the web domain 190, the servers 140a to 140c that belong to the AP domain 200, and the servers 150a to 150a that belong to the DB domain 210.

A processing procedure of a server assigning process to a task as described in FIG. 1 is explained next. FIG. 4 is a flowchart of a processing procedure for assigning a server to a task.

In the following explanation, it is assumed that an operation management program is previously installed on the site management server 20, which causes the site management server 20 to perform functions of the system resource manager 21, the server RM 22, the software RM 23, the network RM 24, the storage RM 25, the system resource DB 26, and the AP-management control unit 27.

Furthermore, a program is previously installed on the domain management servers 50 and 60, which causes the domain management servers 50 and 60 to perform functions of the system resource domain manager 51, the server sub RM 52, the software sub RM 53, and the network sub RM 54.

Moreover, programs are previously installed on each of the servers 110a, 110b, 140a, 140b, 150a, and 150b, which cause the servers 110a, 110b, 140a, 140b, 150a, and 150b to perform functions of the resource manager agent 111a, the server RM agent 112a, the software RM agent 113a, the network RM agent 114a, the storage RM agent 115a, and the AP managing unit 116a.

As shown in FIG. 4, the system resource manager 21 of the site management server 20 performs a registering process of an operation management server and a management-LAN (step S101). The operation management server and the management-LAN are the site management server 20, the domain management server 50, and the LAN used for managing management target resources such as the servers 110a to 110c, 140a to 140c, and 150a to 150c, and the SAN 170.

The process performed at step S101 is explained in detail below. FIG. 5 is a diagram of an example of site data 300 registered as information on an operation management server. The site data 300 contains information on site name, site management server name, and domain management server name.

The site name is information for identifying a site that includes a resource to be managed. The site management server name is information for identifying the site management server 20 set to manage the site. The domain management server name is information for identifying the domain management servers 50 and 60 set to manage domains set in the site.

FIG. 6 is a diagram of an example of domain management server data 310 registered as information on the domain management servers 50 and 60. The domain management server data 310 contains information on domain management server name and management subnet name.

The domain management server name is the same information as the domain management server name explained in connection with FIG. 5. The management subnet name is information for identifying a subnet (a management subnet) in which a resource is to be managed by the domain management servers.

FIG. 7 is a diagram of an example of management subnet data 320 registered as information on subnets to be managed. The management subnet data 320 contains information on management subnet name, network address, netmask, and default gateway.

The management subnet name is the same information as the management subnet name explained in connection with FIG. 6. The network address is a network address for identifying the management subnet. The netmask is a netmask that defines which bits in an IP address are to be used as the network address. The default gateway is information on an IP address for identifying a default gateway used for transmitting data to outside the management subnet.

At step S101, the system resource manager 21 receives information on site, site management server, and domain management server, set by a user by operating the operation management client 10, and registers received information to the site data 300 shown in FIG. 5.

The system resource manager 21 receives information on domain management server and management subnet, which are set by the user by operating the operation management client 10, and registers received information to the domain management server data 310 shown in FIG. 6.

Thereafter, the system resource manager 21 registers information on network address, netmask, and default gateway, corresponding to the management subnet explained in FIG. 6, to the management subnet data 320 shown in FIG. 7.

In addition, the system resource manager 21 notifies the AP-management control unit 27 of occurrence of an event such as addition to or deletion from the servers 110a to 110c, 140a to 140c, and 150a to 150c, and sets commands for executing various processes in cooperation with the AP-management control unit 27.

FIG. 8 is a diagram of an example of middleware cooperation IF data 330 including commands for performing various processes in cooperation with middleware. The middleware cooperation IF data 330 contains information on middleware name, target event, timing, location, and execution command.

The middleware name is information on middleware with which the system resource manager 21 performs processes. The target event is information on events that the system resource manager 21 requests the middleware to execute. The timing is information on timing at which the system resource manager 21 transmits a request for executing processes to the middleware (before or after a process for the target event)

The location is information on locations where a command of the middleware (a “manager” or an “agent”) is execute. The “manager” indicates that the command is executed on the site management server 20, while the “agent” indicates that the command is executed on the servers 110a to 110c, 140a to 140c, and 150a to 150c to be managed. The execution command is information on commands that notifies the middleware of occurrence of various events.

Referring back to FIG. 4, the system resource manager 21 performs a domain creating process and a linking process between created domains (step S102). The processes performed at step S102 is explained in detail below.

FIG. 9 is a diagram of an example of server domain data 340 stored as information on server domains to which the servers 110a to 110c, 140a to 140c, and 150a to 150c belong.

The server domain data 340 contains information on server domain name, server architecture name, and management subnet name. The server domain name is information for identifying a domain to which the servers 110a to 110c, 140a to 140c, and 150a to 150c belong.

The server architecture name is information for identifying CPU (Central Processing Unit) architecture of the servers 110a to 110c, 140a to 140c, and 150a to 150c that belong to each of the server domains. The management subnet name is the same information as the management subnet name shown in FIG. 6.

At step S102, the system resource manager 21 receives information on settings of the server domains and the server architectures specified by the administrator by operating the operation management client 10, and registers received information to the server domain data 340. The server domains are set in units of the management subnet set at step S101.

Furthermore, at step S102, the system resource manager 21 sets server groups that belong to each of the server domains, and sets pool groups shared between the server groups and pool groups exclusive to specific server groups.

In this case, the server group is created by classifying servers in the same server domain into one or more groups. The pool group is a pool of the servers assigned to each of the server groups.

FIG. 10 is a diagram of an example of pool group data 350 stored as information on pool groups. The pool group data 350 contains information on pool group name, type, and server domain name.

The pool group name is information for identifying a pool of each of the above described servers. The type is information that indicates whether the pool group is to be shared by a plurality of the server groups or to be exclusively permitted for usage by specific server groups. The server domain name is the same information as the server domain name explained in connection with FIG. 9.

The system resource manager 21 assigns the pool group to each of the server domains. When the server domain includes a plurality of the sever groups, the system resource manager 21 assigns the pool group exclusive to the server groups.

Thereafter, the system resource manager 21 receives information on storage domains set by the administrator by operating the operation management client 10, and registers received information to the system resource DB 26 as storage domain data 360 explained below.

FIG. 11 is a diagram of an example of the storage domain data 360 stored as information on storage domains. The storage domain data 360 contains information on storage domain name and redundancy of path. The storage domain name is information for identifying a set storage domain. The redundancy of path is information on redundancy of a data communication path on the SAN.

Furthermore, the system resource manager 21 receives information on a network sub domain set by the user by operating the operation management client 10, and registers the information on the system resource DB 26 as network sub-domain data 470 described below.

In this case, the network sub domain is a sub domain obtained by dividing a network domain to which a plurality of network devices connecting servers that belong to different server domains belong.

FIG. 12 is a schematic diagram for explaining a network domain and network sub domains. In FIG. 12, switches 430a, 430b, 450a, and 450b and SLBs 460a and 460b are depicted, which connect servers 380a to 380e that belong to a web domain 370 to servers 400a to 400e that belong to an AP domain 390.

Switches 430a and 430b constitute a “Web-Back” network sub-domain 420, and switches 450a and 450b constitute an “AP-Front” network sub-domain 440.

The “Web-Back” network sub-domain 420, the “AP-Front” network sub-domain 440, the SLBS 460a and 460b constitute a “Web-AP” network domain 410.

FIG. 13 is a diagram of an example of the network sub-domain data 470 stored as information on network sub domains. The network sub-domain data 470 contains information on network sub domain name, switch model, and switch management IP.

The network sub domain name is information for identifying the network sub domain explained in connection with FIG. 12. The switch model is information on a switch model that belongs to the network sub domain. The switch management IP is information on an IP address assigned to each of the switches for a management.

The system resource manager 21 receives information on the network domain set by the user by operating the operation management client 10, and registers the information on the system resource DB 26 as network domain data 480 described below.

FIG. 14 is a diagram of an example of the network domain data 480 stored as information on network domains. The network domain data 480 contains information on network domain name, front network sub-domain name, connection system, device name, back network sub-domain name, and redundancy system.

The network domain name is information for identifying the network domain explained in connection with FIG. 12. The front network sub-domain name is information for identifying a sub domain closer to the Internet 70, when the network domain is divided into two sub domains by the SLBs 460a and 460b as a border.

The connection system is information on a system for connecting the network devices, such as the switches 430a and 430b that belong to the front network sub-domain, to the network devices, such as the switches 450a and 450b that belong to the back network sub-domain. For example, the above systems can include a system requiring a load balancer for a connection and a system requiring a firewall for a connection. The device name is information for identifying the network device.

The back network sub-domain name, as shown in FIG. 12, is information for identifying a network sub-domain closer to the Internet 70, when the network domain is divided into the two network sub-domains by the SLBs 460a and 460b as a border. The redundancy system is information that indicates a redundancy system if the data communication path is redundant on the network domain.

Moreover, the system resource manager 21 receives information on a connection device for the network sub domain set by the user by operating the operation management client 10, registers the information on the system resource DB 26 as load distributing apparatus data 490 described below. The connection device for the network sub domain indicates devices such as the SLBs 460a and 460b described in FIG. 12.

FIG. 15 is a diagram of an example of the load distributing apparatus data 490 stored as information on load distributing apparatuses. The load distributing apparatus data 490 contains information on load distributing apparatus name, management IP, model, SNMP community, and ID/password

The load distributing apparatus name is a name for identifying a connection device for the network sub domain. The management IP is information on an IP address assigned to each of the connection devices for administrating the connection device. The model is information on a model of the connection device.

The SNMP (Simple Network Management Protocol) community is information for identifying an SNMP community to which the domain management servers 50 and 60 and the site management server 20 that manage the connection devices, and an SNMP community to which the connection devices belong. The ID/password is information on an ID and a password required for accessing the connection devices.

The system resource manager 21 receives information on the network sub group set by the user by operating the operation management client 10, registers the information on the system resource DB 26 as network sub-group data 660 described below.

In this case, the network sub group is a plurality of networks obtained by dividing the networks connecting between server groups that belong to different server domains.

FIG. 16 is a schematic diagram for explaining a configuration of network sub groups. In FIG. 16, switches 590 and 610, and SLBs 600a and 600b are depicted, which connect servers 520a to 520e that belong to a web domain 510 to servers 560a to 560e that belong to an AP domain 550.

Servers 520a and 520b constitute an “A_Web” server group 530, servers 520c and 520d constitute a “B_Web” server group 540, servers 560a and 560b constitute an “A_AP” server group 570, and servers 560c and 560d constitute a “B_AP” server group 580.

A network that connects the “A_Web” server group 530 with an SLB 600a constitute an “A_Web-Back” network server group 620, a network that connects the “B_Web” server group 540 with an SLB 600b constitute an “B_Web-Back” network sub-group 630, a network that connects the SLB 600a with the “A_AP” server group 570 constitute an “A_AP_Front” network sub-group 640, and a network that connects the SLB 600b with the “B_AP” server group 580 constitute a “B_AP_Front” network sub-group 650.

FIG. 17 is an example of the network sub-group data 660 in which information of the network sub-group is stored. The network sub-group data 660 stores network sub-group names, network sub-domain names, and information of subnets and subnets for redundancy.

The network sub-group name is identification information for identifying the network sub-group explained in FIG. 16. Network sub-domain name is identification information for identifying the network sub-domain, to which the network sub-group belongs.

The subnet is information on a network address and a subnet mask assigned to the network sub group. The subnet for redundancy is information on the network address and the subnet mask assigned to the network constituted of a redundant data communication line added as an extra, when the network that belongs to the network sub group is made redundant using a plurality of data communication lines.

After that, the system resource manager 21 receives information on association between server domains set by the user by operating the operation management client 10, registers the information on the system resource DB 26 as inter-server-domain link data 670 described below.

FIG. 18 is a diagram of an example of the inter-server-domain link data 670 stored as information on correspondence relations between server domains. The inter-server-domain link data 670 contains information on front server domain name, network domain name, and back server domain name.

The front server domain name is identification information for identifying the server domain closest to the Internet 70 side, of the server domains putting the network domains therebetween as shown in FIG. 12. The network domain name is identification information of the network domain explained in FIG. 12. The back server domain name is information indicating the server domain farthest from the Internet 70, of the server domains putting the network domains therebetween as shown in FIG. 12.

Moreover, the system resource manager 21 receives information on association between server domain and storage domain set by the user by operating the operation management client 10, and registers the information on the system resource DB 26 as inter-server/storage-domain link data 680 described below

FIG. 19 is a diagram of an example of the inter-server/storage-domain link data 680 stored as information on correspondence relations between server domains. The inter-server/storage-domain link data 680 contains information on server domain name and storage domain name. The server domain name is information equivalent to the server domain shown in FIG. 9. The storage domain name is information equivalent to the storage domain shown in FIG. 11.

Referring back to FIG. 4, the system resource manager 21 performs a registering process of server resources and storage resources to be managed (step S103). The process performed at step S103 is explained in detail below.

When a user operates the operation management client 10 to select the management subnet to which the server is to be registered, the system resource manager 21 receives information of the management subnet selected by the user.

The system resource manager 21 also receives information on servers to be managed, which is input by the user by operating the operation management client 10, from the operation management client 10, and stores received information in the domain resource DB 55 of the domain management server 50 as network boot server data 690 explained below. Subsequently, the servers registered are network booted, and registered as the server resources after various information on the severs are acquired.

FIG. 20 is a diagram of an example of the network boot server data 690 stored as information on network boot servers. The network boot server data 690 contains information on MAC address, IP address, and host name.

The MAC address is information on a MAC address of the server. The IP address is information on an IP addresses assigned to the server. The host name is information on a host name assigned to the server.

In this case, upon receiving information on MAC address of the network boot server input by the user, the system resource manager 21 automatically assigns the IP address and the host name to the server corresponding to the MAC address.

The system resource manager 21 performs network boot on the server to which the IP address and the host name are assigned, by using the virtual OS stored in the domain resource DB 55 of the domain management server 50, in cooperation with the system resource domain manager 51 of the domain management server 50.

The server sub RM 52, the resource manager agent 111a, and the server RM agent 112a work together to collect information on hardware of the server and transmit collected information to the system resource domain manager 51.

Thereafter, the system resource manager 21 acquires information on hardware of the server from the system resource domain manager 51, and stores acquired information in the system resource DB 26 as management target server data 700 explained below.

When the user inputs, by operating the operation management client 10, setting information indicating whether SAN boot is to be performed, in which a server is booted by the storages 160a to 160d connected via the SAN 170, the system resource manager 21 receives the setting information and registers the setting information on the management target server data 700.

FIG. 21 is a diagram of an example of the management target server data 700 stored as information on servers to be managed. The management target server data 700 contains information on server name, IP address, MAC address, server architecture, model, SAN boot, and status.

The server name identifies the server to be managed. IP address is allocated to the server. The MAC address is a MAC address of the server. The server architecture name is identification information of CPU architecture of the server. The model name is information indicating a type of the server. The SAN boot is setting information indicating whether to perform SAN boot for booting the server from the storages 160a to 160d connected via the SAN 170. The status is information indicating if there is an abnormality in the server.

Although it is assumed herein that the user specifies the MAC address of a network boot server, the server can be automatically selected. Specifically, when the user sets information that specifies the number of servers to be automatically selected by operating the operation management client 10, the system resource manager 21 receives the information from the operation management client 10.

The system resource manager 21 selects servers of specified number, and registers information on an IP address and a host name of the servers on the network boot server data 690 shown in FIG. 20.

In cooperation with the system resource domain manager 51 in the domain management server 50, the system resource manager 21 performs network boot on the servers assigned the IP address and the host name using the virtual OS stored in the domain resource DB 55 in the domain management server 50.

With the cooperation of the server sub RM 52, the resource manager agent 111a, and the server RM agent 112a, information on the MAC address, server architecture, model, and status of each server is collected and transmitted to the system resource domain manager 51.

After that, the system resource manager 21 obtains the information on the MAC address, server architecture, model, and status of each server from the system resource domain manager 51. The system resource manager 21 stores the information in the system resource DB 26 as the management target server data 700.

Subsequently, the system resource manager 21 registers a storage device to be managed. Examples of the storage device include FC (Fiber Channel) switch and RAID device.

Specifically, when the user inputs information on the IP address of a storage to be registered as a management target with respect to each management subnet shown in FIG. 7, the system resource manager 21 receives the information from the operation management client 10. The system resource manager 21 stores information on a storage device corresponding to the IP address in the system resource DB 26, thereby registering the storage device.

After that, the system resource manager 21 adds the servers registered on the management target server data 700 shown in FIG. 21 to a server domain. Specifically, when the administrator specifies a server and a server domain where the server is to be added by operating the operation management client 10, the system resource manager 21 receives the information on the server and the server domain from the operation management client 10.

Referring to the management target server data 700 shown in FIG. 21, the system resource manager 21 checks whether the server architecture of the server matches server architecture registered on the server domain data 340 shown in FIG. 9.

The system resource manager 21 retrieves the management target server data 700 shown in FIG. 21, and checks that SAN boot is to be performed on the server.

Moreover, the system resource manager 21 checks a wire connection status of the network of the server that is added to the server domain. Specifically, the system resource manager 21 reads the inter-server-domain link data 670 shown in FIG. 18, acquires information on a front server domain and a back server domain for the server domain.

The system resource manager 21 reads the network domain data 480 shown in FIG. 14, and acquires information on a front server domain and a back server domain corresponding to the network domain.

After that, the system resource manager 21 reads the network sub-domain data 470 shown in FIG. 13, and identifies a switch corresponding to the front sub domain and the back sub domain.

The system resource manager 21 requests the network RM 24 and the network sub RM 54 to check wire connections between servers and switches. In addition, the network RM 24 and the network sub RM 54 request the network RM agent 114a to check the wire connections between servers and switches, and acquire a check result.

When no error occurs in the wire connections between servers and switches, the system resource manager 21 associates information on the server with the pool group explained in connection with FIG. 10, and stores the information provisioning configuration data 710 in the system resource DB 26.

FIG. 22 is a diagram of an example of the provisioning configuration data 710 stored as information on groups to which servers belong. The provisioning configuration data 710 contains information on server name, pool group name, server group name, storage sub-group name, and accessibility.

The server name is the same information as described in connection with FIG. 21. The pool group name is the same information as described in connection with FIG. 10. The server group name is information for identifying a server group when servers on the same server domain are classified into one or more groups. At this point, information on the server group name has not been registered.

The storage sub-group name is information for identifying a storage group when storages on the same storage domain are classified into one or more groups and assigned to each server in the server group. At this point, information on the storage sub-group name has not been registered. The accessibility is information that indicates whether a server is allowed to access storages. At this point, information on the accessibility has not been registered.

After registering the saver name and the pool group name on the provisioning configuration data 710, the system resource manager 21 registers the storage device, which has been previously registered, on a storage domain.

Specifically, when the user specifies, by operating the operation management client 10, a storage domain and a storage device registered on the storage domain, the system resource manager 21 receives the information from the operation management client 10.

The system resource manager 21 reads the inter-server/storage-domain link data 680 shown in FIG. 19, and identifies the server domain corresponding to the storage domain.

Moreover, the system resource manager 21 checks uniformity of wire connections between servers that belong to the specified server domain and storage devices that belong to the storage domain, in corporation with the storage RM 25 and the storage RM agent 115a.

FIG. 23 is a diagram of an example of wire connections between servers and storage devices having uniform connections. In this example, as shown in FIG. 23, a wire connection between an FC switch 750a that belongs to a storage domain 740 and servers 730a and 730b that belong to a server domain 720, and a wire connection between an FC switch 750b that belongs to the storage domain 740 and the servers 730a and 730b are uniform.

In addition, a wire connection between the FC switches 750a and 750b and a RAID device 760a that belongs to the storage domain 740, and a wire connection between the FC switches 750a and 750b and a RAID device 760b that belongs to the storage domain 740 are uniform.

The system resource manager 21 performs the uniformity check of the above wire connections based on information on WWPN (world wide port name). At this check, the system resource manager 21 reads information on redundancy of a storage domain path from the storage domain data 360 shown in FIG. 11, and performs a redundancy check. FIG. 24 is a diagram for explaining a processing of checking a connection uniformity based on WWPN.

In FIG. 24, there depicted RAID device WWPN data 770a and 770b that are stored in the RAID devices 760a and 760b shown in FIG. 23, FC switch WWPN data 780a and 780b that are stored in the FC switches 750a and 750b, and server WWPN data 790a and 790b that are stored in the servers 730a and 730b.

The RAID device WWPN data 770a and 770b contains information on CA (channel adapter) and WWPN. The CA is information for identifying a channel adapter included in the RAID devices 760a and 760b. The WWPN is information on WWPN assigned to the channel adapter included in the RAID devices 760a and 760b.

The FC switch WWPN data 780a and 780b contains information on port and other side WWPN. The port is information for identifying ports of the FC switches 750a and 750b. The other side WWPN is information on WWPN assigned to the channel adapter of the RAID devices 760a and 760b connected to the ports of the FC switches 750a and 750b, or information on WWPN assigned to an HBA (host bus adapter) of the servers 730a and 730b connected to the ports of the FC switches 750a and 750b.

The server WWPN data 790a and 790b contain information on HBA and WWPN. The HBA is information for identifying an HBA included in the servers 730a and 730b. The WWPN is information on WWPN assigned to the HBA included in the servers 730a and 730b.

The system resource manager 21 can check the uniformity of a wire connection between devices by collecting the RAID device WWPN data 770a and 770b, the FC switch WWPN data 780a and 780b, and the server WWPN data 790a and 790b from the RAID devices 760a and 760b, the FC switches 750a and 750b, and the servers 730a and 730b, and by checking the associations of WWPN.

After that, the system resource manager 21 registers a storage area having an LUN (logical unit) set in advance and a storage area having an unset LUN, as storages for a pool.

Subsequently, the system resource manager 21 performs processing of creating a server group (step S104). The processing performed at step S104 are explained in detail below.

The system resource manager 21 receives information on a storage template set by the user by operating the operation management client 10, and registers the information on the system resource DB 26 as storage template data 800 described below. The storage template is setting information on configuration of later created storage for server group.

FIG. 25 is a diagram of an example of the storage template data 800 stored as information on storage templates. The storage template data 800 contains information on storage template name, disk type, disk name, reliability need, load level, disk capacity, and boot disk.

The storage template name is identification information for identifying an established storage template. The disk type is information on a type of an application of the disk included in the storage template.

For example, “root” denotes that the disk is used to store therein system data, “local” denotes that the disk is used to store therein individual server data, and “shared” denotes that the disk is used to store therein shared data among servers.

The disk name is a name for identifying a disk, and assigned to each of the disks. The reliability need is information on a reliability needed for the disk. The load level is information on a load level on the disk. The disk capacity is a storage capacity of the disk. The boot disk is information on whether the disk is used to boot a system.

Subsequently, the system resource manager 21 receives information on server groups that are set by a user by operating the operation management client 10, and stores the information in the system resource DB 26 as server group data 810 explained below.

FIG. 26 is a diagram of an example of the server group data 810 stored as information on server groups. The server group data 810 contains information on server group name, server domain name, software distribution image name, revision, storage template name, SAN boot, and auto recovery.

The server group name is identification information for identifying a group, if servers included in the same server domain are classified into one or a plurality of groups. The server domain name is identification information on a server domain to which server groups belong. The software distribution image name is information for identifying an image file in software distributed to the server that belongs to the server group.

The version is information on a version of a software distribution image. The storage template name is same information as the storage template explained in connection with FIG. 25. The SAN boot is information on whether a SAN boot of the servers that belongs to the server group is performed. The auto recovery is information on whether a process of adding a server is automatically executed when a failure occurs in a server having a scale-out configuration in which a plurality of servers cooperatively work.

The system resource manager 21 registers information of a storage group corresponding to the server group in the system resource DB 26 as server/storage group link data 820. The storage group is obtained by dividing the storage included in the same storage domain into one or a plurality of groups.

FIG. 27 is a diagram of an example of the server/storage group link data 820 stored as information on storage groups corresponding to the server groups. The server/storage group link data 820 contains information on server group name, storage group name, and storage domain name.

The server group name is the same information as the server group shown in FIG. 26. The storage group name is identification information for identifying a storage group that is created correspondingly with respect to each of the server groups. The storage domain name is identification information for identifying a storage domain to which the storage group belongs.

At the time of creating the storage group, the system resource manager 21 retrieves information on a storage template associated with the server group from the server group data 810 shown in FIG. 26, and retrieves information on a disk type corresponding to the storage template from the storage template data 800 shown in FIG. 25.

The system resource manager 21 creates the storage group with respect to each of disk types such as “root”, “local”, and “shared” with respect to each of the server groups, and registers the information on the server/storage group link data 820.

Furthermore, the system resource manager 21 retrieves information on a storage domain corresponding to the server domain to which the server group belongs from the inter-server/storage-domain link data shown in FIG. 19, and registers the information on the server/storage group link data 820.

After that, the system resource manager 21 transmits a command for causing the AP managing unit 116a to recognize that the server group is added to the AP managing unit 116a. Specifically, the system resource manager 21 transmits “issvgrp add” shown in FIG. 8 to the AP managing unit 116a.

Subsequently, the system resource manager 21 receives information on correspondence relations among the server groups that are set by the user by operating the operation management client 10, and registers the information on the system resource DB 26 as inter-server-group link data 830 explained below.

FIG. 28 is a diagram of an example of the inter-server-group link data 830 stored as information on the correspondence relations among the server groups. The inter-server-group link data 830 contains information on front server group name, network group name, and back server group name.

The front server group name is identification information for identifying a server group closer to the Internet 70 among server groups that are linked via the network group. In this case, the network group denotes a network group consisting of a combination of the network sub groups that link the server groups as explained in connection with FIG. 16.

The network group name is identification information for identifying the network group. The back server group name is identification information for identifying a server group located more distant from the Internet 70 among server groups that are linked via the network group.

The system resource manager 21 stores information on the network group in the system resource DB 26 as network group data 850 explained below.

Specifically, the system resource manager 21 retrieves the inter-server-domain link data 670 shown in FIG. 18, and obtains information on a network domain that is set to be sandwiched between two server domains.

The system resource manager 21 retrieves the network domain data 480 shown in FIG. 14, and obtains information on a front sub domain, a back sub domain, and a device those corresponding to the network domain.

Furthermore, the system resource manager 21 retrieves the network sub-group data 660 shown in FIG. 17, searches a network sub domain corresponding to the front sub domain and the back sub domain from the network sub-group data 660, and extracts an unused network sub group out of network sub groups corresponding to the searched network sub domain.

Subsequently, the system resource manager 21 classifies a network device corresponding to the information on a device retrieved from the network domain data 480 shown in FIG. 14 into one or a plurality of groups, and stores the information in the system resource DB 26 as load distribution group data 840 explained below.

FIG. 29 is a diagram of an example of the load distribution group data 840 stored as information on groups of load distributing apparatuses. The load distribution group data 840 contains information on load distribution group name, load balancer name, and representative IP.

The load distribution group name is information for identifying a group, if a load balancer is classified into one or a plurality of groups. The load balancer name is a name for identifying a load balancer. The representative IP is information on an IP address assigned to each of the load distribution groups.

After that, the system resource manager 21 stores, based on information on a correspondence relation between the network domain, the network sub-group, and the load distribution group belonging to each of the network groups, the information in the system resource DB 26 as the network group data 850.

FIG. 30 is a diagram of an example of the network group data 850 stored as information on the network groups. The network group data 850 contains information on network group name, network domain name, front network sub-group name, load distribution group name, and back network sub-group name.

The network group name is the same information as the network group explained in connection with FIG. 28. The network domain name is the same information as the network domain explained in connection with FIG. 18.

The front network sub-group name corresponds to the network sub-group name explained in connection with FIG. 17, and is identification information for identifying a network sub group closer to the Internet 70 among network sub groups sandwiching the load distribution groups.

The load distribution group name is the same information as the load distribution group name explained in connection with FIG. 29. The back network sub-group name corresponds to the network sub-group name explained in connection with FIG. 17, and is identification information for identifying a network sub group more distant from the Internet 70 among network sub groups sandwiching the load distribution groups.

Furthermore, the system resource manager 21 sets up VLAN of the network sub group in a switch that is registered on the network sub-domain data 470 shown in FIG. 13 in cooperation with the network RM 24 and the network sub RM 54.

Subsequently, the system resource manager 21 adds a first server into the server group, and performs a process of creating a software image of software that is installed on the server (step S105). The process at step S105 is explained in detail below.

First, if the user specifies a server and a server group where the server is registered by operating the operation management client 10, the system resource manager 21 receives information on the server and the server group and registers the server on the server group.

The system resource manager 21 retrieves the server group data 810 shown in FIG. 26, searches a storage template corresponding to the server group, and obtains a setting condition of the storage template from the storage template data 800 shown in FIG. 25.

The storage RM 25 sets up such a logical volume that fulfills the setting condition of the storage template obtained by the system resource manager 21 to a pooled storage, and performs a process of assigning the storage in which the logical volume is set to the server group.

FIG. 31 is a flowchart of a processing procedure of a setting process of setting a logical volume to a RAID device. As shown in FIG. 31, the system resource manager 21 obtains information on a necessary condition for the logical volume (step S201). In this case, the necessary condition indicates information on reliability need, load level, and disk capacity those stored in the storage template data 800 shown in FIG. 25.

FIG. 32 is a diagram of an example of a setting screen for setting a logical volume. In FIG. 32, there are described a necessary-condition output screen 860 on which the necessary condition for outputting the logical volume from the system resource manager 21 to the operation management client 10 is displayed and a logical-volume-configuration output screen 880 after setting the logical volume.

In the example shown in FIG. 32, a case is described in which three logical volumes that fulfill three necessary conditions needs to be created. Three necessary conditions 870a to 870c are output onto the necessary-condition output screen 860.

Referring back to FIG. 31, the system resource manager 21 determines a RAID level of the RAID device depending on the reliability need and the load level (step S202). FIG. 33 is a diagram of an example of RAID-level setting data 940 stored as information on settings of RAID-levels.

The RAID-level setting data 940 contains information on reliability need, load level, and RAID level. The reliability need is the same information as the reliability need explained in connection with FIG. 25. The load level is the same information as the load level explained in connection with FIG. 25. The RAID level is information on a RAID level that is determined depending on the reliability need and the load level.

Referring back to FIG. 31, the system resource manager 21 determines a model of the RAID device based on a total amount of a required disk capacity (step S203). FIG. 34 is a diagram of an example of RAID device data 950 stored as information on the RAID device.

The RAID device data 950 contains information on total amount of required disk capacity, RAID device model, data access speed, the number of disk drives configuring RAID group (in a case of RAID 0+1), the number of disk drives configuring RAID group (in a case of RAID 5), and the maximum number of RAID groups.

The total amount of required disk capacity is information on a total amount of a disk capacity required for a logical volume. The RAID device model is information on a model of a RAID device appropriate for ensuring the total amount of the required disk capacity.

The data access speed is information on a data access speed of a disk drive that is specified by the RAID device model. The data access speed contains information on three types of the “first”, “second”, and “third” disk drives in order of data access speed.

The number of disk drives configuring RAID group (in a case of RAID 0+1) is information on the number of disk drives configuring a RAID group in the case of RAID 0+1. The number of disk drives configuring RAID group (in a case of RAID 5) is information on the number of disk drives configuring a RAID group in the case of RAID 5. The maximum number of RAID groups is information on the maximum number of RAID groups to be created.

Referring back to FIG. 31, the system resource manager 21 obtains unique information with respect to each of the RAID device models from the RAID device data 950 as explained in FIG. 34 (step S204).

In this case, the unique information is information on a type of the “first” disk drive out of the data access speed, the number of disk drives configuring the RAID group (in the case of RAID 0+1), the number of disk drives configuring the RAID group (in the case of RAID 5), and the maximum number of the RAID groups.

Then, the storage RM 25 creates a logical volume (step S205). Specifically, the storage RM 25 creates such a logical volume that fulfills each of the necessary conditions of the logical volume, and sets up the logical volume in the RAID device.

On the logical-volume-configuration output screen 880 shown in FIG. 32, a case is described in which logical volumes 910a to 910d and 920a to 920e that fulfill each of necessary conditions 900a to 900c are set in a RAID device 890.

Referring back to FIG. 31, the storage RM 25 creates a RAID group in which the logical volumes are grouped by each of RAID levels (step S206). Then, the storage RM 25 assigns a logical volume to the created RAID group (step S207).

In the example shown in FIG. 32, the logical volumes 910a to 910d that fulfill the necessary conditions 900a and 900b have the same RAID level of RAID 0+1, and thus the logical volumes 910a to 910d are grouped into a RAID group 930a. In addition, the logical volumes 920a to 920e that fulfill the necessary condition 900c have the same RAID level of RAID 5, and thus the logical volumes 920a to 920e are grouped into a RAID group 930b.

Upon creating the RAID groups, the storage RM 25 sets disk drives that belong to each of the RAID groups to disk drive types determined based on the data access speed of the RAID device data 950 shown in FIG. 34.

Furthermore, the storage RM 25 sets the number of disk drives that configure a RAID device to the number of disk drives determined based either on the number of disk drives configuring the RAID group (in the case of RAID 0+1) or the number of disk drives configuring the RAID group (in the case of RAID 5) those included in the RAID device data 950 shown in FIG. 34.

Furthermore, the storage RM 25 creates such RAID groups that the number of the RAID groups is below the maximum number of the RAID groups included in the RAID device data 950 shown in FIG. 34.

On the logical-volume-configuration output screen 880 shown in FIG. 32, the logical volumes 910a to 910d and 920a to 920e, which fulfill the necessary conditions 900a to 900c and are respectively assigned to the RAID groups 930a and 930b, are respectively connected to the corresponding necessary conditions 900a to 900c by lines.

Referring back to FIG. 31, the storage RM 25 creates a command file that reflects the configuration of the logical volumes shown in FIG. 32 to the RAID device (step S208). Then, the storage RM 25 reflects the created logical volume to the actual apparatus based on the command file (step S209).

After that, the system resource manager 21 registers the logical volume set in the RAID device as a storage sub group by associating the logical volume with server groups to which each of servers belongs, and sets an access right to the server groups of the servers. Specifically, the system resource manager 21 stores information on server group, storage sub group, and availability of access in the provisioning configuration data 710 shown in FIG. 22.

FIG. 35 is a diagram of an example of provisioning configuration data 960 containing storage sub-groups. The provisioning configuration data 960 contains information on server group name, storage sub group name, and availability of access in addition to the provisioning configuration data 710 shown in FIG. 22.

When the logical volume configured in the RAID device is to be recognized by a server and registered as a storage sub group, the storage RM 25 sets up the logical volume in the following procedure.

FIG. 36 is a flowchart of a processing procedure of a process of setting a logical volume, in which the server recognizes the logical volume. As shown in FIG. 36, the storage RM 25 groups logical volumes included in a RAID device, and sets up an affinity group (step S301).

In this case, the affinity group is information on a correspondence relation between a logical unit number (LUN) to be recognized by the server and a logical volume (LV) number in the RAID device.

FIG. 37 is a schematic diagram for explaining a process of setting the logical volume configured in the RAID device. In FIG. 37, there are described a server group 970, which is configured by a server A and a server B, and a storage pool 980, which is configured by a RAID device a in which logical volumes LV0, LV1, LV2, and LV3 are configured and a RAID device β in which logical volumes LV10, LV11, LV12, and LV13 are configured.

Moreover, in FIG. 37, there is described a storage group 990 to which the logical volumes LV0 and LV1 in the RAID device α and the logical volumes LV12 and LV13 in the RAID device β are added from the storage pool 980.

The logical volumes LV0 and LV1 in the RAID device α, which are added into the storage group 990, are set to belong to an affinity group AG0 and an affinity group AG1. Also, the logical volumes LV12 and LV13 in the RAID device β are set to belong to an affinity group 10 and an affinity group 11.

FIG. 38 is a diagram of affinity group data 1010 containing information on affinity groups. The affinity group data 1010 contains information on RAID device name, affinity group name, LUN, and LV.

The RAID device name is identification information for identifying each of RAID devices. The affinity group name is information on an affinity group that is set in each of the RAID devices. The LUN is identification information for identifying a logical volume when accessed from the server A or the server B. The LV is identification information for identifying a logical volume.

Referring back to FIG. 36, the storage RM 25 checks redundancy paths between the servers A and B and the logical volumes LV0, LV1, LV12, and LV13, and sets an access path by selecting a path (step S302).

The storage RM 25 sets a multipath for a logical unit (step S303). FIG. 39 is a diagram of an example of multipath configuration data 1020 stored as information on multipath configurations.

The multipath configuration data 1020 contains information on multipath instance name and LUN. The multipath instance name is information for identifying an instance of set multipath. The LUN is information for identifying a logical unit that corresponds to the set multipath instance and that is to be recognized by either the server A or the server B.

The storage RM 25 registers the set multipath instance as a constituent element of the mirror volume on a cluster resource of the server to which a clustering is performed (step S304). Thereafter, the storage RM 25 sets a mirror volume group constituted of a pair of volumes of different RAID devices, using the multipath instance registered on the cluster resource (step S305).

An intra-server storage configuration 1000 set inside the server “A” or the server “B” is described in FIG. 37. In the storage configuration 1000, a mirror volume M0 configured with a multipath instance mplb0 and a multipath instance mplb2, and a mirror volume M1 configured with a multipath instance mplb1 and a multipath instance mplb3 are set.

FIG. 40 is a diagram of an example of mirror volume configuration data 1030 stored as information on configurations of mirror volumes. The mirror volume configuration data 1030 contains information on mirror volume and configuring disk.

The mirror volume is identification information for identifying a set mirror volume. The configuring disk is identification information for identifying a logical unit constituting the mirror volume. The configuring disk stores therein information on the multipath instance stored as the multipath configuration data 1020 shown in FIG. 39. Accordingly, it is possible to specify the LUN corresponding to the mirror volume by referring to the multipath configuration data 1020.

The affinity group data 1010 shown in FIG. 38 is stored in the system resource DB 26 and the RAID device by the storage RM 25. The multipath configuration data 1020 shown in FIG. 39 and the mirror volume configuration data 1030 shown in FIG. 40 are stored in the system resource DB 26 by the storage RM 25, and stored, by the storage RM agent 115a, in the server to be managed.

Referring back to the explanation of the processing of creating the software image at step S105 shown in FIG. 4, the network RM 24 performs a setting of a network of the server registered on the server group.

More specifically, the network RM 24 reads information on a network group that includes the server group to which the server is added as a front server group and a back server group, from the inter-server-group link data 830.

The network RM 24 reads the network group data 850 shown in FIG. 30 and extracts a front network sub-group and a back network sub-group corresponding to the network group.

Subsequently, the network RM 24 reads the network sub-group data 660 shown in FIG. 17, searches the network sub group corresponding to the front network sub-group and the back network sub-group, and assigns an IP address to the server based on information on the subnet assigned to the network sub group.

FIG. 41 is a diagram of an example of IP address management data 1040 stored as information on IP addresses assigned to servers. The IP address management data 1040 is stored in the system resource DB 26 by the system resource manager 21.

The IP address management data 1040 contains information on IP address and assignment destination. The IP address is information on an IP address assigned to the server. The assignment destination is information for identifying the server to which the IP address is assigned.

Subsequently, the network RM 24 assigns a load distribution group including a representative IP address to the network group corresponding to the server group to which the server is added, based on the load distribution group data 840 shown in FIG. 29 and the network group data 850 shown in FIG. 30. At this state, a load distribution function of the load balancer is stopped.

A user installs the software such as OS to be installed in the server to the storage sub group associated with the server to be added to the server group. The storage sub group is configured by using a SAN technology.

After the installation is finished, the software sub RM 53 creates the software image constituted of a group of the software such as OS, device driver, and application software, in cooperation with the software RM 23 and the software RM agent 113a, and stores the software image created in the domain resource DB 55.

More specifically, the software RM 23 reads the middleware cooperation IF data 330 shown in FIG. 8, and the software RM agent 113a transmits a command necessary to be executed before acquiring the software image to the AP managing unit 116a that is a function unit realized by the middleware.

In other words, the software RM agent 113a transmits a command for stopping the function of the AP managing unit 116a and stops the function of the AP managing unit 116a. The software sub RM 53 shutdowns the system of the server. The software sub RM 53 performs a network boot of the server using tentative OS stored in the domain resource DB 55 of the domain management server 50 of the server.

Thereafter, the software sub RM 53 creates the software image of the software installed in the server started. The software RM 23 registers information on the software image on the system resource DB 26 as software image management data 1050 described below.

FIG. 42 is a diagram of an example of the software image management data 1050 stored as information on software images. The software image management data 1050 contains information on software image name, format, OS property, and software name.

The software image name is a name of a software image. The format is information that indicates whether a software image is created in archive format or in patch format. The OS property is information that indicates whether a software image is an OS software image. The software name is a name of software for which a software image is created.

The software sub RM 53 creates a software distribution image to be distributed to other servers, based on the software image created. Specifically, the software sub RM 53 creates a software distribution image in which software images are grouped of a plurality of software installed in a storage for the first server.

The system resource manager 21 stores information on the software distribution image in the system resource DB 26 as software distribution image management data 1060 described below.

FIG. 43 is a diagram of an example of the software distribution image management data 1060 stored as information on software distribution images. The software distribution image management data 1060 contains information on software distribution image name, version, server architecture name, and software image/snapshot name.

The software distribution image name is a name of a software distribution image. The version is a version of the software distribution image. The server architecture name is identification information for identifying a CPU architecture of the server to which the software distribution image is distributed. The software image/snapshot name is information that indicates a software image or a snapshot included in the software distribution image.

The snapshot is a software image of the software installed in the server at a specific timing. The system resource manager 21 registers information on the snapshot on the system resource DB 26 as snapshot management data 1070 described below.

FIG. 44 is a diagram of an example of the snapshot management data 1070 stored as information on snapshots. The snapshot management data 1070 contains information on snapshot name and software image name. The snapshot name is a name of a snapshot. The software image name is information for identifying a software image included in the snapshot.

The software RM 23 reads the middleware cooperation IF data 330 shown in FIG. 8. The software RM agent 113a transmits a command necessary to be executed after acquiring the software image to the AP managing unit 116a that is a function unit realized by the middleware.

More specifically, the software RM agent 113a transmits a command for starting the AP managing unit 116a on standby and starts the AP managing unit 116a. The network RM 24 connects the server to a VLAN by performing a setting of the VLAN to a switch, activates a load distribution function of the load balancer, and assigns the server as a target server to which a load is distributed.

Thereafter, the system resource manager 21 reads the middleware cooperation IF data 330 shown in FIG. 8, and transmits a command necessary to be executed after creating the server group to the AP-management control unit 27 that is a function unit realized by the middleware.

More specifically, the system resource manager 21 transmits a command that enables a recognition of an addition of the server group to the AP-management control unit 27. The AP-management control unit 27 performs an installation and a setting of application programs to the server in cooperation with the AP managing unit 116a, and sets the server to be in a state available for a task.

Referring back to FIG. 4, the system resource manager 21 performs a processing of adding the second server and subsequent servers to the server group (step S106). The processing performed at step S106 is described in detail below.

FIG. 45 is a flowchart of a processing procedure of a processing of adding a server to a server group. As shown in FIG. 45, the system resource manager 21 receives information on the server and the server group when a user specifies the server and the server group on which the server is registered by operating the operation management client 10 (step S401).

The system resource manager 21 registers the server on the server group (step S402). Subsequently, the system resource manager 21 reads the management target server data 700 shown in FIG. 21 and the software distribution image management data 1060 shown in FIG. 43, and checks whether the server architecture of the server is enabled for an installation of the software image (step S403). When the server architecture of the server is not enabled for the installation of the software image (NO at step S403), the processing of adding the server to the server group ends.

When the server architecture of the server is enabled for the installation of the software image (YES at step S403), the storage RM 25 performs a processing of setting the storage to the server, in the same manner for setting the storage to the first server (step S404). Specifically, the storage RM 25 performs a processing of setting the logical volume described in connection with FIGS. 31 and 36 to the server.

Thereafter, the network RM 24 performs a network boot of the server registered on the server group using a tentative OS in the same manner for setting the network to the first server, and performs a setting of the network to the server (step S405).

The software sub RM 53 expands the software distribution image created from the software installed in the first server onto the storage sub group associated with the second server, and reboots the server using expanded software (step S406).

When the software distribution image is expanded onto the storage sub group associated with the server, the software RM 23 stores information on the software distribution image distributed in the system resource DB 26.

FIG. 46 is a diagram of an example of distribution management data 1080 stored as information on distribution statuses of software distribution images. The distribution management data 1080 contains information on server name, storage sub group name, software distribution image name, version, and status.

The server name is identification information for identifying the server to which the storage sub group is allocated. The storage sub-group name is identification information for identifying the storage sub group in which a software distribution image is developed. The software distribution image name is identification information for identifying the software distribution image developed in the storage sub group. The version is information of the version of the distributed software distribution image. The status is information indicating distribution status of the software distribution image.

Referring back to FIG. 45, the system resource manager 21 performs a processing of moving a mode of the second server to be in an operation mode in cooperation with the network RM 24 and the AP-management control unit 27 (step S407).

Specifically, the network RM 24 assigns an IP address to the second server based on information on the subnet to which the first server belongs, at the timing of rebooting the server. The information on the IP address assigned to the second server is stored in the IP address management data 1040 shown in FIG. 41 by the system resource manager 21.

Thereafter, the network RM 24 connects the server to VLAN by performing a setting of VLAN to a switch, and registers the server on the load balancer as a target server to which a load is distributed.

The system resource manager 21 transmits a command for causing the AP-management control unit 27 to recognize that the server is added to the server group to the AP-management control unit 27. The AP-management control unit 27 performs an installation or a setting of the application to the server in cooperation with the AP managing unit 116a, and sets the server to be in a state available for the task.

When adding the third server or subsequent servers to the server group, the processing of adding the server described in connection with FIG. 45 is repeated.

The repurposing process procedure explained in FIG. 2 is explained with reference to FIGS. 47 and 48. FIG. 47 is a flowchart for explaining a presetting process procedure according to the repurposing process, and FIG. 48 is a flowchart of a repurposing process procedure.

As shown in FIG. 47, the system resource manager 21 receives repurposing setting information set by the user by operating the operation management client 10 to register the information in the system resource DB 26 as repurposing setting data 1090 and schedule setting data 1110 explained below (step S501).

FIG. 49 is an example of the repurposing setting data 1090 in which information of repurposing setting is stored. The repurposing setting data 1090 stores information of repurposing definition name, number of operating servers, and status 1, status 2, and status 3.

The repurposing definition name is information of repurposing definition name imparted to respective repurposing settings. The operating server name is information of number of the servers used for the repurposing process. Status 1, status 2, and status 3 are information for identifying to which server group the server belongs in each status, when there are three statuses in which the server belongs to the server group of a different application in the repurposing process. The identification information of the server group to which the server belongs in each status is stored in status 1, status 2, and status 3.

The information of the status indicating to which server group the server currently belongs is registered in the system resource DB 26 as repurposing operation data 1100 by the system resource manager 21. FIG. 50 is an example of the repurposing operation data 1100 in which information of server status is stored.

The repurposing operation data 1100 stores information of repurposing definition name and current status. Repurposing definition name is the same information as the repurposing definition name explained in FIG. 49. The current status identifies the status indicating to which server group the server currently belongs. In current status, information of any one of status 1, status 2, and status 3 of the repurposing setting data 1090 in FIG. 49 is stored.

FIG. 51 is an example of the schedule setting data 1110 in which schedule information for executing the repurposing process is stored. The schedule setting data 1110 stores information of the repurposing definition name, date, and operation.

The repurposing definition name is the same information as the repurposing definition name explained in FIG. 49. The date is information of date when the repurposing process is to be executed. The operation is information for identifying the status of a switching origin and the status of a switching destination when the status explained in FIG. 49 is switched in the repurposing process.

The information of status 1, status 2, and status 3 is stored in the repurposing setting data 1090 shown in FIG. 49, the repurposing operation data 1100 shown in FIG. 50, and the schedule setting data 1110 shown in FIG. 51. However, the number thereof is not limited to three, and the information of optional number of statuses can be stored. For the sake of brevity, an instance in which the repurposing process is performed for switching two statuses, that is, status 1 and status 2 is explained.

Returning to the explanation in FIG. 47, the system resource manager 21 checks if the server group, whose status is to be switched, belongs to a server group belonging to the same server domain, and if there are servers to be managed in a number set in the number of operating servers in FIG. 49 in the pool group (step S502).

Specifically, the system resource manager 21 refers to the server group data 810 shown in FIG. 26 to execute checking of the server group. The system resource manager 21 refers to the provisioning configuration data 710 shown in FIG. 22 to execute checking of the pool group.

The system resource manager 21 registers the server to the switching server group, which corresponds to status 1 shown in FIG. 49 (step S503). The system resource manager 21 creates the storage sub group corresponding to the server group, to which the server is registered, in cooperation with the storage RM 25 (step S504).

Specifically, the system resource manager 21 sets the logical volume in the RAID device by cooperating with the storage RM 25, and refers to the storage template data 800 shown in FIG. 25 and the server group data 810 shown in FIG. 26 to create the storage sub group corresponding to the server group as shown in FIG. 35. The system resource manager 21 permits an access from the server corresponding to the created storage sub group.

Subsequently, the system resource manager 21 refers to the server group data 810 shown in FIG. 26 to select a software distribution image to be distributed to the server group, to which the server is registered. The software sub RM 53 distributes the software distribution image to the storage sub group corresponding to the server group to develop the image (step S505).

Thereafter, the system resource manager 21 cooperates with the network sub RM 54 to set to reject an access to the storage sub-group from the server corresponding to the storage sub-group having distributed the software distribution image, thereby disconnecting the server from the server group (step S506). At this time, the system resource manager 21 does not delete the storage sub-group and stores the group.

Subsequently, the system resource manager 21 registers the server disconnected from the server group to another switching server group corresponding to status 2 (step S507). The system resource manager 21 creates the storage sub-group corresponding to the server group, to which the server is registered, in cooperation with the storage RM 25 (step S508).

Specifically, the system resource manager 21 sets the logical volume in the RAID device by cooperating with the storage RM 25, and refers to the storage template data 800 shown in FIG. 25 and the server group data 810 shown in FIG. 26 to create the storage sub-group corresponding to the server group as shown in FIG. 35. The system resource manager 21 permits an access from the server corresponding to the created storage sub-group.

Thereafter, the system resource manager 21 refers to the server group data 810 shown in FIG. 26 to select a software distribution image to be distributed to the server group, to which the server is registered. The software sub RM 53 distributes the software distribution image to the storage sub-group corresponding to the server group to develop the image (step S509), and finish the presetting process.

When the number of statuses is more than three, the server is disconnected from the server group, and the process from step S507 to step S509 and the process for disconnecting the server from the server group need only to be repetitively executed for the number of the statuses, after step S509.

As shown in FIG. 48, in the repurposing process, the system resource manager 21 acquires information of the server group of the switching destination from the repurposing setting data 1090 shown in FIG. 49 (step S601).

The system resource manager 21 refers to the server group data 810 shown in FIG. 26 to acquire the information of the software distribution image corresponding to the server group, and refers to FIG. 46 to check if the software distribution image has been distributed (step S602).

Thereafter, the system resource manager 21 cooperates with the network sub RM 54 to set to reject an access to the storage sub-group from the server, thereby disconnecting the server from the server group to which the server currently belongs, and add the server to the pool group (step S603). At this time, the system resource manager 21 does not delete the storage sub-group and stores the group.

Subsequently, the system resource manager 21 registers the server added to the pool group to the server group of the switching destination (step S604), and permits an access from the server to the logical volume created in the storage sub group corresponding to the registered server group (step S605).

The server RM 22 cooperates with the server sub RM 52 to boot the server, designating the logical volume, to which the access is permitted, as a boot disk (step S606), and finishes the repurposing process.

In the repurposing process, as shown in FIG. 49, one server group is set to each status, however, more than one server group can be set to each status.

FIG. 52 is an example of repurposing setting data 1120 in which at least one server group is set to each status. The repurposing setting data 1120 stores information of repurposing definition name, number of operating servers, status 1, and status 2.

Repurposing definition name is the same information as the repurposing definition name explained in FIG. 49. Number of operating servers is the same information as the number of operating servers explained in FIG. 49. Status 1 and status 2 identify to which server group the server belongs in each status, when there are two statuses in which the server belongs to the server group of a different application in the repurposing process. The identification information of the server group to which the server belongs is stored in the respective statuses 1 and 2.

A different point from the statuses 1, 2, and 3 in the repurposing setting data 1090 explained in FIG. 49 is that at least one server group is set to each status relative to one repurposing definition name, and the software used by the server that belongs to the server group is switched to another software, thereby changing the application of the server that belongs to the server group to another application.

In the example shown in FIG. 52, server group “A_DB” and server group “B_DB” are registered to status 1, and server group “A_Batch” is registered to status 2. When the status is changed from status 1 to status 2, the application of the server is changed from two applications of the server that belongs to server groups “A_DB” and “B_DB” to one application of the server that belongs to server group “A_Batch”.

When the status is changed from status 2 to status 1, the application of the server is changed from one application of the server that belongs to server group “A_Batch” to two applications of the server that belongs to server groups “A_DB” and “B_DB”. When a plurality of server groups are registered to each of status 1 and status 2, the application of the server is changed from a plurality of applications of the server that belongs to the respective sever groups to a plurality of other applications.

The number of servers allocated to the respective server groups can be set to the respective server groups. In the example in FIG. 52, server group “A_DB” and server group “B_DB” are registered to status 1, and it is set such that one server is allocated to server group “A_DB” and three servers are allocated to server group “B_DB”, of four servers specified by the number of operating servers. In status 2, it is set such that four servers are allocated to server group “A_Batch”.

Various processes explained in the present embodiment can be realized by having a computer execute a program prepared in advance. An example of the computer that executes the program that realizes the various processes is explained with reference to FIGS. 53 to 55.

FIG. 53 depicts a hardware configuration of a computer 1200, which is the site management server 20 shown in FIG. 3. The computer 1200 is configured by connecting an input device 1210 that receives an input of data from the user, a monitor 1220, a medium reader 1230 that reads a program from a recording medium that records various programs, a ROM (read only memory) 1240, a network interface 1250 that transfers data to and from another computer via the network, a HDD (hard disk drive) 1260, a RAM (random access memory) 1270, and a CPU (central processing unit) 1280 to each other by a bus 1290.

Programs that demonstrate the same function as that of the site management server 20, that is, a system-resource management program 1260b and an AP-management control program 1260c shown in FIG. 53 are stored in the HDD 1260.

The system-resource management program 1260b and the AP-management control program 1260c can be appropriately united or distributed and stored.

The CPU 1280 reads the system-resource management program 1260b and the AP-management control program 1260c from the HDD 1260 and executes these programs, so that the system-resource management program 1260b and the AP-management control program 1260c function as a system-resource management process 1280a and an AP-management control process 1280b.

The system-resource management process 1280a corresponds to the system resource manager 21, the server RM 22, the software RM 23, the network RM 24, and the storage RM 25 shown in FIG. 3. The AP-management control process 1280b corresponds to the AP-management control unit 27 shown in FIG. 3.

System resource data 1260a is stored in the HDD 1260. The system resource data 1260a corresponds to various data stored in the system resource DB 26 shown in FIG. 3.

The CPU 1280 stores various data related to the resource management as the system resource data 1260a, reads the system resource data 1260a from the HDD 1260 to store the data in the RAM 1270, and executes various types of data processing based on system resource data 1270a stored in the RAM 1270.

FIG. 54 depicts a hardware configuration of a computer 1300, which is the domain management server 60 shown in FIG. 3. The computer 1300 is configured by connecting an input device 1310 that receives an input of data from the user, a monitor 1320, a medium reader 1330 that reads a program from a recording medium that records various programs, a ROM 1340, a network interface 1350 that transfers data to and from other computers via the network, an HDD 1360, a RAM 1370, and a CPU 1380 to each other by a bus 1390.

A program that demonstrates the same function as that of the domain management servers 50 and 60, that is, a domain-resource management program 1360b shown in FIG. 54 is stored in the HDD 1260. The domain-resource management program 1360b can be appropriately united or distributed and stored.

The CPU 1380 reads the domain-resource management program 1360b from the HDD 1360 to execute the program, so that the domain-resource management program 1360b functions as a domain-resource management process 1380a.

The domain-resource management process 1380a corresponds to the system resource domain manager 51, the server sub RM 52, the software sub RM 53, and the network sub RM 54 shown in FIG. 3.

Domain resource data 1360a is stored in the HDD 1360. The domain resource data 1360a corresponds to various data stored in the domain resource DB 55 shown in FIG. 3.

The CPU 1380 stores various data related to the resource management in the domain as the domain resource data 1360a, reads the domain resource data 1360a from the HDD 1360 to store the data in the RAM 1370, and executes various types of data processing based on the domain resource data 1370a stored in the RAM 1370.

FIG. 55 depicts a hardware configuration of a computer 1400, which is a server 110a shown in FIG. 3. The computer 1400 is configured by connecting an input device 1410 that receives an input of data from the user, a monitor 1420, a medium reader 1430 that reads a program from a recording medium that records various programs, a RAM 1440, a ROM 1450, a network interface 1460 that transfers data to and from other computers via a network, an HDD 1470, and a CPU 1480 to each other by a bus 1490.

Programs that demonstrate the same function as that of the server 110a, that is, an agent-resource management program 1470a and an AP control program 1470b shown in FIG. 55 are stored in the HDD 1470. The agent-resource management program 1470a and the AP control program 1470b can be appropriately united or distributed and stored.

The CPU 1480 reads the agent-resource management program 1470a and the AP control program 1470b from the HDD 1470 to execute these programs, so that the agent-resource management program 1470a and the AP control program 1470b function as an agent-resource management process 1480a and an AP control process 1480b.

The agent-resource management process 1480a corresponds to the resource manager agent 111a, the server RM agent 112a, the software RM agent 113a, the network RM agent 114a, and the storage RM agent 115a shown in FIG. 3. The AP control process 1480b corresponds to the AP managing unit 116a shown in FIG. 3.

The system-resource management program 1260b, the AP-management control program 1260c, the domain-resource management program 1360b, the agent-resource management program 1470a, and the AP control program 1470b need not necessarily be stored initially in the HDD 1260, 1360, or 1470.

For example, the respective programs can be stored in a “portable physical medium” such as a flexible disk (FD), CD-ROM, MO disk, DVD disk, magneto-optical disk, or IC card inserted into the computer 1200, 1300, or 1400, a “fixed physical medium” such as a hard disk drive (HDD) equipped in or out of the computer, or “another computer (or server)” connected to the computer 1200, 1300, or 1400 via a public line, the Internet, LAN, or WAN, so that these programs are read therefrom and executed by the computer 1200, 1300, or 1400.

As described above, according to the present embodiment, the system resource manager 21 registers the server group as a group of servers using uniform software and controls the switching of the software used by the servers belonging to the registered server group. Accordingly, even in the large-scale information processing system including a large number of servers, a change of server application can be performed by the administrator with ease and efficiency by managing the servers in a unit of server group.

Furthermore, according to the present embodiment, the system resource manager 21 registers the server domain as a group of servers having uniform physical connection, and registers the server group as a group of servers using uniform software in the registered server domain. Therefore, the administrator can easily construct the server group of the server used by changing the application, and can change the application of the server belonging to the constructed server group easily and efficiently, by registering the server group, to which the server belongs, whose application is switched, in the respective server domains in which uniformity of the physical connection is guaranteed.

Moreover, according to the present embodiment, the system resource manager 21 controls the switching of the software used by the server by controlling an access from the server to the software stored in the RAID device connected to the server belonging to the server group via the SAN. Accordingly, the switching of the software can be easily executed, and an application changing process of the server group can be efficiently performed.

Furthermore, according to the present embodiment, the system resource manager 21 controls the switching of the software used by the server belonging to the server group based on the schedule setting data 1110. Accordingly, switching of the application of the server can be performed systematically.

Moreover, according to the present embodiment, the system resource manager 21 changes one of a plurality of servers or a plurality of applications to another application, by controlling the switching of the software respectively used by the servers belonging to a plurality of server groups to another software, or switching of the software used by the servers belonging to one server group to the another plurality of software, based on the repurposing setting data 1120. Accordingly, a change of the server application can be flexibly and efficiently performed.

Furthermore, according to the present embodiment, the system resource manager 21 changes one of a plurality of resources or a plurality of applications to another application by controlling the switching of the software respectively used by the specified number of resources belonging to the resource groups to another software based on the repurposing setting data 1120, or controls the switching of the software used by the resource belonging to one resource group to another plurality of software for each of the specified number of resources. Accordingly, required number of servers can be distributed to respective applications.

While the embodiment of the present invention has been explained above, variously modified embodiments other than the explained ones can be made without departing from the scope of the technical spirit of the appended claims.

Among the respective processes explained in the present embodiment, all or a part of the processes explained as being performed automatically can be performed manually, or all or a part of the processes explained as being performed manually can be performed automatically in a known method.

In addition, information including the process procedures, the control procedures, specific names, and various kinds of data and parameters shown in the present specification or the drawings can be optionally changed unless otherwise specified.

Furthermore, the respective constituent elements of the respective devices shown in the drawings are functionally conceptual, and physically the same configuration is not always necessary. In other words, the specific mode of dispersion and integration of the devices is not limited to the shown ones, and all or a part thereof can be functionally or physically dispersed or integrated in an optional unit, according to various kinds of load and the status of use.

Further, all or an optional part of various process functions performed by the respective devices can be realized by a CPU or a program analyzed and executed by the CPU, or can be realized as hardware by the wired logic.

As described above, according to one aspect of the present invention, a resource groups is registered as a group of resources using uniform software, and the switching of software used by the resources belonging to the registered resource group is controlled. Accordingly, even in the large-scale information processing system including a large number of resources, a change of resource application can be performed by the administrator with ease and efficiency by managing the resources in a unit of resource group.

Although the invention has been described with respect to a specific embodiment for a complete and clear disclosure, the appended claims are not to be thus limited but are to be construed as embodying all modifications and alternative constructions that may occur to one skilled in the art that fairly fall within the basic teaching herein set forth.

Claims

1. An apparatus for managing an operation of resources constituting an information processing system, the apparatus comprising:

a server-information storage unit that stores information on a plurality of servers belonging to a server group;
a storage unit that stores number of servers being able to be switched from a first server group to a second server group, identification information of the first server group, identification information of the second server group and switching schedule information including timing information on switching from the first server group to the second server group; and
a switching unit that identifies, depending on the number, a server switched from the first server group and a server group the server being switched to, and switches the identified server to the identified server group as the second server group with timing specified by the timing information.

2. The apparatus according to claim 1, wherein

the switching unit switches the identified server with different timing based on number of servers belonging to the first server group.

3. A method of managing an operation of resources constituting an information processing system, the method comprising:

identifying, depending on number of servers being able to be switched from a first server group to a second server group, a server switched from the first server group and a server group the server being switched to, the identifying identifies using a server-information storage unit that stores information on a plurality of servers belonging to a server group and a storage unit that stores the number, identification information of the first server group, identification information of the second server group and switching schedule information including timing information on switching from the first server group to the second server group; and
switching the identified server to the identified server group as the second server group with timing specified by the timing information using the storage unit.

4. The method according to claim 3, wherein

the switching switches the identified server with different timing based on number of servers belonging to the first server group.

5. A computer-readable, non-transitory storing medium that stores therein a computer program for managing an operation of resources constituting an information processing system, the computer program causing a computer to execute:

identifying, depending on number of servers being able to be switched from a first server group to a second server group, a server switched from the first server group and a server group the server being switched to, the identifying identifies using a server-information storage unit that stores information on a plurality of servers belonging to a server group and a storage unit that stores the number, identification information of the first server group, identification information of the second server group and switching schedule information including timing information on switching from the first server group to the second server group; and
switching the identified server to the identified server group as the second server group with timing specified by the timing information using the storage unit.

6. The computer-readable, non-transitory storing medium according to claim 5, wherein

the switching switches the identified server with different timing based on number of servers belonging to the first server group.
Patent History
Publication number: 20120233305
Type: Application
Filed: May 16, 2012
Publication Date: Sep 13, 2012
Applicant: FUJITSU LIMITED (Kawasaki-shi)
Inventors: Shigehiro Yoshikawa (Kawasaki), Yoshinobu Hibi (Kawasaki), Masayuki Naitou (Kawasaki), Satoshi Iyoda (Kawasaki)
Application Number: 13/473,436
Classifications
Current U.S. Class: Computer Network Managing (709/223)
International Classification: G06F 15/173 (20060101);