WO2017002222A1

WO2017002222A1 - System deployment device and system deployment method

Info

Publication number: WO2017002222A1
Application number: PCT/JP2015/068935
Authority: WO
Inventors: 良一植田
Original assignee: 株式会社日立製作所
Priority date: 2015-07-01
Filing date: 2015-07-01
Publication date: 2017-01-05

Abstract

A system deployment device according to the present invention is provided with: a template DB storing a first template that contains information on a server included in a business system; and a configuration conversion information DB storing a configuration conversion information list that has written therein an implementation method for realizing, on a cloud, a function of the server. The system deployment device receives information specifying the first template and information specifying the type of cloud on which the business system is to be constructed, searches the configuration conversion information list for the server implementation method on the basis of the received information, creates a second template containing the details of the implementation method obtained as a hit, and constructs the business system on a cloud of the specified type on the basis of the second template. According to the present invention, a business system can be constructed from a predetermined system template without depending on the type of cloud on which the business system is to be constructed.

Description

System deployment apparatus and system deployment method

The present invention relates to cloud computing technology. In particular, the present invention relates to a technology for building a business system composed of a plurality of computer resources on a cloud environment.

In a cloud environment (hereinafter referred to as cloud), computer resources such as virtual servers and storage are collectively procured / pooled, and resources used for business system construction are deployed from this resource pool as necessary. In the cloud, since resources are virtualized, it is possible to deploy resources only with software.

Patent Document 1 discloses a technique for constructing a virtual server in a virtual environment using a template.

JP2012-141698

In the technology of Patent Document 1, a virtual server can be constructed only on a specific virtual environment from a predetermined template. That is, in a situation where there are a plurality of clouds as virtual server construction destinations, it is necessary to prepare a template for each cloud.

The system deployment apparatus of the present invention includes a template DB that stores a first template that includes information on servers that constitute a business system, and configuration conversion information that describes a mounting method for realizing server functions on the cloud. And a configuration conversion information DB that stores information, and receives information specifying the first template and information specifying the business system construction destination cloud type, and based on the received information, the server conversion method is used to specify the server mounting method. The second template including the contents of the mounting method that has been hit is created.

According to the present invention, it is possible to create a business system template applicable to various clouds from a predetermined system template.

Overall configuration diagram of environment in which the present invention is utilized Functional configuration diagram of system deployment engine 102 Process flow diagram of system construction program 221 The figure which shows the example of the system template information 211 The figure which shows the example of the cloud classification information 213 The figure which shows the example of the edge update list | wrist 215 Diagram showing an example of a system template before conversion Software configuration diagram showing an example of a system template before conversion The figure which shows the example of the system template before conversion in a YAML format The figure which shows the example of the system configuration | structure conversion information 212 Process flow diagram of system configuration conversion program 222 The figure which shows the example of the system template after conversion The figure which shows the example of the system template after conversion The figure which shows the example of the requirement change information 214 according to aspect System construction process flow diagram of embodiment 2 Diagram showing an example of a system template before conversion The figure which shows the example of the system template after conversion

FIG. 1 shows the overall configuration of an environment in which the present invention is used.

The environment includes a cloud 103, 141 that is a pool of computer resources such as a server 122, a storage 123, a network 121, etc., and a cloud management API 104 that cuts out the designated computer resource from the cloud and makes it usable for construction of a business system. A system deployment engine 102 that constructs a business system in response to an instruction from the system builder 101, and a network 111 that connects them.

The storage 123 stores a software group 131 such as an OS and middleware necessary for building a business system. An end user 105 who uses the business system constructed by the system builder 101 can access the clouds 103 and 141 via the network 111.

FIG. 2 shows the configuration of the system deployment engine 102.

The system deployment engine 102 includes a CPU 201, a memory 202, a display device 203, an input device 204, a communication device 205, and a storage device 206.

The storage device 206 stores a system construction program 221, a system configuration conversion program 222, system template information 211, system configuration conversion information 212, cloud type information 213, mode-specific requirement change information 214, and an edge update list 215. .

