WO2017002222A1 - Dispositif de déploiement de système et procédé de déploiement de système - Google Patents

Dispositif de déploiement de système et procédé de déploiement de système Download PDF

Info

Publication number
WO2017002222A1
WO2017002222A1 PCT/JP2015/068935 JP2015068935W WO2017002222A1 WO 2017002222 A1 WO2017002222 A1 WO 2017002222A1 JP 2015068935 W JP2015068935 W JP 2015068935W WO 2017002222 A1 WO2017002222 A1 WO 2017002222A1
Authority
WO
WIPO (PCT)
Prior art keywords
template
server
cloud
information
configuration conversion
Prior art date
Application number
PCT/JP2015/068935
Other languages
English (en)
Japanese (ja)
Inventor
良一 植田
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2015/068935 priority Critical patent/WO2017002222A1/fr
Publication of WO2017002222A1 publication Critical patent/WO2017002222A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]

Definitions

  • the present invention relates to cloud computing technology.
  • the present invention relates to a technology for building a business system composed of a plurality of computer resources on a cloud environment.
  • cloud 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • CRM Customer Relationship Management
  • 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.
  • 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.
  • 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
  • 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.
  • 521 represents the requirements for the LB
  • 522 represents the requirements for the Web server
  • 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.
  • “Linux (registered trademark)” 542 is set as an OS, and “HPProxy” 541 is installed as middleware for load distribution.
  • “Linux” 553 is set as an OS
  • “P-Lang” 552 is set as a language processing system thereon
  • “SgCRM” 551 is installed as an application. It is set as follows.
  • VLinux is set as an OS
  • PgDB database management middleware
  • 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.
  • description of the corresponding parts in FIG. 5a and FIG. 5b is shown by adding “c” to the end of the corresponding part.
  • 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.
  • 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.
  • 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.
  • 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.
  • HA high availability
  • 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.
  • “$” is added before the variable name such as “$ x”, it means that the variable is referred to.
  • “Scalable ⁇ x ⁇ - ⁇ y ⁇ ” within the requirement of ID “7” corresponds to a description such as “Scalable 2-4”.
  • x is 2 and y is 4, and is referred to by “$ xVM” of the mounting method 605 with the same ID “7”.
  • “$ xVM” is interpreted as “2VM”.
  • 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.
  • 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.
  • 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.
  • 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.
  • a mounting method is searched for each requirement.
  • step 704 the selected node is converted by the determined mounting method.
  • 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.
  • Step 707 Steps 702-706 are executed for all nodes.
  • the node 501 indicating the LB is selected from the nodes 501, 502, and 503 in the selected system template (step 702).
  • 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).
  • 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).
  • 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).
  • step 707 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).
  • Step 702 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.
  • 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).
  • 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.
  • step 708 an item registered in the edge update list is referred to and one unprocessed item is selected.
  • step 709 the edge is converted according to the referenced item.
  • Step 710 Steps 708 to 709 are executed for all items in the edge update list, and the system configuration conversion process is completed.
  • registration to the edge update list is performed in the conversion process (step 704) between the node 501 and the node 503.
  • each DB configured with two VMs connects with all Web servers configured with two VMs. So that the edges are transformed.
  • 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.
  • 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.
  • a predetermined policy for example, “prioritize cost reduction”, “prioritize high reliability”, and the like are assumed.
  • 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.
  • 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.
  • 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.
  • 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.
  • the ID “4” of the system configuration conversion information 212 is applied.
  • the ID “5” having a lower availability requirement is used. Is selected, and the mounting method “[ELB]” is applied.
  • 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.
  • the ID “8” of the system configuration conversion information 212 is applied.
  • “Perf” is not imposed as the performance requirement.
  • the mounting method ID “11” is selected, and the mounting method “1VM” is applied.
  • the performance of the business system can be adjusted according to the mode of the business system without manually processing the template.
  • 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.
  • step 1001 the system deployment engine 102 receives a system template selected from the system template information 212.
  • step 1002 the system deployment engine 102 receives the use cloud selected for each node in the received template.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Inter-Cloud Network corresponding to the exit of each cloud
  • 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.
  • 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.
  • 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.
  • Step 1008 network settings between the clouds are performed so that servers arranged on different clouds can communicate with each other via ICN.
  • 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.
  • 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.
  • the communication here is not limited to communication by a business application on a business system.
  • 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
  • an edge 1222 is an edge indicating a network connection between the DB server and the “Hit” ICN 1202.
  • 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.
  • a business system can be constructed across multiple clouds.
  • 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
  • the cloud may be connected to the outside using ICN.
  • 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.
  • 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.
  • the constructed business system can use the functions of the system existing outside the cloud of the construction destination.
  • System builder 102 System deployment engine 103: Resource pool 104: Cloud management API 105: End user

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

