Processing method, device and equipment for abnormal detection of bare metal server and medium

Abstract

The invention provides a processing method, device and equipment for abnormal detection of a bare metal server and a medium. The method comprises the following steps: performing cloud entry detection on a bare metal server, acquiring error reporting information of detection failure under the condition of detection failure, executing a hardware configuration acquisition script based on the error reporting information to acquire hardware configuration information of the corresponding bare metal server, determining abnormal hardware configuration information in the hardware configuration information, and executing the hardware configuration acquisition script according to the abnormal hardware configuration information. Modifying the abnormal hardware configuration information of the bare metal server; according to the method, automatic anomaly detection and processing of the bare metal server are realized, the anomaly detection efficiency and the anomaly processing efficiency are improved, and the method is suitable for deployment work of large-scale bare metal servers.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a method, apparatus, device and medium for detecting anomalies in bare metal servers. Background Technology

[0002] Bare metal servers are servers that combine the characteristics of traditional physical servers with the virtualization service capabilities of cloud computing technology. They are widely used in scenarios where high performance and data security are critical for computing services. Furthermore, these servers can be managed and delivered through cloud computing management platforms. In a cloud computing management platform environment, the deployment process of bare metal servers mainly consists of three stages: cloud migration, deployment, and operation. Failure to migrate to the cloud can severely impact subsequent deployment and delivery. Current methods for handling anomalies in bare metal servers typically involve administrators manually checking for and troubleshooting potential causes of cloud migration failures, and then manually addressing the problem after locating it.

[0003] However, there are many reasons for cloud migration failures, and as the scale of cloud platform nodes expands, the existing methods for detecting and handling anomalies in bare metal servers are not only inefficient in detecting anomalies, but also inefficient in handling anomalies, and cannot meet the needs of large-scale bare metal server deployment. Summary of the Invention

[0004] This application provides a method, apparatus, device, and medium for handling anomalies in bare metal server detection, in order to solve the problem that existing methods for handling anomalies in bare metal server detection have low detection efficiency and low anomaly handling efficiency.

[0005] Firstly, this application provides a method for handling anomaly detection in a bare metal server, the method comprising:

[0006] Perform cloud inbound detection on the bare metal server;

[0007] If the detection fails, obtain the error message indicating the failure.

[0008] Based on the error message, execute the hardware configuration acquisition script to acquire the corresponding hardware configuration information of the bare metal server;

[0009] Identify the abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

[0010] In some embodiments, determining abnormal hardware configuration information in the hardware configuration information and modifying the abnormal hardware configuration information of the bare metal server includes:

[0011] Based on the error message, determine the correct first configuration information corresponding to the error message;

[0012] If the second configuration information corresponding to the error information in the hardware configuration information is inconsistent with the first configuration information, then the second configuration information is determined to be the abnormal hardware configuration information;

[0013] Modify the second configuration information of the bare metal server to the first configuration information.

[0014] In some embodiments, the method further includes:

[0015] Perform cloud ingress detection on the bare metal server again;

[0016] If the detection is successful, execute the network configuration acquisition script to collect the network configuration information of the bare metal server;

[0017] Identify the abnormal network configuration information in the network configuration information and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information.

[0018] In some embodiments, determining the abnormal network configuration information in the network configuration information includes:

[0019] According to the preset network configuration rules, determine whether each piece of information in the network configuration information conforms to the network configuration rules;

[0020] If the network configuration information contains information that does not conform to the network configuration rules, then the information that does not conform to the network configuration rules is identified as abnormal network configuration information.

[0021] In some embodiments, modifying the abnormal network configuration information of the bare metal server includes:

[0022] Modify the abnormal network configuration information according to the network configuration rules described above;

[0023] The step of updating the bare metal server's image driver based on the abnormal network configuration information includes:

[0024] If the abnormal network configuration information indicates that switch information is missing, then update the image driver of the bare metal server.

[0025] In some embodiments, the method further includes:

[0026] Execute the network configuration acquisition script again to acquire the network configuration information of the bare metal server once more;

