Cloud application deployment method and apparatus

Abstract

Disclosed in the embodiments of the present application are a cloud application deployment method and apparatus, which are used for improving the deployment efficiency and deployment security of a cloud application. The method in the embodiments of the present application comprises: a cloud data center receiving an asset creation request, wherein the asset creation request is used for requesting the creation and hosting of a cloud application in a cloud market, the asset creation request carries the cloud application, and the cloud application comprises one or more of the following: an image, and application software; on the basis of the asset creation request, generating asset parameters, wherein the asset parameters comprise an asset identifier, and the asset parameters are used for generating an interface function of a deployment template, the interface function of the deployment template being used for making a query, on the basis of the asset identifier, to the cloud market for an application identifier corresponding to the cloud application, and the application identifier comprising one or more of the following: an image identifier (ID), and a uniform resource locator (URL) of the application software; and executing the deployment template on a deployment platform, wherein the deployment template is used for calling the interface function to make a query to the cloud market and deploy the cloud application.

Description

A cloud application deployment method and device

[0001] The present application claims priority to Chinese Patent Application No. 202410788726.X, filed on June 18, 2024, entitled "A cloud asset deployment method and device", and Chinese Patent Application No. 202411131932.X, filed on August 16, 2024, entitled "A cloud application deployment method and device", the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of cloud computing, and in particular to a cloud application deployment method and device. BACKGROUND

[0003] With the development of cloud computing technology, cloud computing technology has evolved from a service form of information technology resources to a standard architecture paradigm of a new generation of software. Various industries will further embrace cloud computing. In the application layer of cloud computing technology, merchants can develop various cloud applications and upload the cloud applications to a cloud market. Users can obtain the cloud applications from the cloud market and deploy the cloud applications on a deployment platform.

[0004] In the current cloud application deployment scheme, a user deploys a cloud application based on a deployment template. The deployment template includes a uniform resource locator (URL) of a software package of the cloud application. After obtaining the deployment template, the user can obtain the corresponding cloud application through the URL of the software package of the cloud application in the template.

[0005] However, since the deployment process of the cloud application includes multiple stages such as merchant deployment template debugging, cloud market certification testing, and cloud application asset publishing, the URL of the software package of the cloud application in the deployment template is modified by the developer in each stage. The developer needs to frequently modify the deployment template, which is tedious and results in low deployment efficiency of the cloud application. In addition, since the URL of the software package of the cloud application is written in the deployment template, once the deployment template is leaked, the user can obtain the cloud application without purchase, which results in poor deployment security of the cloud application. SUMMARY

[0006] Embodiments of the present application provide a cloud application deployment method. In the deployment method, a merchant side or a user side can request an application identifier corresponding to a cloud application from a cloud market in real time through an interface function in a deployment template, thereby improving the deployment efficiency and deployment security of the cloud application. Embodiments of the present application also provide a cloud application deployment device, a computing device, a computing device cluster, a computer readable storage medium, and a computer program product corresponding to the cloud application deployment method.

[0007] In a first aspect, an embodiment of the present application provides a cloud application deployment method. The method can be executed by a computing device, or by a component of the computing device, such as a processor, a chip, or a chip system of the computing device, or by a logic module or software that can implement all or part of the functions of the computing device. The method provided in the first aspect includes: receiving, by a cloud data center, an asset creation request, the asset creation request being used to request creation and hosting of a cloud application in a cloud market, the asset creation request carrying the cloud application, the cloud application including one or more of the following: an image and application software. Generating, by the cloud data center, asset parameters based on the asset creation request, the asset parameters including an asset identifier, an asset version, and an asset type, the asset parameters being used to generate an interface function of a deployment template, the interface function of the deployment template being used to query an application identifier corresponding to the cloud application from the cloud market according to the asset identifier, the application identifier including one or more of the following: an image identifier ID and an application software uniform resource locator URL. Executing, by the cloud data center, the deployment template on a deployment platform, the deployment template being used to call the interface function to query and deploy the cloud application from the cloud market.

[0008] In the cloud application deployment template developed by the merchant end in the embodiment of the present application, the application identifier corresponding to the cloud application can be requested from the cloud market in real time through the interface function, and the cloud application can be obtained according to the application identifier and the cloud application deployment can be completed. Compared with the current way of directly writing the application identifier into the deployment template in the development of the deployment template, in the cloud application deployment method in the embodiment of the present application, the application identifier can be queried from the cloud market in real time based on the interface function in the deployment template, so that the application identifier in the deployment template does not need to be modified in different scenarios of the cloud application deployment, thereby improving the deployment efficiency of the cloud application. At the same time, querying the application identifier from the cloud market by calling the interface function avoids leakage of the application identifier in the deployment template, thereby improving the security of the cloud application deployment.

[0009] In a possible implementation, after the cloud data center generates the asset parameters based on the asset creation request, when the merchant needs to update the cloud application corresponding to the asset identifier, the merchant sends an updated version of the cloud application to the cloud market, the cloud data center receives the updated version of the cloud application sent by the merchant, and the updated version of the cloud application is used to update the cloud application corresponding to the asset parameters in the cloud market. The cloud data center modifies the cloud application corresponding to the asset parameters according to the updated version of the cloud application, wherein the asset ID does not change, and the asset version changes with the updated version of the cloud application.

[0010] In the embodiment of the present application, when the merchant needs to update the cloud application corresponding to the asset identifier, the updated version of the cloud application can be updated to the cloud market again, without the need to modify the deployment template, thereby simplifying the update steps of the cloud application, improving the update efficiency of the cloud application, and further improving the cloud application deployment efficiency of the deployment template.

[0011] In a possible implementation, the merchant end can not carry the cloud application when sending the asset creation request to the cloud market, and in this case, the asset creation request sent by the merchant end to the cloud market is used to request the cloud market to assign asset parameters. The merchant end can separately upload the image or application package for the asset parameters after sending the asset creation request.

[0012] In the embodiments of the present application, the merchant end can upload the cloud application to the cloud market through the asset creation request, or upload the cloud application to the cloud market through a separate request. The multiple uploading modes of the cloud application improve the richness of the cloud application deployment method.

[0013] In a possible implementation, during the process in which the cloud data center deploys the platform to execute the deployment template, the deployment platform invokes the interface function in the deployment template. The cloud market of the cloud data center receives a first interface function invocation request sent by the deployment platform based on the deployment template, and the first interface function invocation request carries the merchant identity information. The cloud market verifies the merchant identity information. If the verification of the merchant identity information is passed, the cloud market sends an application identifier to the deployment platform, so that the deployment platform obtains and deploys the cloud application based on the application identifier. If the verification of the merchant identity information is not passed, the cloud market reports an error to the deployment platform.

[0014] In the embodiments of the present application, in the test scenario of the deployment template of the cloud application by the merchant, the deployment platform can invoke the interface function in the deployment template to obtain the application identifier, and further obtain and deploy the cloud application according to the application identifier, thereby improving the application deployment efficiency of the cloud application in the deployment template test scenario.

