Management method, management apparatus, and management program

Abstract

To properly estimate a cost of usage.SOLUTION: A management apparatus executes: an acquisition process to acquire configuration management information including at least a first storage region and a second storage region; an extraction process to extract a cost calculation formula in the second storage region included in the configuration management information acquired by the acquisition process, from a cost calculation rule table; a calculation process which acquires a value to be assigned to a variable of the cost calculation formula from a performance capacity history table, to calculate the cost through the cost calculation formula; a preparation process to prepare a cost estimate result including the cost calculated by the calculation process, the first storage region, the second storage region, and a type of a use configuration for using the second storage region; and an output process to output the cost estimate result prepared by the preparation process.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a management method, a management device, and a management program. [Background technology]

[0002] The IT system departments of clients who have traditionally used on-premise systems are being asked to optimise costs and would like to use Pubkura as well. However, it is difficult to estimate the cost of using Pubkura, and the costs are often higher than expected.

[0003] The following Patent Document 1 discloses a system and method for providing an estimate of cloud performance capabilities and supporting a recommender system by simulating bottlenecks and transitions of specific complex applications in a cost-effective manner.

[0004] In Patent Document 1, the system and method first construct an abstract performance model of an application based on the application's resource usage pattern in an in-house testbed (white-box environment).

[0005] Second, the system and method uses a cloud metering system to calculate relative performance scores for many different cloud configurations given a black-box cloud.

[0006] Third, the system and method apply the collected performance scores to an abstract performance model to estimate the performance capabilities and potential bottleneck conditions of these cloud configurations.

[0007] Finally, the systems and methods can support recommender systems by using the models to provide performance estimation and simulation of bottlenecks and bottleneck transitions between resource subsystems while new resources are being added or replaced. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] US Patent Application Publication No. 2015 / 0019301 Summary of the Invention [Problem to be solved by the invention]

[0009] However, in the above-mentioned Patent Document 1, it is not possible to appropriately estimate the public cloud usage cost before starting the operation of a hybrid cloud configuration. For example, if there is a configuration that connects on-premise and public clouds, it is difficult for the user to input the public cloud usage details that take into account the configuration. In addition, a certain level of hybrid cloud configuration operation is required to estimate the public cloud resource usage in a hybrid cloud configuration.

[0010] An object of the present invention is to optimize utilization cost estimates. [Means for solving the problem]

[0011] A management method according to one aspect of the invention disclosed in the present application is a management method executed by a management device that manages a usage configuration of a service provided between a first device of a first device group and a second device of a second device group, the management device having a processor that executes a program and a storage device that stores the program, the storage device storing a configuration management table, a cost calculation rule table, and a performance capacity history table, the configuration management table storing a first storage area of ​​the first device, a second storage area of ​​the second device, and a type of the usage configuration, the performance capacity history table storing observation items in the first storage area, observed values ​​related to the observed items, and acquisition dates and times of the observed values, the cost calculation rule table calculating the cost of the second storage area based on at least one of the first storage area, the observed values, and the acquisition dates and times, and in the management method, the processor executes at least an acquisition process for acquiring configuration management information including the first storage area and the second storage area, an extraction process for extracting from the cost calculation rule table the cost calculation formula for the second storage area included in the configuration management information acquired by the acquisition process, a first calculation process for acquiring values ​​to be substituted for variables of the cost calculation formula from the performance capacity history table and calculating a cost estimate value using the cost calculation formula, a creation process for creating a cost estimate result including the cost estimate value calculated by the first calculation process, the first storage area, the second storage area, and the type of the usage configuration that utilizes the second storage area, and an output process for outputting the cost estimate result created by the creation process. Effect of the Invention

[0012] According to the representative embodiment of the present invention, it is possible to optimize the utilization cost estimate. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiment. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram illustrating an example of a system configuration of a hybrid cloud system. [Diagram 2] FIG. 2 is a block diagram showing an example of the hardware configuration of a computer. [Diagram 3] FIG. 3 is an explanatory diagram illustrating an example of the configuration management table. [Figure 4] FIG. 4 is an explanatory diagram illustrating an example of a performance capacity history table. [Diagram 5] FIG. 5 is an explanatory diagram illustrating an example of the cost management table. [Figure 6] FIG. 6 is an explanatory diagram illustrating an example of a cost calculation rule table. [Figure 7] FIG. 7 is an explanatory diagram illustrating an example of the improvement plan table. [Figure 8] FIG. 8 is an explanatory diagram illustrating an example of the policy table. [Figure 9] FIG. 9 is a flowchart illustrating an example of an inter-datacenter usage configuration setting process. [Figure 10] FIG. 10 is a flowchart showing a detailed example of the process of estimating costs for the inter-datacenter usage configuration to be set (step S902). [Figure 11] FIG. 11 is a flowchart illustrating an example of a hybrid cloud cost display process. [Figure 12] FIG. 12 is a flowchart illustrating a detailed example of a procedure for estimating costs for setting an inter-datacenter usage configuration (step S1113). [Figure 13] FIG. 13 is a flowchart illustrating a detailed example of the individual improvement plan creating process (step S1205) illustrated in FIG. [Figure 14] FIG. 14 is an explanatory diagram showing an example of a cost estimate result display screen. [Figure 15] FIG. 15 is an explanatory diagram showing an example of the actual cost result screen. [Figure 16] FIG. 16 is an explanatory diagram showing an example of the cost estimate screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] <Example of hybrid cloud system configuration> 1 is a block diagram showing an example of the system configuration of a hybrid cloud system. The hybrid cloud system 100 includes a management server 101, a source-side (e.g., on-premise) data center DC1 that serves as a backup source, and a target-side (e.g., public cloud) data center DC2 that serves as a backup destination (when there is no need to distinguish between DC1 and DC2, they are simply referred to as DC).

[0015] The management server 101 and the data center DC are communicatively connected via a network 102 such as the Internet, a local area network (LAN), or a wide area network (WAN). The hybrid cloud system 100 is a cloud system that can establish a configuration (hereinafter, a usage configuration) in which data centers DC (on-premise-public cloud) are connected to each other and one can use the services of the other.

[0016] In the configuration covered here, each data center DC may be on-premise or a public cloud, but the target data center DC that is the backup destination is assumed to be an environment in which cost management is performed according to the service used. Here, the environment in which cost management is performed is generally a public cloud, and the target data center DC that uses a public cloud as the target destination is often on-premise, so hereafter, the connection between data center DCs will be described and explained using an example between on-premise and a public cloud, but the environment is not limited to this as long as the target data center DC that is the backup destination is an environment in which cost management is performed according to the service used.

