Bare metal server management method, device, equipment, medium and program product

Abstract

The application discloses a bare metal server management method, device, equipment, storage medium and program product, wherein the method comprises: configuring a preset parameter template; wherein the preset parameter template comprises multi-dimensional parameters required by one or more types of bare metal servers; based on the preset parameter template, an algorithm development is performed on the management process of each type of bare metal server in the one or more types of bare metal servers, to obtain a bare metal management algorithm of each type of bare metal server; input parameters of each type of bare metal server are acquired, and the batch management process of each type of bare metal server is completed based on the input parameters of each type of bare metal server through the bare metal management algorithm of each type of bare metal server.

Description

Technical Field

[0001] This application relates to the field of bare metal management technology in cloud computing, and in particular to a method, apparatus, device, storage medium and program product for bare metal server management. Background Technology

[0002] Bare metal servers are physical servers without a pre-installed operating system, typically used in scenarios with high performance and resource control requirements. Management technologies enable unified scheduling, deployment, and management of bare metal servers. Currently, this primarily relies on open-source projects such as OpenStack Ironic for bare metal server registration, configuration, and automated deployment. In related technologies, the bare metal server management process usually includes steps such as node creation, network configuration, and hardware testing, and relies on manual input of numerous parameters to complete server initialization. This process requires designing management schemes for different server specifications, involving a large amount of manual configuration and repetitive operations. Especially when dealing with multiple types of bare metal servers, this process is inefficient and error-prone, making it difficult to meet the needs of rapid deployment of large-scale, multi-type bare metal servers. Summary of the Invention

[0003] To address the aforementioned technical problems, embodiments of this application provide a method, apparatus, device, storage medium, and program product for managing bare metal servers.

[0004] The bare metal server management method provided in this application includes:

[0005] Configure a preset parameter template; wherein, the preset parameter template includes multi-dimensional parameters required for one or more types of bare metal servers; based on the preset parameter template, develop an algorithm for the management process of each type of bare metal server in one or more types of bare metal servers to obtain a bare metal management algorithm for each type of bare metal server;

[0006] The input parameters of each type of bare metal server are obtained, and the batch management process of each type of bare metal server is completed based on the input parameters of each type of bare metal server using the bare metal management algorithm of each type of bare metal server.

[0007] The bare metal server management device provided in this application includes:

[0008] A configuration unit is used to configure a preset parameter template; wherein the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers;

[0009] The development unit is used to develop an algorithm for the management process of each type of bare metal server in one or more types of bare metal servers based on the preset parameter template, so as to obtain the bare metal management algorithm for each type of bare metal server.

[0010] The acquisition unit is used to acquire the input parameters of each type of bare metal server;

[0011] The management unit is used to complete the batch management process of each type of bare metal server based on the input parameters of each type of bare metal server through the bare metal management algorithm of each type of bare metal server.

[0012] The processing device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the bare metal server management methods described above.

[0013] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the above-described bare metal server management methods.

[0014] The computer program product provided in this application includes computer program instructions that cause a computer to execute any of the above-described bare metal server management methods.

[0015] In the technical solution of this application embodiment, a preset parameter template is configured; based on the preset parameter template, an algorithm is developed for the management process of each type of bare metal server in one or more types of bare metal servers, resulting in a bare metal management algorithm for each type of bare metal server; input parameters for each type of bare metal server are obtained, and the batch management process for each type of bare metal server is completed based on the input parameters of each type of bare metal server using the bare metal management algorithm for each type of bare metal server; wherein, the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers. Thus, firstly, a preset parameter template is configured, covering different dimensional parameters required by various types of bare metal servers, thereby constructing a standardized management process framework for different types of bare metal servers; then, algorithm development is performed based on the preset parameter template to generate a bare metal management algorithm suitable for each type of bare metal server, realizing automated processing logic; then, input parameters for each type of bare metal server are obtained, and the corresponding bare metal management algorithm is used to complete the batch management process. In this way, on the one hand, by using preset parameter templates and algorithm development, the bare metal conduit process can be standardized and modularized, avoiding the need to manually design conduit schemes each time, thereby improving conduit efficiency; on the other hand, by using batch conduit processes, manual intervention can be reduced, improving execution efficiency and consistency during large-scale deployment. Attached Figure Description

[0016] Figure 1 This is a schematic flowchart of the bare metal nanotube method provided in the embodiments of this application;

[0017] Figure 2 This is a flowchart illustrating a bare metal server management method provided in an embodiment of this application;

[0018] Figure 3 This is a schematic diagram of the architecture of a multi-type bare metal nanotube method and system based on an automated platform provided in an embodiment of this application;

[0019] Figure 4 This is a schematic diagram of a bare metal server ducting device provided in an embodiment of this application;

[0020] Figure 5 This is a schematic diagram of the processing device provided in the embodiments of this application. Detailed Implementation

[0021] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0022] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0023] Bare Metal Service is a physical server management service based on the OpenStack Ironic project. Users can directly operate physical servers and deploy images to real, physical bare metal servers. Ironic's main functions include adding, deleting, managing power, and deploying bare metal servers. Ironic allows vendors to add specific extension drivers to their servers, thus supporting most physical servers.

[0024] Ironic manages bare metal device clusters, which do not have operating systems installed. Therefore, it is necessary to obtain the physical properties of these bare metal device clusters. The physical properties of these bare metal device clusters are crucial for the deployment of bare metal operating systems.

[0025] (1) Scheduling requirements: The scheduler needs to know information such as the CPU, disk, memory, and architecture of the bare metal device, otherwise it cannot be deployed effectively.

[0026] (2) Requirements for interfacing with Software Defined Network (SDN): If you want to use SDN to control the Top of Rack (TOR) connected to the bare metal device, you must know the Link Layer Discovery Protocol (LLDP) information of the TOR port connected to the device; otherwise, you cannot complete the deployment.

[0027] (3) Network configuration requirements: Automatic discovery can extract the network card information of physical devices and create an ironic port / portgroup, thereby clarifying the media access control (MAC) address and bond information of the physical device's network card in order to configure the network; otherwise, it cannot be configured correctly.

[0028] Figure 1 This is a schematic flowchart of the bare metal nanotube method provided in the embodiments of this application, as shown below. Figure 1 As shown, the method includes the following steps:

[0029] Step 101: Create the corresponding flavor configuration.

[0030] Step 102: Create chassis information for the actual physical server location.

[0031] Step 103: Create the corresponding node based on the Low-Level Design (LLD) table provided by the hard set.

[0032] Step 104: Create a Dynamic Host Configuration Protocol (DHCP) whitelist so that the physical server can obtain an IP address during the Preboot Execution Environment (PXE) process and complete operations such as downloading small images.

[0033] Step 105: Enable DNS forwarding (DNS masquerade, dnsmasq) service to provide DNS resolution services for the bare metal server.

[0034] Step 106: Perform an inspection operation. The bare metal server will scan its hardware devices, collect hardware information such as CPU, memory, disk, and network interface, and send this information to the Ironic service.

[0035] Step 107: Update the network configuration based on the LLD table.

[0036] However, the above solutions involve a complex management process and require the design of a management solution for each bare metal server with different specifications, which requires a lot of effort to complete.

[0037] To address the aforementioned technical issues, this application proposes a bare metal server management method. First, a preset parameter template is configured, covering various dimensions of parameters required by different types of bare metal servers. This establishes a standardized management process framework for different types of bare metal servers. Next, algorithms are developed based on the preset parameter template to generate bare metal management algorithms suitable for each type of bare metal server, achieving automated processing logic. Then, the input parameters for each type of bare metal server are obtained, and the corresponding bare metal management algorithm is used to complete the batch management process. In this way, on the one hand, the bare metal management process can be standardized and modularized through the preset parameter template and algorithm development, avoiding manual design of management schemes each time and improving management efficiency; on the other hand, the batch management process can reduce manual intervention and improve execution efficiency and consistency during large-scale deployments.

[0038] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0039] This application proposes a bare metal server management method, which can be executed by an automation platform, such as a web-based management system or a script scheduling system. Figure 2 This is a flowchart illustrating a bare-metal server management method provided in an embodiment of this application, as shown below. Figure 2 As shown, the method includes the following steps:

[0040] Step 201: Configure the preset parameter template; wherein, the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers.

[0041] Here, a preset parameter template refers to a set of multi-dimensional parameters pre-defined for different types of bare metal servers, including but not limited to control node address, server node information, and management type. Automation platforms can achieve standardized processing of different types of bare metal servers by using preset parameter templates. For example, a preset parameter template may include the following fields: ironic_ip_list (to identify the IP address of the Ironic control node), k8s_master_ip (to identify the IP address of the master control node), node_info (to describe the basic connection and identity information of a single server node), and vm_type (to distinguish the type of bare metal server, such as computeV1, storage, network, etc.).

[0042] In this embodiment, the configuration process of the preset parameter template is typically completed on an automated platform. Users can select different bare metal server types according to their actual business needs and fill in the corresponding parameter values. For example, when configuring the preset parameter template for a compute bare metal server, the user can set `vm_type` to `computeV1` and fill in the corresponding node name, Intelligent Platform Management Interface (IPMI) address, username, password, and other information. When configuring the preset parameter template for an elastic bare metal server, the user needs to configure parameters specific to elastic bare metal servers separately, such as dynamic resource adjustment strategies and extension interfaces.

[0043] In practice, the design of preset parameter templates not only simplifies user operations but also ensures the consistency and standardization of the management process. Adopting a unified parameter input method avoids problems caused by inconsistent manual configurations, thereby improving the overall system's stability and reliability.

[0044] Step 202: Based on the preset parameter template, develop an algorithm for the management process of each type of bare metal server in one or more types of bare metal servers, and obtain the bare metal management algorithm for each type of bare metal server.

[0045] In this embodiment, the bare metal management algorithm is an automated processing logic developed based on a preset parameter template, used to guide the bare metal server management process. Each type of bare metal server is equipped with a corresponding bare metal management algorithm, which can automatically execute the corresponding management steps according to the input parameters. For example, the bare metal management algorithm configured for a computeV1 bare metal server may include steps such as creating a flavor, creating a node, executing an inspection process, and updating network configuration.

[0046] In practical implementation, the bare metal management process developed through algorithms is highly automated, significantly reducing manual operations and improving the efficiency and consistency of batch management. Furthermore, the bare metal management algorithm can be flexibly adjusted according to different types of bare metal servers, thus supporting diverse deployment needs.

[0047] Step 203: Obtain the input parameters for each type of bare metal server, and complete the batch management process for each type of bare metal server based on the input parameters using the bare metal management algorithm for each type of bare metal server.

[0048] In this embodiment, the input parameters refer to the actual parameter values ​​specific to a certain type of bare metal server input on the automation platform. These input parameters correspond to fields in a preset parameter template and are used to drive the execution of the bare metal server inclusion algorithm. By obtaining the input parameters for each type of bare metal server and inputting them into the bare metal server inclusion algorithm for each type, the corresponding bare metal server inclusion algorithm can automatically execute each step in the batch inclusion process for each type of bare metal server based on the input parameters. The number of bare metal servers of each type can be one or more.

[0049] For example, suppose there are 100 bare metal compute servers (computeV1) awaiting management. Users only need to input the parameter 'computeV1' into the automation platform. The platform will then invoke the corresponding bare metal management algorithm based on the 'computeV1' input to complete the batch management process for these bare metal compute servers. This algorithm includes steps such as creating a flavor, creating a node, executing an inspection, and updating network configurations. Each step can be completed by the automation platform calling the underlying API or command-line tools, thus automating the entire management process.

[0050] The automation platform can display the execution status of the entire batch management process in real time on the platform interface, so that operation and maintenance personnel can troubleshoot problems and optimize processes.

[0051] It should be noted that for the newly added bare metal server type, the preset parameter templates of the automation platform can be modified to expand the pipeline and enable the management of more types of bare metal servers.

[0052] In some embodiments, the input parameters for each type of bare metal server include one or more of the following: a first control node network address, a second control node network address, server node information, and management type; wherein, the first control node network address is used to manage the entire lifecycle of the bare metal server; and the second control node network address is used to manage containerized workloads running on the bare metal server.

[0053] The first control node network address refers to the IP address (Ironic control node IP address) used to manage and control the bare metal server throughout its entire lifecycle. This address typically corresponds to the Ironic (OpenStack Bare Metal Service) control node, responsible for performing operations such as power control, image deployment, and hardware detection. Through the first control node network address, critical operations such as powering on / off, installing the operating system, and configuring the network can be performed on the bare metal server. For example, in a real-world scenario, the first control node network address might be the IP address of a physical server in the cluster, such as 192.168.1.1, used to receive instructions from the automation platform and execute related tasks.

[0054] The second control node network address refers to the IP address (master control node IP address) used to manage containerized workloads running on bare metal servers. This IP address typically corresponds to the master node in the Kubernetes (k8s) control plane, used for scheduling, monitoring, and managing the running status of containerized applications. By using the second control node network address, containerized business applications can be deployed on bare metal servers, and lifecycle management of these applications can be performed. For example, in a real-world scenario, the second control node network address might be the IP address of the Kubernetes Master node, such as 192.168.1.2, used to receive container orchestration instructions from an automation platform and start container services.

[0055] Server node information refers to the detailed configuration information of the bare metal server to be managed, including but not limited to IPMI address, username, password, port number, device matrix number, etc. Server node information is used to uniquely identify and connect to the bare metal server, ensuring that the automation platform can accurately identify and connect to the target device.

[0056] Management type refers to the classification identifier of bare metal servers, used to distinguish bare metal servers of different uses or specifications. Common management types include compute-type (computeV1, computeV2), network-type, storage-type, and DPU-type. The management type determines the configuration template and algorithm logic used in the subsequent management process. For example, in a real-world scenario, if the management type is computeV1, the system will load the corresponding management configuration file for the compute-type bare metal server, thereby executing the corresponding management steps.

[0057] In some embodiments, step 203, "completing the batch management process for each type of bare metal server based on the input parameters of each type of bare metal server using the bare metal management algorithm for each type of bare metal server," includes:

[0058] For each type of bare metal server, network-related information of that type of bare metal server is determined based on the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type.

[0059] The network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server, as well as the network-related information of the bare metal server, are input into the bare metal management algorithm of the bare metal server of this type. The bare metal management algorithm of the bare metal server of this type outputs the configuration file corresponding to the bare metal server of this type, which describes the management requirements and attributes of the bare metal server of this type in the automation platform, and completes the batch management process of the bare metal server of this type based on the configuration file corresponding to the bare metal server of this type.

[0060] First, based on the network address of the first control node and / or the network address of the second control node and / or server node information and / or management type of each type of bare metal server, this information collectively constitutes the network context environment of each type of bare metal server. Based on this information, the appropriate network configuration (network-related information) for each type of bare metal server can be determined. For example, if a certain type of bare metal server is compute-based, the system determines that the network configuration of this type of bare metal server may involve the binding of high-performance network interfaces; if a certain type of bare metal server is DPU-based, the system determines that the network configuration of this type of bare metal server may require specific SDN policy support.

[0061] Specifically, based on the server node information of each type of bare metal server, the network hardware information of each type of bare metal server, including the PXE network card MAC address, can be obtained. Then, based on the network address of the first control node and / or the network address of the second control node of each type of bare metal server, the managed environment can be logged into to query the planned PXE network information and obtain the managed network planning information, including the PXE network ID. Simultaneously, combined with the actual business purpose of each type of bare metal server, the business-side network planning can be aligned to supplement business network configuration parameters, such as the business Virtual Local Area Network (VLAN) ID, business network segment, gateway, and DNS server. Furthermore, if the business requires a fixed IP address, a static business IP address must be confirmed. The PXE network card MAC address must be consistent with the actual PXE network card of the bare metal server, the PXE network ID must be consistent with the managed network planning, and the business network configuration parameters must be consistent with the business-side network planning and not conflict with the PXE network.

[0062] Next, for each type of bare metal server, the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type, as well as the network-related information of the bare metal server for that type, are input into the bare metal management algorithm for that type of bare metal server. This enables the bare metal management algorithm for that type of bare metal server to generate specific configuration files based on the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type, as well as the network-related information of the bare metal server for that type, such as flavor configuration, node configuration, DHCP whitelist configuration, inspect script, etc.

