Execution method and device for arranging nodes and electronic equipment

Abstract

The invention discloses an execution method and device for arranging nodes and electronic equipment. The method comprises the steps of obtaining input parameters of arrangement nodes in a task to be arranged; determining a parameter configuration template from the configuration information of the input parameters; acquiring a context parameter value in the parameter configuration template; determining a parameter value of a parameter corresponding to the context parameter in a parameter configuration template according to the context parameter value, and taking the parameter value of the parameter corresponding to the context parameter as a parameter value of an input parameter; and determining target configuration information of the arrangement node according to the parameter value of the input parameter, and executing the arrangement node according to the target configuration information. The technical problems that for mapping of complex parameters in an arrangement task, parameter processing nodes need to be additionally added in related technologies to achieve parameter adaptation between different arrangement nodes, flow configuration is complex, and execution efficiency is low are solved.

Description

Technical Field

[0001] The present application relates to the field of network management technology, and in particular to a method, device and electronic device for executing an orchestration node. Background Art

[0002] The mapping of context parameter values ​​in orchestration tasks is very frequent. The relevant technology only supports the mapping operations of simple parameters, and does not support complex situations such as JSON (JavaScript Object Notation), XML (eXtensible Markup Language), and nested parameters. As a result, additional parameter processing nodes need to be added, which increases the number of orchestration process nodes and the workload of script writing.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide an execution method, device and electronic device for an orchestration node to at least solve the mapping of complex parameters in the orchestration task. The related technology requires additional parameter processing nodes to achieve parameter adaptation between different orchestration nodes, and the process configuration is complex and the execution efficiency is low. Technical problems.

[0005] According to one aspect of an embodiment of the present application, a method for executing an orchestration node is provided, comprising: obtaining input parameters of an orchestration node in a task to be orchestrated, wherein the input parameters include output parameters of a previous orchestration node of the orchestration node in the task to be orchestrated; determining a parameter configuration template from configuration information of the input parameters, wherein the parameter configuration template is used to configure the output parameters as input parameters; obtaining context parameter values ​​in the parameter configuration template, wherein context parameters corresponding to the context parameter values ​​include parameters transmitted between different orchestration nodes in the task to be orchestrated; determining parameter values ​​of parameters corresponding to the context parameters in the parameter configuration template according to the context parameter values, and using the parameter values ​​of the parameters corresponding to the context parameters as parameter values ​​of the input parameters; determining target configuration information of the orchestration node according to the parameter values ​​of the input parameters, and executing the orchestration node according to the target configuration information.

[0006] In some embodiments of the present application, obtaining a context parameter value in a parameter configuration template includes: obtaining a first value expression set contained in the parameter configuration template; obtaining a first value expression from the first value expression set, wherein the first value expression is any one of the value expressions in the value expression set; parsing the first value expression to obtain a variable name of a context parameter contained in the first value expression; and obtaining a context parameter value corresponding to the context parameter from the context information according to the variable name of the context parameter.

[0007] In some embodiments of the present application, the parameter value of the parameter corresponding to the context parameter in the parameter configuration template is determined according to the context parameter value, and the parameter value of the parameter corresponding to the context parameter is used as the parameter value of the input parameter, including: obtaining a second value expression set contained in the parameter configuration template, wherein the value expression in the second value expression set is used to configure the parameter value of the sub-parameter of the input parameter; obtaining a second value expression in the second value expression set, wherein the second value expression includes the outermost value expression of the sub-parameter of the input parameter; when the second value expression does not contain an inner value expression, determining the parameter value of the sub-parameter corresponding to the second value expression according to the second value expression and the context parameter value corresponding to the variable name of the context parameter in the second value expression; when the second value expression contains an inner value expression, determining the dependency relationship between each value expression in the second value expression, and determining the parameter value of the sub-parameter corresponding to the second value expression according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter in each value expression in the second value expression; replacing the second value expression with the parameter value of the sub-parameter corresponding to the second value expression to obtain the parameter value of the input parameter.

[0008] In some embodiments of the present application, the parameter value of the sub-parameter corresponding to the second value-taking expression is determined according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter in each value-taking expression in the second value-taking expression, including: obtaining a third value-taking expression from the inner value-taking expression set where the inner value-taking expression is located, wherein the third value-taking expression includes the innermost value-taking expression; starting from the third value-taking expression, according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter respectively contained in the value-taking expressions in the inner value-taking expression set, calculating the result value of the value-taking expression in the inner value-taking expression set layer by layer; determining the parameter value of the sub-parameter corresponding to the second value-taking expression according to the result value of the value-taking expression in the inner value-taking expression set.

[0009] In some embodiments of the present application, when the second value expression includes an inner value expression, the dependency relationship between each value expression in the second value expression is determined, including: using a template value language to parse the second value expression to obtain variable names of multiple context parameters included in the second value expression; and determining the dependency relationship between multiple value expressions corresponding to the variable names of the multiple context parameters according to the dependency relationship between the variable names of the multiple context parameters.

[0010] In some embodiments of the present application, when the value expression is a numerical operation expression, the numerical value corresponding to the numerical variable in the value expression is obtained, and the numerical value is used as the result value corresponding to the value expression; when the value expression is a character operation expression, the character corresponding to the character variable in the value expression is obtained, and the character is used as the result value corresponding to the value expression; when the value expression is an object operation expression, the object attribute values ​​corresponding to the object variables and attribute variables in the value expression are obtained, and the object attribute values ​​are used as the result value corresponding to the value expression; when the value expression is an array operation expression, the index value of the index variable corresponding to the array variable in the value expression is obtained, and the index value is used as the result value corresponding to the value expression.

[0011] In some embodiments of the present application, after determining the parameter value of the input parameter according to the context parameter value and the template expression, the method further includes: obtaining parameter specification information of the input parameter of the orchestration node, wherein the parameter specification information includes at least one of the following: parameter type, parameter value range, and parameter integrity; verifying the input parameter according to the parameter specification information; if the verification fails, re-determining the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, to obtain the parameter value of the input parameter.

[0012] According to another aspect of an embodiment of the present application, there is also provided a device for executing an orchestration node, comprising: a first acquisition module, used to acquire input parameters of an orchestration node in a task to be orchestrated; a first determination module, used to determine a parameter configuration template from configuration information of the input parameters; a second acquisition module, used to acquire context parameter values ​​in the parameter configuration template; a second determination module, used to determine parameter values ​​of parameters corresponding to the context parameters in the parameter configuration template according to the context parameter values, and use the parameter values ​​of the parameters corresponding to the context parameters as parameter values ​​of the input parameters; and an execution module, used to determine target configuration information of the orchestration node according to the parameter values ​​of the input parameters, and execute the orchestration node according to the target configuration information.

[0013] According to another aspect of the embodiments of the present application, an electronic device is provided, including: a memory and a processor, the memory being used to store program instructions; the processor being connected to the memory and being used to execute the execution method of the above-mentioned orchestration node.

[0014] According to another aspect of an embodiment of the present application, a non-volatile storage medium is provided, which includes a stored computer program, wherein a device where the non-volatile storage medium is located executes the above-mentioned execution method of the orchestration node by running the computer program.

[0015] According to another aspect of the embodiments of the present application, a computer program product is provided, including computer instructions, which implement the execution method of the orchestration node when executed by a processor.

[0016] In an embodiment of the present application, the output parameters of the previous orchestration node are mapped and converted by using a parameter configuration template in the orchestration node to obtain the target configuration information of the orchestration node, and the orchestration node is executed according to the target configuration information. Since the target configuration information can be obtained in the orchestration node, there is no need to add additional parameter processing nodes for parameter mapping and conversion. Therefore, the purpose of reducing the number of parameter processing nodes to reduce the complexity of process configuration can be achieved, thereby achieving the technical effect of improving the execution efficiency of the orchestration task and reducing the orchestration errors, and then solving the technical problem that the mapping of complex parameters in the orchestration task requires additional parameter processing nodes to achieve parameter adaptation between different orchestration nodes, the process configuration is complex, and the execution efficiency is low. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal for an execution method of an orchestration node according to an embodiment of the present application;

[0019] Figure 2 is a flowchart of an execution method of an orchestration node according to an embodiment of the present application;

[0020] Figure 3 is a parameter configuration template parsing flow chart of a method for executing an orchestration node according to an embodiment of the present application;

[0021] Figure 4 It is a parameter configuration template parsing logic diagram of a method for executing an orchestration node according to an embodiment of the present application;

[0022] Figure 5 is a flowchart of an orchestration engine executing a method for executing an orchestration node according to an embodiment of the present application;

[0023] Figure 6 It is a schematic diagram of the implementation principle of the arrangement parameter configuration according to the relevant technology;

[0024] Figure 7 It is a schematic diagram of the implementation principle of the arrangement parameter configuration according to the embodiment of the present application;

[0025] Figure 8 It is a structural diagram of an apparatus for orchestrating node execution according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0029] Orchestration Parameters: In the process of automated orchestration, they are used to define and manage the configuration parameters of network resources and services, including IP addresses, port numbers, protocol types, etc. They are transmitted and converted between different nodes in the orchestration process to ensure the smooth deployment and operation of network services.

[0030] Context Parameters: In the process of automated orchestration, data parameters used to describe the current operating environment or status, including complex data structures such as object properties, arrays, and object arrays. They are passed between different nodes to ensure that each node can correctly understand and process the current operating context.

[0031] Atomic Capability: refers to the smallest, indecomposable operating unit in the system. It is an independent, self-contained unit that can perform a specific task or provide a specific service.

[0032] In the atomic capability instruction arrangement, the mapping of parameters between the atomic capability instructions requires the analysis, conversion, and configuration of parameters. Adding nodes to adapt parameters between different atomic capability instructions results in too many nodes, complex process configuration, reduced execution efficiency, and easy arrangement errors. In order to solve the above technical problems, the embodiments of the present application provide corresponding solutions, which are described in detail below.

[0033] The execution method embodiment of the orchestration node provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal for implementing an execution method of an orchestration node. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0034] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0035] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the execution method of the orchestration node in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the execution method of the orchestration node described above is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0036] The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0037] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0038] It should be noted that, in some optional embodiments, the above Figure 1 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0039] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of an execution method for orchestrating a node. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0040] Figure 2 is a flowchart of a method for executing an orchestration node according to an embodiment of the present application, such as Figure 2As shown, the method comprises the following steps:

[0041] Step S202: obtaining input parameters of an orchestration node in the task to be orchestrated, wherein the input parameters include output parameters of a previous orchestration node of the orchestration node in the task to be orchestrated.

[0042] In the above step S202, the task to be orchestrated refers to a set of ordered atomic capability instructions, which are designed to complete specific network functions or business processes. The task to be orchestrated is usually defined by network management personnel or automation tools by configuring the orchestration engine. For example, the goal of an orchestration task is to automatically configure a new virtual network environment. The orchestration task may include the following atomic capability instructions: verify user permissions, allocate IP addresses, create virtual machines, configure firewall rules, start virtual machines, etc. These atomic capability instructions are executed in sequence to complete the automatic configuration of the network environment.

[0043] An orchestration node is an operation unit in an orchestration task. Each orchestration node represents the execution of an atomic capability instruction. An orchestration node is a node in the orchestration task execution process. It can be a subtask obtained by splitting the orchestration task. Each subtask is executed in sequence to complete the task to be orchestrated. An orchestration node can be an instruction to call a specific API, execute a specific script, or interact with a specific device. For example, in a virtual network environment configuration task, "allocate IP address" can be used as an orchestration node. The orchestration node can use the atomic capability instruction to select a suitable IP address from the IP address pool and record this information as an output parameter for subsequent nodes to use.

[0044] Input parameters are the orchestration parameters required by the orchestration node when executing, which are used to guide the execution of atomic capability instructions, including but not limited to the output parameters of the previous node, environment variables, process startup parameters or node built-in parameters, etc. For example, for the orchestration node of "Configure Network Interface", its input parameters may include: interface name, IP address, subnet mask, gateway address, etc. Among them, the interface name may be static configuration information, while the IP address, subnet mask, gateway address, etc. include the output results from the previous orchestration node (such as the orchestration node of "Assign Network Address").

[0045] In the orchestration process, the orchestration nodes transfer parameters to achieve data flow and status update. For example, the output parameters of the "Verify User Permissions" orchestration node are user ID and permission status, which will be used as input parameters of the "Allocation of IP Addresses" orchestration node to guide the allocation of IP addresses.

[0046] Step S204: determining a parameter configuration template from the configuration information of the input parameters, wherein the parameter configuration template is used to configure the output parameters as input parameters.

