A bare metal server deployment method and apparatus

Abstract

The application relates to the technical field of network communication, in particular to a bare metal server deployment method and device. The method is applied to a cloud platform control device, and the method comprises the following steps: obtaining hardware information and access position information of a target bare metal server, and storing the access position information into a database, wherein the access position information comprises management IP and port information of an access device where the target bare metal server is located; allocating the target bare metal server to a tenant, and creating corresponding provision network and tenant network; determining target management IP and target port information of a target access device where the target bare metal server accesses, and determining tenant network configuration corresponding to the tenant; notifying the target management IP, the target port information and the tenant network configuration to an SDN controller, so that the SDN controller determines a target port of the target access device, and issues the tenant network configuration to the target access device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network communication, and particularly relates to a bare metal server deployment method and device. BACKGROUND

[0002] A bare metal server (BMS) is a kind of physical server. Bare metal server deployment is divided into three stages, wherein, an inspection stage: after a bare metal server accesses a network, a PXE boot loads a start image, reports host information of the bare metal server to a management node, and makes the bare metal server enter a schedulable state. The inspector stage completes collection of hardware information of a physical server accessed by OpenStack, and the management node can create a corresponding "instance type" according to the collected configuration information, so as to facilitate scheduling of a specified physical server to create a bare metal instance according to resource requirements of a user application; a provision stage: a tenant applies for a bare metal resource to a cloud platform, the cloud platform starts a selected server, loads a start image through a PXE boot, and then deploys a system image to complete installation of an operating system of the bare metal server; and a running stage: the server restarts to load the operating system, acquires an IP address through a DHCP, and completes deployment of the bare metal instance.

[0003] When a bare metal server has passed the inspection stage, if a network element access device of the bare metal server is replaced by a new device due to a fault, a bridge MAC of the new device is different from a bridge MAC of the original fault device; then, the bare metal server cannot update host information of the bare metal server to the management node again; at this time, if the bare metal server is offline or online again, network configuration of the network element access device cannot be normally updated, because a controller cannot locate the new network element access device according to the original bridge MAC. SUMMARY

[0004] The present application provides a bare metal server deployment method and device.

[0005] In a first aspect, the present application provides a bare metal server deployment method applied to a cloud platform control device, and the method comprises the following steps.

[0006] Hardware information and access location information of a target bare metal server are acquired, and the acquired access location information is stored in a database, wherein the access location information of one bare metal server comprises management IP address and port information of an access device accessed by the bare metal server;

[0007] If the target bare metal server is allocated to a tenant based on a tenant request, a provision network and a tenant network corresponding to the target bare metal server are created.

[0008] determine a target management IP address and target port information of a target access device accessed by the target bare metal server, and determine a tenant network configuration corresponding to the tenant;

[0009] notify the target management IP address, the target port information and the tenant network configuration to an SDN controller, so that the SDN controller determines a target port of the target access device and issues the tenant network configuration to the target access device.

[0010] Optionally, the SDN controller configures a management IP address for an access device, manages the access device, and instructs the access device to carry the management IP address of the access device in an LLDP packet when the access device interacts with the bare metal server.

[0011] Optionally, after power-on startup, the target bare metal server acquires an initial image through an inspector network, wherein the initial image includes an agent program for collecting hardware information and access location information of the bare metal server; the target bare metal server runs the initial image, learns the bridge MAC, the management IP address and the port information of the target access device by interacting with the target access device through an LLDP packet.

[0012] The step of acquiring the hardware information and the access location information of the target bare metal server includes:

[0013] The agent program is used to acquire the hardware information of the target bare metal server and the bridge MAC, the management IP address and the port information of the target access device.

[0014] Optionally, if the target access device fails, the target access device is replaced by another access device, the physical connection of the replaced access device is consistent with that of the target access device, and the replaced access device inherits the management IP address of the target access device; the method further includes:

[0015] acquire the target management IP address and the target interface information of the target access device from a database, and notify the target management IP address, the target port information and the tenant network configuration to an SDN controller, so that the SDN controller determines a port of the replaced access device and issues the tenant network configuration to the replaced access device.

[0016] In a second aspect, the application provides a bare metal server deployment device applied to a cloud platform control device, the device comprising:

[0017] The acquisition unit is configured to acquire hardware information and access location information of a target bare metal server, and store the acquired access location information in a database, wherein the access location information of one bare metal server comprises management IP address and port information of an access device accessed by the bare metal server.

[0018] The creation unit is configured to, if the target bare metal server is allocated to a tenant based on a tenant request, create a provision network and a tenant network corresponding to the target bare metal server.

[0019] The determination unit is configured to determine target management IP address and target port information of a target access device accessed by the target bare metal server, and determine tenant network configuration corresponding to the tenant.

[0020] The notification unit is configured to notify the target management IP address, the target port information and the tenant network configuration to an SDN controller, so that the SDN controller determines a target port of the target access device, and issues the tenant network configuration to the target access device.

[0021] Optionally, the SDN controller configures a management IP address for one access device, manages the access device, and instructs the access device to carry the management IP address of the access device in an LLDP packet when the access device interacts with the bare metal server.

[0022] Optionally, the target bare metal server acquires an initial image through an inspector network after power-on, wherein the initial image comprises a proxy program for collecting hardware information and access location information of the bare metal server; the target bare metal server runs the initial image, learns bridge MAC, management IP address and port information of the target access device by interacting with the target access device through an LLDP packet.

[0023] When acquiring the hardware information and the access location information of the target bare metal server, the acquisition unit is specifically configured to:

[0024] The proxy program is used to acquire the hardware information of the target bare metal server and the bridge MAC, the management IP address and the port information of the target access device.

[0025] Optionally, if the target access device fails, the target access device is replaced by another access device, the replaced access device is consistent with the physical connection of the target access device, and the replaced access device inherits the management IP address of the target access device; the notification unit is further configured to:

[0026] obtain target management IP address and target interface information of the target access device from the database, and notify the target management IP address, target port information and tenant network configuration to the SDN controller, so that the SDN controller determines the port of the replaced access device, and distributes the tenant network configuration to the replaced access device.

[0027] In a third aspect, an embodiment of the present application provides a bare metal server deployment device, which comprises:

[0028] a memory configured to store program instructions;

[0029] a processor configured to invoke the program instructions stored in the memory and execute the steps of the method according to any one of the first aspect.

[0030] In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium, which stores computer executable instructions for causing a computer to execute the steps of the method according to any one of the first aspect.

[0031] In summary, the bare metal server deployment method provided by the embodiments of the present application is applied to a cloud platform control device, and comprises: obtaining hardware information and access location information of a target bare metal server, and storing the obtained access location information in a database, wherein the access location information of one bare metal server comprises management IP address and port information of an access device to which the bare metal server accesses; if the target bare metal server is allocated to a tenant based on a tenant request, creating a provision network and a tenant network corresponding to the target bare metal server; determining target management IP address and target port information of a target access device to which the target bare metal server accesses, and determining tenant network configuration corresponding to the tenant; notifying the target management IP address, target port information and tenant network configuration to an SDN controller, so that the SDN controller determines a target port of the target access device, and distributes the tenant network configuration to the target access device.

[0032] By using the bare metal server deployment method provided by the embodiments of the present application, when a bare metal server is deployed, the management IP address of the access device where each bare metal server is located is maintained, the cloud platform and the controller locate the access device by using the learned management IP address, and then distribute network configuration, thereby supporting the problem that the bare metal server can be repeatedly online and offline after device failure replacement. BRIEF DESCRIPTION OF DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the present application or the prior art. Obviously, the drawings in the following description are only some embodiments described in the present application, and other drawings can also be obtained by those skilled in the art according to these drawings of the embodiments of the present application.

[0034] Figure 1 A detailed flowchart of a bare metal server deployment method provided by the embodiments of the present application;

[0035] Figure 2 An EVPN networking schematic diagram provided by the embodiments of the present application;