The CPU 201 reads each program into the memory 202 as necessary, and executes various processes.

FIG. 3 shows the overall flow of the business system construction process executed by the system construction program 221.

First, in step 301, the system deployment engine 102 selects “system template”, which is a model of a business system selected from the system template information 211, and “use” corresponding to the place where the system is constructed, selected from the cloud type information 213. "Cloud". The data structures of the system template information 211 and the cloud type information 213 will be described with reference to FIGS. 4a and 4b, respectively.

Next, in step 302, the system configuration conversion program 222 that has received these pieces of information uses the received cloud type and the server type and requirements of each node included in the received system template as keys. A mounting method is determined by searching from the system configuration conversion information 212, and nodes and edges are converted by the determined mounting method to create a new system template. The data structure of the edge update list 215 used for edge update will be described with reference to FIG. Details of the node and edge conversion processing will be described with reference to FIG.

Finally, in step 303, the system construction program 221 constructs a business system on the selected cloud according to the converted system template. That is, according to the converted system template, each server is arranged in a designated cloud, and software such as an OS and middleware is installed.

FIG. 4 a shows an example of the system template information 211. The system template information 211 includes an ID 401 that indicates an identifier of each row, a template name 402 that indicates the name of the system template, and a template content 403 that indicates the contents of the system template. For example, the row with ID “2” is a system template named “CRM”, which indicates a CRM (Customer Relationship Management) system template that is a business system for managing customer relationships.

FIG. 4 b shows an example of the cloud type information 213. The cloud type information 213 includes an ID 411 that indicates the identifier of each row, a cloud name 412 that indicates the name of the cloud, and a cloud management API 413 that indicates the URL of the management API associated with each cloud.

Fig. 4c shows an example of the edge update list 215. The edge update list 215 includes an ID 421 indicating an identifier of each row, a server type 422 indicating a server type of a node associated with the edge update, and an edge conversion method 423 indicating an edge exchange method. For example, ID “1” means that the LB in the system template being converted is set to connect to all Web servers in the system template.

Each line in the edge update list is created when the connection destination of the node is changed during the process of converting the node in the system template. Details will be described in step 706 of FIG.

FIG. 5a shows an example of a system template before conversion of ID “2” in FIG. 4a.

The system template is represented by a graph composed of nodes representing servers (implemented by physical machines, VMs, containers, services, etc. on the cloud) and edges representing network connections between servers. The system template describes requirements to be satisfied by each node and edge, setting parameters and construction scripts necessary for construction, software configuration information of individual servers, and the like.

In the example of FIG. 5a, 501 is represented as a node corresponding to a load balancer (hereinafter referred to as LB), 502 is a node corresponding to a Web server, and 503 is a node corresponding to a DB server.

Reference numeral 510 denotes an edge indicating the network connection between the outside of the system and the LB (corresponding to a connection point between the end user and the business system). Reference numeral 511 denotes an edge indicating the network connection between the LB and the Web server. And an edge indicating the network connection between the DB servers.

Further, 521 represents the requirements for the LB, 522 represents the requirements for the Web server, and 523 represents the requirements for the DB server.

521 means that the LB of the business system requires 99.95% or more availability (Avail). 522 means that the Web server of the business system has a processing performance “Perf” and needs to be scaled out (Scalable 2-4) from 2 to 4 servers. 523 means that the DB server of the business system has an availability of 99.99% or more and “date and time online backup” is a data backup requirement.

FIG. 5b shows an example of the software configuration information of each server indicated by the node in the system template.

In the node 501 indicating LB, “Linux (registered trademark)” 542 is set as an OS, and “HPProxy” 541 is installed as middleware for load distribution.

In the node 502 indicating the Web server, “Linux” 553 is set as an OS, “P-Lang” 552 is set as a language processing system thereon, and “SgCRM” 551 is installed as an application. It is set as follows.

In the node 503 indicating the DB server, “VLinux” 563 is set as an OS, and “PgDB” 561 is set as database management middleware on it.

The symbol such as “+ ver: 2+” written on the right side of each software means the condition of the version of each software. For example, 564 means that a version “3.0” or higher of “VLinux” 563 is required. “+ Port: 6543” 562 means that the PgDB 561 uses the number “6543” as a communication port.

In FIG. 5a, the system configuration is described in an easy-to-understand manner for human beings.

FIG. 5c shows an example in which FIGS. 5a and 5b are expressed in the YAML format.

The description of the corresponding parts in FIG. 5a and FIG. 5b is shown by adding “c” to the end of the corresponding part. For example, description of YAML format corresponding to node 501 indicating LB is 501c, description of YAML format corresponding to edge 511 indicating network connection between the LB and the Web server is 511c, description of YAML format corresponding to LB requirement 521 Is 521c.

FIG. 6 shows an example of the system configuration conversion information 212.

The system configuration conversion information 212 includes an ID 601 indicating an identifier of each row, a server type 602, a “requirement” 603 indicating a requirement to be satisfied by the server, a cloud type 604 indicating a cloud environment of a business system construction destination, and each server And a mounting method 605 indicating a setting parameter and a construction script necessary for constructing the cloud in the cloud.

As described in the description of FIG. 3, the system configuration conversion information 212 includes the server type 602 and the requirement 603 using the server type and requirement of the node included in the system template received by the system deployment engine and the type of use cloud as keys. , And a cloud type 604, and a list for searching the mounting method 605.

Although the program is actually described in the construction script of the mounting method 605, here, for the sake of explanation, not a program code but a character string representing a process executed by the program is described. For example, in the row of ID “1”, when an “RDB” server with an availability of 99.99% or more is constructed on the “Hit” cloud, two VMs are arranged in different racks (2 VM: different rack), and the 2 This means that high availability (HA) middleware is operated between two VMs, and the two VMs are set to perform disk sharing (device layer Shared Disk) by the function of the storage device. The setting parameters and the construction script included in the mounting method 605 are utilized by the system construction program 221 when step 303 is executed.

The row of ID “2” indicates that when an “RDB” server having an availability of 99.99% or more is constructed on the “Amz” cloud, “RDS” service is set to two nodes (: x2), and “Multi- It means to use with "AZ" setting. That is, it is not always necessary to create and set a VM for server construction, and a service such as “RDB” may be set as a node. The “Multi-AZ” setting means that resources of different AZs (resource areas) are used.

Requirement 603 items with curly braces such as “{x}” represent a variable, which means to correspond to an arbitrary number. In addition, when “$” is added before the variable name such as “$ x”, it means that the variable is referred to. For example, “Scalable {x}-{y}” within the requirement of ID “7” corresponds to a description such as “Scalable 2-4”. During the processing of the requirement, x is 2 and y is 4, and is referred to by “$ xVM” of the mounting method 605 with the same ID “7”. In this case, “$ xVM” is interpreted as “2VM”.

In the implementation method 605, items in square brackets such as “[RDS]” mean that the service provided by the cloud is used instead of creating and setting a VM as described above.

“FS layer synchronization” in the mounting method 605 means “synchronizing VMs with file system functions”.

“[RDS] +: DailySnapshot” of the implementation method 605 means that “setting to collect date and time snapshot” (“: Snapshot”) is added (“+”) to “RDS service”.

“Grouping to the number of LBs” in the mounting method 605 means “perform grouping as many as the number of LBs in the business system”.

The item starting with “Destination:” in the mounting method 605 describes the network connection (edge) conversion method, and the corresponding conversion is executed after the node conversion processing. Details will be described with reference to FIG.

The server type 602 describes only items corresponding to the role of the server, such as LB and Web server, but may be described in combination with information on the OS and software to be installed on the server. For example, it may be described as “DB / Linux”. When described in this way, it means that a DB is realized using Linux as an OS.

In addition, although only one item is described in the requirement 603, a plurality of items may be described, and each item may be combined with an AND condition or an OR condition.

FIG. 7 shows a detailed flow of the system configuration conversion process in step 302. Steps 702 to 707 are node conversion processes, and steps 708 to 710 are edge conversion processes.

