JP2022158061A - Display method and display program - Google Patents

Abstract

To provide a display method and a display program that allow a user to determine which container should be migrated.SOLUTION: A computer executes processing of: identifying a first resource amount allocated to a program running on a first system; determining, on the basis of the first resource amount, a second resource amount to be allocated to the program in a second system; calculating, on the basis of the second resource amount, a usage fee for the second system; and displaying the calculated usage fee.SELECTED DRAWING: Figure 15

Description

This case relates to a display method and a display program.

When multiple containers are running in an on-premises system, processing may be concentrated in a specific container. As a result, the resources required for the operation of the specific container may be insufficient, and the performance of the system may be degraded. In such a case, for example, it is assumed that the target container is migrated to a system on the public cloud by scaling out to resolve the resource shortage.

However, when a container is migrated to a system on the public cloud, usage fees for using the system on the public cloud may be incurred. This usage fee is determined according to the amount of resources used by the container. For this reason, simply migrating containers to a system on the public cloud may result in a large usage fee, even if system performance degradation is suppressed.

JP 2015-152984 A U.S. Patent Application Publication No. 2016/0173411 Japanese Patent Publication No. 2020-518932 JP 2016-206952 A

According to one aspect, an object is to allow a user to determine which container to migrate.

According to one aspect, a first resource amount allocated to a program running on a first system is identified, and a second resource amount allocated to the program on a second system is determined based on the first resource amount. Then, the computer executes a process of calculating a usage fee for the second system based on the second resource amount and displaying the calculated usage fee.

According to one aspect, a user can determine which containers to migrate.

FIG. 1 is a diagram for explaining the first system and the second system. FIG. 2 is a configuration diagram of the hardware of the first system and each program executed thereon. FIG. 3 is an example of the hardware configuration of the management server. FIG. 4(a) is an example of the functional configuration of the management server. FIG. 4(b) is an example of the functional configuration of the deployment unit. FIG. 5A is a flowchart showing an example of processing executed by the first collection unit. FIG. 5B is a flowchart showing an example of processing executed by the second collection unit. FIG. 5C is a flowchart showing an example of processing executed by the third collection unit. FIG. 6 is a diagram explaining how the management server collects various kinds of information from the first system and the second system. FIG. 7 is a diagram illustrating an example of messages sent between containers according to the first embodiment. FIG. 8A is an example of tracing information according to the first embodiment. FIG. 8B is an example of traffic information according to the first embodiment. FIG. 8C is an example of container configuration information according to the first embodiment. FIG. 9 is a flowchart (part 1) showing an example of processing executed by the deployment unit according to the first embodiment; FIG. 10 is a flowchart (part 2) showing an example of processing executed by the deployment unit according to the first embodiment; FIG. 11(a) is a diagram for explaining generation of subgroups "1-1" and "1-2" in group "1" according to the first embodiment. FIG. 11(b) is a diagram for explaining generation of subgroups "2-1" and "2-2" in group "2" according to the first embodiment. FIG. 12 is a diagram for explaining a comparison between the total amount of resources and the amount of resources to be reinforced according to the first embodiment. FIG. 13(a) is an example of the first billing information. FIG. 13(b) is an example of the second billing information. FIG. 14 is a diagram explaining calculation of the total usage fee according to the first embodiment. FIG. 15 is an example of a display screen according to the first embodiment. FIG. 16A is an example of a first setting file according to the first embodiment. FIG. 16B is an example of a second setting file according to the first embodiment. FIG. 17(a) is an example of the first system and the second system before container migration. FIG. 17(b) is an example of the first system and the second system after container migration. FIG. 18 is part of a flowchart showing an example of processing executed by the deployment unit according to the second embodiment. FIG. 19 is a diagram illustrating an example of messages sent between containers according to the second embodiment. FIG. 20A is an example of tracing information according to the second embodiment. FIG. 20B is an example of traffic information according to the second embodiment. FIG. 20C is an example of container configuration information according to the second embodiment. FIG. 21 is a diagram for explaining generation of subgroups "1-1" and "1-2" in group "1" according to the second embodiment. FIG. 22 is a diagram illustrating generation of subgroups "2-1" and "2-2" in group "2" according to the second embodiment. FIG. 23 is a diagram for explaining a comparison between the total resource amount and the resource amount to be reinforced according to the second embodiment. FIG. 24 is a diagram for explaining calculation of the total usage fee according to the second embodiment. FIG. 25 is an example of a display screen according to the second embodiment. FIG. 26 is an example of a first setting file according to the second embodiment. FIG. 27 is an example of a second setting file according to the second embodiment.

Hereinafter, the form for carrying out this case will be described with reference to the drawings.

(First embodiment)
As shown in FIG. 1, the first system ST1 is arranged on the on-premise side together with the first person-in-charge terminal 110, the second person-in-charge terminal 120, the user terminal 130, and the management server 200. FIG. The first system ST1, the first person-in-charge terminal 110, the second person-in-charge terminal 120, the user terminal 130, and the management server 200 are connected to each other by the first communication network NW1. As the first communication network NW1, for example, there is a LAN (Local Area Network). The first communication network NW1 is connected to a second communication network NW2 such as the Internet.

The second system ST2 is arranged on the cloud side. For example, the second system ST2 is installed in a data center DC that provides cloud services of a public cloud. The second system ST2 is connected to various systems other than the second system ST2 installed in the data center DC via a communication line NW3 such as a LAN. This communication line NW3 is connected to the second communication network NW2. Therefore, the second system ST2 and the first system ST1 can communicate with each other through the communication line NW3, the second communication network NW2 and the first communication network NW1. The communication line NW3, the second communication network NW2, and the first communication network NW1 all include at least one of wired communication and wireless communication.

