Bare metal management method and device, server and readable storage medium

Abstract

The invention relates to a bare metal management method and device, a server and a readable storage medium, the method is applied to a management server in a cloud desktop system, the cloud desktop system further comprises a plurality of bare metal servers, and the method comprises the steps of obtaining information of the plurality of bare metal servers; under the condition that it is determined that the bare metal servers which do not support the out-of-band network exist in the multiple bare metal servers according to the information, the bare metal servers which do not support the out-of-band network are selected from the multiple bare metal servers, and a first server set is obtained; and deploying a KVM virtual machine for the bare metal server in the first server set. By adopting the method, the bare metal server can be managed through the virtual machine.

Description

Technical Field

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

[0002] Bare metal servers are widely used in cloud desktop systems due to their advantages of physical machine security, high performance, and multi-format computing resources. Openstack Ironic is a service component for managing and deploying bare metal servers in an Openstack environment. It can provide users with more flexible and diverse cloud computing service options in cloud desktop systems by providing bare metal management and deployment functions. Openstack Ironic requires that the bare metal server be equipped with hardware devices that support out-of-band networks. If the bare metal server is not equipped with hardware devices that support out-of-band networks, the bare metal server cannot be managed. Summary of the invention

[0003] Based on this, it is necessary to provide a bare metal management method, device, server and readable storage medium that can manage bare metal servers through virtual machines to address the above technical problems.

[0004] In a first aspect, the present application provides a bare metal management method, which is applied to a management server in a cloud desktop system, wherein the cloud desktop system further includes a plurality of bare metal servers, and the method includes:

[0005] Obtain information about the multiple bare metal servers;

[0006] When it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, selecting the bare metal server that does not support an out-of-band network from the multiple bare metal servers to obtain a first server set;

[0007] Deploy a KVM virtual machine on the bare metal server in the first server set.

[0008] In one embodiment, deploying a KVM virtual machine on a bare metal server in the first server set includes:

[0009] A KVM deployment instruction is sent to a first bare metal server to configure a KVM network for the first bare metal server, KVM resources are determined according to resources of the first bare metal server, and a KVM virtual machine is deployed according to the KVM network and the KVM resources. The first bare metal server is any bare metal server in the first server set.

[0010] In one embodiment, the method further comprises:

[0011] Sending an authentication request to the first bare metal server;

[0012] Receive authentication success information from the first bare metal server.

[0013] In one embodiment, sending the authentication request to the first bare metal server includes:

[0014] Sending an authentication request to the first bare metal server according to SSH or SASL;

[0015] Libvirtd is deployed on the first bare metal server, and the authentication pass information is generated by the first bare metal server after the Libvirtd successfully authenticates the management server.

[0016] In one of the embodiments, the management server is deployed with a plurality of VPCE components, the plurality of VPCE components correspond one-to-one to the plurality of bare metal servers, and the method further includes:

[0017] The first VPCE component is called to obtain status data of a second bare metal server, where the second bare metal server is any bare metal server among the multiple bare metal servers, and the first VPCE component is a VPCE component corresponding to the second bare metal server among the multiple VPCE components.

[0018] In one embodiment, the bare metal server is deployed with Exporter, and the management server is deployed with Prometheus;

[0019] Calling the first VPCE component to obtain the status data of the second bare metal server includes:

[0020] The first VPCE component is called to obtain the status data of the second bare metal server in a pull manner through the Prometheus, where the status data of the second bare metal server is obtained by the Exporter in the second bare metal server monitoring the status of the second bare metal server.

[0021] In one embodiment, the method further comprises:

[0022] Selecting a bare metal server that supports an out-of-band network from the plurality of bare metal servers to obtain a second server set;

[0023] An operating system is installed on the bare metal servers in the second server set.

[0024] In a second aspect, the present application further provides a bare metal management device, which is applied to a management server in a cloud desktop system, wherein the cloud desktop system further includes a plurality of bare metal servers, and the device includes:

[0025] An acquiring unit, configured to acquire information of the plurality of bare metal servers;

[0026] a selection unit, configured to select, when it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, the bare metal server that does not support an out-of-band network from the multiple bare metal servers to obtain a first server set;