[0063] After the configuration file for each type of bare metal server is generated, the automation platform will execute steps such as creating flavor, creating node, performing inspection, and updating network configuration in a pipeline manner, and finally complete the batch management operation for each type of bare metal server.

[0064] In some embodiments, the batch management process for this type of bare metal server is completed based on the configuration file corresponding to that type of bare metal server, including:

[0065] Based on the basic identifier, server node information and hardware configuration parameters of this type of bare metal server, complete the creation of the specification template for this type of bare metal server and the registration of the bare metal node for this type of bare metal server;

[0066] Obtain the actual hardware information of this type of bare metal server, and update the network configuration of this type of bare metal server based on the actual hardware information of this type of bare metal server and the corresponding hardware configuration parameters and network configuration parameters;

[0067] Based on the management type corresponding to this type of bare metal server, determine the deployment logic corresponding to this type of bare metal server; based on the deployment logic corresponding to this type of bare metal server, complete the batch deployment of this type of bare metal server.

[0068] Here, the configuration file for this type of bare metal server includes: Management Type, Basic Identifier, Server Node Information, Hardware Configuration Parameters, and Network Configuration Parameters. The Management Type distinguishes different types of bare metal servers, such as computeV1, network, storage, and DPU. The Basic Identifier assigns a unique identity to each type of bare metal server. The Server Node Information contains detailed information for each physical server, such as IPMI address, username, password, and port number, used to establish a connection with the physical device. The Hardware Configuration Parameters define the hardware specifications for each type of bare metal server, including the number of CPUs, memory size, disk capacity, and network interface card (NIC) model. The Network Configuration Parameters describe the configuration information of each type of bare metal server in the network environment, such as MAC address, network segment, subnet mask, and gateway.

[0069] Specifically, for each type of bare metal server, firstly, a specification template is automatically generated based on the hardware configuration parameters in the configuration file of that type of bare metal server. This template defines the basic hardware configuration of that type of bare metal server, such as CPU, memory, and disk. Then, based on the specification template, basic identifier, and server node information corresponding to that type of bare metal server, the corresponding bare metal node is registered and included as part of the schedulable resource pool. Here, the bare metal node is a logical mapping of the bare metal server in Ironic, corresponding one-to-one with the bare metal server, laying the foundation for subsequent consistency verification and deployment.

[0070] Next, the actual hardware information of this type of bare metal server is collected and obtained, including CPU, memory, disk, network card, etc. This collected hardware information is compared with the hardware configuration parameters in the configuration file of this type of bare metal server to verify consistency. If discrepancies exist, the anomaly is recorded for manual inspection; if they match, the network configuration of this type of bare metal server is updated according to its network configuration parameters. This network configuration update includes generating a MAC address list, configuring bond information, and setting network segments and routing rules to ensure that this type of bare metal server has correct communication capabilities in the network environment.

[0071] Subsequently, based on the management type specified in the configuration file of that type of bare metal server, the corresponding deployment logic is invoked. For example, a Kubernetes-based deployment scheme might be used for compute-v1 bare metal servers, while an SDN integration scheme might be used for network-v1 bare metal servers. Different deployment logics are suitable for different types of business needs. According to the deployment logic corresponding to that type of bare metal server, the configured bare metal nodes are added to the deployment queue, and deployment tasks are executed sequentially. During deployment, the status of each node is monitored in real time. If any anomalies are detected, the deployment process is immediately paused and reported so that relevant personnel can promptly investigate the problem.

[0072] In some embodiments, based on the basic identifier, server node information, and hardware configuration parameters corresponding to this type of bare metal server, the creation of the specification template corresponding to this type of bare metal server and the registration of the bare metal node corresponding to this type of bare metal server are completed, including:

[0073] Based on the memory specifications and / or built-in disk specifications and / or allocated CPU specifications of this type of bare metal server, create a specification template corresponding to this type of bare metal server.

[0074] Register the bare metal node corresponding to this type of bare metal server based on the specification template, basic identifier, and server node information.

[0075] Here, the hardware configuration parameters for this type of bare metal server include one or more of the following: the equipped memory specifications, the built-in disk specifications, and the allocated CPU specifications. Memory specifications refer to the capacity and type of memory equipped in the bare metal server, such as DDR4 64GB, ECC 128GB, etc. Memory specifications determine the maximum memory space and data processing capacity that the server can support during operation. Higher memory specifications result in more stable server performance when performing high-concurrency, high-throughput tasks. Disk specifications refer to the capacity, interface type (such as SATA, NVMe), read / write speed, and other parameters of the bare metal server's built-in hard drive. CPU specifications refer to the model, number of cores, number of threads, clock speed, cache size, and other parameters of the central processing unit used by the bare metal server.

[0076] Specifically, firstly, based on the memory specifications and / or built-in disk specifications and / or allocated CPU specifications of this type of bare metal server, a standardized configuration model is constructed. This model serves as a specification template for this type of bare metal server, defining its basic hardware configuration, enabling unified management of this type of bare metal server, and providing a reference for subsequent management processes. By abstracting actual hardware configuration parameters into specification templates, standardized management can be achieved in large-scale deployments. Operations personnel can avoid redundant configurations, thereby improving system compatibility and deployment efficiency.

[0077] Then, the specification template, basic identifier, and server node information corresponding to this type of bare metal server are integrated and processed to register the bare metal node corresponding to this type of bare metal server and generate a complete bare metal node registration record. This record not only includes the specific hardware resource configuration corresponding to this type of bare metal server, but also covers metadata such as physical location and network connection, providing basic support for subsequent deployment, scheduling, and maintenance operations.