Both the first system ST1 and the second system ST2 are computer systems. A container is an example of a program that runs on the first system ST1 or the second system ST2. Both the first system ST1 and the second system ST2 provide various services (specifically, communication service, information processing service, etc.) using a plurality of containers. A user terminal 130 can access both the first system ST1 and the second system ST2. An application user who operates the user terminal 130 can use services provided by the first system ST1, for example. Both the first staff terminal 110 and the second staff terminal 120 can access the first system ST1 and the second system ST2. A person in charge of analysis who operates the first person-in-charge terminal 110 can analyze the load of the service provided by the first system ST1, for example. The second person-in-charge terminal 120 is similar to the first person-in-charge terminal 110 .

The management server 200 is a server device operated by an administrator who manages the container configuration of the first system ST1. An administrator may also be called a user of the management server 200 . The management server 200 accesses the first system ST1 and periodically collects various kinds of information managed by the first system ST1. When the management server 200 receives a specific request based on the administrator's operation, the management server 200 provides information that allows the administrator to determine the container to be migrated based on the collected information. For example, the management server 200 provides information that is useful for making decisions when migrating part of the plurality of containers operating on the first system ST1 to the second system ST2 by scale-out. Although the details will be described later, this useful information includes, for example, the usage fee of the second system ST2 and the amount of resources allocated to containers to be transferred to the second system ST2.

Details of the first system ST1 will be described with reference to FIG. Since the second system ST2 has basically the same configuration as the first system ST1, detailed description of the second system ST2 is omitted.

As shown in FIG. 2, the first system ST1 has hardware resources 11 such as a memory and a CPU (Central Processing Unit). A memory and a CPU included in the hardware resource 11 cooperate to execute an OS (Operating System) 12 , and the hardware resource 11 executes a container engine 15 on the OS 12 . The container engine 15 is a program such as DOCKER (registered trademark) for generating the container 16 . Containers 16 are housed in pods. A pod is the minimum unit for managing the containers 16 and is an aggregation of a plurality of containers 16 . Pods allow containers 16 to be managed as a group instead of being managed individually.

Although the number of containers 16 is not particularly limited, in this example, it is assumed that the container engine 15 activates a total of n containers 16, and each container is denoted by "#1", "#2", ..., "# It is identified by a character string such as "n". Also, each of the n containers 16 executes one application 17 . Each application 17 is an application program for realizing a web application, an analysis application, and the like, which will be described later.

Furthermore, in this example, the hardware resource 11 runs the container orchestration program on the OS 12 . As a result, n containers 16 are placed under the container orchestration program, and each container 16 is activated in the same container execution environment 20 . An example of a container orchestration program is Kubernetes (K8s).

A container execution environment 20 is an environment under the control of a container orchestration program. A container orchestration program gives a name to each of a plurality of containers 16, but in one container execution environment 20 there is no collision of names, and a container can be uniquely identified by its name.

Also, one container execution environment 20 can be regarded as a cluster computer formed by a plurality of containers 16 . The container orchestration program gives each container execution environment 20 a cluster ID for uniquely identifying different container execution environments 20 .

A hardware configuration of the management server 200 will be described with reference to FIG. As shown in FIG. 3, the management server 200 includes a controller 210 that implements the display method. The control device 210 includes a CPU 210A, a RAM (Random Access Memory) 210B and a ROM (Read Only Memory) 210C. The control device 210 includes a network I/F (interface) 210D and a HDD (Hard Disk Drive) 210E. An SSD (Solid State Drive) may be employed instead of the HDD (Hard Disk Drive) 210E.

The control device 210 may include at least one of an input I/F 210F, an output I/F 210G, an input/output I/F 210H, and a drive device 210I, as required. The CPU 210A to the drive device 210I are interconnected by an internal bus 210J. That is, the controller 210 can be implemented by a computer.

An input device 710 is connected to the input I/F 210F. The input device 710 includes, for example, a keyboard, a mouse, and a touch panel. Input device 710 may be included in management server 200 . A display device 720 is connected to the output I/F 210G. The display device 720 is, for example, a liquid crystal display. A display device 720 may be included in the management server 200 . A semiconductor memory 730 is connected to the input/output I/F 210H. Examples of the semiconductor memory 730 include USB (Universal Serial Bus) memory and flash memory. The input/output I/F 210H reads the display program stored in the semiconductor memory 730 . The input I/F 210F and the input/output I/F 210H are provided with USB ports, for example. The output I/F 210G has, for example, a display port.

A portable recording medium 740 is inserted into the drive device 210I. Examples of the portable recording medium 740 include removable discs such as CD (Compact Disc)-ROM and DVD (Digital Versatile Disc). The drive device 210I reads the display program recorded on the portable recording medium 740 . The network I/F 210D has, for example, a LAN port and a communication circuit.

A display program stored in at least one of ROM 210C, HDD 210E, and semiconductor memory 730 is temporarily stored in RAM 210B by CPU 210A. The display program recorded on the portable recording medium 740 is temporarily stored in the RAM 210B by the CPU 210A. As the CPU 210A executes the stored display program, the CPU 210A implements various functions described later and also executes various processes described later. Note that the display program may correspond to a flow chart described later.

The functional configuration of the control device 210 will be described with reference to FIGS. 4(a) and 4(b). Note that FIG. 4A shows the essential functions of the control device 210 .

As shown in FIG. 4( a ), the control device 210 includes a storage section 211 , a processing section 212 , an input section 213 , an output section 214 and a communication section 215 . The storage unit 211 can be implemented by the above-described RAM 210B, HDD 210E, or the like. The processing unit 212 can be implemented by the CPU 210A described above. The input unit 213 can be realized by the input I/F 210F described above. The output unit 214 can be implemented by the output I/F 210G described above. The communication unit 215 can be implemented by the network I/F 210D described above. Therefore, the storage unit 211, the processing unit 212, the input unit 213, the output unit 214, and the communication unit 215 are connected to each other.

The storage unit 211 includes a tracing DB (Database) 221 , a traffic DB 222 and a container configuration DB 223 . The processing unit 212 includes a first collection unit 231 , a second collection unit 232 , a third collection unit 233 and a deployment unit 234 . The first collection unit 231 collects tracing information managed by the first system ST1. The first collection unit 231 registers the collected tracing information in the tracing DB 221 . Thereby, the tracing DB 221 stores the tracing information. The second collection unit 232 collects performance information (metrics information) managed by the first system ST1. The second collection unit 232 registers the collected performance information in the traffic DB 222 as traffic information. Thereby, the communication amount DB 222 stores the communication amount information. The third collection unit 233 collects container configuration information managed by the first system ST1. The third collection unit 233 registers the collected container configuration information in the container configuration DB 223 . Thereby, the container configuration DB 223 stores the container configuration information. Details of the tracing information, traffic information, and container configuration information will be described later.

The deployment unit 234 includes a first identification unit 241, a second identification unit 242, and a determination unit 243, as shown in FIG. 4(b). The deployment section 234 also includes a first calculation section 244 , a second calculation section 245 , a display section 246 and a selection section 247 . The first identifying unit 241, . For example, the first identifying unit 241 accesses the container configuration DB 223 and acquires container configuration information. Then, the first identifying unit 241 identifies the first resource amount allocated to each of the plurality of containers operating in the first system ST1 based on the acquired container configuration information. Details of other components will be described later.

Next, the operation of control device 210 will be described.

First, the operation of the first collection unit 231 will be described. As shown in FIGS. 5A and 6, the first collection unit 231 collects tracing information managed by the container execution environments 20 of the first system ST1 and the second system ST2 (step S1). For example, as shown in FIG. 7, the first system ST1 according to the first embodiment has a plurality of containers 16 such as analysis applications, web applications, and data processing. In this case, the container execution environment 20 manages the flow (processing flow) of messages (communication messages) between the plurality of containers 16 as tracing information for each message ID. Each container 16 has a distributed tracing program 16a installed. The distributed tracing program 16a assigns message IDs and manages information such as the flow and volume of messages between the containers 16, access frequency, and the like. The container execution environment 20 acquires this information managed by the distributed tracing program 16a and manages it as tracing information. The first collection unit 231 accesses the container execution environment 20 of the first system ST1 and collects tracing information from the container execution environment 20 .

After collecting the tracing information, the first collecting unit 231 registers the tracing information in the tracing DB 221 (step S2). As a result, the tracing DB 221 stores tracing information including message IDs and processing flows, as shown in FIG. 8A, for example. The processing flow can specify the direction of messages between multiple containers 16, and the like.

Next, the operation of the second collection unit 232 will be described. As shown in FIGS. 5B and 6, the second collection unit 232 collects performance information managed by the container execution environments 20 of the first system ST1 and the second system ST2 (step S3). As described above, the distributed tracing program 16a manages information such as the flow rate of messages and the frequency of access to each container 16. FIG. The container execution environment 20 acquires the information and manages it as performance information. The second collection unit 232 accesses the container execution environment 20 of the first system ST1 and collects performance information from the container execution environment 20 .

After collecting the performance information, the second collection unit 232 registers the performance information in the traffic DB 222 (step S4). As a result, as shown in FIG. 8B, for example, the communication volume DB 222 stores communication charge information that can be uniquely identified by a combination of a source container, a destination container, and an API (Application Programming Interface). From the communication fee information, it is possible to specify the message flow rate and access frequency in the above combination. Note that the API can be defined by a URI (Uniform Resource Identifier).

Next, the operation of the third collection unit 233 will be described. As shown in FIGS. 5C and 6, the third collection unit 233 collects container configuration information managed by the container execution environments 20 of the first system ST1 and the second system ST2 (step S5). The distributed tracing program 16a can also manage the amount of first resources such as the number of CPUs and the amount of memory assigned to each container 16 . The container execution environment 20 acquires the first resource amount and manages it as container configuration information. The third collection unit 233 accesses the container execution environment 20 of the first system ST1 and collects container configuration information from the container execution environment 20 .

After collecting the container configuration information, the third collection unit 233 registers the container configuration information in the container configuration DB 223 (step S6). As a result, the container configuration DB 223 stores container configuration information including the container name, the number of CPUs, and the amount of memory, as shown in FIG. 8C, for example. The container configuration information can specify the first resource amount allocated to each of the plurality of containers 16 .

Next, operation of the deployment unit 234 will be described. As shown in FIG. 9, first, the first identifying unit 241 receives a resource enhancement request (step S11). For example, the number of application users who use the web application (see FIG. 7) increases, and the performance of the first system ST1 may be degraded due to insufficient resources in the processing of the web application. In such a case, an administrator who operates the management server 200 inputs a resource enhancement request to the input device 710 . The input device 710 transmits the input resource enhancement request to the first specifying unit 241 . Thereby, the first identifying unit 241 receives the resource enhancement request.

Upon receiving the resource enhancement request, the first identifying unit 241 refers to the tracing DB 221 and determines whether or not all tracing information has been searched (step S12). As shown in FIG. 8A, the tracing DB 221 stores a plurality of pieces of tracing information identified by message IDs. determine whether If all the tracing information has not been searched (step S12: NO), the first specifying unit 241 designates one piece of unsearched tracing information as a processing target. Then, the first identifying unit 241 creates an empty group for grouping the containers 16 by assigning an identification number (step S13). After generating the group, the first specifying unit 241 refers to the processing flow of the tracing information specified as the processing target, and determines whether or not all containers included in the processing flow have been extracted (step S14).

If the extraction of all containers has not been completed (step S14: NO), the first identifying unit 241 extracts the container 16 (step S15) and determines whether or not it has been registered in the group (step S16). In particular, the first identification unit 241 refers to the traffic DB 222 when extracting the container 16 . Then, the first identifying unit 241 extracts the container 16 when the access frequency of the traffic information according to the processing flow of the tracing information is equal to or higher than a predetermined value indicating frequent access. For example, as shown in FIG. 8(a), it is assumed that tracing information with message ID "0" is designated as a processing target. In this case, as shown in FIG. 8B, the access frequency of the traffic information according to the processing flow of this tracing information is 100 requests/30 minutes. In this embodiment, this access frequency corresponds to a predetermined value or more representing frequency. Therefore, the first identifying unit 241 extracts the analysis application as the container 16 and determines whether it has been registered in the group. In addition, in the process of step S15, the first specifying unit 241 stops extracting the container 16 if the access frequency is less than a predetermined value. In this way, containers 16 whose access frequency is less than a predetermined value are assumed to be less affected by communication delays, and are therefore excluded from group registration targets, which will be described later.

