WO2021227564A1

WO2021227564A1 - Application automatic delivery system based on container environment

Info

Publication number: WO2021227564A1
Application number: PCT/CN2021/073966
Authority: WO
Inventors: 罗平; 陈海钊; 季统凯; 贺忠堂
Original assignee: 国云科技股份有限公司
Priority date: 2020-05-13
Filing date: 2021-01-27
Publication date: 2021-11-18
Also published as: CN111654533A

Abstract

Disclosed is an application automatic delivery system based on a container environment. According to the technical solution provided in embodiments of the present application, a central mirror image repository and a local mirror image repository are respectively built in a development environment and a client environment, and mirror image synchronization is controlled by means of a management module, so that automatic mirror image synchronization is achieved in the client environment once a new version of application is released in the development environment, and when updating is detected to be triggered, a proxy end automatically pulls mirror images from a mirror image repository of a server end, constructs scripts, and then deploys brand-new applications. By means of the system, automatic application deployment can be achieved without extra manual intervention.

Description

An application automatic delivery system based on container environment

Technical field

The embodiments of the present application relate to the field of container technology, and in particular, to an application automatic delivery system based on a container environment.

Background technique

At present, traditional monolithic applications have shifted to a micro-service model, and have gradually become the direction of iterative updates of large-scale web application technologies. Due to its lightweight deployment, loosely coupled services and other technical characteristics, microservices enable products to be upgraded and iterated in a more convenient way. Containers, a favorable tool for the iterative and deployment of microservice products, as a lightweight application packaging and isolation technology, enable applications to have high security and portability. The container technology adopts continuous integration and continuous deployment methods, which greatly simplifies the development, testing, and deployment processes, accelerates the delivery of products, and is more in line with today's application market for software products that require continuous iteration, rapid deployment, and high reliability.

However, the current container technology still has the following shortcomings:

1. Container technology is an effective tool for microservices of large-scale monolithic applications. However, the current application methods of microservices containerization on the market mainly highlight the high portability of containerized applications, and only realize the deployment of microservices to Container environment. This method only considers the application itself to simplify the application configuration and avoid the problem of repeated deployment. It does not cause the overhead of the image packaging, import, construction and other processes that are additionally introduced by the container technology. If the technology is not fully utilized, it may bring Continuous delivery, automatic delivery, and rapid deployment advantages.

2. With regard to the continuous delivery and continuous deployment of products between software developers and customers, the current industry’s general operations are mainly divided into two steps: 1. The software developers locally develop, test, and package images, and then deliver the images to Customer operation and maintenance; 2. The customer operation and maintenance talked about image import and deployment. The whole process can meet the basic requirements, but lacks sufficient convenience, many operation steps, and error-prone. There is a lack of a more convenient way between software development and customers to provide support for the continuous deployment of products.

3. The use of container private mirror warehouses is limited to private clouds. But at present, applications across multiple clouds (public cloud, private cloud, hybrid cloud) are very common. To ensure continuous delivery and continuous deployment, it is necessary to ensure that users support access to private container image warehouses in a multi-cloud environment.

Summary of the invention

The embodiment of the present application provides an application automatic delivery system based on a container environment, which can connect the development environment and the customer environment, so that after software development is completed, it can be automatically deployed to the customer environment to realize continuous delivery deployment.

In the first aspect, an embodiment of the present application provides an application automatic delivery system based on a container environment, including: a development end, a server end, and an agent end;

The development end is used to provide a development environment in which container technology is used to build a central mirror warehouse and a business management module is deployed in the development environment. Manage the access authority of the server;

The server is used to provide a customer environment in which container technology is used to build a local mirror warehouse, and a local management module and a mirror synchronization module are deployed in the customer environment. The mirror synchronization module is used to serve as a local management module. Provide a synchronization strategy; the local management module is used to synchronize the mirror information stored on the development end and the server end according to the synchronization strategy of the mirror synchronization module;

The agent end is used to provide an application deployment environment, and the agent end is also used to pull image information and script information from the local mirror warehouse, and perform image construction and application deployment on the agent end.

Further, the central mirror warehouse is used to receive mirror information and corresponding script information uploaded by the software supplier, and update the version information in the mirror information list according to the mirror information;

