JP6313119B2 - System configuration plan generation apparatus and system configuration plan generation method - Google Patents

Description

  The present invention relates to a system configuration plan generation apparatus and a system configuration plan generation method.

  As cloud computing technology matures, the number of cases where cloud services are used to construct information systems is increasing. Cloud computing refers to a method of providing computing resources such as a server as a service, and a service provided by cloud computing is called a cloud service. In recent years, various IT companies have provided such cloud services, while information system departments of user companies have built their own cloud computing environments and provided cloud services for the company.

  Various cloud services provided in this way have different characteristics such as price, performance, reliability, safety, installation location, etc., so when building an information system using them, we grasped the characteristics of each cloud service Above, it is necessary to select an appropriate cloud service. However, there is a problem that it is not easy for an information system builder to select an appropriate cloud service in consideration of various conditions. Therefore, as a conventional technique for solving such a problem, a method of selecting an optimum provider from a list of cloud service providers based on requirements and constraints received from a user (see Patent Document 1) has been proposed.

US2013 / 0117157

  Usually, an information system is composed of a plurality of components. For example, many web systems are composed of a plurality of servers (that is, components) such as a web server, an application server, and a database server. In addition, management servers such as a monitoring server and a backup server are also required.

  Thus, in an information system composed of a plurality of components, it is not always optimal to use only the cloud service provided by one cloud service provider. There are cases where it is appropriate to use cloud services provided by different cloud service providers for each component.

  On the other hand, in the prior art, it is possible to select a cloud service provider suitable for the target system, but it does not support selecting an appropriate cloud service for each component constituting the system.

  The computing resource provided by the cloud service operates in a facility called a data center prepared by the cloud service provider. Therefore, cloud services provided by different cloud service providers operate in different data centers. Therefore, when using a plurality of cloud service providers as described above, communication between components is communication across data centers.

  If communication between data centers is not properly taken into consideration, the communication performance between the data centers, that is, between the components, may be deteriorated from the requirements desired by the user, or the communication fee may exceed the allowable level of the user. May occur. Such a situation needs to be avoided for users who are required to achieve both system performance that meets the requirements and acceptable installation and operation costs.

  Therefore, an object of the present invention is to generate a system configuration plan that takes into account the requirements for inter-data center communication in addition to the user-desired component requirements when the system is configured by a combination of multiple components involving inter-data center communication of a cloud service provider. It is to provide a technology that makes it possible.

A system configuration plan generation apparatus of the present invention that solves the above problems includes a storage device that stores specifications of a component to be provided in each cloud service, information on a location data center, and information on communication specifications between the data centers, and a user Predetermined input of specification of requirements of the execution system component that is a desired component, specification of user-desired component management requirements for the execution system component, and specification of network communication requirements between each of the execution system components For each combination of the searched cloud services, the storage device searches for a cloud service whose specifications satisfy the requirements of the user's desired execution system component and the processing received from the user's predetermined terminal via the screen. Between the data centers where the corresponding cloud services are located Searches the communication specifications in the storage device, includes a process of communication specifications desired by the user of the communication requirements to identify the combinations that satisfy, to a combination of cloud services component has the searched corresponding to the component management requirements If the component corresponding to the component management requirement is not included in the searched cloud service combination as a result of the determination, a cloud service whose specifications satisfy the component management requirement is stored in the storage device. For each combination of the cloud services searched, the communication device searches for the communication specifications between the data centers where the corresponding cloud services are located, and identifies the combination in which the communication specifications satisfy the communication requirements desired by the user. Processing and the execution system component An arithmetic unit for executing processing for generating a respective combination information of the specified cloud services with respect to the capital of the requirements and the component management requirements as a system proposed configuration, characterized in that it comprises a.

In addition, the system configuration plan generation method of the present invention is an information processing apparatus including a storage device that stores specifications of components to be provided in each cloud service, information on a location data center, and information on communication specifications between the data centers. Is a specification of requirements for an execution system component that is a user desired component, a specification of a user desired component management requirement for the execution system component, and a specification of a network communication requirement between each of the execution system components. The storage device searches for a cloud service whose specifications satisfy the requirements of the user-desired execution system component and the processing received from the user's predetermined terminal via a predetermined input screen, and each of the searched cloud services Location data of the corresponding cloud service for each combination The communication specification between printer searched by said memory device, and processing the communication specification desired by the user of the communication requirements to identify the combinations that satisfy, to a combination of cloud services component has the searched corresponding to the component management requirements If the component corresponding to the component management requirement is not included in the searched cloud service combination, the cloud service whose specifications satisfy the component management requirement is determined as the result of the determination. The storage device is searched for, and for each combination of the searched cloud services, the communication specifications between the data centers of the corresponding cloud services are searched in the storage device, and the communication specifications satisfy the communication requirements desired by the user. A process for specifying a combination and the execution system And executes a process of generating combined information of the cloud service as the system proposed configuration identified respectively with respect to components of the requirements and the component management requirements, the.

  According to the present invention, it is possible to generate a system configuration plan that takes into account the requirements for communication between data centers in addition to the component requirements desired by the user when the system is configured by a combination of multiple components that involve communication between data centers of cloud service providers. It becomes.

It is a figure which shows the example of an action | operation outline | summary of users using the system configuration plan generation method of a 1st embodiment. It is a network block diagram containing the system configuration plan production | generation apparatus of 1st Embodiment. It is a figure which shows the hardware structural example of the system configuration plan production | generation apparatus in 1st Embodiment. It is a figure which shows the structural example of the cloud service list of 1st Embodiment. It is a figure which shows the structural example of the communication performance information between data centers of 1st Embodiment. It is a figure which shows the structural example of the communication charge information between data centers of 1st Embodiment. It is a figure which shows the input screen example 1 in 1st Embodiment. It is a flowchart which shows the process procedure example 1 of the system configuration plan production | generation method in 1st Embodiment. It is a figure which shows the input screen example 2 in 1st Embodiment. It is a flowchart which shows process sequence example 2 of the system configuration plan production | generation method in 1st Embodiment. It is a flowchart which shows the process sequence example 3 of the system configuration plan production | generation method in 1st Embodiment. It is a figure which shows the example of the system configuration plan database in 1st Embodiment. It is a figure which shows the example of an output screen in 1st Embodiment. It is a figure which shows the hardware structural example of the system configuration plan production | generation apparatus in 2nd Embodiment. It is a figure which shows the example of the management requirement template in 2nd Embodiment. It is a flowchart which shows the process sequence example 1 of the system configuration plan production | generation method in 2nd Embodiment. It is a figure which shows the input screen example 1 in 2nd Embodiment. It is a flowchart which shows process sequence example 2 of the system configuration plan production | generation method in 2nd Embodiment. It is a figure which shows the input screen example 2 in 2nd Embodiment. It is a figure which shows the example of the system configuration plan database in 2nd Embodiment. It is a figure which shows the example of an output screen in 2nd Embodiment.