[0078] In addition, network configuration parameters can be extracted from the configuration file corresponding to this type of bare metal server, and network cards can be added to the bare metal nodes corresponding to this type of bare metal server according to the network configuration parameters to ensure that subsequent PXE startup and hardware inspection are normal.

[0079] In some embodiments, based on the actual hardware information of the bare metal server and the corresponding hardware configuration parameters and network configuration parameters, the network configuration of the bare metal server is updated, including:

[0080] Perform a consistency check between the actual hardware information of this type of bare metal server and the physical memory and / or built-in disk specifications and / or allocated CPU specifications configured for this type of bare metal server. If the actual hardware information of this type of bare metal server passes the consistency check, update the network configuration of this type of bare metal server based on the PXE network-related configuration parameters and / or service network-related configuration parameters corresponding to this type of bare metal server.

[0081] Here, the network configuration parameters for this type of bare metal server include one or more of the following: PXE network-related configuration parameters and business network-related configuration parameters. PXE network-related configuration parameters refer to network configuration information related to PXE, used to ensure the normal execution of the bare metal server management process (PXE startup, inspection), and are the basic network parameters for management, including the PXE network card MAC address, PXE network ID, etc. Business network-related configuration parameters refer to configuration information related to the business network environment required for the normal operation of the server, used to ensure that the bare metal server can normally access the business network and realize business communication after management, including business VLAN ID, gateway, DNS server address, etc.

[0082] Specifically, firstly, assuming the bare metal node corresponding to this type of bare metal server is registered, a consistency check is performed between the actual hardware information of this type of bare metal server (such as CPU model, memory size, and disk capacity) and the configured physical memory and / or built-in disk specifications and / or allocated CPU specifications to determine whether the hardware status of this type of bare metal server matches expectations. For example, check whether the actual configured memory equals the memory size specified in the configuration file, or whether the built-in disk model matches the expected hard drive specifications. This can avoid deployment failures or performance issues due to hardware incompatibility.

[0083] It should be noted that if the above consistency check fails, the server node information in the configuration file corresponding to this type of bare metal server should be checked first, such as whether the IPMI address, username and password are correct, whether the BMC is enabled, and whether the network is connected. If the actual hardware information of this type of bare metal server fails the consistency check (e.g., the actual memory is less than the configured physical memory), then the configuration file corresponding to this type of bare metal server or the hardware of this type of bare metal server needs to be checked.

[0084] Next, if the actual hardware information of this type of bare metal server passes the consistency check, the network configuration of this type of bare metal server will continue to be automatically updated according to the PXE network-related configuration parameters and / or business network-related configuration parameters corresponding to this type of bare metal server, so as to ensure that this type of bare metal server can correctly access the network and participate in business traffic.

[0085] Specifically, you can update the network attributes of the bare metal node corresponding to this type of bare metal server, bind the bare metal node to the PXE network, and ensure that the PXE can obtain an IP address normally during startup and deployment. If the configuration file of this type of bare metal server specifies a service VLAN, you need to create a VLAN subnet and associate the network card of the bare metal node corresponding to this type of bare metal server with that VLAN. If the configuration file of this type of bare metal server specifies a static service IP, you can assign a static IP address to the bare metal node corresponding to this type of bare metal server to ensure that the IP address is fixed. Finally, you can check the network attributes and network card configuration of the bare metal node corresponding to this type of bare metal server to ensure that they are consistent with the network configuration parameters of this type of bare metal server, and test network connectivity (such as pinging the gateway and DNS).

[0086] Through the above consistency verification and network configuration update mechanism, the resource configuration of each type of bare metal server can be ensured to be accurate, which can avoid deployment failure or performance problems caused by hardware inconsistency, thereby improving the overall management efficiency and reliability.

[0087] In some embodiments, the above method further includes:

[0088] For each type of bare metal server that has completed the management process, multi-dimensional verification is performed on that type of bare metal server. If the bare metal server of that type passes the multi-dimensional verification, it is connected to the operation and maintenance system and its status is updated to available.

[0089] This type of bare metal server is managed automatically throughout its entire lifecycle based on preset rules.

[0090] Specifically, after completing the batch management of each type of bare metal server, each type of bare metal server that has completed the management process can be checked and evaluated from multiple technical dimensions to confirm whether it meets the standards for subsequent operation. These dimensions include, but are not limited to, hardware resources (CPU, memory, disk), network configuration (MAC address, network card information, LLDP information), power status, and IPMI communication capabilities. This multi-dimensional verification process ensures that each type of bare metal server that has completed the management process has the basic conditions for normal operation, avoiding deployment failures due to configuration errors or hardware defects.

[0091] Next, for each type of bare metal server that has completed the management process, once it has passed multi-dimensional verification, it can be integrated into the operations and maintenance (O&M) system for management and maintenance. The O&M system typically includes modules for monitoring, alarms, log collection, and change control, enabling full lifecycle tracking and intervention for each type of bare metal server, making it a resource that can be uniformly scheduled and managed. Then, the O&M system sets the status flag of the bare metal server for that type to "available," indicating that it has passed all verification stages and is capable of executing tasks. At this point, the bare metal server can be assigned tasks by the scheduler and participate in business operations.

[0092] In practice, multi-dimensional verification can be automated through scripts or API calls. For example, after completing the batch management of each type of bare metal server, the system will sequentially verify whether the hardware resources of each type of bare metal server match the expected specifications, whether the network interface is reachable, and whether the power supply is stable. If a verification item for a type of bare metal server fails, the status of that type of bare metal server will not be updated, and the corresponding exception log will be recorded for maintenance personnel to troubleshoot.

[0093] Simultaneously, a set of management logic (pre-defined rules) can be pre-defined based on business needs and system policies, covering all stages of deployment, operation, and maintenance for each type of bare metal server that has completed the management process. Pre-defined rules may include health check cycles, alarm thresholds, automatic repair strategies, and resource reclamation mechanisms for each type of bare metal server that has completed the management process. By using pre-defined rules to automate the entire lifecycle management of each type of bare metal server that has completed the management process and passed multi-dimensional verification, resource allocation can be continuously optimized, and intelligent decisions can be made in different scenarios.

[0094] In practice, preset rules can be stored in configuration files or a database, and the system will trigger corresponding management actions when it detects specific events. For example, when a specific type of bare metal server that has completed the management process fails multiple health checks in a row, the system can automatically isolate the server and initiate a replacement process according to preset rules; when a specific type of bare metal server that has completed the management process reaches its service life, the system can automatically initiate a retirement process and notify relevant maintenance personnel.

[0095] In the technical solution of this application embodiment, a preset parameter template is configured; based on the preset parameter template, an algorithm is developed for the management process of each type of bare metal server in one or more types of bare metal servers, resulting in a bare metal management algorithm for each type of bare metal server; input parameters for each type of bare metal server are obtained, and the batch management process for each type of bare metal server is completed based on the input parameters of each type of bare metal server using the bare metal management algorithm for each type of bare metal server; wherein, the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers. Thus, firstly, a preset parameter template is configured, covering different dimensional parameters required by various types of bare metal servers, thereby constructing a standardized management process framework for different types of bare metal servers; then, algorithm development is performed based on the preset parameter template to generate a bare metal management algorithm suitable for each type of bare metal server, realizing automated processing logic; then, input parameters for each type of bare metal server are obtained, and the corresponding bare metal management algorithm is used to complete the batch management process. In this way, on the one hand, by using preset parameter templates and algorithm development, the bare metal conduit process can be standardized and modularized, avoiding the need to manually design conduit schemes each time, thereby improving conduit efficiency; on the other hand, by using batch conduit processes, manual intervention can be reduced, improving execution efficiency and consistency during large-scale deployment.

[0096] This application also proposes a method and system for multi-type bare metal nanotubes based on an automated platform. Figure 3 This is a schematic diagram of the architecture of a multi-type bare metal nanotube method and system based on an automated platform provided in an embodiment of this application. For example... Figure 3 As shown, the core ideas of this method and system include:

[0097] (1) By using an automated platform, a bare metal pipe installation process is built, and the bare metal pipe installation steps are standardized. Each time, only the parameters required for the step need to be entered to perform the step.

[0098] (2) Supports batch fabrication of various bare metals, such as computing bare metals, network bare metals, and storage bare metals. In particular, it also supports fabrication of flexible bare metals (EBM).

[0099] Based on this, a brief analysis is conducted using the process of managing a computing bare metal server as an example.

[0100] First, for this batch of bare metal servers to be included in the pipeline, the parameters required in the bare metal inclusion algorithm need to be organized, and the input format needs to be designed in the automation platform so that the platform parameters can be correctly transmitted to the inclusion pipeline. An example table is shown in Table 1.

[0101] Table 1

[0102]

[0103] Then, an algorithm was developed for the management process steps so that the corresponding management process can be completed automatically after the parameters are passed in. For example, after inputting the parameter 'computeV1', the corresponding configuration file is found according to the parameter, as shown in Table 2.

[0104] Table 2

[0105]

[0106] The management process mainly includes: creating a flavor, creating a node, completing the inspection process, and updating network configurations.

[0107] By compiling the parameters for pipe installation, the system inputs them into the automation platform, which then distributes them to the production line. Through the production line process, the batch installation of bare metal of a specific specification can be completed quickly and efficiently.

[0108] When managing processes on an automated platform, each step is independent and has a pause / wait function. This allows for confirmation of the result upon completion of each step, or for execution to be completed in one step. During each waiting period, the execution status of the step can be viewed through the results returned to the automation platform from the underlying layer. If any abnormal results are found, the problem can be investigated and resolved by referring to the exception logs.

[0109] In particular, for the flexible bare metal type, due to the different incorporation process, a separate incorporation algorithm is developed in the incorporation pipeline. However, its essence is still to pass parameters through the automation platform, call the incorporation function in the ironic control node / k8s node, complete the corresponding steps, and complete the incorporation process of the flexible bare metal.

[0110] This application implements a method and system for managing multiple types of bare metal servers based on an automated platform, providing a more efficient architectural solution for bare metal server management. By designing an automated platform to interface with bare metal servers, including the design and implementation of the automated platform and the design and implementation of the pipeline process, and completing the algorithm development for each step in the management process, the system achieves automated batch management of multiple types of bare metal servers. This fundamentally solves the problem of cumbersome bare metal management processes, avoiding the need for scheme design and step-by-step command execution for each bare metal management task. This significantly reduces labor costs and greatly increases the efficiency of bare metal management for new construction or expansion scenarios.

[0111] This application also proposes a bare metal server management device. Figure 4 This is a schematic diagram of a bare metal server management device provided in an embodiment of this application, as shown below. Figure 4 As shown, the device includes:

