A bare metal device registration admission method, device, equipment and storage medium

Abstract

The application discloses a bare metal device registration access method and device, equipment and a storage medium, relates to the technical field of bare metal device management, and comprises the following steps: creating a hardware detection task, occupying a target bare metal device, and controlling the target bare metal device to be powered on and recording the power-on time when the occupation is successful; querying hardware reporting data according to the MAC address of the target bare metal device, taking the hardware reporting data after the power-on time as valid hardware reporting data, and then generating a structured hardware specification; obtaining a hardware ID according to the structured hardware specification, and binding the hardware ID to the target bare metal device; when hardware compliance auditing is needed, the target bare metal device is subjected to hardware compliance auditing; and if the auditing is passed, the target bare metal device is registered into a device pool. The method can prevent old hardware reporting misuse and non-standard hardware from entering the device pool, thereby improving the accuracy of bare metal device registration access.

Description

Technical Field

[0001] This application relates to the field of bare metal equipment management technology, and in particular to a method, apparatus, device and storage medium for registration and access of bare metal equipment. Background Technology

[0002] After bare metal devices are listed, they typically only undergo device discovery, wiring identification, or MAC address identification; this does not mean the device is ready for service calls. To make bare metal devices eligible for service calls, registration and access control are required for the listed devices. However, the existing technologies for bare metal device registration and access control suffer from inaccuracies.

[0003] Therefore, how to solve the above-mentioned technical defects has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, device, and storage medium for registration and access of bare metal equipment, which can improve the accuracy of registration and access of bare metal equipment.

[0005] To address the aforementioned technical problems, this application provides a method for registration and access approval of bare metal equipment, comprising: Create a hardware probe task; if an unfinished probe task already exists in the same area, the creation of a new probe task will be rejected. The system occupies the target bare metal device and creates a detection record for it; the target bare metal device is a bare metal device that has been put into storage and is to be detected; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the system controls the target bare metal device to be powered on and records the power-on time. The hardware reporting data is queried based on the MAC address of the target bare metal device, and the hardware reporting data after the power-on time is accepted as the valid hardware reporting data. Generate structured hardware specifications based on the valid hardware report data; Obtain the hardware ID according to the structured hardware specifications, and bind the hardware ID to the target bare metal device; If the target bare metal is registered for the first time, a hardware compliance audit will be conducted on the target bare metal device. If the target bare metal device is not registered for the first time, then query the historical hardware specifications of the target bare metal device. If it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications, then conduct a hardware compliance audit on the target bare metal device. If the review is approved, the target bare metal device will be registered into the device pool.

[0006] In some embodiments, generating structured hardware specifications based on the valid hardware reporting data includes: Filter the valid hardware reported data according to the hardware type, group them according to the sequence number, merge multiple data items or data values ​​of the same component into a structured object, and obtain the fields corresponding to each hardware. The structured hardware specification is generated based on the fields corresponding to the hardware by calling the corresponding parsing rules of the hardware.

[0007] In some embodiments, the method further includes the following steps before obtaining the hardware ID based on the structured hardware specification: Field cleaning is performed on the structured hardware specifications.

[0008] In some embodiments, obtaining the hardware ID based on the structured hardware specification includes: The corresponding hardware ID is retrieved from the platform hardware library based on the hardware source or BIOS version in the structured hardware specification. If found, the corresponding hardware ID is obtained from the platform's hardware library; If no record is found and the corresponding fields for the hardware are complete, the existing platform standard hardware record identifier will be reused, or a new platform hardware basic record will be added and the corresponding identifier will be obtained if the fields are valid. If no results are found and the corresponding fields for the hardware are incomplete, the record is considered to have incomplete or unmaintained hardware information.

[0009] In some embodiments, it also includes: Record the detection batch number, detection record, failure reason, hardware configuration relationship, and review status, and provide feedback on the recorded content to the target.

[0010] In some embodiments, it also includes: Receive the detection configuration and start the detection environment according to the detection configuration so as to control the target bare metal device to power on in the detection environment.

[0011] In some embodiments, hardware compliance auditing of the target bare metal device includes: querying a standard motherboard library based on the motherboard model, matching the BIOS version with the BIOS rules in the standard motherboard library, and querying a standard GPU library based on the GPU hardware source identifier; if the motherboard, BIOS, and GPU all meet the standard conditions, then it is determined that the target bare metal device does not need to be submitted for auditing; if any one of the motherboard, BIOS, and GPU does not meet the standard conditions, then existing audit records are queried based on the identifier of the target bare metal device, the motherboard model, the BIOS version, and the GPU hardware source identifier. If no audit record is found or the audit record is in a failed state, audit submission data containing the target bare metal device's MAC address, region information, motherboard information, BIOS information, and GPU information will be generated, and hardware compliance audit will be submitted when the automatic submission conditions are met.

[0012] To address the aforementioned technical problems, this application also provides a bare metal equipment registration and access device, comprising: A creation unit is used to create hardware probing tasks; if an unfinished probing task already exists in the same area, the creation of a new probing task will be refused. An occupancy unit is used to occupy a target bare metal device and create a detection record for the target bare metal device; the target bare metal device is a bare metal device that has been put into operation and is to be detected; if the occupancy fails, the reason for the failure is recorded; if the occupancy is successful, the target bare metal device is powered on and the power-on time is recorded. The query unit is used to query hardware reporting data based on the MAC address of the target bare metal device, and to accept hardware reporting data after power-on time as valid hardware reporting data. A generation unit is used to generate structured hardware specifications based on the valid hardware reporting data; A binding unit is used to obtain a hardware ID according to the structured hardware specifications and bind the hardware ID to the target bare metal device; The first review unit is used to conduct a hardware compliance review of the target bare metal device if the target bare metal is registered for the first time. The second review unit is used to query the historical hardware specifications of the target bare metal device if the target bare metal device is not registered for the first time, and to conduct a hardware compliance review of the target bare metal device if it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications. The registration unit is used to register the target bare metal device into the device pool if the review is approved.