[0027] A deployment unit is used to deploy a KVM virtual machine on the bare metal server in the first server set.

[0028] In a third aspect, the present application further provides a server, the server being a management server in a cloud desktop system, the cloud desktop system further comprising a plurality of bare metal servers, the server comprising a memory, a transceiver and a processor:

[0029] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0030] Obtain information about the multiple bare metal servers;

[0031] When it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, a bare metal server that does not support an out-of-band network is selected from the multiple bare metal servers to obtain a first server set;

[0032] Deploy a KVM virtual machine on the bare metal server in the first server set.

[0033] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0034] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0035] In an embodiment of the present application, the cloud desktop system includes a management server and multiple bare metal servers. The management server obtains information of the multiple bare metal servers. When it is determined that there are bare metal servers that do not support out-of-band networks among the multiple bare metal servers based on the information of the multiple bare metal servers, the bare metal servers that do not support out-of-band networks are selected from the multiple bare metal servers to obtain a first server set, and KVM virtual machines are deployed on the bare metal servers in the first server set. It can be seen that when the bare metal server does not support out-of-band networks, the management server can deploy KVM virtual machines for the bare metal servers, so that the bare metal servers can be managed by managing virtual machines. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0037] Figure 1 It is a structural diagram of a network architecture provided by an embodiment of the present application;

[0038] Figure 2 It is a flowchart of a bare metal management method provided in an embodiment of the present application;

[0039] Figure 3 It is a flowchart of another bare metal management method provided in an embodiment of the present application;

[0040] Figure 4 It is a schematic diagram of a system architecture of a management server provided in an embodiment of the present application;

[0041] Figure 5 It is a schematic diagram of a KVM deployment provided in an embodiment of the present application;

[0042] Figure 6 It is a schematic diagram of an installation provided by an embodiment of the present application;

[0043] Figure 7 is a schematic diagram of state data acquisition provided by an embodiment of the present application;

[0044] Figure 8 It is a structural schematic diagram of a bare metal management device provided in an embodiment of the present application;

[0045] Fig. 9 It is a structural diagram of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0047] In order to better understand the embodiments of the present application, the relevant technologies are first introduced below.

[0048] In cloud desktop systems, containers and virtual machines are widely used. In addition, bare metal servers are also widely used in cloud desktop systems due to their security, high performance, and multi-format computing resources (virtual machines and physical machines). Bare metal servers are mainly used in high-performance computing scenarios, which have certain requirements for networks and storage. In the current privatization scenario, old equipment needs to be used, and old equipment may not have hardware devices that support out-of-band networks.

[0049] Openstack Ironic is a service component for managing and deploying bare metal in an Openstack environment. It can provide users with more flexible and diverse cloud computing service options in the cloud desktop system by providing bare metal management and deployment functions. Openstack Ironic requires the bare metal server to be equipped with hardware devices that support out-of-band networks. Therefore, if the bare metal server is not equipped with hardware devices that support out-of-band networks, the bare metal server cannot be managed.

[0050] In addition, the management server that manages the bare metal server can only monitor various data of the bare metal server through the Intelligent Platform Management Interface (IPMI), so the data obtained is relatively limited, and the data obtained is basically binary data of normal or abnormal, and has no time series.

[0051] In order to solve the above technical problems, when the bare metal server does not support out-of-band network, the management server can deploy a keyboard video mouse (KVM) virtual machine for the bare metal server, so that the bare metal server can be managed by managing the virtual machine.

[0052] In order to better understand the embodiments of the present application, the network architecture of the present application is first introduced below.

[0053] Figure 1 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 1 As shown, the network architecture may include multiple clients 101 , a management server 102 , and multiple bare metal servers 103 .

[0054] The multiple clients 101 correspond to the multiple bare metal servers 103 one by one, that is, each bare metal server 103 corresponds to a unique client 101. The client 101 and the bare metal server 103 are connected via a network. The network can be a local area network or a wide area network.

[0055] The management server 102 and the bare metal server 103 are connected via a network, which may be a local area network or a wide area network.

