An online method of a cloud-native application

Abstract

The application relates to the technical field of cloud service deployment, and provides an online method of a cloud native application, which comprises the following steps: registering middleware instance service information into a product center through a middleware management service; uploading installation files corresponding to the cloud native application to the product center, and filling in middleware instance deployment information; calling the middleware management service in parallel according to the middleware instance deployment information through the product center to execute hatching and configuration of the middleware instance; and installing the installation files into corresponding namespaces according to the hatched and configured middleware instance through the product center to generate the cloud native application. According to the online method of the cloud native application, the online difficulty of the cloud native application can be reduced, the utilization rate of middleware instance resources can be optimized, and the efficiency of the online of the cloud native application can be improved.

Description

Technical Field

[0001] This invention relates to the field of cloud service deployment technology, and in particular to a method for deploying cloud-native applications. Background Technology

[0002] In the scenario of deploying cloud-native applications, a complete cloud-native application that can provide services externally includes the cloud-native application service itself and the various middleware instances required by the cloud-native application service. Middleware instances need to be incubated and able to provide services normally before the cloud-native application is deployed. In particular, some middleware instances require additional configuration after incubation to provide services normally for the cloud-native application.

[0003] In practical applications, some information about the middleware instances required by cloud-native applications is unavailable before the middleware instances are providing normal services. Currently, there are two main solutions to this problem. One is to encapsulate the middleware instance within the cloud-native application. This approach increases the coupling of the cloud-native application itself, thereby increasing deployment difficulty, reducing observability, and extending deployment time. The second approach involves performing middleware instance incubation, subsequent configuration of the middleware instance, and configuring the middleware instance information for the cloud-native application before deployment in stages. For cloud-native application deployment, this approach requires the application to not only deploy its own services but also to deploy and configure customized middleware instances. Furthermore, for some cloud-native applications, which may already have incubated instances, manual incubation and configuration of middleware instances or configuration of other shareable middleware instances are necessary. This process is complex, reducing deployment efficiency and increasing business complexity.

[0004] Therefore, how to automatically incubate middleware instances that cloud-native applications depend on before they go live, and how to improve the utilization rate of middleware instances, have become urgent technical problems to be solved. Summary of the Invention

[0005] In view of this, in order to overcome the shortcomings of the existing technology, the present invention provides a method for deploying cloud-native applications.

[0006] On one hand, this invention provides a method for deploying cloud-native applications, including:

[0007] Step S1: Register middleware instance service information with the product center through the middleware management service;

[0008] Step S2: Upload the installation file corresponding to the cloud-native application to the product center and fill in the middleware instance deployment information;

[0009] Step S3: Based on the middleware instance deployment information, the middleware management service is invoked in parallel through the product center to perform the incubation and configuration of the middleware instance;

[0010] Step S4: Install the installation files to the corresponding namespace based on the successfully incubated and configured middleware instance through the product center to generate a cloud-native application.

[0011] Furthermore, step S1 of the cloud-native application deployment method of the present invention includes: calling the interface provided by the product center at startup through the middleware management service, registering the middleware instance type, middleware instance configuration method and middleware instance incubation parameters with the product center, and persistently storing and displaying them through the product center.

[0012] Furthermore, step S2 of the cloud-native application deployment method of the present invention includes: uploading the installation file corresponding to the cloud-native application to the product center, selecting the middleware instance type corresponding to the cloud-native application on the product center page, and filling in the middleware instance deployment information according to the middleware instance type. The middleware instance deployment information includes name, affinity, shared attributes, middleware instance incubation parameters, and middleware instance configuration parameters.

[0013] Furthermore, step S3 of the cloud-native application deployment method of the present invention includes:

[0014] Step S31: Generate a deployment task through the product center to record and display the current deployment status of cloud-native applications and persist it for storage;

[0015] Step S32: Create corresponding namespaces for cloud-native applications through the product center;

[0016] Step S33: Based on the middleware instance deployment information of the cloud-native application, the product center calls the middleware management service corresponding to the middleware instance type in parallel to perform the incubation of the middleware instance;

[0017] Step S34: Based on the middleware instance configuration parameters and configuration method, the product center calls the middleware management service corresponding to the middleware instance type in parallel to execute the configuration of the middleware instance.

[0018] Furthermore, in step S33 of the cloud-native application deployment method of the present invention, the middleware management service corresponding to the middleware instance type is called in parallel to perform the incubation of the middleware instance, including:

[0019] Select the corresponding incubation namespace for the middleware instance based on the shared attribute in the middleware instance deployment information. When the shared attribute is a shared instance, the namespace where the middleware management service is located is used as the namespace for the incubated middleware instance; when the shared attribute is a non-shared instance, the namespace where the cloud-native application is located is used as the namespace for the incubated middleware instance.

