A server reliability testing method, device, server and storage medium

Abstract

The present invention discloses a server reliability test method, device, server and storage medium, including: updating the software basic information of the tested server and troubleshooting the hardware basic information until the software basic information and the hardware basic information meet the test requirements; while controlling the tested server to run based on the test content, obtaining the test information of the tested server; the test information at least includes the hardware test information; comparing the basic information and the test information to obtain the test result; the basic information at least includes the hardware basic information. The above technical scheme realizes the standardization and process of server reliability testing, and improves the timeliness and accuracy of server reliability testing.

Description

Technical Field

[0001] The embodiments of the present invention relate to server technology, and in particular to a server reliability testing method, device, server and storage medium. Background Art

[0002] With the rapid development of computer and Internet technologies, the iteration speed of new products and new technologies is also getting faster and faster. Before launching new products and new technologies, they need to undergo reliability testing and compatibility testing. Therefore, it is necessary to shorten the testing cycle as much as possible to launch them as soon as possible and occupy the market.

[0003] Servers under development will be upgraded many times in terms of product process, product technology, product specifications and technical parameters to meet market demand. The original testing methods and tools cannot be fully applied to the upgraded servers. Therefore, when testing new servers under development, the commonly used method is to rewrite the test code based on the characteristics and specifications of the new servers, and upgrade and update the code according to the needs and problems encountered during the testing process.

[0004] The existing technology lacks a unified testing method and process when testing new servers, which affects the timeliness and accuracy of the test. Summary of the invention

[0005] The present invention provides a server reliability testing method, device, server and storage medium, so as to realize reliability testing of the server efficiently and quickly.

[0006] In a first aspect, an embodiment of the present invention provides a server reliability testing method, comprising:

[0007] Update the software basic information of the server under test and troubleshoot the hardware basic information until both the software basic information and the hardware basic information meet the test requirements;

[0008] While controlling the server under test to run based on the test content, obtaining test information of the server under test; the test information at least includes hardware test information;

[0009] The basic information and the test information are compared to obtain a test result; the basic information at least includes the hardware basic information.

[0010] The embodiment of the present invention provides a server reliability testing method, including: updating the software basic information of the tested server, troubleshooting the hardware basic information, until the software basic information and the hardware basic information meet the test requirements; controlling the tested server to run based on the test content, while obtaining the test information of the tested server; the test information at least includes the hardware test information; comparing the basic information and the test information to obtain the test result; the basic information at least includes the hardware basic information. The above technical scheme first updates the software basic information of the tested server so that the software basic information meets the test requirements, troubleshoots the hardware basic information of the tested server so that the hardware basic information meets the test requirements, and then controls the tested server to restart, power on and off without power failure, or power off and power on cycle reliability test based on the test content, and at the same time, the test information of the tested server can be obtained, the test information at least includes the hardware test information, and the hardware test information contained in the basic information is compared with the hardware test information to obtain the test result. The standardization and process of server reliability testing are realized, and the timeliness and accuracy of server reliability testing are improved.

[0011] Furthermore, before updating the basic software information of the tested server and troubleshooting the basic hardware information, the following steps are also included:

[0012] The software basic information and the hardware basic information of the server under test are obtained.

[0013] Further, the software basic information of the server under test is updated, and the hardware basic information is troubleshooted until the software basic information and the hardware basic information meet the test requirements, including:

[0014] When the software basic information is inconsistent with the software tested information included in the test requirement, updating the software basic information to the software tested information;

[0015] When the actual hardware information actually running in the tested server represented by the hardware basic information is inconsistent with the hardware tested information included in the test requirements, troubleshooting and repair are performed on the hardware basic information to make the hardware basic information consistent with the hardware tested information.

[0016] Furthermore, the test information also includes software test information; and the basic information also includes the software basic information.

[0017] Furthermore, the hardware basic information includes at least one of the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, system equipment information, and AI acceleration card information; the software basic information includes at least one of server product information, basic input and output system, intelligent platform management interface IPMI, operating system category, operating system version, operating system core version and device firmware.

[0018] Further, the test content includes: at least one of: restarting, power on / off without power failure, and power off / on cycle without power failure; accordingly, while controlling the server under test to run based on the test content, obtaining the test information of the server under test includes:

[0019] The hardware test information and the software test information of the server under test are obtained while controlling the server under test to restart, turn on and off without power failure, or cycle between power failure and power failure.

[0020] Furthermore, the basic information and the test information are compared to obtain the test results, including:

[0021] Comparing the hardware basic information with the hardware test information, and if the hardware test information is consistent with the hardware basic information, determining that the test result is qualified;

[0022] The software basic information and the software test information are compared, and if the software test information is consistent with the software basic information, the test result is determined to be qualified.

[0023] In a second aspect, an embodiment of the present invention further provides a server reliability testing device, comprising:

[0024] An update and troubleshooting module is used to update the software basic information of the tested server and troubleshoot the hardware basic information until the software basic information and the hardware basic information meet the test requirements;

[0025] An acquisition module, used to control the server under test to run based on the test content and acquire test information of the server under test; the test information at least includes hardware test information;

[0026] The test module is used to compare the basic information with the test information to obtain the test result; the basic information at least includes the hardware basic information.

[0027] In a third aspect, an embodiment of the present invention further provides a server, the server comprising:

[0028] One or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the server reliability testing method as described in any one of the first aspects.

[0029] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, wherein the computer executable instructions, when executed by a computer processor, are used to execute the server reliability testing method as described in any one of the first aspects.

[0030] In a fifth aspect, the present application provides a computer program product, which includes computer instructions. When the computer instructions are executed on a computer, the computer executes the server reliability testing method provided in the first aspect.

[0031] It should be noted that the above computer instructions may be stored in whole or in part on a computer-readable storage medium, wherein the computer-readable storage medium may be packaged together with the processor of the server reliability test device, or may be packaged separately from the processor of the server reliability test device, which is not limited in this application.

[0032] The description of the second, third, fourth and fifth aspects in this application can refer to the detailed description of the first aspect; and the beneficial effects of the description of the second, third, fourth and fifth aspects can refer to the beneficial effect analysis of the first aspect, which will not be repeated here.

[0033] In this application, the name of the server reliability testing device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear with other names. As long as the functions of each device or functional module are similar to those of this application, they fall within the scope of the claims of this application and their equivalent technologies.

[0034] These and other aspects of the present application will become more apparent from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A flow chart of a server reliability testing method provided in Embodiment 1 of the present invention;

[0036] Figure 2 A flow chart of a server reliability testing method provided in Embodiment 2 of the present invention;

[0037] Figure 3 A flow chart of a server reliability testing method according to the second embodiment of the present invention;

[0038] Figure 4A schematic diagram of the structure of a server reliability testing device provided in Embodiment 3 of the present invention;

[0039] Figure 5 A schematic diagram of the structure of a server provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0040] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0041] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0042] The terms "first" and "second" and the like in the specification and drawings of this application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

[0043] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0044] It should be mentioned before discussing exemplary embodiments in more detail that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe various operations (or steps) as sequential processes, many operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of various operations can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to methods, functions, procedures, subroutines, subprograms, etc. In addition, the embodiments in the present invention and the features in the embodiments can be combined with each other without conflict.

[0045] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0046] In the description of the present application, unless otherwise specified, “plurality” means two or more.

[0047] Embodiment 1

[0048] Figure 1 This is a flow chart of a server reliability testing method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where reliability testing of a server needs to be performed quickly and accurately. The method can be performed by a server reliability testing method device, and specifically includes the following steps:

[0049] Step 110: Update the software basic information of the server under test, and troubleshoot the hardware basic information, until both the software basic information and the hardware basic information meet the test requirements.

[0050] The test requirements may include software information requirements and hardware information requirements. The software information requirements may include software version information, and the hardware information requirements may include the quantity, model, and operating status of the hardware.

[0051] Basic software information includes, but is not limited to: server product information, Basic Input Output System (BIOS), Intelligent Platform Management Interface (IPMI), operating system category, operating system version, operating system core version, and device firmware (Firmware, FW). Basic hardware information includes, but is not limited to: the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, system equipment information, and AI acceleration card information.