[0056] The management server 102 is used to manage multiple bare metal servers 103, such as power-on management, power-off management, restart management, password reset management, network management, etc. Network management can include business network management, storage network management, intelligent computing network management, network tenant management, etc. The intelligent computing network can be an IB network (InfiniBand network) or other intelligent computing networks.

[0057] Client 101 is the client of bare metal server 103, which is used to provide a bridge for interaction between users and bare metal server 103. It can receive user operations, respond to user operations, send operation instructions to bare metal server 103, and receive data from bare metal server 103 and display these data.

[0058] A bare metal server is an independent physical server. A management server can be an independent physical server or a cloud server with data processing and communication functions.

[0059] It should be understood that Figure 1 This is an exemplary description of the network architecture of the present application and does not limit the network architecture of the present application.

[0060] Based on the above network architecture, Figure 2 1 is a flow chart of a bare metal management method provided in an embodiment of the present application. The bare metal management method is described from the perspective of managing servers in a cloud desktop system. The cloud desktop system may also include multiple bare metal servers. Figure 2 As shown, the bare metal management method may include the following steps.

[0061] 201. Obtain information of multiple bare metal servers.

[0062] When deploying the cloud desktop system, the management server can obtain information of multiple bare metal servers under management. The management server can obtain corresponding information from multiple bare metal servers. The information of the bare metal servers may include one or more of the hardware information, software information, etc. of the bare metal servers.

[0063] It should be understood that the environment used by the management server is not the Openstack environment.

[0064] 202. According to the information of the plurality of bare metal servers, determine whether there is a bare metal server that does not support the out-of-band network among the plurality of bare metal servers. If there is a bare metal server that does not support the out-of-band network among the plurality of bare metal servers, execute step 203.

[0065] After the management server obtains the information of multiple bare metal servers, it can determine whether there are any bare metal servers that do not support the out-of-band network among the multiple bare metal servers based on the information of the multiple bare metal servers. If it is determined that there are any bare metal servers that do not support the out-of-band network among the multiple bare metal servers, it indicates that there are any bare metal servers among the multiple bare metal servers that cannot be managed through the out-of-band network, and step 203 can be executed.

[0066] In some embodiments, the bare metal server information may include hardware information of the bare metal server. The hardware information of the bare metal server is information about the hardware of the bare metal server.

[0067] The management server can determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers based on the hardware information of the multiple bare metal servers, that is, determine whether there is a bare metal server that does not include hardware information that supports the out-of-band network among the multiple bare metal servers. If it is determined that there is a bare metal server that does not include hardware information that supports the out-of-band network among the multiple bare metal servers, it can be determined that there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers. The hardware information that supports the out-of-band network is information about hardware used for the out-of-band network.

[0068] In some embodiments, the bare metal server information may include software information of the bare metal server. The software information of the bare metal server is information about software installed or deployed in the bare metal server.

[0069] The management server can determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers based on the software information of the multiple bare metal servers, that is, determine whether there is a bare metal server that does not include software information associated with the out-of-band network among the multiple bare metal servers. If it is determined that there is a bare metal server that does not include software information associated with the out-of-band network among the multiple bare metal servers, it can be determined that there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers.

[0070] The software information associated with the out-of-band network may be information about software installed on hardware used for the out-of-band network. Exemplarily, the software information associated with the out-of-band network may be information about a baseboard management controller (BMC) installed on hardware used for the out-of-band network.

[0071] The software information associated with the out-of-band network may also be interface information associated with hardware used for the out-of-band network. Exemplarily, the software information associated with the out-of-band network may be IPMI information.

[0072] 203. Select a bare metal server that does not support an out-of-band network from multiple bare metal servers to obtain a first server set.

[0073] When there is a bare metal server that does not support out-of-band network among the multiple bare metal servers, the management server can select all bare metal servers that do not support out-of-band network from the multiple bare metal servers according to information of the multiple bare metal servers to obtain a first server set. The first server set may include one bare metal server or multiple bare metal servers.

[0074] 204. Deploy a KVM virtual machine on the bare metal server in the first server set.

[0075] The management server can deploy KVM virtual machines to the bare metal servers in the first server set. The management server can deploy KVM virtual machines to the bare metal servers in the first server set at the same time, or can deploy KVM virtual machines to the bare metal servers in the first server set one by one in sequence.

[0076] exist Figure 2 In the bare metal management method shown, the management server obtains information of multiple bare metal servers, and when it is determined based on the information of the multiple bare metal servers that there are bare metal servers that do not support out-of-band networks, the management server selects bare metal servers that do not support out-of-band networks from the multiple bare metal servers to obtain a first server set, and deploys KVM virtual machines on the bare metal servers in the first server set. It can be seen that when the bare metal server does not support out-of-band networks, the management server can deploy KVM virtual machines for the bare metal servers, so that the bare metal servers can be managed by managing virtual machines.

[0077] Based on the above network architecture, Figure 3 1 is a flow chart of another bare metal management method provided by an embodiment of the present application. The bare metal management method is described from the perspective of managing servers in a cloud desktop system. The cloud desktop system may also include multiple bare metal servers. Figure 3As shown, the bare metal management method may include the following steps.

[0078] 301. Obtain information of multiple bare metal servers.

[0079] The detailed description of step 301 may refer to the description of step 201 .

[0080] Figure 4 Schematic diagram of the system architecture of a management server provided in an embodiment of the present application. Figure 4 As shown, the management server is deployed with a service component, and the management server can call the service component to obtain information of multiple bare metal servers. The service component can be deployed through a container or other methods.

[0081] 302. Based on the information of multiple bare metal servers, determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers. If there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers, execute step 303; if there is no bare metal server that does not support the out-of-band network among the multiple bare metal servers, execute step 307.

[0082] After the management server obtains the information of the multiple bare metal servers, it can determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers based on the information of the multiple bare metal servers. If it is determined that there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers, it indicates that there is a bare metal server that cannot be managed through the out-of-band network among the multiple bare metal servers, and step 303 can be executed. If there is no bare metal server that does not support the out-of-band network among the multiple bare metal servers, that is, if the multiple bare metal servers all support the out-of-band network, step 307 can be executed.

[0083] In some embodiments, the information of the bare metal server may include the hardware information of the bare metal server. The management server may determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers based on the hardware information of the multiple bare metal servers, that is, determine whether there is a bare metal server that does not include hardware information that supports the out-of-band network among the multiple bare metal servers. If it is determined that there is a bare metal server that does not include hardware information that supports the out-of-band network among the multiple bare metal servers, it can be determined that there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers. If it is determined that there is no bare metal server that does not include hardware information that supports the out-of-band network among the multiple bare metal servers, it can be determined that there is no bare metal server that does not support the out-of-band network among the multiple bare metal servers.

[0084] In some embodiments, the information of the bare metal server may include software information of the bare metal server. The management server may determine whether there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers based on the software information of the multiple bare metal servers, that is, determine whether there is a bare metal server that does not include software information associated with the out-of-band network among the multiple bare metal servers. If it is determined that there is a bare metal server that does not include software information associated with the out-of-band network among the multiple bare metal servers, it can be determined that there is a bare metal server that does not support the out-of-band network among the multiple bare metal servers. If it is determined that there is no bare metal server that does not include software information associated with the out-of-band network among the multiple bare metal servers, it can be determined that there is no bare metal server that does not support the out-of-band network among the multiple bare metal servers.

[0085] For a detailed description of other information in step 302 , please refer to the relevant description below step 202 .

[0086] 303. Select a bare metal server that does not support an out-of-band network from multiple bare metal servers to obtain a first server set.

[0087] 304. Select a bare metal server that supports an out-of-band network from the plurality of bare metal servers to obtain a second server set.

[0088] In the case that there are bare metal servers that do not support out-of-band networks among multiple bare metal servers, the management server can directly select bare metal servers that do not support out-of-band networks from the multiple bare metal servers based on information of the multiple bare metal servers to obtain a first server set, and select bare metal servers that support out-of-band networks from the multiple bare metal servers to obtain a second server set.