[0015] In a possible implementation, before the cloud data center receives the first interface function invocation request sent by the deployment platform based on the deployment template, the cloud data center receives a test request sent by the merchant. The test request is used to request to test the deployment template. The cloud market sends a first deployment link to the merchant based on the test request, and the first deployment link is used to test the deployment template in the deployment platform. After receiving the first deployment link, the merchant tests the deployment template in the deployment platform based on the first deployment link.

[0016] In the embodiments of the present application, in the test scenario of the deployment template of the cloud application by the merchant, the merchant can send a test request of the deployment template to the cloud market, and the cloud market returns a deployment link to the merchant, thereby improving the realizability of the deployment template test scheme.

[0017] In a possible implementation, when the deployment template test fails, the merchant renews the interface function, for example, updates the deployment template, checks whether the asset parameters of the interface function are correct, and corrects them. Or the merchant updates the cloud application corresponding to the asset parameters, for example, the merchant re-uploads the cloud application to the cloud market.

[0018] In the test scenario of the deployment template of the cloud application by the merchant in the embodiment of the application, when the deployment template test fails, the merchant can update the interface function or update the cloud application corresponding to the asset parameter, thereby improving the success rate of deployment of the cloud application.

[0019] In a possible implementation, in the process of the deployment platform executing the deployment template, the cloud data center receives a second interface function call request sent by the deployment platform based on the deployment template, and the second interface function call request carries subscription information of the cloud application. After receiving the second interface function call request, the cloud market verifies the subscription information. If the subscription information of the cloud application passes the verification, the cloud market sends an application identifier to the deployment platform, so that the deployment platform obtains the cloud application based on the application identifier. If the subscription information of the cloud application does not pass the verification, the cloud market reports an error to the deployment platform.

[0020] In the embodiment of the application, in the scenario of deploying the cloud application based on the deployment template by the user, the deployment platform can call the interface function in the deployment template to obtain the application identifier, and further obtain and deploy the cloud application according to the application identifier, thereby improving the application deployment efficiency of the cloud application in the deployment template use scenario. Meanwhile, in the process of the deployment platform calling the interface function in the deployment template to obtain the application identifier, the cloud market can verify the subscription information of the user, thereby improving the deployment security of the cloud application in the deployment template use scenario.

[0021] In a possible implementation, the cloud data center receives a cloud application subscription request sent by a user, the cloud application subscription request is used to obtain a deployment template of a cloud application, the cloud market sends a second deployment link to the user based on the cloud application subscription request, and the second deployment link is used to start the deployment template on a deployment platform. After the user obtains the second deployment link, the user performs deployment of the cloud application on the deployment platform.

[0022] In the embodiment of the application, in the scenario of deploying the cloud application based on the deployment template by the user, the user needs to subscribe to the required cloud application from the cloud market, the cloud market sends a deployment link of the cloud application to the user based on the cloud application subscription request, and the user completes the deployment of the cloud application based on the deployment link of the cloud application, thereby improving the deployment security of the cloud application in the deployment template use scenario.

[0023] In a second aspect, the embodiments of the present application provide a cloud application deployment method. The method can be executed by a computing device, or by a component of the computing device, such as a processor, a chip or a chip system of the computing device, or by a logic module or software that can realize all or part of the functions of the computing device. The method provided in the second aspect includes: a cloud application subscription request sent by a user to a cloud market, the cloud application subscription request being used to obtain a deployment template of a cloud application. The cloud market sends a second deployment link to a user end based on the cloud application subscription request, the second deployment link being used to obtain the deployment template of the cloud application. After the user end obtains the deployment template of the cloud application, the deployment template is executed on a deployment platform, wherein the deployment template includes an interface function, and after the interface function is called, the deployment platform queries an application identifier of the cloud application from the cloud market based on an asset identifier in the interface function, so as to further obtain and deploy the cloud application based on the application identifier, wherein the cloud application includes an image and application software, and the application identifier includes an image ID and an application software URL.

[0024] In the embodiments of the present application, the user end can request the application identifier of the cloud application from the cloud market in real time through the interface function in the deployment template, and obtain the cloud application and complete the deployment of the cloud application according to the application identifier, thereby improving the deployment efficiency of the cloud application. At the same time, the interface function is called to query the application identifier from the cloud market, which avoids the leakage of the application identifier in the deployment template, thereby improving the security of the deployment of the cloud application.

[0025] In a possible fact way, the deployment platform sends a second interface function call request to the cloud market based on the interface function during the execution of the deployment template, wherein the second interface function call request carries an asset ID and subscription information of the cloud application. After the cloud market receives the second interface function call request, the cloud market verifies the subscription information of the cloud application carried in the second interface function, and if the subscription information of the cloud application is verified, the cloud market sends the application identifier to the deployment platform, so that the deployment platform can obtain the cloud application based on the application identifier.

[0026] In the embodiments of the present application, the cloud market can verify the subscription information of the user during the process in which the deployment platform calls the interface function in the deployment template to obtain the application identifier, thereby improving the security of the deployment of the cloud application in the use scenario of the deployment template.

[0027] In a third aspect, an embodiment of the present application provides a cloud application deployment apparatus. The apparatus includes a transceiver and a processor. The transceiver is configured to receive an asset creation request, the asset creation request being used to request creation and hosting of a cloud application in a cloud marketplace, and the asset creation request carrying the cloud application, the cloud application including one or more of an image and application software. The processor is configured to generate asset parameters based on the asset creation request, the asset parameters including an asset identifier, an asset version, and an asset type, the asset parameters being used to generate an interface function of a deployment template, the interface function of the deployment template being used to query an application identifier corresponding to the cloud application from the cloud marketplace according to the asset identifier, the application identifier including one or more of an image identifier ID and an application software uniform resource locator URL. The processor is further configured to execute the deployment template on a deployment platform, the deployment template being used to call the interface function to query and deploy the cloud application from the cloud marketplace.

[0028] In a possible implementation, the transceiver is further configured to receive a cloud application update version sent by a merchant, the cloud application update version being used to update the cloud application corresponding to the asset parameters in the cloud marketplace, and the processor is further configured to modify the cloud application corresponding to the asset parameters according to the cloud application update version.

[0029] In a possible implementation, the transceiver is specifically configured to receive a first interface function call request sent by the deployment platform based on the deployment template, the first interface function call request carrying merchant identity information. If the merchant identity information is verified, the cloud marketplace sends the application identifier to the deployment platform, so that the deployment platform acquires and deploys the cloud application based on the application identifier.

[0030] In a possible implementation, the transceiver is further configured to receive a test request sent by a merchant, the test request being used to request testing of the deployment template, and a first deployment link is sent to the merchant based on the test request, the first deployment link being used to test the deployment template on the deployment platform.

[0031] In a possible implementation, the processor is further configured to update the interface function or the cloud application corresponding to the asset parameters when the deployment template fails.

[0032] In a possible implementation, the transceiver is further configured to receive a second interface function call request sent by the deployment platform based on the deployment template, the second interface function call request carrying subscription information of the cloud application. If the subscription information of the cloud application is verified, the application identifier is sent to the deployment platform, so that the deployment platform acquires the cloud application based on the application identifier.

[0033] In a possible implementation, the transceiver is further configured to receive a cloud application subscription request sent by a user, the cloud application subscription request being used to acquire the deployment template of the cloud application, and a second deployment link is sent to the user based on the cloud application subscription request, the second deployment link being used to start the deployment template on the deployment platform. In a possible implementation, the transceiver is further configured to receive a cloud application subscription request sent by a user, the cloud application subscription request being used to acquire the deployment template of the cloud application, and a second deployment link is sent to the user based on the cloud application subscription request, the second deployment link being used to start the deployment template on the deployment platform.

[0034] In a fourth aspect, an embodiment of the present application provides a computing device, the computing device comprising a processor coupled to a memory, the processor configured to store instructions that, when executed by the processor, cause the computing device to perform the method of the first aspect or any possible implementation of the first aspect, or cause the computing device to perform the method of the second aspect or any possible implementation of the second aspect.

[0035] In a fifth aspect, an embodiment of the present application provides a computing device cluster, the computing device cluster comprising one or more computing devices, each computing device comprising a processor coupled to a memory, the processor configured to store instructions that, when executed by the processor, cause the computing device cluster to perform the method of the first aspect or any possible implementation of the first aspect, or cause the computing device cluster to perform the method of the second aspect or any possible implementation of the second aspect.

[0036] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of the first aspect or any possible implementation of the first aspect.

[0037] In a seventh aspect, an embodiment of the present application provides a computer program product, the computer program product comprising instructions that, when executed by a computer, cause the computer to implement the method of the first aspect or any possible implementation of the first aspect.

[0038] It can be understood that the beneficial effects achievable by any one of the cloud application deployment apparatus, the computing device, the computing device cluster, the computer-readable medium, or the computer program product provided above can refer to the beneficial effects in the corresponding method, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0039] FIG. 1 is a system architecture diagram of a cloud application deployment system according to an embodiment of the present application;

[0040] FIG. 2 is a flow diagram of a cloud application deployment method according to an embodiment of the present application;

[0041] FIG. 3 is a diagram of a cloud application deployment method in a test scenario according to an embodiment of the present application;

[0042] FIG. 4 is a diagram of a cloud application deployment method in another test scenario according to an embodiment of the present application;

[0043] FIG. 5 is a flow diagram of another cloud application deployment method according to an embodiment of the present application;

[0044] FIG. 6 is a schematic diagram of a cloud application deployment method in a release scenario according to an embodiment of the present application;

[0045] FIG. 7 is a schematic diagram of another cloud application deployment method in a release scenario according to an embodiment of the present application;

[0046] FIG. 8 is a schematic diagram of a cloud application deployment apparatus according to an embodiment of the present application;

[0047] FIG. 9 is a schematic diagram of a computing device according to an embodiment of the present application;

[0048] FIG. 10 is a schematic diagram of a computing device cluster according to an embodiment of the present application;

[0049] FIG. 11 is a schematic diagram of another computing device cluster according to an embodiment of the present application. DETAILED DESCRIPTION

[0050] The embodiments of the present application provide a cloud application deployment method and apparatus, which can improve the deployment efficiency and security of the cloud application.

[0051] The terms "first", "second", "third", "fourth" and the like in the description and in the claims of the present application, if any, are used for distinguishing between similar objects talking about the embodiments and not necessarily for describing a specific sequential or chronological order. It is to be understood that the data so distinguished can occur in any order. The terms "comprise", "comprising", "include", "including" and the like are to be construed open-ended, i.e. in the sense of "including, but not limited to", unless otherwise indicated. It is to be understood that the terms "comprise", "comprising", "include", "including" and the like, when used in this specification including the claims, can be construed to be in the sense of "consist of", "consisting of", "consists of", "consisting essentially of", "consisting essentially of" and the like, unless otherwise indicated.

[0052] In the embodiments of the present application, the word "exemplary" or "for example" is used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the embodied or designed word "exemplary" or "for example" is used to present concepts in a concrete manner.

[0053] First, some terms involved in the embodiments of the present application are introduced, which can help the skilled in the art to understand the technical solutions.

[0054] The deployment template refers to a predefined cloud resource deployment scheme, which contains a creation template and installation, start scripts of software. The deployment template can be used to complete the automatic purchase, creation and configuration of software dependent cloud resources, and after the cloud resource configuration is completed, the installation and start of the software are automatically completed.

[0055] The deployment stage refers to several deployment stages involved by the deployment template, including local development and commissioning, online self-test after being put on the cloud market, test during cloud market operation audit and formal deployment after the customer purchases the software, etc.

[0056] In order to make the technical solutions of the present application clearer and easier to understand, the system architecture of the present application will be introduced below in combination with the drawings.

[0057] Please refer to FIG. 1, which is a system architecture schematic diagram of a cloud application deployment system provided by an embodiment of the present application. In the example shown in FIG. 1, the cloud application deployment system 10 includes a merchant end 101, a user end 102 and a cloud data center 103, wherein the cloud data center 103 includes a cloud market 1031 and a deployment platform 1032. The specific functions of each part in the cloud application deployment system 10 will be introduced below.

[0058] The merchant end 101 is a provider of the cloud application. The merchant end 101 can create a cloud asset in the cloud market 1031, for example, the merchant end 101 can develop a cloud application locally and upload the developed application to the cloud market 1031, thereby creating a cloud asset. The merchant end 101 is also used to develop a deployment template of the cloud application, which can complete the automatic deployment of the cloud application on the deployment platform 1032. Specifically, the deployment template contains an interface function that can call the interface of the cloud market 1031 to obtain the application identifier of the cloud application.

[0059] The merchant end 101 is also used to test the deployment template of the developed cloud application, including local development test and authentication test of the cloud market, etc. The merchant end 101 tests the deployment template, which can verify whether the deployment template can call the interface of the cloud market 1031 to obtain the cloud application identifier during runtime, and complete the automatic installation and start of the cloud application according to the application identifier, wherein the cloud application includes an image and a software package, and the application identifier of the cloud application includes an image identifier ID and a software uniform resource locator URL.

[0060] The user terminal 102 is a purchaser of the cloud application. The user terminal 102 can order the cloud application from the cloud market 1031, thereby obtaining a deployment template of the cloud application, and the user terminal 102 can also deploy the cloud application in the deployment platform 1032 by using the deployment template. Specifically, the user terminal 102 runs the deployment template in the deployment platform 1032, and requests the cloud market 1031 to obtain an application identifier of the cloud application by calling an interface function in the deployment template, and further installs and starts the cloud application in the deployment platform 1031 based on the application identifier.

[0061] It can be understood that the merchant terminal 101 and the user terminal 102 in the embodiments of the present application can interact with the cloud data center 103, and deploy the cloud application in the deployment platform 1032, thereby realizing respective functions, and therefore, the merchant terminal 101 and the user terminal 102 can also be collectively referred to as a client of the cloud data center 103.

[0062] The cloud data center 103 is configured to provide various cloud resources required by the merchant terminal 101 and the client 102. The cloud data center 103 includes the cloud market 1031 and the deployment platform 1032, wherein the cloud market 1031 and the deployment platform 1032 are deployed on a plurality of cloud servers of the cloud data center 103, and the plurality of cloud servers can also be referred to as a computing device cluster.

[0063] The cloud market 1031 provides an open digital transaction and service platform for the merchant terminal 101 and the user terminal 102 based on computing and network resources of the cloud data center 103. For example, the cloud market 1031 can provide a large number of digital products and services, including various types of cloud applications. For the merchant terminal 101, the merchant terminal 101 can upload the cloud application on the cloud market 1031, thereby realizing business growth. For the user terminal 102, the user terminal 102 can purchase the required cloud application from the cloud market 1031.

[0064] The cloud market 1031 also has a strict test certification mechanism and an evaluation system, thereby ensuring the quality and reliability of the cloud application uploaded on the cloud market 1031. For example, the cloud market 1031 can perform certification testing on the cloud application deployment template developed by the merchant terminal 101, to ensure that the interface function of the deployment template can be successfully called, thereby obtaining the application identifier of the cloud application. For another example, the cloud market 1031 can provide a scoring and evaluation system for the cloud application by the user terminal 102, thereby enabling the user to score and evaluate the cloud application.

[0065] The deployment platform 1032 is one of the core infrastructures of the cloud data center 103, and is used to provide a running environment for the deployment template of the merchant end 101 and the user end 102. For example, the deployment platform 1032 can deploy various cloud applications, services, and data resources, etc. to the servers of the cloud data center 103 based on the deployment template. The deployment platform 1032 can also help the merchant end 101 and the user end 102 test the deployment template and test the installation of the cloud application.

[0066] The deployment platform 1032 also has resource management and scheduling capabilities. For example, the deployment platform 1032 can dynamically adjust the computing resources, storage resources, and network resources according to the actual needs of the cloud application, to ensure the performance and stability of the cloud application. In addition, the integration of the deployment platform 1032 with the cloud market 1031 can enable the deployment platform 1032 to seamlessly interface with various digital products and services, enabling one-key deployment and rapid delivery of cloud applications. The deployment platform 1032 can also provide monitoring, management, and security protection functions, thereby helping the client better manage and maintain the cloud application, and ensuring the continuity and security of the service.

[0067] Based on the cloud application deployment system 10 shown in FIG. 1, the present application also provides a cloud application deployment method. The cloud application deployment method provided by the embodiments of the present application will be introduced below in conjunction with the embodiments.

[0068] Please refer to FIG. 2, which is a flowchart of a cloud application deployment method provided by an embodiment of the present application. In the example shown in FIG. 2, the cloud application deployment method is a deployment method of the merchant end 101 in the test scenario of the deployment template. In the test scenario of the deployment template, the method includes the following steps:

[0069] 201. The cloud data center receives an asset creation request, the asset creation request is used to request to create and host a cloud application in the cloud market, and the asset creation request carries the cloud application.

[0070] After the merchant end 101 develops the cloud application, the merchant end 101 creates an asset in the cloud market 1031 of the cloud data center 103 based on the developed cloud application. The merchant end 101 sends an asset creation request to the cloud data center 103, the asset creation request is used to request to create and host a cloud application in the cloud market 1031, and the asset creation request can carry the cloud application. The cloud application includes one or more of the following: an image and application software.

[0071] The image refers to a storage form of a file, and the image usually contains a complete running environment, including an operating system, middleware, library files, etc. Therefore, the image has less dependence on the external environment and can maintain consistent running effects in different environments. The application software refers to an application program that implements a specific function, and the application software usually needs to run on a specific operating system or platform and may depend on specific middleware, library files, etc. Therefore, the application software has more dependence on the external environment and needs to ensure that the installation conditions are met before installation.

[0072] Referring to FIG. 3, FIG. 3 is a schematic diagram of a cloud application deployment method in a test scenario provided by the present application. In the example shown in FIG. 3, the merchant end 101 sends an asset creation request to the cloud market 1031, and the asset creation request carries the image or application software package developed by the merchant end 101. It should be noted that the merchant end 101 can upload the image and the application software package to the cloud market 1031 by sending the asset creation request, and the asset creation request carries the image or the application software package, or the image or the application software package can be uploaded separately after sending the asset creation request.

[0073] It can be understood that in some possible scenarios, the cloud application in the embodiments of the present application can also be referred to as cloud software, cloud service or cloud resource, etc., and the specific implementation is not limited.

[0074] 202. The cloud data center generates asset parameters based on the asset creation request, and the asset parameters are used to generate an interface function of a deployment template, and the interface function of the deployment template is used to query an application identifier corresponding to the cloud application from the cloud market according to the asset identifier.

[0075] After the cloud data center 103 receives the asset creation request sent by the merchant end 101, the cloud market 1031 generates asset parameters based on the asset creation request, wherein the asset parameters include an asset identifier ID, an asset version and an asset type, and the merchant end 101 can develop a deployment template of the cloud application based on the asset parameters. Specifically, the asset parameters are used to generate an interface function of a deployment template, and the interface function of the deployment template is used to query an application identifier corresponding to the cloud application from the cloud market 1031 according to the asset identifier, wherein the application identifier includes an image ID and an application software uniform resource locator URL.

[0076] In the process of generating the asset parameters based on the asset creation request by the cloud market 1031, the cloud market 1031 allocates an asset identifier, an asset version and an asset type based on the cloud application carried in the asset creation request, wherein a set of asset identifier, asset version and asset type can determine a cloud application, and when the cloud application is updated, the cloud market 1031 will allocate a set of asset identifier, asset version and asset type to the cloud application after the version update, wherein the asset identifier will not change.

[0077] The cloud market 1031 generates asset parameters based on the asset creation request, and sends the asset parameters to the merchant end 101. The merchant end 101 develops and deploys a template based on the received asset parameters. During the development of the deployment template, the merchant end 101 writes an interface function based on the asset identifier in the asset parameters. When the interface function is called, the deployment platform 1032 can query the cloud market 1031 for the application identifier of the cloud application corresponding to the asset identifier.

[0078] Please continue to refer to FIG. 3. In the example shown in FIG. 3, after the cloud market 1031 receives the asset creation request sent by the merchant end 101, the cloud market 1031 assigns asset parameters to the cloud application based on the asset creation request. The asset parameters include asset ID, asset version, and asset type. The cloud market 1031 sends the asset parameters to the merchant end 101. After the merchant end 101 receives the corresponding asset parameters of the cloud application, the merchant end 101 develops a deployment template for the cloud application based on the asset parameters.

[0079] Please refer to FIG. 4, which is a schematic diagram of a cloud application deployment method in another cloud market test scenario provided by an embodiment of the present application. In steps a to b of the example shown in FIG. 4, the merchant end 101 sends an asset creation request to the cloud market 1031. The asset creation request is used to request the cloud market 1031 to assign asset parameters. The asset parameters returned by the cloud market 1031 to the merchant end 101 include asset ID, asset version, and asset type.

[0080] It should be noted that the asset creation request sent by the merchant end 101 to the cloud market 1031 can also not carry the cloud application. The merchant end 101 can separately upload the cloud application to the cloud market 1031 in the asset creation request. For example, in steps a to c of the example shown in FIG. 4, the merchant end 101 sends an asset creation request to the cloud market 1031. After the cloud market 1031 returns the asset parameters corresponding to the asset creation request, the merchant end 101 uploads the image and application software to the cloud market 1031.

[0081] 203. The cloud data center executes the deployment template on the deployment platform. The deployment template is used to call the interface function to query and deploy the cloud application from the cloud market.

[0082] After the merchant end 101 develops the deployment template based on the asset parameters, the cloud data center 103 executes the deployment template on the deployment platform 1032. Specifically, during the execution of the deployment template on the deployment platform 1032, the cloud data center 103 queries the cloud market 1031 for the cloud application identifier corresponding to the asset identifier based on the interface function in the deployment template. During the further execution of the deployment template, the deployment platform 1032 can obtain the cloud application based on the application identifier of the cloud application, and install and start the cloud application on the deployment platform 1032.

[0083] In a possible implementation, in the cloud market test scenario of the deployment template, the cloud data center 103 calls the interface function in the deployment template in the process of the deployment platform executing the deployment template, and sends a first interface function call request to the cloud market 1031, where the first interface function call request carries the merchant identity information. After the cloud market 1031 receives the first interface function call request sent by the deployment platform 1032 based on the deployment template, if the merchant identity information passes the verification, the cloud market sends an application identifier to the deployment platform, so that the deployment platform obtains and deploys the cloud application based on the application identifier.

[0084] Please continue to refer to FIG. 3. In the example shown in FIG. 3, after the merchant end 101 develops the deployment template, the merchant end 101 tests the deployment template on the deployment platform 1032, that is, runs the deployment template on the deployment platform 1032. In the process of running the deployment template, the deployment platform 1032 queries the application identifier corresponding to the cloud application from the cloud market 1031 based on the asset ID in the interface function. Specifically, the deployment platform 1032 sends a first interface function call request to the cloud market 1031, where the first interface function call request is used to query the image ID corresponding to the image or query the application software URL corresponding to the application software from the cloud market 1031.

[0085] In the example shown in FIG. 3, after the cloud market 1031 receives the first interface function call request sent by the deployment platform 1032, the cloud market 1031 performs verification based on the merchant identity information carried in the first interface function call request. When the merchant identity information passes the verification, the cloud market 1031 sends the image ID corresponding to the asset ID or the application software URL corresponding to the asset ID to the deployment platform 1032.

[0086] In a possible implementation, before the cloud market 1031 receives the first interface function call request sent by the deployment platform 1032 based on the deployment template, the cloud market 1031 of the cloud data center 103 receives a test request sent by the merchant end 101, where the test request is used to request to test the deployment template. The cloud market 1031 sends a first deployment link to the merchant end 101 based on the test request, where the first deployment link is used to test the deployment template on the deployment platform.

[0087] Please continue to refer to FIG. 4. In steps d to e in the example shown in FIG. 4, the merchant end 101 develops the deployment template based on the asset parameters allocated by the cloud market 1031, and tests the deployment template on the deployment platform 1032. In the process of testing the deployment template, that is, in step e, the merchant end 101 can send a test request to the cloud market 1031. The cloud market 1031 returns a first deployment link to the merchant end 101 based on the test request. The merchant end 101 runs the deployment template on the deployment platform 1032 based on the first deployment link.

[0088] In steps f-i of the example shown in FIG. 4, during the process of testing the deployment template by the deployment platform 1032, the deployment platform 1032 calls the interface function of the deployment template, so that the deployment platform 1032 sends a first interface function call request to the cloud market 1031, the first interface function call request queries the image ID or the application URL based on the asset ID, the cloud market 1031 performs identity information verification according to the merchant identity information carried in the first interface function call request, and returns the image ID and the application URL corresponding to the asset ID to the deployment platform 1032 after the verification is passed.

[0089] In the deployment template testing process of the example shown in FIG. 4, after the deployment platform 1032 obtains the image ID or the application URL corresponding to the asset ID, the deployment platform 1032 further obtains the image based on the image ID or the application software based on the application URL, and then installs and starts the image and the application software package, and determines the test result according to the installation and starting result of the image and the application software package. When the image and the application software package are installed and started successfully, the deployment template testing is successful, and when the image and the application software package are installed and started unsuccessfully, the deployment template testing is unsuccessful. After the deployment platform 1032 determines the deployment result, the deployment platform 1032 sends the test result to the merchant end 101.

[0090] In a possible implementation, in the cloud market testing scenario of the deployment template, when the deployment template testing is unsuccessful, that is, the cloud application fails to be installed and started on the deployment platform 1032, the merchant end 101 needs to update the interface function in the deployment template, for example, the merchant end 101 checks whether the asset parameter of the interface function is correct and corrects it. Or the merchant end 101 updates the cloud application corresponding to the asset parameter, for example, the merchant end 101 re-uploads the cloud application in the cloud market 1031, and updates the cloud application corresponding to the asset ID.

[0091] In a possible implementation, the merchant end 101 updates the cloud application in the cloud market 1031, the cloud market 1031 receives the cloud application update version sent by the merchant end 101, and the cloud application update version is used to update the cloud application corresponding to the asset parameter in the cloud market. Then the cloud market 1031 modifies the cloud application corresponding to the asset parameter according to the cloud application update version.

[0092] It can be understood that the merchant end 101 uploads the new version of the cloud application, and the asset ID corresponding to the cloud application does not change. The cloud market 1031 updates the cloud application corresponding to the original asset ID, and modifies the asset ID corresponding to the asset version.

[0093] Please continue to refer to FIG. 4, in step j of the example shown in FIG. 4, the merchant end 101 sends an update request of the cloud application to the cloud market 1031, so as to upload the new version of the cloud application, and the update request of the cloud application carries the updated image or the updated application software. After the cloud market 1031 updates the cloud application corresponding to the asset ID and the asset version based on the update request of the cloud application, the updated asset parameters are returned to the merchant end 101, and the merchant end 101 can update the deployment template based on the updated asset parameters.

[0094] It should be noted that in the example shown in FIG. 4, the timing of updating the cloud application by the merchant end 101 to the cloud market 1031 in step j is not limited, and the cloud application can be updated before the deployment template test, or the cloud application can be updated after the deployment template test.

[0095] As can be seen from the above embodiments, in the cloud application deployment template developed by the merchant end in the embodiments of the present application, the application identifier corresponding to the cloud application can be requested from the cloud market in real time through the interface function, and the cloud application is obtained and deployed according to the application identifier. Since the deployment platform can query the application identifier from the cloud market in real time based on the interface function in the deployment template, the application identifier in the deployment template does not need to be modified in different scenarios of deploying the cloud application, thereby improving the deployment efficiency of the cloud application. At the same time, the application identifier is queried from the cloud market by calling the interface function, which avoids the leakage of the application identifier in the deployment template, thereby improving the security of the cloud application deployment.

[0096] The above introduces an embodiment of the merchant end 101 and the cloud data center 103 interacting to deploy the cloud application in the deployment template test scenario, and the following introduces an embodiment of the user end 102 and the cloud data center 103 interacting to deploy the cloud application in the deployment template use scenario.

[0097] Please refer to FIG. 5, which is a flow diagram of another cloud application deployment method provided by the embodiments of the present application. In the example shown in FIG. 5, the cloud application deployment method is the deployment method of the user end 102 in the deployment template use scenario, and in the deployment template use scenario, the method includes the following steps:

[0098] 501. The cloud data center receives the cloud application subscription request sent by the user end, and the cloud application subscription request is used to obtain the deployment template of the cloud application.

[0099] The cloud application subscription request sent by the user end 102 to the cloud market 1031 is used to obtain the deployment template of the cloud application. The cloud market 1031 sends a second deployment link to the user end 102 based on the cloud application subscription request, the second deployment link is used to obtain the deployment template of the cloud application, and the deployment platform 1032 starts the deployment template.

[0100] Referring to FIG. 6, FIG. 6 is a schematic diagram of a cloud application deployment method in a cloud application publishing scenario according to an embodiment of the present application. In the example shown in FIG. 6, the user terminal 102 sends a cloud application subscription request to the cloud market 1031, the cloud market 1031 sends a deployment link corresponding to the cloud application to the user terminal 102, the user terminal 102 can obtain a deployment template corresponding to the cloud application based on the deployment link, and start deployment on the deployment platform 1032 to execute the deployment template.

[0101] Referring to FIG. 7, FIG. 7 is a schematic diagram of another cloud application deployment method in a cloud application publishing scenario according to an embodiment of the present application. In steps a to b of the example shown in FIG. 7, the user terminal 102 browses and selects a cloud application to be purchased in the cloud market 1031, and after the user terminal 102 determines the cloud application to be purchased in the cloud market 1031, the user terminal 102 sends a cloud application subscription request to the cloud market 1031, and the cloud market 1031 returns a subscription result to the user terminal 102, the subscription result including a deployment link of a deployment template corresponding to the cloud application.

[0102] 502. The deployment platform of the cloud data center executes the deployment template, which is used to query the application identifier corresponding to the cloud application from the cloud market according to the asset identifier.

[0103] After the user terminal 102 obtains the deployment template of the cloud application, the deployment platform 1032 executes the deployment template, which includes an interface function, and the interface function includes asset parameters, the asset parameters including an asset identifier, an asset type and an asset version, and a set of asset parameters can determine a cloud application. After the interface function is called, the deployment platform 1032 queries the application identifier of the cloud application from the cloud market 1031 based on the asset identifier in the interface function, and the deployment platform 1032 can further obtain the cloud application based on the application identifier, and install and start the cloud application in the deployment platform 1032, wherein the cloud application includes an image and application software, and the application identifier includes an image ID and an application software URL.

[0104] Specifically, in the process of executing the deployment template, the deployment platform 1032 sends a second interface function call request to the cloud market 1031 based on the interface function, wherein the second interface function call request carries an asset ID and subscription information of the cloud application. After the cloud market 1031 receives the second interface function call request, the cloud market 1031 verifies the cloud application subscription information carried in the second interface function, and if the cloud application subscription information passes the verification, the cloud market 1031 sends the application identifier to the deployment platform 1032, so that the deployment platform 1032 can obtain the cloud application based on the application identifier. If the cloud application subscription information fails the verification, the cloud market 1031 reports an error to the deployment platform 1032, preventing the deployment platform 1032 from continuing to obtain the cloud application.

[0105] Please continue to refer to FIG. 6, in the example shown in FIG. 6, during the execution of the deployment template, the deployment platform 1032 queries the image ID or the application software URL from the cloud market 1031 according to the asset ID in the interface function, the cloud market 1031 checks the subscription information of the user terminal 102, if the checking is successful, the cloud market 1031 sends the image ID and the application software URL to the deployment platform 1032, if the checking fails, the cloud market 1031 reports an error to the deployment platform 1032 to prevent deployment.

[0106] Please continue to refer to FIG. 7, in steps c to g of the example shown in FIG. 7, after the user terminal 102 obtains the deployment link of the deployment template corresponding to the cloud application, the user terminal 102 deploys the cloud application on the deployment platform 1032, during the execution of the deployment template, the deployment platform 1032 sends a second interface function call request to the cloud market 1031, the second interface function call request is used to query the image ID and the application software URL corresponding to the asset ID.

[0107] In the example shown in FIG. 7, after the cloud market 1031 receives the second interface function call request, the cloud market 1031 checks the subscription information of the cloud application, the subscription information includes the user identity to subscribe to the record, after the subscription information of the cloud application is checked successfully, the cloud market 1031 sends the image ID or the application software URL corresponding to the asset ID to the deployment platform 1032. After the deployment platform 1032 receives the image ID or the application software URL, the deployment platform 1032 obtains the image based on the image ID, or obtains the application software based on the application software URL, and further installs and starts the image or the application software. Then the deployment platform 1032 sends the deployment result to the user terminal 102, the deployment result is used to indicate the user terminal 102 that the cloud application deployment is successful or failed.

[0108] As can be seen from the above implementation, the cloud market in the embodiment of the present application can provide unified cloud application hosting and query capability. Since the merchant terminal 101 creates assets and hosts the cloud application package to the cloud market in the development stage of the deployment template, during the subsequent local testing, cloud market self-testing, joint certification testing of the merchant terminal 101 and cloud application deployment of the user terminal 102, the interface of the cloud market 1031 can be called by the deployment platform 1032 to query the application identifier of the cloud application in the cloud market in real time, without modifying the application identifier in the deployment template in different stages, thereby improving the deployment efficiency of the cloud application.

[0109] It should be noted that the above embodiment shown in FIG. 2 and the above embodiment shown in FIG. 5 can be two embodiments of the cloud application deployment method in different scenarios, so the above embodiment shown in FIG. 2 and the above embodiment shown in FIG. 5 can also be combined as one embodiment.

[0110] Based on the method embodiments, the embodiments of the present application further provide a cloud application deployment device, and the cloud application deployment device provided by the embodiments of the present application is specifically introduced as follows.

[0111] Referring to FIG. 8, FIG. 8 is a structural schematic diagram of a cloud application deployment device provided by the embodiments of the present application. In the example shown in FIG. 8, the cloud application deployment device 800 is used to implement the steps performed by the end-side sharing module in the above embodiments, and the cloud application deployment device 800 includes a transceiver unit 801 and a processing unit 802.

[0112] The transceiver unit 801 is configured to receive an asset creation request, the asset creation request being used to request to create and host a cloud application in a cloud market, and the asset creation request carrying the cloud application, the cloud application including one or more of the following: an image and application software. The processing unit 802 is configured to generate asset parameters based on the asset creation request, the asset parameters including an asset identifier, an asset version, and an asset type, the asset parameters being used to generate an interface function of a deployment template, the interface function of the deployment template being used to query an application identifier corresponding to the cloud application from the cloud market according to the asset identifier, the application identifier including one or more of the following: an image identifier ID and an application software uniform resource locator URL. The processing unit 802 is further configured to execute the deployment template on a deployment platform, and the deployment template is used to call the interface function to query and deploy the cloud application from the cloud market.

[0113] In a possible implementation, the transceiver unit 801 is further configured to receive a cloud application update version sent by a merchant, the cloud application update version being used to update the cloud application corresponding to the asset parameters in the cloud market, and the processing unit 802 is further configured to modify the cloud application corresponding to the asset parameters according to the cloud application update version.

[0114] In a possible implementation, the transceiver unit 801 is specifically configured to receive a first interface function call request sent by the deployment platform based on the deployment template, and the first interface function call request carries merchant identity information. If the merchant identity information is verified, the cloud market sends the application identifier to the deployment platform, so that the deployment platform acquires and deploys the cloud application based on the application identifier.

[0115] In a possible implementation, the transceiver unit 801 is further configured to receive a test request sent by a merchant, the test request being used to request to test the deployment template, and a first deployment link is sent to the merchant based on the test request, the first deployment link being used to test the deployment template on the deployment platform.

[0116] In a possible implementation, the processing unit 802 is further configured to update the interface function or the cloud application corresponding to the asset parameters when the deployment template fails.

[0117] In a possible implementation, the transceiver 801 is further configured to receive a second interface function call request sent by the deployment platform based on the deployment template, the second interface function call request carrying subscription information of the cloud application. If the subscription information of the cloud application is verified, the application identifier is sent to the deployment platform, so that the deployment platform obtains the cloud application based on the application identifier.

[0118] In a possible implementation, the transceiver 801 is further configured to receive a cloud application subscription request sent by a user, the cloud application subscription request being used to obtain the deployment template of the cloud application, and send a second deployment link to the user based on the cloud application subscription request, the second deployment link being used to start the deployment template on the deployment platform.

[0119] It can be understood that the transceiver 801 and the processing unit 802 in the cloud application deployment apparatus 800 can be mapped to the modules in the cloud application deployment system 10 in FIG. 1 as functional modules, so as to realize the functions of the modules in the cloud application deployment system 10.

[0120] It should be understood that the division of the units in the above apparatus is only a logical functional division, and all or part of the units can be integrated into one physical entity, or can be physically separated. The units in the apparatus can all be implemented in the form of software invoked by a processing element; or all be implemented in the form of hardware; or part of the units are implemented in the form of software invoked by a processing element, and part of the units are implemented in the form of hardware. For example, each unit can be a separately established processing element, or can be integrated into a chip of the apparatus, and in addition, can be stored in the form of a program in a memory, and the function of the unit is invoked and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together, or can be independently implemented. The processing element described herein can be a processor, and can be an integrated circuit with a signal processing capability. In the implementation process, each step of the above method or each unit can be implemented by an integrated logic circuit of hardware in the processing element, or in the form of software invoked by the processing element.

[0121] It should be noted that, for the above method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited to the action sequence described, and those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions involved are not necessarily required by the present application.

[0122] Other reasonable combinations of steps, which can be conceived by those skilled in the art based on the foregoing description, are also within the scope of the present application. Secondly, those skilled in the art should also be familiar with the fact that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the present application.

[0123] Referring to FIG. 9, FIG. 9 is a structural schematic diagram of a computing device provided by an embodiment of the present application. As shown in FIG. 9, the computing device 900 includes a processor 901, a memory 902, a communication interface 903, and a bus 904, the processor 901, the memory 902, and the communication interface 903 are coupled through a bus (not labeled in the figure). The memory 902 stores instructions, and when the instructions stored in the memory 902 are executed, the computing device 900 executes the method performed by the deployment system of the cloud application in the above method embodiments.

[0124] The computing device 900 can be one or more integrated circuits configured to implement the above method, for example, one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the units in the apparatus can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can invoke programs. For another example, these units can be integrated together to implement in the form of a system-on-a-chip (SOC).

[0125] The processor 901 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, or any conventional processor.

[0126] The memory 902 can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0127] The executable program code stored in the memory 902 is executed by the processor 901 to respectively implement the functions of the foregoing units or modules, thereby implementing the cloud application deployment method described above. That is, the memory 902 has instructions for executing the cloud application deployment method described above.

[0128] The communication interface 903 uses a transceiving module such as, but not limited to, a network interface card, a transceiver, to implement communication between the computing device 900 and other devices or communication networks.

[0129] The bus 904 can include, in addition to a data bus, a power bus, a control bus, and a state signal bus, etc. The bus can be a peripheral component interconnect express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0130] Referring to FIG. 10, FIG. 10 is a schematic diagram of a computing device cluster provided by an embodiment of the present application. As shown in FIG. 10, the computing device cluster 1000 includes at least one computing device 900.

[0131] As shown in FIG. 10, the computing device cluster 1000 includes at least one computing device 900. The memory 902 in one or more computing devices 900 in the computing device cluster 1000 can have the same instructions for performing the cloud application deployment method described above.

[0132] In some possible implementations, the memory 902 in one or more computing devices 900 in the computing device cluster 1000 can also respectively have partial instructions for performing the cloud application deployment method described above. In other words, the combination of one or more computing devices 900 can collectively execute the instructions for performing the cloud application deployment method described above.

[0133] It should be noted that the memory 902 in different computing devices 900 in the computing device cluster 1000 can store different instructions, respectively used to perform part of the functions of the cloud application deployment apparatus described above. That is, the instructions stored in the memory 902 in different computing devices 900 can implement the functions of one or more modules in the processing unit and the transceiver unit.

[0134] In some possible implementations, one or more computing devices 900 in the computing device cluster 1000 can be connected through a network. The network can be a wide area network or a local area network, etc.

[0135] Referring to FIG. 11, FIG. 11 is a schematic diagram of the connection of the computer devices in a computer cluster through a network according to an embodiment of the present application. As shown in FIG. 11, two computer devices 900A and 900B are connected through a network. Specifically, the communication interface in each computer device is connected to the network.

[0136] In a possible implementation, the memory in the computer device 900A stores instructions for executing the function of the transceiver unit. Meanwhile, the memory in the computer device 900B stores instructions for executing the function of the processing unit.

[0137] It should be understood that the function of the computer device 900A shown in FIG. 11 can also be completed by multiple computer devices. Similarly, the function of the computer device 900B can also be completed by multiple computer devices.

[0138] In another embodiment of the present application, a computer readable storage medium is also provided, which stores computer execution instructions. When the processor of a device executes the computer execution instructions, the device executes the method performed by the deployment system of the cloud application in the above method embodiments.

[0139] In another embodiment of the present application, a computer program product is also provided, which includes computer execution instructions stored in a computer readable storage medium. When the processor of a device executes the computer execution instructions, the device executes the method performed by the deployment system of the cloud application in the above method embodiments.

[0140] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0141] In the several embodiments of the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or in other forms.

[0142] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0143] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware, or in the form of a software functional unit.

[0144] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, read-only memory), a random access memory (RAM, random access memory), a magnetic disk or an optical disk, and various program code storage media.

Claims

1. A method of deploying a cloud application, characterized by, The method comprises: receiving an asset creation request, the asset creation request being used to request to create and host a cloud application in a cloud market, the asset creation request carrying the cloud application, the cloud application comprising one or more of the following: an image and application software; generating asset parameters based on the asset creation request, the asset parameters comprising an asset identifier, an asset version, and an asset type, the asset parameters being used to generate an interface function of a deployment template, the interface function of the deployment template being used to query an application identifier corresponding to the cloud application from the cloud market according to the asset identifier, the application identifier comprising one or more of the following: an image identifier ID and an application software uniform resource locator URL; executing the deployment template on a deployment platform, the deployment template being used to call the interface function to query and deploy the cloud application from the cloud market.

2. The method of claim 1, wherein, After the asset parameters are generated based on the asset creation request, the method further comprises: receiving a cloud application update version sent by a merchant, the cloud application update version being used to update the cloud application corresponding to the asset parameters in the cloud market; modifying the cloud application corresponding to the asset parameters according to the cloud application update version.

3. The method according to claim 1 or 2, characterized in that, The execution of the deployment template on the deployment platform comprises: receiving a first interface function call request sent by the deployment platform based on the deployment template, the first interface function call request carrying the merchant identity information; if the merchant identity information is verified, the cloud market sends the application identifier to the deployment platform, so that the deployment platform acquires and deploys the cloud application based on the application identifier.

4. The method of claim 3, wherein, Before the first interface function call request sent by the deployment platform based on the deployment template is received, the method further comprises: receiving a test request sent by a merchant, the test request being used to request to test the deployment template; sending a first deployment link to the merchant based on the test request, the first deployment link being used to test the deployment template on the deployment platform.

5. The method of claim 4, wherein, The method further comprises: if the deployment template fails, updating the interface function, or updating the cloud application corresponding to the asset parameters.

6. The method according to claim 1 or 2, characterized in that, The execution of the deployment template on the deployment platform further comprises: receiving a second interface function call request sent by the deployment platform based on the deployment template, the second interface function call request carrying subscription information of the cloud application; if the subscription information of the cloud application is verified, the application identifier is sent to the deployment platform, so that the deployment platform acquires the cloud application based on the application identifier.

7. The method of claim 6, wherein, The method further comprises: receiving a cloud application subscription request sent by a user, the cloud application subscription request being used to acquire a deployment template of the cloud application; sending a second deployment link to the user based on the cloud application subscription request, the second deployment link being used to start the deployment template on the deployment platform.

8. An apparatus for deployment of a cloud application, characterized by The apparatus comprises: a transceiver unit configured to receive an asset creation request, the asset creation request being used to request to create and host a cloud application in a cloud market, the asset creation request carrying the cloud application, the cloud application comprising one or more of the following: an image and application software; The processing unit is configured to generate asset parameters based on the asset creation request, the asset parameters comprising an asset identifier, an asset version, and an asset type, the asset parameters being used to generate an interface function of a deployment template, the interface function of the deployment template being used to query an application identifier corresponding to the cloud application from the cloud marketplace according to the asset identifier, the application identifier comprising one or more of an image identifier ID and an application software uniform resource locator URL. The processing unit is further configured to execute the deployment template on a deployment platform, the deployment template being used to invoke the interface function to query and deploy the cloud application from the cloud marketplace.

9. The apparatus of claim 8, wherein, The transceiver unit is further configured to: receive a cloud application update version sent by a merchant, the cloud application update version being used to update a cloud application corresponding to the asset parameters in the cloud marketplace; The processing unit is further configured to modify the cloud application corresponding to the asset parameters according to the cloud application update version.

10. The apparatus of claim 8 or 9, wherein, The transceiver unit is specifically configured to: receive a first interface function invocation request sent by the deployment platform based on the deployment template, the first interface function invocation request carrying the merchant identity information; if the merchant identity information passes the verification, the cloud marketplace sends the application identifier to the deployment platform, so that the deployment platform acquires and deploys the cloud application based on the application identifier.

11. The apparatus of claim 10, wherein, The transceiver unit is further configured to: receive a test request sent by a merchant, the test request being used to request testing of the deployment template; send a first deployment link to the merchant based on the test request, the first deployment link being used to test the deployment template on the deployment platform.

12. The apparatus of claim 11, wherein, The processing unit is further configured to: if the deployment template fails the test, update the interface function, or update the cloud application corresponding to the asset parameters.

13. The apparatus of claim 8 or 9, wherein, The transceiver unit is further configured to: receive a second interface function invocation request sent by the deployment platform based on the deployment template, the second interface function invocation request carrying subscription information of the cloud application; if the subscription information of the cloud application passes the verification, send the application identifier to the deployment platform, so that the deployment platform acquires the cloud application based on the application identifier.

14. The apparatus of claim 13, wherein, The transceiver unit is further configured to: receive a cloud application subscription request sent by a user, the cloud application subscription request being used to acquire a deployment template of the cloud application; send a second deployment link to the user based on the cloud application subscription request, the second deployment link being used to start the deployment template on the deployment platform.

15. A computing device, comprising: A computing device comprising a processor coupled with a memory, the processor being configured to store instructions that, when executed by the processor, cause the computing device to perform the method of any one of claims 1-7.

16. A cluster of computing devices, characterized in that, A computing device cluster comprising at least one computing device, the computing device comprising a processor coupled with a memory, the processor being configured to store instructions that, when executed by the processor, cause the computing device cluster to perform the method of any one of claims 1-7.

17. A computer-readable storage medium having stored thereon instructions, The instructions, when executed, cause a computer to perform the method of any one of claims 1-7.

18. A computer program product comprising instructions therein, the computer program product characterized by, The instructions, when executed, cause a computer to implement the method of any one of claims 1 to 7.

Images