JP6293683B2 - Computer system and coping method for performance failure of computer system - Google Patents

Description

  The present invention relates to management of cloud services.

  A service providing form called a cloud, which provides a computer resource and a service that operates on the computer resource via the Internet and charges a user according to the use, is widely used.

  Initially, since the cloud is difficult to provide stable performance because it is accessed via the Internet, the cloud has been used in applications that require relatively low performance such as backup. However, in recent years, there are many cases where online businesses are operated on the cloud, and stability of performance is required for the cloud.

  As one of the technologies for realizing this, a function of automatically scaling the virtual machine according to the load status of the virtual machine on the cloud is known. For example, in the Web three-tier system provided using the cloud, the above-described technology is applied to the front-end Web server. By increasing or decreasing the number of virtual machines corresponding to the Web server, the load balance of the Web three-tier system is maintained.

  In order to maintain the performance of the entire system, it is necessary to increase the DB server on the back end side as the Web server is scaled. As a method for dealing with the performance failure of the DB server, for example, there is a technique for analyzing the cause of the bottleneck of the DB server in Patent Document 1 or the like.

  Patent Document 1 describes managing the performance of a DB server and analyzing a bottleneck, resizing server resources according to the analysis result, and the like.

US Pat. No. 7,526,508

  In conventional DB server failure handling technology, a management computer or the like detects a performance degradation of a DB server and analyzes the cause of the performance degradation, thereby causing a bottleneck such as a shortage of CPU resources or a lack of I / O latency. Identify the location and calculate the amount of the missing resource.

  In the cloud environment, it is necessary to select a coping method that prioritizes the coping time for a failure or a coping method that prioritizes the cost in accordance with the contract contents of the service.

  However, in the conventional technology, it is not possible to determine which countermeasure is preferentially executed in consideration of the contract contents of the service and whether each countermeasure can be executed in consideration of the cloud configuration. There is a problem that an appropriate DB server failure for guaranteeing the performance of the system in the cloud cannot be handled. Therefore, there is a need for a DB server scale-up technique in a cloud environment.

  A typical example of the invention disclosed in the present application is as follows. That is, a computer system including a plurality of computers, wherein the plurality of computers includes at least one first computer that manages the computer system and computer resources for constructing a business system used for a user's business. A plurality of second computers provided, wherein the at least one first computer is connected to a first processor, a first memory connected to the first processor, and the first processor; Each of the plurality of second computers includes a second processor, a second memory connected to the second processor, and a second memory connected to the second processor. The business system includes at least one interface and a storage device, and the business system can change processing performance by executing scale-out processing. 1 business computer and a plurality of business computers whose processing performance can be changed by executing a scale-up process, wherein the at least one first computer is a plurality of business systems constructed on the computer system. Service requirement management information for managing the service requirements, and coping management information for managing coping methods that are control methods for improving performance degradation for each type of computer resource when performance degradation of the business computer is detected And a processing procedure management information including an order for determining whether or not the processing method can be executed on the business computer in which performance degradation is detected. A procedure generation unit, and the service requirement includes a condition for guaranteeing performance of each of the plurality of business computers included in the business system, the business system Each of the plurality of countermeasures included in the countermeasure management information corresponds to the countermeasures, including information regarding the operating conditions of each of the plurality of business computers and the accounting system conditions of the business system. The handling procedure generation unit selects a target business system for generating the handling procedure management information, and the plurality of business computers included in the target business system are managed. A processing target business computer is selected, a target computer resource in the processing target business computer is selected, and based on the service requirement management information, among the plurality of processing methods included in the processing method management information From the above, select a plurality of countermeasures that match the service requirements of the target business system, and determine whether or not the selected plurality of countermeasures can be executed. The coping procedure management information is generated by determining the determination order.

  According to the present invention, the handling procedure generation unit can generate handling procedure management information for dealing with performance degradation of a business computer (DB server) based on service requirements of a business system (tenant). As a result, it is possible to satisfy the service requirements and realize efficient failure recovery of the business computer.

  Problems, configurations, and effects other than those described above will become apparent from the description of the following examples.

