TWI554876B - Method for processing node replacement and server system using the same - Google Patents

Description

Node replacement processing method and server system using the same

A node replacement processing technique, in particular, relates to a node replacement processing 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 server system may cause node replacement due to detection of a node error or impending error, the user suddenly removing the node and then reinstalling it, or the server system maintenance is performed. However, in the prior art, when a node performs replacement (that is, the original node is removed and replaced by a new node or the node is removed and then replaced), the operating system and the software package need to be reinstalled for the node. data. However, if the node is replaced and the node is removed and replaced, and the node already has the operating system and software package data, the system will reinstall the operating system and software package data for this node. As such, the efficiency of the server system will be reduced.

In view of the above problems, the present disclosure provides a node replacement processing method and a server system using the same, thereby automatically identifying whether a node needs to reinstall related operating systems and software package materials, thereby avoiding reconfiguration of the operating system every time node replacement is performed. With software, the efficiency of the server system is reduced.

A node replacement processing method of the present disclosure is suitable for a server system, such as a Container Data Center providing Infrastructure as a Service (IaaS). This node replacement processing method includes the following steps. Receive node information of the node to get the node type. Power on the node. Start the operating system of the node. Check the software package data of the operating system and the node to generate a check result. Determine whether the check result meets the requirements of the node type. If it is judged that the check result meets the requirements of the node type, the node is added to the server system. If it is judged that the check result does not meet the requirements of the node type, install the operating system and the software package data to the node according to the node type and the installation file.

In an embodiment, the foregoing node replacement processing method further includes the following steps. Perform a self-boot test procedure. Determine if the node has a network boot mode. If it is determined that the node does not have the network boot mode, then the step of starting the operating system of the node is entered. If it is determined that the node has the network boot mode, the step of installing the operating system and the software package data to the node according to the node type and the installation file is entered.

In an embodiment, the foregoing node replacement processing method further includes the following steps. Determine whether the operating system is started at the preset time. If it is determined that the operating system is started at the preset time, the software package information of the operating system and the node is checked to generate a check result. If it is determined that the operating system has not been started at the preset time, the node's boot flag setting has a network boot mode, and the node is rebooted, and returns to the step of executing the self-boot test procedure.

In an embodiment, the foregoing node replacement processing method further includes the following steps. Set the boot flag of the node to the network boot mode. Reboot the node and return to the step of performing the self-boot test procedure.

In an embodiment, the step of determining whether the check result meets the requirements of the node type includes the following steps. If it is judged that the inspection result partially meets the requirements of the node type, it is judged whether the operating system meets the requirements of the node type. If it is judged that the operating system meets the requirements of the node type, the software package data is installed to the node according to the node type. If it is determined that the operating system does not meet the requirements of the node type, the node's boot flag setting has the network boot mode and the node is rebooted, and returns to the step of executing the self-boot test procedure.

A server system of the present disclosure includes a node, a capture unit, a control unit, an inspection unit, and a determination unit. The aforementioned node has node information. The capturing unit is coupled to the foregoing node for extracting node information to obtain a node type of the node. The control unit is coupled to the foregoing node and the capturing unit for controlling the node to be powered on and starting the operating system of the node. The checking unit is coupled to the foregoing node for checking the operating system of the node and the plurality of software package materials to generate an inspection result. The determining unit is coupled to the checking unit, the control unit and the capturing unit for receiving and determining whether the checking result meets the requirement of the node type. If the judgment result meets the requirement of the node type, the control unit adds the node to the server system. If the check result does not meet the requirement of the node type, the control unit installs the operating system and the software package data to the node according to the node type and the installation file. .

In an embodiment, the control unit control node performs a self-boot test procedure, and the determining unit determines whether the node has a network boot mode, wherein if the node is determined to have no network boot mode, the control unit controls the node to start the operating system, if When the node is determined to have a network booting mode, the control unit installs the operating system and the software package data to the node according to the node type and the installation file.

In an embodiment, the determining unit determines whether the operating system is started at a preset time. If it is determined that the operating system is started at the preset time, the checking unit checks the software package information of the operating system and the node to generate an inspection result. It is judged that the operating system is not started at the preset time, and the control unit sets the boot flag of the node to the network boot mode, so that the node is restarted, the node performs the self-boot test procedure, and the determining unit determines that the node has the network. The way of starting the circuit enables the control unit to install the operating system and the software package data to the node according to the node type and the installation file.

In an embodiment, the foregoing control unit sets the boot flag of the node to a network boot mode, and restarts the node, so that the node performs a self-boot test procedure, and the determining unit determines that the node has a network boot mode. The control unit is configured to install the operating system and the software package data to the node according to the node type and the installation file.

In an embodiment, if the foregoing checking result partially meets the requirement of the node type, the determining unit determines whether the operating system meets the requirement of the node type, wherein if the operating system is determined to meet the requirement of the node type, the control unit installs the software according to the node type. Encapsulate the data to the node. If it is judged that the operating system does not meet the requirements of the node type, the control unit installs the operating system and the software package data to the node according to the node type and the installation file.

The node replacement processing method and the server system using the same according to the present invention, and the node is added to the servo by starting the operation system of the node and determining whether the operating system and the software package data configured by the node meet the requirements of the node type. The operation of the system, or install the operating system and software package information to the node according to the node type and installation file. In this way, it is possible to avoid reconfiguring the operating system and the software package data after each node replacement, thereby reducing the efficiency of the server system, thereby increasing the usability after node replacement.

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 nodes 110_1 110 110_N, a capture unit 120, a control unit 130, an inspection unit 140, and a determination unit 150, 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 100_1~110_N each have node information. The capturing unit 120 is coupled to the nodes 110_1 110 110_N for extracting node information to obtain the node type of the nodes 110_1 110 110_N. The node type is, for example, a service node, a computing node, and a storage node.

The control unit 130 is coupled to the nodes 110_1 110 110_N and the capture unit 120 for controlling the startup of the nodes 110_1 110 110_N and starting the operation system (OS) of the nodes 110_1 110 110_N. The checking unit 140 is coupled to the nodes 110_1 110 110_N for checking the operating systems of the nodes 110_1 110 110_N and a plurality of software packages to generate inspection results. The determining unit 150 is coupled to the checking unit 140, the control unit 130, and the capturing unit 120 for receiving and determining whether the checking result meets the requirements of the node type.

If it is determined that the check result meets the requirements of the node type, the control unit 130 adds the nodes 110_1 110 110_N to the server system 100. If it is determined that the check result does not meet the requirement of the node type, the control unit 130 may install the operating system and the plurality of software package materials to the nodes 110_1~110_N according to the node type and the installation file, so that the nodes 110_1~110_N have a correlation with the node type. Operating system and software.

The above briefly illustrates the internal components of the server system 100 and their coupling relationship. Hereinafter, the operation mode of the server system 100 after node replacement will be further explained. For convenience of explanation, the following will take the node 110_1 as an example, and assume that the node 110_1 is a node after replacing the component, and the node 110_1 has an operating system.

First, the server system 100 detects that the node 110_1 is damaged and notifies the user. When the user knows the aforementioned damage, the damaged component of the node 110_1 is removed and the new component is replaced with the node 110_1.

Then, the capturing unit 120 sends an Intelligent Platform Management Interface (IPMI) command to the Baseboard Management Controller (BMC) on the node 110_1 to request the baseboard management controller to obtain the node of the node 110_1. The information is passed back to the capture unit 120. Then, the capturing unit 120 can learn the node type (for example, the service node, the computing node, or the storage node) of the node 110_1 according to the node information, so as to perform subsequent processing.

After obtaining the node type of the node 110_1, the control unit 130 controls the node 110_1 to power on, and starts the operating system of the node 110_1. Next, after the startup of the operating system is completed, the checking unit 140 checks the operating system and the software package data of the node 110_1 to generate an inspection result, and transmits the inspection result to the determination unit 150. The inspection result includes, for example, the type and version of the operating system and the software package data.

Next, the judging unit 150 judges whether or not the check result meets the demand of the node type. If it is determined that the check result meets the requirement of the node type, the determining unit 150 generates, for example, a determination signal to the control unit 130, and the control unit 130 accordingly joins the node 110_1 to the server system 100 for operation. If it is determined that the check result does not meet the requirement of the node type, the determining unit 150 generates a judgment signal to the control unit 130, for example, the control unit 130 installs the operating system and the software package information to the node 110_1 according to the node type and the installation file, so that Node 110_1 joins the operation of server system 100. In this way, after the node 110_1 is replaced, the server system 100 can automatically determine whether the node 110_1 can directly join the operation of the server system 100 or need to reinstall the operating system and the software package data, thereby increasing the convenience of use.

Next, another example will be described to explain the processing operation after the node replacement by the server system 100. Further, the node 110_1 will be described as an example, and it is assumed that the node 110_1 is a node after the component has been replaced.

After the node 110_1 performs the replacement, the capturing unit 120 issues a smart platform management interface command to the baseboard management controller on the node 110_1 to request the baseboard management controller to obtain the node information of the node 110_1 and transmit it back to the capturing unit 120. Then, the capturing unit 120 can learn the node type (for example, the service node, the computing node, or the storage node) of the node 110_1 according to the node information.