[0020] Check if the middleware instance already exists in the namespace of the incubated middleware instance. If the middleware instance does not exist, render the middleware instance resource file according to the name, affinity, and middleware instance incubation parameters in the middleware instance deployment information, and perform middleware instance incubation. If the middleware instance exists, determine whether the middleware instance incubation parameters of the existing middleware instance are consistent with the middleware instance incubation parameters in the middleware instance deployment information. If they are inconsistent, upgrade the middleware instance according to the middleware instance incubation parameters in the middleware instance deployment information.

[0021] Furthermore, in step S33 of the cloud-native application deployment method of the present invention, the parallel invocation of the middleware management service corresponding to the middleware instance type to perform the incubation of the middleware instance also includes:

[0022] The product center calls the middleware management service to check the incubation status of middleware instances. When the incubation of a middleware instance exceeds the preset time, the status of the online task is changed to "middleware instance incubation failed", and the information is persisted and displayed on the page.

[0023] Once a middleware instance is successfully incubated, the product center calls the middleware management service to obtain the connection method of the middleware instance and persists it. When all middleware instances are successfully incubated, the status of the online task is changed to "middleware instance successfully incubated," and after persistent storage, it is displayed on the page.

[0024] Furthermore, in step S34 of the cloud-native application deployment method of the present invention, the middleware instance configuration method is defined by an array of JSON objects. Each JSON object in the array includes a configuration step number, a call interface address, and call interface parameters.

[0025] Furthermore, step S34 of the cloud-native application deployment method of the present invention includes: after the middleware instance is successfully incubated, the product center matches the corresponding parameters in the middleware instance configuration parameters according to the configuration step number and the call interface parameters, assigns values ​​to the call interface parameters, and calls the corresponding call interface address with the assigned call interface parameters to execute the configuration of the middleware instance.

[0026] Furthermore, step S4 of the cloud-native application deployment method of the present invention includes: matching the connection method of the middleware instance in persistent storage according to the name in the middleware instance deployment information through the product center, using the matching connection method of the middleware instance as the installation parameter of the installation file, installing the installation file to the namespace corresponding to the cloud-native application, and generating the corresponding cloud-native application.

[0027] Furthermore, step S4 of the cloud-native application deployment method of the present invention further includes: cyclically checking the running status of the cloud-native application through the product center; if the cloud-native application in the namespace is not fully ready after a preset time period, interrupting the deployment process, changing the status of the deployment task to deployment failure, persisting the data, and displaying it on the page; and when the status of all cloud-native applications in the namespace is running, changing the status of the deployment task to deployment success, persisting the data, and displaying it on the page.

[0028] The cloud-native application deployment method of this invention has the following beneficial effects:

[0029] 1. By calling the middleware management service through the product center to automatically incubate middleware instances and configure the incubated middleware instances, the process of deploying cloud-native applications has been optimized. This allows cloud-native application deployment to focus only on its own installation files and processes, without having to perform middleware instance incubation and configuration.

[0030] 2. The product center configures shared middleware instances between cloud-native applications through middleware management services, optimizing the utilization of middleware instance resources.

[0031] 3. It can improve the efficiency of deploying cloud-native applications. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart illustrating a method for deploying a cloud-native application, as exemplarily described in the first embodiment of the present invention.

[0034] Figure 2 This is a flowchart illustrating a method for deploying a cloud-native application, as exemplarily described in the second embodiment of the present invention.

[0035] Figure 3 This is a flowchart illustrating a method for deploying a cloud-native application, as exemplarily described in the third embodiment of the present invention.

[0036] Figure 4 This is a flowchart illustrating a cloud-native application deployment method according to an exemplary fourth embodiment of the present invention. Detailed Implementation

[0037] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0038] It should be noted that, in the absence of conflict, the following embodiments and features can be combined with each other; and, based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0039] It should be noted that various aspects of embodiments within the scope of the appended claims are described below. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any particular structure and / or function described herein is merely illustrative. Based on this disclosure, those skilled in the art will understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement the device and / or practice the method. Additionally, this device and / or method can be implemented using structures and / or functionalities other than one or more of the aspects set forth herein.

[0040] Figure 1 This is a flowchart of a cloud-native application deployment method according to an exemplary first embodiment of the present invention, such as... Figure 1 As shown, the method in this embodiment includes:

[0041] Step S1: Register middleware instance service information with the product center through the middleware management service;

[0042] Step S2: Upload the installation file corresponding to the cloud-native application to the product center and fill in the middleware instance deployment information;

[0043] Step S3: Based on the middleware instance deployment information, the middleware management service is invoked in parallel through the product center to perform the incubation and configuration of the middleware instance;

[0044] Step S4: Install the installation files to the corresponding namespace based on the successfully incubated and configured middleware instance through the product center to generate a cloud-native application.

[0045] Step S1 of the method in this embodiment includes: calling the interface provided by the product center at startup through the middleware management service, registering the middleware instance type, middleware instance configuration method and middleware instance incubation parameters with the product center, and persistently storing and displaying them through the product center.

[0046] Step S2 of the method in this embodiment includes: uploading the installation file corresponding to the cloud-native application to the product center, selecting the middleware instance type corresponding to the cloud-native application on the product center page, and filling in the middleware instance deployment information according to the middleware instance type. The middleware instance deployment information includes name, affinity, shared attributes, middleware instance incubation parameters, and middleware instance configuration parameters.

[0047] Figure 2 This is a flowchart illustrating a method for deploying a cloud-native application according to an exemplary second embodiment of the present invention. This embodiment is... Figure 1 Preferred embodiments of the method shown, such as Figure 2 As shown, step S3 of the method in this embodiment includes:

[0048] Step S31: Generate a deployment task through the product center to record and display the current deployment status of cloud-native applications and persist it for storage;

[0049] Step S32: Create corresponding namespaces for cloud-native applications through the product center;

[0050] Step S33: Based on the middleware instance deployment information of the cloud-native application, the product center calls the middleware management service corresponding to the middleware instance type in parallel to perform the incubation of the middleware instance;

[0051] Step S34: Based on the middleware instance configuration parameters and configuration method, the product center calls the middleware management service corresponding to the middleware instance type in parallel to execute the configuration of the middleware instance.

[0052] Figure 3 This is a timing flowchart of a cloud-native application deployment method according to an exemplary third embodiment of the present invention. Figure 1 and Figure 2 A preferred embodiment of the method shown.

[0053] like Figure 3 As shown, in step S33 of this embodiment, the middleware management service corresponding to the middleware instance type is called in parallel to perform the incubation of the middleware instance, including:

[0054] Select the corresponding incubation namespace for the middleware instance based on the shared attribute in the middleware instance deployment information. When the shared attribute is a shared instance, the namespace where the middleware management service is located is used as the namespace for the incubated middleware instance; when the shared attribute is a non-shared instance, the namespace where the cloud-native application is located is used as the namespace for the incubated middleware instance.

[0055] Check if the middleware instance already exists in the namespace of the incubated middleware instance. If the middleware instance does not exist, render the middleware instance resource file according to the name, affinity, and middleware instance incubation parameters in the middleware instance deployment information, and perform middleware instance incubation. If the middleware instance exists, determine whether the middleware instance incubation parameters of the existing middleware instance are consistent with the middleware instance incubation parameters in the middleware instance deployment information. If they are inconsistent, upgrade the middleware instance according to the middleware instance incubation parameters in the middleware instance deployment information.

[0056] like Figure 3 As shown, in step S33 of this embodiment, the parallel invocation of the middleware management service corresponding to the middleware instance type to perform middleware instance incubation further includes:

[0057] The product center calls the middleware management service to check the incubation status of middleware instances. When the incubation of a middleware instance exceeds the preset time, the status of the online task is changed to "middleware instance incubation failed", and the information is persisted and displayed on the page.

[0058] Once a middleware instance is successfully incubated, the product center calls the middleware management service to obtain the connection method of the middleware instance and persists it. When all middleware instances are successfully incubated, the status of the online task is changed to "middleware instance successfully incubated," and after persistent storage, it is displayed on the page.

[0059] In step S34 of this embodiment, the middleware instance configuration method is defined by an array of JSON objects. Each JSON object in the array includes a configuration step number, a call interface address, and call interface parameters.

[0060] In practical applications, step S34 of the method in this embodiment includes: after the middleware instance is successfully incubated, the product center matches the corresponding parameters in the middleware instance configuration parameters according to the configuration step number and the call interface parameters, assigns values ​​to the call interface parameters, and calls the corresponding call interface address with the assigned call interface parameters to execute the configuration of the middleware instance.

[0061] Figure 4 This is a timing flowchart of a cloud-native application deployment method according to an exemplary fourth embodiment of the present invention. Figure 1 A preferred embodiment of the method shown.

[0062] like Figure 4 As shown, step S4 of the method in this embodiment includes:

[0063] The product center matches the connection method of the middleware instance in the persistent storage based on the name in the middleware instance deployment information. The matching connection method of the middleware instance is used as the installation parameter of the installation file, and the installation file is installed to the namespace corresponding to the cloud-native application to generate the corresponding cloud-native application.

[0064] The product center continuously checks the running status of cloud-native applications. If the cloud-native applications in the namespace are not fully ready after a preset time, the deployment process is interrupted, the deployment task status is changed to deployment failure, and the information is persisted and displayed on the page. When all cloud-native applications in the namespace are running, the deployment task status is changed to deployment success, and the information is persisted and displayed on the page.