[0089] If there is a bare metal server that does not support out-of-band network among the multiple bare metal servers, the management server may continue to determine whether there is a bare metal server that supports out-of-band network among the multiple bare metal servers, and if there is a bare metal server that supports out-of-band network among the multiple bare metal servers, steps 303 and 304 may be performed. If there is no bare metal server that supports out-of-band network among the multiple bare metal servers, the management server may deploy KVM virtual machines to the multiple bare metal servers, and a detailed description may refer to the description of step 305.

[0090] The management server can first establish a first server set and a second server set, and then determine one by one whether the multiple bare metal servers support the out-of-band network based on the information of the multiple bare metal servers. When it is determined that a bare metal server does not support the out-of-band network, the bare metal server can be classified into the first server set. When it is determined that a bare metal server supports the out-of-band network, the bare metal server can be classified into the second server set until all bare metal servers are classified.

[0091] The management server can also determine one by one whether each bare metal server in the multiple bare metal servers supports the out-of-band network based on the information of the multiple bare metal servers. When it is determined that a bare metal server does not support the out-of-band network, the bare metal server can be selected from the multiple bare metal servers until all the bare metal servers are selected. After that, the bare metal servers selected from the multiple bare metal servers can be determined as the first server set, and the bare metal servers not selected from the multiple bare metal servers, that is, the remaining bare metal servers, can be determined as the second server set.

[0092] 305. Deploy a KVM virtual machine on the bare metal server in the first server set.

[0093] After the management server obtains the first server set, it can deploy KVM virtual machines to the bare metal servers in the first server set. The management server can deploy KVM virtual machines to the bare metal servers in the first server set at the same time, or deploy KVM virtual machines to the bare metal servers in the first server set one by one in sequence.

[0094] The management server may send a KVM deployment instruction to the first bare metal server. The management server may send a KVM deployment instruction to the first bare metal server in a scripted manner. The management server may send a KVM deployment instruction to the first bare metal server through an Ansible script, or may send a KVM deployment instruction to the first bare metal server through other scripts. The first bare metal server is any bare metal server in the first server set.

[0095] Accordingly, the first bare metal server can receive the KVM deployment instruction from the management server, and then in response to the KVM deployment instruction, can configure the KVM network, can determine the KVM resources based on the resources of the first bare metal server, and can deploy the KVM virtual machine based on the KVM network and KVM resources.

[0096] The first bare metal server can first obtain the resources of the first bare metal server (i.e., total resources), and can determine the reserved resources based on the resources of the first bare metal server, and can determine the KVM resources based on the resources of the first bare metal server and the reserved resources, that is, the difference between the resources of the first bare metal server and the reserved resources can be determined as the KVM resources. The reserved resources are resources reserved for the operating system of the first bare metal server, that is, resources used for the operating system of the first bare metal server. The KVM resources are resources of the KVM virtual machine, that is, resources used for the KVM virtual machine.

[0097] Resources may include computing resources (i.e., processing resources), storage resources, etc. Computing resources may be central processing units (CPUs), graphics processing units (GPUs), etc. Storage resources may be memory, cache, etc.

[0098] In some embodiments, the management server may send an authentication request to the first bare metal server and may receive authentication pass information from the first bare metal server.

[0099] Libvirtd is deployed in the first bare metal server. After obtaining the first server set, the management server can initialize Libvirtd in the first bare metal server, that is, initialize the environment of Libvirtd in the first bare metal server, and then send an authentication request to the first bare metal server. The management server can send the authentication request to the first bare metal server according to the Secure Shell (SSH) protocol or the Simple Authentication and Security Layer (SASL) protocol.

[0100] Accordingly, the first bare metal server receives an authentication request from the management server, and then responds to the authentication request, can authenticate the management server through Libvirtd, and if the authentication is successful, can generate authentication success information, and then can send the authentication success information to the management server.

[0101] Accordingly, the management server can receive authentication pass information from the first bare metal server, and then deploy a KVM virtual machine to the bare metal server in the first server set.

[0102] It can be seen that when the management server performs authentication, Libvirt authentication is performed through SSH or SASL, which can avoid exposing the Libvirt port to the outside world, thereby improving security and not adding additional authentication management work.