If the container has not been registered in the group (step S16: NO), the first specifying unit 241 registers the container 16 in the group (step S17). As a result, as shown in FIG. 7, the analysis application container 16 is registered in the group "1".

When the container 16 is registered in the group, the first specifying unit 241 determines whether or not the container 16 is present in another message ID (step S18). If the container 16 exists in another message ID (step S18: YES), the first identification unit 241 extracts another container 16 included in the other message ID (step S19). In particular, the first identification unit 241 refers to the traffic volume DB 222 when extracting another container 16, and if the access frequency of the traffic volume information according to the processing flow of the tracing information is equal to or higher than a predetermined value indicating frequent access. , another container 16 is extracted.

For example, as shown in FIG. 8A, the analysis application is also present in message ID "1" in addition to message ID "0". Message ID "1" contains another container 16 representing data manipulation. However, as shown in FIG. 8B, the access frequency of the traffic information according to the processing flow of the tracing information of the message ID "1" is 1 request/1 day. In this embodiment, this access frequency corresponds to less than the predetermined value. Therefore, the first identifying unit 241 stops extracting another container 16 . That is, it is excluded from the extraction target of another container 16 . In this way, when the access frequency is less than the predetermined value, extraction of another container 16 is stopped, so the process returns to step S14. If the container 16 has already been registered in the group (step S16: YES), or if there is no container 16 in another message ID (step S18: NO), the process returns to step S14.

In the processing of step S14, there is one container 16 representing the analysis application in the processing flow in the tracing information with message ID "0". Therefore, the first specifying unit 241 determines that extraction of all containers has been completed (step S14: YES), and returns to the process of step S12. In the process of step S12, the tracing information of the message ID "1" has not yet been designated as a processing target. Therefore, the first identifying unit 241 determines that all tracing information has not been searched, and repeats the processing from steps S13 to S19. As a result, group "2" is also generated as shown in FIG.

In the process of step S12, if all tracing information has been searched (step S12: YES), the first specifying unit 241 determines whether or not all groups have been searched for the subsequent process (step S20). . If all groups have not been searched (step S20: NO), the first identifying unit 241 designates one of the unsearched groups as a processing target, and then calculates the first resource amount of the container 16 belonging to the processing target group. is specified (step S21). As shown in FIG. 7, when group "1" is designated as a processing target, the first identifying unit 241 identifies the first resource amount of the container 16 of the analysis application. As shown in FIG. 8C, the container configuration DB 223 stores container configuration information. Therefore, the first identifying unit 241 can identify the amount of CPU "8" and the amount of memory "24 GB" allocated to the container 16 of the analysis application as the first resource amount.

After specifying the first resource amount, the determining unit 243 then determines candidates for the second resource amount (step S22). More specifically, the determination unit 243 determines a plurality of candidates for the second resource amount to be allocated to the container 16 after shifting to the second system ST2 based on the first resource amount. For example, as shown in FIG. 11A, the container 16 of the analysis application is assigned a first resource amount of "8" for the CPU and "24 GB" for the memory. The determination unit 243 determines candidates for the second resource amount obtained by dividing the first resource amount based on a predetermined equal division condition. In this embodiment, the equal splitting condition is splitting into two. Therefore, as shown in FIG. 11(a), the determination unit 243 determines the first candidate for the second resource amount, which is the amount of CPU of "4" and the amount of memory of "12 GB". Further, the determination unit 243 determines the second candidate for the second resource amount, which is the amount of CPU "4" and the amount of memory "12 GB". For group "1", a plurality of candidates for the second resource amount to be allocated to the container 16 after shifting to the second system ST2 are thus determined. The first candidate belongs to subgroup "1-1" and the second candidate belongs to subgroup "1-2". Note that the equal division condition may be equal to or greater than three divisions. When the process of step S22 is completed, the process returns to step S20.

Since group "2" is not specified as a processing target, group "2" is specified as a processing target and similar processing is executed. As a result, as shown in FIG. 11(b), the determination unit 243 determines the third candidate for the second resource amount with the CPU amount of "2" and the memory amount of "6 GB". Further, the determination unit 243 determines the fourth candidate for the second resource amount, which is the amount of CPU "2" and the amount of memory "6 GB". For group "2", a plurality of candidates for the second resource amount to be allocated to the container 16 after shifting to the second system ST2 are thus determined. The third candidate belongs to subgroup "2-1" and the fourth candidate belongs to subgroup "2-2". This completes the search for all groups (step S20: YES). Thereafter, as shown in FIG. 10, the determining unit 243 determines whether or not all subgroups have been searched for subsequent processing (step S23). If all subgroups have not been searched (step S23: NO), the determination unit 243 designates one of the unsearched subgroups as a processing target. Then, the determining unit 243 calculates the total resource amount of all containers 16 belonging to the subgroup to be processed (step S24).

For example, assume that the subgroup "1-1" is designated as the processing target. In this case, as shown in FIGS. 11A and 11B, there is one container 16 belonging to the subgroup "1-1". Therefore, for the subgroup "1-1", the total resource amount is "4" for the CPU and "12 GB" for the memory, as shown in the upper part of FIG.

