Configuration processing method, device, medium, equipment and product for large model application

Abstract

A configuration processing method, device, medium, equipment and product of a large model application. Including: in response to detecting a new component, obtaining application information, the application information is used to indicate a first application; generating first configuration information, the first configuration information is associated with the first application, the format of the first configuration information matches the new component; in response to detecting that a container group runs on a node, obtaining the first configuration information, the container group is associated with the first application, and the node is associated with the new component; based on the first configuration information, configure the container group.

Description

Technical Field

[0001] This article relates to the field of computer technology, and more specifically, to a configuration processing method, apparatus, medium, device, and product for large-scale model applications. Background Technology

[0002] Model as a Service (MaaS) cloud service providers can offer large models as a service to model users. When using services related to large models, model users typically containerize and deploy the large models in a cluster. To ensure security, multiple components are usually deployed within the cluster, and the configuration and management of these components are usually done manually, which is very inefficient. Summary of the Invention

[0003] This content section is provided to briefly introduce the ideas, which will be described in detail in the examples section later. This content section is not intended to identify key or essential features of the claimed content, nor is it intended to limit the scope of the claimed content.

[0004] Firstly, a configuration processing method for large-scale model applications is provided, including: In response to the detection of a new component, application information is obtained, which is used to indicate a first application; Generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component; In response to detecting that a container group is running on a node, the first configuration information is obtained, wherein the container group is associated with the first application and the node is associated with the newly added component; The container group is configured based on the first configuration information.

[0005] Secondly, a configuration processing device for large-scale model applications is provided, comprising: The first acquisition module is used to acquire application information in response to the detection of a new component, wherein the application information is used to indicate a first application; A first generation module is used to generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component. The second acquisition module is used to acquire the first configuration information in response to detecting that a container group is running on a node, wherein the container group is associated with the first application and the node is associated with the newly added component; The configuration module is used to configure the container group based on the first configuration information.

[0006] Thirdly, a computer-readable medium is provided having a computer program stored thereon, wherein the computer program, when executed by a processing device, implements the method described in the first aspect.

[0007] Fourthly, an electronic device is provided, comprising: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the method described in the first aspect.

[0008] Fifthly, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method described in the first aspect.

[0009] The above method, in response to the detection of a new component, obtains application information, which is used to instruct the first application to generate first configuration information. This first configuration information is associated with the first application, and its format matches the new component. In response to the detection of a container group running on a node, the first configuration information is obtained again, and the container group is configured based on this information. The container group is associated with the first application, and the node is associated with the new component. Therefore, when a new component is added, first configuration information related to and matching the format of the new component can be automatically generated for the first application. When the container group runs on a node managed by the new component, the generated first configuration information is automatically used to configure the container group. In other words, if a new component is added to the cluster, configuration information that the new component can recognize can be automatically generated for applications already deployed in the cluster. When the new component needs configuration, it is configured according to this information. Regardless of where the application's container group is subsequently scheduled within the cluster, the configuration can be executed correctly without manual intervention, and the configuration efficiency is high. Thus, even if the types of components in the cluster are different, the configuration information of applications under different components can be automatically synchronized, ensuring configuration consistency and accuracy even in complex cluster structures.

[0010] Other features and advantages will be described in detail in the following examples section. Attached Figure Description

[0011] The above and other features, advantages, and aspects of this document will become more apparent when viewed in conjunction with the accompanying drawings and the following examples. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1 This is an application scenario diagram illustrating the configuration processing method for large model applications based on certain situations; Figure 2 This is a flowchart illustrating the configuration processing methods for large model applications under certain circumstances; Figure 3 This is a block diagram illustrating the configuration processing device for a large model application, based on certain scenarios. Figure 4 A schematic diagram of an electronic device suitable for implementing the above method is shown. Detailed Implementation

[0012] The following description will be given in more detail with reference to the accompanying drawings. While certain scenarios are shown in the drawings, it should be understood that this document can be implemented in various forms and should not be construed as limited to the scenarios described herein. Rather, these scenarios are provided to provide a more thorough and complete understanding of this document. It should be understood that the accompanying drawings and the scenarios depicted are for illustrative purposes only and are not intended to limit the scope of this document.

