A device management method and a management server

Abstract

The application discloses a device management method and a management server. The method is applied to a device management system, the device management system comprises a management server and at least one service server, a preset model library of the management server comprises at least one sub-model, each sub-model comprises configuration items and configuration parameters of components, and the method comprises the following steps: the management server acquires component identifiers of components in each service server, and determines a first sub-model set in the preset model library according to the component identifiers of the first service server, wherein the first sub-model set comprises at least one sub-model corresponding to the component identifiers of the first service server; the first configuration information is sent to the first service server, the first configuration information carries at least one configuration item and configuration parameter in the first sub-model set, so that the first service server configures the configuration parameters of the configuration items of at least one to-be-configured component according to the first configuration information.

Description

[0001] This application is a divisional application. The original application has the application number 201810506587.1 and the original application date is May 24, 2018. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of server technology, and in particular to a device management method and a server management system. Background Technology

[0003] In operational scenarios such as deploying new service servers, adding new service servers, and changing service server components, maintenance personnel need to configure the parameters of service server components. Components may include devices or firmware such as redundant arrays of independent disks (RAID), Basic Input Output System (BIOS), and network interface cards (NICs). For example, configuring RAID parameters may involve configuring the RAID level or other configuration items to enable the RAID to perform its corresponding functions.

[0004] In practical applications, such as Figure 1 As shown, management software on the management server typically configures the parameters of components on the business server. For example, business server 1 includes a RAID card of model LSI3108. When configuring business server 1, the management software always outputs configuration parameters for the attributes of the LSI3108 RAID card, such as the RAID level configuration parameters for RAID 0, RAID 1, and RAID 10. The user can select the configuration parameters. The management software sends the user-selected configuration parameter RAID 1 to business server 1. Business server 1 then configures the RAID level to RAID 1.

[0005] However, in many cases, updating the management software is necessary to configure the parameters of the business servers. For example, when a new business server 2 with different components is added to the system, the management software needs to be updated so that it can provide users with the corresponding configuration parameters output by business server 2 for parameter configuration. In other words, every time a new business server with different components is added to the system, the management software must be updated for parameter configuration.

[0006] It is evident that existing server operation and maintenance methods suffer from low maintenance efficiency. Summary of the Invention

[0007] This application provides a device management method and a management server, thereby improving the maintenance efficiency of server operation and maintenance and quickly configuring the parameters of business server components.

[0008] In a first aspect, this application provides a device management method applied in a device management system, the device management system including a management server and at least one business server, the business server including one or more components, the one or more components including hardware, firmware or software; the management server is used to manage at least one business server, the management server having a pre-set model library; the pre-set model library including at least one sub-model, each sub-model including configuration items and configuration parameters of the component, and the sub-models are reused by at least one business server; the method includes: the management server obtaining the component identifier of at least one component in each of the at least one business server; the management server determining a first sub-model set in the pre-set model library according to the component identifier of the first business server, the first business server being any one of the at least one business server, the first sub-model set including sub-models corresponding to each component identifier of the first business server; the management server sending first configuration information to the first business server, the first configuration information carrying at least one configuration item and configuration parameter in the first sub-model set, so that the first business server can configure the configuration parameters of the configuration item of at least one component to be configured according to the first configuration information.

[0009] As can be seen, by implementing the method described in the first aspect, when the components of the business server change, the latest configuration items and parameters of the business server can be dynamically obtained without updating the management software. This facilitates quick parameter configuration of the business server components and improves the maintenance efficiency of server operation and maintenance. Furthermore, different business servers may have some identical components. By implementing the method described in the first aspect, multiple business servers can reuse the same sub-model, thereby helping to save development costs.

[0010] As an optional implementation, when the pre-built model library does not contain a sub-model corresponding to the identifier of the first component, the management server obtains the configuration items and configuration parameters of the first component from the first business server. The first component can be any one of the components of the first business server. The management server adds a first sub-model to the pre-built model library based on the configuration items and configuration parameters of the first component. This first sub-model includes the configuration items and configuration parameters of the first component. By implementing this optional implementation, the sub-models in the pre-built model library can be expanded, making the sub-models in the pre-built model library more complete.

[0011] Optionally, if the pre-built model library does not contain a sub-model corresponding to the identifier of the first component (e.g., the identifier of the first component could be a CPU identifier or a motherboard identifier), which includes firmware configuration items and parameters, the management server obtains the firmware configuration items and parameters from the first service server. The management server then adds a first sub-model to the pre-built model library based on the firmware configuration items and parameters. This first sub-model includes the firmware configuration items and parameters. By implementing this optional implementation method, the sub-models in the pre-built model library can be expanded, making the sub-models in the pre-built model library more complete.

[0012] As an optional implementation, the management server obtains the identifier of a component in each of at least one business server as follows: The management server obtains the identifier of a component in each of at least one business server when it detects that at least one business server has been powered on; or, the management server periodically obtains the identifier of a component in each of at least one business server. By implementing this optional implementation, the latest component identifier of the business server can be determined in a timely manner, thereby determining the latest sub-model set corresponding to the business server in a timely manner.

[0013] Optionally, if the first service server is not powered on for the first time, after the management server obtains the identifier of the first service server's component, if the first service server's component is detected to have changed in this power-on compared to the first service server's component detected in the previous power-on, the management server determines the first sub-model set in the preset model library based on the first service server's component identifier.

[0014] Optionally, the management server periodically obtains the identifier of the component in each of at least one business server; when a change is detected in the component of the first business server in the current period compared to the component of the first business server detected in the previous period, the management server determines the first sub-model set in the preset model library based on the component identifier of the first business server.

[0015] As an optional implementation, the specific implementation of the management server determining the first sub-model set in the preset model library based on the component identifier of the first business server is as follows: the management server determines at least one second sub-model set in the preset model library that corresponds to at least one component category of the first business server, each second sub-model set including sub-models corresponding to components of the same category, the component category being used to indicate the component classification information to which the components of the first business server belong; the management server determines the first sub-model set from at least one second sub-model set based on at least one component identifier of the first business server.

[0016] By implementing this optional implementation method, a second sub-model set can be determined first based on the category of the component. The second sub-model set includes sub-models corresponding to components of the same category. Then, the sub-model corresponding to the component identifier is searched in the second sub-model set. This can narrow the search range for the sub-model corresponding to the component identifier, thereby enabling the sub-model corresponding to the component identifier to be found more quickly.

[0017] As an optional implementation, before sending the first configuration information to the first business server, the management server selects at least one configuration item and configuration parameter from the first sub-model set as the configuration items and configuration parameters included in the first configuration information.

[0018] By implementing this optional implementation, it is possible to flexibly select configuration items and configuration parameters from the first sub-model set for parameter configuration.

[0019] As an optional implementation, the sub-models in the first sub-model set also include preset display rules for configuration items and configuration parameters; before the management server selects at least one configuration item and configuration parameter in the first sub-model set as the configuration items and configuration parameters included in the first configuration information, it displays the configuration items and configuration parameters in the first sub-model set according to the preset display rules in the first sub-model set.

[0020] In practical applications, if the components of the business server change, or if the business server is newly added to the device management system, the management software needs to be updated to update the configuration items and parameters of the business server, as well as the display rules for these configuration items and parameters. By implementing this optional implementation method, the display rules for the configuration items and parameters are added to the sub-model. The management server can then dynamically obtain the display rules for the configuration items and parameters of the business server, thus eliminating the need to update the management software and facilitating quick parameter configuration of the business server's configuration items.

[0021] As an optional implementation, the sub-models of the first sub-model set also include dependent configuration items, dependent configuration items, and dependency conditions; wherein, the configuration parameters of the dependent configuration items and the dependent configuration items in the first sub-model set are displayed according to whether the current configuration parameters of the dependent configuration items meet the dependency conditions.

[0022] Setting dependencies improves user experience and prevents conflicting configuration items. Furthermore, by adding dependent configuration items, dependent configuration items, and dependency conditions to the sub-model, the management server can dynamically obtain these information from the business server, eliminating the need to update the management software and facilitating quick parameter configuration for the business server.