Correspondingly, the service management module obtains the mirror information list, and determines whether the stored mirror version information is consistent with the version information in the mirror information list. The version information is updated to obtain the current mirror version information.

Further, said synchronizing the mirroring information stored on the development end and the server end includes:

Obtain the current image version information of the development end;

Determine whether the current mirror version information is consistent with the mirror version information stored on the server, and if not, execute the next step;

Pull the corresponding image information and script information from the central image repository of the development end;

Push the mirror information and the script information to the local mirror warehouse of the server.

Further, the pulling image information and script information from the local image repository, and performing image construction and application deployment on the agent side includes:

Determine whether the received current mirror version information is consistent with the mirror version information stored on the agent, if not, proceed to the next step;

Pull the corresponding image information and the script information from the local image warehouse of the server;

Perform image construction according to the image information and perform application deployment according to the script information.

Further, the synchronization strategy of the mirror synchronization module includes:

Obtain the current image version information of the development terminal every preset time; or,

Obtain the current mirror version information of the development terminal at a preset time point.

Further, the management of the access authority of the server includes:

The receiving server sends a mirroring synchronization request and determining whether the corresponding server has access authority according to the mirroring synchronization request, and if so, performing a mirroring synchronization operation. The mirroring synchronization request includes the authority information of the server.

Further, the MQ mirror queue is used for communication between the server and the agent, and the HTTP/HTTPS communication protocol is used for communication between the development and the server.

Further, the server is set in one or more of a private cloud, a hybrid cloud, or a public cloud.

Further, the number of the server and the agent is multiple.

The solution of the embodiment of this application builds a central mirror warehouse and a local mirror warehouse in the development environment and the client environment respectively, and controls the mirror synchronization through the management module, so that as soon as a new version of the application is released in the development environment, the client environment will automatically synchronize the mirrors, and the agent When the client detects that the update is triggered, it automatically pulls the image from the mirror warehouse of the server, builds the script, and then deploys a new application. Through this system, automated application deployment can be achieved without additional manual intervention.

Description of the drawings

FIG. 1 is a structural block diagram of an application automatic delivery system based on a container environment provided by an embodiment of the present application;

Figure 2 is a flowchart of mirroring synchronization between the development end and the server provided by an embodiment of the present application;

FIG. 3 is a flowchart of application deployment on the agent side provided by an embodiment of the present application;

Fig. 4 is a sequence diagram of a method for automatic application delivery based on a container environment provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, specific embodiments of the present application will be described in further detail below with reference to the accompanying drawings. It can be understood that the specific embodiments described here are only used to explain the application, but not to limit the application. In addition, it should be noted that, for ease of description, the drawings only show part of the content related to the present application, but not all of the content. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowchart describes various operations (or steps) as sequential processing, many of the operations can be implemented in parallel, concurrently, or simultaneously. In addition, the order of operations can be rearranged. The processing may be terminated when its operation is completed, but may also have additional steps not included in the drawings. The processing may correspond to methods, functions, procedures, subroutines, subroutines, and so on.

Containerization will enable microservice applications to have excellent portability, but this only simplifies the application deployment process, and does not fundamentally solve the problem of how to quickly deploy applications in the local development environment to the customer's production environment. At present, the practice of deploying by copying application image files offline completely separates the connection between the customer environment and the development environment, and the process is cumbersome and error-prone. Through the method of this embodiment, the software provider environment and the customer environment are opened up, and after software development is completed, it can be automatically deployed to the customer environment to realize continuous delivery and deployment.

Most of the existing application deployment requires manual assistance for deployment, which makes the entire process lack of sufficient convenience. Based on this, the automatic delivery of the application based on the container environment provided by this application builds a central mirror warehouse and a local mirror warehouse in the development environment and the customer environment, and controls the mirror synchronization through the management module, so as to realize the release of a new version of the application in the development environment. The environment automatically synchronizes the mirror, and when the agent detects that the update is triggered, it automatically pulls the mirror from the mirror warehouse on the server, builds the script, and then deploys a new application. The application deployment process is simple and not prone to errors.