--- First Embodiment ---
A first embodiment of the present invention will be described below in detail with reference to the drawings. First, a situation where a system design support service (configuration plan generation service) is provided by the system configuration plan generation apparatus 100 of the first embodiment will be described. FIG. 1 is a diagram illustrating an example of an action summary of users who use the system configuration plan generation method of the first embodiment. Here, the flow of processing when a system builder (hereinafter referred to as user 301) uses the design support service described above and the cloud services provided by the cloud service providers 303 and 304 to construct a necessary information system. Is shown.

  In this case, the user 301 provides information such as requirements necessary for design to the design support service provider 302 (details will be described later). On the other hand, the design support service provider 302 uses the information given by the user 301 to generate an appropriate system configuration plan and informs the user 301 of the result. On the other hand, the user 301 determines a cloud service to be used for the system configuration based on the system configuration plan created by the design support service provider 302. Thereafter, the user 301 makes a cloud service use application to the cloud service providers 303 and 304 to be used. The cloud service providers 303 and 304 provide computing resources to the user 301 as a cloud service based on the content of the usage application from the user 301. The user 301 constructs an information system using the provided computing resources. In the example of FIG. 1, a case where two cloud service providers 303 and 304 are used is shown, but three or more cloud service providers may be used. Based on such a situation, the configuration of the system configuration plan generation apparatus 100 and the embodiment of the system configuration plan generation method will be described.

  FIG. 2 is a network configuration diagram including the system configuration plan generation apparatus 100 of this embodiment. The system configuration plan generating apparatus 100 shown in FIG. 2 is a system that takes into consideration the requirements for communication between data centers in addition to the component requirements desired by the user when the system configuration is a combination of a plurality of components involving communication between data centers of a cloud service provider. A computer system capable of generating a configuration plan.

  Such a system configuration plan generation apparatus 100 is an information processing apparatus that generates a system configuration plan based on information input by the administrator of the design support service provider 302 and the user 301 described above. Therefore, the system configuration plan generating apparatus 100 is connected to the administrator terminal 200 and the user terminal 300 via the network 10 such as the Internet or an intranet. The above-mentioned administrator accesses the system configuration plan generation apparatus 100 using the administrator terminal 200, refers to and inputs necessary information, and the user 301 accesses the system configuration plan generation apparatus 100 using the user terminal 300. Then, refer to and input necessary information.

  Next, the hardware configuration of the system configuration plan generation apparatus 100 will be described. FIG. 3 is a diagram illustrating a hardware configuration example of the system configuration plan generating apparatus 100 according to the first embodiment. The system configuration plan generation device 100 is stored in a storage device 101 configured by an appropriate nonvolatile storage device such as an SSD (Solid State Drive) or a hard disk drive, a memory 103 configured by a volatile storage device such as a RAM, and the storage device 101 The computer 102 is executed by reading out the program 102 to the memory 103 and executing the overall control of the device itself, and the arithmetic device 104 such as a CPU for performing various determinations, computations and control processes, and the input for accepting key input and voice input from the operator An apparatus 105, an output device 106 such as a display for displaying processing data, and a communication device 107 connected to the network 10 and responsible for communication processing with other devices. In the storage device 101, in addition to the program 102 for implementing functions necessary as the system configuration plan generation device 100 of this embodiment, a cloud service list 560, inter-data center communication performance information 570, inter-data center communication Charge information 580 and a system configuration plan database 590 are stored at least.

  Of the hardware configuration of the system configuration plan generation apparatus 100 described above, a general configuration as a computer includes the administrator terminal 200 and the user terminal 300 as well.

  Next, functions provided in the system configuration plan generation apparatus 100 according to the first embodiment will be described. As described above, the functions described below can be said to be functions implemented by executing the program 102 included in the system configuration plan generation apparatus 100, for example.

  The system configuration plan generating apparatus 100 searches the cloud service list 560 of the storage device 101 for cloud services whose specifications satisfy the component requirements desired by the user, and for each combination of the searched cloud services, The communication specifications between the data centers located are searched with the communication performance information between the data centers of the storage device 101, the combination in which the communication specifications satisfy the communication requirements desired by the user is specified, and the combination information of the specified cloud service is determined in the system A function to generate as a configuration plan is provided.

  In addition, the system configuration plan generation apparatus 100 further includes a function of outputting the combination information of the cloud services generated as the system configuration plan as described above to the output device 106.

  In addition, the system configuration plan generation apparatus 100 searches the cloud service list 560 of the storage device 101 for a cloud service that satisfies the management component specifications for user-desired component management requirements incidental to the component requirements, and performs the search The system further includes a function for generating a system configuration plan by further including each information of the communication specification of the cloud service and the specification of the corresponding management system component.

  In addition, the system configuration plan generation apparatus 100 indicates, for each combination of cloud services identified above, the cloud service usage fee included in the combination and the communication charge between the data centers of the corresponding cloud service in the cloud of the storage device 101. It further has a function of calculating based on each information of the service list 560 and the inter-data center communication charge information 580 and outputting it to the output device 106 together with the system configuration plan.

  As the functional unit in which each function described above is implemented by executing the program 102, a control unit 510 that controls the entire function, an input screen that receives input from a user, an administrator, or the like along with the execution of each function, or a processing result Screen generation unit 520 that performs generation processing of the output screen to be displayed, requirement evaluation unit 530 that identifies an appropriate cloud service by comparing the specifications with the specifications, and the usage and inter-data center regarding combinations of cloud services that are identified as satisfying the requirements A charge evaluation unit 540 that performs communication charge calculation and the like, and a configuration pattern generation unit 550 that generates a system configuration plan. The requirement evaluation unit 530 includes a server requirement evaluation unit 531 and a communication requirement evaluation unit 532. The fee evaluation unit 540 includes a server fee evaluation unit 541 and a communication fee evaluation unit 542. A specific example of the processing contents executed by each functional unit will be described later along with the flow description of the system configuration plan generation method.

  Next, an example of information held in the storage device 101 by the system configuration plan generation apparatus 100 will be described. The administrator of the design support service provider 302 described above needs to pre-register information necessary for providing the design support service before the user 301 uses the design support service. Specifically, the administrator terminal 200 operated by the above-mentioned administrator accesses the system configuration plan generation apparatus 100, receives the cloud service list 560 and data received from the administrator by the input device of the administrator terminal 200 Each information of the inter-center communication performance information 570 and the inter-data center communication charge information 580 is registered in the system configuration plan generating apparatus 100. Each information stored in the storage device 101 by the system configuration plan generation device 100 is registered in this way.

  Among these, the cloud service list 560 is a collection of information related to each cloud service that the above-described administrator recognizes as usable in the system configuration. In the example of the cloud service list 560 of FIG. 4, the provider 702 that provides the corresponding cloud service, the name 703 of the corresponding cloud service, and the computing resource provided by the corresponding cloud service are operating using the identifier 701 of the cloud service as a key. A set of records in which each information of the data center 704 (corresponding to the information of the location data center), the property 705 (corresponding to the component specification) representing the characteristics of the corresponding cloud service, and the usage fee 706 of the corresponding cloud service is associated It is a body.

  The inter-data center communication performance information 570 is a table storing information on communication performance (corresponding to communication specifications) between the data centers 704 defined in the cloud service list 560 described above. FIG. 5 is a diagram showing a configuration example of inter-data center communication performance information 570 in the first embodiment. The inter-data center communication performance information 570 illustrated in FIG. 5 includes information groups of inter-data center throughput 810 and inter-data center latency 820.

  Among these, the inter-data center throughput 810 is a table in which the throughput of data transfer from the server in the data center described in the “From” field to the server in the data center described in the “To” field is registered. . In the example of FIG. 5, for example, it is understood that the throughput of data transfer from the data center with the name “DC-A” to the data center with the name “DC-X” is “10 Mbps”.

  On the other hand, the inter-data center latency 820 is a table in which the latency in data transfer from the server in the data center described in the “From” field to the server in the data center described in the “To” field is registered. . In the example of FIG. 5, for example, it can be seen that the latency in data transfer from the data center with the name “DC-A” to the data center with the name “DC-X” is “30 msec”. If the latency in data transfer from “DC-X” to “DC-A” is approximately the same as the latency in data transfer from “DC-A” to “DC-X”, the latency value Is omitted, and "-" (hyphen) is described. Such inter-data center communication performance information 570 is registered based on performance information pre-measured by the above-described administrator regarding the network between the data centers or performance information published by the cloud service provider.

  FIG. 6 is a diagram showing a configuration example of the inter-data center communication fee information 580 in the first embodiment. The inter-data center fee information 580 is information that is input by the administrator using the administrator terminal 200 on the input screen 110 illustrated in FIG. 7 and is stored in the system configuration plan generation apparatus 100.

  In this case, the above-described administrator inputs each information on the connection relation between the data centers and the communication fee to the canvas 1120 in the input screen 1101 via the input device of the administrator terminal 200. This manager is well-known about the information on the connection relationship between data centers and communication charges. In response to this, the administrator terminal 200 transmits the information on the connection relation between the data centers and the communication charges input by the administrator to the system configuration plan generation apparatus 100, and the system configuration plan generation apparatus 100 receives the information. Then, it is stored in the storage device 101 as inter-data center communication fee information 580.

  In the example of the input screen 1101 in FIG. 7, the icons “DC-A” 1121, “DC-B” 1122, and “DC-X” 1123 represent data centers, and “NW in ABC” 1124 and “Internet” 1125. Each icon represents a network connecting data centers. In the input screen 1101, an arrow connecting the data center and the network indicates data communication, and the direction of the arrow indicates the direction of data communication. Furthermore, the numerical value given to the arrow represents the charge for data communication (unit: yen / GB). Therefore, for example, data communication denoted by reference numeral 1126 represents data communication transmitted from the data center “DC-A” to the network “NW in ABC”, and the charge is “10” yen / GB. The administrator operates the input device of the administrator terminal 200 and drags and drops the icons (corresponding to the data center and network) and the arrow parts on the palette 1110 onto the canvas 1120, thereby Each information of the connection relation between the data centers and the communication fee is input.

  Each information input by the administrator on the input screen 1101 is transmitted from the administrator terminal 200 to the system configuration plan generating apparatus 100 and stored in the inter-data center communication fee information 580 illustrated in FIG. The inter-data center communication charge information 580 illustrated in FIG. 6 includes a network list 581 that is a list of available networks, a data center list 582 that is a list of available data centers, and a communication charge 583 that is a list of communication charges. Composed.

  Among these, in the table of the communication fee 583, the “From” field 1131 is set with the value of the data transmission source, and the “To” field 1132 is set with the value of the data transmission destination. In the fee field 1133, a communication fee per unit data amount when data is transmitted from the transmission source to the transmission destination is set. Information equivalent to the information input on the input screen 1101 can be managed in a table format by the system configuration plan generation apparatus 100 by setting each table group of the network list 581, the data center list 582, and the communication fee 583. it can.

  Next, the actual procedure of the system configuration plan generation method in the first embodiment will be described with reference to the drawings. Various operations corresponding to the system configuration plan generation method described below are realized by a program 102 that the system configuration plan generation apparatus 100 reads into the memory 103 and executes. And this program 102 is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 8 is a flowchart showing a processing procedure example 1 of the system configuration plan generation method in the first embodiment. Here, first, the screen generation unit 520 of the system configuration plan generation apparatus 100 transmits input screen information to the user terminal 300 (S11). This input screen information is information relating to an input screen described using, for example, HTML (HyperText Markup Language) or the like, and is stored in advance in the storage device 101 by the system configuration plan generation device 100.

  On the other hand, the user terminal 300 displays the input screen information received from the system configuration plan generating device 100 as an input screen 601 on the output device. An example of the input screen 601 is shown in FIG. The user 301 who operates the user terminal 300 browses the input screen 601 described above, uses the input device of the user terminal 300, and inputs the logical system configuration and requirements regarding the system to be constructed on the input screen 601. . Here, the logical system configuration input by the user 301 is information indicating a server, that is, a component that is a component of the system, and a connection relationship between each server.

  Here, the logical system configuration input by the user 301 on the canvas 620 in the input screen 601 is configured by the servers host1 (621), host2 (622), and host3 (623) as in the example of FIG. , Conn1 (624) and conn2 (625) are connected to each other. Note that the user 301 inputs information related to the logical system configuration described above by dragging and dropping a part on the palette 610 into the canvas 620.

  Further, it is assumed that the user 301 selects a predetermined server from among host1 (621), host2 (622), and host3 (623) arranged in the canvas 620 by using the mouse of the user terminal 300 or the like. In this case, the system configuration plan generation apparatus 100 that has received the selection operation of the user 301 from the user terminal 300 returns a detailed field 630 to the user terminal 300 for inputting detailed information regarding the server. The user 301 designates detailed information regarding the corresponding server in the detail field 630, and the user terminal 300 acquires this designation information.

  In the example of FIG. 9, host 3 (623) is selected by the user 301, while the detailed information specified by the user regarding the host 3 (623) is displayed in the detail field 630. A broken line 626 in the canvas 620 is a mark indicating that host 3 (623) is selected by the user 301.

  The detail field 630 includes an OS input field 631 for specifying the OS requirement of the server, a CPU core number input field 632 for specifying the CPU core number requirement of the server, and a memory capacity input field 633 for specifying the memory capacity requirement of the server. In addition, an occupation / share input field 634 for inputting requirements regarding the occupation of the computing resources of the physical server, and an operation time input field 635 for specifying the operation time requirement of the corresponding server are included. The user 301 inputs the requirement for the corresponding server selected in the canvas 620, that is, the requirement for host 3 (623) in the above example, using these input fields 631 to 635. When the values that can be input by the user 301 are limited, the input fields 631 to 635 may be pull-down menu interfaces. The user 301 inputs requirements for host1 (621) and host2 (622) in the same manner.

  As described above, the user 301 can input the requirement for the desired server, that is, the component requirement by using the above-described detail field 630, and the user terminal 300 acquires and inputs the user-desired component requirement. The server requirement list 640 on the screen 601 is displayed. Information on such requirements is transmitted from the user terminal 300 to the system configuration plan generation apparatus 100. In the first embodiment, the user specifies the OS, the number of CPU cores, the memory, the occupation / sharing, and the operating time as the requirements for the server. The user may specify the requirements regarding the property, the requirements regarding the location of the data center, the requirements regarding the presence or absence of resource sharing with other users, and the like.

  In the same manner as the server requirements described above, the user 301 can also use the input screen 601 to input requirements related to communication between servers in which icons are arranged on the canvas 620. The requirements regarding communication between servers include latency and throughput values. In this case, when the user 301 performs a selection operation on each line display of conn1 (624) and conn2 (625) connecting the icons of the servers on the canvas 620, a system configuration is received from the user terminal 300. The plan generation apparatus 100 returns a detailed field for inputting detailed information related to the communication to the user terminal 300. Although the detailed field in this case is not particularly illustrated, it has the same form as the detailed field 630 described above, and includes an interface that receives user designation for latency, throughput, and communication data amount. When the communication-related requirements are specified in these detailed fields, the user terminal 300 or the system configuration plan generating apparatus 100 shows the communication requirement information in the communication requirement list 650. The first line of the communication requirement list 650 in FIG. 9 is that the inter-server communication “conn1” is communication from “host1” to “host2”, and the latency for this communication is within “10 msec”. The throughput is “30 Mbps” or more for both upstream (host 1 to host 2) and downstream (host 2 to host 1), indicating that the communication data amount in the inter-server communication is “2000 GB / month”. Note that the requirements related to latency are not distinguished in the example of FIG. 9 because the requirements for uplink (host 1 to host 2) and the requirements for downlink (host 2 to host 1) are the same.

  As described above, the logical system configuration and the information on each requirement input by the user 301 on the input screen 601 in the user terminal 300 are transmitted from the user terminal 300 to the system configuration plan generation apparatus 100 via the network 10, and the system It will be used to generate a configuration plan.

  Hereinafter, the description returns to the flowchart of FIG. Subsequent to step S <b> 11 (transmission of input screen information) described above, the control unit 510 of the system configuration plan generation apparatus 100 transmits the information on the user-desired components and communication requirements input by the user 301 from the user terminal 300. The server requirement evaluation unit 531 evaluates the component requirements, that is, the server requirements (S12).

  In this step S12, the server requirement evaluation unit 531 refers to the cloud service list 560 registered in advance in the storage device 101 by the administrator, and configures the corresponding system that the above-described user 301 is considering to construct. The cloud service that matches the server requirements (received from the user terminal 300) and satisfies the user-specified server requirements is extracted from the cloud service list 560.

  Hereinafter, the case where the user 301 inputs the logical system configuration and each requirement as shown in the input screen 601 in FIG. 9 will be described as an example, and the server requirement evaluation (S12) processing details by the server requirement evaluation unit 531 will be specifically described. To do.

  In this case, the server requirement evaluation unit 531 executes a requirement evaluation process described below for all the servers constituting the system planned to be built by the user. As can be seen from the server requirement list 640 in FIG. 9, there are three servers that constitute the system planned to be built by the user: “host1”, “host2”, and “host3”. Therefore, the server requirement evaluation unit 531 sequentially performs requirement evaluation on these three servers.

  First, in the server requirement evaluation for “host 1”, the server requirement evaluation unit 531 extracts a cloud service whose specifications satisfy the requirement for “host 1” from all the cloud services registered in the cloud service list 560. . As described above, the characteristics of each cloud service are described in the property 705 of the cloud service list 560. Therefore, the server requirement evaluation unit 531 can determine whether the specification of each cloud service can satisfy the server requirement specified by the user by comparing the server requirement specified by the user with the property 705 in the cloud service list 560.

  As can be seen from the server requirement list 640 in FIG. 9, the requirements for the above “host 1” are that the OS is “Linux (registered trademark)”, the number of CPU cores is “1” or more, and the memory is “2 GB” or more. The operating time is “720 hours / month”. Therefore, the server requirement evaluation unit 531 extracts three cloud services “# 03”, “# 04”, and “# 07” from the cloud service list 560 as cloud services that satisfy these requirements.

  Similarly, the server requirement evaluation unit 531 performs server requirement evaluation for “host 2”. As shown in the server requirement list 640, the requirements for “host 2” are that the OS is “Linux”, the number of CPU cores is “2” or more, the memory is “8 GB” or more, and the operation time is “720”. Time / month ". Therefore, the server requirement evaluation unit 531 extracts three cloud services “# 05”, “# 06”, and “# 07” from the cloud service list 560 as cloud services that satisfy these requirements. Similarly, the server requirement evaluation unit 531 extracts “# 07” from the cloud service list 560 as a cloud service that satisfies the requirement for “host3”.

  Summarizing the above results, the following were extracted as cloud services that satisfy the requirements of each server specified by the user.

(1) Cloud services satisfying host 1 requirements: # 03, # 04, # 07
(2) Cloud services satisfying host2 requirements: # 05, # 06, # 07
(3) Cloud service satisfying host 3 requirements: # 07
Following the server requirement evaluation process (S12), the configuration pattern generation unit 550 in the system configuration plan generation apparatus 100 generates a combination pattern for the cloud service that is extracted in step S12 and satisfies the requirements of each server. (S13).

  The configuration pattern generation unit 550 selects from the cloud services extracted in step S12 as a cloud service that can be used by each server (host1, host2, and host3) designated by the user 301 described above. In the first embodiment, there are three cloud services that satisfy the requirements of “host 1”, three cloud services that satisfy the requirements of “host 2”, and one cloud service that satisfies the requirements of “host 3”. The configuration pattern generation unit 550 generates a combination of nine cloud services shown below. This combination pattern of cloud services is hereinafter referred to as a system configuration pattern.

[Pattern 1] host1: # 03, host2: # 05, host3: # 07
[Pattern 2] host1: # 03, host2: # 06, host3: # 07
[Pattern 3] host1: # 03, host2: # 07, host3: # 07
[Pattern 4] host1: # 04, host2: # 05, host3: # 07
[Pattern 5] host1: # 04, host2: # 06, host3: # 07
[Pattern 6] host1: # 04, host2: # 07, host3: # 07
[Pattern 7] host1: # 07, host2: # 05, host3: # 07
[Pattern 8] host1: # 07, host2: # 06, host3: # 07
[Pattern 9] host1: # 07, host2: # 07, host3: # 07
Following the above-described system configuration pattern generation process (S13), the communication requirement evaluation unit 532 in the system configuration plan generation apparatus 100 evaluates the inter-server communication requirements for all system configuration patterns generated in step S13 (S14). The process of (S15) is performed. In the following, the details of the processing will be described by taking the evaluation of the inter-server communication requirements for the system configuration patterns of [Pattern 2] host 1: # 03, host 2: # 06, and host 3: # 07 as an example.

  FIG. 10 shows a detailed processing flow of the evaluation of server-to-server communication requirements (S15). In this case, the communication requirement evaluation unit 532 evaluates all the inter-server communications in the corresponding system configuration pattern (S151). As shown in FIG. 9, there are two inter-server communications “conn1” and “conn2” in the corresponding system that the user 301 plans to construct. Therefore, the communication requirement evaluation unit 532 performs evaluation for each of these inter-server communications. In the following, the details of the processing will be described by taking the evaluation for the inter-server communication “conn1” as an example.

  In this case, the communication requirement evaluation unit 532 extracts, from the storage device 101 or the memory 103, information on the transmission source server and the transmission destination server obtained in advance as the communication requirement list 650 from the user terminal 300 in the communication between servers to be evaluated. (S152). Here, it can be seen from the example of the communication requirement list 650 in FIG. 9 that the transmission source server in “conn1” is “host1” and the transmission destination server is “host2”.

  Next, the communication requirement evaluation unit 532 stores the information on the data center on which the transmission source server and the transmission destination server that have obtained information at the above-described step S152 (the corresponding information generated at the above-described step S13 is stored). Obtained from the storage device 101 or memory 103 (S153). As described above, in [Pattern 2], which is the system configuration pattern to be evaluated, “host 1” uses the cloud service “# 03” and “host 2” uses the cloud service “# 06”. By referring to the cloud service list 560, the evaluation unit 532 can specify that the cloud service “# 03” operates in the data center “DC-A” and the cloud service “# 06” operates in the data center “DC-B”. Therefore, the communication requirement evaluation unit 532 recognizes that “host1” as the transmission source server operates as “DC-A” and “host2” as the transmission destination server operates as “DC-B”.

  Next, the communication requirement evaluation unit 532 evaluates whether the latency between the transmission source server and the transmission destination server satisfies the requirement (S154). As shown in the communication requirement list 650 in FIG. 9, the latency requirement for “conn1” which is communication between servers in the system configuration pattern to be evaluated is “10 msec” or less. Further, in the inter-data center latency 820 shown in FIG. 5, it is understood that the latency of data communication transmitted from the server in “DC-A” to the server in “DC-B” is “5 msec”. Therefore, the communication requirement evaluation unit 532 determines that “conn1” in [Pattern 2] satisfies the communication requirement regarding latency.

  Thus, when the communication between applicable servers satisfy | fills the requirement regarding latency (S155: Yes), the communication requirement evaluation part 532 advances a process to S156 and implements the requirement regarding throughput. On the other hand, when the communication between applicable servers does not satisfy the requirements regarding latency (S155: No), the communication requirement evaluation part 532 complete | finishes the process with respect to this system configuration pattern.

  The communication requirement evaluation unit 532 is based on the information of the communication requirement list 650 already obtained from the user terminal 300 and the inter-data center throughput information 810 of the inter-data center communication performance information 570 in the throughput requirement evaluation (S156). Thus, it is determined whether or not the throughput requirement for communication between servers in the system configuration pattern to be evaluated is satisfied. For example, as shown in the communication requirement list 650 of FIG. 9, the throughput requirement for “conn1” which is communication between servers in the system configuration pattern to be evaluated is “30 Mbps” or more for uplink and “30 Mbps” or more for downlink. Further, in the inter-data center throughput information 810 shown in FIG. 5, it is understood that the throughput of data communication transmitted from the server in “DC-A” to the server in “DC-B” is “50 Mbps”. Therefore, the communication requirement evaluation unit 532 determines that “conn1”, which is communication between servers, satisfies the requirement of “30 Mbps” or higher from these information.

  Further, the communication requirement evaluation unit 532 refers to the inter-data center throughput information 810, and the throughput of data communication transmitted from the server in “DC-B” to the server in “DC-A” may be “40 Mbps”. recognize. For this reason, the communication requirement evaluation unit 532 determines that “conn1”, which is communication between servers, also satisfies a requirement of “30 Mbps” or lower. Through the above processing, the communication requirement evaluation unit 532 determines whether or not the system configuration pattern to be evaluated satisfies the communication requirement between servers.

  As a result of such determination, when the communication between the data satisfies the requirements regarding the throughput (S157: Yes), the communication requirement evaluation unit 532 returns the processing to S151 when there is unevaluated server-to-server communication, Evaluate communication requirements for server-to-server communication in the same way. On the other hand, when there is no unevaluated server-to-server communication, the communication requirement evaluation unit 532 determines that the communication between the data satisfies the communication requirement, and ends the process (S158). On the other hand, when the requirements regarding the throughput are not satisfied (S157: No), the communication requirement evaluation unit 532 determines that the communication requirements are not satisfied and ends the processing (S159).

  As described above, by evaluating the communication requirements for each system configuration pattern generated in step S13, the system configuration plan generation apparatus 100 determines that the system configuration pattern satisfying the user-specified communication requirements is [Pattern 1]. , [Pattern 2], [Pattern 4], [Pattern 5], and [Pattern 9].

  For the system configuration pattern determined to satisfy the communication requirements in step S15 described above, the fee evaluation unit 540 performs fee estimation processing (S17). On the other hand, the system configuration plan generating apparatus 100 ends the process for the system configuration pattern for the system configuration pattern determined not to satisfy the communication requirement in step S15, and performs the process for the next system configuration pattern.

  Hereinafter, the trial calculation process (S17) of the usage fee (including communication fee) of the cloud service in the fee evaluation unit 540 will be described. FIG. 11 shows a detailed processing flow of the fee calculation process (S17). The details of the fee calculation process will be described below by taking the process for the system configuration of [Pattern 2] as an example.

  In this case, first, the server fee evaluation unit 541 performs a trial calculation of the server usage fee (S171 to 173). In the trial calculation of the server usage fee, the server fee evaluation unit 541 performs the process of step S172 for all servers included in the corresponding system configuration pattern.

  In step S172, the server fee evaluation unit 541 executes a process of multiplying the fee (unit price per hour) of the cloud service to be used and the operating time of the server, and calculates the usage fee for each server. As described above, the system configuration planned to be constructed by the user in the first embodiment includes three servers “host1”, “host2”, and “host3”. In the following, an explanation will be given by taking a server usage fee for “host 1” as an example. In the system configuration of [Pattern 2], “host 1” uses the cloud service “# 03”. Therefore, the server fee evaluation unit 541 refers to the cloud service list 560 and specifies that the fee for the cloud service “# 03” is “15 yen / hour”. The server fee evaluation unit 541 recognizes that the operating time of “host1” is “720 hours / month” by referring to the information in the server requirement list 640 (FIG. 9) input by the user 301. Therefore, the server fee evaluation unit 541 multiplies “15 yen / hour” by “720 hours / month” to calculate that the usage fee of “host1” is “10,800 yen / month”.

  Similarly, the server fee evaluation unit 541 calculates “14,400 yen / month” as the usage fee for “host 2” and “28,800 yen / month” as the usage fee for “host 3”.

  Next, the communication fee evaluation unit 542 calculates the communication fee between servers (S174 to S176). In the trial calculation of the inter-server communication fee, the process of step S175 is executed for all the inter-server communication included in the corresponding system configuration pattern.

  In step S175, the communication fee evaluation unit 542 calculates each communication fee by multiplying the communication fee per unit data amount required for the communication between servers by the communication data amount generated by the communication between servers.

  As described above, the inter-server communication “conn1” and “conn2” exists in the above-described system configuration pattern. Therefore, in the following, an explanation will be given taking an example of a trial calculation of communication charges for “conn1”. In the system configuration pattern [Pattern 2], “conn1” corresponds to data communication from “DC-A” to “DC-B”. Therefore, the communication fee evaluation unit 542 refers to the inter-data center communication fee information 580 shown in FIG. 6 and calculates the communication fee per unit data amount for communication from the data center “DC-A” to “DC-B”. Find the value.

  When data is transmitted from the data center “DC-A” to “DC-B”, there are two routes: a route for transmitting data via the network “NW in ABC” and a route for transmitting data via “Internet”. There is a route. In this way, when there are a plurality of data transmission paths, the communication charge evaluation unit 542 performs a charge calculation using the path with the lowest charge.

  When data is transmitted from the data center “DC-A” to the “DC-B” via the network “NW in ABC”, the data transmission from the data center “DC-A” to the network “NW in ABC” is “10”. Since the data transmission from the network “YW / GB” and the network “NW in ABC” to the data center “DC-B” is charged “0 yen / GB”, the communication fee evaluation unit 542 starts from “DC-A” to “ It is calculated that the data transmission to “DC-B” takes a charge of “10 yen / GB” which is the total value of these charges. Similarly, the communication fee evaluation unit 542 calculates that a fee of “20 yen / GB” is charged when data is transmitted from the data center “DC-A” to “DC-B” via “Internet”. Therefore, the communication fee evaluation unit 542 performs a trial calculation of the communication fee using the fee of “10 yen / GB” when data is transmitted via the “NW in ABC” where the fee is low.

  The data amount of data communication from the data center “DC-A” to “DC-B” is “2,000 GB / month” as shown in the communication requirement list 650 of FIG. Therefore, the communication fee evaluation unit 542 multiplies the above-mentioned fee “10 yen / GB” by the data amount “2000 GB / month”, so that the communication fee of the inter-data center communication “conn1” is “20,000 yen / month”. It is calculated that Similarly, the communication fee evaluation unit 542 calculates “10,000 yen / month” as the communication fee for “conn2”.

  Next, the communication fee evaluation unit 540 adds the fees obtained in steps S172 and S176 described above to obtain a total fee. That is, the usage fee for “host1” “10,800 yen / month”, the usage fee for “host2” “14,400 yen / month”, the usage fee for “host3” “28,800 yen / month”, “conn1” The communication charge “20,000 yen / month” for “Conn2” and the communication charge “10,000 yen / month” for “conn2” are added together to calculate “84,000 yen / month” as the total charge.

  On the other hand, the control unit 510 obtains the system configuration pattern that satisfies the server requirement and the communication requirement and the result of the trial calculation when the system configuration pattern is adopted, that is, the system configuration plan obtained by the above processing. Stored in the configuration plan database 590. For example, as shown in FIG. 12, the system configuration plan database 590 is a server candidate that has specifications satisfying both the server requirements and the communication requirements specified by each user regarding the predetermined system configuration as a result of the above steps. Can be assumed to be a table structure in which each component is listed.

  After executing each processing of steps S15 to S18 for all system configuration patterns, the screen generation unit 520 generates a screen 1200 (FIG. 13) for transmitting the processing result to the user 301, and the corresponding screen data is used for the user. It transmits to the terminal 300. The screen 1200 illustrated in FIG. 13 draws the components “host1”, “host2”, and “host3” specified by the user, and the icons “conn1” and “conn2” that are communication relations between them, It includes a display field 1202 that shows the logical system configuration again, and a candidate server list 1202 that is the result of executing the above steps. Among these, the candidate server list 1202 is a list of cloud service candidates (that satisfy all specifications) for realizing each of the servers “host 1”, “host 2”, and “host 3” as components in the display field 1202. It becomes a table.

  The user terminal 300 receives the data on the screen 1200 and displays it on the output device. The user 301 selects a cloud service to be used for system construction for each component based on the display information on the above-described screen 1200 displayed on the user terminal 300, and determines the system configuration.

  Through the processing described above, the system configuration plan generation apparatus 100 can create a cloud service plan used by each server that configures the system and present it to the user together with the trial calculation at that time.