First, in Step 702, one arbitrary node included in the system template to be converted is selected. Depending on the dependency between the nodes, unconfirmed information may be required depending on the selection order of the nodes. In this case, the selection of the node is discarded, another node is selected, and the process proceeds. For example, when the node corresponding to the ID “8” in FIG. 5 is processed, it is necessary to determine the “number of LBs” in the system before the conversion process. Here, when the node corresponding to the ID “8” is selected with the LB number being undetermined, the selection is discarded, another node is selected, and the process proceeds.

Next, in step 703, the system configuration conversion information 212 is searched using the server type and requirement of the selected node and the cloud type selected in step 301 as keys, and the mounting method of the selected node is determined. Here, when a plurality of server requirements are described, a mounting method is searched for each requirement.

Next, in step 704, the selected node is converted by the determined mounting method.

Next, in step 705, it is determined whether or not there is a description related to edge conversion in the mounting method. If there is a description related to edge conversion, the process proceeds to step 706; In step 706, the edge conversion contents related to the selected node are registered in the edge update list 215.

Next, in Step 707, Steps 702-706 are executed for all nodes.

Here, as an example of the node conversion process, a process of converting the system template in FIG. 5A when the use cloud “Hit” is selected will be described.

First, the node 501 indicating the LB is selected from the

nodes

501, 502, and 503 in the selected system template (step 702). Next, an implementation method that matches the server type “LB”, the requirement “availability 99.95+”, and the cloud type “Hit” to be used is searched from the system configuration conversion information 212, and the item of ID “3” is applied. Is determined (step 703).

Since the mounting method is “2VM: different rack,“ HA ”,“ FS layer synchronization ”,“ connection destination: all nodes ”, LB is configured with two VMs arranged on different racks, and the two VMs The HA configuration is set between them (settings for operating HA middleware and performing pairing settings), and the configuration is converted so that the disk synchronization between the 2VMs is performed in the file system layer (step 704).

Next, the presence or absence of edge conversion is confirmed for the node indicating the LB. Specifically, it is determined whether or not there is a line beginning with “connection destination:” in the mounting method column of the LB node (step 705).

In this example, “Connect to all nodes of the connection destination (Web server in this example) connected to the LB” is described, so the edge update (network connection destination change) content is registered in the edge update list 215. (Step 706).

Next, it is determined whether all the nodes in the system template have been converted. In this example, since the nodes 502 and 503 are unprocessed, the process loops to step 702 (step 707).

Next, the node 502 is selected (step 702), the implementation method of the ID “7” is applied (step 703), and the “performance monitoring” service and the “manual scale-out” service are added to the two VMs. (Step 704). Since there is no line beginning with “connection destination” in the mounting method column for ID “7”, step 706 is skipped.

Finally, through the same loop processing (step 707), the node 503 is selected (step 702), the mounting method of ID “1” is applied (step 703), and the RDB is configured with two VMs on different racks. Then, the HA configuration is assembled between the two VMs, converted to a configuration for sharing the disk with the function of the storage apparatus (step 704), and after the determination in step 705, the “connection destination connected to the DB server (Web server in this example) ) ”Is registered in the edge update list 215 (step 706). Furthermore, since the node 503 has the second requirement “Backup: OnlineDaily”, the implementation method “VM +: DailyBackup” corresponding to the ID “9” is applied, and “: DailyBackup” is applied to the VM that bears the RDB. Add settings (step 604)
As described above, by executing steps 702 to 707 which are node conversion processes, the nodes in the template can be converted into nodes having a form suitable for the construction destination cloud.

Return to the description of the edge update process in steps 708 to 710.

First, in step 708, an item registered in the edge update list is referred to and one unprocessed item is selected.

Next, in step 709, the edge is converted according to the referenced item.

Finally, in Step 710, Steps 708 to 709 are executed for all items in the edge update list, and the system configuration conversion process is completed.

Here, an example of the conversion process for items in the edge update list will be described following the example of the node update process described above.

In this example, registration to the edge update list is performed in the conversion process (step 704) between the node 501 and the node 503. In the conversion process of the node 501, as described above, “connect to all Web server nodes”, so that each LB configured with two VMs connects with all Web servers configured with two VMs. Convert edges. In the conversion process of the node 503, as described above, “Connect to all Web server nodes”, each DB configured with two VMs connects with all Web servers configured with two VMs. So that the edges are transformed.

As described above, by performing Steps 708 to 710 that are edge conversion processes, it becomes possible to automatically set a network between servers in a business system constructed on the cloud.

Then, by executing the processing in steps 702 to 710, it is possible to create a template in a form suitable for each cloud from the template in which only the server type and the requirements of the server are described.

In this example, an example in which only one item is hit when the system configuration conversion information (212) in FIG. 6 is searched is shown, but a situation in which a plurality of items are hit is also assumed. In that case, a column is added to FIG. 6, attribute information (for example, cost, reliability, length of remaining support period, etc.) is stored, and these information are displayed on the display unit, You may use the method of making a system builder select which mounting method is adopted among the mounting methods which hit multiple. For example, when the system configuration conversion information (212) is searched on the basis of the usage cloud “Amz”, the requirement “availability: 99.5%”, and the server type “LB”, the items of ID “5” and ID “6” are hit. To do. In that case, it is good also as a system which presents the above-mentioned attribute information to a user with each mounting method, and determines a mounting method. Alternatively, the system deployment engine may automatically select a mounting method based on a predetermined policy, and inquire the user for a final determination as to whether or not to adopt the mounting method. As the policy, for example, “prioritize cost reduction”, “prioritize high reliability”, and the like are assumed. As a result, when a plurality of server mounting methods are hit, it is possible to construct a business system that more reflects the intention of the system builder.
FIG. 8 a shows the converted system template when the usage cloud “Amz” is selected.

The node 501 indicating LB is composed of two nodes of the service “ELB” (801). For this configuration, DNS round robin and multi-AZ are set (802). Note that ELB is indicated by an ellipse in the figure, but this ellipse means “service” instead of “VM”.

The node 502 indicating the Web server is composed of two VMs (802). Then, it is set to be autoscaled in the range of minimum 2VM and maximum 4VM and divided into groups of the number of ELB nodes (two in this example) (822).

The node 503 indicating the DB server is composed of two nodes of service “RDS” (803). Multi-AZ is set for this configuration (823). Furthermore, “date and time snapshot” is set as a data backup requirement.

The edge 511 indicating the network connection between the LB and the Web server is converted into two edges 811 connecting the ELB node and the Web server VM, and the edge 512 indicating the network connection between the Web server and the DB server is converted into the Web server. It is converted into two edges 812 connecting the working VM and the RDS node.

FIG. 8b shows the converted system template when the use cloud “Hit” is selected.

The node 501 indicating the LB server is configured with 2 VM (851). The 2VMs are arranged in different racks, an HA configuration is assembled between the 2VMs, and the two VMs are set to perform data synchronization in the file system layer (871).

The node 502 indicating the Web server is configured with 2VM (852). Then, the 2VM is placed under the monitoring of the performance monitoring service, and is set so that scale-out can be executed by an instruction from the administrator from the manual scale-out service screen (872).

The node 503 indicating the DB server is configured with 2VM (853). The 2VMs are arranged in different racks, an HA configuration is assembled between the 2VMs, and the two VMs are set to share disks with the function of the storage device (873). Further, “date and time online backup” is set as a data backup requirement.

The edge 511 indicating the network connection between the LB and the Web server is converted into four edges 861 connecting the LB and the Web server, and the edge 512 indicating the network connection between the Web server and the DB server is converted between the Web server and the DB server. Are converted into four edges 862.

When accepting the specification of the system template and the cloud to be used in step 301, the business system mode such as “for production” or “for development” is input as additional information, and the mode-specific requirement change information 214 is used. The node requirements (521-523) in the system template may be changed according to the mode. This change is used when determining the node configuration mounting method 605 in step 703.

