Object storage-based large model container rapid startup system, method and medium

Abstract

The present application relates to a system, method, and medium for quickly starting a large model container based on object storage. The system includes a user plane component, a driver component, a persistent volume controller, a first control plane component, and a second control plane component. The user plane component is used to monitor data volume resource creation events and create PVC requests. The driver component is used to query the size of required data files in the object storage database; the persistent volume controller is used to initiate a PV resource creation request; the first control plane component is used to receive the PV resource creation request and initiate a data volume creation request to the driver component based on the file list information; the driver component is used to load the required data files based on the file list and aggregate them to form a file tree structure to obtain a read-only data volume; the second control plane component is used to mount the read-only data volume to the node of the large model container based on the PVC request, thereby realizing the rapid startup of the large model container.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a system, method, and medium for quickly starting a large model container based on object storage. Background Art

[0002] When deploying and running large models in a Kubernetes environment, in addition to the demand for computing resources such as CPUs (central processing units) and GPUs (graphics processing units), the primary task is to load the model data. Currently, large models with high accuracy and the ability to handle complex tasks often require data in the gigabyte range, often exceeding 100GB after a complete load. This places high demands on the storage space and network bandwidth of the machine nodes within the Kubernetes cluster. If model data needs to be downloaded again for each model run, a series of problems will arise, including slow startup of large model containers, significant Kubernetes cluster network bandwidth utilization, affecting the timely response of network requests from other containers, and the storage space of some cluster nodes becoming full, making it impossible to accept container deployment and scheduling requests.

[0003] Currently, no effective solution has been proposed to the problem of slow startup of large model containers in related technologies. Summary of the Invention

[0004] Based on this, it is necessary to provide a large model container quick startup system, method and medium based on object storage to address the above technical problems.

[0005] In a first aspect, an embodiment of the present application provides a large-model container rapid startup system based on object storage, which is applied to a Kubernetes cluster. The system includes: a user plane component, a driver component, a persistent volume controller, a first control plane component, and a second control plane component.

[0006] The user plane component is configured to initiate a query request to the driver component based on the file list information of the required data files when a data volume resource creation event is monitored;

[0007] The driver component is configured to query an object storage database based on the query request to obtain the size of the data file, wherein the object storage database stores large model training data;

[0008] The user plane component is configured to create a PVC request according to the file list information and size of the data file;

[0009] The persistent volume controller is configured to initiate a PV resource creation request when monitoring the PVC creation request;

[0010] The first control plane component is configured to receive the PV resource creation request, extract the file list information, and initiate a data volume creation request to the driver component based on the file list information;

[0011] The driver component is used to load the required data files based on the file list and aggregate them to form a file tree structure to obtain a read-only data volume;

[0012] The first control plane component is configured to create a PV resource based on the PV resource creation request, and bind the PV resource to the PVC request according to the PVC reference information in the request;

[0013] The second control plane component is configured to mount the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model data based on the read-only data volume.

[0014] In one embodiment, the user plane component is further configured to, upon monitoring a data volume resource creation event, determine whether the data volume has been created, and if so, skip creation of the data volume.

[0015] In one embodiment, the user plane component is further configured to initiate a query request to the driver component based on a file list of required data files to determine whether the data files are missing; if so, terminating the creation of the data volume.

[0016] In one embodiment, the user plane component is further configured to delete the PVC request when a data volume resource deletion event is monitored;

[0017] The persistent volume controller is further configured to initiate a PV resource deletion request when a deletion request of the PVC is detected;

[0018] The first control plane component is configured to extract the file list information based on the PV resource deletion request, unbind the binding relationship between the PVC request and the PV resource, and initiate a data volume deletion request to the driver component based on the file list information;

[0019] The driver component is configured to search for a specified data volume for deletion based on the file list information;

[0020] The first control plane component is further configured to delete the PV resource after the data volume is deleted.

[0021] In one of the embodiments, the user-side component is further used to determine whether the data volume exists when a data volume resource deletion event is monitored, and if not, terminate the deletion of the data volume; if so, determine whether the data volume is used by the large model container, and if so, terminate the deletion of the data volume.

[0022] In one embodiment, the second control plane component is further configured to extract the file list information in response to the data volume unmounting request of the large model container, and initiate a data volume unmounting request to the driver component based on the file list information;

[0023] The driver component is further configured to search for a designated data volume for uninstallation based on the file list information.

[0024] In one of the embodiments, a custom CSI plug-in is constructed based on the user plane component, the driver component, the first control plane component, and the second control plane component, and the custom CSI plug-in is integrated into a Kubernetes cluster.

[0025] In a second aspect, an embodiment of the present application further provides a method for quickly starting a large model container based on object storage, which is applied to the system described in the first aspect above, and the method includes:

[0026] When the user plane component monitors the data volume resource creation event, it initiates a query request to the driver component according to the file list information of the required data file;

[0027] The driver component queries the object storage database based on the query request to obtain the size of the data file;

[0028] The user plane component creates a PVC request according to the file list information and size of the data file;

[0029] The persistent volume controller initiates a PV resource creation request when monitoring the PVC creation request;

[0030] The first control plane component receives the PV resource creation request, extracts the file list information, and initiates a data volume creation request to the driver component based on the file list information;

[0031] The driver component loads the required data files based on the file list and aggregates them into a file tree structure to obtain a read-only data volume;

[0032] The first control plane component creates a PV resource based on the PV resource creation request, and binds the PV resource to the PVC request according to the PVC reference information in the request;

[0033] The second control plane component mounts the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model data based on the read-only data volume.

[0034] In a third aspect, an embodiment of the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the method as described in the second aspect above.

[0035] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the storage medium stores a computer program, wherein when the computer program is executed by a processor, the method described in the second aspect above is implemented.

[0036] The above-mentioned large model container rapid startup system, method and medium based on object storage, the system includes: a user plane component, a driver component, a persistent volume controller, a first control plane component, and a second control plane component, the user plane component is used to initiate a query request to the driver component based on the file list information of the required data file when monitoring the data volume resource creation event; the driver component is used to query in the object storage database based on the query request to obtain the size of the data file, wherein the object storage database stores large model training data; the user plane component is used to create a PVC request based on the file list information and size of the data file; the persistent volume controller is used to initiate a PV resource creation request when monitoring the creation of the PVC request; the first A control plane component is configured to receive the PV resource creation request, extract the file list information, and initiate a data volume creation request to the driver component based on the file list information; the driver component is configured to load the required data files based on the file list, aggregate them into a file tree structure, and obtain a read-only data volume; the first control plane component is configured to create a PV resource based on the PV resource creation request, and bind the PV resource to the PVC request according to the PVC reference information in the request; the second control plane component is configured to mount the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model data based on the read-only data volume, thereby solving the problem of slow startup of the large model container and achieving fast startup of the large model container.

[0037] The details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more readily apparent. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0039] Figure 1 is a schematic diagram of the structure of a large model container quick startup system based on object storage in one embodiment;

[0040] Figure 2 This is a schematic diagram of a large model data volume creation process in a large model container fast startup system based on object storage in one embodiment;

[0041] Figure 3 This is a schematic diagram of a large model data volume mounting process of a large model container fast startup system based on object storage in one embodiment;

[0042] Figure 4 This is a schematic diagram of a large model data volume unloading process in a large model container fast startup system based on object storage in one embodiment;

[0043] Figure 5 This is a schematic diagram of a large model data volume deletion process in a large model container fast startup system based on object storage in one embodiment;

[0044] Figure 6 It is a schematic diagram of the structure of a computer device in an embodiment. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in this application, all other embodiments obtained by those of ordinary skill in the art without making any creative work are within the scope of protection of this application. Based on the embodiments provided in this application, all other embodiments obtained by those of ordinary skill in the art without making any creative work are within the scope of protection of this application.

[0046] Obviously, the drawings described below are merely examples or embodiments of the present application. Those skilled in the art can, without inventive effort, apply the present application to other similar scenarios based on these drawings. Furthermore, it is also understood that, although the effort involved in such a development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, changes in design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as an insufficiency of the content disclosed in this application.

[0047] References to "embodiments" in this application mean that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described in this application may be combined with other embodiments unless there is a conflict.

