Application release management system and application release management method based on credential environment

Abstract

The invention relates to an application release management system and an application release management method based on a credential environment, and the system comprises an infrastructure layer which is used for constructing the credential environment according to hardware resources; the publishing system platform layer is used for deploying at least one publishing platform, and the publishing platform is used for publishing an application; the presentation layer is used for providing a user interaction interface and acquiring configuration information of a user; the third-party tool layer is used for providing a release mirror image; the application layer is used for executing an application publishing task according to the publishing platform, the configuration information and the publishing mirror image, and the application layer comprises one or any combination of a login verification module, a publishing window management module, an application module management module, a publishing peripheral resource management module, an application service management module and a publishing configuration management module; and the logic layer is used for carrying out logic abstract packaging on the business of each module in the application layer. According to the invention, applications can be published and managed efficiently and safely in a unified manner.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of application release management, and specifically to an application release management system and an application release management method based on a trusted innovation environment. Background Art

[0002] Against the backdrop of rapid development of information technology and a severe international environment, the trusted innovation environment has become a key platform for software innovation. The revolution in cloud computing has made frequent small-batch releases the key to improving customer satisfaction and market competitiveness. However, with the complexity of infrastructure, application releases face challenges such as cloud migration, off-site disaster recovery, and cloud environment upgrades. The rise of cloud-native technology is accompanied by powerful PaaS container release platforms such as OpenShift and Cloud Foundry. Although these platforms can provide functions such as building, development, and deployment, the management of application releases in the trusted innovation environment is still insufficient, limiting the flexibility and efficiency of enterprises in the cloud environment.

[0003] The shortcomings of existing application release management solutions include: (1) There is a lot of manual intervention in the application service and system migration process, which is prone to errors and leads to a high migration failure rate. (2) They usually focus on specific functions and lack a unified view to monitor cloud resources and application status, which increases the difficulty and cost of operation and maintenance. (3) There is insufficient support for complex cloud infrastructure management and a lack of strategies to simplify application release. (4) There is a lack of flexibility to adapt to market demand and changes in technology stacks, which affects the release speed and quality. (5) Unified release on heterogeneous cloud infrastructure faces challenges in technical differences, which affects resource management and scheduling efficiency.

[0004] In the complex and ever-changing information and innovation environment, the existing application release management solutions cannot uniformly release and manage applications efficiently and securely. Summary of the invention

[0005] The technical problem to be solved by this application is to provide an application release management system and an application release management method based on a trusted innovation environment, which can efficiently and securely release and manage applications in a unified manner, adapt to the complexity and dynamics of the trusted innovation environment, and take into account both release efficiency and application security; it not only supports cross-platform application deployment, but also can intelligently manage the release process to achieve optimal configuration and use of resources.

[0006] The technical solution adopted by the present application to solve the above-mentioned technical problems is an application publishing management system based on a trusted innovation environment, including: an infrastructure layer, which is used to build a trusted innovation environment based on hardware resources; a publishing system platform layer, which is used to deploy at least one publishing platform, and the publishing platform is used to publish applications; a presentation layer, which is used to provide a user interaction interface and obtain user configuration information; a third-party tool layer, which is used to provide a publishing image; an application layer, which is used to perform application publishing tasks based on the publishing platform, configuration information and publishing image, and the application layer includes: a login verification module, a publishing window management module, an application module management module, a publishing peripheral resource management module, an application service management module, and a publishing configuration management module, or any combination of these; a logic layer, which is used to logically abstract and encapsulate the business of each module in the application layer.

[0007] In one embodiment of the present application, the user interaction interface includes: a tenant user interface, including a tenant user login authentication interface, an interactive interface related to the application publishing process, and the tenant user interface is related to the tenant permissions; a platform management interface, including a management interface for the cloud platform administrator to configure the publishing platform, and a tenant authorization interface, and the platform management interface is related to the cloud platform administrator permissions.

[0008] In one embodiment of the present application, the login verification module is configured to: verify the identity of the logged-in user according to the login information; the release window management module is configured to: create a release window according to user instructions and manage and control the execution time of the application release; the application module management module is configured to: create an application module according to user instructions and manage the life cycle of the application module; send the application module to the release platform; synchronize the application module to the trusted innovation environment; the release peripheral resource management module is configured to: create and manage peripheral resources according to user instructions, and the peripheral resources include configuration files and confidentiality dictionaries; the application service management module is configured to: create and manage application services according to user instructions; bind application services, application modules, security domains, functional domains, and container cluster information; the release configuration management module is configured to: generate a release version according to the configuration information, and the configuration information includes copy configuration, template configuration, access configuration, and deployment scheduling configuration; execute application release tasks according to the release version, release image, and release window.

[0009] In one embodiment of the present application, the application layer also includes: one or any combination of an application system management module, a basic data synchronization management module, an automation tool docking management module, and a release and operation and maintenance module; wherein the application system management module is configured to: pull application system information and cache it in a database; authorize tenants at the application system level; the basic data synchronization management module is configured to: synchronize basic data according to the release platform and process the correspondence between the basic data, and the basic data includes workspace groups, workspaces, deployment units, and container clusters; the automation tool docking management module is configured to: dock and manage third-party automation tools and obtain CI / CD deliverables; the release and operation and maintenance module is configured to: perform operation and maintenance operations on application releases, and the operation and maintenance operations include stopping, restarting, starting, and displaying release progress.

[0010] In one embodiment of the present application, the hardware resources include: one or any combination of a server, a memory, a network device, and a load balancer.

[0011] In order to solve the above technical problems, the present application also proposes an application release management method, which uses the above application release management system, including: obtaining and verifying the user's login information, and displaying the relevant interactive interface in the application release process after the verification; creating the configuration information required to execute the application release task according to the user's instructions; and executing the application release task according to the release platform, configuration information and release image.

[0012] In one embodiment of the present application, the steps of creating configuration information required to execute an application publishing task according to user instructions include: creating a publishing window according to user instructions; creating an application module according to user instructions; creating peripheral resources according to user instructions; creating an application service according to user instructions; and generating a publishing version based on the publishing window, application module, peripheral resources, and application service.

[0013] In one embodiment of the present application, the process of creating an application service according to user instructions includes: obtaining application system information from an application system management module; obtaining binding relationship information of basic data from a basic data synchronization management module; obtaining container cluster data published by the application; and creating application service data based on the application system information, binding relationship information, and container cluster data.

[0014] In one embodiment of the present application, in the process of executing an application publishing task based on a publishing platform, configuration information and a publishing image, it includes: obtaining a publishing window and verifying a publishing time; if the current time is outside the publishing time configured in the publishing window, ending the application publishing task; if the current time is within the publishing time configured in the publishing window, executing the application publishing task according to a preset publishing type.

[0015] In one embodiment of the present application, the step of executing an application publishing task according to a preset publishing type includes: if the preset publishing type is manual publishing, and a current publishing failure is detected during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is to be retried, the application publishing task is re-executed according to the manual instruction; if the preset publishing type is automatic publishing, and a current publishing failure is detected during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is to be retried, the application publishing task is placed in a publishing task queue, and the application publishing task is automatically re-executed after waiting for a preset publishing execution cycle.

[0016] The technical solution of the present application uses the presentation layer as a unified management entry point, and makes the release process compatible with the company's specific business process from the perspective of the application system. By providing a unified application system view to manage the entire application, the operational complexity and management cost can be reduced. At the same time, the unified release operation process standard is encapsulated and abstracted, the differences between different release platforms are shielded at the bottom, and the release standard is unified at the top, reducing the complexity of operation and maintenance; the application layer abstracts and encapsulates the operation details of the underlying release resources, and handles the comprehensive step strategy of simplifying application release in a modular manner, reducing the errors that may be caused by manual intervention, so that the application release operation can be completed efficiently, automatically, quickly and safely; the third-party tool layer can integrate emerging automation tools and development and operation and maintenance practices to adapt to the rapidly changing market demands and technology stacks, improve the release speed and quality of applications, and achieve the goals of rapid iteration and continuous delivery; the release system platform layer can shield the technical differences between different cloud service providers and release platforms, and users can use a unified method to efficiently manage and schedule release resources, which is more conducive to the migration, expansion and disaster recovery strategy implementation of applications.

[0017] The present application divides the architecture of the application release management system into different levels. This layered modular design is centered on application release and can provide independent management functions for various peripheral resources used for application release in the form of independent modules. The specific application release and peripheral resources can be associated for overall use. In this way, the functions of each layer and each module are both independent of each other and easy to expand, and can be closely related in business, so that isolation at the application system level can be achieved, which effectively reduces the process of manual intervention and reduces the complexity and risk of the release process. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below with reference to the accompanying drawings, wherein:

[0019] Figure 1 It is a schematic diagram of an application publishing management system based on a trusted innovation environment according to an embodiment of the present application;

[0020] Figure 2It is a schematic diagram of an application publishing management system based on a trusted innovation environment according to another embodiment of the present application;

[0021] Figure 3 is a schematic diagram of the corresponding relationship of basic data in an embodiment of the present application;

[0022] Figure 4 is an exemplary flow chart of an application publishing management method according to an embodiment of the present application;

[0023] Figure 5 It is an exemplary flowchart of an application publishing management method according to another embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below with reference to the accompanying drawings.

[0025] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application may also be implemented in other ways different from those described herein, and therefore the present application is not limited to the specific embodiments disclosed below.

[0026] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0027] Flowcharts are used in the present application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed accurately in order. On the contrary, various steps may be processed in reverse order or simultaneously. At the same time, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0028] This application proposes an application publishing management system based on a trusted innovation environment, which can be applied to scenarios where applications need to be published and managed in a unified and efficient, secure manner.

[0029] Here, we first use an embodiment to introduce the composition of the application publishing management system based on the trusted innovation environment of this application to facilitate the understanding of the technical content below.

[0030] Figure 2 This is a schematic diagram of an application publishing management system based on a trusted innovation environment according to another embodiment of the present application, with reference to Figure 2As shown, the application publishing management system 100 includes: a presentation layer 110, an application layer 120, a logic layer 130, a publishing system platform layer 140, an infrastructure layer 150, a third-party tool layer 160, and a data layer 170. Exemplarily, the above-mentioned layers and modules in each layer in the application publishing management system 100 based on the trust innovation environment of the present application can be implemented by a computer hardware device composed of a processor and a memory, for example, the above-mentioned layers are stored in the memory as program units, and the processor executes each program unit stored in the memory to realize thread control.

[0031] The following text will introduce in detail the application publishing management system 100 based on the trusted innovation environment of this application.

[0032] Figure 1 This is a schematic diagram of an application publishing management system based on a trusted innovation environment according to an embodiment of the present application, with reference to Figure 1 As shown, the application publishing management system 100 based on the trusted innovation environment of this embodiment includes: an infrastructure layer 150, which is used to build a trusted innovation environment based on hardware resources; a publishing system platform layer 140, which is used to deploy at least one publishing platform, and the publishing platform is used to publish applications; a presentation layer 110, which is used to provide a user interaction interface and obtain user configuration information; a third-party tool layer 160, which is used to provide a publishing image; an application layer 120, which is used to perform application publishing tasks according to the publishing platform, configuration information and publishing image, and the application layer 120 includes: a login verification module 121, a publishing window management module 128, an application module management module 122, a publishing peripheral resource management module 127, an application service management module 125, and a publishing configuration management module 124, or any combination of these; a logic layer 130, which is used to logically abstract and encapsulate the business of each module in the application layer 120.

[0033] Combination Figure 2 As shown, for example, the logic layer 130 includes business rules and processing logic, and can perform logical abstraction and encapsulation of the business involved in each module in the application layer 120 in combination with the company's business. The publishing system platform layer 140 can deploy publishing platforms of different manufacturers (such as Figure 2The publishing platform A to the publishing platform D shown in the figure provide basic atomic publishing capabilities and are deployed on the infrastructure of the data center. The third-party tool layer 160 is also the third-party CI / CD tool layer. CI / CD is the abbreviation of continuous integration (Continuous Integration) and continuous delivery / deployment (Continuous Delivery / Deployment). The third-party tool layer 160 can provide third-party automation tools and DevOps (development, operation and maintenance) peripheral system platforms for the publishing portal to connect to and use. These platforms can provide CI / CD deliverables, such as basic images, configuration files, etc. The publishing portal can make choices as needed when publishing applications, so that the entire publishing process can be connected as a whole.

[0034] For example, Figure 2 The data layer 170 shown in FIG. 1 includes a database and a cache library. The database is used to store all user data, logs, permission configuration, resource information, etc. The cache library is used to increase the reading speed and reduce the pressure on the database.

[0035] The technical solution of the present application uses the presentation layer 110 as a unified management entry point, and makes the release process compatible with the company's specific business process from the perspective of the application system. By providing a unified application system view to manage the entire application, the operational complexity and management costs can be reduced. At the same time, an abstract unified release operation process standard is encapsulated to shield the differences between different release platforms at the bottom and unify the release standards at the top, thereby reducing the complexity of operation and maintenance. The application layer 120 abstracts and encapsulates the operation details of the underlying release resources, and handles the comprehensive step strategy of simplifying application release in a modular manner, thereby reducing the errors that may be caused by manual intervention, so that the application release operation can be completed efficiently, automatically, quickly and safely.

[0036] The third-party tool layer 160 of the present application can integrate emerging automation tools and development and operation and maintenance practices to adapt to rapidly changing market demands and technology stacks, improve the release speed and quality of applications, and achieve the goals of rapid iteration and continuous delivery; the release system platform layer 140 can shield the technical differences between different cloud service providers and release platforms, and users can use a unified method to efficiently manage and schedule release resources, which is more conducive to the migration, expansion and implementation of disaster recovery strategies for applications.

[0037] The present application divides the architecture of the application release management system 100 into different levels. This layered modular design is centered on application release and can provide independent management functions for various peripheral resources used for application release in the form of independent modules. The specific application release and peripheral resources can be associated for overall use. In this way, the functions of each layer and each module are both independent of each other and easy to expand, and can be closely related in business, so that isolation at the application system level can be achieved, which effectively reduces the process of manual intervention and reduces the complexity and risk of the release process.

[0038] In some embodiments, the hardware resources include: one or any combination of servers, storage, network equipment, and load balancers. Exemplarily, the infrastructure layer 150 includes various complex information innovation infrastructures that can provide hardware resources for upper-layer services.

[0039] refer to Figure 2 As shown, in some embodiments, the user interaction interface of the presentation layer 110 includes: a tenant user interface, including a tenant user login authentication interface, an interaction interface related to the application publishing process, and the tenant user interface is related to the tenant permissions; a platform management interface, including a management interface for the cloud platform administrator to configure the publishing platform, a tenant authorization interface, a resource synchronization interface, etc., and the platform management interface is related to the cloud platform administrator permissions.

[0040] In some embodiments, the login verification module 121 is configured to: verify the identity of the logged-in user according to the login information. Exemplarily, the login verification module 121 is responsible for the unified identity verification of the logged-in user to ensure the security protection of the user interface.

[0041] Continue to refer Figure 2 As shown, in some embodiments, the publishing window management module 128 is configured to: create a publishing window according to user instructions and manage and control the execution time of application publishing. Exemplarily, the publishing window management module 128 can manage and control the execution time of publishing, and can automatically execute the publishing task within the publishing window time and when the publishing configuration selects automatic publishing, but cannot execute automatic publishing outside the publishing window.

[0042] In actual applications, the company's application release and delivery often have a strict execution window, and administrators often need to wait for the execution window to perform release execution. The configuration of release execution is often relatively complex, and hastily performing release configuration in a short period of time is prone to errors. This application provides administrators with a pre-selected creation of release versions through the release window management module 128, and the specific release task will be automatically executed when the specified release time arrives. Users can configure the release version at any time before the release execution window, and automatically or manually execute the release when the execution window arrives, which can greatly save the operation and maintenance time cost.

[0043] In some embodiments, the application module management module 122 is configured to: create application modules according to user instructions and manage the life cycle of application modules; send application modules to the publishing platform; synchronize application modules to the information creation environment. Exemplarily, the application module management module 122 is an abstract management concept of the publishing platform, and all applications are ultimately published under the application module management module 122. In the publishing control portal, this module mainly manages the life cycle of application modules, including the creation of application modules sent to the underlying publishing platform, and can also provide the ability for the portal application module to be synchronized to the underlying layer to avoid the deletion of underlying resources and cause abnormalities during actual publishing.

[0044] In some embodiments, the publishing peripheral resource management module 127 is configured to: create and manage peripheral resources according to user instructions, and the peripheral resources include configuration files and confidentiality dictionaries. Exemplarily, the publishing peripheral resource management module 127 is responsible for the creation and management of the peripheral resources required for publishing, and serves the publishing configuration management module 124. When an application service is published, it often involves the creation of many resources, and these peripheral resources are created on demand according to different publishing requirements.