FIG. 9 shows an example of the mode-specific requirement change information 214. The mode-specific requirement change information 214 includes an ID 901 that indicates an identifier of each row, a mode 902 that indicates a mode of a business system, and a requirement change content 903 that indicates a requirement to be changed when the business system of the mode is constructed. The

For example, ID “3” reduces (Down) the portion related to availability (Avail) among the requirements specified for each node in the system template when the business system mode is “for development”. This means that a change is made to delete (Delete) the part related to performance (Perf). “-” In the requirement change content column means that the requirement is not changed.

Hereinafter, an example of processing when the system template illustrated in FIG. 5A is selected, “Amz” is selected as the use cloud, and “Development” is selected as the mode will be described.

The requirement used when determining the configuration of the node 501 indicating LB is “Avail: 99.95+”, but when the mode is “for development”, the availability requirement is lowered. When the availability requirement is not changed, the ID “4” of the system configuration conversion information 212 is applied. However, when the availability requirement is reduced as in this example, the ID “5” having a lower availability requirement is used. Is selected, and the mounting method “[ELB]” is applied.

Similarly, the requirement used when determining the configuration of the node 502 indicating the Web server is “Perf: Scalable2-4”, but when the mode is “for development”, the performance requirement is deleted. When the performance requirement is not changed, the ID “8” of the system configuration conversion information 212 is applied. However, when the performance requirement is deleted as in this example, “Perf” is not imposed as the performance requirement. The mounting method ID “11” is selected, and the mounting method “1VM” is applied.

In this way, by using the requirement change information 214 by mode, the performance of the business system can be adjusted according to the mode of the business system without manually processing the template.

Hereinafter, a second embodiment to which the present invention is applied will be described. The second embodiment will be described with a focus on differences from the first embodiment.

In the first embodiment, a process is described in which one cloud to be used is selected and all servers that construct the business system are arranged on the cloud. In the second embodiment, each server is arranged for each server. A case where a cloud to be selected is selected will be described. That is, it is assumed that a business system is constructed across multiple clouds.

FIG. 10 shows an overall processing flow in the construction of the business system in the second embodiment.

First, in step 1001, the system deployment engine 102 receives a system template selected from the system template information 212.

Next, in step 1002, the system deployment engine 102 receives the use cloud selected for each node in the received template. As a result, the cloud type is associated with each node in the received system template.

The cloud type associated with each node in the system template is recorded in the system deploy engine as attribute information of each node.

Here, the node attribute information recorded in the system deployment engine will be described with reference to FIG.

Attribute information 1101, 1102, 1103 starting with “@” indicates the type of cloud that is the placement destination of each node. This example is an example in which it is instructed to place the LB and the Web server in the “Amz” cloud and the DB server in the “Hit” cloud among the LB, the Web server, and the DB server.

Returning to the explanation of FIG.

Next, in step 1003, the system template is converted according to the system configuration conversion information 212 based on the cloud type 1101-1103 of the placement destination for each node determined in step 1002. The detailed procedure of this process is the same as that in the first embodiment.

Next, in step 1004, it is determined whether a plurality of nodes are arranged across the cloud. Specifically, in step 1002, it is determined whether or not a plurality of cloud types are selected. If a plurality of nodes are arranged across the cloud, the process proceeds to step 1005. Otherwise, the process proceeds to step 1006.

In the case of proceeding to Step 1005, since a plurality of nodes are arranged across the clouds, the network connection between the servers indicated by these nodes is set to an inter-cloud network (Inter-Cloud Network: corresponding to the exit of each cloud). ICN) must be substituted. Therefore, the arrangement of nodes at both ends of all edges in the system template is examined, the edge connecting between nodes arranged on different clouds is detected, and the connections at both ends of the detected edges are connected to the ICN existing in each cloud. Converts to an edge indicating the connection.

