WO2013183249A1 - 配備装置、及び、配備方法 - Google Patents
配備装置、及び、配備方法 Download PDFInfo
- Publication number
- WO2013183249A1 WO2013183249A1 PCT/JP2013/003346 JP2013003346W WO2013183249A1 WO 2013183249 A1 WO2013183249 A1 WO 2013183249A1 JP 2013003346 W JP2013003346 W JP 2013003346W WO 2013183249 A1 WO2013183249 A1 WO 2013183249A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- module
- deployment
- confirmation
- normality
- configuration information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Definitions
- the present invention relates to a program deployment apparatus and a deployment method.
- an environment for executing a service application may be manually configured.
- the developer of the service application creates a work procedure for constructing the execution environment as a construction procedure manual, and the construction staff deploys various modules such as OS (Operating System), middleware, and related libraries according to the procedure manual. After setting, deploy and set the developed application module. Then, the construction staff checks whether the execution environment has been constructed normally by visually checking the logs and files related to the deployed modules and other outputs according to the confirmation items described in the construction procedure. Confirm.
- Non-Patent Document 1 discloses a method for constructing an execution environment using an orchestration tool.
- the orchestration tool constructs an execution environment according to a workflow described individually for each system. Then, the orchestration tool confirms whether or not the execution environment is normally constructed according to the procedure described in the workflow.
- Patent Document 1 discloses a technique for inserting a probe for confirming the normality of an operating system for each component constituting the system.
- Non-Patent Document 1 When the system is constructed with an orchestration tool as in Non-Patent Document 1 described above, the developer needs to define the procedure for confirming the normality of the system as part of the workflow for each system. is there. For this reason, when it is necessary to construct many different types of systems, or when the system to be constructed is a complex system composed of many modules, the burden on the developer for generating a workflow increases. .
- An object of the present invention is to provide a deployment apparatus and a deployment method that can solve the above-described problems and can more efficiently check the normality of the system at the time of system construction.
- a deployment apparatus is a PF confirmation module for confirming the normality of deployment of a platform (PF) module, which is another module on which the module depends, in association with an identifier of a module constituting the system.
- Configuration information storage means for storing configuration information including at least one of PF confirmation information including the identifier of the module, self-confirmation information including the identifier of the self-confirmation module for confirming the normality of the module deployment, , Referring to the configuration information, confirming the normality of deployment of the PF module by the PF confirmation module on the processing device before deployment of the module to the processing device, and applying the module to the processing device. Deployment of the module by the self-confirmation module on the processing device after deployment Provided confirmation of normality and, and a normality confirmation means for performing at least one of.
- a deployment method includes a PF confirmation module for confirming normality of deployment of a platform (PF) module, which is another module on which the module depends, in association with an identifier of a module constituting the system.
- the normality of the deployment of the platform (PF) module is associated with the identifier of the module constituting the system.
- Configuration information including at least one of PF confirmation information including an identifier of a PF confirmation module for confirming the self-confirmation information including an identifier of a self-confirmation module for confirming normality of the module deployment
- PF confirmation information including an identifier of a PF confirmation module for confirming the self-confirmation information including an identifier of a self-confirmation module for confirming normality of the module deployment
- the effect of the present invention is that the normality of the system at the time of system construction can be confirmed more efficiently.
- FIG. 2 is a block diagram showing a configuration of the deployment system in the first exemplary embodiment of the present invention.
- the deployment system includes a development environment 1, an external repository 2, a deployment device 100, and a processing device 200.
- the deployment apparatus 100 constructs a system by deploying program modules (hereinafter referred to as modules) such as an OS, middleware (MW), and application (AP) that constitute the IT system to the processing apparatus 200.
- modules program modules
- MW middleware
- AP application
- deployment refers to transmitting a module to the processing apparatus 200 and installing the module by an installation program in the processing apparatus 200.
- the deployment device 100 deploys each module to the processing device 200 according to the dependency described in the configuration information 300 of each module.
- FIG. 3 is a diagram showing an example of dependency between modules in the first embodiment of the present invention.
- rectangles indicate modules, and arrows between the rectangles indicate dependency relationships.
- the module indicated by the arrow is provided in the processing apparatus 200. That is, the original module of the arrow depends on the module at the end of the arrow.
- the module “AP1” depends on the modules “Tomcat” and “PostgreSQL”, and the module “Tomcat” depends on the module “Java (registered trademark)”.
- the module at the end of the arrow is referred to as a platform (PF) module for the original module at the arrow, or a lower module, and the original module at the arrow is referred to as an upper module for the module at the end of the arrow.
- PF platform
- a module group obtained by tracing a PF module from a certain module is called a platform of the module.
- the order in which the modules are deployed is determined so that the PF modules on which the modules depend are deployed in the processing apparatus 200 first.
- the deployment apparatus 100 includes a module management unit 101, a module storage unit 102, a configuration information management unit 103, a configuration information storage unit 104, a deployment unit 105, a normality confirmation unit 106, and a construction request input unit 107.
- the module management unit 101 acquires modules necessary for constructing the system from the development environment 1 and the external repository 2 and stores them in the module storage unit 102.
- the module management unit 101 acquires an AP module from the development environment 1 and acquires a module common to a plurality of systems, such as an OS module and an MW module, from the external repository 2.
- the configuration information management unit 103 acquires the configuration information 300 of each module from the development environment 1 or the external repository 2 and stores it in the configuration information storage unit 104.
- FIGS 4 and 5 are diagrams showing examples of the configuration information 300 in the first embodiment of the present invention.
- the configuration information 300 is set for each module.
- the configuration information 300 includes module information 310, one or more PF module information 320, and self-confirmation information 330.
- the module information 310 includes a module identifier 311 and a file identifier 312 of the module (deployment target module) indicated by the module identifier 311.
- the file identifier 312 may be a package file identifier.
- the PF module information 320 includes a PF module identifier 321 that is an identifier of the PF module for the deployment target module, and PF confirmation information 322.
- the PF confirmation information 322 includes a module type 323 of a PF confirmation module and a file identifier 324.
- the PF confirmation module is a module (program or script) used to confirm the normality of the deployment of the PF module before the deployment target module is deployed, and is deployed and executed on the PF module or the OS.
- the module type 323 of the PF confirmation module is “deploy”, the PF confirmation module is deployed on the PF module.
- the module type 323 is “standalone”, the PF confirmation module is directly deployed on the OS.
- the PF confirmation module confirms the normality of PF module deployment based on, for example, the presence or absence of a predetermined file generated when the PF module is deployed or a predetermined process to be activated.
- the PF confirmation module may confirm the normality based on the presence or absence of a predetermined character string in a log generated by the OS or the like when the PF module is deployed.
- the PF confirmation module may call a predetermined function or API (Application Program Interface) of the PF module and confirm the normality of the PF module deployment depending on whether a predetermined return value is obtained. Furthermore, the PF confirmation module may give a predetermined script and data to the PF module and confirm the normality of the deployment of the PF module depending on whether a predetermined result is obtained.
- API Application Program Interface
- PF confirmation module may perform the above-described confirmation of files, processes, functions, APIs, and the like used by the deployment target module.
- the self-confirmation information 330 includes a module type 331 and a file identifier 332 of the self-confirmation module.
- the self-confirmation module is a module (program or script) used to confirm the normality of deployment of the deployment target module after the deployment target module is deployed, and is deployed and executed on the deployment target module or OS. .
- the module type 331 of the self-confirmation module is “deploy”, the self-confirmation module is deployed on the deployment target module.
- the module type 331 is “standalone”, the self-confirmation module is directly deployed on the OS.
- the self-confirmation module normally detects the deployment of the deployment target module based on the presence or absence of a predetermined file generated when the deployment target module is deployed or a predetermined process to be activated. Check sex.
- the self-confirmation module may confirm normality based on the presence or absence of a predetermined character string in a log generated by the OS or the like when the deployment target module is deployed.
- the self-confirmation module like the PF confirmation module, calls the predetermined function or API of the deployment target module and confirms the normality of the deployment of the deployment target module depending on whether a predetermined return value is obtained. Good. Furthermore, the self-confirmation module may confirm the normality of the deployment of the deployment target module by giving a predetermined script and data to the deployment target module and obtaining a predetermined result.
- 4 is configuration information 300 related to the AP module having the module identifier 311 “AP1”.
- a PF module whose PF module identifier 321 is “Tomcat” and “PostgreSQL” is required.
- the normality of the deployment of the PF modules “Tomcat” and “PostgreSQL” is confirmed by the PF confirmation modules of the file identifiers 324 “Pf4AP1.war” and “PSQLAP1.sql”, respectively.
- the normality of the deployment of the module “AP1” is confirmed by the self-confirmation module having the file identifier 332 “Ap1self”.
- each module generates a PF confirmation module and a self-confirmation module related to the module in advance, and sets the type and file identifier of these modules as the PF confirmation information 322 in the module configuration information 300 and the self-confirmation module. Each is set in the confirmation information 330.
- the module management unit 101 acquires the generated PF confirmation module and the self-confirmation module from the development environment 1 or the external repository 2 and stores them in the module storage unit 102. Further, the configuration information management unit 103 acquires the generated configuration information 300 from the development environment 1 or the external repository 2 and stores it in the configuration information storage unit 104.
- the configuration information 300 may be described in other formats such as XML (Extensible Markup Language). If there is no PF module on which the deployment target module depends, the PF module information 320 may not be set. Further, when it is not necessary to confirm the normality of the deployment of the PF module or the deployment target module, the PF confirmation information 322 and the self-confirmation information 330 may not be set.
- XML Extensible Markup Language
- the deployment unit 105 includes a provisioning unit 108, an AP module deployment unit 109, an MW deployment unit 110, an OS deployment unit 111, a virtual machine (VM) deployment unit 112, and a network (NW) deployment unit 113.
- the provisioning unit 108 deploys each module to the processing device 200 based on the configuration information 300 of each module that configures the system.
- the provisioning unit 108 uses the VM deployment unit 112 and the NW deployment unit 113 to generate the virtual server 202 for constructing the system on the processing device 200.
- the provisioning unit 108 deploys each module to the generated virtual server 202 using the AP module deployment unit 109, the MW deployment unit 110, and the OS deployment unit 111.
- the normality confirmation unit 106 confirms the normality of the PF module deployment by the PF confirmation module and the normality of the deployment target module deployment by the self-confirmation module.
- the construction request input unit 107 receives a system construction request input from a user or the like.
- the processing device 200 is, for example, a computer including a basic OS having a communication function, an installation program, and the like.
- the processing device 200 includes a virtualization platform 201 such as a VM monitor or a hypervisor.
- the virtualization infrastructure 201 generates a virtual server 202 in response to a request from the deployment unit 105, and deploys each module received from the deployment unit 105 to the generated virtual server 202.
- the virtual server 202 executes processing for each deployed module.
- the deployment device 100 may be a computer that includes a CPU (Central Processing Unit) and a storage medium that stores a program, and operates by control based on the program.
- the module storage unit 102 and the configuration information storage unit 104 may be configured as individual storage media or a single storage medium.
- FIG. 6 is a diagram showing an outline of the normality confirmation method in the first embodiment of the present invention.
- the normality confirmation unit 106 refers to the configuration information 300 of the deployment target module, deploys the PF confirmation module acquired from the module storage unit 102 to the processing apparatus 200, and confirms the normality of the deployment of the PF module (state 2) .
- the provisioning unit 108 refers to the configuration information 300 and deploys the deployment target module acquired from the module storage unit 102 to the processing device 200 (state 3).
- the normality confirmation unit 106 refers to the configuration information 300, deploys the self-confirmation module acquired from the module storage unit 102 to the processing device 200, and confirms the normality of deployment of the deployment target module (state 4).
- the module group below the deployment target module is set as a new platform (state 5), and the upper module of the deployment target module is deployed.
- the deployment target module before the deployment target module is deployed.
- the confirmation of the normality of the deployment of the PF module from the viewpoint and the confirmation of the normality of the deployment of the deployment target module from the viewpoint of the deployment target module after the deployment of the deployment target module are repeated.
- FIG. 8 is a flowchart showing system construction processing in the first exemplary embodiment of the present invention.
- the construction request input unit 107 receives an input of a system construction request in which a construction target system is designated from a user or the like (step S11).
- the construction target system is specified by, for example, an identifier of an AP module that is the highest module of the system.
- the construction request input unit 107 receives the identifier “AP1” of the AP module of the construction target system.
- the provisioning unit 108 generates a construction list (step S12).
- FIG. 7 is a diagram showing an example of a construction list in the first embodiment of the present invention.
- the construction list is a list in which configuration information 300 of modules to be deployed in system construction is arranged in the order of deployment.
- FIG. 9 is a flowchart showing details of the construction list generation process (step S12) in the first embodiment of the present invention.
- the configuration information 300 associated with the dependency relationship is regarded as a directed graph, and a construction list is generated based on a topological sort algorithm in graph theory.
- the provisioning unit 108 initializes the construction list (step S1201).
- the provisioning unit 108 acquires the configuration information 300 of the AP module specified in step S11 from the configuration information storage unit 104.
- the provisioning unit 108 recursively repeats the acquisition of the configuration information 300 of the PF module specified by the PF module identifier 321, thereby identifying the module to be deployed and extracting the configuration information 300 of each module (step) S1202).
- the dependency between modules does not constitute a cross-reference or a cycle.
- the provisioning unit 108 recursively acquires the PF module identifier 321 from the configuration information 300 (FIG. 4) of “AP1”, and deploys the modules “AP1”, “Tomcat”, “PostgreSQL”, and “Java”.
- the module is specified as a power module, and the configuration information 300 of each module is acquired.
- the provisioning unit 108 selects one of the acquired configuration information 300 (step S1203), designates the selected configuration information 300, and executes node processing to be described later (step S1204).
- the provisioning unit 108 repeats steps S1203 and S1204 for all the configuration information 300 extracted in step S1202 (step S1205).
- the provisioning unit 108 designates the configuration information 300 of each of the modules “AP1”, “Tomcat”, “PostgreSQL”, and “Java”, and executes node processing.
- FIG. 10 is a flowchart showing details of the node processing (step S1204) in the first embodiment of the present invention.
- the provisioning unit 108 determines whether the designated configuration information 300 has been processed (step S12041). When the designated configuration information 300 has been processed (step S12041 / Y), the provisioning unit 108 ends the process. When the designated configuration information 300 has not been processed (step S12041 / N), the provisioning unit 108 sets the designated configuration information 300 to processed (step S12042). The provisioning unit 108 extracts all the PF module identifiers 321 in the designated configuration information 300 (step S12043).
- step S12044 / N the provisioning unit 108 proceeds to the process of step S12048.
- the provisioning unit 108 selects one of the extracted PF modules and acquires the configuration information 300 of the PF module (step S12045).
- the provisioning unit 108 designates the acquired configuration information 300 and recursively executes node processing (step S12041 ⁇ ) (step S12046).
- the provisioning unit 108 repeats steps S12045 and S12046 for all the PF modules extracted in step S12043 (step S12047).
- the provisioning unit 108 adds the specified configuration information 300 to the construction list (step S12048).
- step S1204 the configuration information 300 (FIG. 4) of the module “AP1” is designated and the node process is executed.
- the provisioning unit 108 sets the configuration information 300 of the module “AP1” as processed.
- the provisioning unit 108 extracts the PF module identifiers 321 “Tomcat” and “PostgreSQL” from the configuration information 300 of the module “AP1”.
- the provisioning unit 108 designates the configuration information 300 (FIG. 5) of the module “Tomcat” and executes node processing.
- the provisioning unit 108 sets the configuration information 300 of the module “Tomcat” as processed.
- the provisioning unit 108 extracts the PF module identifier 321 “Java” from the configuration information 300 of the module “Tomcat”.
- the provisioning unit 108 specifies a module “Java” and executes node processing.
- the provisioning unit 108 sets the configuration information 300 of the module “Java” as processed.
- the PF module information 320 is not set in the configuration information 300 of the module “Java”. Since the PF module identifier 321 does not exist in the configuration information 300 of the module “Java”, the provisioning unit 108 adds the configuration information 300 of the module “Java” to the top of the construction list.
- the provisioning unit 108 adds the configuration information 300 of the module “Tomcat” to the construction list.
- the provisioning unit 108 specifies a module “PostgreSQL” and executes node processing.
- the provisioning unit 108 sets the configuration information 300 of the module “PostgreSQL” to processed.
- the PF module information 320 is not set in the configuration information 300 of the module “PostgreSQL”. Since the PF module identifier 321 does not exist in the configuration information 300 of the module “PostgreSQL”, the provisioning unit 108 adds the configuration information 300 of the module “PostgreSQL” to the construction list.
- the provisioning unit 108 adds the configuration information 300 of the module “AP1” to the construction list.
- step S1204 the configuration information 300 of each of the modules “Tomcat”, “PostgreSQL”, and “Java” is specified and the node process is executed. However, the configuration information 300 has already been processed. Therefore, the construction list does not change.
- step S12 a configuration list in which configuration information 300 is arranged in the order of modules “Java”, “Tomcat”, “PostgreSQL”, and “AP1” as shown in FIG. Generated.
- a construction list is generated by another method, such as using another algorithm for topological sorting. Also good.
- the provisioning unit 108 requests the virtualization platform 201 to generate the virtual server 202 for constructing the system via the VM deployment unit 112 and the NW deployment unit 113 (step S13). .
- step S15 the provisioning unit 108 outputs a “construction error” (step S15) and ends the process.
- the provisioning unit 108 acquires one configuration information 300 from the top of the generated construction list (step S16), and specifies the acquired configuration information 300. Then, module deployment processing described later is executed (step S17). When the module deployment process ends, the provisioning unit 108 determines whether or not the module deployment process has ended normally (step S18).
- step S15 the provisioning unit 108 outputs a “construction error” (step S15) and ends the process.
- the provisioning unit 108 repeats steps S16 to S18 for all the configuration information 300 included in the construction list (step S19).
- the provisioning unit 108 outputs “construction normal termination” (step S20) and ends the processing.
- the provisioning unit 108 specifies the configuration information 300 of each of the modules “Java”, “Tomcat”, “PostgreSQL”, and “AP1” included in the construction list in FIG. Execute.
- FIG. 11 is a flowchart showing details of module deployment processing (step S17) in the first embodiment of the present invention.
- the normality confirmation unit 106 extracts all the PF confirmation information 322 from the designated configuration information 300 (step S1701).
- step S1702 / N the normality confirmation unit 106 proceeds to the process of step S1708.
- the normality confirmation unit 106 selects one of the extracted PF confirmation information 322 (step S1703).
- the normality confirmation unit 106 acquires the file of the PF confirmation module indicated by the file identifier 324 in the selected PF confirmation information 322 from the module storage unit 102.
- the normality confirmation unit 106 deploys a PF confirmation module to the processing apparatus 200 via the deployment units 109 to 111 and instructs execution thereof (step S1704).
- the normality confirmation unit 106 cancels (uninstalls) the deployment of the PF confirmation module (step S1705).
- the normality confirmation unit 106 When the normality of the PF module deployment cannot be confirmed as a result of the execution of the PF confirmation module (step S1706 / N), the normality confirmation unit 106 outputs an error (step S1713) and ends the process.
- the normality confirmation unit 106 repeats steps S1703 to S1706 for all the PF confirmation information 322 extracted in step S1701 (step S1707).
- the provisioning unit 108 extracts module information 310 from the configuration information 300.
- the provisioning unit 108 acquires the deployment target module file indicated by the file identifier 312 of the module information 310 from the module storage unit 102.
- the provisioning unit 108 deploys the deployment target module to the processing apparatus 200 via the deployment units 109 to 111 (step S1708).
- the normality confirmation unit 106 extracts the self-confirmation information 330 from the configuration information 300 (step S1709).
- the normality confirmation unit 106 acquires the file of the self-confirmation module indicated by the file identifier 332 in the extracted self-confirmation information 330 from the module storage unit 102.
- the normality confirmation unit 106 deploys the self-confirmation module to the processing apparatus 200 via the deployment units 109 to 111, and instructs execution thereof (step S1710).
- the normality confirmation unit 106 cancels (uninstalls) the deployment of the self-confirmation module (step S1711).
- the normality confirmation unit 106 outputs a “deployment error” (step S1713), and performs processing. finish.
- the normality confirmation unit 106 outputs “deployment normal end” (step S1714), and ends the process.
- the normality confirmation unit 106 acquires the file “Pf4Tomcat” of the PF confirmation module indicated by the file identifier 324 of the PF confirmation information 322 and deploys it to the processing apparatus 200.
- the normality confirmation unit 106 confirms the normality of deployment of the PF module “Java” by executing the PF confirmation module.
- the normality confirmation unit 106 transmits the file “apache-tomcat-6.0.35.tgz” of the deployment target module indicated by the file identifier 312 of the module information 310. Obtaining and deploying the deployment target module “Tomcat” to the processing device 200 using the file. Further, the normality confirmation unit 106 acquires the file “Tomcatself” of the self-confirmation module indicated by the file identifier 332 of the self-confirmation information 330 and deploys it to the processing device 200. The normality confirmation unit 106 confirms the normality of deployment of the deployment target module “Tomcat” by executing the self-confirmation module. When the deployment target module “Tomcat” is normally deployed, the normality confirmation unit 106 outputs “deployment normal end”.
- the normality confirmation unit 106 acquires the file “Pf4AP1.war” of the PF confirmation module indicated by the file identifier 324 of the PF confirmation information 322 and deploys it to the processing apparatus 200.
- the normality confirmation unit 106 confirms the normality of deployment of the PF module “Tomcat” by executing the PF confirmation module.
- the normality confirmation unit 106 acquires the file “PSSQL4AP1.sql” of the PF confirmation module indicated by the file identifier 324 of the PF confirmation information 322 and deploys it to the processing apparatus 200.
- the normality confirmation unit 106 confirms the normality of deployment of the PF module “PostgreSQL” by executing the PF confirmation module.
- the normality confirmation unit 106 acquires the file “ap1Module.war” of the deployment target module indicated by the file identifier 312 of the module information 310, and The deployment target module “AP1” is deployed to the processing apparatus 200 using the file.
- the normality confirmation unit 106 acquires the file “AP1self” of the self-confirmation module indicated by the file identifier 332 of the self-confirmation information 330 and deploys it to the processing device 200.
- the normality confirmation unit 106 confirms the normality of the deployment of the deployment target module “AP1” by executing the self-confirmation module.
- the normality confirmation unit 106 outputs “deployment normal end”.
- the provisioning unit 108 outputs “construction normal end” when the deployment process is normally completed for all modules “Java”, “Tomcat”, “PostgreSQL”, and “AP1”.
- FIG. 1 is a block diagram showing a characteristic configuration of the first embodiment of the present invention.
- the deployment device 100 includes a configuration information storage unit 104 and a normality confirmation unit 106.
- the configuration information storage unit 104 associates the identifier of the module constituting the system with the identifier of the PF confirmation module for confirming the normality of the deployment of the platform (PF) module which is another module on which the module depends.
- the configuration information 300 including at least one of the PF confirmation information 322 including the self-confirmation information 330 including the identifier of the self-confirmation module for confirming the normality of the module deployment is stored.
- the normality confirmation unit 106 refers to the configuration information 300, confirms the normality of the PF module deployment by the PF confirmation module on the processing apparatus 200 and deploys the module to the processing apparatus before the module is deployed to the processing apparatus. After the deployment, at least one of confirmation of the normality of module deployment by the self-confirmation module on the processing apparatus 200 is performed.
- the normality of the system at the time of system construction can be confirmed more efficiently.
- the configuration information 300 of the modules constituting the system includes the identifiers of the PF confirmation module and the self-confirmation module, and the normality confirmation unit 106 uses the PF confirmation module in the deployment of each module constituting the system. This is because the normality of the PF module deployment is confirmed and the normality of the deployment of the deployment target module by the self-confirmation module is confirmed. As a result, it is not necessary to define a procedure for confirming normality for each system to be built, and the burden on the developer is reduced.
- the normality confirmation unit 106 confirms the normality of the deployment of the PF module and the normality of the deployment of the deployment target module in the deployment of each module constituting the system. It is. This makes it easy to identify which module has failed to deploy. This also makes it easy to identify whether the cause of deployment failure is due to the PF module or the deployment target module.
- the normality of the deployment of the PF module and the normality of the deployment of the deployment target module are confirmed in the deployment of each module constituting the system. For this reason, although the reliability of the constructed system is improved, it takes time to construct the system.
- the second embodiment of the present invention it is determined whether to check the normality of the deployment of the PF module and the normality of the deployment of the deployment target module according to the importance and the reliability threshold. In this respect, it differs from the first embodiment of the present invention.
- the configuration of the second embodiment of the present invention is the same as the configuration of the first embodiment of the present invention (FIG. 2).
- FIG. 12 is a diagram showing an example of the configuration information 300 in the second embodiment of the present invention.
- the PF confirmation information 322 includes the importance 325 in addition to the module type 323 of the PF confirmation module and the file identifier 324.
- the importance 325 indicates the importance of checking the normality of the PF module deployment.
- the self-confirmation information 330 includes the importance 333 in addition to the self-confirmation module type 331 and the file identifier 332.
- the importance level 333 indicates the importance level of the normality confirmation of the deployment of the deployment target module. Here, it is assumed that the importance is higher as the values of the importance 325 and the importance 333 are larger.
- the normality confirmation unit 106 determines whether to confirm the normality of the PF module deployment according to the importance 325 and the reliability threshold. Further, the normality confirmation unit 106 determines whether to confirm the normality of the deployment of the deployment target module according to the importance 333 and the reliability threshold.
- a reliability threshold is specified in addition to the identifier of the AP module in the system construction request from the user or the like.
- the normality confirmation unit 106 compares the importance 325 in the selected PF confirmation information 322 with the reliability threshold value. When the importance 325 is equal to or higher than the reliability threshold, the normality confirmation unit 106 performs normality confirmation of the PF module deployment by the PF confirmation module (steps S1704 to S1706). Are omitted.
- the normality confirmation unit 106 compares the importance 333 in the extracted self-confirmation information 330 with the reliability threshold value. Then, when the importance 333 is equal to or higher than the reliability threshold, the normality confirmation unit 106 performs normality confirmation of the deployment target module by the self-confirmation module (steps S1710 to S1712), and is less than the reliability threshold. If this is the case, omit it.
- the system construction time can be shortened as compared with the first embodiment of the present invention.
- the reason is that the normality confirmation unit 106 compares the importance of normality confirmation with the reliability threshold to confirm the normality of the PF module deployment and the normality of the deployment of the deployment target module. This is to determine whether or not to confirm.
- confirmation of the normality of the deployment can be omitted, and the system construction time can be shortened.
- the normality of deployment can be confirmed for the minimum module by increasing the reliability threshold, and the system can be constructed at high speed.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
次に、本発明の第1の実施の形態について説明する。
次に、本発明の第2の実施の形態について説明する。
2 外部レポジトリ
100 配備装置
101 モジュール管理部
102 モジュール記憶部
103 構成情報管理部
104 構成情報記憶部
105 配備部
106 正常性確認部
107 構築要求入力部
108 プロビジョニング部
109 APモジュール配備部
110 MW配備部
111 OS配備部
112 VM配備部
113 NW配備部
200 処理装置
201 仮想化基盤
202 仮想サーバ
300 構成情報
310 モジュール情報
311 モジュール識別子
312 ファイル識別子
320 PFモジュール情報
321 PFモジュール識別子
322 PF確認情報
323 モジュール種別
324 ファイル識別子
325 重要度
330 自己確認情報
331 モジュール種別
332 ファイル識別子
333 重要度
Claims (11)
- システムを構成するモジュールの識別子に対応付けて、当該モジュールが依存する他のモジュールであるプラットフォーム(PF)モジュールの配備の正常性を確認するためのPF確認モジュールの識別子を含むPF確認情報と、前記モジュールの配備の正常性を確認するための自己確認モジュールの識別子を含む自己確認情報と、の内の少なくとも一方を含む構成情報を記憶する構成情報記憶手段と、
前記構成情報を参照し、前記モジュールの処理装置への配備前における、前記処理装置上での前記PF確認モジュールによる前記PFモジュールの配備の正常性の確認と、前記モジュールの前記処理装置への配備後における、前記処理装置上での前記自己確認モジュールによる前記モジュールの配備の正常性の確認と、の内の少なくとも一方を行う正常性確認手段と、を備える配備装置。 - さらに、前記モジュールを前記処理装置に配備する配備手段を備える請求項1に記載の配備装置。
- 前記構成情報記憶手段は、前記システムを構成する複数の前記モジュールの各々の識別子に対応付けて、前記構成情報を記憶し、
前記構成情報は、さらに、前記PFモジュールの識別子を含み、
前記配備手段は、前記複数の前記モジュールの各々の前記構成情報を参照し、前記複数の前記モジュールの各々の前記PFモジュールが当該モジュールよりも前に前記処理装置に配備されるように前記複数の前記モジュールの配備の順序を決定し、当該決定した順序に従って前記複数の前記モジュールの各々を配備し、
前記正常性確認手段は、前記複数の前記モジュールの各々を配備する場合に、前記PF確認モジュールによる前記PFモジュールの配備の正常性の確認と、前記自己確認モジュールによる前記モジュールの配備の正常性の確認と、の内の少なくとも一方を行う請求項2に記載の配備装置。 - 前記配備手段は、前記PF確認モジュールによる前記PFモジュールの配備の正常性の確認の結果、前記PFモジュールの配備が正常に行われている場合、前記モジュールを前記処理装置に配備する請求項2または3に記載の配備装置。
- 前記配備手段は、前記自己確認モジュールによる前記モジュールの配備の正常性の確認の結果、前記モジュールの配備が正常に行われている場合、当該モジュールを前記PFモジュールとする前記モジュールの配備を行う請求項2乃至4のいずれかに記載の配備装置。
- 前記PF確認情報は、さらに、前記PFモジュールの配備の正常性の確認の重要度を含み、
前記正常性確認手段は、前記PFモジュールの配備の正常性の確認の重要度と入力された閾値とを比較することにより、前記PFモジュールの配備の正常性の確認を行うかどうかを判断する請求項1乃至5のいずれかに記載の配備装置。 - 前記自己確認情報は、さらに、前記モジュールの配備の正常性の確認の重要度を含み、
前記正常性確認手段は、前記モジュールの配備の正常性の確認の重要度と入力された閾値とを比較することにより、前記モジュールの配備の正常性の確認を行うかどうかを判断する請求項1乃至6のいずれかに記載の配備装置。 - 前記PF確認モジュールは、前記PFモジュールが配備されたときに生成される所定のファイルの有無、前記PFモジュールが配備されたときに起動される所定のプロセスの有無、前記PFモジュールが配備されたときに生成されるログの所定の文字列の有無、及び、前記PFモジュールの所定の関数の実行結果の内の少なくとも一つを基に、前記PFモジュールの配備の正常性の確認を行う請求項1乃至7のいずれかに記載の配備装置。
- 前記自己確認モジュールは、前記モジュールが配備されたときに生成される所定のファイルの有無、前記モジュールが配備されたときに起動される所定のプロセスの有無、前記モジュールが配備されたときに生成されるログの所定の文字列の有無、及び、前記モジュールの所定の関数の実行結果の内の少なくとも一つを基に、前記モジュールの配備の正常性の確認を行う請求項1乃至8のいずれかに記載の配備装置。
- システムを構成するモジュールの識別子に対応付けて、当該モジュールが依存する他のモジュールであるプラットフォーム(PF)モジュールの配備の正常性を確認するためのPF確認モジュールの識別子を含むPF確認情報と、前記モジュールの配備の正常性を確認するための自己確認モジュールの識別子を含む自己確認情報と、の内の少なくとも一方を含む構成情報を記憶し、
前記モジュールを処理装置に配備し、
前記構成情報を参照し、前記モジュールの配備前における、前記処理装置上での前記PF確認モジュールによる前記PFモジュールの配備の正常性の確認と、前記モジュールの配備後における、前記処理装置上での前記自己確認モジュールによる前記モジュールの配備の正常性の確認と、の内の少なくとも一方を行う、配備方法。 - コンピュータに、
システムを構成するモジュールの識別子に対応付けて、当該モジュールが依存する他のモジュールであるプラットフォーム(PF)モジュールの配備の正常性を確認するためのPF確認モジュールの識別子を含むPF確認情報と、前記モジュールの配備の正常性を確認するための自己確認モジュールの識別子を含む自己確認情報と、の内の少なくとも一方を含む構成情報を記憶し、
前記モジュールを処理装置に配備し、
前記構成情報を参照し、前記モジュールの配備前における、前記処理装置上での前記PF確認モジュールによる前記PFモジュールの配備の正常性の確認と、前記モジュールの配備後における、前記処理装置上での前記自己確認モジュールによる前記モジュールの配備の正常性の確認と、の内の少なくとも一方を行う、処理を実行させるプログラムを格納する、コンピュータが読み取り可能な記録媒体。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
RU2014153134A RU2014153134A (ru) | 2012-06-04 | 2013-05-28 | Устройство развертывания и способ развертывания |
US14/405,034 US20150127787A1 (en) | 2012-06-04 | 2013-05-28 | Deployment device and deployment method |
CN201380029307.8A CN104335174A (zh) | 2012-06-04 | 2013-05-28 | 部署设备和部署方法 |
EP13800947.7A EP2857966A4 (en) | 2012-06-04 | 2013-05-28 | PROVISION DEVICE AND PROVISION METHOD |
JP2014519823A JPWO2013183249A1 (ja) | 2012-06-04 | 2013-05-28 | 配備装置、及び、配備方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012127259 | 2012-06-04 | ||
JP2012-127259 | 2012-06-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013183249A1 true WO2013183249A1 (ja) | 2013-12-12 |
Family
ID=49711657
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/003346 WO2013183249A1 (ja) | 2012-06-04 | 2013-05-28 | 配備装置、及び、配備方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20150127787A1 (ja) |
EP (1) | EP2857966A4 (ja) |
JP (1) | JPWO2013183249A1 (ja) |
CN (1) | CN104335174A (ja) |
RU (1) | RU2014153134A (ja) |
WO (1) | WO2013183249A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015194139A1 (ja) * | 2014-06-17 | 2015-12-23 | 日本電気株式会社 | 情報処理装置、配備方法、及び、記録媒体 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005044011A (ja) * | 2003-07-24 | 2005-02-17 | Hitachi Ltd | ソフトウェアパッケージ管理方法 |
JP2006338606A (ja) * | 2005-06-06 | 2006-12-14 | Nec Corp | ファイル管理手続実行システム |
JP2007079773A (ja) * | 2005-09-13 | 2007-03-29 | Fuji Xerox Co Ltd | ソフトウエア配布サーバ及びソフトウエア配布方法 |
JP2007128522A (ja) * | 2005-11-03 | 2007-05-24 | Internatl Business Mach Corp <Ibm> | システム機能をソフトウェア・パッケージ管理システム内のソフトウェア・パッケージとして表すシステムおよび方法 |
JP2007193696A (ja) * | 2006-01-20 | 2007-08-02 | Rikogaku Shinkokai | 支援プログラム、支援プログラム生成プログラム、支援プログラム生成方法、ファイル生成・配布方法、及びインストールサーバ |
JP4809772B2 (ja) | 2003-10-23 | 2011-11-09 | マイクロソフト コーポレーション | コンピュータシステムおよび分散アプリケーションのモデルに基づく管理 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100573451C (zh) * | 2005-04-25 | 2009-12-23 | 株式会社理光 | 考虑***稳定性的程序版本管理 |
US20080040455A1 (en) * | 2006-08-08 | 2008-02-14 | Microsoft Corporation | Model-based deployment and configuration of software in a distributed environment |
US9251498B2 (en) * | 2006-10-23 | 2016-02-02 | Oracle International Corporation | Facilitating deployment of customizations of enterprise applications |
US8522234B2 (en) * | 2007-02-05 | 2013-08-27 | Microsoft Corporation | Tailoring an operating system to a computer system |
US20080201705A1 (en) * | 2007-02-15 | 2008-08-21 | Sun Microsystems, Inc. | Apparatus and method for generating a software dependency map |
US8893106B2 (en) * | 2010-03-15 | 2014-11-18 | Oracle International Corporation | Change analysis on enterprise systems prior to deployment |
US9256412B2 (en) * | 2012-07-04 | 2016-02-09 | Sap Se | Scheduled and quarantined software deployment based on dependency analysis |
-
2013
- 2013-05-28 RU RU2014153134A patent/RU2014153134A/ru unknown
- 2013-05-28 WO PCT/JP2013/003346 patent/WO2013183249A1/ja active Application Filing
- 2013-05-28 CN CN201380029307.8A patent/CN104335174A/zh active Pending
- 2013-05-28 US US14/405,034 patent/US20150127787A1/en not_active Abandoned
- 2013-05-28 EP EP13800947.7A patent/EP2857966A4/en not_active Withdrawn
- 2013-05-28 JP JP2014519823A patent/JPWO2013183249A1/ja active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005044011A (ja) * | 2003-07-24 | 2005-02-17 | Hitachi Ltd | ソフトウェアパッケージ管理方法 |
JP4809772B2 (ja) | 2003-10-23 | 2011-11-09 | マイクロソフト コーポレーション | コンピュータシステムおよび分散アプリケーションのモデルに基づく管理 |
JP2006338606A (ja) * | 2005-06-06 | 2006-12-14 | Nec Corp | ファイル管理手続実行システム |
JP2007079773A (ja) * | 2005-09-13 | 2007-03-29 | Fuji Xerox Co Ltd | ソフトウエア配布サーバ及びソフトウエア配布方法 |
JP2007128522A (ja) * | 2005-11-03 | 2007-05-24 | Internatl Business Mach Corp <Ibm> | システム機能をソフトウェア・パッケージ管理システム内のソフトウェア・パッケージとして表すシステムおよび方法 |
JP2007193696A (ja) * | 2006-01-20 | 2007-08-02 | Rikogaku Shinkokai | 支援プログラム、支援プログラム生成プログラム、支援プログラム生成方法、ファイル生成・配布方法、及びインストールサーバ |
Non-Patent Citations (2)
Title |
---|
HEWLETT-PACKARD COMPANY: "HP Operations Orchestration software", - 29 May 2012 (2012-05-29), Retrieved from the Internet <URL:http://www8.hp.com/us/en/software/software-product.html?compURI =tcm:245-936143&pageTitle=operations-orchestration-software> |
See also references of EP2857966A4 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015194139A1 (ja) * | 2014-06-17 | 2015-12-23 | 日本電気株式会社 | 情報処理装置、配備方法、及び、記録媒体 |
US10180830B2 (en) | 2014-06-17 | 2019-01-15 | Nec Corporation | Information processing device, deployment method, and recording medium |
Also Published As
Publication number | Publication date |
---|---|
EP2857966A1 (en) | 2015-04-08 |
CN104335174A (zh) | 2015-02-04 |
JPWO2013183249A1 (ja) | 2016-01-28 |
EP2857966A4 (en) | 2016-03-16 |
US20150127787A1 (en) | 2015-05-07 |
RU2014153134A (ru) | 2016-08-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10606739B2 (en) | Automated program code analysis and reporting | |
CN108108297B (zh) | 自动化测试的方法和装置 | |
US10353807B2 (en) | Application development management | |
US8108456B2 (en) | Method and apparatus for migrating the system environment on which the applications depend | |
EP3499364B1 (en) | Method and device for loading kernel module | |
US11182132B1 (en) | Determining functional equivalence of configurations of a model | |
KR102044046B1 (ko) | 텔레메트리 파일 해시 및 충돌 검출 기법 | |
JP6673355B2 (ja) | 配備装置、配備方法、及び、プログラム | |
US20140040299A1 (en) | Automated Method of Detecting Pattern Matches between Converged Infrastructure Models and an Operating Converged Infrastructure | |
CN110888652B (zh) | 基于jenkins插件的多版本构建方法及终端 | |
US11409631B2 (en) | Verification automation apparatus, verification automation method, and computer-readable recording medium | |
CN110532182B (zh) | 一种虚拟化平台的自动化测试方法及装置 | |
CN112241360A (zh) | 一种测试用例生成方法、装置、设备及存储介质 | |
US20170109257A1 (en) | Use case driven stepping component automation framework | |
CN111831567B (zh) | 应用的测试环境配置方法、装置、***和介质 | |
CN113330419A (zh) | 一种设备应用安装方法和装置 | |
US20100153913A1 (en) | Systems and Methods for Executing Object-Oriented Programming Code Invoking Pre-Existing Objects | |
US20100077382A1 (en) | Computer-readable recording medium string a bug detection support program, similar structure identification information list output program, bug detection support apparatus, and bug detection support method | |
CN113297081B (zh) | 一种持续集成流水线的执行方法和装置 | |
US20150067697A1 (en) | Computer system and program | |
CN116166907B (zh) | 一种使用WebAssembly和服务页面编译技术开发Web应用的方法及装置 | |
WO2013183249A1 (ja) | 配備装置、及び、配備方法 | |
CN111209197B (zh) | 应用程序持续集成测试方法、***、设备和存储介质 | |
CN112667491A (zh) | 虚拟机的功能测试方法及装置 | |
CN111158696A (zh) | 版本部署方法及装置 |
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: 13800947 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013800947 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2014519823 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14405034 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2014153134 Country of ref document: RU Kind code of ref document: A |