A method and device for automatic orchestration of a service component pipeline

Abstract

The application provides a pipeline automatic arrangement method and device of service components, and the method comprises the following steps: receiving a pipeline automatic arrangement request of at least one service component sent by a client according to a business requirement; performing automatic arrangement processing on the pipeline of the at least one service component required according to the pipeline automatic arrangement request, and obtaining an automatic arrangement processing result of the at least one service component; the pipeline comprises an automatic execution process of a plurality of management operation stages of the at least one service component on a preset platform; performing automatic execution of the plurality of management operation stages of the service component on the preset platform according to the pipeline of the at least one service component, and obtaining an execution result; and feeding back the execution result to the client. The scheme of the application realizes automatic execution of service components, and meets the intelligent demand of industry chain integration full process and full value chain cooperation.

Description

Technical Field

[0001] This invention relates to the field of computer information processing technology, and in particular to a method and apparatus for automatic pipeline arrangement of service components. Background Technology

[0002] To achieve integrated product design, manufacturing, and service across a specific industry, and collaborative product supply, marketing, and service across the entire supply chain, service network collaborative manufacturing platforms have emerged. Containerized microservice architecture within the new internet architecture can provide excellent end-to-end and full-chain collaborative operation services for these platforms. However, microservice architecture still cannot fully meet practical needs in real-world applications. Summary of the Invention

[0003] The technical problem this invention aims to solve is to provide a method and apparatus for automatically orchestrating service components in a pipeline. This enables the automated execution of service components, meeting the intelligent requirements of integrated supply chain and full-value chain collaboration.

[0004] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows:

[0005] An automated pipeline orchestration method for service components includes:

[0006] Receives a pipeline auto-orchestration request from a client, based on business requirements, to execute at least one service component;

[0007] Based on the pipeline auto-arrangement request, the pipeline of at least one required service component is automatically arranged to obtain the pipeline auto-arrangement result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform.

[0008] According to the pipeline of at least one service component, the service component is automatically executed in multiple management operation stages on a preset platform to obtain the execution result;

[0009] The execution result is then fed back to the client.

[0010] Optionally, the pipeline of at least one required service component is automatically orchestrated to obtain the automatic orchestration result of the pipeline of at least one service component, including:

[0011] According to the preset pipeline orchestration template, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline of at least one service component. The preset pipeline orchestration template includes: at least one stage executed by the service component, the environment corresponding to each stage, and at least one task atom included in each environment.

[0012] Optionally, each stage can have multiple parallel jobs, each job can specify a different environment, and at least one task can be executed atomically in sequence.

[0013] Optionally, according to the pipeline of the at least one service component, the service component is automatically executed through multiple management operation stages on a preset platform to obtain execution results, including:

[0014] Based on the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, automatically execute at least one management operation of the service component in the preset platform, including discovery, registration, update, detection and destruction, and obtain the execution result.

[0015] Optionally, the discovery of service components on the default platform includes:

[0016] Receive service component launch notifications;

[0017] Based on the service component online notification, a service component online notification event is generated on a preset platform.

[0018] Based on the service component online notification event, a microservice instance corresponding to the service component is generated.

[0019] Optionally, the registration of service components on the preset platform includes:

[0020] Obtain the registration configuration information of the service components;

[0021] Based on the registration configuration information, configure the corresponding address, interface, and resources for the service component.

[0022] Optionally, updates to service components on the default platform include:

[0023] Obtain the online time and service weight of the service components on the preset platform;

[0024] If the online time is greater than a preset time threshold and the service weight is less than a preset weight threshold, the service component is updated.

[0025] Optionally, the detection of service components on the preset platform includes:

[0026] The service component is subjected to a health check at a preset number of times within a preset time period to obtain the health check result of whether the service component can provide services normally.

[0027] Optionally, the destruction of service components on the preset platform includes:

[0028] If the service corresponding to a service component is disconnected from the service component for more than a certain period of time, the service component will be destroyed from the preset platform.

[0029] Embodiments of the present invention also provide an automatic orchestration device for a service component pipeline, comprising:

[0030] The receiving module is used to receive requests from clients for automatic pipeline orchestration of at least one service component, sent by the client according to business requirements.

[0031] The processing module is used to automatically orchestrate the pipeline of at least one required service component according to the pipeline automatic orchestration request, and obtain the pipeline automatic orchestration result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform;

[0032] The execution module is used to automatically execute multiple management operation stages of the service component on a preset platform according to the pipeline of the at least one service component, and obtain the execution result;

