Device management method and apparatus, device, and computer readable storage medium

Abstract

The present application discloses a device management method and apparatus, a device, and a computer readable storage medium. The method can comprise: on the basis of a non-standard interface of at least one server, configuring at least one plug-in, the non-standard interface representing an interface used for calling a non-standard network management protocol; upon reception of a management instruction for a server to be managed, acquiring attribute information of said server; determining a target plug-in from among the at least one plug-in on the basis of the attribute information of said server; and calling the target plug-in to manage said server. Use of the present application can improve the efficiency and flexibility of server management.

Description

Device management method, apparatus, device, and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 25, 2024, with application number 202410346284.3 and application name “Device Management Method, Apparatus, Equipment and Computer-Readable Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a device management method, apparatus, device, and computer-readable storage medium. Background Art

[0003] With the rapid development of computer technology, the requirements for computer device management, especially server management performance, are becoming increasingly stringent. Currently, server management systems interact with servers through interfaces provided by network management protocols, enabling server management. However, since servers of different manufacturers and models may support different network management protocols and provide different interfaces, server management is diverse and complex. Therefore, efficient server management is a technical issue worthy of research.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a device management method, apparatus, device, and computer-readable storage medium, which are conducive to improving the efficiency and flexibility of server management.

[0006] In a first aspect, an embodiment of the present application provides a device management method, which includes: configuring at least one plug-in based on a non-standard interface of at least one server, where the non-standard interface represents an interface for calling a non-standard network management protocol; upon receiving a management instruction for the server to be managed, obtaining attribute information of the server to be managed; based on the attribute information of the server to be managed, determining a target plug-in from at least one plug-in; and calling the target plug-in to manage the server to be managed.

[0007] It can be seen that in this technical solution, the management device can manage the management server by calling the target plug-in. In this way, flexible management of the server can be achieved, which is conducive to improving the efficiency and flexibility of server management.

[0008] In one implementation, at least one plug-in includes a manufacturer model plug-in and / or a manufacturer plug-in. Based on the non-standard interface of at least one server, at least one plug-in is configured, including: obtaining the manufacturer and / or model of at least one server; plug-inizing the non-standard interface of at least one server to obtain a manufacturer model plug-in and / or a manufacturer plug-in, the manufacturer model plug-in corresponds to the manufacturer and model of the server, and the manufacturer plug-in corresponds to the manufacturer of the server.

[0009] It can be seen that in this technical solution, by processing the non-standard interface of the server into a plug-in, a manufacturer model plug-in corresponding to the manufacturer model of the server and / or a manufacturer plug-in corresponding to the manufacturer of the server is obtained, which is conducive to improving the convenience of server management.

[0010] In one implementation, the attribute information of the server to be managed includes the manufacturer of the server to be managed and the model of the server to be managed; the above-mentioned determining the target plug-in from at least one plug-in based on the attribute information of the server to be managed includes: when there is a manufacturer model plug-in in at least one plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed, the target plug-in is the manufacturer model plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed.

[0011] It can be seen that in this technical solution, the target plug-in can be a manufacturer and model plug-in that matches both the manufacturer and model of the server to be managed, which is conducive to quickly managing different servers.

[0012] In one implementation, the above-mentioned determining the target plug-in from at least one plug-in based on the attribute information of the server to be managed also includes: when there is no vendor plug-in in the at least one plug-in that matches both the manufacturer and the model of the server to be managed, and there is a vendor plug-in that matches the manufacturer of the server to be managed, the target plug-in is the vendor plug-in that matches the manufacturer of the server to be managed.

[0013] It can be seen that in this technical solution, the target plug-in can be a common plug-in shared by manufacturers, which is conducive to quickly managing servers of the same manufacturer.

[0014] In one implementation, the method further includes: when the target plug-in does not exist in at least one plug-in, calling a standard interface to manage the server to be managed, where the standard interface represents an interface for calling a standard network management protocol.

[0015] It can be seen that in this technical solution, when there is no target plug-in, the standard interface can be called to manage the management server, which is conducive to ensuring the minimum management capability of the management device.

[0016] In one implementation, the above-mentioned calling of the target plug-in to manage the server to be managed includes: if the target plug-in is a manufacturer model plug-in that matches both the manufacturer and model of the server to be managed, calling the manufacturer model plug-in to send interaction information to the server to be managed; and using the manufacturer model plug-in to receive response information sent by the server to be managed.

[0017] It can be seen that in this technical solution, calling the manufacturer model plug-in to send interactive information to the server to be managed is conducive to more efficient management of the server.

[0018] In one implementation, the above-mentioned calling the target plug-in to manage the server to be managed includes: if the target plug-in is a vendor plug-in that matches the vendor of the server to be managed, calling the vendor plug-in to send interaction information to the server to be managed; and using the vendor plug-in to receive response information sent by the server to be managed.

[0019] It can be seen that in this technical solution, calling the manufacturer plug-in to send interactive information to the server to be managed is conducive to more flexible management of the server.

[0020] In one implementation, the calling of the standard interface to manage the server to be managed includes: calling the standard interface to send interaction information to the server to be managed; and using the standard interface to receive response information sent by the server to be managed.

[0021] It can be seen that in this technical solution, sending interactive information to the server to be managed through a standard interface is conducive to more convenient management of the server.

[0022] In one implementation, the non-standard network management protocol called by the non-standard interface includes the Intelligent Platform Management Interface IPMI or Redfish; the standard network management protocol called by the standard interface includes the Simple Network Management Protocol SNMP or the Secure Shell Protocol SSH.

[0023] In the second aspect, an embodiment of the present application provides a device management device, which includes: a processing unit for configuring at least one plug-in based on a non-standard interface of at least one server, where the non-standard interface represents an interface for calling a non-standard network management protocol; a communication unit for receiving management instructions for the server to be managed; the processing unit is also used to obtain attribute information of the server to be managed when receiving management instructions for the server to be managed; based on the attribute information of the server to be managed, determine a target plug-in from at least one plug-in; and call the target plug-in to manage the server to be managed.

[0024] In a third aspect, an embodiment of the present application provides a management device comprising: a memory, a processor, and a network interface, wherein the processor is connected to the memory and the network interface, wherein the network interface is used to provide network communication functions, the memory is used to store program code, and the processor is used to call the program code to execute the method as in the first aspect and any possible implementation thereof.

[0025] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method in the first aspect and any possible implementation thereof.

[0026] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or computer instructions, and when the computer program or computer instructions are executed by a processor, implements the method in the first aspect and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG1 is a schematic diagram of an interaction between a server management system and a server provided in an embodiment of the present application;

[0028] FIG2 is a schematic diagram of a system architecture applied to an embodiment of the present application;

[0029] FIG3 is a schematic diagram of the structure of a plug-in server management system provided in an embodiment of the present application;

[0030] FIG4 is a flow chart of a device management method provided in an embodiment of the present application;

[0031] FIG5 is a schematic diagram of deploying a plug-in in a plug-in module provided in an embodiment of the present application;

[0032] FIG6 is a flow chart of another device management method provided in an embodiment of the present application;

[0033] FIG7 is a schematic structural diagram of a device management apparatus provided in an embodiment of the present application;

[0034] FIG8 is a schematic structural diagram of a management device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0036] In order to better understand the solutions of the embodiments of the present application, the relevant concepts that may be involved in the embodiments of the present application are first explained.

[0037] (1) Plug-ins

[0038] Plugins are a software design and development approach that allows a system to dynamically load and extend functionality at runtime to meet diverse needs and customization requirements. This approach separates core functionality from pluggable plugins. Core functionality is typically stable and infrequently changes, while plugins provide customizable and extensible functionality that can be adjusted to specific needs.

[0039] (2) Network Management Protocol

[0040] A network management protocol is a communication protocol used to manage and monitor network devices. It defines the interaction between management systems and managed devices, enabling administrators to detect, configure, and control network devices. Common network management protocols include the Intelligent Platform Management Interface (IPMI), Simple Network Management Protocol (SNMP), Redfish (a management protocol), and Secure Shell (SSH). IPMI and Redfish have unified or standardized commands and interfaces, while SNMP and SSH are mostly proprietary.

[0041] (3) Server Management System

[0042] A server management system is a software tool or platform that centrally manages and monitors server devices remotely. Alternatively, a server management system can be a management device such as a server with management functions that can centrally manage server hardware, operate servers, monitor alarms, etc.

[0043] The server management system can be used to connect and manage servers from different manufacturers, and can interact with the servers by using commands and / or interfaces in the network management protocol. The interaction between the server management system and the server includes but is not limited to: ① querying basic information of the server, such as model, serial number, health status, etc.; ② querying component information of the server, such as central processing unit (CPU) information, memory information, hard disk information, etc.; ③ operating the server, such as controlling server power on and off, controlling the unit identification light (UID) switch, account management, etc.; ④ monitoring server alarm information.

[0044] For example, see Figure 1, which is a schematic diagram illustrating interaction between a server management system and a server according to an embodiment of the present application. As shown in Figure 1, taking a server from manufacturer H as an example, the server management system can query basic information about the server from manufacturer H by calling IPMI or Redfish, query component information about the server from manufacturer H by calling Redfish, operate the server from manufacturer H by calling IPMI or Redfish, and monitor alarm information from the server from manufacturer H by calling SSH.

[0045] As can be seen from Figure 1, the network management protocols used by the server management system may be different depending on the content of the interaction between the server and the server, and servers from different manufacturers or models support different network management protocols, which makes server management diverse and complex.

[0046] Based on this, the embodiments of the present application provide a device management method and related devices, which can flexibly manage servers of different models from different manufacturers, and realize automated and intelligent server management.

[0047] The following describes the system architecture used in the embodiments of the present application.

[0048] Please refer to Figure 2, which is a schematic diagram of a device management system architecture applied to an embodiment of the present application. As shown in Figure 2, the system architecture may include a management device 210 and a server 220. Among them, the management device 210 may be a server or terminal with management functions, or the management device 210 may be a baseboard management controller such as a BMC. The management device 210 may be integrated with a server management system, and the management device 210 and the server 220 may communicate through a network management protocol. The server 220 may be a file server, a database server, an application server, etc. The server 220 may include servers from different manufacturers and may also include servers of different models. The embodiment of the present application does not impose any restrictions on this. It will be understood that the number and form of the devices shown in Figure 2 are for example only and do not constitute a limitation on the embodiment of the present application. In actual applications, management devices and servers of a number different from that shown in Figure 2 may be included.

[0049] In an embodiment of the present application, the management device 210 can use different network management protocols to interact with different servers 220. For example, for servers 220 using standard interfaces, the management device 210 can interact with the servers 220 by calling a standard network management protocol through the standard interface; for servers 220 using non-standard interfaces, the management device 210 can interact with the servers 220 by calling a non-standard network management protocol through the non-standard interface. Optionally, the management device 210 can also connect to a cloud platform, for example, by sending acquired server 220 information to the cloud platform via a northbound interface, so that the cloud platform can manage the servers 220.

[0050] In an embodiment of the present application, the management device 210 may be integrated with a server management system. This server management system may be implemented based on a plug-in, which may also be described as a plug-in server management system. The management device 210, through the plug-in server management system, can call different network management protocols to interact with different servers 220, thereby more efficiently managing the servers 220.

[0051] Please refer to Figure 3, which is a schematic diagram of the structure of a plug-in server management system provided by an embodiment of the present application. As shown in Figure 3, the plug-in server management system 30 may include a business logic module 301, a standard module 302, and a plug-in module 303.

[0052] The business logic module 301 can be used to manage the business logic of the device control calling the standard module 302 and the plug-in module 303, for example, controlling the timing and order of calling the standard module 302 and the plug-in module 303. In addition, the business logic module 301 can also be used to define the interface format for interaction between the business logic module 301 and the plug-in module 303, including but not limited to interface methods, input and output structures, and response codes.

[0053] The standard module 302 may include a standard interface control module 3021 and a standard interface 3022 .

[0054] The standard interface control module 3021 can be used to manage the standard interface called by device control.

[0055] The standard interface 3022 may include multiple standard interfaces for calling standard network management protocols (such as Redfish and IPMI).

[0056] The plug-in module 303 may include a plug-in control module 3031 and a plug-in 3032 .

[0057] The plug-in control module 3031 can be used to manage the plug-in 3032 that the device controls. Specifically, the plug-in control module 3031 can receive a directive message from the business logic module 301 and, based on the content of the directive message, select the plug-in 3032 that corresponds to the server's manufacturer and model. Furthermore, the plug-in control module 3031 can also be used to manage the device's ability to invoke methods within the plug-in 3032 based on received instructions. For example, in response to receiving an instruction to query the CPU information of a server from manufacturer A, the management device can invoke the CPU information query method within the plug-in 3032 corresponding to the server from manufacturer A through the plug-in control module 3031.

[0058] Plug-in 3032 may include plug-ins corresponding to servers of different manufacturers and / or different models. Plug-in 3032 may include multiple non-standard interfaces for calling non-standard network management protocols (such as SNMP, SSN), where multiple non-standard interfaces may be deployed in plug-in module 303 in a plug-in manner.

[0059] It is understood that the structure shown in FIG3 does not constitute a specific limitation on the plug-in server management system 30. In other embodiments of the present application, the plug-in server management system 30 may include more or fewer modules than shown, or combine or split some modules, or arrange the modules differently.

[0060] The following describes a device management method provided in an embodiment of the present application.

[0061] Please refer to Figure 4, which is a flow chart of a device management method provided by an embodiment of the present application. As shown in Figure 4, the method may include but is not limited to the following steps:

[0062] S401: Configure at least one plug-in based on a non-standard interface of at least one server.

[0063] In an embodiment of the present application, a management device can be used to manage at least one server, and the management device can be configured with at least one plug-in based on the non-standard interface of the at least one server. The non-standard interface can be understood as an interface for calling a non-standard network management protocol. Since different servers support different network management protocols, for non-standard network management protocols supported by the server, the non-standard interface for calling the non-standard network management protocol can be configured in the form of a plug-in. Non-standard network management protocols may include, for example, SNMP and SSH. The management device can interact with at least one server through a plug-in.

[0064] In some embodiments, at least one plug-in may include a manufacturer model plug-in and / or a manufacturer plug-in. The manufacturer model plug-in can be used to interact with a server of a specified model from a specified manufacturer, and the manufacturer plug-in can be used to interact with a server from a specified manufacturer. The management device may first obtain the manufacturer and / or model of at least one server, and then plug-in the non-standard interface of the non-standard network management protocol supported by at least one server to obtain a manufacturer model plug-in and / or a manufacturer plug-in. Optionally, the manufacturer model plug-in may use the manufacturer model identifier of the server as the plug-in identifier, and the manufacturer plug-in may use the manufacturer identifier of the server as the plug-in identifier, so that the management device can subsequently quickly find the corresponding plug-in for each server based on the plug-in identifier. By implementing the non-standard interface of the server based on plug-in technology, for a newly added server to be managed, the management device only needs to configure the plug-in of the newly added server to be managed to interact with the newly added server to be managed, which is conducive to the management device managing the server more efficiently.

[0065] In some embodiments, at least one plug-in may further include a model plug-in. The model plug-in may be used to interact with a server of a specified model. Optionally, the server of the specified model may be a server of a different manufacturer. The model plug-in may use the server's model identifier as the plug-in identifier.

[0066] In some embodiments, the management device may also process both the standard interface and the non-standard interface of at least one server as plug-ins to obtain at least one plug-in. The standard interface may be understood as an interface for calling a standard network management protocol. Standard network management protocols may include, for example, IPMI and Redfish. In other words, the interfaces of the network management protocols (standard network management protocols and / or non-standard network management protocols) supported by the server may be configured in the management device in the form of plug-ins. This facilitates more convenient management of the server by the management device.

[0067] Optionally, the management device may be integrated with a plug-in server management system, and at least one plug-in may be configured in the plug-in server management system.

[0068] S402: When receiving a management instruction for the server to be managed, obtain attribute information of the server to be managed.

[0069] In an embodiment of the present application, the management device may receive a management instruction for a server to be managed, and then obtain attribute information of the server to be managed. The server to be managed may be any server among the at least one server.

[0070] The management instructions for the server to be managed can be understood as management instructions that include identification information of the server to be managed. The identification information of the server to be managed can be an identifier used to uniquely identify the server to be managed, such as a name or numeric information. The attribute information of the server to be managed can include the manufacturer and / or model of the server to be managed. Optionally, the attribute information of the server to be managed can also include the IP (Internet Protocol) address, MAC (Media Access Control) address, or service type of the server to be managed.

[0071] In some embodiments, the management device may obtain attribute information of the server to be managed based on the identification information of the server to be managed. Optionally, the management device may send a query request to the server to be managed based on the identification information of the server to be managed. The query request may be used to request the attribute information of the server to be managed. For example, if the identification information of the server to be managed is digital ID 1, the management device may send a query request to the server corresponding to digital ID 1.

[0072] In some embodiments, the management device may be pre-installed with a standard interface, through which the management device can call a standard network management protocol (such as Redfish or IPMI) to send a query request to the server to be managed. After receiving the query request from the management device, the server to be managed can send a query response to the management device. The query response may include attribute information of the server to be managed, and the management device can then obtain the attribute information of the server to be managed.

[0073] In some embodiments, the management device may also pre-store attribute information of at least one server in a storage space. When the attribute information of at least one server includes attribute information of the server to be managed, the management device may also obtain the attribute information of the server to be managed from the storage space based on the identification information of the server to be managed after receiving a management instruction for the server to be managed.

[0074] In some embodiments, the management instructions for the server to be managed can be obtained directly from the user by the management device. That is, the management device can receive the management instructions from the user. Optionally, the management instructions from the user can be voice instructions, that is, the user can control the management device by voice. The management instructions can also be obtained by the management device from the cloud platform. That is, the cloud platform can send management instructions to the management device, and correspondingly, the management device can receive management instructions from the cloud platform. Optionally, the cloud platform can periodically send management instructions to the management device so that the cloud platform can manage the server in a timely manner through the management device. For example, the cloud platform can periodically monitor the server's alarm information through the management device.

[0075] S403: Determine a target plug-in from at least one plug-in based on the attribute information of the server to be managed.

[0076] In an embodiment of the present application, after obtaining the attribute information of the server to be managed, the management device can determine a target plug-in from at least one plug-in. The target plug-in is a plug-in used to interact with the server to be managed.

[0077] In some embodiments, the management device may first determine whether there is a vendor model plug-in in at least one plug-in that matches both the vendor and model of the server to be managed. If there is a vendor model plug-in in at least one plug-in that matches both the vendor and model of the server to be managed, the target plug-in may be the vendor model plug-in that matches both the vendor and model of the server to be managed.

[0078] Each manufacturer model plug-in may have a plug-in identifier, and the plug-in identifier of the manufacturer model plug-in may be the manufacturer name and model of the server, for example, in the form of "manufacturer_model". In this way, the management device can quickly search for a target plug-in that matches both the manufacturer and model of the server to be managed based on the manufacturer name and model of the server to be managed. For example, assuming that the manufacturer of the server to be managed is A and the model is a1, the management device can quickly search for a manufacturer model plug-in with a plug-in identifier of manufacturer A_model a1. If there is a manufacturer model plug-in with a plug-in identifier of manufacturer A_model a1, then the manufacturer model plug-in with a plug-in identifier of manufacturer A_model a1 is the target plug-in.

[0079] In some embodiments, if at least one plug-in does not contain a vendor-model plug-in that matches both the vendor and model of the server to be managed, the management device may determine whether at least one plug-in contains a vendor plug-in that matches the vendor of the server to be managed. If at least one plug-in contains a vendor plug-in that matches the vendor of the server to be managed, the target plug-in may be the vendor plug-in that matches the vendor of the server to be managed.

[0080] Each vendor plug-in may have a plug-in identifier, which may be the vendor name of the server. This allows the management device to quickly search for a vendor plug-in that matches the vendor of the server to be managed based on the vendor name of the server to be managed. For example, assuming the vendor of the server to be managed is Manufacturer A, the management device can quickly search for a vendor plug-in with the plug-in identifier of Manufacturer A. If a vendor plug-in with the plug-in identifier of Manufacturer A exists, then the vendor plug-in with the plug-in identifier of Manufacturer A is the target plug-in.

[0081] In some embodiments, if at least one plug-in does not contain a vendor plug-in that matches the vendor of the server to be managed, the management device may determine whether at least one plug-in contains a model plug-in that matches the model of the server to be managed. If at least one plug-in contains a model plug-in that matches the model of the server to be managed, the target plug-in may be the model plug-in that matches the model of the server to be managed.

[0082] Each model plug-in may have a plug-in identifier, and the plug-in identifier of the model plug-in may be the server model. In this way, the management device can quickly search for a model plug-in that matches the model of the server to be managed based on the model of the server to be managed. For example, assuming the model of the server to be managed is model a1, the management device can quickly search for a model plug-in with a plug-in identifier of model a1. If a model plug-in with a plug-in identifier of model a1 exists, then the model plug-in with a plug-in identifier of model a1 is the target plug-in.

[0083] In some embodiments, when there is no manufacturer model plug-in in at least one plug-in that matches both the manufacturer and the model of the server to be managed, the management device may also determine the target plug-in from at least one plug-in in the following manner: first determine whether there is a model plug-in that matches the model of the server to be managed in at least one plug-in; if there is a model plug-in that matches the model of the server to be managed, then the target plug-in is the model plug-in that matches the model of the server to be managed; if there is no model plug-in that matches the model of the server to be managed, then determine whether there is a manufacturer plug-in that matches the manufacturer of the server to be managed in at least one plug-in; if there is a manufacturer plug-in that matches the manufacturer of the server to be managed, then the target plug-in is the manufacturer plug-in that matches the manufacturer of the server to be managed.

[0084] In some embodiments, the plug-in server management system may include a plug-in module, at least one plug-in may be deployed in the plug-in module, and the management device may call the plug-in module to determine the target plug-in from at least one plug-in. Optionally, at least one plug-in may be deployed in the plug-in module based on the manufacturer and model. Among them, servers of the same manufacturer may correspond to the same manufacturer plug-in, and the manufacturer plug-in may include a non-standard interface shared by servers of the same manufacturer. In other words, the management device may interact with the server of the manufacturer corresponding to the manufacturer plug-in through the manufacturer plug-in to achieve unified management of the server of the manufacturer. In addition, for servers of different manufacturers and models, different manufacturer model plug-ins may be deployed in the plug-in module, and the manufacturer model plug-in may include non-standard interfaces unique to servers of different manufacturers and models. In other words, the management device may interact with the server of a specified model of a specified manufacturer through the manufacturer model plug-in to achieve independent management of the server of a specified model of a specified manufacturer. Optionally, for newly added servers (such as servers of newly added manufacturers or servers of newly added models), the management device may directly load the plug-in corresponding to the newly added server into the plug-in module without the need to upgrade and then take effect.

[0085] For example, please refer to Figure 5, which is a schematic diagram of deploying a plug-in in a plug-in module provided in an embodiment of the present application. As shown in Figure 5, the plug-in module 50 may include a manufacturer plug-in 501 and a manufacturer plug-in 502. Among them, the manufacturer plug-in 501 can be used to manage the device to interact with at least one server of manufacturer A, and the manufacturer plug-in 502 can be used to interact with at least one server of manufacturer B. In addition, the plug-in module 50 may also include a manufacturer model plug-in 5011, a manufacturer model plug-in 5012, a manufacturer model plug-in 5013, and a manufacturer model plug-in 5021. The manufacturer model plug-in 5011 can be used to interact with the server of model 1 of manufacturer A, the manufacturer model plug-in 5011 can be used to interact with the server of model 2 of manufacturer A, the manufacturer model plug-in 5011 can be used to interact with the server of model 3 of manufacturer A, and the manufacturer model plug-in 5021 can be used to interact with the server of model 1 of manufacturer B.

[0086] In some embodiments, the plug-in server management system may include a business logic module. The management device may first call the business logic module to send a plug-in query message to the plug-in module. The query message may be used to query whether a target plug-in exists in at least one plug-in. The management device may then call the plug-in module to determine whether the target plug-in exists. The plug-in module may send a query response message to the business logic module based on the query result. Here, the business logic module and the plug-in module may communicate in a manner specified by the business logic module, that is, the business logic module may define the communication specifications between it and the plug-in module. In other words, the plug-in module may send a query response message to the business logic module in the format specified by the business logic module.

[0087] S404: Call the target plug-in to manage the server to be managed.

[0088] In an embodiment of the present application, when the management device determines a target plug-in from at least one plug-in, the management device may call the target plug-in to manage the server to be managed.

[0089] In some embodiments, the management device may call a target plug-in to manage a server to be managed by calling the target plug-in to send interaction information to the server to be managed and using the target plug-in to receive response information sent by the server to be managed. The interaction information may include operation instructions for the server to be managed. Specifically, if the target plug-in is a vendor model plug-in that matches both the vendor and model of the server to be managed, the management device may call the vendor model plug-in to send interaction information to the server to be managed and use the vendor model plug-in to receive response information sent by the server to be managed. If the target plug-in is a vendor plug-in that matches the vendor of the server to be managed, the management device may call the vendor plug-in to send interaction information to the server to be managed and use the vendor plug-in to receive response information sent by the server to be managed. If the target plug-in is a model plug-in that matches the model of the server to be managed, the management device may call the model plug-in to send interaction information to the server to be managed and use the model plug-in to receive response information sent by the server to be managed.

[0090] In some embodiments, the target plug-in may correspond to at least one plug-in method, with different plug-in methods corresponding to different operating instructions. Upon determining the existence of the target plug-in, the management device may invoke a first plug-in method corresponding to the target plug-in to send interaction information to the server to be managed. The first plug-in method matches the operating instruction for the server to be managed. Alternatively, the management device may, through the plug-in module, invoke the first plug-in method corresponding to the target plug-in to send interaction information to the server.

[0091] In some embodiments, the operation instruction for the server to be managed may be a query instruction, that is, the interaction information may include a query instruction for the server to be managed. Accordingly, the first plug-in method may be a query method. The management server may call the query method corresponding to the target plug-in to send the interaction information to the server to be managed. Optionally, the query instruction for the server to be managed may be an instruction to query component information of the server to be managed, for example, an instruction to query the CPU information of the server to be managed, an instruction to query the memory information of the server to be managed, an instruction to query the hard disk information of the server to be managed, etc.

[0092] In some embodiments, the operation instructions for the server to be managed may be control instructions, that is, the interaction information may include control instructions for the server to be managed. Accordingly, the first plug-in method may be a control method. The management server may call the control method corresponding to the target plug-in to send interaction information to the server to be managed. Optionally, the control instructions for the server to be managed may be instructions for controlling the power on and off of the server to be managed, instructions for controlling the UID light on or off of the server to be managed, instructions for controlling the creation, modification, or deletion of accounts on the server to be managed, and so on.

[0093] In some embodiments, the operation instruction for the server to be managed may be a monitoring instruction, that is, the interaction information may include a monitoring instruction for the server to be managed. Accordingly, the first plug-in method may be a monitoring method. The management server may invoke the monitoring method corresponding to the target plug-in to send the interaction information to the server to be managed. Optionally, the monitoring instruction for the server to be managed may be an instruction to monitor the alarm information of the server to be managed.

[0094] In some embodiments, the server to be managed may receive interaction information from the management device, and then the server to be managed may send response information to the management device based on the interaction information. Correspondingly, the management device may receive response information from the server to be managed. The response information may include the response result of the server to be managed to the interaction information.

[0095] If the interaction information includes a query instruction for the server to be managed, the response information may include the query result of the server to be managed in response to the query instruction. For example, if the interaction information includes an instruction to query the CPU information of the server to be managed, the response information may include the CPU information of the server to be managed; if the interaction information includes an instruction to query the memory information of the server to be managed, the response information may include the memory information of the server to be managed; if the interaction information includes an instruction to query the hard disk information of the server to be managed, the response information may include the hard disk information of the server to be managed.

[0096] In the case where the interaction information includes control instructions for the server to be managed, the response information may include the execution result of the control instructions by the server to be managed. For example, when the interaction information includes an instruction to control the power-on of the server to be managed, the response information may include the result of whether the server to be managed successfully powered on or failed to power on; when the interaction information includes an instruction to control the UID light of the server to be managed, the response information may include the result of whether the server to be managed successfully lit up or failed to light up. Optionally, in the case where the execution result of the server to be managed indicates a failure, the response information may also include the reason for the failure of the server to be managed to facilitate timely troubleshooting.

[0097] If the interaction information includes monitoring instructions for the server to be managed, the response information may include alarm information reported by the server to be managed in response to the monitoring instructions. Optionally, the server to be managed may report alarm information periodically or once.

[0098] In some embodiments, the managed server can send response information to the plug-in module of the management device based on the interaction information. Accordingly, the management device can receive the response information from the managed server using the target plug-in through the plug-in module. Furthermore, the plug-in module of the management device can send the response information to the business logic module in the format specified by the business logic module.

[0099] In some embodiments, if the management device determines that the target plug-in does not exist, it may send interaction information to the server to be managed by invoking a standard interface. The management device may have at least one standard interface pre-installed. Alternatively, the management device may include a standard module, and the at least one standard interface may be pre-installed in the standard module.