Le dispositif de déploiement de système de la présente invention comprend : une base de données de modèles stockant un premier modèle contenant des informations sur un serveur appartenant à un système d'entreprise ; et une base de données d'informations de conversion de configuration stockant une liste d'informations de conversion de configuration dans laquelle est écrit un procédé de mise en œuvre pour la réalisation, sur un nuage, d'une fonction du serveur. Le dispositif de déploiement de système reçoit des informations spécifiant le premier modèle et des informations spécifiant le type de nuage sur lequel le système d'entreprise doit être construit, recherche dans la liste d'informations de conversion de configuration le procédé de mise en œuvre de serveur d'après les informations reçues, crée un deuxième modèle contenant les détails du procédé de mise en œuvre obtenu sous la forme d'un impact, et construit le système d'entreprise sur un nuage du type spécifié d'après le deuxième modèle. Selon la présente invention, un système d'entreprise peut être construit à partir d'un modèle de système prédéterminé, indépendamment du type de nuage sur lequel le système d'entreprise doit être construit.
PCT/JP2015/068935 2015-07-01 2015-07-01 Dispositif de déploiement de système et procédé de déploiement de système WO2017002222A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/068935 WO2017002222A1 (fr) 2015-07-01 2015-07-01 Dispositif de déploiement de système et procédé de déploiement de système

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/068935 WO2017002222A1 (fr) 2015-07-01 2015-07-01 Dispositif de déploiement de système et procédé de déploiement de système

Publications (1)

Publication Number Publication Date
WO2017002222A1 true WO2017002222A1 (fr) 2017-01-05

Family

ID=57609491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/068935 WO2017002222A1 (fr) 2015-07-01 2015-07-01 Dispositif de déploiement de système et procédé de déploiement de système

Country Status (1)

