TW201328248A - Method for updating system firmware and server system using the same - Google Patents

Abstract

A method for updating a system firmware is suitable to a server system with a plurality of nodes. The method includes the following steps. A firmware updating package data is received. The nodes needed to update are searched in a lookup table according to the firmware updating package data and a node information corresponding to each of the nodes. A priority corresponding to each of the nodes is arranged according to an updating sequence policy, and an updating list is established according the priority. A firmware updating is performed for nodes and the node information corresponding to each of the nodes and the updating list are updated in sequence according to the updating list.

Description

System firmware update method and server system using the same

A firmware update method, in particular, relates to a system firmware update method and a server system using the same.

With the development of technology, computers around the world can be connected through the Internet. A computer can exchange data and access data with another computer through a network connection. On the client and server system architecture, the client and server communicate through the network.

In general, a server system can be configured with multiple nodes, and each node runs multiple virtual machines (VMs) at the same time, thereby providing each user with a separate operating environment. Moreover, each node can be regarded as a separate computer, that is, each node has a memory, a storage space, a computing capability, and a network connection function. Therefore, each node can run a separate operating system, and each node can also communicate and transmit data through a network switch (Switch).

After the server system is running, the firmware of the node needs to be updated because of the new firmware version. In the prior art, when the firmware update is received by the server system, the firmware update is performed on the node that needs to be updated, and the firmware update mode is to perform the firmware update on a certain node. It is isolated from the operation of the server system, and the node is added to the operation of the server system after the firmware update is completed. However, if the server system performs firmware update of a large number of nodes, or performs firmware update under a large load of the node, the operation performance of the server system will be affected, resulting in inconvenience in use.

In view of the above problems, the present invention provides a system firmware update method and a server system using the same, in order to avoid affecting the operational efficiency of the server system, complete the required firmware update to the server system.

A system firmware update method according to the present disclosure is suitable for a server system having a plurality of nodes, for example, a container data center for providing Infrastructure as a Service (IaaS) ( Data Center). This system firmware update method includes the following steps. Receive firmware update package information. According to the firmware update encapsulation data and the node information corresponding to each of the foregoing multiple nodes, the nodes that need to be updated are searched by means of table lookup. According to the update order policy, the corresponding priority order of the nodes is arranged, and the update list is established in priority order. According to the update list, the node is firmware updated in sequence, and the corresponding node information and update list of the nodes are updated.

In an embodiment, the step of sequentially performing firmware update on the node includes the following steps. According to the update list, the node with the highest priority is selected as the update node among the plurality of nodes. The update node is updated, and the node information corresponding to the update node is updated, and the update node is removed from the update list. According to the update list, it is detected whether all nodes are updated. If it is detected that all nodes have not been updated, it is determined whether the number of node updates reaches a critical value. If it is determined that the number of updates of the node does not reach the critical value, the process returns to the update list, and the node with the highest priority is selected as the update node by the node. If it is determined that the number of updates of the node reaches a critical value, waiting for a predetermined time, and then returning to the update list, the node having the highest priority is selected as the update node by the node.

In an embodiment, the aforementioned system firmware update method. Determine whether the load of the update node exceeds the preset value. If it is determined that the load of the update node exceeds the preset value, the process returns to the update list, and the node with the highest priority is selected as the update node by the node. If it is determined that the load of the update node does not exceed the preset value, the step of updating the update node is entered.

In an embodiment, the step of updating the update node includes the following steps. Determine if the update node is running the operating system. If it is judged that the update node runs the operating system, the firmware update data of the firmware update package data is used to perform the online firmware update to update the update node. If it is judged that the update node is not running the operating system, the image file of the firmware update package data is used to open the operating system to perform an offline firmware update to update the update node.

A server system of the present disclosure includes a plurality of nodes, a database, and an update module. Each of the plurality of nodes has node information. The database is used to store the aforementioned node information. The update module is coupled to the plurality of nodes and the database for receiving the firmware update package data, and updating the package data and the node information according to the firmware, searching for the node to be updated in a table lookup manner, and then updating the order policy according to the update order Arranging the corresponding priority order of the nodes, and establishing an update list in priority order, storing the update list in the database, and performing firmware update on the nodes according to the update list, and updating the node information and the update list.