[0100] It is understood that the interaction information sent by the management device to the managed server via the standard interface can be used to implement server management operations supported by the standard interface. For server management operations not supported by the standard interface, if the target plug-in on the server does not exist, the management device will fail the operation. Optionally, the management device can output a failure prompt to prompt the server to load the target plug-in in a timely manner.

[0101] In some embodiments, the management device may include a standard module, and the managed server may send response information to the standard module of the management device based on the interaction information. Accordingly, the management device may receive the response information from the managed server via the standard module using a standard interface. Furthermore, the standard module of the management device may send the response information to the business logic module in a format specified by the business logic module.

[0102] By implementing the embodiment of the present application, the management device can manage the management server by calling the plug-in. In this way, flexible management of the server can be achieved, which is conducive to improving the efficiency and flexibility of server management.

[0103] In an embodiment of the present application, the management device can be integrated with a plug-in server management system. The plug-in server system can include a business logic module, a standard module, and a plug-in module. Please refer to Figure 6, which is a flowchart of another device management method provided by an embodiment of the present application. As shown in Figure 6, it can include but is not limited to the following steps:

[0104] S601: The business logic module receives a management instruction for a server to be managed.

[0105] The management device can be used to manage at least one server, and the management device can receive management instructions for the server to be managed through the business logic module. The server to be managed can be any server in the at least one server. The management instructions for the server to be managed can be understood as management instructions that include identification information of the server to be managed. For example, the management instructions for the server to be managed can be used to query the CPU information of the server to be managed. Optionally, the business logic module can receive management instructions for the server to be managed from a user, or from an upper-layer network element, such as a cloud platform.

[0106] S602: The business logic module sends a query request to the server to be managed. Correspondingly, the server to be managed receives the query request from the business logic module.

[0107] The query request can be used to query the attribute information of the server to be managed. Optionally, the business logic module can send a query request to the server to be managed based on the identification information of the server to be managed. The attribute information of the server to be managed can include the manufacturer and / or model of the server to be managed.

[0108] Optionally, the business logic module may call a standard interface to send a query request to the server to be managed.

[0109] S603: The server to be managed sends a query response to the business logic module. Correspondingly, the business logic module receives the query response from the server to be managed.

[0110] The query response may include attribute information of the server to be managed.

[0111] S604: The business logic module sends a query message to the plug-in module. Correspondingly, the plug-in module receives the query message from the business logic module.

[0112] After obtaining the attribute information of the server to be managed through the business logic module, the business logic module can send a query message to the plug-in module. The plug-in module can be configured with at least one plug-in, and the query message can be used to query whether there is a target plug-in that matches the attribute information of the server to be managed in the at least one plug-in.

[0113] S605: The plug-in module determines whether a target plug-in exists in at least one plug-in.

[0114] Specifically, the plug-in module may determine whether there is a target plug-in matching the attribute information of the server to be managed in at least one plug-in according to the following process:

[0115] (1) Determine whether there is a vendor model plug-in that matches both the vendor and the model of the server to be managed in at least one plug-in. If there is a vendor model plug-in that matches both the vendor and the model of the server to be managed, the target plug-in is the vendor model plug-in that matches both the vendor and the model of the server to be managed.

[0116] (2) If there is no vendor-model plug-in that matches both the vendor and model of the server to be managed, determine whether there is a vendor plug-in that matches the vendor of the server to be managed in at least one plug-in. If there is a vendor plug-in that matches the vendor of the server to be managed, the target plug-in is the vendor plug-in that matches the vendor of the server to be managed.

[0117] Optionally, (3) if no plug-in matching the manufacturer of the server to be managed exists, determine whether a model plug-in matching the model of the server to be managed exists in at least one plug-in. If a model plug-in matching the model of the server to be managed exists, the target plug-in is the model plug-in matching the model of the server to be managed.

[0118] Optionally, (2) and (3) in the above process can also be exchanged in order, that is, when there is no manufacturer model plug-in that matches both the manufacturer and the model of the server to be managed, it can be determined first whether there is a model plug-in that matches the model of the server to be managed in at least one plug-in, and then it can be determined whether there is a manufacturer plug-in that matches the manufacturer of the server to be managed in at least one plug-in.

[0119] If the plug-in module determines that the target plug-in exists in at least one plug-in, steps S606 to S608 may be executed. If the plug-in module determines that the target plug-in does not exist in at least one plug-in, steps S609 to S611 may be executed.

[0120] S606: The plug-in module calls the target plug-in to send interaction information to the server to be managed. Correspondingly, the server to be managed receives the interaction information from the plug-in module.

[0121] The target plug-in can be any of the following: a plug-in that matches both the vendor and model of the server to be managed, a plug-in that matches the vendor of the server to be managed, or a plug-in that matches the model of the server to be managed. The target plug-in can include at least one non-standard interface. Invoking the target plug-in enables interaction with the server to be managed, i.e., invoking the target plug-in can send interaction information to the server to be managed. The interaction information can include operational instructions for the server to be managed.

[0122] S607: The server to be managed sends a response message to the plug-in module. Correspondingly, the plug-in module receives the response message from the server to be managed.

[0123] The management device can use the target plug-in through the plug-in module to receive response information from the management server. The response information may include the response result of the server to be managed to the interactive information.

[0124] S608: The plug-in module sends a response message to the business logic module. Correspondingly, the business logic module receives the response message from the plug-in module.

[0125] After receiving the response information from the server to be managed, the plug-in module may send the response information to the business logic module based on the format specified by the business logic module.

[0126] Optionally, if the target plug-in does not exist, the plug-in module can send a query response to the business logic module. Correspondingly, the business logic module can receive the query response from the plug-in module. The query response can be used to notify the query result that the target plug-in does not exist.

[0127] S609: The standard module calls the standard interface to send interaction information to the server to be managed. Correspondingly, the server to be managed receives the interaction information from the standard module.

[0128] The standard module is pre-installed with at least one standard interface. Optionally, before the standard module calls the standard interface to send interaction information to the server to be managed, the business logic module can first send instruction information to the standard module, and the instruction information can be used to instruct the standard module to call the standard interface.

[0129] S610: The server to be managed sends a response message to the standard module. Correspondingly, the standard module receives the response message from the server to be managed.

[0130] The response information may include a response result of the server to be managed to the interaction information.

[0131] S611: The standard module sends a response message to the business logic module. Correspondingly, the business logic module receives the response message from the standard module.

[0132] After receiving the response information, the standard module can send the response information to the business logic module based on the format specified by the business logic module. Optionally, the business logic module can also send the response information to the upper layer network element (such as the cloud platform).

[0133] The embodiments of the present application provide two methods of managing the server: calling the network management protocol through a plug-in non-standard interface and calling the network management protocol through a preset standard interface, which is conducive to improving the efficiency and flexibility of device management.

[0134] It is understood that, in order to implement the functions in the above embodiments, the management device and server include hardware structures and / or software modules corresponding to the respective functions. Those skilled in the art should readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software.

[0135] Please refer to Figure 7, which is a schematic diagram of the structure of a device management device provided in an embodiment of the present application. This device management device can be used to implement the device management functions described in the above embodiments. Specifically, the device management device can be used to manage at least one server, and the device management device can be installed with at least one plug-in. As shown in Figure 7, the device management device 70 may include a communication unit 701 and a processing unit 702.

[0136] A processing unit 702 is configured to configure at least one plug-in based on a non-standard interface of at least one server, where the non-standard interface is an interface for invoking a non-standard network management protocol;

[0137] The communication unit 701 is used to receive management instructions for the server to be managed;

[0138] The processing unit 702 is further configured to, upon receiving a management instruction for the server to be managed, obtain attribute information of the server to be managed; determine a target plug-in from at least one plug-in based on the attribute information of the server to be managed; and call the target plug-in to manage the server to be managed.

[0139] In one implementation, at least one plug-in includes a manufacturer model plug-in and / or a manufacturer plug-in, and the processing unit 702 is further used to obtain the manufacturer and / or model of at least one server; the non-standard interface of at least one server is plug-in-processed to obtain a manufacturer model plug-in and / or a manufacturer plug-in, the manufacturer model plug-in corresponds to the manufacturer and model of the server, and the manufacturer plug-in corresponds to the manufacturer of the server.

[0140] In one implementation, the attribute information of the server to be managed includes the manufacturer of the server to be managed and the model of the server to be managed; when there is a manufacturer-model plug-in in at least one plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed, the target plug-in is the manufacturer-model plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed.

[0141] In one implementation, when there is no at least one plug-in that matches both the manufacturer and the model of the server to be managed, and there is a vendor plug-in that matches the manufacturer of the server to be managed, the target plug-in is the vendor plug-in that matches the manufacturer of the server to be managed.

[0142] In one implementation, the processing unit 702 is further configured to, when the target plug-in does not exist in at least one plug-in, call a standard interface to manage the server to be managed, where the standard interface is an interface for calling a standard network management protocol.

[0143] In one implementation, the communication unit 701 is further used to call the manufacturer model plug-in to send interaction information to the server to be managed if the target plug-in is a manufacturer model plug-in that matches both the manufacturer and model of the server to be managed; and use the manufacturer model plug-in to receive response information sent by the server to be managed.

[0144] In one implementation, the communication unit 701 is further configured to, if the target plug-in is a vendor plug-in that matches the vendor of the server to be managed, call the vendor plug-in to send interaction information to the server to be managed; and use the vendor plug-in to receive response information sent by the server to be managed.

[0145] In one implementation, the communication unit 701 is further configured to call a standard interface to send interaction information to the server to be managed; and receive response information sent by the server to be managed using the standard interface.

[0146] In one implementation, the non-standard network management protocol called by the non-standard interface includes the Intelligent Platform Management Interface IPMI or Redfish; the standard network management protocol called by the standard interface includes the Simple Network Management Protocol SNMP or the Secure Shell Protocol SSH.

[0147] It can be understood that the functions of each functional unit of the equipment management device provided in the embodiment of the present application can be specifically implemented according to the relevant methods in the above method embodiments. The specific implementation process can refer to the relevant description in the above method embodiments and will not be repeated here.

[0148] Please refer to Figure 8, which is a structural diagram of a management device provided in an embodiment of the present application. The management device can be used to implement the functions of the management device in the above embodiment. As shown in Figure 8, the management device 80 may include: a network interface 801, a memory 802 and a processor 803, and the network interface 801, the memory 802 and the processor 803 are connected via one or more communication buses, and the communication bus is used to realize the connection and communication between these components. The network interface 801 may include a standard wired interface and a wireless interface (such as a WIFI interface). The memory 802 may include a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 802 may also include a non-volatile memory (non-volatile memory), such as a flash memory (flash memory), a solid-state drive (SSD), etc.; the memory 802 may also include a combination of the above types of memory. The processor 803 may be a central processing unit (CPU). The processor 803 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), etc. The PLD may be a field-programmable gate array (FPGA), a generic array logic (GAL), etc.

[0149] Optionally, the memory 802 is also used to store program instructions, and the processor 803 can also call the program instructions to implement the device management method in the embodiment of the present application.

[0150] In one implementation, the processor 803 calls program instructions stored in the memory 802 to implement: configuring at least one plug-in based on a non-standard interface of at least one server, where the non-standard interface represents an interface for calling a non-standard network management protocol; obtaining attribute information of the server to be managed when receiving a management instruction for the server to be managed; determining a target plug-in from at least one plug-in based on the attribute information of the server to be managed; and calling the target plug-in to manage the server to be managed.

[0151] In one implementation, at least one plug-in includes a manufacturer model plug-in and / or a manufacturer plug-in, and the processor 803 can also call the program instructions to implement: obtaining the manufacturer and / or model of at least one server; plug-in-processing the non-standard interface of at least one server to obtain a manufacturer model plug-in and / or a manufacturer plug-in, the manufacturer model plug-in corresponds to the manufacturer and model of the server, and the manufacturer plug-in corresponds to the manufacturer of the server.

[0152] In one implementation, the attribute information of the server to be managed includes the manufacturer of the server to be managed and the model of the server to be managed; when there is a manufacturer-model plug-in in at least one plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed, the target plug-in is the manufacturer-model plug-in that matches both the manufacturer of the server to be managed and the model of the server to be managed.

[0153] In one implementation, when there is no at least one plug-in that matches both the manufacturer and the model of the server to be managed, and there is a vendor plug-in that matches the manufacturer of the server to be managed, the target plug-in is the vendor plug-in that matches the manufacturer of the server to be managed.

[0154] In one implementation, the processor 803 may further call the program instruction to implement: when the target plug-in does not exist in at least one plug-in, calling a standard interface to manage the server to be managed, where the standard interface represents an interface for calling a standard network management protocol.

[0155] In one implementation, the processor 803 can also call the program instructions to achieve: if the target plug-in is a manufacturer model plug-in that matches both the manufacturer and model of the server to be managed, then call the manufacturer model plug-in to send interaction information to the server to be managed; and use the manufacturer model plug-in to receive response information sent by the server to be managed.

[0156] In one implementation, the processor 803 may also call the program instructions to implement: if the target plug-in is a vendor plug-in that matches the vendor of the server to be managed, calling the vendor plug-in to send interaction information to the server to be managed; and using the vendor plug-in to receive response information sent by the server to be managed.

[0157] In one implementation, the processor 803 may further call the program instructions to implement: calling the standard interface to send interaction information to the server to be managed; and using the standard interface to receive response information sent by the server to be managed.

[0158] In one implementation, the non-standard network management protocol called by the non-standard interface includes the Intelligent Platform Management Interface IPMI or Redfish; the standard network management protocol called by the standard interface includes the Simple Network Management Protocol SNMP or the Secure Shell Protocol SSH.

[0159] It should be understood that the principles and beneficial effects of the management device 80 described in the embodiment of the present application in solving the problem are similar to the principles and beneficial effects of the embodiments shown in Figures 4 and 6 of the present application and the aforementioned contents in solving the problem. For the sake of concise description, they will not be repeated here.

[0160] Accordingly, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method in the embodiment of the present application is implemented.

[0161] Accordingly, an embodiment of the present application further provides a computer program product, which includes a computer program or computer instructions, and when the computer program or computer instructions are executed by a processor, the method in the embodiment of the present application is implemented.

[0162] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0163] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0164] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0165] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, which can include: a flash drive, ROM, RAM, a magnetic disk or an optical disk, etc.

[0166] The above disclosure is only a preferred embodiment of the present application and is only a part of the embodiments of the present application. It cannot be used to limit the scope of rights of the present application.

Claims

1. A device management method, characterized in that: The method comprises: Configuring at least one plug-in based on a non-standard interface of at least one server, wherein the non-standard interface represents an interface for invoking a non-standard network management protocol; When receiving a management instruction for a server to be managed, obtaining attribute information of the server to be managed; Determining a target plug-in from the at least one plug-in based on the attribute information of the server to be managed; The target plug-in is called to manage the server to be managed.

2. The method according to claim 1, wherein The at least one plug-in includes a manufacturer model plug-in and / or a manufacturer plug-in, and the configuring of the at least one plug-in based on the non-standard interface of the at least one server includes: Obtaining the manufacturer and / or model of at least one server; The non-standard interface of the at least one server is plug-in-processed to obtain the manufacturer model plug-in and / or the manufacturer plug-in, the manufacturer model plug-in corresponds to the manufacturer and model of the server, and the manufacturer plug-in corresponds to the manufacturer of the server.

3. The method according to claim 2, wherein The attribute information of the server to be managed includes the manufacturer of the server to be managed and the model of the server to be managed; The determining a target plug-in from the at least one plug-in based on the attribute information of the server to be managed includes: In the case that there is a manufacturer model plug-in that matches both the manufacturer and the model of the server to be managed in the at least one plug-in, the target plug-in is the manufacturer model plug-in that matches both the manufacturer and the model of the server to be managed.

4. The method according to claim 3, wherein The determining a target plug-in from the at least one plug-in based on the attribute information of the server to be managed further includes: If there is no plug-in in the at least one plug-in that matches both the manufacturer and the model of the server to be managed, and there is a vendor plug-in that matches the manufacturer of the server to be managed, the target plug-in is the vendor plug-in that matches the manufacturer of the server to be managed.

5. The method according to claim 3 or 4, wherein: The method further comprises: In the case that the target plug-in does not exist in the at least one plug-in, a standard interface is called to manage the server to be managed, where the standard interface is an interface for calling a standard network management protocol.

6. The method according to any one of claims 1 to 5, characterized in that The calling of the target plug-in to manage the server to be managed includes: If the target plug-in is a vendor model plug-in that matches both the vendor of the server to be managed and the model of the server to be managed, calling the vendor model plug-in to send interaction information to the server to be managed; The manufacturer model plug-in is used to receive response information sent by the server to be managed.

7. The method according to any one of claims 1 to 5, characterized in that The calling of the target plug-in to manage the server to be managed includes: If the target plug-in is a vendor plug-in that matches the vendor of the server to be managed, calling the vendor plug-in to send interaction information to the server to be managed; The manufacturer plug-in is used to receive response information sent by the server to be managed.

8. The method according to claim 5, wherein The calling of the standard interface to manage the server to be managed includes: Calling the standard interface to send interaction information to the server to be managed; The standard interface is used to receive response information sent by the server to be managed.

9. The method according to any one of claims 1 to 8, wherein The non-standard network management protocol called by the non-standard interface includes an Intelligent Platform Management Interface (IPMI) or Redfish; and / or the standard network management protocol called by the standard interface includes a Simple Network Management Protocol (SNMP) or a Secure Shell Protocol (SSH).

10. A management device, characterized in that: It includes a memory, a processor and a network interface, the processor is connected to the memory and the network interface, wherein the network interface is used to provide a network communication function, the memory is used to store program code, and the processor is used to call the program code to execute the method described in any one of claims 1 to 9.

Images