[0065] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for deploying cloud-native applications, characterized in that, The method includes: Step S1: Register middleware instance service information with the product center through the middleware management service; Step S2: Upload the installation file corresponding to the cloud-native application to the product center and fill in the middleware instance deployment information; Step S3: Based on the middleware instance deployment information, the middleware management service is invoked in parallel through the product center to perform the incubation and configuration of the middleware instance; Step S4: Install the installation files to the corresponding namespace through the product center based on the successfully incubated and configured middleware instance to generate a cloud-native application; Step S3 includes: Step S31: Generate a deployment task through the product center to record and display the current deployment status of cloud-native applications and persist it for storage; Step S32: Create corresponding namespaces for cloud-native applications through the product center; Step S33: Based on the middleware instance deployment information of the cloud-native application, the product center calls the middleware management service corresponding to the middleware instance type in parallel to perform the incubation of the middleware instance; Step S34: Based on the middleware instance configuration parameters and middleware instance configuration method, the product center calls the middleware management service corresponding to the middleware instance type in parallel to execute the middleware instance configuration; In step S33, the middleware management service corresponding to the middleware instance type is invoked in parallel to perform the incubation of the middleware instance, including: Select the corresponding incubation namespace for the middleware instance based on the shared attribute in the middleware instance deployment information. When the shared attribute is a shared instance, the namespace where the middleware management service is located is used as the namespace for the incubated middleware instance; when the shared attribute is a non-shared instance, the namespace where the cloud-native application is located is used as the namespace for the incubated middleware instance. Check if the middleware instance already exists in the namespace of the incubated middleware instance. If the middleware instance does not exist, render the middleware instance resource file according to the name, affinity, and middleware instance incubation parameters in the middleware instance deployment information, and perform middleware instance incubation. If the middleware instance exists, determine whether the middleware instance incubation parameters of the existing middleware instance are consistent with the middleware instance incubation parameters in the middleware instance deployment information. If they are inconsistent, upgrade the middleware instance according to the middleware instance incubation parameters in the middleware instance deployment information.

2. The method for deploying cloud-native applications according to claim 1, characterized in that, Step S1 includes: calling the interface provided by the product center at startup through the middleware management service, registering the middleware instance type, middleware instance configuration method and middleware instance incubation parameters with the product center, and persistently storing and displaying them through the product center.

3. The method for deploying cloud-native applications according to claim 1, characterized in that, Step S2 includes: uploading the installation file corresponding to the cloud-native application to the product center, selecting the middleware instance type corresponding to the cloud-native application on the product center page, and filling in the middleware instance deployment information according to the middleware instance type. The middleware instance deployment information includes name, affinity, shared attributes, middleware instance incubation parameters, and middleware instance configuration parameters.

4. The method for deploying cloud-native applications according to claim 1, characterized in that, Step S33, which involves concurrently calling the middleware management service corresponding to the middleware instance type to perform middleware instance incubation, also includes: The product center calls the middleware management service to check the incubation status of middleware instances. When the incubation of a middleware instance exceeds the preset time, the status of the online task is changed to "middleware instance incubation failed", and the information is persisted and displayed on the page. Once a middleware instance is successfully incubated, the product center calls the middleware management service to obtain the connection method of the middleware instance and persists it. When all middleware instances are successfully incubated, the status of the online task is changed to "middleware instance successfully incubated," and after persistent storage, it is displayed on the page.

5. The method for deploying cloud-native applications according to claim 1, characterized in that, The middleware instance configuration method in step S34 is defined as a JSON object array. Each JSON object in the array includes the configuration step number, the call interface address, and the call interface parameters.

6. The method for deploying cloud-native applications according to claim 5, characterized in that, Step S34 includes: after the middleware instance is successfully incubated, the product center matches the corresponding parameters in the middleware instance configuration parameters according to the configuration step number and the call interface parameters, assigns values ​​to the call interface parameters, and calls the corresponding call interface address with the assigned call interface parameters to execute the configuration of the middleware instance.

7. The method for deploying cloud-native applications according to claim 1, characterized in that, Step S4 includes: matching the connection method of the middleware instance in persistent storage based on the name in the middleware instance deployment information through the product center, using the matching connection method of the middleware instance as the installation parameter of the installation file, installing the installation file to the namespace corresponding to the cloud-native application, and generating the corresponding cloud-native application.

8. The method for deploying cloud-native applications according to claim 1, characterized in that, Step S4 also includes: cyclically checking the running status of cloud-native applications through the product center; if the cloud-native applications in the namespace are not fully ready after a preset time period, interrupting the deployment process, changing the status of the deployment task to deployment failure, persisting the data, and displaying it on the page; when the status of all cloud-native applications in the namespace is running, changing the status of the deployment task to deployment success, persisting the data, and displaying it on the page.

Images