It is explanatory drawing which shows the structural example of the system which implement | achieves the cloud service of Example 1. FIG. It is explanatory drawing which shows the structural example of the cloud system of Example 1. FIG. 3 is a block diagram illustrating an example of a hardware configuration and a software configuration of a cloud management computer according to the first embodiment. FIG. FIG. 3 is a block diagram illustrating an example of a hardware configuration and a software configuration of the infrastructure management computer according to the first embodiment. It is explanatory drawing which shows an example of the input screen displayed via a portal when the cloud user of Example 1 inputs a policy. It is explanatory drawing which shows an example of the service requirement management information of Example 1. It is explanatory drawing which shows an example of the policy management information of Example 1. FIG. FIG. 6 is an explanatory diagram illustrating an example of DB failure handling method management information according to the first embodiment. It is explanatory drawing which shows an example of the cloud infrastructure configuration information of Example 1. FIG. 3 is an explanatory diagram illustrating an example of computer resource allocation information according to the first embodiment. It is explanatory drawing which shows an example of the server resource usage status information of Example 1. FIG. 3 is an explanatory diagram illustrating an example of storage resource usage state information according to the first embodiment. FIG. 3 is an explanatory diagram illustrating an example of storage configuration information according to the first embodiment. It is explanatory drawing which shows an example of the handling procedure management information of Example 1. FIG. It is explanatory drawing which shows an example of the handling procedure management information of Example 1. FIG. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment. 6 is a flowchart illustrating an example of a handling procedure generation process (A) executed by the cloud management computer according to the first embodiment. 10 is a flowchart illustrating an example of a handling procedure generation process (B) executed by the cloud management computer according to the first embodiment. It is explanatory drawing which shows an example of the handling procedure management information produced | generated by performing the handling procedure production | generation process (B) of Example 1. FIG. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. 6 is a flowchart illustrating an example of processing executed by the cloud management computer according to the first embodiment in accordance with handling procedure management information. It is explanatory drawing which shows an example of the handling procedure management information of Example 2. 10 is a flowchart illustrating an example of processing executed by the cloud management computer according to the second embodiment in accordance with handling procedure management information. 10 is a flowchart illustrating an example of processing executed by the cloud management computer according to the second embodiment in accordance with handling procedure management information. 10 is a flowchart illustrating an example of processing executed by the cloud management computer according to the second embodiment in accordance with handling procedure management information. 10 is a flowchart illustrating an example of processing executed by the cloud management computer according to the second embodiment in accordance with handling procedure management information.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is an explanatory diagram illustrating a configuration example of a system that implements the cloud service according to the first embodiment.

  In the first embodiment, the system includes the cloud system 90 and the portal 30. The cloud system 90 and the portal 30 are connected via the network 40. The network 40 may be the Internet or the like, but is not limited to the type of network. Further, the connection method between the cloud system 90 and the portal 30 may be either wireless or wired.

  The cloud system 90 is a system in which a tenant 50 that is a business system of the cloud user 10 is constructed. In FIG. 1, a web three-tier system including a load balancer 60, a web server 70, and a DB server 80 is shown as an example of a tenant 50 used by the cloud user 10. In the cloud service, generally, the load balancer 60, the Web server 70, and the DB server 80 are realized using a virtual machine 600 described later.

  Since the tenant 50 of each cloud user 10 coexists in the cloud system 90, an operation corresponding to each tenant 50 is required. For example, when the service level of each tenant 50 is different, the operation of the tenant 50 according to the service level is required.

  The portal 30 is a user interface provided to the cloud user 10. The cloud user 10 applies for service, confirms service contents, or monitors resources in the tenant 50 via the portal 30.

  In the first embodiment, a cloud service in which the cloud user 10 pays a usage fee and uses a computer resource provided by the cloud system 90 via the network 40 is assumed. In the first embodiment, processing executed when the cause of performance degradation of the DB server 80 is a shortage of CPU resources will be described.

  FIG. 2 is an explanatory diagram illustrating a configuration example of the cloud system 90 according to the first embodiment.

  The cloud system 90 includes a cloud management computer 100, a infrastructure management computer 200, a host computer 500, a network connection device 400, a storage device 300, and a billing computer 800. Each device is connected to the cloud management computer 100 via the management network 700.

  The cloud management computer 100 manages a cloud service provided to the cloud user 10. The hardware configuration and software configuration of the cloud management computer 100 will be described later with reference to FIG. The infrastructure management computer 200 manages cloud-based computer resources including the host computer 500, the network connection device 400, and the storage device 300. For example, the infrastructure management computer 200 performs monitoring of the cloud system 90, allocation of computer resources, failure processing, and the like. The billing computer 800 calculates a usage fee according to the usage status of the cloud user 10.

  The cloud administrator 20 manages the cloud system 90 using the cloud management computer 100 or the infrastructure management computer 200.

  The host computer 500 provides computer resources to be allocated to the tenant 50. The host computer 500 includes a CPU, memory, I / O device, and storage medium (not shown). In the first embodiment, a cluster 900 is configured using a plurality of host computers 500.

  The host computer 500 has a virtualization function. The virtualization function can be realized using, for example, a hypervisor. The host computer 500 generates and manages one or more virtual computers 600 using a virtualization function.

  In the virtual machine 600, the guest OS 620 operates. On the guest OS 620, the DB 610 is executed as an application. The present embodiment is not limited to the type of application executed on the guest OS 620.

  The virtual computer 600 has a virtual CPU, a virtual memory, and the like. Data accessed by the guest OS 620 or the DB 610 is stored in the virtual disk 630. Further, a volume 640 provided by the storage apparatus 300 is allocated to one host computer 500. The host computer 500 allocates a part of the storage area of the volume 640 to each virtual computer 600 as a virtual disk 630.

  The volume 640 may be realized using a storage medium such as an HDD (Hard Disk Drive) provided in the host computer 500, or may be realized using a logical storage area 310 of the storage apparatus 300 described later.

  The network connection device 400 connects the host computer 500 and the storage device 300. The network connecting the host computer 500 and the storage apparatus 300 may be, for example, SAN or LAN, but is not limited thereto.

  The storage device 300 provides a storage area used by the virtual machine 600. The storage apparatus 300 includes a controller, a disk interface, and a plurality of storage media (not shown).

  The storage apparatus 300 according to the first embodiment has a thin provisioning function, manages each storage area of a plurality of storage media as a virtual storage pool 320, and uses a part of the storage area of the storage pool 320. A logical storage area 310 is generated. The storage apparatus 300 provides the logical storage area 310 to the host computer 500 as a storage area for realizing the volume 640 or the like.

  In the first embodiment, by sharing a storage area provided by the storage apparatus 300 in units of clusters 900, it is possible to optimize the arrangement of the virtual machines 600 among the host computers 500 in the cluster 900.

  In the first embodiment, the cloud management computer 100 and the infrastructure management computer 200 are described as separate computers, but the cloud management computer 100 and the infrastructure management computer 200 may be realized using a single computer.

  FIG. 3 is a block diagram illustrating an example of a hardware configuration and a software configuration of the cloud management computer 100 according to the first embodiment.

  The cloud management computer 100 includes an arithmetic processing unit 180, a program memory 1000, a data input / output cache memory 160, a storage medium 170, a management communication interface 110, an input interface 120, and an output interface 125 as hardware configurations. . Each component of the cloud management computer 100 is connected to each other via a bus 190.

  The arithmetic processing unit 180 is a device that performs various calculations such as a CPU. When the arithmetic processing unit 180 executes a program stored in the program memory 1000, the functions of the cloud management computer 100 can be realized. In the following description, when a process is described mainly with a program, it indicates that the program is being executed by the arithmetic processing unit 180.

  The program memory 1000 stores various programs executed by the arithmetic processing unit 180 and information used by the various programs. The program memory 1000 may be a magnetic storage device or a volatile semiconductor memory, but is not limited thereto. Various programs and information stored in the program memory 1000 will be described later.

  The data input / output cache memory 160 temporarily stores data written to the cloud management computer 100 or data read from the cloud management computer 100.

  The storage medium 170 stores various programs and information such as an operating system and applications. Various programs and information stored in the program memory 1000 may be stored in the storage medium 170. In this case, the arithmetic processing unit 180 reads various programs and information from the storage medium 170 and loads them into the program memory 1000.

  The management communication interface 110 is an interface for connecting to a device in the cloud system 90 via the management network 700 and inputting / outputting management information. The input interface 120 is an interface for the cloud administrator 20 to input information. The output interface 125 is an interface for outputting information to the cloud administrator 20.

  The input interface 120 may be a keyboard and a mouse, for example. The output interface 125 may be a general-purpose display, for example.

  Here, various programs and information stored in the program memory 1000 will be described.

  The program memory 1000 stores a service management program 1010, a policy management program 1011, a countermeasure management program 1012, a DB countermeasure procedure generation program 1013, a DB failure countermeasure determination program 1014, a charging management program 1015, and a configuration management program 2012 as programs. To do. The program memory 1000 includes service requirement management information 1001, policy management information 1002, DB failure handling method management information 1003, handling procedure management information 1004, cloud infrastructure configuration information 2001, computer resource allocation information 2002, and server resource usage. Stores status information 2003 and storage resource usage status information 2004.

  The service management program 1010 is a program for managing service contents provided to each cloud user 10. The policy management program 1011 is a program for managing a policy used when selecting a countermeasure and a countermeasure procedure.

  The countermeasure management program 1012 is a program for managing each countermeasure against a failure of the DB server 80 and the characteristics of each countermeasure. The DB handling procedure generation program 1013 is a program for generating a handling procedure based on the characteristics of service requirements, policies, and handling methods. The coping procedure generated by the DB coping procedure generation program 1013 is managed as coping procedure management information 1004.

  Here, the coping method indicates a control method such as various setting changes and configuration changes of the DB server 80 which are performed to improve the performance failure according to the cause of the performance failure of the DB server 80. The coping procedure is a set of coping methods, and the order in which it is determined whether each coping method can be applied (determination order) is determined.

  The DB failure countermeasure determination program 1014 determines whether each countermeasure included in the countermeasure procedure generated by the DB countermeasure procedure generation program 1013 can be executed based on the resource securing method of the tenant 50, the availability of computer resources, and the like. It is a program to do. The billing management program 1015 is a program for managing a fee paid by the cloud user 10 to a cloud provider that provides a cloud service using the cloud system 90. The configuration management program 2012 will be described with reference to FIG.

  Details of the various information will be described later with reference to various drawings. Specifically, FIG. 6 shows the service requirement management information 1001, FIG. 7 shows the policy management information 1002, FIG. 8 shows the DB failure handling management information 1003, and FIGS. 14A and 14B show the handling procedure management information 1004. The infrastructure configuration information 2001 will be described later with reference to FIG. 9, the computer resource allocation information 2002 with reference to FIG. 10, the server resource usage status information 2003 with reference to FIG. 11, and the storage resource usage status information 2004 with reference to FIG.

  It is assumed that the billing computer 800 has the same hardware configuration as the cloud management computer 100. The program memory 1000 of the billing computer 800 stores a billing program for calculating a usage fee, information for calculating the usage fee, and the like.

  FIG. 4 is a block diagram illustrating an example of a hardware configuration and a software configuration of the infrastructure management computer 200 according to the first embodiment. The infrastructure management computer 200 performs cloud system monitoring, resource allocation, and failure handling.

  The infrastructure management computer 200 includes an arithmetic processing unit 280, a program memory 2000, a data input / output cache memory 260, a storage medium 270, a management communication interface 210, an input interface 220, and an output interface 225 as hardware configurations. . Each component of the infrastructure management computer 200 is connected to each other via a bus 290.

  The arithmetic processing unit 280, the program memory 2000, the data input / output cache memory 260, the storage medium 270, the management communication interface 210, the input interface 220, and the output interface 225 are respectively the arithmetic processing unit 180 and the program memory. 1000, the data input / output cache memory 160, the storage medium 170, the management communication interface 110, the input interface 120, and the output interface 125 are the same and will not be described.

  In the following description, when a process is described mainly with a program, it indicates that the program is being executed by the arithmetic processing unit 280.

  The program memory 2000 stores a DB failure detection program 2010, a DB bottleneck analysis program 2011, a configuration management program 2012, a DB failure recovery program 2013, and a resource monitoring program 2014 as programs. Further, the program memory 2000 stores, as information, cloud infrastructure configuration information 2001, computer resource allocation information 2002, server resource usage status information 2003, storage resource usage status information 2004, and storage configuration information 2005.

  The DB failure detection program 2010 is a program for detecting a failure of the DB server 80 and notifying the cloud administrator 20 and the cloud management computer 100 of the occurrence of the failure. The DB bottleneck analysis program 2011 is a program for analyzing the bottleneck of the DB server 80 in which a failure has occurred. The DB bottleneck analysis program 2011 identifies a cause (bottleneck) of performance degradation such as CPU resource shortage or I / O latency shortage, and identifies the identified cause to the cloud administrator 20 and the cloud management computer 100. Notice.

  The configuration management program 2012 is a program for acquiring information about the cloud system 90 and managing the acquired information when the configuration of the cloud system 90 is changed. The DB failure recovery program 2013 is a program for executing configuration change processing such as addition of computer resources based on a countermeasure. The resource monitoring program 2014 is a program for acquiring operating information such as the performance of the platform in the cloud system 90 and the resource amount of each computer resource.

  The cloud infrastructure configuration information 2001, the computer resource allocation information 2002, the server resource usage status information 2003, and the storage resource usage status information 2004 are the same as the information held by the cloud management computer 100. Details of the storage configuration information 2005 will be described later with reference to FIG.

  FIG. 5 is an explanatory diagram illustrating an example of an input screen displayed via the portal 30 when the cloud user 10 according to the first embodiment inputs a policy.

  The input screen illustrated in FIG. 5 is provided to the cloud user 10 to which the performance guarantee option is applied. The cloud user 10 sets a policy for generating a handling procedure for a DB failure using the input screen. Specifically, the cloud user 10 selects the target virtual machine 600 and designates a policy for the performance failure of the target virtual machine 600. The target virtual computer 600 is assumed to be the virtual computer 600 that implements the DB server 80.

  The cloud user 10 may select all the virtual machines 600 in the tenant 50 as the target virtual machine 600, or may select individual virtual machines 600. In addition, the cloud user 10 can designate a policy such as “no physical server migration”, “non-stop”, and “emphasis on processing time” for the target virtual machine 600.

  When no policy is input using the input screen, a handling procedure is generated based on a default policy set in the cloud management computer 100 in advance.

  FIG. 6 is an explanatory diagram illustrating an example of the service requirement management information 1001 according to the first embodiment.

  The service requirement management information 1001 is information for managing the service requirements of each tenant 50 including the service contract contents of the tenant 50 and business information operating on the virtual computer 600 that implements the DB server 80. The service requirement management information 1001 includes a tenant identifier 10011, a virtual machine identifier 10012, and a service requirement 10013.

  The tenant identifier 10011 stores identification information of the tenant 50. The virtual machine identifier 10012 stores identification information of the virtual machine 600 corresponding to the DB server 80 among the virtual machines 600 included in the tenant 50.

  The service requirement 10013 is a column for storing the management information of the tenant 50 and the service requirement contracted at the start of use of the cloud service. The service requirement 10013 further includes a performance guarantee option 10014, an allocation guarantee item 10015, non-stop operation 10016, and billing 10017.

  The performance guarantee option 10014 is a column for storing option information related to the performance guarantee set for the virtual computer 600, and includes an application state 100141 and a target 100142.

  When the application state 100141 is “present”, it indicates that a performance guarantee option is applied, and when the application state 100141 is “none”, it indicates that a performance guarantee option is not applied. A target 100142 indicates a target whose performance is guaranteed. When the target 100142 is “VM”, a coping procedure described later is applied to the virtual machine 600 when performance degradation in the tenant 50 occurs.

  The allocation guarantee item 10015 is a column for storing information related to computer resources that need to be guaranteed in the allocation of computer resources, and includes resource allocation 100151 and hardware designation 100152.

  The resource allocation 100151 includes a resource allocation 100151 indicating a computer resource that needs to be guaranteed, and a guaranteed value 100154 that is a setting value of the computer resource to be guaranteed. When the target 100153 is “CPU” and the guaranteed value 100154 is “upper limit value: 4 GHz”, it indicates that the upper limit value of the assigned CPU frequency is 4 GHz. When the target 100153 is “CPU” and the guaranteed value 100154 is “assigned value: 1 GHz”, it means that 1 GHz is always assigned as the CPU frequency. In particular, for the virtual computer 600 for which the guarantee of computer resource allocation is not set, “None” is stored in the target 100153 and “Null” is stored in the guaranteed value 100154.

  The hardware specification 100152 stores information indicating whether performance guarantee is specified in units of hardware, such as server occupation. It should be noted that “None” is stored in the hardware designation 100152 when the performance guarantee is not designated in hardware units.

  The non-stop operation 10016 stores information indicating whether or not non-stop operation is necessary for the virtual computer 600. When the non-stop operation 10016 is “necessary”, it indicates that the non-stop operation is necessary, and when the non-stop operation 10016 is “unnecessary”, it indicates that the non-stop operation is not necessary.

  The billing 10017 is a column for storing information related to the usage fee of the tenant 50, and includes a system 100171 and a scheduled payment amount 100172 for the current month. The value set in the billing 10017 is acquired when the cloud management computer 100 cooperates with the billing computer 800.

  The system 100171 stores information related to the usage fee system. For example, when the system 100171 is “fixed amount”, it indicates that the cloud user 10 using the tenant 50 has a contract to pay a fixed amount of usage fee. Further, when the system 100171 is “pay-as-you-go”, it indicates that the cloud user 10 using the tenant 50 has contracted to pay a usage fee according to the allocated amount of computer resources.

  In this example, when the usage fee system is “Flat”, all countermeasures are applicable. When the usage fee system is “pay-as-you-go”, in principle, only the countermeasures that do not incur additional charges are applicable. It shall be That is, although the “fixed amount” has a higher usage fee than “pay-as-you-go”, it can cope with the performance guarantee of the tenant 50 without incurring an additional fee. On the other hand, “usage-based billing” has a low usage fee, but an additional fee is incurred to guarantee the performance of the tenant 50.

  The scheduled payment amount 100172 of this month stores the usage fee that the cloud user 10 pays to the cloud provider that provides the cloud service.

  FIG. 7 is an explanatory diagram illustrating an example of the policy management information 1002 according to the first embodiment.

  The policy management information 1002 is information for managing a policy used when generating a handling procedure described later. The policy management information 1002 includes a tenant identifier 10021, a virtual machine identifier 10022, and a policy 10023.

  The tenant identifier 10021 and the virtual machine identifier 10022 are the same as the tenant identifier 10011 and the virtual machine identifier 10012.

  The policy 10023 stores the policy set for each virtual machine 600 by the cloud user 10. The cloud user 10 sets a policy using an input screen as shown in FIG. If no policy is set for the virtual machine 600, “Null” is stored in the policy 10023.

  FIG. 8 is an explanatory diagram illustrating an example of the DB failure countermeasure management information 1003 according to the first embodiment.

  The DB failure handling method management information 1003 is information for managing a handling method when a failure occurs in the DB server 80 and the characteristics of each handling method. The DB failure handling method management information 1003 includes a bottleneck location 10031, a handling method 10032, and a feature 10033.

  The bottleneck location 10031 stores the type of computer resource specified as the bottleneck. The coping method 10032 stores a specific coping method for eliminating the performance degradation. In the first embodiment, in the DB failure handling method management information 1003, a plurality of handling methods are managed for each type of bottleneck, that is, for each type of computer resource.

  A feature 1003 is a column for storing information about the feature of the countermeasure, and includes non-stop 10034, an influence 10033, an average processing time 10030, a physical server migration 10030, and an additional charge 10030.

  The non-stop 10034 stores information indicating whether or not the service can be continued without restarting the virtual computer 600 when the process corresponding to the countermeasure is executed. In the first embodiment, when the non-stop 10034 is “applicable”, it indicates that the service can be continued without restarting the virtual computer 600. When the non-stop 10034 is “non-applicable”, the virtual computer 600 needs to be restarted. Indicates that the service will be interrupted.

  The influence 1003 stores information indicating the magnitude of the influence on the host computer 500 or the virtual machine 600 when the processing corresponding to the countermeasure is executed. The average processing time 10036 stores the average processing time until the processing corresponding to the countermeasure is completed.

  Note that the relative weight of each countermeasure may be stored in the influence 10033 and the average processing time 10033. In this case, the cloud management computer 100 calculates a value from the weight, the data amount, and the like when the virtual computer 600 in which the performance deterioration is detected is specified.

  The physical server migration 1003 indicates information indicating whether or not the virtual computer 600 needs to be migrated from the currently running host computer 500 to another host computer 500 when executing processing corresponding to the countermeasure. Store. When the physical server migration 10037 is “present”, it indicates that the virtual computer 600 needs to be migrated between the host computers 500. When the physical server migration 10037 is “none”, the virtual computer 600 is migrated between the host computers 500. Indicates that there is no need to

  The additional charge 10030 stores information indicating whether or not an additional charge is generated when processing corresponding to the countermeasure is executed for each charging system. Specifically, the additional fee 1000038 includes a fixed amount 1000038 and a pay-per-use 1000038. The fixed amount 10031 stores information indicating whether or not an additional fee is generated when the charging system is a fixed amount, and the pay-per-use 10032 is information indicating whether or not an additional fee is generated when the charging system is a pay-per-use charge. Is stored.

  Note that the charge itself may be stored in the fixed amount 10000381 and the pay-per-use charge 100322.

  Among the columns included in the feature 10033, the non-stop 10033, the influence 10033, the average processing time 10033, and the physical server migration 10033 represent the processing cost related to the processing corresponding to the countermeasure, and the additional charge 10030 indicates the usage cost of the tenant 50. Represent.

  The cloud management computer 100 may calculate the time when the performance deterioration occurs again after the countermeasure is executed in accordance with the trend of the usage rate, and manage the time as the feature 10033. Accordingly, for example, when it is desired to reduce the execution frequency of the countermeasure, the cloud management computer 100 can preferentially select a countermeasure with a late performance degradation occurrence time.

  FIG. 9 is an explanatory diagram illustrating an example of the cloud infrastructure configuration information 2001 according to the first embodiment.

  The cloud infrastructure configuration information 2001 is information for managing information related to a storage area that can be used by the virtual machine 600, and information such as CPU and memory allocated to the virtual machine 600 running on the host computer 500. Specifically, the cloud infrastructure configuration information 2001 includes a virtual machine identifier 20011, a physical machine identifier 20012, a server resource 20013, and a storage 201414.

  The virtual machine identifier 20011 is the same as the virtual machine identifier 10012. The physical computer identifier 20012 stores identification information of the host computer 500 on which the virtual computer 600 operates.

  The server resource 20013 is a column that stores information regarding the correspondence between the computer resource of the virtual computer 600 and the computer resource of the host computer 500. The server resource 20013 includes a CPU 200131 and a memory 200132.

  The CPU 200131 further includes two columns, virtual and physical. The virtual column of the CPU 200131 stores the identification information of the virtual CPU included in the virtual computer 600, and the physical column of the CPU 200131 stores the identification information of the physical CPU that allocates the CPU resource to the virtual CPU. Two or more physical CPUs may be assigned to one virtual CPU, or a plurality of virtual CPUs may be assigned to share one physical CPU.

  Memory 200132 further includes two columns, virtual and physical. The virtual column of the memory 200132 stores the identification information of the virtual memory included in the virtual computer 600, and the physical column of the memory 200132 stores the identification information of the physical memory that allocates resources to the virtual memory.

  The storage 20014 is a column that is provided by the storage apparatus 300 and stores information related to a storage area that can be used by the host computer 500, and includes a virtual disk identifier 200141 and a volume identifier 200142.

  The virtual disk identifier 200141 stores identification information of the virtual disk 630. The volume identifier 200142 stores identification information of the volume 640 that provides a storage area for the virtual disk 630.

  FIG. 10 is an explanatory diagram of an example of the computer resource allocation information 2002 according to the first embodiment.

  The computer resource allocation information 2002 is information related to the allocation type and usage of computer resources allocated to the virtual computer 600 operating on the host computer 500, and information for managing the HA configuration using the plurality of virtual computers 600. It is. Specifically, the computer resource allocation information 2002 includes a physical computer identifier 20021, a virtual computer identifier 200222, an allocation 20023, and an HA configuration state 20022.

  The physical computer identifier 200021 is the same as the physical computer identifier 20012. Further, the virtual machine identifier 20022 is the same as the virtual machine identifier 10012. The virtual computer identifier 20022 stores identification information of the virtual computer 600 operating on the host computer 500 corresponding to the physical computer identifier 200221.

  The allocation 20023 is a column for storing information related to the computer resources allocated to the virtual computer 600, and includes a computer resource type 200231, a reservation form 2002022, and an actual usage amount 2000023.

  The computer resource type 200201 stores information related to the type of computer resource. The reservation form 200202 stores information related to the reservation form determined by the service contract or service operation. The actual use amount 2002003 stores the computer resource amount actually used.

  The HA configuration state 20024 stores information indicating whether the HA is configured. When the HA configuration state 20024 is “present”, it indicates that the HA is configured, and when the HA configuration state 20024 is “not present”, it indicates that the HA is not configured.

  FIG. 11 is an explanatory diagram illustrating an example of the server resource usage state information 2003 according to the first embodiment.

  The server resource usage status information 2003 is information for managing the usage status and free capacity of computer resources such as CPU and memory in the host computer 500. Specifically, the server resource usage status information 2003 includes a cluster identifier 20003, a physical computer identifier 20032, and a server resource usage status 20003.

  The cluster identifier 20031 stores identification information of the cluster 900. The physical computer identifier 20032 is the same as the physical computer identifier 20012, and stores identification information of the host computer 500 included in the cluster 900.

  The server resource usage state 20033 is a column for storing information related to the computer resources included in the host computer 500, and includes a computer resource 200031, a usage amount 200032, and a free capacity 2003.3.

  The computer resource 200031 stores computer resource identification information included in the host computer 500. The usage amount 20032 stores the value of the computer resource amount actually used. The free capacity 20033 stores the value of the computer resource amount that is not used.

  It should be noted that values used by the resource monitoring program 2014 are stored in the used amount 20032 and the free space 20033.

  FIG. 12 is an explanatory diagram of an example of the storage resource usage state information 2004 according to the first embodiment.

  The storage resource usage status information 2004 is information for managing the capacity and IOPS of the logical storage area 310 and the storage pool 320. Specifically, the storage resource usage state information 2004 includes a volume identifier 20041, a logical storage area 20042, and a storage pool 20043.

  The volume identifier 20009 is the same as the volume identifier 200142.

  The logical storage area 20004 is a column for storing information related to the logical storage area 310 associated with the volume 640, and includes a logical storage area identifier 2000411, a capacity 200042, and an IOPS 200093.

  The logical storage area identifier 200041 is the same as the logical storage area identifier 200133 and stores identification information of the logical storage area 310 associated with the volume 640.

  The capacity 200042 is a column for storing information related to the storage capacity of the logical storage area 310, and includes a usage rate 2004221 and a free capacity 2004222. The usage rate 200042 stores a value indicating the usage rate of the storage capacity of the logical storage area 310. The free capacity 200000422 stores a value indicating the free capacity of the storage capacity of the logical storage area 310.

  The IOPS 200093 stores a value indicating the IOPS of the logical storage area 310.

  The storage pool 20043 is a column for storing information related to the storage pool 320 to which the logical storage area 310 belongs, and includes a pool identifier 2000411, a capacity 20000432, and an IOPS 20000433.

  The pool identifier 200031 is the same as the pool identifier 200134, and stores identification information of the storage pool 320 to which the logical storage area 310 corresponding to the logical storage area identifier 200041 belongs.

  The capacity 2000043 is a column for storing information related to the storage capacity of the storage pool 320, and includes a usage rate 20003921 and a free capacity 20000432. The usage rate 20003921 stores a value indicating the usage rate of the storage capacity of the storage pool 320. The free capacity 20003922 stores a value indicating the free capacity of the storage capacity of the storage pool 320.

  The IOPS 20033 stores a value indicating the IOPS of the storage pool 320.

  It should be noted that values acquired by the resource monitoring program 2014 are stored in the capacity 200042, the IOPS200393, the capacity 20000432 and the IOPS2000043.

  FIG. 13 is an explanatory diagram of an example of the storage configuration information 2005 according to the first embodiment.

  The storage configuration information 2005 is information for managing the configuration of the storage pool 320. Specifically, the storage configuration information 2005 includes a pool identifier 20051, a capacity 20052, a RAID group 20053, a storage medium 20054, and a spare disk 20055.

  The pool identifier 20051 is the same as the pool identifier 200134, and stores identification information of the storage pool 320. The capacity 20052 stores a value indicating the total storage capacity of the storage pool 320.

  The RAID group 20053 is a column that stores information on the RAID groups that make up the storage pool 320, and includes a RAID group identifier 20000531, a capacity 20000532, and a limit IOPS 200353.

  The RAID group identifier 200531 stores RAID group identification information. The capacity 200532 stores a value indicating the total storage capacity of the RAID group. The limit IOPS 201053 stores I / O that can be processed by the RAID group, that is, the maximum value of IOPS.

  The storage medium 20054 stores identification information of the storage medium that constitutes the RAID group. The spare disk 20055 stores identification information of storage media that can be added to the storage pool 320. The spare disk 20055 may store RAID group identification information.

  14A and 14B are explanatory diagrams illustrating an example of handling procedure management information 1004 according to the first embodiment.

  The handling procedure management information 1004 is information for managing a handling procedure applied to the virtual machine 600. Specifically, the handling procedure management information 1004 includes metadata 10041 and handling procedure 10042.

  The metadata 1000041 stores information indicating the attribute of the handling procedure management information 1004. In the first embodiment, the metadata 10041 includes identification information of the target virtual computer 600 and computer resource type information. The coping procedure 10042 stores a specific coping procedure.

  FIG. 14A and FIG. 14B show the coping procedure applied to the virtual computer 600 in which the charge form is “fixed amount”, the computer resource type is “CPU”, and the identification information of the virtual computer 600 is “VM05”. For the virtual machine 600 corresponding to “VM05”, it is assumed that the hardware specification 100152 of the service requirement management information 1001 is “server specification” and the policy management information 1002 is “Null”.

  In the case of the handling procedure management information 1004 in FIG. 14A, whether or not each handling method can be executed on the virtual machine 600 is determined according to the determination order set in the handling procedure 10044. On the other hand, in the case of the handling procedure management information 1004 in FIG. 14B, no handling method is executed on the virtual machine 600.

  Note that the handling procedure management information 1004 may not include the metadata 10041. For example, when the handling procedure management information 1004 is generated when the performance of the DB server 80 deteriorates, information for identifying the handling procedure management information 1004 to be applied is not necessary.

  FIG. 15 is a flowchart illustrating an example of processing executed by the cloud management computer 100 according to the first embodiment.

  The processing described below may be started when the DB handling procedure generation program 1013 of the cloud management computer 100 receives a notification from the DB failure detection program 2010 that a failure of the DB server 80 has been detected, May be executed periodically.

  Here, it shall execute periodically. In this case, the cloud management computer 100 repeatedly executes the processing from step S103 to step S109 for each type of bottleneck for the virtual computer 600. When the DB failure detection program 2010 starts processing upon receiving a notification that a failure of the DB server 80 has been detected, the cloud management computer 100 receives information on the bottleneck from the DB bottleneck analysis program 2011. .

  The service management program 1010 refers to the service requirement management information 1001 (step S101). Since the service requirement management information 1001 is regularly updated, it is in the latest state.

  The DB handling procedure generation program 1013 starts the loop processing of the tenant 50 (step S102). In the first embodiment, the processing from step S103 to step S114 is repeatedly executed for all tenants 50 existing in the cloud system 90. Only the tenant 50 including the DB server 80 in which a failure has occurred may be targeted. Here, it is assumed that the tenant 50 is selected in the order of entry of the service requirement management information 1001.

  The DB handling procedure generation program 1013 refers to the service requirement management information 1001 and determines whether or not the virtual machine 600 to which the performance guarantee option is set exists in the virtual machines 600 included in the target tenant 50. (Step S103). Specifically, the following processing is executed.

  The DB handling procedure generation program 1013 searches for an entry in which the tenant identifier 10011 matches the identification information of the target tenant 50. The DB handling procedure generation program 1013 refers to the application state 100141 of the searched entry and determines whether or not there is a virtual computer 600 in which “Yes” is stored.

  In the following description, the virtual machine 600 in which the performance guarantee option is set is also referred to as a target virtual machine 600.

  If the target virtual machine 600 does not exist among the virtual machines 600 included in the target tenant 50 (No in step S103), the DB handling procedure generation program 1013 does not need to generate handling procedure management information 1004. Determine and proceed to step S114.

  When the target virtual computer 600 exists in the target tenant 50 (Yes in step S103), the DB handling procedure generation program 1013 starts loop processing of the target virtual computer 600 ( Step S104). Specifically, the DB handling procedure generation program 1013 selects one target virtual machine 600 from the target virtual machines 600. The processing from step S105 to step S113 is repeatedly executed for the selected virtual machine 600.

  The DB handling procedure generation program 1013 starts loop processing of computer resources for the selected target virtual computer 600 (step S105). Specifically, the DB handling procedure generation program 1013 refers to the row of the selected virtual computer 600 in the service requirement management information 1001 and selects one computer resource from among the computer resources set in the target 100153. The processing from step S106 to step S112 is repeatedly executed for the selected computer resource.

  The DB handling procedure generation program 1013 determines whether or not the charging system of the selected target virtual computer 600 is pay-per-use (step S106).

  Specifically, the DB handling procedure generation program 1013 determines whether or not the row system 100171 of the virtual machine 600 selected in step S104 is “pay-as-you-go”.

  When it is determined that the charging system of the target virtual computer 600 is pay-per-use (Yes in step S106), the DB handling procedure generation program 1013 generates an additional fee for the cloud user 10 using the target tenant 50. An inquiry is made as to whether or not to accept (step S107). The DB handling procedure generation program 1013 continues to wait for the next process until a response from the cloud user 10 is received.

  The inquiry is notified to the cloud user 10 via the portal 30. The cloud user 10 transmits a response to the notification to the cloud management computer 100 via the portal 30.

  Based on the response from the cloud user 10, the DB handling procedure generation program 1013 determines whether or not an additional fee has been approved (step S108).

  When the generation of the additional fee is approved (step S108 is Yes), the DB handling procedure generation program 1013 proceeds to step S108.

  When the generation of the additional fee is not approved (No in step S108), the DB handling procedure generation program 1013 executes the handling procedure generation process (A) (step S109) and outputs the generated handling procedure management information 1004. (Step S111). Details of the handling procedure generation process (A) will be described later with reference to FIG.

  When it is determined that the charging system of the target virtual computer 600 is not pay-per-use (No in step S106), or when the generation of an additional fee is approved (Yes in step S108), the DB handling procedure generation program 1013 The coping procedure generation process (B) is executed (step S110), and the generated coping procedure management information 1004 is output (step S111). Details of the handling procedure generation process (B) will be described later with reference to FIG.

  If the target virtual machine 600 does not exist in the virtual machine 600 included in the target tenant 50 (No in step S103), or after the processing in step S111, the DB handling procedure generation program 1013 selects the selected target It is determined whether or not the processing has been completed for all the computer resources of the virtual computer 600 (step S112).

  When it is determined that the processing has not been completed for all the computer resources of the selected target virtual computer 600 (No in step S112), the DB handling procedure generation program 1013 selects the next computer resource, and the same Processing (step S106 to step S112) is executed.

  When it is determined that the processing has been completed for all the computer resources of the selected target virtual computer 600 (Yes in step S112), the DB handling procedure generation program 1013 has completed the processing for all the target virtual computers 600. Is determined (step S113).

  When it is determined that the processing has not been completed for all target virtual machines 600 (No in step S113), the DB handling procedure generation program 1013 selects the next target virtual machine 600 and performs the same process (step Steps S105 to S113) are executed.

  When it is determined that processing has been completed for all target virtual machines 600 (Yes in step S113), the DB handling procedure generation program 1013 determines whether processing has been completed for all tenants 50 (step S114). ).

  When it is determined that the processing has not been completed for all tenants 50 (No in step S114), the DB handling procedure generation program 1013 next selects the tenant 50 and performs similar processing (from step S103 to step S114). Run.

  When it is determined that the processing has been completed for all tenants 50 (Yes in step S114), the DB handling procedure generation program 1013 notifies the handling procedure management information 1004 generated to the infrastructure management computer 200 (step S115). The process ends.

  Note that the DB handling procedure generation program 1013 does not have to notify the infrastructure management computer 200 of handling procedure management information 1004. For example, when a failure occurs in the DB server 80, the cloud management computer 100 selects one handling procedure management information 1004 from among a plurality of handling procedure management information 1004 based on the metadata 10041, and the selected handling procedure management information. 1004 is notified to the infrastructure management computer 200.

  Note that when processing is started when a notification indicating that a failure of the DB server 80 has been detected is received, loop processing of the tenant 50, virtual computer 600, and computer resources can be omitted. This is because the target for generating the handling procedure management information 1004 is specified.

  FIG. 16 is a flowchart illustrating an example of the handling procedure generation process (A) executed by the cloud management computer 100 according to the first embodiment.

  The DB handling procedure generation program 1013 acquires values related to the target virtual computer 600 from the service requirement management information 1001 and the computer resource allocation information 2002 (step S201). Specifically, the following processing is executed.

  The DB handling procedure generation program 1013 refers to the service requirement management information 1001 and the computer resource allocation information 2002 based on at least the identification information of the target virtual computer 600 and the type of bottleneck.

  The DB handling procedure generation program 1013 searches for a row in which the virtual machine identifier 10012 of the service requirement management information 1001 matches the identification information of the target virtual machine 600 and the target 100153 matches the bottleneck type. The DB handling procedure generation program 1013 acquires the value stored in the guaranteed value 100154 of the searched entry.

  The DB handling procedure generation program 1013 searches for a row in which the virtual machine identifier 200222 of the computer resource allocation information 2002 matches the identification information of the target virtual machine 600 and the computer resource type 200201 matches the bottleneck type. The DB handling procedure generation program 1013 acquires the values of the searched row reservation mode 200232 and the actual usage amount 2002003. The above is the description of the process in step S201.

  Next, based on the values acquired from the service requirement management information 1001 and the computer resource allocation information 2002, the DB handling procedure generation program 1013 determines whether or not the computer resources for the guaranteed value are allocated to the target virtual computer 600. Is determined (step S202).

  For example, when the virtual machine identifier 10012 is “VM01” and the target 100153 is “CPU”, the guaranteed value 100154 is “upper limit value: 4 GB”. On the other hand, when the virtual computer identifier 20022 is “VM01” and the computer resource type 200201 is “CPU”, the reservation form 200202 is “1 GHz-4 GHz”, and the actual usage amount 2000023 is “4 GHz”. Therefore, in this case, the DB handling procedure generation program 1013 determines that computer resources for the guaranteed value are allocated to the target virtual computer 600.

  When it is determined that the guaranteed virtual machine 600 has been allocated to the target virtual machine 600 (Yes in step S202), the DB handling procedure generation program 1013 determines that the handling procedure is not required to be generated, and processing Exit. In order to improve the performance of the target virtual computer 600, it is necessary to secure computer resources that are equal to or greater than the guaranteed value, and an additional fee is generated. For this reason, there is no countermeasure that does not generate an additional charge.

  When it is determined that the guaranteed virtual machine resources are not allocated to the target virtual machine 600 (No in step S202), the DB handling procedure generation program 1013 generates an additional charge from the DB failure handling method management information 1003. The coping method which is not to be selected is selected (step S203). Specifically, the following processing is executed.

  The DB handling procedure generation program 1013 searches for an entry in which the bottleneck location 10031 matches the type of the bottleneck, and refers to the column of the additional charge 10030 of the searched entry.

  When the system 100171 of the target virtual computer 600 is “fixed amount”, the DB handling procedure generation program 1013 selects a handling method in which “none” is set for the fixed amount 100311. Further, when the system 100171 of the target virtual computer 600 is “pay-as-you-go”, the DB handling procedure generation program 1013 selects a handling method in which “none” is set in the metered charging 100322. The above is the description of the process in step S203.

  Next, the DB coping procedure generation program 1013 extracts a coping method that matches the performance guarantee and operation contents for the target virtual machine 600 from the selected coping methods (step S204).

  For example, the DB handling procedure generation program 1013 searches for a row in which the virtual machine identifier 10012 of the service requirement management information 1001 matches the target virtual machine 600. When the non-stop operation 10016 of the searched row is “necessary”, the DB handling procedure generation program 1013 extracts a handling method that does not require restart of the virtual computer 600 corresponding to the DB server 80. Note that the above-described processing is an example, and a countermeasure may be extracted based on information such as hardware occupancy.

  Steps S203 and S204 are processes for selecting a countermeasure that matches the service requirements. In the handling procedure generation process (A), since it is a condition that no additional fee is generated, the determination process in step S203 is executed.

  Next, the DB handling procedure generation program 1013 refers to the policy management information 1002 and determines whether or not a policy is set for the target virtual computer 600 (step S205).

  Specifically, the DB handling procedure generation program 1013 searches for a row in which the virtual machine identifier 10022 matches the identification information of the target virtual machine 600. If there is no corresponding line, the DB handling procedure generation program 1013 determines that no policy is set for the target virtual machine 600. Further, even when the corresponding row exists and the policy 10023 of the row is “Null”, the DB handling procedure generation program 1013 determines that no policy is set for the target virtual machine 600.

  When it is determined that a policy is set in the target virtual machine 600 (Yes in step S205), the DB handling procedure generation program 1013 rearranges the extracted handling methods according to the set policy, Coping procedure management information 1004 is generated (step S206). Thereafter, the DB handling procedure generation program 1013 ends the process.

  For example, when the policy 10027 is “processing time priority”, the DB handling procedure generation program 1013 rearranges the handling methods extracted in ascending order of the average processing time 10036. As a result, the handling procedure 10042 of the handling procedure management information 1004 is generated. The DB handling procedure generation program 1013 further generates metadata 10041 from the identification information of the virtual computer 600 and computer resources selected in steps S104 and S105.

  When it is determined that no policy is set for the target virtual computer 600 (No in step S205), the DB handling procedure generation program 1013 extracts the handling that is extracted based on the average processing time, the load on the host computer 500, and the like. The methods are rearranged (step S207). Thereafter, the DB handling procedure generation program 1013 proceeds to step S207. For example, the following processing is executed.

  The DB handling procedure generation program 1013 first sorts the handling methods extracted in ascending order of the average processing time 10036. When a countermeasure with the same average processing time 10036 exists, the DB handling procedure generation program 1013 refers to the influence 10033 and rearranges the countermeasures with the same average processing time 1003 in the order of increasing load on the host computer 500.

  The DB coping procedure generation program 1013 rearranges the extracted coping methods, and generates coping procedure management information 1004 by adding an accommodation process at the end of the sorted coping methods (step S208). Thereafter, the DB handling procedure generation program 1013 ends the process. Since the generation method of the handling procedure management information 1004 is the same as the processing in step S206, the description thereof is omitted.

  Note that the process of step S208 may be omitted. In this case, handling procedure management information 1004 is generated in step S207.

  Here, the accommodation process is a process of diverting a computer resource allocated to another virtual machine 600 running on the host computer 500 on which the target virtual machine 600 is run. The other virtual machines 600 running on the host computer 500 are not targeted for all virtual machines 600, but are those for which the application state 100141 of the performance guarantee option 10014 is “none”.

  By the processing in FIG. 16, handling procedure management information 1004 as shown in FIG. 14A is generated. In step S204, the DB handling procedure generation program 1013 extracts handling methods that do not migrate between the host computers 500. In step S205, the handling procedure management as shown in FIG. Information 1004 is generated.

  FIG. 17 is a flowchart illustrating an example of the handling procedure generation process (B) executed by the cloud management computer 100 according to the first embodiment.

  The DB handling procedure generation program 1013 selects a handling method that matches the performance guarantee and operation contents for the target virtual machine 600 from the DB failure handling method management information 1003 (step S301). For example, the following processing is executed.

  The DB handling procedure generation program 1013 searches for a row in which the virtual machine identifier 10012 of the service requirement management information 1001 matches the target virtual machine 600. When the non-stop operation 10016 of the searched row is “necessary”, the DB handling procedure generation program 1013 selects a handling method that does not require restart of the virtual computer 600 corresponding to the DB server 80. Note that the above-described processing is an example, and a coping method that matches the contract content may be selected based on information such as hardware occupancy.

  Step S301 is processing for selecting a countermeasure that matches the service requirements. In the handling procedure generation process (B), since it is not a condition that no additional fee is generated, the determination process as in step S203 is not executed.

  Next, the DB handling procedure generation program 1013 refers to the policy management information 1002 and determines whether or not a policy is set for the target virtual computer 600 (step S302). The process in step S302 is the same as the process in step S205.

  When it is determined that a policy is set for the target virtual machine 600 (Yes in step S302), the DB handling procedure generation program 1013 is selected according to the set policy. By sorting the handling methods, the handling procedure management information 1004 is generated (step S303). Thereafter, the DB handling procedure generation program 1013 ends the process. The process in step S303 is the same as the process in step S206.

  When it is determined that no policy is set for the target virtual machine 600 (No in step S302), the DB handling procedure generation program 1013 selects the handling that is selected based on the average processing time, the load on the host computer 500, and the like. The methods are rearranged (step S304). The process of step S304 is the same as the process of step S207.

  The DB coping procedure generation program 1013 rearranges the selected coping methods, and generates coping procedure management information 1004 by adding an accommodation process to the end of the sorted coping methods (step S305). Thereafter, the DB handling procedure generation program 1013 ends the process. The process in step S305 is the same as the process in step S208.

  FIG. 18 is an explanatory diagram illustrating an example of handling procedure management information 1004 generated by executing the handling procedure generation process (B) according to the first embodiment.

  FIG. 18 shows a coping procedure applied to the virtual computer 600 in which the accounting system is “usage”, the computer resource type is “CPU”, and the identification information of the virtual computer 600 is “VM02”. In the virtual machine 600 corresponding to “VM02”, the non-stop operation 10016 of the service requirement management information 1001 is “necessary”, and the policy management information 1002 is “Null”. The coping procedure 10042 shows a coping procedure in which coping methods that do not cause restart of the virtual machine 600 are arranged in order of short average processing time.

  Hereinafter, processing according to the coping procedure will be described with reference to FIGS.

  19 to 23 are flowcharts for explaining an example of processing executed by the cloud management computer 100 according to the first embodiment in accordance with the handling procedure management information 1004.

  If the cloud management computer 100 is notified from the DB bottleneck analysis program 2011 that the CPU resource shortage of the virtual computer 600 for which the performance guarantee option is set is detected, the identification information of the virtual computer 600 and the type of the computer resource Based on the above, the metadata 10040 is referred to, and the handling procedure management information 1004 is selected. The cloud management computer 100 executes the coping method described with reference to FIGS. 19 to 23 according to the selected coping procedure management information 1004.

  Note that when the performance degradation of the virtual computer 600 is detected, the DB bottleneck analysis program 2011 identifies the type of bottleneck and calculates the resource amount of the computer resources that are insufficient. The DB bottleneck analysis program 2011 transmits a notification including the identification information of the virtual computer 600, the type of bottleneck, and the insufficient resource amount to the cloud management computer 100.

  In the following description, the virtual computer 600 corresponding to the DB server 80 with degraded performance is also referred to as a target virtual computer 600.

  First, the process shown in FIG. 19 will be described. FIG. 19 shows processing corresponding to a coping method in which the bottleneck portion 10031 is “CPU” and the coping method 10032 is “change share value”.

  The DB failure countermeasure determination program 1014 of the cloud management computer 100 will be described below when a countermeasure corresponding to “determination of whether or not the share value can be changed” is called based on the countermeasure procedure management information 1004. The process to start is started.

  The DB failure countermeasure determination program 1014 acquires the insufficient CPU resource amount calculated by the DB bottleneck analysis program 2011 from the infrastructure management computer 200 (step S401). Note that the processing in step S401 can be omitted when the CPU resource amount that is lacking is acquired before the countermeasure is executed.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and the computer resource allocation information 2002 to determine whether or not the share value of the target virtual computer 600 can be changed (step S402). Specifically, the following processing is executed. The share value is a value for determining the allocation rate of computer resources to a plurality of virtual computers 600 managed by the hypervisor of the host computer 500 or the like.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and searches for a row in which the virtual machine identifier 10012 matches the identification information of the target virtual machine 600 and the target 100153 is “CPU”. The DB failure countermeasure determination program 1014 acquires a value stored in the guaranteed value 100154 of the searched row.

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for a row in which the virtual computer identifier 20022 matches the identification information of the target virtual computer 600 and the computer resource type 200201 is “CPU1”. . The DB failure countermeasure determination program 1014 obtains the value stored in the searched row reservation form 2002022.

  The DB failure countermeasure determination program 1014 determines whether or not the share value of the target virtual machine 600 can be changed based on the guaranteed value 100154 and the value acquired from the reservation form 2002022.

  For example, when resource allocation based on the share value is set in the reservation form 2002022, the DB failure countermeasure determination program 1014 determines that the share value of the target virtual machine 600 can be changed. Further, when the share value of the target virtual machine 600 is changed, if the computer resource allocated to another virtual machine 600 sharing the same computer resource as the target virtual machine 600 is not smaller than the guaranteed value 100154, the DB failure countermeasure determination The program 1014 determines that the share value of the target virtual machine 600 can be changed. The above is the description of the process in step S402.

  When it is determined that the share value of the target virtual machine 600 cannot be changed (No in step S402), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and determines whether or not the next countermeasure is present. Is determined (step S403).

  When it is determined that the next countermeasure is present (Yes in step S403), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in Step S403), the DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (Step S412). Thereafter, the DB failure countermeasure determination program 1014 ends the process. For example, it is notified that there is no appropriate countermeasure. Note that the processing result notification method may be performed via the portal 30, for example.

  If it is determined in step S402 that the share value of the target virtual computer 600 can be changed (Yes in step S402), the DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and is the same as the target virtual computer 600. The other virtual computer 600 running on the host computer 500 is searched (step S404). That is, another virtual machine 600 that shares a computer resource with the target virtual machine 600 is searched. Specifically, the following processing is executed.

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for a row in which the virtual computer identifier 20022 matches the identification information of the target virtual computer 600. The DB failure countermeasure determination program 1014 identifies the host computer 500 on which the target virtual computer 600 is operating based on the entry including the retrieved row.

  The DB failure countermeasure determination program 1014 specifies another virtual computer 600 that shares a computer resource with the target virtual computer 600 based on the specified entry of the host computer 500. The above is the description of the process in step S404.

  The DB failure countermeasure determination program 1014 calculates a computer resource that is excessively allocated to the searched other virtual computer 600 (step S405). Specifically, the following processing is executed.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and acquires the value of the guaranteed value 100154 in which the target 100153 of the row corresponding to the other virtual machine 600 is “CPU”. Further, the DB failure countermeasure determination program 1014 obtains the value of the actual usage amount 20023 when the computer resource type 200231 corresponding to the other virtual computer 600 of the computer resource allocation information 2002 is “CPU1”.

  The DB failure countermeasure determination program 1014 searches for other virtual machines 600 satisfying the following expression (1) among the other virtual machines 600 sharing the computer resources with the target virtual machine 600. That is, another virtual computer 600 to which computer resources are allocated excessively is searched.

  Further, the DB failure countermeasure determination program 1014 calculates the surplus computer resource amount of the searched other virtual computer 600 based on the following equation (2).

  The above is the description of the process in step S405.

  The DB failure countermeasure determination program 1014 determines whether or not a shortage of computer resources can be secured using the computer resources allocated to the other searched virtual computers 600 (step S406). Specifically, the DB failure countermeasure determination program 1014 determines whether or not the value calculated based on Expression (2) is equal to or more than the CPU resource amount that is insufficient.

  If it is determined that the insufficient computer resources cannot be secured (No in step S406), the DB failure countermeasure determination program 1014 proceeds to step S403.

  If it is determined that an insufficient computer resource can be secured (Yes in step S406), the DB failure countermeasure determination program 1014 changes the share value of the target virtual computer 600 (step S407).

  For example, the DB failure countermeasure determination program 1014 instructs the DB failure recovery program 2013 of the infrastructure management computer 200 to change the share values of the target virtual computer 600 and other virtual computers 600. The DB failure recovery program 2013 changes the share values of the target virtual machine 600 and other virtual machines 600 according to the instruction.

  Based on the DB failure countermeasure management information 1003, the DB failure countermeasure determination program 1014 determines whether or not an additional fee is incurred due to the change of the share value (step S408). Specifically, the following processing is executed.

  The DB failure countermeasure determination program 1014 inquires of the charging management program 1015 whether or not charging has occurred regarding a countermeasure whose countermeasure is “change in share value”. The inquiry includes metadata 10041 of the handling procedure management information 1004.

  The charging management program 1015 refers to the DB failure handling method management information 1003 and searches for a row in which the bottleneck portion 10031 is “CPU” and the handling method 10032 is “change share value”. The charge management program 1015 acquires a value of either a fixed amount 10000381 or a pay-per-use charge 10032 from the additional charge 10030 of the searched row based on the metadata 10029. The accounting management program 1015 responds to the DB failure countermeasure determination program 1014 with the acquired value.

  When the value included in the response is “none”, the DB failure countermeasure determination program 1014 determines that no additional charge is incurred even if the share value is changed. On the other hand, when the value included in the response is “Yes”, the DB failure countermeasure determination program 1014 determines that an additional fee is generated by changing the share value. The above is the description of the process in step S408.

  When it is determined that no additional fee is generated even if the share value is changed (No in step S408), the DB failure countermeasure determination program 1014 notifies the cloud user 10 of the processing result (step S412). Thereafter, the DB failure countermeasure determination program 1014 ends the process. For example, it is notified that a countermeasure for changing the share value has been executed.

  When it is determined that an additional fee is generated by changing the share value (Yes in step S408), the DB failure countermeasure determination program 1014 notifies the charging computer 800 of the occurrence of the additional fee (step S409). The notification includes information related to the countermeasure such as identification information of the target virtual machine 600 and a changed share value. The DB failure countermeasure determination program 1014 continues to wait until there is a response from the billing computer 800.

  When the billing computer 800 receives the notification from the cloud management computer 100, the billing computer 800 calculates an additional fee based on the information included in the notification, and notifies the cloud management computer 100 of the calculated additional fee. Note that the method for calculating the additional fee is a publicly known method and is not directly related to the present embodiment, so that the description thereof is omitted.

  The DB failure countermeasure determination program 1014 updates the service requirement management information 1001 (step S411) when receiving a notification of the additional fee from the billing computer 800 (step S410).

  Specifically, the DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and searches for a row in which the virtual machine identifier 10012 matches the identification information of the target virtual machine 600. The DB failure countermeasure determination program 1014 updates the billing 10017 of the searched row based on the notified additional fee.

  The DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S412). Thereafter, the DB failure countermeasure determination program 1014 ends the process. For example, the fact that the countermeasure for changing the share value has been executed and the additional fee are notified.

  Next, the process shown in FIG. 20 will be described. FIG. 20 illustrates a process corresponding to a coping method in which the bottleneck portion 10031 is “CPU” and the coping method 10032 is “change upper limit value”.

  The DB failure countermeasure determination program 1014 acquires the insufficient CPU resource amount calculated by the DB bottleneck analysis program 2011 from the infrastructure management computer 200 (step S501).

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and the computer resource allocation information 2002 to determine whether or not the upper limit value of the target virtual computer 600 can be changed (step S502).

  The process in step S502 is similar to the process in step S402. In other words, the DB failure countermeasure determination program 1014 determines whether or not the upper limit value of the target virtual machine 600 can be changed based on the guaranteed value 100154 and the value acquired from the reservation form 2002022.

  When it is determined that the upper limit value of the target virtual machine 600 cannot be changed (No in step S502), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and determines whether or not the next countermeasure is present. Is determined (step S503).

  When it is determined that the next countermeasure is present (Yes in step S503), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S503), the DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S512). Thereafter, the DB failure countermeasure determination program 1014 ends the process. The process of step S512 is the same as the process of step S412.

  When it is determined in step S502 that the upper limit value of the target virtual machine 600 can be changed (Yes in step S502), the DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and is the same as the target virtual machine 600. The other virtual computer 600 running on the host computer 500 is searched (step S504). The process in step S504 is the same as the process in step S404.

  The DB failure countermeasure determination program 1014 calculates a computer resource that is excessively allocated to the other searched virtual computer 600 (step S505). The process of step S505 is the same as the process of step S405.

  The DB failure countermeasure determination program 1014 determines whether or not the insufficient computer resources can be secured using the computer resources allocated to the other searched virtual computers 600 (step S506). The process in step S506 is the same as the process in step S406.

  When it is determined that insufficient computer resources cannot be secured (No in step S506), the DB failure countermeasure determination program 1014 proceeds to step S503.

  If it is determined that an insufficient computer resource can be secured (Yes in step S506), the DB failure countermeasure determination program 1014 changes the upper limit value of the target virtual computer 600 (step S507). The process in step S507 is the same as the process in step S407.

  The DB failure countermeasure determination program 1014 determines whether or not an additional fee is generated due to the change of the upper limit value based on the DB failure countermeasure management information 1003 (step S508). The process of step S508 is the same as the process of step S408.

  If it is determined that no additional fee will be generated even if the upper limit value is changed (No in step S508), the DB failure countermeasure determination program 1014 notifies the cloud user 10 of the processing result (step S512). Thereafter, the DB failure countermeasure determination program 1014 ends the process.

  When it is determined that an additional fee is generated by changing the upper limit value (Yes in step S508), the DB failure countermeasure determination program 1014 notifies the charging computer 800 of the occurrence of the additional fee (step S509). The process in step S509 is the same as the process in step S409.

  The DB failure countermeasure determination program 1014 updates the service requirement management information 1001 (step S511) when receiving a notification of the additional charge from the billing computer 800 (step S510). The DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S512). Steps S510, S511, and S512 are the same as steps S410, S411, and S412.

  Next, the process shown in FIGS. 21A and 21B will be described. FIG. 21A and FIG. 21B show processing corresponding to the coping method in which the bottleneck portion 10031 is “CPU” and the coping method 10032 is “migrate VM that shares resources with the target VM to another server”.

  The DB failure countermeasure determination program 1014 acquires the insufficient CPU resource amount calculated by the DB bottleneck analysis program 2011 from the base management computer 200 (step S601).

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for another virtual computer 600 operating on the same host computer 500 as the target virtual computer 600 (step S602). The process in step S602 is the same as the process in step S404.

  The DB failure countermeasure determination program 1014 includes, among other searched virtual machines 600, other virtual machines 600 that can be migrated from the host computer 500 in which the other virtual machine 600 is currently operating to another host machine 500. It is determined whether or not it exists (step S603).

  Specifically, the DB failure countermeasure determination program 1014 does not cause performance degradation due to a shortage of computer resources, and the virtual computer 600 in which the hardware specification 100152 of the service requirement management information 1001 is “none”. It is determined whether or not exists. When the virtual computer 600 that satisfies the above-described condition exists, it is determined that there is another virtual computer 600 that can be migrated from the currently running host computer 500 to another host computer 500.

  When it is determined that there is no other virtual computer 600 that can be migrated from the currently running host computer 500 to another host computer 500 (No in step S603), the DB failure countermeasure determination program 1014 executes the countermeasure procedure management information. Referring to 1004, it is determined whether or not the next countermeasure exists (step S604). The process in step S604 is the same as the process in step S403.

  When it is determined that the next countermeasure is present (Yes in step S604), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S604), the DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S613). Thereafter, the DB failure countermeasure determination program 1014 ends the process. The process in step S613 is the same as the process in step S412.

  In step S603, when it is determined that there is another virtual computer 600 that can be migrated from the currently running host computer 500 to another host computer 500 (step S603 is Yes), the DB failure countermeasure determination program 1014 performs migration. The computer resource allocated to the possible virtual computer 600 is calculated (step S605).

  For example, the DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for a row in which the virtual computer identifier 20022 matches the identification information of the virtual computer 600 that can be migrated. The DB failure countermeasure determination program 1014 calculates the value of the searched row reservation mode 200202 as a computer resource assigned to the migratable virtual computer 600. It may be a value calculated using the actual usage amount 2002003, the guaranteed value 100154, or the like.

  The DB failure countermeasure determination program 1014 determines whether or not an insufficient computer resource can be secured using the calculated computer resource (step S606). The process in step S606 is the same as the process in step S406.

  When there are a plurality of virtual computers 600 that satisfy the determination condition in step S606 among the virtual computers 600 that can be migrated, the DB failure countermeasure determination program 1014 transfers a virtual computer 600 to which the calculated virtual computer 600 with the smallest computer resource is migrated. The computer 600 is selected.

  When it is determined that the insufficient computer resources cannot be secured (No in step S606), the DB failure countermeasure determination program 1014 proceeds to step S604.

  When it is determined that the insufficient computer resources can be secured (Yes in step S606), the DB failure countermeasure determination program 1014 has the host computer 500 that can secure the computer resources necessary for the migratable virtual computer 600 exist. It is determined whether or not (step S607). For example, the following processing is executed.

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for a row in which the virtual computer identifier 20022 matches the identification information of the virtual computer 600 that satisfies the determination condition in step S607. This is the host computer 500 in which the virtual computer 600 to which the entry including the searched row is to be migrated operates.

  The DB failure countermeasure determination program 1014 refers to the server resource usage state information 2003 and searches for a row in which the physical computer identifier 20032 matches the identification information of the host computer 500 described above. Thereby, the DB failure countermeasure determination program 1014 can specify the cluster 900 including the host computer 500 described above.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and the server resource usage state information 2003, and excludes the host computer 500 that is used exclusively from the specified host computer 500.

  Further, the DB failure countermeasure determination program 1014 has free resources for the computer resources to be allocated to the virtual computer 600 to be migrated from the remaining host computers 500 with reference to the free capacity 200033 of the server resource usage status information 2003 and the like. The host computer 500 is searched. The above is an example of the process of step S607.

  When it is determined that there is no host computer 500 that can secure necessary computer resources in the migratable virtual computer 600 (No in step S607), the DB failure countermeasure determination program 1014 proceeds to step S604.

  If it is determined that there is a host computer 500 that can secure the necessary computer resources in the migratable virtual computer 600 (Yes in step S607), the DB failure countermeasure determination program 1014 determines the host computer 500 that is the migration destination (step In step S608), the virtual computer 600 that satisfies the determination condition in step S606 is transferred to the determined host computer 500 (step S609).

  For example, the DB failure countermeasure determination program 1014 instructs the DB failure recovery program 2013 of the infrastructure management computer 200 to migrate the virtual computer 600. In accordance with the instruction, the DB failure recovery program 2013 migrates the virtual computer 600 that satisfies the determination condition of step S606 to the determined host computer 500. Note that the migration process of the virtual machine 600 between the host machines 500 is a well-known process and will not be described.

  In step S608, if there are a plurality of host computers 500 as migration destination candidates, it is assumed that the host computer 500 with a large amount of free resources is preferentially selected.

  The processing of step S610, step S611, step S612, step S613, and step S614 is the same as the processing of step S408, step S409, and step S410, step S411, and step S412.

  Next, the process shown in FIG. 22 will be described. FIG. 22 shows a process corresponding to a coping method in which the bottleneck portion 10031 is “CPU” and the coping method 10032 is “migrate the target VM to another server”.

  The DB failure countermeasure determination program 1014 acquires the insufficient CPU resource amount calculated by the DB bottleneck analysis program 2011 from the infrastructure management computer 200 (step S701).

  The DB failure countermeasure determination program 1014 determines whether or not there is a host computer 500 that can secure a computer resource necessary for the target virtual computer 600 (step S702). The process in step S702 is the same as the process in step S607. Step S702 is different from the processing in step S607 in that the virtual computer 600 to be migrated is the target virtual computer 600.

  When it is determined that there is no host computer 500 that can secure the necessary computer resources in the target virtual computer 600 (No in step S702), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and performs the following It is determined whether there is a countermeasure (step S703). The process in step S703 is the same as the process in step S403.

  When it is determined that the next countermeasure is present (Yes in step S703), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S703), the DB failure countermeasure determination program 1014 notifies the cloud user 10 of the processing result (step S710). Thereafter, the DB failure countermeasure determination program 1014 ends the process. The process in step S710 is the same as the process in step S412.

  If it is determined in step S702 that there is a host computer 500 that can secure the necessary computer resources in the target virtual computer 600 (Yes in step S702), the DB failure countermeasure determination program 1014 determines the migration destination host computer 500. (Step S704), the target virtual computer 600 is migrated to the determined host computer 500 (Step S705). The process in step S704 is the same as the process in step S608. Further, the process in step S705 is the same as the process in step S609. Step S705 is different from step S609 in that the virtual machine 600 to be migrated is the target virtual machine 600.

  The processes in steps S706, S707, S708, S709, and S710 are the same as those in steps S408, S409, S410, S411, and S412.

  Next, the process shown in FIG. 23 will be described. FIG. 23 shows the accommodation process.

  The DB failure countermeasure determination program 1014 acquires the insufficient CPU resource amount calculated by the DB bottleneck analysis program 2011 from the infrastructure management computer 200 (step S801).

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 and searches for another virtual computer 600 operating on the same host computer 500 as the target virtual computer 600 (step S802). That is, another virtual machine 600 that shares a computer resource with the target virtual machine 600 is searched. The process in step S802 is the same as the process in step S404.

  Based on the service requirement management information 1001, the DB failure countermeasure determination program 1014 determines whether or not there is a virtual computer 600 for which the performance guarantee option is not set in the virtual computer 600 sharing the computer resources with the target virtual computer 600. Is determined (step S803).

  Specifically, the DB failure countermeasure determination program 1014 refers to the application state 100141 of the row of the virtual computer 600 that shares the computer resources with the target virtual computer 600, and there is a virtual computer 600 whose application state 100141 is “None”. It is determined whether or not to do.

  When it is determined that there is no virtual machine 600 for which the performance guarantee option is not set (No in step S803), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and the following countermeasure is present. It is determined whether or not to perform (step S804). The process in step S804 is the same as the process in step S403.

  When it is determined that the next countermeasure is present (Yes in step S804), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S804), the DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S811). Thereafter, the DB failure countermeasure determination program 1014 ends the process. The process in step S811 is the same as the process in step S412.

  When it is determined that there is a virtual machine 600 for which the performance guarantee option is not set (Yes in step S803), the DB failure countermeasure determination program 1014 is insufficient using the virtual machine 600 for which the performance guarantee option is not set. It is determined whether or not a certain computer resource can be secured (step S805).

  For example, the DB failure countermeasure determination program 1014 determines whether or not the CPU resource amount allocated to the virtual machine 600 for which the performance guarantee option is not set is equal to or more than the insufficient CPU resource amount.

  When it is determined that the insufficient computer resources cannot be secured using the virtual computer 600 for which the performance guarantee option is not set (No in step S805), the DB failure countermeasure determination program 1014 proceeds to step S804.

  When it is determined that the insufficient computer resources can be secured using the virtual computer 600 for which the performance guarantee option is not set (Yes in step S805), the DB failure countermeasure determination program 1014 displays the computer of the virtual computer 600. The resource is used as the computer resource of the target virtual computer 600 (step S806).

  For example, the DB failure countermeasure determination program 1014 instructs the DB failure recovery program 2013 of the infrastructure management computer 200 to divert the computer resources of the virtual computer 600 for which the performance guarantee option is not set. In accordance with the instruction, the DB failure recovery program 2013 diverts the computer resource of the virtual computer 600 for which the performance guarantee option is not set as the computer resource of the target virtual computer 600.

  The DB failure countermeasure determination program 1014 determines, based on the DB failure countermeasure management information 1003, whether or not a charge change occurs by diverting the computer resources of the virtual computer 600 for which the performance guarantee option is not set. (Step S807).

  In step S807, not only whether or not an additional fee is generated for the target virtual computer 600, but also whether or not a reduced fee is generated for the virtual computer 600 to which the computer resource is diverted. Note that the content of the process is the same as that in step S408, and thus the description thereof is omitted.

  If the charge does not change even if the computer resources of the virtual machine 600 for which the performance guarantee option is not set are used (No in step S807), the DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10. (Step S811). Thereafter, the DB failure countermeasure determination program 1014 ends the process. The process in step S811 is the same as the process in step S412.

  If it is determined that a charge change occurs by diverting the computer resources of the virtual machine 600 for which the performance guarantee option is not set (Yes in step S807), the DB failure countermeasure determination program 1014 sends the charge to the charging computer 800. The occurrence of the change is notified (step S812). The notification includes information regarding the coping method such as the identification information of the target virtual machine 600, the identification information of the virtual machine 600 for which the performance guarantee option is not set, and the diverted computer resource amount. The DB failure countermeasure determination program 1014 continues to wait until there is a response from the billing computer 800.

  At this time, the billing computer 800 calculates an additional fee for the target virtual computer 600 and a reduced fee for the virtual computer 600 to which the computer resource is diverted. The billing computer 800 transmits billing information notification including the calculated fee to the cloud management computer 100.

  The DB failure countermeasure determination program 1014 updates the service requirement management information 1001 (step S810) when receiving a notification of charging information from the charging computer 800 (step S809). The process in step S809 is the same as the process in step S410. Further, the processing in step S810 is the same as the processing in step S411. Step S810 differs from the processing in step S411 in that the additional fee for the target virtual computer 600 and the reduced fee for the virtual computer 600 for which the computer resources are diverted are reflected in the service requirement management information 1001.

  The DB failure countermeasure determination program 1014 notifies the processing result to the cloud user 10 (step S811). Thereafter, the DB failure countermeasure determination program 1014 ends the process. For example, an additional charge and a reduced charge are notified that the computer resources of the virtual machine 600 for which the performance guarantee option is not set are used.

  The second embodiment is different from the first embodiment in that the cause of performance degradation of the DB server 80 is insufficient IO. Hereinafter, the second embodiment will be described focusing on differences from the first embodiment.

  Since the system configuration of the second embodiment is the same as that of the first embodiment, the description thereof is omitted. Further, the hardware configuration and software configuration of the cloud management computer 100 and the infrastructure management computer 200 of the second embodiment are the same as those of the first embodiment, and thus description thereof is omitted. The information managed by the cloud management computer 100 and the infrastructure management computer 200 according to the second embodiment is the same as that according to the first embodiment, and a description thereof will be omitted. The processing executed by the DB handling procedure generation program 1013 of the cloud management computer 100 according to the second embodiment is the same as that according to the first embodiment, and a description thereof will be omitted.

  In the second embodiment, the contents of the handling procedure management information 1004 and the handling method are different from those in the first embodiment. FIG. 24 is an explanatory diagram illustrating an example of handling procedure management information 1004 according to the second embodiment.

  The data structure of the handling procedure management information 1004 is the same as that of the first embodiment. The coping procedure management information 1004 of the second embodiment is different from the first embodiment in the content of the coping procedure management information 1004.

  The cause of the shortage of IO includes a case caused by a shortage of IOPS processing capacity of a storage medium such as an HDD, and a case caused by an increase in IO due to a swap to the storage medium due to a shortage of memory capacity. For this reason, a series of countermeasures for dealing with the shortage of IOs is processing that spans the host computer 500 side and the storage apparatus 300 side.

  Specifically, in the handling method, processing that can be realized by the function on the host computer 500 side is preferentially performed, and when it cannot be handled only by processing on the host computer 500, the processing on the storage device 300 side handles it.

  As in the case where the cause of the bottleneck is a shortage of CPU resources, the coping procedures for the memory and the storage medium are as follows, as shown in FIG. 15, FIG. 16, and FIG. Is determined based on the input policy.

  25A, 25B, 25C, and 25D are flowcharts illustrating an example of processing that the cloud management computer 100 according to the second embodiment executes in accordance with the handling procedure management information 1004.

  The IO shortage due to the shortage of memory resources can be dealt with in the same way as the shortage of CPU resources, so here the memory capacity is sufficient and the cause of performance degradation Suppose that the storage medium has insufficient IOPS processing capability. That is, a countermeasure when the determination result of whether or not the memory capacity shown in FIG. 24 is insufficient is branched to No will be described.

  It is assumed that the insufficient IO resource amount has already been acquired. Furthermore, the processing related to the additional fee is omitted because it is the same as that in the first embodiment.

  FIG. 25A shows processing corresponding to a countermeasure in which the countermeasure 10032 is “priority update of disk IO of host computer”.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and determines whether or not the priority of the disk IO of the volume 640 that provides a storage area to the virtual disk 630 of the virtual machine 600 can be updated (step). S901). That is, it is determined whether or not the share value can be changed. Note that the determination method in step S901 is the same method as in step S402.

  When it is determined that the priority of the disk IO of the volume 640 cannot be updated (No in step S901), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and determines whether the following countermeasure is present. Is determined (step S902). The process in step S902 is the same as the process in step S403.

  When it is determined that the next countermeasure is present (Yes in step S902), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S902), the DB failure countermeasure determination program 1014 ends the process.

  When it is determined in step S901 that the priority of the disk IO of the volume 640 can be updated (step S901 is Yes), the DB failure countermeasure determination program 1014 includes service requirement management information 1001, cloud infrastructure configuration information 2001, computer resource allocation. By referring to the information 2002 and the storage resource usage state information 2004, whether or not an insufficient computer resource can be secured by reducing the IOPS allocation amount of another virtual computer 600 sharing the volume 640 to a guaranteed value. Determination is made (step S903). Specifically, the following processing is executed.

  The DB failure countermeasure determination program 1014 refers to the cloud infrastructure configuration information 2001 and searches for a row in which the virtual machine identifier 20011 matches the identification information of the target virtual machine 600. The DB failure countermeasure determination program 1014 acquires a value stored in the volume identifier 200142 of the searched row.

  The DB failure countermeasure determination program 1014 searches for a row in which the volume identifier 201423 matches the acquired value. The value of the virtual machine identifier 20011 of the retrieved row is acquired. A virtual machine 600 corresponding to identification information other than the target virtual machine 600 becomes a virtual machine 600 that shares the same volume 640 as the target virtual machine 600.

  In the following description, a virtual machine 600 that shares the same volume 640 as the target virtual machine 600 is also referred to as a shared virtual machine 600.

  The DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 and searches for a row in which the virtual computer identifier 10012 matches the identification information of the target virtual computer 600 and the target 100153 is “disk”. Also, the DB failure countermeasure determination program 1014 searches for a row in which the virtual machine identifier 10012 matches the identification information of the shared virtual machine 600 and the target 100153 is “disk”. The DB failure countermeasure determination program 1014 acquires a value stored in the guaranteed value 100154 of the searched row.

  The DB failure countermeasure determination program 1014 refers to the computer resource allocation information 2002 to search for a row in which the virtual computer identifier 20022 matches the identification information of the target virtual computer 600 and the computer resource type 200201 is “disk”. . Further, the DB failure countermeasure determination program 1014 searches for a row in which the virtual computer identifier 20022 matches the identification information of the shared virtual computer 600 and the computer resource type 200201 is “disk”. The DB failure countermeasure determination program 1014 obtains the value stored in the searched row reservation form 2002022.

  The DB failure countermeasure determination program 1014 is shared based on the guaranteed value 100154 of the target virtual machine 600 and the value acquired from the secured form 2002022 and the value obtained from the guaranteed value 100154 and secured form 200202 of the shared virtual machine 600. By reducing the IOPS allocation amount of the virtual computer 600 to the guaranteed value, it is determined whether or not the insufficient computer resources can be secured. The above is the description of the process in step S903.

  If it is determined that insufficient computer resources cannot be secured (No in step S903), the DB failure countermeasure determination program 1014 proceeds to step S902.

  When it is determined that the insufficient computer resources can be secured (Yes in step S903), the DB failure countermeasure determination program 1014 secures the insufficient computer resources by updating the share value of the target virtual computer 600. (Step S904). Thereafter, the DB failure countermeasure determination program 1014 ends the process.

  FIG. 25B shows processing corresponding to a countermeasure whose countermeasure 10032 is “migrate another VM volume”.

  Here, “migrate the volume of another VM” means copying the volume 640 storing the image data of the virtual machine 600 to the other volume 640.

  The DB failure countermeasure determination program 1014 refers to the hardware specification 100152 of the service requirement management information 1001 and determines whether or not another virtual machine 600 sharing the disk can be migrated to another volume (step S911).

  When it is determined that another virtual machine 600 sharing the disk cannot be migrated to another volume (No in step S911), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and takes the following countermeasures. Is determined (step S912). The process of step S912 is the same as the process of step S403.

  When it is determined that the next countermeasure is present (Yes in step S912), the DB failure countermeasure determination program 1014 starts processing for the next countermeasure. When it is determined that there is no next countermeasure (No in step S912), the DB failure countermeasure determination program 1014 ends the process.

  When it is determined that the other virtual computer 600 sharing the disk can be migrated to another volume (Yes in step S911), the DB failure countermeasure determination program 1014 includes the computer resource allocation information 2002, the storage resource usage state information 2004, and the storage. With reference to the configuration information 2005, it is determined whether or not the total IOPS value for the virtual computer 600 with no disk designation among the other virtual computers 600 sharing the disk with the target virtual computer 600 is equal to or larger than the IO resource amount that is insufficient. Is determined (step S913).

  When the total IOPS value for the virtual machine 600 with no disk designation is smaller than the insufficient IO resource amount (No in step S913), the DB failure countermeasure determination program 1014 proceeds to step S912.

  If the total IOPS for the virtual machine 600 with no disk designation is equal to or greater than the insufficient IO resource amount (Yes in step S913), the DB failure countermeasure determination program 1014 stores the storage resource usage status information 2004 and the storage configuration information 2005. With reference to the table, it is determined whether or not the storage apparatus 300 having the computer resources necessary for the virtual machine 600 with no disk designation can be secured (step S914).

  When it is determined that the storage device 300 that satisfies the condition cannot be secured (No in step S914), the DB failure countermeasure determination program 1014 proceeds to step S912.

  When it is determined that the storage device 300 that satisfies the condition can be secured (Yes in step S914), the DB failure countermeasure determination program 1014 migrates the other virtual machine 600 selected in step S913 to the storage device 300 that satisfies the condition. (Step S918). Thereafter, the DB failure countermeasure determination program 1014 ends the process. When there are a plurality of migration destination storage apparatuses 300, the DB failure countermeasure determination program 1014 preferentially selects a storage device with a large IOPS space.

  FIG. 25C shows processing corresponding to a countermeasure whose countermeasure 10032 is “increase in logical storage area”.

  The DB failure countermeasure determination program 1014 refers to the storage configuration information 2005, confirms whether there is a spare disk, and determines whether the logical storage area 310 can be increased (step S921).

  When it is determined that the logical storage area cannot be increased (No in step S921), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and determines whether or not the next countermeasure method exists. (Step S922). The process of step S922 is the same as the process of step S403.

  When it is determined that the next countermeasure is present (Yes in step S922), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S922), the DB failure countermeasure determination program 1014 ends the process.

  If it is determined in step S921 that the logical storage area can be increased (step S921 is Yes), the DB failure countermeasure determination program 1014 adds a disk to the storage pool 320 (step S923). Thereafter, the DB failure countermeasure determination program 1014 ends the process.

  FIG. 25D shows a process corresponding to a countermeasure whose countermeasure 10032 is “IOPS interchange”.

  The DB failure countermeasure determination program 1014 searches for another virtual machine 600 that shares a disk with the target virtual machine 600 (step S931). Further, the DB failure countermeasure determination program 1014 refers to the service requirement management information 1001 to determine whether or not the searched virtual machine 600 includes a virtual machine 600 for which the performance guarantee option is not set. (Step S932).

  When it is determined that there is no other virtual machine 600 that satisfies the condition (No in step S932), the DB failure countermeasure determination program 1014 refers to the countermeasure procedure management information 1004 and determines whether the next countermeasure is present. Is determined (step S933). The process in step S933 is the same as the process in step S403.

  When it is determined that the next countermeasure is present (Yes in step S933), the DB failure countermeasure determination program 1014 starts processing corresponding to the next countermeasure. When it is determined that there is no next countermeasure (No in step S933), the DB failure countermeasure determination program 1014 ends the process.

  If it is determined in step S932 that there is another virtual computer 600 that satisfies the condition (Yes in step S932), the DB failure countermeasure determination program 1014 has insufficient IOPS of the disk used by the virtual computer 600. It is determined whether or not the amount is greater than or equal to the existing IO resource amount (step S934).

  When it is determined that the IOPS of the disk used by the other virtual machine 600 is smaller than the insufficient IO resource amount (No in step S934), the DB failure countermeasure determination program 1014 gives the load balancer 60 A request for limiting the flow rate on the front end side is transmitted (step S935). Thereafter, the DB failure countermeasure determination program 1014 ends the process.

  When it is determined that the IOPS of the disk used by the other virtual machine 600 is equal to or greater than the insufficient IO resource amount (Yes in step S934), the DB failure countermeasure determination program 1014, for example, the IOPS of the volume 640 Using the share value changing function, the IOPS of another virtual machine 600 for which the performance guarantee option is not set is diverted to the target virtual machine 600 (step S936). Thereafter, the DB failure countermeasure determination program 1014 ends the process.

  If the number of accesses to the target virtual machine 600 decreases and the load on the disk decreases after executing the process of step S936, the DB failure countermeasure determination program 1014 returns the setting to the normal share value.

  As described above, the cloud management computer 100 selects a countermeasure to deal with the failure of the DB server 80 based on the contract contents of the service of the tenant 50, and is selected based on the policy or the like. The order of determination of countermeasures can be determined. That is, appropriate handling procedure management information 1004 is generated.

  In addition, the cloud management computer 100 executes another countermeasure based on the handling procedure management information 1004 and the information on the other tenant 50 such as the service requirement management information 1001 and the computer resource allocation information 2002, thereby providing another tenant 50. It is possible to guarantee the performance of the tenant 50 including the DB server 80 in which a failure has occurred while suppressing the influence on the server.

  The DB server 80 is realized by using the virtual computer 600, but may be realized by using one host computer 500. In this case, the DB failure handling method management information 1003 stores a handling method for the host computer 500.

  In addition, this invention is not limited to an above-described Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. Further, a part of the configuration of each embodiment can be added to, deleted from, or replaced with another configuration.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. The present invention can also be realized by software program codes that implement the functions of the embodiments. In this case, a storage medium in which the program code is recorded is provided to the computer, and a CPU included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. As a storage medium for supplying such a program code, for example, a flexible disk, a CD-ROM, a DVD-ROM, a hard disk, an SSD (Solid State Drive), an optical disk, a magneto-optical disk, a CD-R, a magnetic tape, A non-volatile memory card, ROM, or the like is used.

  The program code for realizing the functions described in the present embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, perl, Shell, PHP, Java (registered trademark).

  Furthermore, by distributing the program code of the software that implements the functions of the embodiments via a network, the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R The CPU included in the computer may read and execute the program code stored in the storage unit or the storage medium.

  In the above-described embodiments, the control lines and information lines indicate what is considered necessary for the explanation, and not all control lines and information lines on the product are necessarily shown. All the components may be connected to each other.