[0017] The management server 101 includes an inter-datacenter usage configuration setting management unit 111 , a hybrid cloud cost presentation unit 112 , and a hybrid cloud cost prediction unit 113 .

[0018] The inter-datacenter utilization configuration setting management unit 111 presents costs resulting from the settings related to the utilization configuration when planning and executing management operations.

[0019] The hybrid cloud cost presenting unit 112 presents the costs attributable to the settings related to the usage configuration separately from the other costs when confirming and estimating the actual costs.

[0020] The hybrid cloud cost prediction unit 113 estimates the costs arising from the settings related to the usage configuration based on instructions from the inter-datacenter usage configuration setting management unit 111 and the hybrid cloud cost presentation unit 112, and returns the estimates to the inter-datacenter usage configuration setting management unit 111 and the hybrid cloud cost presentation unit 112.

[0021] In addition, the management server 101 has a configuration management table 121 , a performance and capacity history table 122 , a cost management table 123 , a cost calculation rule table 124 , an improvement plan table 125 , and a policy table 126 .

[0022] The configuration management table 121 is a table for managing the usage configuration, the details of which will be described later with reference to FIG.

[0023] The performance and capacity history table 122 is a table for holding history information on the performance of the data center DC and the capacity of the storage ST in the data center DC. Details will be described later with reference to FIG.

[0024] The cost management table 123 is a table for managing the costs incurred for the services used by the data center DC. Details will be described later with reference to FIG.

[0025] The cost calculation rule table 124 holds cost calculation rules for each destination data center DC, storage type, and management operation for connecting between the on-premise (DC1) and the public cloud (DC2). Details will be described later with reference to FIG.

[0026] The improvement plan table 125 is a table for holding improvement plans for reducing costs, the details of which will be described later with reference to FIG.

[0027] The policy table 126 is a table that holds policies such as a cost priority policy for setting a backup with the highest priority on cost, and an RTO priority policy for setting a remote copy with the highest priority on RTO (Recovery Time Objective). The policy table 126 is set in advance by a user of the management server 101. Details will be described later with reference to FIG. 8.

[0028] A data center DC1 on the source side (for example, an on-premise type) that is the backup source has a gateway GW1 and a storage group ST1s. A storage in the storage group ST1s is represented as a storage ST1. If there are multiple storages ST1, a branch number is added to the end.

[0029] A data center DC2 on the target side (for example, a public cloud type) that is the backup destination has a gateway GW2 and a storage group ST2s. A storage in the storage group ST2s is represented as a storage ST2. If there are multiple storages ST2, a branch number is added to the end.

[0030] When there is no distinction between the gateways GW1 and GW2, they are referred to as gateway GW. When there is no distinction between the storage groups ST1s and ST2s, they are referred to as storage group STs. Storage in the storage group STs is referred to as storage ST.

[0031] <Example of hardware configuration of computer (management server 101, data center DC)> FIG. 2 is a block diagram showing an example of a hardware configuration of a computer. The computer 200 includes a processor 201, a storage device 202, an input device 203, an output device 204, and a communication interface (communication IF) 205. The processor 201, the storage device 202, the input device 203, the output device 204, and the communication IF 205 are connected by a bus 206. The processor 201 controls the computer 200. The storage device 202 serves as a working area for the processor 201. The storage device 202 is a non-transient or temporary recording medium that stores various programs and data. Examples of the storage device 202 include a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), and a flash memory. The input device 203 inputs data. Examples of the input device 203 include a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a microphone, and a sensor. The output device 204 outputs data. The output device 204 may be, for example, a display, a printer, or a speaker. The communication IF 205 is connected to the network 102 and transmits and receives data.

[0032] The inter-datacenter usage configuration setting management unit 111, the hybrid cloud cost presentation unit 112, and the hybrid cloud cost prediction unit 113 are specifically functions realized by, for example, making the processor 201 execute a program stored in the storage device 202. The configuration management table 121, the performance capacity history table 122, the cost management table 123, the cost calculation rule table 124, the improvement plan table 125, and the policy table 126 are specifically realized by, for example, data tables stored in the storage device 202.

[0033] 3 is an explanatory diagram showing an example of the configuration management table 121. The configuration management table 121 has a source 301, a target 302, a pair type 303, and a status 304 as fields.

[0034] Source 301 is information for identifying the source of data, and has subfields of data center 311, storage 312, and device 313. Data center 311 is a data center DC that is the source of data, or identification information for identifying that data center DC. Storage 312 is a storage ST in a storage group STs in the data center DC that is the source of data, or identification information for identifying that storage ST. Device 313 is a device DV that is a volume (data storage area) prepared for each user, each application used, etc. in the storage ST identified by storage 312, or identification information for identifying that device DV.

[0035] The target 302 is information for identifying a destination of data transmission, and has subfields of a data center 321, a storage 322, and a device 323. The data center 321 is a data center DC to which data is transmitted or identification information for identifying the data center DC. The storage 322 is a storage ST in a storage group STs in the data center DC to which data is transmitted, or identification information for identifying the storage ST.

[0036] The device 323 is a device DV1, DV4-1, DV4-2, DV5, . . . (when there is no need to distinguish between these, they are simply referred to as device DV) or identification information for identifying the device DV.

[0037] The storages 312 and 322 may include the type of storage ST (e.g., whether it is a solid state drive (SSD) or a hard disk drive (HDD)). The storage 322 may be a public cloud service type such as "storage service 1" or a detailed description of the public cloud service type (level of quality of service).

[0038] The pair type 303 indicates the type of usage configuration between pairs, which are combinations of the source 301 and the target 302, created by management operations by the operator of the management server 101. Note that "remote copy (synchronization)" is an operation for completely matching the data of the source 301 and the data of the target 302. In other words, writing to the source 301 will be successful after writing to the target 302 is successful.

[0039] The status 304 indicates the state of the usage configuration between the pair of the source 301 and the target 302. Here, the status 304 being "synchronized" indicates a state in which writing to the source 301 is successful after writing to the target 302 is successful.

[0040] 4 is an explanatory diagram showing an example of the performance capacity history table 122. The performance capacity history table 122 has an acquisition date and time 401, a target node 402, an observation item 403, and an observation value 404 as fields.

[0041] The acquisition date and time 401 is the date and time when the target node 402 of the entry acquired the observation value 404 of the observation item 403. The target node 402 is identification information for identifying the observation source of the observation value 404. The target node 402 has a data center 411, a storage 412, and a device 413 as subfields. The data center 411 is a data center DC constituting the target node 402 or identification information for identifying the data center DC. The storage 412 is a storage ST in a storage group STs in the data center DC constituting the target node 402 or identification information for identifying the storage ST. The device 413 is a device DV of the storage 412 constituting the target node 402 or identification information for identifying the device DV.