FIG. 1 is a structural block diagram of an application automatic delivery system based on a container environment provided by an embodiment of the present application. As shown in FIG. 1, an embodiment of the present application provides an application automatic delivery system based on a container environment, including: a development end , Server and agent;

The development end is used to provide a development environment in which container technology is used to build a central mirror warehouse and a business management module is deployed in the development environment. The access authority of the server is managed.

On the development side, there are Web UI on the center side, business management modules on the center side, and a central mirror warehouse. The center side refers to the software provider environment, which includes software development, testing, and release, and provides Web UI to manage the central warehouse and customer environment groups. Wait for daily maintenance. It also includes the software supplier releasing the new version of the service image to the local mirror warehouse, creating a service release group, and formulating a planned release strategy. In this embodiment, the center end also refers to the development end.

In addition to management, service release groups are also created in this embodiment, which means that different customer environments are divided into groups based on customers. The new version of service mirroring will be based on groups to provide mirror synchronization URLs for qualified customer environments. And Version. The business management module refers to providing functions including central image management and access authority management. Central mirror warehouse management means that after the software supplier completes the new version of the software update test, he manually pushes the original mirror to the central mirror warehouse, and provides APIs for modifying, querying, and deleting mirror information for page calls. Access rights management means that when the client environment initiates a mirror synchronization request, it first checks the verification conditions, then checks whether it meets the grouping environment, and returns the new version of the mirror information, the mirror update URL, and the mirror build script URL if it meets the requirements. Detecting whether it conforms to the grouping environment refers to the management of permissions.

Further, the central mirror repository is used to receive mirror information and corresponding script information uploaded by the software supplier, and update the version information in the mirror information list according to the mirror information.

Correspondingly, the service management module obtains the mirror information list, and determines whether the stored mirror version information is consistent with the version information in the mirror information list. The version information is updated to obtain the current mirror version information. The above steps are mainly to confirm the current mirror version information on the development side. When the mirror version information is confirmed to be inconsistent, the mirror version information stored on the development side can be updated.

The server is used to provide a customer environment in which container technology is used to build a local mirror warehouse, and a local management module and a mirror synchronization module are deployed in the customer environment. The mirror synchronization module is used to serve as a local management module. Provide a synchronization strategy; the local management module is used to synchronize the mirror information stored on the development end and the server end according to the synchronization strategy of the mirror synchronization module.

The server side refers to the client environment. The server side does not perceive the existence of the center side. The environment can also complete management work independently. The software supplier can also upload mirroring and other operations on its own to complete the local environment update.

The aforementioned mirror warehouses on the Center and Server sides refer to private warehouses built based on container technologies such as Docker. This method uses a registry warehouse running in a docker environment. The center end and the server end communicate through https, and the mirror synchronization strategy adopts the docker-based "pull-push" method, which completely shields the heterogeneous cloud environment deployed at the bottom layer, and only requires network interoperability.

The server-side management module refers to a local mirroring module and a mirroring synchronization module. The local mirror management module allows customers to manage mirrors in their environment, providing all the functions and Agent grouping management the same as the Center end except for group management, so that for the customer environment, it also has a logically independent management end. The agent is directly deployed in the application environment which encapsulates the docker client, the server and the agent communicate with MQ mirroring.

The mirror synchronization module means that the server side provides manual and automatic upgrade strategies. If the automatic upgrade strategy is selected, the mirror synchronization timer will periodically access the Center to obtain software version information, and then automatically pull the mirror from the Center to the server mirror warehouse based on the URL of the new mirror and script obtained from the Center. During this process, the server side and the center side network interaction is the only requirement, completely cross-cloud (public cloud, private cloud, hybrid cloud).

As shown in Figure 2, Figure 2 is a flowchart of mirroring synchronization between the development end and the server provided by an embodiment of the present application. The synchronization of the mirror information stored on the development end and the server includes:

S101: Obtain the current image version information of the development end;

S102: Determine whether the current image version information is consistent with the image version information stored on the server, and if not, execute the next step;

S103: Pull the corresponding mirror information and script information from the central mirror warehouse of the development end;

S104: Push the mirror information and the script information to the local mirror warehouse of the server.

The above steps are specific mirror synchronization steps. The mirror version is compared on the server first, and then the mirror information in the central mirror repository is pulled. Finally, the image information created by the development side is pulled to the server side.

The agent end is used to provide an application deployment environment, and the agent end is also used to pull image information and script information from the local mirror warehouse, and perform image construction and application deployment on the agent end. The solution of this embodiment separately builds a central mirror warehouse and a local mirror warehouse in the development environment of the software provider and the customer environment, and manages the near-in real-time synchronization of the mirrors through the management modules on the center and server sides to realize the release of a new version of the application in the development environment. , The customer environment will automatically synchronize the mirroring. When the agent side regularly detects that the update is triggered, it automatically pulls the image from the server side warehouse, builds the script, and deploys a new application. Realize the automatic and rapid deployment of applications to the customer environment.

Further, as shown in FIG. 3, FIG. 3 is a flowchart of application deployment on the agent side provided by an embodiment of the present application. The image information and script information are pulled from the local mirror warehouse and performed on the agent side. Image construction and application deployment, including:

S201: Determine whether the received current mirror version information is consistent with the mirror version information stored on the agent, and if not, execute the next step;

S202: Pull the corresponding mirror information and the script information from the local mirror warehouse of the server;

S203: Perform image construction according to the image information and perform application deployment according to the script information.

The agent side includes the Agent side operation module, which refers to the container operation module integrated with the docker client, and the client's application production environment is deployed in the docker environment. The agent side regularly obtains the new version information and the image and script URL of the application image from the server side. If there is a new version image or a new image, it will pull the image to the local environment and call the startup script to complete the application deployment and update. This process does not require human intervention. , The automation is completed. Through the agent, it is the automatic deployment of the current application without manual intervention.

Fig. 4 is a sequence diagram of an application automatic delivery method based on a container environment provided by an embodiment of the present application. As shown in Fig. 4, based on the automatic delivery system of this embodiment, the above-mentioned automatic delivery method mainly includes the following steps:

Software developers package the developed applications and scripts into docker images and push them to the center image warehouse;

The center management module regularly obtains the docker warehouse image information list;

The center side obtains the request and returns the central warehouse mirror information list;

center compares the mirror version information in the database, and updates if there is no existing version;

Server regularly obtains center mirroring information request;

After the center end passes the group permission detection, it returns the image information including the image url and the container instance construction script url;

The server compares and updates the center image version information;

The server pulls mirror images and script requests from the central mirror warehouse;

The central warehouse on the center side returns mirror images and scripts;

Push the mirror on the server side to the local mirror warehouse;

The server side waits for the upgrade strategy to trigger the agent side image upgrade;

The agent obtains the mirror information from the server;

The server side returns the mirroring information;

The agent compares and updates the server mirror version information;

The agent pulls images and script requests from the local mirror factory library;

The server side returns the image and script;

The agent builds images, executes scripts, and deploys applications. Through the above steps, the application deployment on the client can be realized as soon as the development is completed on the development side. In this embodiment, the server side refers to the server side, the agent side refers to the agent side, and the center side refers to the development side.

The main improvement points of the application rapid delivery system based on the container environment of this embodiment include: 1. Open up the software provider environment and the customer environment. After software development is completed, it can be automatically deployed to the customer environment to achieve continuous delivery and deployment; 2. Software The supplier can manage all customer environments across the cloud, completely shielding the customer's heterogeneous cloud environment; 3. The entire application is fully automated from delivery to final deployment without additional manual intervention.

Since the solution of this embodiment is based on the docker container technology, it is only required that the platform is compatible with docker, and that the Center end and the Server end are network interoperable. The specific implementation method is that the Center and Server use HTTPS communication, and the mirror synchronization is implemented based on the docker image warehouse registry. Through the above method, the heterogeneous cloud environment or physical environment for application deployment is completely shielded, with high performance and guaranteed security.

The solution of this embodiment implements the "Center, Server, Agent" deployment mode. The Center can manage all client environments in groups, but the Server cannot sense the existence of the Center. "Server, Agent" also constitutes an independent local application delivery management The system ensures the testability and modifiability of the system.