For example, when the edges in the system template of FIG. 11 are examined in order, an edge 512 indicating a network connection between the Web server and the DB server is detected as a connection between nodes arranged on different clouds. Therefore, the edges of the two Web server nodes are converted into edges indicating the network connection with the ICN of the cloud “Amz” in which they are arranged, and the edges of the two DB server nodes are converted into the cloud “Hit in which they are arranged. To an edge indicating a network connection with the ICN.

In step 1006, the system construction program 221 constructs a business system on the selected cloud according to the converted system template. That is, each server is arranged on a designated cloud in accordance with the converted system template, and software such as an OS and middleware is installed as necessary.

Next, in step 1007, it is determined whether or not the edge has been converted into a connection with the ICN. If the edge has been converted to an ICN connection, go to step 1008, otherwise skip step 1008.

In Step 1008, network settings between the clouds are performed so that servers arranged on different clouds can communicate with each other via ICN. In this example, settings are made so that communication is possible between the ICNs of the clouds “Amz” and “Hit”. The network connecting the clouds is a network setting method provided by the cloud service provider, such as a connection using a dedicated line, a virtual private network (VPN) via the Internet, and a direct connect service that connects two clouds at high speed. Any of them may be adopted. Further, the ICN of each cloud may exist on a one-to-one basis for each business system, or one ICN may be shared by a plurality of business systems.

In this embodiment, an example in which two clouds are selected as placement destinations has been described, but it is also assumed that three or more clouds are selected as server placement destinations. When three or more clouds are selected, a network between clouds that requires communication is set according to the arrangement of each server.

In addition, although expressed as “a network between clouds that requires communication depending on the arrangement of each server”, the communication here is not limited to communication by a business application on a business system. For example, communication for transmitting status information observed by the monitoring agent for monitoring the operating status of the business system to the monitoring server may be included.

FIG. 12 shows an example of the converted system template when an instruction is given to distribute and arrange business systems in the cloud “Amz” and the cloud “Hit”.

The LB node 501 and the Web server node 502 arranged in the cloud “Amz” are converted into a node 801 and a node 802, respectively, and the DB server node 503 arranged in the cloud “Hit” is converted into a node 853. An edge 511 indicating a network connection between the LB-Web server is converted into an edge 811.

The edge 512 indicating the network connection between the Web server and the DB server is converted into an edge 1221 and an edge 1222. An edge 1221 is an edge indicating a network connection between the Web server and the “Amz” ICN 1201, and an edge 1222 is an edge indicating a network connection between the DB server and the “Hit” ICN 1202.

In step 1006 of FIG. 10, a business system is constructed on the “Amz” cloud and the “Hit” cloud according to the converted system template. Then, by setting the inter-cloud network 1211 after the business system is constructed, the “Amz” cloud and the “Hit” cloud are connected.

In this way, by selecting a construction destination cloud for each individual server, a business system can be constructed across multiple clouds.

In addition, although a present Example is an example which sets the network between clouds when a business system is built ranging over several clouds, like Example 1, all the servers are arrange | positioned on one cloud. In some cases, the cloud may be connected to the outside using ICN. For example, when the business system constructed according to the present invention uses the authentication function of an existing system on a different cloud, etc., a cloud in which servers constituting the business system to be constructed are arranged, and an existing authentication function exists. The system needs to be connected via ICN. In such a case, all servers in the business system to be constructed that use the authentication function can communicate with the authentication function providing server in the existing system via the ICN in the cloud. The corresponding edge is converted into an edge indicating the network connection with the ICN, and the network setting between the cloud and the existing system is performed using the same method as in Step 1008 described above.

Thus, by converting the edge in the template into an edge indicating the network connection with the ICN, the constructed business system can use the functions of the system existing outside the cloud of the construction destination.

101: System builder 102: System deployment engine 103: Resource pool 104: Cloud management API
105: End user

Claims