[0042] The observation item 403 is an item of the observation value 404 observed from the device 413, that is, a performance index. The observation item 403 is, for example, the capacity and write speed (Write IOPS) of the device 413. The observation value 404 is a value observed for the observation item 403.

[0043] The information stored in the performance capacity history table 122 is information that can be input to the cost calculation formula of the cost calculation rule 604 of the cost calculation rule table 124 (FIG. 6). For example, if the cost calculation formula has a term including an acquisition period length, the difference between two acquisition dates and times 401 can be substituted into the cost calculation formula as the acquisition period length. Also, if the cost calculation formula satisfies a specific condition depending on the type of storage 412 or device 413, for example, if a free quota is applied, the storage 412 or device 413 can be applied to the cost calculation formula. Also, if the cost calculation formula has a term including an observation item 403, the observation value 404 of the observation item 403 can be substituted into the cost calculation formula.

[0044] 5 is an explanatory diagram showing an example of the cost management table 123. The cost management table 123 is a table for managing the performance value for each service executed in the data center DC. The cost management table 123 has fields of date 501, data center 502, service 503, service instance 504, and service cost 505.

[0045] A date 501 is the date on which the service was executed at the data center DC. A data center 502 is the data center DC that executed the service.

[0046] A service 503 is a software function provided by the data center 502. A service instance 504 is an entity of the service 503 provided by the data center 502. A service cost 505 is a cost incurred for the service 503, and specifically, for example, a unit price per capacity of the storage ST used in the service 503.

[0047] 6 is an explanatory diagram showing an example of the cost calculation rule table 124. The cost calculation rule table 124 has fields such as a data center 321, a storage 322, a pair type 303, and a cost calculation rule 604. A combination of values ​​of the fields in the same row forms an entry that specifies one cost calculation rule. An entry may be registered for each piece of information such as an available region with different fees.

[0048] The cost calculation rule 604 is a predefined rule for calculating the service fee 505, and is defined by a cost calculation formula for calculating the cost. In the cost calculation rule 604, “S device” refers to the device 313 of the source 301, and “T device” refers to the device 323 of the target 302.

[0049] The "device capacity change trend" is the amount of capacity change of the device DV per unit time (1 minute). Specifically, for example, the "device capacity change trend" is a value obtained by dividing the difference in the observed value 404 having different acquisition dates and times 401 between entries for the same target node 402 and the observation item 403 being "Capacity" in the performance capacity history table 122 by the difference in the acquisition dates and times 401.

[0050] For example, the entry on the first line and the entry on the third line are the same target node 402 and the observation item 403 is "Capacity". Therefore, the difference in the observation value 404 is 1 GB (= 101 GB - 100 GB), and the difference in the acquisition date and time 401 is 5 minutes (= "2022 / 05 / 18 / 13:35" - "2022 / 05 / 18 / 13:30"). Therefore, when the observation item 403 is "Capacity", the "device capacity change trend" of the target node 402 whose data center 411 is "DC1", whose storage 412 is "ST1-1", and whose device 413 is "DV1" is 0.2 GB / min (= 1 G / 5 min).

[0051] "Time(s)" is a variable for converting the unit time of the "device capacity fluctuation trend" from minutes to seconds.

[0052] "Device capacity unit price" is the unit price per capacity of the device DV, and is the service fee 505 in the cost management table 123 in Fig. 5. Specifically, for example, the data center DC and storage ST of the device DV are identified from the configuration management table 121. The management server 101 acquires, as the "device capacity unit price", the fee corresponding to "Storage", which is the service 503, where the identified data center DC exists in the data center 502, from known usage fee information provided by the cloud vendor.

[0053] "Device performance Write IOPS average" is the average value of Write IOPS, which is the performance of the device DV per unit time (1 minute). Specifically, for example, it is the average value of observed values ​​404 with different acquisition dates and times 401 between entries in the performance capacity history table 122 for the same target node 402 and with the observation item 403 being "Write IOPS".

[0054] For example, the entries on the second and fourth lines are for the same target node 402 and the observation item 403 is "Write IOPS". Therefore, the average value of the observation value 404 is 600 (= (200 + 1000) / 2). Therefore, when the observation item 403 is "Write IOPS", the "Device performance Write IOPS average" for the acquisition period ("2022 / 05 / 18 / 13:30" to "2022 / 05 / 18 / 13:35") of the target node 402 whose data center 411 is "DC1", whose storage 412 is "ST1-1", and whose device 413 is "DV1" when the observation item 403 is "Write IOPS" is "600".

[0055] The "free limit (Write IOPS)" is a free limit for charges when the observation item 403 specified in a data center DC such as a public cloud is "Write IOPS", and is set in advance in a table not shown.

[0056] "Backup acquisition elapsed time (s)" is the interval between regular backups (user-specified or default setting), and is set in advance in a table (not shown). When "regular backup" is selected as the pair type 303, the cost calculation result calculated by the cost calculation rule 604 is the cumulative total for each regular backup interval.

[0057] The "basic license fee for device usage" is a license fee required when using software installed in the storage ST, and is set in advance in a table (not shown).

[0058] "Device performance IOPS average" is the average value of Write / Read IOPS, which is the performance of the device DV per unit time (1 minute). Write / Read IOPS is the total value of Write IOPS and Read IOPS. Specifically, for example, it is the average value of observed values ​​404 with different acquisition dates and times 401 between entries in the performance capacity history table 122 for the same target node 402 and with the observed item 403 being "Write IOPS" and "Read IOPS".

[0059] "Device IOPS unit price" is the price per 1 IOPS. In the cost management table 123 in Fig. 5, a service fee 505 for each service 503 is specified, and this service fee 505 is exemplified as a capacity unit price, but in a data center DC, particularly in the use of a data center for a public cloud service, in addition to the capacity unit price, more detailed unit prices of the service 503, such as an IOPS unit price and a throughput unit price, are generally specified. Therefore, it is specified in the same way as the "device capacity unit price".

[0060] 7 is an explanatory diagram showing an example of the improvement plan table 125. The improvement plan table 125 has a pair type 303, an improvement plan variable type 701, and a variable setting value 702 as fields.

[0061] The improvement plan variable type 701 is a plan indicating a measure for reducing costs. The variable setting value 702 is a value set to a variable included in the improvement plan variable type 701. Specifically, for example, the variable setting value 702 is a value set to a variable in a cost calculation formula identified by the pair type 303 corresponding to the improvement plan variable type 701.