[0052] Specifically, if the software basic information of the server under test is inconsistent with the software information requirements included in the test requirements, the software basic information of the server under test is updated until the software basic information of the server under test is consistent with the software information requirements included in the test requirements. Specifically, the software of the server under test can be upgraded based on the software information requirements included in the test requirements, and checked for errors. When the software of the server under test is consistent with the software information requirements included in the test requirements and runs normally, it can be determined that the software basic information meets the test requirements.

[0053] If the hardware that can run normally in the server under test is inconsistent with the quantity and / or model of the hardware basic information included in the test requirements, the hardware of the server under test will be checked in turn to increase, reduce or replace the hardware until the hardware that can run normally in the hardware basic information of the server under test is consistent with the hardware basic information included in the test requirements. Specifically, the quantity, model and status of the hardware contained in the server under test can be checked based on the hardware information requirements included in the test requirements, and troubleshooting can be performed. When the quantity, model and status of the hardware of the server under test are consistent with the hardware information requirements included in the test requirements and run normally, it can be determined that the hardware basic information meets the test requirements.

[0054] In an embodiment of the present invention, before performing a reliability test on the server under test, the basic software information of the server under test can be updated and the hardware information can be troubleshooted so that the basic software information of the server under test is consistent with the software information requirements included in the test requirements, and the basic hardware information is consistent with the hardware information requirements included in the test requirements, thereby improving the accuracy of the reliability test.

[0055] Step 120: While controlling the server under test to run based on the test content, obtain test information of the server under test.

[0056] Wherein, the test information at least includes hardware test information.

[0057] The test content may include restarting, powering on and off without power failure, and powering off and starting up again without power failure, etc. The reliability of the server under test may be determined during the restarting, powering on and off without power failure, or powering off and starting up again without power failure.

[0058] Specifically, the hardware test information of the server under test can be obtained while controlling the server under test to restart, including the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, system equipment information, and AI acceleration card information; similarly, the hardware test information of the server under test can be obtained while controlling the server under test to perform uninterrupted power on and off or uninterrupted power off and power on cycles.

[0059] In actual applications, the server under test can be restarted, powered on and off without power failure, and powered off and on again. Of course, when restarting, powering on and off without power failure, and powered off and on again, hardware test information needs to be obtained to obtain a large amount of hardware test information. Based on the hardware test information, the hardware log file corresponding to the hardware can be generated to enrich the test information and improve the accuracy of the test.

[0060] It should be noted that the server under test can be controlled by the remote server to perform cyclic restart, power on and off without power failure, and power off and power on cycle testing. Of course, the remote server can also obtain hardware test information during the cycle.

[0061] In the embodiment of the present invention, the tested server can be controlled to perform cyclic restart, power on / off, and power off / on cyclic testing while hardware test information of the tested server can be obtained to provide data support for server reliability testing.

[0062] Step 130: Compare the basic information with the test information to obtain a test result.

[0063] Wherein, the basic information at least includes the hardware basic information.

[0064] Specifically, the hardware test information corresponding to each hardware can be retrieved from the hardware log file generated above, which can specifically include the quantity, model and status corresponding to each hardware. Compare the hardware test information with the hardware basic information, specifically, compare the test quantity of each hardware contained in the hardware test information and the basic quantity of each hardware contained in the hardware basic information, compare the test model of each hardware contained in the hardware test information and the basic model of each hardware contained in the hardware basic information, and compare the test status of each hardware contained in the hardware test information and the basic status of each hardware contained in the hardware basic information. If the test quantity of each hardware contained in the hardware test information is consistent with the basic quantity of each hardware contained in the hardware basic information, the test model of each hardware contained in the hardware test information is consistent with the basic model of each hardware contained in the hardware basic information, and the test status of each hardware contained in the hardware test information is consistent with the basic status of each hardware contained in the hardware basic information, then determine that the reliability test of the server under test has passed; otherwise, determine that the test result is that the reliability test of the server under test has failed.

[0065] It should be noted that in order to improve the test efficiency, you can first compare the test quantity of each hardware with the basic quantity, then compare the test model of each hardware with the basic model, and finally compare the test status of each hardware with the basic status.