[0013] To address the aforementioned technical problems, this application also provides an electronic device, comprising: Memory, used to store computer programs; A processor, configured to implement the steps of the bare metal device registration admission method as described above when executing the computer program.

[0014] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the bare metal device registration access method described above.

[0015] The bare metal device registration access method provided in this application includes: creating a hardware detection task; wherein, if there is an unfinished detection task in the same area, the creation of a new detection task is refused; occupying a target bare metal device and creating a detection record for the target bare metal device; the target bare metal device is a bare metal device to be detected that has been put on the rack; wherein, if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the target bare metal device is powered on and the power-on time is recorded; querying hardware reporting data according to the MAC address of the target bare metal device, and accepting the hardware reporting data after the power-on time as the valid hardware reporting data. According to the valid hardware reporting data, a structured hardware specification is generated; a hardware ID is obtained based on the structured hardware specification, and the hardware ID is bound to the target bare metal device; if the target bare metal device is registered for the first time, a hardware compliance audit is performed on the target bare metal device; if the target bare metal device is not registered for the first time, the historical hardware specification of the target bare metal device is queried; if it is determined that the target hardware has changed based on the historical hardware specification and the structured hardware specification, a hardware compliance audit is performed on the target bare metal device; if the audit is passed, the target bare metal device is registered into the device pool.

[0016] As can be seen, the bare metal device registration and access method provided in this application records the power-on time of unregistered bare metal devices already on the rack as a time benchmark, and accurately filters valid hardware reporting data by combining it with MAC address, avoiding data distortion caused by client caching and expired hardware information left over from historical power-ups. Structured hardware specifications are generated based on valid hardware reporting data, eliminating differences caused by different data sources and hardware types. After obtaining the hardware ID and binding it to the bare metal device to be detected, the device undergoes hardware compliance review. Upon successful review, it is registered into the device pool, thereby improving the accuracy of bare metal device registration and access.

[0017] The bare metal equipment registration and access device, equipment, and computer-readable storage medium provided in this application all have the aforementioned technical effects. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A schematic flowchart illustrating a bare metal device registration and access method provided in an embodiment of this application; Figure 2This is a schematic diagram of a bare metal equipment registration and access system provided in an embodiment of this application; Figure 3 A hardware specification detection and control flowchart provided in this application embodiment; Figure 4 This is a flowchart illustrating a hardware reporting parsing and standardized mapping process provided in an embodiment of this application. Figure 5 This application provides a flowchart of a hardware compliance review and registration process. Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0020] The core of this application is to provide a method, apparatus, device, and storage medium for registration and access of bare metal equipment, which can improve the accuracy of registration and access of bare metal equipment.

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments 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.

[0022] Please refer to Figure 1 , Figure 1 This is a schematic flowchart illustrating a bare metal device registration and access method provided in an embodiment of this application. (Refer to...) Figure 1 As shown, the method includes: S101: Create a hardware probe task; if an unfinished probe task already exists in the same area, the creation of a new probe task will be rejected. S102: Occupy the target bare metal device and create a detection record for the target bare metal device; the target bare metal device is a bare metal device to be detected that has been put on the rack; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the target bare metal device is powered on and the power-on time is recorded. S103: Query the hardware reporting data according to the MAC address of the target bare metal device, and accept the hardware reporting data after the power-on time as the valid hardware reporting data; S104: Generate structured hardware specifications based on the valid hardware reporting data; S105: Obtain the hardware ID according to the structured hardware specifications, and bind the hardware ID to the target bare metal device; S106 If the target bare metal is registered for the first time, then a hardware compliance audit is performed on the target bare metal device; S107: If the target bare metal device is not registered for the first time, query the historical hardware specifications of the target bare metal device. If it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications, then conduct a hardware compliance audit on the target bare metal device. S108: If the review is approved, the target bare metal device will be registered into the device pool.

[0023] Create a hardware detection task; if an unfinished detection task already exists in the same area, the creation of a new detection task will be rejected. The target bare metal device can be occupied through a unified scheduling service, thus preventing the target bare metal device from being occupied by other service scheduling, hardware detection tasks, or maintenance tasks simultaneously. Create a detection record for the target bare metal device; the target bare metal device is a bare metal device that has been racked and is awaiting detection; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the target bare metal device is powered on and the power-on time is recorded.

[0024] Hardware reporting data is queried by MAC address, and only hardware reporting data after the current power-on time is accepted. If the target bare metal device does not report hardware information within the timeout period, it can be distinguished as either powered on but no hardware information was found or failed to report successful power-on, depending on whether a successful power-on report was submitted. Structured hardware specifications are generated based on the valid hardware reporting data.

[0025] In some embodiments, generating structured hardware specifications based on the valid hardware reporting data includes: Filter the valid hardware reported data according to the hardware type, group them according to the sequence number, merge multiple data items or data values ​​of the same component into a structured object, and obtain the fields corresponding to each hardware. The structured hardware specification is generated based on the fields corresponding to the hardware by calling the corresponding parsing rules of the hardware.

[0026] The valid hardware reports are integrated by hardware type and sequence number to form a set of fields for each hardware component. Then, the parsing rules for CPU, GPU, memory, motherboard, network card, and BIOS are called separately to generate structured hardware specifications. The method of integrating the valid hardware reports by hardware type and sequence number is as follows: the valid hardware reports are first filtered by hardwareType, then grouped by sequence, and multiple dataItem / dataValue records of the same component are merged into a structured object.

[0027] Then, the hardware ID is obtained based on the structured hardware specifications.

[0028] In some embodiments, the method further includes the following steps before obtaining the hardware ID based on the structured hardware specification: Field cleaning is performed on the structured hardware specifications.

[0029] Perform field cleaning on structured hardware specifications. For example, extract the standard model number from the original name for CPU models, extract the standard RTX or GTX expression from the original name for GPU models, convert the units for GPU memory capacity and network card bandwidth, remove leading and trailing spaces from motherboard models, and set the default value when memory brand is missing.

[0030] In some embodiments, obtaining the hardware ID based on the structured hardware specification includes: The corresponding hardware ID is retrieved from the platform hardware library based on the hardware source or BIOS version in the structured hardware specification. If found, the corresponding hardware ID is obtained from the platform's hardware library; If no record is found and the corresponding fields for the hardware are complete, the existing platform standard hardware record identifier will be reused, or a new platform hardware basic record will be added and the corresponding identifier will be obtained if the fields are valid. If no results are found and the corresponding fields for the hardware are incomplete, the record is considered to have incomplete or unmaintained hardware information.

[0031] The system queries the platform hardware library based on the hardware source identifier or BIOS version. If an existing hardware record is found, the platform's standard hardware ID is obtained. If no record is found but the fields are valid, a new hardware record is created and the platform's standard hardware ID is obtained. If the fields are incomplete, the record is considered to have incomplete or unmaintained hardware information.

[0032] Bind the obtained standard hardware IDs of CPU, GPU, memory, motherboard, network card, and BIOS to the target bare metal device. If the target bare metal device is already registered, modification of the hardware relationship will be refused; if the target bare metal device is not registered, configuration will be allowed.

[0033] If the target bare metal device is already registered, it will not be reviewed again. If it is the first time registering, it will be reviewed. If the target bare metal device has been deregistered and then relisted, its historical hardware specifications will be checked, and a decision will be made on whether to re-review it based on whether the key hardware, i.e., the target hardware, has changed.

[0034] In some embodiments, hardware compliance auditing of the target bare metal device includes: querying a standard motherboard library based on the motherboard model, matching the BIOS version with the BIOS rules in the standard motherboard library, and querying a standard GPU library based on the GPU hardware source identifier; if the motherboard, BIOS, and GPU all meet the standard conditions, then it is determined that the target bare metal device does not need to be submitted for auditing; if any one of the motherboard, BIOS, and GPU does not meet the standard conditions, then existing audit records are queried based on the identifier of the target bare metal device, the motherboard model, the BIOS version, and the GPU hardware source identifier. If no audit record is found or the audit record is in a failed state, audit submission data containing the target bare metal device's MAC address, region information, motherboard information, BIOS information, and GPU information will be generated, and hardware compliance audit will be submitted when the automatic submission conditions are met.

[0035] You can query the standard motherboard library, standard GPU library, and BIOS rules. If the motherboard model, BIOS version, and GPU hardware identifier all meet the standard conditions, it will be marked as requiring no review. If there are unsubmitted, failed reviews, or non-standard combinations, the automatic submission process will begin. Submit the hardware combinations that require review. The submission content can include bare metal device identifier, MAC address, motherboard model, motherboard name, BIOS version, GPU hardware identifier, GPU name, and region information.

[0036] Registration admission is determined based on the standard library hit results or the review results. Bare metal devices with complete hardware information and that meet standardization requirements are allowed to register into the device pool; devices with missing hardware information, that are not maintained, or that have failed the review are not allowed to register into the device pool.

[0037] In some embodiments, it also includes: Record the detection batch number, detection record, failure reason, hardware configuration relationship, and review status, and provide feedback on the recorded content to the target.

[0038] The target audience can be operators. Records include detection batches, detection logs, failure reasons, hardware configuration relationships, and review status, and can provide feedback to operators via real-time messages or task results.

[0039] In some embodiments, it also includes: Receive the detection configuration and start the detection environment according to the detection configuration so as to control the target bare metal device to power on in the detection environment.

[0040] The bare metal device registration and access method provided in the above embodiments of this application can be implemented by a bare metal device registration and access system. (See reference...) Figure 2As shown, the system includes a detection control layer, a reporting and parsing layer, a standardization layer, and an access control layer. The detection control layer is used to create detection batches, control mutually exclusive areas, occupy the device to be detected (i.e., the target bare metal device), and start the detection environment; the reporting and parsing layer is used to filter the hardware reporting data after the current power-on and parse the raw fields into structured hardware specifications; the standardization layer is used to map the original hardware identifier to the platform's standard hardware ID and configure it to the bare metal device; the access control layer is used to determine whether the device is allowed to register into the device pool based on the standard hardware library, audit records, and historical hardware differences.

[0041] As a specific implementation, the system may include a detection batch and area mutual exclusion module, a device occupancy and detection environment startup module, a current power-on valid reporting filtering module, a type-based hardware specification parsing module, a platform standard hardware ID mapping module, a bare metal device hardware relationship configuration module, a standard hardware library compliance review module, a historical hardware difference review module, an automatic submission and registration access module, and an anomaly classification and result feedback module.

[0042] The probe batch and region mutual exclusion module is used to create hardware specification probe tasks within the same region and prevent multiple probe batches from operating on bare metal devices in the same region simultaneously through region-level mutual exclusion control. This module generates a batch number for each probe and records the probe device, probe configuration, task status, and operator information. If there are already unfinished probe tasks in the same region, the system rejects new tasks or clears timed-out tasks first.

[0043] The Device Occupancy and Detection Environment Startup module is used to occupy bare metal devices through a unified scheduling service before detection, and to create or start the client, network environment, and startup scheme required for detection according to the detection configuration. This module can prevent the device to be detected from being occupied by other service scheduling, hardware detection tasks, or maintenance tasks at the same time.

[0044] The valid power-on reporting filtering module records the device's power-on time and only accepts records with a reporting time later than the current power-on time when querying hardware reporting data. This module excludes historical power-on data, data from previous probes, or old hardware data cached by the client, ensuring that the current specification probe results correspond to the current device hardware status.

[0045] The hardware specification parsing module is used to integrate multiple hardware fields reported by the client according to hardware type and serial number, and parse them into structured specifications such as CPU, GPU, memory, motherboard, network card, and BIOS. Different parsing rules are used for different hardware types. For example, CPU model regular expression normalization, GPU model normalization, video memory capacity unit conversion, network card bandwidth unit conversion, motherboard model space removal, and memory brand default handling, etc.

[0046] The platform standard hardware ID mapping module is used to map structured hardware specifications to platform-recognizable standard hardware IDs. For hardware such as CPU, GPU, memory, motherboard, and network card, the system can query the platform hardware library based on the hardware source identifier; for BIOS, the system can query the platform BIOS library based on the BIOS version. If a corresponding record already exists in the platform hardware library, its standard hardware ID is reused; if it does not exist but the fields are valid, a new hardware basic record is added and the standard hardware ID is returned; if the fields are incomplete or invalid, the record is marked as unmaintained or incomplete.

[0047] The bare metal device hardware relationship configuration module is used to bind standard hardware IDs such as CPU, GPU, memory, motherboard, network card, and BIOS to bare metal devices. Before configuration, this module verifies whether the bare metal device exists and is in an unregistered state. Registered devices are not allowed to have their hardware relationships modified arbitrarily to avoid inconsistencies in scheduling data caused by device specifications being overwritten after registration.

[0048] The standard hardware library compliance audit module is used to determine whether the key hardware of bare metal devices conforms to platform standards. The system can query the motherboard model from the standard motherboard library, query the GPU hardware identifier from the standard GPU library, and combine this with BIOS version rules to determine if a match is made. The motherboard's BIOS rules can support exact matching and wildcard matching. If the standard motherboard, BIOS, and standard GPU all match, the device does not need to be submitted for review; if no match is found, no review is submitted, or the review fails, the review submission process begins.

[0049] The historical hardware difference review module is used to process bare metal devices that have been deregistered and then relisted. For devices registered for the first time, the system requires a hardware compliance review; for devices that have already been registered, the system does not conduct a duplicate review; for devices that have been deregistered and then relisted, the system queries the historical hardware specifications near the deregistration time. If the key hardware has not changed, the review can be skipped; if the key hardware has changed and the new hardware does not match the standard library, a new review is triggered.

[0050] The automatic submission and registration admission module is used to automatically submit non-standard hardware combinations that have not been submitted or have failed the review for review, and to determine whether to allow registration into the device pool based on the review status. This module links hardware specification detection results, standard library hit results, review results, and device registration status, making the registration process subject to hardware compliance status.

[0051] The anomaly classification and result feedback module records and reports the reasons for failures during the hardware detection process, including no CPU information found, no GPU information found, no memory information found, incomplete hardware information, hardware not being maintained, the device being powered on but no hardware information being found, and the device not reporting successful boot. This module can provide feedback to maintenance personnel via real-time messages or task results.

[0052] refer to Figures 3 to 5 As shown, the following describes a specific implementation method: The system selects bare metal devices that have been put on the shelf but have not yet been registered into the device pool, and receives the detection configuration and device list.

[0053] The system creates hardware specification probe batches and sets probe mutual exclusion flags at the region level. If there are unfinished probe tasks in the same region, the system will refuse to create a new task or clean up timed-out tasks and retry.

[0054] The system uses a unified scheduling service to acquire bare metal devices to be probed and creates a probe record for each device. Devices that fail to acquire the device are recorded with the reason for the failure and are not included in subsequent probes.

[0055] The system initiates the detection environment according to the detection configuration and controls the bare metal device to power on. The system records the power-on time and confirms whether the device has been successfully powered on by querying the power status.

[0056] The system queries hardware reporting data by device MAC address and only accepts reports submitted after the current power-on time. If the device fails to report hardware information within the timeout period, it is categorized as either powered on but no hardware information was found, or the device failed to report a successful power-on, depending on whether a successful power-on report was submitted.

[0057] The system integrates the valid hardware reports by hardware type and serial number to form a set of fields for each hardware component. Then, it calls the parsing rules for CPU, GPU, memory, motherboard, network card and BIOS respectively to generate structured hardware specifications.