[0062] 8 is an explanatory diagram showing an example of the policy table 126. The policy table 126 has, as fields, a policy 801 and a condition 802. The policy 801 is the name of an inter-datacenter usage configuration setting execution policy. The condition 802 is a constraint used for the inter-datacenter usage configuration setting execution policy specified by the policy 801.

[0063] The inter-datacenter usage configuration setting execution policy is a policy that is set in advance by the user, and indicates, for example, a policy for setting backup with "cost priority" and setting remote copy with "RTO (Recovery Time Objective) priority." Specifically, when "cost priority" is set as the policy 801, the management server 101 executes, by the inter-datacenter usage configuration setting management unit 111, the inter-datacenter usage configuration setting process (described later in FIG. 9) for the configuration of the target 302 (combination of datacenter 321, storage 322, and pair type 303) with the lowest service cost 505.

[0064] Furthermore, if a "cost limit" is set as policy 801, the management server 101 executes an inter-datacenter usage configuration setting process using the inter-datacenter usage configuration setting management unit 111 for a target 302 configuration that satisfies a monthly backup cost of "$10,000 / month" or less.

[0065] Furthermore, when "performance priority" is set as the policy 801, the management server 101, via the inter-datacenter usage configuration setting management unit 111, executes the inter-datacenter usage configuration setting process for the configuration of the target 302 that provides the best performance.

[0066] Furthermore, if "RTO limit" is set as policy 801, the management server 101 executes, via the inter-datacenter usage configuration setting management unit 111, an inter-datacenter usage configuration setting process for a configuration of the target 302 that satisfies the recovery time from a failure occurrence of "within 1 hour."

[0067] <Inter-datacenter usage configuration setting process> 9 is a flowchart showing an example of an inter-datacenter usage configuration setting process procedure. The inter-datacenter usage configuration setting management unit 111 acquires inter-datacenter usage configuration setting information (step S901). The inter-datacenter usage configuration setting information includes the source 301, the target 302, and a start date and time. Specifically, for example, the inter-datacenter usage configuration setting management unit 111 displays the configuration management table 121, and accepts the selection of the inter-datacenter usage configuration setting information, which is an entry in the configuration management table 121, from the input device 203, and also accepts the start date and time.

[0068] The inter-datacenter usage configuration setting management unit 111 may accept, as the inter-datacenter usage configuration setting information, an input of the configuration of the target 302 (combination of the datacenter 321, storage 322, and pair type 303) that specifies the cost calculation rule 604. Information such as the maximum transfer speed (speed limit) if the pair type 303 is remote copy, the backup acquisition interval if the pair type 303 is periodic backup, the backup storage period, the number of backups to be saved (how many backups to keep), whether to transfer backup data (snapshots) acquired in the storage 312 of the source 301 to the target 302 together, and whether or not a cost estimate is requested may be included.

[0069] The inter-datacenter usage configuration setting management unit 111 may automatically execute the setting operation of the inter-datacenter usage configuration setting information. In the case where there is only one setting operation, there is only one possible configuration of the target 302 (combination of the datacenter 321, storage 322, and pair type 303), or there is a case where a unique configuration is determined from among multiple target 302 configurations by the inter-datacenter usage configuration setting execution policy. In the latter case, a configuration that satisfies the inter-datacenter usage configuration setting execution policy is set.

[0070] Furthermore, if a condition based on a quantitative value, such as a monthly backup cost per data item being 100,000 yen or less, is set, the inter-datacenter usage configuration setting with the configuration of the target 302 that satisfies that condition is selected and displayed. If an inter-datacenter usage configuration setting execution policy that prioritizes RTO or performance, or more complicated conditions other than cost are specified, it becomes possible to set inter-datacenter usage configuration setting information based on the inter-datacenter usage configuration setting execution policy by using it in combination with the estimation process based on the conventional technology.

[0071] Next, the hybrid cloud cost prediction unit 113 executes a cost estimation process for the inter-datacenter usage configuration to be set (step S902). A cost estimation result is generated by the cost estimation process for the inter-datacenter usage configuration to be set (step S902). Details of the cost estimation process for the inter-datacenter usage configuration to be set (step S902) will be described later with reference to FIG. 10.

[0072] After step S902, the inter-datacenter usage configuration setting management unit 111 displays the inter-datacenter usage configuration setting information including the cost estimation result (step S903) (see FIG. 14).

[0073] Next, the inter-datacenter usage configuration setting management unit 111 receives an inter-datacenter usage configuration setting execution request from the input device 203 (step S904). Upon receiving the inter-datacenter usage configuration setting execution request, the inter-datacenter usage configuration setting management unit 111 executes the inter-datacenter usage configuration setting (step S905). Upon completion of the execution of the inter-datacenter usage configuration setting, the inter-datacenter usage configuration setting process ends.

[0074] <Cost Estimation Process for Planned Inter-Datacenter Usage Configuration (Step S902)> 10 is a flowchart showing a detailed example of a processing procedure of the cost estimation processing (step S902) of the inter-datacenter usage configuration to be set. The hybrid cloud cost prediction unit 113 acquires the inter-datacenter usage configuration setting information (source 301, target 302, start date and time) from the inter-datacenter usage configuration setting management unit 111 (step S1000). If the inter-datacenter usage configuration setting information does not include the configuration of the target 302 (combination of the datacenter 321, storage 322, and pair type 303) that specifies the cost calculation rule 604, the inter-datacenter usage configuration setting management unit 111 may set the configuration of the target 302 that satisfies the inter-datacenter usage configuration setting execution policy as described above.

[0075] Next, the inter-datacenter usage configuration setting management unit 111 judges whether or not the configuration of the target 302 (combination of the data center 321, storage 322, and pair type 303) is specified in the inter-datacenter usage configuration setting information (step S1001).

[0076] If a configuration of the target 302 (a combination of the data center 321, the storage 322, and the pair type 303) exists (step S1001: Yes), the inter-datacenter usage configuration setting management unit 111 extracts a cost calculation formula corresponding to the specified configuration of the target 302 (a combination of the data center 321, the storage 322, and the pair type 303) from the cost calculation rules 604 in the cost calculation rule table 124 (FIG. 6) (step S1002).

[0077] Then, the inter-datacenter usage configuration setting management unit 111 acquires information required for the cost calculation formula from the performance capacity history table 122 (FIG. 4) and usage fee information provided by the cloud vendor (step S1003). The usage fee information provided by the cloud vendor is fee information determined for each cloud resource, such as the hourly usage price of the compute resource, the capacity price of the storage area, the basic license fee for function usage, and free frame information for usage. The usage fee information provided by the cloud vendor is stored in a table not shown.

[0078] Next, the inter-datacenter utilization configuration setting management unit 111 executes cost calculation by substituting the information acquired in step S1004 into the extracted cost calculation formula, and outputs the cost calculation result (step S1004).

[0079] Next, the inter-datacenter usage configuration setting management unit 111 creates a cost estimation result including the cost calculated in step S1004, the configuration of the specified target 302 (combination of data center 321, storage 322, and pair type 303), and the source 301 (step S1005).

[0080] Then, the inter-datacenter usage configuration setting management unit 111 outputs the cost estimation result (step S1006), which ends the cost estimation process for the to-be-set inter-datacenter usage configuration (step S902), and the process proceeds to step S903.

[0081] On the other hand, in step S1001, if the configuration of the target 302 is not specified in the cost estimate request (step S1001: No), the inter-datacenter usage configuration setting management unit 111 extracts the cost calculation rule 604 from the cost calculation rule table 124 (step S1007).

[0082] The inter-datacenter usage configuration setting management unit 111 selects an unselected cost calculation formula from the cost calculation rules 604 (step S1008). As in step S1004, the inter-datacenter usage configuration setting management unit 111 acquires information required for the selected cost calculation formula from the performance capacity history table 122 (FIG. 4) and usage fee information provided by the cloud vendor (step S1009).

[0083] Next, the inter-datacenter utilization configuration setting management unit 111 substitutes the information acquired in step S1009 into the cost calculation formula and outputs the cost calculation result (step S1010). If there is an unselected cost calculation formula, the process returns to step S1008, and if there is no unselected cost calculation formula, the loop ends and the process proceeds to step S1012 (step S1011).

[0084] Next, the inter-datacenter usage configuration setting management unit 111 judges whether or not an inter-datacenter usage configuration setting execution policy is set (step S1012). If an inter-datacenter usage configuration setting execution policy is set (step S1012: Yes), the inter-datacenter usage configuration setting management unit 111 acquires a cost calculation result that satisfies the inter-datacenter usage configuration setting execution policy, creates a cost estimation result (step S1013), and proceeds to step S1006.

[0085] For example, if policy 801 is "cost limit," condition 802 is "$10,000 / month," so if the cost calculated in step S1010 is "$10,000 / month," the cost calculated in step S1010, the configuration of source 301, and target 302 are used to create a cost estimation result.

[0086] When more complex conditions other than cost, such as RTO restrictions or performance-first policies, are specified, it becomes possible to select inter-datacenter usage configuration settings based on the policy by using it in conjunction with estimation processing using known techniques. For example, if policy 801 is "RTO restrictions," and condition 802 is "within 1 hour," configurations using synchronous remote copy or asynchronous remote copy that enable immediate recovery will be subject to the creation of cost estimation results, but regular backups that take more than 1 hour to recover the system will not be subject to them.

[0087] On the other hand, if the inter-datacenter usage configuration setting execution policy has not been set (step S1012: No), the inter-datacenter usage configuration setting management unit 111 acquires the cost calculation results for each cost calculation formula, creates cost estimation results for the configuration of each target 302 (combination of data center 321, storage 322, and pair type 303) (step S1014), and proceeds to step S1006.

[0088] <Hybrid cloud cost display processing> 11 is a flowchart showing an example of a hybrid cloud cost display process procedure. The hybrid cloud cost presenter 112 acquires a cost display request (step S1100). The cost display request includes at least the specification of the date 501 among the date 501, the data center 502, the service 503, and the service instance 504. The specification of the date 501 may be a certain one day, or a period of multiple consecutive days (for example, one week or one month). The date 501 may be specified by default. Hereinafter, this is referred to as a cost display request period.

[0089] When the hybrid cloud cost presenting unit 112 receives a cost display request, it retrieves the public cloud cost from the cost management table 123 (FIG. 5) (step S1101). The public cloud cost includes the date 501, the data center 502, the service 503, the service instance 504, and the service fee 505 that correspond to the cost display request.

[0090] The hybrid cloud cost presenting unit 112 obtains a public cloud cost estimate by using the public cloud cost obtained in step S1101 (step S1102). Specifically, for example, the public cloud cost estimate is an average value (statistical value) of the total service cost 505 per day obtained by dividing the total service cost 505 in the public cloud cost by the period specified by the date 501 included in the cost display request.

[0091] When the hybrid cloud cost presenting unit 112 receives the cost display request, it obtains configuration management information from the configuration management table 121 (FIG. 3) (step S1103). The configuration management information includes the source 301, the target 302, the pair type 303, and the status 304. The hybrid cloud cost presenting unit 112 obtains configuration management information in which the data center 502 in the public cloud cost information corresponds to either the data center 311 of the source 301 or the data center 321 of the target 302.

[0092] The hybrid cloud cost presenting unit 112 determines whether or not an on-premise-public cloud usage configuration exists (step S1104). The on-premise-public cloud usage configuration is configuration management information obtained in step S1102 in which the data center 311 is on-premise and the data center 321 is a public cloud, or the data center 311 is a public cloud and the data center 321 is on-premise.

[0093] A configuration that is not an on-premise-public cloud usage configuration is configuration management information obtained in step S1102 in which data centre 311 and data centre 321 are both on-premise, or in which data centre 311 and data centre 321 are both public clouds.

[0094] If there is no on-premise-public cloud usage configuration (step S1105: No), the hybrid cloud cost presenting unit 112 outputs the public cloud cost information acquired in step S1102 in a displayable manner (step S1105).

[0095] On the other hand, if an on-premise-public cloud usage configuration exists (step S1104: Yes), the hybrid cloud cost presenting unit 112 selects an unselected on-premise-public cloud usage configuration (configuration management information) (step S1106).

[0096] The hybrid cloud cost presentation unit 112 extracts a cost calculation formula for the configuration (data center 321, storage 322, pair type 303) of the target 302 that matches the data center 321, storage 322, and pair type 303 of the target 302 in the selected on-premise-public cloud usage configuration (configuration management information) from the cost calculation rules 604 (Figure 6) of the cost calculation rule table 124 (step S1107).

[0097] The hybrid cloud cost presenting unit 112 acquires information required for the cost calculation formula extracted in step S1107 from the performance and capacity history table 122 (step S1108).

[0098] The hybrid cloud cost presenting unit 112 substitutes the information acquired in step S1108 into the cost calculation formula extracted in step S1107 to calculate the cost to be the actual value (step S1109). If there is an unselected cost calculation formula, the process returns to step S1106, and if there is no unselected cost calculation formula, the loop ends and the process proceeds to step S1111 (step S1110).