[0023] Optionally, after the management server sends the first configuration information to the first service server, the management server can generate a configuration file that includes the first configuration information. The management server saves this configuration file so that the next time a user wants to perform the same configuration, the user can enter a command to allow the management server to directly select the configuration file and configure the configuration items of at least one component to be configured using the configuration parameters in the configuration file.

[0024] As an optional implementation, after the step of the management server sending the first configuration information to the first service server, the method further includes: the management server generating a configuration file, the configuration file including the first configuration information; the management server saving the configuration file, the configuration file being available for use to configure components with the same parameter configuration requirements.

[0025] Optionally, after the management server sends the first configuration information to the first service server, the management server can generate a configuration file that includes the first configuration information. The management server saves this configuration file so that the next time a user wants to perform the same configuration, the user can enter a command to allow the management server to directly select the configuration file and configure the parameters of at least one component to be configured using the configuration parameters in the configuration file, thereby improving configuration efficiency.

[0026] As an optional implementation, the management server determines the first sub-model set in the preset model library based on the component identifier of the first business server, including: searching for the sub-model corresponding to each component identifier based on the first correspondence relationship; wherein, the first correspondence relationship is the correspondence between the component identifier and the sub-model including the configuration items and configuration parameters of the component; and determining the set of sub-models corresponding to all components to be configured as the first sub-model set.

[0027] Optionally, the correspondence between hardware identifiers and sub-models including configuration items and parameters of that hardware can be pre-defined. Similarly, the correspondence between firmware identifiers and sub-models including configuration items and parameters of that firmware can be pre-defined. The correspondence between software identifiers and sub-models including configuration items and parameters of that software can also be pre-defined.

[0028] As an optional implementation, the component identifier includes one or more of the following: component model number, component version number, or component name. The component identifier is used to indicate the component's identity information.

[0029] As an optional implementation, when the management server obtains that multiple business servers have components with the same component identifier and require the same parameter configuration, the management server determines a first sub-model set in a pre-set model library based on the identifiers of the components to be configured on the multiple business servers; the management server then sends first configuration information to the first business server, including: the management server sending the first configuration information to multiple business servers, causing the multiple business servers to configure the parameters of the components to be configured according to the first configuration information. This implementation enables batch configuration of components on multiple business servers, improving configuration efficiency.

[0030] Secondly, a management server is provided, which can execute the methods described in the first aspect or possible embodiments thereof. This function can be implemented in hardware or by executing corresponding software within hardware. The hardware or software includes one or more units corresponding to the described functions. These units can be software and / or hardware. Based on the same inventive concept, the principle of this management server in solving the problem and its beneficial effects can be found in the first aspect or possible embodiments thereof and their beneficial effects described above; repetitions will not be repeated.

[0031] Thirdly, a management server is provided, comprising: a processor, a memory, and a communication interface; the processor, the communication interface, and the memory are connected together. The communication interface is used to enable communication with a business server. One or more programs are stored in the memory, and the processor calls the programs stored in the memory to implement the solutions described in the first aspect or possible embodiments thereof. The implementation methods and beneficial effects of this management server in solving the problem can be found in the first aspect or possible embodiments thereof and their beneficial effects described above; repetitions will not be repeated.

[0032] Fourthly, a computer program product is provided that, when run on a computer, causes the computer to perform the methods described in the first aspect or possible embodiments thereof.

[0033] Fifthly, a chip product for managing servers is provided, which performs the method of the first aspect or the method in a possible implementation of the first aspect.

[0034] In a sixth aspect, a computer-readable storage medium is provided, which stores instructions that, when executed on a computer, cause the computer to perform the method of the first aspect or the method in a possible implementation of the first aspect. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of the structure of a device management system provided in an embodiment of this application;

[0036] Figure 2 This is a flowchart illustrating a device management method provided in an embodiment of this application;

[0037] Figure 3 This is a flowchart illustrating another device management method provided in an embodiment of this application;

[0038] Figure 4 This is a schematic diagram of an interface provided in an embodiment of this application;

[0039] Figure 5 This is another schematic diagram of the interface provided in the embodiment of this application;

[0040] Figure 6 This is a schematic diagram of the structure of a management server provided in an embodiment of this application;

[0041] Figure 7 This is a schematic diagram of another management server structure provided in an embodiment of this application. Detailed Implementation

[0042] The specific embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0043] This application provides a device management method and a management server, which facilitates quick parameter configuration of business server components.

[0044] To better understand the embodiments of this application, the communication system of the embodiments of this application will be described below.

[0045] Please see Figure 1 , Figure 1 This is a schematic diagram of a device management system provided in an embodiment of this application. Figure 1 As shown, the device management system includes a management server and at least one business server; that is, the device management system includes a management server and one or more business servers. Figure 1Taking a device management system comprising three business servers as an example. The management server manages each business server in the device management system. Each business server includes one or more components. These components can be hardware, firmware, or software. Hardware is short for computer hardware, referring to the collective term for various physical devices composed of electronic, mechanical, and optoelectronic components in a computer system. For example, this hardware can be a redundant array of independent disks (RAID) and a network interface card (NIC). Firmware refers to the program written to erasable read-only memory or electrically erasable programmable read-only memory. Firmware is the software that performs the most basic and lowest-level functions of a system. For example, firmware can include the basic input / output system (BIOS). Software can be an operating system, application software, etc.

[0046] The management server can configure the parameters of each business server component in the device management system to ensure that the business server meets business requirements. The management server can simultaneously configure parameters for multiple business servers with identical components in batches. For example, if business servers 1-3 have identical components, the management server can configure parameters for business servers 1-3 in batches. Alternatively, the management server can configure parameters for each business server individually; this is not limited in the embodiments of this application.

[0047] Each component has one or more configuration items that need to be configured, and each configuration item can correspond to one or more configuration parameters. The management server configures a configuration item through one of its configuration parameters. For example, as shown in Table 1 below, the RAID card in the business server has three configuration items: "RAID Controller ID", "RAID Level", and "Boot Disk". The two configuration parameters corresponding to "RAID Controller ID" are "RAIDStorage0" and "RAIDStorage1". The five configuration parameters corresponding to "RAID Level" are "RAID0", "RAID1", "RAID5", "RAID6", and "RAID10". The two configuration parameters corresponding to "Boot Disk" are "Yes" and "No". "Yes" indicates that the current RAID group will be used as the boot disk, and "No" indicates that the current RAID group will not be used as the boot disk. The management server can configure "RAID Controller ID" through "RAIDStorage0", configure "RAID Level" through "RAID0", and configure "Boot Disk" through "Yes".

[0048] Table 1

[0049] RAID controller ID RAIDStorage0, RAIDStorage1 RAID levels RAID0, RAID1, RAID5, RAID6, RAID10 boot disk whether

[0050] For example, as shown in Table 2, the BIOS in the business server has four configuration items: "System Boot Mode," "Energy Efficiency Mode," "VTd Support," and "InterruptRemap." The two configuration parameters for "System Boot Mode" are "Legacy Mode" and "UEFI Mode." The two configuration parameters for "Energy Efficiency Mode" are "Low Power" and "High Performance." The two configuration parameters for "VTd Support" are "Enabled" and "Disabled." The two configuration parameters for "InterruptRemap" are "Enabled" and "Disabled." The management server can configure "System Boot Mode" via "UEFI Mode," "Energy Efficiency Mode" via "Low Power," "VTd Support" via "Enabled," and "InterruptRemap" via "Enabled."

[0051] Table 2

[0052] System startup mode Legacy mode, UEFI mode Energy Efficiency Mode Low power consumption, high performance VTd support Enable, disable InterruptRemap Enable, disable

[0053] For example, the operating system can have a configuration item "Operating System Version," with configuration parameters such as "CentOS 7.3" or "CentOS 7.4." The current operating system version is "CentOS 7.2." The management server can configure the "Operating System Version" using "CentOS 7.4," meaning the management server will upgrade the operating system to CentOS 7.4.

[0054] For example, firmware can have a configuration item "Firmware Version", with configuration parameters such as "0.0.2" or "0.0.3". The current firmware version is "0.0.1". The management server can configure the "Firmware Version" using "0.0.3", meaning the management server will upgrade the firmware to version 0.0.3.

[0055] The following provides a detailed description of the device management method and management server provided in this application.

[0056] Please see Figure 2 , Figure 2 This is a flowchart illustrating a device management method provided in an embodiment of this application. Figure 2 As shown, the equipment management method includes the following steps 201-204, wherein:

[0057] 201. The management server obtains the component identifier of each component in at least one business server.

[0058] Specifically, the management server obtains component identifiers for one or more components of each business server in the device management system. For example, the management server obtains... Figure 1 The component identifier is one or more components of the business servers 1 to 3 shown. For example, the component can be hardware, firmware, and software. The hardware can be a RAID card, network card, CPU, motherboard (i.e., single board), etc., the firmware can be a BIOS, etc., and the software can be an operating system, etc.

[0059] Optionally, the management server can obtain component identifiers from each service server of the device management system via the baseboard management controller (BMC). Specifically, the management server can obtain identifiers of a specified type of component from the service server via the BMC, and the service server will return the identifiers of the specified type of component to the management server. For example, the management server can obtain the identifier of a RAID card from the service server via the BMC, and the service server will return the identifier of the RAID card.

[0060] The component identifier is used to indicate the component's identity information. Optionally, the component identifier can be information that identifies the component, such as the component model, component version number, or component name. For example, if the component is hardware, the component identifier can be the component model. For example, the RAID card model can be "LSI3108," "LSI3008," or "LSI2208." The network card model can be "MZ910" or "MZ920," etc. The CPU model can be "Intelxeon V3," "Intelxeon V5," etc. The motherboard model can be "CH121," "RH1288," etc. If the component is firmware or software, the component identifier can be the component version number. For example, the firmware version number can be 0.0.1, 0.0.2, etc. The operating system version number can be CentOS 7.2, CentOS 7.3, etc.

[0061] As an optional implementation, the management server obtains the identifier of a component in each of at least one business server as follows: when the management server detects that at least one business server has been powered on, it obtains the identifier of a component in each of the at least one business server. By implementing this optional implementation, the component identifiers of the business servers can be obtained in a timely manner, thereby determining the sub-model set of the business servers in advance. Subsequently, when it is necessary to configure the parameters of the components of the business servers, the management server can configure the configuration items of the components of the business servers according to the configuration items and configuration parameters in the sub-model set of the business servers.

[0062] Optionally, if the first service server is powering on for the first time, i.e., the first service server is a newly added service server to the device management system, after the management server obtains the component identifier of the first service server, it can directly execute step 202, i.e., determine the first sub-model set corresponding to the first service server. Here, the first service server is any one of at least one service server included in the device management system. For example, the first service server could be... Figure 1 Any one of the business servers 1 to 3 in the device management system shown.

[0063] Optionally, if the first service server is not powering on for the first time, after the management server obtains the identifiers of the components of the first service server, if the components of the first service server detected during this power-on change compared to the components detected during the previous power-on, step 202 is executed. For example, if the first service server is service server 1, and the management server detects that the components of service server 1 are a RAID card of model "LSI3108" and a network card of model "MZ910" during the first power-on, the management server executes step 202. If the management server detects that the components of service server 1 are still the RAID card of model "LSI3108" and the network card of model "MZ910" during the second power-on, that is, the components in service server 1 have not changed, then the management server ends this process. If, when business server 1 is powered on for the second time, the management server detects that the components of business server 1 are a RAID card with the model number "LSI2208" and a network card with the model number "MZ920", that is, the components in business server 1 have changed, then the management server executes step 202, that is, redetermines the first sub-model set of business server 1.

[0064] As an optional implementation, the management server obtains the identifiers of components in at least one business server as follows: the management server periodically obtains the identifiers of components in at least one business server. By implementing this optional implementation, the latest component identifiers of the business servers can be determined in a timely manner, thereby determining the latest sub-model set corresponding to the business server in a timely manner.

[0065] Optionally, after detecting that the first service server has been powered on, the management server may periodically obtain the identifier of a component in each of at least one service server. If the component of the first service server detected in the current cycle has changed compared to the component of the first service server detected in the previous cycle, step 202 is executed, that is, the first sub-model set of service server 1 is re-determined.

[0066] 202. The management server determines the first sub-model set in the preset model library based on the identifier of the component of the first business server.

[0067] The pre-built model library includes at least one sub-model, each containing configuration items and parameters for a component. For example, the pre-built model library may contain six sub-models, designated as sub-models 1 through 6. Sub-models 1 and 2 both include configuration items and parameters for a RAID card. Sub-models 3 and 4 both include configuration items and parameters for a network card. Sub-models 5 and 6 both include configuration items and parameters for a BIOS. The configuration items and parameters included in sub-models 1 and 2 are different. The configuration items and parameters included in sub-models 3 and 4 are different. The configuration items and parameters included in sub-models 5 and 6 are different. Optionally, the sub-model file format can be a tag-based file format, such as XML or JSON. Tag-based file formats are small in size, typically a few to tens of KB, which is beneficial for user downloads and easily expandable.

[0068] Each sub-model includes one or more configuration items, and each configuration item corresponds to one or more configuration parameters. For example, sub-model 1 may include the configuration items and configuration parameters shown in Table 1 above. Similarly, sub-model 5 may include the configuration items and configuration parameters shown in Table 2 above.

[0069] The first sub-model set includes at least one sub-model corresponding to the component identifier of the first business server.

[0070] It is worth noting that the process by which the management server determines the first sub-model corresponding to any business server in the management system is the same. In the following description of the embodiments of this application, the process of how the management server determines the first sub-model and first configuration information corresponding to the first business server will be described as an example.

[0071] Optionally, the management server can pre-set the correspondence between sub-models and component identifiers. After obtaining the component identifier of the first business server, the management server determines the sub-model corresponding to the component identifier of the first business server in the pre-set model library according to the pre-set correspondence between sub-models and component identifiers, thereby determining the first sub-model set.

[0072] Typically, different hardware has different configuration items and parameters. Therefore, the correspondence between hardware identifiers and sub-models containing those configuration items and parameters can be pre-defined. Similarly, different hardware often has different firmware configuration items and parameters. Furthermore, because firmware identifiers are relatively simple, firmware from different manufacturers may share the same identifier, but their configuration items and parameters may differ. Therefore, to uniquely determine the required sub-model containing the firmware's configuration items and parameters, the correspondence between hardware identifiers and sub-models containing these parameters can be pre-defined. Of course, the correspondence between firmware identifiers and sub-models containing those parameters can also be pre-defined. Likewise, different software typically has different configuration items and parameters. Therefore, the correspondence between software identifiers and sub-models containing those parameters can be pre-defined.

[0073] For example, the mapping between RAID card identifiers and sub-models including RAID card configuration items and parameters can be pre-configured. The mapping between network card identifiers and sub-models including network card configuration items and parameters can be pre-configured. The mapping between CPU identifiers or motherboard identifiers and sub-models including BIOS configuration items and parameters can be pre-configured, or the mapping between BIOS version numbers and sub-models including BIOS configuration items and parameters can be pre-configured. The mapping between operating system identifiers and sub-models including operating system configuration items and parameters can be pre-configured.

[0074] For example, consider a component identifier that includes the component model. The pre-built model library includes sub-models 1 to 6 mentioned above. A correspondence between the sub-models and component models can be established as shown in Table 3 below. Here, "LSI3108" and "LSI3008" are RAID card models. "MZ910" and "MZ920" are network card models. "IntelxeonV3" and "IntelxeonV5" are CPU models.

[0075] When the management server detects that the RAID card model of the first service server is "LSI3108", the network card model is "MZ910", and the CPU model is "IntelxeonV3", it determines that "LSI3108" corresponds to sub-model 1, "MZ910" corresponds to sub-model 3, and "IntelxeonV3" corresponds to sub-model 5. The management server retrieves sub-model 1, sub-model 3, and sub-model 5 from the preset model library. Sub-model 1, sub-model 3, and sub-model 5 are sub-models in the first sub-model set.

[0076] Table 3

[0077]

[0078]

