JP2012173751A - Shared resource management system and resource management server device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the availability of an information processing center in which a shared resource is arranged.SOLUTION: A configuration catalog 140 carries the configuration of a system using a resource as a component. A center manager is able to update the content by appropriate input means. A function module 150 notifies a function module 120 of the state information and failure information of each resource configuring servers (1000-5000). The function module 150 obtains the state information and failure information from each resource configuring each server. The function module 120 collects the state information and failure information of which the function module 150 has notified the function module 120, and stores the state information and failure information in a database 110. A function module 130 rearranges the resource while referring to the state information and failure information, and performs calculation for constructing the system requested by the configuration catalog 140, and performs the mounting of hardware configuring the system including wire connection.

Description

  The present invention relates to a shared resource management system and a resource management server device, and in particular, manages the status of a resource shared by a plurality of systems and the status at the time of a failure while performing other functions of the failed resource when a failure occurs. The present invention relates to a shared resource management system and a resource management server device that can be allocated to other resources.

In recent years, as a large-scale information processing system, in a large-scale data center (resource sharing management center system) that manages a customer's server device and the like, various types of data center side including a server device on the data center side are used. Resource sharing type information processing systems in which resources are centrally managed and a plurality of systems including customer-side server devices and the like share these data center resources as shared resources are becoming widespread.
Here, the resources on the data center side include CPU devices, memory devices, disk devices, network devices (including interfaces), and the like that constitute the server device on the data center side. The server equipment itself on the data center side is also included in the category of the resource.

Therefore, a large-scale data center or the like that manages server devices on the customer side has these multiple resources, thereby operating a plurality of systems that include the server devices on the customer side. Will be.
In addition, the data center side server group that constitutes these multiple systems has a cluster configuration (hot standby, cold standby as availability terms) that can use the system continuously by applying availability technology. Things are also being developed. In this case, if a part of the resources of the server devices constituting the cluster fails, it may be necessary to disconnect and repair the server devices constituting the failed resource from the system. It was one of the problems.

Further, as described above, since it is necessary on the data center side to manually manage server devices and the like separated from the system, this solution is also one of the problems in the present invention.
In addition, resources that replace server devices that are operating on the data center side are pooled in advance on the data center side as alternative server devices, and the server devices that are operating are disconnected from the system when a failure occurs. It becomes necessary to replenish the server device and the like in real time. Therefore, providing such a technique was also one of the problems in the present invention.

  Furthermore, in preparation for a configuration request for a new server device or the like from a data center administrator, resources that can meet the configuration requirements of the new server device or the like are pooled in advance under collective management, and a new server When a configuration request for a device or the like is issued, it is also one of the problems in the present invention to automatically mount a server device or the like that meets the configuration requirement including connection.

  As a known technique in this field, for example, Patent Document 1 discloses a technique for providing an “automatic” mechanism for defining resource groups in a high availability cluster network configuration. Specifically, an administrator need only identify a set of resources that must be juxtaposed with an application if a failure occurs on the computer that is currently executing the given application. In this case, the resource group is automatically generated using a set of collocation “constraints” or rules. The first collocation constraint states that it is preferable to implement any user-defined collocation for a given application, and the second constraint is to juxtapose disk partition resources that reside on the same physical disk.

  Further, for example, Patent Document 2 discloses a technology that enables an administrator to grasp and manage the resource usage status for each node, and to reduce the management cost of a storage system with a cluster configuration. Specifically, the management server has data physical position information of each node integrated, and includes means for presenting the data in association with the configuration of the cluster configuration storage system and the configuration of each node. The node includes means for acquiring the amount and load of resources used in processing, and the management server collects and aggregates the usage status of each resource from each server, the resource usage status, the data information, and the configuration There is provided means for associating with information and providing a hierarchy. Further, a means for moving the logical volume between nodes transparently to the host computer is provided. The management server includes means for supporting selection of movement source data and movement destination physical position by displaying information, and means for receiving the movement instruction and instructing movement to the cluster configuration storage system.

  Further, for example, Patent Document 3 discloses a technique for performing flexible autonomous control according to control requirements (policy) in an autonomous control system including a server, a storage, and a network device connected via a network. . Specifically, various policies are stored in a policy DB or the like, and each node constituting the system cooperates with other nodes and performs autonomous control based on the policy. In addition, spare resources are managed using a shared pool, a bare metal pool, and a standby pool, and a work group system resource manager selects spare resources in the order of the standby pool and the bare metal pool in the event of a failure or performance degradation.

  Further, for example, Patent Document 4 discloses a means for obtaining a resource that does not affect even when another information processing system is already in operation, and for making effective use of continuous execution of business services and shared resources. ing. Specifically, for each business application, a storage unit storing information for identifying a computer system that executes each business application, and resource usage rate information including a usage rate of resources constituting each computer system, An impact range investigating unit that aggregates and outputs the utilization rate of each resource constituting the computer system after the change using the resource utilization rate information when newly requesting the use of the resource of the computer system; It is a resource management system provided.

  Furthermore, for example, Patent Document 5 discloses a technique for dynamically providing software resources. Specifically, it is a technology that dynamically provides software resources such as an operating system, application programs, and software drivers.

