Container service multi-level deployment method and device, storage medium and program product

Abstract

The invention provides a container service multi-level deployment method and device, a storage medium and a program product, and relates to the technical field of cloud computing. The method comprises the steps of obtaining multi-level container service configuration information and target task information, wherein the multi-level container service configuration information comprises dynamic storage and association relationships of environments, components, modules and deployment units; inputting the target task information into a pre-training container deployment analysis large model to obtain to-be-matched container information; according to the to-be-matched container information and the dynamic storage and association relationship of the environment, the component, the module and the deployment unit, a target deployment combination is obtained, and the target deployment combination comprises at least one environment, at least one component, at least one module and at least one deployment unit; and executing container service starting or capacity expansion operation based on the target deployment combination. The method has the effects of improving the automation level and flexibility of container service multi-level deployment and improving the container service resource utilization rate.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, specifically to the field of microservice architecture technology, and in particular to a multi-level deployment method, device, storage medium, and program product for container services. Background Technology

[0002] In microservice architecture systems in the financial industry (such as banks), containerization has become the mainstream technical solution. Bank systems typically contain multiple core components (such as distributed core platforms, routing services, customer information management, etc.), and each component is further divided into several functional modules (such as message processing modules, batch processing job modules, high-frequency trading sub-task modules, etc.). Each module may need to deploy multiple units according to business needs (such as batch processing units for different regional branches or deployment units for different file processing regions).

[0003] The container service startup method in related technologies requires developers to manually select a large number of environments (such as test environment, production environment), components, modules and deployment units one by one based on experience and requirements for configuration and startup. Especially when it comes to complex deployment scenarios involving cross-project and cross-module, developers need to repeatedly operate multiple interfaces and frequently switch configuration parameters, resulting in low deployment efficiency and easy errors.

[0004] Therefore, there is an urgent need for a multi-level deployment method for container services to improve the above situation. Summary of the Invention

[0005] This application provides a method, device, storage medium, and program product for multi-level deployment of container services, which aims to improve the automation level and flexibility of multi-level deployment of container services and increase the utilization rate of container service resources.

[0006] In a first aspect, embodiments of this application provide a multi-level deployment method for container services, including:

[0007] Obtain multi-level container service configuration information and target task information. The multi-level container service configuration information includes the dynamic storage and association relationships of environment, components, modules and deployment units.

[0008] The target task information is input into the pre-trained container deployment analysis model to obtain the container information to be matched.

[0009] Based on the container information to be matched and the dynamic storage and association relationships of the environment, components, modules and deployment units, a target deployment combination is obtained, wherein the target deployment combination includes at least one environment, at least one component, at least one module and at least one deployment unit;

[0010] Based on the target deployment combination, perform container service startup or scaling operations.

[0011] In one possible implementation, obtaining multi-level container service configuration information includes: obtaining environment information of the runtime environment of each container service and storing the environment information in a graphical manner through a persistent device; obtaining component information of each project component under the runtime environment information of each container service and storing the component information in a graphical manner through the persistent device; obtaining module information of each module under each project component and storing the module information in a graphical manner through the persistent device; obtaining unit information of each deployment unit under each module and storing the unit information in a graphical manner through the persistent device, so as to form a dynamic storage and association relationship based on environment, component, module and deployment unit as multi-level container service configuration information.

[0012] In one possible implementation, obtaining the target deployment combination based on the dynamic storage and association relationships of the container information to be matched and the environment, components, modules, and deployment units includes: performing a configuration matching operation by calling a graphical interface based on the dynamic storage and association relationships of the container information to be matched and the environment, components, modules, and deployment units, and extracting a target deployment combination containing at least one environment, at least one component, at least one module, and at least one deployment unit.

[0013] In one possible implementation, the method further includes: in response to a configuration selection operation performed by a user through a graphical user interface, obtaining a target deployment combination that includes at least one environment, at least one component, at least one module, and at least one deployment unit.

[0014] In one possible implementation, after performing container service startup or scaling operations based on the target deployment combination, the method further includes: obtaining the load status of the deployment unit, the load status including processor utilization and / or task queue length; and performing a container instance number adjustment operation based on the processor utilization and / or task queue length.

[0015] In one possible implementation, the method further includes: storing the target deployment combination as a deployment combination template to be reused; performing copy, modification, or deletion operations on the deployment combination template through a graphical user interface to obtain the deployment combination to be reused; and performing container service startup or scaling operations based on the deployment combination to be reused.

[0016] In one possible implementation, the method further includes: obtaining container service dynamic update data by calling a preset interface; maintaining the multi-level container service configuration information based on the container service dynamic update data, and obtaining the updated multi-level container service configuration information.

[0017] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0018] The memory stores computer-executed instructions;

[0019] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0021] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0022] This application provides a method, device, storage medium, and program product for multi-level container service deployment. The method first addresses the configuration issues of container service startup schemes being unable to cross environments, components, modules, and deployment units by using multi-level container service configuration information. Simultaneously, it utilizes a pre-trained container deployment analysis model to analyze target task information, obtaining matching container information. This allows for more accurate and rapid generation of the target deployment combination based on the matching container information and the dynamic storage and association relationships of environments, components, modules, and deployment units. Container service startup or scaling operations are then performed based on the target deployment combination. By automatically resolving hierarchical relationships and executing container service startup or scaling operations, manual selection of configuration items is eliminated, reducing the complexity of manual deployment operations and improving deployment efficiency. This achieves the effects of improving the automation level and flexibility of multi-level container service deployment and increasing container service resource utilization. Attached Figure Description

[0023] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0024] Figure 1 A schematic diagram illustrating a multi-level deployment process for a container service provided in this application;

[0025] Figure 2 A schematic diagram of a graphical interface provided in an embodiment of this application. Figure 1 ;

[0026] Figure 3 A schematic diagram of a graphical interface provided in an embodiment of this application. Figure 2 ;

[0027] Figure 4 A schematic diagram of a multi-level container service deployment device provided in this application;

[0028] Figure 5 A schematic diagram of the structure of the electronic device provided in this application.

[0029] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0030] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0031] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0032] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0033] In related technologies, container service startup solutions mainly rely on container orchestration systems (such as Kubernetes) or customized container management tools. The container service startup process mainly includes: 1) defining the deployment parameters of the container service (such as image version, resource quota, network policy) through configuration files or command lines; 2) starting the container service at the project level and increasing the number of container instances through horizontal scaling (scale-out); 3) dynamically adjusting container resources through monitoring tools. It is evident that the above-mentioned technologies cannot quickly combine project components, modules, or deployment units into a unified startup task, resulting in manual selection and startup for cross-project deployments, leading to low efficiency. Furthermore, manual operation can easily lead to uneven distribution of container service resources; for example, in batch processing scenarios, it may be impossible to dynamically allocate the number of deployment units based on the load of different regions.

[0034] Therefore, to address the aforementioned technical challenges, the applicant proposes a multi-layered dynamic maintenance mechanism and a visual pluggable configuration framework to achieve automated deployment of container services across environments, components, modules, and deployment units. The core of this approach lies in abstracting the deployment requirements of container services into a dynamically maintainable four-layer structure: environment, components, modules, and deployment units, and storing information at each layer through persistent storage. Based on this, a visual interface is provided to support user-defined combinations of startup tasks. This ultimately improves the automation and flexibility of multi-layered container service deployment and enhances the utilization of container service resources.

[0035] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0036] Figure 1 This application provides a flowchart illustrating a multi-level deployment process for a container service, as shown below. Figure 1 As shown, the method includes:

[0037] S101: Obtain multi-level container service configuration information and target task information. The multi-level container service configuration information includes the dynamic storage and association relationships of the environment, components, modules and deployment units.

[0038] In this embodiment, the environment in the multi-level container service configuration information can be the environment in which all container services run. These environments can be obtained by the user in advance through environment enumeration. Components can be all project components in the corresponding environment. For example, all components under all financial service projects can include distributed core platform components, routing components, customer information components, index maintenance components, and digital account service system components.

[0039] In this embodiment, a module can be any functional module under all components. For example, modules under the distributed core platform component include a time receiving module, a private microservice-quick module, a batch job configuration module, etc.

[0040] In this embodiment, the deployment unit can be used to maintain various processing units under all modules. Examples include public batch processing, batch file transfer, and public batch processing. Dynamic storage and association refer to the fact that each environment has corresponding components, each component has corresponding modules, and each module has corresponding deployment units. These components form multi-level container service configuration information through hierarchical associations.

