BIOS option value batch modification method based on redfish interface

Abstract

The invention relates to the technical field of computer application, and discloses a BIOS option value batch modification method based on a redfish interface, which comprises the following steps: modifying BIOS configuration information needing to be modified in a corresponding server group in batch by modifying a BIOS configuration file, sending a pre-configured update script and a BIOS configuration file corresponding to the server group to each server in the server group, when the update script runs, obtaining current BIOS configuration information of the current server through a redfish interface, analyzing to obtain each BIOS option value in the current server, constructing an option value modification request, and sending the option value modification request to the server; and modifying the BIOS option value of the current server, generating an update record, and sending the update record to the configuration end. Therefore, batch modification of BIOS option values in the production line process of server production line production is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of computer applications, and in particular to a method for batch modifying BIOS option values ​​based on a redfish interface. Background Art

[0002] BIOS (Basic Input Output System) is a set of programs fixed to a ROM chip on the motherboard of the computer. It stores the most important basic input and output programs of the computer, system setting information, self-test program after power-on and system self-starting program. Its main function is to provide the lowest-level and most direct hardware setting and control for the computer. BIOS parameters are generally placed in a readable and writable CMOS (Complementary Metal Oxide Semiconductor) RAM (Random Access Memory) chip. After the computer is turned off, the system supplies power to the CMOS RAM through a backup battery to maintain the information in it. If the BIOS configuration information about the computer is incorrect, it will cause the system performance to degrade and the components to be unrecognizable, which will cause a series of software and hardware failures.

[0003] The existing factory production line production method of modifying BIOS option values ​​often has the following technical problems:

[0004] First, in order to meet the different requirements of different customers for BIOS configuration option values, factory server production currently mainly releases specific BIOS versions to modify the default values ​​of some BIOS options, and then imports the specific BIOS version into the production line process to update the BIOS to meet customer needs. This method is too time-sensitive and requires re-modifying the BIOS code and releasing the version, and the released version needs to complete relevant tests before it can be officially released for use;

[0005] Second, the existing method of determining eligible update records is outdated, resulting in a complicated process for submitting customer customized information;

[0006] Third, during the process of configuring BIOS information, when problems arise in the server configuration, there are insufficient troubleshooting methods. Summary of the invention

[0007] The summary of the invention is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The summary of the invention is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0008] The present invention proposes a method for batch modifying BIOS option values ​​based on a redfish interface to solve one or more of the technical problems mentioned in the above background technology part.

[0009] The present invention provides a method for batch modifying BIOS option values ​​based on a redfish interface, the method comprising:

[0010] Obtain customer customization information corresponding to the server cluster to be configured, and generate a BIOS configuration file group and a configuration quantity corresponding to each BIOS configuration file according to the customer customization information; divide the server cluster to be configured according to the configuration quantity corresponding to each BIOS configuration file, and obtain a server group corresponding to each BIOS configuration file, wherein the number of servers included in the server group matches the configuration quantity corresponding to the BIOS configuration file, and the BIOS configuration file includes multiple BIOS option names that need to be modified and an update value corresponding to each BIOS option name;

[0011] For each server group, the pre-configured update script and the BIOS configuration file corresponding to the server group are sent to each server in the server group. When the update script runs, the current BIOS configuration information of the current server is obtained through the redfish interface, and the current BIOS configuration information is parsed to obtain the URL path corresponding to each BIOS option name in the current server. According to the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name, an option value modification request is constructed to modify the BIOS option value of the current server, generate an update record and send the update record to the configuration end.

[0012] Optionally, before obtaining the customer customized information corresponding to the server cluster to be configured, the following is further included:

[0013] Acquire multiple update records within a historical time period, wherein each update record includes an update timestamp, a customer identifier, an update BIOS option name and an update value corresponding to the update BIOS option name, a customer type, a server order quantity, and a business scenario;