--- Second Embodiment ---
Hereinafter, a second embodiment of the present invention will be described. In an information system that requires high reliability, in addition to a server that executes a business application (hereinafter referred to as an execution system server), a management system server that performs life / death monitoring and collection of operation statistical information is required. Therefore, when the user determines the system configuration, it is necessary to consider these management servers.

  A configuration example of the system configuration plan generation apparatus 100 in the second embodiment based on such background is shown in FIG. In addition to the configuration of the system configuration plan generation apparatus 100 according to the first embodiment, the system configuration plan generation apparatus 100 according to the second embodiment includes the functions of the management system configuration generation unit 555 implemented by executing the program 102. A management requirement template 600 is provided. Other functions and data configurations are the same as those of the system configuration plan generating apparatus 100 of the first embodiment.

  The management requirement template described above is registered in advance by the administrator of the design support service provider 302 by operating the administrator terminal 200 to access the system configuration plan generation apparatus 100. An example of the management requirement template 600 is shown in FIG. The management requirement template 600 includes tables of a management communication requirement 1401 and a management server requirement 1402.

  Among these, the management communication requirement 1401 is a table storing information indicating what kind of communication between servers occurs when various operations management is performed and what kind of requirement is required at that time. . For example, the record in the first line in the management communication requirement 1401 causes communication between the management server named “mon” and “target” representing the management target server when “life monitoring” is performed. This indicates that the latency of this communication needs to be “1 min” or less, and the data amount of this communication is “10 MB / month”. Note that the throughput value “-(hyphen)” indicates that there is no requirement for throughput for this communication.

  The management server requirement 1402 is a table that stores information representing requirements for the management server. For example, the record on the first line in the management server requirement 1402 indicates that the management server named “mon” has an OS type of “Linux”, a core number of “1” or more, and a memory of “2 GB”. ”Or more, and the operating time is“ 720 hours / month ”. The above-described administrator registers each piece of information of the management requirement template 600 in the system configuration plan generating apparatus 100 based on a past typical case. On the other hand, the system configuration plan generating apparatus 100 receives data of the management requirement template 600 from the administrator terminal 200 and stores and holds it in the storage device 101.

  Next, a specific processing flow of the system configuration plan generation method according to the second embodiment will be described. FIG. 16 is a flowchart showing a processing procedure example 1 of the system configuration plan generation method according to the second embodiment. In the flowchart, the input screen transmission (S161) and management system configuration generation (S162) are different from the processing contents of the first embodiment, but other processes are the same as those of the first embodiment. .

  First, the system configuration plan generating apparatus 100 transmits an input screen 1700 shown in FIG. 17 to the user terminal 300 (S161). The input screen 1700 in the second embodiment has substantially the same configuration as the input screen 601 in the first embodiment shown in FIG. 9, but a life / death monitoring input field 1301 and an operation statistics input field 1302 are included in the detailed field 630. Different points are included.

  The life / death monitoring input field 1301 is an interface for designating whether to perform life / death monitoring for the corresponding server selected by the user on the canvas 620, while the operation statistics input field 1302 is selected by the user on the canvas 620. This interface specifies whether or not to perform operation statistics for the corresponding server.

  The user 301 can operate the user terminal 300, specify each requirement in these input fields 1301 and 1302, and input the operation management requirement for the corresponding server selected on the canvas 620. The requirements specified by the user 301 in the life / death monitoring input field 1301 and the operation statistics input field 1302 are set and displayed in the life / death monitoring field 1301 and the operation statistics field 1302 of the server requirement list 640 on the input screen 1700. The point that the life / death monitoring column 1301 and the operation statistics column 1302 are included in the server requirement list 640 is different from the input screen 601 of one embodiment.

  Each information of the logical system configuration and each requirement (including life / death monitoring and operation statistics requirements) input by the user 301 is transmitted from the user terminal 300 to the system configuration plan generation apparatus 100 via the network 10. The system configuration plan generation apparatus 100 receives the logical system configuration and information on each requirement transmitted from the user terminal 300, and stores and holds them in, for example, the storage device 101 or the memory 103.

  Next, the management system configuration generation unit 555 of the system configuration plan generation apparatus 1201 stores the management requirement template 600 pre-registered in the information input by the user on the input screen 1700 as described above and held in the storage device 101. And the entire configuration of the information system including the management system is generated (S162).

  FIG. 18 shows a processing flow of the management system configuration generation (S162). The management system configuration generation unit 555 executes the processing of S1622 to S1627 for all the active servers that constitute the information system that the user plans to construct. In the second embodiment, as shown in the input screen 1700 of FIG. 17, the management system configuration generator 555 includes three execution servers “host1”, “host2”, and “host3”. Performs the processes of S1622 to S1627 for these three servers. In the following, details will be described by taking a process for the active server “host1” as an example.

  In this case, the management system configuration generation unit 555 executes the processing of steps S1623 to S1626 for all management requirements. As shown in FIG. 17, in this embodiment, since the user designates two management requirements of “life monitoring” and “operation statistics”, processing is performed on these two management requirements. The details of the processing will be described below by taking “operation statistics” as an example.

  The management system configuration generation unit 555 designates that the target management requirements are required for the target active server “host1” or based on the information on each requirement received from the user terminal 300. It is determined whether operation management for satisfying the corresponding management requirement is necessary (S1623). As shown in FIG. 17, since the management requirement “operation statistics” is designated by the user as “present (detailed)” for the active server “host 1”, the management system configuration generation unit 555 It is determined that operation management is necessary to satisfy the management requirements.

  Therefore, when it is determined that the operation management is “necessary” (S 1623: Yes), the management system configuration generation unit 555 needs to change the system configuration, and thus the process proceeds to S 1623. On the other hand, when it is determined that the operation management is “not required” (S1623: No), the management system configuration generation unit 555 determines that it is not necessary to change the system configuration with respect to the corresponding management requirement “operation statistics”, and performs processing. The process proceeds to S1627.

  Subsequently, the management system configuration generation unit 555 performs the management requirement “operational statistics” on the current system configuration (at least the active system component = the system configuration in which the configuration of the active server is a user specified state). It is determined whether a necessary management server has already been arranged, for example, by searching the screen data of the input screen 1700 (S1624).

  For example, the management system configuration generation unit 555 refers to the management communication requirement 1401 in the management requirement template 600 shown in FIG. 15, and the management server “stats” is necessary to implement the management requirement “operation statistics”. Can be identified.

  On the other hand, since “stats” is not arranged in the current system configuration of the input screen 1700 shown in FIG. 17, the management system configuration generation unit 555 determines that the necessary management server does not exist (S1624: No), the process proceeds to S1625 to add the management server “stats”. On the other hand, when the management system server “stats” has already been arranged in the current system configuration of the input screen 1700 shown in FIG. 17 (S1624: Yes), the management system configuration generator 555 does not need to add a management system server. And the process advances to step S1626.

  As described above, if the management system server that satisfies the management requirements specified by the user is not included in the current system configuration and the corresponding management system server needs to be added, the management system configuration generation unit 555 Adds the management server “stats” to the system configuration on the input screen 1700 shown in FIG. 17 (S1625). The server requirements (OS, CPU, memory, operating time, etc.) required for the management server to be added here are acquired by the management system configuration generation unit 555 with reference to the management server requirement 1402 (FIG. 15). Shall.

  Next, the management system configuration generation unit 555 adds a record related to server-to-server communication necessary for implementing the above-described management requirement “operation statistics” to the communication requirement list 650 regarding the current system configuration (S1626). . The management system configuration generation unit 555 acquires information related to communication between servers that is necessary when the management requirement “operational statistics” is performed with reference to the management communication requirement 1401 (FIG. 15).

  When the management system configuration generation unit 555 adds the information on the requirements regarding the communication between servers obtained here to the communication requirement list 650, the management system configuration generation unit 555 described in the “transmission destination” column of the management communication requirement list 650 The character string “target” representing the target is replaced with the actual server name. Here, since the management requirement for “host1” is added, the management system configuration generation unit 555 sets the value of “target” to “host1” in the communication requirement list 650.

  The management system configuration generation unit 555 generates the configuration of the entire information system including the management system by performing the above processing on all management requirements and all execution servers. A result of generating a management system configuration related to the system configuration exemplified in the input screen 1700 of FIG. 17 is shown in a screen 1900 of FIG. As a server constituting the system shown here, two management servers “mon” and “stats” are added, and “mon1”, “mon2”, “mon3”, “statS1”, It can be seen that five communications of “stats2” are added.

  On the other hand, control unit 510 stores the system configuration plan obtained by the above processing in system configuration plan database 590. As shown in FIG. 20, for example, the system configuration plan database 590 in the second embodiment satisfies both the server requirements and communication requirements specified by each user regarding a predetermined system configuration as a result of the above steps. It is possible to assume a table configuration in which a candidate for an active server having specifications and a candidate for a management server having specifications satisfying the management requirements are listed for each corresponding component.

  In addition, the system configuration plan generation apparatus 100 may transmit the system configuration information generated in this way to the user terminal 300 for confirmation by the user 301. FIG. 21 shows an example of a screen that the system configuration plan generation apparatus 100 transmits to the user terminal 300 in that case. The screen 2100 shown in FIG. 21 includes components “host1”, “host2”, and “host3” that are execution servers designated by the user, and “conn1” and “conn2” that are communication relationships between these components, The components of the management servers “mon” and “stats” and the icons of “mon1”, “mon2”, “stats1”, “stats2”, etc., which are the communication relationship between the execution server and the management server are drawn. In addition, a display field 2101 that shows the logical system configuration again and a candidate server list 2102 that is a result of executing the above steps are included. Among these, the candidate server list 2102 is a cloud service for realizing the active servers “host1”, “host2”, and “host3” as components in the display field 2101 and the management servers “mon” and “stats”. This is a table in which candidates (those satisfying all specifications) are listed.

  The user terminal 300 receives the data on the screen 2100 from the system configuration plan generation device 100 and displays it on the output device. Based on the display information on the above-described screen 2100 displayed on the user terminal 300, the user 301 selects a cloud service used for system construction for each component of the execution system and the management system, and determines the system configuration.

  In this way, the system configuration plan generating apparatus 100 can generate a system configuration plan that also considers the management system.

  Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

  According to the present embodiment, when a system is configured by a combination of a plurality of components involving communication between data centers of a cloud service provider, generation of a system configuration plan that takes into consideration the requirements for communication between data centers in addition to the component requirements desired by the user. This makes it easy to design a system using a cloud service applied by a plurality of cloud service providers.

  At least the following will be clarified by the description of the present specification. That is, in the system configuration plan generation apparatus according to the present embodiment, the arithmetic device may further execute processing for outputting the combination information of the cloud services generated as the system configuration plan to an output device. According to this, the user can easily recognize the system configuration plan.

  Further, in the system configuration plan generation apparatus according to the present embodiment, the storage device stores information on specifications of the execution system component and the management system component that manages the execution system component as the specification of the provided component. The computing device searches the storage device for a cloud service that satisfies the specifications of the management system component for a user-desired component management requirement incidental to the component requirement, and The system configuration plan may be generated by further including each information of the communication specification and the specification of the corresponding management system component. According to this, it is possible to generate a system configuration plan that also considers requirements for management components such as a management server.

  Further, in the system configuration plan generation apparatus according to the present embodiment, the storage device further stores information on usage charges for each cloud service and communication charges between the data centers, and the arithmetic unit is configured to store the specific information. For each combination of the cloud services, the cloud service usage charge included in the combination and the communication charge between the data centers of the corresponding cloud services are calculated based on each information of the storage device and output together with the system configuration plan The process of outputting to the apparatus may be further executed. According to this, the user can study the system configuration plan in consideration of not only the functional requirements but also the fee requirements.

  Further, in the system configuration plan generation method of the present embodiment, the information processing apparatus may further execute a process of outputting the cloud service combination information generated as a system configuration plan to an output device.

  According to this, the user can easily recognize the system configuration plan.

  Further, in the system configuration plan generation method according to the present embodiment, the information processing apparatus includes an execution system component and a management system component that manages the execution system component as specifications of the provided component in the storage device. Stores the information of each specification, searches the storage device for a cloud service that satisfies the specifications of the management system component for the component management requirements desired by the user attached to the component requirements, and The system configuration plan may be generated by further including each information of the communication specification and the specification of the corresponding management system component.

  According to this, it is possible to generate a system configuration plan that also considers requirements for management components such as a management server.

  Further, in the system configuration plan generation method according to the present embodiment, the information processing apparatus further stores, in the storage device, each information of a usage fee of each cloud service and a communication fee between the data centers. For each combination of the cloud services, the cloud service usage charge included in the combination and the communication charge between the data centers of the corresponding cloud services are calculated based on each information of the storage device and output together with the system configuration plan The process of outputting to the apparatus may be further executed.

  According to this, the user can study the system configuration plan in consideration of not only the functional requirements but also the fee requirements.

