Pod scheduling management and control method and related equipment thereof

Abstract

The invention provides a pod scheduling management and control method and related equipment thereof, applied to a container cloud platform, the method comprises: receiving a plurality of task sets sent by a plurality of tenant terminals, the task sets comprising associated task entities and resource usage amounts; according to the resource usage amount of a target task set and the queue residual resources of the corresponding queue, whether pod is created for a task entity of the target task set or not is judged, the target task set is determined from the queue of the corresponding target task set according to the priority, and the task entity of the target task set is in a suspended state; if it is judged that the pod is created for the task entities of the target task set, the pod is created for the task entities of the target task set; if it is judged that the pod is not created for the task entities of the target task set, the pod is not created for the task entities of the target task set.

Description

Technical Field

[0001] The present application relates to the field of containerization technology, and in particular to a pod scheduling and control method and related equipment. Background Art

[0002] Building distributed clusters based on cloud-native solutions has become the current mainstream solution, resulting in tasks of different tenants sharing the resources of the same container cloud platform.

[0003] Specifically, after the container cloud platform receives the task sent by the tenant, the controller of the container cloud platform creates a corresponding container group (pod) for the task, and then the scheduler of the container cloud platform (Kubernetes) uses the node to process the pod to complete the execution of the task.

[0004] However, in the case of large-scale tasks, the above processing method has insufficient node resources, resulting in low efficiency of task processing on the container cloud platform and even the crash of the container cloud platform. Summary of the Invention

[0005] The present application provides a pod scheduling and control method and related equipment for reducing the low efficiency of container cloud platform task processing and even the probability of container cloud platform crash in large-scale task scenarios.

[0006] In a first aspect, the present application provides a pod scheduling and control method, which is applied to a container cloud platform. The method includes:

[0007] Receiving multiple task sets sent by multiple tenant terminals, wherein the task sets include associated task entities and resource usage;

[0008] Determine whether to create a pod for a task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, wherein the target task set is determined from the queue corresponding to the target task set based on priority, and the task entity of the target task set is in a suspended state;

[0009] If it is determined that a pod is to be created for the task entity of the target task set, a pod is created for the task entity of the target task set;

[0010] If it is determined not to create a pod for the task entity of the target task set, then no pod is created for the task entity of the target task set.

[0011] In some implementations, determining whether to create a pod for a task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue includes:

[0012] In response to the remaining resources of the queue being greater than or equal to the resource usage of the task entity of the target task set, generating a decision to create a pod for the task entity of the target task set;

[0013] In response to the remaining resources of the queue being less than the resource usage of the task entity of the target task set, a determination is generated not to create a pod for the task entity of the target task set.

[0014] In some implementations, after receiving the multiple task sets sent by the multiple tenant terminals, the method further includes:

[0015] Creating a plurality of queues, wherein the queues include some of the plurality of task sets;

[0016] For each task set in the queue, activating a task entity of the task set to a suspended state;

[0017] The target task set is determined from a plurality of task sets in the queue according to the priority.

[0018] In some implementations, after creating the plurality of queues, the method further comprises:

[0019] For each task set in the queue, obtaining the task type of the task set;

[0020] Then, for each task set in the queue, activating the task entity of the task set to a suspended state includes:

[0021] For each task set in the queue, activating a task entity of the task set to a suspended state of a corresponding task type;

[0022] Then, creating a pod for the task entity of the target task set includes:

[0023] A pod of the task type is created for the task entity of the target task set.

[0024] In some embodiments, the task set further includes a task type identifier, and the container cloud platform is preset with a relationship table including task type identifiers and task types. Then, for each task set in the queue, obtaining the task type of the task set includes:

[0025] For each task set of the queue, the task type is determined according to the corresponding task type identifier and the relationship table.

[0026] In some embodiments, after not creating a pod for the task entity of the target task set, the method further includes:

[0027] Re-determining the target task set after excluding the target task set from the queue of the target task set according to the priority;

[0028] The re-determined target task set is executed based on the resource usage of the target task set and the queue remaining resources of the corresponding queue to determine whether to create a pod for the task entity of the target task set and its subsequent steps.

[0029] In some embodiments, after receiving multiple task sets sent by multiple tenant terminals and before determining whether to create a pod for a task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, the method includes:

[0030] Acquire snapshot data of a cache of a queue of the target task set, where the snapshot data includes remaining resources of the queue.

[0031] A second aspect of the present application provides a pod scheduling and control method, which is applied to a tenant terminal, including:

[0032] A plurality of task sets including task entities and resource usage are sent to a container cloud platform, so that a queue controller of the container cloud platform determines whether to create pods for the task entities of the task sets.