Thereafter, the control unit 130 controls the node 110_1 to power on, and executes a self-boot test program, such as a Basic Input Output System (BIOS) Power On Self Test (POST). Next, the determining unit 150 determines whether the node 110_1 has the network booting mode, that is, whether the booting flag of the node 110_1 is set to the network booting mode. The network booting mode is, for example, a Preboot eXecution Environment (PXE) booting, that is, the node 110_1 can use the network booting mode to install the operating system and the software package data through the network card.

Then, if the boot flag of the node 110_1 does not have the network boot mode, the determining unit 150 determines that the node 110_1 does not have the network boot mode, for example, generates a determination signal to the control unit 130, and the control unit 130 controls the node 110_1 accordingly. Start the operating system. Then, during the startup of the operating system, the timer configured by the determining unit 150 (for example, the FRB4 timer) counts the process of starting the operating system to determine whether the operating system can be started within a preset time. The preset time can be adjusted by the user according to the needs.

If it is determined that the operating system is started at the preset time, indicating that the operating system is operating normally (ie, no error has occurred), the determining unit 150 generates a determination signal to the checking unit 140, for example. Next, the checking unit 140 checks the operating system and the software package data of the node 110_1 to generate an inspection result. That is, check the type and version of the operating system and software package qualifications. Thereafter, the inspection result is transmitted to the judging unit 150.

Next, the judging unit 150 judges whether or not the check result meets the demand of the node type. If it is determined that the check result meets the requirement of the node type, the determining unit 150 generates a judgment signal to the control unit 130, for example. Next, the control unit 130 joins the node 110_1 to the server system 100, that is, the node 110_1 joins the operation of the server system 100.

If the determining node 110_1 has the network booting mode, if the booting flag of the node 110_1 has the network booting mode, indicating that the node 110_1 can be powered on in the network boot mode, the determining unit 150 generates a determining signal to the control unit 130, for example. Then, the control unit 130 installs the operating system and the software package information required by the node 110_1 to the node 110_1 according to the node type and the installation file (for example, the Kick Start File), so that the node 110_1 has the original operation before the replacement. Types of.

The foregoing determining whether the operating system is started at a preset time, and if it is determined that the operating system is not completed at the preset time, indicating that the operating system is abnormal (that is, an error occurs) or the node 110_1 is not equipped with the operating system, then determining Unit 150, for example, generates a decision signal to control unit 130. Next, the control unit 130 accordingly sets the boot flag of the node 110_1 to a network boot mode, such as a one-time network boot mode. That is to say, when the node 110_1 uses the network boot mode and installs the operating system through the network card, for example, the boot flag of the node 110_1 does not have the network boot mode.

After the foregoing boot flag setting is completed, the control unit 130 controls the node 110_1 to perform rebooting, so that the node 110_1 executes the self-detection program again. Next, the determining unit 150 determines that the boot flag of the node 110_1 has a network booting mode, and generates a determining signal to the control unit 130, for example. Then, the control unit 130 causes the node 110_1 to install the operating system and the software package data to the node 110_1 according to the node type and the installation file of the node 110_1, so that the node 110_1 has the original operation type before the replacement.

If the result of the foregoing judgment check is consistent with the requirement of the node type, if it is judged that the check result does not meet the requirement of the node type, it indicates that all the operating systems and the software package data of the node 110_1 do not conform to the original type, so the determining unit 150 generates a judgment signal, for example. Control unit 130. Next, the control unit 130 accordingly sets the boot flag of the node 110_1 to the network boot mode.

Thereafter, the control unit 130 controls the node 110_1 to perform a reboot, causing the node 110_1 to perform the self-detection procedure again. Next, the determining unit 150 determines that the boot flag of the node 110_1 has a network booting mode, and generates a determining signal to the control unit 130, for example. Then, the control unit 130 causes the node 110_1 to install the operating system and the software package data to the node 110_1 according to the node type and the installation file of the node 110_1, so that the node 110_1 has the original operation type before the replacement.

If the result of the foregoing judgment is consistent with the requirement of the node type, if it is determined that the inspection result partially meets the requirement of the node type, and the operating system of the node 110_1 is partially matched with the software package data, the determining unit 150 further determines the operation configured by the node 110_1. Whether the system meets the needs of the node type. If it is determined that the operating system meets the requirements of the node type, the determining unit 150 generates a control signal to the control unit 130, for example. Next, the control unit 130 installs the relevant software package data to the node 110_1 according to the node type of the node 110_1, so that the node 110_1 has the original operation type before the replacement.

On the other hand, if it is judged that the operating system does not meet the requirements of the node type, the determining unit 150 generates a determination signal to the control unit 130, for example. Next, the control unit 130 accordingly sets the boot flag of the node 110_1 to the network boot mode.

Thereafter, the control unit 130 controls the node 110_1 to perform a reboot, causing the node 110_1 to perform the self-detection procedure again. Next, the determining unit 150 determines that the boot flag of the node 110_1 has a network booting mode, and generates a determining signal to the control unit 130, for example. Then, the control unit 130 causes the node 110_1 to install the operating system and the software package data to the node 110_1 according to the node type and the installation file of the node 110_1, so that the node 110_1 has the original operation type before the replacement.

In addition, after the node 110_1 reinstalls the operating system and the software package data through the network boot mode, the foregoing processing operations may be repeated until it is determined that the operating system and the software package data installed by the node 110_1 meet the node type requirements. The node 110_1 is added to the operation of the server system 100.

In this way, a description of the foregoing embodiment can be summarized as a node replacement processing method. Please refer to "Figure 2" for a flowchart of the node replacement processing method disclosed herein. The node replacement processing method of this embodiment is suitable for a server system. In step S202, the node information of the node is received to obtain the node type. In step S204, the node is powered on. In step S206, the operating system of the node is started. In step S208, a plurality of software package materials of the operating system and the node are checked to generate an inspection result. In step S210, it is determined whether the check result meets the requirement of the node type. If the check result meets the requirement of the node type, the process proceeds to step S212 to join the node to the server system. If the result of the check does not meet the requirements of the node type, proceed to step S214 to install the operating system and the software package data to the node according to the node type and the installation file.

Please refer to "Figure 3" for a flowchart of another node replacement processing method disclosed herein. The node replacement processing method of this embodiment is suitable for a server system.

In step S302, the node information of the node is received to obtain the node type. In step S304, the node is powered on. In step S306, a self-boot test program is executed. In step S308, it is determined whether the node has a network boot mode. If it is determined that the node does not have the network booting mode, the process proceeds to step S310 to start the operating system of the node.

In step S312, it is determined whether the operating system is started up at a preset time. If it is determined that the operating system is started up at the preset time, then the process proceeds to step S314 to check a plurality of software package materials of the operating system and the node to generate an inspection result. In step S316, it is determined whether the check result meets the requirement of the node type. If the result of the check conforms to the requirement of the node type, the process proceeds to step S318 to join the node to the server system.

In step S308, if it is determined that the node has the network boot mode, the process proceeds to step S320, and the operating system and the software package information are installed to the node according to the node type and the installation file.

In step S312, if it is determined that the operating system is not completed at the preset time, the process proceeds to step S322, and the node startup flag setting has a network boot mode. Next, in step S324, the node is rebooted, and the process returns to step S306. Then, in step S308, it is determined that the node is powered on in the network boot mode, and in step S320, the operating system and the software package information are installed to the node according to the node type and the installation file.

In step S316, if it is determined that the check result does not meet the requirement of the node type, the process proceeds to step S322, and the node boot flag setting has a network boot mode. Next, in step S324, the node is rebooted, and the process returns to step S306. Then, in step S308, it is determined that the node will have a network boot mode, and in step S320, the operating system and the software package information are installed to the node according to the node type and the installation file.

In step S316, if it is determined that the inspection result partially meets the requirements of the node type, the process proceeds to step S326 to determine whether the operating system meets the requirements of the node type. If it is determined that the operating system meets the requirements of the node type, the process proceeds to step S328, and the software package information is installed to the node according to the node type. Next, proceeding to step S318, the node is added to the server system.

If it is determined that the operating system does not meet the requirements of the node type, then the process proceeds to step S322, and the node's boot flag setting has a network boot mode. Next, in step S324, the node is rebooted, and the process returns to step S306. Then, in step S308, it is determined that the node is powered on in the network boot mode, and in step S320, the operating system and the software package information are installed to the node according to the node type and the installation file.

In addition, after step S320 is performed, the process returns to step S304 to repeatedly perform steps S304 to S324 except for step S318 until it is determined in step S316 that the check result meets the requirement of the node type, and proceeds to step S318 to join the node to the servo. Up to the system, or until it is determined in step S326 that the operating system meets the requirement of the node type, proceeding to step S328, installing the software package data to the node according to the node type, and proceeding to step S318 to join the node to the server system .