[0103] like Figure 4 As shown, the management server may also be deployed with a KVM deployment component. The management server may call the KVM deployment component to deploy a KVM virtual machine to the bare metal server in the first server set. The KVM deployment component may be deployed through a container or in other ways.

[0104] For example, Figure 5 Schematic diagram of a KVM deployment provided by an embodiment of the present application. Figure 5 As shown, after the user initiates the KVM deployment service, the service component can respond to the KVM deployment service, and then call the KVM deployment component to send an authentication request to the bare metal server according to the SSH protocol. The bare metal server authenticates the management server through Libvirtd, and if the authentication is successful, it can send an authentication pass message to the management server. After the management server receives the authentication pass message, it can call the KVM component to send a KVM deployment instruction to the bare metal server through the Ansible script. The bare metal server can deploy a KVM virtual machine according to the KVM deployment instruction, so that KVM CPU direct access can be achieved between the management server and the bare metal server.

[0105] Through the KVM virtual machine, direct communication between the KVM CPU of the management server and the bare metal server can be achieved, and fewer CPU resources are required, which can improve resource utilization.

[0106] In order to ensure the normal operation of the bare metal servers in the first server set, it is necessary to install an operating system offline on each bare metal server in the first server set.

[0107] 306. Install an operating system on the bare metal server in the second server set.

[0108] After the management server obtains the second server set, it can install the operating system on the bare metal servers in the second server set. The management server can install the operating system for the bare metal servers in the second server set at the same time, or deploy KVM virtual machines for the bare metal servers in the second server set one by one in sequence.

[0109] The management server may simultaneously (ie, in parallel) install the operating system for the bare metal servers in the second server set through a preboot execution environment (PXE), or may install the operating system for the bare metal servers in the second server set through other methods.

[0110] like Figure 4As shown, the management server can also be deployed with an installation component. The management server can call the installation component to install the operating system on the bare metal server in the second server set. Since the IPMI installation is managed by a separate installation component, it can be responsible for the asynchronous management of the installation task, thereby achieving decoupling between services. The installation component can be deployed through a container or in other ways.

[0111] For example, Figure 6 Schematic diagram of a machine provided in an embodiment of the present application. Figure 6 As shown, after the user initiates the installation service, the service component can respond to the installation service, and then call the installation component to remotely install the operating system in batches on the bare metal servers in the second server set.

[0112] 307. Install operating systems on multiple bare metal servers.

[0113] When there is no bare metal server that does not support out-of-band network among the multiple bare metal servers, that is, when the multiple bare metal servers all support out-of-band network, the management server can install operating systems on the multiple bare metal servers. For detailed description, please refer to the description of step 306.

[0114] 308. Call the first VPCE component to obtain status data of the second bare metal server.

[0115] like Figure 4 As shown, the management server can also be deployed with multiple Virtual Private Cloud (VPC) endpoint (VPC Endpoint, VPCE) components. The multiple VPCE components correspond to the multiple bare metal servers one by one. It can be seen that the management server can be deployed with a VPCE component for each of the multiple bare metal servers.

[0116] After executing the above steps and deploying multiple VPCE components for multiple bare metal servers, the management server can call the first VPCE component to obtain the status data of the second bare metal server. The second bare metal server is any bare metal server among the multiple bare metal servers. The first VPCE component is the VPCE component corresponding to the second bare metal server among the multiple VPCE components. The status data of the bare metal server may include the running status data, hardware status data, network status data and other status data of the bare metal server.

[0117] The bare metal server is deployed with Exporter, and the management server is deployed with Prometheus. Exporter can be pre-installed in the operating system image. Therefore, when the operating system is installed for the bare metal server, Exporter will be deployed for the bare metal server. After the bare metal server operating system is successfully installed, Exporter can automatically monitor the status of the bare metal server, obtain the status data of the bare metal server and store it. The management server can periodically or when needed call the first VPCE component to obtain the status data of the second bare metal server through Prometheus in a pull manner.