[0041] In this embodiment, the target task information may be a detailed description of the container service deployment task obtained by the user through the terminal. The target task information may be a piece of voice, a piece of text, a piece of code, or a file.

[0042] Based on the above embodiments, in an optional embodiment of this application, step S101, obtaining multi-level container service configuration information, includes:

[0043] S101a: Obtain the environment information of each container service's runtime environment and store the environment information in a graphical way through a persistent device.

[0044] In this embodiment, the runtime environment information of each container service can be maintained by the user through a graphical enumeration method. For example, when the user adds a specific verification VT environment in the graphical interface, the system automatically persists it and displays it in the environment list. The persistence device in this embodiment can be a data block or a configuration file, or it can be a combination of hardware storage and software management system working together. The hardware storage is responsible for storing data at the physical level, while the software management system is responsible for managing data at the logical level.

[0045] Storing environmental information in a graphical way can be done by displaying the environmental information in visual graphics, tables, or other content that is easy for users to view, such as: development test pl1 environment, integration test pl2 environment, system test pl3 environment, pre-production pl4 environment, special verification vt environment, and non-public performance environment.

[0046] S101b: Obtain the component information of each project component under the environment information of each container service running, and store the component information in a graphical way through a persistent device.

[0047] In this embodiment, the component maintenance function is used to maintain all project components corresponding to each environment through a persistent storage device in a graphical manner. Taking the financial services project component as an example, the maintenance process is as follows:

[0048] APD01 Distributed Core Platform;

[0049] F5001 Router;

[0050] A0042 Customer Information;

[0051] DP001 index maintenance;

[0052] A3391 Digital Account Service System.

[0053] S101c: Retrieves module information for each module under each project component and stores this module information in a graphical manner via a persistent storage device.

[0054] In this embodiment, the module maintenance function is used to maintain all module information corresponding to each component through a persistent device in a graphical manner. Taking the module information under the APD001 distributed core platform in the above example as an example, the maintenance process is as follows:

[0055] APD01: erm time receiving module;

[0056] km message processing;

[0057] KAX Private Microservices - Quick Module;

[0058] JCB batch job configuration module;

[0059] kt timer module;

[0060] bsb batch processing module;

[0061] ka refers to the private microservice module;

[0062] HSB high-frequency subtask module;

[0063] ISB batch processing access module;

[0064] DTM (Transaction Management) module.

[0065] S101d: Obtain the unit information of each deployment unit under each module, and store the unit information in a graphical way through a persistent device to form a dynamic storage and association relationship based on environment, component, module and deployment unit as multi-level container service configuration information.

[0066] In this embodiment, the deployment unit maintenance function is used to maintain all unit information under each module through a persistent storage device in a graphical manner. Taking the BSB batch processing module in the above example as an example, the maintenance process is as follows:

[0067] bsb: skb1 is for batch processing of public data;

[0068] nfb1 batch file transfer;

[0069] psb1 Common Batch Processing;

[0070] Batch processing of fsb1 files;

[0071] pkbqh handles private batch processing of Qinghai trips;

[0072] pkbdl handles private batch processing in Dalian.

[0073] ...;

[0074] fsbs1 file batch processing (Southern Taiwan);

[0075] fsbn1 file batch processing (Northern region);

[0076] fsbe1 file batch processing (Eastern Region);

[0077] fsbw1 file batch processing (Western region).

[0078] S102: Input the target task information into the pre-trained container deployment analysis model to obtain the information of the container to be matched.

[0079] In this embodiment, the pre-trained container deployment analysis model can be a large model obtained by training an open-source analysis model or a machine learning model using a training set and a validation set of task information related to container deployment. The open-source analysis model can be a natural language processing (NLP) model. After the pre-trained container deployment analysis model analyzes the target task information and extracts key information, the information of the container to be matched can be obtained.

[0080] S103: Based on the container information to be matched and the dynamic storage and association relationships of environment, components, modules and deployment units, obtain the target deployment combination, wherein the target deployment combination includes at least one environment, at least one component, at least one module and at least one deployment unit.

[0081] In this embodiment, the container information to be matched includes the environment, components, modules, and deployment units to be deployed, as well as the relationships between these environments, components, modules, and deployment units. Through matching the container information to be matched with the previously maintained dynamic storage and relationship indexing, a target deployment combination including at least one environment, at least one component, at least one module, and at least one deployment unit is automatically obtained.

