CN111796801B

CN111796801B - Automatic construction method and system for application version based on container

Info

Publication number: CN111796801B
Application number: CN202010611859.1A
Authority: CN
Inventors: 沈震宇; 王磊; 白佳乐; 沈一帆
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2023-08-11
Anticipated expiration: 2040-06-30
Also published as: CN111796801A

Abstract

The application provides a container-based automatic application version construction method and a system, wherein the method comprises the following steps: determining the program of the application version and source codes of various configurations according to a preset application version model; calling a version making tool to convert the source code into a target code; according to the target code, setting the container and the operation parameters of the application version, the application can realize the rapid deployment of the application version.

Description

Automatic construction method and system for application version based on container

Technical Field

The application relates to the technical field of application version construction and deployment, in particular to a container-based automatic application version construction method and system.

Background

In terms of business, with the development of the internet, the demand for rapid update iteration of a business system is more and more vigorous. Therefore, in order to adapt to the rapid update of the application version of the service system, development technologies and concepts providing technical support for the construction and deployment of the application version are also rapidly developed, for example, the concepts of agile development are widely spread, various development frameworks are increasingly standardized and agile, and a version construction mode after development and production operation and maintenance deployment based on the version output by construction are also more selected, for example, containers, ANSIBLE and other self-developed deployment tools and systems. Various complex techniques exist in the fields of development, version production, version deployment and the like of application versions, and the requirement of rapid iteration of the business is supported. However, when the business system application version is constructed and deployed in an enterprise-level large-scale environment under the condition that the scale of the business system is larger and larger, the problems of insufficient content integrity of the application version, lack of replicability in the process of making the application version, and poor expandability of the version due to the continuously-changing version making requirements exist.

Disclosure of Invention

The application aims to provide an automatic construction method for an application version based on a container, which realizes quick deployment of the application version. It is another object of the present application to provide a container-based application version automation construction system. It is a further object of the application to provide a computer device. It is a further object of the application to provide a readable medium.

To achieve the above object, one aspect of the present application discloses a container-based application version automation construction method, including:

determining the program of the application version and source codes of various configurations according to a preset application version model;

calling a version making tool to convert the source code into a target code;

and setting the container and the operation parameters of the application version according to the target code.

Preferably, the determining the program of the application version and the source codes of various configurations according to the preset application version model specifically includes:

defining the hierarchical relation of all containers of the application version in a preset application version model and the environment configuration file of each container;

and obtaining the program of the application version and source codes of various configurations according to the preset application version model after the hierarchical relation and the environment configuration file are configured.

Preferably, the environment profile includes an inner environment profile and an outer environment profile.

Preferably, further comprising, after invoking the versioning tool to convert the source code to the target code:

storing the target code;

and carrying out compliance verification on the stored target code, and setting the container of the application version according to the target code if the verification is passed.

The application also discloses a container-based application version automatic construction system, which comprises:

the version configuration module is used for determining the program of the application version and source codes of various configurations according to a preset application version model;

the version making module is used for calling a version making tool to convert the source code into a target code;

and the version deployment module is used for setting the container and the operation parameters of the application version according to the target code.

Preferably, the version configuration module is specifically configured to define a hierarchical relationship of all containers of the application version in a preset application version model and an environment configuration file of each container, and obtain a program of the application version and source codes of various configurations according to the preset application version model after the hierarchical relationship and the environment configuration file are configured.

Preferably, the method further comprises a version verification module, wherein the version verification module is used for storing the target code after calling a version making tool to convert the source code into the target code, carrying out compliance verification on the stored target code, and setting a container of an application version according to the target code if the verification is passed.

The application also discloses a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor,

the processor, when executing the program, implements the method as described above.

The application also discloses a computer readable medium, on which a computer program is stored,

the program, when executed by a processor, implements the method as described above.

The application aims to solve the problems of non-automation of application version production, incomplete information content and insufficient expansibility of subsequent version information, and realizes a version construction scheme oriented to the continuous delivery field with automation, replicability and easy maintenance extension of a large number of application construction maintenance by defining a standardized application version model and standardized processes of version production and version deployment by means of container technology. The application forms the application version based on the automatic construction scheme of the application version of the container, not only defines the organization form of the application program, but also contains the definition of the environment parameters such as a system, a network, operation and maintenance and the like required by the operation of the application program, and is the basis for truly realizing the version deployment automation. The version definition has strong replicability, configuration information formed by source code type development can be well combined with a configuration management system to form a plurality of version controls, and corresponding configurations can be rapidly replicated for other similar systems. The version expansibility is strong and the maintainability is good.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 illustrates a flow chart of one embodiment of a container-based application version automation construction method of the present application;