[0112] Configuration unit 401 is used to configure a preset parameter template; wherein the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers.

[0113] Development unit 402 is used to develop algorithms for the management process of each type of bare metal server in one or more types of bare metal servers based on preset parameter templates, so as to obtain the bare metal management algorithm for each type of bare metal server.

[0114] The acquisition unit 403 is used to acquire the input parameters for each type of bare metal server.

[0115] The management unit 404 is used to complete the batch management process of each type of bare metal server based on the input parameters of each type of bare metal server through the bare metal management algorithm of each type of bare metal server.

[0116] In some embodiments, the input parameters for each type of bare metal server include one or more of the following: first control node network address, second control node network address, server node information, and management type; wherein,

[0117] The 404 duct unit is specifically used for:

[0118] For each type of bare metal server, network-related information of that type of bare metal server is determined based on the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type.

[0119] The network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server, as well as the network-related information of the bare metal server, are input into the bare metal management algorithm of the bare metal server of this type. The bare metal management algorithm of the bare metal server of this type outputs the configuration file corresponding to the bare metal server of this type, and completes the batch management process of the bare metal server of this type based on the configuration file corresponding to the bare metal server of this type.

[0120] In some embodiments, the configuration file corresponding to this type of bare metal server includes: management type, basic identifier, server node information, hardware configuration parameters, and network configuration parameters; wherein,

[0121] The 404 unit is also specifically used for:

[0122] Based on the basic identifier, server node information and hardware configuration parameters of this type of bare metal server, complete the creation of the specification template for this type of bare metal server and the registration of the bare metal node for this type of bare metal server;

[0123] Obtain the actual hardware information of this type of bare metal server, and update the network configuration of this type of bare metal server based on the actual hardware information of this type of bare metal server and the corresponding hardware configuration parameters and network configuration parameters;

[0124] Based on the management type corresponding to this type of bare metal server, determine the deployment logic corresponding to this type of bare metal server; based on the deployment logic corresponding to this type of bare metal server, complete the batch deployment of this type of bare metal server.

[0125] In some embodiments, the hardware configuration parameters corresponding to this type of bare metal server include one or more of the following: the equipped memory specifications, the built-in disk specifications, and the allocated CPU specifications; wherein,

[0126] The 404 unit is also specifically used for:

[0127] Based on the memory specifications and / or built-in disk specifications and / or allocated CPU specifications of this type of bare metal server, create a specification template corresponding to this type of bare metal server.

[0128] Register the bare metal node corresponding to this type of bare metal server based on the specification template, basic identifier, and server node information.

[0129] In some embodiments, the hardware configuration parameters corresponding to this type of bare metal server include one or more of the following: the equipped memory specifications, the built-in disk specifications, and the allocated CPU specifications; the network configuration parameters corresponding to this type of bare metal server include one or more of the following: PXE network-related configuration parameters for the pre-boot execution environment, and service network-related configuration parameters; wherein,

[0130] The 404 unit is also specifically used for:

[0131] Perform a consistency check between the actual hardware information of this type of bare metal server and the physical memory and / or built-in disk specifications and / or allocated CPU specifications configured for this type of bare metal server. If the actual hardware information of this type of bare metal server passes the consistency check, update the network configuration of this type of bare metal server based on the PXE network-related configuration parameters and / or service network-related configuration parameters corresponding to this type of bare metal server.

[0132] In some embodiments, the device further includes:

[0133] The verification unit is used to perform multi-dimensional verification of each type of bare metal server that has completed the management process.

[0134] The update unit is used to connect the bare metal server of this type to the operation and maintenance system and update the status of the bare metal server of this type to available after the bare metal server has passed multi-dimensional verification.

[0135] The management unit is used to perform automated management of this type of bare metal server throughout its entire lifecycle based on preset rules.

[0136] Those skilled in the art should understand that Figure 4 The functions of each unit in the communication device shown can be understood by referring to the relevant description of the aforementioned method. Figure 4 The functions of each unit in the communication device shown can be implemented by a program running on a processor or by specific logic circuits.

[0137] Figure 5 This is a schematic diagram of the processing device provided in an embodiment of this application. The processing device may be a terminal device or a network device. Figure 5 The processing device shown includes a processor 501, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0138] Optionally, such as Figure 5 As shown, the processing device may further include a memory 502. The processor 501 can retrieve and run computer programs from the memory 502 to implement the methods described in this embodiment.

[0139] The memory 502 can be a separate device independent of the processor 501, or it can be integrated into the processor 501.

[0140] Optionally, such as Figure 5 As shown, the processing device may also include a transceiver 503, which the processor 501 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0141] The transceiver 503 may include a transmitter and a receiver. The transceiver 503 may further include an antenna, which may be one or more.

[0142] The processing device may specifically be the bare metal server management device in the embodiments of this application, and the processing device can implement the corresponding processes of the various methods in the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0143] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0144] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0145] This application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to the processing device in this application embodiment, and the computer program causes the computer to execute the corresponding processes implemented by the various methods in this application embodiment; for brevity, further details are omitted here.

[0146] This application also provides a computer program product, including computer program instructions. This computer program product can be applied to the processing device in this application embodiment, and the computer program instructions cause the computer to execute the corresponding processes implemented by the various methods in this application embodiment; for brevity, further details are omitted here.

[0147] Those skilled in the art will 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, or a combination of computer software and electronic hardware. 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.

[0148] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0149] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0150] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0151] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0152] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes 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.