[0082] Based on the above embodiments, in an optional embodiment of this application, step S103 specifically includes: calling the configuration matching operation performed by the graphical interface according to the dynamic storage and association relationship of the container information to be matched and the environment, components, modules and deployment units, and extracting the target deployment combination containing at least one environment, at least one component, at least one module and at least one deployment unit.

[0083] In this embodiment, a configuration matching operation can be performed by calling the dynamic storage and association relationship of the container information to be matched and the environment, components, modules and deployment units through a graphical interface, through pre-written automated tools, code or automated instructions, to extract a target deployment combination containing at least one environment, at least one component, at least one module and at least one deployment unit.

[0084] In another optional embodiment of this application, step S103 further includes: in response to a configuration selection operation performed by a user through a graphical user interface, obtaining a target deployment combination that includes at least one environment, at least one component, at least one module and at least one deployment unit.

[0085] In this embodiment, users can select at least one environment, at least one component, at least one module, and at least one deployment unit as a target deployment combination by dragging, clicking, or other operations in the graphical interface. For example, based on the above example, users can select "pl2 environment-A0042 component-bsb module-pkbqh unit" by dragging in the web interface.

[0086] S104: Execute container service startup or scaling operations based on target deployment combinations.

[0087] In this embodiment, an automated process for creating or adjusting the number of container instances is executed based on the target deployment. For example, the "Private Batch Processing Qinghai pkbqh Unit" can be dynamically started or expanded to 3 instances via the Kubernetes API of the container cluster management system or a custom orchestrator.

[0088] Based on the above embodiments, in an optional embodiment of this application, after step S104, the following step is further included:

[0089] Step A: Obtain the load status of the deployment unit, including processor utilization and / or task queue length;

[0090] Step B: Perform a container instance number adjustment operation based on processor utilization and / or task queue length.

[0091] In this embodiment, the load status can be an operational metric of the deployment unit, generally including at least one of processor utilization and task queue length, which can be used to evaluate resource requirements. For example, when the processor utilization of the pkbqh unit for private batch processing in Qinghai exceeds 80%, expansion is triggered. The system will automatically expand the number of container instances in the pkbqh unit, completing the container instance number adjustment operation. When the processor utilization is below 40%, shrinking is triggered, and the number of container instances in the pkbqh unit is automatically reduced.

[0092] By dynamically adjusting the number of container instances based on load status, resources are allocated on demand, ensuring that Case expands load units during peak business hours and automatically shrinks them during off-peak hours, thus avoiding resource waste.

[0093] A multi-level deployment method for container services provided in an optional embodiment of this application further includes:

[0094] Step C: Store the target deployment combination as a deployment combination template to be reused.

[0095] In this embodiment, the deployment template to be reused is a reusable configuration file that represents the combination of storage environment, components, modules, and deployment units.

[0096] In an optional embodiment of this application, when a user selects a target environment, component, or module set deployment unit through a graphical interface, the system parses the combination relationship of these selections into a reusable deployment template. This template is then stored using a persistent storage device (such as a database). For example, if a user selects "pl2 environment-A0042 component-bsb module-pkbqh unit", the system automatically stores this combination as deployment template A. This template can be called in subsequent deployment tasks, avoiding redundant configuration.

[0097] This allows users to select combinations of environments, components, modules, and deployment units through a graphical interface and store them as reusable deployment templates, achieving structured management and reuse of configuration information. Users no longer need to manually enter configuration items each time; instead, they can quickly generate deployment templates through the interface, reducing configuration errors and improving deployment efficiency. Furthermore, the deployment template storage function allows users to quickly recall frequently used combinations, enhancing the system's flexibility and maintainability.

[0098] Step D: Perform copy, modify, or delete operations on the deployment combination template through the graphical user interface to obtain the deployment combination to be reused.

[0099] In this embodiment, based on the deployment combination template, users can freely combine environments, components, modules, and deployment units on the graphical interface in real time according to the needs of the current task by dragging, copying, and modifying, generating reusable startup devices. Building upon the above example, a user can define and adjust the original deployment combination template "pl2 environment - APD01 component - bsb module - pkbqh private batch processing unit" to "pl2 environment - APD01 component - bsb module - pkbql private batch processing unit". This only requires adjusting one deployment unit, eliminating the need for the user to reselect the environment, components, modules, and deployment units. This makes the operation more convenient.

