Deployment methods, devices and electronic equipment for orchestration services
By grouping orchestration services by type and automating their deployment, the problem of low deployment efficiency was solved, enabling efficient management and combined operation of multiple services and improving deployment efficiency.
Patent Information
- Application Number
- CN202210116800.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-02-07
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-02-07
AI Technical Summary
In existing technologies, the deployment efficiency of orchestration services is low, and it is difficult to manage and run different deployment states of multiple services at the same time, making it difficult to achieve efficient deployment of service composition.
By identifying multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information, the services are grouped by type and deployed sequentially. The service engine is determined and the process definition information is registered, thus achieving automated deployment of the orchestration service.
It improves the deployment efficiency of orchestration services, enabling automatic management and combination of multiple services, thereby enhancing deployment efficiency and consistency.
Smart Images

Figure CN116594637B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of artificial intelligence technology, and in particular to a method, apparatus and electronic device for deploying orchestration services. Background Technology
[0002] Currently, a service refers to a component model that can be built and deployed independently to implement a single function. This function can be a single feature or different functional units within an application. An orchestration service, in particular, refers to a service composed of multiple services that need to be executed in a specific order.
[0003] In related technologies, during service deployment, only one deployment state is maintained for each service, and different services have different deployment states. Therefore, only single-service deployment is supported. If multiple services need to be deployed, the deployment states of each service need to be managed separately, and each service needs to be run separately. This makes it difficult to deploy service compositions, such as service orchestration. Summary of the Invention
[0004] This application aims to at least partially address one of the technical problems in the related art.
[0005] This application proposes a method, apparatus, and electronic device for deploying orchestration services, which enables the deployment of orchestration services and allows for state management and combined operation of various services within the orchestration services, thereby improving the deployment efficiency of orchestration services.
[0006] The first aspect of this application proposes a method for deploying an orchestration service, including:
[0007] Identify the multiple services to be deployed in the orchestration service, the deployment-related information of each service, and the process definition information of the orchestration service;
[0008] The multiple services are grouped according to service type to obtain at least one service group;
[0009] For each of the at least one service group, deployment processing is performed on the service group according to the deployment information of the services in the service group;
[0010] The service engine for the orchestration service is determined, and the process definition information is registered to the service engine.
[0011] The deployment method for orchestration services in this application embodiment determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; sequentially performs deployment processing on each service group in the at least one service group according to the deployment-related information of the services in the service group; determines the service engine of the orchestration service, and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0012] A second aspect of this application provides a deployment apparatus for orchestration services, comprising:
[0013] The determination module is used to determine multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service;
[0014] The grouping module is used to group the multiple services according to service type to obtain at least one service group;
[0015] The deployment module is used to sequentially deploy each service group in the at least one service group according to the deployment information of the services in the service group;
[0016] The registration module is used to determine the service engine of the orchestration service and register the process definition information to the service engine.
[0017] The deployment apparatus for orchestration services in this application determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; sequentially performs deployment processing on each service group in the at least one service group according to the deployment-related information of the services in the service group; determines the service engine of the orchestration service, and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0018] A third aspect of this application provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform a deployment method for an orchestration service proposed in a first aspect of this application.
[0019] A fourth aspect of this application provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute a deployment method for orchestration services proposed in a first aspect of this application.
[0020] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0021] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:
[0022] Figure 1 A flowchart illustrating the deployment method of the orchestration service provided in Embodiment 1 of this application;
[0023] Figure 2 This is a flowchart illustrating the deployment method of the orchestration service provided in Embodiment 2 of this application;
[0024] Figure 3 Deployment diagram for orchestration services;
[0025] Figure 4 This is a schematic diagram of the deployment apparatus for the orchestration service provided in Embodiment 3 of this application;
[0026] Figure 5 A block diagram of an exemplary computer device suitable for implementing embodiments of the present application is shown. Detailed Implementation
[0027] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.
[0028] Currently, a service refers to a component model that can be built and deployed independently to implement a single function. This function can be a single feature or different functional units within an application. An orchestration service, in particular, refers to a service composed of multiple services that need to be executed in a specific order.
[0029] In related technologies, during service deployment, only one deployment state is maintained for each service, and different services have different deployment states. Therefore, only single-service deployment is supported. If multiple services need to be deployed, the deployment states of each service need to be managed separately, and each service needs to be run separately. This makes it difficult to deploy service compositions, such as service orchestration.
[0030] Therefore, this application mainly addresses the technical problem of poor deployment efficiency of orchestration services in related technologies, and proposes a deployment method, apparatus and electronic device for orchestration services.
[0031] The deployment method for orchestration services in this application embodiment determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; sequentially performs deployment processing on each service group in the at least one service group according to the deployment-related information of the services in the service group; determines the service engine of the orchestration service, and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0032] The following description, with reference to the accompanying drawings, outlines a method, apparatus, and electronic device for deploying orchestration services according to embodiments of this application.
[0033] Figure 1 This is a flowchart illustrating the deployment method of the orchestration service provided in Embodiment 1 of this application.
[0034] This application embodiment illustrates the example of the orchestration service deployment method being configured in an orchestration service deployment device. The orchestration service deployment device can be applied to any electronic device so that the electronic device can perform the orchestration service deployment function.
[0035] Among these, electronic devices can be personal computers (PCs), cloud devices, mobile devices, etc. Mobile devices can be hardware devices with various operating systems, touch screens, and / or displays, such as mobile phones, tablets, personal digital assistants, wearable devices, and in-vehicle devices. Electronic devices can also include, for example, service development platforms.
[0036] like Figure 1 As shown, the deployment method for this orchestration service may include the following steps:
[0037] Step 101: Determine the multiple services to be deployed in the orchestration service, the deployment information of each service, and the process definition information of the orchestration service.
[0038] In this embodiment of the application, an orchestration service refers to a combined service obtained by executing multiple services in a certain order. Specifically, a service within an orchestration service can use the execution results of other services within the orchestration service as input data, and the execution results of one service can serve as input data for other services within the orchestration service.
[0039] In this embodiment, the orchestration service may include the following five services: model service, data service, function service, logic service, and API interface service. The model component implementing the model service is created by the user uploading an image of the algorithm model to the service development platform, which then records it as a model component for use in the orchestration service. The data component implementing the data service is used to connect to data sources (such as MySQL, Oracle, Kafka, etc.) and is applied to data processing within the orchestration service.
[0040] The function component, which implements the function service, is written by the user and is responsible for handling the upstream and downstream parameter conversions in the orchestration service. The logic component, which implements the logic service, is used for process connections in the orchestration service's process definition information, such as start and end. The API component, which implements the API interface service, is encapsulated from user-entered third-party API interfaces and is used for calling the orchestration service.
[0041] In this embodiment, the logical service and API interface service among the above five services do not need to be deployed. The services to be deployed in the orchestration service are the model service, data service, and function service.
[0042] Step 102: Group the multiple services according to their service types to obtain at least one service group.
[0043] In this embodiment, the service type can include the following two types: function type and non-function type. The non-function type includes at least one of the following types: model type and data type. Specifically, a model type service is a model service; a data type service is a data service; and a function type service is a function service.
[0044] In this embodiment of the application, the process of the service development platform executing step 102 can be, for example, identifying some services among multiple services that are function services; combining the partial services to obtain a function service group; and combining the services among multiple services other than the partial services to obtain a non-function service group.
[0045] Step 103: For each service group in at least one service group, deploy the service group according to the deployment information of the services in the service group.
[0046] In this embodiment of the application, the process of deploying a service group according to the deployment information of the services in the service group can be as follows: for each service in the service group, generate the service deployment configuration according to the service deployment information and the deployment configuration template; generate the service group deployment configuration according to the deployment configuration of each service in the service group; and deploy the service group according to the deployment configuration of the service group.
[0047] Step 104: Determine the service engine for the orchestration service and register the process definition information into the service engine.
[0048] In this embodiment of the application, the process definition information defines the execution order of each service in the orchestration service. For example, taking an orchestration service that includes services A, B, C, and D as an example, the execution result of service A serves as the input data for service B; the execution result of service B serves as the input data for services C and D, respectively. Then, the process definition information defines the execution order among the above four services, as well as the relationship between the output of each service and the input of other services.
[0049] In this embodiment of the application, after step 104, the service development platform may further perform the following process: determine the routing information of the orchestration service; generate the API interface corresponding to the orchestration service based on the routing information, so as to call the orchestration service through the API interface. The routing information of the orchestration service is, in effect, the service access address of the orchestration service.
[0050] The deployment method for orchestration services in this application embodiment determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; sequentially performs deployment processing on each service group in the at least one service group according to the deployment-related information of the services in the service group; determines the service engine of the orchestration service, and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0051] Figure 2 This is a flowchart illustrating the deployment method of the orchestration service provided in Embodiment 2 of this application.
[0052] like Figure 2 As shown, the deployment method for this orchestration service may include the following steps:
[0053] Step 201: Determine the multiple services to be deployed in the orchestration service, the deployment information of each service, and the process definition information of the orchestration service.
[0054] Step 202: Group the multiple services according to their service types to obtain at least one service group.
[0055] Step 203: When a function service group exists in at least one service group, perform function deployment processing on the function service group based on the deployment information of each service in the function service group.
[0056] In this embodiment, the process of the service development platform executing step 203 can be, for example, as follows: when a function service group exists in at least one service group, for each service in the function service group, generate a service deployment configuration based on the service's deployment information and deployment configuration template; generate a function service group deployment configuration based on the deployment configurations of each service in the function service group; and perform deployment processing on the function service group based on the function service group deployment configuration. Specifically, for the function services in the function service group, the user-provided function scripts and dependency lists can be configured into the function service deployment configuration template to obtain the function service deployment configuration.
[0057] In this embodiment of the application, for the function services in the function service group, since the function services are developed based on the OpenFaas framework, the characteristic of this framework is that functions are services, and only scripts are required to publish them as services; therefore, the service development platform can provide the deployment configuration of the function service group to the function publishing system in the service development platform, so that the function service group can be deployed using the function publishing system.
[0058] In one example of this application embodiment, after step 203, the method may further include the following steps: determining that the function service group has been successfully deployed when all services in the function service group have been successfully deployed; determining that the function service group has failed to deploy when there are services that have failed to deploy in the function service group. Wherein, if the function service group deployment fails, the function service group is taken offline, i.e., the deployed function service group is rolled back.
[0059] In another example of this application embodiment, after step 203, the method may further include the following steps: calculating the time required to deploy the function service group according to the number of services in the function service group; periodically obtaining the deployment status of the function service group within the time period; if a successful deployment status is obtained within the time period, the acquisition operation is stopped; if a successful deployment status is not obtained within the time period; or if a failed deployment status is obtained within the time period, the deployment of the function service group is determined to have failed.
[0060] Step 204: When the function service group is successfully deployed, determine whether there is a non-function service group in at least one service group.
[0061] Step 205: When there is a non-function service group in at least one service group, perform mirror deployment processing on the non-function service group according to the deployment information of each service in the non-function service group.
[0062] In this embodiment of the application, the process of the service development platform executing step 205 can be, for example, as follows: when there is a non-function service group in at least one service group, for each service in the non-function service group, generate the service deployment configuration based on the service deployment information and the deployment configuration template; generate the non-function service group deployment configuration based on the deployment configuration of each service in the non-function service group; and perform deployment processing on the non-function service group based on the deployment configuration of the non-function service group.
[0063] The services in the non-function service group can include model services and data services. For model services, user-defined environment variables can be configured into the model service deployment configuration template to generate the model service deployment configuration. For data services, user-defined environment variables, data source connection information, and executed SQL statements can be configured into the data service deployment configuration template as environment variables to generate the data service deployment configuration.
[0064] In this embodiment of the application, for the model service and data service in the non-function service group, since the model service and data service need to be published using the image publishing system, the service development platform can provide the deployment configuration of the non-function service group to the image publishing system in the service development platform so as to deploy the non-function service group using the image publishing system.
[0065] In this embodiment of the application, after step 205, the method may further include the following steps: when all services in the non-function service group are successfully deployed, the non-function service group is determined to be successfully deployed; when there are services in the non-function service group that have failed to be deployed, the non-function service group is determined to have failed to be deployed. Wherein, if the non-function service group fails to be deployed, the function service group and the non-function service group are taken offline, that is, the deployed function service group and the non-function service group are rolled back.
[0066] If some services in the non-function service group are deployed successfully while others are being deployed, then the non-function service group is determined to be under deployment.
[0067] Step 206: Determine the service engine for the orchestration service and register the process definition information into the service engine.
[0068] It should be noted that for details regarding steps 201, 202, and 206, please refer to [the relevant documentation / reference]. Figure 1 Steps 101, 102, and 104 in the illustrated embodiment will not be described in detail here.
[0069] The deployment method for orchestration services in this application embodiment determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; when a function service group exists in the at least one service group, performs function deployment processing on the function service group according to the deployment-related information of each service in the function service group; when the function service group is successfully deployed, determines whether there is a non-function service group in the at least one service group; when a non-function service group exists in the at least one service group, performs mirror deployment processing on the non-function service group according to the deployment-related information of each service in the non-function service group; determines the service engine of the orchestration service and registers the process definition information into the service engine; and determines the service engine of the orchestration service and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0070] To illustrate the above embodiments more clearly, examples are given below.
[0071] For example, such as Figure 3 The diagram shown illustrates the deployment of orchestration services. Figure 3 In the process, (1) Assemble the deployment configuration of each component (i.e., determine the deployment configuration of each service in the orchestration service); (2) Group the component deployment tasks according to the component type (i.e., service grouping); (3) Determine whether the orchestration service contains function components (i.e., function services). If yes, execute (4); (4) Publish the function service group through the function deployment system; (5) Query the deployment status of the function service group; (6) Determine whether the function service group has been successfully published (i.e., deployed successfully). If yes, execute (7); otherwise, execute (16); (7) Determine whether the orchestration service contains model components or data components (i.e., model services or data services). If yes, execute (8); otherwise, execute (16). 2); (8) Register the image service group (i.e., the non-function service group) to the image publishing system, and the image publishing system returns the group ID; (9) The award publishing system publishes the entire group of services; (10) Query the image service group publishing status; (11) Determine whether the image service group has been successfully published (i.e., successfully deployed); if yes, execute (12), otherwise execute (14); (12) Register the orchestration service process definition; (13) Register the orchestration service route to the gateway; (14) Determine whether the image service group has failed to be published (i.e., failed to be deployed); if yes, execute (15), otherwise execute (10); (15) Take the image service group offline; (16) Take the image service group offline.
[0072] Figure 4 This is a schematic diagram of the deployment device for the orchestration service provided in Embodiment 3 of this application.
[0073] like Figure 4 As shown, the deployment device 400 for the orchestration service may include: a determination module 410, a grouping module 420, a deployment module 430, and a registration module 440.
[0074] The determining module 410 is used to determine multiple services to be deployed in the orchestration service, deployment-related information of each service, and process definition information of the orchestration service.
[0075] Grouping module 420 is used to group the multiple services according to service type to obtain at least one service group;
[0076] The deployment module 430 is used to sequentially deploy each service group in the at least one service group according to the deployment information of the services in the service group;
[0077] The registration module 440 is used to determine the service engine of the orchestration service and register the process definition information to the service engine.
[0078] Furthermore, in one possible implementation of this application embodiment, the service type includes: function type and non-function type; the grouping module 420 is specifically used to: determine some services among the plurality of services whose service type is function service; perform combination processing on the partial services to obtain function service group; and perform combination processing on the services among the plurality of services other than the partial services to obtain non-function service group.
[0079] Furthermore, in one possible implementation of this application embodiment, the deployment module 430 is specifically configured to: when a function service group exists in the at least one service group, perform function deployment processing on the function service group according to the deployment information of each service in the function service group; when the function service group is successfully deployed, determine whether there is a non-function service group in the at least one service group; when a non-function service group exists in the at least one service group, perform mirror deployment processing on the non-function service group according to the deployment information of each service in the non-function service group.
[0080] Furthermore, in one possible implementation of this application embodiment, the deployment module 430 is specifically used to: generate a deployment configuration for each service in the function service group based on the service's deployment-related information and a deployment configuration template; generate a deployment configuration for the function service group based on the deployment configurations of each service in the function service group; and perform deployment processing on the function service group based on the deployment configuration of the function service group.
[0081] Furthermore, in one possible implementation of this application embodiment, the deployment module 430 is specifically used to determine that the function service group has been successfully deployed when all services in the function service group have been successfully deployed; and to determine that the function service group has failed to deploy when there are services that have failed to deploy in the function service group.
[0082] Furthermore, in one possible implementation of this application embodiment, the apparatus further includes: an offline processing module, configured to: offline the function service group when the function service group deployment fails; and offline the function service group and the individual non-function service group when the non-function service group deployment fails.
[0083] Furthermore, in one possible implementation of this application embodiment, the non-function type includes at least one of the following types: model type and data type.
[0084] Furthermore, in one possible implementation of this application embodiment, the apparatus further includes: a generation module; the determining module 410 is further configured to determine the routing information of the orchestration service; the generation module is configured to generate an API interface corresponding to the orchestration service based on the routing information, so as to call the orchestration service through the API interface.
[0085] It should be noted that the explanations in the aforementioned Embodiment 1 also apply to the deployment device of the orchestration service in this embodiment, and will not be repeated here.
[0086] The deployment apparatus for orchestration services in this application determines multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; groups the multiple services according to service type to obtain at least one service group; sequentially performs deployment processing on each service group in the at least one service group according to the deployment-related information of the services in the service group; determines the service engine of the orchestration service, and registers the process definition information into the service engine, thereby enabling automatic deployment processing of the orchestration service and improving the deployment efficiency of the orchestration service.
[0087] To implement the above embodiments, this application also proposes an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute the deployment method of the orchestration service proposed in the foregoing embodiments of this application.
[0088] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the deployment method of the orchestration service as proposed in the foregoing embodiments of this application.
[0089] Figure 5 A block diagram of an exemplary computer device suitable for implementing embodiments of the present application is shown. Figure 5 The computer device 12 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.
[0090] like Figure 5 As shown, the computer device 12 is represented in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and a bus 18 connecting different system components (including system memory 28 and processing unit 16).
[0091] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0092] Computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by computer device 12, including volatile and non-volatile media, removable and non-removable media.
[0093] Memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and / or cache memory 32. Computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (…). Figure 5Not shown; usually referred to as a "hard drive"). Although Figure 5 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disc drive for reading and writing to a removable non-volatile optical disc (e.g., a compact disc read-only memory (CD-ROM), a digital video disc read-only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this application.
[0094] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of this application.
[0095] Computer device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with computer device 12, and / or with any device that enables computer device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 22. Furthermore, computer device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0096] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the methods mentioned in the foregoing embodiments.
[0097] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0098] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0099] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.
[0100] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.
[0101] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.
[0102] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.
[0103] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.
[0104] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.
Claims
1. A method for deploying an orchestration service, characterized in that, include: Identify the multiple services to be deployed in the orchestration service, the deployment-related information of each service, and the process definition information of the orchestration service; The multiple services are grouped according to service type to obtain at least one service group; wherein, the service type includes: function type and non-function type; For each of the at least one service group, deployment processing is performed on the service group according to the deployment information of the services in the service group; Determine the service engine for the orchestration service and register the process definition information to the service engine; The step of sequentially deploying the service group according to the deployment information of the services in the at least one service group includes: When a function service group exists in the at least one service group, the function service group is processed for function deployment based on the deployment information of each service in the function service group; When the function service group is successfully deployed, determine whether there is a non-function service group in the at least one service group; When a non-function service group exists in the at least one service group, the non-function service group is mirrored and deployed according to the deployment information of each service in the non-function service group; wherein, the services in the non-function service group include model services and data services.
2. The method of claim 1, wherein, The process of grouping the multiple services according to service type to obtain at least one service group includes: Identify the portion of the services whose service type is function service among the multiple services; The aforementioned partial services are combined to obtain a function service group; The services other than the aforementioned partial services are combined to obtain a non-function service group.
3. The method according to claim 1, characterized in that, The step of performing function deployment processing on the function service group based on the deployment information of each service in the function service group includes: For each service in the function service group, generate the service's deployment configuration based on the service's deployment-related information and deployment configuration template; The deployment configuration of the function service group is generated based on the deployment configuration of each service in the function service group; Based on the deployment configuration of the function service group, the function service group is deployed.
4. The method according to claim 1, characterized in that, After performing function deployment processing on the function service group based on the deployment information of each service in the function service group, the method further includes: When all services in the function service group are successfully deployed, the function service group is determined to have been successfully deployed. If there is a service that has failed to be deployed in the function service group, the function service group is determined to have failed to be deployed.
5. The method according to claim 1, characterized in that, The method further includes: If the deployment of the function service group fails, the function service group shall be taken offline. If the deployment of the non-function service group fails, both the function service group and the individual non-function service group will be taken offline.
6. The method according to claim 1, characterized in that, The method further includes: Determine the routing information for the orchestration service; The routing information is used to generate the corresponding API interface for the orchestration service, so as to call the orchestration service through the API interface.
7. A deployment apparatus for an orchestration service, characterized in that, include: The determination module is used to determine multiple services to be deployed in the orchestration service, deployment-related information for each service, and process definition information of the orchestration service; A grouping module is used to group the multiple services according to service type to obtain at least one service group; wherein, the service type includes: function type and non-function type; The deployment module is used to sequentially deploy each service group in the at least one service group according to the deployment information of the services in the service group; The registration module is used to determine the service engine of the orchestration service and register the process definition information to the service engine; Specifically, the deployment module is used for: When a function service group exists in the at least one service group, the function service group is processed for function deployment based on the deployment information of each service in the function service group; When the function service group is successfully deployed, determine whether there is a non-function service group in the at least one service group; When a non-function service group exists in the at least one service group, the non-function service group is mirrored and deployed according to the deployment information of each service in the non-function service group; wherein, the services in the non-function service group include model services and data services.
8. The apparatus according to claim 7, characterized in that, The grouping module is specifically used for, Identify the portion of the services whose service type is function service among the multiple services; The aforementioned partial services are combined to obtain a function service group; The services other than the aforementioned partial services are combined to obtain a non-function service group.
9. The apparatus according to claim 7, characterized in that, The deployment module is specifically used for, For each service in the function service group, generate the service's deployment configuration based on the service's deployment-related information and deployment configuration template; The deployment configuration of the function service group is generated based on the deployment configuration of each service in the function service group; Based on the deployment configuration of the function service group, the function service group is deployed.
10. The apparatus according to claim 7, characterized in that, The deployment module is also specifically used for, When all services in the function service group are successfully deployed, the function service group is determined to have been successfully deployed. If there is a service that has failed to be deployed in the function service group, the function service group is determined to have failed to be deployed.
11. The apparatus according to claim 7, characterized in that, The device further includes: an offline processing module, used for, If the deployment of the function service group fails, the function service group shall be taken offline. If the deployment of the non-function service group fails, both the function service group and the individual non-function service group will be taken offline.
12. The apparatus according to claim 7, characterized in that, The device further includes: a generation module; The determining module is also used to determine the routing information of the orchestration service; The generation module is used to generate an API interface corresponding to the orchestration service based on the routing information, so as to call the orchestration service through the API interface.
13. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
14. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-6.
Citation Information
Patent Citations
Software package deployment system and method
CN110187898A