The invention provides a rapid application delivery system based on a container environment, which solves the problem of rapid application deployment from a development environment to a customer's production environment, shortens the software development cycle, and reduces operation and maintenance costs. In addition, the hierarchical management deployment method of center and server adopted by this system not only realizes the multi-client requirements of development environment management, but also ensures the independence of the use of the customer environment, which has great economic benefits.

The technical solution provided by the embodiments of this application is to build a central mirror warehouse and a local mirror warehouse in the development environment and the client environment respectively, and control the mirror synchronization through the management module, so that as soon as a new version of the application is released in the development environment, the client environment automatically synchronizes the mirror. , And when the agent detects that the update is triggered, it automatically pulls the image from the mirror warehouse of the server, builds the script, and then deploys a new application. The system realizes automated application deployment without additional manual intervention.

The above are only the preferred embodiments of the present application and the technical principles used. The application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not depart from the protection scope of the application. Therefore, although the application has been described in more detail through the above embodiments, the application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the application. The scope of is determined by the scope of the claims.

Claims

An application automatic delivery system based on a container environment, which is characterized by including: a development end, a server end and an agent end;

The development end is used to provide a development environment in which container technology is used to build a central mirror warehouse and a business management module is deployed in the development environment. Manage the access authority of the server;

The server is used to provide a customer environment in which container technology is used to build a local mirror warehouse, and a local management module and a mirror synchronization module are deployed in the customer environment. The mirror synchronization module is used to serve as a local management module. Provide a synchronization strategy; the local management module is used to synchronize the mirror information stored on the development end and the server end according to the synchronization strategy of the mirror synchronization module;

The agent end is used to provide an application deployment environment, and the agent end is also used to pull image information and script information from the local mirror warehouse, and perform image construction and application deployment on the agent end.
The application automatic delivery system based on the container environment according to claim 1, wherein the central mirror warehouse is used to receive mirror information and corresponding script information uploaded by a software supplier, and to pair the mirror information according to the mirror information. Update the version information in the list;

Correspondingly, the service management module obtains the mirror information list, and determines whether the stored mirror version information is consistent with the version information in the mirror information list. The version information is updated to obtain the current mirror version information.
The application automatic delivery system based on a container environment according to claim 1, wherein said synchronizing the image information stored on the development end and the server end comprises:

Obtain the current image version information of the development end;

Determine whether the current mirror version information is consistent with the mirror version information stored on the server, and if not, execute the next step;

Pull the corresponding image information and script information from the central image repository of the development end;

Push the mirror information and the script information to the local mirror warehouse of the server.
The application automatic delivery system based on a container environment according to claim 3, wherein the pulling image information and script information from the local image repository, and performing image construction and application deployment on the agent side, comprises:

Determine whether the received current mirror version information is consistent with the mirror version information stored on the agent, if not, proceed to the next step;

Pull the corresponding image information and the script information from the local image warehouse of the server;

Perform image construction according to the image information and perform application deployment according to the script information.
The application automatic delivery system based on a container environment according to claim 4, wherein the synchronization strategy of the mirror synchronization module includes:

Obtain the current image version information of the developer terminal every preset time; or,

Obtain the current mirror version information of the development terminal at a preset time point.
The application automatic delivery system based on a container environment according to claim 1, wherein the management of the access authority of the server includes:

The receiving server sends a mirroring synchronization request and determining whether the corresponding server has access authority according to the mirroring synchronization request, and if so, performing a mirroring synchronization operation. The mirroring synchronization request includes the authority information of the server.
The application automatic delivery system based on a container environment according to any one of claims 1-6, wherein the MQ mirror queue is used for communication between the server and the agent, and the development and the server are different from each other. Use HTTP/HTTPS communication protocol to communicate between.
The application automatic delivery system based on a container environment according to any one of claims 1-6, wherein the service management module is also used to provide an application program interface for modifying, querying, and deleting image information for The user makes the call.
The application automatic delivery system based on a container environment according to any one of claims 1-6, wherein the server is set in one or more of a private cloud, a hybrid cloud, or a public cloud.
The application automatic delivery system based on a container environment according to any one of claims 1-6, wherein the number of the server and the agent is multiple.