FIG. 2 illustrates a flow chart of one embodiment S200 of the container-based application version automation construction method of the present application;

FIG. 3 is a logical schematic diagram of an application version model of one embodiment of the container-based application version automation construction method of the present application;

FIG. 4 illustrates a flow chart of a version compliance verification of one embodiment of the container-based application version automation construction method of the present application;

FIG. 5 illustrates a block diagram of one embodiment of a container-based application version automation build system of the present application;

FIG. 6 illustrates a block diagram of a particular embodiment of a container-based application version automation build system of the present application including a version verification module;

fig. 7 shows a schematic diagram of a computer device suitable for use in implementing embodiments of the application.

Detailed Description

In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

It is noted that the terms "comprises" and "comprising," and any variations thereof, in the description and claims of the present application and in the foregoing figures, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.

At present, under the condition that the scale of a business system is larger and larger, when the construction and deployment of an application version of the business system are carried out in an enterprise-level large-scale environment, the problems that the content integrity of the application version is insufficient, the replicability of the process of manufacturing the application version is lacking, the version scalability is poor and the like exist for the continuously-changed version manufacturing requirement.

The problem of insufficient content integrity of the application version refers to the fact that the 3 links of development, version production and version deployment cannot be connected in series in a complete and automatic mode. From application development to final version deployment to production, the normal operation of the application cannot be realized, the unit environment for the operation of the application program is very complex at first, the unit environment comprises hardware, an operating system, middleware and the application program, the definition of the part is incomplete, the application program is managed at present, the middleware is managed at part, and the operating system and the hardware are basically not managed. In addition, besides the unit environment in which the application program operates, the deployment requirements of the application, such as the number of deployed copies, load balancing and the like, are outside the unit environment, and the current application version deliverables cannot be uniformly and standardised to consider the content uniformly into the version, and are usually required to be transferred in a form of a document and the like.

The lack of replicability in the process of application versioning means that the definition of versioning is not sufficiently standardized. Applications need to care about a large amount of content beyond non-version deployment business logic, such as writing of deployment scripts, robustness of deployment scripts by using SHELL or PYTHON, error judgment and the like, and configuration methods of small baselines of the system are diversified. Different applications are defining respective blind version creation and version deployment rules and forming blind version creation script programs based on the rules. And the formed version making rules can not be copied and applied quickly, the parameter definition and deployment script difference between the applications are too large, and special modification and adaptation are still needed.

For the continuously-changed version making demands, poor version expandability means that if some new characteristics or version contents are required to be added into a version package, the version making system needs to be synchronously modified, otherwise, the new version contents cannot be delivered, even if a downstream version deployment system is delivered, the version deployment system cannot be rapidly identified and used, the coupling degree is high, the flexibility is not high, and the modification cost is high. If a load balancing configuration delivery is needed, if the coding is realized without the upstream and downstream agreements, the version system cannot expose the corresponding delivery parameters in an API mode.

According to one aspect of the application, the embodiment discloses an automatic construction method for an application version based on a container. As shown in fig. 1, in this embodiment, the method includes:

s100: and determining the program of the application version and source codes of various configurations according to the preset application version model.

S200: and calling a version production tool to convert the source code into target code.

S300: and setting the container and the operation parameters of the application version according to the target code.

The application aims to solve the problems of non-automation of application version production, incomplete information content and insufficient expansibility of subsequent version information, and realizes a version construction scheme oriented to the continuous delivery field with automation, replicability and easy maintenance extension of a large number of application construction maintenance by defining a standardized application version model and standardized processes of version production and version deployment by means of container technology. The application forms the application version based on the automatic construction scheme of the application version of the container, not only defines the organization form of the application program, but also contains the definition of the environment parameters such as a system, a network, operation and maintenance and the like required by the operation of the application program, and is the basis for truly realizing the version deployment automation. The version definition has strong replicability, configuration information formed by source code type development can be well combined with an external configuration management system to form a plurality of version controls, and corresponding configurations can be rapidly copied for other similar systems. The version expansibility is strong and the maintainability is good.

In a preferred embodiment, as shown in fig. 2, the determining, by S100, the application version program and source codes of various configurations according to the preset application version model specifically includes:

s110: and defining the hierarchical relation of all containers of the application version and the environment configuration file of each container in the preset application version model.

S120: and obtaining the program of the application version and source codes of various configurations according to the preset application version model after the hierarchical relation and the environment configuration file are configured.

It will be appreciated that in the preferred embodiment, the standardized definition of the system level configuration is implemented based on container technology, and the hierarchical relationship of the containers in the preset application version model may be defined autonomously, and the environmental parameters of each container may be configured to form an environmental configuration file. And realizing automation, flow and standardization of application version production according to the standardized application version model. Moreover, since the application version model is relatively stable but the definable parameters are extensible, developers and the operation and maintenance system responsible for deployment only need to perform custom configuration on the stable and strongly-standardized model based on convention. The setting of the application version model is also beneficial to the expandability of application version construction, if the application version model needs to be newly added with configuration content, the configuration information of automatic version verification can be added at the application level, the node level or the container level, for example, besides the complete running environment configuration, the stock content is not influenced by the application version model. In one specific example, the definition of the complex system environment of the container's application, operating system, middleware, etc., may be implemented using the docker container and its environment configuration file Dockerfile.

In a preferred embodiment, the environment profile includes an inner environment profile and an outer environment profile. The external environment configuration file defines configuration requirements outside various containers required by application operation, including container node type information, the number of copies of the container, calculation and storage network resource requirements, monitoring and alarming, load balancing, registration information, health examination and other configuration information. Preferably, each container contains 3 levels, divided into an application global level, a node level, and a container level. The hierarchical relationship of each container defines the standardized specifications of the internal environment configuration file and the external environment configuration file, provides a standard basis for the development stage, and also provides a foundation for the standardized APIs provided for the operation and maintenance system subsequently.

In a specific example, as shown in fig. 3, the environment packaging capability based on the dock mirror image and the text definition capability of dock file on the running environment implement standardized definition of the running environment in the container, including complete elements such as a system on one running unit, middleware, deployment modes of application programs and the like. While the problem of operating environment definition on one operating unit is solved by container technology, for enterprise-level applications, the environment definition capabilities outside of the container are also extremely important and indispensable, and the deployed operating environment definition outside of the container environment, such as copy number, load balancing, monitoring configuration, etc., is implemented by other text definition formats (json/yaml/properties).

In a preferred embodiment, as shown in fig. 4, the method further comprises:

s410: and storing the target code.

S420: and carrying out compliance verification on the stored target code, and setting the container of the application version according to the target code if the verification is passed.

It will be appreciated that in the preferred embodiment, scalability of the application version is achieved by storing the object code. The node-level fine-grained dynamic API registration capability can be realized through version storage, so that the expandability of the near-wireless version information and the deployment characteristic gray level release capability are realized. In S300, the target code obtains the API34 by registering newly added configuration information and dynamically exposing the API to the downstream version deployment system, and it should be emphasized that the API may be multiple open version deployment systems, and the API reads the information required by each of the APIs to perform the deployment action in each responsible domain, and the dynamic extension of the API is to perform extension registration according to the fine granularity of the application and the node, so that the new characteristic gray scale release is very convenient, without affecting the stock application. For example, in the complete process of the version deployment system, an automatic production verification system for version verification is newly added, only configuration information required by production verification is needed to be added into a version package, the production verification at the node level is placed under a node level directory, after the version is stored, a downstream production automatic verification system can read corresponding information, automatic production version verification is realized, and applications using the system are not needed to be concerned.

Further, the version creation tool system preferably pushes the created container image and out-of-container configuration to a storage device for storage for persistence. Finally, the standardized version information reading API33 is exposed to the downstream version deployment system, and the version deployment system forms a deployment action which is fast and stable and has complete development information and operation and maintenance information according to the standardized definition information.

In a preferred embodiment, the source code is converted into the target code by calling the version making tool in S200, and on the basis of unifying the application version models, unified version making is realized by providing the unified version making tool, so that the content which is concerned by the application about non-final version deployment which is originally required to be written in the version making process is shielded to the greatest extent, and only differentiated content among the left applications is left, so that the replicability of the version making process is greatly improved.

The version making tool can realize non-functional characteristics such as making of a container mirror image, correctness checking, packaging format, pushing of a version package, acceleration and compliance checking of version making, scheduling selection of making environment and the like, and the non-functional characteristics are all wrapped by the version making tool, so that the application really only pays attention to personalized definitions required by the application, does not need to care about definitions of other version making processes, and meanwhile, text configuration management is combined with the definition of the version making, thereby being more convenient for copying and pasting of the version making process.

After the development stage finishes the development of the corresponding program and the configuration based on the application version model, all the configurations can be submitted to a configuration management system, such as a Git system, a SVN system and the like, when the version is produced, the configuration management system downloads the source code, and then the unified version production device carries out the construction and the production of the version. And automatically completing the construction of the container mirror image and the information configuration of the external operation configuration of the container, and linking and configuring the container configuration information and the external configuration information to form the connection of the internal and external allowable environment configuration of the container. The relevant version making work can be executed through a stable API call calling version making tool which is already agreed, all containers except the containers are configured to form a fixed directory organization format after the making is finished, zip packaging is carried out, and the container part is formed locally in a container mirror image form.

