IP Library Granted Patent US 11,915,067
Granted Patent B2
US 11,915,067 · App. 17/801,897 · Granted Feb 27, 2024

Resource management method for node in kubernetes, device, and medium

Inventor: Dekui Wang (Jiangsu, CN)
Assignee: INSPUR SUZHOU INTELLIGENT TECHNOLOGY CO., LTD.
G06F9/547G06F9/5016
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,915,067
App. No.
17/801,897
Granted
Feb 27, 2024
Kind
B2
Abstract

A resource management method for a node in Kubernetes, a computer device, and a readable storage medium. The method includes following steps: initializing a component to start a main process; defining, by means of the main process, subprocesses for managing resources respectively; in response to a detection from the main process that a plurality of actual resources is present in a node among the resources, starting a subprocess corresponding to each of the actual resources, and starting gRPC service for each started subprocess; and registering the resources corresponding to a subprocesses where the gRPC service is successfully started to Kubernetes by using the main process enabling the subprocesses where the gRPC service is successfully started to manage the actual resources.

Claims (57)

1. A resource management method for a node in a resource manager, comprising:

initializing a component to start a main process;

defining, by means of the main process, a plurality of subprocesses for managing a plurality of resources respectively;

in response to a detection from the main process that a plurality of actual resources is present in a node among the plurality of resources, starting a subprocess corresponding to each of the plurality of actual resources, and starting Remote Procedure Call (RPC) service for each started subprocess; and

registering resources, corresponding to a subprocess where the RPC service is successfully started, to the resource manager by means of the main process, enabling the subprocess where the RPC service is successfully started to manage the plurality of actual resources;

wherein the defining, by means of the main process, a plurality of subprocesses for managing a plurality of resources respectively further comprises:

defining, by means of the main process, resource names and attributes of preset resource processing interfaces for the plurality of subprocesses respectively.

2. The method according to claim 1 , wherein the enabling the subprocess where the RPC service is successfully started to manage the plurality of actual resources further comprises:

in response to a request, received from the resource manager, to apply for a resource for a container, allocating, by a subprocess corresponding to a resource to be applied for, the resource to be applied for to the container by the RPC service.

3. The method according to claim 2 , further comprising:

recording, by means of the main process, a correspondence between the container and an allocated resource to be applied for; and

generating a persistent file from the correspondence, and storing the persistent file to the node.

4. The method according to claim 3 , wherein the initializing a component to start a main process further comprises:

loading the persistent file to acquire a correspondence between a resource and a container of the node.

5. The method according to claim 3 , further comprising:

starting RPC service for the main process; and

querying, by use of the RPC service of the main process, resource utilization information of the node.

6. The method according to claim 1 , further comprising:

detecting, periodically in the node, a resource corresponding to a subprocess that is not started.

7. The method according to claim 1 , wherein the starting RPC service for each started subprocess further comprises:

storing, locally in the node, a socket file corresponding to the subprocess where the RPC service is successfully started; and

monitoring, by the main process based on a plurality of socket files, states of the subprocess where the RPC service is successfully started.

8. A computer device, comprising:

at least one processor; and

a memory storing a computer program configured to run in the at least one processor, wherein the at least one processor executes the computer program to:

initialize a component to start a main process;

define, by means of the main process, a plurality of subprocesses for managing a plurality of resources respectively;

in response to a detection from the main process that a plurality of actual resources is present in a node among the plurality of resources, start a subprocess corresponding to each of the plurality of actual resources, and start Remote Procedure Call (RPC) service for each started subprocess; and

register resources, corresponding to a subprocess where the RPC service is successfully started, to a resource manager by means of the main process, enabling the subprocess where the RPC service is successfully started to manage the plurality of actual resources;

wherein the at least one processor further executes the computer program to:

define, by means of the main process, resource names and attributes of preset resource processing interfaces for the plurality of subprocesses respectively.

9. The computer device according to claim 8 , wherein in order to enable the subprocess where the RPC service is successfully started to manage the plurality of actual resources, the at least one processor, upon execution of the computer program, is configured to:

in response to a request, received from the resource manager, to apply for a resource for a container, allocate, by a subprocess corresponding to a resource to be applied for, the resource to be applied for to the container by the RPC service.

10. The computer device according to claim 9 , wherein the at least one processor, upon execution of the computer program, is configured to:

record, by means of the main process, a correspondence between the container and an allocated resource to be applied for; and

generate a persistent file from the correspondence, and store the persistent file to the node.

11. The computer device according to claim 10 , wherein in order to initialize the component to start the main process, the at least one processor, upon execution of the computer program, is configured to:

load the persistent file to acquire a correspondence between a resource and a container of the node.

12. The computer device according to claim 10 , wherein the at least one processor, upon execution of the computer program, is configured to:

start RPC service for the main process; and

query, by use of the RPC service of the main process, resource utilization information of the node.

13. The computer device according to claim 8 , wherein the at least one processor, upon execution of the computer program, is configured to:

detect, periodically in the node, a resource corresponding to a subprocess that is not started.

14. The computer device according to claim 8 , wherein in order to start the RPC service for each started subprocess, the at least one processor, upon execution of the computer program, is configured to:

store, locally in the node, a socket file corresponding to the subprocess where the RPC service is successfully started; and

monitor, by the main process based on a plurality of socket files, states of the subprocess where the RPC service is successfully started.

15. The computer device according to claim 8 , the at least one processor, upon execution of the computer program, is configured to:

integrate a plurality of resource device plug-ins into the component based on mechanisms of a multiple process, a RPC communication, and a file monitoring and management.

16. A non-transitory storage medium, storing a computer program that is executable by a processor, wherein upon execution by the processor, is configured to cause the processor to:

initialize a component to start a main process;

define, by means of the main process, a plurality of subprocesses for managing a plurality of resources respectively;

in response to a detection from the main process that a plurality of actual resources is present in a node among the plurality of resources, start a subprocess corresponding to each of the plurality of actual resources, and start Remote Procedure Call (RPC) service for each started subprocess; and

register resources, corresponding to a subprocess where the RPC service is successfully started, to a resource manager by means of the main process, enabling the subprocess where the RPC service is successfully started to manage the plurality of actual resources;

wherein the non-transitory storage medium is further configured to cause the processor to:

defining, by means of the main process, resource names and attributes of preset resource processing interfaces for the plurality of subprocesses respectively.

17. The method according to claim 1 , further comprising:

integrating a plurality of resource device plug-ins into the component based on mechanisms of a multiple process, a RPC communication, and a file monitoring and management.

Assignments (2)
LICENSE Recorded Jun 30, 2026
From: IEIT SYSTEMS CO., LTD
To: AIVRES SYSTEMS INC.
Reel/Frame 075857/0939 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 24, 2022
From: WANG, DEKUI
To: INSPUR SUZHOU INTELLIGENT TECHNOLOGY CO., LTD.
Reel/Frame 060885/0695 →
Priority Claims (1)
CN 202010112361.0 · Feb 24, 2020 · national
Continuity (1)
Related Publication 20230084772A1 · Mar 16, 2023