[0033] The third aspect of the present application provides a pod scheduling device, comprising

[0034] A receiving module, configured to receive multiple task sets sent by multiple tenant terminals, wherein the task sets include associated task entities and resource usage;

[0035] A judgment module is used to judge whether to create a pod for the task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, wherein the target task set is determined from the queue corresponding to the target task set according to the priority, and the task entity of the target task set is in a suspended state; if it is determined to create a pod for the task entity of the target task set, then a pod is created for the task entity of the target task set; if it is determined not to create a pod for the task entity of the target task set, then no pod is created for the task entity of the target task set.

[0036] A fourth aspect of the present application provides a pod scheduling device, including:

[0037] The sending module is used to send multiple task sets including task entities and resource usage to the container cloud platform, so that the queue controller of the container cloud platform determines whether to create pods for the task entities of the task sets.

[0038] In a fifth aspect, the present application provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the pod scheduling and control method in any embodiment of the first aspect.

[0039] In a sixth aspect, the present application provides a computer-readable storage medium having program instructions stored therein, wherein the program instructions are executed by a processor to implement the pod scheduling and control method in any embodiment of the first aspect.

[0040] Compared with the prior art, the technical solution of the present application determines whether to create a pod for the task entity of the target task set. If it is determined that a pod is to be created for the task entity of the target task set, a pod is created for the task entity of the target task set; if it is determined that a pod is not to be created for the task entity of the target task set, a pod is not created for the task entity of the target task set. This controls whether to create a pod for the task entity of the task set, thereby enabling orderly generation of pods. Compared with the prior art, the amount of pod generation is reduced, thereby indirectly reducing the probability of insufficient node resources during subsequent node pod processing, resulting in low efficiency in task processing of the container cloud platform or even a crash of the container cloud platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0042] Figure 1 This is a schematic diagram of a pod scheduling and control process in an embodiment of the present application;

[0043] Figure 2 This is another schematic diagram of the pod scheduling and control process in an embodiment of the present application;

[0044] Figure 3 1 is a flow chart of determining whether to create a pod for a task entity of a target task set according to an embodiment of the present application;

[0045] Figure 4 This is a schematic diagram of the interaction process between the tenant terminal and the container cloud platform in an embodiment of the present application;

[0046] Figure 5 This is a structural diagram of a pod scheduling and control device according to an embodiment of the present application;

[0047] Figure 6 This is a structural diagram of a pod scheduling and control device according to an embodiment of the present application;

[0048] Figure 7 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following describes the embodiments of the present application in detail with reference to the accompanying drawings.

[0050] In the following description, for the purpose of explanation rather than limitation, specific details such as specific system structures, interfaces, and technologies are provided to facilitate a thorough understanding of the present application.

[0051] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0052] The terms "first," "second," and "third" in this application are used only for descriptive purposes and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of such features. In the description of this application, "multiple" means at least two, for example, two, three, etc., unless otherwise specifically defined. All directional indications in the embodiments of this application (such as up, down, left, right, front, back...) are only used to explain the relative positional relationship, movement, etc. between the components under a specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indications also change accordingly. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products, or devices.

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

[0054] Please refer to Figure 1 , Figure 1The following figure shows a schematic diagram of a pod scheduling and control process, which is applied to a container cloud platform and includes:

[0055] 101: Receive multiple task sets sent by multiple tenant terminals, where the task sets include associated task entities and resource usage;

[0056] The container cloud platform receives multiple task sets sent by multiple tenant terminals, each task set including associated task entities and resource usage.

[0057] The task entity refers to the task itself sent by the tenant terminal to the container cloud platform and processed by the container cloud platform. The resource usage refers to the resource consumption required by the container cloud platform to process the task entity, which is generated by the tenant terminal.

[0058] It is understandable that when the container cloud platform processes a task entity, it needs the tenant terminal to provide it with the task entity and resource usage at the same time to complete the processing of the task entity.

[0059] 102: Determine whether to create a pod for a task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, wherein the target task set is determined from the queue corresponding to the target task set based on priority, and the task entity of the target task set is in a suspended state;

[0060] Based on the multiple task sets received, the container cloud platform determines the target task set from the queue including the target task set according to priority, and then determines whether to create a pod for the task entity of the target task set. The queue of the target task set includes multiple task sets, and the task entity of the target task set is in a suspended state, so as to reduce the delay or interruption of the container cloud platform and improve the resource utilization of the container cloud platform.

[0061] A pod is a logical container for a group of container instances and is the smallest deployable and schedulable computing unit that can be created and managed in Kubernetes. Kubernetes, also known as K8S, is an open-source Linux platform for automating the deployment, scaling, and management of containerized applications.

[0062] In some implementations, the container cloud platform determines whether to create a pod for the task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue.

[0063] 103: If it is determined that a pod is to be created for the task entity of the target task set, then a pod is created for the task entity of the target task set;

[0064] If the container cloud platform determines that a pod should be created for the task entity of the target task set, the pod is created for the task entity of the target task set.

[0065] 104: If it is determined that a pod is not to be created for the task entity of the target task set, then a pod is not created for the task entity of the target task set.

[0066] If the container cloud platform determines that a pod should not be created for the task entity of the target task set, the pod will not be created for the task entity of the target task set.

[0067] This application controls whether to create pods for task entities in a task set, thereby enabling orderly generation of pods. Compared with the above-mentioned control method in the prior art, the amount of pod generation is reduced, thereby indirectly reducing the probability of insufficient node resources during subsequent node processing of pods, resulting in low efficiency in task processing on the container cloud platform or even a crash of the container cloud platform.

[0068] See also Figure 2 , Figure 2 The container cloud platform forms a queue for multiple task sets received from multiple tenant terminals and prioritizes the multiple task sets in the queue to obtain a target task set, thereby optimizing the processing flow and improving processing efficiency, including:

[0069] 201: Create multiple queues, wherein the queues include some of the multiple task sets;

[0070] After receiving multiple task sets from multiple tenant terminals, the container cloud platform creates multiple queues, each of which includes part of the multiple task sets.

[0071] In some embodiments, the container cloud platform creates multiple queues based on the respective task attribute classifications of multiple task sets, that is, multiple task sets with the same or similar task attributes in the multiple task sets are determined to be in the same queue to improve processing efficiency.

[0072] 202: For each task set in the queue, activate the task entity of the task set to a suspended state;

[0073] The container cloud platform activates each task set of each queue and puts the task entity of the task set into a suspended state to reduce the delay or interruption of the container cloud platform and improve the resource utilization of the container cloud platform.

[0074] 203: Determine the target task set from the multiple task sets in the queue according to the priority;

[0075] The container cloud platform has preset priorities for determining the order in which multiple task sets in a queue are processed. Therefore, for each queue, the container cloud platform uses the priority to determine the high-priority target task set from the queue to give priority to task sets with high urgency and importance.

[0076] See also Figure 3 , Figure 3 This section shows how to determine whether to create a pod for the task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the queue corresponding to the target task set. That is, the container cloud platform compares the remaining queue resources with the resource usage of the task entity of the target task set. The remaining queue resources refer to the remaining available resources of the queue corresponding to the target task set, specifically including:

[0077] 301: In response to the remaining resources of the queue being greater than or equal to the resource usage of the task entity of the target task set, generating a decision to create a pod for the task entity of the target task set;

[0078] If the remaining queue resources of the queue responding to the target task set are greater than or equal to the resource usage of the task entity of the target task set, the container cloud platform generates a decision to create a pod for the task entity of the target task set.

[0079] 302 : In response to the remaining resources of the queue being less than the resource usage of the task entity of the target task set, generating a decision not to create a pod for the task entity of the target task set.

[0080] If the remaining queue resources of the queue responding to the target task set are less than the resource usage of the task entity of the target task set, the container cloud platform generates a decision not to create a pod for the task entity of the target task set.

[0081] See also Figure 4 , Figure 4 The diagram shows the interaction process between the tenant terminal and the container cloud platform, including:

[0082] 401: The tenant terminal sends multiple task sets including task entities and resource usage to the container cloud platform;

[0083] The tenant terminal sends multiple task sets including task entities and resource usage to the container cloud platform, so that the queue controller of the container cloud platform determines whether to create pods for the task entities of the task sets.

[0084] Among them, the task set includes not only the task entity and resource usage, but also the task type identifier and other necessary information, such as information used to establish a communication link between the tenant terminal and the container cloud platform. It can be understood that the task entity, resource usage and task type identifier correspond to each other.

[0085] Among them, the tenant terminal can be a tablet personal computer (PC), desktop PC, laptop PC, netbook computer, workstation, server, personal digital assistant (PDA), wearable device or vehicle-mounted device, and is not limited here.

[0086] 402: Receive multiple task sets sent by multiple tenant terminals, where the task sets include associated task entities and resource usage;

[0087] Step 402 is similar to the aforementioned step 101 and will not be described in detail here.

[0088] 403: Create multiple queues;

[0089] Step 403 is similar to the aforementioned step 201 and will not be described in detail here.

[0090] 404: Get the task type of the task set;

[0091] For each task set in the queue, the container cloud platform determines the corresponding task type of each task set based on the task type identifier sent by the tenant terminal and the relationship table between task type identifiers and task types preset by the container cloud platform.

[0092] 405: The task entity of the activated task set is in the pending state of the corresponding task type;

[0093] For each task set in the queue, the container cloud platform activates the task entity of the task set to the suspended state of the corresponding task type.

[0094] Specifically, task types include Job, Deployment, Statefulset, etc., which are not limited here. Furthermore, the suspended state of the task entity of the task set can be a suspended state of the Job, Deployment, Statefulset, etc., which are not limited here.

[0095] 406: Determine the target task set from the queue based on priority;

[0096] This step is similar to the aforementioned step 203 and will not be described in detail here.

[0097] It is understandable that, since the task entity of each task set in the queue in step 405 is in the suspended state of its corresponding task type, the task entity of the determined target task set is also in the suspended state of the corresponding task type.

[0098] 407: Get the queue's cached snapshot data, which includes the remaining resources in the queue.

[0099] The container cloud platform obtains the cached snapshot data of the queue to obtain the remaining resources of the queue.

[0100] In some implementations, the snapshot data includes the used resources and available resources of the queue (ie, the remaining resources of the queue). To further improve the processing speed, the snapshot data is cached according to a preset period.

[0101] 408: Determine whether to create a pod for the task entity of the target task set;

[0102] The container cloud platform determines whether to create a pod for the target task set's task entity based on the remaining queue resources of the target task set's queue and the resource usage of the target task set's task entity, for example, through steps 301 and 302 above, which will not be described in detail here.

[0103] 409: If it is determined that a pod is to be created for the task entity of the target task set, a pod is created for the task entity of the target task set;

[0104] If the container cloud platform determines to create a pod for the task entity of the target task set, it will create a pod of the corresponding task type for the task entity of the target task set, and then allocate the task entity of the target task set to a node to execute the task entity of the target task set based on the corresponding resource usage, and reclaim the corresponding resource usage after completion.

[0105] In some embodiments, the present application can also monitor whether the task entity of the target task set is completed. If completed, the corresponding resource usage is recovered. If not completed, a waiting operation is performed on the task entity of the target task set until the task entity of the target task set completes execution and the corresponding resource usage is recovered.

[0106] 410: If it is determined that a pod is not to be created for the task entity of the target task set, then a pod is not created for the task entity of the target task set.

[0107] If the container cloud platform determines that a pod will not be created for the task entity of the target task set, a pod will not be created for the task entity of the target task set, and it will be re-added to other queues, waiting for the next preset cycle to be processed, and then jumping to the aforementioned step 407, re-excluding the target task set from the queue of the target task set according to the priority and re-determining the target task set, and judging whether to create a pod for the task entity of the target task set and its subsequent steps based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, until the pod creation of the task entity of the task set in the queue is completed.

[0108] It can be understood that the present application controls whether to create a pod for the task entity of the task set, and then performs the corresponding branch operation, so that the pod is generated in an orderly manner. Compared with the existing technology, the control method of the present application reduces the amount of pod generation, thereby indirectly reducing the probability of insufficient node resources in the subsequent node processing of the pod, resulting in low efficiency of container cloud platform task processing or even crash of the container cloud platform.

[0109] See also Figure 5 , Figure 5A schematic diagram of the structure of a pod scheduling and control device is shown, including:

[0110] The receiving module 501 is configured to receive multiple task sets sent by multiple tenant terminals, wherein the task sets include associated task entities and resource usage;

[0111] The judgment module 502 is used to judge whether to create a pod for the task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, wherein the target task set is determined from the queue corresponding to the target task set according to the priority, and the task entity of the target task set is in a suspended state; if it is determined to create a pod for the task entity of the target task set, then a pod is created for the task entity of the target task set; if it is determined not to create a pod for the task entity of the target task set, then no pod is created for the task entity of the target task set.

[0112] See also Figure 6 , Figure 6 A schematic diagram of another pod scheduling and control device structure is shown, including:

[0113] The sending module 601 is used to send multiple task sets including task entities and resource usage to the container cloud platform, so that the queue controller of the container cloud platform determines whether to create pods for the task entities of the task sets.

[0114] This application also includes an electronic device, see Figure 7 The system comprises: a memory 701 and a processor 702; wherein the memory is used to store programs; and the processor is used to execute the programs in the memory, including executing any one of the methods in the aforementioned embodiments;

[0115] Optionally, the electronic device further includes a bus system for connecting the memory and the processor so that the memory and the processor communicate with each other.

[0116] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0117] In some embodiments, the memory may be an internal storage unit of the cloud device, for example, a hard disk or memory of the cloud device. In other embodiments, the memory may also be an external storage device of the cloud device, for example, a plug-in hard disk equipped on the cloud device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card, etc. Furthermore, the memory may also include both an internal storage unit of the cloud device and an external storage device. The memory is used to store an operating system, an application, a boot loader (BootLoader), data, and other programs, such as the program code of a computer program. The memory may also be used to temporarily store data that has been output or is to be output.

[0118] The present application also includes a computer-readable storage medium having program instructions stored therein, and the program instructions are executed by a processor to implement any one of the methods in the aforementioned embodiments.

[0119] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above-mentioned method embodiments.

[0120] The computer program includes computer program code, which may be in source code form, object code form, executable file, or some intermediate form. Computer-readable media may include at least any entity or device capable of carrying the computer program code to a camera / terminal device, recording media, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media. Examples include USB flash drives, removable hard drives, magnetic disks, or optical disks.

[0121] The above is only an implementation method of the present application and does not limit the scope of patent protection of the present application. Any equivalent structure or equivalent process transformation made using the contents of the description and drawings of this application, or directly or indirectly applied in other related technical fields, are also included in the scope of patent protection of the present application.

Claims

1. A pod scheduling and control method, characterized in that: Applied to a container cloud platform, the method includes: Receiving multiple task sets sent by multiple tenant terminals, wherein the task sets include associated task entities and resource usage; Determine whether to create a pod for a task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, wherein the target task set is determined from the queue corresponding to the target task set based on priority, and the task entity of the target task set is in a suspended state; If it is determined that a pod is to be created for the task entity of the target task set, a pod is created for the task entity of the target task set; If it is determined not to create a pod for the task entity of the target task set, then no pod is created for the task entity of the target task set.

2. The method according to claim 1, characterized in that The determining whether to create a pod for a task entity of the target task set according to the resource usage of the target task set and the remaining queue resources of the corresponding queue includes: In response to the remaining resources of the queue being greater than or equal to the resource usage of the task entity of the target task set, generating a decision to create a pod for the task entity of the target task set; In response to the remaining resources of the queue being less than the resource usage of the task entity of the target task set, a determination is generated not to create a pod for the task entity of the target task set.

3. The method according to claim 1 or 2, characterized in that: After receiving the multiple task sets sent by the multiple tenant terminals, the method further includes: Creating a plurality of queues, wherein the queues include some of the plurality of task sets; For each task set in the queue, activating a task entity of the task set to a suspended state; The target task set is determined from a plurality of task sets in the queue according to the priority.

4. The method according to claim 3, characterized in that After creating the plurality of queues, the method further includes: For each task set in the queue, obtaining the task type of the task set; Then, for each task set in the queue, activating the task entity of the task set to a suspended state includes: For each task set in the queue, activating a task entity of the task set to a suspended state of a corresponding task type; Then, creating a pod for the task entity of the target task set includes: Create a pod of the corresponding task type for the task entity of the target task set.

5. The method according to claim 4, characterized in that: The task set also includes a task type identifier. The container cloud platform presets a relationship table including task type identifiers and task types. Then, for each task set of the queue, obtaining the task type of the task set includes: For each task set of the queue, the task type is determined according to the corresponding task type identifier and the relationship table.

6. The method according to any one of claims 1 to 2, characterized in that: After not creating a pod for the task entity of the target task set, the method further includes: Re-determining the target task set after excluding the target task set from the queue of the target task set according to the priority; The re-determined target task set is executed based on the resource usage of the target task set and the queue remaining resources of the corresponding queue to determine whether to create a pod for the task entity of the target task set and its subsequent steps.

7. The method according to claim 1, characterized in that: After receiving multiple task sets sent by multiple tenant terminals, and before determining whether to create a pod for the task entity of the target task set based on the resource usage of the target task set and the remaining queue resources of the corresponding queue, the method further includes: Acquire snapshot data of a cache of a queue of the target task set, where the snapshot data includes remaining resources of the queue.

8. A pod scheduling and control method, characterized in that: Applicable to tenant terminals, including: A plurality of task sets including task entities and resource usage are sent to a container cloud platform, so that a queue controller of the container cloud platform determines whether to create pods for the task entities of the task sets.

9. An electronic device comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to run the computer program to execute the pod scheduling and control method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that Program instructions are stored therein, and the program instructions are executed by a processor to implement the pod scheduling and control method according to any one of claims 1 to 8.

Images