In an embodiment, the foregoing update module further selects, according to the update list, the node with the highest priority in the node as the update node, updates the update node, updates the node information corresponding to the update node, and updates the update node by The list is removed, and the update module detects whether all nodes are updated according to the update list. If it is detected that all nodes are not updated, the update module determines whether the number of node updates reaches a critical value, and if the number of nodes is updated. If the critical value is not reached, the update module again selects the node with the highest priority as the update node according to the update list, so as to update the update node until all nodes update are completed, and if the update number of the node reaches the critical value When the value is updated, the update module waits for a predetermined time, and according to the update list, the node with the highest priority is selected as the update node by the node to update the update node until all node updates are completed.

In an embodiment, the update module determines whether the load of the update node exceeds a preset value. If it is determined that the load of the update node exceeds a preset value, the update module again selects the highest priority order among the nodes according to the update list. The node acts as an update node, and if it is determined that the load of the update node does not exceed the preset value, the update module updates the update node.

In an embodiment, the update module determines whether the update node runs the operating system. If it is determined that the update node runs the operating system, the update module uses the firmware update firmware of the firmware update package data to perform online firmware update to update the node. If the update node does not run the operating system, the update module uses the image file of the firmware update package data to open the operating system to perform an offline firmware update to update the update node.

A system firmware update method and a server system using the same, by receiving a user upload firmware update package information, and searching for nodes that need to be updated and arranging the update order of the nodes to automatically complete Online or offline updates of nodes. In this way, the convenience of use of the server system can be effectively increased. In addition, it is also possible to decide whether to update according to the load of the update node and the number of nodes that have completed the update, so as to avoid affecting the operational performance of the server system.

The features and implementations of the present disclosure are described in detail below with reference to the drawings.

Please refer to "Figure 1" for a block diagram of the server system disclosed herein. The server system 100 includes a plurality of nodes 110_1 110 110_N, a database 120 and an update module 130, where N is a positive integer greater than one. The server system 100 is, for example, a Container Data Center that provides Infrastructure as a Service (IaaS).

The nodes 110_1~110_N each have node information. The node information includes, for example, a product number of the node, such as a Universally Unique Identifier (UUID), a firmware version of a Node's Basic Input Output System (BIOS), and a baseboard management controller of the node ( The firmware version of the Baseboard Management Controller (BMC). For example, the node information of the node 110_1 is represented by, for example, "110_1, version 1, version 2", and the remaining nodes 110_2~110_N are analogous.

The database 120 is used to store node information of the nodes 110_1~110_N. In this embodiment, for example, the node information of each of the nodes 110_1 110 110_N can be obtained by the baseboard management controller, and each node information is stored in the database 120. The update module 130 is coupled to the nodes 110_1 110 110_N and the database 120 for receiving the firmware update package information. The firmware update package data can be uploaded by the client to the update module of the server system 100 through the network, so that the update module can use the firmware update package data to perform firmware update on the server system 100.

Then, the update module 130 searches for the node that needs to be updated in a table lookup manner according to the firmware update encapsulation data and the foregoing node information. The firmware update package information has, for example, an update data list, and the update data list includes the product number of the node to be updated and its firmware version. Therefore, the update module can search for the node that needs to be updated according to the foregoing updated data list and node information. For convenience of explanation, the nodes that need to be updated take the nodes 110_1, 110_2, and 110_3 as an example.

After finding the node that needs to be updated, the update module 130 arranges the priority order corresponding to each of the nodes 110_1 110 110_3 according to the update order policy, and creates an update list in priority order and stores the update list in the database 120. In this embodiment, the nodes 110_1~110_N can be divided into a service node (Service Node), a computing node (Computing Node), and a storage node (Storage Node), wherein the service node is used to provide related services and materials to the client, and the operation node Used for data calculation, the storage node is used to store data.

For example, the foregoing update sequence policy is, for example, a service node, a storage node, and a compute node, and the node 110_1 is, for example, a storage node, the node 110_2 is, for example, an operation node, and the node 110_3 is, for example, a service node. Therefore, with the update sequence policy described above, the update order arranged by the update module 130 is the nodes 110_3, 110_1, and 110_2, and is established in the update list in this update order.

Then, the update module 130 performs firmware update on the nodes 110_3, 110_1, and 110_2 according to the update list, and updates the node information of the nodes 110_3, 110_1, and 110_2 and updates the update list. In this way, the server system 100 of the embodiment can automatically perform firmware update on the node that needs to perform firmware update with less impact on efficiency.

Hereinafter, the detailed operation of the firmware update of the update module 130 of the present embodiment will be further described.