[0058] The system performs field cleaning on structured hardware specifications. For example, the CPU model is extracted to obtain the standard model number from the original name, the GPU model is extracted to obtain the standard expression RTX or GTX from the original name, the GPU memory capacity is converted to units, the network card bandwidth is converted to units, leading and trailing spaces are removed from the motherboard model, and the memory brand is set to the default value when it is missing.

[0059] The system queries the platform hardware library based on the hardware source identifier or BIOS version. If an existing hardware record is found, the platform standard hardware ID is obtained; if no record is found but the fields are valid, a new basic hardware record is added and the platform standard hardware ID is obtained; if the fields are incomplete, the record is considered to have incomplete or unmaintained hardware information.

[0060] The system binds the acquired standard hardware IDs for the CPU, GPU, memory, motherboard, network card, and BIOS to the bare metal device. If the device is already registered, modification of the hardware relationship is refused; if the device is not registered, configuration is allowed.

[0061] The system determines whether a hardware compliance audit is required. If the device is already registered, a second audit is not required; if it is registering for the first time, an audit is required; if the device has been deregistered and then relisted, the system queries the historical hardware specifications and decides whether a second audit is needed based on whether key hardware has changed.

[0062] The system queries the standard motherboard library, standard GPU library, and BIOS rules. If the motherboard model, BIOS version, and GPU hardware identifier all meet the standard requirements, it is marked as requiring no review. If there are unsubmitted, failed reviews, or non-standard combinations, the system enters the automatic review process. The automatic review process may include, after the system completes the standardization judgment of the motherboard, BIOS, and GPU, if the key hardware combination does not simultaneously meet the requirements of the standard motherboard library, BIOS rules, and standard GPU library, it queries existing hardware compliance review records based on the bare metal device identifier, motherboard model, BIOS version, and GPU hardware source identifier. If a approved review record is found, the device is marked as meeting the review requirements; if a review record is found, it remains in a pending review state; if no review record is found, or the found review record is in a failed review state, when the automatic review switch is enabled, the MAC address, region information, motherboard model, motherboard name, BIOS version, GPU hardware source identifier, and GPU name of the bare metal device are assembled into review submission information and submitted in batches to the hardware compliance review system. After the automatic submission is completed, the system does not directly determine that the equipment has been approved. Instead, it uses the result of the standard library hit or the result of subsequent review as the basis for registration and access.

[0063] The system will submit the hardware combination that needs to be reviewed for review. The submitted information includes bare metal device identification, MAC address, motherboard model, motherboard name, BIOS version, GPU hardware identification, GPU name, and region information.

[0064] The system determines registration admission based on the standard library hit results or the review results. Bare metal devices with complete hardware information and that meet standardization requirements are allowed to register into the device pool; devices with missing hardware information, that are not maintained, or that have failed the review are not allowed to register into the device pool.

[0065] The system records the detection batches, detection records, failure reasons, hardware configuration relationships, and review status, and provides feedback to operators through real-time messages or task results.

[0066] A hardware specification testing task can be identified by a batch number. A batch can contain multiple bare metal devices, with each device corresponding to one testing record. The batch number is used for task cleanup, result reporting, and termination in case of anomalies.

[0067] Region detection mutexes can be used to limit the simultaneous existence of multiple hardware specification detection tasks within the same region. Mutexes can be stored in a cache, database, or other shareable storage and include region identifier, device list, batch number, task status, addition time, and cleanup time.

[0068] The power-on time is the time recorded when the system control equipment enters the detection environment. Hardware-reported data is only considered valid data for this detection if the reported time is later than this power-on time. This parameter is used to prevent historically reported data from affecting the current specification results.

[0069] The hardware type set includes at least CPU, GPU, memory, motherboard, network card, and BIOS. Different hardware types correspond to different raw reporting types, field sets, and parsing rules.

[0070] The corresponding hardware can be found in the platform's hardware library based on the hardware source identifier. For CPUs, GPUs, memory, motherboards, and network cards, the original hardware ID can be used as the source identifier; for BIOS, the BIOS version can be used as the source identifier.

[0071] The platform's standard hardware ID is a hardware identifier used internally for scheduling, querying, and management. Before registering a bare metal device, the original hardware information should be converted into the platform's standard hardware ID, and the standard hardware ID should be bound to the bare metal device.

[0072] The system can determine whether unknown hardware can be automatically written into the platform's hardware base library based on valid field conditions. If the hardware source identifier is missing, key model is missing, or a field cannot be parsed, no new hardware base record will be added, and the hardware information will be recorded as incomplete.

[0073] The standard motherboard library stores the motherboard models supported by the platform and acceptable BIOS rules; the standard GPU library stores the GPU hardware identifiers supported by the platform. The system uses these standard libraries to determine whether bare metal devices are within the platform's support range.

[0074] BIOS rule matching supports both exact matching and wildcard matching. For example, BIOS rules in the standard library can be configured with a fixed version or a version range that includes wildcards. The system converts the rule into a matching expression and compares it with the BIOS version reported by the device.

[0075] For bare metal devices that have been deregistered and then relisted, the system can query historical hardware specifications based on the deregistration time. If the GPU used this time is the same as the historical GPU, the review can be skipped; if the GPU has changed and the new GPU is not in the standard GPU library, a review will be triggered or the device will be automatically submitted for review.

[0076] For example, a bare metal device in an edge node has been successfully mounted via wiring detection but has not yet been registered. The system selects this device for hardware specification detection, creates a detection batch, and occupies the device. The system records the power-on time after the device is powered on. After the client reports hardware information, the system only reads the CPU, GPU, memory, motherboard, network card, and BIOS data after the power-on time. The system resolves the GPU's original name to a standard model, converts the memory capacity to units, and queries the platform's hardware library based on the GPU's hardware source identifier. If the GPU exists in the platform, the system obtains the GPU's standard hardware ID; if it does not exist but the field is valid, a new GPU basic record is added. The system continues to parse the motherboard and BIOS, and performs compliance checks based on the standard motherboard library, BIOS rules, and standard GPU library. If all standard libraries are matched, the device is allowed to register in the device pool; if the GPU does not match the standard library and has no approved records, the system automatically submits the hardware compliance review and temporarily disallows registration.

[0077] In addition, a specific implementation method is described: After the edge node completes the bare metal device mounting, the system has saved the device's MAC address, wiring relationships, and basic status, but the device is still in an unregistered state. The operator selects the device to initiate hardware specification detection and chooses the configuration used to start the detection environment.

[0078] The system first creates a probe task in the area where the device is located. If an ongoing attribute probe task already exists in the area, the system will indicate that a probe task exists in the current area; if the old task has ended or timed out, the system will first clear the old task and old probe records before creating a new probe task. After the task is created, the system uses a scheduling service to occupy the device to prevent the device from being used by other services during the probe.

[0079] After the scheduling service successfully acquires the device, the system powers on the bare metal device and records the power-on time. The system then polls the device's power status to confirm that the device has been successfully powered on. If the power status query fails or the device remains powered off, the system records the reason for the failure and terminates the probe of the device.

[0080] After the device is powered on, the detection client or detection environment will report hardware information. The system queries the hardware reporting records by device MAC address and filters out records whose reporting time is earlier than the current power-on time. In this way, even if the platform contains historical detection data for the same device, the system will not mistakenly identify old data as the current detection result.

[0081] After obtaining valid reported data, the system aggregates it based on hardware type and serial number. For example, the brand, architecture, model, frequency, number of cores, and number of threads of the same CPU may be scattered across multiple reported items. The system merges them into a single CPU specification object based on the same hardware type and serial number. GPUs, memory, motherboards, network cards, and BIOS are aggregated in a similar manner.

[0082] After aggregation, the system performs hardware field cleaning and standardization parsing. For CPUs, the system extracts a unified model number from the original name; for GPUs, the system extracts standard model numbers such as RTX and GTX from the original name and converts the video memory capacity; for network cards, the system converts the reported bandwidth to a unified unit; for motherboards, the system removes invalid spaces from the model number; and for memory, the system completes the default brand field.

[0083] After parsing, the system maps each type of hardware to the platform hardware library. If the source identifier for the CPU, GPU, memory, motherboard, or network card already exists in the platform hardware library, the system reuses the existing standard hardware ID; if it does not exist but the field is valid, the system adds a new hardware base record and obtains a new standard hardware ID. The BIOS uses the BIOS version for querying or adding. If a type of hardware lacks a key field, the system does not write it to the standard hardware library but records it as incomplete information.

[0084] After obtaining the standard hardware IDs, the system configures these IDs onto the bare metal devices. Before configuration, the system verifies whether the device is still in an unregistered state. If the device is already registered, the system refuses to modify the hardware relationships; if the device is not registered, the system updates the associations between the device and the CPU, GPU, memory, motherboard, network card, and BIOS.

[0085] The system then determines whether a hardware compliance audit is required. For devices registering for the first time, the system conducts an audit; for devices that have already been registered, the system does not conduct a duplicate audit; for devices that have been deregistered and then relisted, the system reads the historical hardware specifications at the time of deregistration. If the current GPU is consistent with the historical GPU, the audit can be skipped; if the GPU has changed, the system determines whether the new GPU is compliant, and if it is not compliant, an audit is triggered.

[0086] During the review process, the system queries the standard motherboard library, standard GPU library, and BIOS rules. If the motherboard model is in the standard motherboard library, the BIOS version meets the BIOS rules corresponding to the standard motherboard, and the GPU hardware identifier is in the standard GPU library, the system considers the hardware combination to be compliant with the platform standard and does not require review. If a critical hardware component does not meet the standard, the system further checks whether there is already a review record; for combinations that have not been submitted or whose review has failed, the system automatically submits them for review.

[0087] Ultimately, the system determines whether to allow a device to register in the device pool based on the completeness of its hardware specifications, the standard hardware ID mapping results, and the compliance audit status. If the hardware specifications are complete and meet the standardization and audit requirements, registration is allowed; if there are issues such as unreported hardware, incomplete hardware fields, unmaintained standard hardware, or failure to pass the compliance audit, registration is blocked, and the reason for the failure is reported back to the operator.

[0088] In summary, the bare metal device registration and access method provided in this application records the power-on time of unregistered bare metal devices already on the rack as a time reference, and accurately filters valid hardware reporting data by combining it with MAC address data, avoiding data distortion caused by client caching and expired hardware information left over from historical power-ups. Structured hardware specifications are generated based on valid hardware reporting data, eliminating differences caused by different data sources and hardware types. After obtaining the hardware ID and binding it to the bare metal device to be detected, the device undergoes hardware compliance review. Upon successful review, it is registered into the device pool, thereby improving the accuracy of bare metal device registration and access.

[0089] This application also provides a bare metal equipment registration access device, which is described below and can be referred to in conjunction with the method described above. The device includes: A creation unit is used to create hardware probing tasks; if an unfinished probing task already exists in the same area, the creation of a new probing task will be refused. An occupancy unit is used to occupy a target bare metal device and create a detection record for the target bare metal device; the target bare metal device is a bare metal device that has been put into operation and is to be detected; if the occupancy fails, the reason for the failure is recorded; if the occupancy is successful, the target bare metal device is powered on and the power-on time is recorded. The query unit is used to query hardware reporting data based on the MAC address of the target bare metal device, and to accept hardware reporting data after power-on time as valid hardware reporting data. A generation unit is used to generate structured hardware specifications based on the valid hardware reporting data; A binding unit is used to obtain a hardware ID according to the structured hardware specifications and bind the hardware ID to the target bare metal device; The first review unit is used to conduct a hardware compliance review of the target bare metal device if the target bare metal is registered for the first time. The second review unit is used to query the historical hardware specifications of the target bare metal device if the target bare metal device is not registered for the first time, and to conduct a hardware compliance review of the target bare metal device if it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications. The registration unit is used to register the target bare metal device into the device pool if the review is approved.

[0090] In some embodiments, the generating unit is used for: Filter the valid hardware reported data according to the hardware type, group them according to the sequence number, merge multiple data items or data values ​​of the same component into a structured object, and obtain the fields corresponding to each hardware. The structured hardware specification is generated based on the fields corresponding to the hardware by calling the corresponding parsing rules of the hardware.

[0091] In some embodiments, it also includes: The cleaning unit is used to clean the fields of the structured hardware specification before obtaining the hardware ID based on the structured hardware specification.

[0092] In some embodiments, the binding unit is used for: The corresponding hardware ID is retrieved from the platform hardware library based on the hardware source or BIOS version in the structured hardware specification. If found, the corresponding hardware ID is obtained from the platform's hardware library; If no record is found and the corresponding fields for the hardware are complete, the existing platform standard hardware record identifier will be reused, or a new platform hardware basic record will be added and the corresponding identifier will be obtained if the fields are valid. If no results are found and the corresponding fields for the hardware are incomplete, the record is considered to have incomplete or unmaintained hardware information.

[0093] In some embodiments, it also includes: The recording unit is used to record the detection batch number, detection record, failure reason, hardware configuration relationship and review status, and to provide feedback of the recorded content to the target object.

[0094] In some embodiments, it also includes: The detection environment activation unit is used to receive the detection configuration and activate the detection environment according to the detection configuration so as to control the target bare metal device to power on under the detection environment.

[0095] In some embodiments, both the first review unit and the second review unit are configured to: query a standard motherboard library based on the motherboard model, match the BIOS version with the BIOS rules in the standard motherboard library, and query a standard GPU library based on the GPU hardware source identifier; if the motherboard, BIOS, and GPU all meet the standard conditions, then it is determined that the target bare metal device does not need to be submitted for review; if any one of the motherboard, BIOS, and GPU does not meet the standard conditions, then existing review records are queried based on the identifier of the target bare metal device, the motherboard model, the BIOS version, and the GPU hardware source identifier. If no audit record is found or the audit record is in a failed state, audit submission data containing the target bare metal device's MAC address, region information, motherboard information, BIOS information, and GPU information will be generated, and hardware compliance audit will be submitted when the automatic submission conditions are met.

[0096] This application also provides an electronic device, referenced... Figure 6 As shown, the device includes a memory 1 and a processor 2.

[0097] Memory 1 is used to store computer programs; Processor 2 is used to execute computer programs to perform the following steps: A hardware detection task is created; if an unfinished detection task exists in the same area, the creation of a new detection task is rejected; a target bare metal device is occupied, and a detection record is created for the target bare metal device; the target bare metal device is a bare metal device that has been put into operation and is to be detected; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the target bare metal device is powered on and the power-on time is recorded; hardware reporting data is queried based on the MAC address of the target bare metal device, and hardware reporting data after the power-on time is accepted as valid hardware reporting data; a structured hardware specification is generated based on the valid hardware reporting data; a hardware ID is obtained based on the structured hardware specification, and the hardware ID is bound to the target bare metal device; if the target bare metal device is registered for the first time, a hardware compliance audit is performed on the target bare metal device; if the target bare metal device is not registered for the first time, the historical hardware specification of the target bare metal device is queried; if it is determined that the target hardware has changed based on the historical hardware specification and the structured hardware specification, a hardware compliance audit is performed on the target bare metal device; if the audit is passed, the target bare metal device is registered into the device pool.

[0098] For a description of the equipment provided in this application, please refer to the above method embodiments; further details will not be provided here.

[0099] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the following steps: A hardware detection task is created; if an unfinished detection task exists in the same area, the creation of a new detection task is rejected; a target bare metal device is occupied, and a detection record is created for the target bare metal device; the target bare metal device is a bare metal device that has been put into operation and is to be detected; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the target bare metal device is powered on and the power-on time is recorded; hardware reporting data is queried based on the MAC address of the target bare metal device, and hardware reporting data after the power-on time is accepted as valid hardware reporting data; a structured hardware specification is generated based on the valid hardware reporting data; a hardware ID is obtained based on the structured hardware specification, and the hardware ID is bound to the target bare metal device; if the target bare metal device is registered for the first time, a hardware compliance audit is performed on the target bare metal device; if the target bare metal device is not registered for the first time, the historical hardware specification of the target bare metal device is queried; if it is determined that the target hardware has changed based on the historical hardware specification and the structured hardware specification, a hardware compliance audit is performed on the target bare metal device; if the audit is passed, the target bare metal device is registered into the device pool.

[0100] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0101] For a description of the computer-readable storage medium provided in this application, please refer to the above method embodiments; further details will not be repeated here.

[0102] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatuses, devices, and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant details can be found in the method section.

[0103] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0104] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0105] The above provides a detailed description of the registration and access method, apparatus, equipment, and storage medium for bare metal devices provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A method for registration and access approval of bare metal equipment, characterized in that, include: Create a hardware probe task; if an unfinished probe task already exists in the same area, the creation of a new probe task will be rejected. The system occupies the target bare metal device and creates a detection record for it; the target bare metal device is a bare metal device that has been put into storage and is to be detected; if the occupation fails, the reason for the failure is recorded; if the occupation is successful, the system controls the target bare metal device to be powered on and records the power-on time. The hardware reporting data is queried based on the MAC address of the target bare metal device, and the hardware reporting data after the power-on time is accepted as the valid hardware reporting data. Generate structured hardware specifications based on the valid hardware report data; Obtain the hardware ID according to the structured hardware specifications, and bind the hardware ID to the target bare metal device; If the target bare metal is registered for the first time, a hardware compliance audit will be conducted on the target bare metal device. If the target bare metal device is not registered for the first time, then query the historical hardware specifications of the target bare metal device. If it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications, then conduct a hardware compliance audit on the target bare metal device. If the review is approved, the target bare metal device will be registered into the device pool.

2. The registration and access method for bare metal equipment according to claim 1, characterized in that, Generating structured hardware specifications based on the valid hardware report data includes: Filter the valid hardware reported data according to the hardware type, group them according to the sequence number, merge multiple data items or data values ​​of the same component into a structured object, and obtain the fields corresponding to each hardware. The structured hardware specification is generated based on the fields corresponding to the hardware by calling the corresponding parsing rules of the hardware.

3. The registration and access method for bare metal equipment according to claim 1, characterized in that, Before obtaining the hardware ID based on the structured hardware specifications, the following steps are also included: Field cleaning is performed on the structured hardware specifications.

4. The registration and access method for bare metal equipment according to claim 1, characterized in that, Obtaining the hardware ID based on the structured hardware specifications includes: The corresponding hardware ID is retrieved from the platform hardware library based on the hardware source or BIOS version in the structured hardware specification. If found, the corresponding hardware ID is obtained from the platform's hardware library; If no record is found and the corresponding fields for the hardware are complete, the existing platform standard hardware record identifier will be reused, or a new platform hardware basic record will be added and the corresponding identifier will be obtained if the fields are valid. If no results are found and the corresponding fields for the hardware are incomplete, the record is considered to have incomplete or unmaintained hardware information.

5. The registration and access method for bare metal equipment according to claim 1, characterized in that, Also includes: Record the detection batch number, detection record, failure reason, hardware configuration relationship, and review status, and provide feedback on the recorded content to the target.

6. The registration and access method for bare metal equipment according to claim 1, characterized in that, Also includes: Receive the detection configuration and start the detection environment according to the detection configuration so as to control the target bare metal device to power on in the detection environment.

7. The registration and access method for bare metal equipment according to claim 1, characterized in that, The hardware compliance audit of the target bare metal device includes: querying the standard motherboard library based on the motherboard model, matching the BIOS version with the BIOS rules in the standard motherboard library, and querying the standard GPU library based on the GPU hardware source identifier; if the motherboard, BIOS, and GPU all meet the standard conditions, then the target bare metal device is determined not to need to be submitted for audit; if any one of the motherboard, BIOS, and GPU does not meet the standard conditions, then existing audit records are queried based on the identifier of the target bare metal device, the motherboard model, the BIOS version, and the GPU hardware source identifier. If no audit record is found or the audit record is in a failed state, audit submission data containing the target bare metal device's MAC address, region information, motherboard information, BIOS information, and GPU information will be generated, and hardware compliance audit will be submitted when the automatic submission conditions are met.

8. A registration and access device for bare metal equipment, characterized in that, include: A creation unit is used to create hardware probing tasks; if an unfinished probing task already exists in the same area, the creation of a new probing task will be refused. An occupancy unit is used to occupy a target bare metal device and create a detection record for the target bare metal device; the target bare metal device is a bare metal device that has been put into operation and is to be detected; if the occupancy fails, the reason for the failure is recorded; if the occupancy is successful, the target bare metal device is powered on and the power-on time is recorded. The query unit is used to query hardware reporting data based on the MAC address of the target bare metal device, and to accept hardware reporting data after power-on time as valid hardware reporting data. A generation unit is used to generate structured hardware specifications based on the valid hardware reporting data; A binding unit is used to obtain a hardware ID according to the structured hardware specifications and bind the hardware ID to the target bare metal device; The first review unit is used to conduct a hardware compliance review of the target bare metal device if the target bare metal is registered for the first time. The second review unit is used to query the historical hardware specifications of the target bare metal device if the target bare metal device is not registered for the first time, and to conduct a hardware compliance review of the target bare metal device if it is determined that the target hardware has changed based on the historical hardware specifications and the structured hardware specifications. The registration unit is used to register the target bare metal device into the device pool if the review is approved.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the bare metal device registration access method as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the bare metal device registration access method as described in any one of claims 1 to 7.

Images