[0100] Step E: Perform container service startup or scaling operations based on the deployment combination to be reused.

[0101] In this embodiment, the implementation principle of step E is similar to that of step S104, so it will not be described in detail here.

[0102] Based on the above embodiments, an optional embodiment of this application provides a multi-level deployment method for container services, which further includes:

[0103] Step F: Obtain dynamically updated data from the container service by calling the preset interface.

[0104] Step G: Maintain multi-level container service configuration information based on the container service dynamic update data to obtain the updated multi-level container service configuration information.

[0105] In this embodiment, the preset interface can be an application programming API (API) interface. Configuration data is dynamically updated by calling the API interface, for example, calling the " / api / update-deployment-unit" interface to update the configuration information of the "pkbqh unit". Of course, besides the method of obtaining dynamically updated container service data in step F, users can also obtain dynamically updated container service data by enumerating according to application requirements or by customizing hierarchical relationships through configuration files.

[0106] This multi-level configuration information maintenance approach, supporting databases, configuration files, or API calls, enables flexible management of configuration data. Users can choose the most suitable maintenance method based on their actual needs; for example, using configuration files to quickly modify configurations in a development environment, and centrally managing configurations through a database in a production environment. Furthermore, the dynamic update capability of API calls ensures real-time synchronization of configuration information, avoiding deployment errors caused by configuration lag.

[0107] Figure 2 A schematic diagram of a graphical interface provided in an embodiment of this application. Figure 1 .

[0108] To more clearly and intuitively demonstrate the graphical interface provided in the above embodiments of the present invention, such as... Figure 2 As shown in the example above, the interface includes: target task information (task name), component (APD001); module (bsb); creation time December 19, 2023, total (40). Users can select the corresponding quick deployment unit on this interface.

[0109] Figure 3 A schematic diagram of a graphical interface provided in an embodiment of this application. Figure 2 .

[0110] like Figure 3 As shown, users can quickly search for corresponding components on this graphical interface, or perform corresponding operations such as packaging, starting, stopping, or scaling container services. Users can also choose deployment combinations that they no longer use.

[0111] In summary, the multi-level container service deployment method provided in this application addresses the issue of container service startup schemes being unable to configure across environments, components, modules, and deployment units by utilizing multi-level container service configuration information. Simultaneously, a pre-trained container deployment analysis model is used to analyze target task information, obtaining matching container information. This allows for more accurate and rapid generation of the target deployment combination based on the matching container information and the dynamic storage and association relationships of environments, components, modules, and deployment units. Container service startup or scaling operations are then performed based on the target deployment combination. By automatically resolving hierarchical relationships and executing container service startup or scaling operations, the need for manual selection of configuration items is eliminated, reducing the complexity of manual deployment operations and improving deployment efficiency. This achieves the effects of improving the automation level and flexibility of multi-level container service deployment and increasing container service resource utilization.

[0112] Figure 4 A schematic diagram of a multi-level deployment device for container services provided in this application is shown below. Figure 4 As shown, the container service multi-level deployment device provided in this embodiment includes:

[0113] The data maintenance module 41 is used to obtain multi-level container service configuration information and target task information. The multi-level container service configuration information includes the dynamic storage and association relationships of the environment, components, modules and deployment units.

[0114] The analysis and processing module 42 is used to input the target task information into the pre-trained container to deploy and analyze the large model, and obtain the information of the container to be matched.

[0115] The deployment combination module 43 is used to obtain the target deployment combination based on the container information to be matched and the dynamic storage and association relationship of environment, component, module and deployment unit, wherein the target deployment combination includes at least one environment, at least one component, at least one module and at least one deployment unit.

[0116] Operation module 44 is used to perform container service startup or scaling operations based on the target deployment combination.

[0117] In one possible implementation, the data maintenance module 41 is specifically used for: obtaining environment information of the runtime environment of each container service and storing the environment information in a graphical manner through a persistent device; obtaining component information of each project component under the runtime environment information of each container service and storing the component information in a graphical manner through a persistent device; obtaining module information of each module under each project component and storing the module information in a graphical manner through a persistent device; obtaining unit information of each deployment unit under each module and storing the unit information in a graphical manner through a persistent device, so as to form a dynamic storage and association relationship based on environment, component, module and deployment unit as multi-level container service configuration information.

[0118] In one possible implementation, the deployment combination module 43 is specifically used to: perform configuration matching operations by calling the graphical interface based on the dynamic storage and association relationships of the container information to be matched and the environment, components, modules and deployment units, and extract a target deployment combination that includes at least one environment, at least one component, at least one module and at least one deployment unit.

[0119] In one possible implementation, the deployment combination module 43 is further specifically used to: obtain a target deployment combination that includes at least one environment, at least one component, at least one module and at least one deployment unit in response to a configuration selection operation performed by the user through a graphical user interface.

[0120] In one possible implementation, the data maintenance module 41 is further configured to: obtain the load status of the deployment unit, including processor utilization and / or task queue length; and perform a container instance number adjustment operation based on the processor utilization and / or task queue length.

[0121] In one possible implementation, the deployment combination module 43 is further configured to: store the target deployment combination as a deployment combination template to be reused; perform copy, modification or deletion operations on the deployment combination template through a graphical operation interface to obtain the deployment combination to be reused; and perform container service startup or scaling operations based on the deployment combination to be reused.

[0122] In one possible implementation, the data maintenance module 41 is further configured to: obtain dynamically updated container service data by calling a preset interface; maintain multi-level container service configuration information based on the dynamically updated container service data, and obtain the updated multi-level container service configuration information.

[0123] The container service multi-level deployment device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0124] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the electronic device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus.

[0125] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0126] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0127] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0128] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0129] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0130] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0131] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0132] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0133] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0134] The division of units is merely a logical functional division; 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 indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0135] 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, depending on actual needs.

[0136] 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.

[0137] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part 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 of 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, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0138] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0139] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for multi-level deployment of container services, characterized in that, include: Obtain multi-level container service configuration information and target task information. The multi-level container service configuration information includes the dynamic storage and association relationships of the environment, components, modules and deployment units. The target task information is input into the pre-trained container deployment analysis model to obtain the container information to be matched. Based on the container information to be matched and the dynamic storage and association relationships of the environment, components, modules and deployment units, a target deployment combination is obtained, wherein the target deployment combination includes at least one environment, at least one component, at least one module and at least one deployment unit; Based on the target deployment combination, perform container service startup or scaling operations.

2. The method according to claim 1, characterized in that, The process of obtaining multi-level container service configuration information includes: Obtain the environment information of each container service's runtime environment, and store the environment information in a graphical manner through a persistent device; Obtain the component information of each project component under the environment information of each container service, and store the component information in a graphical manner through the persistent device; Obtain the module information of each module under each project component, and store the module information in a graphical manner through the persistence device; The unit information of each deployment unit under each module is obtained, and the unit information is stored in a graphical manner through the persistent device to form a dynamic storage and association relationship based on environment, component, module and deployment unit as multi-level container service configuration information.

3. The method according to claim 1, characterized in that, The step of obtaining the target deployment combination based on the information of the container to be matched and the dynamic storage and association relationships of the environment, components, modules, and deployment units includes: Based on the container information to be matched and the dynamic storage and association relationships of the environment, components, modules and deployment units, a configuration matching operation is performed by calling the graphical interface to extract a target deployment combination containing at least one environment, at least one component, at least one module and at least one deployment unit.

4. The method according to claim 3, characterized in that, Also includes: In response to a configuration selection operation performed by a user through a graphical user interface, a target deployment combination is obtained, which includes at least one environment, at least one component, at least one module, and at least one deployment unit.

5. The method according to any one of claims 1 to 4, characterized in that, After performing container service startup or scaling operations based on the target deployment combination, the process further includes: Obtain the load status of the deployment unit, including processor utilization and / or task queue length; The number of container instances is adjusted based on the processor utilization and / or task queue length.

6. The method according to claim 1, characterized in that, Also includes: Store the target deployment combination as a deployment combination template to be reused; By performing copy, modification, or deletion operations on the deployment combination template through a graphical user interface, a deployment combination to be reused can be obtained. Execute container service startup or scaling operations based on the aforementioned deployment combination to be reused.

7. The method according to claim 1, characterized in that, Also includes: Get dynamically updated data from the container service by calling a preset interface; The configuration information of the multi-level container service is maintained based on the dynamically updated container service data, and the updated configuration information of the multi-level container service is obtained.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 7.

Images