10 cloud user 20 cloud administrator 30 portal 40 network 50 tenant 60 load balancer 70 web server 80 DB server 90 cloud system 100 cloud management computer 200 infrastructure management computer 300 storage device 310 logical storage area 320 storage pool 400 network connection device 500 host computer 600 Virtual computer 610 DB
620 guest OS
630 Volume 700 Management network 800 Billing computer 900 Cluster 1000 Program memory 1001 Service requirement management information 1002 Policy management information 1003 DB failure handling method management information 1004 Handling procedure management information 1010 Service management program 1011 Policy management program 1012 Handling management program 1013 DB Handling procedure generation program 1014 DB failure countermeasure determination program 1015 Charge management program 2000 Program memory 2001 Cloud infrastructure configuration information 2002 Computer resource allocation information 2003 Server resource usage status information 2004 Storage resource usage status information 2005 Storage configuration information 2010 DB failure detection program 2011 DB Bottleneck analysis program 2012 configuration management program 2013 DB disaster recovery program 2014 resource monitoring program

Claims (14)

A computer system comprising a plurality of computers,
The plurality of computers includes at least one first computer that manages the computer system, and a plurality of second computers that provide computer resources for constructing a business system used for a user's business,
The at least one first computer has a first processor, a first memory connected to the first processor, and a first interface connected to the first processor;
Each of the plurality of second computers has a second processor, a second memory connected to the second processor, a second interface connected to the second processor, and a storage device. ,
The business system includes a plurality of business computers,
The at least one first computer is:
Service requirement management information for managing service requirements of each of a plurality of business systems constructed on the computer system, and when performance degradation of the business computer is detected, to improve performance degradation for each type of computer resource And management method management information for managing the management method that is the control method of
A coping procedure generation unit that generates coping procedure management information including an order for determining whether or not the coping method can be executed on the business computer in which performance degradation has been detected. ,
The service requirements include performance guarantee conditions for each of the plurality of business computers included in the business system, operating conditions for each of the plurality of business computers included in the business system, and a billing system for the business system Including information about the terms of
Each of a plurality of countermeasures included in the countermeasure management information is managed in association with cost information in processing corresponding to the countermeasures,
The coping procedure generator is
Select a target business system for generating the handling procedure management information,
Select a business computer to be processed from among the plurality of business computers included in the target business system,
Select the target computer resource in the processing target business computer,
Based on the service requirement management information, select a plurality of countermeasures that match the service requirements of the target business system from the plurality of countermeasures included in the countermeasure management information,
A computer system that generates the coping procedure management information by determining a determination order for determining whether or not the plurality of selected coping methods can be executed. The computer system according to claim 1,
The at least one first computer is:
Holding computer resource allocation information for managing a computer resource allocation state for each of the plurality of business systems, and a plurality of coping procedure management information;
According to the handling procedure management information, a failure countermeasure determination unit that executes processing corresponding to the handling method,
The failure countermeasure determination unit
When performance degradation of an arbitrary business computer is detected, based on the identification information of the business computer from which performance degradation has been detected and the type of the computer resource that causes the performance degradation, Select the handling procedure management information to be applied from
Select one of the countermeasures according to the determination order of the selected countermeasure procedure management information,
With reference to the service requirement management information and the computer resource allocation information, based on the service requirements of the business system other than the business system including the business computer in which the performance deterioration is detected and the allocation state of the computer resource, It is determined whether or not the selected countermeasure can be executed for the business computer in which the performance deterioration is detected,
When it is determined that the selected countermeasure can be executed on the business computer in which the performance deterioration is detected, the computer system is configured to execute the selected countermeasure. The computer system according to claim 2,
Each of the plurality of second computers has a virtualization unit that manages virtual computers generated by logically dividing the computer resources,
The first business computer and the business computer are realized by using the virtual computer,
The computer resource allocation information includes information related to allocation of computer resources to a plurality of virtual computers operating on each of the plurality of second computers,
The coping procedure generator is
Determining whether the charging system of the target business system is a charging system that is not allowed to generate additional charges;
If it is determined that the billing system of the target business system is a billing system that does not allow the generation of additional charges, refer to the countermeasure management information and select the plurality of countermeasures that do not cause additional charges And selecting a plurality of countermeasures satisfying the performance guarantee conditions and the operation conditions of the processing target business computer from the selected plurality of countermeasures,
When it is determined that the charging system of the target business system is a charging system that is allowed to generate an additional charge, with reference to the countermeasure management information, the performance guarantee condition of the processing target business computer and A computer system characterized by selecting a plurality of countermeasures that satisfy the conditions of operation. The computer system according to claim 3,
The coping procedure generator is
Referring to the countermeasure management information, determine the determination order of the selected countermeasures in order of decreasing processing load or processing time is short,
A computer system characterized in that the coping procedure management information is generated by adding a coping method that diverts a computer resource allocated to a business computer that is allowed to deteriorate in performance to the end of the determined determination order. . The computer system according to claim 3,
The at least one first computer holds policy management information for determining the determination order of each of the plurality of business systems,
The coping procedure generator is
A computer system, wherein the determination order of the plurality of selected countermeasures is determined with reference to the policy management information. The computer system according to claim 3,
The virtualization unit sets a share value for determining a distribution rate of the computer resource for a plurality of virtual computers managed by the virtualization unit,
The computer system characterized in that the plurality of coping methods include a change process of the share value, a migration process of the virtual machine between the second computers, and addition of the computer resource. The computer system according to claim 3,
The computer system includes a computer having a charging unit that calculates a usage fee for a user of the business system,
The failure countermeasure determination unit
Determining whether there is a change in the usage fee by executing the selected countermeasure,
When it is determined that there is a change in usage fee by executing the selected countermeasure, a computer system including a notification including a processing result of the selected countermeasure is transmitted to the accounting unit. A method for dealing with a performance failure in a computer system comprising a plurality of computers,
The plurality of computers includes at least one first computer that manages the computer system, and a plurality of second computers that provide computer resources for constructing a business system used for a user's business,
The at least one first computer has a first processor, a first memory connected to the first processor, and a first interface connected to the first processor;
Each of the plurality of second computers has a second processor, a second memory connected to the second processor, a second interface connected to the second processor, and a storage device. ,
The business system includes a plurality of business computers,
The at least one first computer is:
Service requirement management information for managing service requirements of each of a plurality of business systems constructed on the computer system, and when performance degradation of the business computer is detected, to improve performance degradation for each type of computer resource And management method management information for managing the management method that is the control method of
A coping procedure generation unit that generates coping procedure management information including an order for determining whether or not the coping method can be executed on the business computer in which performance degradation has been detected. ,
The service requirements include performance guarantee conditions for each of the plurality of business computers included in the business system, operating conditions for each of the plurality of business computers included in the business system, and a billing system for the business system Including information about the terms of
Each of a plurality of countermeasures included in the countermeasure management information is managed in association with cost information in processing corresponding to the countermeasures,
The method of dealing with the performance failure of the computer system is
A first step in which the handling procedure generation unit selects a target business system for generating the handling procedure management information;
A second step in which the handling procedure generation unit selects a business computer to be processed from the plurality of business computers included in the target business system;
A third step in which the coping procedure generation unit selects a target computer resource in the processing target business computer;
Based on the service requirement management information, the handling procedure generation unit selects a plurality of handling methods that match the service requirements of the target business system from among the plurality of handling methods included in the handling method management information. A fourth step to select;
The coping procedure generation unit includes a fifth step of generating the coping procedure management information by determining a determination order for determining whether or not the plurality of selected coping methods can be executed. A method for dealing with a characteristic failure of a computer system. A method for dealing with a performance failure of a computer system according to claim 8, comprising:
The at least one first computer is:
Holding computer resource allocation information for managing a computer resource allocation state for each of the plurality of business systems, and a plurality of coping procedure management information;
According to the handling procedure management information, a failure countermeasure determination unit that executes processing corresponding to the handling method,
A method of dealing with the performance failure of the computer system is as follows:
When the failure countermeasure determination unit detects a performance deterioration of any business computer, the plurality of the plurality of faults are determined based on the identification information of the business computer in which the performance deterioration is detected and the type of the computer resource that causes the performance deterioration. Selecting the handling procedure management information to be applied from handling procedure management information;
The failure countermeasure determination unit selecting one of the countermeasures according to the determination order of the selected countermeasure procedure management information;
The failure countermeasure determination unit refers to the service requirement management information and the computer resource allocation information, and the service requirements of the business system other than the business system including the business computer in which the performance degradation is detected and the computer resource Determining whether the selected coping method can be executed on the business computer in which the performance deterioration is detected based on an allocation state;
A step of executing the selected countermeasure when the failure countermeasure determination unit determines that the selected countermeasure can be executed on the business computer in which the performance deterioration is detected. How to deal with computer system performance problems. A method for dealing with a performance failure of a computer system according to claim 9, comprising:
Each of the plurality of second computers has a virtualization unit that manages virtual computers generated by logically dividing the computer resources,
The first business computer and the business computer are realized by using the virtual computer,
The computer resource allocation information includes information related to allocation of computer resources to a plurality of virtual computers operating on each of the plurality of second computers,
The fourth step includes
Determining whether the charging system of the target business system is a charging system that is not allowed to generate additional charges; and
If it is determined that the billing system of the target business system is a billing system that does not allow the generation of additional charges, refer to the countermeasure management information and select the plurality of countermeasures that do not cause additional charges And selecting a plurality of countermeasures satisfying the performance guarantee condition and the operation condition of the processing target business computer from the selected plurality of countermeasures;
When it is determined that the charging system of the target business system is a charging system that is allowed to generate an additional charge, with reference to the countermeasure management information, the performance guarantee condition of the processing target business computer and Selecting a plurality of countermeasures that satisfy the conditions of operation, and a method for coping with performance faults in a computer system. A method for dealing with a performance failure of a computer system according to claim 10,
The fifth step includes
Determining the determination order of the selected plurality of countermeasures in the order of low processing load or in short processing time with reference to the countermeasure management information;
Generating the coping procedure management information by adding a coping method that diverts a computer resource allocated to a business computer whose performance degradation is allowed to the end of the determined determination order. A method for dealing with a characteristic failure of a computer system. A method for dealing with a performance failure of a computer system according to claim 10,
The at least one first computer holds policy management information for determining the determination order of each of the plurality of business systems,
The fifth step includes a step of determining the determination order of the plurality of selected countermeasures with reference to the policy management information, and a method for coping with a performance fault in a computer system. A method for dealing with a performance failure of a computer system according to claim 10,
The virtualization unit sets a share value for determining a distribution rate of the computer resource for a plurality of virtual computers managed by the virtualization unit,
The method of coping with a performance failure of a computer system, wherein the plurality of coping methods include a change process of the share value, a migration process of the virtual machine between the second computers, and addition of the computer resource. A method for dealing with a performance failure of a computer system according to claim 10,
The computer system includes a computer having a charging unit that calculates a usage fee for a user of the business system,
A method of dealing with the performance failure of the computer system is as follows:
The failure countermeasure determining unit determining whether or not there is a change in a usage fee by executing the selected countermeasure;
A step of transmitting a notification including a processing result of the selected countermeasure to the charging section when the failure countermeasure determining section determines that there is a change in usage fee by executing the selected countermeasure. And a method for dealing with a performance failure of the computer system.

Images