Bare metal server management method and device, electronic equipment and storage medium
By deploying an edge cloud console and management module on edge cloud nodes and adopting thread pool rate limiting and single-threaded processing mechanisms, the management of bare metal servers in Ironic has been optimized, resolving controller crashes and resource discovery issues, and improving management efficiency and stability.
Patent Information
- Application Number
- CN202511263373.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-05
- Publication Date
- 2025-11-07
- Estimated Expiration
- 2045-09-05
AI Technical Summary
Ironic is prone to controller crashes, API responsiveness issues, and resource discovery problems when managing bare metal servers, especially when deployed in parallel, resulting in insufficient resources and affecting management efficiency and stability.
Deploy the edge cloud console and edge bare metal management module on the edge cloud node. By using thread pool rate limiting and single-threaded processing of operation tasks on the same bare metal server, combined with Kubernetes Cluster API and the edge cloud console, and utilizing the mutual exclusion watch mechanism and components of the edge bare metal management module such as BMO, BMCO, and Dnsmasq-Operator, the concurrent processing of bare metal server tasks is optimized.
It effectively avoids the pressure of multi-threading on the underlying Ironic architecture, improves management efficiency, shortens polling time, ensures the performance and stability of edge cloud nodes during expansion, and supports efficient management of a large number of bare metal servers.
Smart Images

Figure CN120750979B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of cloud computing, and in particular to a bare metal server management method and device, electronic equipment and storage medium. BACKGROUND
[0002] Ironic provides comprehensive management of physical servers for OpenStack, so that users can directly control and manage physical hardware in a cloud environment. Through Ironic, users can deploy, manage and monitor physical servers, which are on a par with virtual machines; however, controller crash is a pain point of Ironic management of bare metal, because Ironic uses ISCSI deployment interface, the node exports an Internet Small Computer System Interface (ISCSI) device to the controller, the controller downloads an image from Glance and dumps it to the node. This deployment method causes the controller to be prone to memory shortage when processing a large number of parallel deployments, thereby causing the controller to crash, and since the image is transmitted through the controller, many parallel deployments will cause problems in resource discovery and processing. SUMMARY
[0003] The present application provides a bare metal server management method and device, electronic equipment and storage medium.
[0004] The bare metal server management method provided by the present application is applied to an edge cloud node, and the edge cloud node is deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module includes a Bare Metal Operator (BMO) component and a Baremetal Conductor-Operator (BMCO) component; the BMCO component includes an Ironic component; the BMO component is used to abstract a bare metal server through a Bare Metal Host (BMH) Custom Resource Definition (CRD); the Ironic component is used to perform a corresponding bare metal server management task based on an instruction of the BMO component; and the method includes:
[0005] receiving an operation task through the edge cloud console; the operation task is an operation task for a bare metal server, and the operation task is put into a thread pool;
[0006] The edge cloud console extracts a plurality of operation tasks from a thread pool and calls the edge bare metal management module to process the plurality of operation tasks concurrently; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for the same bare metal server are processed in single thread.
[0007] The bare metal server management device provided by the embodiment of the application is applied to an edge cloud node, and the edge cloud node is deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module comprises a BMO component and a BMCO component; the BMCO component comprises an Ironic component; the BMO component is used to abstract a bare metal server through a BareMetalHost CRD; the Ironic component is used to perform a corresponding bare metal server management task based on an instruction of the BMO component; and the device comprises:
[0008] The receiving unit is configured to receive operation tasks through the edge cloud console; the operation tasks are operation tasks for bare metal servers, and the operation tasks are put into a thread pool;
[0009] The processing unit is configured to extract a plurality of operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to process the plurality of operation tasks concurrently; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for the same bare metal server are processed in single thread.
[0010] The electronic device provided by the embodiment of the application comprises a first processor and a first memory, the first memory is used to store a computer program, and the first processor is used to call and run the computer program stored in the first memory to execute the bare metal server management method corresponding to the embodiment of the application.
[0011] The chip provided by the embodiment of the application comprises a second processor, which is used to call and run a computer program from a second memory, so that a device installed with the chip executes any bare metal server management method provided by the embodiment of the application.
[0012] The storage medium provided by the embodiment of the application is used to store a computer program, and the computer program enables a computer to execute any bare metal server management method provided by the embodiment of the application.
[0013] The computer program product provided by the embodiment of the application comprises a computer program, and the computer program enables a processor to implement any bare metal server management method provided by the embodiment of the application when the computer program is executed by the processor.
[0014] By the bare metal server management method and device, the electronic device and the storage medium provided by the embodiment of the present application, the edge cloud console and the edge bare metal management module are deployed on the edge cloud node, the edge cloud console is used to limit the flow to the edge bare metal management module, the operation tasks of the same bare metal server are processed in single thread, and the pressure on the underlying Ironic caused by the simultaneous operation of the same bare metal server by multiple threads is avoided. BRIEF DESCRIPTION OF DRAWINGS
[0015] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application and illustrate the illustrative embodiments of the present application and their description serve to explain the present application, and do not constitute improper limitations on the present application. In the drawings:
[0016] Figure 1 The implementation flowchart of the bare metal server management method provided by the embodiment of the present application is shown in the figure.
[0017] Figure 2 The bare metal server management architecture provided by the embodiment of the present application is shown in the figure.
[0018] Figure 3 The network plane planning provided by the embodiment of the present application is shown in the figure.
[0019] Figure 4 The structure of the bare metal server management device 400 provided by the embodiment of the present application is shown in the figure.
[0020] Figure 5 The schematic structure of the electronic device provided by the embodiment of the present application is shown in the figure.
[0021] Figure 6 The schematic structure of the chip provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION
[0022] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of the present application.
[0023] It should be noted that in the embodiments of the present application, the term "and / or" is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone. In addition, in the embodiments of the present application, the character " / " generally represents an "or" relationship between the front and rear associated objects.
[0024] In the description of the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, can also represent an associated relationship between the two, or can indicate a relationship with the indicated, configured, and configured.
[0025] In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below, and the following related technologies can be combined with the technical solutions of the embodiments of the present application as optional schemes, which all belong to the protection scope of the embodiments of the present application.
[0026] In recent years, cloud-native technology has rapidly emerged as an important trend in modern software development and deployment. The core of this concept lies in using methods such as microservices architecture, containerization, and continuous delivery to help enterprises achieve rapid iteration and agile response, meeting the market's demand for high performance and flexibility. With the deepening of digital transformation, enterprises are increasingly inclined to adopt cloud-native technology to improve the scalability and reliability of applications, thereby better responding to the rapidly changing business environment. In this context, bare metal servers, as a direct use of physical hardware infrastructure solution, are favored for their excellent performance and resource utilization efficiency.
[0027] Compared with traditional virtualization technology, bare metal servers have several significant advantages. First, since it runs directly on physical hardware, it eliminates the additional overhead brought by the virtualization layer, which enables bare metal servers to provide extremely high computing performance, especially suitable for high-load and latency-sensitive application scenarios. Second, bare metal servers generally have higher resource utilization, which can fully exploit the potential of hardware, thereby reducing the operating costs of enterprises. In addition, bare metal servers also support highly customized configurations, and enterprises can choose suitable hardware combinations according to specific business needs to improve overall efficiency. Therefore, when implementing cloud-native strategies, combining the advantages of bare metal servers, enterprises can obtain stronger computing power and flexibility, thereby achieving more efficient application deployment and management, and promoting the success of digital transformation.
[0028] In related technologies, Ironic provides comprehensive management of physical servers for OpenStack, allowing users to directly control and manage physical hardware in a cloud environment. Through Ironic, users can deploy, manage and monitor physical servers, on a par with virtual machines. Ironic uses intelligent platform management interface technology to remotely power on or off bare machines or other operations without relying on physical switches or operating systems. Preboot Execute Environment (PXE) enables computers to boot through the network rather than from local hard drives, optical drives, etc. Ironic combines PXE technology to achieve remote deployment of operating systems.
[0029] The main disadvantages of Ironic managing bare metal include controller crashes, Application Programming Interface (API) responsiveness issues, and resource discovery issues. These issues are particularly evident when scaling to thousands of nodes, affecting the efficiency and stability of Ironic management.
[0030] Controller crashes are a major problem with Ironic managing bare metal. Since Ironic uses Internet Small Computer System Interface (ISCSI), nodes export ISCSI devices to the controller, which downloads images from Glance and dumps them onto the nodes. This deployment method causes the controller to be prone to Out Of Memory (OOM) situations when handling a large number of parallel deployments, leading to controller crashes.
[0031] API responsiveness is also a significant issue. When scaling the infrastructure, all requests involving the database are very slow because the Inspector component fetches a list of all nodes every 60 seconds to clean up the database. This causes API response times to be extended, affecting the efficiency of management.
[0032] Resource discovery issues also affect the effectiveness of Ironic management. During deployment, since images are "tunneled" through the controller, many parallel deployments can cause resource discovery and processing issues.
[0033] In the embodiments of the present application, a bare metal server management method is proposed, which can be used in edge computing scenarios to implement a bare metal server management method in edge computing scenarios based on Ironic, combined with the Cluster API of Kubernetes and the edge cloud console.
[0034] The Cluster API is a sub-project of Kubernetes, focusing on providing declarative APIs and tools to simplify the creation, upgrade, and operation of multiple Kubernetes clusters. It automates the cluster lifecycle management using Kubernetes-style APIs and patterns. It includes the infrastructure needed to deploy a cluster, such as virtual machines, networks, and load balancers. Simply put, the Cluster API defines a Kubernetes cluster through different CRDs (Cost Representations), and corresponding components read these definitions to deploy and manage their respective clusters. Kubernetes is a complex system, and managing the entire cluster lifecycle is even more complex. The Cluster API simplifies the deployment and management of multiple different clusters, enabling consistent and repeatable cluster management and deployment. By providing various APIs, users can replace the required infrastructure and deployment methods as needed. The Cluster API was designed to provide interfaces for users to specify their own provider; for example, infrastructure providers include OpenStack.
[0035] refer to Figure 1 , Figure 1 This is a schematic diagram illustrating the implementation flow of the bare metal server management method provided in the embodiments of this application, as follows: Figure 1 As shown, the bare metal server management method provided in this embodiment is applied to an edge cloud node, which is equipped with an edge cloud console and an edge bare metal management module. The edge bare metal management module includes a bare metal controller (BMO) component and a bare metal execution controller (BMCO) component. The BMCO component includes an ironic component. The BMO component is used to abstract bare metal servers through a bare metal host (BareMetalHost) using a custom resource CRD. The ironic component is used to execute corresponding bare metal server management tasks based on the instructions of the BMO component. The method includes the following steps:
[0036] Step 101: Receive user operation tasks for the bare metal server through the edge cloud console and put the operation tasks into the thread pool.
[0037] In this embodiment of the application, the edge cloud console can be an Edge Intelligence Station (EIS) console or other types of edge cloud consoles, and this embodiment of the application does not limit this.
[0038] In the embodiment of the present application, the edge cloud console serves as an entry for docking users and plays an important role in the access of the bare metal server. The edge cloud console backend docks with the edge bare metal management module, and the problems of the original Ironic can be solved in the edge cloud console.
[0039] In the embodiment of the present application, the edge bare metal management module can also be referred to as CMetal.
[0040] In the embodiment of the present application, the types of operation tasks include registration, booting, shutting down, hardware inspection, and operation system issuing.
[0041] In the embodiment of the present application, the edge cloud console puts the received operation tasks into a thread pool and limits the parallel operation tasks flowing to the edge bare metal management module.
[0042] Step 102: extracting a plurality of operation tasks from the thread pool through the edge cloud console and calling the edge bare metal management module to concurrently process the plurality of operation tasks; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for the same bare metal server are processed in single thread.
[0043] In the embodiment of the present application, the edge cloud console can limit operation tasks through the bare metal management module in the edge cloud console.
[0044] The edge cloud console utilizes the mutual exclusion Watch mechanism under the edge cloud scenario, which can enable the console to operate only in single thread for the same bare metal server on the basis that a large number of resources can be concurrently processed, thereby avoiding the pressure on the underlying Ironic caused by the simultaneous operation of multiple threads on the same bare metal server.
[0045] In the embodiment of the present application, the edge cloud console has the ability to listen to the state of the underlying resources, and can trigger the corresponding processing event in the first time when the state of the underlying bare metal resources changes.
[0046] Based on this, in an optional embodiment of the present application, the method further includes: listening to the resource state of the bare metal server through the edge cloud console;
[0047] If the change of the resource state of the bare metal server is listened to, the corresponding processing event is triggered.
[0048] For example, when the bare metal server changes from the Created state to the Externally Provisioned state, the edge cloud console extracts the operation task related to the Externally Provisioned state of the bare metal server from the thread pool and puts the operation task into the queue, and calls the edge bare metal management module to perform the related operation task.
[0049] In the embodiments of the present application, the Ironic is optimized for concurrent processing of a large number of bare metals. For a plurality of same operation tasks of different bare metal servers, the console can perform batch operations, extract a preset number of operation tasks at a time, and call the edge bare metal management module for processing, thereby improving the processing efficiency.
[0050] Based on this, in an optional embodiment of the present application, the method further comprises: for a plurality of same operation tasks of different bare metal servers in the thread pool, extracting a preset number of the same operation tasks from the thread pool, and calling the edge bare metal management module for batch processing.
[0051] In the embodiments of the present application, the edge cloud console controls the concurrent tasks through the thread pool, and simultaneously listens to the response of the edge bare metal management module. When the edge bare metal management module does not return a response, when the number of batch-processed bare metals, that is, the number of batch-processed operation tasks, is greater than a preset number, the operation tasks exceeding the preset number are placed in the task queue, so as to avoid blocking a large number of requests at the edge bare metal management module, thereby controlling the flow rate of the interface to the Ironic.
[0052] In the embodiments of the present application, the value of the preset number n is related to the number t of edge cloud nodes. The more the number of edge cloud nodes, the more the number of batch-processed bare metals, and the greater the value of the preset number.
[0053] In the embodiments of the present application, the value of the preset number is related to the number of central processing units (CPUs) of the edge cloud nodes and the number of memories of the edge cloud nodes The more the number of CPUs and the number of memories, the more the number of batch-processed bare metals, and the greater the value of the preset number.
[0054] Based on this, in an optional embodiment of the present application, the value of the preset number is related to a first parameter; the first parameter comprises:
[0055] the number of edge cloud nodes, the number of CPUs of the edge cloud nodes, and the number of memories of the edge cloud nodes.
[0056] In the embodiments of the present application, the preset number of values has the following relationship with the first parameter.
[0057] wherein, The influence weights of the CPU core number and the memory number on the result are 0.7 and 0.3 respectively.
[0058] In the embodiments of the present application, the ratio of the memory number to the CPU core number is less than or equal to 2.
[0059] In the embodiments of the present application, the BMO component is a Kubernetes controller for managing bare metal hosts, represented by bare metal host custom resources in Kubernetes. The functions of the BMO component include one or more of the following:
[0060] 1) Check the hardware of the bare metal server through BMH and report the corresponding detailed information, including information about CPU, Random Access Memory (RAM), disk, Network Interface Card (NIC), etc.
[0061] 2) The bare metal server can be prepared by configuring the Redundant Array of Independent Disks (RAID), changing the firmware settings, or updating the system and / or Baseboard Management Controller (BMC) firmware.
[0062] 3) Configure the required image for the bare metal server.
[0063] 4) Clean up the hard disk content of the bare metal server before and after configuration.
[0064] In the embodiments of the present application, the edge bare metal management module further includes a Dnsmasq-Operator component, which provides the Dynamic Host Configuration Protocol (DHCP) capability for the bare metal server, and has a way to set a whitelist to prevent non-bare metal servers from obtaining a communication address, and finely manages the DHCP; in the embodiments of the present application, the communication address can be an Internet Protocol (IP) address.
[0065] Based on this, in an optional embodiment of the present application, the edge bare metal management module further includes a Dnsmasq-Operator component; the method further includes:
[0066] provide a dynamic host configuration protocol (DHCP) capability for the bare metal server through the Dnsmasq-Operator component; and set a whitelist through the Dnsmasq-Operator component to prevent non-bare metal servers from obtaining a communication address.
[0067] In the embodiments of the present application, the edge bare metal management module further comprises a ProxyCenter component; wherein the ProxyCenter component comprises:
[0068] The BareMetalProxy component is responsible for communicating with a bareAgent in a bare metal operating system, implementing management of the bare metal operating system, and access to a bare metal WebShell, bare metal modification of a host name, and change of a password and other operation and maintenance operations.
[0069] The ImageProxy component is an image mirroring center, and is responsible for providing images for bare metals
[0070] The CloudMonitorMock component acquires hardware monitoring data information of the bare metal through an intelligent platform management interface (IPMI) protocol, such as CPU, hard disk, memory and other hardware information.
[0071] Based on this, in an optional embodiment of the present application, the method further comprises: acquiring, by the edge bare metal management module, hardware monitoring data information of the bare metal server based on an intelligent platform management interface (IPMI) protocol.
[0072] In the embodiments of the present application, the BMCO component comprises Nginx and Ironic CRD resources, wherein the Ironic CRD is controlled by a management mechanism of Kubernetes to control a life cycle of IronicStandalone, Ironic is a specific executor for image distribution of the edge bare metal management module, and the BMO registers, powers on, powers off, checks hardware, and distributes operating systems to the BMH through an API thereof; the CRD of Nginx provides a gateway capability, and realizes dynamic management of configuration.
[0073] In the embodiments of the present application, Ironic is a specific executor for image distribution of the edge bare metal management module, and Ironic provides robust RESTful APIs interfaces and functions covering the entire hardware life cycle: from bare machine registration and hardware specification retrieval of newly discovered bare machines, to configuration and configuration using a custom operating system image, and to machine reset, cleaning for reconfiguration or destruction.
[0074] In this embodiment, the Inspector component retrieves a list of all nodes every 60 seconds to clean the database. By adopting the bare metal server management method of this application, the bare metal server can be processed in batches, shortening the polling time and preventing the Inspector component from occupying the database connection pool and blocking other API requests.
[0075] refer to Figure 2 , Figure 2 This is a schematic diagram of the bare metal server management architecture provided in the embodiments of this application, such as... Figure 2 As shown, the edge cloud node deploys EIS and CMetal. CMetal includes: BMO component, Dnsmasq-Operator component, BMCO component, and ProxyCenter component. The BMO component abstracts the bare metal server through BareMetalHost-CRD. The ProxyCenter component includes: BareMetalProxy component, ImageProxy component, and CloudMonitorMock component. The BMCO component includes: Nginx component and Ironic component. The Ironic component includes: Ironic-API component and Ironic-conductor component. The Ironic-API component provides RESTful API interfaces, and the Ironic-conductor component is the execution engine of the Ironic service, responsible for actually managing the lifecycle of the bare metal server.
[0076] refer to Figure 3 , Figure 3 This is a network plan diagram provided in an embodiment of this application. The Master is CMetal. In this embodiment, CMetal further includes: a MySQL database for storing data; an Ironic-client component, a command-line tool; an Ironic-IPA-Config component, providing Ironic with the ability to remotely access the bare metal server; Ironic-Dnsmasq, which assigns IP addresses to the bare metal server and boots the PXE; and an Ironic-Log-Watch component, used for real-time tracking and analysis of the bare metal server's operation logs. The IPMI network is the out-of-band management network for the bare metal server, enabling server power on / off and hardware information collection and monitoring. The unTag network is the installation network, where edge cloud nodes provide operational provisioning capabilities to the bare metal server through services such as Ironic.
[0077] Continue to refer to Figure 3The management network vlan 1 of the CMetal management server and the IPMI network of the bare metal server are in three-layer routing intercommunication; the monitoring performance data of the bare metal server is reported to the CMetal management server through the IPMI network and the management network vlan 1; the CMetal management server is in three-layer routing intercommunication with the bare metal management network vlan 3 through the management network vlan 1, and realizes the configuration of the operating system (OS) of the bare metal server, such as hostname, key, password and the like.
[0078] With reference to the foregoing Figure 3 The bare metal management network vlan 3 is in three-layer routing intercommunication with the management network vlan 1 of the CMetal management server, and realizes the configuration of the OS of the bare metal server through the management network vlan 1 and the management network vlan 3, such as hostname, key, password and the like.
[0079] With reference to the foregoing Figure 3 The CMetal management server and the edge cloud console are in intercommunication through the management network vlan 2, and the edge cloud console provides a webshell of the bare metal to a user through the management network vlan 2, the management network vlan 1 and the management network vlan 3.
[0080] Based on this, in an optional embodiment of the present application, the management network vlan 1 of the edge bare metal management module is in three-layer routing intercommunication with the IPMI network of the bare metal server; the management network vlan 1 of the edge bare metal management module is in three-layer routing intercommunication with the management network vlan 3 of the bare metal server; the edge bare metal management module and the edge cloud console communicate through the management network vlan 2.
[0081] In the embodiment of the present application, the edge bare metal management module can be deployed in each of the plurality of edge cloud nodes, or the edge bare metal management module can be deployed in part of the plurality of edge cloud nodes. It can be understood that the more the number of the edge bare metal management modules, the more the number of the copies of the bare metal servers, and the more reliable the system,
[0082] The bare metal server management method provided in the embodiments of the present application can support management of 200 bare metal servers and batch operation of a maximum of 40 bare metal servers at a time with only three edge cloud nodes in cooperation with the edge cloud console, and the edge cloud console provides double protection. The first protection is the mutual exclusion Watch mechanism in the edge cloud scenario, and the second protection is the optimization of the edge cloud console for Ironic concurrent processing of a large number of bare metal servers, which can perform batch operation in the console and call the underlying CMetal for processing. The edge cloud node can effectively monitor the state of the bare metal server, and the network planning takes into account the edge cloud scenario, so that the number of bare metal servers managed by the edge cloud node can be linearly increased when the edge cloud node is expanded, and the performance does not decrease significantly.
[0083] The embodiments of the present application also provide a bare metal server management device 400, which is described with reference to Figure 4 , Figure 4 The bare metal server management device 400 provided in the embodiments of the present application is a structural schematic diagram, and the bare metal server management device 400 in the embodiments is applied to an edge cloud node, and the edge cloud node is deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module comprises a BMO component and a BMCO component; the BMCO component comprises an Ironic component; the BMO component is used to abstract a bare metal server through a BareMetalHost CRD; the Ironic component is used to perform a corresponding bare metal server management task based on the instruction of the BMO component; and the bare metal server management device 400 comprises:
[0084] The receiving unit is configured to receive an operation task through the edge cloud console; the operation task is an operation task for a bare metal server, and the operation task is put into a thread pool.
[0085] The processing unit is configured to extract a plurality of operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to concurrently process the plurality of operation tasks; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for the same bare metal server are processed in a single thread.
[0086] In the embodiments of the present application, the processing unit is configured to listen to the resource state of the bare metal server through the edge cloud console; and if a change in the resource state of the bare metal server is listened to, a corresponding processing event is triggered.
[0087] In the embodiments of the present application, the processing unit is configured to extract a preset number of the same operation tasks for different bare metal servers in the thread pool from the thread pool, and call the edge bare metal management module for batch processing.
[0088] In the embodiments of the present application, the preset number of values is related to a first parameter; and the first parameter includes: a number of the edge cloud nodes, a number of central processing unit (CPU) cores of the edge cloud nodes, and a number of memories of the edge cloud nodes.
[0089] In the embodiments of the present application, the edge bare metal management module further includes a Dnsmasq-Operator component; and the processing unit is configured to provide a dynamic host configuration protocol (DHCP) capability for the bare metal server through the Dnsmasq-Operator component, and set a white list through the Dnsmasq-Operator component to prevent non-bare metal servers from obtaining a communication address.
[0090] In the embodiments of the present application, the processing unit is configured to obtain hardware monitoring data information of the bare metal server based on an intelligent platform management interface (IPMI) protocol through the edge bare metal management module.
[0091] In the embodiments of the present application, a management network vlan1 of the edge bare metal management module and an IPMI network of the bare metal server are in three-layer routing intercommunication; the management network vlan1 of the edge bare metal management module and a management network vlan3 of the bare metal server are in three-layer routing intercommunication; and the edge bare metal management module and the edge cloud console communicate through a management network vlan2.
[0092] Those skilled in the art should understand that, Figure 4 The implementation functions of each unit in the bare metal server management apparatus 400 shown can be understood with reference to the related descriptions of the foregoing method. Figure 4 The functions of each unit in the bare metal server management apparatus 400 shown can be implemented by a program running on a processor, or by a specific logic circuit.
[0093] Figure 5 FIG. 5 is a schematic structural diagram of an electronic device 500 provided in an embodiment of the present application. Figure 5 The electronic device 500 shown includes a first processor 510, which can call and run a computer program from a memory to implement the bare metal server management method provided in the embodiments of the present application.
[0094] Optionally, as shown, Figure 5 The electronic device 500 shown can further include a first memory 520. The first processor 510 can call and run a computer program from the first memory 520 to implement the bare metal server management method provided in the embodiments of the present application.
[0095] The first memory 520 can be a separate device independent of the first processor 510, or can be integrated in the first processor 510.
[0096] Optionally, as shown in the figure, the electronic device 500 can further include a transceiver 530, and the first processor 510 can control the transceiver 530 to perform bare metal management with other devices, specifically, can send information or data to other devices, or receive information or data sent by other devices. Figure 5
[0097] The transceiver 530 can include a transmitter and a receiver. The transceiver 530 can further include an antenna, and the number of antennas can be one or more.
[0098] The electronic device 500 can be specifically a bare metal server management apparatus 400 / edge cloud node of the embodiments of the present application, and the electronic device 500 can implement the corresponding processes in the various methods of the embodiments of the present application which are implemented by the bare metal server management apparatus 400 / edge cloud node. For the sake of brevity, they will not be described here.
[0099] Exemplarily, the embodiments of the present application also provide a computer program product including a computer program, which can be executed by the first processor 510 of the electronic device 500 to complete the steps of any of the preceding methods.
[0100] Figure 6 The chip 600 shown in the figure includes a second processor 610, which can call and run a computer program from a memory to implement the method in the embodiments of the present application. Figure 6 The chip 600 shown in the figure includes a second processor 610, which can call and run a computer program from a memory to implement the method in the embodiments of the present application.
[0101] Optionally, as shown in the figure, the chip 600 can further include a second memory 620. The second processor 610 can call and run a computer program from the second memory 620 to implement the method in the embodiments of the present application. Figure 6 The second memory 620 can be a separate device independent of the second processor 610, or can be integrated in the second processor 610.
[0102] Optionally, the chip 600 can further include an input interface 630. The second processor 610 can control the input interface 630 to perform bare metal management with other devices or chips, specifically, can obtain information or data sent by other devices or chips.
[0103]
[0104] Optionally, the chip 600 can further include an output interface 640. The second processor 610 can control the output interface 640 to perform bare metal management with other devices or chips, and specifically, can output information or data to other devices or chips.
[0105] The chip can be applied to the electronic device 500 in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the electronic device 500 in the various methods of the embodiments of the present application. For brevity, details are not repeated here.
[0106] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.
[0107] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip having a signal processing capability. In the implementation process, each step of the above method embodiments can be completed by integrated logic circuits of hardware in the processor or instructions in the form of software. The processor mentioned above can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a ready programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware code processor for execution, or a combination of hardware and software units in the code processor for execution. The software unit can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory, an electrically erasable programmable memory, a register, etc. The storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.
[0108] It is to be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used, such as a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), and a Direct Rambus RAM (DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not be limited to, these and any other suitable types of memory.
[0109] It should be understood that the above-mentioned memory is exemplary but not limiting, for example, the memory in the embodiments of the present application can also be a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), and a direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.
[0110] The embodiment of the present application further provides a storage medium for storing a computer program. The storage medium can be applied to the electronic device 500 in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes of the electronic device 500 in the various methods of the embodiment of the present application. For brevity, details are not repeated here.
[0111] Those skilled in the art can clearly understand that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized 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 realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.
[0112] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.
[0113] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.
[0114] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
[0115] In addition, each functional unit in the various embodiments of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.
[0116] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or an electronic device 500, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various media that can store program codes.
[0117] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application.
Claims
1. A bare metal server management method, characterized by, The application is applied to an edge cloud node, wherein the edge cloud node is deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module comprises a bare metal controller BMO component and a bare metal execution controller BMCO component; the BMCO component comprises an Ironic component; the BMO component is used to abstract a bare metal server through a BareMetalHost custom resource CRD; the Ironic component is used to perform a corresponding bare metal server management task based on an instruction of the BMO component; and the method comprises the following steps: receiving an operation task through the edge cloud console; the operation task is an operation task for a bare metal server; and the operation task is put into a thread pool; extracting a plurality of operation tasks from the thread pool through the edge cloud console and calling the edge bare metal management module to concurrently process the plurality of operation tasks; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for the same bare metal server are processed in a single thread.
2. The method of claim 1, wherein, Further comprising the following steps: listening to a resource state of the bare metal server through the edge cloud console; if a change in the resource state of the bare metal server is listened to, triggering a corresponding processing event.
3. The method of claim 2, wherein, Further comprising the following steps: for a plurality of same operation tasks for different bare metal servers in the thread pool, extracting a preset number of the same operation tasks from the thread pool and calling the edge bare metal management module for batch processing.
4. The method of claim 3, wherein: the preset number is related to a first parameter; and the first parameter comprises: a number of the edge cloud nodes, a number of central processing unit (CPU) cores of the edge cloud nodes, and a number of memories of the edge cloud nodes.
5. The method of claim 4, wherein, The edge bare metal management module further comprises a Dnsmasq-Operator component; and the method further comprises the following steps: providing dynamic host configuration protocol (DHCP) capability for the bare metal server through the Dnsmasq-Operator component; and setting a white list through the Dnsmasq-Operator component to prevent non-bare metal servers from obtaining a communication address.
6. The method of claim 5, wherein, The method further comprises the following step: obtaining hardware monitoring data information of the bare metal server based on an intelligent platform management interface (IPMI) protocol through the edge bare metal management module.
7. The method of any one of claims 1 to 6, wherein: a management network vlan1 of the edge bare metal management module and an IPMI network of a bare metal server are in three-layer route intercommunication; the management network vlan1 of the edge bare metal management module and a management network vlan3 of the bare metal server are in three-layer route intercommunication; and the edge bare metal management module and the edge cloud console communicate through a management network vlan2. 8.A bare metal server management apparatus, characterized by, The application is applied to an edge cloud node, and the edge cloud node is deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module comprises a BMO component and a BMCO component; the BMCO component comprises an Ironic component; the BMO component is used to abstract a bare metal server through a BareMetalHost CRD; the Ironic component is used to perform a corresponding bare metal server management task based on an instruction of the BMO component; and the device comprises: A receiving unit is configured to receive an operation task through the edge cloud console; the operation task is an operation task for a bare metal server; and the operation task is put into a thread pool. A processing unit is configured to extract a plurality of operation tasks from the thread pool through the edge cloud console, and call the edge bare metal management module to concurrently process the plurality of operation tasks; wherein the plurality of operation tasks are operation tasks for different bare metal servers, and operation tasks for a same bare metal server are processed in a single thread.
9. An electronic device, comprising: The application comprises: A first processor and a first memory for storing a computer program; the first processor is configured to call and run the computer program stored in the first memory, and execute the bare metal server management method according to any one of claims 1 to 7.
10. A storage medium, characterized by A computer program for storing a computer program, which enables a computer to execute the bare metal server management method according to any one of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the bare metal server management method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Control method and device for OpenStack cloud computing management platform
CN108984272A
Bare metal server implementation method and system based on intelligent network card
CN114610447A