[0099] The hybrid cloud cost presenting unit 112 waits for an input of an estimate display request (step S1111). The estimate display request includes the estimate display request target period. If there is no estimate display request (step S1111: No), the on-premise portion of the public cloud cost for the acquired cost display request target period is displayed separately (step S1112) (see FIG. 15). This on-premise portion of the cost is the cost (actual value) calculated in step S1109. Specifically, for example, when there is a setting between on-premise and the public cloud, this on-premise portion of the cost is the public cloud cost (actual value) incurred due to the amount of data transferred to the public cloud side by the setting in response to a request to the on-premise side.

[0100] On the other hand, if there is an estimate display request (step S1111: Yes), the hybrid cloud cost presenting unit 112 executes a cost estimate process for the inter-datacenter usage configuration setting (step S1113) (described later with reference to FIG. 12).

[0101] The hybrid cloud cost presenting unit 112 displays the on-premise cost estimate separately from the public cloud cost estimate for the estimate display request period acquired in step S1102 (step S1114) (see FIG. 16). This ends the hybrid cloud cost display process.

[0102] Although the cost of the public cloud and the cost of the public cloud resulting from the configuration connecting the on-premise and the public cloud have been explained, if the on-premise environment is not an environment where the device is purchased outright, but an environment where costs are charged based on capacity etc., the on-premise cost may also be displayed. The on-premise cost can be calculated based on the contract information between the user and the on-premise environment provider (billing method, unit price information) and the on-premise usage status (performance capacity history table 122).

[0103] <Cost Estimation Processing for Inter-Datacenter Usage Configuration Settings (Step S1113)> 12 is a flowchart showing a detailed example of a processing procedure of the cost estimation process (step S1113) for setting an inter-datacenter usage configuration. The cost estimation process (step S1113) for setting an inter-datacenter usage configuration is a process for calculating a cost estimate based on a past performance capacity history. The hybrid cloud cost presenting unit 112 selects an unselected on-premise-public cloud usage configuration (configuration management information) (step S1201).

[0104] The hybrid cloud cost presentation unit 112 extracts a cost calculation formula for the configuration (data center 321, storage 322, pair type 303) of the target 302 that matches the data center 321, storage 322, and pair type 303 of the target 302 in the on-premise-public cloud usage configuration (configuration management information) selected in step S1201 from the cost calculation rules 604 (Figure 6) of the cost calculation rule table 124 (step S1202).

[0105] The hybrid cloud cost presenting unit 112 acquires information required for the cost calculation formula extracted in step S1202 from the performance capacity history table 122 (step S1203). The hybrid cloud cost presenting unit 112 substitutes the information acquired in step S1203 into the cost calculation formula extracted in step S1202 to calculate the cost to be the estimated value, and creates an estimate result for the selected on-premise-public cloud usage configuration (configuration management information) (step S1204).

[0106] The hybrid cloud cost presenting unit 112 executes an individual improvement plan creation process (step S1205) (described later in FIG. 12). If there is an unselected on-premise-public cloud usage configuration (configuration management information), the process returns to step S1201, and if there is no unselected on-premise-public cloud usage configuration (configuration management information), the process ends the loop and proceeds to step S1207 (step S1206).

[0107] The hybrid cloud cost presenting unit 112 creates an overall improvement plan using the individual improvement plan for each on-premise-public cloud usage configuration (configuration management information) (step S1207). The overall improvement plan is not an individual setting, but an improvement plan that can be taken in the public cloud, for example, a measure that can be used at a discounted price on the condition that a certain amount of resources are continuously used. At this time, by clarifying the resource usage amount due to the on-premise-public cloud configuration, it becomes easy to determine whether the continued use will continue in the future. For example, when synchronous remote copy is being executed, the usage will continue continuously, so that amount can be made the subject of a discount application. After this, the cost estimation process for the inter-datacenter usage configuration setting (step S1113) is terminated, and the process proceeds to step S1114.

[0108] <Individual Improvement Plan Creation Process (Step S1205)> Fig. 13 is a flowchart showing a detailed example of the processing procedure of the individual improvement plan creation process (step S1205) shown in Fig. 12. The hybrid cloud cost presenting unit 112 acquires, from the improvement plan table 125, the improvement plan variable type 701 in the entry of the pair type 303 that matches the pair type 303 in the configuration (data center 321, storage 322, pair type 303) of the target 302 in the on-premise-public cloud usage configuration (configuration management information) selected in step S1201 (step S1301).

[0109] The hybrid cloud cost presenting unit 112 selects an unselected combination of an improvement plan variable type 701 and its variable setting value 702 from among the improvement plan variable types 701 acquired in step S1301 (step S1302). The hybrid cloud cost presenting unit 112 creates an individual improvement plan by combining the selected improvement plan variable type 701 and variable setting value 702 (step S1303).

[0110] At that time, the hybrid cloud cost presenting unit 112 extracts a cost calculation formula from the cost calculation rule 604 corresponding to the pair type 303 that matches the improvement plan variable type 701. If the extracted cost calculation formula does not have a term that constrains the variable setting value 702, the hybrid cloud cost presenting unit 112 creates an individual improvement plan that exhaustively covers all the variables (X) of the variable setting value 702 that are applicable to the extracted cost calculation formula.

[0111] For example, assume that the pair type 303 is "regular backup" and there are two improvement plan variable types 701 that can be applied to the extracted cost calculation formula: "change backup frequency (X)" and "change backup speed (X)." The variable (X) in the variable setting value 702 for "change backup frequency (X)" is "3 / 4," "1 / 2," and "1 / 4," while the variable (X) in the variable setting value 702 for "change backup frequency (X)" is "low speed," "medium speed," and "high speed." In this case, nine individual improvement plans are created.

[0112] On the other hand, if the extracted cost calculation formula contains a term that constrains the variable setting value 702, the hybrid cloud cost presenting unit 112 creates an individual improvement plan that applies a variable (X) of the variable setting value 702 that is applicable to the extracted cost calculation formula in accordance with the constraint (for example, an inter-datacenter usage configuration setting execution policy).

[0113] For example, as in the above, assume that the pair type 303 is "regular backup" and the improvement plan variable types 701 applicable to the extracted cost calculation formula are "backup frequency (X) change" and "backup speed (X) change." If the extracted cost calculation formula contains a term where the backup speed is medium or lower and a free limit is applied, the hybrid cloud cost presenting unit 112 applies "medium" and "slow" out of the variable setting values ​​702 of "backup speed (X) change" of the improvement plan variable type 701, "slow," "medium," and "high." In this case, six individual improvement plans are created.

[0114] Furthermore, when a plurality of storages 322 exist in the data center 321 of the target 302, the hybrid cloud cost presenting unit 112 may create an individual improvement plan as described above for each of the plurality of storages 322. Furthermore, when a plurality of devices 323 exist in the storage 322 of the data center 321 of the target 302, the hybrid cloud cost presenting unit 112 may create an individual improvement plan as described above for each of the plurality of devices 323.

[0115] The hybrid cloud cost presenting unit 112 calculates an estimated cost after the improvement plan is implemented for each of the created individual improvement plans (Step S1304).

[0116] If there is an unselected combination of improvement plan variable type 701 and variable setting value 702, the process returns to step S1301, and if there is no unselected combination of improvement plan variable type 701 and variable setting value 702, the loop ends and the process proceeds to step S1206 (step S1305).

[0117] <Cost estimate result display screen> Fig. 14 is an explanatory diagram showing an example of a cost estimate result display screen. The cost estimate result display screen 1400 is a screen displayed in step S903 of Fig. 9. The cost estimate result display screen 1400 displays, as inter-datacenter usage configuration setting information, the device 313 of the source 301, the device 323 of the target 302, the pair type 303, a start date and time 1401 of the pair type 303, and a cost estimate result 1402.

[0118] By referring to the cost estimate result display screen 1400, the user can check whether there are any problems with the input connection configuration and whether there are any problems with the cost estimate result 1402.

[0119] <Cost performance screen> FIG. 15 is an explanatory diagram showing an example of a cost actual result screen. The cost actual result screen 1500 is a screen displayed in step S1112 of FIG. 11. The cost actual result screen 1500 displays a graph 1501 showing the actual usage due to the inter-datacenter usage configuration setting with respect to the total cost. Note that when there are multiple inter-datacenter usage configuration settings, the costs are displayed in a list according to each inter-datacenter usage configuration setting, but the cost of the pubkura usage attributable to the on-premise-public cloud configuration may be displayed separately. Also, a setting or details screen may be prepared to display the type of inter-datacenter usage configuration setting and details of the cost calculation formula.

[0120] Also, although an example of displaying for each datacenter connection configuration has been shown here, it is also possible to display for each public cloud service or function. Specifically, it is also possible to show the portion of the cost of the storage provision service that is based on the inter-datacenter usage configuration setting (TB / h), or the portion of the data inflow that is based on the inter-datacenter usage configuration setting (TB / month), etc. Also, although an example of displaying both the actual results and the estimates together has been shown, they may be presented on separate screens.

[0121] <Cost Estimation Screen> Fig. 16 is an explanatory diagram showing an example of a cost estimate screen. The cost estimate screen 1600 is a screen displayed in step S1114 of Fig. 11. The cost estimate screen 1600 displays a graph 1601 indicating the estimated usage amount based on the inter-datacenter usage configuration setting against the total cost. The black parts of the graph 1601 are the estimation results for each usage configuration calculated in step S1204.

[0122] The details of the graph 1601 correspond to a row selected by a radio button (a black circle radio button) in the inter-datacenter usage configuration setting improvement candidate table 1610. Each row of the inter-datacenter usage configuration setting improvement candidate table 1610 is the calculation result of step S1204. Among these, "Estimated Cost" is the cost calculated in step S1204.

[0123] The cost estimate screen 1600 also displays improvement plan information 1602 indicating the improvement plan and its post-improvement cost. The entry in the first line of the improvement plan information 1602 is the overall improvement plan calculated in step S1207.

[0124] Creating an overall improvement plan is not about individual settings, but about measures that can be taken in the public cloud as a whole system, such as measures that allow for a discounted price on the condition that a certain amount of resources are used continuously. At this time, by clarifying the resource usage resulting from the usage configuration, it becomes easier to determine whether the continued use will continue in the future. For example, if synchronous remote copy is being executed, the usage will continue continuously, so that amount will be subject to the discount. One example is "Continued use discount (1 year) DC2 Storage."

[0125] The entries in the second and third rows of the improvement plan information 1602 are improvement plans and the estimated costs after the improvement plans are implemented (step S1304). The rectangular shape at the left end of the improvement plan information 1602 is a checkbox 1621. When that row is selected, the checkbox 1621 turns black as shown in FIG. 16, and when not selected, the checkbox 1621 turns white.

[0126] The circular shapes on the left edge of the improvement plan information 1602 are radio buttons 1622 and 1623, and the individual improvement plan (created in the individual improvement plan creation process (step S1205)) of either radio button can be selected. When an improvement plan in the second row is selected, the radio button 1622 turns black, and the improvement plan in the third row can no longer be selected, so the radio button 1623 turns white.

[0127] In this way, according to this embodiment, it is possible to optimize the estimate of the public cloud usage costs taking into account the connection configuration using on-premise-public cloud before starting operation of the hybrid cloud configuration.

[0128] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the configurations described. Also, a part of the configuration of one embodiment may be replaced with a configuration of another embodiment. Also, a configuration of another embodiment may be added to a configuration of one embodiment. Also, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0129] Furthermore, each of the aforementioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0130] Information such as programs, tables, files, etc. that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC (Integrated Circuit) card, an SD card, or a DVD (Digital Versatile Disc).

[0131] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0132] 100 Hybrid Cloud Systems 101 Management Server 102 Network 111 Datacenter Inter-Use Configuration Settings Management Unit 112 Hybrid Cloud Cost Presentation Section 113 Hybrid Cloud Cost Estimation Department 113 Hybrid Cloud Cost Presentation Section 121 Configuration Management Table 122 Performance Capacity History Table 123 Cost Management Table 124 Cost Calculation Rule Table 125 Improvement Suggestions Table 126 Policy Table 201 Processor 202 Storage Devices

Claims

1. A management method executed by a management device that manages a usage configuration of a service provided between a first device of a first device group and a second device of a second device group, the method comprising: The management device includes a processor that executes a program and a storage device that stores the program; The storage device has a configuration management table, a cost calculation rule table, and a performance capacity history table, the configuration management table stores a first storage area of ​​the first device, a second storage area of ​​the second device, and a type of the usage configuration; the performance capacity history table stores observation items in the first storage area, observation values ​​related to the observation items, and acquisition dates and times of the observation values; the cost calculation rule table stores one or more cost calculation formulas that are rules for calculating a cost of using the second storage area in the type of the usage configuration based on at least one of the first storage area, the observed value, and the acquisition date and time; In the management method, The processor, an acquisition process for acquiring configuration management information including at least the first storage area and the second storage area; an extraction process of extracting, from the cost calculation rule table, the cost calculation formula in the second storage area included in the configuration management information acquired by the acquisition process; a first calculation process for obtaining values ​​to be substituted into variables of the cost calculation formula from the performance and capacity history table and calculating a cost estimate value using the cost calculation formula; a creation process for creating a cost estimation result including the cost estimate value calculated by the first calculation process, the first storage area, the second storage area, and a type of the usage configuration that uses the second storage area; an output process for outputting the cost estimation result created by the creation process; A management method comprising the steps of:

2. The management method according to claim 1, The processor, execute a determination process to determine whether or not the second storage area and the type of the usage configuration are included in the configuration management information; In the extraction process, the processor extracts the cost calculation formula based on a determination result in the determination process. A management method comprising:

3. The management method according to claim 2, The processor, execute a determination process to determine whether or not the second storage area and the type of the usage configuration are included in the configuration management information; In the extraction process, when the second storage area and the type of the usage configuration are included by the determination process, the processor extracts a specific cost calculation formula for using the second storage area in the type of the usage configuration; In the first calculation process, the processor obtains values ​​to be substituted for variables of the specific cost calculation formula from the performance capacity history table, and calculates the specific cost estimate value using the specific cost calculation formula; In the creation process, the processor creates a cost estimation result including the specific cost estimate value calculated by the first calculation process, the second storage area, and the type of the usage configuration. A management method comprising:

4. The management method according to claim 2, The processor, execute a determination process to determine whether or not the second storage area and the type of the usage configuration are included in the configuration management information; In the extraction process, when the second storage area and the type of the usage configuration are not included by the determination process, the processor extracts the cost calculation formula for all combinations of the second storage area and the type of the usage configuration in the cost calculation rule table, In the first calculation process, the processor obtains values ​​to be substituted for the variables of the cost calculation formula from the performance and capacity history table, and calculates the cost estimate value for each of the combinations using the cost calculation formula; In the creation process, the processor creates a cost estimation result including, for each combination, the cost estimate value calculated by the first calculation process, the second storage area, and the type of the usage configuration. A management method comprising:

5. The management method according to claim 4, the storage device stores a policy table that stores a policy that specifies a constraint condition; In the creation process, the processor creates the cost estimation result for the combination that satisfies the constraint condition. A management method comprising:

6. The management method according to claim 1, the cost calculation rule table stores one or more cost calculation formulas that serve as rules for calculating a cost estimate value for using the first storage area in the type of the usage configuration based on at least one of the second storage area, the observation value, and the acquisition date and time; In the extraction process, the processor extracts the cost calculation formula in the first storage area included in the configuration management information from the cost calculation rule table; In the creation process, the processor creates a cost estimation result including the cost estimate value, the first storage area, the second storage area, and a type of the usage configuration that uses the first storage area. A management method comprising:

7. The management method according to claim 1, the storage device has a cost management table; the cost management table stores actual service costs for a provider device that provides the service among the first device group and the second device group; In the acquisition process, the processor refers to the cost management table to acquire a statistical value of the total service fee, In the output process, the processor outputs the cost estimation result separately from the statistical value of the total service fee acquired by the acquisition process. A management method comprising:

8. The management method according to claim 1, The storage device has an improvement plan table, the improvement plan table stores a type of the utilization configuration and one or more variable setting values ​​that can be set to the variables of the cost calculation formula corresponding to the type of the utilization configuration; The processor, execute a second calculation process in which the variable setting values ​​to be substituted into the variables in the cost calculation formula are obtained from the improvement plan table, and an improvement cost is calculated using the cost calculation formula; In the output process, a calculation result obtained by the second calculation process is output. A management method comprising:

9. The management method according to claim 8, the improvement plan table stores a type of the utilization configuration, one or more improvement target variables included in the cost calculation formula corresponding to the type of the utilization configuration, and one or more variable setting values ​​that can be set to the improvement target variables; In the second calculation process, the processor calculates the improvement cost for each combination of the improvement target variable and the variable setting value. A management method comprising:

10. A management device that manages a usage configuration of a service provided between a first device of a first device group and a second device of a second device group, A processor for executing a program and a storage device for storing the program, The storage device has a configuration management table, a cost calculation rule table, and a performance capacity history table, the configuration management table stores a first storage area of ​​the first device, a second storage area of ​​the second device, and a type of the usage configuration; the performance capacity history table stores observation items in the first storage area, observation values ​​related to the observation items, and acquisition dates and times of the observation values; the cost calculation rule table stores one or more cost calculation formulas that are rules for calculating a cost of using the second storage area in the type of the usage configuration based on at least one of the first storage area, the observed value, and the acquisition date and time; The processor, an acquisition process for acquiring configuration management information including at least the first storage area and the second storage area; an extraction process of extracting, from the cost calculation rule table, the cost calculation formula in the second storage area included in the configuration management information acquired by the acquisition process; a first calculation process for obtaining values ​​to be substituted into variables of the cost calculation formula from the performance and capacity history table and calculating a cost estimate value using the cost calculation formula; a creation process for creating a cost estimation result including a cost estimate value calculated by the first calculation process, the first storage area, the second storage area, and a type of the usage configuration that uses the second storage area; an output process for outputting the cost estimation result created by the creation process; A management device that executes the above.

11. A management program that causes a processor to manage a usage configuration of a service provided between a first device of a first device group and a second device of a second device group, the management program comprising: the processor is capable of accessing a storage device that stores a configuration management table, a cost calculation rule table, and a performance capacity history table; The storage device has a configuration management table, a cost calculation rule table, and a performance capacity history table, the configuration management table stores a first storage area of ​​the first device, a second storage area of ​​the second device, and a type of the usage configuration; the performance capacity history table stores observation items in the first storage area, observation values ​​related to the observation items, and acquisition dates and times of the observation values; the cost calculation rule table stores one or more cost calculation formulas that are rules for calculating a cost of using the second storage area in the type of the usage configuration based on at least one of the first storage area, the observed value, and the acquisition date and time; The processor, an acquisition process for acquiring configuration management information including at least the first storage area and the second storage area; an extraction process of extracting, from the cost calculation rule table, the cost calculation formula in the second storage area included in the configuration management information acquired by the acquisition process; a first calculation process for obtaining values ​​to be substituted into variables of the cost calculation formula from the performance and capacity history table and calculating a cost estimate value using the cost calculation formula; a creation process for creating a cost estimation result including a cost estimate value calculated by the first calculation process, the first storage area, the second storage area, and a type of the usage configuration that uses the second storage area; an output process for outputting the cost estimation result created by the creation process; A management program for causing the user to execute the above steps.

Images