[0045] The release peripheral resource management module 127 can perform abstract management of peripheral resources, including the life cycle management of configuration files, the life cycle management of confidential dictionaries, etc. The created resources will be used on demand when publishing configuration management. In the traditional application publishing process, the creation of these peripheral resources is implied in the publishing process, and the manual operation of users during the publishing process is very cumbersome and prone to errors. The present application abstracts the management of these resources by releasing the peripheral resource management module 127, and users can apply them on demand. The present application can unify the abstract strategy and standardize the publishing process to simplify the execution of user publishing details.

[0046] Continue to refer Figure 2 As shown, in some embodiments, the application service management module 125 is configured to: create and manage application services according to user instructions; bind application services, application modules, security domains, functional domains, and container cluster information. Exemplarily, the application service management module 125 can abstractly manage user-level application services and perform operations such as creating, deleting, and editing application services. When a user creates an application service, the created application service can be bound to surrounding resources such as application modules, security domains, functional domains, and container cluster information. When the application is published, it will be published to the bound cluster without the user having to pay attention to the details of the publication. The present application can simultaneously perform isolation at the security domain and functional domain levels to meet the security isolation requirements of the company's business level.

[0047] In some embodiments, the release configuration management module 124 is configured to: generate a release version according to configuration information, the configuration information includes copy configuration, template configuration, access configuration, and deployment scheduling configuration; and execute application release tasks according to the release version, release image, and release window. Exemplarily, the release configuration management module 124 is the core module of the entire release, which can abstract the steps of the release process and unify the release process. The peripheral resources and CI / CD deliverables of other modules can be used by the release configuration management module 124.

[0048] Exemplarily, the release configuration determines how the release of the application service is executed and the final state of the application service, including the published copy configuration, template configuration, access configuration, deployment and scheduling configuration, the image used for the release, configuration files, etc. After the final release configuration is applied, a release version will be formed, and the release version contains the resources to be used in each step of the process. When the release is executed, you only need to select the release version to be executed to execute the release, which ultimately determines the final state of the release. This application is set up so that during the release period, the release executor only needs to pay attention to the version to be released this time to quickly release and deliver it, and the release configuration can be left to more professional release administrators to set.

[0049] Continue to refer Figure 2 As shown, in some embodiments, the application layer 120 also includes: one or any combination of: an application system management module 123, a basic data synchronization management module 1210, an automated tool docking management module 129, and a release operation and maintenance module 126; wherein the application system management module 123 is configured to: pull application system information and cache it in a database; and authorize tenants at the application system level. Exemplarily, the application system management module 123 can handle the logic of pulling and caching application system information for the entire company, can pull application system information from the company's third-party system and cache it in the database of the release control portal, and the application system information used by the portal can all be derived from the application system management module 123, and the authorization of the application system tenant level is also processed by business logic in this module to achieve tenant isolation at the application system level.

[0050] In some embodiments, the basic data synchronization management module 1210 is configured to: synchronize basic data according to the publishing platform and process the corresponding relationship of the basic data, where the basic data includes a workspace group, a workspace, a deployment unit, and a container cluster. Figure 3 is a schematic diagram of the basic data correspondence relationship in an embodiment of the present application, refer to Figure 3 As shown, exemplarily, a workspace group may include multiple workspaces; a workspace may include multiple deployment units; a deployment unit corresponds to a container cluster; a container cluster may include multiple namespaces; and a namespace may correspond to different application systems.

[0051] For example, the release and execution of an application service is ultimately based on the underlying release platform, so the underlying release platform needs to provide basic data information, including the correspondence between workspace groups, workspaces, container clusters, and deployment units. These basic data do not need to be provided to users, and users do not need to pay attention to these details. At the usage level, users only need to pay attention to which cluster their application services should be released to. These basic data are needed during the release and execution process.

[0052] The basic data synchronization management module 1210 of the present application can synchronize the basic data, and the portal can synchronize these basic data from the underlying publishing platform and process the data correspondence. The processed data will be available for users to select clusters when they create application services. After the user selects a cluster, the program will indirectly know the workspace corresponding to the cluster when publishing, and will know how to publish when the publishing task is executed. At the same time, the basic data synchronization management module 1210 also provides a data migration function, which can synchronize basic data information from the bottom layer to the publishing portal to ensure data consistency.

