Deployment delivery method for distributed applications

Abstract

The present invention discloses a deployment and delivery method for distributed applications, which belongs to the relevant technical field of distributed application deployment. The technical problem to be solved by the present invention is that the delivery process is complicated due to the diversification of project requirements, there is a lack of standard processes, and the efficiency is low. The technical solution is as follows: the method is to assist the deployment of the entire platform system through a web interface, and guide the platform deployment personnel to complete the deployment work in a guided manner; when the deployment system is used, the installation package of the deployment system and the package of the entire platform are uploaded to a server in a server cluster to be deployed, and the server is called a management node; then the deployment system is started, and the deployment page is accessed to perform the operation of the platform deployment process, which is specifically as follows: S1, determine the environment and environment server maintenance; S2, select the platform application module to be deployed: S3, deploy and start the component; S4, configure the configuration items of the platform application; S5, verify each configuration item of the platform; S6, detect the platform application module.

Description

Technical Field

[0001] The present invention relates to the technical field related to distributed application deployment, and in particular to a deployment and delivery method for distributed applications. Background Art

[0002] The software platform products developed by the company adopt the concept of modular development and distributed technical architecture, and each relatively independent functional module is a separate application. When the product is delivered, it will also deploy several application modules required by the project customer according to different customer needs. At the same time, the components that each module needs to rely on are also different. Because there are many projects and the requirements of each project are different, each project will have different requirements when it is deployed and delivered. Therefore, the requirements of application modules, components, configuration items, etc. that need to be deployed for each project have become complex and diverse. Therefore, how to simplify the deployment process and improve product delivery efficiency is a technical problem that needs to be solved urgently. Summary of the invention

[0003] The technical task of the present invention is to provide a deployment and delivery method for distributed applications to solve the problems of complex delivery procedures, lack of standard processes and low efficiency caused by diversified project requirements.

[0004] The technical task of the present invention is achieved in the following way: a deployment and delivery method for distributed applications, which assists the deployment of the entire platform system through a web interface, and guides the platform deployment personnel to complete the deployment work in a guided manner; when the deployment system is used, the installation package of the deployment system and the package of the entire platform are uploaded to a server in the server cluster to be deployed, and the server is called a management node; then the deployment system is started, and the deployment page is accessed to perform the platform deployment process, which is specifically as follows:

[0005] S1. Determine the environment and environment server maintenance;

[0006] S2. Select the platform application module to be deployed;

[0007] S3, deploy and start components;

[0008] S4. Configuration items of configuration platform applications;

[0009] S5. Verification of each configuration item of the platform;

[0010] S6. Detection platform application module.

[0011] Preferably, the deployment system is written in Java language, relies on JDK environment, and supports management of deployment of multiple environments.

[0012] Preferably, the environment and environment server maintenance determined in step S1 are specifically as follows:

[0013] Create a set of basic information for a deployment environment or select a previously added deployment environment, and add new application modules or components by improving the deployment environment that was previously added. The basic information of the deployment environment includes the project name, environment name, and servers required for the environment, and configure the connections to each server.

[0014] Preferably, the platform application modules to be deployed in step S2 are selected as follows:

[0015] S201, selecting an application module to be deployed in the deployment environment according to the environment information created or determined in step S1;

[0016] S202. The platform includes dozens of application modules. There are dependencies between the application modules. The deployment system records the dependencies between the application modules of the platform.

[0017] Preferably, the components deployed and started in step S3 are specifically as follows:

[0018] Deploy the components that the application depends on. The deployment of components depends on Ansible. The installation scripts of all platform components are written in advance. The server information of the specific deployment components can be configured in the form of variables.

[0019] After all applications that need to be deployed are determined in step S2, the deployment system will compile a list of all components that need to be deployed in this environment based on the components that each application module needs to depend on, and display it to trigger the component deployment task.

[0020] Preferably, the value of the configuration item in step S4 includes automatic generation and manual filling;

[0021] Among them, automatic generation: the deployment system will pre-store a set of configuration information for platform applications, which includes the key values ​​and default values ​​of all configuration items that need to be modified according to the project environment; for configuration items related to component information, when each component is deployed, the configuration generation function in the deployment system is triggered, and the value of the configuration item is automatically generated according to the rules through the configuration generator module. The logic of the rule is to automatically generate the value of the corresponding configuration item based on the previously stored configuration items and the information of the components deployed this time; among them, the configuration items related to component information include the database service connection address and the cache service address;

[0022] Manual filling: For configuration items that are not related to platform components, you need to make corresponding modifications in the page provided by the deployment platform; among them, configuration items that are not related to platform components include the default partition used by the project and the default password of the project.

[0023] Preferably, the verification of each configuration item of the platform in step S5 is specifically as follows:

[0024] When the deployer triggers the verification operation, all required configuration items of this environment will be verified, including whether all required configuration items have been filled in, whether there are any format errors in each configuration item, and whether each service configured in the configuration item is normal.

[0025] Preferably, the detection platform application module in step S6 is as follows:

[0026] S601, trigger the platform to start all applications in this environment, and provide application status monitoring based on springboot-actua tor;

[0027] S602. By calling the monitoring interface of each application module, the information is sorted and displayed for deployment personnel to observe the running status of each application instance, so as to timely discover abnormal applications and handle them accordingly.

[0028] The deployment and delivery method for distributed applications of the present invention has the following advantages:

[0029] (1) The present invention solves the problems of complex delivery procedures, lack of standard processes, and low efficiency caused by diversified project requirements, and can simplify the deployment process and improve product delivery efficiency;

[0030] (ii) The present invention improves the efficiency of deployment work, simplifies the deployment process, and reduces the probability of problems occurring in these links during the deployment process by adding functions such as module dependency maintenance, component deployment automation, and application status monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The present invention is further described below in conjunction with the accompanying drawings.

[0032] Attached Figure 1 A flowchart of a deployment delivery method for distributed applications is provided. DETAILED DESCRIPTION

[0033] The deployment and delivery method for distributed applications of the present invention is described in detail below with reference to the accompanying drawings and specific embodiments of the specification.

[0034] Example:

[0035] As attached Figure 1As shown, the deployment and delivery method for distributed applications of the present invention assists the deployment of the entire platform system through a web interface, and guides the platform deployment personnel to complete the deployment work in a guided manner; when the deployment system is used, the installation package of the deployment system and the package of the entire platform are uploaded to a server in the server cluster to be deployed, and the server is called a management node; then the deployment system is started, and the deployment page is accessed to perform the operation of the platform deployment process, which is specifically as follows:

[0036] S1. Determine the environment and environment server maintenance;

[0037] S2. Select the platform application module to be deployed;

[0038] S3, deploy and start components;

[0039] S4. Configuration items of configuration platform applications;

[0040] S5. Verification of each configuration item of the platform;

[0041] S6. Detection platform application module.

[0042] The deployment system in this embodiment is written in Java language, relies on JDK environment, and supports the management of deployment of multiple environments.

[0043] In step S1 of this embodiment, the environment and environment server maintenance are determined as follows:

[0044] Create a set of basic information for a deployment environment or select a previously added deployment environment, and add new application modules or components by improving the deployment environment that was previously added. The basic information of the deployment environment includes the project name, environment name, and servers required for the environment, and configure the connections to each server.

[0045] In step S2 of this embodiment, the platform application modules to be deployed are selected as follows:

[0046] S201, selecting an application module to be deployed in the deployment environment according to the environment information created or determined in step S1;

[0047] S202. The platform includes dozens of application modules. There are dependencies between the application modules. The deployment system records the dependencies between the application modules of the platform.

[0048] For example, when the deployer chooses to deploy system A, the two systems B and C that system A depends on for normal operation will be automatically bound and deployed together with A in the subsequent application deployment process. This solves the problem of manually maintaining the dependencies between the various systems and reduces the occurrence of application dependency problems during the deployment process.

[0049] In step S3 of this embodiment, components are deployed and started as follows:

[0050] S301. Deploy the components that the application depends on. The deployment of the components depends on Ansible. The installation scripts of all platform components are written in advance. The server information of the specific deployment components can be configured in the form of variables.

[0051] S302. After all applications that need to be deployed are determined in step S2, the deployment system will compile a list of all components that need to be deployed in this environment based on the components that each application module needs to depend on, and display it to trigger the component deployment task.

[0052] For example: if it is determined in step S2 that three application modules A, B, and C need to be deployed, module A needs to rely on three components, redis, zookeeper, and mysql, module B needs to rely on two components, redis and zookeeper, and module C needs to rely on redis, zookeeper, and kafka, then the deployment system will list all the components that need to be deployed, namely redis, zookeeper, mysql, and kafka. After the deployer arranges all the components that need to be deployed on the servers they will occupy, the component deployment operation is triggered. The deployment system will pass the component server address assigned by the deployer to the deployment script of each component as a parameter by triggering the ansible interface, distribute the installation packages of each component to the specified server, and use the script to automatically install and deploy the component.

[0053] In this embodiment, the value of the configuration item in step S4 includes automatic generation and manual filling;

[0054] Among them, automatic generation: the deployment system will pre-store a set of configuration information for platform applications, which includes the key values ​​and default values ​​of all configuration items that need to be modified according to the project environment; for configuration items related to component information, when each component is deployed, the configuration generation function in the deployment system is triggered, and the value of the configuration item is automatically generated according to the rules through the configuration generator module. The logic of the rule is to automatically generate the value of the corresponding configuration item based on the previously stored configuration items and the information of the components deployed this time; among them, the configuration items related to component information include the database service connection address and the cache service address;

[0055] Manual filling: For configuration items that are not related to platform components, you need to make corresponding modifications in the page provided by the deployment platform; among them, configuration items that are not related to platform components include the default partition used by the project and the default password of the project.

[0056] The verification of each configuration item of the platform in step S5 of this embodiment is specifically as follows:

[0057] When the deployer triggers the verification operation, all required configuration items of this environment will be verified, including whether all required configuration items have been filled in, whether there are any format errors in each configuration item, and whether each service configured in the configuration item is normal.

[0058] The detection platform application module in step S6 of this embodiment is specifically as follows:

[0059] S601, trigger the platform to start all applications in this environment, and provide application status monitoring based on springboot-actua tor;

[0060] S602. By calling the monitoring interface of each application module, the information is sorted and displayed for deployment personnel to observe the running status of each application instance, so as to timely discover abnormal applications and handle them accordingly.

[0061] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A deployment and delivery method for distributed applications, characterized in that: This method uses a web interface to assist in the deployment of the entire platform system, and uses a guided approach to guide platform deployment personnel to complete the deployment work; when the deployment system is used, the installation package of the deployment system and the package of the entire platform are uploaded to a server in the server cluster that needs to be deployed. This server is called a management node; then the deployment system is started, and the deployment page is accessed to perform operations on the platform deployment process, as follows: S1. Determine the environment and environment server maintenance; S2. Select the platform application module to be deployed; S3, deploy and start components; S4. Configuration items of configuration platform applications; S5. Verification of each configuration item of the platform; S6, detection platform application module; The deployment system is written in Java, relies on the JDK environment, and supports the management of deployment in multiple environments. The environment and environment server maintenance determined in step S1 are as follows: Create a set of basic information of the deployment environment or select a previously added deployment environment, and add a new application module or component by improving the deployment of the previously added deployment environment; the basic information of the deployment environment includes the environment; The platform application modules to be deployed in step S2 are as follows: S201, selecting an application module to be deployed in the deployment environment according to the environment information created or determined in step S1; S202, the platform includes dozens of application modules, each of which has dependencies, and the deployment system records the dependencies between the application modules of the platform; The components deployed and started in step S3 are as follows: Deploy the components that the application depends on. The deployment of components depends on Ansible. The installation scripts of all platform components are written in advance. The server information of the specific deployment components can be configured in the form of variables. After all applications to be deployed are determined in step S2, the deployment system will sort out a list of all components to be deployed in this environment based on the components that each application module needs to depend on, and display it to trigger the component deployment task; The values ​​of the configuration items in step S4 include automatically generated and manually filled in; Among them, automatic generation: the deployment system will pre-store a set of configuration information for platform applications, which includes the key values ​​and default values ​​of all configuration items that need to be modified according to the project environment; for configuration items related to component information, when each component is deployed, the configuration generation function in the deployment system is triggered, and the value of the configuration item is automatically generated according to the rules through the configuration generator module. The logic of the rule is to automatically generate the value of the corresponding configuration item based on the previously stored configuration items and the information of the components deployed this time; among them, the configuration items related to component information include the database service connection address and the cache service address; Manual filling: For configuration items not related to platform components, you need to make corresponding modifications in the page provided by the deployment platform; configuration items not related to platform components include the default partition used by the project and the default password of the project; The verification of each configuration item of the platform in step S5 is as follows: When the deployer triggers the verification operation, all required configuration items of this environment will be verified, including whether all required configuration items have been filled in, whether there are format errors in each configuration item, and whether each service configured in the configuration item is normal; The detection platform application module in step S6 is as follows: S601, trigger the startup of all applications in the environment of the platform, and provide application status monitoring based on springboot-actuator; S602. By calling the monitoring interface of each application module, the information is sorted and displayed for deployment personnel to observe the running status of each application instance, so as to timely discover abnormal applications and handle them accordingly.

Images