After calculating the total resource amount, the determining unit 243 determines whether or not the total resource amount is equal to or greater than the resource amount of the container 16 to be reinforced (step S25). The decision unit 243 may skip the processing of step 25 . In the present embodiment, as described above, the number of application users using web applications has increased, and the performance of the first system ST1 has been degraded due to insufficient resources in the processing of the web applications. Therefore, as shown in the right corner of FIG. 12, the web application corresponds to the container 16 to be reinforced. The resource amount of the container 16 to be reinforced is equal to or greater than a predetermined threshold. In the process of step S<b>25 , the determination unit 243 determines whether both the amount of CPUs and the amount of memory in the total resource amount are equal to or greater than the number of CPUs and the amount of memory in the resource amount of the container 16 to be reinforced. As shown in FIG. 12, comparing the total resource amount of the subgroup "1-1" and the resource amount of the reinforcement target container 16, the total resource amount and the resource amount of the reinforcement target container 16 are the same. Therefore, the determination unit 243 determines that the total resource amount is equal to or greater than the resource amount of the container 16 to be reinforced (step S25: YES).

In this case, the determination unit 243 determines the resource type (step S26), and the first calculation unit 244 calculates the usage fee for the second system ST2 based on the determined resource type (step S27). The usage fee corresponds to the resource cost for using the hardware resources of the second system ST2. For example, as shown in FIG. 13A, the determination unit 243 refers to the first billing information managed inside or outside the management server 200 and determines the resource type corresponding to the total resource amount. For the subgroup "1-1", the resource type "medium" is determined because the total resource amount is the number of CPUs "4" and the amount of memory "12 GB". After determining the resource type, the first calculator 244 calculates the monthly usage fee based on the determined resource type. For the subgroup "1-1", as shown in the lower part of FIG. By multiplying the number of days, the monthly usage fee can be calculated.

After calculating the usage fee, the second calculator 245 calculates the communication fee (step S28). You may skip the process of step S28. The communication fee corresponds to the communication cost of communication from the second system ST2 to the first system ST1. Communication from the first system ST1 to the second system ST2 is often free of charge. On the other hand, communication from the second system ST2 to the first system ST1 is often charged. For this reason, the communication charge can be calculated with high accuracy by using the communication from the second system ST2 to the first system ST1 as the object of calculation of the communication charge.

For example, as shown in FIG. 13B, the second calculator 245 refers to the second billing information managed inside or outside the management server 200 and determines the communication unit price corresponding to the communication volume. As shown in the upper part of FIG. 14, if the communication amount of the container 16 belonging to the subgroup "1-1" is "7 GB", the communication unit price "$0.114/GB" corresponding to the communication amount of "7 GB" is determined. do. Then, as shown in the lower part of FIG. 14 , the second calculation unit 245 calculates the communication amount “6 GB” by subtracting the free communication amount “1 GB” from the communication amount “7 GB” from the communication unit price “$0.114/GB”. ” can be used to calculate the monthly communication fee.

After calculating the communication fee, the first calculator 244 calculates the total usage fee (step S29). Specifically, as shown in the lower part of FIG. 14, the total usage fee is calculated by adding the communication fee to the usage fee. As a result, the total usage fee is specified when the container 16 belonging to the subgroup "1-1" is transferred to the second system ST2. When the process of step S29 is completed, the process returns to step S23. If the total resource amount is less than the resource amount of the container 16 to be reinforced (step S25: NO), similarly, the process returns to step S23. The processing of steps S24 to S29 is repeated until all subgroups are searched. As a result, the total charge for each of the containers 16 belonging to the subgroups "1-2", . It should be noted that if the process of step S28 is skipped, the total usage fee will be the same amount as the usage fee.

When all subgroups have been searched (step S23: YES), the display unit 246 displays the total charge (step S30). More specifically, the display unit 246 displays the resource amount and total usage fee for each API on the display device 720 . Thereby, as shown in FIG. 15, a plurality of candidates for the container 16 to be transferred to the second system ST2 appear on the display device 720. FIG. Destination candidate 1 corresponds to subgroup "1-1", and destination candidate 4 corresponds to subgroup "2-2". Destination candidates 2 and 3 corresponding to subgroups "1-2" and "2-1" are omitted. If the process of step S25 is skipped, four destination candidates 1 to 4 appear. On the other hand, when the process of step S25 is executed, the migration destination candidate 3 and the migration destination candidate 4 (see FIG. 12) whose total resource amount is less than the resource amount of the container 16 to be reinforced do not appear. Two destination candidates 1 and 2 appear. When the display unit 246 displays the total charge, the selection unit 247 waits until one of the migration destination candidates 1 to 4 (or either of the migration destination candidates 1 and 2) is selected ( Step S31: NO).

The administrator can operate the input device 710 to specify the migration destination candidate 1 corresponding to the subgroup "1-1" with the lowest total usage fee, for example. When the migration destination candidate 1 is specified, the selection unit 247 selects the migration destination candidate 1, migrates the selected migration destination candidate 1 to the second system ST2 (step S32), and ends the process. Specifically, the selection unit 247 generates a first setting file F1 for the first system ST1 as shown in FIG. to generate a second setting file F2. Then, as shown in FIG. 17A, the selection unit 247 notifies the first setting file F1 to the container execution environment 20 of the first system ST1, and transfers the second setting file F2 to the container execution environment of the second system ST2. 20.

As a result, as shown in FIG. 17B, the container 16 of the migration destination candidate 1 corresponding to the subgroup "1-1" migrates to the second system ST2, and the migration corresponding to the subgroup "1-2" The container 16 of the destination candidate 2 remains in the first system ST1. In this way, even if the container 16 representing the Web application is added to the first system ST1, resource shortage does not occur, and the performance of the first system ST1 is reinforced. Also, by designating the subgroup with the lowest total usage fee, the total usage fee for the second system ST2 can be kept low. Some of the persons in charge of analysis use the second system ST2 to perform various kinds of analysis work.

In the above-described embodiment, the administrator designates the migration destination candidate 1 corresponding to the subgroup "1-1" with the lowest total usage fee, but the selector 247 selects the subgroup "1-1" with the lowest total usage fee. -1”, the migration destination candidate 1 may be dynamically selected. In this case, the processing of steps S30 and S31 may be omitted. As a result, the operational burden on the administrator can be reduced.