[0079] For example, as shown in Table 4 below, BIOS version numbers "0.0.1" and "0.0.2" both correspond to sub-model 5. BIOS version number "0.0.3" corresponds to sub-model 6. When the management server detects that the RAID card model of the first service server is "LSI3108", the network card model is "MZ910", and the BIOS version number is "0.0.1", it determines that "LSI3108" corresponds to sub-model 1, "MZ910" corresponds to sub-model 3, and "0.0.1" corresponds to sub-model 5. The management server retrieves sub-model 1, sub-model 3, and sub-model 5 from the preset model library. Sub-model 1, sub-model 3, and sub-model 5 are sub-models in the first sub-model set.

[0080] Table 4

[0081] LSI3108 Sub-model 1 LSI3008 Sub-model 2 MZ910 Sub-model 3 MZ920 Sub-model 4 0.0.1 or 0.0.2 Sub-model 5 0.0.3 Sub-model 6

[0082] Alternatively, the names of sub-models in the pre-built model library can include component identifiers. The sub-models corresponding to these component identifiers are those whose names include that component identifier. The management server determines the sub-models in the pre-built model library whose names include the component identifier of the first business server, thereby determining the first set of sub-models. This eliminates the need to separately establish the correspondence between sub-model identifiers and component identifiers as shown in Table 3.

[0083] For example, taking the component identification as the component model, the pre-built model library includes sub-models 1 to 6. Sub-model 1 is named "RAID-LSI3108", sub-model 2 is named "RAID-LSI3008", sub-model 3 is named "NIC-MZ910", sub-model 4 is named "NIC-MZ920", sub-model 5 is named "BIOS-IntelxeonV3", and sub-model 6 is named "BIOS-IntelxeonV5". The management server obtains the component models of the first service server as "LSI3108", "MZ910", and "IntelxeonV3". The management server finds "LSI3108" in the names of sub-model 1, "MZ910" in the names of sub-model 3, and "IntelxeonV3" in the names of sub-model 5. Therefore, the first set of sub-models determined by the management server includes sub-model 1, sub-model 3, and sub-model 5.

[0084] As an optional implementation, the specific implementation of the management server determining the first sub-model set in the preset model library based on the identifier of the component of the first business server is as follows: the management server determines at least one second sub-model set in the preset model library that corresponds to at least one component category of the first business server, each second sub-model set including sub-models corresponding to components of the same category, the component category being used to indicate the component classification information to which the component of the first business server belongs; the management server determines the first sub-model set from at least one second sub-model set based on the identifier of at least one component of the first business server.

[0085] By implementing this optional implementation method, a second sub-model set can be determined first based on the category of the component. The second sub-model set includes sub-models corresponding to components of the same category. Then, the sub-model corresponding to the component identifier is searched in the second sub-model set. This can narrow the search range for the sub-model corresponding to the component identifier, thereby enabling the sub-model corresponding to the component identifier to be found more quickly.

[0086] For example, a component category often includes multiple different models. For instance, RAID cards with the model number "LSI3108," "LSI3008," and "LSI2208" all belong to the same component category: RAID cards. Similarly, network cards with the model numbers "MZ910" and "MZ920" also belong to the same component category: network cards. Likewise, CPUs with model numbers "IntelxeonV3" and "IntelxeonV5" belong to the CPU category.

[0087] As shown in Table 5 below, the management server can pre-store the correspondence between component categories and the second sub-model set. The second sub-model set 1 includes sub-model 1 and sub-model 2. The second sub-model set 2 includes sub-model 3 and sub-model 4. The second sub-model set 3 includes sub-model 5 and sub-model 6. The management server obtains the RAID card model "LSI3108", the network card model "MZ910", and the CPU model "IntelxeonV3" of the first service server. The management server determines that the component category "RAID card" corresponds to the second sub-model set 1, the component category "network card" corresponds to the second sub-model set 2, and the component category "CPU" corresponds to the second sub-model set 3. The management server retrieves sub-model 1 from the second sub-model set 1 based on the model "LSI3108", retrieves sub-model 3 from the second sub-model set 2 based on the model "MZ910", and retrieves sub-model 5 from the second sub-model set 3 based on the model "IntelxeonV3". The method for the management server to obtain sub-models from the second sub-model set based on the model can be found in the above description. For example, based on the pre-established correspondence between model and sub-model, the sub-model corresponding to the component model of the first business server can be determined, or the sub-model whose name includes the component model of the first business server can be determined.

[0088] Table 5

[0089] RAID Second Sub-model Set 1 NIC Second Sub-model Set 2 CPU Second Sub-model Set 3

[0090] Of course, when a firmware identifier corresponds to a sub-model that includes the firmware's configuration items and configuration parameters, the second sub-model set corresponding to the firmware's component type can be determined first, and then the sub-model corresponding to the firmware identifier can be obtained from the second sub-model set corresponding to the firmware's component type. For example, when a BIOS identifier corresponds to a sub-model that includes the BIOS's configuration items and configuration parameters, the second sub-model set corresponding to the component type "BIOS" can be determined first, and then the sub-model corresponding to the BIOS identifier can be obtained from the second sub-model set corresponding to the component type "BIOS".

[0091] As an optional implementation, when there is no sub-model corresponding to the identifier of the first component in the pre-built model library, the management server obtains the configuration items and configuration parameters of the first component from the first business server. This first component can be any one of the components of the first business server. The management server adds a first sub-model to the pre-built model library based on the configuration items and configuration parameters of the first component. This first sub-model includes the configuration items and configuration parameters of the first component. By implementing this optional implementation, sub-models can be automatically generated, expanding the sub-models in the pre-built model library and making the sub-models in the pre-built model library more complete.

[0092] For example, the management server obtains that the RAID card model of the first service server is "LSI3108" and the network card model is "MZ910". There is no sub-model corresponding to the network card model "MZ910" in the pre-built model library. Therefore, the management server obtains the configuration items and parameters of the network card model "MZ910" from the first service server. The management server generates a first sub-model based on the configuration items and parameters of the network card model "MZ910". The first sub-model includes the configuration items and parameters of the network card model "MZ910". After generating the first sub-model, the management server stores it in the pre-built model library to expand the sub-models in the library and make them more complete. Optionally, the management server can establish and store the correspondence between the model "MZ910" and the first sub-model, or the name of the first sub-model may include the model "MZ910", so that the corresponding first sub-model can be found based on the component model "MZ910". After the management server generates the first sub-model, it determines the first sub-model and the sub-model corresponding to the model "LSI3108" obtained from the preset model library as the sub-models in the first sub-model set.

[0093] Optionally, if the pre-built model library does not contain a sub-model corresponding to the identifier of the first component (e.g., the identifier of the first component could be a CPU identifier or a motherboard identifier), which includes firmware configuration items and configuration parameters, the management server obtains the firmware configuration items and configuration parameters from the first service server. The management server then adds a first sub-model to the pre-built model library based on the firmware configuration items and configuration parameters. This first sub-model includes the firmware configuration items and configuration parameters.

[0094] Optionally, after determining the first sub-model set, the first sub-model set corresponding to the first business server can be stored so that the configuration items of the components of the first business server can be configured according to the configuration items and configuration parameters in the first sub-model set.

[0095] Optionally, if a sub-model corresponding to the identifier of the first component does not exist in the pre-built model library, it can be downloaded from the Internet. For example, the sub-model can be published on the company's official website by the management software development team, so that when a sub-model corresponding to the identifier of the first component does not exist in the pre-built model library, the management server can download the sub-model corresponding to the identifier of the first component from the company's official website.

[0096] Alternatively, sub-models in the pre-built model library can also be copied from other devices.

[0097] 203. The management server sends the first configuration information to the first business server.

[0098] In this embodiment, after the management server determines the first sub-model set in the preset model library based on the identifier of the component of the first business server, it sends first configuration information to the first business server. The first configuration information carries at least one configuration item and configuration parameters from the first sub-model set, so that the first business server can configure the configuration parameters of the configuration item of the at least one component to be configured according to the first configuration information. The component to be configured may be a portion of the components of the first business server; that is, the management server may configure parameters only for a portion of the components of the first business server. Alternatively, the component to be configured may be all components of the first business server; this embodiment does not limit the scope.

[0099] For example, the first sub-model set includes sub-model 1 and sub-model 5 as described above. Sub-model 1 includes the configuration items and parameters of the RAID card. Sub-model 5 includes the configuration items and parameters of the BIOS. The configuration items and parameters included in sub-model 1 are shown in Table 1 above. The configuration items and parameters included in sub-model 5 are shown in Table 2 above. The management server can configure only the configuration items of the RAID card. For example, the management server sends first configuration information to the first service server. This first configuration information includes the configuration items "RAID controller ID" and "RAID level", the configuration parameter "RAIDStorage0" for configuring the "RAID controller ID", and the configuration parameter "RAID10" for configuring the "RAID level". After receiving the first configuration information, the first service server configures the "RAID controller ID" of the RAID card to "RAIDStorage0" and the "RAID level" to "RAID10".

[0100] For different components to be configured, the management server can send configuration items and parameters to the first service server via the BMC through different configuration paths. For example, the components to be configured include a RAID card and a BIOS. The management server can send the RAID card's configuration items and parameters to the first service server via configuration path 1 through the BMC, and also send the BIOS's configuration items and parameters to the first service server via configuration path 2 through the BMC. After receiving the configuration items and parameters via configuration path 1, the first service server uses the configuration parameters to configure the RAID card. Similarly, after receiving the configuration items and parameters via configuration path 2, the first service server uses the configuration parameters to configure the BIOS.

[0101] Optionally, this application can also be used in scenarios involving firmware upgrades of a first service server. The component identifier of the first service server obtained by the management server includes the firmware version number. The management server obtains the sub-model corresponding to the firmware version number. The sub-model corresponding to the firmware version number includes configuration items for the firmware version and configuration parameters for one or more firmware version numbers. After obtaining the sub-model corresponding to the firmware version number, the management server can use at least one configuration item and configuration parameter in the sub-model as configuration parameters in the first configuration information and send the first configuration information to the first service server. After receiving the first configuration information, the first service server upgrades the firmware version to the version in the first configuration information. For example, if the first configuration information includes the configuration item "firmware version" and the configuration parameter "0.0.2", the first service server upgrades the firmware version to 0.0.2.

[0102] Optionally, this application can also be used in scenarios where the operating system of a first business server is upgraded. The component identifier of the first business server obtained by the management server includes the operating system version number. The management server obtains the sub-model corresponding to the operating system version number. The sub-model corresponding to the operating system version number includes configuration items for the operating system version and configuration parameters for one or more operating system version numbers. After obtaining the sub-model corresponding to the operating system version number, the management server can use at least one configuration item and configuration parameter in the sub-model as configuration parameters in the first configuration information and send the first configuration information to the first business server. After receiving the first configuration information, the first business server upgrades the operating system version to the version in the first configuration information. For example, when the first configuration information includes the configuration item "operating system version" and the configuration parameter "CentOS7.3", the first business server upgrades the operating system version to CentOS7.3.

[0103] 204. The first service server configures the configuration parameters of at least one configuration item of the component to be configured according to the first configuration information.

[0104] Optionally, the management server can send the first configuration information to multiple business servers in batches to achieve batch configuration. For example, business server 1 and business server 2 have the same components and need to be configured with the same parameters. The management server can send the first configuration information to both business server 1 and business server 2 simultaneously, enabling business server 1 and business server 2 to configure the parameters of the components according to the first configuration information.

[0105] It is evident that through implementation Figure 2The described method includes a pre-built model library containing at least one sub-model, each sub-model including configuration items and configuration parameters for a component. The management server can dynamically obtain a set of sub-models corresponding to the business server, where each sub-model set includes at least one sub-model corresponding to a component identifier of the business server. Therefore, the management server can dynamically obtain the configuration items and configuration parameters of the business server, allowing for subsequent parameter configuration of the components' configuration items on the business server. It is evident that through implementation... Figure 2 The described method allows for the dynamic acquisition of the latest configuration items and parameters of the business server without requiring updates to the management software when components change. This facilitates quick parameter configuration of business server components, improving the efficiency of server operation and maintenance. Furthermore, different business servers may share some common components, which can be addressed through implementation... Figure 2 The described method allows multiple business servers to reuse the same sub-model, which helps save development costs.

[0106] As a possible embodiment, after step 203, the management server can also save the first configuration information and create a new sub-model in the preset model library. This sub-model is used to identify the component configuration parameter set information of the first business server, so that when the management node performs update configuration parameters, firmware upgrade, or OS upgrade operations again, it can quickly obtain the sub-model set corresponding to the first business server, determine the first configuration parameters, and then send them to the first business server. This improves the operation and maintenance efficiency of the business server, reduces the operation time of operation and maintenance scenarios such as parameter configuration, firmware upgrade, and OS upgrade, and reduces the impact on applications running on the business server.

[0107] Please see Figure 3 , Figure 3 This is a flowchart illustrating a device management method provided in an embodiment of this application. Wherein, Figure 3 The equipment management method shown is the same as Figure 2 The difference between the equipment management methods shown is that... Figure 3 After determining the first sub-model set, the management server can display the configuration items and parameters in the first sub-model set according to the preset display rules, and can select at least one configuration item and parameter from the first sub-model set as the configuration items and parameters included in the first configuration information. For example... Figure 3 As shown, the equipment management method includes the following steps 301 to 306, wherein:

[0108] 301. The management server obtains the identifier of a component in at least one business server.

[0109] 302. The management server determines the first sub-model set in the preset model library based on the identifier of the component of the first business server.

[0110] The specific implementation methods of steps 301 and 302 are the same as those of steps 201 and 202 above. For details, please refer to the descriptions corresponding to steps 201 and 202 above, which will not be repeated here.

[0111] 303. The management server displays the configuration items and configuration parameters in the first sub-model set according to the preset display rules in the first sub-model set.

[0112] The first sub-model set includes preset display rules for configuration items and parameters. After determining the first sub-model set, the management server can display the configuration items and parameters in the first sub-model set according to the preset display rules.

[0113] In practical applications, if the components of the business server change, or if the business server is newly added to the device management system, the management software needs to be updated to update the configuration items and parameters of the business server in the management software, as well as the display rules for these configuration items and parameters. By implementing step 303, the display rules for the configuration items and parameters are added to the sub-model. The management server can then dynamically obtain the display rules for the configuration items and parameters of the business server, thus eliminating the need to update the management software and facilitating quick parameter configuration of the business server's configuration items.

[0114] Optionally, the preset display rules for configuration items may include at least one of the display order of configuration items and the menu path of configuration items. The display order of configuration items refers to the display order among several configuration items of the same component. The menu path of configuration items refers to the directory where the configuration item is located.

[0115] Optionally, the preset display rules for configuration parameters include at least one of the following: whether the configuration parameter is read-only, whether the configuration parameter is grayed out, and whether the configuration parameter is hidden. Whether the configuration parameter is read-only means whether the configuration parameter can only be read and cannot be modified. Whether the configuration parameter is grayed out means whether the configuration parameter should be grayed out if the dependency conditions are not met. Whether the configuration parameter is hidden means whether the configuration parameter needs to be hidden when it is not needed.

[0116] For example, Table 6 below uses a sub-model corresponding to a RAID card as an example. This sub-model may include the information shown in Table 6 below.

[0117] Table 6

[0118]

[0119]

[0120] As an optional implementation, the sub-models of the first sub-model set also include dependent configuration items, dependent configuration items, and dependency conditions; wherein, the configuration parameters of the dependent configuration items and the dependent configuration items in the first sub-model set are displayed according to whether the current configuration parameters of the dependent configuration items meet the dependency conditions.

[0121] Setting dependencies improves user experience and prevents conflicting configuration items. Furthermore, by adding dependent configuration items, dependent configuration items, and dependency conditions to the sub-model, the management server can dynamically obtain these information from the business server, eliminating the need to update the management software and facilitating quick parameter configuration for the business server.