First, the update module 130 selects the node with the highest priority among the nodes 110_1~110_3 as the update node according to the update list to update the update node. Since the priority order of the node 110_3 is the highest, the update module 130 preferentially selects the node 110_3 as an update node to update the update node 110_3. Moreover, after the firmware update is completed, the update module 130 updates the node information of the node 110_3, for example, "110_3, version 1, version 3". And, the update node 110_3 is removed from the update list, and therefore, only the nodes 110_1, 110_2 remain in the update list.

Next, the update module 130 detects whether all nodes are updated according to the update list. Since the nodes 110_1 and 110_2 still exist in the update list, the update module 130 detects that all nodes have not been updated, and the update module 130 further determines whether the number of node updates reaches a critical value. Since the update node must be isolated from the operation of the server system 100 during the firmware update of the node, and the update node is added to the operation of the server system after the firmware update is completed, the server system may be lowered. 100 operational efficiency. It can be seen that a large number of firmware updates of the nodes may greatly reduce the operational efficiency of the server system 100. Therefore, the user can set the number of nodes (ie, threshold values) for each firmware update to avoid affecting the operational efficiency of the server system 100.

Assuming that the threshold is set to 2, the maximum number of nodes for each firmware update is two, but the disclosure is not limited thereto. Since only the firmware update of the node 110_3 is performed, the update module 130 determines that the number of updates of the node does not reach the critical value. Then, the update module 130 selects the node with the highest priority among the nodes 110_1~110_2 as the update node according to the update list. Since only the nodes 110_1, 110_2 remain in the update list, and the priority order of the node 110_1 is higher than the node 110_2, the update module 130 selects the node 110_1 as the update node to update the node 110_1.

After that, the update module 110 updates the node information of the node 110_1, for example, "110_1, version 1, version 3". Afterwards, the update module 130 continues to select the node with the highest priority among the nodes to be updated according to the update list, for firmware update until all node updates are completed.

On the other hand, when the update module 130 updates the nodes 110_3, 110_1, the number of nodes completing the update has reached two. At this time, the update module 130 determines that the number of updates of the node reaches a critical value, so the update module 130 waits for a predetermined time, and according to the update list, the node with the highest priority is selected as the update node by the node to update the node. Update until all node updates are complete. The predetermined time can be adjusted by the user, for example, 6 hours, half a day, or one day, to avoid the firmware update of the node to reduce the operating efficiency of the server system 100.

The update module 130 can further determine whether the load of the update node exceeds a preset value. The preset value is set, for example, to 60% of the full load of the node. That is to say, the update node has a load of less than 60% of its full load, and the update module 130 performs firmware update on the update node, thereby reducing the impact on the operational efficiency of the server system 100.

If it is judged that the load of the update node exceeds the preset value, it indicates that the node is performing calculation or transmission of a large amount of data. In order not to affect the operational efficiency of the server system 100, the update module 130 continues to select the node with the highest priority among the nodes as the update node according to the update list. On the other hand, if it is determined that the load of the update node does not exceed the preset value, the update module 130 can update the update node. In this way, the firmware update of the node system under high load can be avoided, and the operating efficiency of the server system 100 can be reduced.

In addition, when performing firmware update on the update node, the update module 130 can further determine whether the update node runs the operating system (OS), that is, determine whether the update node is in the normal operation mode or in the standby mode. If it is determined that the update node runs the operating system, indicating that the update node is in the normal operation mode, the update module 130 performs firmware update on the firmware by using the firmware update information of the firmware update package data to update the update node.

For example, the update module 130 can further determine the type of the firmware version, such as the firmware update of the basic input/output system or the baseboard management controller. If it is determined that the type of firmware update is a basic input/output system or a baseboard management controller, the update module 130 unpacks the firmware update package data into a firmware update tool for the basic input/output system or the baseboard management controller. The firmware update data is updated to the update node. And, after the firmware update is completed, the update node is rebooted (Reboot), and the baseboard management controller is reset to update the node's basic input/output system or the baseboard management controller to operate with the new firmware. In addition, after the basic I/O system update is completed, an Intelligent Platform Management Interface (IPMI) command is transmitted to the baseboard management controller to inform the update status to update the node information of the update node and update the list.

If it is determined that the type of the firmware update is the baseboard management controller, the update module 130 extracts the firmware update data of the baseboard management controller from the firmware update package data, and then executes the baseboard management controller by using the smart platform management interface command. Firmware update. Moreover, after the firmware update is completed, the baseboard management controller of the update node is reset, so that the baseboard management controller of the update node operates with the new firmware.

On the other hand, if it is determined that the update node is not running the operating system, indicating that the update node is in the standby mode, the update module uses the firmware file to update the package file (ISO file) to open the operating system to perform offline firmware update. Update the node for updates. Wherein, the foregoing image file may include a Bootable OS and an automatic execution file, and the update node may run the foregoing operating system.

For example, the update module 130 can further determine the type of the firmware version, such as the firmware update of the basic input/output system or the baseboard management controller. If it is determined that the type of firmware update is a basic input/output system, the update module 130 mounts an image file of the firmware update package data to the update node, so that the update node is booted from the image file, and is executed during the boot process. The foregoing automatic execution file is used to update the firmware of the basic input/output system or the baseboard management controller (for example, the update module 130 updates the image of the package data by firmware update the baseboard management controller of the node. The optical disc of the virtual optical disc drive is set as the baseboard management controller, and the update node is used to update the node to start the operating system by the virtual optical disc drive, but not limited thereto.

And, after the firmware update is completed, the update node is rebooted (Reboot), and the baseboard management controller is reset to update the node's basic input/output system or the baseboard management controller to operate with the new firmware. In addition, after the basic input/output system update is completed, the smart platform management interface command is transmitted to the baseboard management controller to inform it of the update status, so as to update the node information of the update node and update the list.

If it is determined that the type of the firmware update is the baseboard management controller, the update module 130 extracts the firmware update data of the baseboard management controller from the firmware update package data, and then executes the baseboard management controller by using the smart platform management interface command. Firmware update. Moreover, after the firmware update is completed, the baseboard management controller of the update node is reset, so that the baseboard management controller of the update node operates with the new firmware.

Please refer to "Figure 2" for a flowchart of the system firmware update method disclosed herein. The system firmware update method of this embodiment is suitable for a server system, and the server system has a plurality of nodes. In step S210, the firmware is updated to update the package data. In step S220, the node information corresponding to each of the plurality of nodes is updated according to the firmware update, and the plurality of nodes that need to be updated are searched in a table lookup manner. In step S230, according to the update order policy, the priority order corresponding to each of the plurality of nodes is arranged, and the update list is established in priority order. In step S240, the firmware update is performed on the plurality of nodes in sequence according to the update list, and the node information and the update list corresponding to each of the plurality of nodes are updated.

Please refer to "Figure 3" for a flowchart of another system firmware update method disclosed herein. The system firmware update method of this embodiment is suitable for a server system, and the server system has a plurality of nodes. In step S302, the firmware is updated to update the package data. In step S304, the node information corresponding to each of the plurality of nodes is updated according to the firmware update, and a plurality of nodes that need to be updated are searched in a table lookup manner. In step S306, according to the update order policy, the priority order corresponding to each of the plurality of nodes is arranged, and the update list is established in priority order.

In step S308, the node with the highest priority is selected as the update node among the plurality of nodes according to the update list. In step S310, it is determined whether the load amount of the update node exceeds a preset value. If it is determined that the load amount of the update node exceeds the preset value, the process returns to step S308 until it is determined that the load amount of the update node does not exceed the preset value.

On the other hand, if it is judged that the load amount of the update node does not exceed the preset value, the process proceeds to step S312 to update the update node. In step S314, the node information corresponding to the update node is updated, and the update node is removed from the update list. In step S316, based on the update list, it is detected whether all nodes are updated. If it is detected that all nodes have been updated, the process of firmware update of this system is ended.

On the other hand, if it is detected that all the nodes have not been updated, the process proceeds to step S318, and it is determined whether the number of node updates reaches a critical value. If it is determined that the number of updates of the node has not reached the critical value, the process returns to step S308. If it is determined that the number of updates of the node reaches the critical value, the process proceeds to step S320, and the predetermined time is awaited. Next, the process returns to step S308.

In addition, updating the update node in step S312 further includes the following steps S322 to S326. In step S322, it is determined whether the update node runs the operating system. If it is determined that the update node runs the operating system, the process proceeds to step S324, where the firmware update is performed by using the firmware update information of the firmware update package data to update the update node. If it is determined that the update node does not run the operating system, proceed to step S326 to update the operating system by using the firmware update firmware image file to perform an offline firmware update to update the update node.

The system firmware update method of the embodiment of the present disclosure and the server system using the same, which receive the firmware update package information (with online update data and offline update image file) by the user upload firmware, and search for The nodes that need to be updated and the update order of the nodes are arranged to automatically complete the online update or offline update of the node. In this way, the convenience of use of the server system can be effectively increased. In addition, it is also possible to decide whether to update according to the load of the update node and the number of nodes that have completed the update, so as to avoid affecting the operational performance of the server system.

The present disclosure has been disclosed in the foregoing preferred embodiments. However, it is not intended to limit the scope of the disclosure, and it is obvious to those skilled in the art that the present invention can be modified and retouched without departing from the spirit and scope of the disclosure. The scope of patent protection disclosed is subject to the definition of the scope of the patent application attached to this specification.

100. . . Server system

110_1~110_N. . . node

120. . . database

130. . . Update module

Figure 1 is a block diagram of the server system of the present disclosure.

Figure 2 is a flow chart of the method for updating the firmware of the system disclosed herein.

Figure 3 is a flow chart of another system firmware update method disclosed herein.

Claims (8)

A system firmware update method is suitable for a server system, the server system has a plurality of nodes, and the system firmware update method comprises: receiving a firmware update package data; updating the package data and the nodes according to the firmware Corresponding one-node information, searching for the nodes to be updated in a look-up manner; sorting out a priority order corresponding to each of the nodes according to an update order policy, and establishing an update list in the priority order; According to the update list, firmware updates are performed on the nodes in sequence, and the node information corresponding to the nodes and the update list are updated. The system firmware update method of claim 1, wherein the step of performing firmware update on the nodes in sequence comprises: selecting, according to the update list, the node having the highest priority among the nodes as one Updating the node; updating the update node, and updating the node information corresponding to the update node, and removing the update node from the update list; detecting, according to the update list, whether all of the nodes are updated; All of the nodes are not updated, and it is determined whether the number of the node updates reaches a critical value; if it is determined that the number of updates of the nodes does not reach the threshold, then returning to the update list, the selection is prioritized by the nodes. The node having the highest order is the step of updating the node; and if it is determined that the number of updates of the nodes reaches the critical value, waiting for a predetermined time, and returning to the update list, the highest priority is selected among the nodes. The node acts as the step of the update node. The system firmware update method of claim 2, further comprising: determining whether the load of the update node exceeds a preset value; if it is determined that the load of the update node exceeds the preset value, returning According to the update list, the node having the highest priority is selected as the update node among the nodes; and if it is determined that the load of the update node does not exceed the preset value, the step of updating the update node is entered. . The system firmware update method of claim 2, wherein the updating the update node comprises: determining whether the update node runs a work system; and determining that the update node runs the operating system, utilizing the toughness The firmware update data of the body update package data performs an online firmware update to update the update node; and if it is determined that the update node does not run the operation system, the firmware updates the package data to open the image file. The operating system updates the update node by performing an offline firmware update. A server system includes: a plurality of nodes each having a node information; a database for storing the node information; and an update module coupled to the nodes and the database for Receiving a firmware update package data, and updating the package data and the node information according to the firmware, searching for the nodes that need to be updated by means of table lookup, and arranging corresponding nodes according to an update order policy a priority order, and an update list is created in the priority order, and the update list is stored in the database, and firmware updates are performed on the nodes in sequence according to the update list, and the node information is updated and update list. The server system of claim 5, wherein the update module further selects, according to the update list, the node with the highest priority among the nodes as an update node to update the update node. And updating the node information corresponding to the update node, and removing the update node from the update list, and the update module further detects, according to the update list, whether all of the nodes are updated, wherein if all of the nodes are detected After the node is not updated, the update module determines whether the number of the node updates reaches a critical value. If it is determined that the number of updates of the nodes does not reach the threshold, the update module again depends on the update list. The node with the highest priority is selected as the update node to update the update node until all the nodes are updated, and when it is determined that the update quantity of the nodes reaches the critical value, the update mode Waiting for a predetermined time, and according to the update list, selecting the node with the highest priority among the nodes as the The node is updated to update the update node until all of the node updates are complete. The server system of claim 6, wherein the update module determines whether the load of the update node exceeds a preset value, and if it is determined that the load of the update node exceeds the preset value, the update mode The group again selects, according to the update list, the node with the highest priority among the nodes as the update node, and if it is determined that the load of the update node does not exceed the preset value, the update module updates the node. Update. The server system of claim 6, wherein the update module determines whether the update node runs an operating system, and if the update node determines that the update node runs the operating system, the update module uses the firmware to update the package data. The firmware update data performs an online firmware update to update the update node, and if it is determined that the update node is not running the operating system, the update module uses the firmware to update an image of the package data. The operating system updates the update node by performing an offline firmware update.