[0048] Unless otherwise defined, technical or scientific terms used herein shall have the ordinary meaning as understood by persons of ordinary skill in the art to which this application belongs. The terms "a," "an," "an," "the," and similar expressions used herein do not denote quantitative limitations and may refer to either the singular or the plural. The terms "comprise," "include," "have," and any variations thereof, used herein, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or modules (units) is not limited to the listed steps or units but may also include steps or units not listed, or may include other steps or units inherent to the process, method, product, or apparatus. The terms "connected," "connected," "coupled," and similar expressions used herein are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. As used herein, "plurality" means two or more. "And / or" describes an association between associated objects, indicating that three possible relationships exist. For example, "A and / or B" may mean: A exists alone; A and B exist simultaneously; or B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific order for the objects.

[0049] The following are explanations of terms that appear in some embodiments of this application:

[0050] PV (Persistent Volume): A resource in a Kubernetes cluster that provides volumes for containers to mount.

[0051] PVC (Persistent Volume Claims): A resource configuration that dynamically creates and reclaims PVs based on user-required storage resources and features in a Kubernetes cluster.

[0052] CSI (Container Storage Interface): A standardized plug-in interface used in Kubernetes clusters. It mainly solves the compatibility issues between storage plug-in developers and the Kubernetes platform, allowing various types of storage solutions to be integrated into Kubernetes.

[0053] Kubelet node controller: It is an important component in the Kubernetes cluster. It runs on each node and is responsible for interacting with the node's operating system and performing container lifecycle management, including creation, starting, stopping, and deletion.

[0054] Storage Class: An object in Kubernetes that defines storage volume provisioning policies. Kubernetes cluster administrators can configure and name different storage classes to facilitate the creation of storage volumes using different storage classes according to different requirements when deploying containers.

[0055] The embodiment of the present application provides a large model container fast startup system based on object storage, which is applied to Kubernetes clusters, such as Figure 1 The structure diagram of the large model container rapid startup system based on object storage is shown, and the system includes a user plane component, a driver component, a persistent volume controller, a first control plane component, and a second control plane component.

[0056] The user plane component is used to initiate a query request to the drive component according to the file list information of the required data file when monitoring the data volume resource creation event; the drive component is used to query the object storage database based on the query request to obtain the size of the data file.

[0057] Among them, the object storage database stores large model training data; the object storage database is deployed inside the Kubernetes cluster, and the large model pre-training data is manually stored in the object storage database by the operation and maintenance personnel, and interacts with the object storage database through the driver component.

[0058] The user plane component is used to create a PVC request based on the file list information and size of the data file; the persistent volume controller is used to initiate a PV resource creation request when monitoring the creation of the PVC request; the first control plane component is used to receive the PV resource creation request, extract the file list information, and initiate a data volume creation request to the driver component based on the file list information; the driver component is used to load the required data files based on the file list, and aggregate them to form a file tree structure to obtain a read-only data volume; the first control plane component is used to create a PV resource based on the PV resource creation request, and bind the PV resource and the PVC request based on the PVC reference information in the request; the second control plane component is used to mount the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model data based on the read-only data volume.

[0059] The user-side component's primary responsibility is to monitor events related to large model pre-trained data volume resources. These events are categorized into two main types: volume creation and volume deletion. Volume creation occurs when users manually configure large model pre-trained data volume resources to specify the pre-trained data files (including directory structure) required for their applications. This event is triggered when these resources are created in the Kubernetes cluster. Volume deletion occurs when users manually locate and delete a large model pre-trained data volume resource with the corresponding name in the Kubernetes cluster. This component manages the lifecycle of the PVC and storage class for large model data volumes.

[0060] The driver component's primary responsibilities are operating the object storage database, interacting with it, providing a gRPC interface for remote calls to other components, and running in a Kubernetes cluster as a DaemonSet. Object storage operations involve searching for files and aggregating them into a file tree structure (implementing a custom read-only file system), ultimately creating a read-only volume for external use. The driver component provides remote call interfaces for first-control-plane components, including CreateVolume (volume creation), DeleteVolume (volume deletion), ControllerPublishVolume (controller mounts volume to a node), ControllerUnpublishVolume (controller unmounts volume from a node), NodeStageVolume (node ​​prepares volume), and NodeUnstageVolume (node ​​unprepare volume). It also provides remote call interfaces for second-control-plane components, including NodePublishVolume (node ​​publishes volume to a container path) and NodeUnpublishVolume (node ​​unpublishes volume). It also provides remote call interfaces for user-plane components, including interfaces for retrieving file information, such as querying whether a file exists, obtaining file size, and volume reference information.

[0061] The first control plane component's main responsibility is to connect to the Kubernetes cluster's Persistent Volume Controller (PVController) request call, implement the business logic of creating and deleting underlying storage volumes, creating and deleting PVs, and binding and unbinding PVs to PVCs. It runs in the Kubernetes cluster as a DaemonSet.

[0062] The second control plane component's main responsibility is to connect to the Kubelet node controller of the Kubernetes cluster node, complete the volume mounting of the large model container application before it is assigned to a specific node for running, and complete the volume unmounting when it stops running.

[0063] The user plane component, the driver component, the first control plane component, and the second control plane component implement a custom CSI plug-in according to the Kubernetes CSI (Container Storage Interface) specification to provide the capability of large model data volumes. The custom CSI plug-in is integrated into the Kubernetes cluster.

[0064] The Persistent Volume Controller (PVC) is a control plane component that monitors PVC request objects within the Kubernetes cluster, automatically matches appropriate PV resources to satisfy the storage resources requested by the PVC, and manages the PV resource declaration lifecycle.

[0065] The large model container quick startup system based on object storage provided by the embodiment of the present application is combined with the object storage database, so that after the large model pre-training data is manually stored in the object storage by the operation and maintenance personnel, it can be quickly searched, combined and formed into a read-only volume from the object storage database according to the large model pre-training data requirements, and finally mounted to the container of the large model application, avoiding the process of pulling the full amount of model data before starting the large model container, thereby significantly speeding up the startup speed of the large model container.

[0066] In one embodiment, the user plane component is further configured to, upon monitoring a data volume resource creation event, determine whether the data volume has been created, and if so, skip creation of the data volume.

[0067] In one embodiment, the user plane component is further configured to initiate a query request to the driver component based on a file list of required data files to determine whether the data files are missing; if so, terminating the creation of the data volume.

[0068] In one of the embodiments, the user plane component is further used to delete the PVC request when a data volume resource deletion event is detected; the persistent volume controller is further used to initiate a PV resource deletion request when a PVC request deletion is detected; the first control plane component is used to extract the file list information based on the PV resource deletion request; and unbind the binding relationship between the PVC request and the PV resource, and initiate a data volume deletion request to the driver component based on the file list information; the driver component is used to search for a specified data volume for deletion based on the file list information; the first control plane component is further used to delete the PV resource after the data volume is deleted.

[0069] In one of the embodiments, the user-side component is further used to determine whether the data volume exists when a data volume resource deletion event is monitored, and if not, terminate the deletion of the data volume; if so, determine whether the data volume is used by the large model container, and if so, terminate the deletion of the data volume.

[0070] In one of the embodiments, the second control plane component is further used to respond to the data volume unloading request of the large model container, extract the file list information, and initiate a data volume unloading request to the driver component based on the file list information; the driver component is further used to search for a specified data volume for unloading based on the file list information.

[0071] In one of the embodiments, a custom CSI plug-in is constructed based on the user plane component, the driver component, the first control plane component, and the second control plane component, and the custom CSI plug-in is integrated into a Kubernetes cluster.

[0072] By using customized CSI plug-ins and object storage, the system can flexibly adapt to different storage requirements and is easy to expand, enhancing the flexibility and scalability of the system.

[0073] The present application also provides a method for quickly starting a large model container based on object storage, which is applied to Figure 1 The large model container rapid startup system based on object storage shown in the figure includes the following steps:

[0074] Step 201: When the user plane component monitors a data volume resource creation event, it initiates a query request to the driver component based on the file list information of the required data file.

[0075] Step 202: The driver component queries the object storage database based on the query request to obtain the size of the data file;

[0076] Step 203: The user plane component creates a PVC request based on the file list information and size of the data file.

[0077] Step 204: Upon receiving the PVC creation request, the persistent volume controller initiates a PV resource creation request.

[0078] Step 205: The first control plane component receives the PV resource creation request, extracts the file list information, and initiates a data volume creation request to the driver component based on the file list information.

[0079] Step 206: The driver component loads the required data files based on the file list and aggregates them into a file tree structure to obtain a read-only data volume.

[0080] Step 207: The first control plane component creates a PV resource based on the PV resource creation request, and binds the PV resource to the PVC request according to the PVC reference information in the request.

[0081] In step 208 , the second control plane component mounts the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model data based on the read-only data volume.

[0082] In a specific embodiment, a method for creating a large model data volume is provided, which is applied to Figure 1The large model container quick start system based on object storage is shown in FIG. Figure 2 As shown, the following steps are included:

[0083] Step 301: The user plane component completes the establishment of a long link through the API Server (Application Programming Interface Server) interface of the Kubernetes cluster and continuously monitors events of the large model data volume resource;

[0084] Step 302: The user plane component receives the event of creating a large model data volume and checks whether the same volume has already been created. If so, the creation process is skipped and the existing data volume is directly reused; if not, the full data volume creation process is entered;

[0085] Step 303: The user-side component obtains all pre-trained model data files required for the large model data volume resource and initiates a file existence query request to the driver component. If some files are missing, the volume creation process will be terminated.

[0086] Step 304: After the user plane component completes the file retrieval, it again sends a request to the driver component to obtain the space size of all files;

[0087] Step 305: The user plane component creates a specific Storage Class based on the file information list, and then creates a PVC based on the file space size information and the Storage Class.

[0088] Step 306: The persistent volume controller of the Kubernetes cluster monitors the PVC creation event and then initiates a PV creation request.

[0089] Step 307: The first control plane component receives the request to create a PV, extracts the file list information parameters, and then entrusts the driver component to create a volume.

[0090] In step 308, the driver component loads all required files, merges them into a file tree structure, and finally provides a read-only volume, thus completing the delegation process.

[0091] Step 309: The first control plane component starts creating a PV and completes the binding between the PV and the PVC based on the PVC reference information in the request.

[0092] In step 310, when the large model application needs to be containerized and deployed in the Kubernetes cluster, it is only necessary to configure the PVC created previously. Then, during the actual container creation phase, the Kubelet node controller calls the second control plane component to mount the volume, which can quickly complete the fast mounting of the large model pre-training data and shorten the container startup time.

[0093] In a specific embodiment, the application Figure 1 The large model container quick start system based on object storage shown in the figure has a large model data volume mounting process as shown in the figure. Figure 3 As shown, the following steps are included:

[0094] Step 401: reference the PVC of the data volume in the large model container and deploy the container;

[0095] Step 402: The Kubelet node controller initiates a volume mount request.

[0096] Step 403: The second control plane component receives the request parameters and remotely calls the driver component.

[0097] Step 404: The driver component finds the specified volume and returns the volume;

[0098] Step 405: The second control plane component mounts the volume to the path specified by the node;

[0099] In step 406, the Kubelet node controller updates the container's mount point and starts the container.

[0100] At this point, the large model container starts quickly to process the business.

[0101] In a specific embodiment, the application Figure 1 The large model container quick start system based on object storage shown in the figure, the large model data volume unloading process is as follows Figure 4 As shown, the following steps are included:

[0102] Step 501: The large model application container stops running;

[0103] Step 502: The Kubelet node controller detects that the container is stopped, cleans up the volume mount point of the container on the node, and initiates a volume unmount request.

[0104] Step 503: The second control plane component receives the request parameters and remotely calls the driver component.

[0105] Step 504: The driver component finds the specified volume and completes the volume unmounting.

[0106] In step 505, the Kubelet node controller completely terminates the container, and the life cycle of the large model application container ends.

[0107] In a specific embodiment, the application Figure 1 The large model container quick start system based on object storage is shown in FIG. Figure 5 As shown, the following steps are included:

[0108] Step 601: When the large model application container is terminated, the Kubelet node controller on the corresponding Kubernetes cluster node monitors the event and calls the second control plane component to remove the large model data volume on the container mount point.

[0109] Step 602: When there is no reference to the large model data volume in the Kubernetes cluster, the user can manually delete it.

[0110] Step 603: When the user-side component monitors the deletion event of the large model data volume, it will first check whether the volume exists. If not, the deletion process will be terminated directly. Then, it will check whether the volume is still in use through the driver component interface. If so, the deletion process will be terminated directly.

[0111] Step 604: The user plane component completes the check and submits a request to delete the PVC.

[0112] Step 605: The persistent volume controller of the Kubernetes cluster monitors the PVC deletion event and then initiates a PV deletion request.

[0113] Step 606: The first control plane component receives the PV deletion request, extracts the request parameters, first unbinds the binding between the PVC and the PV, and then delegates the driver component to complete the volume deletion.

[0114] Step 607: The first control plane component formally enters the deletion submission of the PV;

[0115] In step 608, after the PV is deleted, the user plane component formally submits the deletion of the Storage Class and the final cleanup and recycling process of the PVC.

[0116] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, memory, communication interface, display screen and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner. The wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a large model container fast startup system based on object storage is implemented.

[0117] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0118] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned large model container fast startup system embodiments based on object storage are implemented.

[0119] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0120] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0121] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A large model container rapid startup system based on object storage, characterized in that: Applied to Kubernetes cluster, the system includes: user plane component, driver component, persistent volume controller, first control plane component, second control plane component, The user plane component is configured to initiate a query request to the driver component based on the file list information of the required data files when a data volume resource creation event is monitored; The driver component is configured to query an object storage database based on the query request to obtain the size of the data file, wherein the object storage database stores large model training data; The user plane component is configured to create a PVC request according to the file list information and size of the data file; The persistent volume controller is configured to initiate a PV resource creation request when monitoring the PVC creation request; The first control plane component is configured to receive the PV resource creation request, extract the file list information, and initiate a data volume creation request to the driver component based on the file list information; The driver component is used to load the required data files based on the file list and aggregate them to form a file tree structure to obtain a read-only data volume; The first control plane component is configured to create a PV resource based on the PV resource creation request, and bind the PV resource to the PVC request according to the PVC reference information in the request; The second control plane component is used to mount the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model training data based on the read-only data volume.

2. The system according to claim 1, wherein: The user plane component is further configured to, upon monitoring a data volume resource creation event, determine whether the data volume has been created, and if so, skip creation of the data volume.

3. The system according to claim 1, wherein: The user plane component is further configured to initiate a query request to the driver component according to a file list of required data files to determine whether the data files are missing; if so, terminate the creation of the data volume.

4. The system according to claim 1, wherein: The user plane component is further configured to delete the PVC request when a data volume resource deletion event is monitored; The persistent volume controller is further configured to initiate a PV resource deletion request when a deletion request of the PVC is detected; The first control plane component is configured to extract the file list information based on the PV resource deletion request, unbind the binding relationship between the PVC request and the PV resource, and initiate a data volume deletion request to the driver component based on the file list information; The driver component is configured to search for a specified data volume for deletion based on the file list information; The first control plane component is further configured to delete the PV resource after the data volume is deleted.

5. The system according to claim 4, characterized in that The user plane component is further configured to, upon monitoring a data volume resource deletion event, determine whether the data volume exists, and if not, terminate the response to the data volume resource deletion event; If so, the driver component determines whether the data volume is used by the large model container. If so, the user plane component terminates the response to the data volume resource deletion event.

6. The system according to claim 1, wherein: The second control plane component is further configured to extract the file list information in response to the data volume unmounting request of the large model container, and initiate a data volume unmounting request to the driver component based on the file list information; The driver component is further configured to search for a designated data volume for uninstallation based on the file list information.

7. A method for quickly starting a large model container based on object storage, characterized in that: Applied to the system according to any one of claims 1 to 6, the method comprises: When the user plane component monitors the data volume resource creation event, it initiates a query request to the driver component according to the file list information of the required data file; The driver component queries the object storage database based on the query request to obtain the size of the data file; The user plane component creates a PVC request according to the file list information and size of the data file; The persistent volume controller initiates a PV resource creation request when monitoring the PVC creation request; The first control plane component receives the PV resource creation request, extracts the file list information, and initiates a data volume creation request to the driver component based on the file list information; The driver component loads the required data files based on the file list and aggregates them into a file tree structure to obtain a read-only data volume; The first control plane component creates a PV resource based on the PV resource creation request, and binds the PV resource to the PVC request according to the PVC reference information in the request; The second control plane component mounts the read-only data volume to the node of the large model container based on the PVC request, so that the large model container loads the large model training data based on the read-only data volume.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the method according to claim 7 is implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to claim 7 is implemented.

Images