JP 2001-109639 A JP 2003-296039 A JP 2005-346204 A JP 2008-033852 A Special table 2008-502967

By the way, in the conventional shared resource management system described in the background art, as described above, the plurality of resources are allocated to a large-scale data center or the like that manages a plurality of systems constructed including customer servers and the like. It is configured to prepare and manage. In addition, some servers on the data center side configuring each system have a cluster configuration to which availability technology is applied.
In addition, as described above, when a part of the resources of a server in this cluster configuration fails, the server configured with the failed resource must be manually managed by separating it from the system, and in some cases, it is necessary to repair it. However, the conventional resource-sharing information processing system system has a problem that it cannot cope with such management and repair.

  On the data center side, resources that replace the operating server device, etc. are pooled in advance as an alternative server device, etc., and when the failure occurs, the operating server device, etc. is disconnected from the system, and this replacement It becomes necessary to replenish the server device and the like in real time. However, in the conventional resource sharing type information processing system, there is a problem that such an alternative server device is pooled in advance and is not taken into account for supplementing the device when a failure occurs.

Furthermore, in the conventional resource-sharing information processing system system, the configuration requirements of a new system (server device, etc.) specifically requested by the data center manager from the resources pooled in advance under the collective management. There is a problem that it is not taken into consideration to extract a matching resource and to supplement the resource when a failure occurs.
Therefore, in the present invention, it is important to construct a system that does not have to stop providing a service even if a resource constituting the system fails (that is, a system that places more importance on availability). It was a difficult task.