[0153] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A method for managing bare metal servers, characterized in that, The method includes: Configure a preset parameter template; wherein, the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers; Based on the preset parameter template, an algorithm is developed for the management process of each type of bare metal server in one or more types of bare metal servers, so as to obtain the bare metal management algorithm for each type of bare metal server. The system acquires the input parameters for each type of bare metal server and completes the batch management process for each type of bare metal server based on these input parameters using the bare metal management algorithm for each type of bare metal server. The input parameters for each type of bare metal server include one or more of the following: a first control node network address, a second control node network address, server node information, and management type. The first control node network address is the IP address used to manage and control the bare metal server throughout its entire lifecycle. The second control node network address is the IP address used to manage containerized workloads running on the bare metal server. Server node information refers to the detailed configuration information of the bare metal server to be managed. The management type refers to the classification identifier of the bare metal server. The process of batch managing each type of bare metal server based on the input parameters of each type of bare metal server using the bare metal management algorithm includes: For each type of bare metal server, based on the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server of that type, determine the network-related information of the bare metal server of that type; The network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server, as well as the network-related information of the bare metal server, are input into the bare metal management algorithm of the bare metal server of this type. The bare metal management algorithm of the bare metal server of this type outputs the configuration file corresponding to the bare metal server of this type, and completes the batch management process of the bare metal server of this type based on the configuration file corresponding to the bare metal server of this type.

2. The method according to claim 1, characterized in that, The configuration file for this type of bare metal server includes: management type, basic identifier, server node information, hardware configuration parameters, and network configuration parameters; The process of batch managing this type of bare metal server based on the configuration file corresponding to this type of bare metal server includes: Based on the basic identifier, server node information and hardware configuration parameters of this type of bare metal server, complete the creation of the specification template for this type of bare metal server and the registration of the bare metal node for this type of bare metal server; Obtain the actual hardware information of this type of bare metal server, and update the network configuration of this type of bare metal server based on the actual hardware information of this type of bare metal server and the corresponding hardware configuration parameters and network configuration parameters; Based on the management type corresponding to this type of bare metal server, determine the deployment logic corresponding to this type of bare metal server; based on the deployment logic corresponding to this type of bare metal server, complete the batch deployment of this type of bare metal server.

3. The method according to claim 2, characterized in that, The hardware configuration parameters corresponding to this type of bare metal server include one or more of the following: the equipped memory specifications, the built-in disk specifications, and the allocated CPU specifications. The process of creating a specification template for this type of bare metal server and registering the bare metal nodes corresponding to this type of bare metal server, based on the basic identifier, server node information, and hardware configuration parameters, includes: Based on the memory specifications and / or built-in disk specifications and / or allocated CPU specifications of this type of bare metal server, create a specification template corresponding to this type of bare metal server. Register the bare metal node corresponding to this type of bare metal server based on the specification template, basic identifier, and server node information.

4. The method according to claim 2, characterized in that, The hardware configuration parameters for this type of bare metal server include one or more of the following: the equipped memory specifications, the built-in disk specifications, and the allocated CPU specifications; the network configuration parameters for this type of bare metal server include one or more of the following: configuration parameters related to the pre-boot execution environment PXE network and configuration parameters related to the business network. The process of updating the network configuration of this type of bare metal server based on its actual hardware information, hardware configuration parameters, and network configuration parameters includes: Perform a consistency check between the actual hardware information of this type of bare metal server and the physical memory and / or built-in disk specifications and / or allocated CPU specifications configured for this type of bare metal server. If the actual hardware information of this type of bare metal server passes the consistency check, update the network configuration of this type of bare metal server based on the PXE network-related configuration parameters and / or service network-related configuration parameters corresponding to this type of bare metal server.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: For each type of bare metal server that has completed the management process, multi-dimensional verification is performed on that type of bare metal server. If the bare metal server of that type passes the multi-dimensional verification, it is connected to the operation and maintenance system and its status is updated to available. This type of bare metal server is managed automatically throughout its entire lifecycle based on preset rules.

6. A bare metal server management device, characterized in that, The device includes: A configuration unit is used to configure a preset parameter template; wherein the preset parameter template includes multi-dimensional parameters required by one or more types of bare metal servers; The development unit is used to develop an algorithm for the management process of each type of bare metal server in one or more types of bare metal servers based on the preset parameter template, so as to obtain the bare metal management algorithm for each type of bare metal server. The acquisition unit is used to acquire the input parameters of each type of bare metal server; The management unit is used to complete the batch management process for each type of bare metal server based on the input parameters of each type of bare metal server using the bare metal management algorithm for each type of bare metal server. The input parameters for each type of bare metal server include one or more of the following: a first control node network address, a second control node network address, server node information, and management type. The first control node network address refers to the IP address used to manage and control the bare metal server throughout its entire lifecycle. The second control node network address refers to the IP address used to manage containerized workloads running on the bare metal server. The server node information refers to the detailed configuration information of the bare metal server to be managed. The management type refers to the classification identifier of the bare metal server. The aforementioned control unit is specifically used for: For each type of bare metal server, based on the network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server of that type, determine the network-related information of the bare metal server of that type; The network address of the first control node and / or the network address of the second control node and / or the server node information and / or the management type of the bare metal server, as well as the network-related information of the bare metal server, are input into the bare metal management algorithm of the bare metal server of this type. The bare metal management algorithm of the bare metal server of this type outputs the configuration file corresponding to the bare metal server of this type, and completes the batch management process of the bare metal server of this type based on the configuration file corresponding to the bare metal server of this type.

7. A processing device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 5.

9. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 5.

Images