Lightweight transformation method for cloud native platform and plug-in system

Abstract

The invention discloses a cloud native platform lightweight transformation method and a plug-in system. The method comprises the following steps: S1, analyzing each regional module in a cloud native platform, extracting middleware with similar functions in each regional module, setting the middleware as public middleware, and setting a switch to call different regional modules; s2, merging the front end of the cloud native platform to an Nginx, deploying a secondary directory, merging a plurality of micro-services of the cloud native platform into one micro-service, and calling the micro-service through a micro-service gateway; s3, setting a database pre-installation script, and constructing a database pre-installation interface; and S4, testing the transformed cloud native platform. According to the method, the cloud native platform is subjected to lightweight transformation, so that the resource occupation is reduced to 16C32G; and meanwhile, by setting a calling switch for each area module, each component in the cloud native platform realizes hierarchical single-item dependent calling, so that on-demand installation is realized, and subsequent maintenance is facilitated.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of cloud platforms, and in particular to a method for lightweight modification of a cloud native platform and a plug-in system. BACKGROUND

[0002] Cloud native is a distributed cloud based on distributed deployment and unified management, and is a set of cloud technology product systems based on technologies such as containers, microservices and DevOps. Containerization technology realizes standardized encapsulation of applications through Docker, eliminates the influence of environment differences on deployment, and realizes cross-node resource scheduling in combination with Kubernetes; the microservice architecture splits monolithic applications into loosely coupled modules, each of which can be independently expanded and distributed on different physical nodes; a distributed orchestration system supports million-level node computing power collaboration, and optimizes resource utilization through intelligent scheduling algorithms.

[0003] Although the existing cloud native platform is powerful, it has high resource consumption and complex deployment, and is difficult to adapt to lightweight application scenarios. These problems limit its application in resource-constrained environments, and an efficient and lightweight modification method is urgently needed. SUMMARY

[0004] To solve the above problems, the application provides a method for lightweight modification of a cloud native platform, comprising the following steps: S1. Analyze each regional module in the cloud native platform, extract middleware with similar functions in each regional module as common middleware, and set switches to call different regional modules; S2. Merge the front end of the cloud native platform to one Nginx, deploy in a two-level directory, and merge multiple microservices of the cloud native platform into one microservice, and call through the microservice gateway; S3. Set up a database pre-installation script and build a database pre-installation interface; S4. Test the modified cloud native platform.

[0005] Further, the S1 step includes the following specific regional modules: API gateway, BPM, monitoring module, front-end architecture, platform system architecture; and the specific similar function middleware includes: middleware providing MQ asynchronous and database type.

[0006] Further, the S2 step includes the following specific regional modules: API gateway, BPM, monitoring module, front-end architecture, platform system architecture; and the specific similar function middleware includes: middleware providing MQ asynchronous and database type.

[0007] Further, the S3 step includes the following specific regional modules: API gateway, BPM, monitoring module, front-end architecture, platform system architecture; and the specific similar function middleware includes: middleware providing MQ asynchronous and database type.

[0008] Further, a step of deploying the reformed cloud native platform is further included: a operation and maintenance deployment tool is constructed, after the data generated in steps S1-S3 is copied to the target deployment environment for installation through the operation and maintenance deployment tool, the API interface is started.

[0009] A plug-in system for lightweight reform of a cloud native platform, comprising a platform analysis extraction module, a platform code retrieval module, a micro-service management and control module, a script preset module, an operation and maintenance deployment module, and a test module. The platform analysis module is used for scanning and analyzing the cloud native platform, and extracting the middleware with similar functions. The platform code retrieval module is used for scanning and analyzing the architecture code of the cloud native platform, and obtaining the Git branch of the current front-end and back-end code of the cloud native platform. The micro-service management and control module is used for scanning each micro-service in the cloud native platform, extracting the configurations with the same meaning as public variables, and setting a calling switch. The script preset module is used for constructing a database pre-installation script, and managing the version of the cloud native platform through Git. The operation and maintenance deployment module is used for constructing an operation and maintenance deployment tool, and deploying the reformed cloud native platform through the operation and maintenance deployment tool. The test module is used for running test on the deployed cloud native platform.

[0010] The present application provides a method and a plug-in system for lightweight reform of a cloud native platform, which has the following beneficial effects: The present application reduces the resource occupation to 16C32G and the delivery time to 8 hours by reforming the cloud native platform, and enables each component in the cloud native platform to realize hierarchical single-item dependent calling by setting a calling switch for each regional module, so that the installation is on demand, and the subsequent maintenance is facilitated. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or the prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of the drawings shown.

[0012] Figure 1 The method flowchart provided by the present application is provided. DETAILED DESCRIPTION

[0013] It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

[0014] The embodiments of the present application will be described in detail below with reference to the drawings, which are described only as part of the embodiments, and not all embodiments, and the representations and descriptions irrelevant to the present application are omitted in the drawings and the description for the purpose of clarity.

[0015] In order to have a clearer understanding of the technical features, objectives and benefits of the present application, the technical solutions of the present application are selected for the following detailed description. Obviously, the described embodiments are part of the embodiments of the present application, not all embodiments, and cannot be understood as limiting the scope of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0016] As shown in Figure 1 The present application provides a method for lightweight modification of a cloud-native platform, comprising the following steps: S1. Analyze each regional module in the cloud-native platform, and extract the middleware with similar functions in each regional module as common middleware, and set a switch to call different regional modules; S2. Merge the front end of the cloud-native platform to one Nginx, deploy in a two-level directory, and merge multiple microservices of the cloud-native platform into one microservice, and call through the microservice gateway; S3. Set up a database pre-installation script and build a database pre-installation interface; S4. Test the modified cloud-native platform.

[0017] The regional modules in the S1 step specifically include: API gateway, BPM, monitoring module, front-end architecture, platform system architecture; the specific similar function middleware includes: middleware providing MQ asynchronous, database type. For example, RabbitMQ, RocketMQ, Kafka, all provide MQ asynchronous function, and after comparison and verification, the most compatible Kafka is retained, the microservices using RabbitMQ and RocketMQ are modified, the logic is compatible with the original MQ and Kafka, and is controlled through a switch. The method for the database is similar, ES and Doris have basically the same function, and since ES is widely used, the microservices using Doris are modified for ES compatibility, mainly monitoring, storing data supporting ES and Doris, and controlled through a switch.

[0018] The step S2 of merging multiple microservices into one microservice specifically includes: extracting configurations with the same meaning in each microservice as common variables, and setting a call switch for different microservices. Each microservice corresponds to its own database pre-installed SQL script, and the information related to the field environment in the script is replaced with variables. During database initialization, the variables in the SQL script are uniformly replaced with the configuration information of the field, and an executable SQL script is formed, which is convenient for subsequent automatic execution of database initialization. For example, all Redis connections uniformly use the variable dcp.redis.hosts, and in the configuration center, dcp-common is used for unified management. Each microservice shares this configuration, so that only one common configuration needs to be changed for the entire platform. After generating the version, the specific variables in the common configuration are replaced according to the field information, and the initialization of the configuration is completed.

[0019] The step S3 specifically includes: setting and writing database pre-installed scripts, and replacing environment parameters in the scripts with variables, and managing cloud-native platform versions through Git. First, build a Maven private service, an Npm private service, and a cache of local compilation environment. When the source code is pulled to this environment, call the relevant Maven and Npm compilation commands according to the front-end and back-end engineering description information to perform compilation. The engineering information includes JKD version, React version, etc., and the compilation environment pre-prepares related compilers.

[0020] Database script: (example with MySQL) Table structure change: source code engineering / sql / mysql / DDL / yyyymmdd-serial number.sql; Table content change: source code engineering / sql / mysql / DML / yyyymmdd-serial number.sql; Each microservice needs to save both mysql and kingbase ( / kingbase) scripts; -----The operation and maintenance tool will automatically execute each SQL to initialize / upgrade the database according to the serial number; -----The microservice responsible person needs to ensure the integrity and correctness of the SQL, and the bug of incorrect table structure in the field is borne by the microservice responsible person.

[0021] It also includes the step of deploying the reformed cloud-native platform: build an operation and maintenance deployment tool, copy the data generated in steps S1-S3 to the target deployment environment for installation through the operation and maintenance deployment tool, and then start through the API interface. In order to run lightly, the commonly used CICD tools such as jekins are not used, and go and pathon languages are used to realize related functions, which requires low deployment environment and reduces the complexity of deployment tools to prolong the risk of delivery time.

