Patent Application
20160006630
The present invention relates to a technology to select and control a node such as computer or storage apparatus included in a computer system.
When a target node is to be selected from a plurality of apparatuses (nodes) having different configurations, such as when a back-up computer for an active computer is to be selected upon fail-over or a computer to install new software is to be selected, it is sometimes necessary to evaluate the degree of similarity to the past configuration information. When an apparatus needs to be replaced due to fail-over of computer (JP2011-258233 A) or volume transfer of storage, for example, the combination of apparatuses in the host computer may have changed from the combination at the time when the host computer was constructed and tested.
When the combination of apparatuses of the host computer changes, malfunction (freeze or performance degradation) possibly occurs due to the compatibility between the respective apparatuses, compatibility between an apparatus and software, or the like after the apparatus is replaced. In other words, the conventional example had a problem of not being able to determine whether or not the combination of the standby host computer can ensure stable operation.
In order to solve this problem, the present invention is aiming at making it possible to evaluate whether or not the new combination of apparatuses can ensure stable operation in advance before the change in apparatuses configuration of the host computer occurs.
The present invention includes an evaluation method of a computer system that includes a management computer having a processor and a memory and coupled with a host computer and a storage apparatus via a switch apparatus, the management computer being configured to evaluate components of nodes including the host computer and the storage apparatus, the evaluation method comprising: a first step wherein, when one of the nodes performs a prescribed task, the management computer obtains a replaceable part value group containing configuration information for components of a group that includes the node, and stores the obtained replaceable part value group in history information; a second step wherein the management computer receives at least one node to be evaluated; a third step wherein the management computer obtains a replaceable part value group containing configuration information for respective components of a group that includes said node to be evaluated, and stores the obtained replaceable part value group in history comparison target information; a fourth step wherein the management computer selects a combination of the history comparison target information and the history information having matching elements; a fifth step wherein the management computer calculates an evaluation value for the selected combination of the history comparison target information and the history information; and a sixth step wherein the management computer outputs a combination of an evaluation value and a node identifier indicating the history comparison target information and the history information having the matching elements.
According to the present invention, the management computer can store the operation history of each combination of apparatuses, and evaluate the similarity of the configuration of node to be selected to the configurations of nodes in the operation history based on the evaluation values. This allows the management computer to select a node having a configuration similar to that of an apparatus that has a proven operation history with ease, and as a result, it is possible to reduce occurrences of malfunction (such as freeze or performance degradation) after fail-over or installation of software, for example.
Embodiments of the present invention will be explained with reference to the figures.
The management computer 100 is a computer that is operated by program control, and includes NIC (network interface card) coupled with the switch apparatus 111-2. This NIC is illustrated as the management interface 107 in
The management computer 100 communicates with the host computer 200, the storage apparatus 300, and the input/output apparatus 110, which are coupled with the management network 400-2, via the switch apparatus 111-2. The management computer 100 manages at least one of the host computer 200, the storage apparatus 300, and the switch apparatus 111, which are coupled with the management network 400-2, and controls those managed apparatuses and acquires information from those managed apparatuses. Below, the apparatuses that are managed by the management computer 100 will be referred to as managed nodes. The management computer 100 operates an evaluation part 101. The evaluation part 101 will be explained in detail with
The host computer 200 is a computer that is operated by program control, and includes NIC and HBA (host bus adapter) coupled with the switch apparatus 111. This NIC is illustrated as the management interface 206 in
The host computer 200-1 communicates with the other host computer 200-2, the input/output apparatus 111, the storage apparatus 300 and the management computer 100, which are coupled with the management network 400-2, via the switch apparatus 111. The internal configuration of the host computer will be explained with reference to
The switch apparatus 111 contains one or more network apparatuses. Specific examples of the network apparatus include network switch, router, load balancer, firewall, and fiber channel switch.
The management network 400-2 allows for communications between the respective devices coupled with the switch apparatus 111-2 such as the management computer 100. The respective apparatuses coupled with the management network 400-2 or the network 400-1 exchange data and control information, which are processed by respective apparatuses or programs that run on the apparatuses.
The storage apparatus 300 includes FC (fiber channel) and LAN interface, and contains at least one disk (or non-volatile memory medium) that is to be used by the management computer 100 and the host computer 200. The internal configuration of the storage apparatus 300 will be explained with reference to
The input/output apparatus 110 is coupled with respective parts of the computer system such as the management computer 100 to input commands and to output responses to the commands. Specific examples of the input apparatus of the input/output apparatus 110 include a keyboard, a mouse, a touch panel, and a client computer apparatus to which those devices are connected. Specific examples of the output apparatus of the input/output apparatus 110 include a display and a client computer apparatus to which the display is connected. The input/output apparatus 110 contains NIC coupled with the switch apparatus 111-2, and through the NIC, the input/output apparatus 110 is coupled with the management computer 100 and the like, but it is also possible to couple the input/output apparatus directly with the management computer 100 and the like.
The evaluation part 101, the group management part 102, the configuration management part 103, and the task management part 104 may be implemented by hardware, firmware, or a combination thereof built in the management computer 100.
The respective programs that function as the evaluation part 101, the group management part 102, the configuration management part 103, and the task management part 104 are loaded into the memory 106, and then executed by the CPU of the control apparatus 105. The respective programs that function as the evaluation part 101, the group management part 102, the configuration management part 103, and the task management part 104 are stored in an auxiliary memory (or built-in disk) 108 in the management computer 100. Alternatively, the respective programs may be stored in the storage apparatus 300 coupled with the management computer 100 via the network 400.
The evaluation part 101 calculates evaluation values that each indicates the degree of similarity of one or more managed nodes, which are the evaluation targets, based on the operation history. The operation history is information collected from one or more managed nodes, and includes the configuration, status, and settings of the components of the nodes such as apparatuses, internal parts, and programs that run on the apparatus. In other words, the operation history is the information containing the past operation status of the components of each managed node. Below, those components will be referred to as replaceable parts. Specific examples of the apparatus information include chassis identifiers, model identifiers, product identifiers, lot numbers, serial numbers, and vendor names. Specific examples of the program information include product names, program names, build numbers, version information, revision information, and vendor names regarding software such as OS, business application, driver, and firmware. The replaceable parts are devices (such as I/O device) required to operate the OS and applications upon fail-over or take-over, for example, and if the driver used by the OS in the active system is hardware that can be used as is, such a device is a replaceable part.
The evaluation part 101 generates the operation history before a history similarity calculating process 1013 is performed, using component information 1230 periodically collected from the managed nodes by the configuration management part 103. The history similarity calculating process 1013 is a process to calculate, as evaluation values, the degrees of similarity between the respective components by comparing the value of operation history and the value of history comparison target information 1017 collected from one or more managed nodes, i.e., the evaluation target. The history comparison target information 1017 and the calculation of evaluation values will be explained with reference to
In order to perform the history similarity calculating process 1013, the evaluation part 101 includes a history information generating process 1011, a replaceable part value obtaining process 1012, trigger information for generating history information 1014, replaceable part defined information 1015, history information 1016, and history comparison target information 1017, each of which will be explained later with reference to
The group management part 102 manages information for coupling and usage relationships of one or more managed nodes. The group management part 102 includes group information 1220 that groups together one or more managed nodes based on the coupling and usage relationships, and a group information control process 1221 updating the group information 1220 based on the configuration information for the managed node obtained from the configuration management part 103 or a request from the user. An example of the group information will be explained with reference to
The configuration management part 103 collects and stores configuration information 1230 of the host computer 200, the storage apparatus 300, and the switch apparatus 111 by conducting a configuration information control process 1231 at a prescribed interval. Examples of the configuration information 1230 include host names, IP addresses, virtual server names, logical partition configurations, volume configurations, virtual machine configurations, port numbers, and coupling and usage relationships between the storage apparatuses, the host computers and the switch apparatuses.
A part of the configuration information 1230 collected by the configuration management part 103 is used for the history similarity calculating process 1013 of the evaluation part 101, or the update process for the group information 1220 of the group management part 102. Below, the configuration information 1230 only contains information relating to the history similarity calculating process 1013 of the evaluation part 101. An example of the configuration information 1230 will be explained with reference to
The task management part 104 holds task information 1240 collected by a task information control process 1241. The task information 1240 includes types of tasks given to the respective managed nodes and the management computer 100 such as information acquisition or control, and execution results of such tasks. An example of the task information 1240 will be explained with reference to
The CPU of the control apparatus 105 achieves the functions of the above-mentioned function parts, respectively, by performing processes in accordance with the respective programs thereof. For example, the CPU of the control apparatus 105 functions as the evaluation part 101 by performing processes in accordance with the evaluation program. The same applies to other programs. The CPU of the control apparatus 105 also operates as a function part that achieves each of a plurality of processes performed in each program. The computer and computer system are a device and system that contain these function parts.
The programs for realizing the respective functions of the evaluation part 101, the group management part 102, the configuration management part 103, and the task management part 104 can be stored in a storage device such as a storage sub-system apparatus, a non-volatile semiconductor memory, hard disk drive, or SDD (solid state drive), or a computer-readable non-transitory data storage medium such as IC card, SD card, or DVD.
The storage apparatus 300 is coupled with the management network 400-2 via the management I/F 330. The disk apparatus 303 includes one or more disk volumes 320-1, 320-2.
In the example shown in the figure, the trigger ID=2, which is for the task identifier of “reconnection,” is defined as a trigger for the history information generating process 1011. As described below, a successful execution of the task specified by the task identifier triggers the history information generating process 1011.
A defined ID 800 is a unique ID that is given to an entry of the replaceable part defined information 1015. A part information identifier 801 is a unique identifier for a replaceable part. The part information identifier 801 is generated by the evaluation part 101 based on information defined by the configuration management part 103 and the respective apparatuses of the managed nodes.
For example, when the evaluation part 101 requires a chassis name for the history similarity calculating process 1013, and when the value obtained by the evaluation part 101 from a chassis_ID acquisition I/F, which is externally published by the host computer 200, is used for a chassis name, the part information identifier 801 is named “Server_Chassis_ID” with the prefix “Server_” that denotes the host computer 200. An evaluation coefficient 802 is a weighing factor used for calculation in the history similarity calculating process 1013 by the evaluation part 101 as described below. The evaluation coefficient 802 indicates the degree of difference in environments for operating the OS 210, and the greater the evaluation coefficient 802 is, the more different the operating environment is from the initial environment in which the OS 210 was first installed.
The entries of the history information 1016 may be updated by adding new entries constantly as in the form of a log, or overwriting the existing entries having the same history No. 901.
An acquisition time 902 is the time at which the history information 1016 was generated. A node ID 903 is an ID for a managed node specified by an entry of the history information 1016. The node ID 903 corresponds to a node ID 1200 of the configuration information 1230.
A part defined ID 904 is an identifier for the replaceable part defined information 1015 registered as the operation history. The part defined ID 904 corresponds to the defined ID 800 of the replaceable part defined information 1015. A part information value 905 is a value indicating the operation history for the part defined ID 904. The part information value 905 corresponds to a component value 1202 of the configuration information 1230.
In the example of
A part defined ID 1002 is an identifier of the replaceable part defined information 1015 registered as the operation history. The part defined ID 1002 corresponds to the defined ID 800 of the replaceable part defining information 1015. A part information value 1003 is a value indicating the operation history for the part defined ID 904 of the history information 1016 of
In the example of
A node ID 1200 is an identifier of a managed node. A configuration identifier 1201 identifies an item of the configuration information 1230. In the present embodiment, the value of the configuration identifier 1201 corresponds to that of the defined ID 800 of the replaceable part defined information 1015, but alternatively, the configuration identifier 1201 may be determined based on the part information identifier 801 shown in
In the example of
In the example illustrated in the figure, the task specified by the task ID 1301=Coldstandby_test has been successfully executed at the target node 1303=1. Coldstandby_test is a task to conduct a process handover test from an active system to a back-up system on cold standby.
In the history information generating process 1011, when new task information 1240 is generated and inputted, the following processes are conducted to generate the history information 1016 for a group that includes the managed node for which the task is to be implemented. The task information 1240 is generated by the task management part 104. An administrator or the like gives an instruction to implement a task through the input/output apparatus 110 to the host computer 200 via the management computer 100, and the task management part 104 of the management computer 100 obtains the result of the task from the host computer 200, which is then added to the task information 1240.
The history information generating process 1011 extracts the execution result 1302 for the inputted task information 1240, and determines whether the execution result indicates success or not (Step S1400). If the execution result 1302 indicates success, the process moves to Step S1401, and if the result indicates failure, the process is ended.
The history information generating process 1011 obtains a task identifier 1301 from the inputted task information 1240, and determines whether this task identifier 1301 exists as an entry in the trigger information 700 for generating history information or not (Step S1401, S1402). If the entry of the task identifier 1301 exists in the trigger information 700 for generating history information, the process moves to Step S1403. If the entry of the task identifier 1301 does not exist in the trigger information 700 for generating history information, the process is ended (Step S1402).
The history information generating process 1011 obtains, from the group information 1220, group IDs 1100 that include the target nodes 1303 of the inputted task information 1240 (Step S1403). The history information generating process 1011 selects one group ID from the group IDs obtained in Step S1403, and calls upon the replaceable part value obtaining process 1012, which will be described later, to receive a replaceable part value group (Step S1404). The replaceable part value group is made up of components that are selected from the configuration information 1230 and that are similar to the components of the group ID 1100 including the node to implement the task, as explained with
The history information generating process 1011 sets, to the history information 1016 (
The history information generating process 1011 determines whether the replaceable part value obtaining processes 1012 have been conducted for all of the group IDs 1100 obtained in the Step S1403 or not (S1406). If the replaceable part value obtaining processes 1012 have been conducted for all of the group IDs 1100, the process is ended, and if not, the process returns to Step S1404, and the above-mentioned steps are repeated.
Through the above-mentioned process, when the task information 1240 is generated and the execution result of the task indicated success, the replaceable part value group for each group ID 1100 that includes the managed node to implement the task is set to the history information 1016.
The replaceable part value obtaining process 1012 is called upon in Step S1404 of the history information generating process 1011 in order to generate the history information 1016. The replaceable part value obtaining process 1012 is also called upon in Step S1603 of the history similarity calculating process 1013 shown in
The replaceable part value obtaining process 1012 obtains the current time based on the OS run by the evaluation part 101, BIOS of the management computer 100, or the like. The replaceable part value obtaining process 1012 determines the history No. 901 of the history information 1016 shown in
The replaceable part value obtaining process 1012 obtains one node ID 1101 associated with the inputted group ID 1100 with reference to the group information 1220, and sets this node ID 1101 for the next process node ID (Step S1502).
The replaceable part value obtaining process 1012 then obtains one entry associated with the process node ID with reference to the configuration information 1230 (Step S1503). The replaceable part value obtaining process 1012 obtains the configuration identifier 1201 and the component value 1202 from the entry of the configuration information 1230 obtained in the previous step (Step S1504).
The replaceable part value obtaining process 1012 groups together the process node ID, the current time obtained in Step S1500, the history No. determined in Step S1501, and the configuration identifier 1201 and the component value 1202 obtained in Step S1504 into one replaceable part value group (Step S1505). This replaceable part value group is the information that is set as an entry of the history information 1016 and the history comparison subject information 1017.
The replaceable part value obtaining process 1012 determines whether another entry associated with the process node ID exists or not with reference to the configuration information 1230 (Step S1506). If another entry exists, the process goes back to Step S1503, and the above-mentioned steps are repeated. On the other hand, if no entry that corresponds to the process node ID exists, the process moves to Step S1507.
The replaceable part value obtaining process 1012 determines whether the replaceable part value group has been acquired for all node IDs for the input group ID or not (or in other words, whether there is an unprocessed node ID or not) with reference to the group information 1220 (Step S1507). If an unprocessed node ID still exists, the process goes back to Step S1503, and the above-mentioned steps are repeated. On the other hand, if the replaceable part value group has been acquired for all of the node IDs corresponding to the input group ID, the process moves to Step S1508. Then, the replaceable part value obtaining process 1012 calls upon and returns the replaceable part value groups to the original process (Step S1508), and the process is ended.
Through the process described above, the node IDs 1101 that correspond to the input group ID are obtained from the group information 1220, and a configuration identifier 1201 and a component value 1202 are obtained for each of the node IDs 1101, which are then grouped into a replaceable part value group. Thereafter, the obtained replaceable part value groups are sent to the original process that called upon the replaceable part value obtaining process 1012.
The history similarity calculating process 1013 receives an input of at least one node ID, which is the comparison target for the operation history, and by generating the history comparison target information 1017 and comparing the generated history comparison target information 1017 with the history information 1016, outputs the evaluation value.
The history similarity calculating process 1013 is called upon through the evaluation part 101 when the management computer 100 or the administrator who operates the management computer 100 through the input/output apparatus 110 conducts the history similarity calculating process 1013 for two or more managed nodes based on the operation history.
The history similarity calculating process 1013 is conducted when selecting a destination node to transfer the current active node from two or more standby nodes, and when selecting a host computer for installing a software program of OS or the server virtualization part from two or more new host computers 200, for example.
The history similarity calculating process 1013 is started when one or more node IDs are received. The history similarity calculating process 1013 selects one node ID from the received node IDs, and sets the node ID as the process node ID (Step S1600).
The history similarity calculating process 1013 initializes a prescribed variable that holds a new evaluation value (Step S1601). In the present invention, the new evaluation value is initialized to 1. The history similarity calculating process 1013 obtains a group ID 1100 that corresponds to the process node ID from the group information 1220, and sets the obtained value as the process group ID (Step S1602).
The history similarity calculating process 1013 calls upon the replaceable part value obtaining process 1012 shown in
The history similarity calculating process 1013 obtains an entry of the history information 1016 associated with one history No. 901 (Step S1605).
The history similarity calculating process 1013 searches for matching combinations of the part defined IDs (904, 1002) and the part information values (905, 1003) among the history comparison target information 1017 set in Step S1604 and the entry of the history information 1016 obtained in Step S1605, by comparing respective values (Step S1606).
The history similarity calculating process 1013 calculates and updates a new evaluation value using the number of matching combinations of the part defined IDs (904, 1002) and part information values (905, 1003) obtained in Step S1606, or evaluation coefficients 802 for the matching part defined IDs (904, 1002). The evaluation coefficients 802 are associated with the defined IDs 800 that correspond to the part defined IDs 904, and are obtained from the replaceable part defined information 1015 by the history similarity calculating process 1013.
The history similarity calculating process 1013 calculates a new evaluation value by adding four (quantity of items) to the evaluation value when there are four matching items, for example, or multiplying the evaluation value by two (evaluation coefficient 802 of Server_Chassis_ID) when Server_Chassis_ID of
The history similarity calculating process 1013 determines whether the evaluation values have been calculated for all of the input node IDs or not (Step S1608). If the evaluation values have been calculated for all of the input node IDs, the process moves to Step S1609, and after outputting the combinations of the node IDs and evaluation values, the process is ended.
Through the above-described process, with respect to the input of the node IDs to be evaluated, replaceable part value groups for the components of the group IDs that include the input node IDs are obtained and stored in the history comparison target information 1017. The history similarity calculating process 1013 of the evaluation part 101 then selects combinations of the history comparison target information 1017 and the history information 1016 with matching elements (part defined IDs, part information values), and calculates evaluation values for those combinations of the history comparison target information 1017 and the history information 1016 with matching elements. Thereafter, the history similarity calculating process 1013 of the evaluation part 101 outputs the respective combinations of the node IDs and evaluation values for the history comparison target information 1017 and the history information 1016 with matching elements.
Through this process, evaluation values are calculated based on the history comparison target information 1017 and the history information 1016 having matching combinations of the part defined IDs 1002 and the part information values 1003, and it is possible to evaluate the degree of similarity of the operation history of respective combinations of apparatuses and the operation history of the configurations of the available nodes. This allows the management computer 100 to select a node that has a configuration similar to the apparatus with proven operation history with ease, and the occurrence of problems (freeze or performance degradation) after fail-over or installation of software can be suppressed.
In Embodiment 1 above, the process to evaluate the degree of similarity of replaceable part defined information 1015 to the operation history was described. In Embodiment 2, the replaceable part defined information 1015 has a priority level.
The priority level 1700 is set based on the granularity of part information identifier 801, or in other words, based on the size of the effect of a change in replaceable part defined information on a host system. For example, Server_Chassis_ID, which is the chassis information of the host computer 200, has a larger granularity than that for Server_Driver_VR, which is the driver version information, i.e., one component of the host computer 200 (or in other words, a change in chassis information causes a change on the chassis level), and therefore, the priority level of Server_Chassis_ID is higher. The priority level 1700 is related to the order to calculate evaluation values in the history similarity calculating process 1013. In the example of the figure, the smaller the value under the priority level 1700 is, the higher the priority is.
The necessity flag 1701 indicates whether comparison values for the part information identifiers 801 need to match or not in the history similarity calculating process 1013. In the present embodiment, Y (true) indicates that it is necessary, and N (false) indicates that it is not necessary, but true/false values or values that correspond to true/false values may alternatively be used. In the history similarity calculating process 1013, if the values for the part information identifiers with the necessity flag 1701 indicating True do not match, the evaluation value is invalid (0 or negative value, for example).
The history similarity calculating process 1013 of
For this reason,
The history similarity calculating process 1013 obtains, in Step S1800, one node ID that corresponds to the process group ID, and sets the obtained value for the process node ID (Step S1800).
The history similarity calculating process 1013 obtains the part defined ID 904 that corresponds to the process node ID with reference to the history information 1016. The history similarity calculating process 1013 then obtains the priority level 1700 of the defined ID 800 that corresponds to the part defined ID 904 with reference to the replaceable part defined information 1015.
The history similarity calculating process 1013 obtains a defined ID 800 that has the next highest priority level 1700 to the obtained priority level 1700, and determines whether combinations of part defined IDs and part information values match each other among the history comparison target information 1017 and the entry of the history information 1016 (Step S1801). If the combinations match, the process moves to Step S1803, and if not, the process moves to S1809 (Step S1802).
The history similarity calculating process 1013 obtains an evaluation coefficient 802 associated with the matching part defined ID (904, 1002, 800), and updates the evaluation value by calculating a new evaluation value using the evaluation coefficient 802 (Step S1803).
The history similarity calculating process 1013 then determines whether the process from Step S1801 to Step S1803 has been completed for the process node ID (Step S1804). If the process for the process node ID has been completed, the history similarity calculating process 1013 moves to Step S1805, and if not, returns to Step S1801 and repeats the steps described above.
The history similarity calculating process 1013 determines whether the process from Step S1800 to Step S1804 has been completed for the process group ID (Step S1805). If the process from Step S1800 to Step S1804 for the process ID has been completed, the history similarity calculating process 1800 moves to Step S1608, and if not, returns to Step S1800 and repeats the steps described above.
In Step S1802, if the history comparison target information 1017 and the history information 1016 are deemed not matching, the history similarity calculating process 1013 determines whether the necessity flag 1701 for the part defined ID (904, 1002) and the defined ID (800) indicates False or not (Step S1809). If False, the process moves to Step S1804, and conducts the above-mentioned process. If the necessity flag 1701 indicates True, the process moves to Step S1810. The history similarity calculating process 1013 makes the current evaluation value invalid (0 or negative value, for example) because the necessity flag indicates True (Step S1810).
As described above, with Embodiment 2 of the present invention, in the case where the replaceable part defined information 1015 has the priority level, the similarity of the specific components of the managed nodes to the operation history can be calculated as evaluation values, and based on the evaluation values, the similarity can be evaluated.
Embodiment 2 described the process to calculate the similarity of the specific components of the managed nodes to the operation history as evaluation values when the replaceable part defined information 1015 has a priority level. Embodiment 3 describes a process to control the managed nodes based on the evaluation values calculated in Embodiment 1 or Embodiment 2 above (fail-over, for example).
The control part 1900 changes the configuration or status of the managed nodes in accordance with a request from the management computer 100 or an administrator operating the management computer 100. Examples of the request include fail-over of a host computer 200, or installation of software such as OS or server virtualization part in a new host computer 200. In the present embodiment, the control scope of the control part 1900 is separated from the control scopes of the group information control process 1221, the configuration information control process 1231, and the task information control process 1241, but these control scopes may be consolidated into the control part 1900.
The control part 1900 determines whether or not there is only one candidate node ID (Step S2001). If there is only one candidate node ID, the process moves to Step S2004 where the control is implemented. If there are more than one node IDs, the process moves to Step S2002 to select a candidate node ID having the greatest evaluation value.
The control part 1900 calls upon the history similarity calculating process 1013 for the candidate node IDs (Step S2002). The control part 1900 obtains combinations of the candidate node IDs and evaluation values from the history similarity calculating process 1013, and then selects, as the candidate node ID, a node ID having the greatest evaluation value from the combinations of node IDs and evaluation values (Step S2003). The control part 1900 implements the control in accordance with the task request information on the candidate node ID selected above (Step S2004).
With the present embodiment, the evaluation part 101 can control the managed node based on the calculated evaluation values (fail-over, for example). In the example of the fail-over, selecting a node with a greater evaluation value makes it possible to select a destination node having a higher degree of similarity to the components of the originating node. This reduces a change in components of the node that runs OS or applications after transfer, and stable operation of the OS and applications in a new node is ensured. In other words, by reducing a change in components of the destination node, a change in running environment of software can be suppressed, which prevents occurrence of freeze or degradation of process capability.
The external network 401 is the Internet with the encrypted communication capability, or wide area network connected via special lines. The remote management computer 2101 communicates with the management computer 100 in the computer system 2100 via the external network 401, thereby operating the evaluation part 101.
Any one of the evaluation parts 101 of Embodiment 1 to Embodiment 3 may be used. In this case, in a manner similar to Embodiment 1 to Embodiment 3 above, combinations of node IDs and evaluation values in each computer system 2100 can be calculated.
The above-described configurations, functions, and processors, for all or a part of them, may be implemented by dedicated hardware.
The above-described software may be stored in an electric, electromagnetic, or optical storage device or the like, and may be downloaded to a computer via a network such as internet.
This invention is not limited to the above-described embodiments but includes various modifications. The above-described embodiments are explained in details for better understanding of this invention and are not limited to those including all the configurations described above.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2013/063764 | 5/17/2013 | WO | 00 |