[0066] In an embodiment of the present invention, by comparing the basic information and test information of each hardware in the server under test, it is possible to determine whether the hardware test information of the server under test during the test operation is consistent with the initially set hardware basic information, and then determine whether the reliability test of the server under test is passed or failed, so as to implement reliability testing of the server under test, improve the efficiency of the reliability test, and improve the accuracy of the reliability test.

[0067] A server reliability testing method provided in the first embodiment of the present invention includes: updating the software basic information of the tested server and troubleshooting the hardware basic information until the software basic information and the hardware basic information meet the test requirements; while controlling the tested server to run based on the test content, obtaining the test information of the tested server; the test information at least includes the hardware test information; comparing the basic information and the test information to obtain the test result; the basic information at least includes the hardware basic information. The above technical scheme first updates the software basic information of the tested server so that the software basic information meets the test requirements, troubleshoots the hardware basic information of the tested server so that the hardware basic information meets the test requirements, and then controls the tested server to restart, power on and off without power failure, or power off and power on cycle reliability test based on the test content, and at the same time, the test information of the tested server can be obtained, and the test information can at least include the hardware test information, and the hardware test information contained in the basic information and the hardware test information are compared to obtain the test result. The standardization and process of server reliability testing are realized, and the timeliness and accuracy of server reliability testing are improved.

[0068] Embodiment 2

[0069] Figure 2 This is a flow chart of a server reliability testing method provided in Embodiment 2 of the present invention. This embodiment is specific based on the above embodiment. In this embodiment, the method may also include:

[0070] Step 210: Obtain the software basic information and the hardware basic information of the server under test.

[0071] Specifically, the software basic information and hardware basic information of the server under test can be obtained based on the control server that is in communication connection with the server under test. Specifically, the software configuration information of the server under test can be identified, and the software configuration information can be parsed, and the software basic information can be determined according to the parsing result; similarly, the hardware configuration information of the server under test can be identified, and the hardware configuration information can be parsed, and the hardware basic information can be determined according to the parsing result.

[0072] In the embodiment of the present invention, the control server that is in communication connection with the server under test can obtain basic software information and basic hardware information of the server under test, and perform reliability testing on the server under test.

[0073] Step 220: Update the software basic information of the server under test, and troubleshoot the hardware basic information, until both the software basic information and the hardware basic information meet the test requirements.

[0074] Specifically, the control server may also receive a test requirement sent by a user through a terminal device, and based on the test requirement, update the basic software information of the server under test and perform troubleshooting on the basic hardware information.

[0075] In one implementation, step 220 may specifically include:

[0076] When the software basic information is inconsistent with the software tested information included in the test requirements, the software basic information is updated to the software tested information; when the actual information of the hardware actually running in the tested server represented by the hardware basic information is inconsistent with the hardware tested information included in the test requirements, the hardware basic information is troubleshooted and repaired to make the hardware basic information consistent with the hardware tested information.

[0077] Preferably, the software basic information includes at least one of server product information, basic input and output system, intelligent platform management interface, operating system category, operating system version, operating system core version and device firmware; the hardware basic information includes at least one of the number and model of central processing units, the number and model of system cache memories, the number and model of mass storage devices, system whole machine equipment information and AI acceleration card information.

[0078] Specifically, if any of the server product information, BIOS, IPMI, operating system category, operating system version, operating system core version and FW of the server under test is inconsistent with the software information requirements included in the test requirements, at least one of the server product information, BIOS, IPMI, operating system category, operating system version, operating system core version and FW can be updated until the basic software information is inconsistent with the software information requirements included in the test requirements; if any of the actual hardware information of the actual running of the server under test, that is, the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, the system equipment information and the AI ​​accelerator card information is inconsistent with the hardware tested information included in the test requirements, the basic hardware information can be troubleshooted and repaired to make the basic hardware information consistent with the hardware tested information.

[0079] In an embodiment of the present invention, before performing a reliability test on the server under test, the basic software information of the server under test can be updated and the hardware information can be troubleshooted so that the basic software information of the server under test is consistent with the software information requirements included in the test requirements, and the basic hardware information is consistent with the hardware information requirements included in the test requirements, thereby improving the accuracy of the reliability test.

[0080] Step 230: While controlling the server under test to run based on the test content, obtain test information of the server under test.

[0081] Wherein, the test information at least includes hardware test information.

[0082] In one implementation, the test content includes: at least one of: restarting, powering on and off without power failure, and powering off and on again; accordingly, step 230 may specifically include:

[0083] The hardware test information and the software test information of the server under test are obtained while controlling the server under test to restart, turn on and off without power failure, or cycle between power failure and power failure.

[0084] As shown in the first embodiment, the server under test can be restarted, powered on and off without power failure, and powered off and on again in a cycle test, and hardware test information can be obtained while restarting, powering on and off without power failure, and powered off and on again in a cycle test. A hardware log file corresponding to the hardware can also be generated based on the hardware test information.

[0085] Furthermore, the test information also includes software test information.

[0086] Of course, while the server under test is being restarted, powered on and off, and powered off and on again, software test information can also be obtained, including server product information, BIOS, IPMI, operating system category, operating system version, operating system core version, and FW of the server under test. Software log files corresponding to the software can also be generated based on the software test information.

[0087] In an embodiment of the present invention, the control server controls the server under test to cyclically restart, power on and off without power failure, and power off and on again without power failure, while obtaining hardware test information and software test information of the server under test to provide data support for server reliability testing.

[0088] Step 240: Compare the basic information with the test information to obtain a test result.

[0089] Wherein, the basic information at least includes the hardware basic information.

[0090] Furthermore, the basic information also includes the software basic information.

[0091] The basic software information is used to compare with the acquired software test information to implement reliability testing of the basic software information of the tested service area.

[0092] In one implementation, step 240 may specifically include:

[0093] Compare the hardware basic information with the hardware test information. If the hardware test information is consistent with the hardware basic information, determine that the test result is qualified; compare the software basic information with the software test information. If the software test information is consistent with the software basic information, determine that the test result is qualified.

[0094] Specifically, the control server can retrieve the hardware test information corresponding to each hardware from the hardware log file generated above, which may specifically include the quantity, model and status corresponding to each hardware; compare the hardware basic information and the hardware test information to obtain the hardware test result. As described in the previous embodiment 1, if the test quantity of each hardware contained in the hardware test information is consistent with the basic quantity of each hardware contained in the hardware basic information, the test model of each hardware contained in the hardware test information is consistent with the basic model of each hardware contained in the hardware basic information, and the test status of each hardware contained in the hardware test information is consistent with the basic status of each hardware contained in the hardware basic information, then the hardware test result is determined to be a passed test; otherwise, the hardware test result is determined to be a failed test.

[0095] Retrieve the software test information corresponding to each software from the software log file generated above, which may specifically include the version information corresponding to each software; compare the software basic information and the software test information to obtain the software test result. Specifically, the test version information of each software contained in the software test information and the basic version information of each software contained in the software basic information can be compared. If the test version information of each software contained in the software test information is consistent with the basic version information of each software contained in the software basic information, then determine that the software test result is a passed test; otherwise, determine that the software test result is a failed test.

[0096] In actual applications, it is also necessary to check whether there are fatal errors in the software log file and the hardware log file. If there are no fatal error logs in the software log file and the hardware log file, and the software test results and the hardware test results are both passed, it is determined that the reliability test of the server under test has passed.

[0097] Of course, the acquired software basic information, hardware basic information and test results may also be stored correspondingly.

[0098] In an embodiment of the present invention, by comparing the basic information and test information of each hardware in the server under test, it can be determined whether the hardware test information of the server under test during the test operation is consistent with the initially set hardware basic information; by comparing the test information and basic information of each software of the server under test, it can be determined whether the software test information of the server under test during the test operation is consistent with the initially set software basic information; and then determine whether the reliability test of the server under test is passed or failed, so as to realize the reliability test of the server under test, improve the efficiency of the reliability test, and improve the accuracy of the reliability test.