[0033] The sending module is used to send the execution result back to the client.

[0034] The above-described solution of the present invention has at least the following beneficial effects:

[0035] The above-described solution of the present invention receives, through a preset platform, a request from a client to automatically orchestrate a pipeline for executing at least one service component based on business needs; according to the automatic orchestration request, the required pipeline for at least one service component is automatically orchestrated to obtain an automatic orchestration result for the pipeline of at least one service component; the pipeline includes the automatic execution process of at least one service component across multiple management operation stages on the preset platform; following the pipeline of at least one service component, the automatic execution of the service component across multiple management operation stages on the preset platform is performed to obtain an execution result; and the execution result is fed back to the client. This achieves automated execution of service components, meeting the intelligent requirements of integrated supply chain and full-process, full-value-chain collaboration. Attached Figure Description

[0036] Figure 1 This is a schematic flowchart of the automated orchestration method for service components in an embodiment of the present invention;

[0037] Figure 2 This is a schematic diagram of the pipeline of service components according to an embodiment of the present invention;

[0038] Figure 3 This is a schematic diagram of the automatic arrangement device for the service components of an embodiment of the present invention. Detailed Implementation

[0039] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0040] In the following embodiments of the present invention, a service component refers to a collection of services provided by an organization in a specific business domain. A service component is composed of multiple subsystems and modules; the service component completes the instantiation, configuration, and connection of modules. Subsystems are used to combine module elements, entry points, and extended services. Module elements provide a Java interface or a WSDL (Web Services Description Language) interface; modules combine elements together and selectively encapsulate the interfaces of elements as entry points; thus, the granularity of a module is larger than that of an element, and the granularity of a subsystem is higher than that of a module. A module is a "largest organizational unit" of tightly coupled component composition during development and deployment. In a service component, it is a loosely coupled "basic organizational unit." A module assembles elements, extended services, entry points, and the lines used to interconnect these objects. A module constructs a service component by implementing services. A module defines the visible boundaries of components; components cannot be directly referenced by external modules. Component communication within a module is local, while component communication between modules is remote.

[0041] A module element is a configuration instance of a module within a subsystem. A module is the implementation of a module element. The subsystem only focuses on the module element and the entry point it provides, not on the module's implementation details, such as parameters, extended services, etc.

[0042] An entry point is used to declare externally accessible services provided by a module. These services can be provided by components within the module or by external services referenced by the module. Entry points use bindings to link interfaces and implementations together.

[0043] The `<service>` element is a configuration instance of a service component, binding the implementation and interface together. The interfaces exposed by the `<service>` element support both Java and WSDL interfaces. Other types of interfaces can also be supported.

[0044] like Figure 1 As shown, an embodiment of the present invention proposes an automatic pipeline orchestration method for service components, comprising:

[0045] Step 11: Receive a pipeline auto-orchestration request from the client to execute at least one service component based on business requirements;

[0046] Step 12: Based on the pipeline auto-arrangement request, perform auto-arrangement processing on the pipeline of at least one required service component to obtain the pipeline auto-arrangement processing result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform.

[0047] Step 13: According to the pipeline of the at least one service component, automatically execute multiple management operation stages of the service component on the preset platform to obtain the execution result;

[0048] Step 14: Feedback the execution result to the client.

[0049] The above-described solution of the present invention receives, through a preset platform, a request from a client to automatically orchestrate a pipeline for executing at least one service component based on business needs; according to the automatic orchestration request, the required pipeline for at least one service component is automatically orchestrated to obtain an automatic orchestration result for the pipeline of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on the preset platform; according to the pipeline of at least one service component, the automatic execution of the service component in multiple management operation stages on the preset platform is executed to obtain an execution result; and the execution result is fed back to the client. Here, the preset platform can be a network collaborative manufacturing platform; the service component can be an information management system used in any link of the industrial chain or an information management system used by any manufacturer. The service component can support functional modules and standard interfaces for product R&D, design, manufacturing, operation and maintenance services, and collaborative manufacturing industry value chain, efficiently building, expanding, and connecting enterprise applications to achieve automated execution of the service component, overcome the differences between different management systems, and meet the intelligent needs of integrated industrial chain full-process and full-value chain collaboration.

[0050] In an optional embodiment of the present invention, step 12 above, which involves automatically orchestrating the pipeline of at least one required service component to obtain the automatic orchestration result of the pipeline of at least one service component, includes:

