CN116668277A - Bare metal server deployment method and device - Google Patents

Bare metal server deployment method and device Download PDF

Info

Publication number
CN116668277A
CN116668277A CN202310526693.7A CN202310526693A CN116668277A CN 116668277 A CN116668277 A CN 116668277A CN 202310526693 A CN202310526693 A CN 202310526693A CN 116668277 A CN116668277 A CN 116668277A
Authority
CN
China
Prior art keywords
target
bare metal
access device
metal server
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310526693.7A
Other languages
Chinese (zh)
Inventor
黄云丰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN202310526693.7A priority Critical patent/CN116668277A/en
Publication of CN116668277A publication Critical patent/CN116668277A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

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 cloud platform control equipment, and comprises the following steps: acquiring 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 access equipment where the target bare metal server is located; distributing a target bare metal server for a tenant, and creating a corresponding provision network and a tenant network; determining target management IP and target port information of target access equipment accessed by a target bare metal server, and determining tenant network configuration corresponding to a tenant; and notifying the target management IP, 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.

Description

Bare metal server deployment method and device
Technical Field
The application relates to the technical field of network communication, in particular to a bare metal server deployment method and device.
Background
The bare metal server (Bare Metal Server) is a physical server, for short, BMS. Bare metal server deployment is divided into three phases, with an in-cloud phase (instrumentation): after the bare metal server is accessed to the network, the PXE is used for starting and loading a starting mirror image, and host information of the bare metal server is reported to the management node, so that the bare metal server enters a schedulable state. The Injector stage completes the collection of the OpenStack on the hardware information of the accessed physical server, and the management node can create a corresponding 'instance type' according to the collected configuration information, so that the physical server is conveniently scheduled and designated to create a bare metal instance according to the resource application requirements of users; deployment phase (provisioning): the tenant applies for bare metal resources to the cloud platform, the cloud platform starts the selected server, starts up the mirror image through PXE starting loading, and then deploys the system mirror image to complete the installation of the bare metal server operating system; run phase (Running): the server restarts to load the operating system, acquires the IP address through the DHCP, and completes the deployment of the bare metal instance.
When the bare metal server has passed through the cloud entering stage entity, if the network element access equipment of the bare metal server is replaced by a new equipment due to a fault, the MAC of the new equipment bridge is different from the MAC of the original fault equipment bridge; then, the bare metal server can not update its own host information to the management node any more; at this time, if the bare metal is off-line or on-line again, the network configuration of the network element access device cannot be updated normally, because the controller cannot locate the new network element access device according to the original bridge MAC.
Disclosure of Invention
The application provides a bare metal server deployment method and device.
In a first aspect, the present application provides a bare metal server deployment method, applied to a cloud platform control device, the method comprising:
acquiring hardware information and access position information of a target bare metal server, and storing the acquired access position information into a database, wherein the access position information of one bare metal server comprises a management IP address and port information of access equipment accessed by the bare metal server;
if the target bare metal server is distributed for the tenant based on the tenant request, creating a program network and a tenant network corresponding to the target bare metal server;
determining target management IP address and target port information of target access equipment accessed by the target bare metal server, and determining tenant network configuration corresponding to the tenant;
and notifying 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.
Optionally, the SDN controller configures a management IP address for an access device, and manages the access device, and instructs the access device to carry the management IP address of the access device in an LLDP packet when interacting with the bare metal server.
Optionally, after the target bare metal server is powered on and started, acquiring an initial image through an insactor network, wherein the initial image comprises an agent program for collecting hardware information and access position information of the bare metal server; the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment through interacting LLDP messages with the target access equipment;
the step of obtaining the hardware information and the access position information of the target bare metal server comprises the following steps:
and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
Optionally, if the target access device fails, replacing the target access device with other access devices, where the replaced access device is consistent with the physical connection line 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 steps of:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
In a second aspect, the present application provides a bare metal server deployment apparatus applied to a cloud platform control device, the apparatus comprising:
the system comprises an acquisition unit, a database and a control unit, wherein the acquisition unit is used for acquiring hardware information and access position information of a target bare metal server and storing the acquired access position information into the database, wherein the access position information of one bare metal server comprises a management IP address and port information of access equipment accessed by the bare metal server;
the creating unit is used for creating a program network and a tenant network corresponding to the target bare metal server if the target bare metal server is distributed to the tenant based on the tenant request;
a determining unit, configured to 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;
and the notification unit is used for notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the target port of the target access equipment and issues the tenant network configuration to the target access equipment.
Optionally, the SDN controller configures a management IP address for an access device, and manages the access device, and instructs the access device to carry the management IP address of the access device in an LLDP packet when interacting with the bare metal server.
Optionally, after the target bare metal server is powered on and started, acquiring an initial image through an insactor network, wherein the initial image comprises an agent program for collecting hardware information and access position information of the bare metal server; the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment through interacting LLDP messages with the target access equipment;
when acquiring the hardware information and the access position information of the target bare metal server, the acquiring unit is specifically configured to:
and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
Optionally, if the target access device fails, replacing the target access device with other access devices, where the replaced access device is consistent with the physical connection line 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:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
In a third aspect, an embodiment of the present application provides a bare metal server deployment apparatus, including:
a memory for storing program instructions;
a processor for invoking program instructions stored in said memory, performing the steps of the method according to any of the first aspects above in accordance with the obtained program instructions.
In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method according to any one of the first aspects.
As can be seen from the foregoing, the bare metal server deployment method provided by the embodiment of the present application is applied to a cloud platform control device, and the method includes: acquiring hardware information and access position information of a target bare metal server, and storing the acquired access position information into a database, wherein the access position information of one bare metal server comprises a management IP address and port information of access equipment accessed by the bare metal server; if the target bare metal server is distributed for the tenant based on the tenant request, creating a program network and a tenant network corresponding to the target bare metal server; determining target management IP address and target port information of target access equipment accessed by the target bare metal server, and determining tenant network configuration corresponding to the tenant; and notifying 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.
By adopting the bare metal server deployment method provided by the embodiment of the application, when the bare metal servers are deployed, the cloud platform and the controller position the access equipment by maintaining the management IP address of the access equipment where each bare metal server is located, and then issue network configuration by using the learned management IP address, so that the problem that the bare metal server can be repeatedly connected to the Internet and disconnected after equipment fault replacement is supported.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly describe the drawings required to be used in the embodiments of the present application or the description in the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings of the embodiments of the present application for a person having ordinary skill in the art.
FIG. 1 is a detailed flowchart of a bare metal server deployment method according to an embodiment of the present application;
fig. 2 is a schematic diagram of EVPN networking according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a bare metal server deployment device according to an embodiment of the present application;
fig. 4 is a schematic hardware architecture diagram of a bare metal server deployment device according to an embodiment of the present application.
Detailed Description
The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in 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 one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".
In practical application, when bare metal has passed through the cloud insactor stage, the equipment is replaced by a new equipment due to the fault, and the MAC of the new equipment bridge is different from the MAC of the original fault equipment bridge; the bare metal can not update own host information to the bare metal management node any more; at this time, if the bare metal is off-line or on-line again, the network configuration of the network element access device cannot be updated normally, because the controller cannot locate the new network element access device according to the original bridge MAC.
In the related art, in order to solve the above-mentioned problem, after the replacement of the failed device is performed on the controller, the bridge MAC address is configured on the new network element access device as the bridge MAC of the original failed device. Thus, the original bridge MAC needs to be configured on the new device, which depends on the device having the capability of supporting configuration or modification of the bridge MAC, and additional operations are added; in addition, the fault equipment cannot be directly managed after repair, because the bridge MAC is the same, the unique identifier Datapath ID of the Openflow connection is the same, the conflict that the same Datapath ID corresponds to a plurality of equipment can be caused, and the complexity in management is increased.
In order to solve the problem that under EVPN networking, bare metal cannot be on-line again due to the fact that the bare metal passes through an indicator stage, a bridge MAC address which is learned on a cloud platform cannot be updated, the cloud platform is positioned to an access device through the bridge MAC, after the access device is replaced by faults, the bridge MAC changes, and the controller has no original fault device information, the bare metal cannot be on-line and off-line again.
Exemplary, referring to fig. 1, a detailed flowchart of a bare metal server deployment method according to an embodiment of the present application is shown, where the method is applied to a cloud platform control device, and the method includes the following steps:
step 100: and acquiring the hardware information and the access position information of the target bare metal server, and storing the acquired access position information into a database.
The access position information of one bare metal server comprises the management IP address and port information of the access equipment accessed by the bare metal server.
In the embodiment of the application, the SDN controller configures a management IP address for an access device, manages the access device, and indicates the access device to carry the management IP address of the access device in an LLDP message when interacting with a bare metal server.
That is, when any access device is managed by the controller, the controller issues a configuration to the access device through netconf, instructs the access device to allow the management address to be issued in the LLDP message, and configures the issued management address, where the management IP address issued by the LLDP is the same as the IP address of the access device managed by the controller. Both IPv4 and IPv6 are supported, and the controller supports on-demand delivery as intended by the user.
In the embodiment of the application, after the power-on starting, a target bare metal server acquires an initial mirror image through an insactor network, wherein the initial mirror image comprises an agent program for collecting hardware information and access position information of the bare metal server; and the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment by interacting an LLDP message with the target access equipment.
Then, when acquiring the hardware information and the access location information of the target bare metal server, one preferred implementation is: and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
In practical application, when the bare metal server is started to enter the cloud, after the bare metal server is powered on and started, an initial mirror image is obtained through an insactor network. The process can be divided into two steps, 1, sending a DHCP message to an entity tftp to obtain an IP address and an initial mirrored tftp server address; 2. the initial image is downloaded to the insactor tftp via the tftp protocol. The insactor network is pre-configured to pull through by the controller. The initial image contains Ironic Python Agent agent program for collecting hardware information and LLDP data of bare metal server. The bare metal server runs the initial mirror image, and learns the bridge MAC, the management IP address and the port information of the access device where the bare metal server is located through interaction of the LLDP message with the access device.
In the embodiment of the present application, an agent for collecting hardware information of a bare metal server and location information of an access device to which bare metal is currently connected is added to an initial mirror image, for example, after the bare metal server accesses an access device, performing an LLDP message Wen Jiaohu with the access device, the access device carries information (access device location information, for example, a management IP address) of itself in the LLDP message and sends the LLDP message to the bare metal server, and 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, and the cloud platform controller obtains the hardware information and the access position information (at least including the management IP address of the access device and the port information of the access device for accessing the bare metal server) of the bare metal server through the agent program.
Of course, the cloud platform controller may also obtain, through the agent, the LLDP packet sent by the access device from the bare metal server, then parse the LLDP packet to obtain the bridge MAC, manage the IP address, port information, and write the port information into the local neutron database.
Specifically, an infrared indicator service in the cloud platform acquires hardware information and access position information of the bare metal server from a Ironic Python Agent module through a management network, wherein the access position information comprises bridge MAC, management IP address and port information of access equipment where the bare metal server is located, and writes the information into a neutron database. Because the management IP address belongs to the LLDP optional field, the current Openstack does not perform the operations of resolving and writing into the neutron database, and therefore, an Ironic plug-in needs to be newly added on the cloud platform control device to determine and resolve the management IP address in the process and write into the neutron database.
Step 110: and if the target bare metal server is distributed for the tenant based on the tenant request, creating a program network and a tenant network corresponding to the target bare metal server.
Specifically, the tenant may apply for the bare metal server resource through the cloud platform, and the cloud platform allocates the bare metal resource to the tenant according to the tenant application, and sequentially creates a provisioning network and a tenant network, where the provisioning network is used to download the bare metal service image.
Step 120: and determining target management IP address and target port information of target access equipment accessed by the target bare metal server, and determining tenant network configuration corresponding to the tenant.
In practical application, tenant network configuration corresponding to each tenant, for example, configuration of an access device and port configuration of the access device, is preset in the cloud platform.
Step 130: and notifying 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.
Specifically, the cloud platform informs the SDN controller of the access information and the logical network information allocated to the access device where the bare metal server is located through the controller plug-in, 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 cloud platform notification information, the SDN controller analyzes the management IP address from the request body, searches the corresponding access device according to the management IP address, and then issues vlan-vxlan mapping configuration for the access device on the corresponding port through netconf, so that the bare metal server can access the provisioning network and the tenant network.
In the embodiment of the application, if the target access equipment fails, the target access equipment is replaced by other access equipment, and the replaced access equipment is consistent with the physical connection line of the target access equipment, and inherits the management IP address of the target access equipment; the method further comprises the steps of:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
In practical application, it is assumed that after the failure of the access device a occurs, the device replacement needs to be performed, and the method is divided into two steps, 1, the failed device is removed and accessed by a new device C, and meanwhile, the original physical connection mode is maintained, 2, the device backup file of the access device a is operated on the controller to replace the failed device a with the new device C, so that the configuration (management IP address) on the device a can be inherited by the device C, including the configuration issued to allow the management address to be issued in the LLDP message.
In this way, the cloud platform control device may notify the SDN controller of the network configuration of the tenant based on the management IP address, the port information, and the management IP address, so that the SDN controller finds a device C after replacement based on the management IP address, and then issues the network configuration of the tenant to the device C, so that the SDN controller can normally go online and offline regardless of whether it is an already accessed bare metal server or a newly accessed bare metal server.
The bare metal server deployment method provided by the embodiment of the application is described in detail below in connection with a specific application scenario. Exemplary, referring to fig. 2, an EVPN networking schematic is provided according to an embodiment of the present application, where Leaf-A, leaf-B is an EVPN distributed gateway device (access device). Leaf-A is the failed device and Leaf-C is the replacement device. The Spine is a BGP RR device responsible for establishing BGP neighbors with all Leaf devices and reflecting EVPN routes. The Ironic server is a bare metal server, and provides high-performance exclusive physical computing resources for tenants. The SDN controller provides a northbound RestAPI interface for the cloud platform and is responsible for unified management of physical equipment resources, network deployment in three stages of online of a bare metal server and the like. And the cloud platform control node manages the bare metal resource pool and allocates an entrance of the bare metal resource for the tenant. And an inspecer tftp and Provision ironic tftp service is deployed on the cloud platform control node, wherein the inspecer tftp is responsible for providing a DHCP (dynamic host configuration protocol) service in a bare metal inspecer stage and an initial image downloading service, the network node is responsible for providing a DHCP service in a bare metal Provision stage, and Provision ironic tftp is responsible for providing a downloading service of a bare metal service image.
And a newly-added custom plug-in (Ironic plug-in) is deployed on the cloud platform control node and is used for analyzing and managing IP address information, and the information and the port information are written into a Neutron database together for the bare metal logical port.
When the plugin of the Neutron issues a logical network to the SDN controller, the plugin needs to read management IP and port information from a Neutron database and convert the management IP and port information and logical vxlan and vlan information into RestAPI interface parameters provided by the controller.
When the SDN controller receives a RestAPI request for opening the logic network of the bare metal server, management IP address information is analyzed from a request body, corresponding access equipment is found according to the management IP address information, and logic network opening configuration is issued to the access equipment through Netconf.
To facilitate understanding of the embodiments of the present application, a main flow of the system will be described, corresponding to the serial numbers noted in fig. 2:
1. leaf-a activation, SDN controller decides to issue configuration according to user configuration, instructs access device to allow issuing management address in LLDP message and configures issued management address
2. After the Ironic server is powered up to acquire the deployment image and Ironic Python Agent, an LLDP message is acquired from the Leaf-A, and the management IP address and port information of the Leaf-A device are learned.
3. The Ironic obtains the instrtor information from Irnoic Python Agent through the restAPI, containing LLDP information. The Irnoic plug-in is responsible for resolving and managing IP address information and writing the IP address information into a Neutron database.
4. When the Neutron opens the logic network for the bare metal, reading information such as a management IP address from a Neutron database, performing adaptive conversion according to a northbound RestAPI interface provided by the SDN controller, calling the northbound RestAPI interface provided by the SDN controller, and opening the logic network.
5. After receiving the restAPI request, the SDN controller reads the management IP address information from the request, positions the management IP address information to the appointed network element equipment, and issues network opening configuration through netconf according to the physical port, vxlan and vlan information.
By adopting the mode, the problem that the bare metal server can not normally be off line or be on line again after the fault replacement of the access equipment is avoided because the bare metal server can be on line and off line again after the fault replacement of the access equipment is solved.
Exemplary, referring to fig. 3, a schematic structural diagram of a bare metal server deployment device according to an embodiment of the present application is shown, where the device is applied to a cloud platform control apparatus, and the device includes:
an obtaining unit 30, configured to obtain hardware information and access location information of a target bare metal server, and store the obtained access location information in a database, where the access location information of one bare metal server includes a management IP address and port information of an access device to which the bare metal server is connected;
a creating unit 31, if the target bare metal server is allocated to the tenant based on the tenant request, the creating unit 31 is configured to create a provisioning network and a tenant network corresponding to the target bare metal server;
a determining unit 32, configured to 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;
a notifying unit 33, configured to notify the SDN controller of the target management IP address, the target port information and the tenant network configuration, 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.
Optionally, the SDN controller configures a management IP address for an access device, and manages the access device, and instructs the access device to carry the management IP address of the access device in an LLDP packet when interacting with the bare metal server.
Optionally, after the target bare metal server is powered on and started, acquiring an initial image through an insactor network, wherein the initial image comprises an agent program for collecting hardware information and access position information of the bare metal server; the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment through interacting LLDP messages with the target access equipment;
when acquiring the hardware information and the access location information of the target bare metal server, the acquiring unit 30 is specifically configured to:
and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
Optionally, if the target access device fails, replacing the target access device with other access devices, where the replaced access device is consistent with the physical connection line 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:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
These above units may be one or more inheritance circuits configured to implement the above methods, for example: one or more specific inheritance circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (digital singnal processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), etc. For another example, when a unit is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the units may be inherited together and implemented in the form of a system-on-a-chip (SOC).
Further, in the bare metal server deployment device provided by the embodiment of the present application, as for a hardware architecture schematic diagram of the bare metal server deployment device may be shown in fig. 4, the bare metal server deployment device may include: a memory 40 and a processor 41,
memory 40 is used to store program instructions; the processor 41 invokes the program instructions stored in the memory 40 to execute the above-described method embodiments in accordance with the obtained program instructions. The specific implementation manner and the technical effect are similar, and are not repeated here.
Optionally, the present application further provides a cloud platform control device, including at least one processing element (or chip) for executing the above method embodiment.
Alternatively, the application also provides a program product, such as a computer-readable storage medium, having stored thereon computer-executable instructions for causing a computer to perform the above-described method embodiments.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.

Claims (10)

1. A bare metal server deployment method, characterized by being applied to a cloud platform control device, the method comprising:
acquiring hardware information and access position information of a target bare metal server, and storing the acquired access position information into a database, wherein the access position information of one bare metal server comprises a management IP address and port information of access equipment accessed by the bare metal server;
if the target bare metal server is distributed for the tenant based on the tenant request, creating a program network and a tenant network corresponding to the target bare metal server;
determining target management IP address and target port information of target access equipment accessed by the target bare metal server, and determining tenant network configuration corresponding to the tenant;
and notifying 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.
2. The method of claim 1, wherein the SDN controller configures a management IP address for an access device and hosts the access device and instructs the access device to carry the management IP address of the access device in an LLDP message when interacting with a bare metal server.
3. The method of claim 1, wherein the target bare metal server obtains an initial image via an insactor network after power-up, wherein the initial image comprises an agent for collecting hardware information and access location information of the bare metal server; the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment through interacting LLDP messages with the target access equipment;
the step of obtaining the hardware information and the access position information of the target bare metal server comprises the following steps:
and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
4. A method according to any one of claims 1-3, wherein if the target access device fails, the target access device is replaced with another access device, and 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 method further comprises the steps of:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
5. A bare metal server deployment apparatus, characterized by being applied to a cloud platform control device, the apparatus comprising:
the system comprises an acquisition unit, a database and a control unit, wherein the acquisition unit is used for acquiring hardware information and access position information of a target bare metal server and storing the acquired access position information into the database, wherein the access position information of one bare metal server comprises a management IP address and port information of access equipment accessed by the bare metal server;
the creating unit is used for creating a program network and a tenant network corresponding to the target bare metal server if the target bare metal server is distributed to the tenant based on the tenant request;
a determining unit, configured to 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;
and the notification unit is used for notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the target port of the target access equipment and issues the tenant network configuration to the target access equipment.
6. The apparatus of claim 5, wherein the SDN controller configures a management IP address for an access device and hosts the access device and instructs the access device to carry the management IP address of the access device in an LLDP message when interacting with a bare metal server.
7. The apparatus of claim 5, wherein the target bare metal server obtains an initial image via an insactor network after power-up, wherein the initial image comprises an agent for collecting hardware information and access location information of the bare metal server; the target bare metal server runs an initial mirror image, and learns the bridge MAC, the management IP address and the port information of the target access equipment through interacting LLDP messages with the target access equipment;
when acquiring the hardware information and the access position information of the target bare metal server, the acquiring unit is specifically configured to:
and acquiring the hardware information of the target bare metal server and the bridge MAC of the target access equipment through the agent program, and managing the IP address and the port information.
8. The apparatus of any of claims 5-7, wherein if the target access device fails, the target access device is replaced with another access device, and the replaced access device is consistent with a physical connection of the target access device, and the replaced access device inherits a management IP address of the target access device; the notification unit is further configured to:
and acquiring the target management IP address and the target interface information of the target access device from a database, and notifying the SDN controller of the target management IP address, the target port information and the tenant network configuration, so that the SDN controller determines the port of the replaced access device, and issues the tenant network configuration to the replaced access device.
9. A bare metal server deployment apparatus, the apparatus comprising:
a memory for storing program instructions;
a processor for invoking program instructions stored in said memory and for performing the steps of the method according to any of claims 1-4 in accordance with the obtained program instructions.
10. A computer readable storage medium storing computer executable instructions for causing a computer to perform the steps of the method according to any one of claims 1-4.
CN202310526693.7A 2023-05-11 2023-05-11 Bare metal server deployment method and device Pending CN116668277A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310526693.7A CN116668277A (en) 2023-05-11 2023-05-11 Bare metal server deployment method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310526693.7A CN116668277A (en) 2023-05-11 2023-05-11 Bare metal server deployment method and device