[0022] A cloud native platform lightweight transformation plug-in system, comprising a platform analysis extraction module, a platform code retrieval module, a micro-service management and control module, a script preset module, an operation and maintenance deployment module and a test module; The platform analysis module is used for scanning and analyzing the cloud native platform, and extracting the middleware with similar functions therein; The platform code retrieval module is used for scanning and analyzing the architecture code of the cloud native platform, and obtaining the Git branch of the current front-end and back-end code of the cloud native platform; The micro-service management and control module is used for scanning each micro-service in the cloud native platform, extracting the configurations with the same meaning as public variables, and setting a calling switch; The script preset module is used for constructing a database pre-installed script, and managing the version of the cloud native platform through Git; The operation and maintenance deployment module is used for constructing an operation and maintenance deployment tool (CICD full-process control system), and deploying the transformed cloud native platform through the operation and maintenance deployment tool; The test module is used for running test on the deployed cloud native platform.

[0023] The present application reduces the resource occupation to 16C32G and the delivery time to 8 hours by lightweight transformation of the cloud native platform.

[0024] The above is only the preferred embodiment of the present application, and it should be understood that the present application is not limited to the form disclosed herein, and should not be considered as excluding other embodiments, but can be used in various other combinations, modifications and environments, and can be modified within the scope of the concept described herein by the above-mentioned teaching or related art or knowledge. Any modification and change made by the person skilled in the art without departing from the spirit and scope of the present application shall be within the protection scope of the appended claims of the present application.

Claims

1. A method for lightweight transformation of a cloud-native platform, characterized in that, Includes the following steps: S1. Analyze the modules in each region of the cloud-native platform, extract middleware with similar functions from each region module and set it as common middleware, and set a switch to call different region modules; S2. Merge the cloud-native platform front-end into a single Nginx instance and deploy it in a second-level directory. Also, merge multiple microservices of the cloud-native platform into a single microservice and call them through a microservice gateway. S3. Configure the database pre-installation script and build the database pre-installation interface; S4. Test the modified cloud-native platform.

2. The method for lightweight transformation of a cloud-native platform according to claim 1, characterized in that, The various regional modules mentioned in step S1 specifically include: API gateway, BPM, monitoring module, front-end architecture, and platform system architecture; The specific middleware with similar functions includes: middleware that provides asynchronous MQ and database types.

3. The method for lightweight transformation of a cloud-native platform according to claim 1, characterized in that, In step S2, merging multiple microservices into one microservice specifically involves: extracting configurations with the same meaning from each microservice as common variables, and setting invocation switches for different microservices.

4. The method for lightweight transformation of a cloud-native platform according to claim 1, characterized in that, The S3 step specifically involves: setting up and writing a pre-installed database script, replacing the environment parameters in it with variables, and managing the cloud-native platform version using Git.

5. The method for lightweight transformation of a cloud-native platform according to claim 1, characterized in that, It also includes the steps of deploying the modified cloud-native platform: building an operation and maintenance deployment tool, copying the data generated in steps S1 to S3 to the target deployment environment for installation through the operation and maintenance deployment tool, and then starting it through the API interface.

6. A plug-in system for implementing the method of lightweight transformation of a cloud-native platform as described in any one of claims 1-5, characterized in that, It includes a platform analysis and extraction module, a platform code retrieval module, a microservice management and control module, a script preset module, an operation and maintenance deployment module, and a testing module; The platform analysis module is used to scan and analyze cloud-native platforms and extract middleware with similar functions. The platform code retrieval module is used to scan and analyze the architecture code of the cloud-native platform to obtain the Git branches of the current front-end and back-end code of the cloud-native platform. The microservice management module is used to scan each microservice in the cloud-native platform, extract configurations with the same meaning as public variables, and set call switches; The script preset module is used to build database pre-installed scripts and manage cloud-native platform versions via Git; The operation and maintenance deployment module is used to build operation and maintenance deployment tools and deploy the modified cloud-native platform through these tools. The testing module is used to perform operational tests on the deployed cloud-native platform.

Images