[0047] In the above step S204, the configuration information refers to the specific settings of the input and output parameters defined for each orchestration node (i.e., atomic capability instruction) in the orchestration process, including detailed descriptions of the parameter name, type, source, and how to format or process it. Configuration information is usually set according to specific business requirements and the operating environment of the system, and it directly determines the execution logic of the orchestration process and the direction of the data flow. For example, the orchestration process includes an orchestration node A, whose input parameters include wsnbr, WsCode, netInfo, etc. The configuration information of these input parameters is as follows:

[0048] (1)wsnbr: from the environment variable, type is string.

[0049] (2)WsCode: dynamically generated by the runtime function bpceFunc.createCode, the type is string.

[0050] (3)netInfo.trunkName: Output from the previous node, of type string.

[0051] Parameter configuration templates are predefined rules or syntax used to convert and map parameters of various data types in the orchestration process, including but not limited to basic data types such as strings, numbers, null values, dates, and complex data types such as JSON (JavaScript Object Notation), XML (eXtensible Markup Language), or YAML (YAML Ain't Markup Language) formats. Parameter configuration templates can also perform subsequent calculations on the extracted data, such as numerical operations, string concatenation, conditional screening of arrays, conversion of array objects to simple type arrays, extraction of values ​​at specific locations or ranges in arrays, and function call calculations.

[0052] The parameter configuration template can be used in the configuration information of the orchestration node, for example, to directly reference or calculate the context parameter to map the corresponding parameter value to the input parameter of the orchestration node (i.e., the atomic capability instruction). Since each orchestration node can include multiple input parameters, a separate parameter configuration template can be set for each input parameter, or a parameter configuration template can be uniformly configured for all input parameters.

[0053] In some embodiments, the parameter configuration template can be determined in the following manner: analyzing the input parameter requirements of the atomic capability instruction interface, obtaining the necessary parameter set and the source of the parameters, for example, from the output of the previous orchestration node or the orchestration process context; determining the operation method of extracting data from the output parameters or context parameters and converting them into the required input parameter format, for example, it can include data screening, format conversion, numerical calculation, string concatenation and other operations; executing the above operation method to create a parameter configuration template for the input parameter, for example, the parameter configuration template can be created according to a preset template value language.

[0054] Step S206, obtaining context parameter values ​​in the parameter configuration template, wherein the context parameters corresponding to the context parameter values ​​include parameters transmitted between different orchestration nodes in the task to be orchestrated.

[0055] In the above step S206, context parameters refer to data parameters transmitted and used between various orchestration nodes in the orchestration process, including various data types such as object attributes, arrays, strings, etc. Some context parameters will change dynamically at different stages of the orchestration process. They store the intermediate results or status information of the execution of the orchestration process and can be used for the execution of subsequent orchestration nodes.

[0056] The context parameter value refers to the actual value or content of the context parameter at a specific moment, that is, the specific performance of the context parameter at a certain point in the orchestration process. The context parameter value contains the output and input information of all nodes when the orchestration process is executed to the current point, including but not limited to environment variables, process startup parameters, node execution return parameters and node built-in parameters. These parameter values ​​constitute the overall context of the orchestration execution process.

[0057] In some embodiments, the parameter configuration template can be parsed to obtain the context parameters contained therein, and the specific parameter values ​​of the context parameters can be obtained from the overall context of the orchestration execution process. The parameter values ​​are loaded into a local context, and the local context is used to parse and calculate the parameter configuration template, which includes all referenced variables (i.e., context parameters) in the parameter configuration template and their corresponding values, ensuring that the parameters used when executing the orchestration node (i.e., atomic capability instructions) are the latest and most accurate values, while avoiding the need to repeatedly configure the parameter mapping logic in the orchestration process, thereby simplifying the process configuration and improving execution efficiency.

[0058] Step S208: determining the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and taking the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter.

[0059] In the above step S208, before the orchestration node is executed, the orchestration engine will parse the parameter configuration template and associate the parameter configuration template with the context parameters to obtain the parameter values ​​of the input parameters of the orchestration node.

[0060] In some embodiments, when an input parameter includes multiple sub-parameters, a value expression can be configured for each sub-parameter in which a parameter value needs to be dynamically obtained or calculated, and the value expression is used to determine the parameter value of the sub-parameter according to the context parameter value. According to the context parameter value and the value expression, the parameter values ​​corresponding to the sub-parameters of the input parameter (i.e., the parameters corresponding to the context parameter in the parameter configuration template) can be determined respectively, and finally the parameter value of the input parameter is obtained.

[0061] Step S210, determining target configuration information of the orchestration node according to the parameter value of the input parameter, and executing the orchestration node according to the target configuration information.

[0062] In the above step S210, the target configuration information is the actual parameter configuration required for the orchestration node to execute. In some embodiments, the parameter values ​​of the input parameters can all be dynamically parsed and converted by the parameter configuration template, that is, when the orchestration process is executed to the orchestration node, the parameter value of the context parameter is obtained in real time through the parameter configuration template; it can also be partially parsed and converted through the parameter configuration template, and the remaining part is statically set (i.e., pre-set) to jointly constitute the parameter value of the input parameter of the orchestration node. After determining the parameter value of the input parameter, in some embodiments, the parameter value of the input parameter can be used to update or fill in the corresponding parameter in the configuration information of the orchestration node to obtain the target configuration information of the orchestration node.

[0063] Through the above steps S202 to S210, the output parameters of the previous orchestration node are mapped and converted by using the parameter configuration template in the orchestration node to obtain the target configuration information of the orchestration node, and the orchestration node is executed according to the target configuration information, thereby achieving the purpose of reducing the number of parameter processing nodes to reduce the complexity of process configuration, thereby achieving the technical effect of improving the execution efficiency of the orchestration task, and further solving the technical problems that the mapping of complex parameters in the orchestration task requires additional parameter processing nodes to achieve parameter adaptation between different orchestration nodes, the process configuration is complex, and the execution efficiency is low.

[0064] In the case where the parameter configuration template of the input parameter contains a value expression, the context parameter value in the parameter configuration template can be obtained according to the following steps: obtain a first value expression set contained in the parameter configuration template; obtain a first value expression from the first value expression set, wherein the first value expression is any value expression in the value expression set; parse the first value expression to obtain the variable name of the context parameter contained in the first value expression; and obtain the context parameter value corresponding to the context parameter from the context information according to the variable name of the context parameter.

[0065] A value expression is a formula or instruction for extracting or calculating data from context parameters during orchestration parameter configuration. It can contain variable references, data sources, and possible calculation logic, and is used to extract required values ​​from existing data structures, or to calculate and convert these values. For example, extracting the value of a field in a JSON object, adding two values, etc. A value expression can be embedded in the parameter configuration template of the input parameter of an orchestration node to dynamically obtain or calculate the actual parameter value of the input parameter.

[0066] In some embodiments, the parameter configuration template includes one or more value expressions, and the first value expression set is composed of all value expressions in the parameter configuration template of the input parameter. Each value expression may include one or more context parameters (i.e., variable names of context parameters), and the context parameter value is obtained from the local context information through the variable name of the context parameter.

[0067] When implementing parameter mapping of complex structures, nested value expressions can be set in the parameter configuration template to dynamically configure input parameters based on multi-level context information. In order to ensure the accuracy of the input parameter configuration, when the context parameter value is associated with the parameter configuration template to obtain the parameter value of the input parameter, the following steps can be performed: obtain a second value expression set contained in the parameter configuration template, wherein the value expressions in the second value expression set are used to configure the parameter values ​​of the sub-parameters of the input parameter; obtain a second value expression in the second value expression set, wherein the second value expression includes the outermost value expression of the sub-parameter of the input parameter; when the second value expression does not contain an inner value expression, determine the parameter value of the sub-parameter corresponding to the second value expression according to the second value expression and the context parameter value corresponding to the variable name of the context parameter in the second value expression; when the second value expression contains an inner value expression, determine the dependency relationship between each value expression in the second value expression, and determine the parameter value of the sub-parameter corresponding to the second value expression according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter in each value expression in the second value expression; replace the second value expression with the parameter value of the sub-parameter corresponding to the second value expression to obtain the parameter value of the input parameter.

[0068] In the above steps, the second value expression set is the same as the first value expression set, and is composed of all value expressions in the parameter configuration template of the input parameter. In some embodiments, the value expression can be used to configure the parameter value of a sub-parameter of the input parameter, which is a sub-parameter that needs to dynamically obtain or calculate the parameter value.

[0069] The second value expression can be the outermost value expression of the sub-parameter, that is, the value expression whose result value corresponds to the parameter value of the sub-parameter. The second value expression does not contain the inner value expression, that is, the value expression of the sub-parameter (that is, the second value expression) is a non-nested expression, and the parameter value of the sub-parameter can be directly obtained according to the context parameter value and the value expression.

[0070] The inner layer value expression, i.e., the value expression of the sub-parameter (i.e., the second value expression), contained in the second value expression is a nested expression, and the dependency relationship between the value expressions in the nested value expression can be determined. The dependency relationship is used to indicate the mutual influence or sequence of different value expressions during calculation, and may include direct dependency, indirect dependency, synchronous dependency, and hierarchical dependency:

[0071] (1) Direct dependency: A value expression directly uses the result of another value expression as part of its calculation. For example, if the result of value expression A is used as a parameter by value expression B, then value expression B depends on expression A.

[0072] (2) Indirect dependency: A value expression indirectly uses the calculation result of another value expression through a series of intermediate value expressions. For example, if value expression C depends on value expression D, and value expression D depends on value expression E, then value expression C indirectly depends on value expression E.

[0073] (3) Synchronous dependency: Two or more value expressions depend on the value of the same context parameter, but there is no direct usage relationship between them. In this case, the values ​​of these value expressions can be calculated in parallel, but it is necessary to ensure that the value of the context parameter has been correctly assigned before calculation.

[0074] (4) Hierarchical dependency: When dealing with nested value expressions, the value expressions may depend on the values ​​of the same or different context parameters at different levels. For example, the outer value expression depends on the calculation result of the inner value expression, or the inner value expression depends on the calculation result of the deeper value expression.

[0075] In order to determine the dependency relationship between each value expression in a nested value expression (second value expression), the following steps can be performed: use a template value language to parse the nested value expression to obtain the variable names of multiple context parameters contained in the nested value expression; determine the dependency relationship between multiple value expressions corresponding to the variable names of multiple context parameters based on the dependency relationship between the variable names of multiple context parameters.

[0076] The template value language corresponds to the value expression, which refers to the expression language that extracts and converts data from context parameters during the parameter configuration process of the orchestration node. It can be used to embed value expressions in parameter configuration templates. The template value language can include elements such as variable reference syntax, data type processing, and function calls, so that complex context parameters can be flexibly processed during the orchestration process.

[0077] In some embodiments, the dependencies may be determined by:

[0078] (1) Using the template value language to perform syntax analysis on the second value expression, identify the location and content of the inner value expression, and construct an abstract syntax tree (AST) of the value expression;

[0079] (2) Based on the AST, analyze the usage of context parameter variables in each value expression, identify which variables are the results of other expressions, and thus determine direct and indirect dependencies. At the same time, identify which expressions can be calculated in parallel and determine synchronization dependencies.

[0080] (3) Identify the hierarchical structure of value expressions and determine which value expressions are at the same level and which are at different levels, so as to facilitate hierarchical dependency analysis in hierarchical order.

[0081] (4) Determine the dependency relationship between each value expression in the second value expression based on the above direct dependency, indirect dependency, synchronous dependency and hierarchical dependency analysis results.

[0082] After determining the dependency relationship between each value expression in the nested value expression (i.e., the second value expression), the parameter value of the sub-parameter corresponding to the nested value expression can be determined by the following steps, specifically: obtaining a third value expression from the inner value expression set where the inner value expression is located, wherein the third value expression includes the innermost value expression; starting from the third value expression, according to the dependency relationship and the context parameter values ​​corresponding to the variable names of the context parameters respectively contained in the value expressions in the inner value expression set, the result values ​​of the value expressions in the inner value expression set are calculated layer by layer in sequence; and determining the parameter value of the sub-parameter corresponding to the second value expression according to the result value of the value expression in the inner value expression set.

[0083] In the above steps, the inner value expressions are all value expressions except the outermost value expression, and the innermost value expression is the expression in the inner value expression set that does not contain a value expression, that is, the smallest separable unit in the nested value expression.

[0084] In some embodiments, the tree structure of the value expression (i.e., the dependency relationship between each value expression in the nested value expression) can be traversed in depth first, starting from the leaf node (i.e., the innermost value expression), the variable name of the context parameter in the value expression is obtained, the variable name is matched from the local context according to the variable name level of the context parameter to obtain the value of the context parameter, and then the result value of the value expression is calculated through the value expression. The variable name level refers to the hierarchical relationship of the variable name in the nested structure, which can include top-level parameters (i.e., variables defined directly in the context, not nested in other variables) and sub-level parameters (i.e., variables nested in other variables, which can be accessed through paths). Different variable name levels can be separated by dots (.). For example, dots (.) can be used to represent nested attributes or fields. In the value expression {{user.address.street}}, user is the top-level parameter, address is the sub-level parameter of user, and street is the sub-level parameter of address.

[0085] After calculating the result value of each inner value expression layer by layer, the result value of the second value expression (ie, the nested value expression) can be calculated, and the result value of the second value expression is the parameter value of its corresponding sub-parameter.

[0086] In some embodiments, since the initial value of the sub-parameter of the input parameter in the parameter configuration template is represented by a value expression, after the parameter value of the sub-parameter is calculated, the parameter value of the sub-parameter can be used to replace the corresponding value expression to obtain the actual parameter value of the input parameter.

[0087] Figure 3 is a parameter configuration template parsing flow chart according to an embodiment of the present application, such as Figure 3 As shown in the figure, the process mainly includes the following four steps:

[0088] (1) Node parameter template extraction: Extract the value expression in the parameter configuration template of the node, collect the context parameter variables used in the parameter configuration template, and traverse the value expression nested in the parameter configuration template in a depth-first manner to form a parsed template value tree structure.

[0089] (2) Loading context parameters: Load the context parameters used in the parameter configuration template from the overall process context into the template parsing context (i.e., local context). The source of context parameters can be environment variables, process startup parameters, node execution return parameters, and node built-in parameters.

[0090] (3) Template value calculation and extraction: Perform depth-first traversal according to the template value tree to obtain the variable name in the value expression, match the variable name from the loaded context according to the context parameter name hierarchy to obtain the value of the context parameter, and then calculate the result value of the value expression through the value expression.

[0091] (4) Node parameter replacement: All value expressions in the node parameters are replaced with the result values ​​of the value expressions, and converted into actual node execution parameter configurations to wait for the next step of node execution.

[0092] In order to adapt to the extraction and conversion of various data types, the value expression in the parameter configuration template can perform different types of operations. Specifically: when the value expression is a numerical operation expression, the numerical value corresponding to the numerical variable in the value expression is obtained, and the numerical value is used as the result value corresponding to the value expression; when the value expression is a character operation expression, the character corresponding to the character variable in the value expression is obtained, and the character is used as the result value corresponding to the value expression; when the value expression is an object operation expression, the object attribute value corresponding to the object variable and the attribute variable in the value expression is obtained, and the object attribute value is used as the result value corresponding to the value expression; when the value expression is an array operation expression, the index value of the index variable corresponding to the array variable in the value expression is obtained, and the index value is used as the result value corresponding to the value expression.

[0093] To facilitate understanding of the above process of calculating the result value of the value expression from the context parameter, the following is explained in conjunction with a specific embodiment:

[0094] In some embodiments, the value expression can be set according to the following rules:

[0095] (1) {{variable name}}, ${expression}, there are spaces before and after the variable name and expression;

[0096] (2) Object attribute value expressions are separated by English “.”, for example, “user.name”;

[0097] (3) The array uses the format of "array name [idx]", that is, take the value corresponding to the subscript "idx".

[0098] In a specific embodiment, the context parameter is a "user object", the variable name of the context parameter is "user", and the parameter value corresponding to "user" is:

[0099] {

[0100] "name": "admin",

[0101] "age": 18,

[0102] "sport": ["basketball", "swimming"],

[0103] "detail": {"relationUser": "zhangsan"}

[0104] }

[0105] Among them, "name", "age", "sport" and "detail" are the four attributes of the variable "user", "admin" is the attribute value of "name", "18" is the attribute value of "age", "basketball, swimming" are the two attribute values ​​of "sport", and "relationUser:zhangsan" is the attribute value of "detail".

[0106] (1) When the value expression is "{{user.name}}", the result value is the name attribute value of the variable user object (that is, the object attribute value corresponding to the object variable and the attribute variable in the value expression is obtained): admin;

[0107] (2) When the value expression is "{{user.sport[0]}}", the result value is the first attribute value of the sport of the variable user object: basketball;

[0108] (3) When the value expression is "{{user.detail.relationUser}}", the result value is the relationUser attribute value corresponding to the detail of the variable user object: zhangsan.

[0109] In another specific embodiment, the context parameter is an "array of user objects", the variable name of the context parameter is "users", and the parameter value corresponding to "users" is: [

[0111] {"name":"admin","age":28,"sport":"swimming"},

[0112] {"name":"zhangsan","age":38,"sex":"male","sport":"basketball"},

[0113] {"name":"lisi","age":20,"sex":"male","sport":"volleyball"} ]

[0115] Among them, the variable "users" contains three objects. The first object contains three attributes: "name", "age", and "sport". The second and third objects contain four attributes: "name", "age", "sex", and "sport". "Admin" is the attribute value of "name" of the first object, "28" is the attribute value of "age" of the first object, and "swimming" is the attribute value of "sport" of the first object; "zhangsan" is the attribute value of "name" of the second object, "38" is the attribute value of "age" of the second object, "male" is the attribute value of "sex" of the second object, and "basketball" is the attribute value of "sport" of the second object; "lisi" is the attribute value of "name" of the third object, "20" is the attribute value of "age" of the third object, "male" is the attribute value of "sex" of the third object, and "volleyball" is the attribute value of "sport" of the third object.

[0116] (1) When the value expression is "{{users.[0].name}}", the result value is the name attribute value of the first object in the variable users array (that is, the index value of the index variable corresponding to the array variable in the value expression is obtained): admin;

[0117] (2) When the value expression is "{{users.[1].name}}", the result value is the name attribute value of the second object in the variable users array: zhangsan;

[0118] (3) When the value expression is "{{users.[0,1].name}}", the result value is the first two user name attribute values ​​in the variable users array: ["admin", "zhangsan"];

[0119] (4) When the value expression is "{{users.[*].name}}", the result value is the name attribute value of all objects in the variable users array: ["admin", "zhangsan", "test"];

[0120] (5) When the value expression is "{{users.[age>20].name[0]}}", the result value is the name attribute value of the first user whose age "age" is greater than 20 in the variable users array: admin;

[0121] (6) When the value expression is "{{users.[?(@.sex)].name[0]}}", the result value is the first user name attribute value with gender in the variable users array: admin.

[0122] In another specific embodiment, when the value expression is "${{{a}}+{{b}}}", the value expression is a nested value expression. In the context parameter value, when variables a=1 and b=2, the calculated value of the value expression is 3.

[0123] In order to improve the accuracy of parameter mapping, after determining the parameter value of the input parameter, the following steps can also be performed: obtain parameter specification information of the input parameter of the orchestration node, wherein the parameter specification information includes at least one of the following: parameter type, parameter value range, and parameter integrity; verify the input parameter according to the parameter specification information; if the verification fails, re-determine the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and use the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter.

[0124] The parameter type is verified, that is, whether the current parameter value type after conversion according to the parameter configuration template matches the parameter type requirement of the orchestration node. If the current parameter type does not match, it is determined to have failed the verification.

[0125] The parameter value range is checked, that is, whether the current parameter value after conversion according to the parameter configuration template is within the parameter value range of the orchestration node. When the current parameter value does not fall within the parameter value range, it is determined that the check has failed.

[0126] The parameter integrity is verified, that is, whether the current parameters converted according to the parameter configuration template are missing the necessary parameters for executing the orchestration node. If the necessary parameters are missing, it is determined that the verification has failed.

[0127] In some embodiments, redetermining the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value means redetermining the parameter value of the sub-parameter that has not passed the verification in the input parameter according to the corresponding value expression and the context parameter value, and replacing the original parameter value with the redetermined parameter value until it passes the verification.

[0128] In order to facilitate understanding of the above process, a specific embodiment is described in detail below. The embodiment mainly includes the following seven steps:

[0129] (1) Select an orchestration node.

[0130] (2) Configure the orchestration node input parameters.

[0131] In this orchestration node, the atomic capability instruction interface parameters include the request method, request URL, request header, and request body, as follows:

[0132] 1) Request method