[0036] Figure 3 A structural schematic diagram of a bare metal server deployment device provided by the embodiments of the present application;

[0037] Figure 4 A hardware architecture schematic diagram of a bare metal server deployment device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0038] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "an" and "the" used in the present application and claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein means any or all possible combinations of one or more associated listed items.

[0039] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, the first information can also be referred to as the second information without departing from the scope of the present application, and similarly, the second information can also be referred to as the first information. In addition, depending on the context, the word "if" used can be interpreted as "when" or "upon" or "in response to determining".

[0040] In actual application, when the bare metal has passed the cloud entry inspector stage, the device is replaced by a new device due to failure, the bridge MAC of the new device is not the same as the bridge MAC of the original failed device; the bare metal cannot update the host information of itself to the bare metal management node; at this time, if the bare metal is offline or online again, the network configuration of the network element access device cannot be normally updated, because the controller cannot locate the new network element access device according to the original bridge MAC.

[0041] In the related art, in order to solve the above problems, after the replacement of the faulty device is completed on the controller, the bridge MAC address of the original faulty device is configured on the new network element access device. In this way, the original bridge MAC needs to be configured on the new device, which depends on the device having the ability to support the configuration or modification of the bridge MAC, and additional operations are added; in addition, after the faulty device is repaired, it cannot be directly managed because the same bridge MAC will cause the same Datapath ID of the Openflow connection, which will cause a conflict of multiple devices corresponding to the same Datapath ID, and increase the complexity of management.

[0042] In order to solve the problem that under the EVPN networking, the bare metal has gone through the Inspector stage, and the bridge MAC address learned by the cloud platform cannot be updated, the cloud platform locates the access device through the bridge MAC, when the access device is replaced due to failure, the bridge MAC changes, and the controller no longer has the information of the original faulty device, resulting in the problem that the bare metal cannot be online and offline again, the embodiment of the application provides a bare metal server deployment method, so that the access device can continue to support the online and offline of the bare metal server after the replacement of the faulty device.

[0043] For example, referring to Figure 1 As shown in the detailed flowchart of the bare metal server deployment method provided by the embodiment of the application, the method is applied to a cloud platform control device, and the method comprises the following steps:

[0044] Step 100: Obtain the hardware information and access location information of the target bare metal server, and store the obtained access location information in the database.

[0045] The access location information of a bare metal server comprises the management IP address and port information of the access device to which the bare metal server is connected.

[0046] In the embodiment of the application, the SDN controller configures a management IP address for an access device, manages the access device, and instructs the access device to carry the management IP address of the access device in the LLDP message when interacting with the bare metal server.

[0047] That is, when managing any access device, the controller issues a configuration to the access device through netconf, instructs the access device to allow the publication of the management address in the LLDP message, and configures the published management address. The management IP address published by the LLDP is the same as the IP address of the access device managed by the controller. IPv4 and IPv6 are supported, and the controller supports on-demand issuance according to user intention.

[0048] In the embodiment of the present application, the target bare metal server obtains an initial image through an inspector network after power-on, wherein the initial image includes an agent program for collecting hardware information and access location information of the bare metal server; the target bare metal server runs the initial image, and learns bridge MAC, management IP address and port information of the target access device by interacting with the target access device through LLDP messages.

[0049] Therefore, when obtaining the hardware information and the access location information of the target bare metal server, a preferred implementation manner is to obtain the hardware information of the target bare metal server and the bridge MAC, management IP address and port information of the target access device through the agent program.

[0050] In actual application, when the bare metal server starts to enter the cloud, the bare metal server obtains an initial image through an inspector network after power-on. The process can be divided into two steps: 1. sending a DHCP message to the inspector tftp to obtain an IP address and a tftp server address of the initial image; 2. downloading the initial image to the inspector tftp through the tftp protocol. The inspector network is pre-configured to be pulled through a controller. The initial image includes an Ironic Python Agent agent program for collecting hardware information and LLDP data of the bare metal server. The bare metal server runs the initial image, and learns bridge MAC, management IP address and port information of the access device where the bare metal server is located by interacting with the access device through LLDP messages.

[0051] In the embodiment of the present application, an agent program for collecting hardware information of the bare metal server and location information of the access device where the bare metal server is currently accessed is added in the initial image. For example, after the bare metal server accesses an access device, the bare metal server interacts with the access device through LLDP messages. The access device sends its own information (access device location information, such as management IP address) in the LLDP message to the bare metal server. The bare metal server parses the LLDP message to obtain LLDP data (access device location information). Then, the bare metal server interacts with the cloud platform controller. The cloud platform controller obtains the hardware information of the bare metal server and the access location information (at least including management IP address of the access device and port information of the access device where the bare metal server is accessed) through the agent program.

[0052] Of course, the cloud platform controller can also obtain the LLDP message sent by the access device from the bare metal server through the agent program, and then parse the LLDP message to obtain bridge MAC, management IP address and port information, and write the information into a local neutron database.

[0053] Specifically, the Ironic Inspector service in the cloud platform obtains hardware information of the bare metal server and access location information of the bare metal server from the Ironic Python Agent module through the management network, wherein the access location information includes bridge MAC, management IP address and port information of an access device where the bare metal server is located, and is written into a neutron database. Since the management IP address belongs to an optional field of LLDP, the current Openstack does not perform parsing and writing into the neutron database, therefore, an Ironic plug-in needs to be added on the cloud platform control device, which is used to judge and parse the management IP address, and write into the neutron database.

[0054] Step 110: If the target bare metal server is allocated to the tenant based on the tenant request, creating a provision network and a tenant network corresponding to the target bare metal server.

[0055] Specifically, the tenant can apply for a bare metal server resource through the cloud platform, and the cloud platform allocates a bare metal resource to the tenant according to the tenant application, and sequentially creates a provision network and a tenant network, wherein the provision network is used to download a bare metal service image.

[0056] Step 120: Determining a target management IP address and target port information of a target access device accessed by the target bare metal server, and determining a tenant network configuration corresponding to the tenant.

[0057] In actual application, the cloud platform is preset with tenant network configurations corresponding to each tenant, such as configuration of an access device and port configuration of the access device.

[0058] Step 130: Notifying the target management IP address, target port information and tenant network configuration to an SDN controller, so that the SDN controller determines a target port of the target access device, and issues the tenant network configuration to the target access device.

[0059] Specifically, the cloud platform notifies the SDN controller of access information and logical network information of the access device where the bare metal server is located through a controller plug-in, wherein the access information includes bridge MAC, management IP address and port information of the access device, and the logical network (tenant network) information includes vlan id and vxlan id information. After receiving the notification information from the cloud platform, the SDN controller parses the management IP address from the request body, finds the corresponding access device according to the management IP address, and then issues vlan-vxlan mapping configuration on the corresponding port of the access device through netconf, so that the bare metal server can access the Provision network and the tenant network.

[0060] In the embodiment of the present application, if the target access device fails, the target access device is replaced by another access device, and the physical connection of the replaced access device is consistent with that of the target access device, and the replaced access device inherits the management IP address of the target access device; the method further comprises the following steps:

[0061] The target management IP address and target interface information of the target access device are obtained from the database, and the target management IP address, target port information and tenant network configuration are notified to the SDN controller, so that the SDN controller determines the port of the replaced access device and issues the tenant network configuration to the replaced access device.

[0062] In actual application, it is assumed that after the access device A fails, device replacement is needed, which is divided into two steps, 1, removing the failed device and accessing the new device C, while maintaining the original physical connection mode, 2, using the device backup file of the access device A to replace the failed device A with the new device C on the controller, so that the configuration (management IP address) on the device A is inherited by the device C, including the configuration of allowing the management address to be published in the LLDP packet.

[0063] In this way, the cloud platform control device can notify the SDN controller of the management IP address, port information and tenant network configuration, so that the SDN controller finds the replaced device C based on the management IP address, and then issues the tenant network configuration to the device C, so that both the already accessed bare metal server and the newly accessed bare metal server can be normally online on the cloud platform.

[0064] The bare metal server deployment method provided by the embodiment of the present application will be described in detail in combination with a specific application scenario. For example, refer to Figure 2As shown, an EVPN networking schematic diagram provided by the embodiment of the application is shown, wherein Leaf-A and Leaf-B are EVPN distributed gateway devices (access devices). Leaf-A is a faulty device, and Leaf-C is a replacement device. The spine is a BGP RR device, responsible for establishing a BGP neighbor with all Leaf devices and reflecting EVPN routes. The ironic sever is a bare metal server, providing high-performance dedicated physical computing resources for tenants. The SDN controller provides a northbound RestAPI interface for the cloud platform, responsible for unified management of physical device resources and network deployment in three stages of the online bare metal server. The cloud platform control node is an entrance for managing the bare metal resource pool and allocating bare metal resources for tenants. The cloud platform control node is deployed with an inspector tftp, a provision ironic tftp service, wherein the inspector tftp is responsible for providing a bare metal inspector stage DHCP and initial image download service, the network node is responsible for providing a bare metal Provision stage DHCP service, and the provision ironic tftp is responsible for providing a bare metal service image download service.

[0065] The cloud platform control node is deployed with a newly added custom plug-in (Ironic plug-in) for analyzing management IP address information, which is written into the Neutron database together with port information and bare metal logical port information.

[0066] When the Neutron plug-in issues a logical network opening request to the SDN controller through the plug-in, the management IP and port information need to be read from the Neutron database, and the logical vxlan and vlan information are converted into RestAPI interface parameters provided by the controller.

[0067] When the SDN controller receives a RestAPI request for opening a logical network of a bare metal server, the management IP address information is parsed from the request body, the corresponding access device is found according to the management IP address information, and the logical network opening configuration is issued to the access device through Netconf.

[0068] For the convenience of understanding the embodiment of the application, the main process of the system is described, and the corresponding Figure 2 number is marked in the description:

[0069] 1. Leaf-A is activated, and the SDN controller issues a configuration according to user configuration, instructing the access device to allow publishing a management address in an LLDP packet and configuring the published management address

[0070] 2, Ironic server power-on to obtain deployment image and Ironic Python Agent, get LLDP packet from Leaf-A, and learn the management IP address and port information of Leaf-A device.

[0071] 3, Ironic obtains Inspector information including LLDP information from Irnoic Python Agent through restAPI. Irnoic plug-in is responsible for parsing management IP address information and writing into Neutron database.

[0072] 4, When Neutron opens logical network for bare metal, read management IP address and other information from neutron database, and adapt and convert according to northbound RestAPI interface provided by SDN controller, call northbound restAPI interface provided by SDN controller, and open logical network.

[0073] 5, After the SDN controller receives the restAPI request, read the management IP address information from the request, locate to the specified network element device, and download network opening configuration through netconf according to physical port, vxlan and vlan information.

[0074] By the above method, after the access device is replaced due to fault, the bare metal server can still be repeatedly online and offline, and the problem that the bare metal server cannot be normally offline and reconnected after the access device is replaced due to fault is avoided.

[0075] For example, refer to Figure 3 As shown in the figure, a structure schematic diagram of a bare metal server deployment device provided by the embodiment of the application is provided, the device is applied to a cloud platform control device, and the device comprises:

[0076] The acquisition unit 30 is configured to acquire hardware information and access position information of a target bare metal server, and store the acquired access position information into a database, wherein the access position information of one bare metal server comprises management IP address and port information of an access device accessed by the bare metal server.

[0077] The creation unit 31 is configured to, if the target bare metal server is allocated to a tenant based on a tenant request, create a provision network and a tenant network corresponding to the target bare metal server.

[0078] The determination unit 32 is configured to determine target management IP address and target port information of a target access device accessed by the target bare metal server, and determine tenant network configuration corresponding to the tenant.

[0079] The notification unit 33 is configured to notify the target management IP address, the target port information and the tenant network configuration to the SDN controller, so that the SDN controller determines the target port of the target access device and issues the tenant network configuration to the target access device.

[0080] Optionally, the SDN controller configures a management IP address for an access device, manages the access device, and instructs the access device to carry the management IP address of the access device in the LLDP packet when interacting with the bare metal server.

[0081] Optionally, the target bare metal server obtains an initial image through the inspector network after power-on, wherein the initial image includes an agent for collecting hardware information and access location information of the bare metal server; the target bare metal server runs the initial image, and learns the bridge MAC, the management IP address and the port information of the target access device by interacting with the target access device through the LLDP packet.

[0082] When obtaining the hardware information and the access location information of the target bare metal server, the obtaining unit 30 is specifically configured to:

[0083] The agent is used to obtain the hardware information of the target bare metal server and the bridge MAC, the management IP address and the port information of the target access device.

[0084] Optionally, if the target access device fails, the target access device is replaced by another access device, the physical connection of the replaced access device is consistent with that of the target access device, and the replaced access device inherits the management IP address of the target access device; the notification unit 33 is further configured to:

[0085] The target management IP address and the target interface information of the target access device are obtained from the database, and the target management IP address, the target port information and the tenant network configuration are notified to the SDN controller, so that the SDN controller determines the port of the replaced access device and issues the tenant network configuration to the replaced access device.

[0086] The above units can be one or more inherited circuits configured to implement the above method, for example: one or more Application Specific Integrated Circuits (ASICs), or one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), etc. For example, when a certain unit above is implemented in the form of a processing element scheduling code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can call program code. For example, these units can be inherited together to implement in the form of a system-on-a-chip (SOC).

[0087] Further, the bare metal server deployment apparatus provided by the embodiment of the present application, from the hardware level, the hardware architecture diagram of the bare metal server deployment apparatus can be seen from Figure 4 As shown, the bare metal server deployment apparatus can include a memory 40 and a processor 41,

[0088] The memory 40 is used to store program instructions; the processor 41 calls the program instructions stored in the memory 40, and executes the above method embodiments according to the obtained program instructions. The specific implementation and technical effects are similar, and will not be repeated here.

[0089] Optionally, the present application also provides a cloud platform control device, comprising at least one processing element (or chip) for executing the above method embodiments.

[0090] Optionally, the present application also provides a program product, for example, a computer readable storage medium, which stores computer executable instructions for causing the computer to execute the above method embodiments.

[0091] Here, the machine readable storage medium can be any electronic, magnetic, optical or other physical storage device, which can contain or store information, such as executable instructions, data, etc. For example, the machine readable storage medium can be: RAM (Radom Access Memory, Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state disk, any type of storage disk (such as optical disk, dvd, etc.), or similar storage medium, or combination thereof.

[0092] The systems, apparatuses, modules, or units disclosed in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0093] For the sake of clarity, the above apparatuses are described with reference to functional divisions into various units. Of course, the functions of the units can be implemented in one or more software and / or hardware in implementing the present application.

[0094] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0095] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce the functions described in the flowcharts and / or block diagrams for implementing the flows and / or blocks in the flowcharts and / or block diagrams. Figure 1 The functions specified in the flow or flows and / or blocks Figure 1 The apparatus that performs the functions specified in the flow or flows and / or blocks.

[0096] Moreover, these computer program instructions can also be stored in a computer readable memory capable of directing the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer readable memory produce the manufactured product including the instruction apparatus, which implements the flows and / or blocks in the flowcharts and / or block diagrams. Figure 1 The functions specified in the flow or flows and / or blocks Figure 1 The apparatus that performs the functions specified in the flow or flows and / or blocks.

[0097] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operation steps are performed on the computer or other programmable data processing devices to generate computer-implemented processes, thus the instructions executed on the computer or other programmable data processing devices provide processes for implementing the functions specified in the flow Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0098] The above only the preferred embodiment of the present application, and not to limit the present application, any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application, should be included within the scope of the present application.

Claims

1. A method for deploying a bare-metal server, characterized in that, The method, applied to cloud platform control devices, includes: Obtain the hardware information and access location information of the target bare metal server, and store the obtained access location information in the database. The access location information of a bare metal server includes the management IP address and port information of the access device to which the bare metal server is connected. If the target bare metal server is allocated to the tenant based on the tenant's request, then the provision network and tenant network corresponding to the target bare metal server are created; Determine the target management IP address and target port information of the target access device to which the target bare metal server is connected, and determine the tenant network configuration corresponding to the tenant; The target management IP address, target port information, and tenant network configuration are notified to the SDN controller, so that the SDN controller can determine the target port of the target access device and send the tenant network configuration to the target access device.

2. The method as described in claim 1, characterized in that, The SDN controller configures a management IP address for an access device, manages the access device, and instructs the access device to include its management IP address in LLDP messages when interacting with the bare metal server.

3. The method as described in claim 1, characterized in that, After power-on, the target bare metal server obtains an initial image through the inspector network. The initial image includes a proxy program for collecting hardware information and access location information of the bare metal server. The target bare metal server runs the initial image and learns the bridge MAC, management IP address, and port information of the target access device by exchanging LLDP messages with the target access device. The steps to obtain the hardware information and access location information of the target bare metal server include: The proxy program obtains the hardware information of the target bare metal server and the bridge MAC address, management IP address, and port information of the target access device.

4. The method according to any one of claims 1-3, characterized in that, If the target access device fails, it is replaced with another access device, and the physical connection of the replaced access device is consistent with that of the target access device. The replaced access device inherits the management IP address of the target access device. The method further includes: The target management IP address and target interface information of the target access device are obtained from the database, and the target management IP address, target port information and tenant network configuration are notified to the SDN controller so that the SDN controller can determine the port of the replacement access device and send the tenant network configuration to the replacement access device.

5. A bare-metal server deployment device, characterized in that, The device is used in cloud platform control equipment and includes: The acquisition unit is used to acquire the hardware information and access location information of the target bare metal server, and store the acquired access location information in the database. The access location information of a bare metal server includes the management IP address and port information of the access device to which the bare metal server is connected. If the creation unit allocates the target bare metal server to the tenant based on the tenant's request, then the creation unit is used to create the provision network and tenant network corresponding to the target bare metal server; The determining unit is used to determine the target management IP address and target port information of the target access device to which the target bare metal server is connected, and to determine the tenant network configuration corresponding to the tenant; The notification unit is used to notify the SDN controller of the target management IP address, target port information and tenant network configuration, so that the SDN controller can determine the target port of the target access device and send the tenant network configuration to the target access device.

6. The apparatus as claimed in claim 5, characterized in that, The SDN controller configures a management IP address for an access device, manages the access device, and instructs the access device to include its management IP address in LLDP messages when interacting with the bare metal server.

7. The apparatus as claimed in claim 5, characterized in that, After power-on, the target bare metal server obtains an initial image through the inspector network. The initial image includes a proxy program for collecting hardware information and access location information of the bare metal server. The target bare metal server runs the initial image and learns the bridge MAC, management IP address, and port information of the target access device by exchanging LLDP messages with the target access device. When acquiring the hardware information and access location information of the target bare metal server, the acquisition unit is specifically used for: The proxy program obtains the hardware information of the target bare metal server and the bridge MAC address, management IP address, and port information of the target access device.

8. The apparatus according to any one of claims 5-7, characterized in that, If the target access device fails, it is replaced with another access device, and the physical connection of the replaced access device is consistent with that of the target access device. The replaced access device inherits the management IP address of the target access device. The notification unit is also used for: The target management IP address and target interface information of the target access device are obtained from the database, and the target management IP address, target port information and tenant network configuration are notified to the SDN controller so that the SDN controller can determine the port of the replacement access device and send the tenant network configuration to the replacement access device.

9. A bare-metal server deployment device, characterized in that, The device includes: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of claims 1-4 according to the obtained program instructions.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing the computer to perform the steps of the method as described in any one of claims 1-4.

Images