[0027] If the network configuration information collected again is normal, then node characteristic information is added to the bare metal server.

[0028] In some embodiments, the method further includes:

[0029] In response to a user request, an instance is created on the bare metal server based on the resource requirement information in the user request.

[0030] Secondly, this application provides a processing device for detecting anomalies in bare metal servers, comprising:

[0031] The detection module is used to perform cloud ingress detection on the bare metal server;

[0032] The acquisition module is used to obtain the error message of the detection failure in the event of a detection failure.

[0033] The processing module is used to execute a hardware configuration acquisition script based on the error information to acquire the corresponding hardware configuration information of the bare metal server.

[0034] The processing module is further configured to determine abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

[0035] In some embodiments, the processing module is further configured to determine the correct first configuration information corresponding to the error information based on the error information;

[0036] The processing module is further configured to determine the second configuration information as the abnormal hardware configuration information when the second configuration information corresponding to the error information in the hardware configuration information is inconsistent with the first configuration information;

[0037] The processing module is further configured to modify the second configuration information of the bare metal server to the first configuration information.

[0038] In some embodiments, the detection module is further configured to perform cloud ingress detection on the bare metal server again;

[0039] The acquisition module is also used to execute a network configuration acquisition script to acquire the network configuration information of the bare metal server if the detection is successful.

[0040] The processing module is further configured to determine abnormal network configuration information in the network configuration information and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information.

[0041] In some embodiments, the apparatus further includes: a determination module;

[0042] The judgment module is used to determine whether each piece of information in the network configuration information conforms to the preset network configuration rules.

[0043] The processing module is further configured to, when there is information in the network configuration information that does not conform to the network configuration rules, determine the information that does not conform to the network configuration rules as the abnormal network configuration information.

[0044] In some embodiments, the processing module is further configured to modify the abnormal network configuration information according to the network configuration rules;

[0045] The processing module is also used to update the image driver of the bare metal server when the abnormal network configuration information is that the switch information is missing.

[0046] In some embodiments, the processing module is further configured to execute the network configuration acquisition script again to acquire the network configuration information of the bare metal server again;

[0047] The processing module is also used to add node characteristic information to the bare metal server when the network configuration information collected again is normal.

[0048] In some embodiments, the processing module is further configured to create an instance on the bare metal server in response to a user request, based on the resource requirement information in the user request.

[0049] Thirdly, this application provides a processing device for detecting anomalies in a bare metal server, including: a memory and a processor;

[0050] The memory stores computer-executed instructions;

[0051] The processor executes computer execution instructions stored in the memory, causing the processor to perform the bare metal server anomaly detection processing method as described in the first aspect and / or various possible embodiments of the first aspect.

[0052] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the bare-metal server anomaly detection processing method as described in the first aspect and / or various possible embodiments of the first aspect.

[0053] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the bare metal server anomaly detection processing method as described in the first aspect and / or various possible embodiments of the first aspect.

[0054] The bare metal server anomaly handling method provided in this application performs cloud-based detection on the bare metal server. If the detection fails, it obtains the error message and executes a hardware configuration collection script based on the error message to collect the corresponding bare metal server's hardware configuration information. It then identifies and modifies any abnormal hardware configuration information within the hardware configuration file. This method achieves automated anomaly detection and handling for bare metal servers, improving the efficiency of both detection and handling, and is suitable for large-scale bare metal server deployments. Attached Figure Description

[0055] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0056] Figure 1 A flowchart illustrating the method for handling anomalies in bare metal server detection provided in this application. Figure 1 ;

[0057] Figure 2 A flowchart illustrating the method for handling anomalies in bare metal server detection provided in this application. Figure 2 ;

[0058] Figure 3 A schematic diagram of the processing device for detecting anomalies in bare metal servers provided in this application;

[0059] Figure 4 A schematic diagram of the processing device for detecting anomalies in a bare metal server provided in this application.

[0060] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0061] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0062] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein.

[0063] In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0064] First, the terms used in this application will be explained.

[0065] OpenStack technology is an open-source cloud computing operating system that has become an important platform for managing data center resources. It manages compute, storage, and network resources through a series of Application Programming Interfaces (APIs) and web services, supporting the deployment and operation of large-scale virtual machines and enabling dynamic resource allocation and expansion. OpenStack's core components include compute (Nova), networking (Neutron), object storage (Swift), and block storage (Cinder), which together form the infrastructure of the cloud platform.

[0066] Ironic service: is a component in OpenStack primarily used for managing and operating bare metal servers. The Ironic component enables the management of physical servers without relying on virtualization technology, allowing them to be managed and used like virtual machines in a cloud environment.

[0067] Inspection Phase: Cloud Adoption Phase. This phase takes place after the bare metal server is connected to the network. It loads the boot image via PXE, detects its own host hardware configuration information, and reports it to the bare metal management node, enabling it to enter a schedulable state.

[0068] In an OpenStack environment, the deployment process of bare metal services (Ironic) is mainly divided into three stages: inspection, provisioning, and running. If the cloud inspection fails, it will seriously affect subsequent deployment and delivery. The existing method for handling bare metal server anomalies is usually that when the bare metal server fails to be installed in the cloud, the administrator will manually check and investigate various possible causes of the failure, and then manually handle the anomaly after locating it.

[0069] However, as the scale of cloud platform nodes expands, existing methods for detecting anomalies in bare metal servers are not only inefficient in detecting anomalies, but also inefficient in processing them, and cannot meet the needs of large-scale bare metal server deployment.

[0070] To address the aforementioned issues, this application provides a method for handling anomalies in bare metal server detection. Users control the bare metal server to perform cloud inbound detection via a cloud platform or command-line tools. If the cloud inbound detection fails, a hardware configuration collection script is executed based on the error information returned by the bare metal server to locate the problem and modify the identified abnormal hardware configuration information. If the cloud inbound detection succeeds, a network configuration collection script is executed to confirm the status. Based on the network configuration information of the bare metal server collected by the network configuration collection script, abnormal network configuration information is identified and modified or updated. Finally, after confirming successful cloud inbound detection and status confirmation, node characteristic information is added to the bare metal server. This method achieves automated anomaly detection and handling for bare metal servers, improving the efficiency of anomaly detection and handling, and is suitable for large-scale bare metal server deployments.

[0071] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0072] Figure 1 A flowchart illustrating the method for handling anomalies in bare metal server detection provided in this application embodiment. Figure 1 In this embodiment, the executing entity is, for example, a bare metal management server. Figure 1 As shown, the method for handling anomalies in bare metal server detection provided in this embodiment includes:

[0073] S101. Perform cloud access detection on bare metal servers.

[0074] Among them, cloud entry detection refers to the process of bare metal servers entering the cloud. Cloud entry detection is performed after the bare metal server connects to the network. Specifically, it loads the boot image through PXE, detects its own host hardware configuration information, and reports it to the bare metal management node, so that it enters a schedulable state. The result of cloud entry detection can confirm whether the bare metal server's cloud entry operation is successful. In addition, there can be one or more bare metal servers.

[0075] For example, users can log in to the management server system through the cloud platform's front-end interface or command-line interface, and control the bare metal server to perform corresponding cloud inbound operations through the management server. After the cloud inbound operation is completed, users can obtain the cloud inbound detection results fed back by the bare metal server.

[0076] S102. In the event of a detection failure, obtain the error message indicating the failure.

[0077] If the cloud inbound detection results from the bare metal server indicate that the bare metal server's cloud inbound process has failed, the error message indicating the failure will be further extracted from the detection results. This information will facilitate subsequent error localization and correction. The error message includes the cause of the error, such as incorrect Intelligent Platform Management Interface (IPMI) level, incorrect IPMI out-of-band username and password, or non-standard hardware configuration.

[0078] S103. Execute the hardware configuration acquisition script based on the error message to collect the hardware configuration information of the corresponding bare metal server.

[0079] There is a correspondence between the hardware configuration acquisition script and the error reasons in the error message. The hardware configuration acquisition script is pre-written and can access the bare metal server and obtain the corresponding hardware configuration information by executing corresponding query commands. For example, when the error reason is IPMI level error, the hardware configuration acquisition script is used to collect the IPMI protocol level information of the bare metal server; when the error reason is IPMI out-of-band user and password error, the hardware configuration acquisition script is used to collect the out-of-band account and password information of the bare metal server; when the error reason is non-standard hardware configuration, the hardware configuration acquisition script is used to collect the CPU architecture and boot mode of the bare metal server.

[0080] For example, by calling the Ironic component, it can be ensured that the Ironic deployment has a PXE network set up so that bare metal servers can be booted over the network. Ironic can then load a temporary operating system image from the network via PXE. This image includes a hardware configuration acquisition script. In the temporary operating system environment, the hardware configuration acquisition script is run to collect hardware configuration information from the database.

[0081] S104. Identify the abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

[0082] By comparing the collected hardware configuration information with the standard configuration, abnormal hardware configuration information can be identified. The abnormal hardware configuration information of the bare metal server can be modified in ways such as: changing the boot mode, updating the IPMI protocol level, resetting the IPMI account, etc.

[0083] The bare metal server anomaly handling method provided in this embodiment performs cloud access detection on the bare metal server. In the event of detection failure, it obtains the failure error information, executes a hardware configuration collection script based on the error information to collect the corresponding bare metal server's hardware configuration information, identifies abnormal hardware configuration information in the hardware configuration information, and modifies the abnormal hardware configuration information of the bare metal server. This method realizes automated anomaly detection and handling of bare metal servers, improving the efficiency of anomaly detection and handling.

[0084] Figure 2 A flowchart illustrating the method for handling anomalies in bare metal server detection provided in this application. Figure 2 ,like Figure 2 As shown, in this embodiment... Figure 1 Based on the embodiments, the method for handling anomalies in bare metal server detection is described in detail. The method for handling anomalies in bare metal server detection provided in this embodiment includes:

[0085] S201. Perform cloud ingress detection on bare metal servers.

[0086] Step S201 is similar to step S101 above, and will not be repeated here.

[0087] S202. Determine whether the cloud entry detection is successful. If yes, proceed to step S203; otherwise, proceed to step S204.

[0088] The status information returned after the bare metal server enters the cloud can be used to determine whether the cloud entry test was successful. If the status information indicates that the cloud entry test was successful, it means that the hardware configuration information of the bare metal server is normal, but the network configuration needs to be further tested. If the status information indicates that the cloud entry test failed, it means that the hardware configuration information of the bare metal server is abnormal, and the problem needs to be located by executing the preset hardware configuration collection script.

[0089] S203. Execute the network configuration collection script to collect network configuration information of the bare metal server.

[0090] The network configuration acquisition script is a pre-written script that can access the bare metal server and obtain network configuration information by executing corresponding query commands. The network configuration information may include, for example, switch information and its port information, bare metal server port information, image driver information, etc.

[0091] S204. Obtain error messages for failed detections.

[0092] Step S204 is similar to step S102 above, and will not be described again here.

[0093] S205. Execute the hardware configuration acquisition script based on the error message to collect the hardware configuration information of the corresponding bare metal server.

[0094] Step S205 is similar to step S103 above, and will not be described again here.

[0095] S206. Determine the correct first configuration information corresponding to the error message based on the error message.

[0096] Since the error message includes the reason for the error, the correct configuration information, namely the first configuration information, can be determined based on the error message after the bare metal server fails to enter the cloud. The first configuration information refers to the standard configuration information stored in the database.

[0097] For example, when the error message is that the IPMI security protocol level does not meet the requirements, the correct IPMI security protocol level can be retrieved from the database by configuring the data acquisition script through hardware; when the error message is that the IPMI out-of-band username and password are incorrect, the credential information corresponding to the username and password of the account can be determined; when the error message is that the boot mode is incorrect, the correct boot mode corresponding to the CPU architecture of the bare metal server can be determined.

[0098] S207. When the second configuration information corresponding to the error message in the hardware configuration information is inconsistent with the first configuration information, the second configuration information is determined to be abnormal hardware configuration information.

[0099] The second configuration information refers to the actual configuration information of the bare metal server corresponding to the error message, while the first configuration information refers to the correct configuration information corresponding to the second configuration information.

[0100] For example, when the second configuration information is IPMI security protocol level 1.5, but the first configuration information indicates that the correct IPMI security protocol level is level 2, it can be determined that IPMI security protocol level 1.5 is abnormal hardware configuration information; when the second configuration information is the current IPMI username and password, but the username and password information indicated by the first configuration information is inconsistent with those in the second configuration information, it can be determined that the current username and password information is abnormal hardware configuration information; when the second configuration information indicates that the actual configured boot mode is UEFI mode, but the first configuration information indicates that the correct boot mode should be Legacy mode, it can be determined that UEFI mode is abnormal hardware configuration information.

[0101] S208. Modify the second configuration information of the bare metal server to the first configuration information.

[0102] The purpose of this step is to modify the abnormal hardware configuration information to the correct hardware configuration information, so as to handle the abnormal hardware configuration problem.

[0103] After completing step S208, step S201 can be executed again, that is, the bare metal server is re-performed cloud entry detection, so that the bare metal server can re-perform PXE boot, boot image loading, hardware information collection and information reporting, and after confirming that the cloud entry detection is successful.

[0104] S209. Determine if there is any abnormality in the network configuration information. If yes, proceed to step S210; otherwise, proceed to step S211.

[0105] If the cloud access test is successful and the hardware configuration information of the bare metal server is normal, it is necessary to further check whether the network configuration is normal. By executing the network configuration collection script, the network configuration information of the bare metal server is collected, and it is determined whether there is any abnormality in the network configuration information. If so, the abnormal network configuration information needs to be identified first, and then the abnormal network configuration information is processed; if not, node characteristic information is added to the bare metal server.

[0106] S210. Determine the abnormal network configuration information in the network configuration information and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information.

[0107] For example, the following is a specific implementation method for determining abnormal network configuration information: according to preset network configuration rules, determine whether each piece of information in the network configuration information conforms to the network configuration rules;

[0108] If any information in the network configuration information does not conform to the network configuration rules, then the information that does not conform to the network configuration rules will be identified as abnormal network configuration information.

[0109] Among them, network configuration rules refer to the specific rules for the pre-defined network configuration of bare metal servers, including but not limited to IP address allocation, gateway configuration, interface configuration, etc. For example, the serial numbers of two service ports of the same bare metal server on a set of switches must be consistent.

[0110] Understandably, network configuration information that does not conform to network configuration rules means that the actual network configuration information is inconsistent with the correct network configuration information. Such abnormal network configuration information may not affect the bare metal server's cloud deployment, but it will affect the subsequent deployment and operation of the bare metal server. Abnormal network configuration information may include missing switch information, inconsistent switch side connections, single port information, etc.

[0111] For example, abnormal network configuration information can be modified according to network configuration rules.

[0112] Understandably, the network configuration rules include the correct network configuration information corresponding to the abnormal network configuration information. Therefore, the abnormal network configuration information can be modified based on the correct network configuration information.

[0113] For example, if the abnormal network configuration information indicates missing switch information, the bare metal server's image driver will be updated; if two service ports of the same bare metal server have inconsistent serial numbers on a set of switches, the port serial numbers of the switches will be adjusted.

[0114] In some embodiments, after executing step S210, the execution can be returned to step S203, that is, the network configuration acquisition script is executed again to collect the network configuration information of the bare metal server again, thereby verifying whether the network configuration of the bare metal server has returned to normal.

[0115] If the network configuration information collected again is normal, then node characteristic information is added to the bare metal server.

[0116] S211. Add node characteristic information to the bare metal server.

[0117] Among them, node trait information is used to mark the attributes of bare metal servers, such as hardware characteristics, performance indicators, network characteristics or other specific hardware functions.

[0118] Understandably, node characteristic information can only be added to a bare metal server after the bare metal server has successfully passed the cloud entry test and there are no abnormalities in the network configuration information. This adds node attribute tag information to the bare metal server, which facilitates subsequent instance activation and resource access.

[0119] S212. In response to a user request, create an instance on the bare metal server based on the resource requirement information in the user request.

[0120] In this step, OpenStack completes the hardware and network configuration checks of the connected bare metal server. After adding node characteristic information to the node, the bare metal server is ready to be scheduled. Therefore, after receiving a user request, the management server can select the most suitable bare metal server to meet the user's request based on the resource requirements in the user's request and the node characteristic information of all available nodes. The management server then calls the Ironic component to perform hardware configuration, PXE booting, operating system deployment, and instance creation operations on the bare metal server. The created instance information is recorded in the database to provide users with corresponding access interfaces, such as IP address and login credentials, so that users can access their newly created bare metal instance through this information.

[0121] The bare metal server anomaly handling method provided in this application embodiment obtains the failure error information when the bare metal server fails cloud access detection, executes a network configuration collection script to collect the network configuration information of the bare metal server, determines the correct first configuration information corresponding to the error information based on the error information, and when the second configuration information corresponding to the error information in the hardware configuration information is inconsistent with the first configuration information, the second configuration information is identified as abnormal hardware configuration information, the second configuration information of the bare metal server is modified to the first configuration information, and the cloud access detection of the bare metal server is performed again. If the detection is successful, the network configuration collection script is executed again to collect the network configuration information of the bare metal server, identify abnormal network configuration information in the network configuration information, and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information, until the network configuration information is normal. Finally, in response to the user request, an instance is created on the bare metal server based on the resource requirement information in the user request. This method realizes automated anomaly detection and handling of bare metal servers, improving the efficiency of anomaly detection and handling.

[0122] Figure 3 This is a schematic diagram of the processing device for detecting anomalies in bare metal servers provided in this application, as shown below. Figure 3As shown, the bare metal server anomaly detection processing device 300 provided in this embodiment includes:

[0123] Detection module 301 is used to perform cloud access detection on the bare metal server;

[0124] The acquisition module 302 is used to acquire the error message of the detection failure in the event of a detection failure.

[0125] The processing module 303 is used to execute a hardware configuration acquisition script based on the error information to acquire the corresponding hardware configuration information of the bare metal server.

[0126] The processing module 303 is further configured to determine abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

[0127] In some embodiments, the processing module 303 is further configured to determine the correct first configuration information corresponding to the error information based on the error information;

[0128] The processing module 303 is further configured to determine the second configuration information as the abnormal hardware configuration information when the second configuration information corresponding to the error information in the hardware configuration information is inconsistent with the first configuration information;

[0129] The processing module 303 is further configured to modify the second configuration information of the bare metal server to the first configuration information.

[0130] In some embodiments, the detection module 301 is further configured to perform cloud ingress detection on the bare metal server again;

[0131] The acquisition module 302 is also used to execute a network configuration acquisition script to acquire the network configuration information of the bare metal server if the detection is successful.

[0132] The processing module 303 is further configured to determine abnormal network configuration information in the network configuration information and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information.

[0133] In some embodiments, the device further includes: a determination module 304;

[0134] The judgment module 304 is used to judge whether each piece of information in the network configuration information conforms to the preset network configuration rules.

[0135] The processing module 303 is further configured to, when there is information in the network configuration information that does not conform to the network configuration rules, determine the information that does not conform to the network configuration rules as the abnormal network configuration information.

[0136] In some embodiments, the processing module 303 is further configured to modify the abnormal network configuration information according to the network configuration rules;

[0137] The processing module 303 is also used to update the image driver of the bare metal server when the abnormal network configuration information is that the switch information is missing.

[0138] In some embodiments, the processing module 303 is further configured to execute the network configuration acquisition script again to acquire the network configuration information of the bare metal server again;

[0139] The processing module 303 is also used to add node characteristic information to the bare metal server when the network configuration information collected again is normal.

[0140] In some embodiments, the processing module 303 is further configured to, in response to a user request, create an instance on the bare metal server based on the resource requirement information in the user request.

[0141] Figure 4 This is a schematic diagram of the processing device for detecting anomalies in bare-metal servers provided in this application. Figure 4 As shown, this application provides a processing device for detecting anomalies in bare metal servers. The bare metal server anomaly detection processing device 400 includes: a receiver 401, a transmitter 402, a processor 403, and a memory 404.

[0142] Receiver 401 is used to receive instructions and data;

[0143] Transmitter 402 is used to send commands and data;

[0144] Memory 404 is used to store instructions executed by the computer;

[0145] The processor 403 is configured to execute computer execution instructions stored in the memory 404 to implement the various steps of the bare metal server detection anomaly handling method in the above embodiments. For details, please refer to the relevant descriptions in the foregoing embodiments of the bare metal server detection anomaly handling method.

[0146] Alternatively, the memory 404 can be either standalone or integrated with the processor 403.

[0147] When the memory 404 is set up independently, the bare metal server's anomaly detection processing device also includes a bus for connecting the memory 404 and the processor 403.

[0148] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for handling abnormal detection in bare metal servers.

[0149] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method for handling abnormal detection in a bare-metal server.

[0150] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0151] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0152] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for handling anomalies detected in bare metal servers, characterized in that, The method includes: Perform cloud inbound detection on the bare metal server; If the detection fails, obtain the error message indicating the failure. Based on the error message, execute the hardware configuration acquisition script to acquire the corresponding hardware configuration information of the bare metal server; Identify the abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

2. The method according to claim 1, characterized in that, The step of determining the abnormal hardware configuration information in the hardware configuration information and modifying the abnormal hardware configuration information of the bare metal server includes: Based on the error message, determine the correct first configuration information corresponding to the error message; If the second configuration information corresponding to the error information in the hardware configuration information is inconsistent with the first configuration information, then the second configuration information is determined to be the abnormal hardware configuration information; Modify the second configuration information of the bare metal server to the first configuration information.

3. The method according to claim 1, characterized in that, Also includes: Perform cloud ingress detection on the bare metal server again; If the detection is successful, execute the network configuration acquisition script to collect the network configuration information of the bare metal server; Identify the abnormal network configuration information in the network configuration information and modify the abnormal network configuration information of the bare metal server, or update the image driver of the bare metal server based on the abnormal network configuration information.

4. The method according to claim 3, characterized in that, The step of determining abnormal network configuration information in the network configuration information includes: According to the preset network configuration rules, determine whether each piece of information in the network configuration information conforms to the network configuration rules; If the network configuration information contains information that does not conform to the network configuration rules, then the information that does not conform to the network configuration rules is identified as abnormal network configuration information.

5. The method according to claim 4, characterized in that, The modification of the abnormal network configuration information of the bare metal server includes: Modify the abnormal network configuration information according to the network configuration rules described above; The step of updating the bare metal server's image driver based on the abnormal network configuration information includes: If the abnormal network configuration information indicates that switch information is missing, then update the image driver of the bare metal server.

6. The method according to claim 3, characterized in that, Also includes: Execute the network configuration acquisition script again to acquire the network configuration information of the bare metal server once more; If the network configuration information collected again is normal, then node characteristic information is added to the bare metal server.

7. The method according to claim 6, characterized in that, Also includes: In response to a user request, an instance is created on the bare metal server based on the resource requirement information in the user request.

8. A processing device for detecting anomalies in bare metal servers, characterized in that, The device includes: The detection module is used to perform cloud ingress detection on the bare metal server; The acquisition module is used to obtain the error message of the detection failure in the event of a detection failure. The processing module is used to execute a hardware configuration acquisition script based on the error information to acquire the corresponding hardware configuration information of the bare metal server. The processing module is further configured to determine abnormal hardware configuration information in the hardware configuration information and modify the abnormal hardware configuration information of the bare metal server.

9. A processing device for detecting anomalies in bare metal servers, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the bare metal server anomaly detection processing method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the bare metal server anomaly detection processing method as described in any one of claims 1-7.

Images