Bare metal server management method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a bare metal server management method and device, electronic equipment and a storage medium, the bare metal server management method 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 method comprises the following steps: receiving an operation task through the edge cloud console; the operation task is an operation task aiming at a bare metal server, and putting the operation task into a thread pool; extracting a plurality of operation tasks from a 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 aiming at different bare metal servers, and the operation tasks aiming at the same bare metal server are processed by a single thread.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a bare metal server management method, device, electronic device, and storage medium. Background Art

[0002] Ironic provides comprehensive management of physical servers for OpenStack, allowing users to directly control and manage physical hardware in a cloud environment. With Ironic, users can deploy, manage, and monitor physical servers alongside virtual machines. However, controller crashes are a pain point for Ironic in managing bare metal servers. Because Ironic uses the iSCSI deployment interface, nodes export Internet Small Computer System Interface (iSCSI) devices to the controller, which then downloads images from Glance and dumps them onto the nodes. This deployment method makes it easy for the controller to run out of memory when handling a large number of parallel deployments, causing the controller to crash. Because images are "tunneled" through the controller, many parallel deployments can lead to problems with resource discovery and processing. Summary of the Invention

[0003] Embodiments of the present application provide a bare metal server management method, device, electronic device, and storage medium.

[0004] The bare metal server management method provided in an embodiment of the present 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 includes: a bare metal operator (BMO) component and a bare metal conductor-operator (BMCO) component; the BMCO component includes an Ironic component; the BMO component is used to abstract the bare metal server through a bare metal host (BMH) custom resource definition (CRD); the Ironic component is used to execute corresponding bare metal server management tasks based on instructions of the BMO component; the method includes: receiving an operation task through the edge cloud console; the operation task is an operation task for a bare metal server, and placing the operation task into a thread pool; The edge cloud console extracts multiple operation tasks from the thread pool and calls the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

[0005] The bare metal server management device provided in an embodiment of the present 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 includes: a BMO component and a BMCO component; the BMCO component includes an Ironic component; the BMO component is used to abstract the bare metal server through the BareMetalHost CRD; the Ironic component is used to execute corresponding bare metal server management tasks based on the instructions of the BMO component; the device includes: 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 placed in a thread pool; Processing unit: used to extract multiple operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

[0006] The electronic device provided in an embodiment of the present application includes: 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 present application.

[0007] The chip provided in the embodiment of the present application includes: a second processor, which is used to call and run a computer program from a second memory, so that a device equipped with the chip executes any bare metal server management method provided in the embodiment of the present application.

[0008] The storage medium provided in the embodiments of the present application is used to store a computer program, which enables a computer to execute any bare metal server management method provided in the embodiments of the present application.

[0009] The computer program product provided in the embodiments of the present application includes a computer program, which, when executed by a processor, implements any bare metal server management method provided in the embodiments of the present application.

[0010] Through the bare metal server management method, device, electronic device and storage medium provided in the embodiments of the present application, by deploying the edge cloud console and edge bare metal management module on the edge cloud node, the edge cloud console is used to limit the flow to the edge bare metal management module, and the operation tasks of the same bare metal server are processed in a single thread, avoiding the pressure on the underlying Ironic caused by multiple threads operating the same bare metal server at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings: Figure 1 A schematic diagram of the implementation process of the bare metal server management method provided in an embodiment of the present application; Figure 2 A schematic diagram of the bare metal server management architecture provided in an embodiment of the present application; Figure 3 A schematic diagram of the network plan provided for an embodiment of the present application; Figure 4 A schematic diagram of the structure of a bare metal server management device 400 provided in an embodiment of the present application; Figure 5 A schematic structural diagram of an electronic device provided in an embodiment of the present application; Figure 6 A schematic structural diagram of the chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0012] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0013] It should be noted that in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the embodiments of the present application, the character " / " generally indicates that the associated objects are in an "or" relationship.

[0014] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0015] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0016] In recent years, cloud-native technologies have rapidly emerged as a key trend in modern software development and deployment. This concept, centered around enabling enterprises to achieve rapid iteration and agile response through approaches like microservices architecture, containerization, and continuous delivery, meets market demands for high performance and flexibility. With the deepening of digital transformation, enterprises are increasingly adopting cloud-native technologies to improve application scalability and reliability, enabling them to better navigate the rapidly changing business environment. Against this backdrop, bare metal servers, as an infrastructure solution that directly leverages physical hardware, have become increasingly popular due to their superior performance and resource efficiency.

[0017] Bare metal servers offer several significant advantages over traditional virtualization technologies. First, because they run directly on physical hardware, they eliminate the additional overhead introduced by the virtualization layer. This enables bare metal servers to provide extremely high computing performance, making them particularly suitable for high-load and latency-sensitive application scenarios. Second, bare metal servers typically have higher resource utilization, fully leveraging the potential of hardware and thus reducing an enterprise's operating costs. Furthermore, bare metal servers support highly customized configurations, allowing enterprises to select the appropriate hardware combination based on specific business needs, improving overall efficiency. Therefore, when implementing a cloud-native strategy, combined with the advantages of bare metal servers, enterprises can gain greater computing power and flexibility, enabling more efficient application deployment and management, and driving the success of digital transformation.

[0018] Among related technologies, Ironic provides comprehensive management of physical servers for OpenStack, allowing users to directly control and manage physical hardware in a cloud environment. With Ironic, users can deploy, manage, and monitor physical servers alongside virtual machines. Leveraging intelligent platform management interface technology, Ironic can remotely power on and off bare metal servers, performing other operations without relying on physical switches or operating systems. The Preboot Execute Environment (PXE) allows computers to boot over the network rather than from local hard drives, optical drives, and other devices. Combined with PXE technology, Ironic enables remote deployment of operating systems.

[0019] The main drawbacks of Ironic's bare metal management include controller crashes, application programming interface (API) responsiveness issues, and resource discovery issues. These issues are particularly noticeable when scaling to thousands of nodes, affecting Ironic's management efficiency and stability.

[0020] Controller crashes are a major issue with Ironic managing bare metal instances. Because Ironic uses the Internet Small Computer System Interface (ISCSI), nodes export ISCSI devices to the controller, which then downloads images from Glance and dumps them to the nodes. This deployment method makes the controller prone to out-of-memory (OOM) errors when handling large numbers of concurrent deployments, leading to controller crashes.

[0021] API responsiveness was also a significant issue. As we scaled our infrastructure, all database requests became extremely slow because the Inspector component retrieved a list of all nodes every 60 seconds to clean up the database. This resulted in longer API response times and hindered management efficiency.

[0022] Resource discovery issues also hampered Ironic's management. During deployment, because images were "tunneled" through the controller, many concurrent deployments led to resource discovery and processing issues.

[0023] In an embodiment of the present application, a bare metal server management method is proposed, which can be implemented in an edge computing scenario based on Ironic combined with the Cluster API of Kubernetes and the edge cloud console.

[0024] The Cluster API is a subproject of Kubernetes, focused on providing declarative APIs and tools to simplify the creation, upgrade, and operation of multiple Kubernetes clusters. It uses Kubernetes-style APIs and patterns to automate cluster lifecycle management. This includes the infrastructure required for cluster deployment, such as virtual machines, networks, and load balancers. Simply put, the Cluster API defines a Kubernetes cluster using various CRDs. Components read these definitions and deploy and manage the corresponding 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 clusters, enabling consistent and repeatable cluster management and deployment. By providing a variety of APIs, users can customize their infrastructure and deployment methods based on their needs. The Cluster API was designed to provide interfaces for users to define their own providers, such as OpenStack.

[0025] refer to Figure 1 , Figure 1 This is a schematic diagram of the implementation process of the bare metal server management method provided in the embodiment of the present application, as shown in FIG. Figure 1 As shown, the bare metal server management method provided in this embodiment 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 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 the bare metal server through the bare metal host BareMetalHost 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: Step 101: Receive a user's operation task for a bare metal server through the edge cloud console, and put the operation task into a thread pool.

[0026] In the embodiment of the present application, the edge cloud console can be an edge intelligence station (EIS) console or other types of edge cloud consoles, and the embodiment of the present application does not limit this.

[0027] In this embodiment, the Edge Cloud Console serves as the user's portal for accessing bare metal servers. The Edge Cloud Console's backend connects to the Edge Bare Metal Management Module, resolving native Ironic issues within the Edge Cloud Console.

[0028] In the embodiment of the present application, the edge bare metal management module may also be referred to as CMetal.

[0029] In the embodiment of the present application, the types of operation tasks include: registration, startup, shutdown, hardware inspection, operating system distribution and other tasks.

[0030] In an embodiment of the present application, the edge cloud console will place the received operation tasks into the thread pool and limit the flow of parallel operation tasks flowing to the edge bare metal management module.