(Second embodiment)
Next, a second embodiment of the present case will be described with reference to FIGS. 18 to 27. FIG. In FIG. 18, steps S20 to S22, which are the same processes as in FIG. 9 according to the first embodiment, are denoted by the same reference numerals and indicated by dashed lines, and detailed description thereof will be omitted.

First, as shown in FIG. 18, when the first identifying unit 241 identifies the first resource amount in the process of step S21, the first identifying unit 241 extracts the API to be processed (step S31). The first system ST1 according to the second embodiment includes seven containers 16, as shown in FIG. By the processing of steps S13 to S19 in the first embodiment, a group "1" including three containers 16 such as a GUI (Graphical User Interface) for analysis is generated from the seven containers 16. FIG. A group "2" including three containers 16 such as Web applications (front side) is also generated by the processing of steps S13 to S19. The data processing container 16 has a low access frequency and is excluded from group generation targets. Thus, both group "1" and group "2" contain multiple containers 16, unlike the first embodiment.

When group "1" is designated as a processing target, the first identifying unit 241 identifies the first resource amount of each container 16 of the analysis GUI, analysis engine, and application log DB. As shown in FIG. 20(c), the container configuration DB 223 stores container configuration information. Therefore, the first identifying unit 241 can identify the amount of CPU "3" and the amount of memory "9 GB" allocated to the container 16 of the GUI for analysis as the first resource amount. Similarly, the first identifying unit 241 can identify the amount of CPU "9" and the amount of memory "9 GB" allocated to the container 16 of the analysis engine as the first resource amount. The first identifying unit 241 can identify the CPU amount “8” and the memory amount “16 GB” allocated to the container 16 of the application log DB as the first resource amount.

After specifying the first resource amount in this way, the first specifying unit 241 extracts the API to be processed. For example, assume that group "1" is specified as a processing target. In this case, as shown in FIG. 19, the first specifying unit 241 performs API "bnsk.../fr" and API "bnsk.../bk" for three containers 16 belonging to group "1" (see FIG. 20(b)). to extract Note that the first identification unit 241 refers to the traffic DB 222 and compares the traffic information that does not include the container 16 representing the data processing excluded from the extraction target with the container 16 such as the GUI for analysis, thereby identifying the API. can be extracted.

After extracting the API to be processed, the first specifying unit 241 determines whether or not there are two or more APIs (step S32). In this embodiment, two APIs are extracted and defined by different URIs, so there are two types. Therefore, the first identifying unit 241 determines that there are two or more types of APIs (step S32: YES). In this case, the first identifying unit 241 determines whether all the containers 16 belonging to the group "1" designated as the processing target have been searched (step S33). If all the containers 16 have not been searched (step S33: NO), the second specifying unit 242 repeats the processes of steps S34 to S36 until all the containers 16 have been searched.

First, the second identifying unit 242 refers to the traffic DB 222 to identify traffic for each API when accessing the container 16 (step S34). Note that the second identifying unit 242 can identify the traffic based on the numerical value of the flow rate registered in the flow rate of the traffic information stored in the traffic DB 222 .

For example, as shown in FIG. 21, the second specifying unit 242 calculates the sum of the first flow rate and the second flow rate of messages per unit time of the front API for the container 16 of the GUI for analysis. As a result, assume that the sender has a total flow rate of '5 GB' and the receiver side has a total flow rate of '15 GB'. In this case, the second identifying unit 242 identifies the traffic volume of "20 GB". Similarly, the second identifying unit 242 calculates the sum of the first message flow rate and the second message flow rate per unit time of the back API. As a result, assume that the sender has a total flow rate of '5 GB' and the receiver side has a total flow rate of '5 GB'. In this case, the second identifying unit 242 identifies the traffic volume of "20 GB".

Also, the second identifying unit 242 calculates the sum of the second flow rate and the third flow rate of messages per unit time of the front API for the container 16 of the analysis engine. As a result, assume that the sender has a total flow of "10 GB" and the receiver has a total flow of "60 GB". In this case, the second identifying unit 242 identifies the communication volume of "70 GB". Similarly, the second identifying unit 242 calculates the sum of the second flow rate and the third flow rate of messages per unit time of the back API. As a result, assume that the sender has a total flow rate of '5 GB' and the receiver side has a total flow rate of '30 GB'. In this case, the second identifying unit 242 identifies the communication volume of "35 GB".

After identifying the traffic, the second identifying unit 242 refers to the traffic DB 222 to identify the data amount for each data type in the database that stores the log output by the data processing container 16 (step S35). In addition, the second specifying unit 242 can specify the data amount based on the numerical value of the data amount registered in the flow rate of the communication amount information stored in the communication amount DB 222 .

For example, as shown in FIG. 21, if the data amount of the log related to the front in the application log DB is "300 GB", the second identifying unit 242 identifies the data amount "300 GB" of the front. If the data amount of the log related to the background in the application log DB is the data amount "100 GB", the second identifying unit 242 identifies the data amount "100 GB" of the background. These logs are processed by the container 16 for data processing. The data processing container 16 processes logs output from the web application (front side) container 16 and the web application (back side) container 16 and accumulated in the storage container 16 .

After specifying the data amount, the second specifying unit 242 calculates the communication amount ratio and the data amount ratio (step S36). As shown in FIG. 21, for the container 16 of the GUI for analysis, the amount of communication on the front side is "20 GB" and the amount of communication on the back side is "10 GB". Therefore, the second identifying unit 242 calculates the communication traffic ratio “2:1”. In the case of the container 16 of the analysis engine, the amount of communication on the front side is "70 GB" and the amount of communication on the back side is "35 GB". Therefore, the second identifying unit 242 calculates the communication traffic ratio “2:1”. In the case of the container 16 of the application log DB, the data amount on the front side is "300 GB" and the data amount on the back side is "100 GB". Therefore, the second specifying unit 242 calculates the data amount ratio “3:1”.