[0053] refer to Figure 2 As shown, in some embodiments, the automation tool docking management module 129 is configured to: dock and manage third-party automation tools and obtain CI / CD deliverables. Exemplarily, the automation tool docking management module 129 can be docked and managed with third-party automation tools. After the abstraction of the automation tool docking management module 129, it is convenient to quickly integrate different third-party automation tools. After docking, the CI / CD deliverables can be obtained from the third-party automation tool platform, including some configuration files, basic images for construction, etc. These deliverables will provide optional configuration options for users to use when the release configuration management module 124 performs release configuration of application services.

[0054] In some embodiments, the release and maintenance module 126 is configured to perform operation and maintenance operations on application release, including stopping, restarting, starting, and displaying release progress.

[0055] The overall architecture of the application publishing management system 100 of this application is as follows Figure 2As shown, the overall application release control is located on top of the existing release platforms of different manufacturers. The idea of ​​modular design is adopted to abstract and split the different functions of the release platform and hide the implementation details, thereby realizing overall release control. This application provides users with unified user login authentication, release operations and other functions, and provides a unified release control process in terms of operation methods, standardizing the company's business release process and reducing the process of manual intervention. The release control of this application is also flexibly integrated with third-party automation tools and DevOps practices to improve the release speed and quality of the application and achieve the goals of rapid iteration and continuous delivery.

[0056] The present application also proposes an application release management method, using the application release management system 100 as mentioned above. Figure 4 is an exemplary flow chart of an application publishing management method according to an embodiment of the present application, with reference to Figure 4 As shown, the application publishing management method of this embodiment includes the following steps:

[0057] Step S110: Acquire and verify the user's login information, and display the relevant interactive interface during the application release process after the verification is passed.

[0058] Step S120: Create configuration information required to execute the application publishing task according to user instructions.

[0059] Step S130: Execute the application publishing task according to the publishing platform, configuration information and publishing image.

[0060] Exemplarily, steps S110 to S130 are equivalent to steps executed inside the application publishing management system 100 . Figure 5 is an exemplary flow chart of an application publishing management method according to another embodiment of the present application. Figure 5 Some of the steps shown in the figure are equivalent to the steps when the user performs the process operation. Figure 5 The above steps S110 to S130 are described in detail:

[0061] In step S110, the user's login information is obtained and verified, and after the verification is passed, the relevant interactive interface in the application publishing process is displayed. Figure 5 Steps in the tenant user interface. Figure 5 As shown in the figure, the user logs in to the publishing portal interface and enters the user password for login verification. If the verification passes, the user will be redirected to the tenant user operation interface. If it fails, a login authentication failure prompt will be given.

[0062] In step S120, configuration information required for executing the application publishing task is created according to the user instruction. Exemplarily, step S120 corresponds to Figure 5The steps in the release window management module 128, the application module management module 122, the release peripheral resource management module 127, and the application service management module 125 are performed.

[0063] In some embodiments, the step of creating configuration information required to execute the application publishing task according to the user instruction includes:

[0064] Step S121: Create a publishing window according to the user instruction. Figure 5 As shown, in the publishing window management module 128, the user creates a publishing window from the operation interface.

[0065] Step S122: Create an application module according to the user instruction. Figure 5 As shown, in the application module management module 122, the user creates an application module.

[0066] Step S123: Create surrounding resources according to user instructions. Figure 5 As shown, in the publishing peripheral resource management module 127, the user can create the peripheral resources required for publishing as needed. The peripheral resources include configuration files, confidentiality dictionaries, PV / PVC (PersistentVolume / PersistentVolumeClaim) and other storage resources.

[0067] Step S124: Create application services according to user instructions. Figure 5 As shown, in the application service management module 125, the user can create an application service. The application service is an abstract representation of the user's application. When it is created, it will obtain the application system information from the application system management module 123 and the binding relationship information of the basic data from the basic data synchronization management module 1210. The user selects the container cluster data that the application service needs to publish, and then creates the application service data, so that the target cluster and related basic data to be published by the application service will be bound accordingly. The application system management module 123 and the basic data synchronization management module 1210 are not displayed to the user. The functions of these two modules are automatically and periodically managed by the program for data synchronization cache management, and can be used directly when the application service is created.