Incidentally, in recent years, technologies for realizing virtual environments and the like have been rapidly developed due to the necessity of reducing maintenance costs and operation costs of physical equipment and from a technical point of view. It has become an important issue to reduce the system management cost and the operation cost by effectively using the system and simplifying the operation of the operator.
It is also important to increase the operating rate of all resources in the system environment by providing visualization technology to reduce the complexity of the virtual technology, and to reduce the work of the center operation manager. It is coming.

  Note that in the technology described in Patent Document 1, when a failure occurs in a computer that executes a given application, the administrator simply identifies a set of resources to be juxtaposed with the application. Are automatically generated using a set of collocation “constraints” or rules, and like the present invention, they collect up to failure information and allocate the function of the failed resource to other resources. Even if a resource is replaced or failed, a device that can be configured in another system among the devices that constitute the resource is not intended to utilize the device as much as possible.

  In addition, the technique described in Patent Document 2 is limited to reducing the management cost of a storage system having a cluster configuration, and therefore, only the storage system is considered as a resource. Servers, CPU devices, memory devices, disk devices, and network devices (including interfaces) constituting the servers are not handled as resources.

  Furthermore, the technology described in Patent Document 3 defines service policies by the layers such as the Front layer, Web layer, AP layer, and DB layer, and adds or switches server groups according to the policy for each layer at the time of failure in each layer. Is to implement. However, in the present invention, it is not conscious of what a higher-level server such as the Web layer or AP layer operates. That is, in the present invention, since the layer is not conscious, it is not a service of the layer, but a hardware level resource (for example, CPU device, memory device, disk device, network device (including interface)) is allocated to the system. As a component.

  The technique described in Patent Document 4 defines a business application as a business configuration object. However, in the present invention, the business configuration object and resource pooling are not linked. Furthermore, the present invention is characterized by the provision of a quick replacement resource in the event of a failure. The fault countermeasure / recovery function of configuration requirements is left to each subsystem, and the management server is configured and pooled for each subsystem. It is managed separately from resource management.

  Furthermore, the technique described in Patent Document 5 is mainly a countermeasure in terms of software, and in particular, dynamically provides an operating system, application programs, and software drivers. Therefore, it does not solve the problem of providing a hard resource that is a problem of the present invention by flexibly and dynamically changing the configuration.

  That is, according to the present invention, in a means for sharing resources with other system groups and automatically changing resources in the event of a failure or the like, the central management center (management server) stores the status information of the failed resource. Collected and checked against the system's business catalog (configuration catalog, requirements) of other systems requested by customers (center managers) and collated with resource accumulation (pooling) information managed in advance in an integrated manner. When there is a resource, the main point is to construct the other system required by the customer by incorporating the resource.

  The present invention has been made in view of the above-described conventional problems. When a failure occurs in a part of resources shared by a plurality of systems configured via a network, the failure is It is an object of the present invention to provide a shared resource management system and a resource management server apparatus capable of allocating the function of a failed resource to other resources based on information and new server requirements requested by a system administrator. .

  In order to solve the above problems, a shared resource management system according to the present invention includes a plurality of resources as hardware resources, status information indicating the state of each of the plurality of resources, and a failure of each of the plurality of resources. Means for collecting failure information indicating a situation, means for registering the collected situation information and failure information in a database, and hardware configurations of each of a plurality of configured systems, the plurality of resources A configuration catalog that can describe at least a part of the plurality of resources as a component, and the configuration catalog is updated. The new information specified in the configuration catalog with reference to the status information and the failure information. And a means for configuring and implementing the hardware of the system that uses the resource after confirming that each of the resources configuring the system hardware is operable. .

  The resource management server device of the present invention is hardware-connected to a plurality of resources as hardware resources, and indicates status information indicating the status of each of the plurality of resources, and indicates a fault status of each of the plurality of resources. A means for collecting failure information and registering it in a database, and a hardware configuration of each of a plurality of configured systems, including at least a part of the plurality of resources as constituent elements and a new configuration A configuration catalog capable of describing at least a part of the plurality of resources as components, and referring to the status information and the failure information when the configuration catalog is updated, Each of the resources that make up the hardware of the new system specified in the configuration catalog is operational. After having Ensure, to configure the hardware of the system using the resource, and characterized by comprising a means for mounting.

  As described above, according to the shared resource management system of the present invention, resources are managed and accumulated (pooled) in advance in an integrated manner, and one resource shared by a plurality of systems configured via a network is used. When a failure occurs in a part, the new server requirements required by the system administrator are checked against the management / stored information. If there is a resource that can be replaced, the system can be restarted using the resource. In addition to the configuration, hardware such as a server device corresponding to the system including the wiring can be mounted, so that there is an effect that the availability of the information processing center in which the shared resource is deployed can be improved.

