CN114721743B - Task execution method and device and electronic equipment - Google Patents
Task execution method and device and electronic equipment Download PDFInfo
- Publication number
- CN114721743B CN114721743B CN202210397497.XA CN202210397497A CN114721743B CN 114721743 B CN114721743 B CN 114721743B CN 202210397497 A CN202210397497 A CN 202210397497A CN 114721743 B CN114721743 B CN 114721743B
- Authority
- CN
- China
- Prior art keywords
- task
- target agent
- description file
- module
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 172
- 230000008569 process Effects 0.000 claims abstract description 109
- 230000007246 mechanism Effects 0.000 claims abstract description 75
- 238000012217 deletion Methods 0.000 claims description 19
- 230000037430 deletion Effects 0.000 claims description 19
- 230000008520 organization Effects 0.000 claims description 15
- 239000003795 chemical substances by application Substances 0.000 description 141
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
In the task execution method, the target Agent obtains the description file of the first task to be executed, then starts an application process corresponding to the application program according to the application program corresponding to the first task carried in the description file, and finally executes the first task in the application process, so that the task (Pod) can be executed by the Agent (Agent), and when the task is executed, the target Agent only creates a common process without any permission, and the target Agent can successfully start the first task no matter whether the target Agent is operated on a physical machine or in a container environment, so that K8s can adapt to deployment environments of different mechanisms and differences in infrastructure of the mechanisms are shielded.
Description
[ field of technology ]
The embodiment of the specification relates to the technical field of internet, in particular to a task execution method, a task execution device and electronic equipment.
[ background Art ]
Currently, shared intelligence has involved a variety of services including secure multi-party computing (MPC), multi-party security analysis (secure collaborative query language, SCQL), federal learning (federated learning, FL), etc., and a common feature of these services is that tasks need to be performed at the institution side, how to rapidly distribute different tasks to multiple institutions, how to effectively control the tasks at the institution side, which is a difficult problem in engineering implementation. Fortunately, kubernetes (K8 s) is widely popular in the field of cloud protogenesis in recent years, and is an ideal basic platform, the K8s can automatically deploy, expand and manage containerized application programs, and if the application programs are used in institutions, the K8s can well meet various business requirements.
However, for sharing intelligent services, tasks are performed at multiple organizations, where the software and hardware environments of the organizations are various, some are physical machines, and some are virtualized environments, for example: dock et al, while K8s has high requirements on the environment and can only be deployed on physical machines, if a mechanism cannot provide a physical machine, K8s cannot be deployed.
Thus, there is a need to provide a solution so that K8s can adapt to the deployment environment of different institutions, shielding differences in the infrastructure of the institutions.
[ invention ]
The embodiment of the specification provides a task execution method, a task execution device and electronic equipment, so that K8s can adapt to deployment environments of different institutions, and differences in infrastructure of the institutions are shielded.
In a first aspect, an embodiment of the present disclosure provides a task execution method, including: acquiring a description file of a first task to be executed; the description file is sent to a target agent by a central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; the execution mechanism label is consistent with the mechanism label provided when the target agent is registered, and the content of the stain tolerance statement is consistent with the content of stain information provided when the target agent is registered; starting an application process corresponding to the application program according to the application program corresponding to the first task; and executing the first task in the application process.
In the task execution method, the target Agent acquires the description file of the first task to be executed, then starts an application process corresponding to the application program according to the application program corresponding to the first task carried in the description file, and finally executes the first task in the application process, so that the task (Pod) can be executed by the Agent (Agent), and when the task is executed, the target Agent only creates a common process without any permission, and the target Agent can successfully start the first task no matter whether the target Agent operates on a physical machine or in a container environment, so that K8s can adapt to deployment environments of different mechanisms and differences on infrastructure of the mechanisms are shielded.
In one possible implementation manner, the starting the application process corresponding to the application program according to the application program corresponding to the first task includes: assigning a process group to the first task; starting an application process corresponding to the application program; and adding the application process into the allocated process group.
In one possible implementation manner, after the first task is executed in the application process, the method further includes: acquiring a task deleting instruction, wherein the task deleting instruction carries a second task to be deleted; a task termination signal is sent to a process group corresponding to the second task, so that an application process corresponding to the second task in the process group is terminated; notifying the central node that the second task has been deleted.
In one possible implementation manner, before the obtaining the description file of the first task to be executed, the method further includes: sending a node registration request to a central node; the node registration request comprises an organization label of a target agent and stain information of the target agent.
In one possible implementation manner, the method further includes: acquiring a node deleting request; notifying the central node that the target agent cannot be scheduled; deleting the task executed on the target agent; notifying the central node to mark the state of the target agent as unavailable so that the central node deletes the target agent.
In a second aspect, embodiments of the present disclosure provide a task execution method, including: acquiring a description file of a first task to be executed; determining an executing mechanism of the first task according to the executing mechanism tag carried in the description file; selecting a target agent suitable for executing the first task from the executing mechanism according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file; and sending the description file to the target agent, wherein the description file carries the execution mechanism label, the application program corresponding to the first task and the stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task, and executes the first task in the application process.
In the task execution method, after the description file of the first task to be executed is acquired, an execution mechanism of the first task is determined according to the execution mechanism tag carried in the description file, and then a target agent suitable for executing the first task is selected from the execution mechanism according to the content of the stain tolerance statement carried in the description file. And finally, the description file is sent to a target Agent, the description file carries the executing mechanism label, an application program corresponding to the first task and a stain tolerance statement, so that the target Agent can start the first task according to the application program corresponding to the first task, start the application process corresponding to the basic information according to the basic information of the first task carried in the description file, execute the first task in the application process, and therefore the task (Pod) can be executed by an Agent (Agent), and when the task is executed, the target Agent only creates a common process without any permission, and can successfully start the first task no matter whether the target Agent operates on a physical machine or in a container environment, so that K8s can adapt to deployment environments of different mechanisms and differences on infrastructure of the mechanisms.
In a third aspect, embodiments of the present specification provide a task execution device, provided in a target agent, the device including: the acquisition module is used for acquiring a description file of a first task to be executed; the description file is sent to a target agent by a central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; the execution mechanism label is consistent with the mechanism label provided when the target agent is registered, and the content of the stain tolerance statement is consistent with the content of stain information provided when the target agent is registered; the starting module is used for starting an application process corresponding to the application program according to the application program corresponding to the first task; and the execution module is used for executing the first task in the application process.
In one possible implementation manner, the starting module is specifically configured to allocate a process group for the first task, start an application process corresponding to the application program, and add the application process to the allocated process group.
In one possible implementation manner, the apparatus further includes: a sending module and a notification module; the acquisition module is further configured to acquire a task deletion instruction after the execution module executes the first task, where the task deletion instruction carries a second task to be deleted; the sending module is used for sending a task termination signal to the process group corresponding to the second task so as to terminate the application process corresponding to the second task in the process group; and the notification module is used for notifying the center node that the second task is deleted.
In one possible implementation manner, the apparatus further includes: a transmitting module; the sending module is used for sending a node registration request to the central node before the obtaining module obtains the description file of the first task to be executed; the node registration request comprises an organization label of a target agent and stain information of the target agent.
In one possible implementation manner, the apparatus further includes: a notification module and a deletion module; the acquisition module is also used for acquiring a node deletion request; the notification module is used for notifying the central node that the target agent cannot be scheduled; the deleting module is used for deleting the task executed on the target agent; the notification module is further configured to notify the central node to mark the state of the target agent as unavailable, so that the central node deletes the target agent.
In a fourth aspect, embodiments of the present disclosure provide a task execution device, where the task execution device is disposed on a central node, the device including: the acquisition module is used for acquiring a description file of a first task to be executed; the determining module is used for determining the executing mechanism of the first task according to the executing mechanism label carried in the description file; the selection module is used for selecting a target agent suitable for executing the first task from the execution mechanism according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file; the sending module is used for sending the description file to the target agent, wherein the description file carries the execution mechanism label, the application program corresponding to the first task and the stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task, and executes the first task in the application process.
In a fifth aspect, embodiments of the present disclosure provide an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method provided in the first aspect.
In a sixth aspect, the present description embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the method provided in the first aspect.
In a seventh aspect, embodiments of the present disclosure provide an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method provided in the second aspect.
In an eighth aspect, the present description embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the method provided in the second aspect.
It should be understood that, the third, fifth and sixth aspects of the embodiments of the present disclosure are consistent with the technical solutions of the first aspect of the embodiments of the present disclosure, and the beneficial effects obtained by each aspect and the corresponding possible implementation manner are similar, and are not repeated herein;
the fourth, seventh and eighth aspects of the embodiments of the present disclosure are consistent with the technical solutions of the second aspect of the embodiments of the present disclosure, and the beneficial effects obtained by each aspect and the corresponding possible implementation manner are similar and are not repeated.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present description, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a block diagram of a K8s cluster according to the prior art;
FIG. 2 is a schematic diagram of a K8s cluster according to one embodiment of the present disclosure;
FIG. 3 is a flow chart of a task execution method provided by one embodiment of the present disclosure;
FIG. 4 is a flow chart of a task execution method according to another embodiment of the present disclosure;
FIG. 5 is a flow chart of a task execution method provided in yet another embodiment of the present disclosure;
FIG. 6 is a flow chart of a task execution method provided in yet another embodiment of the present disclosure;
FIG. 7 is a flow chart of a task execution method provided in yet another embodiment of the present disclosure;
FIG. 8 is a schematic diagram of a task execution device according to an embodiment of the present disclosure;
FIG. 9 is a schematic diagram of a task execution device according to another embodiment of the present disclosure;
FIG. 10 is a schematic diagram of a task execution device according to another embodiment of the present disclosure;
fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
[ detailed description ] of the invention
For a better understanding of the technical solutions of the present specification, embodiments of the present specification are described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are only some, but not all, of the embodiments of the present description. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present disclosure.
The terminology used in the embodiments of the description presented herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description presented herein. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
For various services involved in sharing intelligence, including MPC, SCQL or FL, the related art realizes task distribution through K8s cluster, and task execution at the control mechanism side. K8s is short for Kubernetes, K8s is an open-source container arrangement service and is also an automatic container operation and maintenance management platform, a plurality of hosts are combined into a cluster to run a containerized application program, and the K8s can automatically create or delete a container, so that a plurality of manual operations involved in deployment, capacity expansion and/or offline of the application program are eliminated.
Fig. 1 is a block diagram of a K8s cluster according to the related art. As shown in fig. 1, the K8s cluster is composed of a host (Master) and a node (Kubelet), the Master is disposed at a central end of the K8s cluster and used for controlling, managing and/or scheduling tasks (Pod), and the Kubelet is disposed at an actuator end and used for receiving instructions of the Master and executing related actions. Pod is the smallest computational unit in a K8s cluster, consisting of one or more containers within which runs services involved in shared intelligence, such as: MPC, FL, SCQL, etc. Currently, sharing intelligence has involved multiple services, and in order to distinguish between different services, a specific service type may be abstracted into an Application (APP), for example: MPC is an APP, SCQL is an APP, and FL is an APP.
MPC refers to a plurality of parties holding private data, collectively executing a calculation logic, and obtaining a calculation result.
SCQL refers to a plurality of participants holding private data, commonly execute a data query logic, and obtain a query result. The difference between the SCQL and the MPC is that the computation logic of the MPC is predefined, only a limited number of computation logics can be executed, the data query logic of the SCQL can be changed arbitrarily, the data query logic is represented by a specific query language (query language), written by a user, and after the user submits a specific query (query) request, the SCQL engine executes the query request according to the intention of the user and displays the query result. As with MPC, both the query results and the query intermediate process of SCQL are secure, and the original data of any party is not revealed.
However, the above-described scheme provided by the related art has the following disadvantages:
1) The K8s is originally designed for a single mechanism, and the K8s is designed without considering that kubelets belong to different mechanisms, namely, the Kubelet of the Alice mechanism is completely equivalent to the Kubelet of the Bob mechanism in view of the Master, and no difference exists, so that in order to accurately issue Pod to the Alice mechanism or the Bob mechanism, an additional mechanism is needed to ensure that Pod is issued.
2) Kubelet can only be deployed on physical machines, and Pod cannot be started if Kubelet is deployed in a container environment. This is because a Kubelet creates one or more containers for each Pod, and if the Kubelet itself runs in a container, the container cannot be re-nested inside, and all Pod creation instructions fail to execute. N containers can be deployed on one physical machine, the running speed is high, the resource isolation can be realized, and the environments among the containers deployed on the same physical machine are completely isolated.
3) Sharing intelligent related APPs involves cross-mechanism calls, and kubelets do not support cross-mechanism Pod calls.
The embodiment of the specification is based on K8s cluster creation, modifications are made on the basis of the K8s clusters, and FIG. 2 is a schematic diagram of the K8s clusters provided by one embodiment of the specification.
As shown in fig. 2, the present embodiment of the present specification completely multiplexes the K8s Master, but discards the Kubelet, using an entirely new Agent (Agent) instead. The Agent implements the same interface as the Kubelet and can therefore register itself with the Master. The benefits of this embodiment of the present description are:
1) The capability of the K8s Master can be multiplexed;
2) The Agent is the same as the Kubelet interface, so that the Master does not need to distinguish whether the node is the Kubelet or the Agent, and the embodiment of the specification does not need to modify the Master;
3) The Agent can be deployed in a physical machine or a container environment, while the Kubelet can only be deployed on the physical machine, so that the mechanism deployment environment limit is solved.
In the embodiment of the specification, two types of communication interfaces between the Master and the Kubelet are needed to be realized by an Agent, and the two types of interfaces are a node registration and deletion interface and a Pod creation and deletion interface respectively.
The following describes the process of the Agent implementing the two interfaces respectively.
1. Node creation
When the Agent starts, the Agent needs to register itself with the Master, and only after registration, the Master will issue the Pod instruction. The information required to be attached when the Agent registers may include:
1) The node basic information may include all information attached at the time of Kubelet registration, including node name and/or node machine hardware configuration information, and the like.
2) And (5) an organization name label. The Agent additionally labels itself with a label associated with the institution, such as: the Agent of Alice organization registers with the "kubernetes/io/naspace: alice" tag.
3) Stain information for distinguishing agents from kubelets, which additionally places themselves with a stain "nueva. Alipoy. Com/Agent: noSchedule" for preventing irrelevant Pod from being scheduled onto Agent nodes. So-called taint is a mechanism provided by K8s Master, and if a node is tainted, pod will not be scheduled onto that node unless Pod states that i can tolerate some taint.
Why is an Agent stained? Because the Agent is a "masquerading" Kubelet, not supporting all types of Pod operations, only supporting pulling up MPC, SCQL and/or FL-related APPs, the Agent can actively stain itself in order to avoid the Master from dispatching other unrelated pods onto the Agent.
2. Pod creation
Pod creation is initially triggered by the user, who needs to submit one or more task (Pod) description files to the Master when triggering MPC, SCQL, and/or FL tasks, for example, the Pod description files may be as follows:
1.apiVersion:v1
2.kind:Pod
3.metadata:
4.name:task
5.namespace:alice
6.spec:
7.containers:
8.-name:main
9.image:mpc_trainer:v1
10.nodeSelector:
11.kubernetes.io/namespace:alice
12.tolerations:
13.-key:nueva.alipay.com/agent
14.operator:Exists
15.effect:NoSchedule
the main content of the Pod description file may include:
1) Task (Pod) basic information, lines 1-9;
2) Node selection (node selector) statement, lines 10-11, tells the Master that Pod must be scheduled to nodes with "kubernetes. Io/Namespace: alice" labels that are consistent with the labels provided at Agent registration. In this way, the Master can ensure that Pod will only be dispatched to Alice's machine and not Bob.
3) Stain tolerance statement, lines 12-15. Since the Agent blemishes itself, the user must indicate that blemishes can be tolerated when submitting the Pod, otherwise the Pod cannot be scheduled to the Agent. The content of the stain tolerance declaration is consistent with the content of the Agent declaration.
In particular, when a user submits a Pod, the Pod description file is issued to the Agent, and after the Agent receives the Pod description file, the Agent pulls up the related APP according to the image field in the Pod description file. Agents differ most from Kubelets in how to pull up an APP by creating one or more containers for the APP and then starting the APP within the container. The Agent allocates a process group to each Pod, directly pulls up the APP process, and adds the APP process to the allocated process group. The benefits of doing so are: the container is started to be a heavyweight operation, a plurality of rights are needed, the related rights can be provided only by a physical machine, and the interior of the container is not authorized, so if the Kubelet runs in the container, the Kubelet rights are insufficient, the Pod container cannot be created any more, and the APP cannot be started. The Agent only creates a common process, no permission is needed, and the Agent can successfully start the Pod no matter the Agent runs on a physical machine or in a container environment.
3. Pod deletion
After the Agent acquires the Pod delete instruction, the following procedure may be performed:
step 1, the agent sends a task Stop (SIGKILL) signal to the whole process group, and the process is terminated after the process receives the SIGKILL signal. It should be noted that killing the process through the SIGKILL signal is a mechanism provided by the Linux operating system.
And step 2, notifying a Master that the Pod is deleted.
4. Node deletion
The node deleting instruction is triggered by the organization administrator, when the organization administrator wants to drop a machine or delete a container where an Agent is located, a node deleting request can be initiated to the Agent, and the node deleting process of the Agent is as follows:
and 1, informing a Master that the node is not schedulable by the agent. At this point, the Master will not schedule a new Pod onto the node.
And 2, for the Pod in operation of the local machine, executing a process of deleting the Pod in sequence, deleting all the pods on the local machine, and informing a Master Pod of deleting.
And 3, the agent informs a Master to mark the node as unavailable.
And 4, deleting information related to all nodes from the K8s Master, namely logging off the nodes.
The embodiment of the specification carries out certain transformation and upgrading on the architecture of the K8s cluster, and can achieve the following technical effects:
1) The node execution framework Agent replaces a Kubelet container creation mode by using a creation process mode, and is applicable to all mechanism environments;
2) The interfaces of the Agent and the Kubelet are consistent, the central node does not need to be modified, the K8s central node can be directly multiplexed, and the implementation cost of the scheme is low;
3) Through flexible collocation of the K8s label and the stain mechanism, the oriented distribution of Pod is realized.
The task execution method provided in the embodiment of the present specification is described below based on fig. 2 and the above description.
Fig. 3 is a flowchart of a task execution method according to an embodiment of the present disclosure, where the task execution method may be executed by an Agent (Agent) in the K8s cluster shown in fig. 2. As shown in fig. 3, the task execution method may include:
step 302, a target agent acquires a description file of a first task to be executed; the description file is sent to the target agent by the central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; wherein the actuator tag is consistent with an actuator tag provided at the time of registration of the target agent, and the contents of the stain tolerance statement are consistent with the contents of stain information provided at the time of registration of the target agent.
For example, the description file of the first task may be as follows:
1.apiVersion:v1
2.kind:Pod
3.metadata:
4.name:task
5.namespace:alice
6.spec:
7.containers:
8.-name:main
9.image:mpc_trainer:v1
10.nodeSelector:
11.kubernetes.io/namespace:alice
12.tolerations:
13.-key:nueva.alipay.com/agent
14.operator:Exists
15.effect:NoSchedule
in the above example, the 5 th row "nano space" field shows the actuator label "alice" that is the first task; an application program "MPC" corresponding to the first task is shown in the line 9 "image" field; lines 12-15 are the smudge tolerance statements.
In step 304, the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task.
Specifically, according to the application program corresponding to the first task, starting the application process corresponding to the application program may be: distributing a process group for the first task, and starting an application process corresponding to the application program; and adding the application process into the allocated process group.
That is, in this embodiment, the target agent allocates a process group to the first task, then directly starts the application process corresponding to the application program, and adds the application process to the allocated process group, so that the target agent only creates a normal process, and no permission is required, and the target agent can successfully start the first task whether the target agent is running on the physical machine or in the container environment.
Step 306, executing the first task in the application process.
In the task execution method, the target Agent acquires the description file of the first task to be executed, then starts an application process corresponding to the application program according to the application program corresponding to the first task carried in the description file, and finally executes the first task in the application process, so that the task (Pod) can be executed by the Agent (Agent), and when the task is executed, the target Agent only creates a common process without any permission, and the target Agent can successfully start the first task no matter whether the target Agent operates on a physical machine or in a container environment, so that K8s can adapt to deployment environments of different mechanisms and differences on infrastructure of the mechanisms are shielded.
Fig. 4 is a flowchart of a task execution method according to another embodiment of the present disclosure, as shown in fig. 4, in the embodiment shown in fig. 3 of the present disclosure, after step 306, the method may further include:
step 402, acquiring a task deletion instruction, where the task deletion instruction carries a second task to be deleted.
And step 404, sending a task termination signal to the process group corresponding to the second task so as to terminate the application process corresponding to the second task in the process group.
Step 406, notifying the central node that the second task has been deleted.
Fig. 5 is a flowchart of a task execution method according to still another embodiment of the present disclosure, as shown in fig. 5, in the embodiment shown in fig. 3 of the present disclosure, before step 302, the method may further include:
step 502, a node registration request is sent to a central node; wherein the node registration request includes an organization tag of the target agent and stain information of the target agent.
For example, the target agent of Alice organization may carry a "kubernetes. Io/naspace: alice" tag in the node registration request when registering; the stain information carried by the target agent in the node registration request may be "nueva.
Fig. 6 is a flowchart of a task execution method according to still another embodiment of the present disclosure, as shown in fig. 6, where the embodiment shown in fig. 3 of the present disclosure may further include:
step 602, a node deletion request is obtained.
Specifically, the node delete request may be triggered by an organization administrator, who may initiate the node delete request to the target agent when the organization administrator wants to drop a machine or delete a container in which the target agent is located.
Step 604, notifying the central node that the target agent cannot be scheduled.
Step 606, delete task executing on the target agent.
Specifically, when deleting the task executed on the target agent, the method provided in the embodiment shown in fig. 4 of the present specification may be adopted, which is not described herein.
Step 608, notifying the central node to mark the state of the target agent as unavailable, so that the central node deletes the target agent.
In this embodiment, steps 602 to 608 may be performed after the target agent sends the node registration request to the central node, and the order of performing steps 602 to 608 is not limited in this embodiment.
Fig. 7 is a flowchart of a task execution method according to another embodiment of the present disclosure, where the task execution method provided by the present embodiment may be executed by a central node in the K8s cluster shown in fig. 2. As shown in fig. 7, the task execution method may include:
Step 702, a description file of a first task to be executed is obtained.
Step 704, determining the execution mechanism of the first task according to the execution mechanism label carried in the description file.
Step 706, selecting a target agent suitable for executing the first task from the executing mechanism according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file.
Step 708, the description file is sent to the target agent, where the description file carries the execution mechanism tag, the application program corresponding to the first task, and the stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task, and executes the first task in the application process.
In the task execution method, after the description file of the first task to be executed is acquired, an execution mechanism of the first task is determined according to the execution mechanism tag carried in the description file, and then a target agent suitable for executing the first task is selected from the execution mechanism according to the content of the stain tolerance statement carried in the description file. And finally, the description file is sent to a target Agent, the description file carries the executing mechanism label, an application program corresponding to the first task and a stain tolerance statement, so that the target Agent starts an application process corresponding to the application program according to the application program corresponding to the first task and executes the first task in the application process, the task (Pod) can be executed by an Agent (Agent), and when the task is executed, the target Agent only creates a common process without any permission, and the target Agent can successfully start the first task no matter whether the target Agent operates on a physical machine or in a container environment, so that K8s can adapt to deployment environments of different mechanisms and differences in infrastructure of the mechanisms are shielded.
It should be noted that, the task description file mentioned in the embodiment of the present specification is just one way to transfer information, and in a practical scenario, the file herein may be replaced by a string sent on a network, or a JS object numbered musical notation (JavaScript Object Notation, JSON) text, and the "file" is just one form of data transfer, and does not constitute a limitation of the embodiment of the present specification.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Fig. 8 is a schematic structural diagram of a task execution device according to an embodiment of the present disclosure, where the task execution device may be disposed in a target Agent (Agent) of a K8s cluster shown in fig. 2, and as shown in fig. 8, the task execution device may include: an acquisition module 81, a starting module 82 and an execution module 83;
The acquiring module 81 is configured to acquire a description file of a first task to be executed; the description file is sent to the target agent by the central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; wherein the executing mechanism label is consistent with the mechanism label provided when the target agent is registered, and the content of the stain tolerance statement is consistent with the content of stain information provided when the target agent is registered;
a starting module 82, configured to start an application process corresponding to the application program according to the application program corresponding to the first task;
the executing module 83 is configured to execute the first task in the application process.
The task execution device provided by the embodiment shown in fig. 8 may be used to execute the technical solution of the method embodiment shown in fig. 3 in this specification, and the implementation principle and technical effects may be further referred to in the related description of the method embodiment.
Fig. 9 is a schematic structural diagram of a task execution device according to another embodiment of the present disclosure, where in the task execution device shown in fig. 9, a starting module 82 is specifically configured to allocate a process group for a first task, start an application process corresponding to the application program, and add the application process to the allocated process group.
Further, the task performing device may further include: a transmission module 84 and a notification module 85;
the obtaining module 81 is further configured to obtain a task deletion instruction after the executing module 83 executes the first task, where the task deletion instruction carries a second task to be deleted;
a sending module 84, configured to send a task termination signal to a process group corresponding to a second task, so as to terminate an application process corresponding to the second task in the process group;
a notification module 85, configured to notify the central node that the second task has been deleted.
Further, a sending module 84, configured to send a node registration request to the central node before the obtaining module 81 obtains the description file of the first task to be executed; wherein the node registration request includes an organization tag of the target agent and stain information of the target agent.
Further, the task performing device may further include: a notification module 85 and a deletion module 86;
the obtaining module 81 is further configured to obtain a node deletion request;
a notification module 85, configured to notify the central node that the target agent cannot be scheduled;
a delete module 86 for deleting tasks performed on the target agent;
the notification module 85 is further configured to notify the central node to mark the state of the target agent as unavailable, so that the central node deletes the target agent.
The task execution device provided in the embodiment shown in fig. 9 may be used to execute the technical solutions of the method embodiments shown in fig. 3 to 6 in the present specification, and the implementation principle and technical effects may be further referred to in the related description of the method embodiments.
Fig. 10 is a schematic structural diagram of a task execution device according to still another embodiment of the present disclosure, where the task execution device may be disposed on a central node (Master) of the K8s cluster shown in fig. 2, and as shown in fig. 10, the task execution device may include: an acquisition module 1001, a determination module 1002, a selection module 1003, and a transmission module 1004;
the acquiring module 1001 is configured to acquire a description file of a first task to be executed;
a determining module 1002, configured to determine an executing mechanism of the first task according to the executing mechanism tag carried in the description file;
a selecting module 1003, configured to select, from the executing mechanism, a target agent suitable for executing the first task according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file;
the sending module 1004 is configured to send the description file to a target agent, where the description file carries the execution mechanism tag, an application program corresponding to the first task, and a stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task, and executes the first task in the application process.
The task execution device provided by the embodiment shown in fig. 10 may be used to execute the technical solution of the method embodiment shown in fig. 7 in this specification, and the implementation principle and technical effects may be further referred to in the related description of the method embodiment.
FIG. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure, where the electronic device may include at least one processor as shown in FIG. 11; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to execute the task execution method provided in the embodiments shown in fig. 3 to 6 of the present specification.
The Agent (Agent) in the K8s cluster may be deployed in the electronic device, and the form of the electronic device is not limited in this embodiment.
Fig. 11 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present description. The electronic device shown in fig. 11 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present description.
As shown in fig. 11, the electronic device is in the form of a general purpose computing device. Components of an electronic device may include, but are not limited to: one or more processors 410, a communication interface 420, a memory 430, and a communication bus 440 that connects the different components (including the memory 430, the communication interface 420, and the processing unit 410).
The communication bus 440 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, communication buses 440 may include industry standard architecture (industry standard architecture, ISA) buses, micro channel architecture (micro channel architecture, MCA) buses, enhanced ISA buses, video electronics standards association (video electronics standards association, VESA) local bus, and peripheral component interconnect (peripheral component interconnection, PCI) buses.
Electronic devices typically include a variety of computer system readable media. Such media can be any available media that can be accessed by the electronic device and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 430 may include computer system readable media in the form of volatile memory, such as random access memory (random access memory, RAM) and/or cache memory. Memory 430 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments shown in fig. 3-6 of the present description.
A program/utility having a set (at least one) of program modules may be stored in the memory 430, such program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules generally carry out the functions and/or methods of the embodiments described in fig. 3-6 of the present specification.
The processor 410 executes programs stored in the memory 430 to perform various functional applications and data processing, for example, to implement the task execution methods provided in the embodiments shown in fig. 3 to 6 of the present specification.
Embodiments of the present disclosure also provide an electronic device that may include at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, which invokes the program instructions to perform the task execution method provided in the embodiment shown in fig. 7 of the present specification.
The form of the electronic device is not limited in this embodiment, where a central node (Master) in the K8s cluster may be deployed in the electronic device. In a specific implementation, the electronic device may be implemented by using the structure shown in fig. 11, which is not described herein.
Embodiments of the present disclosure provide a non-transitory computer-readable storage medium storing computer instructions that cause a computer to execute the task execution method provided by the embodiments shown in fig. 3 to 6 of the present disclosure.
Embodiments of the present disclosure provide a non-transitory computer readable storage medium storing computer instructions that cause a computer to perform the task execution method provided by the embodiment of fig. 7 of the present disclosure.
The non-transitory computer readable storage media described above may employ any combination of one or more computer readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (erasable programmable read only memory, EPROM) or flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for the present specification may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (local area network, LAN) or a wide area network (wide area network, WAN), or may be connected to an external computer (e.g., connected via the internet using an internet service provider).
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present specification, the meaning of "plurality" means at least two, for example, two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present specification in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present specification.
Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.
It should be noted that, the terminals in the embodiments of the present disclosure may include, but are not limited to, a personal computer (personal computer, PC), a personal digital assistant (personal digital assistant, PDA), a wireless handheld device, a tablet computer (tablet computer), a mobile phone, an MP3 player, an MP4 player, and the like.
In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.
The foregoing description of the preferred embodiments is provided for the purpose of illustration only, and is not intended to limit the scope of the disclosure, since any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.
Claims (14)
1. A method of task execution, comprising:
acquiring a description file of a first task to be executed; the description file is sent to a target agent by a central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; the execution mechanism label is consistent with the mechanism label provided when the target agent is registered, and the content of the stain tolerance statement is consistent with the content of stain information provided when the target agent is registered;
Starting an application process corresponding to the application program according to the application program corresponding to the first task;
executing the first task in the application process;
before the obtaining the description file of the first task to be executed, the method further includes:
sending a node registration request to a central node; the node registration request comprises an organization label of a target agent and stain information of the target agent.
2. The method of claim 1, wherein the launching the application process corresponding to the application program according to the application program corresponding to the first task comprises:
assigning a process group to the first task;
starting an application process corresponding to the application program;
and adding the application process into the allocated process group.
3. The method of claim 2, wherein the executing the first task in the application process further comprises:
acquiring a task deleting instruction, wherein the task deleting instruction carries a second task to be deleted;
a task termination signal is sent to a process group corresponding to the second task, so that an application process corresponding to the second task in the process group is terminated;
Notifying the central node that the second task has been deleted.
4. A method according to any one of claims 1-3, further comprising:
acquiring a node deleting request;
notifying the central node that the target agent cannot be scheduled;
deleting the task executed on the target agent;
notifying the central node to mark the state of the target agent as unavailable so that the central node deletes the target agent.
5. A method of task execution, comprising:
acquiring a description file of a first task to be executed;
determining an executing mechanism of the first task according to the executing mechanism tag carried in the description file;
selecting a target agent suitable for executing the first task from the executing mechanism according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file;
the description file is sent to the target agent, and the description file carries the execution mechanism label, the application program corresponding to the first task and the stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task, and executes the first task in the application process;
Wherein before determining the execution mechanism of the first task according to the execution mechanism tag carried in the description file, the method further comprises:
receiving a node registration request sent by a target agent; the node registration request comprises an organization label of a target agent and stain information of the target agent.
6. A task execution device provided in a target agent, the device comprising:
the acquisition module is used for acquiring a description file of a first task to be executed; the description file is sent to a target agent by a central node, and the description file carries an execution mechanism label of the first task, an application program corresponding to the first task and a stain tolerance statement; the execution mechanism label is consistent with the mechanism label provided when the target agent is registered, and the content of the stain tolerance statement is consistent with the content of stain information provided when the target agent is registered;
the starting module is used for starting an application process corresponding to the application program according to the application program corresponding to the first task;
the execution module is used for executing the first task in the application process;
wherein the apparatus further comprises: a transmitting module;
The sending module is used for sending a node registration request to the central node before the obtaining module obtains the description file of the first task to be executed; the node registration request comprises an organization label of a target agent and stain information of the target agent.
7. The apparatus of claim 6, wherein,
the starting module is specifically configured to allocate a process group for the first task, start an application process corresponding to the application program, and add the application process to the allocated process group.
8. The apparatus of claim 7, further comprising: a sending module and a notification module;
the acquisition module is further configured to acquire a task deletion instruction after the execution module executes the first task, where the task deletion instruction carries a second task to be deleted;
the sending module is used for sending a task termination signal to the process group corresponding to the second task so as to terminate the application process corresponding to the second task in the process group;
and the notification module is used for notifying the center node that the second task is deleted.
9. The apparatus of any of claims 6-8, further comprising: a notification module and a deletion module;
The acquisition module is also used for acquiring a node deletion request;
the notification module is used for notifying the central node that the target agent cannot be scheduled;
the deleting module is used for deleting the task executed on the target agent;
the notification module is further configured to notify the central node to mark the state of the target agent as unavailable, so that the central node deletes the target agent.
10. A task execution device provided on a center node, the device comprising:
the acquisition module is used for acquiring a description file of a first task to be executed;
the determining module is used for determining the executing mechanism of the first task according to the executing mechanism label carried in the description file;
the selection module is used for selecting a target agent suitable for executing the first task from the execution mechanism according to the content of the stain tolerance statement carried in the description file; the content of the stain information provided during the registration of the target agent is consistent with the content of the stain tolerance statement carried in the description file;
the sending module is used for sending the description file to the target agent, wherein the description file carries the execution mechanism label, the application program corresponding to the first task and the stain tolerance statement, so that the target agent starts an application process corresponding to the application program according to the application program corresponding to the first task and executes the first task in the application process;
The acquisition module is further configured to receive a node registration request sent by a target agent before the determination module determines the execution mechanism of the first task; the node registration request comprises an organization label of a target agent and stain information of the target agent.
11. An electronic device, comprising:
at least one processor; and
at least one memory communicatively coupled to the processor, wherein:
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-4.
12. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of any one of claims 1 to 4.
13. An electronic device, comprising:
at least one processor; and
at least one memory communicatively coupled to the processor, wherein:
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of claim 5.
14. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of claim 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210397497.XA CN114721743B (en) | 2022-04-15 | 2022-04-15 | Task execution method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210397497.XA CN114721743B (en) | 2022-04-15 | 2022-04-15 | Task execution method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114721743A CN114721743A (en) | 2022-07-08 |
| CN114721743B true CN114721743B (en) | 2024-02-13 |
Family
ID=82243255
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210397497.XA Active CN114721743B (en) | 2022-04-15 | 2022-04-15 | Task execution method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114721743B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116339956B (en) * | 2023-05-29 | 2023-10-10 | 天翼云科技有限公司 | Distribution method and device of configuration tasks, electronic equipment and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110704165A (en) * | 2019-10-08 | 2020-01-17 | 浪潮云信息技术有限公司 | High-availability deployment method for container |
| CN111897550A (en) * | 2020-07-30 | 2020-11-06 | 哈尔滨海能达科技有限公司 | Mirror image preloading method, device and storage medium |
| CN112199200A (en) * | 2020-12-04 | 2021-01-08 | 腾讯科技（深圳）有限公司 | Resource scheduling method and device, computer equipment and storage medium |
| CN112199193A (en) * | 2020-09-30 | 2021-01-08 | 北京达佳互联信息技术有限公司 | Resource scheduling method and device, electronic equipment and storage medium |
| CN113419813A (en) * | 2021-05-21 | 2021-09-21 | 济南浪潮数据技术有限公司 | Method and device for deploying bare engine management service based on container platform |
| US11144362B1 (en) * | 2020-05-05 | 2021-10-12 | International Business Machines Corporation | Container scheduling in a container orchestration system |
| CN113535411A (en) * | 2021-09-17 | 2021-10-22 | 阿里云计算有限公司 | Resource scheduling method, equipment and system |
| KR102318533B1 (en) * | 2020-06-29 | 2021-10-28 | 인하대학교 산학협력단 | Method and System for GPU-based Embedded Edge Server Configuration and Neural Network Service Utilization |
| CN113672353A (en) * | 2021-08-24 | 2021-11-19 | 支付宝(杭州)信息技术有限公司 | Container-based task execution method and device |
| CN113672352A (en) * | 2021-08-23 | 2021-11-19 | 支付宝(杭州)信息技术有限公司 | Method and device for deploying federated learning task based on container |
-
2022
- 2022-04-15 CN CN202210397497.XA patent/CN114721743B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110704165A (en) * | 2019-10-08 | 2020-01-17 | 浪潮云信息技术有限公司 | High-availability deployment method for container |
| US11144362B1 (en) * | 2020-05-05 | 2021-10-12 | International Business Machines Corporation | Container scheduling in a container orchestration system |
| KR102318533B1 (en) * | 2020-06-29 | 2021-10-28 | 인하대학교 산학협력단 | Method and System for GPU-based Embedded Edge Server Configuration and Neural Network Service Utilization |
| CN111897550A (en) * | 2020-07-30 | 2020-11-06 | 哈尔滨海能达科技有限公司 | Mirror image preloading method, device and storage medium |
| CN112199193A (en) * | 2020-09-30 | 2021-01-08 | 北京达佳互联信息技术有限公司 | Resource scheduling method and device, electronic equipment and storage medium |
| CN112199200A (en) * | 2020-12-04 | 2021-01-08 | 腾讯科技（深圳）有限公司 | Resource scheduling method and device, computer equipment and storage medium |
| CN113419813A (en) * | 2021-05-21 | 2021-09-21 | 济南浪潮数据技术有限公司 | Method and device for deploying bare engine management service based on container platform |
| CN113672352A (en) * | 2021-08-23 | 2021-11-19 | 支付宝(杭州)信息技术有限公司 | Method and device for deploying federated learning task based on container |
| CN113672353A (en) * | 2021-08-24 | 2021-11-19 | 支付宝(杭州)信息技术有限公司 | Container-based task execution method and device |
| CN113535411A (en) * | 2021-09-17 | 2021-10-22 | 阿里云计算有限公司 | Resource scheduling method, equipment and system |
Non-Patent Citations (1)
| Title |
|---|
| Kubernetes资源调度算法的改进与实现;常旭征;焦文彬;;计算机系统应用(第07期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114721743A (en) | 2022-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10467025B2 (en) | Managing delivery of code and dependent data using application containers | |
| US10614117B2 (en) | Sharing container images between mulitple hosts through container orchestration | |
| US20240223666A1 (en) | Multiple model injection for a deployment cluster | |
| US10833955B2 (en) | Dynamic delivery of software functions | |
| US10191735B2 (en) | Language-independent program composition using containers | |
| US9798663B2 (en) | Granting exclusive cache access using locality cache coherency state | |
| US10169238B2 (en) | Memory access for exactly-once messaging | |
| US20140012767A1 (en) | Managing a Legal Hold on Cloud Documents | |
| CN110287146A (en) | Using the method, equipment and computer storage medium of downloading | |
| US11194629B2 (en) | Handling expiration of resources allocated by a resource manager running a data integration job | |
| CN114721743B (en) | Task execution method and device and electronic equipment | |
| CN113760543A (en) | Resource management method and device, electronic equipment and computer readable storage medium | |
| US10936385B2 (en) | Running kernel dependent applications inside a container | |
| CN110659104B (en) | Service monitoring method and related equipment | |
| WO2013027922A1 (en) | Compressed image file management device and method, for cloud computing system | |
| CN114168269A (en) | WebAssembly data execution method, device, equipment and medium | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN113127134A (en) | Container cluster, multi-tenant deployment method based on container cluster and electronic equipment | |
| US20140223112A1 (en) | System and method for managing data elements | |
| CN111241368B (en) | Data processing method, device, medium and equipment | |
| CN114726657A (en) | Method and device for interrupt management and data receiving and sending management and intelligent network card | |
| CN114721804B (en) | Task scheduling method and device and electronic equipment | |
| CN116996704B (en) | Single-instance container-based data management method and related device for multiple living rooms | |
| CN110750316B (en) | Method and application architecture system for processing internal tasks or input events | |
| CN110750316A (en) | Method for processing internal task or input event and application program architecture system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |