Server management method, baseboard management controller and server

Abstract

The invention provides a server management method, a baseboard management controller and a server. Relates to the technical field of servers. In order to solve the problem that the configuration cost of a management server of a baseboard management controller is high, the server management method comprises the steps that the baseboard management controller receives a management request sent by an electronic device, the management request is used for querying hardware information of a target server hardware system, one or more containers run in the baseboard management controller, the containers correspond to the server hardware systems, and each container comprises an application program used for obtaining hardware information of the corresponding server hardware system; and the substrate management controller obtains hardware information of the target server hardware system and sends the hardware information to the electronic equipment. According to the embodiment of the invention, based on the multiple deployed containers, the substrate management controller can realize management of multiple server hardware systems, and the configuration cost of the substrate management controller is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of servers, and in particular to a controller system, a baseboard management controller and a server. Background Art

[0002] A baseboard management controller (BMC) is a management system for computing devices (such as servers) that is used to monitor and manage the hardware status of computing devices. BMC includes a hardware part (also called BMC hardware) and a software part (also called BMC software).

[0003] At present, with the increase in the number of single processor cores, the application of single processor systems is becoming more and more widespread; for example, multiple single processor systems can be deployed in the physical frame of a server to form a server with multiple single processor systems (also called a multi-processor server or a server containing multiple server hardware systems, etc.).

[0004] However, for multi-processor servers, since each single-processor system needs to be configured with a set of BMC hardware and software, it takes up more motherboard area and requires complex software modification, resulting in a high configuration cost for the baseboard management controller to manage multi-processor servers. Summary of the invention

[0005] According to various embodiments of the present application, a server management method, a baseboard management controller and a server are provided, which can manage one or more server hardware systems and reduce the configuration cost of the baseboard management controller.

[0006] In a first aspect, an embodiment of the present application provides a server management method, which is applied to a baseboard management controller, the baseboard management controller is communicatively connected with one or more server hardware systems, and the method includes:

[0007] The baseboard management controller receives a management request sent by an electronic device, where the management request is used to query the hardware information of a target server hardware system, wherein one or more containers are running in the baseboard management controller, the containers correspond to the server hardware systems, and each container includes an application for obtaining the hardware information of the corresponding server hardware system; the baseboard management controller obtains the hardware information of the target server hardware system and sends it to the electronic device, and the hardware information of the target server hardware system is obtained by the application of the corresponding container.

[0008] Through the above method, for a server containing multiple server hardware systems, the baseboard management controller deploys the application for managing the server based on the container, so that each container corresponds to each server hardware system; by running multiple containers, based on the application in the container, the hardware information of the multiple server hardware systems is obtained respectively, so that the baseboard management controller can manage the server containing multiple server hardware systems, reducing the configuration cost of the baseboard management controller; it has strong ease of use and practicality.

[0009] In a possible implementation of the first aspect, a baseboard management controller is configured with a unified network address for communicating with the electronic device; the baseboard management controller receives a management request sent by the electronic device, including: the baseboard management controller receives the management request sent by the electronic device based on the unified network address; the baseboard management controller obtains hardware information of a target server hardware system, including: the baseboard management controller obtains hardware information from a corresponding container based on the target server hardware system targeted by the management request.

[0010] In a possible implementation manner of the first aspect, the baseboard management controller obtains hardware information of a target server hardware system and sends the information to the electronic device, including:

[0011] The baseboard management controller aggregates the acquired hardware information of the target server hardware system based on the unified network address and sends the information to the electronic device.

[0012] Through the above method, based on the configured unified network address, the baseboard management controller can provide a unified network address to the outside world. The electronic device does not need to understand the internal structure of the baseboard management controller. It can interact with the electronic device based on the unified network address and obtain the management request sent by the electronic device. By summarizing the hardware information of the target server hardware system obtained from the container and feeding it back to the electronic device based on the unified network address, the occupation of network address resources can be reduced and network address resources can be saved.

[0013] In a possible implementation manner of the first aspect, the baseboard management controller is configured with an independent network address corresponding to each container one by one; and the baseboard management controller receives a management request sent by the electronic device, including:

[0014] The baseboard management controller receives a management request sent by the electronic device based on an independent network address; the baseboard management controller obtains hardware information of the target server hardware system, including: the baseboard management controller calls a container corresponding to the independent network address used to receive the management request to obtain the hardware information.

[0015] In the above manner, based on the configured independent network address corresponding to the container one by one, the interaction with the electronic device can improve the data interaction efficiency.

[0016] In a possible implementation manner of the first aspect, the method further includes:

[0017] The baseboard management controller periodically obtains hardware information through the container, and issues hardware fault alarm information when the hardware information meets the fault condition.

[0018] Through the above method, by periodically obtaining the server's hardware information and timely feeding back the server's hardware operating status, the server hardware system is monitored and warned in real time, thereby improving the server's system stability.