[0099] A server reliability testing method provided in the second embodiment of the present invention includes: updating the software basic information of the tested server and troubleshooting the hardware basic information until the software basic information and the hardware basic information meet the test requirements; while controlling the tested server to run based on the test content, obtaining the test information of the tested server; the test information at least includes the hardware test information; comparing the basic information and the test information to obtain the test result; the basic information at least includes the hardware basic information. The above technical scheme first updates the software basic information of the tested server so that the software basic information meets the test requirements, troubleshoots the hardware basic information of the tested server so that the hardware basic information meets the test requirements, and then controls the tested server to restart, power on and off without power failure, or power off and power on cycle reliability test based on the test content, and at the same time, the test information of the tested server can be obtained, the test information at least includes the hardware test information, and the hardware test information contained in the basic information is compared with the hardware test information to obtain the test result. The standardization and process of server reliability testing are realized, and the timeliness and accuracy of server reliability testing are improved.

[0100] Figure 3 The following is a flow chart of a server reliability testing method provided in the second embodiment of the present invention, which exemplifies one of the implementation methods. Figure 3 As shown, including:

[0101] Step 310: Obtain basic software information and basic hardware information of the server under test.

[0102] Step 320: Determine whether the software basic information is consistent with the software testing requirements included in the testing requirements.

[0103] If the software basic information is inconsistent with the software testing requirement, execute step 330 ; otherwise, execute step 340 .

[0104] Step 330: Update the basic software information of the server under test.

[0105] After step 330 , the process returns to step 320 .

[0106] Step 340: Determine whether the hardware basic information is consistent with the hardware test requirements included in the test requirements.

[0107] If the hardware basic information is inconsistent with the hardware test requirement, execute step 350; otherwise, execute step 360.

[0108] Step 350: troubleshoot basic hardware information of the server under test.

[0109] After step 350 , the process returns to step 340 .

[0110] In actual applications, steps 340 - 350 may be performed first, and then steps 320 - 330 may be performed.

[0111] Step 360: While controlling the server under test to restart, power on and off without power failure, or power off and on again, obtain hardware test information and software test information of the server under test.

[0112] Step 370: Compare the software basic information with the software test information to obtain the software test result; compare the hardware basic information with the hardware test information to obtain the hardware test result.

[0113] Step 380: If both the software test result and the hardware test result are passed, it is determined that the reliability test of the tested server has passed.

[0114] The implementation of the server reliability method provided in the second embodiment of the present invention realizes the standardization and process-based testing of server reliability, and improves the timeliness and accuracy of the server reliability testing.

[0115] Embodiment 3

[0116] Figure 4 This is a schematic diagram of the structure of a server reliability test device provided in Embodiment 3 of the present invention, which can be applied to situations where reliability testing of a server needs to be performed quickly and accurately. The device can be implemented by software and / or hardware and is generally integrated in a server.

[0117] like Figure 4 As shown, the device comprises:

[0118] An update and troubleshooting module 410 is used to update the software basic information of the tested server and troubleshoot the hardware basic information until both the software basic information and the hardware basic information meet the test requirements;

[0119] The acquisition module 420 is used to control the server under test to run based on the test content and acquire the test information of the server under test; the test information at least includes hardware test information;

[0120] The test module 430 is used to compare the basic information with the test information to obtain a test result; the basic information at least includes the hardware basic information.

[0121] The server reliability testing device provided in the third embodiment updates the software basic information of the tested server and troubleshoots the hardware basic information until the software basic information and the hardware basic information meet the test requirements; while controlling the tested server to run based on the test content, the test information of the tested server is obtained; the test information at least includes the hardware test information; the basic information and the test information are compared to obtain the test result; the basic information at least includes the hardware basic information. The above technical scheme first updates the software basic information of the tested server so that the software basic information meets the test requirements, troubleshoots the hardware basic information of the tested server so that the hardware basic information meets the test requirements, and then controls the tested server to restart, power on and off without power failure, or power off and power on cycle reliability test based on the test content, and at the same time, the test information of the tested server can be obtained, and the test information can at least include the hardware test information, and the hardware test information contained in the basic information is compared with the hardware test information to obtain the test result. The standardization and process of server reliability testing are realized, and the timeliness and accuracy of server reliability testing are improved.

[0122] Based on the above embodiment, the device further includes:

[0123] The information acquisition module is used to acquire the basic software information and the basic hardware information of the server under test.

[0124] Based on the above embodiment, the update checking module 410 is specifically used for:

[0125] When the software basic information is inconsistent with the software tested information included in the test requirement, updating the software basic information to the software tested information;

[0126] When the hardware basic information is inconsistent with the hardware tested information included in the test requirements and the actual hardware information actually running in the tested server, troubleshooting and repair are performed on the hardware basic information and the actual hardware information to make the hardware basic information consistent with the hardware tested information and the actual hardware information.

[0127] In one implementation, the test information also includes software test information; and the basic information also includes software basic information.

[0128] In one embodiment, the hardware basic information includes at least one of the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, system device information, and AI acceleration card information; the software basic information includes at least one of server product information, basic input and output system, intelligent platform management interface IPMI, operating system category, operating system version, operating system core version, and device firmware.

[0129] In one implementation, the test content includes at least one of: restarting, power on / off without power failure, and power off / on / off cycle without power failure; accordingly, the acquisition module 420 is specifically used to:

[0130] The hardware test information and the software test information of the server under test are obtained while controlling the server under test to restart, turn on and off without power failure, or cycle between power failure and power failure.

[0131] In one implementation, the testing module 430 is specifically configured to:

[0132] Comparing the hardware basic information with the hardware test information, and if the hardware test information is consistent with the hardware basic information, determining that the test result is qualified;

[0133] The software basic information and the software test information are compared, and if the software test information is consistent with the software basic information, the test result is determined to be qualified.

[0134] The server reliability testing device provided in the embodiment of the present invention can execute the server reliability testing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0135] Embodiment 4

[0136] Figure 5 A schematic diagram of the structure of a server provided in Embodiment 4 of the present invention. Figure 5 A block diagram of an exemplary server 5 suitable for implementing embodiments of the present invention is shown. Figure 5 The server 5 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0137] like Figure 5As shown, the server 5 is in the form of a general purpose computing electronic device. The components of the server 5 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0138] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0139] The server 5 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the server 5, including volatile and non-volatile media, removable and non-removable media.

[0140] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The server 5 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 5 not shown, usually called a "hard drive"). Although Figure 5 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0141] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0142] The server 5 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), one or more devices that enable a user to interact with the server 5, and / or any device that enables the server 5 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. Furthermore, the server 5 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 20. Figure 5 As shown, the network adapter 20 communicates with other modules of the server 5 via the bus 18. It should be understood that although Figure 5 Not shown, other hardware and / or software modules may be used in conjunction with the server 5, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0143] The processing unit 16 executes various functional applications and page displays by running the programs stored in the system memory 28, for example, implementing the server reliability testing method provided by the embodiment of the present invention, the method comprising:

[0144] Update the software basic information of the server under test and troubleshoot the hardware basic information until both the software basic information and the hardware basic information meet the test requirements;

[0145] While controlling the server under test to run based on the test content, obtaining test information of the server under test; the test information at least includes hardware test information;

[0146] The basic information and the test information are compared to obtain a test result; the basic information at least includes the hardware basic information.

[0147] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the server reliability testing method provided by any embodiment of the present invention.

[0148] Embodiment 5

[0149] Embodiment 5 of the present invention further provides a storage medium including computer executable instructions, wherein the computer executable instructions are used to execute a server reliability testing method when executed by a computer processor, the method comprising:

[0150] Update the software basic information of the server under test and troubleshoot the hardware basic information until both the software basic information and the hardware basic information meet the test requirements;

[0151] While controlling the server under test to run based on the test content, obtaining test information of the server under test; the test information at least includes hardware test information;

[0152] The basic information and the test information are compared to obtain a test result; the basic information at least includes the hardware basic information.