[0013] It should be understood that the steps described in the method may be performed in different orders and / or in parallel. Furthermore, the method may include additional steps and / or omit the steps shown. The scope of this document is not limited in this respect.

[0014] The term "comprising" and its variations can be open-ended, meaning "including but not limited to". The term "based on" can mean "at least partially based on". The term "one case" means "at least one case"; the term "another case" means "at least one additional case"; the term "some cases" means "at least some cases". Definitions of other terms will be given in the following description.

[0015] It should be noted that the concepts of "first" and "second" are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0016] It should be noted that the modifiers “one” and “multiple” can be illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as “one or more”.

[0017] The names of messages or information exchanged between multiple devices are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0018] It is understandable that the data involved in the technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of relevant regulations.

[0019] As described in the background section, in the Model-as-a-Service (MAS) model, model providers offer large model entities, and cloud service providers take over these large models and then use them to provide services such as inference and fine-tuning. Large models refer to deep learning models trained on large amounts of data, possessing complex computational structures, capable of handling complex tasks, and exhibiting a certain degree of generalization. They can understand, generate, reason about, and interact with various types of information, including text, images, audio, video, and code. Large models can include various types, such as large language models, visual large models, multimodal large models, visual-language-action models, and world models. The capabilities of large models are typically provided externally as large model services, which package large models and their capabilities into reusable services for rapid deployment. Large model services are usually implemented based on large model applications deployed in a cluster. Large model applications can refer to applications with large models as their core functions or components. Large model services can be deployed in a containerized manner, meaning that the large model application runs in a container group, and the container group runs in the cluster. A cluster can include multiple nodes, which are the basic units for running workloads within the cluster. Nodes can be physical servers or virtual machines, and each node can include the core components required to run a container group (Pod). Large model applications can be deployed in a cluster, corresponding to at least one container group. A container group can consist of at least one container, and the container group runs on the nodes of the cluster. The configuration of the container group on a node is achieved through the components installed on that node. When model users utilize the model service, they expect tasks to run in a secure environment, which requires configuration. In related technologies, the above configuration needs to be written by the user as needed, which is cumbersome and inefficient.

[0020] To address the aforementioned issues, a configuration processing method, apparatus, medium, device, and product for large-scale model applications are provided.

[0021] Figure 1 This is a schematic diagram illustrating application scenarios for configuration processing methods in large-scale model applications, based on certain situations. For example... Figure 1 As shown, this application scenario can include a client 100 and a server 200. The client 100 can communicate with the server 200. It should be understood that this communication connection can refer to data interaction via a wired or wireless connection. The configuration processing method for this large-scale application can be executed by the server 200.

[0022] Client 100 can refer to the terminal device used by the user (e.g., a computer). Client 100 can display an interface that allows the user to view the cluster status or trigger operations, including but not limited to adding a new node to the cluster and deleting a node from the cluster. For example, client 100 can send a node join request to server 200 to add a new node and can receive feedback information returned by server 200.

[0023] Server 200 may include control center 210 and cluster 220, and cluster 220 may include at least one node. Control center 210 can communicate with the nodes in cluster 220. Control center 210 can be located inside or outside cluster 220, without restriction. Container groups of applications can run on the nodes of cluster 220, and components (such as network components) can be installed on the nodes. The types of components installed on different nodes can be the same (homogeneous components) or different (heterogeneous components).

[0024] When a new node (managed by the new component) is added to cluster 220, control center 210 can detect the new component and perform a series of operations on the new component, such as generating first configuration information that is associated with the first application deployed in the cluster and can be recognized by the new component, and configuring the container group according to the first configuration information when it is detected that the container group of the first application is running on the node managed by the new component.

[0025] Figure 2 This is a flowchart illustrating a configuration processing method for a large model application under certain circumstances. This configuration processing method for a large model application can be executed by a configuration processing device for a large model application, which can be implemented in software and / or hardware. For example... Figure 2 As shown, the method may include steps 21 to 24.

[0026] In step 21, in response to the detection of a new component, application information is obtained, which is used to indicate the first application.

[0027] When a new node is added to the cluster, this node has a component installed and is managed by that component. The presence of a new component can be determined based on the addition of the new node. In other words, the addition of a new node to the cluster can be used as a trigger to detect the presence of a new component. Once the presence of a new component is detected, subsequent processes can be triggered. The detection method for the new component can be configured according to actual needs.

[0028] In some cases, a new component can be of any type, and it can be detected in the following ways: In response to the detection of a new node in the cluster, it is determined that a new component has been detected.

[0029] In other words, if any type of component can be added as a new component, the addition of a new node in the cluster can be used as a trigger event. Once a new node is detected in the cluster, the component on that new node will be added as the new component.

[0030] In some cases, a new component may be a component of a different type than those already existing in the cluster. New components can be detected in the following ways: In response to the detection of a new node in the cluster, obtain the component type of the components on the new node; Match the component type with the component types that already exist in the cluster; If a match fails, it is determined that a new component has been detected.

[0031] In other words, when a new node is added to the cluster, the component type of the new node is first matched against the component types of all already installed components in the cluster. If the component type of the new node matches a component type already installed in the cluster, it is determined that no new component has been added, and the subsequent process is not triggered. If the component type of the new node cannot match any component type already installed in the cluster, it is determined that a new component has been added, and the subsequent process is triggered. This allows for the automatic configuration of heterogeneous components in the cluster.

[0032] In some cases, the added component can be the Container Network Interface (CNI).

[0033] In some cases, the newly added component can also be a permission-related component, such as a component related to storage permissions or a component related to access permissions.

[0034] Upon detecting a new component in the cluster, application information can be obtained. This application information can be used to indicate the application deployed in the cluster (the first application). Optionally, the first application can refer to at least one application currently deployed in the cluster, such as any application, any number of applications, or all applications.

[0035] Optionally, an application list can be set up in the cluster to manage the applications currently deployed in the cluster. When a new component is detected, the application information can be obtained by querying the application list. This application list can record the real-time application deployment status within the cluster. When an application is added to the cluster, its information is added to the application list; when an application is deleted from the cluster, its information is removed from the application list. Different applications in the cluster can be distinguished by different application identifiers, and the application list can record the applications currently deployed in the cluster by recording the application identifiers.

[0036] In step 22, first configuration information is generated, which is associated with the first application, and the format of the first configuration information matches the newly added component.

[0037] Optionally, if there is more than one first application, first configuration information can be generated for at least one first application separately. For example, first configuration information can be generated for each first application separately. The generation of first configuration information for one first application will be explained here, and the generation of each first configuration information can be referred to the description here. The first configuration information can be used to indicate the complete configuration information corresponding to the first application. The first configuration information can also be used to indicate the partial configuration information corresponding to the first application.

[0038] Based on the first application, configuration information matching the format of the new component can be generated according to the configuration requirements of the first application itself, and used as the first configuration information associated with the first application, so that the first configuration information can be recognized by the new component.

[0039] In some cases, the first configuration information can be generated in the following ways: Obtain the first configuration requirement information, which corresponds to the first application.

[0040] Based on the first configuration requirement information, generate the first configuration information so that the format of the first configuration information matches the newly added component.

[0041] Application configuration requirements can be used to indicate requirements related to application configuration. Configuration requirements may include, for example, allowing access between containers within the same container group and prohibiting access to external clusters.

[0042] Optionally, if there is more than one first application, the configuration requirement information of each of the at least one first application can be obtained as the first configuration requirement information. For example, the first configuration requirement information can be obtained for each first application separately. The following will explain how to obtain the first configuration requirement information for a single first application.

[0043] In some cases, the first configuration requirement information may include the configuration requirements of components already existing in the cluster. Optionally, the configuration information already configured by the first application under existing components in the cluster can be searched, and the semantic content of the configuration information can be extracted to form the first configuration requirement information. For example, the semantic content of the configuration information can be extracted using a machine learning model.

[0044] In some cases, configuration templates can be set up in the cluster, such as requirement description files related to the configuration requirements of different applications. Optionally, the first configuration requirement information can be obtained from the configuration template corresponding to the first application set up in the cluster.

[0045] In some cases, preset configuration rules can be set in the cluster. Optionally, the first configuration requirement information can be obtained through the configuration rules stored in the cluster. For example, if the first application does not have any configuration related to any component, the first configuration requirement information can be obtained through the configuration rules.

[0046] After obtaining the initial configuration requirements, for each initial configuration requirement, configuration information with a format matching the new component can be generated, which is the initial configuration information. Based on the initial configuration information, the new component can recognize the configuration of any application in the cluster and execute it.

[0047] In some cases, conversion rules between configuration requirement information and configuration information can be stored. Based on these conversion rules, the first configuration requirement information can be converted into a format that can be recognized by the newly added component to obtain the first configuration information.

[0048] In some cases, machine learning models can be used to convert the initial configuration requirements into a format that can be recognized by the new component. Optionally, a large model can be used as the machine learning model.

[0049] Optionally, generating the first configuration information based on the first configuration requirement information may include the following steps: Retrieve component information; the component information corresponds to the newly added component. Select the configuration format based on the component information; Based on the configuration format and the first configuration requirement information, first configuration information is generated so that the format of the first configuration information matches the configuration format.

[0050] The component information of a newly added component may include, but is not limited to, at least one of the following: the component identifier of the newly added component, the component name of the newly added component, and the version information of the newly added component.

[0051] Different component information can be associated with different configuration formats. By obtaining the component information of the newly added component, the corresponding configuration format can be determined. Then, the first configuration requirement information can be filled or combined according to the configuration format to obtain the first configuration information.

[0052] In some cases, the configuration format can correspond to a configuration template, which can set fields to be filled. The field content corresponding to the field to be filled is extracted from the first configuration requirement information and filled into the position corresponding to the field to be filled in the configuration template to form the first configuration information.

[0053] After generating the first configuration information, it can be stored in a first storage location. When storing the first configuration information, it is associated with a first application so that the corresponding first configuration information can be found based on the first application later. The first storage location can correspond to a newly added component, allowing the new component to directly retrieve configuration information from the first storage location when needed. Thus, when an application's container group is scheduled to run on a node managed by a newly added component, the new component can obtain the first configuration information associated with that application through the first storage location and perform configuration management based on that information.

[0054] In step 23, in response to detecting that a container group is running on a node, first configuration information is obtained, the container group is associated with the first application, and the node is associated with the newly added component.

[0055] In step 24, the container group is configured based on the first configuration information.

[0056] When it is detected that a container group associated with the first application is running on a node managed by the newly added component, first configuration information associated with the first application and matching the format of the newly added component can be obtained. For example, the first configuration information associated with the first application can be obtained from the first storage location mentioned above. Then, based on the first configuration information, the container group of the first application is configured.

[0057] The above method, in response to the detection of a new component, obtains application information, which is used to instruct the first application to generate first configuration information. This first configuration information is associated with the first application, and its format matches the new component. In response to the detection of a container group running on a node, the first configuration information is obtained again, and the container group is configured based on this information. The container group is associated with the first application, and the node is associated with the new component. Therefore, when a new component is added, first configuration information related to and matching the format of the new component can be automatically generated for the first application. When the container group runs on a node managed by the new component, the generated first configuration information is automatically used to configure the container group. In other words, if a new component is added to the cluster, configuration information that the new component can recognize can be automatically generated for applications already deployed in the cluster. When the new component needs configuration, it is configured according to this information. Regardless of where the application's container group is subsequently scheduled within the cluster, the configuration can be executed correctly without manual intervention, and the configuration efficiency is high. Thus, even if the types of components in the cluster are different, the configuration information of applications under different components can be automatically synchronized, ensuring configuration consistency and accuracy even in complex cluster structures.

[0058] In some cases, the configuration processing method for this large model application may also include the following steps: Obtain the second configuration requirement information, which is used to indicate the preset configuration rules; Based on the second configuration requirement information, second configuration information is generated, and the format of the second configuration information matches the newly added component.

[0059] The configuration requirements information can be preprocessed to separate the application-related and application-independent parts. The application-independent parts of the configuration requirements information form preset configuration rules, which are shared among all components in the cluster and are unaffected by the application. Based on this, the configuration information of the first application may include not only the first configuration requirements information corresponding to the first application, but also the second configuration requirements information.

[0060] The second configuration requirement information can be converted into second configuration information that matches the format of the new component, so that the second configuration information can also be recognized by the new component. The method of generating configuration information based on configuration requirement information has been explained in detail in the section on generating first configuration information based on first configuration requirement information. The principle of generating second configuration information based on second configuration requirement information is the same, and will not be repeated here.

[0061] After generating the second configuration information, the first configuration information can be stored in the second storage location corresponding to the newly added component. Thus, when the application's container group is scheduled to run on a node managed by the newly added component, the new component can obtain the first and second configuration information associated with the application through the first and second storage locations, and perform configuration management based on the first and second configuration information.

[0062] Therefore, by dynamically and statically dividing configuration requirements according to actual conditions, first configuration information is generated based on dynamic configuration requirements, and second configuration information is generated based on static configuration requirements, thus forming the component's configuration information. In this way, common static configuration requirements within the cluster only need to be generated and stored once, effectively reducing configuration resource consumption. Furthermore, these common static configuration requirements only need to be modified once, eliminating the need to modify each application individually, improving the ease of cluster maintenance.

[0063] Optionally, if the newly added component is a container network interface, the first configuration information and the second configuration information may include network isolation information.

[0064] In some cases, the configuration processing method for this large model application may also include the following steps: In response to a deletion operation on a newly added component, delete the second configuration information.

[0065] In other words, if a new component is removed from the cluster, the second configuration information that already indicates the static configuration rules can be directly deleted to save storage resources within the cluster. Optionally, the first configuration information of the new component can also be deleted at the same time.

[0066] In some cases, the configuration processing method for this large model application may also include the following steps: In response to the detection of a second application, at least one third configuration information is generated, such that the format of the third configuration information matches an existing component, the second application is a newly added application, and the third configuration information is associated with the second application.

[0067] When a second application is added to the cluster, at least one third configuration information can be generated based on the components in the cluster. This ensures that the generated third configuration information covers different types of components in the cluster, avoiding situations where components cannot recognize the application. Optionally, the configuration requirements of the second application (i.e., the third configuration requirements) can be obtained first. Then, based on these requirements, third configuration information can be generated for each type of component, and stored in a storage location associated with each component, associating the third configuration information with the second application during storage. In this way, regardless of which node the container group of the second application is subsequently scheduled to, the components on that node can obtain the configuration information of the second application through the third storage location and perform configuration management.

[0068] The principle of generating third configuration information based on third configuration requirement information is the same as that of generating first configuration information based on first configuration requirement information, and will not be elaborated here.

[0069] In this way, when adding a new application to the cluster, the configuration of each type of component can be completed at once based on the existing components in the cluster, ensuring the integrity of the configuration information and avoiding failures caused by missing configuration information when the new application is subsequently scheduled to the nodes associated with other components.

[0070] In some cases, the configuration processing method for this large model application may also include the following steps: In response to the deletion operation of the third application, a fourth configuration information is selected, which includes configuration information associated with the third application; Delete the fourth configuration information.

[0071] When a deletion operation is performed on an application within the cluster, that application (the third application) will no longer exist in the cluster, and its associated configuration information is no longer necessary. Therefore, the configuration information associated with that application can also be deleted. Select the configuration information associated with the third application stored in the cluster, which is the fourth configuration information, and delete each piece of fourth configuration information from its corresponding storage location.

[0072] In this way, configuration information related to the application can be automatically deleted when the application is removed from the cluster, avoiding the continuous occupation of storage resources by configuration information. Furthermore, only the configuration information related to the deleted application is deleted, and the configuration information of other applications is not affected, ensuring the normal operation of other application container groups.

[0073] In some cases, the configuration processing method for this large model application may also include the following steps: In response to the detection of a new component, the node is set to a disabled state, and the node is the node managed by the new component; In response to the generation of the first configuration information, the node is set to an available state.

[0074] When a new component is detected in the cluster, the new node managed by that component can be disabled. In the disabled state, application containers in the cluster will not be scheduled to the new node, preventing errors due to lack of configuration information. Furthermore, after the initial configuration information has been generated, the node's configuration is complete and the container group can run normally, at which point the node can be made available. For example, the node can be made available after the initial configuration information has been stored in the first storage location.

[0075] In some scenarios, if a deletion operation is detected for a component, the configuration information corresponding to that component can be selected and deleted. In other words, when a component is deleted from the cluster, all configuration information related to that component can also be deleted synchronously. This configuration information can include application-related configuration information, as well as application-independent, cluster-shared configuration information.

[0076] Figure 3 This is a block diagram illustrating the configuration processing device for a large-scale model application, based on certain scenarios. For example... Figure 3 As shown, the device 30 may include: The first acquisition module 31 is used to acquire application information in response to the detection of a new component, the application information being used to indicate a first application; The first generation module 32 is used to generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component. The second acquisition module 33 is used to acquire the first configuration information in response to detecting that a container group is running on a node, wherein the container group is associated with the first application and the node is associated with the newly added component; Configuration module 34 is used to configure the container group based on the first configuration information.

[0077] Optionally, the first generation module 32 includes: The first acquisition submodule is used to acquire first configuration requirement information, which corresponds to the first application. The first generation submodule is used to generate first configuration information based on the first configuration requirement information, so that the format of the first configuration information matches the newly added component; Optionally, the first generation submodule includes: The second acquisition submodule is used to acquire component information, which corresponds to the newly added component. Select a submodule, which is used to select a configuration format based on the component information; The second generation submodule is used to generate the first configuration information based on the configuration format and the first configuration requirement information, so that the format of the first configuration information matches the configuration format.

[0078] Optionally, the device 30 further includes: The third acquisition module is used to acquire the second configuration requirement information, which is used to indicate the preset configuration rules; The second generation module is used to generate second configuration information based on the second configuration requirement information, wherein the format of the second configuration information matches the newly added component.

[0079] Optionally, the device 30 further includes: The first deletion module is used to delete the second configuration information in response to the deletion operation for the newly added component.

[0080] Optionally, the device 30 further includes: A third generation module is configured to generate at least one third configuration information in response to the detection of a second application, such that the format of the third configuration information matches an existing component, the second application being a newly added application, and the third configuration information being associated with the second application.

[0081] Optionally, the device 30 further includes: A selection module is used to select fourth configuration information in response to a deletion operation for a third application, the fourth configuration information including configuration information associated with the third application; The second deletion module is used to delete the fourth configuration information.

[0082] Optionally, the device 30 further includes: The first setting module is used to set a node to a disabled state in response to the detection of the newly added component, wherein the node is a node managed by the newly added component; The second setting module is used to set the node to an available state in response to the generation of the first configuration information.

[0083] Optionally, the newly added component is of a different type than the existing component.

[0084] Optionally, the newly added component is a container network interface, and the first configuration information includes network isolation information.

[0085] It should be understood that the execution logic of each functional module in the configuration processing device 30 for large model applications has been described in detail in the section on the configuration processing method for large model applications, and can be referred to the relevant description of the configuration processing method for large model applications.

[0086] The following is for reference. Figure 4 The diagram illustrates a structural schematic of an electronic device 600 suitable for implementing the above-described method. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Personal Computers), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs (Televisions), desktop computers, etc. Figure 4 The electronic device shown is merely an example and should not be construed as limiting its functionality or scope of use.

[0087] like Figure 4 As shown, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. The random access memory 603 also stores various programs and data required for the operation of electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. An input / output (I / O) interface 605 is also connected to bus 604.

[0088] Typically, the following devices can be connected to the input / output interface 605: input devices 606 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 608 including, for example, magnetic tape, hard disk, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 4 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0089] In particular, depending on certain circumstances, the processes described in the flowchart above can be implemented as computer software programs. For example, a computer program product is provided, comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. This computer program can be downloaded and installed from a network via communication device 609, or installed from storage device 608, or installed from read-only memory 602. When the computer program is executed by processing device 601, it performs the functions defined in the above-described methods.

[0090] It should be noted that the aforementioned computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In one case, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In another case, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (Radio Frequency), etc., or any suitable combination thereof.

[0091] In some scenarios, clients and servers can communicate using any currently known or future network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include Local Area Networks (LANs), Wide Area Networks (WANs), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad-hoc peer-to-peer networks), as well as any currently known or future network.

[0092] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0093] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: In response to the detection of a new component in the cluster, application information is obtained, which is used to indicate at least one first application deployed in the cluster; In response to the detection of a new component, application information is obtained, which is used to indicate a first application; Generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component; In response to detecting that a container group is running on a node, the first configuration information is obtained, wherein the container group is associated with the first application and the node is associated with the newly added component; The container group is configured based on the first configuration information.

[0094] Computer program code for performing the above operations can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages, as well as conventional procedural programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0095] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. Each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that, in some alternative cases, the functions indicated in the blocks may occur in a different order than those indicated in the figures. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0096] The modules mentioned above can be implemented in software or hardware. In some cases, the name of a module does not necessarily limit the module itself; for example, the first acquisition module can also be described as a "module for acquiring application information".

[0097] The functions described above can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Parts (ASSPs), Systems on Chips (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0098] In this context, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0099] The above description is merely illustrative and explains the technical principles employed. Those skilled in the art should understand that the scope of this document is not limited to the specific combinations of the above-described technical features, but should also cover any combination of the above-described technical features or their equivalents without departing from the above concept.

[0100] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain environments. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this paper. Certain features described in the context of a single example can also be implemented in combination in a single example. Conversely, various features described in the context of a single example can also be implemented individually or in any suitable sub-combination in multiple examples.

[0101] Although this document has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims. Regarding the aforementioned apparatus, the specific manner in which the various modules perform their operations has already been described in detail in the section concerning the method, and will not be elaborated upon here.

Claims

1. A configuration processing method for large-scale model applications, comprising: In response to the detection of a new component, application information is obtained, which is used to indicate a first application; Generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component; In response to detecting that a container group is running on a node, the first configuration information is obtained, wherein the container group is associated with the first application and the node is associated with the newly added component; The container group is configured based on the first configuration information.

2. The method according to claim 1, wherein generating the first configuration information includes: Obtain the first configuration requirement information, which corresponds to the first application; Based on the first configuration requirement information, first configuration information is generated so that the format of the first configuration information matches the newly added component.

3. The method according to claim 2, wherein generating the first configuration information based on the first configuration requirement information includes: Obtain component information, which corresponds to the newly added component; Based on the component information, select the configuration format; Based on the configuration format and the first configuration requirement information, the first configuration information is generated so that the format of the first configuration information matches the configuration format.

4. The method according to claim 1, further comprising: Obtain second configuration requirement information, which is used to indicate preset configuration rules; Based on the second configuration requirement information, second configuration information is generated, and the format of the second configuration information matches the newly added component.

5. The method according to claim 4, further comprising: In response to the deletion operation for the newly added component, the second configuration information is deleted.

6. The method according to claim 1, further comprising: In response to the detection of a second application, at least one third configuration information is generated, such that the format of the third configuration information matches an existing component, the second application being a newly added application, and the third configuration information being associated with the second application.

7. The method according to claim 1, further comprising: In response to a deletion operation targeting a third application, fourth configuration information is selected, the fourth configuration information including configuration information associated with the third application; Delete the fourth configuration information.

8. The method according to claim 1, further comprising: In response to the detection of the newly added component, the node is set to a disabled state, and the node is the node managed by the newly added component; In response to the generation of the first configuration information, the node is set to an available state.

9. The method according to any one of claims 1-8, wherein the newly added component is of a different type than the existing component.

10. The method according to any one of claims 1-8, wherein the newly added component is a container network interface, and the first configuration information includes network isolation information.

11. A configuration processing apparatus for a large model application, comprising: The first acquisition module is used to acquire application information in response to the detection of a new component, wherein the application information is used to indicate a first application; A first generation module is used to generate first configuration information, which is associated with the first application, and the format of the first configuration information matches the newly added component. The second acquisition module is used to acquire the first configuration information in response to detecting that a container group is running on a node, wherein the container group is associated with the first application and the node is associated with the newly added component; The configuration module is used to configure the container group based on the first configuration information.

12. A computer-readable medium having a computer program stored thereon, wherein, When executed by a processing device, the computer program implements the method described in any one of claims 1-10.

13. An electronic device, comprising: A storage device on which computer programs are stored; A processing apparatus for executing the computer program in the storage device to implement the method according to any one of claims 1-10.

14. A computer program product comprising a computer program, wherein, When executed by a processor, the computer program implements the method described in any one of claims 1-10.

Images