10 Network 100 System Configuration Proposal Generation Device 101 Storage Device 102 Program 103 Memory 104 CPU (Calculation Device)
105 input device 106 output device 107 communication device 200 administrator terminal 300 user terminal 510 control unit 520 screen generation unit 530 requirement evaluation unit 531 server requirement evaluation unit 532 communication requirement evaluation unit 540 fee evaluation unit 541 server fee evaluation unit 542 communication Fee evaluation unit 550 Configuration pattern generation unit 555 Management system configuration generation unit 560 Cloud service list 570 Inter-data center communication performance information 580 Inter-data center communication fee information 581 Network list 582 Data center list 583 Communication fee 590 System configuration plan database 600 Management Requirement template 810 Inter-data center throughput 820 Inter-data center latency 1401 Management communication requirements 1402 Management server requirements

Claims (6)

A storage device storing the specifications of the components provided in each cloud service and information on the location data center, and information on communication specifications between the data centers;
The specification of the requirements of the specifications of the execution system components that are user-desired components, the specification of the user-desired component management requirements for the execution system components, and the specification of the communication requirements of the network between each of the execution system components Processing for receiving from the user's predetermined terminal via the input screen, and searching for cloud services whose specifications satisfy the requirements of the user-desired execution system component in the storage device, and for each combination of the searched cloud services In addition, a process for searching for a communication specification between the data centers where the corresponding cloud service is located in the storage device, identifying the combination that satisfies the communication specification desired by the user, and a component corresponding to the component management requirement The set of cloud services searched If the component corresponding to the component management requirement is not included in the searched cloud service combination, the cloud service whose specifications satisfy the component management requirement is determined. The storage device is searched for, and for each combination of the searched cloud services, the communication specification between the data centers of the corresponding cloud services is searched in the storage device, and the communication specification satisfies the communication requirements desired by the user. A processing unit that executes the process of generating the combination information of the cloud service identified as the system configuration proposal , the process of identifying the combination, and the requirements of the execution system component and the component management requirement ,
A system configuration plan generation apparatus comprising: The arithmetic unit is:
The system configuration plan generation apparatus according to claim 1, further executing a process of outputting the combination information of the cloud services generated as a system configuration plan to an output device. The storage device
Each information of the usage fee of each cloud service and the communication fee between the data centers is further stored,
The arithmetic unit is:
For each combination of the specified cloud services, a cloud service usage fee included in the corresponding combination and a communication fee between data centers of the corresponding cloud services are calculated based on each information of the storage device, and the system configuration plan Together with the process of outputting to the output device.
The system configuration plan generation apparatus according to claim 1. An information processing apparatus including a storage device that stores specifications of a component to be provided in each cloud service and information on a location data center and information on communication specifications between the data centers.
The specification of the requirements of the specifications of the execution system components that are user-desired components, the specification of the user-desired component management requirements for the execution system components, and the specification of the communication requirements of the network between each of the execution system components Processing received from the predetermined terminal of the user via the input screen;
The storage device is searched for a cloud service whose specifications satisfy the requirements for the execution system component desired by the user , and for each combination of the searched cloud services, the communication specifications between the data centers where the corresponding cloud services are located are A process of searching in a storage device and identifying the combination that the communication specifications satisfy the communication requirements desired by the user ;
It is determined whether a component corresponding to the component management requirement is included in the searched cloud service combination. As a result of the determination, a component corresponding to the component management requirement is not included in the searched cloud service combination. A cloud service whose specifications satisfy the component management requirements are searched in the storage device, and for each combination of the searched cloud services, the communication specifications between the data centers where the corresponding cloud services are located are stored in the storage device. in search, the user desired a process of communication requirements to communicate specification identifies the combination meets the combination information system configuration requirements and cloud services identified respectively with respect to the component management requirements of the active system components And the process of generating as a draft,
A system configuration plan generation method characterized by: The information processing apparatus is
The system configuration plan generation method according to claim 4, further comprising a process of outputting the combination information of the cloud services generated as a system configuration plan to an output device. The information processing apparatus is
In the storage device, each information of the usage fee of each cloud service and the communication fee between the data centers is further stored,
For each combination of the specified cloud services, a cloud service usage fee included in the corresponding combination and a communication fee between data centers of the corresponding cloud services are calculated based on each information of the storage device, and the system configuration plan And further executing a process of outputting to the output device.
The system configuration plan generation method according to claim 4.