It is a block diagram which shows the whole structure of the shared resource management system which concerns on embodiment of this invention. It is explanatory drawing which shows that a failure generate | occur | produced in network I / F3100 which is a part of resource of the server 3000 in the shared resource management system of embodiment of this invention. FIG. 11 is an explanatory diagram illustrating an operation example when a failure occurs in the network I / F 3100 that is a part of the resource of the server 3000. FIG. 10 is an explanatory diagram illustrating another operation example when a failure occurs in the network I / F 3100 that is a part of the resource of the server 3000. It is a sequence diagram which shows an example of the operation | movement order of the shared resource management system which concerns on embodiment of this invention.

The shared resource management system of the present invention is configured for a plurality of systems configured to include the customer-side server device and the like in a large-scale data center that manages the server device and the like on the customer side. It is characterized in that the status of resources deployed on the data center side can be managed and shared.
Here, the resources deployed on the data center side are hardware resources allocated to construct a system. For example, a CPU device, a memory device, a disk device, and a server device constituting the server device on the data center side. It is a network device (responsible for the interface function with the network). However, in the present invention, the server device itself composed of the device group is considered to fall within the category of the resource.

In addition, the present invention is characterized in that resources that are not currently used are pooled and managed collectively.
Here, pooling means holding a certain number of resources.
Furthermore, the present invention uses the pooled resources to configure a system that meets the configuration requirements of a new server device or the like requested by a data center manager, and automatically constructs the system configuration (connection). Etc.), and is implemented as hardware.

In the present invention, the hardware of a system having a given system configuration is constructed using various resources, and some of these resources are caused by operational convenience, configuration convenience, or failure occurrence. There may also be resources left unused and left behind.
The shared resource management system of the present invention manages the state of all resources including such resources, and selects resources that meet the new server requirements specified by the center administrator from among the pooled resources. If it is determined that the resource is valid (including verification of whether or not it can be operated), a system that uses the resource is configured, and hardware such as a server device corresponding to the system is constructed (that is, connected) It is featured that it is implemented inclusive).

Hereinafter, embodiments of a resource sharing management center system and a resource management server apparatus according to the present invention will be described in detail with reference to the drawings.
FIG. 1 is a configuration diagram showing the overall configuration of a shared resource management system according to an embodiment of the present invention.
In the figure, the shared resource management system of the present embodiment includes a resource management server 100 (resource management server apparatus according to the embodiment of the present invention) that is a server device that manages a plurality of resources, and a program provided as a resource. And servers 1000 to 5000 which are server devices to be executed.
It is assumed that the server 5000 is a server device that is not actually operating at present (a server device at the planning stage).

  The resource management server 100 includes a database 110 for storing data, a function module 120 having a function of collecting status information and failure information of resources (hardware resources) described later, and a function module 130 responsible for resource rearrangement and implementation. And a configuration catalog 140 that describes the configuration requirements of the system requested by the center manager, including specific resources such as server devices.

  The servers (1000 to 5000) are commonly provided with a functional module 150 having a function of transmitting resource state information and failure information to the resource management server 100, but in addition to this, a network I / F that performs an interface function with the network. (1100-5100) and network I / F (1200, 3100, 3200), and a disk storage device (reference numerals are omitted).

Here, the network I / F is not provided in the resource management server 100, but in the present invention, generally, the resource management server 100 can also be provided with the network I / F.
Generally, the server (1000 to 5000) is configured to process user information via a network (Internet network or the like) using a communication protocol provided in the network I / F (1100 to 5100) or the network I / F (1200 to 3200). Connected to the device.
Here, the above-mentioned resources indicate general hardware resources necessary for constructing a system, and include, for example, a CPU device, a memory device, a built-in disk device, and a network I / F. Shall.

Hereinafter, the function of the shared resource management system of this embodiment will be described with reference to FIG.
The shared resource management system (FIG. 1) according to the present invention can manage a plurality of resources existing in a large-scale data center that manages a customer's server, etc., by a single server and can be shared among a plurality of systems. To.
That is, among the resources of server devices having a cluster configuration, the resource status information of some failed servers and the failure information indicating the failure status of resources that occurred in a single server device are also allocated in real time. The resource management server 100 to be managed is notified.
In addition, the new system is configured by collating pooling information of resources managed in an integrated manner with respect to the new configuration requirements of the system requested by the center manager, and implemented as hardware constituting the system. Do.