Publications (1)

Publication Number Publication Date
CN116668277A true CN116668277A (en) 2023-08-29

Family

ID=87719773

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310526693.7A Pending CN116668277A (en) 2023-05-11 2023-05-11 Bare metal server deployment method and device

Country Status (1)

Country Link
CN (1) CN116668277A (en)

Similar Documents

Publication Publication Date Title
US10347542B2 (en) Client-initiated leader election in distributed client-server systems
US10091274B2 (en) Method, device, and system for controlling network device auto-provisioning
CN113015961A (en) Seamless automation of network device migration to and from a cloud management system
US11082505B2 (en) Dynamic discovery of available storage servers
CN110635987B (en) Message transmission method, device, equipment and machine readable storage medium
JP6466003B2 (en) Method and apparatus for VNF failover
EP3291499A1 (en) Method and apparatus for network service capacity expansion
CN107579900B (en) Method, device and system for accessing VX L AN network from V L AN network
CN109981493B (en) Method and device for configuring virtual machine network
US11177974B2 (en) Consistent provision of member node group information on virtual overlay network
CN103595801B (en) Cloud computing system and real-time monitoring method for virtual machine in cloud computing system
US9612924B1 (en) Fault tolerance in a distributed file system
CN113419815B (en) Method, system, equipment and medium for pre-starting operation environment installation
CN112688814B (en) Equipment access method, device, equipment and machine readable storage medium
CN114070723A (en) Virtual network configuration method and system of bare metal server and intelligent network card
CN110716787A (en) Container address setting method, apparatus, and computer-readable storage medium
CN112187958A (en) Method and device for registering, discovering and forwarding microservice
CN106657444A (en) Method and device for configuring IP address of BMC
US10282346B1 (en) Scalable network device self-configuration in large networks
US9716631B2 (en) End host physical connection on a switch port using multiple ethernet frames
US10931581B2 (en) MAC learning in a multiple virtual switch environment
US10033803B1 (en) Data volume auto-repair based on volume degradation level
US9417900B2 (en) Method and system for automatic assignment and preservation of network configuration for a virtual machine
CN116668277A (en) Bare metal server deployment method and device
US20220350632A1 (en) Automated referencing and resolution of properties across virtual network functions and network service

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination