TW202020659A - System and methods for rapid deployment of containerized applications - Google Patents

Abstract

The disclosure provides a system and methods for rapid deployment of containerized applications. In the disclosure, one or multiple applications are combined to construct a configuration file of containerized applications based on a descriptive file combination and transformed to be configuration data related to at least one container management cluster and an interdependence between one or multiple applications. The user changes parameters via various interfaces provided by the system, and the system accordingly checks the resource condition and the interdependence configuration of the container management cluster. The disclosure technically solve the difficulties of inter container cluster systems, while allowing the user to construct the cluster of applications and activate the applications rapidly, such that the problems of limited invokable applications of the system can be solved.

Description

System and method for quickly providing containerized software service

The present invention generally relates to a system and method for providing software services in a container computing environment. More specifically, exemplary embodiments of the present invention relate to systems and methods for deploying software services to multiple container management cluster environments and quickly providing software services.

LXC (Linux Containers), also known as containers or software containers, is a virtualization technology at the computer OS layer. Containers can be packaged (such as image files), which can include: software services, software service dependencies (for example, software use Services), software service operating environment (such as environment variables, privileges, etc.), software libraries, other executable files and configuration files, packaged into a software container (Container).

The Docker software project allows the software services in the container to be automatically run on the operating system of the physical computer device or virtual machine, and provides an isolated sandbox mechanism so that the software containers do not affect each other, with only a slight overhead. Many containers can run on the same computer system.

Container cluster systems (such as Kubernetes, Mesos, Docker Swarm, etc.) provide functions to manage container clusters. The main functions of the container cluster management system include: using Docker or similar technologies to package, instantiate and run software services; run and manage containers across hosts in a clustered manner; solve the problems of running between different hosts Communication problems between containers, etc. To simplify container/container cluster deployment, containers or container clusters are usually modularized and provided as services. Container as a Service (CaaS, Container as a Service) refers to container-based virtualization, which involves the delivery of container cluster management, container orchestration, and underlying computing resources as services (for example, from cloud infrastructure providers) to end users. Software service developers usually use CaaS solutions to deploy new container-based software services.

However, in traditional solutions, for users who wish to deploy one or more software services on a container cluster, the process of deploying software services may be inefficient and cumbersome. For example, for container-based software services, even if the container cluster is provided as CaaS, the CaaS provided by different container cluster systems may be different in the application service deployment. Therefore, application service developers often face the task of rewriting code or reconfiguring software service parameters. If they plan to deploy container-based software services on multiple container cluster systems, this is inefficient, cumbersome, and increases the possibility of errors Increase the maintenance cost of software services. In addition, users of software services often need to spend a long time to clarify the relationship between multiple software services and design the configuration before obtaining an instance of the software service. This not only consumes time, but also increases the activation of software services. The possibility of failure.

In view of the shortcomings of the above-mentioned traditional solutions, the inventor of the present case is anxious to improve and innovate, and successfully developed and applied this system and method for rapidly providing containerized software services.

In order to achieve the above object of the invention, one aspect of the present invention may be a system for quickly providing containerized software services. The system operates on one or more physical servers or virtual machines or a cluster of physical machines and virtual machines mixed to operate. The system includes one or more software applications, one or more databases, one or more servers, one or more tools, and one or more software containers. The servers are used to execute the software containers, not limited to physical devices or virtual machines; and the software containers are used to host the system itself and related applications; the software applications include the underlying operating host Software programs such as procedures, APIs, and upper-layer user interfaces; these tools are used to collect application data of these software applications and store the application data in these databases.

In order to achieve the above object, one aspect of the present invention may be a method of creating a containerized software service template. This method can include the following steps: one or more software services, using an effective markup language (such as JSON superset), specifically configured to be a type of message based on a human-readable text format (textual format); this text format message is The above system is converted into model data of software services that can be used across systems. The content of the data includes various software constants, variables, and permissions control. The system stores the data in the database; the system can execute new data according to the instructions received. Add, delete, and modify templates, etc.

In order to achieve the above object, one aspect of the present invention may be a method of creating a containerized software service instance. This method can include the following steps: a user of a software service, using the interface provided by the system (such as a graphical interface and an API), through authorization verification to obtain a list of available software service templates; select the desired software on the list Service, provide the minimum variables and software control related information according to the demand; this system determines the user command, selects the target container cluster system according to the user's needs, and deploys one or more software containers through the container cluster system and combines into the target software service ; The system provides the software instructions and necessary data required by the user according to different environments (for example, the database service provides the user login account password).

The present invention proposes a system and method for quickly providing containerized software services that integrate the above-described aspects and various possible extensions. The present invention can convert software services into text-formatted templates that can be dynamically adapted to the container cluster system through text format messages. In order to allow software service users to quickly activate one or more software services according to their needs.

The above content presents a summary description of the present invention (covering the problems solved by the present invention, the means adopted and the effects achieved), in order to provide a basic understanding of the present invention. The above content is not intended to summarize all aspects of the invention. In addition, the above content is neither a key or necessary element for confirming any or all aspects of the invention, nor is it for describing the scope of any or all aspects of the invention. The purpose of the foregoing is to present some concepts of some aspects of the invention in a simple form.

In order to make the above-mentioned features and advantages of the present invention more obvious and understandable, the embodiments are specifically described below and described in detail in conjunction with the accompanying drawings.

The present invention discloses a system and method for quickly providing containerized software services. In the present invention, one or more application softwares are combined to create a description file of a containerized software service through a graphical interface provided by the system administrator through the system. The description file includes various software constants, variables and permissions Information such as control is converted into a cross-system format and exists in this system database. After verifying the authority, the software user authorized by the system can deploy the software composed of one or more containerized software through the user interface provided by the system, changing the parameter value or not according to the need. service.

Although the following description describes specific titles in the figures, in various embodiments, the specific modules, databases, procedures, and user interfaces illustrated in the figures may be repeated, renamed, and combined with other described entities, Divided into additional entities, or omitted. In addition, although a particular set of modules can be described in this document as appearing in various combinations, this term should not be understood as implying any specific ordering of the operations of the entities described herein, nor any of the information flow. Specific directionality.

Please refer to FIG. 1 for the architecture diagram of a system and method for rapidly providing containerized software services. In various embodiments, the system may include a user portal 100, which may be used for user authorization verification management and user interaction with the system, and may be used to present user information, such as new software service templates Add, modify, delete and activate software services. In various embodiments, the user portal 100 may include a user rights management module 101, which may include user control of the following rights, such as template creation, modification, deletion, service permission, and priority control. It is stored in or not stored in the persistent storage database of this system, but all must access the relevant authority information in a safe way. The user portal 100 may also include a user interface 102, which may provide a variety of information presentations, provide an administrator user rights management operation interface, and provide user interaction functions.

In various embodiments, the user interface 102 can coordinate the template management module 112 and the container cluster adaptation module 113 through the central management program 110, and the database module 120 obtains data and adjusts the adaptation to organize user requests. Software service template information, and in response presents the available software service template information to the user, for example, from the catalog of software service templates and the available list of software service templates. In various embodiments, the user portal 100 may perform user command tasks by receiving interaction from the user, for example, adding a software service template or enabling a software service. In various embodiments, the user portal 100 may be configured to present the results of various user command tasks to the user. In various embodiments, the user portal 100 may also request feedback from the user when necessary, for example, after completing the service.

In various embodiments, the system may include a DATABASE module 120 whose function is persistent storage, which may include one or more databases. In various embodiments, it can be understood that the database module 120 may include various storage devices or systems. The database module 120 may include a software image file database 121, which may be configured to store information such as but not limited to the following: software container image files, software container image source records, software container image version records, Software container image dependencies and other related information. The database module 120 may also include a software model database 122, which may be configured to store information such as but not limited to the following: software container model description, software service information, software service instance, dependent package information, basic software Startup sequence, etc. The database module 120 may also include a software supply record database 123, which may be configured to store information such as but not limited to the following: software service supply model source, software service supply model creation information, software service demanders, Software service activation date, software service activation report, etc. The database module 120 may also include a permission database 124, which may be configured to store information such as, but not limited to, the following: user relative software service template usage permission information, user relative software service activation permission information Permission information for creators of software service templates, permission information for software service enablers, permission information for system administrators, etc. Although the database module 120 is illustrated in FIG. 1 as including a software image file database 121, a software model database 122, a software supply record database 123, and a rights database 124, in various embodiments, the database module 120 can use other different databases or any suitable structure to store information according to usage and needs. In various embodiments, the database module 120 may be distributed among multiple systems and/or devices.

In various embodiments, the system may include a central management program 110. The central management program 110 can provide various interfaces, such as a user graphical interface (UI) or an application program interface (API), which can be used by the user interface 102 or by various modules or programs that communicate with the system. In various embodiments, it can be understood that such interfaces may include interfaces such as a RESTful API (Representation State Transfer API) or a terminal command-line, but are not limited to these examples.

Please refer to FIG. 2 for a flowchart of a method for creating a containerized software service template. FIG. 2 illustrates an example method 200 for accessing software service templates according to various embodiments. Although FIG. 2 illustrates specific example operations for example method 200, in various embodiments, example method 200 may include additional operations, omit the illustrated operations, and/or combine the illustrated operations.

In various embodiments, the example method 200 may be performed by one or more examples of the system shown in FIG. In various embodiments, a containerized software service template can be created by a user (software service template creator) interacting with the user portal 100, through the operation user interface 102, after being authenticated by the user rights management module 101, and then through the in-process authentication software Service template creator authority 201. After the user obtains the permission, he can enter the editing software service template interface, and enter the process 202 to access the software service template. Here, accessing the template includes adding, deleting, and modifying templates. Group 111 is configured to analyze the markup language input by the user terminal, convert the common template content of the cross-container management cluster system, and achieve the action of creating or updating one or more software service templates. After that, the process proceeds to create or update a software service template 203, which is converted into configuration data about the interdependence between the container management cluster and the software service through the system. Enter the process 205 to create a task report, enter the data and action content and results into the persistent storage through the recording module 114, and enter the decision process for opening the open software service. The user determines whether to open the template to modify the results through the report data. Open can choose to temporarily save as a draft template to enter the process 206 or delete the previously changed software service template to enter the process 207, if you decide to open it, this software service template is opened to software service users with assigned permissions as a template to start the software service Go to process 206.

The final change decision above is performed by the template management module 112 and saved and interacted with the recording module 114, and then the persistent data is stored through the software template database 122. After the status report of the software service template is created in the process 206, the above method flow can be repeated to add, delete and modify other software service templates, or submit the software service template change report that is the process 208 and through the recording module 114 to the software supply record The database 123 records software supply data, which can be configured to store information such as but not limited to: software service supply model image file source, software service supply model creation information, software service model creator, software Service template usage permission related data and software service template create summary report.

Please refer to Figure 3 for a flow chart of a method for creating a containerized software service instance. FIG. 3 illustrates an example method 300 of creating a containerized software service according to various embodiments. Although FIG. 3 illustrates specific example operations for example method 300, in various embodiments, example method 300 may include additional operations, omit the illustrated operations, and/or combine the illustrated operations.

In various embodiments, the example method 300 may be performed by one or more examples of the system shown in FIG. Create a containerized software service template that can be used by users (software service users) to interact with the user portal 100, through the operation user interface 102, after verification by the user rights management module 101, through the process to verify the software service user rights 301, use After gaining permission, the user can enter the software service directory and list interface. The process 302 indicates that the user can obtain the software service template through the template management module 112 and decide which software service to start. In process 303, the target container cluster system is selected according to the user's needs, and the resource situation and dependency configuration of the container management cluster are checked through the container cluster adaptation module 113, and one or more software containers are deployed in the container cluster system and configured Target software service and start software service. If the start of the software service fails and the error cannot be located, enter the process 304 to end the method, and in all other cases, enter the process 305 software service creation task status report. After the process 305, the user can choose whether to continue to create other software services. After the user’s task of creating a software service is completed, the process 306 is entered to generate an end report. The content of the report information can be configured to store information such as but not limited to the following: software service introduction, software service operating instructions, software service connection method Information, software service user account password, software service health status, and software service restrictions, and the recording module 114 records all information related to the activation of the software service. The information content can be configured to store such as but not limited to the following The information of each party: the source of the software service supply model, the software service creation information, the software service demander, the software service activation date, and the software service activation summary report.

Although the above description of the implementation method has mentioned some embodiments for the purpose of illustration, without departing from the scope of the present invention, various alternatives and/or etc. can be achieved by other means to achieve the same purpose Examples or implementations to replace the examples shown and described. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is obvious that the embodiments described herein are only limited by the scope of the patent application.

[Features and effects]

The previous traditional technology is mainly based on a closed set of software service templates, and can only provide software services for a single container management cluster system. The system and method for rapidly providing containerized software services of the present invention have the following advantages when compared with other conventional technologies:

1. The present invention provides a unified board for different container management cluster systems to achieve the characteristics of a cross-container management cluster system.

2. The present invention allows users to create templates freely without being limited by the system itself, and maximizes the number and possibility of templates.

3. The present invention is designed for the user's convenience, user management graphic interface and other APIs, so that users can create complex software services or simply enable software services according to different technical capabilities.

4. According to the convenience of the user, the present invention designs a user management graphic interface and other APIs, so that the user can easily initialize the settings and observe the data flow path of the current cluster structure and the status of the members of the current cluster structure.

5. The system provided by the present invention conforms to the basic characteristics of the cloud (Essential Characteristics), including: On-demand Self-service, Broad Network Access, Resource Pooling, and rapid flexibility (Rapid Elasticity) and Measured Service.

Although the present invention has been disclosed as above with the embodiments, it is not intended to limit the present invention. Any person with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be subject to the scope defined in the appended patent application.

100: User portal 101: User rights management module 102: User interface 110: Central management program 111: Markup language module 112: Template management module 113: Container cluster adaptation module 114: Recording module 120: Database module 121: software image database 122: software model database 123: software supply record database 124: permission database 200 ~ 208: process flow for creating a containerized software service model 300 ~ 306: creating containerized software Service instance method flow

Figure 1 is an architecture diagram of a system and method for quickly providing containerized software services; Figure 2 is a flowchart of a method for creating a containerized software service template; Figure 3 is a flowchart of a method for creating a containerized software service example.

100: User entrance

101: User rights management module

102: User interface

110: central management program

111: Markup Language Module

112: Model management module

113: Container cluster matching module

114: Recording module

120: Database module

121: Software image database

122: Software sample database

123: Software supply record database

124: Permission database

Claims (5)

A system for quickly providing containerized software services, including: one or more servers; a user entry program running on the one or more servers, configured with a graphical, application programming interface (application programming) interface, API) and command line to provide system services to the user, and the user can use it to perform the following actions: set and confirm user permissions, manage software service templates, create software services; and a central management program that runs on On the one or more servers, it uses the software service description provided by the user to provide the software service template of the cross-container management cluster to facilitate the cross-container management cluster to quickly start the software service; and a database model The group, running on the one or more servers, includes a plurality of databases, and provides a persistent storage function. The system as described in item 1 of the patent application scope, wherein the user entry procedure includes: a user authority management module for authority management, responsible for setting and confirming the authority of the user, and if the user’s authority Abnormal permissions will prevent the user from creating the software service template or allow the user to start the software service; a user interface, according to the user to enter the necessary data to create the software service template: specify the appropriate to start the Multiple container cluster systems for software services, source of container software image files, environmental parameters assigned by the system by the container software, environmental parameters assigned by the container software to the user, and available through the graphical, API, and command line methods Observe the current status of the software service template to manage the software service template. The system as described in item 2 of the patent application scope, in which the central management program includes: a markup language module, analyzes the markup language input by the user, converts the common sample content of the cross-container management cluster system, and accesses the database module Persistent storage area in the group and displayed in the user interface; a board management module, to perform logical management of the software service template, by the user in the process of creating the software service template; a container cluster with a suitable model Group, when you need to edit the software service template and start the software service, perform logical operations; a record module, used as the software service template modification record and the start software service, in which the markup language module and the template management module Groups, the container cluster adaptation module and the recording module interact with each other, access the database module for continuous storage and display on the user interface. A method for adding, deleting, and modifying containerized software service templates to obtain materials for quickly starting software services. The steps include: A. Editing containerized software service templates, which are interacted by users and user portals; B. Through operations After the user interface is verified by permissions, the creator service permission of the software service template is verified in the process, and the operation input data is added to add, delete, and modify the software service template; C. After editing the software service template, the action The content and results enter the persistent storage database; D. Decide whether to open the software service activation; E. Return the revised task report of the software service model; F. Use the user interface to confirm the status of the software service model. A method for starting a containerized software service, providing the function of starting a software service across a container management cluster, and achieving the result of quickly starting the software service through a software service template. The steps include: A. Users and user portals of the software service Interaction; B. Through the operation user interface, after verifying the permissions, verify the permissions of the creator of the software service through the process, start operating the input data to start the software service; C. start the software service; D. decide whether to enable other software services, If yes, return to step B; E. According to step D, reply to a user's software service auxiliary data report, which includes: introduction of the software service, operation instructions of the software service, connection methods and information of the software service, The user account password of the software service, the health status of the software service, and the software service restrictions, so that the user can normally connect to the software service that is activated; F. According to step D, activate the activation status of the software service , Which includes: whether the software service is successfully started, the cause of the failure of the software service, and the resource quota of the software service, so that the user can understand the activation of the software service. G. Generate an end report, which includes: the source of the software service model, the creation information of the software service, the demander of the software service, the start date of the software service, the start summary report of the software service, and the action content And the results are stored in the database module.

Images