[0014] According to the customer type included in each update record, multiple update records are divided into multiple update record groups, each update record group corresponds to one customer type, and multiple update record groups correspond to multiple customer types; according to the business scenarios included in the update records, each update record group is divided to obtain update record subgroups corresponding to each customer type, and each update record subgroup corresponds to a business scenario; and

[0015] Before obtaining the customized information corresponding to the server cluster to be configured, the method further includes: upon receiving a configuration page acquisition request sent by a target user through a target user terminal, sending the configuration page to the target user terminal so that the target user submits the customized information in the configuration page; and

[0016] Obtain the customer-customized information corresponding to the server cluster to be configured, including:

[0017] When receiving the target customer identifier and the target business scenario submitted by the target user in the configuration page, the target customer identifier is queried in multiple update records, and if there is an update record matching the target customer identifier in the multiple update records, the matching update record is determined as the target update record;

[0018] The target update record is sent to the target user terminal, and the target user terminal is controlled to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

[0019] Optionally, obtaining the customer-customized information corresponding to the server cluster to be configured also includes:

[0020] If there is no update record matching the target customer identifier among the multiple update records, the customer type corresponding to the target customer identifier is determined as the target customer type, and the customer type with the highest degree of matching with the target customer type is determined from the multiple customer types, and the customer type with the highest degree of matching is determined as the matching customer type;

[0021] According to the target business scenario, a business scenario with the highest matching degree with the target business scenario is determined from multiple business scenarios corresponding to the matching customer type, and is determined as the matching business scenario;

[0022] Recommended configuration information is generated according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page.

[0023] Optionally, obtaining the customer-customized information corresponding to the server cluster to be configured also includes:

[0024] If there is no business scenario matching the target business scenario among the multiple business scenarios corresponding to the matching customer type, then for the update record subgroup corresponding to each business scenario in the multiple business scenarios, determine the average update timestamp corresponding to each update record subgroup;

[0025] According to the average update timestamp and current time corresponding to each update record subgroup, the update record subgroup closest to the current time is selected from multiple business scenarios, and recommended configuration information is generated based on the update record subgroup closest to the current time; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

[0026] Optionally, for each server group, a pre-configured update script and a BIOS configuration file corresponding to the server group are sent to each server in the server group, including:

[0027] According to the manufacturer information of each server, an update script matching the manufacturer information of each server is selected from a pre-configured update script library, and the matching update script is sent to the corresponding server.

[0028] The present invention has the following beneficial effects:

[0029] 1. It realizes batch modification of different customers' requirements for BIOS option configuration in factory server production. Specifically, different customers have different requirements for server BIOS option configuration. On this basis, according to customer customization information, BIOS configuration file groups and the number of configurations corresponding to each BIOS configuration file are generated in a targeted manner. After that, the server cluster to be configured is divided to obtain the server group corresponding to each BIOS configuration file, and then targeted configuration is performed for each server group. This specifically solves the need to import specific BIOS versions into the production line production process to update the BIOS to meet customer needs. This improves the efficiency of different customers' requirements for BIOS option configuration and ensures timeliness.

[0030] 2. The target user sends a configuration page acquisition request to the backend server through the target user terminal. The backend server sends the configuration page to the target user terminal, allowing the target user to submit the customized information in the configuration page. The backend server determines the target update record that matches it, sends the target update record to the target user terminal, and controls the target user terminal to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page. In this way, in the process of submitting customized information, the target user terminal displays the update record that meets the conditions, thereby providing reference information for user customization and facilitating the rapid submission of customized information.

[0031] 3. By counting the actual configuration time of each BIOS option for each server in the server cluster to be configured, the BIOS options and servers to be checked are determined, thereby optimizing the troubleshooting method and avoiding missing problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above and other features, advantages and aspects of the embodiments of the present invention will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0033] Figure 1 The present invention discloses a flow chart of a method for batch modifying BIOS option values ​​based on a redfish interface. DETAILED DESCRIPTION

[0034] The present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not intended to limit the scope of protection of the present invention.

[0035] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other.

[0036] It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0037] It should be noted that the modifications of "one" and "plurality" mentioned in the present invention are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0038] The names of the messages or information exchanged between multiple devices of the present invention are only used for illustrative purposes, and are not used to limit the scope of these messages or information.

[0039] The present invention will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0040] Figure 1 The present invention is a flow chart of a method for batch modifying BIOS option values ​​based on the redfish interface, which specifically includes the following steps:

[0041] Step 101, obtain customer customization information corresponding to the server cluster to be configured, generate a BIOS configuration file group and a configuration quantity corresponding to each BIOS configuration file according to the customer customization information; divide the server cluster to be configured according to the configuration quantity corresponding to each BIOS configuration file, and obtain a server group corresponding to each BIOS configuration file, the number of servers included in the server group matches the configuration quantity corresponding to the BIOS configuration file, and the BIOS configuration file includes multiple BIOS option names that need to be modified and an update value corresponding to each BIOS option name.

[0042] In some embodiments, the execution subject of the method for batch modifying BIOS option values ​​based on the redfish interface of the present invention may be a user terminal. As an example, the user terminal may be a computer, a mobile phone, etc.

[0043] In practice, redfish is a modern, open and standardized remote management and monitoring interface that uses JSON or OData format for data exchange. The execution subject establishes a communication connection with the background server through various communication methods. On this basis, the customer customized information corresponding to the server cluster to be configured is obtained from the background server through the redfish interface. It can be understood that the background server is different from the server in the server cluster to be configured. The customer customized information is the customer's demand to modify the specific BIOS configuration options of the server.

[0044] In practice, the BIOS option values ​​that need to be modified in the corresponding server group are modified in batches by modifying the BIOS configuration file. The BIOS configuration file includes multiple BIOS option names that need to be modified and the update value corresponding to each BIOS option name. For example, define the first string of each line as the option name, the first string after the colon as the new option value, and ignore the leading and trailing spaces.

[0045] In practice, a BIOS configuration file group and the configuration quantity corresponding to each BIOS configuration file are generated through customer customization information; then, the server cluster to be configured is divided according to the configuration quantity corresponding to each BIOS configuration file to obtain the server group corresponding to each BIOS configuration file, and the number of servers contained in the server group matches the configuration quantity corresponding to the BIOS configuration file. As an example, the customer customization information is: the customer ordered 10 servers, of which 3 use the first configuration file and the other 7 use the second configuration file. The configuration file group of this example includes two configuration files, the first configuration file and the second configuration file, and the corresponding configuration quantities are 3 and 7 respectively. According to the configuration quantities corresponding to the two configuration files, the 10 servers to be configured are divided to obtain the server group a corresponding to the first configuration file and the server group b corresponding to the second configuration file. The configuration quantity corresponding to the server group a is 3, and the configuration quantity corresponding to the server group b is 7. At this point, the two configuration files and their configuration quantities in the configuration file group in this example correspond one-to-one to the server groups divided above. By modifying the BIOS configuration file, the BIOS configuration information that needs to be modified in the corresponding server group can be modified in batches.

[0046] Step 102, for each server group, send the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group. When the update script runs, the current BIOS configuration information of the current server is obtained through the redfish interface, and the current BIOS configuration information is parsed to obtain the URL path corresponding to each BIOS option name in the current server. According to the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name, an option value modification request is constructed to modify the BIOS option value of the current server, generate an update record and send the update record to the configuration end.

[0047] In some embodiments, the execution subject has locally stored a pre-configured update script and a BIOS configuration file corresponding to each server group in the above-mentioned server cluster. Among them, the script is an extension of the batch file, which is a program saved in plain text, and can usually be temporarily called and executed by an application. As an example, the BIOS option value of one of the server groups is modified, for example, server group a. The remaining server groups in the above-mentioned server cluster perform similar operations. Server group a includes server 1, server 2 and server 3. For server group a, the pre-configured update script and the first configuration file corresponding to server group a are sent to each server in server group a, and the update script is run. The current BIOS configuration information of server 1, server 2 and server 3 is obtained through the redfish interface, and the current BIOS configuration information is parsed to obtain the URL path corresponding to each BIOS option name in server 1, server 2 and server 3. Through the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name, an option value modification request is constructed to modify the BIOS option values ​​of server 1, server 2 and server 3, generate an update record and send the update record to the configuration end.

[0048] In these embodiments, the requirements of different customers for BIOS option configuration in factory server production are modified in batches. Specifically, different customers have different requirements for server BIOS option configuration. On this basis, BIOS configuration file groups and the number of configurations corresponding to each BIOS configuration file are generated in a targeted manner according to customer customization information. After that, the server cluster to be configured is divided to obtain the server group corresponding to each BIOS configuration file, and then each server group is configured in a targeted manner. This specifically solves the need to import a specific BIOS version into the production line production process to update the BIOS to meet customer needs. This improves the efficiency of different customers' requirements for BIOS option configuration and ensures timeliness.

[0049] In some embodiments, in order to further solve the second technical problem described in the background technology section, that is, "the existing method for determining qualified update records is backward, resulting in a complicated process for submitting customer customized information", in some embodiments of the present invention, before obtaining the customer customized information corresponding to the server cluster to be configured, it also includes:

[0050] Step 1: Obtain multiple update records within a historical time period, wherein each update record includes an update timestamp, a customer identifier, an update BIOS option name and an update value corresponding to the update BIOS option name, a customer type, a server order quantity, and a business scenario.

[0051] In some embodiments, the execution subject has stored multiple update records locally. Each update record includes an update timestamp, a customer identifier, an update BIOS option name and an update value corresponding to the update BIOS option name, a customer type, a server order quantity, and a business scenario. The timestamp is used to represent a point in time. The customer identifier is used to uniquely identify the customer. The customer identifier can be used to better identify the customer, thereby providing personalized products and services to the customer. Customer types can be divided according to different standards, including: consumer customers, intermediary customers, internal customers, and public benefit customers. In addition, according to comprehensive factors such as customer value, demand, and preference, they can also be divided into VIP customers, important customers, ordinary customers, loyal customers, old customers, new customers, and potential customers. The business scenario is a usage scenario of the server, for example, an industrial control scenario, data storage. On this basis, multiple update records within a historical time period are obtained.

[0052] Step two, according to the customer type included in each update record, divide the multiple update records into multiple update record groups, each update record group corresponds to one customer type, and multiple update record groups correspond to multiple customer types; according to the business scenarios included in the update records, divide each update record group to obtain update record subgroups corresponding to each customer type, and each update record subgroup corresponds to a business scenario.

[0053] In some embodiments, multiple update records are divided into multiple update record groups by the customer type included in each update record, so that each update record group corresponds to a customer type, and multiple update record groups correspond to multiple customer types; each update record group is divided by the business scenario included in the update record to obtain an update record subgroup corresponding to each customer type, and each update record subgroup corresponds to a business scenario. As an example, there are 20 update records in a certain historical time period. Among them, there are a total of 3 customer types, namely, customer type 1, customer type 2, and customer type 3. Then the corresponding update record groups are update record group 1, update record group 2, and update record group 3. Among them, update record group 1 has 10 update records, update record group 2 has 6 update records, and update record group 3 has 4 update records. The three update record groups divided above are divided again by the business scenarios included in each update record therein, and divided into update record subgroups. Among them, in update record group 1, there are business scenarios 1, 2, and 3, which correspond to 5 update records, 3 update records, and 2 update records, respectively. Then, the update record subgroups corresponding to business scenarios 1, 2, and 3 are update record subgroup 1, update record subgroup 2, and update record subgroup 3; in update record group 2, there are business scenarios 4 and 5, which correspond to 4 update records and 2 update records, respectively. Then, the update record subgroups corresponding to business scenarios 4 and 5 are update record subgroup 4 and update record subgroup 5; in update record group 3, there is business scenario 6, which corresponds to 4 update records, and then, the update record subgroup corresponding to business scenario 6 is update record subgroup 6. Finally, the update record subgroups corresponding to each customer type are obtained, and each update record subgroup corresponds to a business scenario.

[0054] Step three, when receiving a configuration page acquisition request sent by the target user through the target user terminal, the configuration page is sent to the target user terminal, so that the target user submits the customized information in the configuration page.

[0055] In some embodiments, the target user establishes a communication connection with the background server through the target user terminal and sends a configuration page acquisition request to the background server. After receiving the request, the background server sends the configuration page to the target user terminal so that the target user submits customer customization information in the configuration page.

[0056] On this basis, obtain the customer-customized information corresponding to the server cluster to be configured, including:

[0057] When receiving the target customer identifier and the target business scenario submitted by the target user in the configuration page, the target customer identifier is queried in multiple update records, and if there is an update record matching the target customer identifier in the multiple update records, the matching update record is determined as the target update record;

[0058] The target update record is sent to the target user terminal, and the target user terminal is controlled to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

[0059] In some embodiments, when the backend server receives the target customer identifier and target business scenario submitted by the target user in the configuration page, the target customer identifier is used to query the update record matching it in multiple update records within the historical time period, and the matching update record is determined as the target update record. The target update record is sent to the target user terminal, and the target user terminal is controlled to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page. As an example, the target user submits the target customer identifier 2 and the target business scenario 4 to the backend server in the configuration page, and uses the target customer identifier 2 to query whether there is a target business scenario 4 under the corresponding customer type in multiple update records within the historical time period. If there is, then the update record subgroup corresponding to the target business scenario 4 is determined as the target update record. The backend server sends this target update record to the target user terminal, and displays the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page by controlling the target user terminal. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

[0060] Obtain the customer-customized information corresponding to the server cluster to be configured, including:

[0061] If there is no update record matching the target customer identifier among the multiple update records, the customer type corresponding to the target customer identifier is determined as the target customer type, and the customer type with the highest degree of matching with the target customer type is determined from the multiple customer types, and the customer type with the highest degree of matching is determined as the matching customer type;

[0062] According to the target business scenario, a business scenario with the highest matching degree with the target business scenario is determined from multiple business scenarios corresponding to the matching customer type, and is determined as the matching business scenario;

[0063] Recommended configuration information is generated according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page.

[0064] In some embodiments, among the multiple update records within the historical time period, there is no update record matching the target customer identification and target business scenario submitted by the target user in the configuration page in the server backend. Then, the customer type corresponding to the above target customer identification can be determined as the target customer type, and the customer type with the highest degree of matching with the target customer type can be determined from the multiple customer types, and it can be determined as the matching customer type. Then, through the above target business scenario, the business scenario with the highest degree of matching with the above target business scenario can be determined from the multiple business scenarios corresponding to the matching customer type, and it can be determined as the matching business scenario. Then, the recommended configuration information is generated by the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page. As an example, the target customer identification A and the target business scenario a submitted by the target user in the configuration page cannot find a matching target update record in the multiple update records within the historical time period of the server backend. In the update records in the historical time period of the server background, the customer types include customer type A1, customer type B2, and customer type C3, and the corresponding update record groups are update record group A1, update record group B2, and update record group C3. The business scenarios include business scenario a1, business scenario b1, business scenario c1, and business scenario d1. By business scenario, each update record group above is divided. Update record group A1 has business scenario a1 and business scenario d1, which correspond to update record subgroup a1 and update record subgroup d1 respectively. Update record group B1 has business scenario b1, and business scenario b1 corresponds to update record subgroup b1; Update record group C1 has business scenario c1, and business scenario c1 corresponds to update record subgroup c1. The customer type corresponding to the target customer identifier A is determined as the target customer type A, and the customer type A1 with the highest degree of matching with the target customer type A is found among the above-mentioned customer types A1, customer type B1, and customer type C1, and customer type A1 is determined as the matching customer type; through the target business scenario a, the business scenario a1 with the highest degree of matching with the target business scenario a is found from the business scenarios a1 and business scenarios d1 in the matching customer type A1, and the business scenario a1 is determined as the matching business scenario; the recommended configuration information is generated by the update record subgroup a1 corresponding to the above-mentioned matching business scenario a1; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

[0065] For each server group, a pre-configured update script and a BIOS configuration file corresponding to the server group are sent to each server in the server group, including:

[0066] According to the manufacturer information of each server, an update script matching the manufacturer information of each server is selected from a pre-configured update script library, and the matching update script is sent to the corresponding server.

[0067] In some embodiments, there is a need to configure servers produced by different manufacturers. In this case, different manufacturers correspond to different server groups. The background server will pre-configure matching update scripts for different manufacturers. When needed, only the matching update scripts need to be sent to the corresponding servers of different manufacturers.

[0068] In these embodiments, the target user sends a configuration page acquisition request to the backend server through the target user terminal, and the backend server sends the configuration page to the target user terminal, so that the target user submits the customized information in the configuration page. The backend server determines the target update record that matches it, sends the target update record to the target user terminal, and controls the target user terminal to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page. In this way, in the process of submitting customized information, the target user terminal displays the update record that meets the conditions, thereby providing reference information for user customization and facilitating the rapid submission of customized information.

[0069] In some embodiments, in order to further solve the technical problem 3 described in the background technology section, that is, "in the process of BIOS configuration information, when there is a problem with the server configuration, there is insufficient troubleshooting method", in some embodiments of the present invention,

[0070] Each update record also includes the configuration duration for each BIOS option; on this basis, the method of the present invention also includes:

[0071] Step 1: Count the average configuration time for BIOS options based on multiple update records.

[0072] In some embodiments, the target user can modify the BIOS configuration information that needs to be modified in the corresponding server group in batches by modifying the BIOS configuration file at the target user terminal. In the process of BIOS configuration information, it is inevitable that there will be problems with the configuration of the server, so it is necessary to find out which server has a configuration problem and solve it in time. To know which server has a configuration problem, a more intuitive way is to count the average configuration time for the BIOS option. The configuration time corresponding to the same BIOS option is consistent.

[0073] Step 2: During the running of the update script, configuration progress information sent by each server in the server cluster to be configured is received, and actual configuration time for each BIOS option of each server in the server cluster to be configured is counted.

[0074] In some embodiments, the target user runs an update script on the target user terminal, receives configuration progress information sent by each background server, and counts the actual configuration time for each BIOS option of each server in the server cluster to be configured.

[0075] Step three: if the actual configuration time is longer than the average configuration time, the corresponding BIOS option is determined as the BIOS option to be checked, and the corresponding server is determined as the server to be checked.

[0076] In some embodiments, if the actual configuration time of a server in the server cluster to be configured is longer than the average configuration time, the BIOS options corresponding to the servers in the server cluster to be configured are determined as BIOS options to be checked, and the corresponding servers are determined as servers to be checked.

[0077] Step 4: Send the information of the BIOS option to be checked and the server to be checked to the checking terminal, so that the checking personnel can check the BIOS option to be checked and the server to be checked.

[0078] In some embodiments, the servers in the server cluster to be configured send information about the BIOS options to be checked and the servers to be checked to the checking terminal, so that the checking personnel can check the BIOS options to be checked and the servers to be checked.

[0079] In these embodiments, by counting the actual configuration time for each BIOS option of each server in the server cluster to be configured, the BIOS options to be checked and the servers to be checked are determined, thereby optimizing the troubleshooting method and avoiding missing problems.

[0080] The above descriptions are only some preferred embodiments of the present invention and the explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present invention is not limited to the technical solutions formed by the specific combination of the above technical features, but also should cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present invention (but not limited to) to form a technical solution.

Claims