[0019] In the second aspect, the present application provides a baseboard management controller, which includes: an interface layer, an application layer, and a hardware control layer. The interface layer is connected to the application layer, and the application layer is connected to the hardware control layer. The interface layer is used to interact with electronic devices, and the hardware control layer is used to connect to one or more server hardware systems. One or more containers are deployed in the application layer, and the containers correspond to the server hardware systems. Each container includes an application for obtaining hardware information of the corresponding server hardware system.

[0020] In a possible implementation of the second aspect, the interface layer is configured with a unified network address for interacting with the electronic device, and the interface layer is used to receive a management request based on the unified network address, and based on the target server hardware system targeted by the management request, transmit the management request to a container corresponding to the target server hardware system.

[0021] In a possible implementation manner of the second aspect, the interface layer is further used to receive hardware information collected and transmitted by an operating system of the baseboard management controller, and send the hardware information to the electronic device based on a unified network address.

[0022] In a possible implementation of the second aspect, the interface layer corresponds to the container of the application layer one by one; each interface layer corresponding to each container is configured with an independent network address; each interface layer is used to receive a management request based on the independent network address and send a management request to the corresponding container.

[0023] In a third aspect, the present application provides a server, comprising: one or more server hardware systems and a baseboard management controller; the one or more server hardware systems are respectively connected to the baseboard management controller, and the baseboard management controller is used to execute the server management method described in the first aspect.

[0024] In a fourth aspect, the present application provides a server, comprising: one or more server hardware systems, and a baseboard management controller as described in the second aspect; the one or more server hardware systems are respectively connected to the baseboard management controller.

[0025] In a fifth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any one of the methods described in the first aspect.

[0026] In a sixth aspect, the present application provides a computer program product, which, when executed on a device, enables the device to execute any of the methods described in the first aspect.

[0027] It can be understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 A schematic diagram of the system architecture of a server provided in an embodiment of the present application;

[0030] Figure 2 A schematic diagram of a container deployment architecture provided for an embodiment of the present application;

[0031] Figure 3 Another schematic diagram of the system architecture of the server provided in the embodiment of the present application;

[0032] Figure 4 A schematic diagram of the implementation flow of the server management method provided in the embodiment of the present application;

[0033] Figure 5 A schematic diagram of a system architecture for configuring a unified network address provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of interaction with an electronic device based on a unified network address provided in an embodiment of the present application;

[0035] Figure 7 A schematic diagram of a system architecture for configuring an independent network address provided in an embodiment of the present application;

[0036] Figure 8A schematic diagram of interaction with an electronic device based on an independent network address provided in an embodiment of the present application;

[0037] Fig. 9 The server provided in the embodiment of the present application. DETAILED DESCRIPTION

[0038] The following embodiments of the technical solution of the present application are described in detail in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.

[0039] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by technicians in the technical field to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned figure descriptions and any variations thereof are intended to cover non-exclusive inclusions.

[0040] In the description of the embodiments of the present application, the technical terms "first", "second", etc. are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance or implicitly indicating the number, specific order or primary and secondary relationship of the indicated technical features. In the description of the embodiments of the present application, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

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

[0042] In the description of the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0043] To facilitate understanding of the technical solutions of the embodiments of the present application, the terms involved in this document are explained below.

[0044] The Baseboard Management Controller (BMC) is a dedicated controller used to monitor and manage computing devices (such as servers) and is a small operating system. BMC consists of two parts: BMC hardware (such as BMC chip or BMC hardware system) and BMC software. BMC software includes user-state software and system-state software (also called the base software of the operating system). Among them, user-state software, that is, the business software of the BMC application layer, may include: applications (Application, APP) of various feature functions of BMC and related dependencies required for the operation of each APP, wherein the related dependencies include, for example, library files, software frameworks and system operating environments on which each APP depends for operation; system-state software may include kernel-state system components such as the operating system (Operating System, OS) and the boot loader (u-boot).

[0045] It should be noted that different computing devices have different names for BMC, for example, some computing devices are called BMC, some computing devices are called iLO (Integrated lights-out), and some computing devices are called Integrated Dell Remote Access Controller (iDRAC). Regardless of whether it is called BMC, iLO or iDRAC, it can be understood as the baseboard management controller in the embodiment of the present invention.

[0046] Containers are a virtualization technology used to encapsulate applications and their dependencies or configurations so that they can run in different computer environments. The deployment of containers can be performed through a container engine (such as the isula container engine), and an application (such as an application layer APP) with a baseboard management controller is deployed in the container. Containerized deployment can mirror the application code during the deployment process, reducing the difficulty of modifying the application layer code.

[0047] The file system refers to a collection of files and software that operates and manages files and related data structures, and is a subsystem in the operating system responsible for managing persistent data. In the embodiment of the present application, each container deployed also has a file system of each container embedded in it.

[0048] The number of processor cores refers to the number of independent processing units contained in a single processor in a computing system. The independent processing unit, namely the core, can independently execute instructions and process data, and each core can execute instructions in parallel.

[0049] The embodiment of the present application provides a baseboard management controller, which deploys the application layer of BMC software in a containerized manner, so that multiple application layers deployed based on containers share a hardware control layer, and each application layer corresponds to a server hardware system one-to-one, and the hardware control layer is connected to one or more server hardware systems, so that the baseboard management controller can monitor and manage multiple server hardware systems based on a set of software and hardware, improve system resource utilization, and reduce the cost of configuring and implementing the baseboard management controller; and deploy multiple application layers based on containerization technology, encapsulate the application layer corresponding to each server system in a container, without modifying the software code of the application layer, shortening the application layer deployment cycle, and reducing the software modification cost.

[0050] The baseboard management controller provided in the embodiment of the present application can be applied to a server or other computing devices (including computing devices monitored and managed by the baseboard management controller or other computing devices that can communicate with the baseboard management controller). The following is explained using the baseboard management controller applied to a server as an example. The implementation principle of the baseboard management controller applied to other computing devices is similar to the implementation principle of the baseboard management controller applied to a server. For details, please refer to the implementation scenario of the baseboard management controller applied to a server.

[0051] A server management method, a baseboard management controller, and a system architecture of a server provided in an embodiment of the present application are introduced below in conjunction with the accompanying drawings.

[0052] The baseboard management controller provided in the embodiment of the present application can be applied to a server, which may include one or more server hardware systems. The baseboard management controller can communicate with one or more server hardware systems to monitor and manage the hardware status of each server hardware system.

[0053] See also Figure 1 , a schematic diagram of the system architecture of a server provided in an embodiment of the present application, wherein the server may be a multi-processor server or a server including multiple server hardware systems, etc. Figure 1 As shown, the server may include a baseboard management controller (BMC) 10 and one or more server hardware systems 20 , and the baseboard management controller is communicatively connected with the one or more server hardware systems 20 .

[0054] The baseboard management controller 10 includes BMC software 101 and BMC hardware 102 (also referred to as a hardware control layer or a BMC hardware system). The BMC software 101 may include an interface layer 1011 and an application layer 1012. The interface layer 1011 is connected to the application layer 1012, and the application layer 1012 is connected to the hardware control layer. The interface layer 1011 is used to interact with electronic devices; the hardware control layer is used to connect to one or more server hardware systems; the hardware control layer is connected to one or more server hardware systems 20.

[0055] like Figure 1 As shown, one or more containers (such as N containers, N is an integer greater than or equal to 1) are deployed in the application layer 1012, and the application layer 1012 of the baseboard management controller 10 deploys applications based on containerization technology; the container corresponds to the server hardware system; each container includes an application for obtaining hardware information of the corresponding server hardware system, such as heat dissipation management, power on and off management, and power management applications.

[0056] Exemplarily, the baseboard management controller 10 deploys the application of the application layer 1012 based on the containerization technology. The implementation principle is to introduce a container mechanism in the BMC operating system running on the BMC hardware 102, and smoothly copy the application with server management function in the BMC software 101 based on the container mechanism, deploy it in each container, and share the underlying driver; wherein the driver is the underlying software for the interaction between the application layer 1012 and the BMC hardware 102, such as a device driver, etc., which is responsible for converting the management request of the application layer 1012 into hardware operations, and passing the status and data of the server hardware obtained based on the hardware operation to the application layer 1012.

[0057] Among them, container platform engines such as docker and isula can be introduced into the BMC operating system. The engine supports the integration and startup of containers, and supports running applications of the application layer 1012 (such as various applications such as user management) in containers. Applications in multiple containers can reuse drivers that interact with the BMC hardware 102.

[0058] Exemplarily, the process of smoothly copying the application program of the application layer 1012 may be a process of mirroring the logic code of the application program, such as Figure 1 As shown in the figure, the logic code of the application is copied N times, and one copy is deployed in each container; for the system architecture of multi-processor servers, the BMC software can be deployed quickly, reducing the complexity and cost of program code modification.

[0059] In some embodiments, Figure 1The container shown is deployed based on the isula container engine; the operating system of the baseboard management controller is configured with a function of configuring more than two containers based on the isula container engine.

[0060] like Figure 2 As shown, a containerized platform engine, such as the isula container engine, is introduced into the operating system of the baseboard management controller, and a containerized BMC control software is configured in the operating system. The software entity (binary file) corresponding to the containerized BMC control software is located in the root file system of the operating system; the containerized BMC control software is used to execute container operations to achieve container management; wherein the executed container operations include: starting the container, initializing the container image file, closing the container, etc.

[0061] For example, Figure 2 As shown, the containerized BMC control software implements container operations by calling the open source isula container engine, such as scheduling containers (such as container 1 and container 2), image file management, etc. The containerized BMC control software also controls the container's access to the baseboard management controller (host) resources, such as access to the baseboard management controller's network card, device interface, etc.

[0062] In some embodiments, the application layer of the baseboard management controller is configured with an independent file system, such as the BMC root file system Rootfs; the file system includes dynamic libraries that the applications in the container (such as APP1, APP2) depend on and a basic tool command set of the Linux system.

[0063] like Figure 2 As shown, the containerized BMC control software is also responsible for managing the container image root file system, which includes all the contents of the BMC root file system of the BMC container, such as all files and directories required for the baseboard management controller to run.

[0064] Exemplarily, when the baseboard management controller runs an application in a container, the BMC root file system of the container is loaded from the container image file system, and the image file system occupies a certain storage space in the file system of the BMC; the operating system of the baseboard management controller mounts the image file system to the target directory (i.e., the mount point) so that the container process can access the files therein.

[0065] When the baseboard management controller runs the container, the root file system of the container is mounted from an image file or directory of the baseboard management controller. For example, when the baseboard management controller is running, the image file of the container is loaded from the specified location and the image file or directory is mounted to the preset mount point. The image file contains all the contents of the BMC root file system of the container.

[0066] like Figure 2As shown, each container is embedded with a BMC root file system, and each container can run independently of each other; and the file system of each container is separated from the file system of the baseboard management controller, reducing the dependency or conflict between the application in the container and other software, and ensuring that the application in the container can obtain sufficient resource support during operation, thereby improving the independence and stability of the application layer; at the same time, the independent file system is easy to deploy and migrate in different containers, reducing the deployment cost.

[0067] Correspondingly, the above-mentioned container platform engine can also be an open source Docker container engine, etc. The specific choice can be determined based on the actual application scenario.

[0068] For example, Figure 1 As shown, the BMC software 101 of the baseboard management controller also includes a data layer 1013 , a software development kit (SDK) 1014 , an operating system 1015 , and a boot loader (Uboot) 1016 .

[0069] In some embodiments, in order to simplify the deployment process and improve application performance, the baseboard management controller can also encapsulate the data layer 1013 in a container corresponding to the application program of the application layer; that is, deploy more than two data layers 1013 based on containerization technology, and the data layer corresponds to the application layer one by one, and deploy the corresponding data layer 1013 and application layer 1012 in the same container. Figure 3 The application layer 1012 and the data layer 1013 are deployed in the containers 1 to N shown.

[0070] The data layer 1013 is provided with the configuration of the application layer 1012, i.e., instructions for how the application programs of the application layer 1012 use and access data, such as database connection information, environment settings, application parameters, etc. The configuration content of the data layer 1013 can be stored in a configuration file or an environment variable, and can be loaded when the application layer 1012 is started or running.

[0071] In the embodiment of the present application, the code logic of the application layer 1012 is separated from the data layer 1013, so as to facilitate the deployment of the application layer based on the containerization technology. For the architecture of multi-processor servers, there is no need to modify the application code itself for each server hardware system. Encapsulating the application layer 1012 and the data layer 1013 in a container can reduce the configuration complexity during the deployment process, reduce the communication delay between the application layer 1012 and the data layer 1013, and reduce the communication overhead.

[0072] It should be noted that when the application layer 1012 is deployed based on containerization technology, the logic code of the application program of the application layer 1012 can be copied and deployed in each container; and the data layer 1013 in each container needs to adjust the configuration content for different server hardware systems 20 to adapt to the operating environment of each server hardware system 20.

[0073] Exemplarily, the data layer 1013 can also be deployed outside the container and include the configuration content corresponding to each server hardware system 20; the SDK 1014 can also be deployed in each corresponding container based on the corresponding relationship with each server hardware system 20. Based on the deployment method of containerization technology, the application layer 1012, the data layer 1013 and the SDK 1014 can be deployed accordingly based on the actual application scenario, which is not specifically limited here.

[0074] Exemplarily, each container application and BMC hardware 102 correspond to manage a server hardware system 20, such as Figure 1 As shown, each server hardware system may include components such as a graphics card, a fan, an operating system OS, etc. Among them, each server hardware system in the server refers to a device including a processor, such as a single-channel server. In addition, in addition to the processor, the server hardware system also includes a south bridge, a complex programmable logic device (CPLD) or a power supply module Power Supply Unit (PSU) in the same device as the processor.

[0075] It should be noted that Figure 3 The application layer shown in Figure 1 The above applications included in the container and the components included in the server hardware system 20 are only exemplary, and can be configured according to actual application scenarios, and the specific contents included are not limited.

[0076] Based on the system architecture of the above server, the implementation process of the baseboard management controller managing the server is further introduced below through embodiments.

[0077] See also Figure 4 , Figure 4 The implementation flow diagram of the server management method provided in the embodiment of the present application is as follows. The execution subject of the method can be Figure 1 The baseboard management controller 10 shown in FIG. 1 is connected to one or more server hardware systems 20 in the server in communication. Figure 4 As shown, the method may include the following steps:

[0078] S201: A baseboard management controller receives a management request sent by an electronic device.

[0079] In the embodiment of the present application, the management request is used to query the hardware information of the target server hardware system in the server. Figure 1 As shown, one or more containers are running in the baseboard management controller, each container corresponds to a server hardware system, and each container includes an application for obtaining hardware information of the corresponding server hardware system. The electronic device can be an external device or a client.

[0080] Exemplarily, the baseboard management controller includes an interface layer, and the baseboard management controller can receive management requests based on an interface application of the interface layer. Figure 1 As shown, the interface layer of the baseboard management controller can include interface applications of multiple interface protocols, such as the World Wide Web WEB communication protocol, the modern server management protocol Redfish based on RESTful API, the command line interface (Command-Line Interface, CLI) interface, the open source standard interface for managing computer systems and monitoring their operating status (Simple Network Management Protocol, SNMP), the open source standard interface for managing computer systems and monitoring their operating status (Intelligent Platform Management Interface, IPMI), as well as the keyboard, display and mouse interface (Keyboard Video Mouse, KVM), the virtual machine manager interface (Virtual Machine Monitor, VMM), etc.

[0081] Exemplarily, the operating system of the baseboard controller configures the interface (such as Ethernet Eth interface) at the interface layer through the web interface or command line interface (CLI) of the interface layer, including the configuration of the physical parameters (such as rate, duplex mode, etc.) and logical parameters (i.e., network address, such as IP address, gateway, etc.) of the interface. Among them, the IP address is used by the electronic device to access the BMC software of the baseboard management controller, such as the baseboard management controller receives the management request sent by the electronic device based on the interface application of the interface layer, and sends the received management request to the corresponding container to run the application in the container according to the management request.

[0082] S202: The baseboard management controller obtains hardware information of the target server hardware system and sends the information to the electronic device.

[0083] In an embodiment of the present application, each container of the baseboard management controller includes an application for obtaining hardware information of a corresponding server hardware system; the baseboard management controller runs the application in the container according to the management request, calls the hardware control layer based on the application to obtain the hardware information of the corresponding target server hardware system, and feeds back the hardware information to the electronic device.

[0084] Exemplarily, the baseboard management controller stores the correspondence between the server hardware system and the container; the management request may carry the network address of the interface layer and the identifier of the target server hardware system to be accessed. After receiving the management request, the interface application of the interface layer determines the target container based on the identifier of the server hardware system in the management request and the aforementioned correspondence, and sends the management request to the target container. The operating system of the baseboard management controller runs the application in the target container according to the management request; in the process of running the application, the management request is converted into a hardware operation by calling the hardware control layer, and the hardware information of the target server hardware system connected to it is read by the hardware control layer; the operating system of the baseboard management controller feeds back the acquired hardware information to the electronic device through the interface layer.

[0085] The hardware information fed back by the baseboard management controller to the electronic device may include an identifier of the target server hardware system.

[0086] In some embodiments, the baseboard management controller is configured with a unified network address for communicating with the electronic device; the baseboard management controller receives a management request sent by the electronic device, including: the baseboard management controller receives the management request sent by the electronic device based on the unified network address; the baseboard management controller obtains hardware information of the target server hardware system, including: the baseboard management controller obtains hardware information from a corresponding container based on the target server hardware system targeted by the management request.

[0087] For example, Figure 5 As shown, the baseboard management controller is configured with an interface layer for communicating with the electronic device, and the interface layer is configured with a unified network address for interacting with the electronic device; the interface layer is used to receive a management request sent by the electronic device based on the unified network address, and based on the target server hardware system targeted by the management request, transmit the management request to the container corresponding to the target server hardware system.

[0088] The unified network address may be an Internet Protocol (IP) address.

[0089] Exemplarily, the baseboard management controller stores the correspondence between the server hardware system and the container; the interface layer can receive multiple management requests sent by the electronic device for different server hardware systems, and each management request can include the identifier of the target server hardware system; after receiving multiple management requests based on the unified network address, the interface layer determines the target container identifier according to the identifier of the target server hardware system in each management request and the aforementioned correspondence, and sends the management request to the target container according to the target container identifier; the operating system of the baseboard management controller calls the hardware control layer based on the application in the target container to read the hardware information of the server hardware system.

[0090] Accordingly, after reading the hardware information, the hardware control layer can feed back to the application in the target container through the operating system. The operating system of the baseboard management controller obtains the hardware information of the target server hardware system from each corresponding target container by running the application in the target container.

[0091] In some embodiments, the baseboard management controller obtains hardware information of the target server hardware system and sends it to the electronic device, including: the baseboard management controller summarizes the obtained hardware information of the target server hardware system based on a unified network address and sends it to the electronic device.

[0092] Exemplarily, after reading the hardware information of the server hardware system, the hardware control layer of the baseboard management controller transmits the hardware information to the application in the container of the baseboard management controller; the operating system of the baseboard management controller obtains the hardware information from each target container, and aggregates and processes the hardware information of each target server hardware system; the operating system feeds back the aggregated hardware information to the interface application of the interface layer; after receiving the hardware information, the interface application of the interface layer sends the hardware information to the electronic device based on a unified network address.

[0093] In order to more clearly describe the interaction process between the baseboard management controller and the electronic device based on the unified network address, Figure 6 FIG. 1 shows a schematic diagram of interaction with an electronic device based on a unified network address provided by an embodiment of the present application. Figure 6 As shown, the interface layer of the baseboard management controller receives the management request sent by the electronic device based on the unified network address, and based on the target server hardware system targeted by the management request, transmits the management request to the container corresponding to the target server hardware system, and receives the hardware information collected and transmitted by the operating system of the baseboard management controller, and sends the hardware information to the electronic device based on the unified network address; based on the same implementation principle as the aforementioned embodiment, it will not be repeated here; the interaction process may include:

[0094] Step 61: An interface application of a baseboard management controller interface layer receives a management request sent by an electronic device based on a unified network address.

[0095] In step 621, the interface application determines the corresponding target container, such as container 1-application, based on the identifier of the server hardware system in the management request, and sends a first management request to container 1-application; wherein the management request in step 61 includes the first management request.

[0096] In step 622, the interface application determines the corresponding target container, such as container 2-application, based on the identifier of the server hardware system in the management request, and sends a second management request to container 2-application; wherein the management request in step 61 includes the second management request.

[0097] Among them, the baseboard management controller reads the hardware information of the target server hardware system by running the container application and calling the hardware control layer; for example, the operating system of the baseboard management controller calls the hardware control layer based on container 1-application to read the first hardware information of the first server hardware system, and calls the hardware control layer based on container 2-application to read the second hardware information of the second server hardware system; the hardware control layer feeds back the read first hardware information and second hardware information to container 1 and container 2 respectively.

[0098] Step 631 : The operating system of the baseboard management controller obtains first hardware information from container 1 .

[0099] Step 632 : The operating system of the baseboard management controller obtains second hardware information from container 2 .

[0100] Step 64 : The operating system of the baseboard management controller aggregates the first hardware information and the second hardware information, and feeds back the aggregated hardware information to the interface application of the interface layer, where the hardware information includes the first hardware information and the second hardware information.

[0101] Container 1 and container 2 may send the first hardware information and the second hardware information to the operating system of the baseboard management controller based on the shared volume technology.

[0102] Exemplarily, a shared volume may be a storage area shared between multiple containers, storing data that needs to be shared between the containers. The operating system of the baseboard management controller may configure and manage the shared volume through the container engine. For example, when an application in a container needs to pass data to the operating system of the baseboard management controller, the data may be written to the shared volume, and the application in the operating system of the baseboard management controller may read the data in the shared volume, thereby realizing data transfer from the container to the operating system of the baseboard management controller.

[0103] Step 65: The interface application of the interface layer sends hardware information to the electronic device based on the unified network address.

[0104] Through the above method, interaction with electronic devices is achieved based on a unified network address, management requests sent by electronic devices for different target server hardware systems are received, management requests sent by electronic devices are aggregated and processed based on applications in different containers, and applications in multiple containers share one network address. Aggregated hardware information is fed back to the electronic devices based on the unified network address, thereby reducing the occupancy of network address resources and saving network address resources.

[0105] In some embodiments, the baseboard management controller is configured with an independent network address corresponding one-to-one to the container; the baseboard management controller receives a management request sent by the electronic device, including: the baseboard management controller receives the management request sent by the electronic device based on the independent network address; the baseboard management controller obtains hardware information of the target server hardware system, including: the baseboard management controller calls the container corresponding to the independent network address to obtain hardware information based on the independent network address used to receive the management request.

[0106] For example, Figure 7 As shown, the baseboard management controller is configured with an interface layer for communicating with the electronic device; the interface layer corresponds one-to-one to the container of the application layer; each interface layer corresponding to each container is configured with an independent network address; each interface layer is used to receive a management request based on the independent network address and send a management request to the corresponding container.

[0107] The independent network address may be an Internet Protocol (IP) address, and different interface layers may correspond to different independent network addresses, such as different Internet Protocol addresses may correspond to different interface layers.

[0108] Exemplarily, the interface layer corresponding to each container in the baseboard management controller receives the management request sent by the electronic device based on the corresponding independent network address; each management request may include the identification of the target server hardware system and the independent network address of the interface layer; after each interface layer receives the management request based on the independent network address, it sends the management request to the corresponding target container respectively; based on the application program in each target container, the management request is sent to the baseboard management controller, and the baseboard management controller calls the hardware control layer based on the management request to read the hardware information corresponding to each target server hardware system.

[0109] Accordingly, after reading the hardware information, the hardware control layer can feed back to the operating system of the baseboard management controller. The operating system transmits the hardware information to the application in the target container. Each container sends the hardware information to the interface application of the corresponding interface layer; the interface application of the interface layer sends the hardware information to the electronic device based on the independent network address.

[0110] In order to more clearly describe the interaction process between the baseboard management controller and the electronic device based on the independent network address, Figure 8 FIG. 1 shows a schematic diagram of interaction with an electronic device based on an independent network address provided by an embodiment of the present application. Figure 8 As shown, the interface layer of the baseboard management controller receives a management request sent by the electronic device based on an independent network address, and transmits the management request to the corresponding container based on the target server hardware system and the independent network address targeted by the management request, and receives the hardware information transmitted by the corresponding container, and sends the hardware information to the electronic device based on the independent network address; based on the same implementation principle as the aforementioned embodiment, it will not be repeated here; the interaction process may include:

[0111] For container 1:

[0112] Step 811: An interface application of a baseboard management controller interface layer receives a first management request sent by an electronic device based on an independent network address.

[0113] Step 812: The interface application of the interface layer sends the first management request to the container corresponding to the interface layer based on the independent network address or the identifier of the target server hardware system in the first management request, such as sending the first management request to container 1-application.

[0114] Among them, the baseboard management controller reads the hardware information of the target server hardware system by running the container's application and calling the hardware control layer; for example, the operating system of the baseboard management controller calls the hardware control layer based on container 1-application to read the first hardware information of the first server hardware system; the operating system feeds back the first hardware information read by the hardware control layer to container 1.

[0115] Step 813: After acquiring the first hardware information, the application in the container sends the first hardware information to the interface application of the interface layer.

[0116] Step 814: The interface application of the interface layer sends the first hardware information to the electronic device based on the independent network interface.

[0117] For container 2:

[0118] Step 821: The interface application of the baseboard management controller interface layer receives a second management request sent by the electronic device based on the independent network address.

[0119] Step 822: The interface application of the interface layer sends the second management request to the container corresponding to the interface layer based on the independent network address or the identifier of the target server hardware system in the second management request, such as sending the second management request to container 2-application.

[0120] Among them, the baseboard management controller reads the hardware information of the target server hardware system by running the container's application and calling the hardware control layer; for example, the operating system of the baseboard management controller calls the hardware control layer based on container 2-application to read the second hardware information of the second server hardware system; the operating system feeds back the second hardware information read by the hardware control layer to container 2.

[0121] Step 823: After acquiring the second hardware information, the application in the container sends the second hardware information to the interface application of the interface layer.

[0122] Step 824: The interface application of the interface layer sends the second hardware information to the electronic device based on the independent network interface.

[0123] The embodiment of the present application deploys application layer applications based on containerization technology to achieve low-cost transformation of the overall BMC software, which can meet the management of multi-processor servers by single BMC hardware and BMC software, and reduce software implementation costs based on optimal hardware costs.

[0124] In some embodiments, the method further comprises:

[0125] The baseboard management controller periodically obtains hardware information through the container, and issues hardware fault alarm information when the hardware information meets the fault condition.

[0126] Exemplarily, the baseboard management controller periodically checks the hardware information of the server through an application deployed based on a container, and issues a hardware failure alarm message when the hardware information does not meet the qualified indicator threshold, promptly reminding the user to maintain the server hardware, thereby improving the timeliness and flexibility of server management, and improving the system stability of the server.

[0127] The present application embodiment also provides a server 90, such as Fig. 9 As shown, the server 90 includes one or more server hardware systems (such as server hardware system 201 and server hardware system 202) and a baseboard management controller 10; one or more server hardware systems are respectively connected to the baseboard management controller 10, and the baseboard management controller 10 can be connected to the server 90 or integrated in the server 90.

[0128] The baseboard management controller 10 includes: at least one processor and a memory, wherein the memory stores a computer program that can be run on the processor. When the processor executes the computer program, the steps in the above-mentioned server management method embodiment are implemented, such as Figure 4 Alternatively, the processor implements the functions of each module / unit in the above-mentioned device embodiments when executing the computer program.

[0129] It should be noted that the above-mentioned server structure is only illustrative, and may include other entity structures based on different application scenarios, and the entity structure of the server is not limited here.

[0130] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0131] An embodiment of the present application also provides a chip system, which is applied to a baseboard management controller. The chip system includes one or more processors, and the one or more processors are used to call computer instructions so that the baseboard management controller implements the steps in the above-mentioned method embodiments.

[0132] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0133] An embodiment of the present application provides a computer program product. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0134] The chip system, substrate management controller, computer storage medium, and computer program product provided in the above-mentioned embodiments of the present application are all used to execute the methods provided above. Therefore, the beneficial effects that can be achieved can refer to the corresponding beneficial effects of the methods provided above, and will not be repeated here.

[0135] The server provided in the above-mentioned embodiment of the present application is implemented based on the baseboard management controller provided above. Therefore, the beneficial effects that can be achieved can refer to the corresponding beneficial effects of the baseboard management controller provided above, which will not be repeated here.

[0136] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, rather than to limit the scope of the embodiments of the present application. Those skilled in the art can obviously make various equivalent modifications or changes based on the above examples given. Or a combination of any two or any multiple embodiments of the above. Such modifications, changes or combined solutions also fall within the scope of the embodiments of the present application.

[0137] It should also be understood that the division of the methods, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various methods, categories, situations and embodiments can be combined without contradiction.

[0138] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0139] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0140] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

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

[0142] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

[0143] Finally, it should be noted that the above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A server management method, characterized in that: Applied to a baseboard management controller, the baseboard management controller is communicatively connected with one or more server hardware systems, the method comprises: The baseboard management controller receives a management request sent by an electronic device, wherein the management request is used to query hardware information of a target server hardware system, wherein one or more containers are running in the baseboard management controller, the containers correspond to the server hardware systems, and each of the containers includes an application for obtaining hardware information of the corresponding server hardware system; The baseboard management controller obtains the hardware information of the target server hardware system and sends it to the electronic device. The hardware information of the target server hardware system is obtained by the corresponding application of the container.

2. The method according to claim 1, characterized in that: The baseboard management controller is configured with a unified network address for communicating with the electronic device; The baseboard management controller receives a management request sent by an electronic device, including: The baseboard management controller receives a management request sent by the electronic device based on the unified network address; The baseboard management controller obtains hardware information of the target server hardware system, including: The baseboard management controller obtains the hardware information from a corresponding container based on a target server hardware system targeted by the management request.

3. The method according to claim 2, characterized in that The baseboard management controller obtains the hardware information of the target server hardware system and sends it to the electronic device, including: The baseboard management controller summarizes the acquired hardware information of the target server hardware system based on the unified network address and sends the information to the electronic device.

4. The method according to claim 1, characterized in that: The baseboard management controller is configured with an independent network address corresponding one-to-one to the container; The baseboard management controller receives a management request sent by an electronic device, including: The baseboard management controller receives a management request sent by the electronic device based on the independent network address; The baseboard management controller obtains hardware information of the target server hardware system, including: The baseboard management controller acquires the hardware information by calling a container corresponding to the independent network address used to receive the management request.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The baseboard management controller periodically obtains the hardware information through the container, and issues hardware failure alarm information when the hardware information meets a failure condition.

6. A baseboard management controller, characterized in that: The baseboard management controller includes: an interface layer, an application layer, and a hardware control layer. The interface layer is connected to the application layer, and the application layer is connected to the hardware control layer. The interface layer is used to interact with electronic devices, and the hardware control layer is used to connect to one or more server hardware systems. One or more containers are deployed in the application layer, and the containers correspond to the server hardware systems. Each of the containers includes an application program for obtaining hardware information of the corresponding server hardware system.

7. The baseboard management controller according to claim 6, characterized in that: The interface layer is configured with a unified network address for interacting with the electronic device. The interface layer is used to receive the management request based on the unified network address, and based on the target server hardware system targeted by the management request, transmit the management request to a container corresponding to the target server hardware system.

8. The baseboard management controller according to claim 7, characterized in that: The interface layer is also used to receive the hardware information collected and transmitted by the operating system of the baseboard management controller, and send the hardware information to the electronic device based on the unified network address.

9. The baseboard management controller according to claim 6, characterized in that: The interface layer corresponds to the container of the application layer one by one; each interface layer corresponding to each container is configured with an independent network address; each interface layer is used to receive the management request based on the independent network address and send the management request to the corresponding container.

10. A server, characterized in that: include: One or more server hardware systems and a baseboard management controller; the one or more server hardware systems are respectively connected to the baseboard management controller, and the baseboard management controller is used to execute the server management method according to any one of claims 1 to 5.

11. A server, characterized in that: include: One or more server hardware systems, and a baseboard management controller as claimed in any one of claims 6 to 9; The one or more server hardware systems are respectively connected to the baseboard management controller.

Images