A template DB that stores a first template that includes information about servers that make up a business system, and a configuration conversion information DB that stores configuration conversion information that describes the implementation method for realizing the functions of the server on the cloud A storage unit comprising:
An input unit for receiving information for specifying the first template and information for specifying a business system construction destination cloud type;
Based on the type of the server included in the specified first template, the configuration requirements of the server, and the specified cloud type, the implementation method of the server is searched from the configuration conversion information DB, and the implementation hit by the search And a system configuration conversion unit that creates a second template including the content of the method.
In the system deployment apparatus of Claim 1,
The first template includes information of a plurality of servers,
The system deployment device characterized in that the contents of the mounting method include information indicating a network connection destination of the server.
The system deployment device according to claim 2,
A system deployment apparatus, further comprising a system construction unit that constructs a business system on a specified type of cloud based on the second template.
In the system deployment apparatus of Claim 3,
When the network connection destination of the server is an external system, the system configuration conversion unit sets the network connection destination of the server as a network interface that is a connection point between the business system construction destination cloud and the external system. Create a template for
The system construction unit constructs a business system on a cloud of a type designated based on the third template, and sets a network between the network interface and the external system. apparatus.
In the system deployment apparatus of Claim 4,
The input unit accepts information specifying the cloud type for each server included in the first template;
If the server connection destination is in a different cloud, the system configuration conversion unit creates a fourth template with the network connection destination of the server as the network interface,
The system construction unit is configured to construct a business system on each specified type of cloud based on the fourth template, and to set up a network that connects the respective clouds. apparatus.
In the system deployment apparatus of Claim 3 thru | or 5,
The input unit further accepts information indicating an aspect of a business system and a requirement change content of a server associated with the aspect,
The system configuration conversion device, wherein the system configuration conversion unit changes configuration requirements of a server included in the first template based on the content of the requirement change.
In the system deployment apparatus of Claim 3 to 6,
A display unit;
When a plurality of mounting methods are hit by the search, the contents of each mounting method and the cost information associated with each mounting method are displayed on the display unit,
The input unit accepts a mounting method selected from the plurality of mounting methods;
The system configuration conversion unit creates a template including the contents of the accepted mounting method.
A template DB that stores a first template that includes information about servers that make up a business system, and a configuration conversion information DB that stores configuration conversion information that describes the implementation method for realizing the functions of the server on the cloud And comprising
The input unit receives information specifying the first template and information specifying the business system construction destination cloud type,
The system configuration conversion unit searches the configuration conversion information DB for the server mounting method based on the server type and the server configuration requirement included in the specified first template, and the specified cloud type,
A system deployment method characterized by creating a second template including the contents of the mounting method hit in the search.
The system deployment method according to claim 8,
The first template includes information of a plurality of servers,
The contents of the mounting method include information indicating the network connection destination of the server.
The system deployment method according to claim 9,
A system deployment method, wherein the system construction unit constructs a business system on a specified type of cloud based on the second template.
The system deployment method according to claim 10,
The cloud where the business system is built has a network interface that is a connection point with an external system.
When the network connection destination of the server is an external system, the system configuration conversion unit creates a third template having the network connection destination of the server as the network interface;
The system construction unit constructs a business system on a cloud of a type designated based on the third template, and sets a network between the network interface and the external system. Method.
The system deployment method according to claim 11,
The input unit accepts information specifying the cloud type for each server included in the first template;
If the server connection destination is in a different cloud, the system configuration conversion unit creates a fourth template with the network connection destination of the server as the network interface,
The system construction unit is configured to construct a business system on each specified type of cloud based on the fourth template, and to set up a network that connects the respective clouds. Method.
In the system deployment method of Claim 10 thru | or 12,
The input unit further accepts information indicating an aspect of a business system and a requirement change content of a server associated with the aspect,
The system configuration conversion unit is configured to change a configuration requirement of a server included in the first template based on the requirement change content.
The system deployment method according to any one of claims 10 to 13,
When a plurality of mounting methods are hit by the search, the contents of each mounting method and the cost information associated with each mounting method are displayed on the display unit,
The input unit accepts a mounting method selected from the plurality of mounting methods;
The system configuration method, wherein the system configuration conversion unit creates a template including the contents of the accepted mounting method.
A business system constructed on the basis of a template created by the system deployment method according to claim 8.