APPLICATION UPGRADE METHOD AND APPARATUS

• US 20150347123A1
• Filed: 08/07/2015
• Published: 12/03/2015
• Est. Priority Date: 08/13/2013
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: ZHU, Jie, ZHANG, Chuxiong, ZHANG, Yi
• Granted Patent: US 9,696,984 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Embodiments of the present invention provide an application upgrade method and an apparatus. The application upgrade method includes: receiving an application deployment request; determining a deployment package of a to-be-deployed application; determining that a version of a first platform node is below a version requirement of a node template of the to-be-deployment application for a first platform node template; acquiring a first platform node upgrade package that meets the version requirement of the node template of the to-be-deployed application for the first platform node template; upgrading the first platform node indicated by an identifier of the first platform node by using the first platform node upgrade package; determining an identifier of a to-be-upgraded application node; and upgrading the application node indicated by the identifier of the to-be-upgraded application node by using the deployment package of the to-be-deployed application.

Claims

1. An application upgrade method, comprising:

receiving an application deployment request, wherein the application deployment request comprises a deployment package of a to-be-deployed application, wherein the deployment package of the to-be-deployed application describes a node template of the to-be-deployed application, an identifier of a deployed application, an identifier of a node template of the deployed application, an identifier of a first platform node template, a version requirement of the node template of the to-be-deployed application for the first platform node template, and an upgrade identifier indicating that the node template of the to-be-deployed application is used to upgrade the node template of the deployed application indicated by the identifier of the node template of the deployed application;

determining, according to the upgrade identifier, that the deployment package of the to-be-deployed application is an upgrade package of the deployed application indicated by the identifier of the deployed application;

acquiring, according to the identifier of the deployed application, an identifier that is of a first platform node and corresponding to the identifier of the first platform node template, and acquiring a version of the first platform node indicated by the identifier of the first platform node;

determining, according to the version of the first platform node, that the version of the first platform node is below the version requirement of the node template of the to-be-deployed application for the first platform node template;

acquiring, according to the version requirement of the node template of the to-be-deployed application for the first platform node template, a first platform node upgrade package that meets the version requirement of the node template of the to-be-deployed application for the first platform node template;

upgrading the first platform node indicated by the identifier of the first platform node by using the first platform node upgrade package;

determining an identifier of a to-be-upgraded application node; and

upgrading the application node indicated by the identifier of the to-be-upgraded application node by using the deployment package of the to-be-deployed application.

2. The method according to claim 1, wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and the upgrade identifier is carried in the relationship template;

or

the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and the upgrade identifier is carried in the node type implementation.

3. The method according to claim 1 wherein the determining an identifier of a to-be-upgraded application node is specifically:

determining identifiers that are of all application nodes and corresponding to the identifier of the node template of the deployed application, as the identifier of the to-be-upgraded application node;

or

when the deployment package of the to-be-deployed application further comprises an identifier that is of at least one deployed application node and corresponding to the identifier of the node template of the deployed application, the determining an identifier of a to-be-upgraded application node is specifically;

determining the identifier that is of the at least one deployed application node, corresponding to the identifier of the node template of the deployed application, and comprised in the application deployment package, as the identifier of the to-be-upgraded application node.

4. The method according to claim 1, wherein before the upgrading the first platform node indicated by the identifier of the first platform node, the method further comprises:

acquiring, according to the identifier of the deployed application, a stored description file of a deployment package of the deployed application;

determining, according to the acquired description file of the deployment package of the deployed application, that the description file of the deployment package of the deployed application describes a second platform node template that uses the first platform node template as a source node template;

acquiring a version requirement of an upgraded first platform node for a second platform node, and a version of the second platform node; and

determining that the version of the second platform node is below the version requirement of the upgraded first platform node for the second platform node; and

before the upgrading the first platform node by using the first platform node upgrade package, the method further comprises;

acquiring, according to the version requirement of the upgraded first platform node for the second platform node, a second platform node upgrade package that meets the version requirement of the upgraded first platform node for the second platform node; and

upgrading the second platform node according to the second platform node upgrade package.

5. An application upgrade method, comprising:

generating a deployment package of a to-be-deployed application, wherein the deployment package of the to-be-deployed application describes a node template of the to-be-deployed application, an identifier of a deployed application, an identifier of a first platform node template, an identifier of a node template of the deployed application, a version requirement of the node template of the to-be-deployed application for the first platform node template, and an upgrade identifier indicating that the node template of the to-be-deployed application is used to upgrade the node template of the deployed application indicated by the identifier of the node template of the deployed application;

generating an application deployment request, wherein the application deployment request comprises the deployment package of the to-be-deployed application; and

sending the application deployment request to an application deployment server.

6. The method according to claim 5, wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and the upgrade identifier is carried in the relationship template;

or

the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and the upgrade identifier is carried in the node type implementation.

7. The method according to claim 5, wherein the deployment package of the to-be-deployed application further comprises an identifier that is of at least one deployed application node and corresponding to the identifier of the node template of the deployed application.

8. The method according to claim 5, wherein before the generating a deployment package of a to-be-deployed application, the method further comprises:

determining, according to a description file of a deployment package of the deployed application, the first platform node template of the deployed application indicated by the identifier of the deployed application, wherein the first platform node template uses the node template of the deployed application as a source node template.

9. An application deployment server, comprising:

a receiver, configured to receive an application deployment request, wherein the application deployment request comprises a deployment package of a to-be-deployed application, wherein the deployment package of the to-be-deployed application describes a node template of the to-be-deployed application, an identifier of a deployed application, an identifier of a node template of the deployed application, an identifier of a first platform node template, a version requirement of the node template of the to-be-deployed application for the first platform node template, and an upgrade identifier indicating that the node template of the to-be-deployed application is used to upgrade the node template of the deployed application indicated by the identifier of the node template of the deployed application; and

send the deployment package of the to-be-deployed application to a processor; and

the processor, configured to;

receive the deployment package of the to-be-deployed application sent by the receiver, and determine, according to the upgrade identifier, that the deployment package of the to-be-deployed application is an upgrade package of the deployed application indicated by the identifier of the deployed application;

acquire, according to the identifier of the deployed application, an identifier that is of a first platform node and corresponding to the identifier of the first platform node template, and acquire a version of the first platform node indicated by the identifier of the first platform node;

determine, according to the version of the first platform node, that the version of the first platform node is below the version requirement of the node template of the to-be-deployed application for the first platform node template;

acquire, according to the version requirement of the node template of to-be-deployed application for the first platform node template, a first platform node upgrade package that meets the version requirement of the node template of the to-be-deployed application for the first platform node template;

upgrade the first platform node indicated by the identifier of the first platform node template by using the first platform node upgrade package;

determine an identifier of a to-be-upgraded application node; and

upgrade the application node indicated by the identifier of the to-be-upgraded application node by using the deployment package of the to-be-deployed application.

10. The application deployment server according to claim 9, wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and the upgrade identifier is carried in the relationship template;

or

the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and the upgrade identifier is carried in the node type implementation.

11. The application deployment server according to claim 10 wherein the processor is specifically configured to determine identifiers that are of all application nodes and corresponding to the identifier of the node template of the deployed application, as the identifier of the to-be-upgraded application node;

or

when the deployment package of the to-be-deployed application further comprises an identifier that is of at least one deployed application node and corresponding to the identifier of the node template of the deployed application, the determining an identifier of a to-be-upgraded application node is specifically;

determining the identifier that is of the at least one deployed application node, corresponding to the identifier of the node template of the deployed application, and comprised in the application deployment package, as the identifier of the to-be-upgraded application node.

12. The application deployment server according to claim 9, wherein the processor is further configured to:

acquire, according to the identifier of the deployed application, a stored description file of a deployment package of the deployed application;

determine, according to the acquired description file of the deployment package of the deployed application, that the description file of the deployment package of the deployed application describes a second platform node template that uses the first platform node template as a source node template;

acquire a version requirement of an upgraded first platform node for a second platform node, and a version of the second platform node;

determine that the version of the second platform node is below the version requirement of the upgraded first platform node for the second platform node;

acquire, according to the version requirement of the upgraded first platform node for the second platform node, a second platform node upgrade package that meets the version requirement of the upgraded first platform node for the second platform node; and

upgrade the second platform node according to the second platform node upgrade package.

13. A user equipment, comprising:

a processor, configured to;

generate a deployment package of a to-be-deployed application, wherein the deployment package of the to-be-deployed application describes a node template of the to-be-deployed application, an identifier of a deployed application, an identifier of a first platform node template, an identifier of a node template of the deployed application, a version requirement of the node template of the to-be-deployed application for the first platform node template, and an upgrade identifier indicating that the node template of the to-be-deployed application is used to upgrade the node template of the deployed application indicated by the identifier of the node template of the deployed application;

generate an application deployment request, wherein the application deployment request comprises the deployment package of the to-be-deployed application; and

send the application deployment request to a transmitter; and

the transmitter, configured to receive the application deployment request sent by the processor, and send the application deployment request to an application deployment server.

14. The user equipment according to claim 13, wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and the upgrade identifier is carried in the relationship template;

or

the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and the upgrade identifier is carried in the node type implementation.

15. The user equipment according to claim 13, wherein the deployment package of the to-be-deployed application further comprises an identifier that is of at least one deployed application node and corresponding to the identifier of the node template of the deployed application.

16. The user equipment according to claim 13, wherein the processor is further configured to:

determine, according to a description file of a deployment package of the deployed application, the first platform node template of the deployed application indicated by the identifier of the deployed application, wherein the first platform node template uses the node template of the deployed application as a source node template.