[0118] For example, Figure 7 Schematic diagram of a state data acquisition provided by an embodiment of the present application. Figure 7 As shown in the figure, the management server can call the VPCE component to pull the status data monitored by the Exporter in the bare metal server through Prometheus.

[0119] The management server can also call service components to remotely manage multiple bare metal servers and / or KVM virtual machines and perform network management. Remote management can include switch management, shutdown management, restart management, password reset management, etc. Network management can include business network management, storage network management, intelligent computing network management, network tenant management, etc.

[0120] exist Figure 3 In the bare metal management method shown, when the bare metal server does not support out-of-band network, the management server can deploy KVM virtual machines for the bare metal server, so that the bare metal server can be managed by managing virtual machines, which can improve the utilization rate of old bare metal servers, thereby improving resource utilization. In addition, the management server can remotely batch install bare metal servers that support out-of-band network, which can improve installation efficiency. Furthermore, since different VPCE components are deployed for different bare metal servers, so that the management server can call different VPCE components to obtain status data of different bare metal servers, the isolation of different bare metal servers can be guaranteed, and since the second-layer network is connected, the diversity of the obtained data can be improved. Furthermore, the management server is responsible for the management of the bare metal server, and the user does not need to care about the implementation of the bare metal server, which can improve the user experience.

[0121] It should be understood that the same or corresponding contents in different embodiments may be referenced to each other.

[0122] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0123] Based on the same inventive concept, the embodiment of the present application also provides a bare metal management device for implementing the bare metal management method involved above. The implementation solution provided by the bare metal management device to solve the problem is similar to the implementation solution recorded in the above bare metal management method, so the specific limitations in one or more bare metal management device embodiments provided below can refer to the limitations of the bare metal management method above, and will not be repeated here.

[0124] Based on the above network architecture, Figure 8 1 is a schematic diagram of the structure of a bare metal management device provided in an embodiment of the present application. The bare metal management device can be applied to a management server in a cloud desktop system, and the cloud desktop system can also include multiple bare metal servers. The bare metal management device may include:

[0125] An acquisition unit 801 is used to acquire information of multiple bare metal servers;

[0126] A selection unit 802 is configured to select a bare metal server that does not support an out-of-band network from the multiple bare metal servers to obtain a first server set when it is determined according to information of the multiple bare metal servers that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers.

[0127] The deployment unit 803 is used to deploy a KVM virtual machine on the bare metal server in the first server set.

[0128] In some embodiments, the deployment unit 803 is specifically used to send a KVM deployment instruction to the first bare metal server so that the first bare metal server configures the KVM network, determines the KVM resources according to the resources of the first bare metal server, and deploys the KVM virtual machine according to the KVM network and KVM resources. The first bare metal server is any bare metal server in the first server set.

[0129] In some embodiments, the bare metal management device may further include:

[0130] A communication unit, configured to send an authentication request to the first bare metal server;

[0131] The communication unit is also used to receive authentication pass information from the first bare metal server.

[0132] In some embodiments, the communication unit sending the authentication request to the first bare metal server includes:

[0133] Send an authentication request to the first bare metal server according to SSH or SASL;

[0134] Libvirtd is deployed on the first bare metal server, and authentication pass information is generated by the first bare metal server after Libvirtd authenticates the management server.

[0135] In some embodiments, the management server is deployed with multiple VPCE components, and the multiple VPCE components correspond to multiple bare metal servers one by one. The bare metal management device may also include:

[0136] The calling unit is used to call the first VPCE component to obtain status data of a second bare metal server, where the second bare metal server is any bare metal server among multiple bare metal servers, and the first VPCE component is a VPCE component corresponding to the second bare metal server among the multiple VPCE components.

[0137] In some embodiments, the bare metal server is deployed with Exporter and the management server is deployed with Prometheus;

[0138] The calling unit is specifically used to call the first VPCE component to obtain the status data of the second bare metal server in a pull manner through Prometheus. The status data of the second bare metal server is obtained by the Exporter in the second bare metal server monitoring the status of the second bare metal server.

[0139] In some embodiments, the selection unit 802 is further configured to select a bare metal server supporting an out-of-band network from the plurality of bare metal servers to obtain a second server set;

[0140] The bare metal management device may further include:

[0141] The installation unit is used to install an operating system on the bare metal server in the second server set.

[0142] Each unit in the above bare metal management device can be implemented in whole or in part by software, hardware, or a combination thereof. Each unit can be embedded in or independent of a processor in a server in the form of hardware, or can be stored in a memory in a server in the form of software, so that the processor can call and execute operations corresponding to each unit above.

[0143] Based on the above network architecture, Fig. 9 : This is a structural diagram of a server provided in an embodiment of the present application. The server may include a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the server is used to provide computing and control capabilities. The memory of the server includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the server is used to store the corresponding relationship between multiple clients and multiple processing devices, etc. The input / output interface of the server is used to exchange information between the processor and an external device. The communication interface of the server is used to communicate with an external client through a network connection. When the computer program is executed by the processor, a bare metal management method is implemented.

[0144] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. The specific server may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0145] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned bare metal management method are implemented.

[0146] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0147] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0148] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A bare metal management method, characterized in that: A management server applied to a cloud desktop system, wherein the cloud desktop system further comprises a plurality of bare metal servers, and the method comprises: Obtain information about the multiple bare metal servers; When it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, a bare metal server that does not support an out-of-band network is selected from the multiple bare metal servers to obtain a first server set; Deploy a KVM virtual machine on the bare metal server in the first server set.

2. The method according to claim 1, characterized in that The deploying a KVM virtual machine on the bare metal server in the first server set includes: A KVM deployment instruction is sent to a first bare metal server to configure a KVM network for the first bare metal server, KVM resources are determined according to resources of the first bare metal server, and a KVM virtual machine is deployed according to the KVM network and the KVM resources. The first bare metal server is any bare metal server in the first server set.

3. The method according to claim 2, characterized in that The method further comprises: Sending an authentication request to the first bare metal server; Receive authentication success information from the first bare metal server.

4. The method according to claim 3, characterized in that The sending an authentication request to the first bare metal server includes: Sending an authentication request to the first bare metal server according to SSH or SASL; Libvirtd is deployed on the first bare metal server, and the authentication pass information is generated by the first bare metal server after the Libvirtd successfully authenticates the management server.

5. The method according to claim 1, characterized in that The management server is deployed with a plurality of VPCE components, and the plurality of VPCE components correspond one-to-one to the plurality of bare metal servers. The method further includes: The first VPCE component is called to obtain status data of a second bare metal server, where the second bare metal server is any bare metal server among the multiple bare metal servers, and the first VPCE component is a VPCE component corresponding to the second bare metal server among the multiple VPCE components.

6. The method according to claim 5, characterized in that The bare metal server is deployed with Exporter, and the management server is deployed with Prometheus; The calling of the first VPCE component to obtain the status data of the second bare metal server includes: The first VPCE component is called to obtain the status data of the second bare metal server in a pull manner through the Prometheus, where the status data of the second bare metal server is obtained by the Exporter in the second bare metal server monitoring the status of the second bare metal server.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Selecting a bare metal server that supports an out-of-band network from the plurality of bare metal servers to obtain a second server set; An operating system is installed on the bare metal servers in the second server set.

8. A bare metal management device, characterized in that: A management server applied to a cloud desktop system, wherein the cloud desktop system further comprises a plurality of bare metal servers, wherein the device comprises: An acquisition unit, configured to acquire information of the plurality of bare metal servers; a selection unit, configured to select, when it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, the bare metal server that does not support an out-of-band network from the multiple bare metal servers to obtain a first server set; A deployment unit is used to deploy a KVM virtual machine on the bare metal server in the first server set.

9. A server, characterized in that: The server is a management server in a cloud desktop system, and the cloud desktop system also includes multiple bare metal servers, and the server includes a memory, a transceiver, and a processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Obtain information about the multiple bare metal servers; When it is determined according to the information that there is a bare metal server that does not support an out-of-band network among the multiple bare metal servers, selecting the bare metal server that does not support an out-of-band network from the multiple bare metal servers to obtain a first server set; Deploy a KVM virtual machine on the bare metal server in the first server set.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images