CN116166278A

CN116166278A - Application management method and related system

Info

Publication number: CN116166278A
Application number: CN202111535162.1A
Authority: CN
Inventors: 何国洲
Original assignee: Huawei Cloud Computing Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2021-11-24
Filing date: 2021-12-15
Publication date: 2023-05-26
Also published as: WO2023093197A1

Abstract

The application provides an application management method, which comprises the following steps: the method comprises the steps of presenting a specification creation interface to a user, receiving first specification description information configured by the user through the specification creation interface, presenting a specification arrangement interface to the user, wherein the specification arrangement interface carries a plurality of arrangement nodes, the first arrangement node in the plurality of arrangement nodes is a standardized service node, responding to the operation of the user on a target arrangement node in the plurality of arrangement nodes, generating a first arrangement file of an application, submitting the first arrangement file and the first specification description information to an application market, and enabling the application market to release the application. The arrangement file obtained by arranging the standardized service nodes can shield the difference of heterogeneous environments such as public cloud, private cloud, mixed cloud or edge cloud, so that a user only needs to arrange once aiming at different deployment environments suitable for application, and the delivery pressure of the user is reduced. When in deployment, the application can be deployed to different deployment environments in batches through the arrangement file, so that the deployment pressure is reduced.

Description

Application management method and related system

The present application claims priority from the chinese patent application filed at 24 months 11 of 2021, filed with the chinese national intellectual property office under application number 202111407421.2, entitled "a standardized resource node and cloud service orchestration method, apparatus, and system", the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to an application management method and system, a computer cluster, a computer readable storage medium, and a computer program product.

Background

With the continuous development of cloud computing technology, "application cloud up" becomes a trend. "application cloud" refers to the deployment of applications (also referred to as application software) to a cloud environment. After the development of the application is completed, the independent software developer (independent software vendor, ISV) can hand the deployment and upgrade of the application to a professional system integration (system Integration, SI) vendor to complete the application cloud.

In the application cloud process, the system integrator can deploy the application into different cloud environments, considering that the requirements of different clients can be different. For example, for small and medium enterprise customers, a system integrator may deploy applications to public clouds; for large enterprise customers, system integrators may deploy applications to private clouds, public clouds, and smart Sites (FCs).

When an application needs to be deployed to different environments (e.g., public cloud, private cloud, hybrid cloud, or different cloud environments such as smart site), in an application development phase, particularly in a later stage of the application development phase, ISVs need to be adapted for different deployment environments (e.g., arranging application-dependent services and dependency relationships between services), respectively, thus increasing delivery pressure of the ISVs. In addition, in the application deployment stage, the system integrator has difficulty in deploying the application to different environments in batches in a unified mode, and the deployment pressure of the system integrator is increased.

Disclosure of Invention

The application management method comprises the steps of arranging the standardized service nodes to obtain arrangement files, wherein the arrangement files can shield differences of heterogeneous environments such as public cloud, private cloud, mixed cloud or edge cloud, users do not need to arrange different deployment environments applicable to the application only once, and delivery pressure is reduced. Moreover, the batch deployment of the applications to different deployment environments can be realized based on the arrangement files, so that the deployment pressure is reduced. The application also provides a system (such as an application management platform, an application market and the like), a computer cluster, a computer readable storage medium and a computer program product corresponding to the method.

In a first aspect, the present application provides an application management method. The application management method is executed by an application management platform. In some embodiments, the application management platform may be a software system that is run by a computing device or cluster of computing devices to perform the application management method. In other embodiments, the application management platform may also be a hardware system for application management.

In the process of cloud loading, the cloud loading method can be divided into a development stage, a release stage and a deployment stage. In the development stage, after the development of the functions or characteristics of the application is completed, the application provider lays out the layout nodes corresponding to the functions and the characteristics, and further, the application provider can also perform debugging after the layout, so that the application development is completed; in the release stage, the provider of the application can submit the relevant information of the application to the application market, and the application market releases the application; in the deployment stage, the system integrator or the application requirement party can purchase the application on the application market, and further deploy the application into different cloud environments through another application management platform.

For convenience of description, in the embodiment of the present application, a provider of an application is referred to as a first user, an application management platform used by the first user is referred to as a first application management platform, a demander or a system integrator of the application is referred to as a second user, and an application management platform for deploying the application in response to a deployment operation triggered by the second user is referred to as a second application management platform. The first application management platform supports application development of a first user and can cooperate with an application market to complete application release. The second application management platform can cooperate with the application market to complete application deployment.

Specifically, the first application management platform may present a specification creation interface to a first user, receive first specification description information configured by the first user through the specification creation interface, where the first specification description information includes a first specification of an application, then the first application management platform may present a specification arrangement interface to the first user, where the specification arrangement interface carries a plurality of arrangement nodes, a first arrangement node of the plurality of arrangement nodes is a standardized service node, and then, in response to an operation of the first user on a target arrangement node of the plurality of arrangement nodes, generate a first arrangement file of the application, where the first arrangement file records a dependency relationship between the target arrangement node and the target arrangement node on which the application runs under the first specification, and then, the first application management platform submits the first arrangement file and the first specification description information to an application market, so that the application market publishes the application.

In the method, the arrangement node provided by the first application management platform is a standardized service node, and the arrangement file obtained by arrangement based on the standardized service node can shield differences of heterogeneous environments (different deployment environments applicable to the application) such as public cloud, private cloud, mixed cloud or edge cloud (for example, intelligent sites in the edge cloud), so that the first user only needs to arrange once for the different deployment environments applicable to the application, and therefore, the delivery pressure of the first user is reduced.

In some possible implementations, the first orchestration node is any one of: standardized infrastructure as a service IaaS layer nodes, standardized platform as a service PaaS layer nodes, and standardized software as a service SaaS layer nodes. The IaaS layer node comprises a computing resource node, a network resource node and a storage resource node, and the PaaS layer node comprises one or more of an application container engine node, a database, a gateway, unified authentication management and a container mirror warehouse. The SaaS layer node configures one or more of a storage node, a stateless node, a stateful node, a network cluster service node, an ingress node, a namespace node, and a role-based authentication control node. The SaaS layer node may further include a third party application service node, where the third party application service node may be, for example, a service node corresponding to an application service developed by an application provider.

In the method, the first application management platform can realize code multiplexing of some nodes by arranging the standardized IaaS layer nodes, the standardized PaaS layer nodes and/or the standardized SaaS layer nodes, so that the application development threshold is reduced, and the application development efficiency is improved.

In some possible implementations, the first application management platform may create the first orchestration node by normalizing the information before presenting the specification creation interface to the user. The first arrangement node is a standardized service node, and a foundation can be laid for arrangement standardization by standardizing the service node, so that the first user does not need to arrange for different deployment environments to be deployed respectively, and the delivery pressure of the first user is reduced.

In some possible implementations, the application management platform interfaces to a heterogeneous environment. The heterogeneous environment includes one or more of public cloud, private cloud, hybrid cloud, or edge cloud. It should be noted that the heterogeneous environments may be a combination of the different types of environments, or may be a combination of the same type of environments provided by different service providers, for example, a combination of public clouds provided by different service providers.

When the first orchestration node is the standardized IaaS layer node or the standardized PaaS layer node, the standardized information includes preconfigured first standardized information. The first standardized information is specific to standardized information common to the IaaS layer node and the PaaS layer node, and an administrator of the first application management platform can pre-configure the first standardized information so as to realize the standardization of the IaaS layer node or the PaaS layer node. The first standardized information includes an operating system image, an access address of each environment in the heterogeneous environment, and a resource application interface in each environment in the heterogeneous environment. Further, the first normalization information may further include parameters that support modification when the normalized IaaS layer node or the normalized PaaS layer node is orchestrated.

In the method, the first application management platform standardizes the IaaS layer nodes or the PaaS layer nodes in batches based on the universal first standardized information, so that the standardized efficiency is improved.

In some possible implementations, the standardized PaaS layer node includes a standardized application container engine node. When the first orchestration node is the standardized application container engine node, the standardized information further includes second standardized information including a container management platform installation package, a container installation package, and container startup parameters.

Wherein, container management platform installation package can be K8S installation package, and K8S installation package can include kubeadm, kubelet and kubectl. The container installation package may be a dock installation package. The container configuration parameters may include a dock startup mode configured to start up randomly and with security components such as swap/firewall/selinux shut down.

In the method, the first application management platform can perform standardization aiming at some nodes in the PaaS, such as application container engine nodes, by combining the first standardization information and the second standardization information aiming at the nodes, so that different standardization requirements are met.

In some possible implementations, the standardized SaaS layer node includes a standardized third party application service node. When the first orchestration node is the standardized third party application service node, the standardized information includes an interface that the third party application service is open to.

In the method, the first application management platform also supports the opening of the capability of the third-party application service node, for example, an interface of the third-party application service can be opened, so that the standardization of the third-party application service node is realized, the application development is performed based on the standardized third-party application service node, the development efficiency can be improved, and the utilization rate of the third-party application service can be provided.

In some possible implementations, the first specification description information further includes an applicable environment of the first specification, where the applicable environment is selected from the heterogeneous environments that the application management platform interfaces with. For example, the heterogeneous environments that the application management platform interfaces with include public clouds, private clouds, hybrid clouds, and edge clouds, from which the first user may select the public clouds and the private clouds as the applicable environments of the first specification.

In the method, the first application management platform supports the first user to configure the applicable environment of the first specification, and the applicable environment can be a plurality of environments, so that when the application is deployed, the application can be deployed to the corresponding environment based on one layout file in combination with the applicable environment, and the deployment pressure is reduced.

In some possible implementations, the first application management platform may obtain a dependency relationship between the target orchestration nodes in response to a connection operation of the first user to the target orchestration nodes, and then generate the first orchestration file of the application according to the dependency relationship between the target orchestration nodes.

In the method, the first application management platform can provide a graphical specification arrangement interface so that a first user can conveniently connect a target arrangement node in the specification arrangement interface to generate an arrangement file, thus simplifying arrangement operation and improving arrangement efficiency.

In some possible implementations, the first application management platform may obtain parameters of the target orchestration node in response to a configuration operation of the target orchestration node by the user, and then generate a first orchestration file for the application according to the parameters of the target orchestration node.

In the method, the first application management platform can provide a graphical specification arrangement interface so that a first user can carry out parameter configuration on a target arrangement node in the specification arrangement interface and generate an arrangement file according to the configured parameters, thus simplifying arrangement operation and improving arrangement efficiency.

It should be noted that, in some cases, the first user may not perform the configuration operation on the target editing node, so that the first application management platform may generate the editing file according to the default parameters, which further simplifies the editing operation and improves the editing efficiency.

In some possible implementations, the first application management platform may also normalize the application to obtain the second orchestration node. The second orchestration node is a standardized SaaS layer node, and the second orchestration node is used for creating orchestration files of other applications.

Specifically, the first application management platform may add the second orchestration node to the existing multiple orchestration nodes, where the second orchestration node is included on the orchestration interface when the orchestration interface is presented again, so that providers of other applications use the second orchestration node to create orchestration files of other applications. This may improve the development efficiency of other applications.

In some possible implementations, the first application management platform may receive the application-open interface configured by the first user, and normalize the application according to the application-open interface, thereby obtaining the second orchestration node. Further, the first application management platform may further receive parameters supporting modification when the second orchestration node configured by the first user is orchestrated, and the first application management platform normalizes the application according to the application open interface and the parameters supporting modification when the second orchestration node is orchestrated, thereby obtaining the second orchestration node.

In the method, the corresponding second arrangement node can be obtained by opening the interface of the application, and the second arrangement node can provide help for the development of other applications and improve the application development efficiency.

In some possible implementations, the first application management platform may request the authorization of the first user by way of an interrogation and standardize the application after obtaining the authorization of the first user. Specifically, a first application management platform may present a recommendation page to the first user, the recommendation page indicating a recommendation to normalize the application, and then normalize the application to the second orchestration node in response to a normalization operation of the application triggered by the first user through the recommendation page.

In this way, the application can be standardized according to the requirements of the first user. On the basis of guaranteeing the application safety, the application capability is opened, so that assistance is provided for the development of other applications.

In some possible implementations, the first application management platform may obtain the second specification description information, and open the first layout file in the specification layout interface, and obtain the second layout file according to the modification of the first layout file by the user. The second specification description information includes a second specification of the application, and the second orchestration file records information of orchestration nodes on which the application runs under the second specification. And then the first application management platform submits the second arrangement file and the second specification description information to the application market so as to update the information of the application on the application market.

In the method, the first user can modify the first arrangement file to obtain the second arrangement file, and submit the second specification description information and the second arrangement file to the application market so as to update the information of the application in the application market, thereby simplifying the updating flow.

In some possible implementations, the first specification description information further includes a version number of a first version of the first specification, and the first orchestration file records the target orchestration node and a dependency relationship between the target orchestration nodes on which the application runs under the first version of the first specification. The first application management platform may further obtain third specification description information, open the first layout file in the specification layout interface, and obtain a third layout file according to modification of the first layout file by the user, where the third specification description information includes version numbers of the first specification and a second version of the first specification, and the third layout file records information of a layout node on which the application runs under the second version of the first specification. The first application management platform may then submit the third orchestration file and the third specification description information to the application marketplace, so as to update information of the application on the application marketplace.

In the method, the first user can simply modify the first arrangement file to obtain a third arrangement file, and submit the third specification description information and the third arrangement file to the application market so as to update the information of the application in the application market, thereby simplifying the updating flow.

In a second aspect, the present application provides an application management method. The method may be performed by an application marketplace. Specifically, the application marketplace may present an application deployment interface to a second user, and then receive deployment information of a target application configured by the second user through the application deployment interface, where the target application is an application that the second user requests to be deployed, the deployment information includes a target deployment environment, and the target deployment environment includes one or more of public cloud, private cloud, hybrid cloud, or edge environment. The application marketplace then sends the first orchestration file to the target deployment environment. The first orchestration file records orchestration nodes on which the target application runs and dependency relations among the orchestration nodes.

In the method, the application market can send the first arrangement files to different deployment environments according to the requirements of the second user, so that batch deployment application to different deployment environments according to the first arrangement files is realized, and the deployment pressure of the second user is reduced.

In some possible implementations, the deployment information further includes first specification description information of the target application. The first specification description information includes a first specification of the target application. Accordingly, the application marketplace may first determine the first orchestration file matching the first specification from among the orchestration files of the target application according to the first specification description information. The first orchestration file records orchestration nodes on which the target application runs under the first specification and the dependency relations among the orchestration nodes. The application marketplace then sends the first orchestration file to the target deployment environment.

In the method, considering that the application can comprise a plurality of specifications, the second user can specify that the application to be deployed runs under the first specification, and thus, the application market can send the first layout file matched with the first specification to the target deployment environment according to the determination, so that the specific requirement is met.

In some possible implementations, the application marketplace may determine the first orchestration file from orchestration files of the target application according to the target deployment environment, the first orchestration file recording orchestration nodes on which the target application runs under a first specification and dependencies between the orchestration nodes, the applicable environment of the first specification including the target deployment environment. The application marketplace then sends the first orchestration file to the target deployment environment.

In this method, the specification description information generally records an applicable environment of the specification, based on which, the application market may determine, according to a target deployment environment configured by a user, that the applicable environment includes the specification of the target deployment environment, for example, a first specification, and then determine a first layout file according to the first specification. Therefore, the second user does not need to perform additional operation, and the user experience is improved.

In some possible implementations, the second user may also update the deployment information when there is an update to the application published by the application marketplace, so as to upgrade the application in the target deployment environment. Specifically, the application marketplace may receive a first update to the deployment information, for example, a first update to the deployment information by a second user, the first update including second specification description information of the target application, the second specification description information including a second specification of the target application, and then the application marketplace may determine a second orchestration file matching the second specification from among orchestration files of the target application according to the second specification description information. The second orchestration file records orchestration nodes on which the target application runs under the second specification and the dependency relations among the orchestration nodes. The application marketplace then sends the second orchestration file to the target deployment environment to facilitate updating the target application to the second specification on the target deployment environment.

In the method, the application marketplace may determine a second orchestration file from the orchestration files of the application based on the updating of the deployment information, and send the second orchestration file to the target deployment environment to enable upgrading of the application to the second specification in the target deployment environment. Therefore, flexible capacity expansion and capacity shrinkage can be realized, and agile deployment can be realized.

In some possible implementations, the first specification description information includes a version number of a first version of the first specification; the first orchestration file records orchestration nodes on which the target application runs under a first version of the first specification and dependencies between the orchestration nodes. The application marketplace may receive a second update to the deployment information, such as a second update to the deployment information by a second user, the second update including third specification description information of the target application, the third specification description information including version numbers of the first specification and a second version of the first specification of the target application. The application marketplace may then determine, from among the orchestration files of the target application, a third orchestration file that matches the second version of the first specification, based on the third specification description information. The third orchestration file records orchestration nodes on which the target application runs under the second version of the first specification and dependencies between the orchestration nodes. The application marketplace then sends the third orchestration file to the target deployment environment to facilitate updating the target application to the second version of the first specification on the target deployment environment.

In the method, the application marketplace may determine a third orchestration file from the orchestration files of the application based on the updating of the deployment information, and send the third orchestration file to the target deployment environment to enable upgrading of the application to the second version in the target deployment environment. Therefore, the performance expansion can be realized, and the service requirement is met.

In some possible implementations, the application marketplace can also audit the application prior to presenting the application deployment interface to the user. When the audit is passed, the application market can present application introduction information of the application on the application deployment interface.

Therefore, the quality of the application released by the application market can be ensured, and high-quality application is provided for the second user, so that the user experience is improved.

In some possible implementations, the application marketplace can audit the application according to the first orchestration file and the first specification description information of the application submitted by the first application management platform. Wherein the application marketplace may audit applications from one or more dimensions of compliance, security, quality, and development qualification. It should be noted that, the application market may obtain application introduction information and a software package to audit the application.

Wherein, auditing from compliance dimension refers to auditing whether the application meets relevant regulations or policies, for example, the application market can audit the first arrangement file of the application, the first specification description information, the application description information and whether the software package comprises sensitive words.

Auditing from the security dimension refers to auditing whether the software package of the application includes viruses or trojans, etc. Specifically, the application marketplace may determine whether the application is secure by scanning the code to see if the software package of the application includes a virus or Trojan horse.

Auditing from the quality dimension refers to auditing the quality of the application. Specifically, the application marketplace may obtain test reports for the application to determine the quality of the application. In some embodiments, the application marketplace may also test the application in real-time, thereby obtaining the quality of the application.

Auditing from the development qualification dimension refers to auditing the qualification of the development of the application. Specifically, the application marketplace may obtain development qualification information for the application, e.g., from the application description information, and then determine whether the developer of the application has the development qualification specified by the application marketplace.

In the method, the application market selects corresponding dimensions from compliance, safety, quality and development qualification for auditing according to different applications, so as to meet different business requirements.

In a third aspect, the present application provides an application management method. The method may be performed by a second application management platform. Specifically, the second application management platform may receive a first orchestration file of the target application, and then parse the first orchestration file to obtain orchestration nodes on which the target application depends and dependency relationships between the orchestration nodes. The target orchestration node is a standardized service node. And then, the application market sequentially deploys the arrangement nodes on which the target application runs according to the first arrangement file.

In the method, each environment in the target deployment environment is provided with the second application management platform, each second application management platform can analyze the first layout file and sequentially deploy the layout nodes on which the target application operates according to the analysis result, namely, each second application management platform can deploy the target application according to the first layout file, so that the target application is deployed in batches to heterogeneous environments according to a unified mode, and the deployment pressure of a second user is reduced.

In some possible implementations, the first orchestration file records orchestration nodes on which the target application runs under a first specification and dependencies between the orchestration nodes. The second application management platform may also receive a second orchestration file for the target application. The second orchestration file records orchestration nodes on which the target application runs under a second specification and dependency relationships between the orchestration nodes. And then the second application management platform obtains node change information and/or the dependency change information according to the second arrangement file. The node change information is used for describing changes of arrangement nodes on which the target application depends under the second specification compared with the first specification, and the dependency relation change information is used for describing changes of dependency relations among the arrangement nodes. Then, the second application management platform may upgrade the target application to the second specification according to at least one of the node change information and the dependency change information.

In the method, the second application management platform receives the second arrangement file and analyzes the second arrangement file to obtain node change information and/or dependency change information, and the second application management platform can rapidly deploy newly added nodes or unload deleted nodes and/or modify dependency between the nodes based on the node change information, so that the application is rapidly upgraded from the first specification to the second specification, the upgrading efficiency is improved, and the application upgrading can be realized only by a small amount of computing resources or storage resources, and the upgrading threshold is reduced.

In some possible implementations, the first orchestration file records orchestration nodes on which the target application runs under a first version of the first specification and dependencies between the orchestration nodes. The second application management platform may receive a third orchestration file for the target application. The third orchestration file records orchestration nodes on which the target application runs under the second version of the first specification and dependencies between the orchestration nodes. The second application management platform may then upgrade the target application from the first version of the first specification to the second version of the first specification according to the third orchestration file.

In the method, the second application management platform processes the corresponding nodes deployed in the target deployment environment by receiving the third arrangement file and according to the third arrangement file, so that the application is rapidly upgraded from the first version of the first specification to the second version of the first specification, the upgrading efficiency is improved, the application upgrading can be realized only by a small amount of computing resources or storage resources, and the upgrading threshold is reduced.

In some possible implementations, the second application management platform may also initiate a request to establish a connection with an application marketplace, prior to receiving the first orchestration file of the target application. Accordingly, the second application management platform may receive the first orchestration file of the target application through the connection.

In the method, the second application management platform can actively establish connection with the application market, so that even if the second application management platform does not provide access to the outside, the application market can send corresponding arrangement files to the second application management platform through the connection, and further upgrading and deployment of the application are realized.

In a fourth aspect, the present application provides an application management platform. The platform comprises:

The interaction module is used for presenting a specification creation interface to a user and receiving first specification description information configured by the user through the specification creation interface, wherein the first specification description information comprises a first specification of an application;

the interaction module is further configured to present a specification arrangement interface to the user, where the specification arrangement interface carries a plurality of arrangement nodes, and a first arrangement node in the plurality of arrangement nodes is a standardized service node;

an orchestration module, configured to generate a first orchestration file of the application in response to an operation of the user on a target orchestration node of the plurality of orchestration nodes, where the first orchestration file records the target orchestration node and a dependency relationship between the target orchestration nodes on which the application runs under the first specification;

and the interaction module is also used for submitting the first arrangement file and the first specification description information to an application market so that the application market can release the application.

In some possible implementations, the first orchestration node is any one of:

standardized infrastructure as a service IaaS layer nodes, standardized platform as a service PaaS layer nodes, and standardized software as a service SaaS layer nodes.

In some possible implementations, the platform further includes:

and the normalization module is used for creating the first arrangement node through normalization information.

In some possible implementations, the application management platform interfaces with a heterogeneous environment including one or more of public cloud, private cloud, hybrid cloud, or edge cloud;

when the first arrangement node is the standardized IaaS layer node or the standardized PaaS layer node, the standardized information includes preconfigured first standardized information, and the first standardized information includes an operating system image, an access address of each environment in the heterogeneous environment, and a resource application interface in each environment in the heterogeneous environment.

In some possible implementations, the standardized PaaS layer node includes a standardized application container engine node;

when the first orchestration node is the standardized application container engine node, the standardized information further includes second standardized information including a container management platform installation package, a container installation package, and container startup parameters.

In some possible implementations, the standardized SaaS layer node includes a standardized third party application service node;

When the first orchestration node is the standardized third party application service node, the standardized information includes an interface that the third party application service is open to.

In some possible implementations, the first specification description information further includes an applicable environment of the first specification, where the applicable environment is selected from the heterogeneous environments that the application management platform interfaces with.

In some possible implementations, the orchestration module is specifically configured to:

responding to the connection operation of the user to the target orchestration nodes, and obtaining the dependency relationship between the target orchestration nodes;

and generating a first editing file of the application according to the dependency relationship between the target editing nodes.

obtaining parameters of the target orchestration node in response to configuration operation of the user on the target orchestration node;

and generating a first programming file of the application according to the parameters of the target programming node.

In some possible implementations, the platform further includes:

the standardized module is used for standardizing the application to obtain a second arrangement node, the second arrangement node is a standardized SaaS layer node, and the second arrangement node is used for creating arrangement files of other applications.

In some possible implementations, the interaction module is further configured to:

presenting a recommendation page to the user, the recommendation page indicating a recommendation to normalize the application;

the standardized module is specifically used for:

and normalizing the application to obtain the second orchestration node in response to a normalization operation of the application triggered by the user through the recommended page.

acquiring second specification description information, opening the first arrangement file in the specification arrangement interface, and acquiring a second arrangement file according to the modification of the first arrangement file by the user, wherein the second specification description information comprises a second specification of the application, and the second arrangement file records information of an arrangement node on which the application runs under the second specification;

submitting the second orchestration file and the second specification description information to the application marketplace, so as to update information of the application on the application marketplace.

In some possible implementations, the first specification description information further includes a version number of a first version of the first specification, the first orchestration file records the target orchestration node and a dependency relationship between the target orchestration nodes on which the application runs under the first version of the first specification, and the interaction module is further configured to:

Acquiring third specification description information, opening the first layout file in the specification layout interface, and acquiring a third layout file according to the modification of the first layout file by the user, wherein the third specification description information comprises version numbers of the first specification and a second version of the first specification, and the third layout file records information of layout nodes on which the application runs under the second version of the first specification;

submitting the third orchestration file and the third specification description information to the application marketplace, so as to update information of the application on the application marketplace.

In a fifth aspect, embodiments of the present application provide an application marketplace. The application market includes:

the interaction module is used for presenting an application deployment interface to a user;

the interaction module is further configured to receive deployment information of a target application configured by the user through the application deployment interface, the target application is an application requested to be deployed by the user, the deployment information comprises a target deployment environment, and the target deployment environment comprises one or more of public cloud, private cloud, hybrid cloud or edge environment;

The interaction module is further configured to send, to the target deployment environment, a first orchestration file determined by the management module, where the first orchestration file records orchestration nodes on which the target application runs and dependencies between the orchestration nodes.

In some possible implementations, the deployment information further includes first specification description information of the target application, the first specification description information including a first specification of the target application;

the management module is specifically configured to:

and determining the first arrangement file matched with the first specification from the arrangement files of the target application according to the first specification description information, wherein the first arrangement file records arrangement nodes on which the target application runs under the first specification and the dependency relations among the arrangement nodes.

In some possible implementations, the management module is specifically configured to:

determining a first arrangement file from arrangement files of the target application according to the target deployment environment, wherein the first arrangement file records arrangement nodes on which the target application runs under a first specification and the dependency relations among the arrangement nodes, and the applicable environment of the first specification comprises the target deployment environment.

receiving a first update to the deployment information, the first update including second specification description information of the target application, the second specification description information including a second specification of the target application;

the management module is further configured to:

determining a second arrangement file matched with the second specification from the arrangement files of the target application according to the second specification description information, wherein the second arrangement file records arrangement nodes on which the target application runs under the second specification and the dependency relations among the arrangement nodes;

the interaction module is further configured to:

and sending the second programming file to the target deployment environment so as to update the target application to the second specification on the target deployment environment.

In some possible implementations, the first specification description information includes a version number of a first version of the first specification; the first orchestration file records orchestration nodes on which the target application runs under a first version of the first specification and dependency relations among the orchestration nodes;

The interaction module is further configured to further include:

receiving a second update to the deployment information, the second update comprising third specification description information of the target application, the third specification description information comprising version numbers of the first specification and a second version of the first specification of the target application;

the management module is further configured to:

determining a third editing file matched with the second version of the first specification from the editing files of the target application according to the third specification description information; the third orchestration file records orchestration nodes on which the target application runs under the second version of the first specification and the dependency relations among the orchestration nodes;

the interaction module is further configured to:

and sending the third programming file to the target deployment environment so as to update the target application to the second version of the first specification on the target deployment environment.

In some possible implementations, the application marketplace further includes:

the auditing module is used for auditing the application before presenting an application deployment interface to a user;

the interaction module is further configured to:

And when the auditing is passed, presenting application introduction information of the application on the application deployment interface.

In a sixth aspect, the present application provides an application management platform. The platform comprises:

the interaction module is used for receiving a first arrangement file of the target application;

the arrangement engine is used for analyzing the first arrangement file, obtaining arrangement nodes on which the target application depends and the dependency relationship among the arrangement nodes, wherein the target arrangement nodes are standardized service nodes;

and the deployment module is used for sequentially deploying the arrangement nodes on which the target application is run according to the first arrangement file.

In some possible implementations, the first orchestration file records orchestration nodes on which the target application runs under a first specification and dependencies between the orchestration nodes;

the interaction module is further configured to:

receiving a second arrangement file of the target application, wherein the second arrangement file records arrangement nodes on which the target application runs under a second specification and the dependency relations among the arrangement nodes;

the orchestration engine is further configured to:

obtaining node change information and/or dependency change information according to the second arrangement file, wherein the node change information is used for describing the change of arrangement nodes on which the target application runs under the second specification compared with the first specification, and the dependency change information is used for describing the change of dependency between the arrangement nodes;

The platform further comprises:

and the upgrading module is used for upgrading the target application to the second specification according to at least one of the node change information and the dependency change information.

In some possible implementations, the first orchestration file records orchestration nodes on which the target application runs under a first version of a first specification and dependencies between the orchestration nodes;

the interaction module is further configured to:

receiving a third arrangement file of the target application, wherein the third arrangement file records arrangement nodes on which the target application runs under a second version of the first specification and the dependency relations among the arrangement nodes;

the platform further comprises:

and the upgrading module is used for upgrading the target application from the first version of the first specification to the second version of the first specification according to the third arrangement file.

In some possible implementations, the platform further includes:

the connection module is used for initiating a connection establishment request to an application market and establishing connection with the application market;

the interaction module is specifically configured to:

and receiving a first programming file of the target application through the connection.

In a seventh aspect, the present application provides a computing device cluster comprising at least one computing device. The at least one computing device includes at least one processor and at least one memory. The processor and the memory communicate with each other. The at least one processor is configured to execute instructions stored in the at least one memory to cause a computing device or cluster of computing devices to perform the method of any implementation of the first aspect, the second aspect or the third aspect.

In an eighth aspect, the present application provides a computer-readable storage medium having stored therein instructions that instruct a computing device or cluster of computing devices to perform the method of any implementation of the first, second or third aspects described above.

In a ninth aspect, the present application provides a computer program product comprising instructions which, when run on a computing device or cluster of computing devices, cause the computing device or cluster of computing devices to perform the method of any implementation of the first, second or third aspects described above.

Further combinations of the present application may be made to provide further implementations based on the implementations provided in the above aspects.

Drawings

In order to more clearly illustrate the technical method of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below.

Fig. 1 is a system architecture diagram of an application management method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an application creation interface provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of a specification creation interface provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of a specification layout interface according to an embodiment of the present disclosure;

fig. 5A is a schematic diagram of service node standardization according to an embodiment of the present application;

FIG. 5B is a schematic diagram of computing resource node normalization according to an embodiment of the present disclosure;

fig. 5C is a schematic diagram of third party application service node standardization according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an application deployment interface according to an embodiment of the present application;

FIG. 7 is a flowchart of an application management method according to an embodiment of the present application;

FIG. 8 is a schematic flow chart of application deployment and upgrading provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of a computing device cluster according to an embodiment of the present application;

Fig. 10 is a schematic structural diagram of a computing device cluster according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a computing device cluster according to an embodiment of the present application.

Detailed Description

The terms "first", "second" in the embodiments of the present application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature.

Some technical terms related to the embodiments of the present application will be first described.

Applications, also called application software, are in particular collections of software programs that comprise specific functions. Applications can be classified into office-type, game-type, recreational-type, industrial control-type, financial management-type, and other different types of applications according to the purpose of the application. For example, office type applications may include applications such as text processors, form processors, image editors, and the like. As another example, industrial control type applications may include production management systems, materials management systems, and the like.

Deployment of applications in local (specifically, local hardware, such as a local physical server) generally requires that software and hardware such as computation, storage, security and the like are input at one time in the early stage, so that the cost is high, the capacity expansion is time-consuming, and the quick response to a service surge is difficult. Therefore, the 'application cloud-up' can be adopted to realize quick deployment and agile capacity expansion of the application, so that the deployment and operation cost can be reduced.

Application cloud refers to deploying an application to a cloud environment. Wherein the cloud environment indicates a cluster of computing devices owned by a cloud service provider for providing computing, storage, network resources. Cloud service providers may provide different types of cloud environments, such as public clouds, private clouds, or hybrid clouds.

Public clouds refer to clusters of computing devices where resources are shared for use by different tenants (e.g., enterprises, organizations, or individuals). Computing, storage, network resources in the public cloud are owned and operated by third party cloud service providers, and these resources are provided to tenants over the Internet. A private cloud refers to a cluster of computing devices whose resources are dedicated for use by an enterprise, organization, or individual. Hybrid clouds refer to clusters of computing devices that are mixed with different environments. For example, a hybrid cloud may be a cluster of computing devices that incorporate a private cloud or local infrastructure on a public cloud basis. The local infrastructure refers to an end-side device, and includes internet of things (Internet of Things, ioT) devices such as smart home appliances or terminals such as smart phones and tablet computers. Moving data and applications between different environments may be accomplished using a hybrid cloud.

The public cloud and the private cloud substantially belong to a central cloud, and the central cloud controls resources in a centralized manner. With the gradual increase of cloud applications, a centralized cloud environment is generally difficult to meet the cloud resource requirements of 'large connection, low delay and large bandwidth' of end-side equipment, and for this purpose, the cloud environment can be expanded to an edge side closer to the end-side equipment, so that some cloud services are sunk to the edge side. The edge-side devices form an edge cloud. At least one edge node is included in the edge cloud, which may be, for example, a smart site. The edge cloud and the center cloud are matched with each other, so that the capabilities of center-edge coordination, full-network calculation power dispatching, full-network unified management and control and the like can be realized.

After the development of the application is completed, the independent software developer (independent software vendor, ISV) can hand the deployment and upgrade of the application to a professional system integration (system Integration, SI) vendor to complete the application cloud. In the application cloud process, the system integrator can deploy the application into different cloud environments, considering that the requirements of different clients can be different. For example, for small and medium enterprise customers, a system integrator may deploy applications to public clouds; for large enterprise customers, system integrators may deploy applications to private clouds, public clouds, and smart Sites (FCs).

However, when an application needs to be deployed to a different environment (e.g., a public cloud, a private cloud, a hybrid cloud, or a different cloud environment such as a smart site), in an application development phase, particularly in a later stage of the application development phase, ISVs need to be adapted for different deployment environments (e.g., orchestrating application-dependent services and dependencies between services), respectively, thus increasing delivery pressures of ISVs. In addition, in the application deployment stage, the difference of installed software in different environments is large, and the system integrator is difficult to deploy the application to different environments in batches in a unified mode, so that the deployment pressure of the system integrator is increased.

In view of this, an embodiment of the present application provides an application management method. The application management method may be performed by an application management system or an application marketplace. The application management system is also referred to as an application management platform. In some embodiments, the application management platform may be a software system that is run by a computing device or cluster of computing devices to perform the application management method. In other embodiments, the application management platform may also be a hardware system for application management. Similarly, the application market may also be a software system, or a hardware system. The embodiment of the application is exemplified by an application management platform and an application market as a software system.

In the process of cloud loading, the cloud loading method can be divided into a development stage, a release stage and a deployment stage. In the development stage, after the development of the functions or characteristics of the application is completed, the application provider lays out the layout nodes corresponding to the functions and the characteristics, and further, the application provider can also perform debugging after the layout, so that the application development is completed; in the release stage, the provider of the application can submit the relevant information of the application to the application market, and the application market releases the application; in the deployment phase, the system integrator or the application's requirement party can purchase the application in the application market, and further deploy the application into different cloud environments.

Referring to the system architecture diagram of the application management method shown in fig. 1, the application management method of the development stage may be performed by the first application management platform 100, the application management method of the release stage may be marketplaces performed by the first application management platform 100 and the application marketplace 300, and the application management method of the deployment stage may be performed by the application marketplace 300 and the second application management platform 200.

The first application management platform 100 may be deployed in a cloud environment for providing management functions such as application development for use by a first user. The first application management platform 100 may also be deployed in other environments, such as in a terminal, and the first application management platform 100 may interface with a cloud environment. The embodiments of the present application are illustrated with the first application management platform 100 deployed in a cloud environment.

The first user may be a provider of the application, e.g. an independent software developer ISV. In the application development stage, a first user creates a specification (spec) of an application through the first application management platform 100 to obtain specification description information of the application, and programs the specification of the application based on a programming node provided by the first application management platform 100 to obtain a programming file of the application, thereby realizing application development.

The specification description information of the application may include the specification of the application, and the specification of the application may include a specification name and a specification, where the specification may include a capacity of the application, a requirement on a resource, and the like. There may be multiple specifications for an application, and for ease of description, embodiments of the present application refer to the specification currently created by the first user as the first specification. Further, each specification may include one or more versions (versions). Each version (e.g., first version and second version) of a specification may correspond to a orchestration file, respectively. Taking a video conference scene as an example, the video conference application comprises a first specification and a second specification, wherein the first specification can support 100 people to access a conference at the same time, the first specification can comprise two versions, the characteristics of the first version comprise functions such as a shared screen, an electronic whiteboard and the like, and the functions such as a real-time caption, an automatic conference summary and the like are added on the basis of the second version. A second specification may be to support 500 simultaneous access to a meeting, the second specification including a version (e.g., a first version) that features "shared screen", "electronic whiteboard", etc. In this case, the video conferencing application may have three orchestration files corresponding to the first version of the first specification, the second version of the first specification, and the first version of the second specification, respectively.

It should be noted that, in the embodiment of the present application, the orchestration node provided by the first application management platform 100 is a standardized service node, and the orchestration file obtained by orchestrating based on the standardized service node may mask differences of heterogeneous environments (different deployment environments applicable to the application) such as public cloud, private cloud, hybrid cloud or edge cloud (for example, smart sites in the edge cloud), so that the first user only needs to orchestrate once for the different deployment environments applicable to the application, thereby reducing the delivery pressure of the first user. For example, when the environment to which the first version of the first specification of the video conference application is applicable includes four environments of public cloud, private cloud, mixed cloud, and edge cloud, the first user only needs to schedule the first version of the first specification of the video conference application once, and does not need to schedule for the four environments separately.

In the application publishing stage, the first application management platform 100 may submit specification description information (e.g., first specification description information) and a orchestration file (e.g., first orchestration file) of an application to the application marketplace 300, so that the application marketplace 300 publishes the application.

Accordingly, the application market 300 receives the first specification description information and the first layout file of the application, and can release the application to the outside, so that the second user can purchase the application on the application market 300 and trigger the operation of deploying the application. Wherein the second user comprises a system integrator SI or an application demander (e.g. a customer). Optionally, the application marketplace 300 may also audit the applications prior to publishing the applications externally. For example, the application marketplace 300 may audit applications from any one or more of compliance, security, quality, and development qualification dimensions. The application marketplace 300 may publish the application after the audit passes. In some embodiments, the application marketplace 300 may also return an audit opinion when the application marketplace 300 fails the audit, so that the first user may modify relevant information of the application based on the audit opinion.

In the application deployment stage, the second user may select a target application from applications published by the application marketplace 300, where the target application is an application that the second user requests to deploy, and then configure deployment information of the target application through the application deployment interface, where the deployment information includes a target deployment environment, and the application marketplace 300 may send, according to the above operation of the user, a first orchestration file to the target deployment environment, where the first orchestration file records orchestration nodes on which the target application runs and dependencies between the orchestration nodes.

Accordingly, the second application management platform 200 installed in the target deployment environment may receive the first orchestration file of the target application, parse the first orchestration file to obtain the orchestration node on which the target application runs under the first specification and the dependency relationship between the orchestration nodes, and then the second application management platform 200 sequentially deploys the orchestration nodes on which the target application runs under the first specification according to the first orchestration file, thereby implementing deployment of the application in the target deployment environment.

In the embodiment of the application, the first arrangement file is obtained by arranging the standardized service nodes, and the first arrangement file can shield differences of heterogeneous environments such as public cloud, private cloud, mixed cloud or edge cloud, so that the second user can deploy the application to different environments through one-time deployment operation, batch deployment of the application is realized, and deployment pressure of the second user is reduced.

The first application management platform 100, the application marketplace 300, and the second application management platform 200 are described below in connection with fig. 1, respectively.

The first application management platform 100 may include an orchestration management subsystem 102. The orchestration management subsystem 102 includes an interaction module 1022 and an orchestration module 1024. The interaction module 1022 is configured to present a specification creation interface to a user, and receive first specification description information configured by the first user through the specification creation interface. The first specification description information includes a first specification of the application. The interaction module 1022 is then further configured to present a specification orchestration interface to the user, where the specification orchestration interface carries a plurality of orchestration nodes, and a first orchestration node of the plurality of orchestration nodes is a standardized service node, where the first orchestration node may be any orchestration node of the plurality of orchestration nodes. The orchestration module 1024 is configured to generate a first orchestration file for the application in response to the first user selecting a target orchestration node from the plurality of orchestration nodes. The first orchestration file of the application records the target orchestration node on which the application runs under the first specification and the dependency relationship between the target orchestration nodes. The interaction module 1022 is further configured to submit the first orchestration file and the first specification description information to the application marketplace 300, so that the application marketplace 300 publishes the application.

In some possible implementations, the interaction module 1022 can also present the application creation interface before presenting the specification creation interface. Referring to the schematic diagram of the application creation interface shown in fig. 2, the application creation interface 20 carries an application configuration component that includes at least one application configuration control through which a first user can configure application introduction information to create a corresponding application. In this example, the application configuration controls include at least one of a name configuration control 21, an icon configuration control 22, an industry configuration control 23, and a scene configuration control 24, the first user may configure an application name through the name configuration control 21, configure an application logo through the icon configuration control 22, configure an industry to which the application belongs through the industry configuration control 23, and configure a scene to which the application belongs through the scene configuration control 24. Further, the application configuration controls may also include other information configuration controls 25. The first user may configure application introduction information other than the above information through the other information configuration control 25, for example, characteristics or functions supported for the application, openers information of the application, and the like. The application creation interface 20 may further include a determination control 26 and a cancellation control 27, wherein when the determination control 26 is triggered, an operation of creating the application may be triggered, and when the cancellation control 27 is triggered, an operation of creating the application may be cancelled.

When the first user triggers the determination control 27, the interaction module 1022 may present the first user-created application. The first user may trigger entry into the application details interface to create a first specification of the application. The application detail interface displays a specification list of the application, wherein the specification list can be in a list form, and the specification list can comprise specifications created by the first user. The application detail interface may also bear a specification creation control, through which the first user may trigger a specification creation operation of the application. The interaction module 1022 may present a specification creation interface to the first user in response to the first user-triggered specification creation operation.

Referring to the schematic diagram of the specification creation interface 30 shown in fig. 3, the specification creation interface 30 carries a specification configuration component that includes at least one specification configuration control through which a first user can configure specification description information to create a corresponding specification. For example, a first user may configure the first specification description information to create a first specification of the application. The first specification description information includes a first specification, wherein the first specification includes a specification name and a specification. The first specification description information may further include one or more of an applicable environment of the first specification, a pre-deployment capability, a version number of the first version of the first specification. The applicable environment is selected from heterogeneous environments. The heterogeneous environment may include one or more of public clouds, private clouds, hybrid clouds, or edge clouds. For example, the heterogeneous environment may include public clouds of different cloud service providers, and for another example, the heterogeneous environment may include public clouds and private clouds provided by the same cloud service provider.

In this example, the specification configuration controls include a name configuration control 31, an applicable environment configuration control 32, and a specification configuration control 33. The first user may configure the specification name of the first specification of the application through the name configuration control 31, for example, the specification name may be a meal delivery robot management-standard specification, then the first user may configure the deployment environment applicable to the first specification of the application through the applicable environment configuration control 32, for example, may be one or more of a public cloud, a private cloud, a hybrid cloud, or an edge cloud, and configure the specification of the first specification of the application through the specification configuration control 33, which may be, for example: the 10-thousand meal delivery robot equipment is supported to be simultaneously accessed and online; maximum data volume of single robot reported data: 100 transactions/second (transaction per second, TPS); the maximum data amount per piece of data is 2 Megabytes (MB); the maximum number of simultaneous instruction issuing of the application is supported: 50TPS; maximum data amount per instruction: 2 Kilobytes (KB).

Further, specification creation interface 30 may also include deployment configuration controls 34. The deployment configuration control 34 is used to configure the advanced deployment capability, e.g., to support the first user to select whether to deploy in advance. The advanced deployment refers to deploying the application to the matched resource in advance, and issuing the executable instance to the second user. The specification creation interface 30 may also include a version number configuration control 35 by which the first user may configure the version number of the first version of the first specification. The specification creation interface 30 may further include a determination control 36 and a cancellation control 37, wherein the first specification of the application may be created when the determination control 36 is triggered and the first specification of the application may be cancelled when the cancellation control 37 is triggered.

In this example, the specification creation interface 30 is displayed in a pop-up manner over the application details interface, and in some embodiments, the specification creation interface 30 may also be a separately displayed interface. The embodiments of the present application are not limited in this regard.

When the first user triggers the determination control 36, the interaction module 1022 may present a formatting interface. Referring to the schematic diagram of the specification layout interface shown in fig. 4, the specification layout interface 40 includes a layout node display area 41, a layout area 42, and a parameter configuration area 43, which may be located in the left, middle, and right three areas of the layout interface 40, respectively. It should be noted that, the layout interface 40 may first present the layout node display area 41 and the layout area 42, and when the user selects a layout node from the plurality of layout nodes displayed in the layout node display area 41 to the layout area 42 (for example, drags the layout node displayed in the layout node display area 41 to the layout area 42 through a drag operation or the like), and selects (for example, selects by clicking) the layout node in the layout area 42 to trigger a parameter configuration operation on the layout node, the parameter configuration area 43 may be redisplayed.

Orchestration node presentation area 41 includes a plurality of orchestration nodes, each of which is a standardized service node. Among them, standardized service nodes include standardized infrastructure as a service (Infrastructure as a Service, iaaS) layer nodes, standardized PaaS (platform as a service, iaaS) layer nodes, and standardized software as a service (software as a service, saaS) layer nodes.

The IaaS layer node comprises a computing resource node, a network resource node and a storage resource node. Wherein the computing resource nodes include one or more of a resilient computing service (Elastic Compute Service, ECS) and a Virtual Machine (VM); the network resource nodes include one or more of virtual private cloud (virtual private cloud, VPC), subnet (subnet), network address translation (Network Address Translation, NAT), elastic load balancing (Elastic load balance, ELB), and Elastic public IP (EIP); the storage resource nodes include a resilient block storage service (elastic volume service, EVS) and an object storage service (object storage service, OBS).

The ECS is a cloud server with elastically telescopic processing capacity, the processing capacity can be automatically adjusted to meet business requirements, and the VM is a virtual environment which is created in a physical hardware system and serves as a virtual computer system and simulates the whole set of hardware of the ECS, and the ECS comprises a processor, a memory, a network interface and a storage. The VPC is used for simulating the characteristics of the local area network on the public cloud, so that after the local service is cloud-loaded, a network environment similar to the local area network can be set, and the local service does not even need to modify own private network address. The subnetworks are used to partition the VPC, thereby enabling the division of one network into several small networks (i.e. subnetworks). The EIP provides independent public network IP resources, thereby providing access to and ability to be accessed by the public network. NAT refers to rewriting a source IP address or a destination IP address when an IP packet passes through a router or a firewall, and is widely used in private networks (e.g., virtual private clouds) where multiple hosts access the internet through a public IP. The ELB is a flow distribution control service for distributing the access flow to a plurality of servers at the back end according to a distribution strategy, and the service capacity of the application to the outside can be expanded through flow distribution, single-point faults are eliminated, and the availability of the application is improved.

The PaaS layer nodes include one or more of application container engine nodes, databases, container clusters (clusters), nminix load balancing, gateways, unified authentication management (Identity and Access Management, IAM), container mirror warehouse (SoftWare Repository for Container, SWR).

Among them, application container engine nodes are also called cloud container engine (cloud container engine, CCE) nodes, which provide highly scalable, high-performance kubernetes (abbreviated as K8S) clusters. CCE nodes may be used to deploy, manage, and extend containerized applications in a cloud environment. The database can be, for example, a relational database service (relational database service, RDS), is an online cloud database service which is flexible and convenient to manage, and supports a plurality of engines such as MySQL, postgreSQL, SQL Server and the like. The container cluster refers to a cloud resource combination required by container operation, and is associated with cloud resources such as a plurality of cloud server nodes, load balancing and the like. The Nginx load balancing refers to load balancing implemented based on Nginx. Nginx is a high-performance web server implemented based on the C language, and load balancing is implemented through load balancing algorithms such as polling, IP hashing and the like. The gateway may specifically be an application program interface gateway (application programming interface gateway, APIGW), which provides high-performance, high-availability, high-security API hosting services, and may be used for internal system integration and service capability opening. The IAM provides identity authentication and rights management functions that can be used to control access rights to services and resources. SWR is a service supporting full life cycle management of container mirror image, provides a simple, easy-to-use, safe and reliable mirror image management function, and helps users to rapidly deploy containerized service.

The SaaS layer nodes include one or more of configuration store (configMap) nodes, discover nodes, stateful statefulset nodes, network cluster service nodes, ingress nodes, namespaces (namespaces) nodes, role-based authentication control (RBAC) nodes.

The configMap node is used for storing parameters supporting modification when other SaaS layer nodes are arranged, and can be expressed in a key-value form, and other SaaS nodes can refer to data stored by the configMap node for parameter configuration. The capacity expansion or contraction of the stateless service is realized by the node of the deployment, the node of the deployment comprises one or more pod copies, each pod copy has the same function, and the node of the deployment can increase or delete the pod copy according to the service requirement so as to realize the capacity expansion or contraction, thereby improving the reliability and the stability of the stateless service. The statefulset node is a node designed for stateful service capacity expansion or contraction, and comprises a plurality of pod copies, each pod copy has an independent state, and the states are stored through independent storage units. The network cluster service node may be an interface routing service node that may be used to open some services of the third party application to external access, such as stateful services or stateless services. The ingress node is a network load service node for providing the capability of load access, e.g., the ingress node may be configured with a uniform locator (Uniform Resource Locator, URL) for providing externally accessible services. The namespace node is used to provide logical isolation capability between an application and an application or a service of an application. The RBAC is used for setting a plurality of authority control strategies, and provides access capability of different authorities through the control of roles and authorities, thereby meeting the authority control requirements.

The SaaS layer nodes may also include input (input) nodes and output (output) nodes. The input node is used for solving some custom parameters required by application deployment, the custom parameters can be in a key-value format, and a first user can fill in default parameters when editing. After the application is released, if there is an input node in the layout file, after entering the deployment process, the second application management platform can display the custom parameters, the second user (for example, a client or an SI) can adjust the custom parameters according to the actual deployment environment, and if the default custom parameters are set reasonably, the custom parameters can not be modified. The output nodes are used for solving the parameters which need to be output after some nodes are deployed in the application deployment process. For example, after an application is deployed, an access address and a port of the application are required to be output, when the application is arranged, the last node of the arranging file is an output node, and the output node depends on the last node, so that a deployment result of the last node of the output node is output to the output node.

In some possible implementations, the service node may also include other tier nodes, such as function-as-service (function as a service, faaS) tier nodes. The FaaS layer node may include a script execution (script executor) node and a file upload (fileUpload) node. The script execution node is used for executing the script of the application, and the file uploading node is used for uploading files, such as arranging files.

The first user may select (e.g., by dragging) a plurality of orchestration nodes from orchestration node presentation area 41 to orchestration area 42. Wherein the orchestration node dragged to orchestration area 42 is referred to as a target orchestration node. The first user may perform parameter configuration on the target orchestration node in the orchestration area 42 through the parameter configuration area 43 on the right, whereby instantiation of the target orchestration node may be achieved. It should be noted that the parameters supporting modification when different orchestration nodes are orchestrated may be different. Based on this, the parameters presented by the right side parameter configuration area 43 may be different when the first user triggers a parameter configuration operation for different target orchestration nodes.

The parameter configuration process is illustrated with the targeting orchestration node as a standardized computing resource node. For standardized computing resource nodes, the parameters presented by the parameter configuration area 43 include one or more of node name, ECS name, CPU architecture, specification type, mirror source, system disk type, system disk size, data disk type, and data disk size. The node name specifically refers to the name of the object orchestration node instantiation, in this example, the node name is configured as iotda-worker-0003, the ECS name specifically refers to the name of the installation deployment ECS, and the ECS name may be the same as the node name. The CPU architecture supports a mainstream architecture, such as may be configured as an x86 architecture or an advanced reduced instruction set machine (Advanced RISC Machine, ARM) architecture. The x86 architecture may also be divided into a 32-bit (x 86-32) architecture and a 64-bit (x 86-32) architecture. The specification types may be configured as generic or some specific specification types. The image source may be configured as a public standardized image, a non-public standardized image, a public non-standardized image, or a non-public non-standardized image. The standardized image is a general operating system image. The system disk types include a plurality of types including, for example, a hard disk drive (hard disk drive) or a solid state drive (solid state drive, SSD). In this example, the first user may configure the system disk type as an SSD, the system disk size may be set according to traffic requirements, e.g., the first user may configure the system disk size as 1 Terabyte (TB). Similarly, the first user may set the data disc type and the data disc size according to the service requirement.

The first user may furthermore connect the instantiated target orchestration nodes via arrows, wherein the arrow direction may point to the target orchestration nodes being relied upon, such that dependencies between the target orchestration nodes may be represented.

Accordingly, the orchestration module 1024 may obtain the dependencies between the target orchestration nodes (specifically, the instantiated target orchestration nodes) in response to the first user's connection operations to the target orchestration nodes, and generate the first orchestration file of the application according to the dependencies between the target orchestration nodes. The first orchestration file of the application records a target orchestration node on which the application runs depending under a first specification and a dependency relationship between the target orchestration nodes.

In some possible implementations, the specification interface 40 may also include a save control 44. When the first user has finished editing, a save operation may also be triggered by the save control 44 in the specification editing interface 40 to set the format to save the editing file. The set format may include one or more formats, for example, the set format may include formats specified by different cloud service providers.

After saving the orchestration file, the first user may also trigger the publishing control 45 of the specification orchestration interface 40, and the interaction module 1022 of the orchestration management subsystem 102 may submit the first orchestration file and the first specification description information of the application in response to the first user's operation, so that the application marketplace 300 publishes the application.

Wherein the orchestration of the first specification of the application by the first application management platform 100 is dependent on the standardization of the service nodes. Based on this, the first application management platform 100 may also include a node management subsystem 104. The node management subsystem 104 is used to normalize the serving nodes.

Specifically, node management subsystem 104 includes an interaction module 1042 and a normalization module 1044. Referring to the schematic diagram of service node standardization shown in fig. 5A, the interaction module 1042 obtains standardization information, and the standardization module 1044 is used for creating a standardized service node according to the standardization information. The normalization module 1044 may create a node adaptation layer, and store normalization information in the node adaptation layer to adapt to different deployment environments. The normalization module 1044 may create a normalized service node based on the difference of the normalized information in the node adaptation layer to mask different environments (e.g., public cloud, private cloud, hybrid cloud, edge cloud). It should be noted that, the cloud environments of the same type provided by different cloud service providers may also have differences, for example, public clouds provided by different cloud service providers may also be heterogeneous environments, and the normalization module 1044 may mask differences of cloud environments provided by different cloud service providers according to the normalization information.

In some possible implementations, the IaaS layer node or PaaS layer node may be created from general standardized information. For convenience of description, the embodiment of the present application refers to general standardized information as first standardized information. The first standardized information may be pre-configured by an administrator. The administrator may be an administrator of the first application management platform 100. The first standardized information includes an operating system image, an access address of each of the heterogeneous environments, and a resource application interface of each of the heterogeneous environments. Optionally, the first normalization information may further comprise parameters supporting modification when the node is orchestrated. When the orchestration node adopts default parameters, the first normalization information may also not include parameters that support modification when the node is orchestrated. The following illustrates some standardized procedures for IaaS layer nodes and PaaS layer nodes.

For nodes of the IaaS layer, a standardized example of computing resource nodes is described. Referring to the schematic diagram of computing resource node normalization shown in fig. 5B, the node adaptation layer of the computing resource node is also called ECS adaptation layer, and the normalization process of the computing resource node may be: for ECSs of public clouds (e.g., public clouds including different cloud service providers), VMs of smart sites, ECSs of hybrid clouds, and ECSs of private clouds, the required software or services are installed on the ECSs or VMs, followed by making an operating system image (also referred to as a VM image) based on a unified operating system. An administrator may configure the operating system images, access addresses for each of the heterogeneous environments, resource application interfaces and nodes in each of the heterogeneous environments to support modified parameters when orchestrated. The node management subsystem 104 may create an ECS adaptation layer, and save the operating system images, the access address of each environment in the heterogeneous environment, the resource application interfaces in each environment in the heterogeneous environment, and parameters supporting modification when the nodes are programmed in the ECS adaptation layer to create a standardized ECS.

For the node of PaaS layer, the explanation will be given taking the standardization of CCE nodes as an example. The node management subsystem 104 may also be standardized in connection with the second standardized information. The second standardized information includes a container management platform installation package, a container installation package, and container startup parameters. Wherein, container management platform installation package can be K8S installation package, and K8S installation package can include kubeadm, kubelet and kubectl. The container installation package may be a dock installation package. The container configuration parameters may include a dock startup mode configured to start up randomly and with security components such as swap/firewall/selinux shut down. The normalization procedure of CCE nodes may be: the administrator configures the second standardized information. The node management subsystem 104 creates a CCE adaptation layer (i.e., a node adaptation layer of a CCE node) and stores the second normalization information in the CCE adaptation layer, thereby implementing creation of a normalized CCE node based on the first normalization information and the second normalization information. The container management platform installation package and the container installation package in the second standardized information can also be preset in the operating system image.

For the nodes of PaaS layer, we will further describe the standardization of container mirror repository SWR as an example. Different cloud service providers provide different container mirror image storage mechanisms, access interfaces of container mirror images also have certain differences, and an SWR adaptation layer in the node adaptation layer can provide mirror image warehouse software packages adapted to the cloud service providers so as to achieve standardization. The normalized flow of SWR may be: an administrator may configure mirror warehouse software packages that adapt to different cloud service providers, and node management subsystem 104 creates a SWR adaptation layer in which mirror warehouse software packages that adapt to individual cloud service providers are stored, thereby creating a standardized SWR. The image warehouse software package adapting to the intelligent site and the hybrid cloud can be preset in the operating system image. It should be further noted that the image repository software package is configured to be booted after installation, and is booted when the security components such as swap/firewall/selinux are closed, and the network card IP is automatically acquired when the security components are booted.

The SaaS layer nodes may be divided into native cloud service nodes and third party application service nodes. The standardization process of the native cloud service node may refer to the IaaS layer node and the PaaS layer node, which are not described herein. Referring to the standardized schematic diagram of the third party application service node shown in fig. 5C, the node adaptation layer of the third party application service node may be an interface routing service node, such as an APIGW. The standardization process of the third party application service node may be: the developer of the third party application service (e.g., the provider of the third party application) configures an interface opened by the third party application service, optionally, the developer of the third party application service may further configure parameters supporting modification when the standardized third party application service node is arranged, the node management subsystem 104 may create an APIGW, register the interface opened by the third party application service and the parameters supporting modification when the standardized third party application service node is arranged in the APIGW, and thereby create a standardized third party application service node according to the interface opened by the third party application service and the parameters supporting modification when the standardized third party application service node is arranged. In some embodiments, the developer of the third party application service may also configure the functionality of the interface so that the functionality of the interface may be presented after the node is online. After the developer of the third party application service completes configuration of the interface and the parameters, the developer may submit the interface and the parameters to an administrator for auditing, and after the administrator auditing passes, the node management subsystem 104 may issue a standardized third party application service node. In particular, the standardized third party application service node may appear as an orchestration node in the orchestration node display area 41 for use when the first user makes the orchestration of the specifications.

Next, the structure of the application market 300 will be described. The application marketplace 300 includes an interaction module 302 and a management module 304. The interaction module 302 is configured to present an application deployment interface to the second user, and receive deployment information of the target application configured by the second user through the application deployment interface. The target application is an application requested to be deployed by a second user, and the deployment information comprises a target deployment environment. The management module 304 is used to determine a first orchestration file that is an orchestration file for the target application. The interaction module 302 is also operable to send the first orchestration file to the target deployment environment.

For ease of understanding, the following description is provided in connection with specific examples. Referring to the schematic diagram of the application deployment interface 600 shown in FIG. 6, the application deployment interface 600 includes a type control 601 and a recommended application list 602, where the recommended application list 602 includes several applications published by the application marketplace 300, which may be high-download or high-scoring applications. The application deployment interface 600 displays the application name, application logo, or other introduction information of the application. The second user may browse the application introduction information, and when it is determined that the recommended application list 602 includes the target application that is desired to be deployed, the deployment operation may be triggered by clicking the deployment control 603, and the application deployment interface 600 may display the deployment environment configuration control 604 in response to the above operation of the second user, for example, display the deployment environment configuration control 604 in a popup manner, and the second user configures the target deployment environment of the target application through the deployment environment configuration control 604, where the target deployment environment may be, for example, a hybrid cloud and a smart site. The management module 304 may determine a first orchestration file from the orchestration files of the target application, and the interaction module 302 may send the corresponding first orchestration file to the target deployment environments such as the hybrid cloud and the smart site, so as to deploy the target application in the target deployment environment according to the first orchestration file.

The application deployment interface 600 may also include a search control 605. When the target application that the second user wants to deploy is not in the recommended application list 602, or is not in the type application list (not shown in the figure) corresponding to any type control 601, the second user may search for the target application through the search control 605, the application deployment interface 600 may display a search result according to the search operation of the second user, and then the second user may trigger an operation of deploying the target application from the search result.

It should be noted that the application marketplace 300 may also include an audit module 306. The applications published by the application marketplace 300 may be applications that are audited by the auditing module 306. For example, before the application is published on the application marketplace 300, the auditing module 306 is configured to audit the application according to the first orchestration file and the first specification description information of the application submitted by the first application management platform 100. In particular implementations, the auditing module 306 may audit the application from one or more dimensions of compliance, security, quality, and development qualification. After the audit passes, the application is published on the application marketplace 300.

The second application management platform 200 may be installed in a target deployment environment. The second application management platform 200 includes an interaction module 202, an orchestration engine 204, and a deployment module 206. The interaction module 202 is configured to receive a first orchestration file of the target application, and the orchestration engine 204 is configured to parse the first orchestration file to obtain a plurality of orchestration nodes on which the target application runs under a first specification and a dependency relationship between the plurality of orchestration nodes, where each orchestration node in the plurality of orchestration nodes may be a standardized service node. The deployment module 206 is configured to sequentially deploy the orchestration nodes on a target deployment environment according to the first orchestration file, specifically, the orchestration nodes on which the target application recorded by the first orchestration file depends, and the dependency relationships between the orchestration nodes, so as to deploy the target application.

In some possible implementations, the second application management platform 200 may also include an upgrade module 208. The upgrade module 208 is used to upgrade the target application. The first orchestration file records orchestration nodes on which the target application runs under the first specification and dependency relations among the orchestration nodes. In some embodiments, the interaction module 202 is further configured to receive a second orchestration file of the target application, where the second orchestration file records a orchestration node on which the target application runs under a second specification and a dependency relationship between the orchestration nodes, and the orchestration engine 204 is further configured to parse the second orchestration file to obtain node change information and/or the dependency relationship change information, where the node change information is used to describe a change of the orchestration node on which the target application runs under the second specification compared to the first specification, the dependency relationship change information is used to describe a change of the dependency relationship between the orchestration nodes, and the upgrade module 206 is configured to upgrade the target application to the second specification according to at least one of the node change information and the dependency relationship change information. In other embodiments, the first orchestration file records orchestration nodes and dependencies between orchestration nodes on which the target application runs under the first version of the first specification; in this case, the interaction module 202 is further configured to receive a third orchestration file of the target application, where the third orchestration file records orchestration nodes on which the target application runs under the second version of the first specification and dependencies between the orchestration nodes; the upgrade module 208 is configured to upgrade the target application to the second version of the first specification according to the third orchestration file.

The structures of the first application management platform 100, the second application management platform 200, and the application marketplace 300 are described above in detail, and the application management method of the embodiment of the present application is described below from the interaction point of view.

Referring to the flowchart of the application management method shown in fig. 7, the method includes:

s702: the first application management platform 100 receives standardized information configured by an administrator.

S704: the first application management platform 100 creates a standardized service node from the standardized information.

Specifically, the first application management platform 100 may normalize the IaaS layer node, the PaaS layer node, and the SaaS layer node to obtain a normalized service node, where the normalized service node includes a normalized IaaS layer node, a normalized PaaS layer node, and a normalized SaaS layer node. The first application management platform 100 receives the standardized information configured by the administrator of the first application management platform 100, and uses the standardized information to normalize corresponding nodes in a heterogeneous environment such as a heterogeneous cloud, so that a foundation can be laid for the standardization of arrangement, and a first user can obtain an arrangement file for deploying an application to the heterogeneous environment through one-time arrangement.

For the third-party application service node, the first application management platform 100 may further receive an interface configured by a developer of the third-party application service to open the third-party application service and parameters that support modification when the standardized third-party application service node is arranged, and create the standardized third-party application service node according to the standardized information such as the interface and the parameters.

The specific processes of the standardized IaaS layer node, the standardized PaaS layer node, and the standardized SaaS layer node may refer to the related descriptions in the introduction node management subsystem 104, which are not described in detail.

S706: the first application management platform 100 presents an application creation interface to the first user and receives application introduction information configured by the first user through the application creation interface.

After generating the orchestration node, the first application management platform 100 may support the first user to orchestrate the first specification of the application according to the orchestration node, thereby implementing efficient, low-threshold application development.

Specifically, the first application management platform 100 presents an application creation interface to the first user to support the first user creation application. Referring to the schematic diagram of the application creation interface 20 shown in fig. 2, the first user may configure application introduction information such as name configuration control 21, icon configuration control 22, industry configuration control 23, scene configuration control 24, configuration application name, application logo, application belonging industry, application belonging scene, etc. through various application configuration controls carried on the application creation interface 20, and of course, the first user may also configure other application introduction information besides the above information through other information configuration control 25, for example, may include characteristics or functions supported by the application, openers information of the application, etc. Creating an application can thus be achieved.

S708: the first application management platform 100 presents the created application to the first user, and presents an application detail interface to the first user in response to the first user's detail viewing operation of the application.

When the first user completes configuration of application introduction information at the application creation interface and triggers an application creation operation, the first application management platform 100 may present the created application to the first user. The application may include one or more applications created by the first user. The user may trigger a detail view operation for the application, presenting an application detail interface for the application to the first user.

It should be noted that, the application management method according to the embodiment of the present application may not be executed in S708, for example, the first application management platform 100 may directly execute S710 after creating the application to enter the specification creation interface to create the first specification of the application.

S710: the first application management platform 100 responds to a specification creation operation triggered by the first user through an application detail interface, presents a specification creation interface for the first user, and receives first specification description information configured by the first user.

The application detail interface displays a specification list of the application. The specification list may be in the form of a list. The specification list includes the first user created specification. Wherein, when the first user creates the specification of the application for the first time, the specification list may be empty. The application detail interface further includes a specification creation control through which the first user may trigger a specification creation operation, and the first application management platform 100 presents the specification creation interface to the first user in response to the specification creation operation of the first user.

Referring specifically to the schematic diagram of the specification creation interface 30 shown in fig. 3, the specification creation interface 30 carries various specification creation controls, and the first application management platform 100 may receive first specification description information configured by the first user through the specification creation controls. The first specification description information includes a first specification. The first specification includes a specification name and a specification. The specification may be used to describe the capacity of the application, the demand for resources, etc. In some embodiments, the first specification description information may also include one or more of an applicable environment of the first specification, a version number of the first version of the first specification, and the like.

S712: the first application management platform 100 presents a specification orchestration interface to a first user, and generates a first orchestration file for an application in response to the first user's operation on a target orchestration node.

When the first user has configured the first specification description information at the specification creation interface 30, the determination control 37 may be triggered, and the first application management platform 100 may present the specification orchestration interface to the first user in response to the above-described operation by the first user. Referring to the schematic diagram of the specification orchestration interface 40 shown in FIG. 4, the specification orchestration interface 40 includes an orchestration node display area 41 and an orchestration area 42.

The orchestration node display area 41 comprises a plurality of orchestration nodes, from which the first user can select (e.g. drag) several orchestration nodes to the orchestration area 42, the orchestration nodes selected to the orchestration area 42 being the target orchestration nodes. The first user may perform a connection operation or a parameter configuration operation on the target orchestration node. Wherein a first user may click on a target orchestration node in orchestration area 42, orchestration interface 40 may display a corresponding parameter configuration area 42, and the first user may perform a parameter configuration operation on the target orchestration node in parameter configuration area 42.

The first application management platform 100 may obtain a dependency relationship between the target orchestration nodes in response to a connection operation of the first user to the target orchestration nodes, and generate the first orchestration file according to the dependency relationship between the target orchestration nodes. The first application management platform 100 may also generate a first orchestration file of the application according to the parameters of the target orchestration node, and the specific process may be described with reference to the related content of the embodiment shown in fig. 1, which is not described herein again.

Because the arrangement node provided by the first application management platform 100 is a standardized service node, the arrangement file obtained by arrangement based on the standardized service node can shield the difference of heterogeneous environments such as public cloud, private cloud, mixed cloud or edge cloud, so that the first user can arrange the arrangement file only once aiming at different deployment environments, and the delivery pressure of the first user is reduced.

S714: the first application management platform 100 submits a first orchestration file and first specification description information for an application to the application marketplace 300.

In some possible implementations, the first application management platform 100 may also submit application introduction information for the application to the application marketplace 300. Similarly, the first application management platform 100 may also submit a software package of applications to the application marketplace 300, including program code corresponding to the application-dependent services.

S716: the application marketplace 300 audits the application according to the first orchestration document and the first specification description information of the application, and issues the application after the audit is passed.

The application marketplace 300 may audit the application from one or more dimensions of compliance, security, quality, and developer qualification based on the first orchestration file and the first specification description of the application. When the application marketplace 300 also receives application description information and software packages, it may also audit in connection with the application description information and software packages.

Where auditing from the compliance dimension refers to auditing whether the application meets relevant regulations or policies, for example, the application marketplace 300 may audit the first orchestration file, the first specification description information, and the application description information of the application, and whether sensitive words are included in the software package.

Auditing from the security dimension refers to auditing whether the software package of the application includes viruses or trojans, etc. In particular, the application marketplace 300 may determine whether the application is secure by scanning the code to see if the software package of the application includes a virus or Trojan horse.

Auditing from the quality dimension refers to auditing the quality of the application. Specifically, the application marketplace 300 may obtain test reports for the application to determine the quality of the application. In some embodiments, the application marketplace 300 may also test applications in real-time, thereby obtaining the quality of the applications.

Auditing from the development qualification dimension refers to auditing the qualification of the development of the application. Specifically, the application marketplace 300 may obtain development qualification information for an application, such as from application description information, and then determine whether a developer of the application has the development qualification specified by the application marketplace 300.

It should be noted that, in some embodiments, the application market 300 may directly publish the application without auditing the application. For example, where the first user is a trusted user, the application marketplace 300 may publish the application directly. The application marketplace 300 may present application introduction information, first specification description information, of the application, thereby implementing the publishing application.

In some possible implementations, the first application management platform 100 may also standardize applications. Specifically, the first application management platform 100 may request the authorization of the first user by way of an inquiry, and standardize the application after obtaining the authorization of the first user.

The application standardization process may be that the first application management platform 100 may receive the application open interface configured by the first user and parameters supporting modification when the corresponding orchestration node of the application is orchestrated, and then normalize the parameters supporting modification according to the application open interface and the parameters supporting modification when the corresponding orchestration node of the application is orchestrated, so as to obtain the corresponding orchestration node of the application. For ease of description, this orchestration node is also referred to as a second orchestration node. The first application management platform 100 may add the second orchestration node to the existing plurality of orchestration nodes, and when the specification orchestration interface is presented again, the specification orchestration interface includes the second orchestration node thereon, so that providers of other applications use the second orchestration node to create orchestration files of other applications. This may improve the development efficiency of other applications.

In some possible implementations, the first application management platform 100 can present a recommendation page to the first user. The recommendation page indicates a recommendation to normalize the application. Wherein the recommendation page may include a standardized control. The first user may trigger a normalization operation on the application through the normalization control, and the first application management platform 100 may normalize the application in response to the first user triggering the normalization operation on the application through the recommendation page, so as to obtain the second orchestration node.

S718: the application marketplace 300 presents an application deployment interface to the second user, and receives deployment information of the target application configured by the second user through the application deployment interface.

The application marketplace 300 may present an application deployment interface to the second user, so that the second user selects a target application to be deployed from the application deployment interface, and configures deployment information of the target application. The deployment information may be, for example, a target deployment environment. The target deployment environment may be one or more of public cloud, private cloud, hybrid cloud, or edge cloud. The public cloud, the private cloud, the hybrid cloud, the edge cloud, or the like may be further classified according to cloud service providers, for example, may be classified into a first party cloud (cloud environment provided by the cloud service provider of the first application management platform 100) and a third party cloud (cloud environment provided by other cloud service providers). .

S720: the application marketplace 300 sends the first orchestration file to the second application management platform 200 in the target deployment environment.

The application marketplace 300 may determine the first orchestration file and then send the first orchestration file to the second application management platform 200 in the target deployment environment. It should be appreciated that in this embodiment, the second user-configured target deployment environment may comprise a plurality of deployment environments (e.g., a public cloud, a private cloud, etc.), and the application marketplace 300 may send the first orchestration file to each of the target deployment environments, respectively.

Wherein the application marketplace 300 determines that the first orchestration file may include a variety of implementations. The following illustrates various implementations, respectively.

In a first implementation, the deployment information further includes first specification description information of the target application, and the application marketplace 300 may determine, from among the orchestration files of the target application, the first orchestration file that matches the first specification in the first specification description information according to the first specification description information. The first orchestration file records orchestration nodes on which the target application runs under the first specification and the dependency relations among the orchestration nodes. The application marketplace 300 may determine, from the layout files of the target application, a first layout file matching the first version of the first specification according to the first specification description information. The first orchestration file records orchestration nodes on which the target application runs under the first version of the first specification and dependency relations among the orchestration nodes.

In a second implementation manner, the application marketplace 300 may obtain specification description information of each specification of the target application, including, for example, first specification description information, where an applicable environment of the first specification is recorded, and then determine the first layout file according to the applicable environment and the target deployment environment recorded in the specification description information of each specification by the application marketplace 300. The first layout file is a first specification layout file of the target application, and the applicable environment of the first specification comprises the target deployment environment.

It should be appreciated that an application published on the application marketplace 300 may contain multiple specifications, including, for example, a first specification and a second specification. The first orchestration file may be one (e.g., when the first specification of the application contains only one version) or more (e.g., when the first specification of the application contains multiple versions) when the second user chooses to deploy only the first specification. When the second user selects to deploy the first specification and the second specification, the application marketplace 300 may also determine a second orchestration file according to the second specification, and send the second orchestration file to the target deployment environment selected by the second user, based on the above. Wherein the second orchestration file may also be one (e.g. when the second specification of the application contains only one version) or more (e.g. when the second specification of the application contains multiple versions). It should also be appreciated that in either case, when the second user selected target deployment environment includes a plurality of, the application marketplace 300 may send the finalized orchestration file to each of the target deployment environments, respectively. S722: the second application management platform 200 parses the first orchestration file through the orchestration engine to obtain orchestration nodes on which the target application depends and the dependencies between the orchestration nodes.

The second application management platform 200, upon receiving the first orchestration file, may invoke an orchestration engine, also referred to as a parsing engine, a driver engine (driver engine), or a agent (agent), that parses the first orchestration file to obtain orchestration nodes on which the target application depends and dependencies between the orchestration nodes. Wherein each orchestration node of the plurality of orchestration nodes may be described by a node type and a parameter of the orchestration node, wherein the parameter may be a default parameter or a first user configured parameter.

For ease of understanding, an example is described below with one orchestration node. The node type of the orchestration node may be a computing resource node, that is, the orchestration node is used to characterize a standardized computing resource node. The parameters of the programming node are represented by the following key value pairs:

node name: iotda-worker-0003;

ECS name: iotda-worker-0003;

CPU architecture: x86-64;

specification type: a general purpose type;

mirror image source: the disclosed standardized mirror image;

system disk type: SSD;

system disk size: 1TB;

data disc type: SSD;

data disc size: 10TB.

It should be noted that, the second application management platform 200 may be installed on the target deployment environment by an administrator of the second application management platform 200 or an administrator of the target deployment environment. The administrator of the second application management platform 200 or the administrator of the target deployment environment may install the orchestration engine in the target deployment environment in advance, or may install the second application management platform 200 when the second user triggers the application deployment operation. An administrator of the second application management platform 200 or an administrator of the target deployment environment may install the second application management platform in advance in consideration of installation efficiency and user experience.

Further, after the installation of the second application management platform 200 is completed, a request for establishing a connection may be further initiated to the application market 300 to establish a connection with the application market 300. Accordingly, the second application management platform 200 may receive the first orchestration file of the target application through the above connection.

S724: the second application management platform 200 sequentially deploys the orchestration nodes on which the target application runs on the target deployment environment according to the first orchestration file.

Specifically, the second application management platform 200 may determine a deployment order of the plurality of orchestration nodes according to a dependency relationship between the plurality of orchestration nodes, wherein the depended orchestration nodes have a higher priority than the depended orchestration nodes. Then, the second application management platform 200 may sequentially deploy the orchestration nodes on the target deployment environment according to the deployment order of the plurality of orchestration nodes, thereby implementing the deployment of the target application.

When the second application management platform 200 deploys the orchestration node, the orchestration node may be implemented through a corresponding mirror image. Taking the deployment standardized ECS as an example, the second application management platform 200 may install an operating system image on the target deployment environment, then call the corresponding resource application interface to create an ECS instance according to the access address of each environment in the heterogeneous environment recorded by the ECS adaptation layer and the information such as parameters supporting modification when the resource application interface and the node in each environment are arranged, and configure the ECS instance according to the parameters, and set the address referenced by the ECS instance as the access address of the corresponding environment, thereby implementing the deployment standardized ECS.

It should be noted that, if the orchestration node is deployed to the edge cloud, since the corresponding physical server is purchased, the cloud server does not need to be purchased any more, and the second application management platform 200 may automatically apply for the required resources, such as computing resources, network resources, and storage resources, so as to improve the efficiency of remote operation and batch deployment.

Because the first arrangement file is obtained by arranging the standardized service nodes, the first arrangement file can shield the difference of heterogeneous environments such as public cloud, private cloud, mixed cloud or edge cloud, so that a second user can deploy the application to different environments through one-time deployment operation, batch deployment of the application is realized, and deployment pressure of the second user is reduced.

In some possible implementations, the first user may also update applications that have been published on the application marketplace. Wherein the updating of the application can be classified into intra-specification updating and cross-specification updating. Intra-specification update refers to updating one specification of an application from one version to another, e.g., updating a first version of a first specification of an application to a second version of the first specification, and cross-specification update refers to updating an application from one specification to another, e.g., from a V2 version of the first specification to a V1 version of the second specification, or from a V1 version of the first specification to a V1 version of the second specification.

The first user may edit the orchestration file of the application after generating the update based on the orchestration file already existing in the application, and in-specification update and cross-specification update are respectively exemplified below.

In the first case, the first application management platform 100 may obtain the second specification description information, and open the first layout file in the specification layout interface, and obtain the second layout file according to the modification of the first layout file by the first user. The second specification description information comprises a second specification, and the second arrangement file records information of arrangement nodes on which the application runs under the second specification. The first application management platform 100 may then submit the second orchestration file and the second specification description information to the application marketplace 300 in order to update the information of the application at the application marketplace 300.

Specifically, the first user may find the first specification in the specification list of the application detail interface, and then trigger the specification creation operation through the specification creation control of the application detail interface to create the second specification. The first application management platform 100 presents a specification creation interface to the first user through which the first user can configure the second specification description information. Next, the first application management platform 100 opens the first orchestration file in the specification orchestration interface. The first user may modify the first orchestration file, for example, add or delete a target orchestration node, modify a parameter of a target orchestration node, or modify a connection relationship between target orchestration nodes, and then the first application management platform 100 obtains the second orchestration file according to the modification of the first orchestration file by the first user.

In the second case, the first specification description information further includes a version number of the first version of the first specification. The first orchestration file records dependencies between target orchestration nodes and target orchestration nodes on which the application runs under a first version of the first specification. The first application management platform 100 obtains the third specification description information, opens the first layout file in the specification layout interface, and obtains the third layout file according to the modification of the first layout file by the user. The third specification description information comprises a first specification and a version number of a second version of the first specification, and the third arrangement file records information of arrangement nodes on which the application runs under the second version of the first specification. The first application management platform 100 may then submit the third orchestration file and the third specification description information to the application marketplace 300 to facilitate updating information of the application in the application marketplace 300, e.g., updating information of specifications, versions, or functional specifications of the application on a corresponding interface (e.g., an application deployment interface).

Specifically, the first user may find the first version of the first specification in the specification list of the application detail interface, and then trigger an update operation on the first specification by clicking or the like, where the first application management platform 100 presents a specification update interface to the first user, and the first user may configure third specification description information through the specification update interface. The third specification description information comprises a first specification and a version number of a second version of the first specification. Then, the first application management platform 100 opens the first layout file in the specification layout interface, and obtains a third layout file according to the modification of the first layout file by the user.

It should be noted that the application marketplace 300 may provide a software package and/or an upgrade package for the updated application. The updated software package is used for directly deploying the updated application, and the upgrade package is used for upgrading the application from a first specification to a second specification or upgrading the application from a first version of the first specification to a second version of the first specification.

Accordingly, the second application management platform 200 may detect whether the specification or version of the target application is updated. If so, the second application management platform 200 may perform an automatic upgrade or a manual upgrade according to the upgrade policy. Wherein, the automatic upgrade refers to that the second application management platform 200 upgrades directly in the background without manual participation. Manual upgrade refers to upgrade after the second application management platform 200 obtains authorization of the second user, and typically requires manual intervention.

When the specification of the target application published in the application market 300 is updated from the first specification to the second specification, the second application management platform 200 may upgrade the target application in the target deployment environment from the first specification to the second specification. When the target application published in the application marketplace 300 is updated from the first version of the first specification to the second version of the first specification, the second application management platform 200 may upgrade the target application in the target deployment environment from the first version of the first specification to the second version of the first specification. The following detailed description is given respectively.

The first case is that the application marketplace 300 receives a first update to the deployment information, such as a first update to the deployment information by a second user, the first update including second specification description information of the target application, the second specification description information including a second specification of the target application. The application marketplace 300 may then determine, from the orchestration files of the target application, a second orchestration file that matches the second specification based on the second specification description information, and then send the second orchestration file to the target deployment environment. As such, the second application management platform 200 may update the target application from the first specification to the second specification on the target deployment environment.

In a second scenario, the application marketplace 300 receives a second update to the deployment information, such as a second user's second update to the deployment information, that includes third specification description information of the target application. The third specification description information includes a first specification of the target application and a version number of a second version of the first specification. The application marketplace 300 then determines, from among the orchestration files of the target application, a third orchestration file that matches the second version of the first specification, based on the third specification description information, the third orchestration file having recorded orchestration nodes and dependencies between orchestration nodes on which the application runs under the second version of the first specification. The application marketplace 300 may send the third orchestration file described above to the target deployment environment. As such, the second application management platform 200 may update the target application from the version of the first specification to the second version of the first specification on the target deployment environment.

For ease of understanding, the process of application deployment and upgrade is described below in connection with a specific example.

Referring to the flow diagram of application deployment and upgrade shown in fig. 8, as shown in fig. 8, the application identified as APPID1 includes three specifications. These three specifications are denoted SPEC-CODE1, SPEC-CODE2, and SPEC-CODE3, respectively. Among these, SPEC-CODE1 represents three versions of the specification, V1, V2, and V3, respectively. The three versions of the specification SPEC-CODE1 correspond to three orchestration files, respectively, through which a second user can deploy to environment A, environment B, environment C, and environment D when installing an application. The environment A represents a first party cloud (such as a first party public cloud), the environment B represents a hybrid cloud, the environment C represents an intelligent site, and the environment D represents a third party cloud (such as a third party public cloud).

Suppose that environments A and B and environments C and D have corresponding V1 version, V2 version, and V3 version of the specification SPEC-CODE1 installed. Since the orchestration node used for orchestrating the files is a standardized service node, the standardized service node can be installed to a heterogeneous environment in a unified manner when the application is installed, and 4 instances of the application are generated. These 4 examples are identified by instance1, instance2, instance3 and instance4, respectively. Therefore, the installation operation is simplified, and the application deployment efficiency is improved.

In this example, since the specification SPEC-CODE1 has been released to the V3 version, the second application management platform 200 on each environment automatically detects whether the specification or version of the above example is updated, and if so, may enter an upgrade procedure to upgrade the application to the V3 version.

The application management method provided in the embodiment of the present application is described in detail above with reference to fig. 1 to 8, and the first application management platform 100, the application marketplace 300, and the second application management platform 200 provided in the embodiment of the present application will be described below with reference to the accompanying drawings.

Referring to the schematic structural diagram of the first application management platform 100 shown in fig. 1, the first application management platform 100 includes an orchestration management subsystem 102, where the orchestration management subsystem 102 specifically includes:

an interaction module 1022, configured to present a specification creation interface to a user, and receive first specification description information configured by the user through the specification creation interface, where the first specification description information includes a first specification of an application;

the interaction module 1022 is further configured to present a specification layout interface to the user, where the specification layout interface carries a plurality of layout nodes, and a first layout node in the plurality of layout nodes is a standardized service node;

An orchestration module 1024, configured to generate, in response to an operation of a target orchestration node of the plurality of orchestration nodes by the user, a first orchestration file of the application, where the first orchestration file records the target orchestration node and a dependency relationship between the target orchestration nodes on which the application runs under the first specification;

the interaction module 1022 is further configured to submit the first orchestration file and the first specification description information to the application marketplace 300, so that the application marketplace 300 publishes the application.

In some possible implementations, the first orchestration node is any one of:

In some possible implementations, the first application management platform 100 further includes a node management subsystem 104, where the node management subsystem 104 is configured to implement node standardization. Wherein the node management subsystem 104 comprises:

a normalization module 1044 for creating the first orchestration node by normalizing the information.

In some possible implementations, the first application management platform 100 interfaces with a heterogeneous environment including one or more of public cloud, private cloud, hybrid cloud, or edge cloud;

In some possible implementations, the orchestration module 1024 is specifically configured to:

In some possible implementations, the first application management platform 100 further includes:

the normalization module 1044 is configured to normalize the application to obtain a second orchestration node, where the second orchestration node is a normalized SaaS layer node, and the second orchestration node is configured to create orchestration files of other applications.

In some possible implementations, the node management subsystem 104 further includes:

an interaction module 1042 for presenting a recommendation page to the user, the recommendation page indicating that the application is recommended to be standardized;

The normalization module 1044 is specifically configured to:

In some possible implementations, the interaction module 1022 is further configured to:

submitting the second orchestration file and the second specification description information to the application marketplace 300, so as to update information of the application on the application marketplace.

In some possible implementations, the first specification description information further includes a version number of a first version of the first specification, the first orchestration file records the target orchestration node and a dependency relationship between the target orchestration nodes on which the application runs under the first version of the first specification, and the interaction module 1022 is further configured to:

submitting the third orchestration file and the third specification description information to the application marketplace 300, so as to update information of the application on the application marketplace 300.

The first application management platform 100 according to the embodiment of the present application may correspond to performing the method described in the embodiment of the present application, and the above and other operations and/or functions of each module/unit of the first application management platform 100 are respectively for implementing the corresponding flow of each method in the embodiment shown in fig. 7, which is not repeated herein for brevity.

Next, referring to the schematic structure of the application market 300 shown in fig. 1, the application market 300 includes:

an interaction module 302 for presenting an application deployment interface to a user;

The interaction module 302 is further configured to receive deployment information of a target application configured by the user through the application deployment interface, where the target application is an application that the user requests to be deployed, and the deployment information includes a target deployment environment, and the target deployment environment includes one or more of public cloud, private cloud, hybrid cloud, or edge environment;

the interaction module 302 is further configured to send, to the target deployment environment, a first orchestration file determined by the management module 304, where the first orchestration file records orchestration nodes on which the target application runs and dependencies between the orchestration nodes.

the management module 304 is specifically configured to:

In some possible implementations, the management module 304 is specifically configured to:

In some possible implementations, the interaction module 302 is further configured to:

the management module 304 is further configured to:

the interaction module 302 is further configured to:

the interaction module 302 is further configured to further include:

the management module 304 is further configured to:

the interaction module 302 is further configured to:

In some possible implementations, the application marketplace 300 further includes:

an auditing module 306 for auditing the application before presenting the application deployment interface to the user;

the interaction module 302 is further configured to:

The application marketplace 300 according to the embodiment of the present application may correspond to performing the methods described in the embodiment of the present application, and the above and other operations and/or functions of the respective modules/units of the application marketplace 300 are respectively for implementing the respective flows of the respective methods in the embodiment shown in fig. 7, and are not repeated herein for brevity.

Next, referring to the schematic structural diagram of the second application management platform 200 shown in fig. 1, the second application management platform 200 includes:

an interaction module 202 for receiving a first orchestration file of a target application;

an orchestration engine 204, configured to parse the first orchestration file, obtain an orchestration node that the target application depends on, and a dependency relationship between the orchestration nodes, where the target orchestration node is a standardized service node;

and the deployment module 206 is configured to sequentially deploy the orchestration nodes on which the target application runs according to the first orchestration file.

the interaction module 202 is further configured to:

the orchestration engine 204 is also configured to:

the second application management platform 200 further includes:

an upgrade module 208, configured to upgrade the target application to the second specification according to at least one of the node change information and the dependency change information.

The interaction module 202 is further configured to:

the second application management platform 200 further includes:

and an upgrade module 208, configured to upgrade the target application from the first version of the first specification to the second version of the first specification according to the third orchestration file.

In some possible implementations, the second application management platform 200 further includes:

the interaction module 202 is specifically configured to:

The second application management platform 200 according to the embodiment of the present application may correspond to performing the method described in the embodiment of the present application, and the above and other operations and/or functions of each module/unit of the second application management platform 200 are respectively for implementing the corresponding flow of each method in the embodiment shown in fig. 7, which is not repeated herein for brevity.

The embodiment of the application also provides a computing device cluster. The cluster of computing devices includes at least one computing device, which may be, for example, a server. The computing device cluster is specifically configured to implement the functionality of the first application management platform 100 in the embodiment shown in fig. 1.

Fig. 9 provides a schematic diagram of a computing device cluster, and as shown in fig. 9, the computing device cluster 90 includes a plurality of computing devices 900, the computing devices 900 including a bus 901, a processor 902, a communication interface 903, and a memory 904. Communication between the processor 902, the memory 904, and the communication interface 903 is via a bus 901.

Bus 901 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

The processor 902 may be any one or more of a central processing unit (central processing unit, CPU), a graphics processor (graphics processing unit, GPU), a Microprocessor (MP), or a digital signal processor (digital signal processor, DSP).

The communication interface 903 is used for communication with the outside. For example, the communication interface 903 is configured to receive the first specification description information configured by the user through the specification creation interface, submit the first layout file and the first specification description information to the application marketplace 300, and so on.

The memory 904 may include volatile memory (RAM), such as random access memory (random access memory). The memory 904 may also include a non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, hard Disk Drive (HDD), or solid state drive (solid state drive, SSD).

The memory 904 has stored therein computer readable instructions that are executed by the processor 902 to cause the cluster of computing devices 90 to perform the aforementioned application management methods (or to implement the aforementioned functionality of the first application management platform 100).

In particular, in the case of implementing the embodiment of the system shown in fig. 1, and in the case where the functions of the modules of the first application management platform 100 described in fig. 1, such as the orchestration module 1024 and the normalization module 1044, are implemented by software, software or program code required to perform the functions of the modules in fig. 1 may be stored in at least one memory 904 in the computing device cluster 90. The at least one processor 902 executes program code stored in the memory 904 to cause the cluster of computing devices 90 to perform the aforementioned application management methods.

FIG. 10 provides a schematic diagram of a computing device cluster that is specifically used to implement the functionality of the application marketplace 300 in the embodiment shown in FIG. 1. As shown in fig. 10, the computing device cluster 10 includes a plurality of computing devices 1000, the computing devices 1000 including a bus 1001, a processor 1002, a communication interface 1003, and a memory 1004. The processor 1002, the memory 1004 and the communication interface 1003 communicate with each other via a bus 1001.

The specific implementation of the bus 1001, the processor 1002, the communication interface 1003, and the memory 1004 may be described with reference to the embodiment shown in fig. 9. In the present embodiment, the memory 1004 has stored therein computer readable instructions that are executed by the processor 1002 to cause the cluster of computing devices 10 to perform the aforementioned application management method (or to implement the functionality of the aforementioned application marketplace 300).

In particular, in the case of implementing the embodiment of the system shown in fig. 1, and where the functions of the modules of the application marketplace 300 described in fig. 1, such as the management module 304 and the auditing module 306, are implemented by software, the software or program code required to perform the functions of the modules in fig. 1 may be stored in at least one memory 1004 in the computing device cluster 10. The at least one processor 1002 executes program code stored in the memory 1004 to cause the cluster of computing devices 10 to perform the aforementioned application management methods.

FIG. 11 provides a schematic diagram of a computing device cluster that is specifically configured to implement the functionality of the second application management platform 200 of the embodiment shown in FIG. 1. As shown in fig. 11, computing device cluster 11 includes a plurality of computing devices 1100, computing device 1100 including a bus 1101, a processor 1102, a communication interface 1103, and a memory 1104. The processor 1102, the memory 1104 and the communication interface 1103 communicate via the bus 1101.

The specific implementation of the bus 1101, the processor 1102, the communication interface 1103 and the memory 1104 may be described with reference to the embodiment shown in fig. 9. In the present embodiment, the memory 1104 stores therein computer readable instructions that are executed by the processor 1102 to cause the computing device cluster 11 to perform the aforementioned application management method (or to implement the aforementioned functions of the second application management platform 200).

In particular, in the case of implementing the embodiment of the system shown in fig. 1, and where the functions of the modules of the second application management platform 200 described in fig. 1, such as the orchestration engine 202, the deployment module 206, and the upgrade module 208, are implemented by software, the software or program code required to perform the functions of the modules in fig. 1 may be stored in at least one memory 1104 in the computing device cluster 11. The at least one processor 1102 executes the program code stored in the memory 1104 to cause the cluster of computing devices 11 to perform the application management methods described above.

Embodiments of the present application also provide a computer-readable storage medium. The computer readable storage medium may be any available medium that can be stored by a computing device or a data storage device such as a data center containing one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc. The computer-readable storage medium includes instructions that instruct a computing device or cluster of computing devices to perform the above-described application management method.

Embodiments of the present application also provide a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computing device, the processes or functions described in accordance with the embodiments of the present application are produced in whole or in part. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computing device, or data center to another website, computing device, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer program product may be a software installation package that can be downloaded and executed on a computing device or cluster of computing devices in the event that any of the aforementioned methods of application management are desired.

The descriptions of the processes or structures corresponding to the drawings have emphasis, and the descriptions of other processes or structures may be referred to for the parts of a certain process or structure that are not described in detail.

Claims

1. An application management method, performed by an application management platform, the method comprising:

presenting a specification creation interface to a user, and receiving first specification description information configured by the user through the specification creation interface, wherein the first specification description information comprises a first specification of an application;

presenting a specification arrangement interface to the user, wherein the specification arrangement interface carries a plurality of arrangement nodes, and a first arrangement node in the plurality of arrangement nodes is a standardized service node;

generating a first orchestration file of the application in response to the user operating a target orchestration node in the plurality of orchestration nodes, the first orchestration file recording the target orchestration node and the dependency relationship between the target orchestration nodes on which the application runs under the first specification;

submitting the first arrangement file and the first specification description information to an application market so that the application market can release the application.

2. The method of claim 1, wherein the first orchestration node is any one of:

3. The method of claim 2, wherein prior to presenting the specification creation interface to the user, the method further comprises:

the first orchestration node is created by normalizing the information.

4. The method of claim 3, wherein the application management platform interfaces with a heterogeneous environment comprising one or more of a public cloud, a private cloud, a hybrid cloud, or an edge cloud;

5. The method of claim 4, wherein the standardized PaaS layer node comprises a standardized application container engine node;

6. A method according to claim 3, wherein the standardized SaaS layer node comprises a standardized third party application service node;

7. The method of claim 4, wherein the first specification description information further includes an applicable environment of the first specification, the applicable environment being selected from the heterogeneous environments of the application management platform dock.

8. The method of any one of claims 1 to 7, wherein the generating a first orchestration file for the application in response to the user operating a target orchestration node of the plurality of orchestration nodes comprises:

9. The method of any one of claims 1 to 7, wherein the generating a first orchestration file for the application in response to the user operating a target orchestration node of the plurality of orchestration nodes comprises:

10. The method according to any one of claims 1 to 9, further comprising:

and normalizing the application to obtain a second editing node, wherein the second editing node is a normalized SaaS layer node and is used for creating editing files of other applications.

11. The method according to any one of claims 1 to 10, further comprising:

12. The method according to any one of claims 1 to 10, wherein the first specification description information further includes a version number of a first version of the first specification, the first orchestration file having recorded the target orchestration node and dependencies between the target orchestration nodes on which the application runs under the first version of the first specification, the method further comprising:

13. An application management method, the method comprising:

presenting an application deployment interface to a user;

receiving deployment information of a target application configured by the user through the application deployment interface, wherein the target application is an application requested to be deployed by the user, the deployment information comprises a target deployment environment, and the target deployment environment comprises one or more of public cloud, private cloud, mixed cloud or edge environment;

and sending a first programming file to the target deployment environment, wherein the first programming file records programming nodes on which the target application operates and the dependency relations among the programming nodes.

14. The method of claim 13, wherein the deployment information further comprises first specification description information of the target application, the first specification description information comprising a first specification of the target application;

the sending the first orchestration file to the target deployment environment comprises:

determining a first arrangement file matched with the first specification from arrangement files of the target application according to the first specification description information, wherein the first arrangement file records arrangement nodes on which the target application runs under the first specification and the dependency relations among the arrangement nodes;

And sending the first orchestration file to the target deployment environment.

15. The method of claim 13, wherein the sending the first orchestration file to the target deployment environment comprises:

determining a first arrangement file from arrangement files of the target application according to the target deployment environment, wherein the first arrangement file records arrangement nodes on which the target application runs under a first specification and the dependency relations among the arrangement nodes, and the applicable environment of the first specification comprises the target deployment environment;

and sending the first orchestration file to the target deployment environment.

16. The method according to claim 14 or 15, characterized in that the method further comprises:

17. The method of claim 14, wherein the first specification description information includes a version number of a first version of the first specification; the first orchestration file records orchestration nodes on which the target application runs under a first version of the first specification and dependency relations among the orchestration nodes;

the method further comprises the steps of:

18. The method of any of claims 13 to 17, wherein prior to presenting the application deployment interface to the user, the method further comprises:

auditing the application;

the method further comprises the steps of:

19. An application management method, the method comprising:

receiving a first orchestration file of a target application;

analyzing the first layout file to obtain a layout node on which the target application depends and a dependency relationship between the layout nodes, wherein the target layout node is a standardized service node;

and sequentially deploying the arrangement nodes on which the target application operates according to the first arrangement file.

20. The method of claim 19, wherein the first orchestration file records orchestration nodes on which the target application is running under a first specification and dependencies between the orchestration nodes, the method further comprising:

and upgrading the target application to the second specification according to at least one of the node change information and the dependency change information.

21. The method of claim 19, wherein the first orchestration file records orchestration nodes and dependencies between the orchestration nodes on which the target application runs under a first version of a first specification, the method further comprising:

And upgrading the target application from the first version of the first specification to the second version of the first specification according to the third programming file.

22. The method of any one of claims 19 to 21, wherein prior to receiving the first orchestration file for the target application, the method further comprises:

initiating a request for establishing connection to an application market, and establishing connection with the application market;

the receiving the first orchestration file of the target application includes:

23. An application management platform, the platform comprising:

24. The platform of claim 23, wherein the first orchestration node is any one of:

25. The platform of claim 24, further comprising:

26. The platform of claim 25, wherein the application management platform interfaces with a heterogeneous environment comprising one or more of a public cloud, a private cloud, a hybrid cloud, or an edge cloud;

27. The platform of any one of claims 23 to 26, further comprising:

28. The platform of any one of claims 23 to 27, wherein the interaction module is further configured to:

29. An application marketplace, wherein the application marketplace includes:

the interaction module is further configured to send, to the target deployment environment, a first orchestration file determined by the management module, where the first orchestration file records orchestration nodes on which the target application runs and a dependency relationship between the orchestration nodes.

30. The application marketplace of claim 29, wherein the deployment information further includes first specification description information of the target application, the first specification description information including a first specification of the target application;

the management module is specifically configured to:

31. The application marketplace according to claim 30, wherein the interaction module is further configured to:

the management module is further configured to:

the interaction module is further configured to:

32. An application management platform, the platform comprising:

33. The platform of claim 32, wherein the first orchestration file records orchestration nodes on which the target application runs under a first specification and dependencies between the orchestration nodes;

the interaction module is further configured to:

the orchestration engine is further configured to:

the platform further comprises:

34. A cluster of computing devices, characterized in that it comprises at least one computing device comprising at least one processor and at least one memory, the at least one memory having stored therein computer-readable instructions that are executed by the at least one processor to cause the cluster of computing devices to perform the method of any of claims 1 to 22.

35. A computer-readable storage medium comprising computer-readable instructions that, when run on a computing device or cluster of computing devices, cause the computing device or cluster of computing devices to perform the method of any of claims 1-22.

36. A computer program product comprising computer readable instructions which, when run on a computing device or cluster of computing devices, cause the computing device or cluster of computing devices to perform the method of any of claims 1 to 22.