[0153] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0154] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0155] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0156] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0157] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0158] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A server reliability testing method, characterized in that: include: Update the software basic information of the server under test and troubleshoot the hardware basic information until both the software basic information and the hardware basic information meet the test requirements; While controlling the server under test to run based on the test content, obtaining test information of the server under test; The test information includes at least hardware test information and software test information; Comparing the hardware basic information with the hardware test information, and if the hardware test information is consistent with the hardware basic information, determining that the hardware test result is passed; Comparing the software basic information with the software test information, and if the software test information is consistent with the software basic information, determining that the software test result is passed; The basic information at least includes the hardware basic information and the software basic information; The method further comprises: checking whether there are fatal errors in the software log file and the hardware log file, and if there are no fatal error logs in the software log file and the hardware log file, and the software test results and the hardware test results are both passed, determining that the reliability test of the tested server has passed; The comparing the hardware basic information and the hardware test information to obtain the test result specifically includes: retrieving the hardware test information corresponding to each hardware from the hardware log file to obtain the quantity, model and status corresponding to each hardware; obtaining the test result by first comparing the test quantity of each hardware with the basic quantity, then comparing the test model of each hardware with the basic model, and finally comparing the test status of each hardware with the basic status in order; wherein, the hardware log file is a log file corresponding to the hardware generated according to the hardware test information.

2. The server reliability testing method according to claim 1, characterized in that: Before updating the basic software information of the server under test and troubleshooting the basic hardware information, it also includes: The software basic information and the hardware basic information of the server under test are obtained.

3. The server reliability testing method according to claim 2, characterized in that: The software basic information of the server under test is updated, and the hardware basic information is troubleshooted until the software basic information and the hardware basic information meet the test requirements, including: When the software basic information is inconsistent with the software tested information included in the test requirement, updating the software basic information to the software tested information; When the actual hardware information actually running in the tested server represented by the hardware basic information is inconsistent with the hardware tested information included in the test requirements, troubleshooting and repair are performed on the hardware basic information to make the hardware basic information consistent with the hardware tested information.

4. The server reliability testing method according to claim 1, characterized in that: The basic hardware information includes at least one of the number and model of central processing units, the number and model of system cache memories, the number and model of large-capacity storage devices, system device information and AI acceleration card information; the basic software information includes at least one of server product information, basic input and output system, intelligent platform management interface, operating system category, operating system version, operating system core version and device firmware.

5. The server reliability testing method according to claim 1, characterized in that: The test content includes: at least one of restarting, powering on and off without power failure, and powering off and starting up again without power failure; accordingly, while controlling the server under test to run based on the test content, obtaining the test information of the server under test, including: The hardware test information and the software test information of the server under test are obtained while controlling the server under test to restart, turn on and off without power failure, or cycle between power failure and power failure.

6. A server reliability testing device, characterized in that: include: An update and troubleshooting module is used to update the software basic information of the tested server and troubleshoot the hardware basic information until the software basic information and the hardware basic information meet the test requirements; An acquisition module, used to control the server under test to run based on the test content and acquire the test information of the server under test; The test information includes at least hardware test information and software test information; A testing module, used for comparing the hardware basic information with the hardware test information, and determining that the hardware test result is passed if the hardware test information is consistent with the hardware basic information; Comparing the software basic information with the software test information, and if the software test information is consistent with the software basic information, determining that the software test result is passed; The basic information at least includes the hardware basic information and the software basic information; The device further comprises: checking whether there are fatal errors in the software log file and the hardware log file, and if there are no fatal error logs in the software log file and the hardware log file, and the software test result and the hardware test result are both passed, determining that the reliability test of the tested server has passed; The comparing the hardware basic information and the hardware test information to obtain the test result specifically includes: retrieving the hardware test information corresponding to each hardware from the hardware log file to obtain the quantity, model and status corresponding to each hardware; obtaining the test result by first comparing the test quantity of each hardware with the basic quantity, then comparing the test model of each hardware with the basic model, and finally comparing the test status of each hardware with the basic status in order; wherein, the hardware log file is a log file corresponding to the hardware generated according to the hardware test information.

7. A server, characterized in that: The server comprises: one or more processors; A storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the server reliability testing method as described in any one of claims 1-5.

8. A storage medium comprising computer executable instructions, wherein the computer executable instructions are used to execute the server reliability testing method according to any one of claims 1 to 5 when executed by a computer processor.

Images