In FIG. 1, a resource management server 100 has a function of managing each of the above-described resources including servers (1000 to 5000) and changing the configuration of a system constructed using the managed resources. It is.
As described above, the resource management server 100 that manages the source includes the database 110 that stores data, the function module 120 that has a function of collecting resource state information and failure information, and a function module that is responsible for resource rearrangement and implementation. 130.

Here, the data stored in the database 110 is of two types: the status information and failure information of the resource, and the configuration catalog 140 that describes the configuration requirements of the system requested by the center manager with resources such as server devices. . However, in the present invention, in general, the resource state information and failure information and the configuration catalog 140 can be stored in different databases.
Note that the configuration catalog 140 is a configuration catalog in which resources required by each system (that is, names and connections of resources necessary for system construction) are listed. The contents can be updated by the means.

The functional module 150 notifies the functional module 120 of status information and failure information of each resource constituting each server managed by the resource management server 100.
The functional module 150 obtains the status information and the failure information from each resource constituting each server managed by the resource management server 100 (that is, the server (1000 to 5000)).
The functional module 120 collects status information and failure information notified from the functional module 150 and stores them in the database 110.
The function module 130 requested the configuration catalog 140 by referring to the status information and the failure information, and rearranging each server device managed by the resource management server 100 and the resources constituting each server device. The calculation for constructing the system is performed, and the hardware configuring the system including the connection is implemented.

More specifically, a server device that constitutes the system and resources necessary for constructing the server device (for example, a CPU device, a memory device, a built-in disk device, and a network I / F) are assembled and appropriately Network cable connection to various domains.
For disk devices such as built-in disk devices, it is necessary to connect between necessary devices (for example, controller, enclosure, cache memory, disk, etc.), management cable (network) and controller cable (Fibre Channel). Connect the wires.
In addition, for network devices, IP settings, port settings, and VLAN settings are made, and network cables are connected (connected) to appropriate domains.

Hereinafter, the operation of the shared resource management system of this embodiment will be described for each case.
FIG. 2 is an explanatory diagram illustrating that a failure has occurred in the network I / F 3100 that is a part of the resource of the server 3000 in the shared resource management system according to the embodiment of this invention.
In FIG. 2, a server 1000, a server 2000, and a server 3000 have a cluster configuration and indicate that a failure has occurred in the network I / F 3100.
In this case, the cluster determines that the program on the server 3000 is not operable, and switches the execution of the program to the server 1000.

FIG. 3 is an explanatory diagram illustrating an operation example when a failure occurs in the network I / F 3100 that is a part of the resource of the server 3000.
Since a failure has occurred in the network I / F 3100 (FIG. 2), the server 3000 is removed from the cluster configuration of the server 1000, the server 2000, and the server 3000, and starts as a single server 3000.
The function module 150 collects this state and the failure information of the network I / F 3100 and sends the information to the function module 120 that collects the state / failure information. The function module 120 stores the information in the database 110. To do.

On the other hand, the center manager creates a configuration requirement (generally including a server device) necessary for configuring a new system based on a request from a general user, and newly registers it in the configuration catalog 140 of the database 110.
The functional module 130 recalculates resources managed by itself in order to configure a new system by updating the configuration catalog 140 stored in the database 110.
More specifically, referring to the state / failure information stored in the database 110, each of a plurality of resources (including server devices) constituting the new system described in the configuration catalog 140 currently has a failure. Re-verify whether it is possible to operate.

In the case shown in FIG. 3, a resource that satisfies the configuration request for the new system exists as a server 1000 in the configuration catalog 140.
Therefore, the functional module 130 configures the new system with the server 1000 and implements hardware including connection.

FIG. 4 is an explanatory diagram illustrating another operation example when a failure occurs in the network I / F 3100 that is a part of the resource of the server 3000.
Even in this case, as in the case of FIG. 3, a failure has occurred in the network I / F 3100, but the function module 130 is configured as a server function for the system function realized via the network I / F 3200. Instead of transferring to 3000, it is transferred to the server 5000 that matches the catalog configuration requirements. As a result, the system functions can be distributed, so that the effect of reducing the load concentration can be obtained.

In this case, the functional module 130 implements hardware implementation including connection so that only the system functions realized through the network I / F 3100 can be carried by the server 3000 among the system functions carried by the server 3000. At the same time, with respect to the system functions realized through the network I / F 3200, a new system is assigned to the server 5000 to perform the functions, and hardware including the connection is also implemented.
The status information of the resources of the newly constructed server 5000 is also notified from the function module 150 to the function module 120, and the function module 120 registers the information in the resource database 110.

FIG. 5 is a sequence diagram showing an example of the operation order of the shared resource management system according to the embodiment of the present invention.
In the figure, it is assumed that a server 1000, a server 2000, and a server 3000 are a group of server devices that form a cluster configuration. However, the server 1000 is a standby server device, and the server 2000 and the server 3000 are active server devices.
The server 5000 is assumed to be a single server device.

Under the control of the resource management server 100, the functional module 120 receives status information and failure information notified via the functional module 150 from each server constituting the server device group and the resources constituting the server. Collect and store the information in the database 110.
Here, a case where a failure occurs in the network I / F 3100 that is a part of the resource of the server 3000 will be described.
Since the server 1000, the server 2000, and the server 3000 are a group of server devices that form a cluster configuration, the cluster determines that the program on the server 3000 has become unexecutable due to the failure of the network I / F 3100. The execution of the program to the server 1000 is switched.

First, since a failure has occurred in the network I / F 3100 at timing T1, the server 3000 is removed from the cluster configuration of the server 1000, the server 2000, and the server 3000, and the server 3000 is started as a single server device. The function module 150 collects information indicating this state and failure information of the network I / F 3100.
At timing T2, the functional module 150 sends the state / failure information to the functional module 120.
At timing T3, the functional module 120 stores the state / failure information in the database 110.

After that, at timing T4, the center administrator needs a new resource (generally including a server device) to continue the system request of the general user, and therefore registers a new configuration catalog indicating the configuration in the database 110. (That is, update the configuration catalog 140).
At timing T5, since the contents of the (configuration catalog 140) of the database 110 are updated, the function module 130 (function module for calculating resource allocation) is displayed in the configuration catalog 140 while referring to the failure information and the like of the database 110. Verify whether there are any resources that can be operated and configured from among the configured resources.

Here, among the resources listed in the configuration catalog 140, the network I / F 3100 cannot be used to configure the requested new system, but the network I / F 3200 can be used, and the network Since the system configuration corresponding to the system function realized via the I / F 3200 matches the conditions of the configuration catalog that enabled the execution of the program in the configuration including the server 3000 before the failure occurred, the catalog configuration It is determined that the server 5000 that meets the above requirements is a resource that can be implemented.
This determination is performed by collating the resources described in the configuration catalog with the configuration requirements (CPU device, memory device, built-in disk device, and network I / F) of new resources required including the server device.

In the case of a CPU device, the determination factors as to whether or not mounting is possible are the operating frequency and the number of cores (whether or not resource requirements are satisfied).
In the case of a memory device, the criterion for determining whether or not the above-described mounting is possible is whether or not the memory capacity satisfies the resource requirement.
In the case of a built-in disk device, the determination factors for determining whether or not mounting is possible are a disk capacity and a RAID configuration (whether or not resource requirements are satisfied).

Further, in the case of the network I / F, the determination factors for determining whether or not the above-described implementation is possible are the transfer rate and the number of network I / Fs (whether or not the resource requirement is satisfied).
It is not necessary to connect the network cable manually. All are plugged into the network I / F from the beginning, and are connected using the port VLAN of the Switch and the tag VLAN in the connection above the data link layer. Whether or not a connection to an appropriate domain can be made depends on whether or not resource requirements are satisfied.

At timing T6, the functional module 130 determines that the server 5000 can be mounted, configures the new resource described above based on the new configuration information in the configuration catalog 140, and mounts the server 5000.
Here, “implement” means hardware corresponding to a requested new system without physically moving resources such as a CPU device, a memory device, a built-in disk device, and a network I / F actually required for the server. It is assumed that the hardware is reconfigured only by changing the connection between resources.

At timing T7, the functional module 120 also notifies the resource management server 100 via the functional module 150 about the resource status of the newly constructed server 5000.
At timing T8, the functional module 120 registers the resource state of the newly constructed server 5000 in the resource database 110 as well.

According to the shared resource management system according to the embodiment of the present invention, the status of a resource in which a failure has occurred is collected and the resource status information is stored in the resource database 110. There is an effect that the system can verify and confirm whether or not there is any.
In addition, if there is a failed resource, switch to a part of the resource of another system such as a spare so that a part of the function of the system composed of the failed resource is changed to the other resource. There is an effect that can be automatically switched to a part of the system.
In particular, in the case of a cluster configuration in which a plurality of server devices are currently used and one server device is for standby, the present invention can be applied as a system switching condition.

In addition, it can be applied to a platform that is the foundation for building and operating software, such as PaaS (Platform as a Service), and the effect of being able to share resources with other systems between systems can be obtained.
In addition, the central management center (dedicated center for installing computers and switches) that operates a cloud computing system also has the effect of allowing resources to be shared with other systems between the systems. Yes.

  In addition, a grid computing system (a service that combines multiple computing resources (computation functions such as CPU devices and information storage areas such as hard disk devices) on a wide-area network such as the Internet as a combined computer system. In the present invention, the application of the present invention also has the effect of sharing individual resources among the calculation modules of a plurality of computers.

100 Resource management server (for management)
110 Database 120, 130, 150 Function module 140 Configuration catalog 1000-5000 Server (for resources)
1100-5100 Network I / F (interface)
3100, 3200 Network I / F

Claims (6)

Multiple resources as hardware resources,
Means for collecting status information indicating a status of each of the plurality of resources and fault information indicating a fault status of each of the plurality of resources;
Means for registering the collected status information and failure information in a database;
The hardware configuration of each of a plurality of configured systems is described using at least a part of the plurality of resources as a component, and the hardware configuration of a system to be newly configured is described at least a part of the plurality of resources. A configuration catalog that can be described as a component,
When the configuration catalog is updated, referring to the status information and the failure information, it is confirmed that each of the resources constituting the hardware of the new system specified in the configuration catalog is operable. And means for configuring and implementing the hardware of the system that uses the resource;
A shared resource management system characterized by comprising:   The resource category includes a server device and a CPU device, a memory device, a built-in disk device, and a network I / F (interface) necessary for configuring the server device. The shared resource management system according to claim 1.   3. The shared resource management system according to claim 1, wherein the mounting is performed including connection between the resources.   The plurality of configured systems and the system to be newly configured have a hardware configuration including a general user terminal device connected via a network. The shared resource management system according to claim 1.   3. The shared resource management system according to claim 2, wherein the category of the network includes an Internet network. Hardware connection with multiple resources as hardware resources,
Means for collecting and registering in the database the status information indicating the status of each of the plurality of resources and the fault information indicating the fault status of each of the plurality of resources;
The hardware configuration of each of a plurality of configured systems is described using at least a part of the plurality of resources as a component, and the hardware configuration of a system to be newly configured is described at least a part of the plurality of resources. A configuration catalog that can be described as a component,
When the configuration catalog is updated, referring to the status information and the failure information, it is confirmed that each of the resources constituting the hardware of the new system specified in the configuration catalog is operable. And means for configuring and implementing the hardware of the system that uses the resource;
A resource management server device comprising:

Images