Country Link
WO (1) WO2017002222A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018173698A1 (fr) * 2017-03-22 2018-09-27 Kddi株式会社 Système de surveillance, support de stockage lisible par ordinateur et procédé de surveillance
CN110262351A (zh) * 2019-07-02 2019-09-20 许昌许继电科储能技术有限公司 一种组态方法
JP2021522628A (ja) * 2018-04-18 2021-08-30 アイボス・インコーポレイテッド ハイブリッドクラウドコンピューティングネットワーク管理
US11329846B2 (en) 2019-02-14 2022-05-10 Mitsubishi Electric Corporation Data processing device and data processing system
WO2022123843A1 (fr) * 2020-12-10 2022-06-16 株式会社日立製作所 Système de commande de déploiement

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010198529A (ja) * 2009-02-27 2010-09-09 Nec Corp 実システムメモリ使用量概算方法及び装置
JP2014532247A (ja) * 2011-10-11 2014-12-04 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ 容易にクラウド化可能なアプリケーションの発見型の識別および移行
JP2015125701A (ja) * 2013-12-27 2015-07-06 株式会社日立製作所 システム構成案生成方法および設計支援装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010198529A (ja) * 2009-02-27 2010-09-09 Nec Corp 実システムメモリ使用量概算方法及び装置
JP2014532247A (ja) * 2011-10-11 2014-12-04 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ 容易にクラウド化可能なアプリケーションの発見型の識別および移行
JP2015125701A (ja) * 2013-12-27 2015-07-06 株式会社日立製作所 システム構成案生成方法および設計支援装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
RYUTARO YAGUCHI: "TREND: Multi Cloud Kanri Tool Fukusu Cloud ni Tomonau Futatsu no Mondai", NIKKEI SYSTEMS, vol. 232, 26 July 2012 (2012-07-26), pages 12 - 13, ISSN: 1881-1620 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018173698A1 (fr) * 2017-03-22 2018-09-27 Kddi株式会社 Système de surveillance, support de stockage lisible par ordinateur et procédé de surveillance
JP2018160020A (ja) * 2017-03-22 2018-10-11 Kddi株式会社 監視システム、プログラムおよび監視方法
JP2021522628A (ja) * 2018-04-18 2021-08-30 アイボス・インコーポレイテッド ハイブリッドクラウドコンピューティングネットワーク管理
JP7277563B2 (ja) 2018-04-18 2023-05-19 アイボス・インコーポレイテッド ハイブリッドクラウドコンピューティングネットワーク管理
US11818200B2 (en) 2018-04-18 2023-11-14 Iboss, Inc. Hybrid cloud computing network management with synchronization features across different cloud service providers
US11329846B2 (en) 2019-02-14 2022-05-10 Mitsubishi Electric Corporation Data processing device and data processing system
CN110262351A (zh) * 2019-07-02 2019-09-20 许昌许继电科储能技术有限公司 一种组态方法
WO2022123843A1 (fr) * 2020-12-10 2022-06-16 株式会社日立製作所 Système de commande de déploiement

Similar Documents

Publication Publication Date Title
US10749740B2 (en) Deploying network-based cloud platforms on end equipment
JP6291134B2 (ja) サーバ選択装置、サーバ選択方法及びサーバ選択プログラム
JP5976946B2 (ja) 仮想マシンテストシステム、仮想マシンテスト方法
JP4701220B2 (ja) ビジネスプロセス再構成方法、そのプログラム及び計算機
WO2017002222A1 (fr) Dispositif de déploiement de système et procédé de déploiement de système
CN104410672B (zh) 网络功能虚拟化应用升级的方法、转发业务的方法及装置
US9712463B1 (en) Workload optimization in a wide area network utilizing virtual switches
US9246765B2 (en) Apparatus and methods for auto-discovery and migration of virtual cloud infrastructure
EP4231166A1 (fr) Réseau virtuel, permutation à chaud, mise à l'échelle à chaud et reprise après sinistre pour conteneurs
CN105791344B (zh) 灰度发布业务处理的方法、系统、负载均衡器及服务总线装置
US20140280805A1 (en) Two-Sided Declarative Configuration for Cloud Deployment
JP6424823B2 (ja) 情報処理装置、及び、システム設計支援方法
US20130232470A1 (en) Launching an application stack on a cloud platform environment
CN104220988A (zh) 云服务器中的层3服务实现和方法
US20110258620A1 (en) Method and Apparatus for Making a BPM Application Available to Multiple Tenants
CN110601994B (zh) 云环境下微服务链感知的负载均衡方法
JP2012048330A (ja) クラスタシステムおよびソフトウェアデプロイ方法
US20080282242A1 (en) Simulation management within a grid infrastructure
CN113612688B (zh) 分布式软件定义网络控制系统及其构建方法
WO2017127225A1 (fr) Réseau virtuel, permutation à chaud, mise à l'échelle à chaud et reprise sur sinistre pour des conteneurs
JP6801776B2 (ja) 仮想ネットワーク機能管理装置、仮想インフラストラクチャ管理装置、及び仮想ネットワーク機能構築方法
US20230418681A1 (en) Intelligent layer derived deployment of containers
JP6542865B2 (ja) インタフェース集約装置及びインタフェース管理方法
JP6947129B2 (ja) 管理装置およびネットワーク管理方法
JP2015153259A (ja) コンピュータリソース管理装置、コンピュータリソース管理方法及びコンピュータリソース管理プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15897149

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15897149

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP