Management method, system and server based on Kubernetes system

Abstract

The embodiments of the present application disclose a Kubernetes system-based management method, system and server, which can remotely manage and create virtual machines through the Kubernetes system, saves system operation and maintenance cost, integrates hardware resources of a Kubernetes container cluster, improves resource utilization, and makes cluster management more efficient and flexible. The management method comprises the following steps: obtaining an extension management request of a user, wherein the extension management request is a new request with an extension request parameter list added on the basis of a user resource request, and the user resource request is an original request for requesting resources in the Kubernetes system; analyzing the extension management request to determine whether there is an extension parameter in the extension request parameter list obtained after analysis; if there is an extension parameter in the extension request parameter list, calling an Agent service to execute corresponding remote management functions and / or virtual machine creation functions according to the extension parameter, wherein the Agent service is a special background daemon running on all nodes when starting, and provides services for executing remote management functions and virtual machine creation functions.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to management methods, systems and servers based on Kubernetes. Background Technology

[0002] Kubernetes is a brand-new distributed architecture solution based on container technology. It is an open-source container cluster management system from Google, often abbreviated as K8s. K8s has comprehensive cluster management capabilities, including multi-layered security protection and access control mechanisms, multi-tenant application support capabilities, transparent service registration and service discovery mechanisms, built-in intelligent load balancers, powerful fault detection and self-healing capabilities, rolling service upgrades and online scaling capabilities, scalable automatic resource scheduling mechanisms, and multi-granularity resource quota management capabilities.

[0003] Currently, with the acceleration of information system cloudification, enterprises have a stronger need to establish their own private clouds. An important business scenario for private cloud applications is to apply for the creation of virtual machines. However, the K8s system does not currently have the function of creating virtual machines. The traditional way to create virtual machines is to install a private cloud resource management platform, such as OpenStack, to receive requests and create virtual machines.

[0004] Traditional virtual machine creation methods, cloud resource management platforms such as OpenStack, have the following drawbacks: complex installation and configuration processes, require dedicated personnel for maintenance, resulting in high operation and maintenance costs, high consumption of computing resources, and duplication of resource scheduling functions with some functions of the widely used Kubernetes scheduling. Summary of the Invention

[0005] Based on this, it is necessary to address the above-mentioned problems. This application proposes a management method, system, and server based on the Kubernetes system, which can remotely manage and create virtual machines through the Kubernetes system, saving system operation and maintenance costs. At the same time, it integrates the hardware resources of the Kubernetes container cluster, improves resource utilization, and makes cluster management more efficient and flexible.

[0006] Firstly, this application provides a management method based on a Kubernetes system, including:

[0007] Obtain the user's extended management request, where the extended management request is a new request with an extended request parameter list added on top of the user resource request, and the user resource request is the original request used to request resources in the Kubernetes system;

[0008] Parse the extension management request and determine whether the extension parameters exist in the list of extension request parameters obtained after parsing.

[0009] If there are extended parameters in the extended request parameter list, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters. The Agent service is a dedicated background daemon process that runs on all nodes when the cluster nodes start up, providing services to execute the remote management function and the virtual machine creation function.

[0010] Optionally, in one possible implementation of the first aspect, if the extended parameters include the first parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters, including: invoking the Agent service to parse the parameter group of the virtual machine from the first parameter, wherein the parameter group is constructed according to the parameter specification of the virtual machine; and invoking the virtual machine creation callback function to execute the virtual machine creation function according to the parsed parameter group.

[0011] Optionally, in one possible implementation of the first aspect, if the extended parameters include the second parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters, including: invoking the Agent service to execute the remote management function according to the parameter value of the second parameter, wherein the parameter value of the second parameter corresponds one-to-one with the remote management function.

[0012] Optionally, in one possible implementation of the first aspect, the remote management function includes at least one of the following: remotely controlling power on / off, installing / uninstalling software, or running programs.

[0013] Optionally, in one possible implementation of the first aspect, parsing the extension management request and determining whether there are extension parameters in the parsed extension request parameter list includes: calling the requestHandler function to listen for extension management requests and determining whether there are extension parameters in the extension request parameter list.

[0014] Optionally, in one possible implementation of the first aspect, before obtaining the user's extended management request, the method further includes: starting an Agent background daemon during the initialization of the Kubernetes system, wherein the Agent background daemon is started on a cluster node in the Kubernetes system.

[0015] Optionally, in one possible implementation of the first aspect, the above management method further includes: if the extended parameter is not present in the extended request parameter list, calling the system function of the Kubernetes system to create a container.

[0016] Secondly, this application provides a Kubernetes system, including:

[0017] Request module, parsing module, and management module;

[0018] The request module is used to obtain the user's extended management request. The extended management request is a new request with an extended request parameter list added on the basis of the user resource request. The user resource request is the original request used to request resources in the Kubernetes system.

[0019] The parsing module is used to: parse the extension management request and determine whether there are extension parameters in the list of extension request parameters obtained after parsing, wherein the extension parameters include at least two types of parameters;

[0020] The management module is used to: if there are extended parameters in the extended request parameter list, call the Agent service to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters. The Agent service is a dedicated background daemon process that runs on all nodes when the cluster nodes start up, providing services to execute the remote management function and the virtual machine creation function.

[0021] Thirdly, this application provides a server on which a Kubernetes system is deployed, including: a processor and a memory, wherein executable code is stored in the memory; when the executable code is invoked by the processor, the server performs the management method as described in any one of the first aspects and its implementations.

[0022] Fourthly, this application provides a computer-readable storage medium having executable code stored thereon, which, when invoked by a server's processor, causes the server to perform the management method as described in any one of the first aspects and its implementations.

[0023] The technical solution provided in this application has the following beneficial effects:

[0024] In this technical solution, a new extended management request is obtained by redesigning the user resource request, and a dedicated Agent service is created to perform remote management and virtual machine creation functions. This allows the Kubernetes system to extend its functionality beyond its original container creation functions, enabling it to perform remote management and virtual machine creation. This allows for remote management and creation of virtual machines through the Kubernetes system without reinstalling cloud resource management platforms such as OpenStack, thus eliminating the need to deploy such cloud resource management platforms, saving system operation and maintenance costs. At the same time, it integrates the hardware resources of the Kubernetes container cluster, improving resource utilization and making cluster management more efficient and flexible.

[0025] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0026] The above and other objects, features and advantages of this application will become more apparent from the more detailed description of exemplary embodiments thereof in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments thereof.

[0027] Figure 1 This is a schematic diagram of one embodiment of the management method based on the Kubernetes system in this application.

[0028] Figure 2 This is a schematic diagram of the Kubernetes system in an embodiment of this application;

[0029] Figure 3 This is a schematic diagram of the server structure in an embodiment of this application. Detailed Implementation

[0030] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to make this application more thorough and complete, and to fully convey the scope of this application to those skilled in the art.

[0031] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0032] It should be understood that although the terms "first," "second," "third," etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0033] This application provides a management method, system, and server based on the Kubernetes system. By improving the Kubernetes system, it enables remote management and creation of virtual machines, saving system operation and maintenance costs. At the same time, it integrates the hardware resources of the Kubernetes container cluster, improves resource utilization, and makes cluster management more efficient and flexible.

[0034] To facilitate understanding of the Kubernetes-based management method, system, and server in the embodiments of this application, the Kubernetes-based management method in this application will be described in detail below with reference to the accompanying drawings and specific embodiments:

[0035] Figure 1 This is a schematic diagram of one embodiment of the management method based on the Kubernetes system in this application.

[0036] like Figure 1 As shown in the embodiments of this application, the management method based on the Kubernetes system includes:

[0037] 101. Obtain the user's extended management request.

[0038] In this embodiment of the application, the extended management request is a new request with an extended request parameter list added on top of the user resource request, and the user resource request is the original request used to request resources in the Kubernetes system.

[0039] Furthermore, the extended request parameter list may include various extended parameters, with different parameters indicating different functions. Optionally, the extended parameters include a first parameter and a second parameter, corresponding to the virtual machine creation function and the remote management function, respectively. In addition, other functional parameters can be added to the extended request parameter list according to functional requirements, and this application does not impose any restrictions on this.

[0040] Furthermore, the remote management function includes, but is not limited to, at least one of the following: remote control of power on / off, installation / uninstallation of software, or running of programs. Different values ​​of the first parameter can correspond to different remote management functions. On one hand, different values ​​of the set of first parameter values ​​can represent different remote management functions. For example, when the first parameter is set to a first preset value, it represents remote control of power on / off; when the second parameter is set to a second preset value, it represents installation / uninstallation of software; and when the first parameter is set to a third preset value, it represents running a program. On the other hand, more parameters can be set in the extended request parameter list to represent different functions.

[0041] 102. Parse the extended management request and determine whether extended parameters exist in the list of extended request parameters obtained after parsing.

[0042] In this embodiment of the application, the parsing operation can be implemented by calling relevant parsing functions, such as the requestHandler function.

[0043] Optionally, in one embodiment of this application, the requestHandler function is called to listen for extension management requests and determine whether extension parameters exist in the extension request parameter list.

[0044] The requestHandler function can listen for changes in request information. However, if it detects that the extension management request is the same as an existing user resource request in the Kubernetes system or that the extension request parameter list is empty, it determines that there are no extension parameters in the extension request parameter list; otherwise, it determines that there are extension parameters in the extension request parameter list.

[0045] 103. If extended parameters exist in the extended request parameter list, call the Agent service to execute the corresponding remote management function, virtual machine or container creation function according to the extended parameters.

[0046] In this embodiment, the Agent service is newly customized and can complete the remote management function and / or virtual machine creation and other extended functions issued by the task execution module. Specifically, the Agent service is a dedicated background daemon process that runs on all nodes when the cluster nodes start up, providing services for executing remote management functions and virtual machine creation functions.

[0047] When an extended parameter is present in the extended request parameter list, the extended parameter may include at least one of the first parameter or the second parameter.

[0048] Optionally, in one embodiment of this application, if the extended parameters include the first parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters, including:

[0049] The Agent service is invoked to parse the parameter group of the virtual machine from the first parameter, where the parameter group is constructed according to the parameter specification of the virtual machine;

[0050] Based on the parsed parameter set, the virtual machine creation callback function is called to execute the virtual machine creation function.

[0051] Optionally, in one embodiment of this application, if the extended parameters include a second parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters, including:

[0052] The Agent service is invoked to execute remote management functions based on the value of the second parameter, where there is a one-to-one correspondence between the value of the second parameter and the remote management function.

[0053] It should be understood that when creating a virtual machine using extended functions, the first parameter can specifically be the virtual machine's parameter information; when executing extended management requests such as remote management, the second parameter can specifically be the extended management command and parameters. Furthermore, both the first and second parameters can be implemented using the pods parameter, which is a commonly used parameter format in the Kubernetes system and stores JSON formatted information.

[0054] Optionally, in one embodiment of this application, before obtaining the user's extended management request, the method further includes:

[0055] During the initialization of the Kubernetes system, the Agent process is started, which is created on the cluster nodes of the Kubernetes system.

[0056] 104. If the extended parameters are not present in the extended request parameter list, call the Kubernetes system's system function to create the container.

[0057] In this embodiment, when no extension parameters are present in the extension request parameter list, the extension management request is essentially equivalent to the original user resource request in the Kubernetes system. In this case, the user resource request only includes basic parameters such as container parameter information, and the original Kubernetes system logic is executed to create the container.

[0058] In this embodiment, a new extended management request is obtained by redesigning the user resource request, and a dedicated Agent service is created to perform remote management and virtual machine creation functions. This allows the Kubernetes system to extend its functionality beyond its original container creation functions, enabling it to perform remote management and virtual machine creation. This allows for remote management and creation of virtual machines through the Kubernetes system without reinstalling cloud resource management platforms such as OpenStack, thus eliminating the need to deploy such cloud resource management platforms, saving system operation and maintenance costs. At the same time, it integrates the hardware resources of the Kubernetes container cluster, improving resource utilization and making cluster management more efficient and flexible.

[0059] Corresponding to the aforementioned application function implementation method embodiments, this application also provides a Kubernetes system, server, computer-readable storage medium, and corresponding embodiments.

[0060] Figure 2 This is a schematic diagram of the Kubernetes system in an embodiment of this application.

[0061] like Figure 2 As shown, in this embodiment of the application, the Kubernetes system 20 includes: a request module 201, a parsing module 202, and a management module 203;

[0062] Request module 201 is used to obtain the user's extended management request, wherein the extended management request is a new request with an extended request parameter list added on the basis of the user resource request, and the user resource request is the original request used to request resources in the Kubernetes system;

[0063] Parsing module 202 is used to: parse the extended management request and determine whether there are extended parameters in the list of extended request parameters obtained after parsing, wherein the extended parameters include at least two types of parameters;

[0064] Management module 203 is used to: if there are extended parameters in the extended request parameter list, call the Agent service to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameters. The Agent service is a dedicated background daemon process that runs on all nodes when the cluster nodes start up, providing services for executing remote management functions and virtual machine creation functions.

[0065] Optionally, in some embodiments of this application, if the extended parameters include the first parameter, the management module 203 specifically performs the following operations:

[0066] The Agent service is invoked to parse the parameter group of the virtual machine from the first parameter, where the parameter group is constructed according to the parameter specification of the virtual machine;

[0067] Based on the parsed parameter set, the virtual machine creation callback function is called to execute the virtual machine creation function.

[0068] Optionally, in some embodiments of this application, if the extended parameters include the second parameter, the management module 203 specifically performs the following operations:

[0069] The Agent service is invoked to execute remote management functions based on the value of the second parameter, where there is a one-to-one correspondence between the value of the second parameter and the remote management function.

[0070] Optionally, in some embodiments of this application, the remote management functions performed by the management module 203 include at least one of the following: remotely controlling power on / off, installing / uninstalling software, or running programs.

[0071] Optionally, in some embodiments of this application, the parsing module 202 is specifically used to perform the following operation: by calling the requestHandler function to listen for extension management requests, determine whether there are extension parameters in the extension request parameter list.

[0072] Optionally, in some embodiments of this application, before the request module 201 obtains the user's extended management request, the management module 203 is further configured to perform the following operations: during the initialization process of the Kubernetes system, start the Agent background daemon process, wherein the Agent background daemon process is started on the cluster node of the Kubernetes system.

[0073] Optionally, in some embodiments of this application, the management module 203 is further configured to perform the following operations: if there are no extended parameters in the extended request parameter list, call the system function of the Kubernetes system to create a container.

[0074] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation and its beneficial effects have been described in detail in the embodiments related to the method, and will not be elaborated further here.

[0075] Figure 3 This is a schematic diagram of the server structure in an embodiment of this application.

[0076] like Figure 3 As shown, in this embodiment of the application, the server 30 includes a memory 301 and a processor 302. Executable code is stored in the memory, and when the executable code is executed by the processor, the processor performs the method described in any of the above embodiments.

[0077] Specifically, in this embodiment of the application, server 30 can be a cloud server or a node server, etc.

[0078] Processor 302 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0079] Memory 301 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. ROM may store static data or instructions required by processor 302 or other modules of the computer. Permanent storage devices may be read-write storage devices. Permanent storage devices may be non-volatile storage devices that retain stored instructions and data even when the computer is powered off. In some embodiments, permanent storage devices use mass storage devices (e.g., magnetic or optical disks, flash memory) as permanent storage devices. In other embodiments, permanent storage devices may be removable storage devices (e.g., floppy disks, optical drives). System memory may be a read-write storage device or a volatile read-write storage device, such as dynamic random access memory. System memory may store some or all of the instructions and data required by the processor during operation. Furthermore, memory 301 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, memory 301 may include a removable storage device that is readable and / or writable, such as a laser disc (CD), a read-only digital versatile optical disc (e.g., DVD-ROM, dual-layer DVD-ROM), a read-only Blu-ray disc, an ultra-high density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not contain carrier waves or transient electronic signals transmitted wirelessly or via wired connections.

[0080] The memory 301 stores executable code, which, when processed by the processor 302, can cause the processor 302 to execute part or all of the methods described above.

[0081] Furthermore, the method according to this application can also be implemented as a computer program or computer program product, which includes computer program code instructions for performing some or all of the steps in the method described above.

[0082] Alternatively, this application may be implemented as a computer-readable storage medium (or machine-readable storage medium) storing executable code (or computer program, or computer instruction code) thereon, which, when executed by a processor of a server, causes the processor to perform part or all of the steps of the methods described above according to this application.

[0083] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0084] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0085] Finally, it should be noted that in this document, relationships such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "include," "contain," or any other variations are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus.

[0086] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0087] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0088] If the integrated unit is implemented as 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 technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0089] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A management method based on a Kubernetes system, characterized in that, include: During the initialization of the Kubernetes system, the Agent background daemon is started, wherein the Agent background daemon is started on the cluster node of the Kubernetes system; Obtain the user's extended management request, wherein the extended management request is a new request with an extended request parameter list added on top of the user resource request, and the user resource request is the original request used to request resources in the Kubernetes system; Parse the extension management request and determine whether there are extension parameters in the parsed extension request parameter list, including: calling the requestHandler function to listen to the extension management request and determining whether there are extension parameters in the extension request parameter list; If the extended parameter exists in the extended request parameter list, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameter. The Agent service is a dedicated background daemon that automatically runs on all nodes when the cluster nodes start, providing services for executing the remote management function and the virtual machine creation function. If the extended parameter includes a first parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameter, including: invoking the Agent service to parse a parameter group of the virtual machine from the first parameter, wherein the parameter group is constructed according to the virtual machine parameter specification; and invoking a callback function for virtual machine creation to execute the virtual machine creation function according to the parsed parameter group. If the extended parameter includes a second parameter, the Agent service is invoked to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameter, including: invoking the Agent service to execute the remote management function according to the parameter value of the second parameter, wherein the parameter value of the second parameter corresponds one-to-one with the remote management function. If the extended parameter is not present in the list of extended request parameters, the system function of the Kubernetes system is invoked to create the container.

2. The management method according to claim 1, characterized in that, The remote management function includes at least one of the following: remotely controlling power on / off, installing / uninstalling software, or running programs.

3. A Kubernetes system, characterized in that, The system executes the management method as described in any one of claims 1-2, and the system comprises: Request module, parsing module, and management module; The request module is used to obtain the user's extended management request, wherein the extended management request is a new request with an extended request parameter list added on the basis of the user resource request, and the user resource request is the original request used to request resources in the Kubernetes system. The parsing module is used to: parse the extension management request and determine whether there are extension parameters in the extension request parameter list obtained after parsing, wherein the extension parameters include at least two types of parameters; The management module is used to: if the extended parameter exists in the extended request parameter list, call the Agent service to execute the corresponding remote management function and / or virtual machine creation function according to the extended parameter, wherein the Agent service is a dedicated background daemon process that runs on all nodes when the cluster nodes start, providing services for executing the remote management function and the virtual machine creation function; if the extended parameter does not exist in the extended request parameter list, call the system function of the Kubernetes system to create a container.

4. A server, characterized in that, The server is equipped with a Kubernetes system, including: A processor and a memory, wherein executable code is stored in the memory; When the executable code is invoked by the processor, the server performs the management method as described in any one of claims 1-2.

5. A computer-readable storage medium having executable code stored thereon, which, when invoked by a processor of a server, causes the server to perform the management method as described in any one of claims 1-2.

Images