Management method, management device, 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 systems departments of clients who have traditionally used on-premise systems are being asked to optimise costs and would like to use Pubkura. However, it is difficult to estimate the costs 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 migrations 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 resource usage pattern of the application 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] U.S. Patent Application Publication No. 2015 / 0019301 Summary of the Invention [Problem to be solved by the invention]

[0009] However, the above-mentioned Patent Document 1 does not allow for an appropriate estimation of public cloud usage costs before starting operation of a hybrid cloud configuration. For example, if there is a configuration connecting an on-premise system with a public cloud, it is difficult for the user to input public cloud usage details that take into account that configuration. Furthermore, an estimate that includes public cloud resource usage in a hybrid cloud configuration requires operation of a certain level of the hybrid cloud configuration.

[0010] The present invention aims to optimize the estimation of usage costs. [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 observation items, and acquisition dates and times of the observed values, and 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 stores one or more cost calculation formulas that are rules for calculating the costs to be used separately, and in the management method, the processor executes at least an acquisition process to acquire configuration management information including the first storage area and the second storage area; an extraction process to extract 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 to acquire from the performance capacity history table values ​​to be substituted for variables of the cost calculation formula and calculate a cost estimate value using the cost calculation formula; a creation process to create 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 uses the second storage area; and an output process to output the cost estimate result created by the creation process. [Effects of the Invention]

[0012] According to the exemplary embodiment of the present invention, it is possible to optimize the estimation of usage costs. Problems, configurations, and effects other than those described above will become clear from the following description of the embodiment. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram illustrating an example of a system configuration of a hybrid cloud system. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of a computer. [Figure 3] FIG. 3 is an explanatory diagram illustrating an example of a configuration management table. [Figure 4] FIG. 4 is an explanatory diagram illustrating an example of a performance capacity history table. [Figure 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 a policy table. [Figure 9] FIG. 9 is a flowchart illustrating an example of an inter-datacenter usage configuration setting process procedure. [Figure 10] FIG. 10 is a flowchart showing a detailed example of the processing procedure of cost estimation processing (step S902) for the to-be-set inter-datacenter usage configuration. [Figure 11] FIG. 11 is a flowchart illustrating an example of a hybrid cloud cost display process. [Figure 12] FIG. 12 is a flowchart showing a detailed example of the processing procedure of cost estimation processing for inter-datacenter usage configuration setting (step S1113). [Figure 13] FIG. 13 is a flowchart illustrating a detailed example of the processing procedure of the individual improvement plan creating process (step S1205) shown 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 INVENTION

[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 the backup source, and a target-side (e.g., public cloud) data center DC2 that serves as the backup destination (when DC1 and DC2 are not distinguished, 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 referred to as a usage configuration) in which data center DCs (on-premise and public clouds) are connected to each other, allowing one to 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 serves as the backup destination is assumed to be an environment where cost management is performed according to the services used. Here, the environment where 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 an on-premise and a public cloud, but it is not limited to this as long as the target data center DC that serves as the backup destination is an environment where cost management is performed according to the services 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 usage configuration setting management unit 111 presents costs resulting from the settings related to the usage configuration when planning and executing management operations.

[0019] The hybrid cloud cost presenting unit 112 presents the costs resulting from the settings related to the usage configuration separately from other costs when checking 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 in response to 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] The management server 101 also 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 that holds 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 services used by the data center DC, the details of which 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. 6.

[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 cost priority, which places the highest priority on cost when setting up backup, and RTO priority, which places the highest priority on RTO (Recovery Time Objective), when setting up remote copy. 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] The source side (for example, an on-premise type) data center DC1 that is the backup source has a gateway GW1 and a storage group ST1s. A storage in the storage group ST1s is referred to as storage ST1. If there are multiple storages ST1, a sub-number is added to the end.

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

[0030] When there is no need to distinguish between the gateways GW1 and GW2, they are referred to as gateway GW. When there is no need to distinguish between the storage groups ST1s and ST2s, they are referred to as storage group STs. Storage within 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 the 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 via 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-transitory or temporary recording medium that stores various programs and data. Examples of the storage device 202 include a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), 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 connects 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 that are realized, for example, by having 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, for example, by 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 the data center DC from which the data was sent, or identification information for identifying that data center DC. Storage 312 is a storage ST within a storage group STs in the data center DC from which the data was sent, or identification information for identifying that storage ST. Device 313 is a device DV, which is a volume (data storage area) prepared for each user, each application used, etc. within the storage ST identified by storage 312, or identification information for identifying that device DV.

[0035] The target 302 is information for specifying the destination of data, 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 sent, or identification information for specifying the data center DC. The storage 322 is a storage ST within a storage group STs in the data center DC to which data is sent, or identification information for specifying the storage ST.

[0036] The device 323 is the 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 that identifies the device DV.

[0037] The storages 312 and 322 may include the type of storage ST (e.g., SSD (Solid State Drive) or HDD (Hard Disk Drive)). The storage 322 may be a public cloud service type such as "storage service 1," or may be details of the public cloud service type (level of quality of service).

[0038] The pair type 303 indicates the type of usage configuration between a pair, which is a combination of the source 301 and the target 302, created by a management operation by the operator of the management server 101. Note that "remote copy (synchronization)" is an operation that completely matches 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 fields of an acquisition date and time 401, a target node 402, an observation item 403, and an observation value 404.

[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 that identifies 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 that constitutes the target node 402, or identification information that identifies the data center DC. The storage 412 is a storage ST in a storage group STs in the data center DC that constitutes the target node 402, or identification information that identifies the storage ST. The device 413 is a device DV of the storage 412 that constitutes the target node 402, or identification information that identifies 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 or 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 into the cost calculation formula of the cost calculation rule 604 in the cost calculation rule table 124 (FIG. 6). For example, if the cost calculation formula has a term including the 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. Furthermore, 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. Furthermore, if the cost calculation formula has a term including an observation item 403, the observation value 404 of that 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 values ​​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] The date 501 is the date on which the service was executed at the data center DC. The 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, is 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 ​​in each field in the same row forms an entry that defines 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 pre-set 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 fluctuation trend" is the amount of capacity fluctuation of the device DV per unit time (1 minute). Specifically, for example, the "device capacity fluctuation trend" is the value obtained by dividing the difference in the observed value 404 with different acquisition dates and times 401 between entries in the performance capacity history table 122 for the same target node 402 and whose observation item 403 is "Capacity" by the difference in the acquisition dates and times 401.

[0050] For example, the entries on the first and third lines are for 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 fluctuation 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 / minute (= 1 G / 5 minutes).

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

[0052] The "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 of 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 the identified data center DC existing in the data center 502 and the "Storage" service 503 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 in the performance capacity history table 122, for the same target node 402, and among entries whose observation item 403 is "Write IOPS" and whose acquisition dates and times 401 are different.

[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") for the target node 402, whose data center 411 is "DC1," whose storage 412 is "ST1-1," and whose device 413 is "DV1," is "600."

[0055] The "free limit (Write IOPS)" is the free limit of fees 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 (specified by the user or set by default), 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 the 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, in the performance capacity history table 122, it is the average value of observed values ​​404 with different acquisition dates and times 401 between entries for the same target node 402 and for which the observation item 403 is "Write IOPS" and "Read IOPS".

[0059] "Device IOPS unit price" is the price per IOPS. In the cost management table 123 of Fig. 5, a service fee 505 for each service 503 is specified, and this service fee 505 is exemplified as a capacity unit price. However, 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 for 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 fields of a pair type 303, an improvement plan variable type 701, and a variable setting value 702.

[0061] The improvement plan variable type 701 is a plan indicating a cost reduction measure. 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 fields of policy 801 and condition 802. The policy 801 is the name of the 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 set in advance by the user, and represents, for example, a policy of setting backup with "cost priority" or setting remote copy with "RTO (Recovery Time Objective) priority." Specifically, when "cost priority" is set as policy 801, the management server 101, through the inter-datacenter usage configuration setting management unit 111, executes inter-datacenter usage configuration setting processing (described later in FIG. 9) for the configuration of target 302 (combination of datacenter 321, storage 322, and pair type 303) with the lowest service cost 505.

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

[0065] Furthermore, when "performance priority" is set as policy 801, the management server 101 causes the inter-datacenter usage configuration setting management unit 111 to execute the inter-datacenter usage configuration setting process with 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 the inter-datacenter usage configuration setting process using the inter-datacenter usage configuration setting management unit 111 with the configuration of the target 302 that satisfies the recovery time from the occurrence of a failure 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 processing 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 a source 301, a 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 a selection of inter-datacenter usage configuration setting information, which is an entry in the configuration management table 121, from the input device 203, and also accepts a start date and time.

[0068] The inter-datacenter usage configuration setting management unit 111 may accept input of the configuration of the target 302 (combination of datacenter 321, storage 322, and pair type 303) that specifies the cost calculation rule 604 as inter-datacenter usage configuration setting information. 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, 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 cases where there is only one setting operation, there is only one possible target 302 configuration (combination of datacenter 321, storage 322, and pair type 303), or there is a case where a unique target 302 configuration is determined from 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 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 complex conditions other than cost, is 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 estimation processing using conventional technology.

[0071] Next, the hybrid cloud cost prediction unit 113 executes cost estimation processing for the inter-datacenter usage configuration to be set (step S902). The cost estimation processing for the inter-datacenter usage configuration to be set (step S902) generates a cost estimation result. Details of the cost estimation processing 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 the processing procedure of the cost estimation process (step S902) for the inter-datacenter usage configuration to be set. The hybrid cloud cost prediction unit 113 acquires 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 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 a 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 determines whether or not the configuration of the target 302 (combination of the datacenter 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 (combination of data center 321, storage 322, and 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 (combination of data center 321, storage 322, and pair type 303) from the cost calculation rules 604 of the cost calculation rule table 124 (Figure 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 fee for the compute resource, the unit price for the storage capacity, the basic license fee for using functions, and free usage limit information. The usage fee information provided by the cloud vendor is stored in a table (not shown).

[0078] Next, the inter-datacenter usage 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 datacenter 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), thereby completing the cost estimation process for the to-be-set inter-datacenter usage configuration (step S902), and proceeds to step S903.

[0081] On the other hand, in step S1001, if the cost estimate request does not specify the configuration of the target 302 (step S1001: No), the inter-datacenter usage configuration setting manager 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 usage 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 determines whether or not an inter-datacenter usage configuration setting execution policy has been set (step S1012). If an inter-datacenter usage configuration setting execution policy has been 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," and 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 the targets for creating the cost estimation result.

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

[0087] On the other hand, if the inter-datacenter usage configuration setting execution policy is not 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 datacenter 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 processing procedure. The hybrid cloud cost presenting unit 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, data center 502, service 503, and service instance 504. The specification of the date 501 may be a single 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 the cost display request period.

[0089] When the hybrid cloud cost presentation 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, data center 502, service 503, service instance 504, and service fee 505 that correspond to the cost display request.

[0090] The hybrid cloud cost presenting unit 112 obtains a public cloud cost estimate using the public cloud cost obtained in step S1101 (step S1102). Specifically, for example, the public cloud cost estimate is the average value (statistical value) of the total service cost 505 per day, which is 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 presentation unit 112 determines whether or not an on-premise-public cloud usage configuration exists (step S1104). The on-premise-public cloud usage configuration is, among the configuration management information acquired in step S1102, configuration management information in which the data center 311 is on-premise and the data center 321 is a public cloud, or in which 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-to-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 rule 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 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 cost of the public cloud for the acquired cost display request target period is displayed separately (step S1112) (see FIG. 15). This on-premise cost is the cost (actual value) calculated in step S1109. Specifically, for example, if there is a setting between on-premise and a public cloud, this on-premise cost is the public cloud cost (actual value) incurred due to the amount of data transferred to the public cloud side due to that setting in response to a request to the on-premise side.

[0100] On the other hand, if an estimate display request has been made (step S1111: Yes), the hybrid cloud cost presenting unit 112 executes cost estimation processing 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 completes the hybrid cloud cost display process.

[0102] Although the above explanations have been given regarding the cost of the public cloud and the cost of the public cloud resulting from the configuration connecting on-premise and public clouds, if the on-premise environment is not a one-time device purchase environment but an environment where costs are charged based on pay-per-use charges for capacity, etc., the on-premise costs may also be displayed. The on-premise costs can be calculated based on the contract information (billing method, unit price information) between the user and the on-premise environment provider and the on-premise usage status (performance capacity history table 122).

[0103] <Cost Estimation Process for Inter-Datacenter Usage Configuration Settings (Step S1113)> 12 is a flowchart showing a detailed example of the processing procedure of the cost estimation process for setting the inter-datacenter usage configuration (step S1113). The cost estimation process for setting the inter-datacenter usage configuration (step S1113) is a process for calculating a cost estimate based on past performance and capacity history. The hybrid cloud cost presentation 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 rule 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 that will 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 presentation 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 presentation unit 112 creates an overall improvement plan using the individual improvement plans for each on-premise-public cloud usage configuration (configuration management information) (step S1207). The overall improvement plan is not an individual setting, but rather an improvement plan that can be taken in the public cloud, such as a measure that allows for a discounted price on the condition that a certain amount of resources are continuously used. At this time, by clarifying the resource usage amount resulting from the on-premise-public cloud configuration, it becomes easy to determine whether the continued use will continue in the future. For example, if synchronous remote copy is being executed, since the use will continue continuously, it is possible to apply a discount to that amount. After this, the cost estimation process for the inter-datacenter usage configuration setting (step S1113) ends, 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 steps 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 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 this time, the hybrid cloud cost presenting unit 112 extracts a cost calculation formula from the cost calculation rules 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, suppose the pair type 303 is "regular backup" and the improvement plan variable types 701 that can be applied to the extracted cost calculation formula are "backup frequency (X) change" and "backup speed (X) change." The variable (X) in the variable setting value 702 for "backup frequency (X) change" is "3 / 4," "1 / 2," and "1 / 4," while the variable (X) in the variable setting value 702 for "backup frequency (X) change" 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 presentation unit 112 creates an individual improvement plan that applies the variable (X) of the variable setting value 702 that is applicable to the extracted cost calculation formula in accordance with the constraint (for example, the 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 two 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 for which the backup speed is medium or slower and a free quota applies, the hybrid cloud cost presenting unit 112 applies "medium speed" and "slow speed" from among "low speed," "medium speed," and "high speed," which are the variable setting values ​​702 for "backup speed (X) change" in the improvement plan variable type 701. In this case, six individual improvement plans are created.

[0114] Furthermore, if there are multiple storages 322 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 multiple storages 322. Furthermore, if there are multiple devices 323 in the storage 322 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 multiple devices 323.

[0115] The hybrid cloud cost presenting unit 112 calculates the 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; 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 or 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 screen. The cost actual screen 1500 is a screen displayed in step S1112 of FIG. 11. The cost actual screen 1500 displays a graph 1501 showing the actual usage due to the inter-datacenter usage configuration setting relative to the overall cost. Note that when multiple inter-datacenter usage configuration settings exist, the costs are displayed in a list according to each inter-datacenter usage configuration setting. However, the cost of the public cloud usage attributable to the on-premise-public cloud configuration may also be displayed separately. Furthermore, a settings 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, while an example of displaying data for each datacenter connection configuration has been shown here, it is also possible to display data 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 used according to the inter-datacenter usage configuration settings (TB / h), or the portion of the data inflow that is used according to the inter-datacenter usage configuration settings (TB / month), etc. Also, while an example of displaying both actual results and estimates together has been shown, they may be presented on separate screens.

[0121] <Cost Estimate 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 showing the estimated usage portion based on the inter-datacenter usage configuration settings relative to the total cost. The black portions of the graph 1601 represent the estimate results for each usage configuration calculated in step S1204.

[0122] The details of graph 1601 correspond to the row (black circle radio button) selected by a radio button in inter-datacenter usage configuration setting improvement candidate table 1610. Each row of 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 showing the improvement plan and its post-improvement cost. The entry in the first row 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 for the entire system, such as measures that allow for discounted prices 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 continued use will continue in the future. For example, if synchronous remote copy is being performed, since use will continue continuously, that amount will be subject to a discount. One example is the "Continued Use Discount (1 Year) DC2 Storage."

[0125] The entries in the second and third lines of the improvement plan information 1602 are improvement plans and the estimated costs after the improvement plans are implemented (step S1304). The square shape on the left side of the improvement plan information 1602 is a check box 1621. When that line is selected, the check box 1621 turns black, as shown in FIG. 16, and when not selected, the check box 1621 turns white.

[0126] The round shapes on the left side 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 the improvement plan in the second row is selected, its radio button 1622 turns black, and the improvement plan in the third row can no longer be selected, so its radio button 1623 turns white.

[0127] As described above, 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 and public clouds before starting operation of the hybrid cloud configuration.

[0128] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope 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 configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added to, deleted from, or replaced with other configurations.

[0129] Furthermore, the aforementioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by having a processor interpret and execute a program that realizes each function.

[0130] Information such as programs, tables, files, etc. that realize each function can be stored in storage devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

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

[0132] 100 Hybrid Cloud Systems 101 Management Server 102 Network 111 Datacenter Configuration Management Unit 112 Hybrid Cloud Cost Presentation 113 Hybrid Cloud Cost Estimation Department 113 Hybrid Cloud Cost Presentation 121 Configuration Management Table 122 Performance Capacity History Table 123 Cost Management Table 124 Cost Calculation Rule Table 125 Improvement Suggestion 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 ​​for 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 for using the second storage area in accordance with the type of 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 the 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 characterized by executing the following.

2. The management method according to claim 1, The processor: executes a determination process to determine whether 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 of the determination process. A management method characterized by:

3. The management method according to claim 2, The processor: executes a determination process to determine whether 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 usage configuration are included in the determination process, the processor extracts a specific cost calculation formula for using the second storage area in the type of usage configuration; In the first calculation process, the processor obtains values ​​to be substituted into 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 characterized by:

4. The management method according to claim 2, The processor: executes a determination process to determine whether the second storage area and the type of the usage configuration are included in the configuration management information; In the extraction process, if the second storage area and the type of usage configuration are not included in the determination process, the processor extracts the cost calculation formulas for all combinations of the second storage area and the type of usage configuration in the cost calculation rule table; In the first calculation process, the processor obtains values ​​to be substituted for the variables in 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 characterized by:

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

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 accordance with the type of usage configuration based on at least one of the second storage area, the observed 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 characterized by:

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 the service provider devices that have provided the service in 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 cost acquired by the acquisition process. A management method characterized by:

8. The management method according to claim 1, the storage device has an improvement plan table; the improvement plan table stores the type of the usage 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 usage configuration; The processor: executes 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 characterized by:

9. The management method according to claim 8, the improvement plan table stores a type of the usage configuration, one or more improvement target variables included in the cost calculation formula corresponding to the type of the usage 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 characterized by:

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 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 ​​for 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 for using the second storage area in accordance with the type of 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 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 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 ​​for 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 for using the second storage area in accordance with the type of 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 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 uses the second storage area; an output process for outputting the cost estimation result created by the creation process; A management program characterized by causing the program to execute the above.

Images