[0068] Step S125: Generate a release version based on the release window, application module, peripheral resources, and application service. Figure 5 As shown, after the application service is created, the user will enter the interface of the core publishing configuration management module 124, which is mainly used by the user to configure the publishing process. According to actual needs, the surrounding resource data can be obtained from the resources pre-created by the publishing surrounding resource management module 127 for configuration and use, and finally a publishing version representing the publishing process and status will be generated.

[0069] In some embodiments, in step S124, the process of creating an application service according to a user instruction includes:

[0070] Step S124a: Acquire application system information from the application system management module.

[0071] Step S124b: Obtain binding relationship information of basic data from the basic data synchronization management module.

[0072] Step S124c: Obtain container cluster data published by the application.

[0073] Step S124d: Create application service data according to the application system information, binding relationship information, and container cluster data.

[0074] Exemplarily, the above steps S124a to S124d correspond to Figure 5 The steps in the application service management module 125.

[0075] In step S130, the application publishing task is executed according to the publishing platform, configuration information and publishing image. Exemplarily, step S130 corresponds to Figure 5 The steps in the configuration management module 124 are published in Figure 5 As shown, after the release version is created, the release operation of the application is started. When executing the release operation, a request will first be sent to the automation tool docking management module 129 to obtain the deliverables corresponding to the application service on the automation platform, such as the basic image and configuration file required for release, and the obtained deliverables are provided for the user to select the object. Then the program will obtain the pre-configured release window data to verify the release time.

[0076] In some embodiments, in combination Figure 5 As shown in the steps of the release configuration management module 124, in the process of executing the application release task according to the release platform, configuration information and release image, it includes:

[0077] Step S131: Get the publishing window and verify the publishing time.

[0078] Step S132: If the current time is outside the publishing time configured in the publishing window, the application publishing task is terminated. For example, if the current time is outside the publishing time configured in the publishing window, it means that it is not within the window, publishing is not allowed, and the entire publishing process is terminated.

[0079] Step S133: If the current time is within the publishing time configured in the publishing window, the application publishing task is executed according to the preset publishing type. Exemplarily, if the current time is within the publishing window, the publishing process will continue to be executed to check whether automatic publishing is performed.

[0080] In some embodiments, in step S133, the step of executing the application publishing task according to the preset publishing type includes:

[0081] Step S133a: If the preset publishing type is manual publishing, and the current publishing fails during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is to be retried, the application publishing task is re-executed according to the manual instruction. For example, if it is manual publishing, the manual publishing process will be executed, and the user will manually trigger the publishing.

[0082] Step S133b: If the preset publishing type is automatic publishing, and the current publishing fails during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is to be retried, the application publishing task is put into the publishing task queue, and the application publishing task is automatically re-executed after waiting for the preset publishing execution cycle. For example, if it is automatic publishing, the publishing task will be put into the publishing task queue, and the application publishing will be automatically executed when it expires.

[0083] Exemplarily, the present application performs steps S110 to S130 and Figure 5 After following the steps shown, an application will eventually be released to the specified environment for operation as needed. After that, users can perform related release and maintenance through the application release and maintenance interface as needed, including restarting, stopping, and checking release progress of the application.

[0084] The present application also includes a computer-readable medium storing a computer program code, which, when executed by a processor, implements the application publishing management method described above.

[0085] When the application release management method is implemented as a computer program, it can also be stored in a computer-readable storage medium as a product. For example, a computer-readable storage medium may include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD), a digital versatile disk (DVD)), a smart card, and a flash memory device (e.g., an electrically erasable programmable read-only memory (EPROM), a card, a stick, a key drive). In addition, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media (and / or storage media) that can store, contain and / or carry code and / or instructions and / or data.

[0086] It should be understood that the embodiments described above are only illustrative. The embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processor may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and / or other electronic units designed to perform the functions described herein, or a combination thereof.

[0087] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0088] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0089] The basic concepts have been described above. Obviously, for those skilled in the art, the above application disclosure is only an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0090] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0091] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of the present application are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

Claims

1. An application release management system based on a trusted innovation environment, characterized in that: include: The infrastructure layer is used to build the information innovation environment based on hardware resources; The publishing system platform layer is used to deploy at least one publishing platform, which is used to publish applications; The presentation layer is used to provide a user interface and obtain user configuration information; The third-party tool layer is used to provide release images; An application layer, used to execute application publishing tasks according to the publishing platform, the configuration information and the publishing image, the application layer comprising: a login verification module, a publishing window management module, an application module management module, a publishing peripheral resource management module, an application service management module, and a publishing configuration management module, or any combination thereof; The logic layer is used to perform logical abstraction and encapsulation of the services of each module in the application layer.

2. The application publishing management system according to claim 1, characterized in that: The user interaction interface comprises: Tenant user interface, including tenant user login authentication interface and related interactive interface during application publishing. The tenant user interface is related to tenant permissions; The platform management interface includes a management interface for cloud platform administrators to configure and publish the platform and a tenant authorization interface. The platform management interface is related to the cloud platform administrator's permissions.

3. The application publishing management system according to claim 1, characterized in that: The login verification module is configured to: verify the identity of the login user according to the login information; The publishing window management module is configured to: create a publishing window according to a user instruction and manage and control the execution time of application publishing; The application module management module is configured to: create an application module according to user instructions and manage the life cycle of the application module; send the application module to the publishing platform; synchronize the application module to the information creation environment; The publishing peripheral resource management module is configured to: create and manage peripheral resources according to user instructions, and the peripheral resources include configuration files and confidentiality dictionaries; The application service management module is configured to: create and manage application services according to user instructions; bind the application services, the application modules, the security domains, the functional domains, and the container cluster information; The release configuration management module is configured to: generate a release version according to the configuration information, the configuration information including copy configuration, template configuration, access configuration, and deployment scheduling configuration; and execute an application release task according to the release version, the release image, and the release window.

4. The application publishing management system according to claim 1 or 3, characterized in that: The application layer also includes: an application system management module, a basic data synchronization management module, an automation tool docking management module, and a release operation and maintenance module, or any combination thereof; wherein, The application system management module is configured to: pull application system information and cache it in a database; authorize tenants at the application system level; The basic data synchronization management module is configured to: synchronize basic data according to the publishing platform and process the corresponding relationship of the basic data, the basic data including workspace groups, workspaces, deployment units, and container clusters; The automation tool docking management module is configured to: dock and manage third-party automation tools and obtain CI / CD deliverables; The publishing and operation module is configured to perform operation and maintenance operations on application publishing, and the operation and maintenance operations include stopping, restarting, starting, and displaying publishing progress.

5. The application publishing management system according to claim 1, characterized in that: The hardware resources include: one or any combination of servers, storage devices, network devices, and load balancers.

6. An application release management method, characterized in that: Using the application release management system according to any one of claims 1 to 5, comprising: Obtain and verify the user's login information, and display the relevant interactive interface during the application release process after verification; Create the configuration information required to execute the application release task according to user instructions; The application publishing task is executed according to the publishing platform, the configuration information and the publishing image.

7. The application publishing management method according to claim 6, characterized in that: The steps of creating the configuration information required to execute the application release task according to the user instructions include: Creating a publishing window according to the user instruction; Creating an application module according to the user instruction; Creating surrounding resources according to the user instructions; Creating an application service according to the user instruction; A release version is generated according to the release window, the application module, the peripheral resources, and the application service.

8. The application publishing management method according to claim 7, characterized in that: The process of creating the application service according to the user instruction includes: Obtain application system information from the application system management module; Obtain the binding relationship information of basic data from the basic data synchronization management module; Get the container cluster data published by the application; Application service data is created according to the application system information, the binding relationship information, and the container cluster data.

9. The application publishing management method according to claim 6, characterized in that: The process of executing the application publishing task according to the publishing platform, the configuration information and the publishing image includes: Get the release window and verify the release time; If the current time is outside the publishing time configured in the publishing window, then the application publishing task is terminated; If the current time is within the publishing time configured in the publishing window, the application publishing task is executed according to the preset publishing type.

10. The application publishing management method according to claim 9, characterized in that: The steps of executing the application publishing task according to the preset publishing type include: If the preset publishing type is manual publishing, and the current publishing failure is detected during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is to be retried, the application publishing task is re-executed according to the manual instruction; If the preset publishing type is automatic publishing, and the current publishing failure is detected during the application publishing process, the user is asked whether to retry the application publishing; if the application publishing is retried, the application publishing task is placed in the publishing task queue, and the application publishing task is automatically re-executed after waiting for the preset publishing execution cycle.

Images