It should be noted that, the specific techniques related to version deployment and the specific procedures of application versions in the present application may be implemented according to the prior art, which are conventional technical means in the art, and are not described herein again.

Based on the same principle, the embodiment also discloses an application version automatic construction system based on the container. As shown in fig. 5, in this embodiment, the system includes a version configuration module 11, a version creation module 12, and a version deployment module 13.

The version configuration module 11 is used for determining the program of the application version and source codes of various configurations according to a preset application version model;

the versioning module 12 is used to invoke a versioning tool to convert the source code into target code.

The version deployment module 13 is configured to set a container and an operation parameter of an application version according to the object code.

Preferably, the version configuration module 11 is specifically configured to define a hierarchical relationship of all containers of an application version in a preset application version model and an environment configuration file of each container, and obtain a program of the application version and source codes of various configurations according to the preset application version model after configuring the hierarchical relationship and the environment configuration file.

Preferably, as shown in FIG. 6, the system further includes a version verification module 14. The version verification module 14 is configured to store the target code after the source code is converted into the target code by calling a version creation tool, and perform compliance verification on the stored target code, and if the verification is passed, set a container of an application version according to the target code.

In one specific example, the container-based application version automation construction system may implement application version automation construction by:

step S101: the user completes the development of the program and the running configuration based on the version configuration module 11, including the Docker container based Docker file and the configuration required by the running environment outside the container, and forms the source codes of the program and various configurations organized based on the contract model.

Step S102: the tools that invoke unified versioning module 12 execute an API, or versioning tool, that automatically converts the program and various configured source code organized based on the contract model into a target version, including a number of container images, and their associated running configurations.

Step S103: the version creation module pushes the program and various configured object codes organized based on the version configuration module 11 to a storage device for storing the version object codes, and in this process, the version verification module 10 performs compliance verification on the pushed object codes, such as rejecting related pushing in an irregular manner, so as to ensure the correctness of the API subsequently exposed to the version deployment system.

Step S104: the version deployment module 13 can implement the deployment of the container and the configuration of related matched operation parameters after the reading of the target code by calling the version information acquisition API of the version storage device, and the version deployment system can implement the custom implementation, which is not the scope of the application, and can be a deployment system such as an application operation platform developed based on kubernetes system.

Since the principle of solving the problem of the system is similar to that of the above method, the implementation of the system can be referred to the implementation of the method, and will not be repeated here.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer device, which may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

In a typical example the computer apparatus comprises in particular a memory, a processor and a computer program stored on the memory and executable on the processor, said processor implementing the method as described above when said program is executed.

Referring now to FIG. 7, there is illustrated a schematic diagram of a computer device 600 suitable for use in implementing embodiments of the present application.

As shown in fig. 7, the computer apparatus 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate works and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM)) 603. In the RAM603, various programs and data required for the operation of the system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a liquid crystal feedback device (LCD), and the like, and a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on drive 610 as needed, so that a computer program read therefrom is mounted as needed as storage section 608.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims

1. A container-based application version automation construction method, comprising:

calling a version making tool to convert the source code into a target code;

setting a container and operation parameters of an application version according to the target code;

the method for determining the program and the source codes of various configurations of the application version according to the preset application version model specifically comprises the following steps:

2. The container-based application version automation construction method of claim 1, wherein the environment profile comprises an internal environment profile and an external environment profile.

3. The container-based application version automation construction method of claim 1, further comprising, after invoking a version-making tool to convert the source code to a target code, after:

storing the target code;

4. A container-based application version automation construction system, comprising:

the version deployment module is used for setting the container and the operation parameters of the application version according to the target code;

the version configuration module is specifically used for defining the hierarchical relation of all containers of the application version in a preset application version model and the environment configuration files of all containers, and obtaining the program of the application version and source codes of various configurations according to the preset application version model after the hierarchical relation and the environment configuration files are configured.

5. The container-based application version automation construction system of claim 4, wherein the environment profile comprises an internal environment profile and an external environment profile.

6. The automated container-based application version construction system of claim 4, further comprising a version verification module for storing the object code after invoking a version creation tool to convert the source code into the object code, and performing compliance verification on the stored object code, and if the verification is passed, setting the container of the application version according to the object code.

7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that,

the processor implementing the method according to any of claims 1-3 when executing the program.

8. A computer readable medium having a computer program stored thereon, characterized in that,

the program, when executed by a processor, implements a method as claimed in any one of claims 1-3.