[0051] Step 121: According to the preset pipeline orchestration template, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline of at least one service component. The preset pipeline orchestration template includes: at least one stage executed by the service component, the environment corresponding to each stage, and at least one task atom included in each environment.

[0052] Here, each stage can have multiple parallel jobs, each job can specify a different environment, and at least one task is executed atomically in sequence.

[0053] like Figure 2 The image shows an example of a pipeline. Each column represents a stage, and each block represents a task atom. Various pipelines can be flexibly assembled according to business needs. Pipelines can be created starting from a blank template or from templates in a pipeline template library. Templates can pre-configure pipeline stages, build environments, atom types, etc., reducing the difficulty of pipeline orchestration. Optionally, each stage can have multiple parallel jobs, each job can specify a different build environment, allowing the building of programs in different build environments to proceed in parallel during the build stage, such as: backend services, web applications, and mobile applications. Each job can also have multiple task atoms that execute sequentially. Each task atom is configurable, and each atom template has specific functions. You can select an atom template under any atom type. For example, if you select the "Pull GitLab Repository Code" atom template, you can directly configure the GitLab code repository information for the atom in the graphical interface. When the pipeline executes to that atom, it will automatically pull the specified version of code from the specified repository according to the configuration. If you select a code inspection task template, you can configure the language and code inspection tools for the code inspection task; when the pipeline reaches that atom, it will start the code inspection platform to perform code scanning according to the specified settings.

[0054] In an optional embodiment of the present invention, step 13 may include:

[0055] Step 131: Based on the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, automatically execute at least one management operation among the discovery, registration, update, detection and destruction of the service component on the preset platform to obtain the execution result.

[0056] Here, the discovery of service components on the preset platform includes:

[0057] Step 1311: Receive service component online notification;

[0058] Step 1312: Generate a service component online notification event on a preset platform based on the service component online notification.

[0059] Step 1313: Based on the service component online notification event, generate a microservice instance corresponding to the service component. Here, the microservice instance can be an instance that provides any type of service. Each service is built around a specific business function and can be independently deployed to production environments, production-like environments, etc.

[0060] Here, the registration of service components on the preset platform includes:

[0061] Step 1314: Obtain the registration configuration information of the service component;

[0062] Step 1315: Configure the corresponding address, interface and resources for the service component according to the registration configuration information.

[0063] Here, the updates of service components on the preset platform include:

[0064] Step 1316: Obtain the online time and service weight of the service component on the preset platform;

[0065] Step 1317: If the online time is greater than a preset time threshold and the service weight is less than a preset weight threshold, update the service component.

[0066] Here, the detection of service components on the preset platform includes:

[0067] Step 1318: Perform health checks on the service component according to a preset number of checks within a preset time period to obtain the health check results of whether the service component can provide services normally.

[0068] Here, the destruction of service components on the preset platform includes:

[0069] Step 1319: If the service corresponding to the service component is disconnected from the service component for more than a certain period of time, the service component will be destroyed from the preset platform.

[0070] In the above embodiments of the present invention, the service components include, but are not limited to, business collaboration components and value chain optimization components; the client periodically retrieves service information from a preset platform and caches it locally. Even if the preset platform crashes, it will not affect the operation of the entire cluster, because the client has already cached the service information of the entire cluster.

[0071] The platform will periodically perform health checks on each service component. If a service component cannot connect, it will be marked as sub-healthy. In this case, the service component will not be removed, nor will it be returned to the customer for use. The check will then be repeated. If the service returns to normal within one minute, it will be remarked as healthy and can provide services. Otherwise, the service will be permanently removed.

[0072] Here, the Thrift (Remote Procedure Call) protocol can be used to implement service registration, discovery, health checks, and storage for service components and preset platforms.

[0073] In a specific implementation example, the above-mentioned automatic execution of at least one management operation among the discovery, registration, update, detection, and destruction of the service component on a preset platform is performed according to the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, and the execution result is obtained, including:

[0074] Based on the configuration information manually triggered in the first stage of the pipeline, the discovery of service components is triggered;

[0075] Based on the configuration information of the target task atoms in the second stage of the pipeline's build environment, the service components are registered;

[0076] Based on the third stage of the pipeline's compilation-free environment, at least one of the following should be performed on the service components: updating or testing.

[0077] Based on the fourth stage of the pipeline's build environment, the service components are destroyed.

[0078] During the registration process of the aforementioned service components, relevant data information can be queried from the target unit, and a pipeline can be generated based on business needs, software and hardware resources, data information, and other information.

[0079] The above embodiments of the present invention, by automatically orchestrating the pipeline of at least one required service component according to the pipeline auto-orchestration request, obtain the pipeline auto-orchestration result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform; according to the pipeline of the at least one service component, the automatic execution of the service component in multiple management operation stages on the preset platform is executed to obtain the execution result; the execution result is fed back to the client. This achieves automated execution of service components, meeting the intelligent needs of the entire industry chain; enables cluster management of service components, such as container scheduling, container performance monitoring, service discovery, health checks, cluster monitoring, etc.; allows for rapid deployment and application expansion, seamless integration with new application functions, while saving resources, optimizing hardware resource usage, and ultimately establishing a stateless, component-based network collaborative manufacturing platform.

[0080] like Figure 3 As shown, embodiments of the present invention also provide an automatic orchestration device 30 for a service component pipeline, comprising:

[0081] The receiving module 31 is used to receive a pipeline auto-orchestration request sent by the client according to business requirements to execute at least one service component;

[0082] Processing module 32 is used to automatically orchestrate the pipeline of at least one required service component according to the pipeline automatic orchestration request, and obtain the pipeline automatic orchestration result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform;

[0083] Execution module 33 is used to automatically execute multiple management operation stages of the service component on a preset platform according to the pipeline of the at least one service component, and obtain the execution result;

[0084] The sending module 34 is used to send the execution result back to the client.

[0085] Optionally, the pipeline of at least one required service component is automatically orchestrated to obtain the automatic orchestration result of the pipeline of at least one service component, including:

[0086] According to the preset pipeline orchestration template, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline of at least one service component. The preset pipeline orchestration template includes: at least one stage executed by the service component, the environment corresponding to each stage, and at least one task atom included in each environment.

[0087] Optionally, each stage can have multiple parallel jobs, each job can specify a different environment, and at least one task can be executed atomically in sequence.

[0088] Optionally, according to the pipeline of the at least one service component, the service component is automatically executed through multiple management operation stages on a preset platform to obtain execution results, including:

[0089] Based on the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, automatically execute at least one management operation of the service component in the preset platform, including discovery, registration, update, detection and destruction, and obtain the execution result.

[0090] Optionally, the discovery of service components on the default platform includes:

[0091] Receive service component launch notifications;

[0092] Based on the service component online notification, a service component online notification event is generated on a preset platform.

[0093] Based on the service component online notification event, a microservice instance corresponding to the service component is generated.

[0094] Optionally, the registration of service components on the preset platform includes:

[0095] Obtain the registration configuration information of the service components;

[0096] Based on the registration configuration information, configure the corresponding address, interface, and resources for the service component.

[0097] Optionally, updates to service components on the default platform include:

[0098] Obtain the online time and service weight of the service components on the preset platform;

[0099] If the online time is greater than a preset time threshold and the service weight is less than a preset weight threshold, the service component is updated.

[0100] Optionally, the detection of service components on the preset platform includes:

[0101] The service component is subjected to a health check at a preset number of times within a preset time period to obtain the health check result of whether the service component can provide services normally.

[0102] Optionally, the destruction of service components on the preset platform includes:

[0103] If the service corresponding to a service component is disconnected from the service component for more than a certain period of time, the service component will be destroyed from the preset platform.

[0104] It should be noted that this device corresponds to the above-mentioned automatic pipeline arrangement method for service components. All implementations of the above method are applicable to the embodiments of this device and can achieve the same technical effect.

[0105] Embodiments of the present invention also provide a computing device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0106] Embodiments of the present invention also provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0107] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0108] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0109] In the embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0110] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0111] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0112] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0113] Furthermore, it should be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Moreover, the steps performing the above-described series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve by using their basic programming skills after reading the description of the present invention.

[0114] Therefore, the object of the present invention can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of the present invention can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent to the present invention. Furthermore, the steps performing the above series of processes can naturally be performed in the order described, but are not necessarily required to be performed in chronological order. Some steps can be performed in parallel or independently of each other.

[0115] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for automatically orchestrating a pipeline of service components, characterized in that, include: Receives a pipeline auto-orchestration request from a client, based on business requirements, to execute at least one service component; The service component refers to a collection of services provided by an organization in a business domain. A service component is composed of multiple subsystems and modules. Based on the pipeline auto-arrangement request, the pipeline of at least one required service component is automatically arranged to obtain the pipeline auto-arrangement result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform. According to the pipeline of at least one service component, the service component is automatically executed in multiple management operation stages on a preset platform to obtain the execution result; The execution result is fed back to the client; Specifically, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline orchestration result of at least one service component, including: According to the preset pipeline orchestration template, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline of at least one service component. The preset pipeline orchestration template includes: at least one stage executed by the service component, the environment corresponding to each stage, and at least one task atom included in each environment. Each stage has multiple parallel jobs, each job specifies a different environment, and at least one task is executed atomically in sequence. According to the pipeline of at least one service component, the service component is automatically executed in multiple management operation stages on a preset platform to obtain the execution result, including: Based on the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, automatically execute at least one management operation among discovery, registration, update, detection, and destruction of the service component on a preset platform, and obtain the execution result; specifically including: triggering the discovery of the service component according to the manually triggered configuration information of the first stage of the pipeline; registering the service component according to the configuration information of the corresponding target task atoms in the build environment of the second stage of the pipeline; updating and detecting the service component according to the no-compilation environment of the third stage of the pipeline; and destroying the service component according to the build environment of the fourth stage of the pipeline. The discovery of service components on the default platform includes: Receive service component launch notifications; Based on the service component online notification, a service component online notification event is generated on a preset platform. Based on the service component online notification event, a microservice instance corresponding to the service component is generated; The registration of service components on the preset platform includes: Obtain the registration configuration information of the service components; Based on the registration configuration information, configure the corresponding address, interface and resources for the service component; Updates to service components on the default platform include: Obtain the online time and service weight of the service components on the preset platform; If the online time is greater than a preset time threshold and the service weight is less than a preset weight threshold, the service component is updated. The detection of service components on the preset platform includes: The service component is subjected to a health check within a preset time period and a preset number of checks to obtain the health check result of whether the service component can provide services normally. The destruction of service components on the preset platform includes: If the service corresponding to a service component is disconnected from the service component for more than a certain period of time, the service component will be destroyed from the preset platform.

2. An automatic arrangement device for a service component assembly line, characterized in that, include: The receiving module is used to receive requests from clients for automatic pipeline orchestration of at least one service component, sent by the client according to business requirements. The service component refers to a collection of services provided by an organization in a business domain. A service component is composed of multiple subsystems and modules. The processing module is used to automatically orchestrate the pipeline of at least one required service component according to the pipeline automatic orchestration request, and obtain the pipeline automatic orchestration result of at least one service component; the pipeline includes the automatic execution process of at least one service component in multiple management operation stages on a preset platform; Specifically, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline orchestration result of at least one service component, including: According to a preset pipeline orchestration template, the pipeline of at least one required service component is automatically orchestrated to obtain the pipeline of at least one service component. The preset pipeline orchestration template includes: at least one stage executed by the service component, the environment corresponding to each stage, and at least one task atom included in each environment; each stage has multiple parallel jobs, each job specifies a different environment, and at least one task atom is executed serially. An execution module is configured to automatically execute multiple management operation stages of the service component on a preset platform according to the pipeline of the at least one service component, and obtain execution results. Specifically, it includes: automatically executing at least one management operation of the service component in the preset platform, namely discovery, registration, update, detection, and destruction, according to the configuration information of the target task atoms in the target environment specified under each stage of the pipeline of the at least one service component, and obtaining execution results; specifically, it includes: triggering the discovery of the service component according to the manually triggered configuration information of the first stage of the pipeline; registering the service component according to the configuration information of the corresponding target task atoms in the build environment of the second stage of the pipeline; updating and detecting the service component according to the no-compilation environment of the third stage of the pipeline; and destroying the service component according to the build environment of the fourth stage of the pipeline. The discovery of service components on a preset platform includes: receiving a service component online notification; generating a service component online notification event on the preset platform based on the service component online notification; and generating a microservice instance corresponding to the service component based on the service component online notification event. The registration of a service component on a preset platform includes: obtaining the registration configuration information of the service component; and configuring the corresponding address, interface, and resources for the service component according to the registration configuration information. The update of a service component on a preset platform includes: obtaining the online time and service weight of the service component on the preset platform; if the online time is greater than a preset time threshold and the service weight is less than a preset weight threshold, the service component is updated. The detection of service components on the preset platform includes: performing health checks on the service components according to a preset number of checks within a preset time period, and obtaining health check results to determine whether the service components can provide services normally; The destruction of service components on the preset platform includes: if the service corresponding to the service component is disconnected from the service component for more than a certain period of time, the service component is destroyed from the preset platform; The sending module is used to send the execution result back to the client.

Images