1. A method for batch modifying BIOS option values ​​based on redfish interface, characterized in that: include: Obtaining customer customization information corresponding to the server cluster to be configured, and generating a BIOS configuration file group and a configuration quantity corresponding to each BIOS configuration file according to the customer customization information; According to the configuration quantity corresponding to each BIOS configuration file, the server cluster to be configured is divided to obtain a server group corresponding to each BIOS configuration file, the number of servers included in the server group matches the configuration quantity corresponding to the BIOS configuration file, and the BIOS configuration file includes multiple BIOS option names that need to be modified and an update value corresponding to each BIOS option name; For each server group, a pre-configured update script and a BIOS configuration file corresponding to the server group are sent to each server in the server group. When the update script is running, the current BIOS configuration information of the current server is obtained through the redfish interface, and the current BIOS configuration information is parsed to obtain the URL path corresponding to each BIOS option name in the current server. According to the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name, an option value modification request is constructed to modify the BIOS option value of the current server, generate an update record and send the update record to the configuration end.

2. The method for batch modifying BIOS option values ​​based on the redfish interface according to claim 1, characterized in that: Before obtaining the customer customized information corresponding to the server cluster to be configured, the method further includes: Acquire multiple update records within a historical time period, wherein each update record includes an update timestamp, a customer identifier, an update BIOS option name and an update value corresponding to the update BIOS option name, a customer type, a server order quantity, and a business scenario; According to the customer type included in each update record, the multiple update records are divided into multiple update record groups, each update record group corresponds to a customer type, and the multiple update record groups correspond to multiple customer types; according to the business scenarios included in the update records, each update record group is divided to obtain update record subgroups corresponding to each customer type, and each update record subgroup corresponds to a business scenario; and Before obtaining the customized information corresponding to the server cluster to be configured, the method further includes: upon receiving a configuration page acquisition request sent by a target user through a target user terminal, sending the configuration page to the target user terminal so that the target user submits the customized information in the configuration page; and The obtaining of customer customized information corresponding to the server cluster to be configured includes: When receiving the target customer identifier and the target business scenario submitted by the target user in the configuration page, querying the target customer identifier in the multiple update records, and if an update record matching the target customer identifier exists in the multiple update records, determining the matching update record as the target update record; The target update record is sent to the target user terminal, and the target user terminal is controlled to display the historical configuration information viewing component and the historical configuration viewing prompt information in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

3. The method for batch modifying BIOS option values ​​based on the redfish interface according to claim 2, characterized in that: The step of obtaining the customer customized information corresponding to the server cluster to be configured further includes: If there is no update record matching the target customer identifier among the multiple update records, determining the customer type corresponding to the target customer identifier as the target customer type, and determining the customer type with the highest degree of matching with the target customer type from the multiple customer types, and determining the customer type with the highest degree of matching as the matching customer type; According to the target business scenario, determining a business scenario with the highest matching degree with the target business scenario from the multiple business scenarios corresponding to the matching customer types, and determining it as the matching business scenario; Generate recommended configuration information according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

4. The method for batch modifying BIOS option values ​​based on the redfish interface according to claim 3, characterized in that: The step of obtaining the customer customized information corresponding to the server cluster to be configured further includes: If there is no business scenario matching the target business scenario among the multiple business scenarios corresponding to the matching customer type, then for the update record subgroup corresponding to each business scenario in the multiple business scenarios, determining an average update timestamp corresponding to each update record subgroup; According to the average update timestamp and current time corresponding to each update record subgroup, the update record subgroup closest to the current time is selected from multiple business scenarios, and recommended configuration information is generated based on the update record subgroup closest to the current time; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

5. The method for batch modifying BIOS option values ​​based on the redfish interface according to claim 4, characterized in that: For each server group, sending a pre-configured update script and a BIOS configuration file corresponding to the server group to each server in the server group includes: According to the manufacturer information of each server, an update script matching the manufacturer information of each server is selected from a pre-configured update script library, and the matching update script is sent to the corresponding server.

Images