[0031] Step 102: Extract multiple operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

[0032] In an embodiment of the present application, the edge cloud console can limit the flow of operation tasks through the bare metal management module in the edge cloud console.

[0033] The edge cloud console uses the mutually exclusive Watch mechanism in the edge cloud scenario. This mechanism allows the console to implement operations on the same bare metal server only through a single thread while a large number of resources can be processed concurrently. This avoids the pressure on the underlying Ironic caused by multiple threads operating the same bare metal server at the same time.

[0034] In an embodiment of the present application, the edge cloud console has the ability to monitor the status of underlying resources, and can trigger corresponding processing events in the first time when the status of the underlying bare metal resources changes.

[0035] Based on this, in an optional implementation manner of the present application, the method further includes: monitoring the resource status of the bare metal server through the edge cloud console; If the resource status of the bare metal server is monitored to change, a corresponding processing event is triggered.

[0036] For example, when a bare metal server changes from the Created state to the ExternallyProvisioned state, the edge cloud console extracts the operation tasks related to the bare metal server and the ExternallyProvisioned state from the thread pool and puts them into the queue, and calls the edge bare metal management module to execute the related operation tasks.

[0037] In an embodiment of the present application, Ironic is optimized for concurrently processing a large number of bare metal servers. For multiple identical 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 processing efficiency.

[0038] Based on this, in an optional implementation of the present application, the method further includes: for multiple identical operation tasks for different bare metal servers in the thread pool, extracting a preset number of the identical operation tasks from the thread pool, and calling the edge bare metal management module for batch processing.

[0039] In an embodiment of the present application, the edge cloud console manages concurrent tasks through a thread pool control, and monitors the response of the edge bare metal management module at the same time. When the edge bare metal management module does not return a response, when the number of bare metals processed in batches, that is, the operation tasks processed in batches is greater than the preset number, the operation tasks exceeding the preset number are placed in the task queue to avoid blocking a large number of requests in the edge bare metal management module, thereby controlling the flow rate of the interface to Ironic.

[0040] In an embodiment of the present application, the value n of the preset number is related to the number of edge cloud nodes t. The more edge cloud nodes there are, the more bare metals that can be processed in batches, and the larger the value of the preset number.

[0041] In the embodiment of the present application, the value of the preset number is consistent with the number of cores of the central processing unit (CPU) of the edge cloud node. And the memory of the edge cloud node The more CPU cores and memory there are, the more bare metals that can be processed in batches, and the larger the preset number value.

[0042] Based on this, in an optional implementation manner of the present application, the value of the preset number is related to a first parameter; the first parameter includes: The number of edge cloud nodes, the number of CPU cores of the edge cloud nodes, and the amount of memory of the edge cloud nodes.

[0043] In the embodiment of the present application, the value of the preset number has the following relationship with the first parameter.

[0044] ,in, ,The ,influence weights of the number of CPU cores and the ,memory number on the results are 0.7 and 0.3 respectively.

[0045] In the embodiment of the present application, the ratio of the number of memories to the number of CPU cores is less than or equal to 2.

[0046] In this embodiment, the BMO component is a Kubernetes controller that manages bare metal hosts and is represented in Kubernetes by a bare metal host custom resource. The BMO component's functions include one or more of the following: 1) Use BMH to check the hardware of the bare metal server and report the corresponding detailed information, including information about the CPU, random access memory (RAM), disk, network interface card (NIC), etc.

[0047] 2) You can choose to prepare the bare metal server by configuring the Redundant Array of Independent Disks (RAID), changing firmware settings, or updating the system and / or Baseboard Management Controller (BMC) firmware.

[0048] 3) Configure the required image for the bare metal server.

[0049] 4) Clean the hard disk contents of the bare metal server before and after configuration.

[0050] In an embodiment of the present application, the edge bare metal management module also includes: a Dnsmasq-Operator component, which provides the bare metal server with the Dynamic Host Configuration Protocol (DHCP) capability, and has a whitelist setting method to prevent non-bare metal servers from obtaining communication addresses, thereby performing refined management of DHCP; in an embodiment of the present application, the communication address can be an Internet Protocol (IP) address.

[0051] Based on this, in an optional embodiment of the present application, the edge bare metal management module further includes: a Dnsmasq-Operator component; and the method further includes: The Dnsmasq-Operator component provides the bare metal server with Dynamic Host Configuration Protocol (DHCP) capability; and the Dnsmasq-Operator component sets a whitelist to prevent non-bare metal servers from obtaining communication addresses.

[0052] In the embodiment of the present application, the edge bare metal management module further includes: a ProxyCenter component; wherein the ProxyCenter component includes: BareMetalProxy component: Responsible for communicating with the bareAgent in the bare metal operating system to manage the bare metal operating system, access the bare metal WebShell, and perform operations such as host name modification and password change on bare metal.

[0053] ImageProxy component: It is the image center and is responsible for providing images for bare metal. CloudMonitorMock component: obtains bare metal hardware monitoring data information through the IPMI protocol, such as CPU, hard disk, memory, and other hardware information.

[0054] Based on this, in an optional implementation manner of the present application, the method further includes: obtaining hardware monitoring data information of the bare metal server based on the intelligent platform management interface IPMI protocol through the edge bare metal management module.

[0055] In the embodiment of the present application, BMCO components include CRD resources such as Nginx and Ironic, among which Ironic's CRD controls the IronStandalone lifecycle through the Kubernetes management mechanism. Ironic is the specific executor of the image distribution of the edge bare metal management module. BMO registers, starts, shuts down, checks hardware, and distributes the operating system to BMH through its API; Nginx's CRD provides gateway capabilities and realizes dynamic management of configuration.

[0056] In the embodiment of the present application, Ironic is the specific executor of the image distribution of the edge bare metal management module. Ironic provides a robust RESTful APIs interface and functions covering the entire hardware life cycle: from bare metal registration and hardware specification retrieval of newly discovered bare metals, configuration and configuration with custom operating system images, to machine reset, cleanup for reconfiguration or destruction.

[0057] In an embodiment of the present application, the Inspector component obtains a list of all nodes every 60 seconds to clean up the database. By adopting the bare metal server management method of the present application, the bare metal servers can be processed in batches, the polling time can be shortened, and the Inspector component can be prevented from occupying the database connection pool and blocking other API requests.

[0058] refer to Figure 2 , Figure 2 This is a schematic diagram of the bare metal server management architecture provided in the embodiment of the present application, such as Figure 2 As shown in the figure, EIS and CMetal are deployed on the edge cloud node. CMetal includes: BMO component, Dnsmasq-Operator component, BMCO component and ProxyCenter component; BMO component abstracts bare metal server through BareMetalHost-CRD; ProxyCenter component includes: BareMetalProxy component, ImageProxy component and CloudMonitorMock component; BMCO component includes: Nginx component and Ironic component; Ironic component includes: Ironic-API component and Ironic-conductor component; Ironic-API component is used to provide RESTful API interface, and Ironic-conductor component is the execution engine of Ironic service, which is responsible for actually managing the life cycle of bare metal server.

[0059] refer to Figure 3 , Figure 3 In the network plan diagram provided for this embodiment of the application, the Master is CMetal. In this embodiment, CMetal also includes: a MySQL database for data storage; the Ironic-client component is a command-line tool; the Ironic-IPA-Config component provides Ironic with remote access to the bare metal server; the Ironic-Dnsmasq component assigns IP addresses to the bare metal server and initiates PXE boot; and the Ironic-Log-Watch component is used to track and analyze the bare metal server's operation logs in real time. The IPMI network is the bare metal server's out-of-band management network, which enables server startup and shutdown, as well as hardware information collection and monitoring. The unTag network is the installation network, and the edge cloud node provides the bare metal server with the ability to issue operations through services such as Ironic.

[0060] Continue to refer Figure 3The management network VLAN 1 of the CMetal management server is interconnected with the ipmi network layer 3 routing of the bare metal server; 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 interconnected with the bare metal management network VLAN 3 layer 3 routing through the management network VLAN 1 to manage the bare metal server operating system (OS) configuration, such as hostname, key, password, etc.

[0061] Continue to refer Figure 3 The bare metal management network vlan3 is interconnected with the management network vlan1 of the CMetal management server through the three-layer routing. The bare metal server OS configuration, such as hostname, key, password, etc., is managed through the management network vlan1 and management network vlan3.

[0062] Continue to refer Figure 3 , the CMetal management server and the edge cloud console communicate with each other through the management network VLAN2. The edge cloud console provides bare metal webshell to users through the management network VLAN2, management network VLAN1 and management network VLAN3.

[0063] Based on this, in an optional implementation of the present application, the management network vlan1 of the edge bare metal management module is interconnected with the IPMI network layer 3 routing of the bare metal server; the management network vlan1 of the edge bare metal management module is interconnected with the management network vlan3 of the bare metal server; the edge bare metal management module and the edge cloud console communicate through the management network vlan2.

[0064] In the embodiment of the present application, the edge bare metal management module can be deployed in each edge cloud node among the multiple edge cloud nodes, or the edge bare metal management module can be deployed in some nodes among the multiple edge cloud nodes. It can be understood that the more the number of edge bare metal management modules, the more copies of the bare metal server, and the more reliable the system. The bare metal server management method provided in the embodiment of the present application, CMetal, in conjunction with the edge cloud console, can support the management of 200 bare metal servers and batch operations of up to 40 bare metal servers at a time with only three edge cloud nodes. The edge cloud console provides double protection. The first level of protection is the mutually exclusive Watch mechanism in the edge cloud scenario; the second level of protection is the optimization of the edge cloud console for Ironic's concurrent processing of a large number of bare metal servers, which can be operated in batches in the console and call the underlying CMetal for processing. The edge cloud node can effectively monitor the status of the bare metal server, and the network planning takes into account the edge cloud scenario. When the edge cloud node is expanded, the number of bare metal servers connected to the management can be linearly increased without a significant performance degradation.

[0065] The present application embodiment also provides a bare metal server management device 400, referring to Figure 4 , Figure 4 This is a structural diagram of a bare metal server management device 400 provided in an embodiment of the present application. The bare metal server management device 400 in this embodiment 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 BMO component and a BMCO component; the BMCO component includes 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 corresponding bare metal server management tasks based on the instructions of the BMO component; the bare metal server management device 400 includes: 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 placed in a thread pool; Processing unit: used to extract multiple operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

[0066] In an embodiment of the present application, the processing unit is used to monitor the resource status of the bare metal server through the edge cloud console; if the resource status of the bare metal server is monitored to change, a corresponding processing event is triggered.

[0067] In an embodiment of the present application, the processing unit is used to extract a preset number of identical 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.

[0068] In an embodiment of the present application, the value of the preset number is related to a first parameter; the first parameter includes: the number of edge cloud nodes, the number of CPU cores of the edge cloud node, and the amount of memory of the edge cloud node.

[0069] In an embodiment of the present application, the edge bare metal management module also includes: a Dnsmasq-Operator component; the processing unit: used to provide Dynamic Host Configuration Protocol DHCP capabilities 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 communication addresses.

[0070] In an embodiment of the present application, the processing unit is configured to obtain hardware monitoring data information of the bare metal server based on the intelligent platform management interface IPMI protocol through the edge bare metal management module.

[0071] In an embodiment of the present application, the management network vlan1 of the edge bare metal management module is interconnected with the IPMI network layer 3 routing of the bare metal server; the management network vlan1 of the edge bare metal management module is interconnected with the management network vlan3 of the bare metal server; the edge bare metal management module and the edge cloud console communicate through the management network vlan2.

[0072] Those skilled in the art should understand that Figure 4 The implementation functions of each unit in the bare metal server management device 400 shown can be understood by referring to the relevant description of the aforementioned method. Figure 4 The functions of each unit in the bare metal server management device 400 shown can be implemented by a program running on a processor or by a specific logic circuit.

[0073] Figure 5 It 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 an embodiment of the present application.

[0074] Alternatively, as Figure 5 As shown, the electronic device 500 may further include a first memory 520. The first processor 510 may call and run a computer program from the first memory 520 to implement the bare metal server management method provided in the embodiment of the present application.

[0075] The first memory 520 may be a separate device independent of the first processor 510 , or may be integrated into the first processor 510 .

[0076] Alternatively, as Figure 5 As shown, the electronic device 500 may further include a transceiver 530. The first processor 510 may control the transceiver 530 to perform bare metal management with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0077] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0078] The electronic device 500 can specifically be the bare metal server management device 400 / edge cloud node of the embodiment of the present application, and the electronic device 500 can implement the corresponding processes implemented by the bare metal server management device 400 / edge cloud node in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0079] Illustratively, an embodiment of the present application further provides 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 aforementioned methods.

[0080] Figure 6 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 6 The chip 600 shown includes a second processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0081] Alternatively, as Figure 6 As shown, the chip 600 may further include a second memory 620. The second processor 610 may call and execute a computer program from the second memory 620 to implement the method in the embodiment of the present application.

[0082] The second memory 620 may be a separate device independent of the second processor 610 , or may be integrated into the second processor 610 .

[0083] Optionally, the chip 600 may further include an input interface 630. The second processor 610 may control the input interface 630 to perform bare metal management with other devices or chips, specifically, to obtain information or data sent by other devices or chips.

[0084] Optionally, the chip 600 may further include an output interface 640. The second processor 610 may control the output interface 640 to perform bare metal management with other devices or chips, specifically, to output information or data to other devices or chips.

[0085] The chip can be applied to the electronic device 500 in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the electronic device 500 in the various methods of the embodiment of the present application. For the sake of brevity, they will not be described here.

[0086] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0087] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above-described method embodiments may be completed by hardware integrated logic circuits in the processor or by software instructions. The above-described processor may 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. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software units in the decoding processor. The software units may be located in a storage medium known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in a memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above-described method.

[0088] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0089] It should be understood that the above-mentioned memories are exemplary and not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0090] The present invention also provides a storage medium for storing a computer program. The storage medium can be applied to the electronic device 500 in the present invention, and the computer program causes a computer to execute the corresponding processes implemented by the electronic device 500 in the various methods of the present invention. For the sake of brevity, the details are not repeated here.

[0091] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0092] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0093] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0094] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0095] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0096] If the functions are implemented in the form of 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 the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling 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 method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0097] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. A bare metal server management method, characterized in that: Applied to edge cloud nodes, the edge cloud nodes are deployed with an edge cloud console and an edge bare metal management module; wherein 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 a bare metal server through a bare metal host BareMetalHost custom resource CRD; the Ironic component is used to execute corresponding bare metal server management tasks based on instructions from the BMO component; the method includes: receiving an operation task through the edge cloud console; the operation task is an operation task for a bare metal server, and placing the operation task into a thread pool; The edge cloud console extracts multiple operation tasks from the thread pool and calls the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

2. The method according to claim 1, characterized in that Also includes: Monitoring the resource status of the bare metal server through the edge cloud console; If the resource status of the bare metal server is monitored to change, a corresponding processing event is triggered.

3. The method according to claim 2, characterized in that Also includes: For multiple identical operation tasks for different bare metal servers in the thread pool, a preset number of the identical operation tasks are extracted from the thread pool, and the edge bare metal management module is called to perform batch processing.

4. The method according to claim 3, characterized in that The value of the preset number is related to the first parameter; the first parameter includes: The number of edge cloud nodes, the number of CPU cores of the edge cloud nodes, and the amount of memory of the edge cloud nodes.

5. The method according to claim 4, characterized in that The edge bare metal management module further includes: a Dnsmasq-Operator component; the method further includes: The Dnsmasq-Operator component provides the bare metal server with Dynamic Host Configuration Protocol (DHCP) capability; and the Dnsmasq-Operator component sets a whitelist to prevent non-bare metal servers from obtaining communication addresses.

6. The method according to claim 5, characterized in that The method further comprises: The edge bare metal management module obtains hardware monitoring data information of the bare metal server based on the intelligent platform management interface IPMI protocol.

7. The method according to any one of claims 1 to 6, characterized in that The management network vlan1 of the edge bare metal management module is interconnected with the IPMI network layer 3 routing of the bare metal server; the management network vlan1 of the edge bare metal management module is interconnected with the management network vlan3 of the bare metal server; the edge bare metal management module and the edge cloud console communicate through the management network vlan2.

8. A bare metal server management device, characterized in that: Applied to edge cloud nodes, the edge cloud nodes are deployed with an edge cloud console and an edge bare metal management module; wherein the edge bare metal management module includes: a BMO component and a BMCO component; the BMCO component includes an Ironic component; the BMO component is used to abstract a bare metal server through a BareMetalHost CRD; the Ironic component is used to execute corresponding bare metal server management tasks based on the instructions of the BMO component; the device includes: 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 placed in a thread pool; Processing unit: used to extract multiple operation tasks from the thread pool through the edge cloud console and call the edge bare metal management module to concurrently process the multiple operation tasks; wherein, the multiple operation tasks are operation tasks for different bare metal servers, and the operation tasks for the same bare metal server are processed with a single thread.

9. An electronic device, characterized in that: include: A first processor and a first memory, the first memory is used to store a computer program, the first processor is used 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 in that: Used to store a computer program, wherein the computer program 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 When the computer program is executed by a processor, the computer program implements the bare metal server management method according to any one of claims 1 to 7.

Images