The node replacement processing method of the embodiment of the present disclosure and the server system using the same, according to the operating system of the node, and determining whether the operating system and the software package data configured by the node meet the requirements of the node type, Join the operation of the server system, or install the operating system and software package information to the node according to the node type and installation file.

In addition, by determining whether the node has a network booting procedure, the operating system and software package data corresponding to the requirements of its node type are installed on the node. Moreover, it is further determined whether the operating system is started at a predetermined time to confirm whether the operating system installed by the node generates an error or the node does not install the operating system. In this way, it is possible to avoid the need to reconfigure the operating system and the software package data after each node replacement, thereby reducing the efficiency of the server system, thereby increasing the usability after node replacement.

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

100_1~100_N. . . node

120. . . Capture unit

130. . . control unit

140. . . Inspection unit

150. . . Judging unit

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

Figure 2 is a flow chart of the node replacement processing method disclosed herein.

Figure 3 is a flow chart of another node replacement processing method of the present disclosure.

Claims (6)

A node replacement processing method is suitable for a server system, the node replacement processing method includes: receiving a node information of a node to obtain a node type; booting the node; performing a self-boot test procedure; determining whether the node is Having a network booting method; if it is determined that the node has the network booting mode, installing an operating system and a plurality of software package materials to the node according to the node type and the installation file; if it is determined that the node does not have the network The way of starting the road enters the operating system for starting the node; determining whether the operating system is started at a preset time; if it is determined that the operating system is started at the preset time, checking the operating system and the node Some software package data to generate a check result; determine whether the check result meets the requirement of the node type; if it is determined that the check result meets the requirement of the node type, the node is added to the server system; if it is judged that the check result is not Compliance with the requirements of the node type, according to the node type and an installation file, install the System software package and the plurality of data to the node; and determining if the operating system is not the predetermined time at startup is completed, the start flag to a node having the power-mode network, and the node reopened Machine and go back to the steps to perform the self-boot test procedure. The node replacement processing method of claim 1, further comprising: setting a boot flag of the node to have the network boot mode; and restarting the node, and returning to performing the self boot The steps of the test program. The node replacement processing method of claim 1, wherein the step of determining whether the check result meets the requirement of the node type comprises: determining whether the operating system meets the requirements of the node type if the check result partially meets the requirement of the node type The requirement of the node type; if it is determined that the operating system meets the requirements of the node type, installing the software package data to the node according to the node type; and if it is determined that the operating system does not meet the requirement of the node type, A boot flag setting of the node has the network boot mode, and the node is rebooted and returned to the step of executing the self boot test procedure. A server system includes: a node having a node information; a capture unit coupled to the node for capturing the node information to obtain a node type of the node; a control unit coupled to the node and The capturing unit is configured to control the node to be powered on and start an operating system of the node; an checking unit coupled to the node for checking the operating system of the node and the plurality of software package materials to generate an inspection result ;as well as a determining unit, coupled to the checking unit, the control unit and the capturing unit, for receiving and determining whether the checking result meets the requirement of the node type, wherein if the checking result meets the requirement of the node type, the controlling The unit joins the node to the server system. If it is determined that the check result does not meet the requirement of the node type, the control unit installs the operating system and the software package information to the node according to the node type and an installation file; The control unit controls the node to execute a self-boot test program, and the determining unit determines whether the node has a network boot mode, wherein if the node is determined not to have the network boot mode, the control unit controls the node to start the The operating system, if it is determined that the node has the network booting mode, the control unit installs the operating system and the software package information to the node according to the node type and the installation file; wherein the determining unit determines whether the operating system is Startup is completed at a preset time, if it is determined that the operating system is at the preset time After the completion, the checking unit checks the software package data of the operating system and the node to generate the check result. If it is determined that the operating system is not completed at the preset time, the control unit sends a boot flag to the node. The setting has the network booting mode, so that the node is rebooted, so that the node executes the self-booting test program, and the determining unit determines that the node has the network booting mode, so that the control unit is based on the node type and The installation file installs the operating system and the software package materials to the node. The server system of claim 4, wherein the control unit A boot flag setting of the node has the network boot mode, and the node is rebooted, so that the node performs the self-boot test procedure, and the determining unit determines that the node has the network boot mode, so that the node The control unit installs the operating system and the software package information to the node according to the node type and the installation file. The server system of claim 4, wherein if it is determined that the check result partially meets the requirement of the node type, the determining unit determines whether the operating system meets the requirement of the node type, wherein if the operating system is determined Depending on the type of the node, the control unit installs the software package data to the node according to the node type. If it is determined that the operating system does not meet the requirement of the node type, the control unit uses the node type and the installation file according to the node type. Install the operating system and the software package data to the node.