[0133] POST

[0134] 2) Request URL

[0135] https: / / 127.0.0.1:2024 / dispatch / v1 / ipworkbench / dynamicPrivateV4V6IPAllocateCallB

[0136] ack

[0137] 3) Request header

[0138] Parameter encoding Parameter name Parameter Type Parameter Description Access-Api-Key Authentication API Key String Authentication failed 401 Content-Type Request body type String application / json

[0139] 4) Request body

[0140] The request body is a complex JSON object, including the following properties:

[0141] The five attributes are wsnbr, WsCode, callBckStatus, netInfo and devinfo.

[0142] Where netInfo is an object, which includes multiple attributes: trunkName, domainName, portName, cvlan, ipInfo, svlan, and vpnName. Where ipInfo is an array, and each object in the array includes multiple attributes: ipv6PdGateway, ipv6NdAdr, ipv4Mask, subNet, ipv6NdGateway, ipv6PdPoolName, ipv4Adr, ipVersion, ipv4Gateway, ipv6PdAdr, ipTypeCode, and ipv6NdPoolName.

[0143] devinfo is an object containing multiple attributes: id, vendor, mgmtIp.

[0144] (3) Use the parameter configuration template to configure the input parameter value.

[0145] In the above interface parameters (i.e. input parameters), taking the request body as an example, the request body after configuration using the parameter configuration template is:

[0146]

[0147] Among them, wsnbr, WsCode, netInfo, and devinfo are sub-parameters of the request body (i.e., input parameters), trunkName, domainName, portName, cvlan, ipInfo, svlan, and vpnName are sub-parameters of the sub-parameter netInfo, and "{{…}}" and "${…}" represent specific value expressions.

[0148] (4) When the orchestration is executed to the orchestration node, the parameter configuration template in the input parameter is parsed.

[0149] Extract the template expression from the configuration information of the request body (i.e. the parameter configuration template):

[0150] {{ws.wsnbr}}, ${bpceFunc.createCode('yyyyMMddHHmmsss','seq')}, {{port.trunkName}}, {{portName}}, {{cvlan}}, {{ipList.data[portName='{{portName}}']}}, {{svlan}}, {{resp.data}}.

[0151] Among them, "bpceFunc.createCode('yyyyMMddHHmmsss','seq')" in "${bpceFunc.createCode('yyyyMMddHHmmsss','seq')}" is a specific expression; "{{ipList.data[portName='{{portName}}']}}" is a nested value expression, and the outermost value expression is "{{ipList.data[portName='{{portName}}']}}", and the result value can be calculated by the context parameters "ipList" and "portName"; its innermost value expression is "{{portName}}", and the result value can be calculated by the "portName" in the context parameters.

[0152] (5) Associate the parsed value expression with the parameters in the process context and perform value mapping.

[0153] Analyze the context parameters used in the extracted value expression and load the parameter values ​​from the context. The parameters include various types, such as basic types, object types, and array types. Calculate the context parameter values ​​in the value expression to obtain the parameter values ​​converted by the parameters. The calculations that can be performed include expression function calculations, object attribute retrieval, and array calculations.

[0154] (6) The obtained value expression result value is used to replace the value expression in the orchestration node input parameter to obtain the process node parameter value (i.e., the parameter value of the input parameter).

[0155] Map the parameter configuration template to the actual request body, that is, replace the value of the value expression as a whole, where there may be nested expressions in the value expression.

[0156] Figure 4 Schematic diagram of the parameter configuration template parsing principle according to an embodiment of the present application. Figure 4 As shown, after the parsing starts, first, the placeholder (i.e., value expression) is parsed, and all the placeholders used in the parameter configuration template are obtained, and parsed into a multi-layer nested value expression tree structure. Secondly, it is determined whether there is a template (i.e., value expression). In the case where there is no value expression, the placeholder is directly replaced to complete the parsing. In the case of a value expression, the variable name is extracted, that is, the variable name of the context parameter in the placeholder is extracted, and the variable value is extracted, that is, the variable value is extracted according to the value expression and the context parameter variable. It is determined again whether the extracted variable value contains a value expression. In the case of not containing a value expression, the placeholder is a non-nested value expression, and its result value can be calculated to replace the placeholder to complete the parsing; in the case of containing a value expression, the variable name and variable value are extracted until the variable value no longer contains a value expression, and the result value of the value expression is calculated according to the depth-first algorithm, and finally the placeholder is replaced to complete the parsing.

[0157] (7) Execute the orchestration node using the mapped parameter values.

[0158] Figure 5 is a flowchart executed by the orchestration engine according to an embodiment of the present application, such as Figure 5 As shown, before the orchestration engine executes the orchestration node, it calls Figure 5 The process shown can parse and convert the parameter configuration template in the orchestration node according to the node parameter configuration and the process context parameters, and pass the converted node parameter value actually called to the orchestration node for execution.

[0159] In the related art, since the mapping of parameters between atomic capability instructions (i.e., orchestration nodes) during the orchestration process requires the analysis, conversion, and configuration of parameters, it is necessary to add nodes to adapt parameters between different atomic capability instructions. Figure 6 As shown, before instruction 1 (orchestration node 1) is executed, it is necessary to add a parameter processing script node to implement the request parameter adaptation instruction 1. Before instruction 2 (orchestration node 2) is executed, it is necessary to add a parameter processing script node to implement the request parameter and instruction 1 output parameter adaptation instruction 2. This results in too many nodes, complex process configuration, and low execution efficiency.

[0160] The solution provided in the embodiment of the present application can be implemented in the orchestration node, such as Figure 7 As shown, the input parameters of the orchestration node provide a parameter configuration template. When configuring the atomic capability instruction 1 (i.e., orchestration node 1), the complex objects, arrays, strings, and other data in the context parameters (such as request parameters, etc.) can be directly obtained from the parameter values ​​of the atomic capability instruction 1 input. Before the process engine executes, the parameter configuration template in the parameter value is calculated and replaced to adapt to the execution of the atomic capability instruction 1; for the output parameters of the atomic capability instruction 1, the atomic capability instruction 2 (i.e., orchestration node 2) can also directly obtain the complex objects, arrays, strings, and other data in the context parameters (such as the output parameters of the atomic capability instruction 1, etc.) from the parameter values ​​of the atomic capability instruction 2 input. Before the process engine executes, the parameter configuration template in the parameter value is calculated and replaced to adapt to the execution of the atomic capability instruction 2. Therefore, the parameters are mapped between the atomic capability instruction nodes through the scheme provided in the embodiment of the present application, so that there is no need to specially configure the parameter mapping script node between the nodes, which effectively reduces the number of processing nodes.

[0161] Figure 8 is a structural diagram of an apparatus for orchestrating node execution according to an embodiment of the present application, such as Figure 8 As shown, the device comprises:

[0162] A first acquisition module 80 is used to acquire input parameters of an orchestration node in a task to be orchestrated;

[0163] A first determining module 82, configured to determine a parameter configuration template from configuration information of an input parameter;

[0164] A second acquisition module 84 is used to acquire context parameter values ​​in the parameter configuration template;

[0165] A second determination module 86, configured to determine the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and use the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter;

[0166] The execution module 88 is used to determine the target configuration information of the orchestration node according to the parameter value of the input parameter, and execute the orchestration node according to the target configuration information.

[0167] The second acquisition module in the device executed by the above-mentioned orchestration node is also used to obtain a first value expression set contained in the parameter configuration template; obtain a first value expression from the first value expression set, wherein the first value expression is any value expression in the value expression set; parse the first value expression to obtain the variable name of the context parameter contained in the first value expression; and obtain the context parameter value corresponding to the context parameter from the context information according to the variable name of the context parameter.

[0168] The second determination module in the device executed by the above-mentioned orchestration node is also used to obtain a second value expression set included in the parameter configuration template, wherein the value expressions in the second value expression set are used to configure the parameter values ​​of the sub-parameters of the input parameters; obtain the second value expression in the second value expression set, wherein the second value expression includes the outermost value expression of the sub-parameters of the input parameters; when the second value expression does not contain an inner value expression, determine the parameter value of the sub-parameter corresponding to the second value expression according to the second value expression and the context parameter value corresponding to the variable name of the context parameter in the second value expression; when the second value expression contains an inner value expression, determine the dependency relationship between each value expression in the second value expression, and determine the parameter value of the sub-parameter corresponding to the second value expression according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter in each value expression in the second value expression; replace the second value expression with the parameter value of the sub-parameter corresponding to the second value expression to obtain the parameter value of the input parameter.

[0169] The second determination module in the device executed by the above-mentioned orchestration node is also used to obtain a third value expression from the inner value expression set where the inner value expression is located, wherein the third value expression includes the innermost value expression; starting from the third value expression, according to the dependency relationship and the context parameter values ​​corresponding to the variable names of the context parameters respectively contained in the value expressions in the inner value expression set, the result values ​​of the value expressions in the inner value expression set are calculated layer by layer in sequence; and the parameter value of the sub-parameter corresponding to the second value expression is determined according to the result value of the value expression in the inner value expression set.

[0170] The second determination module in the device executed by the above-mentioned orchestration node is also used to obtain a third value expression from the inner value expression set where the inner value expression is located, wherein the third value expression includes the innermost value expression; starting from the third value expression, according to the dependency relationship and the context parameter values ​​corresponding to the variable names of the context parameters respectively contained in the value expressions in the inner value expression set, the result values ​​of the value expressions in the inner value expression set are calculated layer by layer in sequence; and the parameter value of the sub-parameter corresponding to the second value expression is determined according to the result value of the value expression in the inner value expression set.

[0171] The second determination module in the device executed by the above-mentioned orchestration node is also used to obtain the numerical value corresponding to the numerical variable in the value expression when the value expression is a numerical operation expression, and use the numerical value as the result value corresponding to the value expression; when the value expression is a character operation expression, obtain the character corresponding to the character variable in the value expression, and use the character as the result value corresponding to the value expression; when the value expression is an object operation expression, obtain the object attribute value corresponding to the object variable and the attribute variable in the value expression, and use the object attribute value as the result value corresponding to the value expression; when the value expression is an array operation expression, obtain the index value of the index variable corresponding to the array variable in the value expression, and use the index value as the result value corresponding to the value expression.

[0172] The second determination module in the device executed by the above-mentioned orchestration node is also used to obtain parameter specification information of the input parameters of the orchestration node, wherein the parameter specification information includes at least one of the following: parameter type, parameter value range and parameter integrity; verifying the input parameters according to the parameter specification information; if the verification fails, re-determining the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and using the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter.

[0173] It should be noted that Figure 8 The device for executing the orchestration node is used to execute Figure 2 The execution method of the orchestration node shown, therefore Figure 2 The explanations in the execution method of the orchestration node in also apply to Figure 8 The apparatus for executing the orchestration node shown will not be described in detail here.

[0174] An embodiment of the present application further provides an electronic device, which includes a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the steps of the execution method of the orchestration node in each embodiment of the present application.

[0175] For example, the processor performs the following functions by executing program instructions stored in the memory:

[0176] The method comprises: obtaining input parameters of an orchestration node in a task to be orchestrated, wherein the input parameters include output parameters of a previous orchestration node of the orchestration node in the task to be orchestrated; determining a parameter configuration template from configuration information of the input parameters, wherein the parameter configuration template is used to configure the output parameters as input parameters; obtaining context parameter values ​​in the parameter configuration template, wherein context parameters corresponding to the context parameter values ​​include parameters transmitted between different orchestration nodes in the task to be orchestrated; determining parameter values ​​of parameters corresponding to the context parameters in the parameter configuration template according to the context parameter values, and using the parameter values ​​of the parameters corresponding to the context parameters as parameter values ​​of the input parameters; determining target configuration information of the orchestration node according to the parameter values ​​of the input parameters, and executing the orchestration node according to the target configuration information.

[0177] An embodiment of the present application further provides a non-volatile storage medium, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the steps of the execution method of the orchestration node in each embodiment of the present application by running the computer program.

[0178] The embodiments of the present application also provide a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the execution method of the orchestration node in each embodiment of the present application.

[0179] The embodiments of the present application also provide a computer program, which, when executed by a processor, implements the steps of the execution method of the orchestration node in each embodiment of the present application.

[0180] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0181] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0182] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0183] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0184] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0185] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0186] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for executing an orchestration node, characterized in that: include: Acquire input parameters of an orchestration node in a task to be orchestrated, wherein the input parameters include output parameters of a previous orchestration node of the orchestration node in the task to be orchestrated; Determining a parameter configuration template from the configuration information of the input parameter, wherein the parameter configuration template is used to configure the output parameter as the input parameter; Acquire a context parameter value in the parameter configuration template, wherein the context parameter corresponding to the context parameter value includes a parameter transmitted between different orchestration nodes in the task to be orchestrated; Determine the parameter value of the parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and use the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter; Determine target configuration information of the orchestration node according to the parameter value of the input parameter, and execute the orchestration node according to the target configuration information.

2. The method according to claim 1, characterized in that Obtaining the context parameter value in the parameter configuration template includes: Obtain a first value expression set included in the parameter configuration template; Obtain a first value expression from the first value expression set, wherein the first value expression is any value expression in the value expression set; Parsing the first value expression to obtain the variable name of the context parameter included in the first value expression; According to the variable name of the context parameter, a context parameter value corresponding to the context parameter is obtained from the context information.

3. The method according to claim 1, characterized in that Determining a parameter value of a parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and using the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter, includes: Obtaining a second value expression set included in the parameter configuration template, wherein the value expressions in the second value expression set are used to configure parameter values ​​of sub-parameters of the input parameter; Obtain a second value expression in the second value expression set, wherein the second value expression includes the outermost value expression of the sub-parameter of the input parameter; In the case where the second value expression does not contain an inner value expression, determining the parameter value of the sub-parameter corresponding to the second value expression according to the second value expression and the context parameter value corresponding to the variable name of the context parameter in the second value expression; In the case where the second value expression includes an inner value expression, determining a dependency relationship between each value expression in the second value expression, and determining a parameter value of a sub-parameter corresponding to the second value expression according to the dependency relationship and a context parameter value corresponding to a variable name of the context parameter in each value expression in the second value expression; The second value expression is replaced by the parameter value of the sub-parameter corresponding to the second value expression to obtain the parameter value of the input parameter.

4. The method according to claim 3, characterized in that Determining the parameter value of the sub-parameter corresponding to the second value expression according to the dependency relationship and the context parameter value corresponding to the variable name of the context parameter in each value expression in the second value expression includes: Obtaining a third value expression from the inner value expression set where the inner value expression is located, wherein the third value expression includes the innermost value expression; According to the dependency relationship and the context parameter values ​​corresponding to the variable names of the context parameters respectively contained in the value expressions in the inner value expression set, starting from the third value expression, the result values ​​of the value expressions in the inner value expression set are calculated layer by layer in sequence; The parameter value of the sub-parameter corresponding to the second value expression is determined according to the result value of the value expression in the inner value expression set.

5. The method according to claim 3, characterized in that: In the case where the second value expression includes an inner value expression, determining the dependency relationship between the value expressions in the second value expression includes: Parsing the second value expression using a template value language to obtain variable names of multiple context parameters included in the second value expression; Dependency relationships between multiple value expressions corresponding to the variable names of the multiple context parameters are determined according to the dependency relationships between the variable names of the multiple context parameters.

6. The method according to any one of claims 2 to 5, characterized in that: When the value expression is a numerical operation expression, obtaining a numerical value corresponding to a numerical variable in the value expression, and using the numerical value as a result value corresponding to the value expression; When the value expression is a character operation expression, obtaining the character corresponding to the character variable in the value expression, and using the character as the result value corresponding to the value expression; When the value expression is an object operation expression, obtaining object attribute values ​​corresponding to the object variables and attribute variables in the value expression, and using the object attribute values ​​as the result values ​​corresponding to the value expression; When the value expression is an array operation expression, the index value of the index variable corresponding to the array variable in the value expression is obtained, and the index value is used as the result value corresponding to the value expression.

7. The method according to claim 1, characterized in that After obtaining the parameter value of the input parameter, the method further includes: Acquire parameter specification information of the input parameters of the orchestration node, wherein the parameter specification information includes at least one of the following: parameter type, parameter value range, and parameter integrity; Verifying the input parameters according to the parameter specification information; In the case of failure to pass the verification, the parameter value of the parameter corresponding to the context parameter in the parameter configuration template is re-determined according to the context parameter value to obtain the parameter value of the input parameter.

8. A device for scheduling node execution, characterized in that: include: A first acquisition module, configured to acquire input parameters of an orchestration node in a task to be orchestrated, wherein the input parameters include output parameters of a previous orchestration node of the orchestration node in the task to be orchestrated; A first determining module, configured to determine a parameter configuration template from the configuration information of the input parameter, wherein the parameter configuration template is used to configure the output parameter as the input parameter; A second acquisition module, configured to acquire a context parameter value in the parameter configuration template, wherein the context parameter corresponding to the context parameter value includes a parameter transmitted between different orchestration nodes in the task to be orchestrated; A second determination module, configured to determine a parameter value of a parameter corresponding to the context parameter in the parameter configuration template according to the context parameter value, and use the parameter value of the parameter corresponding to the context parameter as the parameter value of the input parameter; An execution module is used to determine target configuration information of the orchestration node according to the parameter value of the input parameter, and execute the orchestration node according to the target configuration information.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the execution method of the orchestration node according to any one of claims 1 to 7.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the execution method of the orchestration node according to any one of claims 1 to 7 by running the computer program.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the execution method of the orchestration node described in any one of claims 1 to 7 is implemented.

Images