WO2018201778A1 - 部署云应用系统的方法及装置 - Google Patents

部署云应用系统的方法及装置 Download PDF

Info

Publication number
WO2018201778A1
WO2018201778A1 PCT/CN2018/076837 CN2018076837W WO2018201778A1 WO 2018201778 A1 WO2018201778 A1 WO 2018201778A1 CN 2018076837 W CN2018076837 W CN 2018076837W WO 2018201778 A1 WO2018201778 A1 WO 2018201778A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
relationship
application system
cloud application
deployment
Prior art date
Application number
PCT/CN2018/076837
Other languages
English (en)
French (fr)
Inventor
茅非
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018201778A1 publication Critical patent/WO2018201778A1/zh

Links

Images

Classifications

    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for deploying a cloud application system.
  • each cloud application system is deployed to the domain to be deployed. Due to various deployment scenarios and involving thousands of computer nodes, very high requirements are placed on the deployment efficiency, if only With the traditional deployment method, that is, simply deploying each node one by one, the deployment process has technical problems that require a lot of time and labor, high cost, high energy consumption, and low deployment efficiency.
  • the present disclosure provides a method and apparatus for deploying a cloud application system with low cost, low power consumption, and high deployment efficiency.
  • a method of deploying a cloud application system includes a topology format description file, and the topology format description file includes a node.
  • the method includes the following steps: when detecting the import of the topology format description file, parsing the topology format description file, and acquiring a node relationship between nodes in the topology format description file; based on the node relationship, Serializing each node and generating a step-by-step deployment process with a serial-parallel relationship; and, based on the step-by-step deployment process, invoking a corresponding deployment script of each node to perform serial or parallel deployment operations on each node.
  • an apparatus for deploying a cloud application system includes a topology format description file, and the topology format description file includes a node.
  • the device includes: a first detecting module configured to parse the topology format description file when the topology format description file is imported, and obtain a node relationship between nodes in the topology format description file; a first generation module configured to serialize each node based on the node relationship, and generate a step-by-step deployment process having a serial-parallel relationship; and a deployment module configured to be invoked based on the step-by-step deployment process
  • the corresponding deployment script of each node performs serial or parallel deployment operations on each node.
  • FIG. 1 is a flowchart illustrating a method of deploying a cloud application system, according to an exemplary embodiment of the present disclosure
  • FIG. 2 is a flowchart illustrating a method of deploying a cloud application system, according to an exemplary embodiment of the present disclosure
  • FIG. 3 is a structural block diagram showing an apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 4 is a structural block diagram showing an apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 5 is a schematic diagram showing a node inclusion in a method and apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 6 is a schematic diagram showing a node connection relationship in a method and apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 7 is a schematic diagram showing a relationship between a plurality of nodes in a method and apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 8 is a flowchart showing a deployment in a method and apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 9 is a flowchart showing a process of uninstalling a cloud application system in a method and apparatus for deploying a cloud application system according to an exemplary embodiment of the present disclosure
  • FIG. 10 is a schematic diagram showing the structure of a hardware operating environment according to an exemplary embodiment of the present disclosure.
  • the method for deploying the cloud application system can be used to deploy the virtualized hardware system and the software system.
  • the enterprise access network element can be deployed by using the method.
  • the enterprise access network element can be a virtualized network element.
  • the enterprise access network element to be deployed is configured to perform topology description processing, and then the cloud access application engine or device is deployed to perform overall deployment on the enterprise access network element. After the deployment, the enterprise access network element can implement hardware enterprise connection. All functions of the network element.
  • the present disclosure provides a method for deploying a cloud application system, where the cloud application system includes a topology format description file, and the topology format description file includes a node. As shown in FIG. 1, the method includes:
  • step S10 when the topology format description file is imported, the topology format description file is parsed to obtain a node relationship between nodes in the topology format description file.
  • Topology and Orchestration Specification for Cloud Applications is an application topology specification developed by the Organization for the Advancement of Structured Information Standards (OASIS).
  • OASIS Structured Information Standards
  • the concept of nodes is used in the topology format description file to describe all virtualized resources or micro-domains.
  • Service application systems such as nodes, can be used to describe a server, a network, a computer, a microservice, etc.
  • the configuration data of each type of node and the deployment scripts of each type of node can also be described using a topology format, nodes and nodes.
  • the relationship between the two is another key concept of the topology format description file.
  • the topology format can be used to describe the various topology levels of the cloud application system of the cloud computing architecture.
  • the configuration data of the node A is also a node, but the configuration data is included in the node A.
  • a workflow refers to the automation of a part or the whole of a business process in a computer application environment.
  • the cloud application system includes application software, system software, and the like. Before the cloud application system is deployed, the cloud application system has been parsed to generate a description file of the topology format, and the description file of the topology format is a topology ordination structure, so that the node can be clearly obtained. , node relationship, and can get the node status of the node.
  • the process of parsing the cloud application system to generate the description file of the topology format is completed in the external environment corresponding to the workflow engine, and the topology format description file is imported into the workflow engine of the disclosure, and the import mode may be automatic or manual, and the workflow engine detects After the topology format description file is imported, parsing the topology description files, parsing the relationship between the nodes in the topology description file, and obtaining the relationship between each node and other nodes, where the node relationship includes the node connection relationship and the node inclusion relationship. .
  • the node inclusion relationship (contained_in)
  • the node B is established inside the node A, and the node B can create the deployment only after the node A is completely created and deployed.
  • node B and node C do not create a deployment relationship, and the deployment can be created in parallel. However, after node C is created and deployed, node C needs to initiate a node with node. B's connection request (attach), only after the connection is completed, the two nodes can work normally, and all other types of custom nodes are connected in this way.
  • Step S20 Perform serialization processing on each node based on the node relationship, and generate a step-by-step deployment process with a serial-parallel relationship.
  • the serialization process of each import node includes sorting according to the deployment priority of each import node. There are often dependencies between the nodes to be deployed. For example, to enable the import node B to be deployed and run successfully, you must first deploy the import. Node A, wherein, as shown in FIG. 5, the included import node B has a lower priority than the import node A including the import node B. For the import node of the connection relationship, the priority is determined according to the actual situation.
  • the node priority level of the connection relationship may be the same or different, especially for the following connection import nodes and connected import nodes, their priorities are often Different:
  • a connection request is initiated at a certain time when a connection import node is received, and the connected import node receives and processes the connection request at a time after the moment, the connection import node and the connected import
  • the node side can work normally.
  • serializing each import node a step-by-step deployment operation flow with a serial-parallel relationship is generated.
  • the parallel relationship means that the import nodes have the same priority and can be deployed synchronously, while the serial relationship refers to the import.
  • the priorities of the nodes are different, and the different nodes are deployed correspondingly according to the priority level relationship.
  • Step S30 based on the step-by-step deployment process, invoking a corresponding deployment script of each node to perform serial or parallel deployment operations on each node.
  • the generated step-by-step deployment process with serial-parallel relationship that is, the deployment sequence relationship of different nodes, and the timing or timing of creating a connection process for nodes connecting the node relationship types.
  • the import nodes are deployed serially in an orderly sequence.
  • the workflow engine provides embedded support for the connection request for the connection type node relationship, and after the node with the connection relationship is detected to be deployed, the third node is created to initiate the fourth node to the fourth node.
  • the connection request and the fourth node receives and processes the connection processing flow of the connection request.
  • the third node initiates a connection request at a certain time in the process of deploying the node, and the connected fourth node can receive and process the connection request at a time after the moment, and the workflow engine automatically inserts the connection processing flow in the deployment process. To ensure accurate execution of the deployment.
  • the node relationship in the topology format description file is parallel according to the workflow string, after the step S10, the step S20, and the step S30 are performed. Deploying the import node corresponding to the cloud application system, not only through the context of the deployment between the node and the node, but also achieving node deployment, thereby improving deployment efficiency.
  • the method for deploying a cloud application system further includes:
  • Step S40 When detecting the request to uninstall the cloud application system, acquire a node and a node relationship in the topology format description file corresponding to the cloud application system to be uninstalled;
  • Step S50 Generate a step-by-step uninstallation process with a serial-parallel relationship corresponding to the cloud application system to be uninstalled based on the node and node relationship in the topology format description file corresponding to the cloud application system to be uninstalled, according to the step-by-step uninstallation process. Complete the uninstallation of the entire cloud application system.
  • the cloud application system node When the request to uninstall the cloud application system is detected, the cloud application system node is uninstalled according to the dependency relationship or the priority relationship between the plurality of uninstall nodes to be deployed, wherein the node to be uninstalled with low priority is first uninstalled.
  • the workflow engine uninstall process does not need to create or initiate a connection request, and thus can be synchronously uninstalled, but the node B to be uninstalled is included in the process.
  • the node A to be uninstalled can be uninstalled after the node B is to be uninstalled.
  • the time for uninstalling the cloud application system including the three nodes A, B, and C to be uninstalled is less than that of the unloading A, B, and C respectively. The sum of the times of the three nodes to be unloaded.
  • the uninstalling cloud application system process also uninstalls the node to be uninstalled corresponding to the cloud application system in parallel according to the workflow string, thereby improving the uninstalling efficiency.
  • the node relationship includes a node inclusion relationship and a node connection relationship
  • the node inclusion relationship is a relationship between the first node and a second node included in the first node
  • the node connection relationship is A connection relationship between the third node and the fourth node connected to the third node.
  • the step S20 includes:
  • the node relationship in the topology format description file is analyzed.
  • the inclusion deployment process of first deploying the first node and then deploying the second node is generated according to the first preset rule.
  • the relationship between the imported node and the imported node in the parsed topology description file is analyzed. As shown in FIG. 5, when the node relationship is a node inclusion relationship, the first node A node is deployed first, and then the first node is deployed.
  • the node C in the corresponding state is deployed first, then the deployment of the node C is blocked, and a connection request is initiated to the node B and the deployment is started.
  • Node B if the Node B receives and processes the connection request after completing the deployment, continues to complete the deployment of the node C.
  • the deployment of the cloud application system can be completed in an orderly and efficient manner.
  • step S20 further includes:
  • a connection processing flow is generated: when detecting that the third node and the fourth node are deployed, the third node initiates a connection request to the fourth node, and the fourth node receives and processes the connection request.
  • step S2020 includes:
  • the workflow engine is embedded in the connection processing flow, and the connection processing flow is embedded at the timing after detecting that both the third node and the fourth node are deployed.
  • the cloud application system has a node relationship of three nodes as shown in FIG. 7 (node B is included in node A and node C is connected to node B)
  • the connection processing flow is such that node C and node B are detected.
  • the third node C initiates a connection request to the fourth node B, and the fourth node B receives and processes the connection request.
  • the connection processing flow can also be performed during the deployment process, as shown in FIG. 8.
  • the third node C can initiate a connection request to the node B between the configure state and the start state of the node C.
  • the process of deploying the cloud application system is as follows: the node A and the node C are deployed in parallel, and after the node A is deployed, the node B is deployed. C is blocked in the configerie state.
  • the connection request between the node C and the node B is initiated.
  • the remaining deployment process in which the node C is in each state, such as the start state is completed.
  • the sub-steps of the process of generating the connection process of step S20 can save the time of deploying the node and improve the user experience, since the process flow can be deployed in parallel according to the generated workflow.
  • a method of deploying a cloud application system according to a fifth exemplary embodiment of the present disclosure is provided.
  • the method for deploying a cloud application system further includes:
  • the deployed cloud application system is automatically rolled back and unloaded.
  • the deployed cloud application system is automatically rolled back and unloaded, and the uninstall process is also performed in sequence or in parallel according to the priority of the node.
  • the processing efficiency of the abnormality condition in the deployment process can be improved by the above steps.
  • the present disclosure provides an apparatus for deploying a cloud application system, where the cloud application system includes a topology format description file, and the topology format description file includes a node.
  • the apparatus includes:
  • a first detecting module 10 configured to parse the topology format description file when the topology format description file is imported, and obtain a node relationship between nodes in the topology format description file;
  • the cloud application system includes application software, system software, and the like. Before the cloud application system is deployed, the cloud application system has been parsed to generate a description file of the topology format, and the description file of the topology format is a topology ordination structure, so that the node can be clearly obtained. , node relationship, and can get the node status of the node.
  • the process of parsing the cloud application system to generate the description file of the topology format is completed in the external environment corresponding to the workflow engine, and the topology format description file is imported into the workflow engine of the disclosure, and the import mode may be automatic or manual, and the workflow engine detects
  • the first detection module 10 parses the topology description files, parses the node relationships in the topology format description file, and obtains the relationship between each node and other nodes, where the node relationship includes the node connection. Relationships, nodes contain relationships. For the node inclusion relationship, as shown in FIG. 5, the node B is established inside the node A, and the node B can create the deployment only after the node A is completely created and deployed.
  • node B and node C do not create a deployment relationship, and the deployment can be created in parallel. However, after node C is created and deployed, node C needs to initiate a node with node. B's connection request, only after the connection is completed, the two nodes can work normally, and all other types of custom nodes are connected in this way.
  • a first generation module 20 configured to perform serialization processing on each node based on the node relationship, and generate a step-by-step deployment process having a serial-parallel relationship
  • the first generation module 20 is configured to serialize the import nodes, including sorting according to the deployment priorities of the import nodes, and the nodes to be deployed often have dependencies, for example, the import node B can be deployed. To run successfully, the import node A must be deployed first. As shown in FIG. 5, the included import node B has a lower priority than the import node A that includes the import node B. For the import node of the connection relationship, the priority is determined according to the actual situation.
  • the node priority level of the connection relationship may be the same or different, especially for the following connection import nodes and connected import nodes, their priorities are often Different:
  • a connection request is initiated at a certain time when a connection import node is received, and the connected import node receives and processes the connection request at a time after the moment, the connection import node and the connected import
  • the node side can work normally.
  • serializing each import node a step-by-step deployment operation flow with a serial-parallel relationship is generated.
  • the parallel relationship means that the import nodes have the same priority and can be deployed synchronously, while the serial relationship refers to the import.
  • the priorities of the nodes are different, and the different nodes are deployed correspondingly according to the priority level relationship.
  • the deployment module 30 is configured to perform a serial or parallel deployment operation on each node by invoking a corresponding deployment script of each node based on the step-by-step deployment process.
  • the generated step-by-step deployment process with serial-parallel relationship that is, the deployment sequence relationship of different nodes, and the timing or timing of creating a connection process for nodes connecting the node relationship types.
  • the deployment module 30 is configured to perform a time serial deployment operation or a parallel deployment operation on each import node based on the generated step-by-step deployment process with a serial-parallel relationship, that is, parallel deployment of nodes with the same priority according to the step-by-step deployment process Import nodes with different priorities are serially deployed in an orderly sequence.
  • the workflow engine provides embedded support for the connection request for the connection type node relationship, and after the node with the connection relationship is detected to be deployed, the third node is created to initiate the fourth node to the fourth node.
  • the connection request and the fourth node receives and processes the connection processing flow of the connection request.
  • the third node initiates a connection request at a certain time in the process of deploying the node, and the connected fourth node can receive and process the connection request at a time after the moment, and the workflow engine automatically inserts the connection processing flow in the deployment process. To ensure accurate execution of the deployment.
  • the node relationship deploys the import node corresponding to the cloud application system in parallel according to the workflow stream, and not only through the context of the deployment between the node and the node, but also implements the node deployment, thereby improving the deployment efficiency.
  • the device for deploying a cloud application system further includes:
  • a second detecting module 40 configured to acquire a node and a node relationship in a topology format description file corresponding to the cloud application system to be uninstalled when the request for uninstalling the cloud application system is detected;
  • a second generation module 50 configured to generate a step-by-step uninstallation process with a serial-parallel relationship corresponding to the cloud application system to be uninstalled, based on a node and a node relationship in the topology format description file corresponding to the cloud application system to be uninstalled, The uninstallation of the entire cloud application system is completed according to the step-by-step uninstallation process.
  • the second detecting module 40 is configured to acquire a dependency relationship or a priority relationship between the plurality of uninstalling nodes to be deployed when the request for uninstalling the corresponding cloud application system is detected, and the second generating module 50 is configured to use the dependency relationship according to the dependency relationship.
  • the priority relationship is performed to uninstall the cloud application system node, wherein the node to be uninstalled with low priority is first uninstalled, as shown in FIG. 9 , because the node C to be uninstalled and the node B to be uninstalled are connection relationship nodes, the workflow engine is uninstalled.
  • the process does not need to create or initiate a connection request, and thus can be uninstalled synchronously, but the node B to be uninstalled is included in the node A to be uninstalled, and thus the node A to be uninstalled can be uninstalled after the node B to be uninstalled is uninstalled.
  • the time of the cloud application system of the three nodes to be uninstalled, B, and C is less than the sum of the time of uninstalling the three nodes to be uninstalled, respectively, A, B, and C.
  • the uninstalling cloud application system process also uninstalls the node to be uninstalled corresponding to the cloud application system in parallel according to the workflow string, thereby improving Unloading efficiency.
  • the node relationship includes a node inclusion relationship and a node connection relationship
  • the node inclusion relationship is a relationship between the first node and a second node included in the first node
  • the node connection relationship is A connection relationship between the third node and the connected fourth node.
  • the first generating module 20 includes:
  • a first deployment unit configured to analyze a node relationship in the topology format description file.
  • the node relationship is a node inclusion relationship, first deploying the first node and then deploying the second according to the first preset rule. The inclusion process of the node;
  • a second deployment unit configured to analyze a node relationship in the topology format description file, and when the node relationship is a node connection relationship, generate a third node and a fourth node simultaneously according to the second preset rule Connect the deployment process;
  • a generation unit configured to generate a step-by-step deployment process with a serial-parallel relationship based on the inclusion deployment process and the connection deployment process.
  • the first deployment unit is configured to analyze the imported node and the imported node relationship in the parsed topology format description file, as shown in FIG. 5, when the node relationship is a node inclusion relationship, the first node is deployed first.
  • a node, the operation flow of the second node B node is deployed later, and as shown in FIG. 6, the second deployment unit is configured to be the third node and the node B is the fourth node when the node relationship is a node connection relationship.
  • the workflow engine provides embedded support for the connection request. Therefore, according to the corresponding serialization process in the topology format description file, the following operation flow can be performed: as shown in FIG. 8, the node C in the corresponding state is deployed first, and the node C is blocked later.
  • the generation unit is configured to generate a step-by-step deployment process with a serial-parallel relationship based on the inclusion deployment process and the connection deployment process.
  • the deployment of the cloud application system can be completed in an orderly manner because the nodes according to different node relationships generate different operation flows.
  • the first generation module 20 further includes:
  • connection processing unit configured to generate a connection processing flow: after detecting that both the third node and the fourth node are deployed, the third node initiates a connection request to the fourth node, and the fourth node receives and processes the connection request;
  • the generating unit includes:
  • a sub-unit is generated that is configured to generate a step-by-step deployment process with a serial-parallel relationship based on the inclusion deployment process, the connection deployment process, and the connection process flow.
  • the workflow engine is embedded in the connection processing flow, and the connection processing flow is embedded at the timing after detecting that both the third node and the fourth node are deployed.
  • the cloud application system has a node relationship of three nodes as shown in FIG. 7 (node B is included in node A and node C is connected to node B)
  • the connection processing flow is such that node C and node B are detected.
  • the third node C initiates a connection request to the fourth node B, and the fourth node B receives and processes the connection request.
  • the connection processing flow can also be performed during the deployment process, as shown in FIG. 8.
  • the third node C can initiate a connection request to the node B between the configure state and the start state of the node C.
  • the process of deploying the cloud application system is as follows: the node A and the node C are deployed in parallel, and after the node A is deployed, the node B is deployed. C is blocked in the configerie state.
  • the connection request between the node C and the node B is initiated.
  • the remaining deployment process in which the node C is in each state, such as the start state is completed.
  • An apparatus for deploying a cloud application system according to a tenth exemplary embodiment of the present disclosure is provided on the basis of an apparatus for deploying a cloud application system according to a sixth exemplary embodiment of the present disclosure.
  • the apparatus for deploying the cloud application system further includes:
  • the returning module is configured to perform automatic rollback and unloading processing on the deployed cloud application system if the node deployment abnormality is detected.
  • the returning module is configured to perform automatic rollback and unloading processing on the deployed cloud application system when the node deployment is abnormal, and the uninstalling process is also performed in sequence or in parallel according to the priority of the node.
  • the processing efficiency of the abnormality condition in the deployment process can be improved by applying the above-described bounce module.
  • the foregoing first detection module, first generation module, deployment module, second detection module, second generation module, first deployment unit, second deployment unit, generation unit, and generation subunit may be embedded in or independent of the device in which the cloud application system is deployed, or may be stored in software in the memory of the device deploying the cloud application system, so that the processor calls and executes the corresponding modules. Operation.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • FIG. 10 is a block diagram showing the structure of a hardware operating environment according to an exemplary embodiment of the present disclosure.
  • the device for deploying the cloud application system may be a PC, or may be a terminal device such as a smartphone, a tablet, a portable computer, or the like.
  • the device deploying the cloud application system may include a processor 1001 (eg, a CPU), a network interface 1002, and a memory 1003. Connection communication between these components can be achieved via a communication bus.
  • Network interface 1002 may include a standard wired interface, a wireless interface (such as a WI-FI interface).
  • the memory 1003 may be a high speed RAM memory or a non-volatile memory such as a magnetic disk memory.
  • the memory 1003 may also be a storage device independent of the aforementioned processor 1001.
  • the device deploying the cloud application system may further include a user interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi module, and the like.
  • the user interface may include a display, an input unit such as a keyboard, and optionally, the user interface may also include a standard wired interface, a wireless interface.
  • the device structure of the deployment cloud application system according to the exemplary embodiment of the present disclosure illustrated in FIG. 10 does not constitute a limitation of the device for deploying the cloud application system of the present disclosure, and the deployment cloud application of the present disclosure
  • the equipment of the system may include more or fewer components than those illustrated, or a combination of certain components, or a different component arrangement.
  • a memory 1003 as a computer storage medium may include an operating system, a network communication module, and a deployment cloud application system program.
  • an operating system is a program that manages and controls device hardware and software resources for deploying a cloud application system, which supports operation of a network communication module, a deployment cloud application system program, and other programs or software, wherein A network communication module can be used to manage and control the network interface 1002.
  • the network interface 1002 is mainly used to connect to a server, and performs data communication with the server, where the server stores a program for deploying the cloud application system; and the processor 1001 can be used to execute A program for deploying a cloud application system stored in the memory 1003 to implement the steps of the method of deploying the cloud application system described in the above first to fifth exemplary embodiments, for example, steps S10, S20, S30 , S2011, S2012, S2020, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本公开提供一种部署云应用系统的方法和装置。所述部署云应用系统的方法包括：当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，以获取拓扑格式描述文件中的节点之间的节点关系；基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；以及基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部署操作。

Description

部署云应用系统的方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种部署云应用系统的方法及装置。
背景技术
目前，在云计算环境下将各云应用系统部署至待部署终端的领域，由于存在各种部署场景，并且涉及成千上万台计算机节点，因而对部署效率提出了非常高的要求，如果仅仅凭借传统的部署方式，即简单地逐个部署各节点，则部署过程存在耗费大量的时间和人力、成本高、能耗大、部署效率低的技术问题。
发明内容
本公开提供一种成本低、能耗小、部署效率高的部署云应用系统的方法及装置。
根据本公开的一个方面，提供一种部署云应用系统的方法。所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点。所述方法包括如下步骤：当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，并获取所述拓扑格式描述文件中的节点之间的节点关系；基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；以及基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部署操作。
根据本公开的另一方面，提供一种部署云应用系统的装置。所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点。所述装置包括：第一检测模块，其配置为当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，并获取所述拓扑格式描述文件中的节点之间的节点关系；第一生成模块，其配置为基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；以及部署模块，其配置为基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部 署操作。
附图说明
图1是示出了根据本公开的示例性实施例的部署云应用系统的方法的流程图；
图2是示出了根据本公开的示例性实施例的部署云应用系统的方法的流程图；
图3是示出了根据本公开的示例性实施例的部署云应用系统的装置的结构框图；
图4是示出了根据本公开的示例性实施例的部署云应用系统的装置的结构框图；
图5是示出了根据本公开的示例性实施例的部署云应用系统的方法及装置中的节点包含关系(contained in)的示意图；
图6是示出了根据本公开的示例性实施例的部署云应用系统的方法及装置中的节点连接关系的示意图；
图7是示出了根据本公开的示例性实施例的部署云应用系统的方法及装置中的多个节点之间的关系的示意图；
图8是示出了根据本公开的示例性实施例的部署云应用系统的方法及装置中的部署的流程示意图；
图9是示出了根据本公开的示例性实施例的部署云应用系统的方法及装置中的卸载云应用系统的流程示意图；以及
图10是示出了根据本公开的示例性实施例的硬件运行环境的设备结构示意图。
具体实施方式
下文将结合附图以及示例性实施例，对本发明公开进行进一步详细说明。应当理解，本文所描述的具体示例性实施例仅仅用以解释本公开，并不用于限定本公开。
部署云应用系统的方法可用于部署虚拟化硬件系统、软件系统，如可使用该方法部署企业接入网元，企业接入网元可以是虚拟化网元，在部署企业接入网元之前，先将待部署的企业接入网元进行拓扑格式描述处理，然后调 用部署云应用系统引擎或者装置对该企业接入网元进行整体部署，部署完成后的企业接入网元可以实现硬件企业接入网元的所有功能。
第一示例性实施例
本公开提供一种部署云应用系统的方法，所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点，如图1所示，所述方法包括：
步骤S10，当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，以获取所述拓扑格式描述文件中的节点之间的节点关系。
拓扑(Topology and Orchestration Specification for Cloud Applications，TOSCA)是由结构化信息标准促进组织(OASIS)制定的应用拓扑编排规范，拓扑格式描述文件中使用节点(node)的概念描述所有的虚拟化资源或微服务应用系统，如节点可用于描述一台服务器、一个网络、一台计算机、一个微服务等等，各类型节点的配置数据以及各类型节点的部署脚本也可使用拓扑格式描述，节点与节点之间的关系则是拓扑格式描述文件的另一关键概念。通过节点与节点关系的定义，可以使用拓扑格式描述云计算架构的云应用系统的各个拓扑层次，如节点A的配置数据也是节点，但该配置数据被包含于该节点A中。另外，工作流(workflow)指的是业务过程的部分或整体在计算机应用环境下的自动化。
云应用系统包括应用软件、系统软件等等，在进行云应用系统部署之前，云应用系统已被解析生成拓扑格式的描述文件，该拓扑格式的描述文件为拓扑编排结构，因而能够清晰地获取节点、节点关系，并且能获取节点当前所处的节点状态。将云应用系统解析生成拓扑格式的描述文件的过程在与工作流引擎对应的外部环境完成，将拓扑格式描述文件导入至本公开的工作流引擎，导入方式可是自动或者用户手动，工作流引擎检测到所述拓扑格式描述文件导入后，解析该各个拓扑格式描述文件，解析出拓扑格式描述文件中的节点关系，获取各个节点与其他节点的关系，其中，节点关系包含节点连接关系、节点包含关系。对于节点包含关系(contained_in)，如图5所示，节点B建立在节点A的内部，只有在节点A完全创建部署完成后节点B才可以创建部署。对于节点连接关系，如图6所示，节点B和节点C并没有创建部署的先后关系，可以平行创建部署，但在节点C创建部署完成后或创建部署 过程中，节点C需要发起一次与节点B的连接请求(attach)，只有连接完成后，两个节点才能正常工作，所有其他类型的自定义节点都以这种方式进行连接。
步骤S20，基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程。
对各导入节点进行序列化处理包括根据各个导入节点的部署优先级进行排序，多个待部署的节点之间往往存在依赖关系，例如，要使导入节点B能够部署且成功运行，必须先部署导入节点A，其中，如图5所示，被包含的导入节点B的优先级低于包含该导入节点B的导入节点A的优先级。而对于连接关系的导入节点，则其优先级根据实际情况而定，连接关系的节点优先级级别可能相同，也可能不同，尤其对于如下的连接导入节点与被连接导入节点，它们的优先级往往不同：在创建部署节点过程中，在某个连接导入节点某一个时刻发起连接请求，而被连接的导入节点在该时刻之后的时刻接收以及处理连接请求后，该连接导入节点与被连接的导入节点方能正常工作。在对各个导入节点进行序列化处理后，生成具有串并行关系的分步部署操作流程，并行关系指的是导入节点的优先级相同，可以对它们进行同步部署，而串行关系指的是导入节点的优先级不同，对不同节点按照优先级级别关系对它们进行相应的前后部署。
步骤S30，基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部署操作。
生成的具有串并行关系的分步部署流程，即不同节点的部署先后关系，以及对连接节点关系类型的节点创建连接过程的时机或时序。基于所述生成的具有串并行关系的分步部署流程，对各导入节点执行时间串行部署操作或并行部署操作，即按照分步部署流程，对优先级相同的节点并行部署，对优先级不同的导入节点按照有序的先后顺序串行部署。在本公开的示例性实施例中，对连接类型的节点关系，工作流引擎提供对连接请求的嵌入支持，在检测到具有连接关系的节点都部署完成后，创建第三节点向第四节点发起连接请求并且第四节点接收并处理该连接请求的连接处理流程。例如，第三节点在部署节点过程中的某一个时刻发起连接请求，而被连接的第四节点在该时刻之后的时刻可以接收以及处理连接请求，工作流引擎自动在部署流程中 插入连接处理流程，从而保证部署的准确执行。
在本示例性实施例中，通过上述步骤S10、步骤S20、步骤S30，由于在获取与云应用系统对应生成的拓扑格式描述文件后，根据该拓扑格式描述文件中的节点关系按照工作流串并行部署与该云应用系统对应的导入节点，而不只是通过节点与节点之间部署的前后关系，实现节点部署，因而能够提高部署效率。
第二示例性实施例
在根据本公开的第一示例性实施例的部署云应用系统的方法的基础上，提供根据本公开的第二示例性实施例的部署云应用系统的方法。如图2所示，所述部署云应用系统的方法还包括：
步骤S40，当检测到卸载云应用系统的请求时，获取与该待卸载云应用系统对应拓扑格式描述文件中的节点、节点关系；以及
步骤S50，基于与该待卸载云应用系统对应的拓扑格式描述文件中的节点、节点关系，生成与该待卸载云应用系统对应的具有串并行关系的分步卸载流程，根据该分步卸载流程完成整个云应用系统的卸载。
当检测到卸载云应用系统的请求时，根据多个待部署的卸载节点之间存在的依赖关系或者优先级关系，进行云应用系统节点的卸载，其中，优先级低的待卸载节点先被卸载，如图9所示，由于待卸载节点C与待卸载节点B是连接关系节点，工作流引擎卸载过程不需要再创建或者发起连接请求，因而可同步卸载，但待卸载节点B被包含于待卸载节点A中，因而待卸载节点A在待卸载节点B卸载后方能被卸载，本申请卸载包含A、B、C三个待卸载节点的云应用系统的时间少于分别卸载A、B、C三个待卸载节点的时间之和。
在本示例性实施例中，通过上述步骤S40、步骤S50，由于卸载云应用系统过程也是按照工作流串并行卸载与该云应用系统对应的待卸载节点，因而提升了卸载效率。
第三示例性实施例
在根据本公开的第一示例性实施例的部署云应用系统的方法的基础上，提供根据本公开的第三示例性实施例的部署云应用系统的方法。在第三示例 性实施例中，所述节点关系包括节点包含关系和节点连接关系，节点包含关系为第一节点与包含在该第一节点中的第二节点之间的关系，节点连接关系为第三节点和与所述第三节点连接的第四节点之间的连接关系。
所述步骤S20包括：
S2011，对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为节点包含关系时，根据第一预置规则生成先部署第一节点、后部署第二节点的包含部署流程；
S2012，对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为节点连接关系时，根据第二预置规则生成同时部署第三节点与第四节点的连接部署流程；以及
S2020，根据包含部署流程与连接部署流程生成具有串并行关系的分步部署流程。
对已解析的所述拓扑格式描述文件中的导入节点、导入节点关系进行分析，如图5所示，当所述节点关系为节点包含关系时，生成先部署第一节点A节点，后部署第二节点B节点的操作流程，而如图6所示，当节点关系为节点连接关系时，节点C为第三节点，节点B为第四节点，工作流引擎提供对连接请求的嵌入支持，因而根据拓扑格式描述文件中的对应序列化过程可以是如下操作流程：如图8所示，先部署处于相应状态的节点C，后阻滞节点C的部署，并向节点B发起连接请求并开始部署节点B，若节点B完成部署后接收并处理该连接请求，则继续完成节点C的部署。
在本示例性实施例中，通过上述步骤S2011、步骤S2012、S2020，由于根据不同节点关系的节点生成不同的流程，因而能够有序高效地完成云应用系统的部署。
第四示例性实施例
在根据本公开的第三示例性实施例的部署云应用系统的方法的基础上，提供根据本公开的第四示例性实施例的部署云应用系统的方法。在第四示例性实施例中，在步骤S2012之后且在步骤S2020之前，步骤S20还包括：
生成这样的连接处理流程：在检测到第三节点与第四节点部署完成时，第三节点向第四节点发起连接请求，第四节点接收并处理该连接请求。
在本示例性实施例中，步骤S2020包括：
根据包含部署流程、连接部署流程、连接处理流程生成具有串并行关系的分步部署流程。
在部署过程中，工作流引擎嵌入连接处理流程，连接处理流程嵌入时机为在检测到第三节点与第四节点都部署完成后。当云层应用系统具有如图7所示三个节点的节点关系(节点B被包含于节点A中，节点C连接到节点B)时，连接处理流程是这样的：在检测到节点C与节点B都部署完成时，第三节点C向第四节点B发起连接请求，第四节点B接收并处理该连接请求。此外，连接处理流程还可在部署过程中进行，如图8所示，如在拓扑格式描述文件中，第三节点C可在节点C的configure状态和start状态之间发起对节点B的连接请求，而节点B接收并处理连接请求的状态为完全启动后，则部署该云应用系统的流程为：并行发起部署节点A和节点C，在节点A部署完成后，发起部署节点B，此时节点C被阻塞于configuire状态，当节点B完全部署完成后，发起节点C与节点B的连接请求，在得到节点B的连接请求回应后，完成节点C处于各个状态如start状态的剩余部署流程。
在本示例性实施例中，通过步骤S20的生成连接处理流程的子步骤，由于能够按照生成的工作流部署流程串并行部署，因而节约了部署节点的时间，提升了用户体验。
第五示例性实施例
在根据本公开的第一示例性实施例的部署云应用系统的方法的基础上，提供根据本公开的第五示例性实施例的部署云应用系统的方法。在第五示例性实施例中，所述部署云应用系统的方法还包括：
若检测到节点部署异常时，对部署的云应用系统进行自动回退卸载处理。
若检测到节点部署异常时，对部署的云应用系统进行自动回退卸载处理，且卸载过程也依据节点的优先级进行先后或者并行卸载。
在本示例性实施例中，通过上述步骤能够提升部署过程对异常状况的处理效率。
第六示例性实施例
本公开提供一种部署云应用系统的装置，所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点，如图3所示，所述装置包括：
第一检测模块10，其配置为当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，并获取所述拓扑格式描述文件中的节点之间的节点关系；
云应用系统包括应用软件、系统软件等等，在进行云应用系统部署之前，云应用系统已被解析生成拓扑格式的描述文件，该拓扑格式的描述文件为拓扑编排结构，因而能够清晰地获取节点、节点关系，并且能获取节点当前所处的节点状态。将云应用系统解析生成拓扑格式的描述文件的过程在与工作流引擎对应的外部环境完成，将拓扑格式描述文件导入至本公开的工作流引擎，导入方式可是自动或者用户手动，工作流引擎检测到所述拓扑格式描述文件导入后，第一检测模块10解析该各个拓扑格式描述文件，解析出拓扑格式描述文件中的节点关系，获取各个节点与其他节点的关系，其中，节点关系包含节点连接关系、节点包含关系。对于节点包含关系，如图5所示，节点B建立在节点A的内部，只有在节点A完全创建部署完成后节点B才可以创建部署。对于节点连接关系，如图6所示，节点B和节点C并没有创建部署的先后关系，可以平行创建部署，但在节点C创建部署完成后或创建部署过程中，节点C需要发起一次与节点B的连接请求，只有连接完成后，两个节点才能正常工作，所有其他类型的自定义节点都以这种方式进行连接。
第一生成模块20，其配置为基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；
第一生成模块20配置为对该各导入节点进行序列化处理包括根据各个导入节点的部署优先级进行排序，多个待部署的节点之间往往存在依赖关系，例如，要使导入节点B能够部署且成功运行，必须先部署导入节点A，其中，如图5所示，被包含的导入节点B的优先级低于包含该导入节点B的导入节点A的优先级。而对于连接关系的导入节点，则其优先级根据实际情况而定，连接关系的节点优先级级别可能相同，也可能不同，尤其对于如下的连接导入节点与被连接导入节点，它们的优先级往往不同：在创建部署节点过程中，在某个连接导入节点某一个时刻发起连接请求，而被连接的导入节点在该时刻之后的时刻接收以及处理连接请求后，该连接导入节点与被连接的导入节 点方能正常工作。在对各个导入节点进行序列化处理后，生成具有串并行关系的分步部署操作流程，并行关系指的是导入节点的优先级相同，可以对它们进行同步部署，而串行关系指的是导入节点的优先级不同，对不同节点按照优先级级别关系对它们进行相应的前后部署。
部署模块30，其配置为基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部署操作。
生成的具有串并行关系的分步部署流程，即不同节点的部署先后关系，以及对连接节点关系类型的节点创建连接过程的时机或时序。部署模块30配置为基于所述生成的具有串并行关系的分步部署流程，对各导入节点执行时间串行部署操作或并行部署操作，即按照分步部署流程，对优先级相同的节点并行部署，对优先级不同的导入节点按照有序的先后顺序串行部署。在本公开的示例性实施例中，对连接类型的节点关系，工作流引擎提供对连接请求的嵌入支持，在检测到具有连接关系的节点都部署完成后，创建第三节点向第四节点发起连接请求并且第四节点接收并处理该连接请求的连接处理流程。例如，第三节点在部署节点过程中的某一个时刻发起连接请求，而被连接的第四节点在该时刻之后的时刻可以接收以及处理连接请求，工作流引擎自动在部署流程中插入连接处理流程，从而保证部署的准确执行。
在本示例性实施例中，通过应用上述第一检测模块10、第一生成模块20、部署模块30，由于在获取与云应用系统对应生成的拓扑格式描述文件后，根据该拓扑格式描述文件中的节点关系按照工作流串并行部署与该云应用系统对应的导入节点，而不只是通过节点与节点之间部署的前后关系，实现节点部署，因而能够提高部署效率。
第七示例性实施例
在根据本公开的第六示例性实施例的部署云应用系统的装置的基础上，提供根据本公开的第七示例性实施例的部署云应用系统的装置。如图4所示，所述部署云应用系统的装置还包括：
第二检测模块40，其配置为当检测到卸载云应用系统的请求时，获取与该待卸载云应用系统对应拓扑格式描述文件中的节点、节点关系；以及
第二生成模块50，其配置为基于与该待卸载云应用系统对应的拓扑格式 描述文件中的节点、节点关系，生成与该待卸载云应用系统对应的具有串并行关系的分步卸载流程，根据该分步卸载流程完成整个云应用系统的卸载。
第二检测模块40配置为当检测到卸载相应云应用系统的请求时，获取多个待部署的卸载节点之间存在的依赖关系或者优先级关系，第二生成模块50，用于根据该依赖关系或者优先级关系进行云应用系统节点的卸载，其中，优先级低的待卸载节点先被卸载，如图9所示，由于待卸载节点C与待卸载节点B是连接关系节点，工作流引擎卸载过程不需要再创建或者发起连接请求，因而可同步卸载，但待卸载节点B被包含于待卸载节点A中，因而待卸载节点A在待卸载节点B卸载后方能被卸载，本申请卸载包含A、B、C三个待卸载节点的云应用系统的时间少于分别卸载A、B、C三个待卸载节点的时间之和。
在本示例性实施例中，通过用于上述第二检测模块40、第二生成模块50，由于卸载云应用系统过程也是按照工作流串并行卸载与该云应用系统对应的待卸载节点，因而提升了卸载效率。
第八示例性实施例
在根据本公开的第六示例性实施例的部署云应用系统的装置的基础上，提供根据本公开的第八示例性实施例的部署云应用系统的装置。在第八示例性实施例中，所述节点关系包括节点包含关系和节点连接关系，节点包含关系为第一节点与包含在该第一节点中的第二节点之间的关系，节点连接关系为第三节点和与被连接的第四节点之间的连接关系。
所述第一生成模块20包括：
第一部署单元，其配置为对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为节点包含关系时，根据第一预置规则生成先部署第一节点、后部署第二节点的包含部署流程；
第二部署单元，其配置为对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为节点连接关系时，根据第二预置规则生成同时部署第三节点与第四节点的连接部署流程；以及
生成单元，其配置为根据包含部署流程与连接部署流程生成具有串并行关系的分步部署流程。
第一部署单元配置为对已解析的所述拓扑格式描述文件中的导入节点、导入节点关系进行分析，如图5所示，当所述节点关系为节点包含关系时，生成先部署第一节点A节点，后部署第二节点B节点的操作流程，而如图6所示，第二部署单元配置为当节点关系为节点连接关系时，节点C为第三节点，节点B为第四节点，工作流引擎提供对连接请求的嵌入支持，因而根据拓扑格式描述文件中的对应序列化过程可以是如下操作流程：如图8所示，先部署处于相应状态的节点C，后阻滞节点C的部署，并向节点B发起连接请求并开始部署节点B，若节点B完成部署后接收并处理该连接请求，则继续完成节点C的部署。生成单元配置为根据包含部署流程与连接部署流程生成具有串并行关系的分步部署流程。
在本示例性实施例中，通过应用上述第一部署单元、第二部署单元、生成单元，由于根据不同节点关系的节点生成不同的操作流程，因而能够有序高效地完成云应用系统的部署。
第九示例性实施例
在根据本公开的第八示例性实施例的部署云应用系统的装置的基础上，提供根据本公开的第九示例性实施例的部署云应用系统的装置。在第九示例性实施例中，所述第一生成模块20还包括：
连接处理单元，其配置为生成这样的连接处理流程：在检测到第三节点与第四节点都部署完成后，第三节点向第四节点发起连接请求，第四节点接收并处理该连接请求；
在本示例性实施例中，所述生成单元包括：
生成子单元，其配置为根据包含部署流程、连接部署流程、连接处理流程生成具有串并行关系的分步部署流程。
在部署过程中，工作流引擎嵌入连接处理流程，连接处理流程嵌入时机为在检测到第三节点与第四节点都部署完成后。当云层应用系统具有如图7所示三个节点的节点关系(节点B被包含于节点A中，节点C连接到节点B)时，连接处理流程是这样的：在检测到节点C与节点B都部署完成时，第三节点C向第四节点B发起连接请求，第四节点B接收并处理该连接请求。此外，连接处理流程还可在部署过程中进行，如图8所示，如在拓扑格式描述 文件中，第三节点C可在节点C的configure状态和start状态之间发起对节点B的连接请求，而节点B接收并处理连接请求的状态为完全启动后，则部署该云应用系统的流程为：并行发起部署节点A和节点C，在节点A部署完成后，发起部署节点B，此时节点C被阻塞于configuire状态，当节点B完全部署完成后，发起节点C与节点B的连接请求，在得到节点B的连接请求回应后，完成节点C处于各个状态如start状态的剩余部署流程。
在本示例性实施例中，通过应用上述生成子单元，由于能够按照生成的工作流部署流程串并行部署，因而节约了部署节点的时间，提升了用户体验。
第十示例性实施例
在根据本公开的第六示例性实施例的部署云应用系统的装置的基础上，提供根据本公开的第十示例性实施例的部署云应用系统的装置。在第十示例性实施例中，所述部署云应用系统的装置还包括：
退回模块，其配置为若检测到节点部署异常时，对所述部署的云应用系统进行自动回退卸载处理。
退回模块配置为若检测到节点部署异常时，对所述部署的云应用系统进行自动回退卸载处理，且卸载过程也依据节点的优先级进行先后或者并行卸载。
在本示例性实施例中，通过应用上述退回模块能够提升部署过程对异常状况的处理效率。
需要说明的是，在硬件实现上，以上第一检测模块、第一生成模块、部署模块、第二检测模块、第二生成模块、第一部署单元、第二部署单元、生成单元、生成子单元等模块或单元可以以硬件形式内嵌于或独立于部署云应用系统的装置中，也可以以软件形式存储于部署云应用系统的装置的存储器中，以便于处理器调用并执行以上各个模块对应的操作。该处理器可以为中央处理单元(CPU)、微处理器、单片机等。
参照图10，图10是示出了根据本公开的示例性实施例的硬件运行环境的设备结构示意图。
根据本公开的示例性实施例的部署云应用系统的设备可以是PC，也可以 是智能手机、平板电脑、便携计算机等终端设备。
如图10所示，部署云应用系统的设备可以包括：处理器1001(例如CPU)、网络接口1002、存储器1003。这些组件之间的连接通信可以通过通信总线实现。网络接口1002可以包括标准的有线接口、无线接口(如WI-FI接口)。存储器1003可以是高速RAM存储器，也可以是稳定的存储器(non-volatile memory)，例如磁盘存储器。存储器1003还可以是独立于前述处理器1001的存储装置。
作为选择，部署云应用系统的设备还可以包括用户接口、摄像头、RF(Radio Frequency，射频)电路、传感器、音频电路、WiFi模块等等。用户接口可以包括显示屏(Display)、输入单元比如键盘(Keyboard)，作为选择，用户接口还可以包括标准的有线接口、无线接口。
本领域技术人员可以理解，图10中示出的根据本公开的示例性实施例的部署云应用系统的设备结构并不构成对本公开的部署云应用系统的设备的限定，本公开的部署云应用系统的设备可以包括比图示更多或更少的部件，或者某些部件的组合，或者不同的部件布置。
如图10所示，作为一种计算机存储介质的存储器1003可以包括操作系统、网络通信模块以及部署云应用系统程序。在根据本公开的示例性实施例中，操作系统是管理和控制部署云应用系统的设备硬件与软件资源的程序，其支持网络通信模块、部署云应用系统程序以及其他程序或软件的运行，其中网络通信模块可以用于管理和控制网络接口1002。
在图10所示的部署云应用系统的设备中，网络接口1002主要用于连接服务器，与服务器进行数据通信，所述服务器中存储有部署云应用系统的程序；而处理器1001可以用于执行存储器1003中存储的部署云应用系统的程序，以实现在上文第一示例性实施例至第五示例性实施例中描述的部署云应用系统的方法的各步骤，例如步骤S10、S20、S30、S2011、S2012、S2020等。
以上示出的本公开的示例性实施例仅用于说明的目的，并非因此限制本公开的专利范围，凡是利用本公开说明书及附图内容所作的等效结构或等效 流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本公开的专利保护范围内。

Claims (12)

  1. 一种部署云应用系统的方法，所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点，所述方法包括如下步骤：
    当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，并获取所述拓扑格式描述文件中的节点之间的节点关系；
    基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；以及
    基于所述分步部署流程，调用各节点的对应部署脚本对各节点执行串行或并行部署操作。
  2. 如权利要求1所述的部署云应用系统的方法，其中，所述方法还包括如下步骤：
    当检测到卸载云应用系统的请求时，获取与待卸载云应用系统对应的拓扑格式描述文件中的节点、节点关系；以及
    基于与该待卸载云应用系统对应的拓扑格式描述文件中的节点、节点关系，生成与该待卸载云应用系统对应的具有串并行关系的分步卸载流程，根据所述分步卸载流程完成整个云应用系统的卸载。
  3. 如权利要求1所述的部署云应用系统的方法，其中，所述节点关系包括节点包含关系和节点连接关系，所述节点包含关系为第一节点与包含在所述第一节点中的第二节点之间的关系，所述节点连接关系为第三节点和与所述第三节点连接的第四节点之间的连接关系，
    所述基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程的步骤包括：
    对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为所述节点包含关系时，根据第一预置规则生成先部署所述第一节点、后部署所述第二节点的包含部署流程；
    对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为所述节点连接关系时，根据第二预置规则生成同时部署所述第三节点与所述第 四节点的连接部署流程；以及
    根据所述包含部署流程与所述连接部署流程生成所述具有串并行关系的分步部署流程。
  4. 如权利要求3所述的部署云应用系统的方法，其中，当所述节点关系为所述节点包含关系时，在根据第一预置规则生成先部署所述第一节点、后部署所述第二节点的包含部署流程之后，所述基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程的步骤还包括：
    生成这样的连接处理流程：在检测到所述第三节点与所述第四节点都部署完成后，所述第三节点向所述第四节点发起连接请求，所述第四节点接收并处理所述连接请求。
  5. 如权利要求4所述的部署云应用系统的方法，其中，所述根据所述包含部署流程与所述连接部署流程生成所述具有串并行关系的分步部署流程的步骤包括：
    根据所述包含部署流程、所述连接部署流程、所述连接处理流程生成所述具有串并行关系的分步部署流程。
  6. 如权利要求1-5中任一项所述的部署云应用系统的方法，所述方法还包括如下步骤：
    当检测到节点部署异常时，对部署的云应用系统进行自动回退卸载处理。
  7. 一种部署云应用系统的装置，所述云应用系统包括拓扑格式描述文件，所述拓扑格式描述文件包括节点，所述装置包括：
    第一检测模块，其配置为当检测到所述拓扑格式描述文件导入时，解析所述拓扑格式描述文件，并获取所述拓扑格式描述文件中的节点之间的节点关系；
    第一生成模块，其配置为基于所述节点关系，对各节点进行序列化处理，并生成具有串并行关系的分步部署流程；以及
    部署模块，其配置为基于所述分步部署流程，调用各节点的对应部署脚 本对各节点执行串行或并行部署操作。
  8. 如权利要求7所述的部署云应用系统的装置，所述装置还包括：
    第二检测模块，其配置为当检测到卸载云应用系统的请求时，获取与待卸载云应用系统对应的拓扑格式描述文件中的节点、节点关系；以及
    第二生成模块，其配置为基于与该待卸载云应用系统对应的拓扑格式描述文件中的节点、节点关系，生成与该待卸载云应用系统对应的具有串并行关系的分步卸载流程，根据所述分步卸载流程完成整个云应用系统的卸载。
  9. 如权利要求7所述的部署云应用系统的装置，其中，所述节点关系包括节点包含关系和节点连接关系，所述节点包含关系为第一节点与包含在所述第一节点中的第二节点之间的关系，所述节点连接关系为第三节点和与所述第三节点连接的第四节点之间的连接关系，
    所述第一生成模块包括：
    第一部署单元，其配置为对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为所述节点包含关系时，根据第一预置规则生成先部署所述第一节点、后部署所述第二节点的包含部署流程；
    第二部署单元，其配置为对所述拓扑格式描述文件中的节点关系进行分析，当所述节点关系为所述节点连接关系时，根据第二预置规则生成同时部署所述第三节点与所述第四节点的连接部署流程；以及
    生成单元，其配置为根据所述包含部署流程与所述连接部署流程生成所述具有串并行关系的分步部署流程。
  10. 如权利要求9所述的部署云应用系统的装置，其中，所述第一生成模块还包括：
    连接处理单元，其配置为生成这样的连接处理流程：在检测到所述第三节点与所述第四节点都部署完成后，所述第三节点向所述第四节点发起连接请求，所述第四节点接收并处理所述连接请求。
  11. 如权利要求10所述的部署云应用系统的装置，其中，所述生成单元 包括：
    生成子单元，其配置为根据所述包含部署流程、所述连接部署流程、所述连接处理流程生成所述具有串并行关系的分步部署流程。
  12. 如权利要求7-11中任一项所述的部署云应用系统的装置，所述装置还包括：
    退回模块，其配置为当检测到节点部署异常时，对部署的云应用系统进行自动回退卸载处理。
PCT/CN2018/076837 2017-05-04 2018-02-14 部署云应用系统的方法及装置 WO2018201778A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710311255.3 2017-05-04
CN201710311255.3A CN108809683B (zh) 2017-05-04 2017-05-04 部署云应用系统的方法及装置

Publications (1)

Publication Number Publication Date
WO2018201778A1 true WO2018201778A1 (zh) 2018-11-08

Family

ID=64016388

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076837 WO2018201778A1 (zh) 2017-05-04 2018-02-14 部署云应用系统的方法及装置

Country Status (2)

Country Link
CN (1) CN108809683B (zh)
WO (1) WO2018201778A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112527251A (zh) * 2020-11-30 2021-03-19 北京百度网讯科技有限公司 业务处理方法、装置、电子设备及存储介质
CN113220283A (zh) * 2021-05-10 2021-08-06 国网陕西省电力公司信息通信公司 一种基于云编排的物联app开发系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366186B (zh) * 2019-06-06 2022-04-12 佛山职业技术学院 一种传感器执行器网络应用程序的部署方法及系统
CN110347422B (zh) * 2019-06-27 2021-03-09 华云数据控股集团有限公司 一种应用编排方法、装置及电子设备
CN112162756B (zh) * 2020-09-17 2022-04-26 武汉联影医疗科技有限公司 软件产品的部署方法、装置、计算机设备和存储介质
CN114816789A (zh) * 2022-03-28 2022-07-29 阿里巴巴（中国）有限公司 基于云应用的文件处理方法、电子设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104583945A (zh) * 2013-08-13 2015-04-29 华为技术有限公司 一种应用升级方法、装置
WO2015065382A1 (en) * 2013-10-30 2015-05-07 Hewlett-Packard Development Company, L.P. Instantiating a topology-based service using a blueprint as input
CN105051687A (zh) * 2013-05-31 2015-11-11 华为技术有限公司 应用部署方法和设备
US9195453B1 (en) * 2014-06-10 2015-11-24 International Business Machines Corporation Remediation of known defects and vulnerabilities in cloud application packages

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101527645A (zh) * 2008-03-03 2009-09-09 华为技术有限公司 网络拓扑信息收集方法、系统及相关设备
CN102223398B (zh) * 2011-05-30 2013-09-11 北京航空航天大学 一种部署在云计算环境中部署服务的方法
CN102404381A (zh) * 2011-09-02 2012-04-04 西安交通大学 一种云计算环境下基于工作流的软件部署系统及部署方法
CN105449676B (zh) * 2015-12-30 2018-02-06 广东电网有限责任公司惠州供电局 配电网区域节点网络生成方法与系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105051687A (zh) * 2013-05-31 2015-11-11 华为技术有限公司 应用部署方法和设备
CN104583945A (zh) * 2013-08-13 2015-04-29 华为技术有限公司 一种应用升级方法、装置
WO2015065382A1 (en) * 2013-10-30 2015-05-07 Hewlett-Packard Development Company, L.P. Instantiating a topology-based service using a blueprint as input
US9195453B1 (en) * 2014-06-10 2015-11-24 International Business Machines Corporation Remediation of known defects and vulnerabilities in cloud application packages

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112527251A (zh) * 2020-11-30 2021-03-19 北京百度网讯科技有限公司 业务处理方法、装置、电子设备及存储介质
CN113220283A (zh) * 2021-05-10 2021-08-06 国网陕西省电力公司信息通信公司 一种基于云编排的物联app开发系统
CN113220283B (zh) * 2021-05-10 2024-05-14 国网陕西省电力公司信息通信公司 一种基于云编排的物联app开发系统

Also Published As

Publication number Publication date
CN108809683B (zh) 2022-07-15
CN108809683A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
WO2018201778A1 (zh) 部署云应用系统的方法及装置
US9590872B1 (en) Automated cloud IT services delivery solution model
US10127069B2 (en) Methods and apparatus to automatically configure monitoring of a virtual machine
WO2017045424A1 (zh) 一种应用程序部署系统及部署方法
US9311161B2 (en) Automatically configured management service payloads for cloud IT services delivery
US9386079B2 (en) Method and system of virtual desktop infrastructure deployment studio
US10275258B2 (en) Systems and methods for enhancing the availability of multi-tier applications on cloud computing platforms
US9274843B2 (en) Multi-redundant switchable process pooling for cloud it services delivery
US11861341B2 (en) Node selection method and apparatus
US9602599B2 (en) Coordinating application migration processes
US9612815B1 (en) Method and tool for automating deployment of reference implementation architectures for pre-integrated multi-product solutions
CN106970880B (zh) 一种分布式自动化软件测试方法及系统
US8918760B2 (en) Test script generation for application image validation
US9053236B1 (en) Automated directory services test setup utility
CN110389903B (zh) 测试环境部署方法和装置、电子设备和可读存储介质
WO2017041486A1 (zh) 一种实现集群部署的方法及装置
US20130152074A1 (en) Method for automatic consecutive installing operating systems
CN109298868B (zh) 测绘影像数据处理软件智能动态部署及卸载方法
CN111198695A (zh) 微服务治理管理平台的自动化部署方法和电子设备
US8645766B2 (en) Serialized error injection into a function under test
WO2017041499A1 (zh) 一种软件升级方法、系统和计算机可读存储介质
US20160253501A1 (en) Method for Detecting a Unified Extensible Firmware Interface Protocol Reload Attack and System Therefor
US8938490B2 (en) System and method for accessing mainframe system automation from a process automation application
CN111176818A (zh) 分布式预测的方法、装置、系统、电子设备及存储介质
US20240045733A1 (en) Method and apparatus for deploying deep learning system

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: 18794416

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18794416

Country of ref document: EP

Kind code of ref document: A1