[0122] For example, Table 7 below uses a sub-model corresponding to a BIOS as an example. This sub-model may include the information shown in Table 7. Specifically, when the current configuration parameters of the dependent configuration item "VTd support" meet the dependency condition, that is, when the current configuration parameters of the dependent configuration item "VTd support" are "enabled", the dependent configuration item "InterruptRemap" and its configuration parameters are not hidden. Otherwise, the dependent configuration item "InterruptRemap" and its configuration parameters are hidden.

[0123] Table 7

[0124]

[0125]

[0126] Optionally, the first sub-model set may also include at least one of the following: data type of configuration parameters (such as enumeration type, boolean type, etc.), creation method of configuration parameters (such as single selection, multiple selection, etc.), help information, alarm information, currently configured value of configuration item, default value of configuration item, maximum string length of configuration parameter, minimum string length of configuration parameter, maximum value of configuration parameter, minimum value of configuration parameter, and effective mode (such as effective immediately or effective after restart).

[0127] 304. The management server selects at least one configuration item and configuration parameter from the first sub-model set as the configuration items and configuration parameters included in the first configuration information.

[0128] Optionally, the management server can select the configuration items to be configured and the appropriate configuration parameters from the displayed configuration items based on the selection instructions entered by the user.

[0129] For example, the first sub-model set includes sub-model 1 and sub-model 5 as described above. The configuration items and parameters included in sub-model 1 are shown in Table 1 above. The configuration items and parameters included in sub-model 5 are shown in Table 2 above. Figure 4This is a schematic diagram of a display interface, such as... Figure 4 As shown, the management server can output the configuration items and parameters included in the first sub-model set. Users can select the configuration items and appropriate configuration parameters to be configured. For example... Figure 4 As shown, the user selects to configure the "RAID controller ID" to "RAIDStorage0", the "RAID level" to "RAID10", and the "boot disk" to "Yes". After receiving the user's selection command, the management server includes the selected "RAID controller ID" and its corresponding configuration parameter "RAIDStorage0", the "RAID level" and its corresponding configuration parameter "RAID10", and the "boot disk" and its corresponding configuration parameter "Yes" as the first configuration information.

[0130] By implementing step 304, configuration items and configuration parameters can be flexibly selected from the first sub-model set for parameter configuration.

[0131] 305. The management server sends the first configuration information to the first business server.

[0132] Optionally, after the management server sends the first configuration information to the first service server, the management server can generate a configuration file that includes the first configuration information. The management server saves this configuration file so that the next time a user wants to perform the same configuration, the user can enter a command to allow the management server to directly select the configuration file and configure the configuration items of at least one component to be configured using the configuration parameters in the configuration file.

[0133] 306. The first service server updates the configuration parameters of the component's configuration items based on the first configuration information.

[0134] The specific implementation methods of parts 305 and 306 are the same as those of parts 203 and 204. For details, please refer to the descriptions corresponding to parts 203 and 204 above, which will not be repeated here.

[0135] To more clearly illustrate the content of this application, three complete examples are provided below to further explain the solution. Example 1 illustrates the configuration of parameters for the RAID card and BIOS of a business server by a management server. Example 2 illustrates the upgrade of the operating system of a business server by a management server. Example 3 illustrates the upgrade of the firmware of a business server by a management server.

[0136] Example 1:

[0137] The management server has a pre-built model library. This library includes four sub-models, designated sub-models 1 through 4. Sub-models 1 and 2 both include RAID card configuration items and parameters. Sub-models 3 and 4 both include BIOS configuration items and parameters. The configuration items and parameters included in sub-models 1 and 2 are different. The configuration items and parameters included in sub-models 3 and 4 are also different. The sub-models in the pre-built model library correspond to specific component models, as shown in Table 8. "LSI3108" and "LSI3008" are RAID card component models. "IntelxeonV3" and "IntelxeonV5" are CPU component models. Different component models correspond to different sub-models.

[0138] Table 8

[0139] LSI3108 Sub-model 1 LSI3008 Sub-model 2 Intelxeon V3 Sub-model 3 Intelxeon V5 Sub-model 4

[0140] The management server can obtain the RAID card and CPU models of service servers 1-3 when they are powered on. Alternatively, the management server can periodically obtain these models. The management server obtained the following information: Service server 1 has a RAID card model of "LSI3108" and a CPU model of "Intelxeon V3". Service server 2 has a RAID card model of "LSI3108" and a CPU model of "Intelxeon V3". Service server 3 has a RAID card model of "LSI2208" and a CPU model of "Intelxeon V5".

[0141] Based on the correspondence in Table 8 above, the management server can directly search the pre-built model library for the sub-model corresponding to the RAID card model "LSI3108" and the CPU model "IntelxeonV3" of business server 1. As shown in Table 8, the management server determines that "LSI3108" corresponds to sub-model 1 and "IntelxeonV3" corresponds to sub-model 3. Therefore, the management server determines that the first sub-model set 1 corresponding to business server 1 includes sub-model 1 and sub-model 3.

[0142] Alternatively, the management server can pre-configure the correspondence between component categories and the second sub-model set. This correspondence is shown in Table 9 below. After obtaining the RAID card model "LSI3108" and CPU model "IntelxeonV3" of business server 1, the management server can first determine that the component category "RAID card" corresponds to the second sub-model set 1, and determine that the component category "CPU" corresponds to the second sub-model set 2. The management server retrieves sub-model 1 from the second sub-model set 1 based on the model "LSI3108", and retrieves sub-model 3 from the second sub-model set 3 based on the model "IntelxeonV3", and combines sub-model 1 and sub-model 3 into the first sub-model set 1.

[0143] Table 9

[0144] RAID Second Sub-model Set 1 CPU Second Sub-model Set 2

[0145] Similarly, the management server uses the same principle to determine that business server 2 corresponds to the first sub-model set 1.

[0146] When the management server determines the first sub-model set 2 corresponding to business server 3, it detects that there is no sub-model corresponding to the RAID card model "LSI2208" in the preset model library. Therefore, the management server obtains the configuration items and configuration parameters of the RAID card model "LSI2208" from business server 3. Based on the obtained configuration items and configuration parameters of the RAID card model "LSI2208", the management server generates sub-model 5, which includes the configuration items and configuration parameters of the RAID card model "LSI2208". The management server establishes the correspondence between sub-model 5 and the model "LSI2208" and stores sub-model 5 in the preset model library. Finally, the management server determines that the first sub-model set 2 corresponding to business server 3 includes sub-model 4 and sub-model 5.

[0147] Alternatively, the management server can determine the first sub-model set corresponding to business servers 1-3 in another way. The pre-built model library includes four different sub-models, namely sub-models 1-4. Sub-models 1 and 2 both include RAID card configuration items and parameters. Sub-models 3 and 4 both include BIOS configuration items and parameters. The sub-models in the pre-built model library have a correspondence with component models, as shown in Table 10 below. "LSI3108" and "LSI3008" are RAID card component models. Different RAID card component models correspond to different sub-models. "0.0.1", "0.0.2", and 0.0.3 are BIOS component version numbers. Different BIOS version numbers may correspond to the same sub-model or different sub-models.

[0148] Table 10

[0149] LSI3108 Sub-model 1 LSI3008 Sub-model 2 0.0.1 or 0.0.2 Sub-model 3 0.0.3 Sub-model 4

[0150] The management server can obtain the RAID card model and BIOS version number of service servers 1-3 when they are powered on. Alternatively, the management server can periodically obtain the RAID card model and BIOS version number of service servers 1-3. The management server obtained the following information: Service server 1's RAID card model is "LSI3108" and BIOS version number is "0.0.1". Service server 2's RAID card model is "LSI3108" and BIOS version number is "0.0.1". Service server 3's RAID card model is "LSI2208" and BIOS version number is "0.0.3".

[0151] Based on the correspondence in Table 10 above, the management server can directly search the pre-built model library for the sub-model corresponding to the RAID card model "LSI3108" of business server 1 and the sub-model corresponding to the BIOS version number "0.0.1". As shown in Table 10 above, the management server determines that "LSI3108" corresponds to sub-model 1 and "0.0.1" corresponds to sub-model 3. Therefore, the management server determines that the first sub-model set 1 corresponding to business server 1 includes sub-model 1 and sub-model 3.

[0152] Alternatively, the management server can pre-configure the correspondence between component categories and the second sub-model set. After obtaining the RAID card model "LSI3108" and BIOS version number "0.0.1" of business server 1, the management server can first determine that the component category "RAID card" corresponds to the second sub-model set 1, and determine that the component category "BIOS" corresponds to the second sub-model set 2. The management server retrieves sub-model 1 from the second sub-model set 1 based on the model "LSI3108", and retrieves sub-model 3 from the second sub-model set 3 based on the version number "0.0.1", and combines sub-model 1 and sub-model 3 into the first sub-model set 1.

[0153] Similarly, the management server determines that business server 2 corresponds to the first sub-model set 1 using the same principle. The management server also determines that the first sub-model set 2 corresponding to business server 3 includes sub-model 4. Since the pre-built model library does not contain a sub-model corresponding to the RAID card of business server 3 with the model number "LSI2208", the management server obtains the configuration items and parameters of the RAID card with the model number "LSI2208" from business server 3. Based on the obtained configuration items and parameters of the RAID card with the model number "LSI2208", the management server generates sub-model 5, which includes the configuration items and parameters of the RAID card with the model number "LSI2208". The management server establishes the correspondence between sub-model 5 and the model number "LSI2208" and stores sub-model 5 in the pre-built model library. Finally, the management server determines that the first sub-model set 2 corresponding to business server 3 includes sub-model 4 and sub-model 5.

[0154] After the management server determines the first sub-model sets corresponding to business servers 1 through 3, the user can open the configuration interface. The management server can display the configuration items and parameters of the first sub-model sets for the user to select from in the configuration interface. The management server can display the configuration items and parameters of the first sub-model sets according to preset display rules. Taking the management server outputting the configuration items and parameters of first sub-model set 1 in the configuration interface for the user to select from as an example, the output interface would look like this: Figure 5 As shown. Users can select the configuration items and appropriate configuration parameters that need to be configured. For example... Figure 5 As shown, the user selects to configure the "RAID controller ID" to "RAIDStorage0", the "RAID level" to "RAID10", and the "boot disk" to "Yes". The user also selects to configure the "system boot mode" to "UEFI mode", the "energy efficiency mode" to "low power", "VTd support" to "enabled", and "InterruptRemap" to "enabled". Alternatively, the user can configure only the RAID card or BIOS parameters. The user can also select the service server to be configured. Figure 5 As shown, users can choose to configure business server 1 and business server 2.

[0155] After receiving the configuration command input by the user, the management server sends the first configuration information to business server 1 and business server 2. The first configuration information includes, for example: Figure 5 The configuration items and parameters selected by the user are shown. After receiving the first configuration information, business server 1 and business server 2 configure the configuration items accordingly based on the configuration parameters in the first configuration information.

[0156] Example 2:

[0157] The management server has a pre-built model library. This library contains two sub-models: Sub-model 1 and Sub-model 2. Both Sub-model 1 and Sub-model 2 include operating system configuration items and parameters. Each sub-model in the pre-built model library corresponds to an operating system identifier. This identifier can be the operating system version number. For example, the operating system version number could be CentOS 7.2, CentOS 7.3, etc. The correspondence between the sub-models in the pre-built model library and the operating system identifiers is shown in Table 11 below.

[0158] Table 11

[0159] CentOS 7.2 Sub-model 1 CentOS 7.3 Sub-model 2

[0160] The management server can obtain the operating system version number of business servers 1-3 when they are powered on. The management server can periodically obtain the operating system version number of business servers 1-3. The management server obtains the operating system version number of business servers 1-3 as "CentOS 7.2". Based on the correspondence shown in Table 11 above, the management server obtains sub-model 1 corresponding to "CentOS 7.2" as a sub-model included in the first sub-model set of business servers 1-3. Of course, if there are other types of component sub-models in the pre-built model library, the management server can first determine the second sub-model set corresponding to the operating system, and then determine the sub-model 1 corresponding to "CentOS 7.2" from the second sub-model set.

[0161] After the management server determines the first sub-model set corresponding to business servers 1-3, the user can open the configuration interface. The management server can display the configuration items and parameters of the first sub-model set for the user to select. The management server can also output the configuration items and parameters of sub-model 1 for the user to select. For example, sub-model 1 includes the configuration item "Operating System Version" and the configuration parameters "CentOS 7.3", "CentOS 7.4", and "CentOS 7.5". If the user selects the configuration parameter "CentOS 7.5" and chooses to upgrade the operating system of business servers 1-3, the management server will send the configuration item "Operating System Version" and the configuration parameter "CentOS 7.5" to business servers 1-3, so that business servers 1-3 will upgrade their operating system version to "CentOS 7.5". Optionally, the user can upload the "CentOS 7.5" installation package to the management server, and the management server can send the "CentOS 7.5" installation package along with the configuration item "Operating System Version" and the configuration parameter "CentOS 7.5" to business servers 1-3.

[0162] Example 3:

[0163] The management server has a pre-built model library. This library contains two sub-models: Sub-model 1 and Sub-model 2. Both Sub-model 1 and Sub-model 2 include firmware configuration items and parameters. Each sub-model in the pre-built model library corresponds to a firmware identifier. This firmware identifier can be the firmware version number. For example, the firmware version number could be 0.0.1, 0.0.2, etc. The correspondence between the sub-models in the pre-built model library and the firmware identifiers is shown in Table 12 below.

[0164] Table 12

[0165] 0.0.1 Sub-model 1 0.0.2 Sub-model 2

[0166] The management server can obtain the firmware version number of business servers 1-3 when they are powered on. The management server obtains the firmware version number of business servers 1-3 as "0.0.1". Based on the correspondence shown in Table 11 above, the management server obtains sub-model 1 corresponding to "0.0.1" as a sub-model included in the first sub-model set of business servers 1-3. Of course, if there are other types of component sub-models in the preset model library, the management server can first determine the second sub-model set corresponding to the firmware, and then determine the sub-model 1 corresponding to "0.0.1" from the second sub-model set.

[0167] The management server can output configuration items and parameters from sub-model 1 for users to select. For example, sub-model 1 includes the configuration item "firmware version" and configuration parameters "0.0.2", "0.0.3", and "0.0.4". If the user selects configuration parameter "0.0.4" and chooses to upgrade the firmware of business servers 1-3, the management server will send the configuration item "firmware version" and configuration parameter "0.0.4" to business servers 1-3, so that business servers 1-3 will upgrade their firmware version to "0.0.4". Optionally, the user can upload the "0.0.4" installation package to the management server, and the management server can send the "0.0.4" installation package along with the configuration item "firmware version" and configuration parameter "0.0.4" to business servers 1-3.

[0168] The above text combines Figures 1 to 5 A device management method according to an embodiment of the present invention has been described in detail below, and will be combined with Figures 6 to 7 This describes the management server provided according to an embodiment of the present invention.

[0169] Please see Figure 6 , Figure 6This invention provides a management server. The management server is deployed in an equipment management system, which also includes at least one business server. The management server manages the at least one business server. The management server has a pre-set model library, which includes at least one sub-model. Each sub-model includes configuration items and configuration parameters for components. The management server includes a communication module 601 and a processing module 602. Wherein:

[0170] The communication module 601 is used to obtain the component identifier of a component in each of the at least one business server; the processing module 602 is used to determine a first sub-model set in a preset model library based on the component identifier of the first business server, wherein the first business server is any one of the at least one business server, and the first sub-model set includes at least one sub-model corresponding to the component identifier of the first business server; the communication module 601 is also used to send first configuration information to the first business server, wherein the first configuration information carries at least one configuration item and configuration parameter in the first sub-model set, so that the first business server can configure the configuration parameter of the configuration item of at least one component to be configured based on the first configuration information.

[0171] Optionally, the communication module 601 is further configured to obtain the configuration items and configuration parameters of the first component from the first business server when there is no sub-model corresponding to the identifier of the first component in the preset model library, wherein the first component is any one of the components of the first business server; the processing module 602 is further configured to add a first sub-model in the preset model library according to the configuration items and configuration parameters of the first component, wherein the first sub-model includes the configuration items and configuration parameters of the first component.

[0172] Optionally, the communication module 601 is specifically used to: acquire the identifier of a component in each of the at least one service server when at least one service server is detected to be powered on; or, periodically acquire the identifier of a component in each of the at least one service server.

[0173] Optionally, the processing module 602 is specifically used to: determine at least one second sub-model set corresponding to at least one component category of the first business server in a preset model library, each second sub-model set including sub-models corresponding to components of the same category, the component category being used to indicate the component classification information to which the components of the first business server belong; and determine a first sub-model set from at least one second sub-model set according to at least one component identifier of the first business server.

[0174] Optionally, the processing module 602 is further configured to select at least one configuration item and configuration parameter as the configuration item and configuration parameter included in the first configuration information in the first sub-model set before the communication module 601 sends the first configuration information to the first service server.

[0175] Optionally, the sub-models in the first sub-model set also include preset display rules for configuration items and configuration parameters; the processing module 602 is further configured to display the configuration items and configuration parameters in the first sub-model set according to the preset display rules in the first sub-model set before the processing module 602 selects at least one configuration item and configuration parameter as the configuration items and configuration parameters included in the first configuration information.

[0176] It should be understood that the management server in this embodiment of the invention can be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. It can also be implemented using software. Figure 2 and Figure 3 In the device management implementation method shown, the management server and its various modules can also be software modules.

[0177] The management server according to embodiments of the present invention can correspond to executing the methods described in the embodiments of the present invention, and the above and other operations and / or functions of each unit in the management server are respectively for implementing Figure 2 and Figure 3 The corresponding processes of each method will not be elaborated here for the sake of brevity.

[0178] visible, Figure 6 The described management server can dynamically obtain the configuration items and parameters of the business servers, allowing for subsequent parameter configuration of the business server components. Therefore, when business server components change, the management server does not need to update its management software to dynamically obtain the latest configuration items and parameters, facilitating quick parameter configuration of business server components and improving the maintenance efficiency of server operations. Furthermore, different business servers may share some common components, allowing multiple business servers to reuse the same sub-model, which helps save development costs.

[0179] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a management server disclosed in an embodiment of this application. Figure 7 As shown, the management server 700 includes a processor 701, a memory 702, and a communication interface 703. The processor 701, memory 702, and communication interface 703 are connected via a bus.

[0180] The processor 701 can be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The processor 701 can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0181] Memory 702 can be volatile memory or non-volatile memory, or both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0182] In addition to the data bus, the bus may also include a power bus, a control bus, and a status signal bus. The communication interface 703 is used to implement communication with the service server.

[0183] The processor 701 can call the program code stored in the memory 702 to execute the steps performed by the management server in the above method embodiment.

[0184] It should be understood that the management server 700 according to an embodiment of the present invention may correspond to the one in the embodiment of the present invention. Figure 6 The management server shown can correspond to the execution of the embodiments of the present invention. Figure 2 and Figure 3 The operation steps in the method for implementing device management are executed by the corresponding management server, and the above and other operations and / or functions of each module in the management server 700 are respectively for implementing... Figures 2 to 3 For the sake of brevity, the corresponding processes of each method in the code will not be elaborated here.

[0185] visible, Figure 7The described management server can dynamically obtain the configuration items and parameters of the business servers, allowing for subsequent parameter configuration of the business server components. Therefore, when business server components change, the management server does not need to update its management software to dynamically obtain the latest configuration items and parameters, facilitating quick parameter configuration of business server components and improving the maintenance efficiency of server operations. Furthermore, different business servers may share some common components, allowing multiple business servers to reuse the same sub-model, which helps save development costs.

[0186] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive (SSD).

[0187] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0188] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for managing equipment, characterized in that, The method is applied in an equipment management system, which includes a management server and at least one business server. Each business server includes one or more components, which may include hardware, firmware, or software. The management server manages the at least one business server and has a pre-built model library. The pre-built model library includes at least one sub-model, each sub-model including configuration items and configuration parameters for components, and the sub-models are reusable by the at least one business server. The method includes: The management server obtains the component identifier of at least one component in each of the at least one business server; The management server determines a first sub-model set in a preset model library based on the component identifier of the first business server. The first business server is any one of the at least one business server. The first sub-model set includes sub-models corresponding to each component identifier of the first business server. In response to a selection command input by the user, the management server determines at least one configuration item and configuration parameter in the first sub-model set; The management server sends first configuration information to the first business server. The first configuration information carries at least one configuration item and configuration parameters selected from the first sub-model set, so as to instruct the first business server to configure the configuration parameters of at least one configuration item of the component to be configured according to the first configuration information. After the step of the management server sending the first configuration information to the first service server, the method further includes: The management server generates a configuration file, which includes the first configuration information. The management server stores the configuration file, which is available for use to configure components with the same parameter configuration requirements.

2. The method according to claim 1, characterized in that, The method further includes: When there is no sub-model corresponding to the identifier of the first component in the preset model library, the management server obtains the configuration items and configuration parameters of the first component from the first business server. The first component is any one of the components of the first business server. The management server adds a first sub-model to the preset model library according to the configuration items and configuration parameters of the first component. The first sub-model includes the configuration items and configuration parameters of the first component.

3. The method according to claim 1 or 2, characterized in that, The management server obtains the identifier of a component in each of the at least one business server, including: When the management server detects that the at least one service server has been powered on, it obtains the identifier of a component in each of the at least one service server; or, The management server periodically obtains the identifiers of components in each of the at least one business server.

4. The method according to claim 1 or 2, characterized in that, The management server determines the first sub-model set from the pre-set model library based on the component identifier of the first business server, including: The management server determines at least one second sub-model set in the preset model library that corresponds to at least one component category of the first business server. Each second sub-model set includes sub-models corresponding to components of the same category. The component category is used to indicate the component classification information to which the components of the first business server belong. The management server determines the first sub-model set from the at least one second sub-model set based on at least one component identifier of the first business server.

5. The method according to claim 1 or 2, characterized in that, The sub-models in the first sub-model set also include preset display rules for configuration items and configuration parameters; Before the management server selects at least one configuration item and configuration parameter from the first sub-model set, the method further includes: Display the configuration items and configuration parameters in the first sub-model set according to the preset display rules in the first sub-model set.

6. The method according to claim 1 or 2, characterized in that, The management server determines the first sub-model set from the pre-set model library based on the component identifier of the first business server, including: Based on the first correspondence, the sub-model corresponding to each component identifier is found respectively; wherein, the first correspondence is the correspondence between the component identifier and the sub-model including the component's configuration items and configuration parameters; The set of sub-models corresponding to all components to be configured is determined as the first set of sub-models.

7. The method according to claim 1 or 2, characterized in that, The component identifier includes one or more of the following: component model, component version number, or component name.

8. The method according to claim 1 or 2, characterized in that, The method further includes: When the management server obtains that the components to be configured of multiple business servers have the same component identifier and require the same parameter configuration, the management server determines the first sub-model set in the preset model library based on the identifier of the components to be configured of the multiple business servers. The management server sends first configuration information to the first service server, including: The management server sends the first configuration information to the plurality of business servers, enabling the plurality of business servers to configure the parameters of the component to be configured according to the first configuration information.

9. A management server, characterized in that, The device management system includes a management server and at least one business server. The business server includes one or more components, which may include hardware, firmware, or software. The management server is used to manage the at least one business server and has a pre-set model library. The pre-set model library includes at least one sub-model, each of which includes configuration items and configuration parameters for the components, and the sub-model can be reused by the at least one server. The management server includes: The communication module, wherein the management server obtains the component identifier of at least one component in each of the at least one business server; The processing module is used to determine a first sub-model set in a preset model library based on the component identifier of the first business server, wherein the first business server is any one of the at least one business server, and the first sub-model set includes sub-models corresponding to each of the component identifiers of the first business server. The processing module is also used to select at least one configuration item and configuration parameter from the first sub-model set; The communication module is further configured to send first configuration information to the first service server, the first configuration information carrying at least one configuration item and configuration parameters selected from the first sub-model set, to instruct the first service server to configure the configuration parameters of the configuration item of the at least one component to be configured according to the first configuration information.

Images