When all the containers 16 have been searched (step S33: YES), the determination unit 243 executes the process of step S22. In this case, the determining unit 243 determines candidates so that the ratio between the second resource amounts of each of the plurality of candidates for the second resource amount becomes the ratio between the plurality of communication amounts. For example, as shown in FIG. 21, for the container 16 of the GUI for analysis, a traffic ratio of "2:1" is calculated. Therefore, the determining unit 243 determines candidates for the second resource amount obtained by dividing the first resource amount of the CPU amount "3" and the memory amount "9 GB" used by the container 16 at a ratio "2:1". As a result, the determination unit 243 determines the first candidate for the second resource amount, which is the amount of CPU "2" and the amount of memory "6 GB". Further, the determination unit 243 determines the second candidate for the second resource amount, which is the amount of CPU "1" and the amount of memory "3 GB". Note that the container 16 of the analysis engine is the same as the container 16 of the GUI for analysis, so the explanation is omitted.

On the other hand, for the container 16 of the application log DB, a data amount ratio of "3:1" is calculated. Therefore, the determination unit 243 determines candidates so that the ratio of the second resource amounts of each of the plurality of candidates for the second resource amount is the ratio of the plurality of data amounts. Therefore, the determination unit 243 selects candidates for the second resource amount obtained by dividing the first resource amount of the CPU amount "8" and the memory amount "16 GB" used by the container 16 of the application log DB at a ratio "3:1". decide. As a result, the determining unit 243 determines the first candidate for the second resource amount, which is the amount of CPU of "6" and the amount of memory of "12 GB". Further, the determination unit 243 determines the second candidate for the second resource amount, which is the amount of CPU "2" and the amount of memory "4 GB". For group "1", a plurality of candidates for the second resource amount to be allocated to the container 16 after shifting to the second system ST2 are determined as described above. The three first candidates belong to the subgroup "1-1", and the three second candidates belong to the subgroup "1-2".

When the process of step S22 is completed, the process returns to step S20. As a result, group "2" is designated as a processing target, and the same processing is repeated. Here, when the group "2" is specified as a processing target and the first specifying unit 241 determines whether or not there are two or more APIs in the process of step S32, as shown in FIG. In , two APIs are extracted. However, since these two APIs are defined by the same URI, they are one type. Therefore, the first identifying unit 241 determines that the number of APIs is not two or more (step S32: NO). In this case, the determination unit 243 executes the process of step S22. In particular, when there is one type of API, similarly to the first embodiment, the determining unit 243 determines second resource amount candidates obtained by dividing the first resource amount based on a predetermined equal division condition.

In this embodiment, the equal splitting condition is splitting into two. For this reason, in the case of the container 16 of the Web application (front side), as shown in FIG. 22, the determination unit 243 determines the first candidate for the second resource amount of the CPU amount "6" and the memory amount "8 GB". do. Further, the determination unit 243 determines the second candidate for the second resource amount, which is the amount of CPU "6" and the amount of memory "8 GB". Since the container 16 of the web application (back side) is the same as the container 16 of the web application (front side), description thereof is omitted. On the other hand, in the case of the storage container 16, the determination unit 243 determines the first candidate for the second resource amount, which is the amount of CPU "2" and the amount of memory "8 GB". Further, the determination unit 243 determines the second candidate for the second resource amount, which is the amount of CPU "2" and the amount of memory "8 GB". For group "2", a plurality of candidates for the second resource amount to be allocated to the container 16 after shifting to the second system ST2 are determined as described above. The above first candidate belongs to the subgroup "2-1", and the second candidate belongs to the subgroup "2-2". When the processing for group "2" ends, the process returns to step S20. In the present embodiment, since all of the two groups "1" and "2" have been searched, the processing after step S23 explained in the first embodiment proceeds.

Here, it is assumed that, for example, the number of application users who use the web application (front side) increases, and the performance of the first system ST1 deteriorates due to resource shortage in the processing of the web application (back side). In this case, as shown in the right corner of FIG. 23, the web application (back side) corresponds to the container 16 to be reinforced. Therefore, in the process of step S25, the determination unit 243 determines whether or not all the total resource amounts are greater than or equal to the resource amount of the container 16 to be reinforced. More specifically, the determination unit 243 determines whether both the amount of CPUs and the amount of memory in the total resource amount are equal to or greater than the number of CPUs and the amount of memory in the resource amount of the container 16 to be reinforced. As shown in FIG. 23, comparing the total resource amount of the subgroup "1-1" with the resource amount of the container 16 to be reinforced, these total resource amounts are greater than or equal to the resource amount of the container 16 to be reinforced. Subgroups "2-1" and "2-2" are similar to subgroup "1-1". On the other hand, comparing the total resource amount of the subgroup "1-2" with the resource amount of the container 16 to be reinforced, the total resource amount is less than the resource amount of the container 16 to be reinforced. Therefore, the plurality of containers 16 belonging to the subgroup "1-2" are not desirable as targets for migration to the second system ST2, and may be excluded from migration targets at this point.

Thereafter, in the processing of steps S26 to S28, the determination unit 243 determines the resource type, the first calculation unit 244 calculates the usage fee for the second system ST2 based on the determined resource type, and the second calculation unit 245 Calculate communication charges. If the subgroup is "1-1", the determination unit 243 determines the resource type "extra-large" (see FIG. 13(a)) defined in the first billing information. Then, as shown in the lower part of FIG. 24, the first calculator 244 identifies the resource charge unit price "$0.992/hour" corresponding to the resource type "extra-large". The first calculation unit 244 can calculate the monthly usage fee by multiplying the identified resource unit price “$0.992/hour” by the number of hours per day and the number of days per month. Also, if the container 16 belonging to the subgroup “1-1” has a communication volume of “7 GB”, the second calculator 245 specifies a communication unit price corresponding to this communication volume. Specifically, the second calculator 245 identifies the communication unit price "$0.114/GB" corresponding to the communication amount "7 GB" defined in the second billing information (see FIG. 13(b)). Then, as shown in the lower part of FIG. 24, the second calculation unit 245 can calculate the monthly communication charge by multiplying the communication unit price of "$0.114/GB" by the communication volume of "6 GB". Accordingly, in the process of step S29, the first calculator 244 calculates the total usage fee. The same is true for subgroups "1-2", "2-1" and "2-2". The amount of communication "6 GB" is the amount obtained by subtracting the free amount of communication "1 GB" from the amount of communication "7 GB".

When the total usage fee is calculated, the display unit 246 displays the resource amount and the total usage fee for each API on the display device 720 in the process of step S30. As a result, as shown in FIG. 25, a plurality of candidates for the container 16 to be transferred to the second system ST2 appear on the display device 720. FIG. Destination candidate 1 corresponds to subgroup "1-1", and destination candidate 4 corresponds to subgroup "2-2". Destination candidates 2 and 3 corresponding to subgroups "1-2" and "2-1" are omitted. If the process of step S25 is skipped, four destination candidates 1 to 4 appear. On the other hand, when the process of step S25 is executed, the migration destination candidate 2 (see FIG. 23) whose total resource amount is less than the resource amount of the container 16 to be reinforced does not appear, and the three migration destination candidates 1 , a migration destination candidate 3 and a migration destination candidate 4 appear.

When the total usage charge is displayed, the selection unit 247 continues until any one of the migration destination candidates 1 to 4 (or any of the migration destination candidates 1, 3, and 4) is selected. stand by. For example, when the administrator designates the migration destination candidate 1 corresponding to the subgroup "1-1" with the lowest total usage fee, the selection unit 247 selects the migration destination candidate 1 and places the selected migration destination candidate 1 as the second candidate. Move to system ST2 and end the process.

Specifically, the selection unit 247 generates a first setting file F1 for the first system ST1 as shown in FIG. 26, and a second setting file F2 for the second system as shown in FIG. to generate Then, the selection unit 247 notifies the first setting file F1 to the container execution environment 20 of the first system ST1, and notifies the second setting file F2 to the container execution environment 20 of the second system ST2. As a result, although not shown, the container 16 of the migration destination candidate 1 corresponding to the subgroup "1-1" is migrated to the second system ST2, and the container 16 of the migration destination candidate 2 corresponding to the subgroup "1-2" is transferred to the second system ST2. remains in the first system ST1.

In this way, even if the container 16 representing the Web application (back side) is added to the first system ST1, resource shortage does not occur and the performance of the first system ST1 is reinforced. Also, by designating the subgroup with the lowest total usage fee, the total usage fee for the second system ST2 can be kept low. Some of the persons in charge of analysis use the second system ST2 to perform various kinds of analysis work.

As in the first embodiment, the selection unit 247 may dynamically select the migration destination candidate 1 corresponding to the subgroup "1-1" with the lowest total usage fee. In this case, the processing of steps S30 and S31 may be omitted. As a result, the operational burden on the administrator can be reduced.

Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to the specific embodiments, and various modifications can be made within the spirit and scope of the present invention described in the claims.・Changes are possible. For example, in the above-described embodiment, the container 16 is described as an example of a program, but a virtual machine may be used as the program.

Further, in the above-described embodiment, the migration from the first system ST1 on the on-premise side to the second system ST2 on the public cloud side has been described as an example. It may be transition to the second system ST2.

200 management server 210 control device 212 processing unit 234 deployment unit 241 first identification unit 243 determination unit 244 first calculation unit 246 display unit ST1 first system ST2 second system

Claims (11)

identifying a first amount of resources allocated to programs running on the first system;
determining a second amount of resources to allocate to the program in a second system based on the first amount of resources;
calculating a usage fee for the second system based on the second resource amount;
displaying the calculated usage fee;
A display method characterized in that processing is executed by a computer. further comprising a process of specifying a traffic volume for each API (application programming interface) when accessing the program;
2. The display method according to claim 1, wherein in the process of determining the second resource amount, the second resource amount is determined so that the ratio of the second resource amount becomes the ratio of the communication traffic. . 3. The display method according to claim 1, wherein the second resource amount is greater than or equal to the first resource amount of the program. 4. The display method according to claim 3, wherein said first resource amount of said program in said first system is equal to or greater than a predetermined threshold. a process of selecting the program of the second resource amount with the lowest usage fee from the second resource amount equal to or greater than the first resource amount as a transfer target from the first system to the second system; 5. A display method according to claim 3 or 4, further comprising: further comprising a process of specifying the amount of data for each data type in a database that stores logs output by the program;
2. The display method according to claim 1, wherein in the process of determining the second resource amount, the second resource amount is determined so that the ratio of the second resource amount becomes the ratio of the data amount. . In the process of determining the second resource amount, when APIs (Application Programming Interfaces) for accessing the program are of the same type, the second resource amount is adjusted so that the ratio of the second resource amount is uniform. 2. The display method according to claim 1, characterized in that it determines . further comprising a process of generating a group of the programs, and a process of registering the programs in the group based on the inter-program communication relationship of the programs;
8. The display method according to any one of claims 1 to 7, wherein in the process of determining the second resource amount, the second resource amount is determined for each of the groups. 9. The display method according to claim 8, wherein, in the process of registering the group, the program whose communication frequency of the inter-program communication is lower than a predetermined threshold frequency is excluded from the registration target of the group. further comprising a process of calculating a communication fee for communication from the second system to the first system;
10. The display method according to any one of claims 1 to 9, wherein in the process of calculating the usage fee, a total usage fee is calculated by adding the communication fee to the usage fee. identifying a first amount of resources allocated to programs running on the first system;
determining a second amount of resources to allocate to the program in a second system based on the first amount of resources;
calculating a usage fee for the second system based on the second resource amount;
displaying the calculated usage fee;
A display program that causes a computer to execute processing.

Images