WO2015021604A1 - 一种应用升级方法、装置 - Google Patents
一种应用升级方法、装置 Download PDFInfo
- Publication number
- WO2015021604A1 WO2015021604A1 PCT/CN2013/081410 CN2013081410W WO2015021604A1 WO 2015021604 A1 WO2015021604 A1 WO 2015021604A1 CN 2013081410 W CN2013081410 W CN 2013081410W WO 2015021604 A1 WO2015021604 A1 WO 2015021604A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- deployed
- node
- template
- platform
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 76
- 101100148256 Actinobacillus pleuropneumoniae apxIB gene Proteins 0.000 description 40
- 101150008617 appB gene Proteins 0.000 description 40
- 238000010586 diagram Methods 0.000 description 13
- 101100148259 Actinobacillus pleuropneumoniae apxIIA gene Proteins 0.000 description 10
- 101150050411 appA gene Proteins 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 230000008676 import Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the present invention relates to the field of cloud computing, and in particular, to an application upgrade method and apparatus. Background technique
- the core idea of cloud computing is to manage and schedule a large number of computing resources connected by network.
- the computing resource pool provides resources and services to users according to users' needs.
- the network that provides such computing resources is called cloud.
- the cloud platform is a platform that provides cloud-based services to application developers.
- PaaS Platinum as a Service, Service Platform
- the generalized cloud computing refers to the need for developers to obtain on demand through the network in an easy-to-expand manner.
- Service The PaaS provides a customized middleware platform as a service to users. The essence is to serve the Internet resources as a programmable interface, providing third-party developers with commercially valuable resources and service platforms.
- the middleware platform also referred to as a platform node, is a general service with standard program interfaces and protocols, and is usually located between hardware and applications or between an operating system and an application.
- PaaS C SP Cloud Service Prov logo, cloud service provider
- C SP can design, develop and optimize platform nodes, while application developers only need to be on the platform. Above the node is focused on the development of application nodes, which brings great convenience to development.
- PaaS C SP currently only provides a fixed version of the platform node to application developers, maintaining the version of the platform node for all applications. If the application developer needs to upgrade an application node, the upgraded application node requires a version of the platform node. If the version of the platform node does not meet the requirements of the upgraded application node, the application node update fails and the application cannot run normally.
- Embodiments of the present invention provide a method and apparatus for applying an upgrade to ensure that an upgraded application can operate normally.
- the first aspect of the present invention provides an application upgrade method, including: receiving an application deployment request, where the application deployment request includes an application deployment to be deployed.
- the application deployment package to be deployed describes the application node template to be deployed, the identifier of the deployed application, the identifier of the deployed application node template, the identifier of the first platform node template, and the application node template to be deployed. a platform section, a version requirement of the template, and an upgrade identifier of the deployed application node template upgrade indicated by the identifier of the deployed application node template to be deployed by the application node template to be deployed;
- the version of the platform node template is required to obtain a first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template;
- the application node indicated by the identifier of the application node to be upgraded is upgraded by using the application deployment package to be deployed.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the determining the identifier of the application node to be upgraded is specifically: determining that the identifier of all the application nodes corresponding to the identifier of the deployed application node template is an identifier of the application node to be upgraded; or
- an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, the identifier of the application node that is determined to be upgraded is specifically:
- the method further includes: obtaining, according to the deployed application identifier, a description file of the stored deployed application deployment package;
- the method further includes: before the upgrading the first platform node according to the first platform node upgrade package, the method further includes:
- a second aspect of the embodiments of the present invention provides an application upgrade method, including:
- An application deployment package to be deployed is generated, and the application deployment package to be deployed describes the to-be-deployed application deployment package.
- the application node template of the deployment the identifier of the deployed application, the identifier of the first platform node template, the identifier of the deployed application node template, the version requirement of the application node template to be deployed, the version of the first platform node template, and the The deployed application node template for the deployed application section indicated by the identifier of the deployed application node template, and the upgrade identifier of the template upgrade;
- the application deployment request is sent to an application deployment server.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the application deployment package to be deployed further includes: at least one deployed corresponding to the identifier of the deployed application node template The ID of the application node.
- the method further includes: deploying the package according to the deployed application And the first platform node template of the deployed application indicated by the deployed application identifier, where the first platform node template uses the deployed application node template as a source node template.
- a third aspect of the embodiments of the present invention provides an application deployment server, including: a receiving module, configured to receive an application deployment request, where the application deployment request includes an application deployment package to be deployed; and the application deployment package description to be deployed
- the application node template to be deployed the identifier of the deployed application, the identifier of the deployed application node template, the identifier of the first platform node template, the version requirement of the application node template to be deployed to the first platform node template, and the The application node template to be deployed is used to upgrade the deployed application node template upgrade indicated by the identifier of the deployed application node template. Identifying, and sending the application deployment package of the application to be deployed to the determining module and the upgrading module;
- a determining module configured to receive an application deployment package of the application to be deployed sent by the receiving module, and determine, according to the upgrade identifier, that the application deployment package to be deployed is a deployed application indicated by the identifier of the deployed application And an identifier of the first platform node corresponding to the identifier of the first platform node template, and a first platform for obtaining the identifier indication of the first platform node, according to the deployed application identifier a version of the node; and determining, according to the version of the first platform node, that the version of the first platform node is lower than a version requirement of the application node template to be deployed to the first platform node template;
- the first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template, and sends the first a platform node upgrade package to the upgrade module;
- the upgrade module is configured to receive the first platform node upgrade package sent by the determining module, and use the first platform node upgrade package to upgrade the first platform node indicated by the identifier of the first platform node ;
- the determining module is further configured to determine an identifier of the application node to be upgraded according to the identifier of the deployed application node template, and send the identifier of the application node to be upgraded to the upgrade module;
- the upgrade module is further configured to receive an application deployment package of the to-be-deployed application sent by the receiving module, and receive an identifier of the application node to be upgrade sent by the determining module, and use the to-be-used
- the deployed application deployment package upgrades the application node indicated by the identifier of the application node to be upgraded.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the determining module is specifically configured to: determine that the identifiers of all the application nodes corresponding to the identifiers of the deployed application node templates are to be The identity of the upgraded application node; or
- an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, the identifier of the application node that is determined to be upgraded is specifically:
- the determining module is further configured to:
- the upgrade module is also used to:
- a fourth aspect of the embodiments of the present invention provides a user equipment, including: a generating module, configured to generate an application deployment package to be deployed, where the application deployment package to be deployed describes an application node template to be deployed, and deployed Application logo, first The identifier of the platform node template, the identifier of the deployed application node template, the version requirement of the application node template to be deployed to the first platform node template, and the application node template to be deployed are used for the deployed application node.
- the upgrade ID of the deployed application node template upgrade indicated by the identifier of the template;
- the generating module is further configured to generate an application deployment request, and send the application deployment request to the sending module, where the application deployment request includes the application deployment package to be deployed;
- the sending module is configured to receive the application deployment request sent by the generating module, and send the application deployment request to an application deployment server.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the application deployment package to be deployed further includes: at least one deployed corresponding to the identifier of the deployed application node template The ID of the application node.
- the user equipment further includes: a determining module, configured to deploy a description file of the application according to the deployed application, The first platform node template of the deployed application indicated by the deployed application identifier is determined, and the first platform node template uses the deployed application node template as a source node template.
- a fifth aspect of the embodiments of the present invention provides an application deployment server, including: a receiver, configured to receive an application deployment request, where the application deployment request includes an application deployment package to be deployed; and the application deployment package description to be deployed
- the application node template to be deployed, the identifier of the deployed application, the identifier of the deployed application node template, the identifier of the first platform node template, the version requirement of the application node template to be deployed to the first platform node template, and the The application node template to be deployed is used to upgrade the deployed application node template upgrade indicated by the identifier of the deployed application node template. And sending the application deployment package to be deployed to the processor;
- the processor is configured to:
- the receiver And receiving, by the receiver, the application deployment package to be deployed, and determining, according to the upgrade identifier, that the application deployment package to be deployed is an upgrade package of the deployed application indicated by the identifier of the deployed application;
- the version of the platform node template is required to obtain a first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template;
- the application node indicated by the identifier of the application node to be upgraded is upgraded by using the application deployment package to be deployed.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the processor is specifically configured to: determine that the identifiers of all the application nodes corresponding to the identifiers of the deployed application node templates are to be upgraded The identity of the application node; or
- the application deployment package to be deployed further includes: an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, the identifier of the application node that is determined to be upgraded is specifically: Determining, by the application deployment package, the at least one deployed application section corresponding to the identifier of the deployed application node template, where the identifier of the application node is an identifier of the application node to be upgraded.
- the processor is further configured to:
- a sixth aspect of the embodiments of the present invention provides a user equipment, including: a processor, configured to generate an application deployment package to be deployed, where the application deployment package to be deployed describes an application node template to be deployed, and deployed
- the identifier of the application, the identifier of the first platform node template, the identifier of the deployed application node template, the version requirement of the application node template to be deployed to the first platform node template, and the application node template to be deployed are used for the An upgrade identifier of the deployed application node template upgrade indicated by the identifier of the deployed application node template;
- the transmitter is configured to receive the application deployment request sent by a processor, and send the application deployment request to an application deployment server.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the application deployment package to be deployed further includes: at least one deployed application corresponding to the identifier of the deployed application node template The identity of the node.
- the processor is further configured to: determine, according to the description file of the deployed application deployment package, The first platform node template of the deployed application indicated by the application identifier is deployed, and the first platform node template uses the deployed application node template as a source node template.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template, the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, so as to ensure that the upgraded application can run normally.
- FIG. 1A is a schematic structural diagram of an application template described in an application deployment description file on which an application deployment method is provided according to an embodiment of the present invention
- FIG. 1B is a schematic structural diagram of a plan corresponding to FIG. 1A according to an embodiment of the present invention.
- FIG. 2 is a schematic flowchart of an application upgrade method according to an embodiment of the present invention
- FIG. 3 is a schematic flowchart of an application upgrade method according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of an application upgrade method according to an embodiment of the present invention
- the schematic diagram of the upgrade application node app obtained by the application deployment server according to the description of the application deployment package A and the application deployment package B in the embodiment of the present invention
- FIG. 6 is an application deployment server upgrade according to an embodiment of the present invention. Schematic diagram of the application node;
- FIG. 7 is a schematic diagram of an application deployment package to be deployed according to an embodiment of the present invention
- FIG. 8 is a schematic structural diagram of an application deployment server according to an embodiment of the present invention
- FIG. 9 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of another user equipment according to an embodiment of the present disclosure; Schematic diagram of the server;
- FIG. 12 is a schematic structural diagram of still another user equipment according to an embodiment of the present invention. detailed description
- the embodiment of the invention provides an application upgrade method, which can be applied to the TOSCA standard and can be applied to other aspects, and is not limited to the TOSCA standard.
- the information required for deploying an application is described in an application deployment package named Cloud Service Archive (CSAR) in the application deployment server.
- the application deployment package contains at least one application deployment description file with the suffix ste.
- the application deployment description file of the ste can describe the deployment information of the application in the XML language.
- the root element of the application deployment description file of the ste is the application template Service. Template. That is to say, in the embodiment of the present invention, the application template ServiceTemplate can be used to completely describe the information of the application to be deployed.
- FIG. 1A is a schematic structural diagram of an application template described in an application deployment description file based on an application upgrade method according to an embodiment of the present invention.
- the embodiment of the present invention uses a TopologyTemplate to describe an application topology.
- the application topology includes node templates for four nodes: al, a2, a3, and a4, that is, each node template represents a node deployed by the application (that is, if the application is deployed multiple times, each node The template corresponds to a plurality of such nodes), and the identifier of each node template is given on the application topology.
- the type of each NodeTemplate is defined by the NodeType (the type attribute of the NodeTemplate describes the NodeType corresponding to the NodeTemplate ).
- the NodeType defines the properties of the node (defined by Properties), the interface of the node (defined by the interface collection Interfaces), and the NodeTemplate is an instance of NodeType.
- Each NodeType corresponds to a Node Type Implementation (NTI), which describes the deployment artifacts of the node corresponding to the NodeType and the method artifacts of all methods contained in the Interface in the NodeType.
- NTI Node Type Implementation
- Each side of the connection node in the TopologyTemplate is a RelationshipTemplate, and the relationship template corresponds to the application node template.
- Each application deployment package also includes a plan, as shown in Figure IB, Figure 1 B is A schematic structural diagram of a plan corresponding to FIG. 1A of the embodiment of the present invention.
- the plan is an executable workflow, which is actually a workflow composed of a plurality of referenced methods. Executing the workflow is actually the method artifact corresponding to each method that constitutes the workflow.
- the application deployment server runs the method products corresponding to the methods corresponding to the tasks one by one according to the definition of the plan. See, for example, Figure 1B, which includes tasks cl, c2, and c3.
- the execution order is to execute the task cl first, then the task c2, and then the task c3; and the cl, c2 and c3 are the methods corresponding to the interface in the NodeType.
- each ServiceTemplate includes a boundary (defined by BoundaryDefinitions), and some components defined in the ServiceTemplate are presented to the user within the BoundaryDefinitions; the components are the above-mentioned NodeTemplate, deployment artifacts, method artifacts, and the like.
- an application deployment package contains information required to deploy the application, such as: application deployment description files, plans, deployed products of nodes, and method products of each method.
- the application deployment description file describes the complete topology of the application, the information about the deployed product of the node in the topology, the method of the node template in the topology, and the method product information step.
- the topology template describes each node template, and the logical relationship between the node templates.
- the node template on the topology may include: an application node template and a platform node template.
- the application node template refers to a node of an application to be deployed that is maintained and used by the user equipment
- the platform node template refers to a node of the application to be deployed that is run and maintained by the server.
- FIG. 2 is a schematic flowchart of an application upgrade method according to an embodiment of the present invention.
- the execution body of the method in this embodiment is an application deployment server. As shown in FIG. 2, the method includes:
- Step 201 Receive an application deployment request, where the application deployment request includes an application deployment package to be deployed.
- the application deployment package to be deployed describes the application node template to be deployed, the deployed application identifier, the identifier of the deployed application node template, the identifier of the first platform node template, and the application node template to be deployed.
- Platform node module The version requirement of the board, and the application node template to be deployed is used to upgrade the upgraded version of the deployed application node template indicated by the identifier of the deployed application node template.
- the application node template to be deployed the deployed application identifier, the identifier of the first platform node template, the identifier of the deployed application node template, the version requirement of the application node template to be deployed to the first platform node template, and
- the upgrade identifier of the deployed application node template upgrade indicated by the identifier of the deployed application node template to be deployed is described in an application description file.
- the platform node template indicated by the identifier of the first platform node template and the application node template indicated by the deployed application node template identifier are described in a description file in the application deployment package indicated by the deployed application identifier.
- the upgrade identifier of the deployed application node template that is to be deployed by the application node template to be deployed may be represented by Patch For.
- the upgrade identifier refers to an upgrade identifier of the deployed application node template that is to be deployed by the application node template to be deployed to the deployed application node template.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template, or the application deployment package to be deployed further includes an application to be deployed.
- the node type corresponding to the node template is executed, and the upgrade identifier is carried in the node type execution.
- a deployed application includes multiple nodes, and the node is equivalent to a module.
- the charging application includes a database module and a management module.
- the user device When the application needs to be deployed, the user device generates an application deployment package to be deployed and sends it to the application deployment server through the application deployment request.
- the application deployment server After receiving the application deployment package, the application deployment server deploys the application deployment description file, deployment artifacts, method products, and planned application deployment according to the application deployment package.
- application deployments include initial deployment, updates, or upgrades. It is assumed in the embodiment of the present invention that the application deployment package to be deployed is an upgrade package for upgrading the deployed application.
- the application deployment server will apply each time it receives an application deployment package. All application description information in the deployment package is logged to the database.
- Step 202 Determine, according to the upgrade identifier, that the application deployment package to be deployed is an upgrade package of the deployed application indicated by the identifier of the deployed application.
- the application deployment server performs the upgrade according to the upgrade identifier that is carried in the relationship template that describes the application node template to be deployed, or according to the node type that is carried in the application node template to be deployed.
- the identifier determines that the application deployment package to be deployed is an upgrade package for the deployed application.
- Step 203 Obtain an identifier of the first platform node corresponding to the identifier of the first platform node template, and obtain a version of the first platform node indicated by the identifier of the first platform node, according to the deployed application identifier.
- the application deployment server stores the version or capability of each node of each deployed application. And applying, by the application deployment server, the version of the first platform node corresponding to the identifier of the first platform node template from the version information of each platform node of the stored deployed application according to the deployed application identifier. And determining, according to the version requirement of the first platform node template and the obtained version of the first platform node, that the version of the first platform node is lower than the application to be deployed. The version requirement of the node template for the first platform node template.
- the version of the first platform node is lower than the version requirement of the application node template to be deployed to the first platform node template, that is, the version number of the version of the first platform node is smaller than the application node template pair to be deployed.
- the version number of the version requirement indication of a platform node template is lower than the version requirement of the application node template to be deployed to the first platform node template, that is, the version number of the version of the first platform node is smaller than the application node template pair to be deployed.
- Step 204 Determine, according to the first platform node version, that the version of the first platform node is lower than the version requirement of the application node template to be deployed to the first platform node template.
- Step 205 Acquire, according to the version requirement of the application node template to be deployed, the first platform node upgrade package that meets the version requirement of the application node template to be deployed on the first platform node template.
- the application deployment server obtains the application node template that meets the to-be-deployed according to the version requirement of the first platform node template of the application node template to be deployed.
- the first platform node upgrade package for the version of the first platform node template.
- the application deployment package to be deployed may not include the identifier of the deployed application node; when the application deployment package does not include the identifier of the deployed application node, the application deployment server may be configured according to the identifier of the deployed application. Acquiring an identifier of all the first platform nodes corresponding to the identifier of the first platform node template, and upgrading, by using the first platform node upgrade package, the first platform node indicated by the identifier of each of the first platform nodes.
- Step 207 Determine an identifier of an application node to be upgraded.
- the application deployment server may determine that the identifiers of all the application nodes corresponding to the identifiers of the deployed application node templates are the identifiers of the application nodes to be upgraded.
- the application deployment package to be deployed further includes: an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, determining the identifier of the application node to be upgraded And determining, by the application deployment package, an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template as an identifier of an application node to be upgraded.
- Step 208 Upgrade the application node indicated by the identifier of the application node to be upgraded by using the application deployment package to be deployed.
- the application deployment server may use the application deployment package to be deployed, and upgrade the The application node indicated by the identity of the deployed application node.
- the application node that is used to upgrade the identifier of the application node to be upgraded is: obtaining an identifier of all the deployed application nodes corresponding to the identifier of the deployed application node template;
- Application deployment package upgrades each An application node indicated by the identity of the deployed application node.
- the plan is an upgrade plan, and the corresponding application node can be upgraded according to the upgrade plan.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, so as to ensure that the upgraded application can run normally.
- the description file of the stored deployed application deployment package is obtained according to the deployed application identifier; and the description file of the deployed application deployment package is determined according to the obtained description file of the deployed application deployment package.
- the second platform node template that uses the first platform node template as a source node template is obtained; the version requirement of the upgraded first platform node to the second platform node and the second platform node version are obtained; determining the second platform node
- the method is further lower than the version of the first platform node that is upgraded by the first platform node to the second platform node, and the method further includes: according to the first platform node upgrade package And obtaining, by the upgraded first platform node, the version of the second platform node, the second platform node upgrade package that meets the upgraded first platform node to the version of the second platform node; according to the second platform node Upgrade the package and upgrade the second platform node.
- the obtaining the version of the second platform node is specifically: obtaining the identifier of the second platform node according to the identifier of the second platform node template and the identifier of the first platform node, and the identifier of the second platform node and the second
- the identifier of the platform node template corresponds to the same, and the deployment number is the same as the number corresponding to the identifier of the first platform node.
- the application deployment server describes, in the description file of the deployed application deployment package, a second platform that uses the first platform node template as a source node template. After the node template, the version requirement of the upgraded first platform node to the second platform node and the version of the second platform node are obtained.
- the embodiment of the invention provides an application upgrade method, which can be performed by a user equipment. As shown in Figure 3, the method includes:
- Step 30 Generate an application deployment package to be deployed, where the application deployment package to be deployed describes the application node template to be deployed, the identifier of the first platform node template, the identifier of the deployed application node template, and the application to be deployed.
- the version of the first platform node template is required by the node template, and the application node template to be deployed is used to upgrade the deployed application node template indicated by the identifier of the deployed application node template.
- the application deployment package to be deployed further includes a relationship template that describes the application to be deployed, a template, and the upgrade identifier is carried in a relationship template that describes the application node template to be deployed; or
- the deployed application deployment package is further executed by the node type corresponding to the application node template to be deployed; the upgrade identifier is carried in the execution of the node type, and the upgrade identifier is the application node template to be deployed for the The upgrade ID of the deployed application node template upgrade indicated by the identifier of the deployed application node template.
- Step 302 Generate an application deployment request, where the application deployment request includes the application deployment package to be deployed.
- Step 303 Send the application deployment request to an application deployment server.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template. Therefore, the application deployment server may determine the first platform node template according to the application node template to be deployed, when the version of the first platform node is lower than the version of the application node template to be deployed. The version requires the first platform node upgrade package. Afterwards, the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package. Making the version of the first platform node after the upgrade meet the waiting The version of the application node template deployed on the first platform node template ensures that the upgraded application runs normally. Specifically, after receiving the application deployment package to be deployed, the application deployment server may perform any action performed by the application deployment server described in FIG. 2 . The actual examples of the present invention will not be described in detail herein.
- the application deployment package to be deployed may further include: an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, so that the application deployment server uses the to-be-deployed The application deployment package upgrades the application node indicated by the identity of the deployed application node.
- the method further includes: determining, according to the profile of the deployed application deployment package, the first platform node template of the deployed application indicated by the deployed application identifier, where the first platform node template is The deployed application node template is used as the source node template.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template, the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, so as to ensure that the upgraded application can run normally.
- An embodiment of the present invention provides an application upgrade method, and the application upgrade method is applied to the TOSCA standard. As shown in FIG. 4, the method includes:
- Step 401 The application deployment server deploys the application deployment package.
- the process of deploying an application deployment package is the same as the prior art.
- the embodiment of the present invention assumes that the application deployment package submitted by the user equipment to the application deployment server is the application deployment package B, and the identifier of the application deployment package B (that is, the identifier of the application) is appB.
- the node template app, the node template apache, and the description file in the application deployment package are described in the description file.
- the node template app is an application node template deployed by the application deployment package B, and the user equipment is responsible for providing resources. That is, in the application deployment package B, the deployment artifacts and method artifacts for the node template app are included.
- the node template apache and the node template j avaModule are platform node templates, and the C SP server is responsible for providing resources and ensuring that the provided resources meet all deployment requirements in the application deployment package. It is assumed that the application deployment server successfully deploys the application according to the application deployment package B, and writes the contents of the two relationship templates into the application information table in the database maintained by the application deployment server, as shown in Table 1. In the embodiment of the present invention, an application appB that has been successfully deployed and run is referred to as a deployed application.
- Step 402 The user equipment generates an application deployment package to be deployed.
- the application deployment package to be deployed is an upgrade package for the deployed application (appB).
- the upgrade package (that is, the application deployment package to be deployed) for the deployed application is the application deployment package A
- the application deployment package A can correspond to the application node template app (that is, the identifier of the deployed application node template).
- Application node upgrade Specifically, after the application deployment server receives the application deployment package appB, the deployment server deploys the application according to appB. Nodes, such as application nodes and platform nodes, are generated for each node template in the appB package, so that each node template corresponds to a node that has been successfully deployed and running.
- the description file of the application deployment package A describes the application node template appPatch to be deployed, and describes the upgrade identifier of the deployed application node template app in the relationship template describing the application node template appPatch to be deployed. Further, the The upgrade ID can also be described in the NTI corresponding to the application node template appPatch to be deployed.
- the user equipment determines, according to the description file of the appB, the application node template app as the source node template in the relationship template describing the application node template app to be deployed, and uses the platform node template as the template Destination platform node template.
- the application node template app is used as the source node template
- the platform node template apache is used as the target node template. Therefore, the user equipment describes the version requirement of the deployed platform node template apache of the application node template appPatch to be deployed in the description file of the application deployment package A.
- the content of the version requirement is determined by the user equipment according to the upgrade content of the application node.
- the platform node template apache is required to support Servlet 3.0, so the platform node apache needs to be upgraded to Tomcat 7.0.
- the requirements of this version indicate that after the application node corresponding to the application node template app is upgraded by appA, the platform node corresponding to the platform node template apache can support Servlet 3.0 (that is, the platform node needs to be upgraded to Tomcat 7.0) to ensure the upgraded application.
- the application node corresponding to the node template app can run normally.
- the user device obtains the description file of the appB by: obtaining the description file of the appB from the file stored by itself, or obtaining the description file of the appB by sending a request to the application deployment server.
- the application deployment package A also provides a deployment artifact and a method artifact of the application node appPatch, and the method artifact is a patchApp.
- the application node template appPatch to be deployed is referred to as the first platform node template in the version requirement of the deployed platform node template
- the first platform node template is Another platform node template in the version requirement of another platform node template is referred to as a second platform node template.
- the version requirement may be a version requirement
- the version requirement may be a specific version number or a certain capability of a version.
- FIG. 5 is a diagram showing an application of the upgrade application node app obtained by the application deployment server according to the description of the application deployment package A and the application deployment package B in the embodiment of the present invention. Intention.
- the application node template appPacth described in the application deployment package A is an upgrade node of the application node template app described in the package B for the deployed application.
- the identifier of the relationship between the two node templates is used to describe the relationship between the two node templates (for example, the upgrade identifier), and the upgrade identifier may be described by other fields.
- Application Deployment Package A also describes the version requirement of the application node template appPacth for the platform node template apache described in the deployed application deployment package B, represented by Requirement For Apache (Apache as a platform node template).
- PatchForApp refers to the appPatch node template in application deployment package A is an upgrade for the app application node template
- RequirementForApache describes the version requirement of the application node template appPatch for the platform node template apache. Since application deployment package B is a deployment package for an already deployed application, and appA is an upgrade for the application node template app.
- ⁇ Deployed product type is Patch
- the application node template appPatch is defined in the topology template TopologyTemplate with the node template NodeTemplate element, and the version requirement requirementOfApp and the deployment product DaOfAppPatch are specified in the node template element.
- the relationship template PatchForAp indicates that the appPatch application node template and the application application node template in the application deployment package B have an upgrade identifier, such as PatchFor.
- the source element indicates the identifier of the source application node template (the identifier of the application node template to be deployed) by the SourceElement
- the target element indicates the identifier of the target application node template (the identifier of the deployed application node template) appB : app.
- the attribute "externalref" indicates that the application node template app is defined in the external application description file, and the external application description file is named appB .tosca by the prefix "appB" and "Import” elements.
- RequirementForApache of the relational template RelationshipTemplate defines the version requirements of the appPatch application node template for Apache in the application deployment package B.
- the source version requirement requiresOfAppPatch is defined by SourceElement
- the target deployment capability appB is defined by TargetElement: cap capability Of A ache.
- the attribute "externalref” indicates that the deployment capability capabilityOfApache is defined in the external application description file
- the prefix "appB” and “Import” elements indicate that the external application description file is appB.tosca.
- the upgrade plan upgrade is also defined in the topology, and its type is Http: ⁇ www. example.com/UpgradePlan.
- the definition of the product patchAp and the definition of the version requirement requireOf AppPatch for the application node template appPatch are given in the NodeType.
- the method product patchApp will be called in the application deployment server execution upgrade plan
- the constraint Constraint field in the version requirement requireOfAppPatch and the attribute constraint type constraintType takes the value http://www.example.com/PropertyConstraints/supportServlet3 It indicates that the application deployment server needs to find out which software version contains the capability of the supportServlet3 in the database according to the above values.
- the description file of the application deployment package A may further include the identifier of the deployed application node, such as app l.
- the identifier of the deployed application node is an identifier of an application node that needs to be upgraded.
- the identifier of the application node template to be upgraded, such as app can also be specified by an upgrade identifier such as apptchFor. If the application deployment package A's description file does not separately indicate the identity of the deployed application node, only the identity of the deployed application node template, such as app, is indicated in the upgrade ID.
- the application deployment server upgrades all the application nodes corresponding to the identified app of the deployed application node template when the application is upgraded. For example, appB is first deployed in Nanjing and then deployed in Shanghai.
- the application nodes of the deployed application node template are: Application node app l of Nanjing and app2 app2 of Shanghai.
- a number will be generated. For example, when appB is deployed in Nanjing, the number 1 is generated, indicating that app l is generated by the first deployment of appB.
- the number 2 is generated, indicating that app2 is the second deployment of appB. Generated, this number can be used to determine which nodes are generated by the same deployment.
- the plan in the deployment package appA can be as follows:
- invokePlan (appInstance identifier, stopplan identifier);
- patchApp (appInstance identifier);
- invokePlan (appInstance identifier, startPlan identifier);
- the input parameters are first defined, where the input parameter "applnstance ID" indicates that the identity of the deployed application node is app 1.
- the interface invokePlan is an API provided by the application deployment server to the user device. The user device can access the management plan defined in the application deployment package A by calling the API.
- the API has two parameters, the first parameter is the identity of the deployed application node, and the second parameter is the plan ID that needs to be called. The steps of the plan are given in the element plan model PlanModel.
- the upgrade plan is as follows:
- appB : stopplan ⁇ is defined in appB .tosca;
- appB startplan ⁇ is defined in appB .tosca; ⁇ /PlanModel>
- the identifier of the deployed application node is not specified, and the application deployment server obtains the identifier app of the deployed application node template, and finds the corresponding application template identifier app corresponding to the deployed application template identifier app according to the application identifier appB.
- the IDs of all deployed application nodes (such as app 1 and app2) are upgraded for all deployed application nodes corresponding to the identity app of the deployed application node template.
- the user device directly executes the "appB: plan" to invoke the plan defined in appB .tosca to generate the upgrade.
- the above program can make the application deployment server know that the identifier of the deployed application is "appB", and the application node corresponding to the identifier "app" of the deployed application node template needs to be upgraded.
- Step 403 The user equipment generates an application deployment request, where the application deployment request includes the application deployment package A.
- Step 404 The application deployment server receives an application deployment request.
- Step 405 The application deployment server determines that the deployment package is an upgrade package for the deployed application (appB).
- the description file of the application deployment package to be deployed may describe the application node template to be deployed, the identifier of the first platform node template, the identifier of the deployed application node template, and the application node template to be deployed.
- the application deployment server determines, according to the application node template to be deployed, an upgrade identifier of the deployed application node template upgrade indicated by the identifier of the deployed application node template, where the deployment package is an upgrade for the deployed application. package.
- the application deployment server checks the deployment descriptor file appA.tosca of the application deployment package A, and the discovery description file appA.tosca contains the upgrade identifier "PatchFor", and/or the source application node template (ie, the application node template to be deployed) appPatch
- the deployed artifact type is "Patch”.
- Application deployment server can identify The PatchFor relationship type, or the type of deployed artifact is "Patch", so that the application deployment package A can be determined to be an upgrade package. Further, the application deployment server can also check the upgrade plan upgrade to find its type as
- Step 406 The application deployment server upgrades the deployed application node according to the application deployment package to be deployed.
- the steps of the application deployment server to upgrade the deployed application node are as follows:
- Step 4061 Obtain an identifier of the first platform node. Go to step 4062.
- the application deployment server After receiving the application deployment package A to be deployed, the application deployment server searches for the deployment package information table stored in the application deployment server according to the URL of the description file included in the "Import" element in the description file of the application deployment package A.
- the location of the description file is File: ste ste / appB .tosca .
- the description file of the application deployment package B is then obtained by the location File ://ste/appB .tosca of the description file.
- the deployment package information table is shown in Table 2.
- the deployed application node template app As shown in FIG. 7, in the topology description of appB.tosca, the deployed application node template app, platform node template apache and j avaModule are defined, and the relationship between these node templates is defined.
- the definition of the main information in the topology description is given below.
- the deployment capabilityOfApache is described, and the definition of the deployment capability is included in the CapabilityDefinition element of the apache's NodeType capability.
- the platform node template apache also gives a description of the deployment product DaOfApache.
- the deployment capability capabilityOfJM is described, and the definition of the deployment capability is included in the CapabilityDefinition of the NodeType of j avaModul.
- the start and stop management plans are also described in the topology description.
- the deployment capability is a version requirement for a platform node template, such as a capability of a version, or a supported version.
- capabilityOfApache is given in the NodeType of apache.
- constraint Contraint is given in this definition, and its attribute value constraintType indicates that the capability "supports Servlet 2.0".
- the application deployment server may first determine whether the application deployment package appA includes the identifier of the deployed application node "app l ", and the identifier of the deployed application node "app l " is used to indicate the application node that needs to be upgraded. If the deployed application deployment package includes the identifier of the deployed application node, the application deployment server may obtain the deployed application node indicated by the identifier of the deployed application node in the database; and deploy the package according to the application to be deployed. And upgrading an application node indicated by the identifier of the deployed application node. For example, suppose the plan in the application deployment request describes the identity of the deployed application node as "app l ", and the application deployment server looks up the identity of the deployed application node app l in its stored deployment application information table.
- the application deployment server acquires all the identifiers corresponding to the identifiers of the deployed application node templates according to the identifier of the deployed application node template.
- the identifier of the deployed application node is used to upgrade the application node indicated by the identifier of each deployed application node by using the application deployment package to be deployed. Further, before upgrading each application node, the application deployment server determines that the version is lower than the application node template to be deployed. And identifying, by using the first platform node upgrade package, the first platform node indicated by the identifier of the first platform node, by using an identifier of the first platform node that is required for the version of the first platform node template.
- the identifier of one application node template can correspond to the identifiers of multiple application nodes.
- the application deployment server determines to upgrade all application nodes corresponding to the identifiers of the deployed application node templates deployed in the application deployment request.
- the application deployment server determines, according to the identifier of the deployed application node template, that the identifier of the application node to be upgraded is: determining that the identifiers of all the application nodes corresponding to the identifiers of the deployed application node templates are to be upgraded.
- the ID of the application node Therefore, you need to get the identity of all application nodes.
- the application deployment server may search for the identifiers of all the application nodes corresponding to the application node template app according to the app in the deployment application information table, and obtain the identifier of the application node as ⁇ app l , App2 ⁇ .
- the application deployment server upgrades each application node app l and app2 separately.
- the application deployment request may further include the deployed application identifier (as an optional method, the deployed application identifier may be the identifier of the deployed application deployment package or the URL of the application description file or the location of the application description file. ).
- the application deployment server searches for the identifiers of all the application nodes corresponding to the application node template app in the deployment application information table according to the identifier of the application node template.
- the application deployment server is based on the identifier of the deployed application deployment package or the application description file.
- the location of the URL or the application description file, and the identifier of all the application nodes corresponding to the application node template app of the deployed application are found in the stored deployment application information table, and the identifier of the application node is ⁇ app l , app2 ⁇ . Upgrade each application node separately.
- the deployment application information table is shown in Table 3.
- the deployment application information table records the relationship between the identifier of the node, the identifier of the deployed application, and the identifier of the node template.
- the deployment number indicates the application deployment.
- the nodes with the same deployment number are generated in the same deployment.
- the identifier of the node includes an identifier of the application node and an identifier of the platform node.
- Step 4062 Determine whether the version of the first platform node meets the version requirement of the application node template to be deployed in the application deployment package to be deployed on the first platform node template. If no, go to step 4063, and if yes, go to step 4068.
- the application deployment server obtains the identifier Apache1 of the first platform node with the same deployment number 1 from the database according to the identifier of the application node to be upgraded, appl and deployment number 1, according to the identifier of the first platform node template. Obtaining a version of the first platform node according to the identifier Apache1 of the first platform node. Specifically, the application deployment server searches the database according to the identifier of the first platform node Apache1, and obtains the deployment capability of the first platform node Apache1. This embodiment assumes that the current deployment product of the first platform node Apache 1 is Tomcat 6.0. As shown in Table 4, only Servlet 2.0 can be supported, so the version of the first platform node Apachel is Tomcat 6.0.
- the identifier Apache1 of the first platform node having the same deployment number as appl is obtained from Table 3 according to the first platform node template identifier.
- the apachel of the capabilityOfApache can only provide the deployment capability of "supporting Servlet 2.0", that is, the version supported by the platform node indicated by the identifier of the first platform node is Tomcat 6.0.
- the application implementation information table is shown in Table 4.
- the application deployment server obtains the version of the first platform node according to the identifier of the first platform node template, and determines that the version of the first platform node cannot meet the application node template to be deployed to the first platform node template. Version requirements. For example, the application deployment server obtains the first platform nodes Apache 1 and Apache2 according to the identifier of the first platform node template in Table 3, and determines that the version of the first platform node Apache 1 is only supportServlet2 or Tomcat 6.0, but cannot satisfy the application to be deployed. The version of the node template for the first platform node template requires Servlet 3.0 or Tomcat 6.0. Therefore, step 4063 is performed.
- the application deployment server also needs to determine the version of the first platform node Apache2 with the same deployment number as app2.
- the number of the department number is the same as the ID of the first platform node. That is, the deployment number corresponding to the identifier of the acquired first platform node is the same as the deployment number corresponding to the identifier of the application node.
- Apache2 determines that the version of the first platform node Apache2 is Servlet3.0. Therefore, it is determined that the capability of the first platform node satisfies the version requirement of the application node template to be deployed on the first platform node template.
- Step 4063 Obtain a first platform node upgrade package.
- the first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template is obtained according to the version requirement of the application node template to be deployed to the first platform node template.
- the version of the first platform node is obtained according to the identifier of the first platform node (for example, the application deployment server may obtain the version of the platform node from the deployed product name of the platform node), and determine that the application node to be deployed is satisfied.
- the template is applied to the version of the first platform node template, and then the upgrade package corresponding to the determined version of the application node template to be deployed to the first platform node template is obtained.
- the application deployment server obtains the version of Apache l from the Apache l deployment product name to Tomcat 6.0 according to Table 4.
- the version required for Apachel is Tomcat 7.0.
- the application deployment server obtains the upgrade package location from Table 5 that can upgrade Apache l from Tomcat 6.0 to Tomcat 7.0 according to the determined version of Tomcat 7.0.
- the location of the upgrade package is File://appcontainer/apache/update/appE, and the upgrade is obtained from this location.
- Package appE. Table 5 Deploying Product Information Table
- the application node template to be deployed is configured to the first platform node.
- the version requirements of the board can also be the capabilities supported by the version, such as supports ervlet3. The embodiments of the present invention are not described in detail herein.
- Step 4064 Determine that the version of the second platform node is lower than the version requirement of the first platform node template to the second platform node template. Otherwise, step 4067 is directly performed.
- the application deployment server determines, according to the stored description file of the deployed application deployment package, that the profile of the deployed application deployment package has a target node template that uses the first platform node template as a source node template (ie, For the second platform node template). Further, the application deployment server determines, according to the relationship template of the description file, a target node template that uses the first platform node template as a source node template in the relationship template. The embodiment of the present invention uses the first platform node template as a target node template of the source node template as the second platform node template.
- the apache node template is used as the source node template
- the javaModule is used as the target node template. Therefore, the javaModule node template acts as the second platform node template.
- the application deployment server determines that the first platform node Apache will be upgraded to Tomcat 7.0 based on the source node template and the target node matching table of the target node template (see Table 6).
- the corresponding node of the second platform node template j avaModule needs to support JDK 1.6.
- Step 4056 Obtain a second platform node upgrade package. Go to step 4066.
- the second platform node upgrade package is obtained according to the version requirement of the first platform node to the second platform node.
- the upgrade package can upgrade the platform node corresponding to the node template j avaModule to JDK1.6, and the second platform node upgrade package is upgrade package D.
- Step 4066 Upgrade the second platform node according to the second platform node upgrade package. Go to step 4067.
- step 4066 the application deployment server needs to continue to determine whether the profile of the deployed application deployment package has a target node template (ie, a third node template) that uses the second platform node template as a source node template. And repeat steps 4064 and 4065) until the version requirements of any node are met after the upgrade.
- a target node template ie, a third node template
- Step 4067 Upgrade the first platform node according to the first platform node upgrade package. Go to step 4068.
- Step 4068 Upgrade the application node of the deployed application according to the application deployment package to be deployed.
- the application deployment package of the deployed application is also generated by the user equipment. Therefore, upgrading the deployed application actually refers to upgrading the application node corresponding to the deployed application.
- the upgrade process may be upgraded according to the information described in the plan of the application deployment package to be deployed.
- the application deployment package describes the application node template to be deployed, the identifier of the first platform node template, and the deployed.
- the identifier of the application node template, the version requirement of the application node template to be deployed, and the upgrade identifier of the application node template to be deployed and the upgrade of the deployed application node template may be used.
- the application deployment package which upgrades the application node indicated by the identifier of the deployed application node template.
- the platform node upgrade Since the upgrade package of the platform node is maintained by the application deployment server, if the installation fails, unless the application deployment server can respond in time to failure, the platform node upgrade is finally guaranteed. Successful, otherwise the application upgrade must fail, and the application node will not run normally even if the upgrade is successful. If the platform node is upgraded first, if the application node fails to be upgraded, it is likely that the user equipment introduced an error in the process of constructing the application node upgrade package. At this time, the CSP can return the error information to the user equipment, and the error information includes the occurrence. The identifier of the wrong application node is modified by the user equipment and then the new application deployment package to be deployed is submitted.
- the application deployment server only needs to install the modified application deployment package to be deployed, and no need to upgrade the platform node. Therefore, in the above upgrade process, when the application deployment package of the first application node, the upgrade package of the first platform node, and the upgrade package of the second platform node are obtained until the nth platform node upgrade package, In the subsequent order, the nth platform node and the n-1th platform node are upgraded in sequence until the second platform node, the first platform node, and the first application node.
- Step 407 The application deployment server returns an upgrade response information to the user equipment.
- each platform node is successfully upgraded, it needs to write a new version of the platform node to the database because it has a new version.
- the application upgrade method provided by the embodiment of the present invention describes the version requirement of the application node template to be deployed to the first platform node template in the application description file of the application deployment package to be deployed.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- An embodiment of the present invention provides an application deployment server 80, as shown in FIG. 8, which includes:
- the receiving module 801 is configured to receive an application deployment request, where the application deployment request includes an application deployment package to be deployed, and the application deployment package to be deployed describes the application node template to be deployed, the identifier of the deployed application, and the deployed
- the identifier of the application node template, the identifier of the first platform node template, the version requirement of the application node template to be deployed, and the application node template to be deployed are used for the deployed application node template.
- the upgrade identifier of the deployed application node template upgrade indicated by the identifier, and the application deployment package of the application to be deployed is sent to the determining module 802 and the upgrading module 803;
- the determining module 802 is configured to receive an application deployment package of the to-be-deployed application sent by the receiving module 801, and determine, according to the upgrade identifier, the to-be-deployed application An upgrade package of the deployed application indicated by the deployment package for the identifier of the deployed application; and an identifier for acquiring the first platform node corresponding to the identifier of the first platform node template according to the deployed application identifier And obtaining a version of the first platform node indicated by the identifier of the first platform node; and determining that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the upgrade identifier is an upgrade identifier used by the application node template to be deployed to upgrade the deployed application node template indicated by the identifier of the deployed application node template.
- the first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template, and sends the first a platform node upgrade package to the upgrade module;
- the upgrade module 803 is configured to receive the first platform node upgrade package sent by the determining module 802, and use the first platform node upgrade package to upgrade the first indicator of the first platform node identifier Platform node
- the determining module 802 is further configured to determine an identifier of the application node to be upgraded according to the identifier of the deployed application node template, and send the identifier of the application node to be upgraded to the upgrade module 803;
- the upgrade module 803 is further configured to receive an application deployment package of the application to be deployed sent by the receiving module 801, and receive an identifier of the application node to be upgrade sent by the determining module 802, and use The application deployment package to be deployed upgrades the application node indicated by the identifier of the application node to be upgraded.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template.
- the upgrade module searches the first platform node template according to the application node template to be deployed.
- the version requires the first platform node upgrade package.
- the upgrade module upgrades the first platform node according to the obtained first platform node upgrade package. Making the version of the first platform node after the upgrade meet the application node mode to be deployed.
- the board requires versioning of the first platform node template to ensure that the upgraded application works properly.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the determining module 802 is specifically configured to: determine that an identifier of all the application nodes corresponding to the identifier of the deployed application node template is an identifier of an application node to be upgraded; or
- an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, the identifier of the application node that is determined to be upgraded is specifically:
- the determining module 802 is further configured to:
- the upgrade module 803 is further configured to:
- application deployment server provided by the embodiment of the present invention may perform any part of the execution of the application deployment server described in FIG. 2 to FIG.
- the embodiments of the present invention will not be described in detail herein.
- the application deployment server provided by the present invention describes the version requirements of the application node template to be deployed to the first platform node template in the application deployment file to be deployed.
- the upgrade module searches the first platform node template according to the application node template to be deployed.
- the version requires the first platform node upgrade package.
- the upgrade module upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, so as to ensure that the upgraded application can run normally.
- the embodiment of the present invention provides a user equipment 90, as shown in FIG. 9, including: a generating module 901, configured to generate an application deployment package to be deployed, where the application deployment package to be deployed describes an application node template to be deployed, The identifier of the deployed application, the identifier of the first platform node template, the identifier of the deployed application node template, the version requirement of the application node template to be deployed to the first platform node template, and the application node template to be deployed. And an upgrade identifier of the deployed application node template upgrade indicated by the identifier of the deployed application node template;
- the generating module 901 is further configured to generate an application deployment request, and send the application deployment request to the sending module 902, where the application deployment request includes the application deployment package to be deployed;
- the sending module 902 is configured to receive the application deployment request sent by the generating module 901, and send the application deployment request to an application deployment server.
- the generating module of the user equipment generates an application deployment package to be deployed, and the application description file in the application deployment package to be deployed describes the application node model to be deployed.
- the board requires versioning of the first platform node template.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, thereby ensuring that the upgraded application can run normally.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed is further executed by a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the application deployment package to be deployed generated by the generating module 901 further includes: an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template.
- the user equipment further includes: a determining module 903, configured to determine, according to the description file of the deployed application deployment package, the first platform of the deployed application indicated by the deployed application identifier A node template, where the first platform node template uses the deployed application node template as a source node template.
- the user equipment provided by the embodiment of the present invention may perform any part of the execution of the user equipment described in FIG. 2 to FIG.
- the embodiments of the present invention are not described in detail herein.
- the generating module of the user equipment generates the application deployment package to be deployed, and the application description file in the application deployment package to be deployed describes the version of the application node template to be deployed to the first platform node template. demand.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the application deployment server searches the first platform according to the application node template to be deployed.
- the version requirement of the node template gets the first level Platform upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- An embodiment of the present invention provides an application deployment server 1 10 , as shown in FIG. 11 , including:
- the receiver 1 1 1 is configured to receive an application deployment request, where the application deployment request includes an application deployment package to be deployed, and the application deployment package to be deployed describes an application node template to be deployed, an identifier of the deployed application, and The identifier of the deployed application node template, the identifier of the first platform node template, the version requirement of the application node template to be deployed to the first platform node template, and the application node template to be deployed are used for the deployed application. An upgrade identifier of the deployed application node template upgrade indicated by the identifier of the node template, and sending the application deployment package to be deployed to the processor 1 12;
- the processor 1 12 is configured to:
- the application deployment package to be deployed Receiving, by the receiver 1 1 1 , the application deployment package to be deployed, and determining, according to the application node template to be deployed, the application deployment package to be deployed as An upgrade package of the deployed application indicated by the identifier of the deployment application; the upgrade identifier is used by the application node template to be deployed for the deployed application indicated by the identifier of the deployed application node template. Upgrade ID of the node template upgrade.
- the first platform node upgrade package that satisfies the version requirement of the application node template to be deployed on the first platform node template; Upgrading the first platform node indicated by the identifier of the first platform node template by using the first platform node upgrade package;
- the application node indicated by the identifier of the application node to be upgraded is upgraded by using the application deployment package to be deployed.
- the application description file in the application deployment package to be deployed describes the version requirement of the application node template to be deployed on the first platform node template.
- the processor determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template, the processor searches the first platform node template according to the application node template to be deployed.
- the version requires the first platform node upgrade package.
- the processor upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node meets the version requirement of the application node template to be deployed on the first platform node template, thereby ensuring that the upgraded application can run normally.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed further includes a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the processor 1 is specifically configured to: determine that the identifiers of all the application nodes corresponding to the identifiers of the deployed application node templates are identifiers of the application nodes to be upgraded; or
- an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template, the identifier of the application node that is determined to be upgraded is specifically:
- the processor 1 12 is also used to:
- application deployment server provided by the embodiment of the present invention may perform any part of the execution of the application deployment server described in FIG. 2 to FIG.
- the embodiments of the present invention will not be described in detail herein.
- the application deployment server provided by the present invention describes the version requirements of the application node template to be deployed on the first platform node template in the application deployment file to be deployed.
- the processor determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template
- the processor searches the first platform node template according to the application node template to be deployed.
- the version requires the first platform node upgrade package.
- the processor upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, thereby ensuring that the upgraded application can run normally.
- An embodiment of the present invention provides a user equipment 120, as shown in FIG.
- a processor 121 configured to generate an application deployment package to be deployed, where the application deployment package to be deployed describes an application node template to be deployed, The ID of the deployed application, the identifier of the first platform node template, the identifier of the deployed application node template, and the to be deployed And the application identifier of the application node template to the upgraded identifier of the deployed application node template indicated by the identifier of the deployed application node template;
- the transmitter 122 is configured to receive the application deployment request sent by the processor, and send the application deployment request to an application deployment server.
- the processor of the user equipment generates an application deployment package to be deployed, and then generates an application deployment request according to the application deployment package to be deployed, and sends the application deployment request to the transmitter, and then sends the application deployment request to the transmitter through the transmitter.
- the application deployment server automatically upgrades the platform node and the application node according to the application deployment package to be deployed in the application deployment request, thereby improving the automation of the application upgrade and reducing manual intervention.
- the application deployment package to be deployed further includes a relationship template that describes the application node template to be deployed, where the upgrade identifier is carried in the relationship template;
- the application deployment package to be deployed is further executed by a node type corresponding to the application node template to be deployed, and the upgrade identifier is carried in the node type execution.
- the application deployment package to be deployed generated by the processor 121 further includes: an identifier of the at least one deployed application node corresponding to the identifier of the deployed application node template.
- the processor 121 is further configured to: determine, according to a description file of the deployed application deployment package, a first platform node template of the deployed application indicated by the deployed application identifier, where the first platform node template is deployed Apply the node template as the source node template.
- the processor generates an application deployment package to be deployed according to the application developer's upgrade requirement, and the application description file in the application deployment package to be deployed describes the application node template to be deployed on the first platform node template. Version requirements.
- the application deployment server determines that the version of the first platform node is lower than the version of the application node template to be deployed to the first platform node template, the application deployment server searches the first platform according to the application node template to be deployed.
- the version of the node template requires the first platform node upgrade package.
- the application deployment server upgrades the first platform node according to the obtained first platform node upgrade package.
- the version of the first platform node after the upgrade meets the version requirement of the application node template to be deployed on the first platform node template, thereby ensuring that the upgraded application can run normally.
- the disclosed systems, devices, and methods may be implemented in other ways.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
- the units described as separate components may or may not be physically separated, and the components displayed as the units may or may not be physical units, that is, may be located at one place, or may be distributed to a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or hard.
- the form is implemented in the form of a software functional unit.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020157023115A KR101782457B1 (ko) | 2013-08-13 | 2013-08-13 | 어플리케이션 업그레이드 방법 및 장치 |
CN201380001370.0A CN104583945B (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
CN201810011915.0A CN108052340B (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
CN201810012326.4A CN108319463B (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
JP2016520235A JP6164440B2 (ja) | 2013-08-13 | 2013-08-13 | アプリケーションアップグレード方法および装置 |
EP13891536.8A EP2945055A4 (en) | 2013-08-13 | 2013-08-13 | METHOD AND DEVICE FOR UPGRADING THE APPLICATION |
PCT/CN2013/081410 WO2015021604A1 (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
AU2013397867A AU2013397867B2 (en) | 2013-08-13 | 2013-08-13 | Application upgrade method and device |
US14/820,977 US9696984B2 (en) | 2013-08-13 | 2015-08-07 | Application upgrade method and apparatus |
US15/618,851 US10191730B2 (en) | 2013-08-13 | 2017-06-09 | Application upgrade method and apparatus |
US16/220,962 US10649761B2 (en) | 2013-08-13 | 2018-12-14 | Application upgrade method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2013/081410 WO2015021604A1 (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/820,977 Continuation US9696984B2 (en) | 2013-08-13 | 2015-08-07 | Application upgrade method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015021604A1 true WO2015021604A1 (zh) | 2015-02-19 |
Family
ID=52467924
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/081410 WO2015021604A1 (zh) | 2013-08-13 | 2013-08-13 | 一种应用升级方法、装置 |
Country Status (7)
Country | Link |
---|---|
US (3) | US9696984B2 (zh) |
EP (1) | EP2945055A4 (zh) |
JP (1) | JP6164440B2 (zh) |
KR (1) | KR101782457B1 (zh) |
CN (3) | CN108319463B (zh) |
AU (1) | AU2013397867B2 (zh) |
WO (1) | WO2015021604A1 (zh) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015021604A1 (zh) * | 2013-08-13 | 2015-02-19 | 华为技术有限公司 | 一种应用升级方法、装置 |
US9998323B2 (en) * | 2014-09-25 | 2018-06-12 | Bank Of America Corporation | Datacenter configuration management tool |
US10318265B1 (en) * | 2015-10-09 | 2019-06-11 | Amazon Technologies, Inc. | Template generation for deployable units |
CN107479862A (zh) * | 2016-06-07 | 2017-12-15 | 阿里巴巴集团控股有限公司 | 一种软件升级的灰度发布方法及*** |
US10353686B1 (en) * | 2016-12-28 | 2019-07-16 | Facebook, Inc. | Application installation system |
CN108809683B (zh) * | 2017-05-04 | 2022-07-15 | 中兴通讯股份有限公司 | 部署云应用***的方法及装置 |
US10749743B2 (en) | 2017-06-12 | 2020-08-18 | Microsoft Technology Licensing, Llc | Upgrade a version of a service |
CN107844314B (zh) * | 2017-12-22 | 2020-12-18 | 税友软件集团股份有限公司 | 一种升级Weblogic应用程序的方法及*** |
CN110308914B (zh) * | 2018-03-27 | 2023-08-22 | 阿里巴巴(中国)有限公司 | 升级处理方法、装置、设备、***及计算机可读存储介质 |
CN109032634B (zh) * | 2018-07-16 | 2021-11-26 | 北京百度网讯科技有限公司 | 用于更新应用的方法、装置、设备和计算机可读存储介质 |
CN109388415A (zh) * | 2018-09-27 | 2019-02-26 | 深圳供电局有限公司 | 一种应用自动化更新装置、***和方法 |
CN112035146B (zh) * | 2020-09-11 | 2023-10-24 | 百富计算机技术(深圳)有限公司 | 固件更新方法、安全设备和计算机可读存储介质 |
WO2023275589A1 (en) * | 2021-06-28 | 2023-01-05 | Sensetime International Pte. Ltd. | Methods and apparatuses for installing device application |
US11861339B2 (en) * | 2021-09-16 | 2024-01-02 | Change Healthcare Holdings, Llc | Systems and methods for deploying software applications using application catalogs |
WO2023230642A1 (en) * | 2022-05-31 | 2023-12-07 | Technological Resources Pty Limited | Ensuring backwards compatbility between a supervisory system and on-device control software |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040261071A1 (en) * | 2003-06-23 | 2004-12-23 | Macronix International Co., Ltd. | Peer version control system |
CN102495733A (zh) * | 2011-12-08 | 2012-06-13 | 方正国际软件有限公司 | 应用程序与相关数据库脚本兼容性检测和升级维护的方法 |
CN103136013A (zh) * | 2011-12-01 | 2013-06-05 | 腾讯科技(深圳)有限公司 | 软件升级方法和*** |
Family Cites Families (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2333864B (en) * | 1998-01-28 | 2003-05-07 | Ibm | Distribution of software updates via a computer network |
US6912711B1 (en) | 2000-05-25 | 2005-06-28 | International Business Machines Corporation | Method of applying an update to a contained collection of program and data files based upon versions |
US7478385B2 (en) | 2003-01-17 | 2009-01-13 | National Instruments Corporation | Installing software using programmatic component dependency analysis |
US20040148370A1 (en) * | 2003-01-23 | 2004-07-29 | Electronic Data Systems Corporation | System and method for composing, configuring, deploying, and managing services using a graphical user interface |
KR101169432B1 (ko) | 2005-12-12 | 2012-07-27 | 삼성전자주식회사 | 자바 어플리케이션의 실행 환경 관리 시스템 및 방법 |
US8726267B2 (en) | 2006-03-24 | 2014-05-13 | Red Hat, Inc. | Sharing software certification and process metadata |
CN100549950C (zh) * | 2006-07-14 | 2009-10-14 | 中兴通讯股份有限公司 | 分布式软件***的部署方法 |
US7874008B2 (en) * | 2006-08-29 | 2011-01-18 | International Business Machines Corporation | Dynamically configuring extensible role based manageable resources |
US7634488B2 (en) * | 2006-11-13 | 2009-12-15 | Ricoh Company, Ltd. | Remote distribution/installation utility and associated method of deploying executable code |
US8205194B2 (en) * | 2007-06-29 | 2012-06-19 | Microsoft Corporation | Updating offline virtual machines or VM images |
US20090133014A1 (en) | 2007-11-16 | 2009-05-21 | Nokia Corporation | Methods, apparatuses and computer program product for automatic download of software dependencies on installation |
KR100952166B1 (ko) * | 2008-07-24 | 2010-04-09 | 인하대학교 산학협력단 | 그리드 데이터 베이스의 데이터 버전 관리 방법 및 장치 |
US8291378B2 (en) * | 2008-07-29 | 2012-10-16 | International Business Machines Corporation | Simplified deployment modeling |
US9280335B2 (en) * | 2010-09-30 | 2016-03-08 | International Business Machines Corporation | Semantically rich composable software image bundles |
US20110055299A1 (en) * | 2008-12-18 | 2011-03-03 | Virtual Computer, Inc. | Managing User Data in a Layered Virtual Workspace |
US20100281475A1 (en) * | 2009-05-04 | 2010-11-04 | Mobile On Services, Inc. | System and method for mobile smartphone application development and delivery |
US8479098B2 (en) * | 2009-08-12 | 2013-07-02 | Ebay Inc. | Reservation of resources and deployment of applications using an integrated development environment |
US20120066672A1 (en) * | 2010-03-16 | 2012-03-15 | Salesforce.Com, Inc. | Systems and Methods for Implementing Upgradeable Subscriber-Controlled Managed Package Components in a Multi-Tenant Environment |
US9448790B2 (en) * | 2010-04-26 | 2016-09-20 | Pivotal Software, Inc. | Rapid updating of cloud applications |
US8661132B2 (en) * | 2010-05-28 | 2014-02-25 | International Business Machines Corporation | Enabling service virtualization in a cloud |
US8782748B2 (en) * | 2010-06-22 | 2014-07-15 | Microsoft Corporation | Online service access controls using scale out directory features |
US8407689B2 (en) * | 2010-06-25 | 2013-03-26 | Microsoft Corporation | Updating nodes considering service model constraints |
US8627310B2 (en) * | 2010-09-30 | 2014-01-07 | International Business Machines Corporation | Capturing multi-disk virtual machine images automatically |
US9753713B2 (en) * | 2010-10-22 | 2017-09-05 | Microsoft Technology Licensing, Llc | Coordinated upgrades in distributed systems |
CN102006332B (zh) * | 2010-12-03 | 2013-12-11 | 杭州华三通信技术有限公司 | 一种软件升级的方法和*** |
US9021465B2 (en) * | 2010-12-15 | 2015-04-28 | Red Hat Israel, Ltd. | Downloading guest software updates by a hypervisor |
US8261295B1 (en) * | 2011-03-16 | 2012-09-04 | Google Inc. | High-level language for specifying configurations of cloud-based deployments |
JP5665188B2 (ja) * | 2011-03-31 | 2015-02-04 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | ソフトウエア更新を適用した情報処理装置を検査するシステム |
US9015710B2 (en) * | 2011-04-12 | 2015-04-21 | Pivotal Software, Inc. | Deployment system for multi-node applications |
CN102811136A (zh) * | 2011-06-01 | 2012-12-05 | 南京中兴新软件有限责任公司 | 软件升级***及方法 |
TW201250482A (en) | 2011-06-02 | 2012-12-16 | Hon Hai Prec Ind Co Ltd | System and method for updating virtual machine templates |
US20130117749A1 (en) * | 2011-11-03 | 2013-05-09 | Microsoft Corporation | Provisioning and Managing an Application Platform |
CN102404147A (zh) * | 2011-11-21 | 2012-04-04 | 中兴通讯股份有限公司 | 一种软件版本的动态更新方法及*** |
US9235398B2 (en) * | 2011-12-07 | 2016-01-12 | Yahoo! Inc. | Development of platform independent applications |
US20130166311A1 (en) * | 2011-12-21 | 2013-06-27 | The TriZetto Group | System and Method for Provisioning and Deploying a Virtual Appliance to Implement Enterprise Solutions |
CN102413022B (zh) * | 2011-12-31 | 2014-04-16 | 北京新媒传信科技有限公司 | 一种应用调试方法和*** |
US9043784B2 (en) * | 2012-01-12 | 2015-05-26 | Red Hat, Inc. | Management of inter-dependent configurations of virtual machines in a cloud |
US9047133B2 (en) * | 2012-03-02 | 2015-06-02 | Vmware, Inc. | Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud environment |
US10031783B2 (en) * | 2012-03-02 | 2018-07-24 | Vmware, Inc. | Execution of a distributed deployment plan for a multi-tier application in a cloud infrastructure |
CN102629207B (zh) * | 2012-03-05 | 2016-12-14 | 浪潮通用软件有限公司 | 一种多租户环境运行实例分时更新的方法 |
US8667486B2 (en) * | 2012-06-26 | 2014-03-04 | Google Inc. | Automatic provisioning of a software platform to a device ecosystem |
US9348652B2 (en) * | 2012-07-02 | 2016-05-24 | Vmware, Inc. | Multi-tenant-cloud-aggregation and application-support system |
CN102821162B (zh) * | 2012-08-24 | 2016-04-27 | 上海和辰信息技术有限公司 | 云计算网络环境下面向松散云节点服务平台的*** |
US8997088B2 (en) * | 2012-11-02 | 2015-03-31 | Wipro Limited | Methods and systems for automated deployment of software applications on heterogeneous cloud environments |
US8875121B2 (en) * | 2012-11-06 | 2014-10-28 | Nvidia Corporation | Framework for multi-type and multi-location firmware updates and hardware feature updates through a single interface protocol |
CN102945175A (zh) * | 2012-11-09 | 2013-02-27 | 杭州易和网络有限公司 | 一种基于云计算环境的终端软件在线升级***及其方法 |
US8924950B2 (en) | 2012-12-17 | 2014-12-30 | Itron, Inc. | Utility node software/firmware update through a multi-type package |
US9189224B2 (en) * | 2013-07-11 | 2015-11-17 | Oracle International Corporation | Forming an upgrade recommendation in a cloud computing environment |
WO2015021604A1 (zh) * | 2013-08-13 | 2015-02-19 | 华为技术有限公司 | 一种应用升级方法、装置 |
US9753784B2 (en) * | 2013-11-27 | 2017-09-05 | At&T Intellectual Property I, L.P. | Cloud delivery platform |
CN106796508B (zh) * | 2014-04-30 | 2020-09-04 | 皮沃塔尔软件公司 | 在云平台上的快速部署 |
-
2013
- 2013-08-13 WO PCT/CN2013/081410 patent/WO2015021604A1/zh active Application Filing
- 2013-08-13 AU AU2013397867A patent/AU2013397867B2/en active Active
- 2013-08-13 CN CN201810012326.4A patent/CN108319463B/zh active Active
- 2013-08-13 JP JP2016520235A patent/JP6164440B2/ja active Active
- 2013-08-13 CN CN201810011915.0A patent/CN108052340B/zh active Active
- 2013-08-13 KR KR1020157023115A patent/KR101782457B1/ko active IP Right Grant
- 2013-08-13 EP EP13891536.8A patent/EP2945055A4/en not_active Withdrawn
- 2013-08-13 CN CN201380001370.0A patent/CN104583945B/zh active Active
-
2015
- 2015-08-07 US US14/820,977 patent/US9696984B2/en active Active
-
2017
- 2017-06-09 US US15/618,851 patent/US10191730B2/en active Active
-
2018
- 2018-12-14 US US16/220,962 patent/US10649761B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040261071A1 (en) * | 2003-06-23 | 2004-12-23 | Macronix International Co., Ltd. | Peer version control system |
CN103136013A (zh) * | 2011-12-01 | 2013-06-05 | 腾讯科技(深圳)有限公司 | 软件升级方法和*** |
CN102495733A (zh) * | 2011-12-08 | 2012-06-13 | 方正国际软件有限公司 | 应用程序与相关数据库脚本兼容性检测和升级维护的方法 |
Also Published As
Publication number | Publication date |
---|---|
KR101782457B1 (ko) | 2017-09-28 |
JP6164440B2 (ja) | 2017-07-19 |
US9696984B2 (en) | 2017-07-04 |
EP2945055A1 (en) | 2015-11-18 |
EP2945055A4 (en) | 2016-05-25 |
US10649761B2 (en) | 2020-05-12 |
US20150347123A1 (en) | 2015-12-03 |
KR20150110766A (ko) | 2015-10-02 |
CN104583945A (zh) | 2015-04-29 |
CN104583945B (zh) | 2018-01-12 |
CN108052340B (zh) | 2021-03-30 |
CN108052340A (zh) | 2018-05-18 |
AU2013397867A1 (en) | 2015-08-27 |
US20190129709A1 (en) | 2019-05-02 |
CN108319463B (zh) | 2021-08-20 |
US20170277532A1 (en) | 2017-09-28 |
AU2013397867B2 (en) | 2017-05-18 |
US10191730B2 (en) | 2019-01-29 |
JP2016521897A (ja) | 2016-07-25 |
CN108319463A (zh) | 2018-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015021604A1 (zh) | 一种应用升级方法、装置 | |
CN107689882B (zh) | 一种虚拟化网络中业务部署的方法和装置 | |
US10382291B2 (en) | Provisioning framework for binding related cloud services | |
US10452372B2 (en) | Method and deployment module for managing a container to be deployed on a software platform | |
JP6329547B2 (ja) | クラウドコンピューティング環境で使用するサービス管理エンジンを提供するためのシステムおよび方法 | |
US10225140B2 (en) | Portable instance provisioning framework for cloud services | |
US8775577B1 (en) | System and method for configuration management service | |
US8887147B2 (en) | Method for supporting new network element software versions in an element management system without upgrading | |
US8799453B2 (en) | Managing networks and machines for an online service | |
CN102413022B (zh) | 一种应用调试方法和*** | |
US11356508B1 (en) | Retry strategies for handling failures during continuous delivery of software artifacts in a cloud platform | |
US20160080479A1 (en) | Application deployment method and device | |
US20140157262A1 (en) | Multi-tier platform-as-a-service (paas) deployment reduced to single-tier architecture for development | |
KR20160067180A (ko) | 가상 머신들을 관리하는 장치 및 방법 | |
US10581823B2 (en) | Web client plugin manager in vCenter managed object browser | |
US11349958B1 (en) | Deployment of software releases on datacenters configured in cloud platforms | |
US20230035486A1 (en) | Managing execution of continuous delivery pipelines for a cloud platform based data center | |
US11392361B2 (en) | Software release orchestration for continuous delivery of features in a cloud platform based data center | |
KR100835272B1 (ko) | 에스시에이 시스템에서의 컴포넌트 관리 장치 및 그 방법 | |
US20220222125A1 (en) | Enforcing system configuration freeze of services deployed via continuous delivery on datacenters configured in cloud platforms | |
CN112351114B (zh) | 一种信息处理方法、装置以及存储介质 | |
US20180167278A1 (en) | A system and method for facilitating migration of server infrastructure services | |
US12035231B2 (en) | Virtualization management method and apparatus | |
WO2021147375A1 (zh) | 数据管理方法、装置、设备、计算机可读存储介质及*** | |
WO2023147882A1 (en) | Version-dependency information for management of a network service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13891536 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013891536 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20157023115 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2013397867 Country of ref document: AU Date of ref document: 20130813 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: IDP00201505925 Country of ref document: ID |
|
ENP | Entry into the national phase |
Ref document number: 2016520235 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |